On Mon, 22 Dec 2003, Anthony de Almeida Lopes wrote: > I want to preface this by saying I've posted this on many lists, forums and > so on... I'm only resorting to the developers because I've exahusted all > other resources........ The following is the post that I put to my distrobutions > forum.... > But first my stats: > Gentoo/PPC > 266Mhz G3 PPC > USB Keyboard: working > USB Mouse: perfect > USB Printer: works > Kernel: 2.4.22 also trying 2.6.0 and 2.6.0-test11 > > IF YOU WANT MORE ERROR MESSAGES/LOGS or dmesg OUTPUT PLEASE LET ME KNOW... > I'm willing to work with anybody who has any idea what iis wrong....
For testing purposes, it's better to use 2.6.0 rather than 2.4. Normally USB Zip drives work with no trouble at all. However, they may not have been tested on PPC systems very much. > Okay. I've recompiled the kernel litterally DOZENS of times... This is > insane! There's nothing wrong with leaving these things as modules. It makes rebuilding a lot easier, since you don't have to install a new kernel each time you try changing something. > I can to get my USB Zip drive to work no matter what I do. I've got hotplug, > usbutils, I've got usb-mass storage, scsi (and scsi ide emulation) Just to rule out any trivial possibilities, I have to ask: Have you tried using a different Zip disk in the drive? Have you tried using the drive on an Intel-based Linux system (or on any other computer at all)? > I should mention I've tried on the 2.6.0 and 2.4.22 kerels. I've tried both > vfat, msdos and hfs filesystems. > > "/dev/scsi/host2/bus0/target0/lun0: I/O error: dev 00:00, sector 0" > > at the moment there is no /dev/sda1 or 2 or 3 or 4... only /dev/sda > fdisk /dev/sda says it can't open it. Sometimes when I put a disk into the > zip drive it makes loud disk spinning noises repeatedly, over and over and > over... (this is only supposed to happen once) ive researched on google and > all > that and i really am at a loss. These error messages indicate that your system is unable to read the partition table on the Zip disk. Since it doesn't know what partitions there are, it doesn't let you see /dev/sda1, sda2, etc. It also isn't able to access any file systems you may have on the disk. > Okay.. I do have OHCI (and UHCI) > heres part of my .config > Code: > > CONFIG_USB=y > CONFIG_USB_DEBUG=y > CONFIG_USB_DEVICEFS=y > CONFIG_USB_UHCI_ALT=y > CONFIG_USB_OHCI=y > CONFIG_USB_STORAGE=m > CONFIG_USB_STORAGE_DEBUG=y > CONFIG_USB_PRINTER=y > CONFIG_USB_HID=y > CONFIG_USB_HIDINPUT=y > CONFIG_USB_SERIAL=m > > > Like I said before, everything that is a module, has at one point or another > also been tried as an in-kernel. > > I know for a fact that USB works because my (this)keyboard, mouse and > printer (which all work) are USB. That looks okay. > And heres my SCSI > > > Code: > > CONFIG_SCSI=m > CONFIG_SCSI_DEBUG_QUEUES=y > CONFIG_SCSI_MULTI_LUN=y > CONFIG_SCSI_CONSTANTS=y > CONFIG_SCSI_MESH=m > CONFIG_SCSI_MESH_SYNC_RATE=5 > CONFIG_SCSI_MESH_RESET_DELAY_MS=4000 > > > and all of these have been tried as in-kernel and module. > note too that MESH is low-level driver SCSI for my PPC. > I also have IDE SCSI emulation as M and at other times in-kernel as wel... Also looks okay... > Ok here are some more error messages I found.. I'm still hunting for more in > my logs > > usb-storage: Bad target number (4/0) > usb-storage: *** thread sleeping. > usb-storage: queuecommand() called > usb-storage: *** thread awakened. > usb-storage: Bad target number (5/0) > usb-storage: *** thread sleeping. > usb-storage: queuecommand() called > usb-storage: *** thread awakened. > usb-storage: Bad target number (6/0) > usb-storage: *** thread sleeping. > usb-storage: queuecommand() called > > > These repeat themselves forever (a while at least). That's what we need to see, but more of it and starting earlier. Try to post all the dmesg output starting from the time you plug in the drive. > here are some errors from /var/log/kernel/current > and that actually goes on forever until i disconnect the drive and/or unload > the modules.... At one point I had a 9MB log file/directory.... Those messages aren't as important as the dmesg ones. > and just for reference this is mounts output: > > Code: > > # mount /dev/sda /mnt/usbzip -t hfs > mount: wrong fs type, bad option, bad superblock on /dev/sda, > or too many mounted file systems > > > or plain > Code: > > #fdisk /dev/sda > Unable to read /dev/sda That's what you expect to see when the system can't read the partition table from the disk. > Anyway... Thanks for any help you can give...... I'll keep digging on > google, forums and other lists too.... > If anyone at all can help me with this I'd soooo appreciate it.... I just am > running out of things to try... This is insane...,. Like I said, post more of the dmesg log. And use 2.6.0. If this really is a PPC-specific problem, the sooner we can find and fix it the better. Alan Stern ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
