Tag Info

New answers tagged

1

It's in kernel space. This article from Linux Device Drivers is a bit dated but still should generally apply: https://lwn.net/images/pdf/LDD3/ch18.pdf However, there is some effort recently towards replacing the kernel driver with a userspace console called "KMSCON" -- see that project's site for more: http://cgit.freedesktop.org/~dvdhrm/kmscon/tree/README


0

The Data Server Driver package for DB2 9.5 does not include the install script - that was introduced in 9.7. Installation in 9.5 is manual. The installDSDriver script does a couple of things - it unzips the driver files to several sub-directories, and it creates a db2profile file for bash users. You have several options: Download the 9.7 DSDriver package ...


0

One of the first places to check after the cable if your sound output device is connected with a cable would be System Settings -> click Sound icon -> Output tab -> make sure that you have selected the correct item from the list under where it says Play sound through. The other thing to check is that Dummy output device does not appear under Play sound ...


0

You could try # apt-get install firmware-iwlwifi # modprobe -r iwlwifi; modprobe iwlwifi


0

aticonfig --initial --adapter=all -f bash: aticonfig: command not found[/code] This leads me to believe that you have not installed the fglrx package. This is the first thing you need to do. Even if you have already done so perform these commands... sudo cp /etc/X11/xorg.conf /etc/X11/xorg.conf.BAK sudo apt-get remove --purge fglrx* sudo reboot ...


0

The first one is EINVAL (a standard POSIX C error) inverted. If you are curious it's from line 4218 in [src]/drivers/usb/core/hub.c (v. 3.19): 4217 if (udev->state != USB_STATE_DEFAULT) 4218 return -EINVAL; The other one is from the hub_port_init() function in the same file. These kinds of error messages aren't really intended to provide ...


0

I probably should have tried this first: sudo apt-get update sudo apt-get upgrade I also followed the instructions linked above, but it may have worked without that. At least it works now!


0

So after some tries, we managed to solve the problem. First, it is interesting to notice that two error messages were noticed that appeared during the linux boot: tps6507x 1-0048: Read from reg 0xd failed (...) tps6507x 1-0048: failed to register tps6507x-pmic regulator tps6507x is the touch-screen driver used. So what we noticed was that even the driver ...


0

I eventually got around to putting together a bug report, and was told that removing the NetworkManager-config-server package would solve it - so I did: sudo yum autoremove NetworkManager-config-server Then I rebooted, and it worked :)


0

Having looked into this further it seems that this is due to the driver only being partially implemented, critical ioctls seem to be stubbed out.


0

So I'm not entirely sure what I did or why I did it. I clean installed and went through the install process, after reboot I just ran the install again out of interested and it installed again which I thought was odd so I rebooted again and now it works. I'm not sure if this is a fix for everyone and god knows why it's happened (maybe someone of higher ...


1

This sounds like the most likely culprit is a missing driver for your network card. You could check this by running the command lspci -k and seeing if your Ethernet adapter lists a kernel driver being used (which I suspect it won't). Providing that this is the cause, you could either tell us here what network card you have installed in your machine ...


0

Did you get the solution ? Same trouble here. Kernel 3.10.17 from git@github.com:wandboard-org/linux.git branch : wandboard_imx_3.10.17_1.0.1_ga System build with buildroot Process : modprobe brcmfmac dmesg output : brcmfmac: F1 signature read @0x18000000=0x16044330 brcmfmac: brcmf_sdioh_f0_write_byte: enable F2 failed:-62 brcmfmac: ...


2

There is an answer in Kernel documentation: 3.1.2 usbmouse ~~~~~~~~~~~~~~ For embedded systems, for mice with broken HID descriptors and just any other use when the big usbhid wouldn't be a good choice, there is the usbmouse driver. It handles USB mice only. It uses a simpler HIDBP protocol. This also means the mice must support this simpler protocol. Not ...



Top 50 recent answers are included