Tiny Core Linux
Tiny Core Base => TCB Bugs => Topic started by: hiro on January 04, 2011, 04:51:53 PM
-
How can I load this?
# modprobe thinkpad_acpi
modprobe: can't load module thinkpad_acpi (kernel/drivers/platform/x86/thinkpad_acpi.ko.gz): unknown symbol in module, or unknown parameter
-
modinfo thinkpad_acpi |grep depends
-
nil
-
It appears to have a param "force_load:Attempts to load the driver even on a mis-identified ThinkPad when true (bool)", but I would think twice before attempting so, better research other options first.
-
I don't think it is mis-identified, the module doesn't get loaded...
-
"unknown symbol in module, or unknown parameter"
I guess I will have to recompile that module. I already had a go once, but forgot the modules and then rebooted.
-
Edit: Well, it seems to depend on the alsa and hwmon extensions.
Should be moved to an extension.
-
By the way,
there is this sorter.sh script which creates those module extensions.
How do you decide whic one to have in base?
-
Everything that is considered base functionality (wired networking among other things), or is small and doesn't depend on something big already decided to be an extension (e.g. alsa).
Relatively arbitrary criteria, but we're always listening if you have suggestions.
-
Wow, this is so stupid, why do these suckers want alsa?
I don't want to blacklist all this stuff, just so that I can control my fans if I modprobe thinkpad_acpi with some experimental option.
Then I'd rather have them running all day, I'll just turn my OSS music a bit louder, so that I won't hear it.
-
http://www.thinkwiki.org/wiki/Thinkpad-acpi
-
Perhaps we should put soundcore in base. Although I don't like this solution very much.
-
Instead of blacklisting you might want to consider to unsquash the extensions, delete whatever is redundant to you, and then squash again.
-
Alsa's soundcore conflicts with OSS IIRC.
-
I have OSS, snd and soundcore loaded (thinkpad_acpi depends on snd).
Everything is working...
-
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.
-
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.
-
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.
-
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
-
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.
-
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...
-
Or you could split out snd and soundcore for these people who try to avoid alsa's bloat.
-
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?
-
Wait, I hoped the simplification of soundon might get into OSS.tcz. No need to bother the user with this stuff.