Fatdog64-611 Final (Updated 12-14-2012)
Hi rcrsn51,rcrsn51 wrote:There are a couple of possibilities.
1. Your sda2 partition has some corruption. What filesystem does it have?
2. The initrd file did not get copied correctly.
3. Your BIOS or your version of GRUB cannot handle Fatdog's humongous initrd. I have a problem when booting Fatdog off a USB drive.
I checked the sda2 and it is clean. I copied the initrd a few different times without any improvement. Perhaps it is GRUB hmm. I am able to boot from the DVD of the ISO image. I'll try a few more things before giving up on Fatdog64.
Thanks for the help.
Rob
loss of sound alsawizrd also wont fix
I had sound, now I do not, no panel volume
tried the control panel script, never completes.
sound card works via vlc device selection.
seems init script is dead
asound.conf is correct
tried the control panel script, never completes.
sound card works via vlc device selection.
seems init script is dead
Code: Select all
lsmod
pcspkr 1779 0
sg 27545 0
snd 55640 10 snd_pcm_oss,snd_mixer_oss,snd_mpu401,snd_mpu401_uart,snd_rawmidi,snd_seq_device,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
snd_ac97_codec 108147 1 snd_intel8x0
snd_intel8x0 26135 0
snd_mixer_oss 14516 1 snd_pcm_oss
snd_mpu401 4728 0
snd_mpu401_uart 5699 1 snd_mpu401
snd_page_alloc 6681 2 snd_intel8x0,snd_pcm
snd_pcm 72118 3 snd_pcm_oss,snd_intel8x0,snd_ac97_codec
snd_pcm_oss 37122 0
snd_rawmidi 18178 1 snd_mpu401_uart
snd_seq_device 4924 1 snd_rawmidi
snd_timer 18081 1 snd_pcm
soundcore 4994 1 snd
Code: Select all
pcm.!default { type hw card 0 device 0 }
ctl.!default { type hw card 0 device 0 }
Re: loss of sound alsawizrd also wont fix
sound has return but I think it is a fluke.galen wrote:I had sound, now I do not, no panel volume
tried the control panel script, never completes.
sound card works via vlc device selection.
seems init script is dead
asound.conf is correctCode: Select all
lsmod pcspkr 1779 0 sg 27545 0 snd 55640 10 snd_pcm_oss,snd_mixer_oss,snd_mpu401,snd_mpu401_uart,snd_rawmidi,snd_seq_device,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer snd_ac97_codec 108147 1 snd_intel8x0 snd_intel8x0 26135 0 snd_mixer_oss 14516 1 snd_pcm_oss snd_mpu401 4728 0 snd_mpu401_uart 5699 1 snd_mpu401 snd_page_alloc 6681 2 snd_intel8x0,snd_pcm snd_pcm 72118 3 snd_pcm_oss,snd_intel8x0,snd_ac97_codec snd_pcm_oss 37122 0 snd_rawmidi 18178 1 snd_mpu401_uart snd_seq_device 4924 1 snd_rawmidi snd_timer 18081 1 snd_pcm soundcore 4994 1 snd
Code: Select all
pcm.!default { type hw card 0 device 0 } ctl.!default { type hw card 0 device 0 }
I ran /etc/init.d/99-alsa
and next reboot sound returned but
fatdog control panel mixer does not work and tray volume control crashes panel (default is does exist)
galen, please try 620beta1 and post your test there. Btw I saw you posted a bug report in the bug report system. Just want to let you know that we've just moved the fossil repository so your bug report is deleted.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
grub legacy mushes all titles into one line
noticed if fatdog is installed to the hard drive and you select grub install,
the menu.lst is corrupt, the installed will find other distros on the hard drive but list them all on one line and then ask you for a title.
something like this
found linux on [/dev/sda1][/dev/sda2][dev/sda4] what title would like
grub4dos works quite well but it not detected by other distros grub or grub2 (yuk)
I do prefer to use grub4dos on MBR and chainload into grub or grub2 for other distros
the menu.lst is corrupt, the installed will find other distros on the hard drive but list them all on one line and then ask you for a title.
something like this
found linux on [/dev/sda1][/dev/sda2][dev/sda4] what title would like
grub4dos works quite well but it not detected by other distros grub or grub2 (yuk)
I do prefer to use grub4dos on MBR and chainload into grub or grub2 for other distros
Cups has stopped working and I've also noticed seamonkey-spot has stopped too.
When running seamonkey-spot from a terminal I get:
# seamonkey-spot
su: can't chdir to home directory '/root/spot'
su: can't execute '/bin/dash': Permission denied
#
Cups also stopped working when I loaded a Firefox SFS. When I unloaded Firefox, Cups began working again but not now.
The Cups home is displayed in seamonkey @ http://localhost:631/ ,
not via the spot script.
If I select Admin I get Internal Server Error.
Classes and Printers gives a permission denied error.
Any ideas?
Thanks
When running seamonkey-spot from a terminal I get:
# seamonkey-spot
su: can't chdir to home directory '/root/spot'
su: can't execute '/bin/dash': Permission denied
#
Cups also stopped working when I loaded a Firefox SFS. When I unloaded Firefox, Cups began working again but not now.
The Cups home is displayed in seamonkey @ http://localhost:631/ ,
not via the spot script.
If I select Admin I get Internal Server Error.
Classes and Printers gives a permission denied error.
Any ideas?
Thanks
Smokey01,
I think the savefile may have been corrupted. "/bin/dash" is the lightweight shell I use for interpreting shell scripts (because its fast), if you can't execute it something must have gone terrible wrong (either it is deleted, or corrupted and not accessible). You can copy the file back from /aufs/pup_ro/bin/dash (that's the read-only Fatdog SFS copy) to /bin/dash, but looking at the seriousness of the problem I doubt you can recover much.
One other alternative you can try is to boot kernel command line "dofsck" (that "do-fsck" without the dash), this is Fatdog's equivalent of "pfix=fsck" in Puppy. I can't remember when it started to be supported though, all I know is recent Fatdogs support it.
cheers!
I think the savefile may have been corrupted. "/bin/dash" is the lightweight shell I use for interpreting shell scripts (because its fast), if you can't execute it something must have gone terrible wrong (either it is deleted, or corrupted and not accessible). You can copy the file back from /aufs/pup_ro/bin/dash (that's the read-only Fatdog SFS copy) to /bin/dash, but looking at the seriousness of the problem I doubt you can recover much.
One other alternative you can try is to boot kernel command line "dofsck" (that "do-fsck" without the dash), this is Fatdog's equivalent of "pfix=fsck" in Puppy. I can't remember when it started to be supported though, all I know is recent Fatdogs support it.
cheers!
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
jamesbond,
dash seems to be working OK. See below.
dash -v
### /etc/shinit - shell init file
# this is executed by shell - both login or non-login
# setup stuff for interactive shells only
case $- in
*i*)
# interactive configurations - prompt, history, etc
# TERM, USER and LOGNAME is already set by login/su
PS1="$USER$ "; [ $USER = root ] && PS1="# "
HISTFILE="$HOME/.history" # ensure all shells use the same history
# aliases
alias ls='ls --color=auto'
alias grep='grep --color=auto'
;;
esac
#
I have been considering making 621 my main OS but I'm waiting for the next release, I guess after the 3.11 kernel is released.
The file dofsck does not appear to be in fd-611 or at least which can't find it.
Thanks
dash seems to be working OK. See below.
dash -v
### /etc/shinit - shell init file
# this is executed by shell - both login or non-login
# setup stuff for interactive shells only
case $- in
*i*)
# interactive configurations - prompt, history, etc
# TERM, USER and LOGNAME is already set by login/su
PS1="$USER$ "; [ $USER = root ] && PS1="# "
HISTFILE="$HOME/.history" # ensure all shells use the same history
# aliases
alias ls='ls --color=auto'
alias grep='grep --color=auto'
;;
esac
#
I have been considering making 621 my main OS but I'm waiting for the next release, I guess after the 3.11 kernel is released.
The file dofsck does not appear to be in fd-611 or at least which can't find it.
Thanks
I am using fatdof 611. It has wpa_gui icon in tray instead of usual networking icon. Now I have to connect to eth0 by opening network wizard from control pannel. Is there a way to connect to eth0 automatically and see the RX/TX in tray icon?
Please help.
Sincerely,
Srinivas Nayak
Please help.
Sincerely,
Srinivas Nayak
[Precise 571 on AMD Athlon XP 2000+ with 512MB RAM]
[Fatdog 720 on Intel Pentium B960 with 4GB RAM]
[url]http://srinivas-nayak.blogspot.com/[/url]
[Fatdog 720 on Intel Pentium B960 with 4GB RAM]
[url]http://srinivas-nayak.blogspot.com/[/url]
Network Wizard does not connect automatically , maybe because wpagui starts first . To have Network Wizard window at startup instead of wpagui one , in /etc/xdg/Startup/ you must link net-setup.sh from /usr/sbin/ and replace wpagui. The connection is not automaticaly , though...
For the tray icon of network : Right click on lxpanel and choose Add/Remove Panel Applets , then add Network Status Monitor and when you have it right click on it and choose Network Satus Monitor Settings . --> Interface to monitor : you have to write eth0 .
For the tray icon of network : Right click on lxpanel and choose Add/Remove Panel Applets , then add Network Status Monitor and when you have it right click on it and choose Network Satus Monitor Settings . --> Interface to monitor : you have to write eth0 .
Dear Gobbi,
Many thanks for your help.
I found "Network Status Monitor" applet, it is good, however, it takes a lot of space (width-wise) in the tray. So I had to remove it.
When I was using Fatdog 521, there was always a head of puppy coming to front and saying, "eth0 connected!". In Fatdog 611 I am missing that. Is it that the autoimatic connection to wired network has all together been banned in fatdog 611?
I don't need wpa, since I have no wireless net facility.
Many thanks for your help.
I found "Network Status Monitor" applet, it is good, however, it takes a lot of space (width-wise) in the tray. So I had to remove it.
When I was using Fatdog 521, there was always a head of puppy coming to front and saying, "eth0 connected!". In Fatdog 611 I am missing that. Is it that the autoimatic connection to wired network has all together been banned in fatdog 611?
I don't need wpa, since I have no wireless net facility.
[Precise 571 on AMD Athlon XP 2000+ with 512MB RAM]
[Fatdog 720 on Intel Pentium B960 with 4GB RAM]
[url]http://srinivas-nayak.blogspot.com/[/url]
[Fatdog 720 on Intel Pentium B960 with 4GB RAM]
[url]http://srinivas-nayak.blogspot.com/[/url]
I downloaded google-chrome from http://distro.ibiblio.org/fatdog/pets/6 ... 547.65.pet.
It didn't generate a menu item.
While I tried to run it from CLI, it gave
Sincerely,
Srinivas Nayak
It didn't generate a menu item.
While I tried to run it from CLI, it gave
How can I fix it?~# google-chrome
/usr/bin/google-chrome: symbol lookup error: /usr/bin/google-chrome: undefined symbol: _XGetRequest
~#
Sincerely,
Srinivas Nayak
[Precise 571 on AMD Athlon XP 2000+ with 512MB RAM]
[Fatdog 720 on Intel Pentium B960 with 4GB RAM]
[url]http://srinivas-nayak.blogspot.com/[/url]
[Fatdog 720 on Intel Pentium B960 with 4GB RAM]
[url]http://srinivas-nayak.blogspot.com/[/url]
snayak,
That pet was made for Fatdog64-630, which is only out as a rc1. Rc2 will be coming out in a couple weeks. To make it work in 611 libX11 would need to be updated. I've uploaded a pet here:
http://distro.ibiblio.org/fatdog/broken ... -1.6.2.pet
No promises that it won't break other things or that other libraries would need to be updated too. But I think that might be all you need.
That pet was made for Fatdog64-630, which is only out as a rc1. Rc2 will be coming out in a couple weeks. To make it work in 611 libX11 would need to be updated. I've uploaded a pet here:
http://distro.ibiblio.org/fatdog/broken ... -1.6.2.pet
No promises that it won't break other things or that other libraries would need to be updated too. But I think that might be all you need.
I noticed that updatedb and locate doesn't work on Fatdog 611.
It shows
I did
It started working!
Please note this.
Sincerely,
Srinivas Nayak
It shows
Code: Select all
~# updatedb
/usr/bin/updatedb: line 278: /var/state/locatedb.n: No such file or directory
Failed to generate /var/state/locatedb.n
~#
Code: Select all
~# mkdir /var/state
~# updatedb
~#
Please note this.
Sincerely,
Srinivas Nayak
[Precise 571 on AMD Athlon XP 2000+ with 512MB RAM]
[Fatdog 720 on Intel Pentium B960 with 4GB RAM]
[url]http://srinivas-nayak.blogspot.com/[/url]
[Fatdog 720 on Intel Pentium B960 with 4GB RAM]
[url]http://srinivas-nayak.blogspot.com/[/url]