Subject: Re: problems with USB floppy
To: Freidank, Kenneth <Kenneth.Freidank@delta.com>
From: Stephen Borrill <netbsd@precedence.co.uk>
List: netbsd-users
Date: 11/21/2005 16:43:17
On Mon, 21 Nov 2005, Steven M. Bellovin wrote:

> In message <21B3CF19E2A7B048A66473CB6E9E6EC50BA289@satladmdlmb37.delta.rl.delta
> .com>, "Freidank, Kenneth" writes:
>> I just installed NetBSD 2.1 on my Thinkpad and get the same messages
>> when using my USB floppy.
>> Did you ever resolve the problem?  I would like to know your solution as
>> I have yet to find one.
>
> I frankly don't recall; that was quite a while ago.  But a *lot* of USB
> problems are fixed in 3.0, I believe; you may want to boot a 3.0
> INSTALL kernel and see what happens when you plug the drive in.

I tried it with my floppy that I gave up using back in the 1.6 era:

With 2.0 and 3.0 I get the same dmesg:
umass1 at uhub2 port 2 configuration 1 interface 0
umass1: NEC NEC USB UF000x, rev 1.10/1.50, addr 2
umass1: using UFI over CBI with CCI
atapibus2 at umass1: 2 targets
sd1 at atapibus2 drive 0: <NEC, USB UF000x, 1.50> disk removable
sd1: 1440 KB, 80 cyl, 2 head, 18 sec, 512 bytes/sect x 2880 sectors

and disklabel:

# /dev/rsd1d:
type: ATAPI
disk: mydisk
label: fictitious
flags: removable
bytes/sector: 512
sectors/track: 18
tracks/cylinder: 2
sectors/cylinder: 36
cylinders: 80
total sectors: 2880
rpm: 10240
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0           # microseconds
track-to-track seek: 0  # microseconds
drivedata: 0

8 partitions:
#        size    offset     fstype [fsize bsize cpg/sgs]
  d:      2880         0     unused      0     0        # (Cyl.      0 -    79)
  e: 544437093 1919950958    unknown                     # (Cyl. 53331971+- 68455223+)
  f: 538976288 1330184202    unknown                     # (Cyl. 36949561+- 51921124+)
  g: 1398362912 538989391    unknown                     # (Cyl. 14971927+- 53815341+)
  h:     21337 1394627663    unknown                     # (Cyl. 38739657+- 38740249+)

Note the duff partition data, so "mount_msdos /dev/sd0d /mnt" should be 
used. On 3.0_BETA this works fine, on 2.0_STABLE I get
"mount_msdos: /dev/sd0d on /mnt: Invalid argument"

-- 
Stephen