OESF Portables Forum
Everything Else => Desktop Operating Systems Issues => Zaurus General Forums => Archived Forums => Linux Issues => Topic started by: rjray on October 27, 2004, 09:51:29 pm
-
I followed the Wiki page closely, installing usbnet-standalone. Turns out I already had a usbnet.o module, and when the standalone package didn't work, I tried the originally. I always get the same results. From my kernal messages log (I'm running Fedora Core 1,current kernel is kernel-smp-2.4.22-1.2199.nptl):
Oct 27 18:42:33 tzimisce kernel: hub.c: new USB device 00:1d.1-1.1, assigned address 37
Oct 27 18:42:33 tzimisce kernel: usb.c: USB device 37 (vend/prod 0x4dd/0x9032) is not claimed by any active driver.
Oct 27 18:42:36 tzimisce usb.agent[7766]: missing kernel or user mode driver acm
Oct 27 18:42:36 tzimisce kernel: sda: Unit Not Ready, sense:
Oct 27 18:42:36 tzimisce kernel: Info fld=0xa00 (nonstd), Current 00:00: sense key Not Ready
Oct 27 18:42:36 tzimisce kernel: sda : READ CAPACITY failed.
Oct 27 18:42:36 tzimisce kernel: sda : status = 1, message = 00, host = 0, driver = 08
Oct 27 18:42:36 tzimisce kernel: Info fld=0xa00 (nonstd), Current sd00:00: sense key Not Ready
Oct 27 18:42:36 tzimisce kernel: sda : block size assumed to be 512 bytes, disk size 1GB.
Oct 27 18:42:36 tzimisce kernel: sda: test WP failed, assume Write Enabled
Oct 27 18:42:36 tzimisce kernel: sda: I/O error: dev 08:00, sector 0
Oct 27 18:42:36 tzimisce kernel: I/O error: dev 08:00, sector 0
Oct 27 18:42:36 tzimisce kernel: unable to read partition table
Oct 27 18:42:37 tzimisce kernel: sda: Unit Not Ready, sense:
Oct 27 18:42:37 tzimisce kernel: Info fld=0xa00 (nonstd), Current 00:00: sense key Not Ready
Oct 27 18:42:37 tzimisce kernel: sda : READ CAPACITY failed.
Oct 27 18:42:37 tzimisce kernel: sda : status = 1, message = 00, host = 0, driver = 08
Oct 27 18:42:37 tzimisce kernel: Info fld=0xa00 (nonstd), Current sd00:00: sense key Not Ready
Oct 27 18:42:37 tzimisce kernel: sda : block size assumed to be 512 bytes, disk size 1GB.
Oct 27 18:42:37 tzimisce kernel: sda: test WP failed, assume Write Enabled
Oct 27 18:42:37 tzimisce kernel: sda: I/O error: dev 08:00, sector 0
Oct 27 18:42:37 tzimisce kernel: I/O error: dev 08:00, sector 0
Oct 27 18:42:37 tzimisce kernel: unable to read partition table
Oct 27 18:42:38 tzimisce devlabel: devlabel service started/restarted
And with all that, no actual connection between the two. I cannot create a usb0 interface device, and nothing new appears to kudzu (the new-hardware sniffer). I do have a module "acm.o" (under the usb hierarchy), but even with that force-loaded via modprobe, I get the above. I've had USB2.0 issues with flash drives, so I also tried plugging in the sync cable to a USB1.1 hub, to force it down to 1.1 when presented to the kernel (it's the only way I can get my Lexar to mount properly). Again, no difference.
I love this thing, but I'd like to be able to at least back it up. Actually exchanging data with my desktop would be just keen.
Randy
-
It looks like your desktop box thinks that the Z is a mass storage device.
What does 'lsmod' show on the Z?
Si
-
What does 'lsmod' show on the Z?
pxa_bi
net_fd
usbdcore
prism2_usb
p80211
usbdmonitor
sharp_mmcsd_m
vtty
usb_ohci_tc6393
usbcore
Keep in mind, this is a factory-fresh SL-6000L. I haven't even been able to install the console application from the CD (I got the above via Konsole, downloaded from ZSI).
Randy
-
are you using the docking station or direct usb from the sl-6000
-
Docking station...
-
what linux os please ?
give us as specific info as possible!!
you already did, sorry, didn't look closely enough
-
Oct 27 18:42:36 tzimisce usb.agent[7766]: missing kernel or user mode driver acm
Oct 27 18:42:36 tzimisce kernel: sda: Unit Not Ready, sense:
I wonder if the first of these is important?
Do you have some other mass storage device attached (as this definitely looks like the sort of output I get when I attach my Z for mass storage).
I think it's possible with the 6000 to change to mass storage mode. Try doing this and attaching, then switch back and try attaching again (in net mode).
Si