[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: usb 2

Thanks for the suggestions everyone. I did some more testing today, and these are my findings:
The drive is a new 1GB stick drive that says "usb2.0 flash drive" right on it. (Until recently many devices here were labelled as usb2.0 *and* 1.1, which is why I thought that might be the problem).
The drive shows up and functions normally under edubuntu, booted from the hard drive.
When the same machine boots as a diskless skolelinux workstation, the drive fails to appear on the gnome desktop. Looking for it in /media/usb reveals an empty drive of 1Gb, which cannot be written to. 
The workstations are using kernel 2.6.8-3-686
This is the output of /var/log/messages. When compared to a working usb drive, there are some lines missing regarding mounting. 

******** new drive **********
Jan 29 14:53:27 static01 kernel: scsi2 : SCSI emulation for USB Mass Storage devices Jan 29 14:53:27 static01 kernel: Vendor: BUFFALO Model: USB Flash Disk Rev: 3.10 Jan 29 14:53:27 static01 kernel: Type: Direct-Access ANSI SCSI revision: 02 
Jan 29 14:53:27 static01 kernel: usbcore: registered new driver usb-storage
Jan 29 14:53:27 static01 kernel: USB Mass Storage support registered.
Jan 29 14:53:27 static01 usb.agent[5371]: usb-storage: loaded successfully Jan 29 14:53:28 static01 kernel: SCSI device sda: 2015232 512-byte hdwr sectors (1032 MB) 
Jan 29 14:53:28 static01 kernel: sda: assuming Write Enabled
Jan 29 14:53:28 static01 kernel: /dev/scsi/host2/bus0/target0/lun0: [CUMANA/ADFS] p1<5>Attached scsi removable disk sda at scsi2, channel 0, id 0, lun 0 Jan 29 14:53:28 static01 scsi.agent[5428]: sd_mod: loaded sucessfully (for disk) Jan 29 14:53:36 static01 kernel: nfs warning: mount version older than kernel 

******** working drive ************
Jan 29 15:31:17 static01 kernel: usb 4-1: new full speed USB device using address 2 Jan 29 15:31:17 static01 kernel: scsi3 : SCSI emulation for USB Mass Storage devices Jan 29 15:31:17 static01 kernel: Vendor: Model: Rev: Jan 29 15:31:17 static01 kernel: Type: Direct-Access ANSI SCSI revision: 02 Jan 29 15:31:17 static01 kernel: SCSI device sda: 128000 512-byte hdwr sectors (66 MB) 
Jan 29 15:31:17 static01 kernel: sda: assuming Write Enabled
Jan 29 15:31:17 static01 kernel:  /dev/scsi/host3/bus0/target0/lun0: p1
Jan 29 15:31:17 static01 kernel: Attached scsi removable disk sda at scsi3, channel 0, id 0, lun 0 Jan 29 15:31:17 static01 scsi.agent[6202]: sd_mod: loaded sucessfully (for disk) 
Jan 29 15:31:17 static01 usb.agent[6196]:      usb-storage: already loaded
Jan 29 15:31:19 static01 usbmount[6264]: executing command: mount -tvfat -osync,noexec,nodev,noatime,umask=0,gid=floppy,dmask=0007,fmask=0117 /dev/sda1 /media/usb0 Jan 29 15:31:19 static01 usbmount[6264]: executing command: run-parts /etc/usbmount/mount.d Jan 29 15:31:26 static01 kernel: nfs warning: mount version older than kernel 


cheers

Nigel

Kevin Mark wrote:


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, Jan 25, 2007 at 10:37:31AM +0100, Gjermund Skogstad wrote:

torsdag 25. januar 2007, 10:14, skrev nigel barker:

Thanks for the reply Gjermund. One of the machines in question spends
most of its time as a Skolelinux diskless workstation, but occasionally
gets booted into Edubuntu from its hard drive. The Usb 2 drives work in
that case, so that's why I thought it must be something to do with
skolelinux.

Thanks,
Nigel
Interesting ... What kernel option do you use in Skolelinux, 2.4 or the newer 2.6 option? My experience is on the 2.6 kernel so that might be it, but it is also a possibility that this is a matter of memory device id missing in database. If that's the case it would probably not help upgrading the kernel. Not even to latest compatible version (which you in any case would have to keep security patched on your own).
(Some years ago I used to add PCMCIA and USB hw id's by hand to get my stuff working, but i scarcely see that as a liable option for your scenario :)
Sorry, I'm out of ideas to a solution for you. (.. unless of course you are running a 2.4 kernel and can make a successful switch to the 2.6 option.) 

:)

Gjermund

Hi Nigel,
have you attempted to extract some lines from /var/log/messages or dmesg
to see if they shed some light on the issue?
cheers,
Kev
- -- | .''`. == Debian GNU/Linux == | my web site: | 
| : :' :      The  Universal     |mysite.verizon.net/kevin.mark/|
| `. `'      Operating System    | go to counter.li.org and     |
|   `-    http://www.debian.org/ |    be counted! #238656       |
|   my keysever: subkeys.pgp.net |     my NPO: cfsg.org         |
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFFuITxv8UcC1qRZVMRAtbIAJ4hgxioH77cPIi/eGl76su2KBXVrQCcC7Ov
QvVj1u+6tgpTEJhJVKq8Wb0=
=0ruA
-----END PGP SIGNATURE-----
Reply to: