alsa sound not loading properly

[LinuxUser01]

I'm not sure at this point if i should just reformat this USB stick (contains TC 5.0) and start over again with the alsa installation or just keep on opening a terminal and typing the same command over to get alsa working, or wait for OSS.tcz to be available in the Apps Browser because it doesn't matter what i try, it just doesn't have the sound enabled after either a reboot or coming from a full shut down. Thanks for all of your help guys.

[Juanito]

rather than doing that, I'd make sure nothing is set "onboot" or "ondemand", boot to the console (boot code "text") and then:

Code: [Select]

$ tce-load -i alsa
$ sudo /usr/local/etc/init.d/alsasound start
$ speaker-test -c2 -t wav -l1
.and see if you have sound

[LinuxUser01]

Not sure how to boot to console properly, but i've tried using the Boot Core (Command Line Only) option which is below the regular options and it was telling me that it can't find alsa.tcz after typing tce-load -i alsa.tcz or tce-load -i alsa. I've tried hitting the TAB button so i can edit the boot and just type in text, but still nothing. I've looked in the F1-F4 options and i did notice the text option available, but can't figure out how to boot to it. Another thing, when i tried booting from Boot COre (Command Line Only on Slow Devices) it took me right into the desktop which i thought it was strange. Maybe the OS has become corrupt somehow at this point. I know its totally irrelevant, but here is how it looks:

ABEL core
MENU LABEL Boot Core (command line only).
TEXT HELP
No embedded X/GUI extensions are loaded. User extensions scanned or specified
will be loaded, and will need to provide X/GUI if required.
ENDTEXT
KERNEL /boot/vmlinuz
INITRD /boot/core.gz
APPEND loglevel=3
LABEL corew
MENU LABEL Boot Core (command line only on slow devices, waitusb=5)
TEXT HELP
No embedded X/GUI extensions are loaded. User extensions scanned or specified
will be loaded, and will need to provide X/GUI if required.
ENDTEXT
KERNEL /boot/vmlinuz
INITRD /boot/core.gz
APPEND loglevel=3 waitusb=5

[coreplayer2]

KERNEL /boot/vmlinuz
INITRD /boot/core.gz
APPEND loglevel=3 waitusb=5

simply add ' text ' to boot text mode only

KERNEL /boot/vmlinuz
INITRD /boot/core.gz
APPEND loglevel=3 waitusb=5 text

or

KERNEL /boot/vmlinuz
APPEND initrd=/boot/core.gz loglevel=3 waitusb=5 text

[Misalf]

I'm not sure what the boot options are when booting via CD or TinyCore created boot menu.
I think you can press "TAB" while in the GRUB4DOS menu or "E" in some other bootloaders to be able to edit the boot entry (it won't be saved).

This should boot TC as normal (restoring backup etc) exept not lauching the desktop.

Alternatively (but I don't know it it makes any sense if no backup has been restored), try to cd into your  tce/optional/  folder after booting to text mode.

On my system that would be:

Code: [Select]

mount /mnt/sda4
cd /boot/tce-5.0/optional
Then I can do (with TAB autocompletion):
tce-load -i alsa

[coreplayer2]

I don't believe there is a need to cd into /tce/optional  to run tce-load -i xxxx.tcz from, it can be run from anywhere

[Misalf]

In case the bootloader has  base norestore  in the menu entry he used.
In that case  tce/  would be in /tmp/.

[LinuxUser01]

Well, after hitting tab on Boot Core (Command Line Only) i added "text" and it booted right into console, but it couldn't find alsa or alsa.tcz after trying to type in tce-load -i alsa.tcz or alsa. So i tried cd /mnt/sdc1/tce/optional since that is the way my USB stick has setup TC 5.0 and it couldn't cd into it. I even tried the /tmp/ that Misalf mention but still didn't work. I have deleted alsa.tcz and alsaconf.tcz from the OnBoot before doing all this as mentioned by Juanito. The funny thing is before i came back into the site to check if you guys had posted the sound was working. So this alsa is either corrupted or somehow buggy with my X-Fi Sound Blaster card. I never had any of these types of problems when i was using TC 4.7.7 with OSS.tcz. But i remember trying alsa on a previous version of TC and i never could get it to work either. I'll try again with the cd, but this time try /mnt/sdc1/tce/optional or if that doesn't work then /tmp/sdc1/tce/optional. Another thing, not sure why the APPEND is loglevel=3 cde for the default boot into TC desktop when this setup has been using tce/optional and not cde. Not sure what i'm talking about, what is cde?

[Misalf]

cde is used when booting from CD.
If booted from CD and no tce directory exists, /tmp/tce/  will be used for (temporary) downloaded apps.

[coreplayer2]

I keep coming back here because I'm interested in the Alsa configuration.  Am trying not to interfere, but there is such confusion

LinuxUser01, It appears your install is not setup correctly

Many ways to correct this, but one method (which I use most of the time now) is first set a Label on your USB stick.  this example uses label USBDRIVE
see the wiki http://wiki.tinycorelinux.net/wiki:install_usb

   kernel /boot/vmlinuz
   append initrd=/boot/core.gz loglevel=3 waitusb=5:LABEL=USBDRIVE text


Alternatively you may use UUID

Code: [Select]

blkid -s UUID /dev/sda1 to find your specific USB UUID then replace the example UUID below with yours
 
   kernel /boot/vmlinuz
   append initrd=/boot/core.gz loglevel=3 waitusb=5:UUID="9aff3da3-474d-440d-bb6c-3240afe84ac6" tce=UUID="9aff3da3-474d-440d-bb6c-3240afe84ac6" text



(rename cde to tce)
Also Replace the boot config entry cde (which is for CD's) with tce.   Make sure the USB path to your extensions is similar to
       /tce/optional

[LinuxUser01]

I have a 2G USB Stick that i formatted and installed TC v5.0 using USB2CORE v1.6. So not sure if USB2CORE created the cde or somehow the setup of TC created it. I think it has been like this since TC 4.7.x, but i never really paid that much attention to it. So just edit the syslinux.cfg file and change APPEND loglevel=3 cde waitusb=5 to APPEND loglevel=3 tce waitusb=5 for the Boot TinyCore and that should do the trick?

[coreplayer2]

I don't think so, please see above

[LinuxUser01]

Okay, i named the USB stick to USBDRIVE and found out the UUID and edited the syslinux.cfg from APPEND initrd=/boot/core.gz loglevel=3 cde waitusb=5 to APPEND initrd=/boot/core.gz loglevel=3 waitusb=5:UUID="C6FA-C9A9" tce=UUID="C6FA-C9A9". So as you can see i replaced the cde before waitusb=5 to the tce=UUID...Wait, i don't even have a cde folder. I only see a tce/optional folder so not sure how that command even existed from the start. Let's see if this boots now.

[LinuxUser01]

It booted fine into the desktop, but the sound is still not working. I'll see how it boots into console with the text command infront of it now.

[LinuxUser01]

Okay, it booted fine into the console with the text command. The tce-load -i alsa gives me alsa already installed, so i typed sudo /usr/local/etc/init.d/alsasound start then speaker-test -c2 -t wav -l1 which gave me these results:

Playback device is default stream parameters are 48000Hz, s16_LE, 2 channels wav file(s)
ALSA lib pcm_dmix.c: 1022:(snd_pcm_dmix_open) Unable to open slave
Playback open error: -2, No such file or directory