Bernd Walter <ticso_at_cicely9.cicely.de> writes: > On Fri, Apr 18, 2003 at 09:59:45AM +0200, Riccardo Torrini wrote: > > On Fri, Apr 18, 2003 at 02:24:48AM +0200, Bernd Walter wrote: > > > > >> # ls -ln /dev/da0* > > >> crw-r----- 1 0 5 4, 20 Apr 17 20:09 /dev/da0 > > >> > > >> # mount -tmsdos /dev/da0 /dist > > >> msdosfs: /dev/da0: Invalid argument > > > > > msdosfs usually lives on slices. > > > > I know that, but DEVFS create _only_ /dev/da0 :-( > > That doesn't mean anything as devicenodes can be created on demand. > > > Apr 17 20:21:52 trudy kernel: umass0: DataFab Systems Inc. USB CF, rev 1.10/3.06, addr 2 > > Apr 17 20:21:55 trudy kernel: da0 at umass-sim0 bus 0 target 0 lun 0 > > Apr 17 20:21:55 trudy kernel: da0: <OEI-Link Media Reader 3.06> Removable Direct Access SCSI-0 device > > Apr 17 20:21:55 trudy kernel: da0: 1.000MB/s transfers > > Apr 17 20:21:55 trudy kernel: da0: 15MB (31488 512 byte sectors: 64H 32S/T 15C) > > (going to sleep...) > > -----8<----- > > That probing worked so far was clear. > What I need is to know why fdisk and dd failed. > Do you get any kernel message with fdisk da0? > Just in case it might help, have a look at: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/50633 FWIW I found that a script that: - sleeps 5 seconds - if /dev/da0s1 doesn't exist, tries to mount /dev/da0 (and always fails) - mounts /dev/da0s1 works, if I hook it to usbd. -- Dan PellegReceived on Fri Apr 18 2003 - 03:27:13 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:04 UTC