Puppy Linux Discussion Forum

[edoc]

[GuestToo]

it depends what the problem with gxine is ... if it's missing or corrupted files, the files need to be replaced ... there may be missing or corrupted library files or configuration files

depending on the circumstances, an upgrade may not work properly

in your case, it sounds like you are having hardware problems, or maybe the cd did not burn properly, or maybe the iso file did not download properly

if the iso does not download properly, you would have a corrupted iso file, which would not be a Puppy iso at all ... it would be some sort of corrupted thing that might do anything to your system

i usually download isos with wget, which usually works well ... i always check the iso file's md5sum to be sure it is perfect ... i usually run Puppy as a frugal install, so i don't burn a cd, i just mount the iso file and copy the 4 files from it ... so to upgrade Puppy i might do something like this:

wget -c http://distro.ibiblio.org/pub/linux/distributions/puppylinux/puppy-2.16-seamonkey-fulldrivers.iso.md5.txt
wget -c http://distro.ibiblio.org/pub/linux/distributions/puppylinux/puppy-2.16-seamonkey-fulldrivers.iso
md5sum -c puppy-2.16-seamonkey-fulldrivers.iso.md5.txt
mount -o loop puppy-2.16-seamonkey-fulldrivers.iso /mnt/data
cp /mnt/data/vmlinuz /mnt/home/
cp /mnt/data/initrd.gz /mnt/home/
cp /mnt/data/pup_216.sfs /mnt/home/
cp /mnt/data/zdrv_216.sfs /mnt/home/

it's a good idea to backup the pup_save file first ... which is very easy, just copy the file somewhere ... i have never had a pup_save file larger than 256 megs

[GuestToo]

if you use a pup_save file (you seem to) you can look in /initrd/pup_rw ... corrupted and damaged and deleted files should be visible in there

there may be hidden .wh. whiteout files in pup_rw that are causing some files in pup_ro2 to be invisible and therefore "deleted" ... if there are .whw. files that should not be there, they could be deleted and the files in pup_ro2 (the pup_216.sfs file0 should be available again ... i have a script that deletes all .wh. whiteout files

find /initrd/pup_rw -noleaf -name '.wh.*' > /tmp/wh.txt
cat /tmp/wh.txt | while read J
do
echo rm -f \"$J\"
[ -r "$J" ] && rm -f "$J"
done
sync
sync

you need to reboot immediately after deleting files in pup_rw (unionfs does not like it)

[basslord1124]

I downloaded 2.16 today to try it out and didn't make it very far. It made it through the first few steps in the boot process on the CD and then it crashes telling me it can't find my CD or something to that effect. I don't remember the exact error but that's basically what it said. CD is good and checksum worked out fine. So for right now, I am halting on 2.16 and just gonna stick with 2.15.

And my 2 cents...
While I absolutely enjoy Puppy Linux, I just have not been impressed with the last 2 versions. While I can get 2.15 to work, it was not without a little bit of headache to make it work. I think the most trouble-free versions I have experienced so far is Puppy 2.13 and 2.14.

[edoc]

[basslord1124]

[basslord1124]

Well, my desktop didn't mind it at least and installed without a hitch. So now the issue is with my laptop....

[basslord1124]

Well I managed to get it going on my laptop....sorry for the previous response, my patience was a little thin that day. I ended up using the ide=nodma option at boot time before I was able to get anywhere with the installation. I have never had to do that before in previous versions of puppy.

The only thing I have noticed now which this is a minor issue, is that my touchpad on my laptop partially works...I can move the mouse pointer around but when I touch it to highlight something nothing happens. I have to use the buttons to highlight or select anything.

[edoc]

[edoc]

[edoc]

[GuestToo]

i'm not sure what the error is referring to

if the iso file name or mount point name is not correct, the error would be something like this:

mount: puppy-2.16.1-seamonkey-fulldrivers.iso: No such file or directory
mount: Could not setup loop device

if there were no free loop devices, the error would be something like:

mount: Could not find a spare loop device

if the iso file is corrupted, it might look like this:

mount: Mounting puppy-2.16.1-seamonkey-fulldrivers.iso on /mnt/data failed: Invalid argument

the closest error message to your error message would be for a corrupted iso file ... i would check the md5sum of the iso file ... type:

md5sum puppy-2.16-seamonkey-fulldrivers.iso

and see if it is the same as the md5sum in the md5sum.txt file

[edoc]

[kirk]

Edoc, make sure that the file your trying to mount on the loopback device is not in Puppy's normal file system (/root or anywhere in your pup_save file). If it is copy it to a harddrive partition (/mnt/home) and try it there.

[alienjeff]