I want to add usb network support to a real-time Linux distribution we're using at work. USB devices are recognized, but when connecting a usb network adapter no network interface is created.
I have given the task of writing a SDXC(32GB~2TB) driver for Kernel 2.6.24. I have following queries..
1> Does Linux Kernel 2.6.24 supports SDXC??? or SDHC(4GB ~ 32GB)..I know i surely supports SD...
If i need to modify the driver for SDXC what changes i need to do..Any pacthes are available?? which files need to be modified... whether driver/mmc/host/sdhci.c???
1> The SDIO host controller is implemented in FPGA in our board, & the Processor to FPGA interfacing is through PCIe.. I am not able to understand this interfacing.. what PCI related functions i need to use... I Have the Device ID & Vendor ID of Host controller...
For several months, I've had a couple problems with my X display. The first is an occasional seg fault that cascades thru all applications, leaving me with nothing, and requiring a reboot.The second is that all mozilla derived browsers -- firefox, epiphany, icecat -- crash very frequently. Sometimes this requires a reboot or restart of the display.Since I am not seeing complaints from other people about this for my distro (f14), but it did not happen on the same hardware with my previous install (f10), I'm putting it down to some combination of software.
My first suspect is the ati catalyst video driver. I don't use GL much, so I actually don't need the proprietary driver installed all the time. If it is the problem, I'd like to leave it installed for when I need it, but mostly use the kernel's native radeon driver.I had hoped this would be as simple as removing the fglrx driver and loading radeon, but that doesn't work -- when I start X again, the kernel loads fglrx. I changed the xorg conf to use the "ati" (xorg) driver; this leads to "no signal" to the monitor and I have to reboot.
A more comprehensive phrased question since I lost access to the other one.I would ask that the other one be deleted, not this one, as it should not have been migrated in the first place.There are currently two NTFS drivers available for Linux.
The NTFS driver included in the kernel, and the userspace NTFS-3G driver that makes use of FUSE.By all accounts, NTFS-3G works perfectly.My question then, is if the NTFS filesystem has been successfully reverse engineered, why have the kernel NTFS team not implemented the changes in their driver? At the moment it is still marked as experimental, and there is a good chance it will destroy your data.
I just updated an Ubuntu 10.04 kernel to 2.6.32-27-generic, and a wifi driver (r8187) is not present there. Is the only solution reinstalling it or is there a simple way to move it from an older kernel I have on the same machine?
About a month ago, I decided to go deeper in my Linux knowledge. I've been reading a lot and found out that Arch linux would be my learning distro. As I was installing Arch, it was a pain at first but I really learned a lot which I would never ever learn with Mint. Now I decided to take a step further is which "compiling your own kernel".
MY PROBLEM:
Everything was smooth in my Arch for a 2 weeks until I decided to compile my own kernel. I currently have a Nvidia GTX 460 1GB card.
BTW, the method I used to install nvidia with 2.6.37 was
Code: pacman -S nvidia nvidia-utils and that worked with all of the .37 kernels (-1 -2 -3 -4) which was download from kernel.org.
When I compiled the .38 (using the same .config of .37), it just boots up to the terminal (not loading gdm). However, I could still login by typing my username and password. So I've checked dmesg of both .37 and .38 and noticed that the Nvidia driver is not loaded in .38.
I tried reinstall it by running pacman and it doesn't do anything. It was thinking of uninstalling nvidia and nvidia-utils but there are so many dependencies conflicts (like screensaver, compiz, etc).
Since, I didn't want to mess up my .37 install, I just grabbed an old HDD and installed from scratch again. This time, I compiled the .38 kernel first (without gui) and then installed nvidia nvidia-utils. It was the same problem.
With this observation, I'm concluding that the nvidia and nvidia-utils from pacman is not compatible with .38.
I've read that I have to wait for nvidia to release a driver that will be compatible with the .38 kernel. Is that true? Does it mean I have to wait for nvidia/nvidia-utils to be updated from pacman? How would I know when it is updated?
I've also read about nouveau, but I guess that is not for me because it doesn't support 3D.
Is there a work around for me to use nvidia/nvidia-utils with .38?
Is nvidia and nvidia-utils proprietary drivers? What is the difference with these two and the one you download directly from nvidia?
First of all, I apologize for the bombardment of questions. As you can tell, I'm so clueless on how nvidia drivers work on linux in general (since it was spoon fed by mint) and I really would love to learn about this is a deeper level. Could someone please explain to me (LAYMANS terms) how nvidia works (and possibly a solution to my issue).
EDIT: Additional info - I have a netbook that also runs arch. It uses an Intel GMA integrated video chip which I used "xf86-video-intel" from pacman and I believe since it is open source, it works with .38 fine. So does that mean if you use an open source driver, it will work with all other kernels?
my problem is on installing nvidia driver on fc12 32bit but, first of all, as i understood the pae kernel requires more than 4gb of ram,i have a 2.2 ghz cpu with 2 gb ram,but when i run command:uname -r it answers: 2.6.31.5-127.PAE [i have fc12 32 bit] when we try to download linux we have a 32bit edition or 64bit edition,do we have an edition which is only for pae? or when we install for example the 32bit edition on a computer with more than 4gb of ram then the kernel automatically will change to be a pae kernel??
I'm attempting to install the driver for my atheros AR8131 PCI-E Gigabit Ethernet adapter (in my Lenovo laptop) on my newly installed RHEL5 system (it's not currently being recognized).
I tried using: 'make install' but hit an error "Makefile:61: *** Linux kernel source not found."
After this, I tried: 'sudo yum install kernel-devel kernel-headers'
To rectify this, but hit this error "No package kernel-devel available" (and the same for the headers). What should I do?
I write the network driver. Transmission of packets in user space I do through netlink socket`s. In user space there is a handling of packets and their transmission on other device (however, it isn't important).
Problem in that any time, packets through the driver in system, and is reverse, are transferred normally. But then there comes the moment when the kernel crash. If to look in syslog it seems to me that comes deadlock. Also I think that it is related with netlink socket`s.
I can't find the information on that anywhere how correctly to use netlink socket`s in kernel space. Can at you will any a reason into the account of synchronization of sockets and the driver in kernel space?
With the recent upgrade kernel, my ATI driver can no longer work. After upgrading to the new kernel, upon reboot I would get stuck at the "checking battery status" and can't boot into kubuntu.
I'm running Kubuntu 10.10 64 on intel i5 with radeon hd 4870.
So I thought I messed something up since I was fooling around with conky script the day before. I did a clean install of kubuntu 10.10 64 and reset all my settings and my files. At this point, everything works smoothly and I can reboot multiple times without a problem.
I proceeded to install the Radeon catalyst driver following the documentation, which worked perfectly for me on the previous kernel. After rebooting, I can no longer get pass the "checking battery state" black screen. I had to boot into safe book, uninstall all fglrx and also delete xorg.conf to be able to boot back in normally.
I compiled the 2.6.31.6 kernel and <insert drumroll> it boots!(my first kernel roll, I'm kind of shocked actually) That's the good news. The bad news is that my NVIDIA drivers are gone in the wind. That's not entirely true as I can still boot into the old kernel and startx. Is there a way to download the driver using the command line for reinstall?
Kernel driver function was called via ioctl and returned success, but when I checked the kernel display buffer with dmesg the printk message was not there. Then when you do lsmod, the driver you were calling showed "used by zero". So it seems like the kernel driver was not accessed. In the kernel driver, I had many printk statements, but nothing printed in the buffer. if the driver get accessed and what could cause this?
I installed the latest kernel liquorix (2.6.35) but when i want to install the Nvidia driver downloaded on the Nvidia website (256.53), i have an error message because Nvidia doesn't found the kernel source tree.
I install linux-image-2.6.35-6.dmz.2-liquorix-686_2.6.35-16_i386.deb, linux-headers-2.6.35-6.dmz.2-liquorix-686_2.6.35-16_i386.deb and build-essential. I don't understand why the installation doesn't works.
I have rtl8187se linux driver, during installation in debian linux it tells that "the kernel is not a generic". How can i install this driver in default debian kernel (without generic)?
i did compiled and installed kernel 3.0.0 on ubuntu 10.04 lucid lynx. well everything is fine except, a error message shown during the booting. Code: error: driver mdio-gpio already registered aborting how can i solve this error?
I have Fedora 12 right now, and I've come to the conclusion that the ATI catalyst drivers version 9.11 aren't going to work at all on that system, so I was going to downgrade to fedora 10 and install 9.8 or so on it. But what I was wondering is if I install Fedora 10 and then upgrade the kernel will that make the ATI drivers not work? Do I need to turn automatic updates off?
I need Ubuntu 8.10 with kernel 2.4.XX because i have device who is using only me country. It is FLARION mobile internet some thing between 2G and 3G T-Mobile is testing this technology in my country. I download Ubuntu 8.10 but every time this ISO or Release have kernel 2.6.xx and my driver do not work. Therefore i need image ubuntu 8.10 with kernel 2.4 or some manual how downgrade kernel. I find same how to manual and i am not able to do it.
This is a followup/secondary question from another post earlier this morning.[URL].. Info: Lucid 10.04, 4GB ram, Nvidia video, home built pc. I'm fairly certain that when I enable the pae kernel this time, I'll get usage of the full 4GB of memory that I have installed.
The problem is, that I did enable the pae kernel earlier this week to test something out, but ran into a problem. It came up in "low graphics mode" (800x600). As you can image, I wasn't real thrilled about that.
I went to System->Administration->Hardware Drivers to get the video driver straightened out. I figured it just needed one compiled for the pae kernel... Well, it didn't find one. Is there one? Is there a procedure to get one installed/compiled, if there isn't one?
I don't know if I want to mess with trying to get the Nvidia drivers working for pae, when I only stand to gain another ~700MB of memory. Currently showing 3.2GB. I'm not sure if its worth my trouble..
I am in the midst of porting a driver that works on kernel version 2.6.21 to version 2.6.27. I am not aware of all the changes that need to be done to achieve my objective.
Having just updated various files including the kernel using Package Manager I no longer seem to have the correct version of the Nvidia graphics driver. On previous updates this has been done automatically by the "kmod Nvidia" Metapackage. My last kernel was 2.6.32.19-163 fc12.i686.PAE and the Nvidia driver for that did get downloaded correctly. Looking on Yumex I cannot see a driver for this latest kernel listed.
when I open virtualbox OSE and tried to run a vm i get this error
Code:
Kernel driver not installed (rc=-1908)
The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Re-setup the kernel module by executing
'/etc/init.d/vboxdrv setup'
as root. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary. So i tried doing what it said and I got this error when i tried to run /etc/init.d/vboxdrv setup (as root)
Code:
Stopping VirtualBox kernel module done Recompiling VirtualBox kernel module, NOT. It has been packaged.Recompiling VirtualBox
[code]....
Then i ran dmesg and there was a ton of stuff that seemed to be unreleated so i ran dmesg -c to clear it. then i ran the vboxdrv this again then checked dmesg again expecting there to be nothing but the vboxdrv stuff but it was still blank.I really dont know what to do at this point I tried uninstalling and reinstalling but that makes no difference
When I start up a virtual machine in Virtualbox on Suse 13.1 I see this message:Kernel driver not installed (rc=-1908)
The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing '/etc/init.d/vboxdrv setup'
as root. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.
I have downloaded vbox from its site and installed it. I created a vm but when I try to start it, I get error: Kernel driver not installed (rc=-1908) The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing: '/etc/init.d/vboxdrv setup' as root. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.
And when I try 'sudo /etc/init.d/vboxdrv setup', I get: Stopping VirtualBox kernel modules done Uninstalling old VirtualBox DKMS kernel modules done Trying to register the VirtualBox kernel modules using DKMS failed (Failed, trying without DKMS) Recompiling VirtualBox kernel modules failed (Look at /var/log/vbox-install.log to find out what went wrong)
And this is /var/log/vbox-install.log: Makefile:159: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.
I've spent about 3 hours yesterday trying to get my GeForce 210 with CUDA DevDriver running on the 3.0.4 kernel. It was running w/o problems on 2.6.39-desktop (with dev-src for 2.6.37). [yeah, I know I should stick to what works - but I don't like it]
After uninstalling the old drivers I tried several ways for an installation of the new ones:
1. ./devdriver_4.0_linux_64_270.41.19.run on the new kernel (even manually navigating to the kernel-src folder)
2. ./devdriver_4.0_linux_64_270.41.19.run on the old kernel, with new dev-src &c. 3. XFree 280.16 driver on the new kernel with the new dev-src &c.
The results:
3. Works now.
2. did not compile telling me the source files were missing (obviously, as they were for 3.0.4 and not 2.6.39)
1. Aborted the installation with the following (excerpt from nvidia-installer.log)
How can I force my kernel to use the ahci driver when both the ahci & sata_nv are built into the kernel.?
My MSI board bios doesn't have an option for "AHCI MODE". The only sata option that it has is "called "On Chip Sata" & is located under "Integrated Peripherals. Also, the only values available for "On Chip Sata" are enabled or disabled. If I choose the disabled option, the sata drives arn't found & bootup fails.
I tried to tell the kernel to use the ahci driver by appending kernel options to my Grub2 bootloader but they all failed.
The only thing I can think of that is left to do is to re-build my kernel with CONFIG_SATA_NV as a loadable module & CONFIG_AHCI as a build-in driver. With only the ahci driver available at boot, the kernel will have to use it or fail to boot.
One more thing I want to say is that my other computer with the ASUS motherboard uses the ahci driver & I have both the sata_via & the ahci drivers built into the kernel. However, it has a bios option for AHCI MODE.
(eg.) Southbridge VT8251 Serial ATA IDE Controller <AHCI>