@Miles - your kernel version doesn't look like an Ubuntu version. I'm
guessing you have EHCI/UHCI/OHCI configured as modules whereas the
Ubuntu kernel config has all of them built into the kernel in a defined
order.
--
warning: ehci_hcd loaded AFTER uhci_hcd and ohci_hcd
I am seeing this still:
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd, not
after
Kernel 2.6.33-rc3-git3
udev 149-5
module-init-tools 3.11.1-1
Distro
module-init-tools (3.7-pre9-1) unstable; urgency=medium
* Since we are already providing workarounds for kernel shortcomings,
add to the aliases file directives to load ehci-hcd before the other
HCD drivers. (Closes: #51)
* docbook-to-man build-dependency replaced by
Hi,
I read this thread with interest. I'm a developer for Puppy Linux and today ran
into this warning when I was testing the 2.6.29.6 kernel with Puppy.
I think that I have fixed it, and my solution might interest you. Our
boot scripts are very Different from Debian, or any other distro for
that
dino99, what worked?? Thanx! Ric
--
warning: ehci_hcd loaded AFTER uhci_hcd and ohci_hcd
https://bugs.launchpad.net/bugs/296710
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Branch linked: lp:ubuntu/karmic/linux-ports
--
warning: ehci_hcd loaded AFTER uhci_hcd and ohci_hcd
https://bugs.launchpad.net/bugs/296710
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
hi all,
problem fixed for me.
Thanks
--
warning: ehci_hcd loaded AFTER uhci_hcd and ohci_hcd
https://bugs.launchpad.net/bugs/296710
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Hi Guys,
is there a kernel I can install which doesn't have these modules compiled in?
I know I can compile my own kernel, but that kinda defeats the object of
running ubuntu
my usb2's been broken since intrepid, i've had to unload ehci_hcd and
deal with usb1 speeds (and use eSATA for big stuff)
On Fri, 2009-05-01 at 18:29 +, Miguel wrote:
On Tue, Apr 14, 2009 at 10:50 AM, Scott James Remnant
sc...@canonical.com wrote:
On Fri, 2009-04-10 at 12:02 +, Miguel wrote:
And here it is my attachment with the report. My computer is just
upgraded right now and the problem with
On Tue, May 5, 2009 at 12:27 PM, Scott James Remnant
sc...@canonical.comwrote:
On Fri, 2009-05-01 at 18:29 +, Miguel wrote:
On Tue, Apr 14, 2009 at 10:50 AM, Scott James Remnant
sc...@canonical.com wrote:
On Fri, 2009-04-10 at 12:02 +, Miguel wrote:
And here it is my
On Tue, Apr 14, 2009 at 10:50 AM, Scott James Remnant
sc...@canonical.com wrote:
On Fri, 2009-04-10 at 12:02 +, Miguel wrote:
And here it is my attachment with the report. My computer is just
upgraded right now and the problem with the printer isn't solved :(.
Did you try unbinding the
Incidentally, he's not the only one. I have having an identical problem
with ehci/uhci mis-detection between a ThinkPad X61s and a Sansa Vuze
mp3 player.
In hardy intrepid, I could blacklist uhci_hcd. Obviously, this is not
possible with the new Jaunty kernel.
unbinding all devices under
I will try in two weeks, but the point is that a lot of people have this
setup ordinary USB 2.0 HP printer with ordinary Intel PC, so I think
this kind of things have to work before the Jaunty will be realesed.
Sorry for my lack of feedback :(.
--
warning: ehci_hcd loaded AFTER uhci_hcd and
@Miguel
Jour problem is not related to this one, or probably indirectly. The fix
should make USB 2 to work. And how you said, your usb 2 do not work
properly. Please open a new bug and subscribe me to it. Attach your
complete dmesg to new bug.
--
warning: ehci_hcd loaded AFTER uhci_hcd and
On Tue, 2009-04-14 at 10:31 +, Miguel wrote:
I will try in two weeks, but the point is that a lot of people have this
setup ordinary USB 2.0 HP printer with ordinary Intel PC, so I think
this kind of things have to work before the Jaunty will be realesed.
Sorry for my lack of feedback
i found a working dmesg of printer you have. Now i can see what you
posted only part with broken storage. So the question, printer or build
in card reader is broken for you?
--
warning: ehci_hcd loaded AFTER uhci_hcd and ohci_hcd
https://bugs.launchpad.net/bugs/296710
You received this bug
On Fri, 2009-04-10 at 12:02 +, Miguel wrote:
And here it is my attachment with the report. My computer is just
upgraded right now and the problem with the printer isn't solved :(.
Did you try unbinding the USB 2.0 host? (see above)
Scott
--
Scott James Remnant
sc...@canonical.com
--
And here it is my attachment with the report. My computer is just
upgraded right now and the problem with the printer isn't solved :(.
** Attachment added: Report files Jaunty 2009-04-10 (USB 2.0 vs USB 1.X
problem)
http://launchpadlibrarian.net/25207469/report.logs.tar.gz
--
warning:
On Tue, 2009-04-07 at 03:36 +, Jeffrey Baker wrote:
Building these modules into the kernel, at this extremely late stage in
the Jaunty development cycle, doesn't seem like a particularly good
idea. Among other things, it has implications for laptop users who are
trying to minimize power
On Tue, Apr 7, 2009 at 10:16 AM, Scott James Remnant
sc...@canonical.com wrote:
Whether or not they're built in or modules, they still have to be loaded
for your USB hardware to work.
True.
Whether or not they're built in or modules, you can still disable
individual host control interfaces -
On Tue, 2009-04-07 at 18:02 +, Jeffrey Baker wrote:
Whether or not they're built in or modules, you can still disable
individual host control interfaces - the method is just slightly
different (though since the one that works for built-ins ALSO works for
modules, we should arguably be
On Sat, 2009-04-04 at 11:45 +, Paul Sladen wrote:
If boot-speed and an easy life are the only reasons to ditch that policy
of modularity then it's the focus narrow-minded and not being forward
looking.
The non-modularity of the HCI drivers has nothing to do with boot speed.
Presumbly
Building these modules into the kernel, at this extremely late stage in
the Jaunty development cycle, doesn't seem like a particularly good
idea. Among other things, it has implications for laptop users who are
trying to minimize power consumption, and it makes life unnecessarily
difficult for
On Fri, 2009-04-03 at 22:52 +, Paul Sladen wrote:
Nikias Bassen: I've opened bug #354832 on the basis of the regression of
the modules being non-modular and therefore certain machine being let
with non-working USB.
Isn't it better to fix the bug that causes the USB to not work than
bitch
Scott: sure, but compiling this in hasn't fixed that bug either... but
has had the (negative) impact of just making it even harder to
diagnose/debug with end-users.
Eg. it's no longer possible to request Hi XYZ, could you try 'modprobe
-r abcd_hci' then 'modprobe ...' and post 'find /sys -path
Building these modules in (rather than just fixing to have a
sensible/optional dependency) means it's impossible to force a
particular driver and impossible (at least AFAICWO) to blacklist for
debugging.
(The solution applied so far doesn't appear to have solved the problem
and is instead just
That's right Paul. I'm having issues now too, as I have defective usb 2.0
hardware (usb 1.1 is working flawlessly via the same usb connector) so I used
to unload the ehci-hcd which is not possible anymore with the latest kernel
revision 2.6.28-11.40 because *hci-hcd are built-in now.
So I
Nikias Bassen: I've opened bug #354832 on the basis of the regression of
the modules being non-modular and therefore certain machine being let
with non-working USB.
--
warning: ehci_hcd loaded AFTER uhci_hcd and ohci_hcd
https://bugs.launchpad.net/bugs/296710
You received this bug notification
There weren't any usb devices conected. Sorry, but I am far away from
that computer for two weeks. If the error is there by that time, I will
send you these files when I come back.
Thank you very much for your guide.
--
warning: ehci_hcd loaded AFTER uhci_hcd and ohci_hcd
Received the latest updates. Works like a charm. Thank you very much.
--
warning: ehci_hcd loaded AFTER uhci_hcd and ohci_hcd
https://bugs.launchpad.net/bugs/296710
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I have a problem with the ehci_hcd too. The printer, HP Photosmart C4180
only works in Linux if the USb 2.0 was disabled previously in the BIOS.
But the point is that this printer has a USB 2 port which allways works
perfectly, and even does a good job today with other operating systems.
I
Miguel, you'll need to provide more information.
1. Are any USB devices connected during power-up?
2. Create a series of reports:
sudo -i
mkdir /tmp/report
uname -a /tmp/report/system.log
lsb_release -a /tmp/report/system.log
lspci -vvnn /tmp/report/lspci-vvnn.log
lsub -v /tmp/report/lsusb-v.log
This bug wasn't fixed yet in 2.6.28-2-rt
$ dmesg | grep _hcd
[4.395576] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[4.395977] ohci_hcd :00:02.0: PCI INT A - Link[APCF] - GSI 22 (level,
low) - IRQ 22
[4.395999] ohci_hcd :00:02.0: setting latency timer to 64
[
On Sat, 2009-03-14 at 17:13 +, TJ wrote:
The modalias reporting command was missing 'drivers/'. Here's an
alternative and an example of the output to expect:
for hci in /sys/bus/pci/drivers/?hci_hcd; do echo $hci; cat
$hci/*/modalias; done
/sys/bus/pci/drivers/ehci_hcd
flor...@jaunty:~$ for chr in 8 9 A B; do
als=pci:v8086d27C${chr}sv144DsdCA00bc0Csc03i00; echo $als; sudo
modprobe -n -v --first-time $als; done
pci:v8086d27C8sv144DsdCA00bc0Csc03i00
FATAL: Module uhci_hcd already in kernel.
On Mon, 2009-03-16 at 16:38 +, Scott James Remnant wrote:
Are you affected by this bug?
At some point a few weeks/months ago I believed I was but then the issue
went away and afterwards I pretty much convinced myself I'd been
imagining a problem since USB transfers were above the USB1
Note: the symptom is exactly what is reported by dino99 on the initial
bug report:
flor...@jaunty:~$ dmesg | grep Warn
[ 10.564129] Warning! ehci_hcd should always be loaded before uhci_hcd and
ohci_hcd, not after
But I do not diagnose any other problem with USB.
--
warning: ehci_hcd loaded
Ok, now I've looked into it, ehci_hcd, uhci_hcd and ohci_hcd have ZERO
overlap in terms of device support. There is no way that any device
would result in more than one of these modules being loaded in any given
modprobe invocation, so modules.order would not apply (as I said above):
Scott,
I still have the problem in initramfs (like reported by Aurius).
module-init-tools 3.7~pre9-1
initramfs-tools 0.92bubuntu25
The workaround add ehci_hcd to /etc/initramfs-tools/modules provided
by Javier works for me.
The workaround MODULES=dep provided by Dimitrio DOES NOT work for
On Mon, 2009-03-16 at 17:02 +, Florent Xicluna wrote:
here is the output of the modalias thing (just in case) :
r...@jaunty# for hci in /sys/bus/pci/drivers/?hci_hcd; do echo $hci; cat
$hci/*/modalias; done
/sys/bus/pci/drivers/ehci_hcd
Adding information here for the ongoing debug session with Keybuk and
rtg on IRC, for the following system:
Sony Viao VGN-FE41Z
lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML
and 945GT Express Memory Controller Hub [8086:27a0] (rev 03)
00:01.0 PCI bridge
dmesg log exhibiting warning message.
for hci in /sys/bus/pci/drivers/?hci_hcd; do echo $hci; cat $hci/*/modalias;
done
/sys/bus/pci/drivers/ehci_hcd
pci:v8086d27CCsv104Dsd81EFbc0Csc03i20
/sys/bus/pci/drivers/uhci_hcd
pci:v8086d27C8sv104Dsd81EFbc0Csc03i00
The laptop has three external-facing USB ports on the right side; number
them from back to front 1 2 3. Attached an external USB hard drive to
port 1:
kernel: [ 393.808054] usb 5-3: new high speed USB device using ehci_hcd and
address 6
kernel: [ 393.941436] usb 5-3: configuration #1 chosen
Test without ehci_hcd. ehci_hcd was blacklisted and didn't load:
lsmod | grep hci
ohci1394 42036 0
ieee1394 108416 1 ohci1394
uhci_hcd 34464 0
/var/log/kern.log:
kernel: [ 365.076048] usb 2-1: new full speed USB device using uhci_hcd and
address 3
Without ehci_hcd
** Attachment added: dmesg
http://launchpadlibrarian.net/23951849/dmesg
--
warning: ehci_hcd loaded AFTER uhci_hcd and ohci_hcd
https://bugs.launchpad.net/bugs/296710
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Without rebooting I disconnected the external USB device, unloaded the
USB modules then loaded ehci_hcd first:
sudo modprobe -r uhci_hcd
sudo modprobe -r ohci_hcd
sudo modprobe ehci_hcd
sudo modprobe uhci_hcd
sudo modprobe ohci_hcd
readlink /sys/block/sdb
So, as described on IRC #ubuntu-kernel by mjg59, the issue is USB host
controllers sharing physical ports.
In this test-case the PC has 4x USB 1.1 host controllers and 1x USB2
host controller.
The three physical external USB ports are connected such that the USB2
host controller and one of the
Something to be aware of: It looks as if once a port has been claimed
after power-up it will always be associated with the host controller
that claimed it until the system does a cold boot.
--
warning: ehci_hcd loaded AFTER uhci_hcd and ohci_hcd
https://bugs.launchpad.net/bugs/296710
You
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
jaunty.git;a=commit;h=462941e9684b5f55b13617e726c54ade0495465a
While not a show stopper, this warning is an indication of a fairly
major annoyance. If you insert a USB 1.0 peripheral, and then insert a
USB 2.0 peripheral in any other port, you are
This bug was fixed in the package linux - 2.6.28-10.33
---
linux (2.6.28-10.33) jaunty; urgency=low
[ Scott James Remnant ]
* SAUCE: nbd: Change default partitions per device to 15
- LP: #342563
[ Tejun Heo ]
* SAUCE: libata: make sure port is thawed when skipping
even with initramfs-tools (0.92bubuntu25) installed and running up-to-
date jaunty with 2.6.28-9-generic x86_64, and after running:
sudo dpkg-reconfigure linux-image-2.6.28-9-generic
the order of the usb modules in modules.order is still not being
respected and i am still getting the error.
Is
Sorry to inform but initramfs-tools - 0.92bubuntu25 does not fixed this
problem. I am still getting this warning and USB misbehaves.
I am running linux-image-2.6.28-9-generic 2.6.28-9.31 (latest). Can we
look at this issue again?
--
warning: ehci_hcd loaded AFTER uhci_hcd and ohci_hcd
** Changed in: module-init-tools (Ubuntu)
Status: Fix Released = Confirmed
** Changed in: initramfs-tools (Ubuntu)
Status: Fix Released = Confirmed
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
warning: ehci_hcd loaded AFTER uhci_hcd and ohci_hcd
Florent:
The modalias reporting command was missing 'drivers/'. Here's an
alternative and an example of the output to expect:
for hci in /sys/bus/pci/drivers/?hci_hcd; do echo $hci; cat
$hci/*/modalias; done
/sys/bus/pci/drivers/ehci_hcd
pci:v8086d27CCsv104Dsd81EFbc0Csc03i20
This bug is present in Jaunty with 2.6.28-9-generic kernel
--
warning: ehci_hcd loaded AFTER uhci_hcd and ohci_hcd
https://bugs.launchpad.net/bugs/296710
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
It's even simpler than you suggest.
Simply add ehci_hcd to /etc/initramfs-tools/modules
without changing anything else.
This worked like a champ for me. added the line then regenerated the initramfs,
no more problems.
I've got kubuntu installed on a USB stick, so it was painfully obvious
No modalias found: No such file or directory
Is it possible that the error occurs at the initramfs stage?
I am not convinced that initramfs take care of modules.order...
How I can check this point?
--
warning: ehci_hcd loaded AFTER uhci_hcd and ohci_hcd
https://bugs.launchpad.net/bugs/296710
On Fri, 2009-03-13 at 12:49 +, Florent Xicluna wrote:
** Attachment added: /lib/modules/2.6.28-9-generic/modules.order
http://launchpadlibrarian.net/23822802/modules.order
This states:
1102 kernel/drivers/usb/host/whci/whci-hcd.ko
1103 kernel/drivers/usb/host/ehci-hcd.ko
1105
** Attachment added: /lib/modules/2.6.28-9-generic/modules.order
http://launchpadlibrarian.net/23822802/modules.order
--
warning: ehci_hcd loaded AFTER uhci_hcd and ohci_hcd
https://bugs.launchpad.net/bugs/296710
You received this bug notification because you are a member of Ubuntu
Bugs,
On Fri, 2009-03-13 at 05:23 +, Alessandro Ghersi wrote:
This bug is present in Jaunty with 2.6.28-9-generic kernel
Please attach your /lib/modules/2.6.28-9-generic/modules.order file.
Scott
--
Scott James Remnant
sc...@canonical.com
--
warning: ehci_hcd loaded AFTER uhci_hcd and
it's very possible that the source of the warning is the initramfs,
because I think that I stopped getting it when I set MODULES=dep in /etc
/initramfs-tools/initramfs.conf
--
warning: ehci_hcd loaded AFTER uhci_hcd and ohci_hcd
https://bugs.launchpad.net/bugs/296710
You received this bug
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
warning: ehci_hcd loaded AFTER uhci_hcd and ohci_hcd
https://bugs.launchpad.net/bugs/296710
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This bug was fixed in the package initramfs-tools - 0.92bubuntu25
---
initramfs-tools (0.92bubuntu25) jaunty; urgency=low
* mkinitramfs: include the modules.order file. LP: #296710.
-- Scott James Remnant sc...@ubuntu.com Fri, 13 Mar 2009 16:11:49
+
** Changed in:
Still problem with Jaunty, kernel 2.6.28-9.29
module-init-tools 3.7~pre7-3
--
warning: ehci_hcd loaded AFTER uhci_hcd and ohci_hcd
https://bugs.launchpad.net/bugs/296710
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
New module-init-tools, combined with new kernel, will load modules in
the order specified by the installed modules.order file - ehci-hcd is
listed before ohci-hcd and uhci-hcd so will be used first.
This obviously doesn't count if hardware not supported by ehci-hcd is
found first, but then that
** Changed in: debian
Status: Unknown = New
--
warning: ehci_hcd loaded AFTER uhci_hcd and ohci_hcd
https://bugs.launchpad.net/bugs/296710
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
On Sun, 2009-02-15 at 14:25 +, Javier Kohen wrote:
It's even simpler than you suggest. Simply add ehci_hcd to /etc
/initramfs-tools/modules without changing anything else. At least
initramfs-tools 0.92o gives preference to the modules set in that file,
even if the MODULES setting is left
@fishor
It's even simpler than you suggest. Simply add ehci_hcd to /etc
/initramfs-tools/modules without changing anything else. At least
initramfs-tools 0.92o gives preference to the modules set in that file,
even if the MODULES setting is left to the default of most. That
behavior is
** Changed in: udev (Ubuntu)
Status: Confirmed = Won't Fix
--
warning: ehci_hcd loaded AFTER uhci_hcd and ohci_hcd
https://bugs.launchpad.net/bugs/296710
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
This issue still occurs in linux-source-2.6.28-4.11 kernels (jaunty)
Thanks for the workaround, fishor. I was trying all sorts of crazy things like
editing modules.dep and using modconf, but I later found out that most of my
work wasn't applicable because update-modules is deprecated.
BTW, this
On Sat, 2009-01-17 at 19:03 +, Luis Silva wrote:
@scot: If you only have usb 1.0 hardware then ehci-hcd will do nothing.
only when you load uhci-hcd will you have access to those deices. The
point is the ehci-hcd driver does not block the uhci-hcd controlled
devices. But the later drier
@fishor: That was the solution for me. In fact it seems that udev has
nothing to do with this. the problem is that there is no control over
what modules are loaded and when if they are in the initram.
@scot: If you only have usb 1.0 hardware then ehci-hcd will do nothing.
only when you load
With last Intrepid kernel (2.6.27-11) this problem is still there !!! (ehci
1.00 driver 10 dec 2004)
What about the possibility to use hal to deal with the right hardware: by
default, first load usb2 driver (if no usb2, then only use it with new one), or
switch to the good driver when
This patch (as1139) adds a warning to the system log whenever ehci-hcd
is loaded after ohci-hcd or uhci-hcd. Nowadays most distributions are
pretty good about not doing this; maybe the warning will help convince
anyone still doing it wrong.
You can use small work around:
1. sudo vi /etc/initramfs-tools/initramfs.conf
change MODULES=list
2. sudo lsmod | sed 's/\([[:graph:]]*\).*/\1/'
/etc/initramfs-tools/modules
3. sudo vi /etc/initramfs-tools/modules
remove Module, move ehci_hcd to the first place
4. sudo update-initramfs -u
The point in having ehci-hcd loaded before the other is that if either
uhci or ohci get loaded before and a usb2.0 is present then it will
behave as a usb1 device and be blocked by these drivers.
--
warning: ehci_hcd loaded AFTER uhci_hcd and ohci_hcd
https://bugs.launchpad.net/bugs/296710
You
On Thu, 2009-01-15 at 21:13 +, Luis Silva wrote:
The point in having ehci-hcd loaded before the other is that if either
uhci or ohci get loaded before and a usb2.0 is present then it will
behave as a usb1 device and be blocked by these drivers.
Right
And what happens if the machine only
My opinion is that this is a kernel bug that the order matters at all.
ehci_hcd is the USB 2.0 HC driver.
ohci_hcd and uhci_hcd are the older USB 1.0 drivers.
Now imagine this scenario:
* a laptop with only USB 1.0 Host Control Devices is booted
* we'll only load ohci_hcd/uhci_hcd because
what scott said seems to make sense, even though i don't know the
internals of the kernel that well...
this warning appears in the kernel since the patch i attached above was
committed into linus's kernel tree on 17.10.2008. Quoting:
Nowadays most distributions are pretty good about not doing
assigning to the linux source package, though it might be udev or
something similar...
i am also seeing this warning, but all the devices on my system (8.10,
32-bit, 2.6.27-8) work perfectly.
also look at this:
http://kerneltrap.org/mailarchive/git-commits-head/2008/10/18/3712134
note: ehci
** Bug watch added: Debian Bug tracker #51
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=51
** Also affects: debian via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=51
Importance: Unknown
Status: Unknown
--
warning: ehci_hcd loaded AFTER uhci_hcd and ohci_hcd
on second thought, i think it's more likely to be a udev bug.
note also that, also in the upstream bug they cannot agree whether it's
the kernel, udev or module-init-tools
** Changed in: udev (Ubuntu)
Sourcepackagename: linux = udev
--
warning: ehci_hcd loaded AFTER uhci_hcd and ohci_hcd
yes , it's a known issue and the kernel is suspected.
Look at bug report, a workaround is proposed, but i have not tested it yet:
http://www.mail-archive.com/debian-bugs-
[EMAIL PROTECTED]/msg570259.html
Some questions also about graphics chipsets:
** Attachment added: lspci.log
http://launchpadlibrarian.net/19670570/lspci.log
--
warning: ehci_hcd loaded AFTER uhci_hcd and ohci_hcd
https://bugs.launchpad.net/bugs/296710
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Yes, I can confirm that this happens on the following:
kernel: 2.6.27-8-generic
release: intrepid ibex 64 bit
where the following message appears in dmesg:
Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd, not
after
And also:
kernel: 2.6.24-21-generic
release: hardy heron
** Attachment added: kern.log
http://launchpadlibrarian.net/19560526/kern.log
--
warning: ehci_hcd loaded AFTER uhci_hcd and ohci_hcd
https://bugs.launchpad.net/bugs/296710
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
86 matches
Mail list logo
