From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <24557a0ed0b4bbb38f0b167cc7c7d4f9@hamnavoe.com> References: <24557a0ed0b4bbb38f0b167cc7c7d4f9@hamnavoe.com> Date: Thu, 12 Jan 2012 12:30:55 +0100 Message-ID: From: Francisco J Ballesteros To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] usb flash drive with ext2 Topicbox-Message-UUID: 58c5de00-ead7-11e9-9d60-3106f5b1d025 you can enable debug diagnostics for devices by using the usbd ctl file. I don=C2=B4t remember which ones are the strings (see the man, probably) bu= t I remember you can enable debug flags without restarting it. You could try to locate them and enable debug for that, plug the disk again, disable debug for that. IIRC, that is. On Thu, Jan 12, 2012 at 12:25 PM, Richard Miller <9fans@hamnavoe.com> wrote= : >> /dev/usb/ep4.0 lun 0: inquiry Generic Flash Disk =C2=A0 =C2=A0 =C2=A08.0= 7 geometry 8007680 512 >> >> ... so I'd think this is ok ... > > My next step would be to get more diagnostic output from usb/disk. > This is no longer easy with the new monolithic usb driver > architecture. =C2=A0You can't just start 'usb/disk -d' because the usb/di= sk > embedded into usb/usbd will have started automatically and seized > control of the device when you plugged it in. > > I think you will need to generate a new usbd with the disk driver > configured out (see /sys/src/cmd/usb/usbd/usbdb), then kill the usbd > which is embedded into the kernel and start your new one, before > running usb/disk. > >