(old)Puppy Linux Discussion Forum

To, too, two, tutu.
Which?

I decided to try Fatdog64-611-firefox.iso and Fatdog64-611-seamonkey.iso and I am getting the same error from both while attempting to boot from a frugal install using grub. Booting from the iso burned to a DVD+RW works fine. The downloaded ISO's md5sum to the correct values.

Let me explain...
# pwd
/mnt/sda2/fd64
# ls -la
total 207072
drwxr-xr-x 2 root root 4096 Feb 5 11:52 .
drwxr-xr-x 10 root root 4096 Feb 6 08:37 ..
-rw-r--r-- 1 root root 208261680 Dec 14 12:50 initrd
-rw-r--r-- 1 root root 3767056 Dec 14 12:50 vmlinuz

# cat /mnt/sda2/boot/grub/menu.lst
# GRUB configuration file '/boot/grub/menu.lst'.
#
# Start GRUB global section
default 0
#timeout 5
timeout 5
color light-gray/blue black/light-gray
# End GRUB global section
# Linux bootable partition config begins
title Puppy Linux 5.4.3 (hard disk hd0,1)
root (hd0,1)
kernel /puppy54/vmlinuz psubdir=puppy54
initrd /puppy54/initrd.gz
# Linux bootable partition config ends
# Linux bootable partition config begins
title Puppy Linux 5.4.3 pfix=ram (no pupsave file loaded, HD as hd0,1)
root (hd0,1)
kernel /puppy54/vmlinuz pfix=ram psubdir=puppy54
initrd /puppy54/initrd.gz
# Linux bootable partition config ends
# Linux bootable partition config begins
title FatDog64 version 611 (hard disk hd0,1)
rootnoverify (hd0,1)
kernel /fd64/vmlinuz
initrd /fd64/initrd
# Linux bootable partition config ends
# Linux bootable partition config begins
title FatDog64 Seamonkey 611 (hard disk hd0,1)
rootnoverify (hd0,1)
kernel /fd64Sea/vmlinuz
initrd /fd64Sea/initrd
# Linux bootable partition config ends

# grub --version
grub (GNU GRUB 0.97)

When booting and selecting either FatDog64 option I get the error:
Error 16: Inconsistent filesystem structure

I tried the root option and later changed it to rootnoverify with no change.

My puppy 5.4.3 boot works fine from grub. I'm not sure if I'm explaining this right :/

Thanks,
Rob

16 : Inconsistent filesystem structure
This error is returned by the filesystem code to denote an internal error caused by the sanity checks of the filesystem structure on disk not matching what it expects. This is usually caused by a corrupt filesystem or bugs in the code handling it in GRUB.

When the GRUB menu comes up, press the 'c' key.

Type each of the three commands from your Fatdog menu.

Which one throws the error message?

rcrsn51 wrote:

16 : Inconsistent filesystem structure
This error is returned by the filesystem code to denote an internal error caused by the sanity checks of the filesystem structure on disk not matching what it expects. This is usually caused by a corrupt filesystem or bugs in the code handling it in GRUB.

When the GRUB menu comes up, press the 'c' key.

Type each of the three commands from your Fatdog menu.

Which one throws the error message?

The step

initrd /fd64/initrd

is where the error message is returned.

rdog wrote:

rcrsn51 wrote:

16 : Inconsistent filesystem structure
This error is returned by the filesystem code to denote an internal error caused by the sanity checks of the filesystem structure on disk not matching what it expects. This is usually caused by a corrupt filesystem or bugs in the code handling it in GRUB.

When the GRUB menu comes up, press the 'c' key.

Type each of the three commands from your Fatdog menu.

Which one throws the error message?

The step

initrd /fd64/initrd

is where the error message is returned.

Sorry for the delay responding... I was off researching the issue and didn't expect such a speedy reply. I was wondering if there was a way to mount the initrd as a loop device and do a file system check on it LOL.

Thanks,
Rob

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.

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.

Hi rcrsn51,
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

rdog,

I've had that problem with Grub-0.97 on somebody's laptop. Not sure what causes it. I think I just copied the file, deleted the original and then renamed the copy and fixed it. Something up with the filesystem I guess, though fsck didn't help. Maybe it's some kind of fragmentation.

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

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

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

asound.conf is correct

Code: Select all

pcm.!default { type hw card 0 device 0 }
ctl.!default { type hw card 0 device 0 }

sound has return but I think it is a fluke.
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.

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

I have a Toshiba Satellite C850 - A825 with a Realtek 8723AE wireless device.

My question is, will my wifi work? I have had problems with Debian and Ubuntu for the past few days.

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

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!

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

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

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 .

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.

I use only wireless , but from what I read in the forum more than one complained that in FD 620 ethernet connects automatically .FD620 is much improoved than FD611 .
I would try it...