XEN - unbind/bind a PCI device

[Tech Writer]

Ben,

Thanks again for the tips.  When my system is in multi-user mode, then I see these device directories in the pci/drivers folder:

# ls /sys/bus/pci/drivers
3c59x    VIA_IDE      imsttfb     pciback          shpchp    via686a
ENS1371  agpgart-via  parport_pc  pcieport-driver  uhci_hcd  vt596_smbus
#

However, when I go down to single user mode, my ENS1371 directory disappears.  So, I can't do the unbind at that point.  Back in multi-user mode, I tried to find out what else might be using this sound card, and found the following:

# lsmod | grep ens
snd_ens1371            30880  1
gameport               19464  1 snd_ens1371
snd_rawmidi            30848  2 snd_seq_midi,snd_ens1371
snd_ac97_codec         98592  1 snd_ens1371
snd_pcm               101124  3 snd_pcm_oss,snd_ens1371,snd_ac97_codec
snd                    63492  12 snd_pcm_oss,snd_mixer_oss,snd_seq_midi,snd_seq,snd_ens1371,snd_rawmidi,snd_seq_device,snd_ac97_codec,snd_pcm,snd_timer
#

The next exercise in this set asks the student to prohibit the bind during boot by editing the file /etc/modprobe.conf.local by adding the line:
#
options pciback hide=(0000:00:0b.0)
# 

After this is done, I ran mkinitrd and rebooted.  When the system came back up, the driver was now available in the /sys/bus/pci/drivers/pciback directory.  I was then able to add the sound card to my virtual machine.  So, this sounds like the better approach.  Still, it would be nice to figure out how to get the highly advertised way to work, as well.

Peg


----- Original Message ----- 
From: "Ben Scott" <dragonhawk at gmail.com>
To: <gnhlug-discuss at mail.gnhlug.org>
Sent: Wednesday, September 26, 2007 12:40 AM
Subject: Re: XEN - unbind/bind a PCI device


> On 9/26/07, Tech Writer <TechWtr at handspun.com> wrote:
>> You're right.  The rmmod command failed because the device was being used.
>> I tried to "force" the remove, but that just hung like the unbind attempt.
> 
>  Yah, forcing a module to unload usually yields results ranging from
> "won't work" to "system crash".  If something is in use, yanking bits
> of it away tends to cause problems.  Problems in the kernel are bad.
> :)
> 
>> I think the gameport is on the same device, and that daemon is running...
>> Will have to look for other connections in the morning.
> 
>  As a test, you can bring the system down to single-user mode and
> then try the echo-to-unbind command.  As root, "init 1" will go to
> single-user.  At the single-user shell prompt, "exit" will usually
> bring you back to the default runlevel.
> 
> -- Ben
> _______________________________________________
> gnhlug-discuss mailing list
> gnhlug-discuss at mail.gnhlug.org
> http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.gnhlug.org/mailman/private/gnhlug-discuss/attachments/20070926/05573d39/attachment-0001.html