newest kernel 3.1.8 & 3.0.16 test on lupu528

[otropogo]

When, and possibly why, did this all change over to Slacko in the stead of Lupu? What did I miss? Is this version of Lupu gone now?
Thanks,
CA

Calexand:
Thank you.I want to say that kernel-3.0.8 on lupu_528 will be tested later.
I plan to test new kernel on any distro of "pup" contains:slacko lupu and so on.
It will comes soon.

I'd like to see a Lupu_K3.08 too. For my purposes, lupu has a hugely greater wealth of applications, so that the only area in which Slacko is superior for me is native 3TB and USB3 support. Presumably that comes with the more recent Kernel.

I would like to settle down for a year or two with a Puppy that can be kept fairly up to date, the way it used to be with Puppy 4.xx and earlier.

[wuxiandianzi]

When, and possibly why, did this all change over to Slacko in the stead of Lupu? What did I miss? Is this version of Lupu gone now?
Thanks,
CA

Calexand:
Thank you.I want to say that kernel-3.0.8 on lupu_528 will be tested later.
I plan to test new kernel on any distro of "pup" contains:slacko lupu and so on.
It will comes soon.

I'd like to see a Lupu_K3.08 too. For my purposes, lupu has a hugely greater wealth of applications, so that the only area in which Slacko is superior for me is native 3TB and USB3 support. Presumably that comes with the more recent Kernel.

I would like to settle down for a year or two with a Puppy that can be kept fairly up to date, the way it used to be with Puppy 4.xx and earlier.

updated!

[jim3630]

installed k3.1.0--on--lupu_528 manual frugal to ext4. would not create a save file. installed pupsaveconfig then able to create a savefile.

although 3.1.0 kernel contains new broadcom drivers it also needs the firmware which apparently wasn't included. installed broadcom firmware pet below then able to make wifi connection on wlan0.

wuxiandianzi great pup and really fast. if you could include the broadcom firmware and pupsaveconfig then your pup would be usefull for noob user out of the box.

---------
the firewall tray icon remain with caution sign even after activating the firewall.

quickpet error "quickpet does not support your puppy"

--------
installed mesa and xorg_high. glxgears hardly moving, jerkie and not sure what is wrong?

[wuxiandianzi]

installed k3.1.0--on--lupu_528 manual frugal to ext4. would not create a save file. installed pupsaveconfig then able to create a savefile.

although 3.1.0 kernel contains new broadcom drivers it also needs the firmware which apparently wasn't included. installed broadcom firmware pet below then able to make wifi connection on wlan0.

wuxiandianzi great pup and really fast. if you could include the broadcom firmware and pupsaveconfig then your pup would be usefull for noob user out of the box.

---------
the firewall tray icon remain with caution sign even after activating the firewall.

quickpet error "quickpet does not support your puppy"

--------
installed mesa and xorg_high. glxgears hardly moving, jerkie and not sure what is wrong?

Thank you, This is a pet to fix quickpet.

[ETP]

wuxiandianzi

Currently testing manual frugal install on FAT 32 USB2 stick. (Syslinux 4.04 boot with vesamenu.c32 ). MD5s were first confirmed.
Upon selecting 528 k3.1.0 from the menu I was after about 2 seconds, presented with the following screen and had to power off.

http://imageshack.us/photo/my-images/84 ... 077ub.jpg/

Having run chkd on the stick together with a virus check I then repeated the installation with the same outcome. All the other pups on the stick continue to boot normally as does my main O/S.
Extract from syslinux.cfg as follows:

Code: Select all

LABEL tc4
MENU LABEL TC 4.0.2          25/09/11
KERNEL /tc4/boot/vmlinuz
APPEND initrd=/tc4/boot/tinycore.gz quiet noswap nodhcp kmap=qwerty/uk  nozswap waitusb=5:UUID=D496-93EA tce=UUID=D496-93EA/tc4

LABEL 528
MENU LABEL Luci Pup 528      12/08/11
KERNEL /pup528/vmlinuz
APPEND initrd=/pup528/initrd.gz pmedia=usbflash pdev1=sdc1 psubdir=pup528

LABEL 5283
MENU LABEL Lupu Pup 528k307  21/10/11
KERNEL /pup5283/vmlinuz rd_NO_MD rd_NO_DM
APPEND initrd=/pup5283/initrd.gz pmedia=usbflash pdev1=sdc1 psubdir=pup5283

LABEL 51110
MENU LABEL Racy-5.1.110      27/10/11
KERNEL /pup51110/vmlinuz
APPEND initrd=/pup51110/initrd.gz pmedia=usbflash pdev1=sdc1 psubdir=pup51110

