* Re: Latest USB code
@ 2005-12-07 21:01 Hien Nguyen
2005-12-07 23:05 ` Harry Butterworth
0 siblings, 1 reply; 4+ messages in thread
From: Hien Nguyen @ 2005-12-07 21:01 UTC (permalink / raw)
To: xen-devel
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Re: Latest USB code
2005-12-07 21:01 Latest USB code Hien Nguyen
@ 2005-12-07 23:05 ` Harry Butterworth
0 siblings, 0 replies; 4+ messages in thread
From: Harry Butterworth @ 2005-12-07 23:05 UTC (permalink / raw)
To: Hien Nguyen; +Cc: xen-devel
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>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Re: Latest USB code
@ 2005-12-12 19:38 Hien Nguyen
2005-12-13 11:37 ` Harry Butterworth
0 siblings, 1 reply; 4+ messages in thread
From: Hien Nguyen @ 2005-12-12 19:38 UTC (permalink / raw)
To: Harry Butterworth; +Cc: xen-devel, plars
[-- Attachment #1.1.1: Type: text/plain, Size: 7369 bytes --]
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@us.ibm.com
Harry Butterworth
<harry@hebutterwo
rth.freeserve.co. To
uk>
Hien Nguyen/Austin/IBM@IBMUS
12/07/2005 05:05 cc
PM xen-devel@lists.xensource.com
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@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>
[-- Attachment #1.1.2: Type: text/html, Size: 9658 bytes --]
[-- Attachment #1.2: graycol.gif --]
[-- Type: image/gif, Size: 105 bytes --]
[-- Attachment #1.3: pic07822.gif --]
[-- Type: image/gif, Size: 1255 bytes --]
[-- Attachment #1.4: ecblank.gif --]
[-- Type: image/gif, Size: 45 bytes --]
[-- Attachment #2: config.dom0.blade --]
[-- Type: application/octet-stream, Size: 14277 bytes --]
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.12.6-xen0
# Wed Dec 7 14:00:31 2005
#
CONFIG_XEN=y
CONFIG_ARCH_XEN=y
CONFIG_NO_IDLE_HZ=y
#
# XEN
#
# CONFIG_XEN_PRIVILEGED_GUEST is not set
# CONFIG_XEN_PHYSDEV_ACCESS is not set
# CONFIG_XEN_IDC_TRACE is not set
# CONFIG_XEN_TPMDEV_FRONTEND is not set
# CONFIG_XEN_TPMDEV_BACKEND is not set
CONFIG_XEN_BLKDEV_FRONTEND=y
CONFIG_XEN_NETDEV_FRONTEND=y
CONFIG_XEN_USBDEV_FRONTEND=m
# CONFIG_XEN_USBDEV_FRONTEND_TRACE is not set
# CONFIG_XEN_BLKDEV_TAP is not set
# CONFIG_XEN_SHADOW_MODE is not set
CONFIG_XEN_SCRUB_PAGES=y
CONFIG_XEN_X86=y
# CONFIG_XEN_X86_64 is not set
CONFIG_HAVE_ARCH_ALLOC_SKB=y
CONFIG_HAVE_ARCH_DEV_ALLOC_SKB=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
# CONFIG_CLEAN_COMPILE is not set
CONFIG_BROKEN=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_INIT_ENV_ARG_LIMIT=32
#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
# CONFIG_POSIX_MQUEUE is not set
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
# CONFIG_AUDIT is not set
CONFIG_HOTPLUG=y
CONFIG_KOBJECT_UEVENT=y
# CONFIG_IKCONFIG is not set
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SHMEM=y
CONFIG_CC_ALIGN_FUNCTIONS=0
CONFIG_CC_ALIGN_LABELS=0
CONFIG_CC_ALIGN_LOOPS=0
CONFIG_CC_ALIGN_JUMPS=0
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y
#
# X86 Processor Configuration
#
CONFIG_XENARCH="i386"
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
CONFIG_M686=y
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_PPRO_FENCE=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
# CONFIG_HPET_TIMER is not set
# CONFIG_HPET_EMULATE_RTC is not set
# CONFIG_SMP is not set
# CONFIG_X86_REBOOTFIXUPS is not set
CONFIG_X86_CPUID=y
#
# Firmware Drivers
#
# CONFIG_EDD is not set
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_HIGHMEM=y
# CONFIG_REGPARM is not set
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_PC=y
CONFIG_SECCOMP=y
CONFIG_EARLY_PRINTK=y
#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_AOUT is not set
# CONFIG_BINFMT_MISC is not set
#
# Device Drivers
#
#
# Generic Driver Options
#
# CONFIG_STANDALONE is not set
CONFIG_PREVENT_FIRMWARE_BUILD=y
# CONFIG_FW_LOADER is not set
# CONFIG_DEBUG_DRIVER is not set
#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
# CONFIG_LBD is not set
# CONFIG_CDROM_PKTCDVD is not set
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_ATA_OVER_ETH is not set
#
# SCSI device support
#
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
# CONFIG_CHR_DEV_SG is not set
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
#
# SCSI Transport Attributes
#
CONFIG_SCSI_SPI_ATTRS=y
CONFIG_SCSI_FC_ATTRS=m
# CONFIG_SCSI_ISCSI_ATTRS is not set
#
# SCSI low-level drivers
#
CONFIG_SCSI_SATA=y
# CONFIG_SCSI_DEBUG is not set
#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
# CONFIG_MD_LINEAR is not set
CONFIG_MD_RAID0=y
CONFIG_MD_RAID1=y
# CONFIG_MD_RAID10 is not set
CONFIG_MD_RAID5=y
# CONFIG_MD_RAID6 is not set
# CONFIG_MD_MULTIPATH is not set
# CONFIG_MD_FAULTY is not set
CONFIG_BLK_DEV_DM=y
# CONFIG_DM_CRYPT is not set
CONFIG_DM_SNAPSHOT=y
CONFIG_DM_MIRROR=y
# CONFIG_DM_ZERO is not set
# CONFIG_DM_MULTIPATH is not set
#
# Networking support
#
CONFIG_NET=y
#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
# CONFIG_IP_PNP_BOOTP is not set
# CONFIG_IP_PNP_RARP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_TUNNEL is not set
CONFIG_IP_TCPDIAG=y
# CONFIG_IP_TCPDIAG_IPV6 is not set
#
# IP: Virtual Server Configuration
#
# CONFIG_IP_VS is not set
# CONFIG_IPV6 is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_BRIDGE_NETFILTER=y
#
# IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
CONFIG_IP_NF_CT_ACCT=y
# CONFIG_IP_NF_CONNTRACK_MARK is not set
# CONFIG_IP_NF_CT_PROTO_SCTP is not set
CONFIG_IP_NF_FTP=m
# CONFIG_IP_NF_IRC is not set
# CONFIG_IP_NF_TFTP is not set
# CONFIG_IP_NF_AMANDA is not set
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=m
# CONFIG_IP_NF_MATCH_LIMIT is not set
CONFIG_IP_NF_MATCH_IPRANGE=m
# CONFIG_IP_NF_MATCH_MAC is not set
# CONFIG_IP_NF_MATCH_PKTTYPE is not set
# CONFIG_IP_NF_MATCH_MARK is not set
# CONFIG_IP_NF_MATCH_MULTIPORT is not set
# CONFIG_IP_NF_MATCH_TOS is not set
# CONFIG_IP_NF_MATCH_RECENT is not set
# CONFIG_IP_NF_MATCH_ECN is not set
# CONFIG_IP_NF_MATCH_DSCP is not set
# CONFIG_IP_NF_MATCH_AH_ESP is not set
# CONFIG_IP_NF_MATCH_LENGTH is not set
# CONFIG_IP_NF_MATCH_TTL is not set
# CONFIG_IP_NF_MATCH_TCPMSS is not set
# CONFIG_IP_NF_MATCH_HELPER is not set
# CONFIG_IP_NF_MATCH_STATE is not set
# CONFIG_IP_NF_MATCH_CONNTRACK is not set
# CONFIG_IP_NF_MATCH_OWNER is not set
CONFIG_IP_NF_MATCH_PHYSDEV=m
# CONFIG_IP_NF_MATCH_ADDRTYPE is not set
# CONFIG_IP_NF_MATCH_REALM is not set
# CONFIG_IP_NF_MATCH_SCTP is not set
# CONFIG_IP_NF_MATCH_COMMENT is not set
# CONFIG_IP_NF_MATCH_HASHLIMIT is not set
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
# CONFIG_IP_NF_TARGET_LOG is not set
# CONFIG_IP_NF_TARGET_ULOG is not set
# CONFIG_IP_NF_TARGET_TCPMSS is not set
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
# CONFIG_IP_NF_TARGET_REDIRECT is not set
# CONFIG_IP_NF_TARGET_NETMAP is not set
# CONFIG_IP_NF_TARGET_SAME is not set
# CONFIG_IP_NF_NAT_SNMP_BASIC is not set
CONFIG_IP_NF_NAT_FTP=m
# CONFIG_IP_NF_MANGLE is not set
# CONFIG_IP_NF_RAW is not set
# CONFIG_IP_NF_ARPTABLES is not set
#
# Bridge: Netfilter Configuration
#
# CONFIG_BRIDGE_NF_EBTABLES is not set
#
# SCTP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
CONFIG_BRIDGE=y
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set
# CONFIG_NET_CLS_ROUTE is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
CONFIG_NETDEVICES=y
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
CONFIG_TUN=y
#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
#
# Ethernet (1000 Mbit)
#
#
# Ethernet (10000 Mbit)
#
#
# Token Ring devices
#
#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set
#
# Wan interfaces
#
# CONFIG_WAN is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
# CONFIG_TCG_TPM is not set
CONFIG_USB=m
#
# TPM devices
#
#
# Character devices
#
#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_REISERFS_FS_XATTR is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
#
# XFS support
#
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
CONFIG_DNOTIFY=y
CONFIG_AUTOFS_FS=y
CONFIG_AUTOFS4_FS=y
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=y
CONFIG_UDF_FS=m
CONFIG_UDF_NLS=y
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
# CONFIG_NTFS_FS is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=y
# CONFIG_TMPFS_XATTR is not set
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y
#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
CONFIG_CRAMFS=y
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
#
# Network File Systems
#
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_NFS_V4=y
CONFIG_NFS_DIRECTIO=y
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
CONFIG_NFSD_V4=y
CONFIG_NFSD_TCP=y
CONFIG_ROOT_NFS=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_SUNRPC=y
CONFIG_SUNRPC_GSS=y
CONFIG_RPCSEC_GSS_KRB5=y
# CONFIG_RPCSEC_GSS_SPKM3 is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ASCII is not set
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set
#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_HMAC=y
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=m
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_WP512 is not set
# CONFIG_CRYPTO_TGR192 is not set
CONFIG_CRYPTO_DES=y
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_AES_586 is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_ARC4 is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_DEFLATE is not set
# CONFIG_CRYPTO_MICHAEL_MIC is not set
CONFIG_CRYPTO_CRC32C=m
# CONFIG_CRYPTO_TEST is not set
#
# Hardware crypto devices
#
# CONFIG_CRYPTO_DEV_PADLOCK is not set
#
# Library routines
#
# CONFIG_CRC_CCITT is not set
CONFIG_CRC32=y
CONFIG_LIBCRC32C=y
CONFIG_ZLIB_INFLATE=y
#
# Kernel hacking
#
# CONFIG_PRINTK_TIME is not set
CONFIG_DEBUG_KERNEL=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_LOG_BUF_SHIFT=14
# CONFIG_SCHEDSTATS is not set
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_KOBJECT is not set
# CONFIG_DEBUG_HIGHMEM is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_FS is not set
# CONFIG_FRAME_POINTER is not set
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_KPROBES is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_4KSTACKS is not set
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Re: Latest USB code
2005-12-12 19:38 Hien Nguyen
@ 2005-12-13 11:37 ` Harry Butterworth
0 siblings, 0 replies; 4+ messages in thread
From: Harry Butterworth @ 2005-12-13 11:37 UTC (permalink / raw)
To: Hien Nguyen; +Cc: xen-devel, plars
I'm fairly confused by your note below: I can't work out whether you
are trying to get the USB cdrom drive working in domain 0 or in another
guest domain.
If you are trying to get the cdrom drive working in domain 0 then you
don't need my patch. The cdrom drive should just work the same as it
does in native Linux provided you compile the kernel with all the
modules that are required. If it doesn't, I can't help you.
If you are trying to get the cdrom drive working in another guest domain
then you have made some mistakes below.
I'll run through again from the beginning in more detail this time...
Let's assume you have two domains: dom0 and domU. dom0 is the one with
physical access to the USB host controller device hardware. domU is a
guest domain. You want to plug the cdrom into the USB host controller
device driven by dom0 and have the cdrom device appear as a USB device
in domU.
You need to:
1) Apply my patch to both the dom0 and the domU kernels.
2) Compile the dom0 kernel with support for the usb back-end driver as a
module. The dom0 kernel also needs to be compiled with USB support and
support for driving the USB host controller device (UHCI/OHCI/EHCI
depending on what hardware you have).
3) Compile the domU kernel with support for the usb front-end driver as
a module. The domU kernel also needs USB support and support for any
other modules required to drive the cdrom under native linux. I think
usb-storage is the only module you need to drive the cdrom device but
I'm not sure. You can check by getting it working in native Linux and
having a look at what USB modules are loaded.
If you want, you can put the union of all these options into one kernel
and use the same kernel for dom0 and domU.
In any case, you will need to disable the usb-storage module in dom0 to
prevent it from grabbing the cdrom before the split driver can export it
to domU.
4) Put a line in the domU configuration---THIS IS THE domU DOMAIN
CONFIGURATION, NOT THE domU KERNEL CONFIGURATION---to export the cdrom
device from dom0 to domU:
If the cdrom device was 1-1 in /sys/bus/usb/devices in dom0 then the
domU domain configuration should contain the line:
usb = ['path=1']
Alternatively, if the cdrom device was 1-2 in /sys/bus/usb/devices in
dom0 then the domU domain configuration should contain the line:
usb = ['path=2']
Or, as a final example, if the cdrom device was 1-2.3 in
sys/bus/usb/devices in dom0 then the domU domain configuration should
contain the line:
usb = ['path=2.3']
You should be able to tell which dom0 device is the cdrom device by
examining the contents of the 'product' entry in the device directory
in /sys/bus/usb/devices in dom0. Alternatively, you could unplug the
cdrom, list sys/bus/usb/devices then plug it back in and list
sys/bus/usb/devices again. A number of directories should have appeared
for the cdrom. The one with the shortest name is the one for the
device, any others are for interfaces of the device.
5) modprobe the usbback module into the dom0 kernel.
6) boot the domU domain.
7) modprobe the usbfront module into the domU kernel.
8) Now have a look at /sys/bus/usb/devices in domU. You should now see
a directory for the cdrom device here in domU.
9) Modprobe usb-storage in domU. This should give you a SCSI device for
your cdrom drive. Look in /var/log/syslog to find out which one.
10) Put a CD in the drive.
11) Mount the scsi device.
All of this works with a USB flash device but I'm not sure how much will
work with a cdrom.
I'll go through your note below to point out any problems I can see...
On Mon, 2005-12-12 at 12:38 -0700, Hien Nguyen wrote:
> 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 ?
Look at the 'product' file or unplug and replug to see what goes away
and then comes back.
>
> 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
It might be 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
It might be 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
It might be 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
It might be 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:
This is dom0 so you should have the usbback module loaded but you don't.
>
> 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)
The .config file doesn't have the usbback module configured. You need
to cuild the usbback module for dom0 and the usbfront module for domU.
Hopefully this will get you a bit further.
Harry.
>
> Regards,
>
> Hien Nguyen
> Linux Technology Center AUSTIN
> Phone: (512) 838-4140 Tie Line: 678-4140
> e-mail: hien1@us.ibm.com
>
> Inactive hide details for Harry Butterworth
> <harry@hebutterworth.freeserve.co.uk>Harry Butterworth
> <harry@hebutterworth.freeserve.co.uk>
>
>
> Harry Butterworth <harry@hebutterworth.freeserve.co.uk>
>
> 12/07/2005 05:05 PM
>
>
> To
>
> Hien
> Nguyen/Austin/IBM@IBMUS
>
> cc
>
> xen-devel@lists.xensource.com
>
>
>
>
>
>
>
>
>
> 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@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>
>
>
>
>
>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2005-12-13 11:37 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-12-07 21:01 Latest USB code Hien Nguyen
2005-12-07 23:05 ` Harry Butterworth
-- strict thread matches above, loose matches on Subject: below --
2005-12-12 19:38 Hien Nguyen
2005-12-13 11:37 ` Harry Butterworth
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.