thinkpad_acpi

[hiro]

Instead of blacklisting you might want to consider to unsquash the extensions, delete whatever is redundant to you, and then squash again.

Definitely easier!
Honestly, why don't we create an extension for *each*
module? I once did something like that, but only because I
had to save space.
But it would be even more useful when it comes to usability.
Blacklisting stuff in linux is way too difficult. I never hit the
right modules, and then what I didn't want still gets loaded.

We could use linux doc as a source for info files.
And with lspci and lsusb we could create something
like "recommended modules for your computer" in appbrowser.

[tinypoodle]

This thought had occurred to me at one point as well, but I think it would make it less userfriendly for beginners, and also create a lot more of administrative work for maintainers of extensions and of the repo.

An examples could be the extension with the in-kernel wireless modules, I think some new users might have way more difficulties if they would be seperated.
Me as a user knowing which modules I need and resquashing after removing redundancy is in my own responsability, to save some resources. Similar with filesystems, of which I would use only reiserfs, getting all those which are not included in base.

[hiro]

I guess you're right. I often don't know which modules I actually need.
One possibility might be providing both, a meta package for the novice and individual packages for each chip. But I don't know what the admins would say to such repo clutter.

[hiro]

While trying to install a newer OSS version I've now looked into this issue in detail again.
Actually oss is *not* incompatible with loaded soundcore or snd modules, just the newer version of the script soundon creates problems. Just remove the following misleading part which will never succeed  (because we don't have a remove_drv.sh)

with this workaround thinkpad_acpi can be used with OSS again.

On a related note - does alsa-modules-3.0.21-tinycore.tcz really have to depend on these two extensions?
input-joystick-KERNEL.tcz
v4l-dvb-KERNEL.tcz

if test -d /proc/asound || grep -q '^ *14 ' < /proc/devices                           
then                                                                                   
        if ! sh $OSSLIBDIR/scripts/remove_drv.sh>> $LOG                               
        then                                                                           
                echo Failed to disable conflicting sound drivers >> $LOG               
                echo Failed to disable conflicting sound drivers       
                echo Reboot and try running soundon again               
                echo                                                   
                echo Also check that you have not compiled sound support statically
                echo into the kernel.                                             
                exit 50                                                           
        fi                                                                         
fi                                                                                 

[curaga]

On a related note - does alsa-modules-3.0.21-tinycore.tcz really have to depend on these two extensions?
input-joystick-KERNEL.tcz
v4l-dvb-KERNEL.tcz

Some of the alsa modules depend on modules in those two extensions (check the modinfo output). Certainly could be moved from a dep to an info file mention if it bothers people much, but I would side with modules successfully loading first.

[tinypoodle]

v4l-dvb-KERNEL.tcz is rather big in proportion to alsa and appears to increase loading time of alsa noticeably, compared to before when it was not a mandatory dep...

[hiro]

Or you could split out snd and soundcore for these people who try to avoid alsa's bloat.

[aus9]

hiro

I have updated the OSS wiki (but confess I am an ALSA user). Sorry for the hijack but if you get a chance to reply, do you use  ossmix or ossxmix?

[hiro]

Wait, I hoped the simplification of soundon might get into OSS.tcz. No need to bother the user with this stuff.