Tiny Core Extensions > TCE Tips & Tricks
Compiling kernel and modules on TC
Juanito:
If you try the two or three commands listed in alsa.tcel.info, do you get any error messages?
kerpob:
--- Quote from: Juanito on February 24, 2009, 05:50:20 AM ---If you try the two or three commands listed in alsa.tcel.info, do you get any error messages?
--- End quote ---
sudo alsaconf gives:
unable to execute /usr/local/sbin/alsaconf no such file or directory
but alsaconf is in that directory, as is alsactl. Same result even if I run same command from /usr/local/sbin/
sudo udevtrigger --subsystem-match=sound
no response, but no error message either. just straight to next command.
speaker-test seems to be working... apart from no sound!
Juanito:
--- Quote from: kerpob on February 24, 2009, 05:22:14 PM ---sudo alsaconf gives:
unable to execute /usr/local/sbin/alsaconf no such file or directory
--- End quote ---
This sounds like you need the bash extension loaded - if you look at alsaconf with a text editor, does the first line contain "bash"?
kerpob:
--- Quote from: Juanito on February 24, 2009, 10:35:04 PM ---
--- Quote from: kerpob on February 24, 2009, 05:22:14 PM ---sudo alsaconf gives:
unable to execute /usr/local/sbin/alsaconf no such file or directory
--- End quote ---
This sounds like you need the bash extension loaded - if you look at alsaconf with a text editor, does the first line contain "bash"?
--- End quote ---
Bash loads as a dependancy... It also doesn't work on the normal tinycore kernel, with the same error message, which suggests to me that either alsa tce isn't working or my eee doesn't accept alsa.
Jason W:
Regarding bash:
It sounds like bash did not create the /bin/bash symlink. I have had that happen for reasons I didn't investigate as it normally works fine. Try recreating /bin/bash:
ln -s /usr/local/bin/bash /bin/bash
and see if that helps.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version