In a previous message, John Pettigrew wrote:
It is seeming more likely to me that my USB system is not working properly somehow. Admittedly, I am running a Mantel kernel (should probably have mentioned that earlier!). When I get the chance, I'll uninstall this and reinstall the standard SuSE kernel to see whether that makes a difference.
OK, I've removed the 2.4.20-31 kernel I was running and reinstated the SuSE default k_athlon 2.4.19-4GB. This has made *some* difference - now, when I plug the device in, I get extra messages: Mar 20 12:45:29 linux kernel: hub.c: USB new device connect on bus1/1/4, assigned device number 5 Mar 20 12:45:29 linux kernel: usb.c: USB device 5 (vend/prod 0x7c4/0xac01) is not claimed by any active driver. Mar 20 12:45:30 linux kernel: Initializing USB Mass Storage driver... Mar 20 12:45:30 linux kernel: usb.c: registered new driver usb-storage Mar 20 12:45:30 linux kernel: usb-uhci.c: interrupt, status 2, frame# 1765 Mar 20 12:45:31 linux kernel: usb_control/bulk_msg: timeout Mar 20 12:45:31 linux kernel: scsi1 : SCSI emulation for USB Mass Storage devices Mar 20 12:45:31 linux kernel: Vendor: Model: Rev: Mar 20 12:45:31 linux kernel: Type: Direct-Access ANSI SCSI revision: 02 Mar 20 12:45:31 linux kernel: sd_init() Mar 20 12:45:31 linux kernel: sd: allocated major 8 Mar 20 12:45:31 linux kernel: sg: find_free_slot ...<7>sg: ... found 15:01 Mar 20 12:45:31 linux kernel: sg_attach: dev1=(21:1) Mar 20 12:45:31 linux kernel: sd_attach() Mar 20 12:45:31 linux kernel: sd: find_free_slot ...<7>sd: ... found 08:00 Mar 20 12:45:31 linux kernel: Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0 Mar 20 12:45:31 linux kernel: sd_finish() Mar 20 12:45:31 linux kernel: sd_init_onedisk (0,0), sda 08:00 Mar 20 12:45:31 linux kernel: SCSI device sda: 125440 512-byte hdwr sectors (64 MB) These messages seem to cover some of the suggestions people made (such as the scsi_ commands). However, I still get a console freeze when I try to mount the device at /dev/sda1 (which is what I think it must be - anything else I've tried has given "not a valid device" type errors). The problem with this kernel + drivers is that it won't let me use my Palm Tungsten, so I'll have to recompile myself a visor.o. Is there anything else I could try? I should probably add that this device works fine on the same box under Windows, so it's not a hardware problem. Thanks John -- John Pettigrew Headstrong Games john@headstrong-games.co.uk Fun : Strategy : Price http://www.headstrong-games.co.uk/ Board games that won't break the bank Valley of the Kings: ransack an ancient Egyptian tomb but beware of mummies!