DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
This all sounds a bit fishy to me.
Along with the rest of the planet, I've been using USB mice and keyboards for a number of years and never had any trouble using them with Debian or it's installer on lots of different hardware, including Gigabyte boards.
1. I don't understand: What will using apt-get accomplish that download + dpkg does not? Granted, download + dpkg is more circuitous, but doesn't it accomplih the same thing? Or, will that automagically eliminate the dependency problems that I encountered? In any case, I now have jessie loaded, complete, which does the same thing (??) that installing the jessie backport does.
2. Rehab for sudo: NSA went to great lengths to separate root from user in Secure Linux, which has been rolled into the kernel. Now people (Ubuntu particularly) want to undo all that work with sudo??
Is invoking a root terminal as a user the same as sudo? Or is that the same as logout; login as root within that window?
Quote:
Originally Posted by Randicus Draco Albus
Add backports to /etc/apt/sources.list.
Code:
#apt-get install -t wheezy-backports <name of package>
As far as I can tell from my research, it is a problem communicating with the (new) AMD 970 Northbridge. I have heard of no problems reported with earlier series Northbridge. Reading the AMD change notices, the 900 series changed the register layout.
Quote:
Originally Posted by descendant_command
This all sounds a bit fishy to me.
Along with the rest of the planet, I've been using USB mice and keyboards for a number of years and never had any trouble using them with Debian or it's installer on lots of different hardware, including Gigabyte boards.
1. I don't understand: What will using apt-get accomplish [...] Or, will that automagically eliminate the dependency problems that I encountered?
Well yes, that's kind of the whole point of APT...
The backports website has comprehensive instructions for installing the pre-built backports from that repo - I'd suggest reading them.
Quote:
Originally Posted by piobair
In any case, I now have jessie loaded, complete, which does the same thing (??) that installing the jessie backport does.
Well no, installing the backported kernel would have upgraded the kernel, whereas you've upgraded the whole system to the testing distribution.
Quote:
Originally Posted by piobair
Is invoking a root terminal as a user the same as sudo? Or is that the same as logout; login as root within that window?
sudo and su is irrelevant here.
If upgrading to testing has made no difference, then I would say that it's extremely unlikely that you have an unsupported USB HID device. It would be unusual for there to be support for such a device in an older kernel and then see that removed from a newer kernel. Also the relevant kernel modules listed in your lsmod output as in use in the squeeze kernel are still present in newer kernels.
In view of this I would suggest again that newer kernels may be exposing a problem with your hardware by trying to configure the USB hubs/devices differently. It could be a motherboard BIOS bug and it's really up to you to research and find out the cause. That may involve building a newer kernel and tweaking the config (leaving out USB 2/3 support as I suggested).
You could also try a different distro with one of the newer kernels (anything between 3.2 and 3.14) and see if - particularly - non debian distros have the same problem. For example, a fedora livecd might be an idea.
Have you tested a different, preferably bog standard wired, USB keyboard and mouse?
Unlikely or not, my machine gets the reported error message after dist-upgrade to wheezy and also after dist-upgrade to jessie.
You suggested switching to a different distro. The Debian i386 live wheezy CD actually works with this machine. (??) On the other hand, I have a 8 core CPU, and switching to an i386 would discard that functionality.
I formally reported the issue as a bug against the udev package (bug #749941). The udev maintainer said that udev was the wrong package, that I should file the issue against kernel, and then closed 749441.
Accordingly, I have filed a bug report against kernel. https://bugs.debian.org/cgi-bin/bugr...cgi?bug=750445
Looking at the summary in debian-kernel@lists.debian.org, there are 1155 outstanding bugs and 64 resolved bugs. That is not a good track record.
For right now, I have jessie installed, but am operating (mostly) successfully while booted up with squeeze.
Quote:
Originally Posted by cynwulf
Well yes, that's kind of the whole point of APT...
The backports website has comprehensive instructions for installing the pre-built backports from that repo - I'd suggest reading them.
Well no, installing the backported kernel would have upgraded the kernel, whereas you've upgraded the whole system to the testing distribution.
sudo and su is irrelevant here.
If upgrading to testing has made no difference, then I would say that it's extremely unlikely that you have an unsupported USB HID device. It would be unusual for there to be support for such a device in an older kernel and then see that removed from a newer kernel. Also the relevant kernel modules listed in your lsmod output as in use in the squeeze kernel are still present in newer kernels.
In view of this I would suggest again that newer kernels may be exposing a problem with your hardware by trying to configure the USB hubs/devices differently. It could be a motherboard BIOS bug and it's really up to you to research and find out the cause. That may involve building a newer kernel and tweaking the config (leaving out USB 2/3 support as I suggested).
You could also try a different distro with one of the newer kernels (anything between 3.2 and 3.14) and see if - particularly - non debian distros have the same problem. For example, a fedora livecd might be an idea.
Have you tested a different, preferably bog standard wired, USB keyboard and mouse?
There is an option in the BIOS to enable/disable IOMMU. The default setting is "disable". When this is set to "enable", the problem goes away.
Some motherboards using this chipset are reported not to work properly
under Linux unless the IOMMU is enabled by the BIOS. Linux's AMD IOMMU
driver is only included in 64-bit kernels
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
