Lucid Puppy 5.0 - Bug Reports and Bug Fixes

Please post any bugs you have found
Message
Author
rsaavedra
Posts: 8
Joined: Sun 06 Jun 2010, 00:18

Bug in grub full installation

#201 Post by rsaavedra »

Ran the live CD, worked fine. Then I used the Universal installer and requested a full install on a dedicated partition, this is on a PC that had four partitions in total: one with WinXP, another with just data, the third one a small partition I created for linux swap, and the fourth the one I was going to use for Puppy. (Wanted to have WinXP and Puppy on this machine in a dual boot mode.)

After installing Puppy I went for the menu option to install grub, and asked to have it installed in the MBR, even though it's not supposed to be the "safest" option, but it had worked before for me in previous versions, if I recall correctly.

Restarted the PC after the grub install finished, and grub's menu appeared. Selecting WinXP worked fine. Restarted and selected Puppy, but it did not work. It gave me a "Kernel panic: no init found. Try passing init= option to kernel" message.

Fortunately, that was an easy to fix bug. The menu.lst file indeed did not have an initrd line.

What is more, for some reason the grub installation left the following line in /boot/grub/menu.lst :
kernel /boot/vmlinuz

When in fact, the installation had left the vmlinuz file right under /, not under /boot

I had to fix both of these problems in the menu.lst file. After that, choosing Puppy on the grub menu did finally boot Puppy.

As easy to fix as these bugs were, they are likely to ruin the installation experience for more than one newbie. Especially because a bare full installation on a dedicated partition using grub I think should require no user intervention to "fix" misconfigurations like these.

It is kind of ironic that the grub installation did perfectly find Windows XP and did launch it without a problem, whereas the fresh Puppy installation just created by the same Live CD could not be launched from that same grub install.

PS. I also think the universal installer could handle the installation of grub by itself, instead of telling the user to go ahead and install grub after having installed Puppy.

User avatar
rjbrewer
Posts: 4405
Joined: Tue 22 Jan 2008, 21:41
Location: merriam, kansas

#202 Post by rjbrewer »

The menu.lst for a full install does not use an initrd line.

The installer does the install of grub itself; just asking where you
want it.

Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs

rsaavedra
Posts: 8
Joined: Sun 06 Jun 2010, 00:18

#203 Post by rsaavedra »

rjbrewer wrote:The menu.lst for a full install does not use an initrd line.
How come my installation needed it then? How come I got the Kernel Panick message? I might be calling the actual kind of install incorrectly?
The installer does the install of grub itself; just asking where you
want it.
This wasn't the case for me. It installed Puppy with the Universal installer, and after installation it told me to go and install grub. I never got asked to have it installed by the Universal installer itself. Am I misremembering some things maybe? I did all of this this very afternoon, don't think I could have such a bad memory.

(For the record, I've installed ealier Puppy versions before at least three times without these problems, and I've installed several linux distros (Ubuntu and Debian) both on dedicated machines, as dual boots, and inside virtual machines using VirtualBox. So I wouldn't consider myself a newbie, and yet I had these end-user problems with a bare full install in this latest version of Puppy.)

User avatar
rjbrewer
Posts: 4405
Joined: Tue 22 Jan 2008, 21:41
Location: merriam, kansas

#204 Post by rjbrewer »

The important thing is; it's working for you.
My guess is that you did a frugal install; did it have you make a
save file?

Here is a full install video ; see if it's the same as the way
you did it.

This video doesn't include the dual boot with Windows.

http://www.murga-linux.com/puppy/viewto ... 65&t=29653

Maybe there's something strange about the installer in these new
releases

Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs

rsaavedra
Posts: 8
Joined: Sun 06 Jun 2010, 00:18

#205 Post by rsaavedra »

rjbrewer wrote:The important thing is; it's working for you.
My guess is that you did a frugal install; did it have you make a
save file?

Here is a full install video ; see if it's the same as the way
you did it.

This video doesn't include the dual boot with Windows.

http://www.murga-linux.com/puppy/viewto ... 65&t=29653
Yet it is working for me, after I had to dig in and fix things though.

Let's say I'm misremembering, and I might have done a frugal install instead of a full one. Even so, why on Earth wouldn't grub simply install properly and point to the right Puppy files in the right places?

Whether invoked directly from the Universal installer or afterwards, and whether in a full or frugal install, the resulting menu.lst file should be correct. The installation should perfectly configure things (and grub) to properly launch whatever type of freshly installed Puppy resides on my partition.

This problem that I had today never happened in previous dual boot installations of Puppy that I had done before. So there is a bug in there somewhere that had an impact in my installation of the latest Puppy. I just wanted to report on it. In fact, I just registered in this forum to do so. --From Puppy 4.0 (2008) I had installed all versions and never needed to register here to post any problems installing those previous Puppies. That might say something about this latest install.

User avatar
8-bit
Posts: 3406
Joined: Wed 04 Apr 2007, 03:37
Location: Oregon

#206 Post by 8-bit »

I used to be able to enter username root password woofwoof in CUPS for administrator settings,
Now it does not work,
So how do I change settings?

EDIT:
Got administrator setting working without having a window pop up for username password!

I edited cupsd.conf by commenting out the line "Require user @SYSTEM" as per the following segment.
Of course you must realize that this takes away some protection. But we never had that much with cups anyway.

Code: Select all

# Restrict access to configuration files...
<Location /admin/conf>
  AuthType None
#  Require user @SYSTEM
  Order deny,allow
</Location>
Last edited by 8-bit on Mon 07 Jun 2010, 05:56, edited 1 time in total.

gcmartin

Lucid Puppy 5.0 - Bug Reports and Bug Fixes

#207 Post by gcmartin »

@rsaavedra is sharing some important info here. Judging from his account of the GRUB changes, it seems that he has a install issue that is cause for some review.

Maybe should take note and address this. For newbie acceptance if nothing else.

User avatar
James C
Posts: 6618
Joined: Thu 26 Mar 2009, 05:12
Location: Kentucky

#208 Post by James C »

rsaavedra wrote: Whether invoked directly from the Universal installer or afterwards, and whether in a full or frugal install, the resulting menu.lst file should be correct. The installation should perfectly configure things (and grub) to properly launch whatever type of freshly installed Puppy resides on my partition.
The Puppy installer doesn't automatically install grub and configure the menu lst because 1) some users want grub installed to the mbr while others choose to leave the mbr untouched and 2) some multi-boot users don't want to reinstall grub every time they install, its easier and faster to just edit the menu lst.

There are several ways to do a frugal install, and the resulting entry in the menu lst will be different as well.

HTH. :)

