Re: [Xen-devel] Re: Latest USB code

[Hien Nguyen <hien1@xxxxxxxxxx>]

Harry,

I know that I missed something. Please tell me what to do to configure the usb cdrom correctly .

How do I know which one is the usb cdrom device that shows up in /sys/bus/usb/devices ?

bl3-5:/sys/bus/usb/devices # ls -lt
total 0
drwxr-xr-x 2 root root 0 Dec 12 13:22 .
lrwxrwxrwx 1 root root 0 Dec 12 13:22 1-0:1.0 -> ../../../devices/pci0000:00/0000:00:0f.2/usb1/1-0:1.0
lrwxrwxrwx 1 root root 0 Dec 12 13:22 1-2 -> ../../../devices/pci0000:00/0000:00:0f.2/usb1/1-2
lrwxrwxrwx 1 root root 0 Dec 12 13:22 1-2.1 -> ../../../devices/pci0000:00/0000:00:0f.2/usb1/1-2/1-2.1
lrwxrwxrwx 1 root root 0 Dec 12 13:22 1-2.1:1.0 -> ../../../devices/pci0000:00/0000:00:0f.2/usb1/1-2/1-2.1/1-2.1:1.0
lrwxrwxrwx 1 root root 0 Dec 12 13:22 1-2.1:1.1 -> ../../../devices/pci0000:00/0000:00:0f.2/usb1/1-2/1-2.1/1-2.1:1.1
lrwxrwxrwx 1 root root 0 Dec 12 13:22 1-2:1.0 -> ../../../devices/pci0000:00/0000:00:0f.2/usb1/1-2/1-2:1.0
lrwxrwxrwx 1 root root 0 Dec 12 13:22 usb1 -> ../../../devices/pci0000:00/0000:00:0f.2/usb1
lrwxrwxrwx 1 root root 0 Dec 12 13:22 1-1 -> ../../../devices/pci0000:00/0000:00:0f.2/usb1/1-1
lrwxrwxrwx 1 root root 0 Dec 12 13:22 1-1.1 -> ../../../devices/pci0000:00/0000:00:0f.2/usb1/1-1/1-1.1
lrwxrwxrwx 1 root root 0 Dec 12 13:22 1-1.1:1.0 -> ../../../devices/pci0000:00/0000:00:0f.2/usb1/1-1/1-1.1/1-1.1:1.0
lrwxrwxrwx 1 root root 0 Dec 12 13:22 1-1.3 -> ../../../devices/pci0000:00/0000:00:0f.2/usb1/1-1/1-1.3
lrwxrwxrwx 1 root root 0 Dec 12 13:22 1-1.3:1.0 -> ../../../devices/pci0000:00/0000:00:0f.2/usb1/1-1/1-1.3/1-1.3:1.0
lrwxrwxrwx 1 root root 0 Dec 12 13:22 1-1:1.0 -> ../../../devices/pci0000:00/0000:00:0f.2/usb1/1-1/1-1:1.0
lrwxrwxrwx 1 root root 0 Dec 12 13:22 1-2.3 -> ../../../devices/pci0000:00/0000:00:0f.2/usb1/1-2/1-2.3
lrwxrwxrwx 1 root root 0 Dec 12 13:22 1-2.3:1.0 -> ../../../devices/pci0000:00/0000:00:0f.2/usb1/1-2/1-2.3/1-2.3:1.0
lrwxrwxrwx 1 root root 0 Dec 12 13:22 1-2.3:1.1 -> ../../../devices/pci0000:00/0000:00:0f.2/usb1/1-2/1-2.3/1-2.3:1.1
drwxr-xr-x 4 root root 0 Dec 7 13:20 ..
------
Also modules loaded included here:

bl3-5:/sys/bus/usb/devices # lsmod
Module Size Used by
ipt_physdev 2640 2
iptable_filter 2944 1
ip_tables 19072 2 ipt_physdev,iptable_filter
udf 90756 0
thermal 10696 0
processor 15492 1 thermal
fan 3428 0
button 5136 0
battery 7780 0
ac 3588 0
qla2300 123104 0
qla2xxx 89936 8 qla2300
scsi_transport_fc 25952 1 qla2xxx
sworks_agp 7712 0
agpgart 31080 1 sworks_agp
subfs 6048 1

------------
Attached the .config file for dom0 on HS20 blade:
(See attached file: config.dom0.blade)

Regards,

Hien Nguyen
Linux Technology Center AUSTIN
Phone: (512) 838-4140 Tie Line: 678-4140
e-mail: hien1@xxxxxxxxxx

Harry Butterworth <harry@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>

Harry Butterworth <harry@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>

12/07/2005 05:05 PM

To	Hien Nguyen/Austin/IBM@IBMUS
cc	xen-devel@xxxxxxxxxxxxxxxxxxx
Subject	Re: [Xen-devel] Re: Latest USB code

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@xxxxxxxxxx
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
> 
-- 
Harry Butterworth <harry@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>

config.dom0.blade
Description: Binary data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel