Puppy Linux Discussion Forum

edoc · Posted: Wed 01 Aug 2007, 08:57 Post subject:

Which log file should I post so someone can spot where my laptop is
finding and loading 216, please?

I have deleted every reference I can find to 216 and all of the displayed
boot text says it is loading 217 but I still end up in the broken 216.

It is driving me nuts ... and more importantly it is preventing productivity.

Sit Heel Speak · Joined: 30 Mar 2006 Posts: 2595 Location: downwind

1. Hooray, puppyinstaller-bk3 ejects the live-DVD!

2. I didn't try the GRUB installation, I just clicked through the "X" close buttons until no more appeared, because I have a pre-existing GRUB installation (Grub4DOS).

2. Umm, but the DVD door is not automatically closed when I reboot.

3. Urk. Unlike with the original PUI from the 2.17 (not .1rc) live-DVD, the full (normal) install from puppyinstaller-bk3 on first disk-boot asks again for locale, puts me through xorgwizard, and needs the NIC and network IP settings reconfigured. In other words, on first disk-boot Puppy isn't reading the pup_save.2fs which I created upon shutting down the initial live-DVD boot. Yes, pup_save.2fs is present in / and its timestamp is correct.

4. On second disk-boot, the locale and xorg settings are not asked for, i.e. pup_save.2fs evidently is being read, but the network IP addresses once again must be reconfigured. The first disk-boot session is not saving them to pup_save.2fs. So, I entered the net stuff again in the Wizard and Seamonkey.

5. On third disk-boot, all ist in ordnung with locale, xorg settings, and network card module and IP addresses.

6. A nit, the "NORMAL" button (option 2) is on the left, the "COEXIST" button (option 1) is on the right. Oy vey! To a native English speaker this looks backward.

Dougal · Posted: Wed 01 Aug 2007, 16:36 Post subject:

edoc · Posted: Wed 01 Aug 2007, 16:58 Post subject:

BarryK · Posted: Wed 01 Aug 2007, 23:04 Post subject:

BarryK · Posted: Wed 01 Aug 2007, 23:10 Post subject:

Sit Heel Speak · Joined: 30 Mar 2006 Posts: 2595 Location: downwind

Ah, I see. This is yet one more reason why I must learn shell scripting. So I can actually hold intelligent conversation with Barry, Dougal, GuestToo, et al...

BarryK · Posted: Fri 03 Aug 2007, 07:44 Post subject:

Sit Heel Speak,
Your feedback is very useful! I was very tired when I posted that last response. From your tester point of view, your comments are perfectly valid and quite intelligent.
Full install is very neglected. The install itself seems basically okay, but the bootup scripts are seeing something different. I did a test full install, and also got that xorgwizard problem. I didn't test the network or anything else. Regarding the xorg wizard needing to be repeated on second boot, I haven't got a clue why. ...it's no doubt some simple little thing, something is or is not being saved on the first boot.

Sit Heel Speak · Joined: 30 Mar 2006 Posts: 2595 Location: downwind

Sage · Joined: 04 Oct 2005 Posts: 4622 Location: GB

Don't worry about it, SHS, there's always plenty of folks much further down the tracks! You can always speak to me in the Queen's English.......

jhecht

This is a description of a (different) consistent bug I found w/the PUI in 2.17.

I had a computer with a 3.4 gig HD set up with Puppy 2.14 on HDA. Only two partitions on HDA, Linux and a swap partition, but two other HD's in the computer as HDB1 and HDD1. Also have a cd-rw drive as HDC1. All the HD's are elderly IDE - no SATA, no SCSI.

Previously, I had partitioned the 3.4 gig drive with a Linux swap partition at the FRONT (beginning) of the drive, followed by an Ext 2 partition for Puppy 2.14.

When I tried to use the PUI, it kept trying to install in the swap partion on HDA1, and did NOT give me the option to go onto HDA2.

This seems consistent - the PUI wants to install on the first partion.

I just wiped the drive, and re-partioned with GParted, putting the swap
partition at the REAR (end) of HDA1, as HDA2. This worked fine, since by reversing the position(s) of the partions, I worked around the PUI's stubborn desire to install on the first partition.

After that, the installation was flawless!

Hope this helps...

bobwrit · Joined: 12 Mar 2007 Posts: 286

Sit Heel Speak · Joined: 30 Mar 2006 Posts: 2595 Location: downwind

/etc/rc.d/rc.shutdown should not offer to create a pup_save.2fs, in the case where Puppy Universal Installer has just been used to create a "normal" hdd install. If upon shutdown from the live-CD you say yes, create a pup_save, having just finished using PUI to make a "normal" install, the pup_save is placed on the "normal" install partition in /. The unfortunate thing then is, when the "normal" install is subsequently booted-into, the pup_save.2fs therein is indeed mounted; PUPSTATE is even written into it. This may confuse the average dummy (ahem *cough*yours truly*cough*) into believing that the pup_save works in the "normal" install as it does in the "coexist."

Sit Heel Speak · Joined: 30 Mar 2006 Posts: 2595 Location: downwind

Aaaand, a craftsmanship quibble: PUI SANITY CHECK is making reference to pup_save.3fs rather than .2fs.