User avatar
Béèm
Posts: 11763
Joined: Wed 22 Nov 2006, 00:47
Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win

#209 Post by Béèm »

peebee wrote:I think I am one of the many who will stick with 4.3.1 until 5.0.1 is properly sorted. I am also having problems with my WiFi connection which I'll put in a separate post.

Thanks for your interest and help - if you think of anything else for me to try I'll be happy to have a go.
I would PM playdayz and reference your thread.
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]

novellahub
Posts: 15
Joined: Thu 21 Jun 2007, 16:11
Location: Shakopee, MN USA
Contact:

Re: Presario laptop 14xl250 (Trident CyberBlade) won't boot

#210 Post by novellahub »

[quote="Gurglin"]I tried to run the live CD on my 10-year-old laptop compaq presario 14 xl 250 (Trident CyberBlade graphic card), which has always worked with ANY puppy version (latest kernel), including Quirky.

With my major disappointment LuPu is the first Puppy Distro EVER which not only gives me problems, but that does not even boot! The boot process ends when on the screen I read “starting X, specs (...)
Joe
Lupu 5.28

rsaavedra
Posts: 8
Joined: Sun 06 Jun 2010, 00:18

#211 Post by rsaavedra »

James C wrote:The Puppy installer doesn't automatically install grub and configure the menu lst because 1) some users want grub installed to the mbr while others choose to leave the mbr untouched and 2) some multi-boot users don't want to reinstall grub every time they install, its easier and faster to just edit the menu lst.
Good reasons to not have it "installed automatically." Not good reasons to simply not offer the user the option to install it right away, instead of asking the user to go ahead and install it afterwards, which is one of my points.
James C wrote:There are several ways to do a frugal install, and the resulting entry in the menu lst will be different as well.
True, but what difference does that make to my other point? I installed Puppy, whichever way, and then I choose to install grub. Said grub installation should *not* be left pointing to the Puppy files in the wrong folder, and should *not* be left with missing lines, as if I had installed Puppy a different way.

User avatar
rjbrewer
Posts: 4405
Joined: Tue 22 Jan 2008, 21:41
Location: merriam, kansas

#212 Post by rjbrewer »

rsaavedra wrote:
James C wrote:The Puppy installer doesn't automatically install grub and configure the menu lst because 1) some users want grub installed to the mbr while others choose to leave the mbr untouched and 2) some multi-boot users don't want to reinstall grub every time they install, its easier and faster to just edit the menu lst.
Good reasons to not have it "installed automatically." Not good reasons to simply not offer the user the option to install it right away, instead of asking the user to go ahead and install it afterwards, which is one of my points.
James C wrote:There are several ways to do a frugal install, and the resulting entry in the menu lst will be different as well.
True, but what difference does that make to my other point? I installed Puppy, whichever way, and then I choose to install grub. Said grub installation should *not* be left pointing to the Puppy files in the wrong folder, and should *not* be left with missing lines, as if I had installed Puppy a different way.
Just did a full install of Lucid to an old laptop.
Worked fine; same as every time since I started with 3.00.
No need to touch grub menu.lst.

Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs

mave
Posts: 129
Joined: Thu 02 Apr 2009, 13:42
Location: Germany

encrypted ext3-lupusave: broken files (?)

#213 Post by mave »

Hi,

