From: Harry Butterworth <harry@hebutterworth.freeserve.co.uk>
To: Hien Nguyen <hien1@us.ibm.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: Latest USB code
Date: Wed, 07 Dec 2005 23:05:54 +0000 [thread overview]
Message-ID: <1133996754.5004.47.camel@localhost> (raw)
In-Reply-To: <OFD8D102CD.B6A49F7A-ON872570D0.00734D5B-862570D0.007368C8@us.ibm.com>
I can't tell what's wrong or very much about how far you got from your
note below. What you are doing has never been tried before so it may
very well simply not work yet but if you are happy to have a go anyway,
here's how to proceed:
It would be a good start to check that a directory for the usb cdrom
device appears in /sys/bus/usb/devices in the front-end domain.
If it doesn't then it means that the USB split driver hasn't been
installed properly or isn't configured properly or has a bug in this
area.
Some things to check in this case would be whether the front-end and
back-end USB driver modules were loaded and whether the front-end domain
configuration contained a line to configure the mapping of the back-end
USB port to the front end domain. Also check that you are actually
configuring the correct back-end port here. You should also disable the
usb driver that would otherwise drive the cdrom in the backend domain
otherwise it may grab the cdrom before the split driver gets a chance.
If a directory for the cdrom device does appear in the
front-end /sys/bus/usb/devices then that means that you have
successfully mapped the cdrom device into the front-end domain and are
halfway towards getting it working.
Then you need to make sure that you have a USB driver for the cdrom
device loaded in the front-end domain.
After that, it may work.
You will of course need to put a cd into the drive :-)
If you are still having problems then you can rebuild the USB back and
front end drivers with tracing turned on (it's a kernel option). Then
retry your test and post me the syslogs containing the trace output of
the back end and front end drivers.
This should be enough information for me to debug the problem.
Thanks for trying this out.
Harry
On Wed, 2005-12-07 at 15:01 -0600, Hien Nguyen wrote:
> I installed both patches ( xenidc and usb) to an HS20 blade which has
> an USB cdrom. Also I installed submount-0.9-33.6 in order to mount CDROM.
> It ends up to an error when I try to access the CD.
> "/media/cdrom; No medium found"
>
> I have the following line in /etc/fstab:
> /dev/cdrom /media/cdrom subfs fs=cdfss,ro 0 0
> ( Tried with different fs like. fs=iso9660 also has the same problem)
>
> dmesg has:
> subfs: submountd execution failure. Error 256
> Anyone has any ideas ?
>
> Regards,
>
> Hien Nguyen
> Linux Technology Center AUSTIN
> Phone: (512) 838-4140 Tie Line: 678-4140
> e-mail: hien1@us.ibm.com
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
--
Harry Butterworth <harry@hebutterworth.freeserve.co.uk>
next prev parent reply other threads:[~2005-12-07 23:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-07 21:01 Latest USB code Hien Nguyen
2005-12-07 23:05 ` Harry Butterworth [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-12 19:38 Hien Nguyen
2005-12-13 11:37 ` Harry Butterworth
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=1133996754.5004.47.camel@localhost \
--to=harry@hebutterworth.freeserve.co.uk \
--cc=hien1@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.