Bug#311222: marked as done (kernel-image 2.6.11-5 not detecting Zaurus 5500)
Your message dated Sun, 7 Aug 2005 14:24:58 +0200
with message-id <20050807122458.GO1807@baikonur.stro.at>
and subject line kernel-image 2.6.11-5 not detecting Zaurus 5500
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 30 May 2005 04:41:16 +0000
>From markj_mail@sbcglobal.net Sun May 29 21:41:16 2005
Return-path: <markj_mail@sbcglobal.net>
Received: from smtp816.mail.sc5.yahoo.com [66.163.170.2]
by spohr.debian.org with smtp (Exim 3.35 1 (Debian))
id 1Dcc5U-0002tE-00; Sun, 29 May 2005 21:41:16 -0700
Received: from unknown (HELO ?192.168.128.32?) (mjohnson?mail@sbcglobal.net@69.208.181.50 with plain)
by smtp816.mail.sc5.yahoo.com with SMTP; 30 May 2005 04:41:15 -0000
Message-ID: <429A996B.3030805@sbcglobal.net>
Date: Sun, 29 May 2005 23:41:15 -0500
From: Mark Johnson <markj_mail@sbcglobal.net>
User-Agent: Debian Thunderbird 1.0.2 (X11/20050331)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: submit@bugs.debian.org
Subject: kernel-image 2.6.11-5 not detecting Zaurus 5500
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: kernel-image-2.6.11-1-386
Version: 2.6.11-5
I am running Debian Sid. Yesterday I upgraded my kernel image. After the
upgrade, my kernel image was 2.6.11-5. After a reboot, my Zaurus 5500
(running OpenZaurus 3.2) was no longer detected.
My kernel image was already 2.6.11. Based on information from the kernel
image change logs, there have been three kernel image updates for this
level of the kernel:
Name version
------------------------- --------
kernel-image-2.6.11-1-386 2.6.11-2 for i386
kernel-image-2.6.11-1-386 2.6.11-3 for i386
kernel-image-2.6.11-1-386 2.6.11-5 for i386
Based on this, it would appear that the problem occured either with
2.6.11-3 or 2.6.11-5. I cannot be more specific, since I am not certain
if I was running 2.6.11-2 or 2.6.11-3 prior to the problem.
While running kernel image 2.6.11-5, here are excerpts from commands
that may help show what's happening:
Debian (sid)
====================
edited results from a dpkg listing showing my current kernel verions and
the usb packages:
# dpkg -l
Name version
------------------------- --------
kernel-image-2.6.11-1-386 2.6.11-5 for i386
kernel-image-2.6.10-1-386 2.6.10-4 for i386
libusb-0.1-4 0.1.10a-11
usbutils 0.71-1
Results of a usb listing using the 2.6.11-5 kernel image. My Zaurus was
connected prior to running this command. I would expect it to be on Bus
004, since I connected it to the USB hub (the "Tetrahub").
# lsusb
Bus 004 Device 002: ID 04b4:6560 Cypress Semiconductor Corp. CY7C65640
USB-2.0 "TetraHub"
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
These are the messages generated from the connection of the Zaurus. I've
excluded earlier messages (determined by running dmesg before connecting
the Zaurus, and comparing with dmesg output after connection).
# dmesg
usb 4-1.1: new full speed USB device using ehci_hcd and address 3
usb 4-1.1: khubd timed out on ep0in
usb 4-1.1: device not accepting address 3, error -32
usb 4-1.1: new full speed USB device using ehci_hcd and address 4
usb 4-1.1: device descriptor read/64, error -32
usb 4-1.1: device descriptor read/64, error -32
Since I still had an old 2.6.10 kernel installed, I tried booting from
it, making *no* other changes to the system. After rebooting, I then
connected the Zaurus. After I plug in the Zaurus, dmesg shows this:
# dmesg
usb 4-1.1: new full speed USB device using ehci_hcd and address 3
usb0: register usbnet at usb-0000:00:10.3-1.1, Sharp Zaurus SL-5x00
usbcore: registered new driver usbnet
usb0: no IPv6 routers present
Results from lsusb running 2.6.10-4 kernel image (Zaurus is plugged into
the same "Tetrahub").
# lsusb
Bus 004 Device 003: ID 04dd:8004 Sharp Corp. Zaurus SL-5000D/SL-5500 PDA
Bus 004 Device 002: ID 04b4:6560 Cypress Semiconductor Corp. CY7C65640
USB-2.0 "TetraHub"
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
Any ideas on what happened? Since it seems that that there are 3
versions of kernel-image-2.6.11-1-386, and one (or both) of the earlier
versions did function correctly, the incorrect behavior must have crept
in with either version 2.6.11-3 or 2.6.11-5. I've checked the
kernel-image 2.6.11 doc files "changelog.Debian.gz" and
"Debian.src.changelog.gz", but I didn't see anything that seemed to be
related to the Zaurus or to usbnet.
Prior to the error, here is a line from my kern.log:
May 11 14:58:23 localhost kernel: Linux version 2.6.11-1-386
(dilinger@mouth) (gcc version 3.3.5 (Debian 1:3.3.5-12)) #1 Mon Apr
2501:18:07 UTC 2005
After the upgrade, here is the relevant line from the kern.log:
/var/log/kern.log:May 29 00:23:49 localhost kernel: Linux version
2.6.11-1-386 (dilinger@mouth) (gcc version 3.3.6 (Debian 1:3.3.6-5)) #1
Fri May 20 06:15:52 UTC 2005
So it appears that a different version of gcc was used with the earlier
kernel image that worked correctly. I do not know if this is relevant.
Unfortunately, I do not have the old kernel-image deb file, so I cannot
be more specific as to the exact version.
Please let me know if there is anything else I can get for you to help
in tracking down the source of this bug.
Thanks,
Mark Johnson
---------------------------------------
Received: (at 311222-done) by bugs.debian.org; 7 Aug 2005 12:25:38 +0000
>From max@baikonur.stro.at Sun Aug 07 05:25:38 2005
Return-path: <max@baikonur.stro.at>
Received: from baikonur.stro.at [213.239.196.228]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1E1kDh-0005Nc-00; Sun, 07 Aug 2005 05:25:37 -0700
Received: by baikonur.stro.at (Postfix, from userid 1001)
id F09835C010; Sun, 7 Aug 2005 14:24:58 +0200 (CEST)
Date: Sun, 7 Aug 2005 14:24:58 +0200
From: Maximilian Attems <debian@sternwelten.at>
To: 311222-done@bugs.debian.org, 311221-done@bugs.debian.org,
313534-done@bugs.debian.org
Subject: Re: kernel-image 2.6.11-5 not detecting Zaurus 5500
Message-ID: <20050807122458.GO1807@baikonur.stro.at>
References: <20050726155930.GP382@baikonur.stro.at> <[🔎] 20050807120826.GA1678@radix50.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[🔎] 20050807120826.GA1678@radix50.net>
User-Agent: Mutt/1.5.9i
X-Virus-Scanned: by Amavis (ClamAV) at stro.at
Delivered-To: 311222-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
X-CrossAssassin-Score: 2
On Sun, Aug 07, 2005 at 02:08:26PM +0200, Baurzhan Ismagulov wrote:
> Hello Maximilian,
>
> On Tue, Jul 26, 2005 at 05:59:30PM +0200, Maximilian Attems wrote:
> > did you test the 2.6.12 linux image from unstable?
>
> Took some time to understand that the new package was called
> linux-image.
>
> I tried it, it works for me.
>
> We could probably close #311221, #311222, and #313534.
>
> With kind regards,
> Baurzhan.
thanks for your quick feedback and aboves bug pointers. :)
closing also those.
if your pain subsist with linux image 2.6.12 please reopen.
thanks
--
maks
Reply to: