BIOS or Puppy problem? (Solved)

Booting, installing, newbie
Message
Author
User avatar
bambuko
Posts: 578
Joined: Wed 14 Nov 2007, 14:03
Location: North Devon

#21 Post by bambuko »

foxpup wrote:Posts just crossed :D
It is syslinux. Can you give the contence of syslinux.cfg?
there it is:
default puppy
display boot.msg
prompt 1
timeout 50

F1 boot.msg
F2 help.msg
F3 help2.msg

label puppy
kernel vmlinuz
append initrd=initrd.gz pmedia=usbflash pfix=copy

foxpup
Posts: 1132
Joined: Fri 29 Jul 2016, 21:08

#22 Post by foxpup »

I don't see why it does not boot.

It looks like Tahrpup misses something.
I have Tahrpup running in my new uefi laptop, but with the xenialpup kernel.
http://murga-linux.com/puppy/viewtopic. ... start=1754
You could try that.Copy the zdrv and vmlinuz from xenialpup onto the usb and change the name of the zdrv for tahrpup.
Your machine may just need a newer kernel.
Someone else who did similar thing:
http://www.murga-linux.com/puppy/viewto ... 438#997438
Last edited by foxpup on Tue 03 Jul 2018, 21:20, edited 1 time in total.

User avatar
nic007
Posts: 3408
Joined: Sun 13 Nov 2011, 12:31
Location: Cradle of Humankind

#23 Post by nic007 »

Do a manual frugal install with grub4dos as bootloader -
Boot with the puppy CD
Backup your savefile first to another media and then prepare the stick with gparted (re-format it and make it bootable)
Create a folder on the stick, call it puppy602 (presuming you are installing tahr 602)
Copy the base sfs, zdrv, initrd.gz and vmlinuz from the cd to folder puppy602 (make sure the names of the files are correct and in small letters)
Run grub4dos bootloader config from menu and install grub to the stick
Reboot with stick and see if it works.

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#24 Post by bigpup »

Tahrpup 6.0.2 was a version of Tahrpup when it was still being bug fixed.
It did have some bugs that still needed fixed.

Tahrpup 6.0.5 was the final bug fixed release version.
I suggest you try it if you want to use Tahrpup.
http://puppylinux.com/

Fat32 format can get a fragmented file system.
I suggest you use Gparted to do a fresh format of the USB stick.
Make sure the partition is flagged as boot.

I have seen a fresh do over fix a lot of issues.
Sometimes installs go wrong.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#25 Post by bigpup »

n the meantime, I have quickly downloaded Xenial-Pup64-7.5 and created bootable stick using Rufus in Win7 - it worked OK first time ...
It could be that the hardware support, for this computer, is just not in Tahrpup 6.0.2
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

User avatar
bambuko
Posts: 578
Joined: Wed 14 Nov 2007, 14:03
Location: North Devon

#26 Post by bambuko »

Thank you all for your advice and recommendations.
I have tried Tahrpup 6.0.5 but it still caused problems on my desktop.
I have tried different sticks with the same result.

Having slept over the problem, I have eventually settled on XenialPup64 7.5 as the "solution".
If Tahrpup was my only option, I would have no choice but to try to make it work... but, the stick with XenialPup64 works on all my machines , so it was an easy decision.

User avatar
nic007
Posts: 3408
Joined: Sun 13 Nov 2011, 12:31
Location: Cradle of Humankind

#27 Post by nic007 »

bambuko wrote:Thank you all for your advice and recommendations.
I have tried Tahrpup 6.0.5 but it still caused problems on my desktop.
I have tried different sticks with the same result.

Having slept over the problem, I have eventually settled on XenialPup64 7.5 as the "solution".
If Tahrpup was my only option, I would have no choice but to try to make it work... but, the stick with XenialPup64 works on all my machines , so it was an easy decision.
Looks like a kernel issue as someone mentioned before. Your machine wants the new stuff.

User avatar
bambuko
Posts: 578
Joined: Wed 14 Nov 2007, 14:03
Location: North Devon

#28 Post by bambuko »

Yes, indeed, that was my guess as well - just wanted to check with you guys whether it wasn't simple operator error...
Thank you for your help!

Post Reply