** Changed in: linux
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/102659
Title:
USB device detection problems in 2.6.20
--
ubuntu-bugs mailing list
ubuntu-bugs@li
The 18 month support period for Feisty Fawn 7.04 has reached it's end of
life - http://www.ubuntu.com/news/ubuntu-7.04-end-of-life . As a result,
we are closing the linux-source-2.6.20 kernel task. Thanks.
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: New => Won't Fix
--
USB device
** Changed in: linux
Status: Incomplete => Fix Released
--
USB device detection problems in 2.6.20
https://bugs.launchpad.net/bugs/102659
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
Thanks for the update Ryan. I'm marking this as "Fix-Released" against
linux-source-2.6.22.
** Also affects: linux-source-2.6.22 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: New => Fix Released
--
USB device detection problems
This is fixed in Gutsy kernel 2.6.22-11, per the release notes. I'm
currently running 2.6.22-14 and this problem is GONE!
--
USB device detection problems in 2.6.20
https://bugs.launchpad.net/bugs/102659
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
That's why I was looking for the quirks.c, however, since that would
allow me to do it per device.
Данило Шеган wrote:
> Ryan, if you are already considering compiling your own kernel, a simple
> CONFIG_USB_SUSPEND=n option should do it for you. Howev
Ryan, if you are already considering compiling your own kernel, a simple
CONFIG_USB_SUSPEND=n option should do it for you. However, it will
disable USB_SUSPEND completely (just like the above echo -1 will on
2.6.22), so your computer may have more problems suspending and getting
back from suspend (
2.6.20 does not appear to HAVE a quirks.c -- is there something I can do
on this version (eg. create a quirks.c), or is there something located
elsewhere? If anyone knows, let me know.
--
USB device detection problems in 2.6.20
https://bugs.launchpad.net/bugs/102659
You received this bug notifica
This does not work for the 2.6.20 kernels, apparently, just as an FYI to
anyone who's thinking of bothering.
--
USB device detection problems in 2.6.20
https://bugs.launchpad.net/bugs/102659
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for U
I feel like spamming this thread, however I tried to write this
workaround which could be easily applied even by newbies and which works
fine for me on Gutsy kernel 2.6.22-11 generic. Concretely it made the
0483:2016 SGS Thomson Microelectronics Fingerprint Reader work properly
on my Dell Latitude
After having carefully read the complete thread below and tested extensively
the proposed workaround I realized it did not work. Sorry for the confusion.
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/85488
--
USB device detection problems in 2.6.20
https://bugs.launchpad.net
Oops, it seems to be evident the "problem" is not in kernel but in devices
which do not comply with the USB specification.
Workaround found here, as mentioned by Danilo Шеган :
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/85488
Well, also Dell seems to be shipping such devic
Problem still found in latest Gutsy kernel: Linux hostname
2.6.22-11-generic #1 SMP Fri Sep 7 04:31:16 GMT 2007 x86_64 GNU/Linux
--
USB device detection problems in 2.6.20
https://bugs.launchpad.net/bugs/102659
You received this bug notification because you are a member of Ubuntu
Bugs, which is t
Ryan, you'll have to ask that upstream (you can notice that only the
upstream bug has been marked as 'incomplete', and that's what upstream
did)
To fix this for us instead, we need to add our devices to
drivers/usb/core/quirks.c in the upstream kernel. Gutsy kernel should
already have usbcore.aut
OK, I understand it's an upstream bug, but what about it is incomplete?
--
USB device detection problems in 2.6.20
https://bugs.launchpad.net/bugs/102659
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: linux
Status: Confirmed => Incomplete
--
USB device detection problems in 2.6.20
https://bugs.launchpad.net/bugs/102659
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
** Changed in: linux (upstream)
Status: Unknown => Confirmed
--
USB device detection problems in 2.6.20
https://bugs.launchpad.net/bugs/102659
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubun
This actually *is* an upstream bug. References to similar problem can be found
in
- Red Hat's Bugzilla:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=243038
- Kernel Bugzilla:
http://bugzilla.kernel.org/show_bug.cgi?id=8606
** Bug watch added: Linux Kernel Bug Tracker #8606
http://bugz
This is likely to be related with CONFIG_USB_SUSPEND=y (look at bug
#85488), so I want to try building kernel without USB_SUSPEND support,
but I am having problems with my set-up atm. If anyone else can try and
report here, it'd be welcome.
--
USB device detection problems in 2.6.20
https://bugs.
I can confirm what's been said in comment 15, except that I use Dell
Latitude D820 and latest Gutsy.
uname -a: Linux satch 2.6.22-6-generic #1 SMP Fri Jun 1 19:24:12 GMT
2007 i686 GNU/Linux
--
USB device detection problems in 2.6.20
https://bugs.launchpad.net/bugs/102659
You received this bug no
This behaviour also found when using USB ADSL modem. Though the hardware
(Huawei WA1003A) is compatible with ueagle-atm driver, driver is not loaded
when usb is plugged in. i need to perform someting like below:
sudo echo -n 1 > /sys/bus/usb/devices/2-2/bConfigurationValue
to get the driver l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Данило Шеган wrote:
>>From my quick tests, regression seems to have been introduced in 2.6.19
> (2.6.18 kernel works fine), where USB subsystem seems to have been
> rewritten.
Would it then be appropriate to assume this is not a Ubuntu bug, but an
ups
>From my quick tests, regression seems to have been introduced in 2.6.19
(2.6.18 kernel works fine), where USB subsystem seems to have been
rewritten.
--
USB device detection problems in 2.6.20
https://bugs.launchpad.net/bugs/102659
You received this bug notification because you are a member of U
Same problems on my Dell Latitude D620 running a fresh install of ubuntu 7.04
:-(
lsusb must be run 2-3 times before the fingerprint reader shows up.
But it's gone again when I try to login to a new terminal via alt-F2
Error messages on the screen:
[ 6032.392000] hub 1-2.3:1.0: hub_port_status fa
Linux ibmtux 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686
GNU/Linux
Got the same problem attaching USB Card Reader,
4434.90] ehci_hcd :00:1d.7: port 3 reset error -110
[ 4434.90] hub 4-0:1.0: hub_port_status failed (err = -32)
[ 4439.932000] usb 4-3: new high speed USB d
This problem is also exhibited by booting off the Feisty DVD -- devices
come and go on the USB chain.
--
USB device detection problems in 2.6.20
https://bugs.launchpad.net/bugs/102659
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Same problem here. My USB cardreader connects and disconnects a few
times. Dmesg full of messages. And finally fails as the cardreader is
considered as 4 harddrives.
--
USB device detection problems in 2.6.20
https://bugs.launchpad.net/bugs/102659
You received this bug notification because you ar
I have the fingerprint reader disappearing and reappearing like the
previous person (I didn't happen to try lsusb over and over before
this). On access, the device seems to connect on lsusb, and a subsequent
lsusb shows the device. This does not appear to affect my Bluetooth --
perhaps I am lucky a
I have this same problem on Dell Latitude D620 and 2.6.20-15: lsusb with
first run doesn't list fingerprint reader, then with the next run it
lists it. Later runs may again show it without fingerprint reader, since
USB hub keeps reloading itself.
The gist of the messages appearing in /var/log/mess
Problem still present in 2.6.20-15.14.
The release date draws near and I'm getting somewhat concerned!
** Description changed:
Binary package hint: linux-image-2.6.20-13-generic
Still present in: linux-image-2.6.20-14-generic
+ Still present in: linux-image-2.6.20-15-generic
Upgraded to
I will now attach files from 2.6.17-11 that show the device working
properly:
Linux novosirj-laptop 2.6.17-11-generic #2 SMP Thu Feb 1 19:52:28 UTC
2007 i686 GNU/Linux
** Summary changed:
- USB fingerprint reader broken in 2.6.20-13, worked fine in 2.6.17-11
+ USB device detection problems in 2.
** Attachment added: "lspci -vvnn from 2.6.17-11"
http://librarian.launchpad.net/7286017/lspci-vvnn-working.log
--
USB device detection problems in 2.6.20
https://bugs.launchpad.net/bugs/102659
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contac
** Attachment added: "lsusb from working USB on 2.6.17-11 (note more devices
than 2.6.20-14)"
http://librarian.launchpad.net/7286021/lsusb-working.log
--
USB device detection problems in 2.6.20
https://bugs.launchpad.net/bugs/102659
You received this bug notification because you are a member
33 matches
Mail list logo