LABEL 53308
MENU LABEL Slacko5.3_k3.0.8  31/10/11
KERNEL /pup53308/vmlinuz-3.0.8
APPEND initrd=/pup53308/initrd-3.0.8.gz pmedia=usbflash pdev1=sdc1 psubdir=pup53308

LABEL 528310
MENU LABEL Lupu Pup 528k310  03/11/11
KERNEL /p528310/vmlinuz-3.1.0
APPEND initrd=/p528310/initrd-3.1.0.gz pmedia=usbflash pdev1=sdc1 psubdir=p528310

Possible causes.
1. School boy error on my part.
2. Kernel 3.1.0 (which contains support for newer NVIDIA cards) clashes with my 6 year old Geoforce7300SE.
3. K 3.1.0 (vmlinuz) does not like booting from FAT32.
4. I need stronger medication!

This is what testing is all about. I have never seen this effect before but someone may know the answer.

[wuxiandianzi]

wuxiandianzi

Currently testing manual frugal install on FAT 32 USB2 stick. (Syslinux 4.04 boot with vesamenu.c32 ). MD5s were first confirmed.
Upon selecting 528 k3.1.0 from the menu I was after about 2 seconds, presented with the following screen and had to power off.

http://imageshack.us/photo/my-images/84 ... 077ub.jpg/

Having run chkd on the stick together with a virus check I then repeated the installation with the same outcome. All the other pups on the stick continue to boot normally as does my main O/S.
Extract from syslinux.cfg as follows:

Code: Select all

LABEL tc4
MENU LABEL TC 4.0.2          25/09/11
KERNEL /tc4/boot/vmlinuz
APPEND initrd=/tc4/boot/tinycore.gz quiet noswap nodhcp kmap=qwerty/uk  nozswap waitusb=5:UUID=D496-93EA tce=UUID=D496-93EA/tc4

LABEL 528
MENU LABEL Luci Pup 528      12/08/11
KERNEL /pup528/vmlinuz
APPEND initrd=/pup528/initrd.gz pmedia=usbflash pdev1=sdc1 psubdir=pup528

LABEL 5283
MENU LABEL Lupu Pup 528k307  21/10/11
KERNEL /pup5283/vmlinuz rd_NO_MD rd_NO_DM
APPEND initrd=/pup5283/initrd.gz pmedia=usbflash pdev1=sdc1 psubdir=pup5283

LABEL 51110
MENU LABEL Racy-5.1.110      27/10/11
KERNEL /pup51110/vmlinuz
APPEND initrd=/pup51110/initrd.gz pmedia=usbflash pdev1=sdc1 psubdir=pup51110

LABEL 53308
MENU LABEL Slacko5.3_k3.0.8  31/10/11
KERNEL /pup53308/vmlinuz-3.0.8
APPEND initrd=/pup53308/initrd-3.0.8.gz pmedia=usbflash pdev1=sdc1 psubdir=pup53308

LABEL 528310
MENU LABEL Lupu Pup 528k310  03/11/11
KERNEL /p528310/vmlinuz-3.1.0
APPEND initrd=/p528310/initrd-3.1.0.gz pmedia=usbflash pdev1=sdc1 psubdir=p528310

Possible causes.
1. School boy error on my part.
2. Kernel 3.1.0 (which contains support for newer NVIDIA cards) clashes with my 6 year old Geoforce7300SE.
3. K 3.1.0 (vmlinuz) does not like booting from FAT32.
4. I need stronger medication!

This is what testing is all about. I have never seen this effect before but someone may know the answer.

I am very very very very sorry.
I can not open your URL~!

[Ray MK]

Hi wuxiandianzi

Wow - this is an interesting Puppy - and fast.

Manual frugal to ext3 sda1 - booting via grub4dos.

Who would think that Puppy using the latest 3.1.0 kernel
would be so responsive on a 10yr old laptop.

Acer Travelmate 243LC
256mb ram, 2.5Ghz Celeron Proc, 800mb swap partition.

Opera 12alpha is very fast and seems stable.
(running from a browser folder on sda1)

Luvly Puppy - thanks for sharing.

Many thanks and very best regards - Ray

[ETP]

wuxiandianzi wrote:
I am very very very very sorry.
I can not open your URL~!

[wuxiandianzi]

Wo ...........

I guess that the kernel crash for bad video card drivers.
It is disp this messages after X or before X? or happens when the kernel load ?
give me more Information of your PC.

thank you!

[jim3630]

Thank you, This is a pet to fix quickpet.

wuxiandianzi,

thanks for the quickpet fix pet. will try it out once back in 3.1.0

ithe upgrade pets mesa and xorg_high had poor performance due to the kernel?

[otropogo]

Just now I was suprised on booting Puppy 5.2.8 to have a popup called "Bootmanager: SFS files" appear on the desktop. I've only seen this popup once before, when trying out one of the other Puppy versions, and I have no idea what makes it appear.

The only thing unusual about this boot up is that I had just finished booting with a different savefile, on another partition, and had changed the name of the savefile running when the bootmanager appeared.

In the left hand column of the bootmanager two sfs files were listed:

puppy_slacko_5.3.sfs
puppy_wary_5.2.sfs

both of these are in the "home" partition.

What would have happend if I had added one of these to the right column?

lupuk310_528.sfs, which is in another partition, was not listed.

If it had been on the home partition, would it have been listed also?

And if I had moved it to the right column, as the bootmanager suggests, then what would happen?

Would the effect take place only on the next reboot? If I had the intrd and vmlinuz files bundled with this sfs in the same folder with the sfs file, would these be loaded too on reboot, or would it be a godawful mess?

And most mysteriously, what is it that causes the SFS Bootmanager to appear as described, and how does it determine which sfs files to display.?

I note that the two displayed are both in the root directory of the home partition. I also have Puppy_4.3.1.sfs in a pubsave folder in that partition, and it was not displayed in the list. Does the boot manager only display sfs files located in the root directory of the home partition?

Update: Since I already had my savefile backed up in order to try the lupu 5.28 instant update 002, I decided to play with the 3.10 kernel sfs as well.

I moved the 310.sfs file, vmlinuz and initrd to the root directory of my home partition, and got the sfs bootmanager popup again. This time, as anticipated, it also showed the 310.sfs in the left column. I then "added" it to the right column, and clicked on OK. Xmanager then reset. Whether this had any effect or not, I couldn't tell. Is there a quick way to tell which kernel is running?

Will now reboot to see what happens.

[ETP]

wuxiandianzi wrote:

Wo ...........

I guess that the kernel crash for bad video card drivers.
It is disp this messages after X or before X? or happens when the kernel load ?
give me more Information of your PC.

Thanks for your prompt reply. Hardware reports are attached. I decided to try another stick with syslinux 3.82 (as opposed to 4.04) with no vesamenu and a very basic syslinux.cfg. Once again I got the same screen and no x or sign of the kernel loading. However across the very bottom of the screen I got error messages:
“please use a boot loader program instead

[puppyluvr]

Hello,
Tried out K3.10 version on CQ-56..
Booted fine, got "woof woof" on bootup..
Then noticed wireless card light "strobing" on and off very rapidly...
Fearing damage, I shut it down...
And thoughts..
Id be willing to boot it again, if there is an error log that you might be able to deduce what it is...

Also, got 3.08 pet and will woof up a few tests with it, and get back...

[ETP]

Wuxiandianzi

Syslinux booting problem solved.

It transpires that if the kernel version finishes with a zero (0) it cannot boot. It is probably interpreting the 3.1.0 as a vga code hence the “multicoloured screen of death

[wuxiandianzi]

[quote="ETP"]Wuxiandianzi

Syslinux booting problem solved.

It transpires that if the kernel version finishes with a zero (0) it cannot boot. It is probably interpreting the 3.1.0 as a vga code hence the “multicoloured screen of death

[wuxiandianzi]

Thank you, This is a pet to fix quickpet.

wuxiandianzi,

thanks for the quickpet fix pet. will try it out once back in 3.1.0

ithe upgrade pets mesa and xorg_high had poor performance due to the kernel?

Thank you, This distro is the same as offical lupu_528 except kernel.
mesa and xorg_high has not be updated. and it should not have much influence on kernel. The main reason is Xorg I think.The new kernel should better support for display.

[wuxiandianzi]

Just now I was suprised on booting Puppy 5.2.8 to have a popup called "Bootmanager: SFS files" appear on the desktop. I've only seen this popup once before, when trying out one of the other Puppy versions, and I have no idea what makes it appear.

The only thing unusual about this boot up is that I had just finished booting with a different savefile, on another partition, and had changed the name of the savefile running when the bootmanager appeared.

In the left hand column of the bootmanager two sfs files were listed:

puppy_slacko_5.3.sfs
puppy_wary_5.2.sfs

both of these are in the "home" partition.

What would have happend if I had added one of these to the right column?

lupuk310_528.sfs, which is in another partition, was not listed.

If it had been on the home partition, would it have been listed also?

And if I had moved it to the right column, as the bootmanager suggests, then what would happen?

Would the effect take place only on the next reboot? If I had the intrd and vmlinuz files bundled with this sfs in the same folder with the sfs file, would these be loaded too on reboot, or would it be a godawful mess?

