WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Can't unbind PCI sound card

I am definitely trying to unbind the PCI sound card.  The "example" I included was one that I pulled off the web.  I just re-read my initial note, and realized i just edited the web example. My exact command is this:
   
       echo -n 0000:00:0b.0 > /sys/bus/pci/drivers/ENS1371/unbind
 
... and this command just hangs.
 
As I mentioned in my original post, I can find a way to use the sound card by editing /etc/modprobe.conf.local with:
    options pciback hide=(0000:00:0b.0)
 
However, my goal is to get the documented example to work.  If a new user of Xen tries to follow the documentation or the web examples, they will be given the steps listed in my original post, which are:
 
# # Unbind a PCI network card from its network driver
# echo -n <pci-slot-nbr> > /sys/bus/pci/drivers/<device>/unbind
# # And now bind it to the PCI Backend
# echo -n <pci-slot-nbr> > /sys/bus/pci/drivers/pciback/new_slot
# echo -n <pci-slot-nbr> > /sys/bus/pci/drivers/pciback/bind
 
I haven't found any indication in any of the web examples, or in the documentation, following this sequence of commands, which indicates what to do if the unbind hangs.  So, I'm trying to figure out why it is hanging, and if there is a workaround that can be included in the training materials.
 
Peg
 
----- Original Message -----
From: "Ian Campbell" <Ian.Campbell@xxxxxxxxxxxxx>
To: "Tech Writer" <TechWtr@xxxxxxxxxxxx>
Sent: Thursday, September 27, 2007 8:55 AM
Subject: Re: [Xen-devel] Can't unbind PCI sound card

> On Thu, 2007-09-27 at 08:10 -0400, Tech Writer wrote:
>>     echo -n 0000:00:0b.0 >  /sys/bus/pci/drivers/e100/unbind
>
> e100 is a network driver not a sound driver, are you sure you aren't
> disconnecting the Ethernet interface you are logged in over or
> something? You probably want /sys/bus/pci/drivers/snd_ens1371/unbind, I
> would actually follow the symlink
> at /sys/bus/pci/devices/0000:00:0b.0/driver instead of going
> vi /sys/bus/pci/drivers to be sure of getting the right device.
>
> Below is the script I use to attach a device to pciback, it takes a list
> of pci devices as its parameter.
>
> Ian.
>
>
> #!/bin/sh
>
> if [ $# -eq 0 ] ; then
>   echo "Require a PCI device as parameter"
>   exit 1
> fi
>
> for pcidev in $@ ; do
>    if [ -h /sys/bus/pci/devices/"$pcidev"/driver ] ; then
>
>        echo "Unbinding $pcidev from" $(basename $(readlink /sys/bus/pci/devices/"$pcidev"/driver))
>        echo -n "$pcidev" > /sys/bus/pci/devices/"$pcidev"/driver/unbind
>    fi
>    echo "Binding $pcidev to pciback"
>    echo -n "$pcidev" > /sys/bus/pci/drivers/pciback/new_slot
>    echo -n "$pcidev" > /sys/bus/pci/drivers/pciback/bind
> done
>
>
>
> _______________________________________________
> Xen-devel mailing list
>
Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>