From: Francisco J Ballesteros <nemo@lsub.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] usb flash drive with ext2
Date: Thu, 12 Jan 2012 12:30:55 +0100 [thread overview]
Message-ID: <CA+N-5bagNq17-rBcMUU1soTi7n=3pyg+6Adaf0BNdOzZVc2PRQ@mail.gmail.com> (raw)
In-Reply-To: <24557a0ed0b4bbb38f0b167cc7c7d4f9@hamnavoe.com>
you can enable debug diagnostics for devices by using the usbd ctl file.
I don´t remember which ones are the strings (see the man, probably) but
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 8.07 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. You can't just start 'usb/disk -d' because the usb/disk
> 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.
>
>
next prev parent reply other threads:[~2012-01-12 11:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 9:45 Rudolf Sykora
2012-01-11 10:06 ` Richard Miller
2012-01-11 10:15 ` Rudolf Sykora
2012-01-12 9:44 ` Rudolf Sykora
2012-01-12 10:07 ` Richard Miller
2012-01-12 10:21 ` Rudolf Sykora
2012-01-12 10:26 ` Richard Miller
2012-01-12 10:40 ` Rudolf Sykora
2012-01-12 11:25 ` Richard Miller
2012-01-12 11:30 ` Francisco J Ballesteros [this message]
2012-01-12 12:05 ` Richard Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+N-5bagNq17-rBcMUU1soTi7n=3pyg+6Adaf0BNdOzZVc2PRQ@mail.gmail.com' \
--to=nemo@lsub.org \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).