And most mysteriously, what is it that causes the SFS Bootmanager to appear as described, and how does it determine which sfs files to display.?

I note that the two displayed are both in the root directory of the home partition. I also have Puppy_4.3.1.sfs in a pubsave folder in that partition, and it was not displayed in the list. Does the boot manager only display sfs files located in the root directory of the home partition?

Update: Since I already had my savefile backed up in order to try the lupu 5.28 instant update 002, I decided to play with the 3.10 kernel sfs as well.

I moved the 310.sfs file, vmlinuz and initrd to the root directory of my home partition, and got the sfs bootmanager popup again. This time, as anticipated, it also showed the 310.sfs in the left column. I then "added" it to the right column, and clicked on OK. Xmanager then reset. Whether this had any effect or not, I couldn't tell. Is there a quick way to tell which kernel is running?

Will now reboot to see what happens.

Thank you.
I think you have been used Bootmanager to load xxx.SFS and you have saved pupsave file.
When you boot this distro the script load your pupsave file and find other sfs files in you "home" folder. so Bootmanager appear.
Note that puppy_XXX.sfs is main filesystem and it has been loaded into tmpfs. you should not load it twice. so it will appear in left column.

[otropogo]

Just now I was suprised on booting Puppy 5.2.8 to have a popup called "Bootmanager: SFS files" appear on the desktop. I've only seen this popup once before, when trying out one of the other Puppy versions, and I have no idea what makes it appear.

The only thing unusual about this boot up is that I had just finished booting with a different savefile, on another partition, and had changed the name of the savefile running when the bootmanager appeared.

In the left hand column of the bootmanager two sfs files were listed:

puppy_slacko_5.3.sfs
puppy_wary_5.2.sfs

both of these are in the "home" partition.

What would have happend if I had added one of these to the right column?

lupuk310_528.sfs, which is in another partition, was not listed.

If it had been on the home partition, would it have been listed also?

And if I had moved it to the right column, as the bootmanager suggests, then what would happen?

Would the effect take place only on the next reboot? If I had the intrd and vmlinuz files bundled with this sfs in the same folder with the sfs file, would these be loaded too on reboot, or would it be a godawful mess?

And most mysteriously, what is it that causes the SFS Bootmanager to appear as described, and how does it determine which sfs files to display.?

I note that the two displayed are both in the root directory of the home partition. I also have Puppy_4.3.1.sfs in a pubsave folder in that partition, and it was not displayed in the list. Does the boot manager only display sfs files located in the root directory of the home partition?

Update: Since I already had my savefile backed up in order to try the lupu 5.28 instant update 002, I decided to play with the 3.10 kernel sfs as well.

I moved the 310.sfs file, vmlinuz and initrd to the root directory of my home partition, and got the sfs bootmanager popup again. This time, as anticipated, it also showed the 310.sfs in the left column. I then "added" it to the right column, and clicked on OK. Xmanager then reset. Whether this had any effect or not, I couldn't tell. Is there a quick way to tell which kernel is running?

Will now reboot to see what happens.

Thank you.
I think you have been used Bootmanager to load xxx.SFS and you have saved pupsave file.
When you boot this distro the script load your pupsave file and find other sfs files in you "home" folder. so Bootmanager appear.
Note that puppy_XXX.sfs is main filesystem and it has been loaded into tmpfs. you should not load it twice. so it will appear in left column.

Afraid I'm not following your explanation.

After adding your kernel 31-_528 to the right column of the sfs boot manager., I rebooted, but noticed no difference. But presumably the changes to bootmanager are in the save file now.

Just now, after reading your reply, I looked for the tmpfs folder you mention above, but couldn't find it. Where would it be? I did look in the initrd folder, and there is the following line in Distro-specs:

DISTRO_KERNEL_PET='linux_kernel-2.6.33.2-tickless_smp_patched-L3.pet'

(I'm guessing this refers to the lupu multimedia instant update pet #2, that I installed last night).


but I see no reference to the 310_528 sfs, which suggests that the kernel 310 sfs wasn't loaded
I'm guessing that the sfs bootmanager can't work with a LiveCD boot, since the loader will always use the vmlinuz and intrd files it finds on the CD. Am I on the right track?

[James C]

Pretty boring day so I put together a Slacko-530-k-3.10 to play with.Working well...internet,sound and display all good on initial boot. PPM and Slickpet both working correctly.
Manually rebuilt the official Slacko iso instead of using Woof....seems to work better for me.

[ETP]

Wuxiandianzi
Lupu 528 with k3.1.0 is now my number one pup ! Tributes (with audio) can be found in my signature panel below.

Many thanks for this pup and the latest NVIDIA pet.