testing encryption on a new Lucid Puppy 5.0.1 with lupusave-file within ext3 file format. After next starting desktop icons (and other) are gone. Look at the screenshot.

Did I fail reading a special info about ext3 and encryption or...? (doing ext2 is okay)

Cheers
Markus
Attachments
desktop-with-encrypted-ext3-lupusave.jpg
(36.32 KiB) Downloaded 1584 times

rsaavedra
Posts: 8
Joined: Sun 06 Jun 2010, 00:18

#214 Post by rsaavedra »

rjbrewer wrote:Just did a full install of Lucid to an old laptop.
Worked fine; same as every time since I started with 3.00.
No need to touch grub menu.lst.
Good for you!

Was that a dual boot setup? (Mine was.)

I haven´t retried the installation, but once again, in my case with the latest version it wasn't the same as every time since I started installing Puppy years ago.

User avatar
rjbrewer
Posts: 4405
Joined: Tue 22 Jan 2008, 21:41
Location: merriam, kansas

#215 Post by rjbrewer »

rsaavedra wrote:
rjbrewer wrote:Just did a full install of Lucid to an old laptop.
Worked fine; same as every time since I started with 3.00.
No need to touch grub menu.lst.
Good for you!

Was that a dual boot setup? (Mine was.)

I haven´t retried the installation, but once again, in my case with the latest version it wasn't the same as every time since I started installing Puppy years ago.
1 install to empty drive
1 dual boot with another puppy
1 dual boot with Xp
1 triple boot with puppies and Xp

Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs

rsaavedra
Posts: 8
Joined: Sun 06 Jun 2010, 00:18

#216 Post by rsaavedra »

rjbrewer wrote:1 install to empty drive
1 dual boot with another puppy
1 dual boot with Xp
1 triple boot with puppies and Xp
Hmm, and did you install Grub onto the MBR in any of those cases, in particular your 3rd case, dual boot with Xp, which would be the closest to my case?

User avatar
rjbrewer
Posts: 4405
Joined: Tue 22 Jan 2008, 21:41
Location: merriam, kansas

#217 Post by rjbrewer »

rsaavedra wrote:
rjbrewer wrote:1 install to empty drive
1 dual boot with another puppy
1 dual boot with Xp
1 triple boot with puppies and Xp
Hmm, and did you install Grub onto the MBR in any of those cases, in particular your 3rd case, dual boot with Xp, which would be the closest to my case?
I've always installed Grub to MBR; with Win98, ME, Xp , and even Win 7
once. They were almost always fresh installs of Win, and just had a
single partition.
It's not too fashionable anymore, with things like Grub4Dos, LinNWin,
etc. being recommended very often.

Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs

User avatar
James C
Posts: 6618
Joined: Thu 26 Mar 2009, 05:12
Location: Kentucky

#218 Post by James C »

rjbrewer wrote: I've always installed Grub to MBR; with Win98, ME, Xp , and even Win 7
once. They were almost always fresh installs of Win, and just had a
single partition.
It's not too fashionable anymore, with things like Grub4Dos, LinNWin,
etc. being recommended very often.
I always install grub to the MBR too.Single boot,dual boot,triple boot........right now my test box has Windows and 14 Linux installs. :lol:

Works fine for me every time.

rsaavedra
Posts: 8
Joined: Sun 06 Jun 2010, 00:18

#219 Post by rsaavedra »

rjbrewer wrote:I've always installed Grub to MBR; with Win98, ME, Xp , and even Win 7
once. They were almost always fresh installs of Win, and just had a
single partition.
It's not too fashionable anymore, with things like Grub4Dos, LinNWin,
etc. being recommended very often.
Well, what I got does not seem easily reproduceable them.

One last question: under which folder did your vmlinuz file ended up located, under / or under /boot?

As I explained earlier, after the install my original (and wrong) menu.lst indicated that vmlinuz was allegedly under /boot, when it actually ended up under /. Why that happened I can't really tell, but it happened (together with the missing initrd line), and it wouldn't let Puppy launch right after installation.

I'll try to redo the installation. It was in an old Sony desktop PC that is not mine, so I'll have to get back to that place and retry the installation from scratch. Will report afterwards.

cinclus_cinclus
Posts: 68
Joined: Sun 22 Feb 2009, 10:00

UnsolvedRe: [solved] compile error: Barry's patched 2.6.33.2

#220 Post by cinclus_cinclus »

cinclus_cinclus wrote:A large part of the kernel source doesn't build with the binutils v. 2.18 which are part of lupu_devx_501.sfs.

Install binutils v. 2.20.1 instead from the Puppy Package Manager of Lupu 501 for compiling Barry's patched 2.6.33.2 kernel-source.
The bug is always there in lucy203 and luci_devx_203.sfs.

Same remedy: use binutils 2.20.1 from Puppy Package Manager.

Tested by recompiling Barry's newest kernel-source (2.6.33.5) patched with BFS-scheduler-patch by Con Kolivas: 2.6.33-sched-bfs-318.patch.

Post Reply