On Fri, Apr 18, 2003 at 12:46:35PM +0200, Bernd Walter wrote: >> 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. Me too :-) > Do you get any kernel message with fdisk da0? I attacched _ALL_ my /var/log/messages, the same messages I got on console, no any other message, neither on shell nor on log file. Only those I already attached. -----8<-----[ /var/log/messages ]-----8<----- Apr 17 20:21:55 trudy kernel: da0: 15MB (31488 512 byte sectors: 64H 32S/T 15C) Apr 17 20:29:48 trudy ntpd[189]: time reset 0.390596 s Apr 17 20:50:23 trudy ntpd[189]: time reset -0.450258 s Apr 18 03:35:36 trudy kernel: umass0: at uhub0 port 1 (addr 2) disconnected Apr 18 03:35:36 trudy kernel: (da0:umass-sim0:0:0:0): lost device Apr 18 03:35:36 trudy kernel: (da0:umass-sim0:0:0:0): removing device entry Apr 18 03:35:36 trudy kernel: umass0: detached (going to sleep...) -----8<----- Nothing happens in the middle. After connecting device I tryed many times with fdisk with all /dev/da0* I can imagine :-) ([a-z], s[1-4], and so on) and dd with the same device. Nothing happens. Now I try to rebuild all modules with extra debug. Stay tuned... -- Riccardo.Received on Sat Apr 19 2003 - 05:42:01 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:04 UTC