Tiny Core Linux
Tiny Core Extensions => TCE Q&A Forum => Topic started by: ejames82 on January 22, 2011, 04:33:15 PM
-
hello,
the computer is an ibm300pl pentium II with 768mb ram. i just ran memtest overnight with no errors. the computer works flawlessly.
every time i want sound, i have to run the following commands:
sudo alsaconf
speaker-test
i always get 'noise' after speaker-test, verifying that it is working. after this, i can play a youtube. the sound works great.
however, every time i reboot, i have to run the commands again or go without sound, so i followed the wiki and edited. here's my .filetool.lst after the recommended edit:
opt/bootlocal.sh
opt/bootsync.sh
opt/shutdown.sh
opt/tcemirror
opt/.filetool.lst
opt/.xfiletool.lst
home
opt/eth0.sh
opt/alsa
etc/modprobe.conf
after making this edit i selected to reboot with backup, but i got an error that interrupted the shutdown with wording similar to this:
"error while shutting down. check /tmp/backup_status"
i was unable to shutdown or reboot with the backup or safe options selected, only the none option would work. i checked /tmp/backup_status, but what i found there was no info that could help me. i also checked my apps audit>onboot list and alsaconf.tcz is listed.
any help would be appreciated, as always.
-
Remove opt/alsa from your .filetool.lst, as it does not exist.
Read the alsa.tcz info in AppsBrowser and folow theinstructions.
-
hello gerald_clark,
thanks, i'm doing it right now.
-
"Remove opt/alsa from your .filetool.lst, as it does not exist."
opt/alsa has been removed. here's my .filetool.lst:
opt/bootlocal.sh
opt/bootsync.sh
opt/shutdown.sh
opt/tcemirror
opt/.filetool.lst
opt/.xfiletool.lst
home
opt/eth0.sh
etc/modprobe.conf
"Read the alsa.tcz info in AppsBrowser and folow theinstructions."
appbrowser said to add this command to opt/bootlocal.sh:
/usr/local/etc/init.d/alsasound start
here's my opt/bootlocal.sh after the recommended edit:
#!/bin/sh
# put other system startup commands here
/opt/eth0.sh &
/usr/local/etc/init.d/alsasound start
did i make the edit correctly?
i then, tried to reboot using backup and again, received the same error message.
there was more instruction in appbrowser, but i wanted to be sure that i was proceeding correctly before i went any further.
any more advice would be most appreciated.
-
I don't have anything regarding alsa in my bootlocal, and I don't have etc/modprobe.conf in my filetool.
Maybe u can try OSS
-
Do what theerror message says.
"error while shutting down. check /tmp/backup_status"
That file will tell you what the problem is.
-
/opt/alsa is where some important data is stored for persistence across reboots after using alsaconf. It should not be empty after running alsaconf.
-
here is the modprobe.conf file:
# /etc/modprobe.conf: Modprobe config file.
#
# --- BEGIN: Generated by ALSACONF, do not edit. ---
# --- ALSACONF version 1.0.23 ---
alias snd-card-0 snd-cs4236
alias sound-slot-0 snd-cs4236
# --- END: Generated by ALSACONF, do not edit. ---
also, could you kind gentlemen tell me whether i edited my .filetool.lst file correctly?
jls_legalize,
oss can be an option, but as it is, running two commands to get the sound isn't so bad. i like the way alsa works. for now i think i will see if alsa can be made to work with persistence.
gerald_clark,
"Do what theerror message says."
here is the output of the /tmp/backup_status
tar: ~: No such file or directory
tar: ~: No such file or directory
tar: error exit delayed from previous errors
Jason W,
unless i am doing something wrong that i'm unaware of, this is my /opt/alsa/.alsaconf (pardon my command line inefficiency)
tc@box:~$ sudo su
root@box:~# cd /opt
root@box:/opt# ls -a
. .filetool.lst backgrounds shutdown.sh
.. .tce_dir bootlocal.sh tcemirror
.appbrowser .xfiletool.lst bootsync.sh
.backup_device alsa eth0.sh
root@box:/opt# cd alsa
root@box:/opt/alsa# ls -a
. .. .alsaconf
root@box:/opt/alsa# vi .alsaconf
1
~
~
~
~
~
- .alsaconf 1/1 100%
"/opt/alsa is where some important data is stored for persistence across reboots after using alsaconf. It should not be empty after running alsaconf."
it has a
1
at the top of the file.
thanks to everybody who replied.
-
Instead of using the GUI, run
filetool.sh -band try to spot at which dir or file tar stalls.
-
hello tinypoodle,
here's the output from the command:
tc@box:~$ sudo filetool.sh -b
Backing up files to /mnt/hda1/tce mounted over device /dev/hda1 tc@box:~$
thanks again.
-
Hey ejames82,
That 1 in the /opt/alsa/.alsaconf file is what causes persistence using a previous alsaconf result. So that file is correct.
-
hello tinypoodle,
here's the output from the command:
tc@box:~$ sudo filetool.sh -b
Backing up files to /mnt/hda1/tce mounted over device /dev/hda1 tc@box:~$
thanks again.
Hmm, using TC 2.10 here where files would be printed, but reading your post I tried with filetool.sh from 3.4.1 and indeed that can not be diagnostical in the same way.
However, 'filetool.sh -d' does print files, not sure if it could be of same diagnostical value but then you have nothing to lose to try (-d = dryrun) ;)
-
Jason W,
though i found just a number "1" to be rather odd, i thought perhaps that was correct.
tinypoodle,
i see what you're saying. you use a different version of tinycore so therefore there's a difference in the behavior. here's the output of the suggested command:
tc@box:~$ filetool.sh -d
Illegal option -d
Usage: filetool.sh options device
Where options are:
-b backup
-p prompt
-r restore
-s safe backup mode
Press enter to continue:
this info appears to be quite beneficial. though it's not getting me what i immediately need, if i'm not mistaken it's showing me how to run a command-line backup or restore (i don't understand what "prompt" means). i'll give a little while and hope i get a reply, if i don't get a reply, i'm going to wing it and see what these commands can provide for me. i also don't recall reading anything in the wiki or core concepts about safe backup mode.
thanks as always.
-
i rebooted and the sound still works without running any commands! :)
i wonder why the gui reboot/shutdown with backup option selected wouldn't cooperate (it looks to me like this was the problem) and the command-line would work? once the backup worked, the commands needed before were no longer needed.
tinypoodle,
when you suggested the filetool.sh -b command, i didn't consider it's use to be of a repair/fix nature. i thought it was being suggested for diagnostic purposes.
thanks for everybody who replied.
-
My thought had been to find a method to evaluate the backup related errors by getting verbose output in order to see at which filenames the backup would stall/fail.
A more direct way to achieve such could be to use a tar command per se, including the include and exclude file lists, but one would have to get the syntax exactly right...
-
tinypoodle,
perhaps, while that command was being run, if there was an error, that error and info relating to it would have been displayed.
if i could ever figure out why the gui tool wouldn't work to create the backup, i'll put it in this thread. for now though, it works.
thanks again.