Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Sat 25 Oct 2014, 00:27
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
newest kernel 3.1.8 & 3.0.16 test on lupu528
Moderators: Flash, JohnMurga
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
Page 8 of 10 Posts_count   Goto page: Previous 1, 2, 3, ..., 6, 7, 8, 9, 10 Next
Author Message
otropogo


Joined: 24 Oct 2009
Posts: 702
Location: Southern Rocky Mt. Trench

PostPosted: Wed 02 Nov 2011, 23:06    Post_subject: Re: re  

wuxiandianzi wrote:
calexand wrote:
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.

_________________
otropogo@gmail.com facebook.com/otropogo
Back to top
View user's profile Send_private_message Visit_website 
wuxiandianzi


Joined: 28 Apr 2009
Posts: 134
Location: china

PostPosted: Thu 03 Nov 2011, 11:56    Post_subject: Re: re  

otropogo wrote:
wuxiandianzi wrote:
calexand wrote:
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!
Back to top
View user's profile Send_private_message 
jim3630


Joined: 13 Feb 2011
Posts: 792
Location: Northern Nevada

PostPosted: Thu 03 Nov 2011, 14:24    Post_subject:  

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?
brcm80211-firmware-0.0.1.pet
Description 
pet

 Download 
Filename  brcm80211-firmware-0.0.1.pet 
Filesize  219.62 KB 
Downloaded  206 Time(s) 
Back to top
View user's profile Send_private_message 
wuxiandianzi


Joined: 28 Apr 2009
Posts: 134
Location: china

PostPosted: Fri 04 Nov 2011, 01:27    Post_subject: bug-fix  

jim3630 wrote:
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.
fix-quickpet.pet
Description 
pet

 Download 
Filename  fix-quickpet.pet 
Filesize  11.12 KB 
Downloaded  215 Time(s) 

Edited_time_total
Back to top
View user's profile Send_private_message 
ETP


Joined: 19 Oct 2010
Posts: 552
Location: UK

PostPosted: Fri 04 Nov 2011, 05:26    Post_subject: k3.1.0--on--lupu_528  

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/843/dsc00077ub.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:
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.

_________________
Regards ETP
Accessibility Pups: -- Magoo -- The Pup With No Name -- MouseCam -- Obedient
Back to top
View user's profile Send_private_message 
wuxiandianzi


Joined: 28 Apr 2009
Posts: 134
Location: china

PostPosted: Fri 04 Nov 2011, 05:46    Post_subject: Re: k3.1.0--on--lupu_528  

ETP wrote:
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/843/dsc00077ub.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:
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.

Surprised
I am very very very very sorry.
I can not open your URL~!
Back to top
View user's profile Send_private_message 
Ray MK


Joined: 05 Feb 2008
Posts: 765
Location: UK

PostPosted: Fri 04 Nov 2011, 05:57    Post_subject:  

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
Back to top
View user's profile Send_private_message 
ETP


Joined: 19 Oct 2010
Posts: 552
Location: UK

PostPosted: Fri 04 Nov 2011, 06:13    Post_subject: Post subject: Re: k3.1.0--on--lupu_528  

wuxiandianzi wrote:
I am very very very very sorry.
I can not open your URL~!
screenshot.39.png
 Description   
 Filesize   367.53 KB
 Viewed   1028 Time(s)

screenshot.39.png


_________________
Regards ETP
Accessibility Pups: -- Magoo -- The Pup With No Name -- MouseCam -- Obedient
Back to top
View user's profile Send_private_message 
wuxiandianzi


Joined: 28 Apr 2009
Posts: 134
Location: china

PostPosted: Fri 04 Nov 2011, 06:30    Post_subject: Re: Post subject: Re: k3.1.0--on--lupu_528  

Wo ........... Shocked

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!
Back to top
View user's profile Send_private_message 
jim3630


Joined: 13 Feb 2011
Posts: 792
Location: Northern Nevada

PostPosted: Fri 04 Nov 2011, 12:40    Post_subject: Re: bug-fix  

wuxiandianzi wrote:

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?
Back to top
View user's profile Send_private_message 
otropogo


Joined: 24 Oct 2009
Posts: 702
Location: Southern Rocky Mt. Trench

PostPosted: Fri 04 Nov 2011, 14:25    Post_subject: calling and using Puppy bootmanager  

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.

