Zaurus SL-5500 is not being detected

[mark541]

I recently upgraded several packages when prompted by the update manager. After the update, my Zaurus SL-5500 is not being detected.

This is what now prints in /var/log/messages when I plug in the Zaurus:

Mar 26 23:22:56 localhost kernel: [ 645.828295] usb 3-1: new full speed USB device using uhci_hcd and address 6
Mar 26 23:22:56 localhost kernel: [ 646.269531] usb 3-1: new full speed USB device using uhci_hcd and address 7
Mar 26 23:22:57 localhost kernel: [ 646.680816] usb 3-1: new full speed USB device using uhci_hcd and address 8
Mar 26 23:22:57 localhost kernel: [ 647.152013] usb 3-1: new full speed USB device using uhci_hcd and address 9

Three days earlier, my last successful detection as listed in /var/log/messages was this:

Mar 23 20:31:48 localhost kernel: [597892.282777] usb0: register usbnet at usb-0000:00:10.2-1, Sharp Zaurus SL-5x00, 66:f4:3f:a4:1a:16
Mar 23 20:31:49 localhost usb.agent[26086]: usbnet: already loaded

The only thing upgraded since March 23 at 8pm (the time and date of the last successful detection) are these packages:

libc6-i686_2.3.5-1ubuntu12.5.10.1_i386.deb
locales_2.3.5-1ubuntu12.5.10.1_all.deb
libc6_2.3.5-1ubuntu12.5.10.1_i386.deb

I suspect the libc6 packages are to blame, but I'm not sure what to do next.

[Phil Bull (philbull)]

Thanks for the report.

Could you run the following command from the terminal, please?

lshal > ~/lshal.txt

Then attach a copy of 'lshal.txt' in your home directory to this bug report.

Thanks

[mark541 (pinjoh541)]

Ran "lshal" as requested to provide additional information.

[Daniel Holbach (dholbach)]

Is this still a problem in Dapper or Edgy?

[mark541 (pinjoh541)]

No, the problem resolved after an upgrade. Don't know what triggered the
problem or the resolution, but it works now.

Thanks for the follow up.
Mark

Daniel Holbach wrote:
> Is this still a problem in Dapper or Edgy?
>
> ** Changed in: glibc (Ubuntu)
> Status: Unconfirmed => Needs Info
>

[Daniel Holbach (dholbach)]

Closing the bug, thanks for following up and please reopen if it should happen again.