[SOLVED]findutils package supplies command xargs...maybe not working?

[aus9]

Hi

I have findutils package installed on a persistent system..v3.0

I am attempting this command

Code: [Select]

sudo su
root@box:~# cat /proc/modules|gawk '/^snd-/{print $1}'|xargs -i rmmod {}
root@box:~# lsmod | grep snd
snd_seq_dummy            648  0
snd_seq_oss            15364  0
snd_seq_midi_event      2624  1 snd_seq_oss
snd_seq                26036  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device          2808  3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss            24484  0
snd_mixer_oss           8648  1 snd_pcm_oss
snd_hda_codec_idt      30668  1
snd_hda_intel          14480  0
snd_hda_codec          33296  2 snd_hda_codec_idt,snd_hda_intel
snd_pcm                37628  3 snd_pcm_oss,snd_hda_intel,snd_hda_codec
snd_timer              10564  2 snd_seq,snd_pcm
snd                    26200 10 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_pcm,snd_timer
soundcore               2640  1 snd
snd_page_alloc          4016  2 snd_hda_intel,snd_pcm

AFAIK I want the modules for snd to be removed.

that does not appear to happen

(2) In a vbox test....I was successful in unloading the snd modules with a far simpler

sudo su
modprobe -r soundcore

however on my host....I get messages about ....modprobe: can't unload module soundcore: Resource temporarily unavailable

IMHO soundcore is the top of the tree of module dependencies but I may be wrong?

(3) before installing findutils....xargs was complaining about it being a busybox command.

I assumed the earlier string of the command was good as the command  should exit if the first bit is wrong?

thanks for any insights

PS I am attempting to expand the sound wiki for alsa to include model strings and quirks where relevant.

[tinypoodle]

Try

Code: [Select]

sudo /usr/local/etc/init.d/alsasound stop
before attempting to remove modules?

[aus9]

hi tinypoodle

thanks for the quick reply...sorry for not extra reporting.

in vbox I had persistence for that script as a start up etc as per wiki.

on host I deliberately removed persistence and here is what happens.
If you load the tcz you will have the /usr pathway for the alsasound so I am merely showing that alsasound was not started....forgive me if I have mislead you in above.

Code: [Select]

sudo su
root@box:~# /usr/local/etc/init.d/alsasound stop
rmmod: can't unload 'snd_hda_codec_idt': Resource temporarily unavailable
rmmod: can't unload 'snd_hda_codec': Resource temporarily unavailable
rmmod: can't unload 'snd_pcm': Resource temporarily unavailable
rmmod: can't unload 'snd_timer': Resource temporarily unavailable
rmmod: can't unload 'snd': Resource temporarily unavailable
root@box:~# lsmod | grep snd
snd_hda_codec_idt      30668  0
snd_hda_codec          33296  1 snd_hda_codec_idt
snd_pcm                37628  1 snd_hda_codec
snd_timer              10564  1 snd_pcm
snd                    26200  4 snd_hda_codec_idt,snd_hda_codec,snd_pcm,snd_timer
soundcore               2640  1 snd
snd_page_alloc          4016  1 snd_pcm
root@box:~# ls /etc/init.d/
crond          rc.shutdown    services       tc-functions   tc_noscan.lst
dhcp.sh        rcS            tc-config      tc-restore.sh


[tinypoodle]

try

Code: [Select]

fuser /usr/local/lib/libasound*

EDIT: Just checked, with

Code: [Select]

sudo /usr/local/etc/init.d/alsasound stop
all modules are removed here, except from snd_page_alloc and ac97_bus (on a CS4624).

[aus9]

hi again

The fun begins?

Code: [Select]

tc@box:~$ fuser /usr/local/lib/libasound*
3077
tc@box:~$ kill 3077  
tc@box:~$

tc@box:~$ sudo su
root@box:~# fuser /usr/local/lib/libasound*
root@box:~#

(next command included even tho I do not have it set up any more)
root@box:~# /usr/local/etc/init.d/alsasound stop
rmmod: can't unload 'snd_hda_codec_idt': Resource temporarily unavailable
rmmod: can't unload 'snd_hda_codec': Resource temporarily unavailable
rmmod: can't unload 'snd_pcm': Resource temporarily unavailable
rmmod: can't unload 'snd_timer': Resource temporarily unavailable
rmmod: can't unload 'snd': Resource temporarily unavailable


root@box:~# cat /proc/modules|gawk '/^snd-/{print $1}'|xargs -i rmmod {}
root@box:~# lsmod | grep snd
snd_hda_codec_idt      30668  0
snd_hda_codec          33296  1 snd_hda_codec_idt
snd_pcm                37628  1 snd_hda_codec
snd_timer              10564  1 snd_pcm
snd                    26200  4 snd_hda_codec_idt,snd_hda_codec,snd_pcm,snd_timer
soundcore               2640  1 snd
snd_page_alloc          4016  1 snd_pcm

verdict........snd-hda-intel is gone but still shows codecs..
IMHO the gawk bit is supposed to remove all snd?

in vbox I can use a real easy modprobe -r to kill the sound modules and with this intel....no good.


I might try to to add a bootlocal

modprobe -b snd-hda-intel and codec ......later


I work so no rush to reply....I do most of my testing on the weekends

regards

EDIT

I have managed to get something different....different is good...heh heh

Code: [Select]

root@box:~# /usr/local/etc/init.d/alsasound stop
/usr/local/sbin/alsactl: save_state:1504: No soundcards found...

[aus9]

ok I will hijack my own post at the moment.....there are other posts on this forum where some forum members have not got a correct reply....so I am working in the dark....but I am a mushroom...heh heh

this is an observation not a criticism!

TESTS....(1) and (2)....are a fail

Remove all alsasound from bootlocal.sh and add /etc/modprobe.conf to .filetool.lst

contents of modprobe,conf

Test (1)
blacklist snd-hda-intel

test (2)
blacklist snd_hda_intel

On both reboots....lsmod show those pesky sound modules alive and kicking

[aus9]

solved

undo all of those tests above....except do not load any alsasound

modify with root powers.....bootlocal.sh add (for me)

/sbin/modprobe -r snd_hda_intel
/sbin/modprobe -r snd_hda_codec_idt

reboot with backup and bingo!! NO sound modules....which is what I wanted.

I will attempt to reply to the other posts to see if they are interested.

(note to my self.....some distros configs convert understems to hyphens

but UNDERSTEM is the correct way for TC.

(2) I can get back to adding more to that script to add index, model and quirks

test that later

thanks

[aus9]

quick test of my model number is a success.

snapshot of new mixer channels upload to wiki