_________________
otropogo@gmail.com facebook.com/otropogo

Edited_time_total
Back to top
View user's profile Send_private_message Visit_website 
ETP


Joined: 19 Oct 2010
Posts: 552
Location: UK

PostPosted: Fri 04 Nov 2011, 14:40    Post_subject: k3.1.0--on--lupu_528  

wuxiandianzi wrote:

Quote:
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”
“remove disk and press any key to reboot” then upon pressing
“disk boot failure insert system disk and press enter” …. Pressed enter and returned to syslinux prompt.

Given that 528 k3.0.7 and Slacko5.3_k3.0.8 both work on this same stick with syslinux 4.04 I doubt whether this is hardware related. My best guess is that 3.1.0 does not recognise syslinux as a valid boot loader.

What is now needed, is for someone else to test a FAT32 stick with k3.1.0--on--lupu_528 with different hardware to eliminate a bios or video card issue.
pup-sysinfo.zip
Description 
zip

 Download 
Filename  pup-sysinfo.zip 
Filesize  2.05 KB 
Downloaded  287 Time(s) 
hardinfo_report.zip
Description 
zip

 Download 
Filename  hardinfo_report.zip 
Filesize  6.32 KB 
Downloaded  142 Time(s) 

_________________
Regards ETP
Accessibility Pups: -- Magoo -- The Pup With No Name -- MouseCam -- Obedient
Back to top
View user's profile Send_private_message 
puppyluvr


Joined: 06 Jan 2008
Posts: 3213
Location: Chickasha Oklahoma

PostPosted: Fri 04 Nov 2011, 18:14    Post_subject:  

Very Happy 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...

_________________
Close the Windows, and open your eyes, to a whole new world
http://puppylinuxstuff.meownplanet.net/puppyluvr/
Puppy Linux Users Group on Facebook

Puppy since 2.15CE...
Back to top
View user's profile Send_private_message Visit_website 
ETP


Joined: 19 Oct 2010
Posts: 552
Location: UK

PostPosted: Sat 05 Nov 2011, 07:29    Post_subject: k3.1.0--on--lupu_528  

Wuxiandianzi

Syslinux booting problem solved. Very Happy Very Happy Very Happy

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”!

Renaming vmlinuz-3.1.0 to vmlinuz-3.1 cures the problem. The syslinux stanza becomes:
Code:
LABEL 528310
MENU LABEL Lupu Pup 528k310  03/11/11
KERNEL /p528310/vmlinuz-3.1
APPEND initrd=/p528310/initrd-3.1.0.gz pmedia=usbflash pdev1=sdc1 psubdir=p528310


Kernel development is ahead of boot-loader development and other loaders may also be effected if anything is appended to vmlinuz or initrd.

_________________
Regards ETP
Accessibility Pups: -- Magoo -- The Pup With No Name -- MouseCam -- Obedient
Back to top
View user's profile Send_private_message 
wuxiandianzi


Joined: 28 Apr 2009
Posts: 134
Location: china

PostPosted: Sat 05 Nov 2011, 07:59    Post_subject: Re: k3.1.0--on--lupu_528  

ETP wrote:
Wuxiandianzi

Syslinux booting problem solved. Very Happy Very Happy Very Happy

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”!

Renaming vmlinuz-3.1.0 to vmlinuz-3.1 cures the problem. The syslinux stanza becomes:
Code:
LABEL 528310
MENU LABEL Lupu Pup 528k310  03/11/11
KERNEL /p528310/vmlinuz-3.1
APPEND initrd=/p528310/initrd-3.1.0.gz pmedia=usbflash pdev1=sdc1 psubdir=p528310


Kernel development is ahead of boot-loader development and other loaders may also be effected if anything is appended to vmlinuz or initrd.


Congratulations to you! Smile Smile Smile
Back to top
View user's profile Send_private_message 
Display_posts:   Sort by:   
Page 8 of 10 Posts_count   Goto page: Previous 1, 2, 3, ..., 6, 7, 8, 9, 10 Next
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
 Forum index » Advanced Topics » Puppy Projects
Jump to:  

Rules_post_cannot
Rules_reply_cannot
Rules_edit_cannot
Rules_delete_cannot
Rules_vote_cannot
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1141s ][ Queries: 13 (0.0063s) ][ GZIP on ]