Lucid Puppy 5.2.8 - Updated ISO Version 005 - APR 05 2012

A home for all kinds of Puppy related projects
Message
Author
gcmartin

#1546 Post by gcmartin »

@Playdayz you shared
TEASER
Is this a "pre-announcment"? or a reference to someone else's work (i'e' Pemasu)?
Anyway, looking forward ..... :D
______________________________________
Iguleder wrote:My advice to you, playdayz: make a x86_64 flavor of this kernel. :wink:

This has five benefits:
- Access to 4 GB (or more) RAM, without the PAE issues (e.g instability under certain circumstances).
- The ability to run x86_64 binaries (e.g compile x86_64 stuff from a chroot environment).
- The performance boost of 64-bit computing - e.g some heavy computations (such as compression) implemented in kernel mode are now faster.
- Same userland - no need to recompile anything or create a separate package repository, as with i486/i686 switching.
- Dual-kernel ISOs with two identical kernels - one for 64-bit machines and another for 32-bit ones - it's quite cool.
@Iguleder shares these great Benefits. LightHouse64 has demonstrated these.

There is one issue that I hope my statement clarifies. PAE doesn't have any more of an instability issue than "normal" or the "4GB only" 32bit kernels present. It, like the others 32bit mentioned, is stable.

The PROBLEM with PAE is that there are a very few CPUs manufactured by Intel and others which (for their cost considerations) did NOT include the PAE hardware. And, some BIOSes were also shipped with a settings that could also have impacted PAE use. But, for the most part, this is a ratity given the 15 years PAE has been built-into CPUs.

Thus, if you can, run 64bit! If you cannot, use 32bit PAE as it affords use of ALL of the RAM you can throw at it (assuming no CPU issues - which you will find out almost immediately), Lastly 32bit non-PAE runs just as fast (reviewing performance measurements already done by both vendors (intel and AMD) as well as independent test reports. PAE merely shines in Puppy which run RAM based because the filesystem is ALL of your RAM.

Hope this helps

User avatar
playdayz
Posts: 3799
Joined: Fri 25 Apr 2008, 18:57

#1547 Post by playdayz »

Downloaded vlc-1.1.7.-full-lucid52 from PPM.
It seems to work OK, but did get this message after the install check.
Problem?
I don't think so. Sometimes PPM misses dependencies that are really there. If it works it's OK. There is also a 1.1.10. This vlc 2.0 is for me working in quick testing -> http://www.murga-linux.com/puppy/viewtopic.php?t=76271

User avatar
rerwin
Posts: 2017
Joined: Wed 24 Aug 2005, 22:50
Location: Maine, USA

#1548 Post by rerwin »

jim3630 wrote:did fresh frugal instal lupu plus to same hp laptop.
wl recognized eth1 by sns but not able to make the connection.
connection wizard easily made connection on this troublesome
Broadcom Corporation BCM4313.
This is the opposite of yesterdays install lupulibre where
connection wizard failed and sns made the connection.
seems odd and cannot remember how prior install of lupu plus
went so attached file.
  • 1. Lupuplus has the older wl driver which uses eth1 and gives you trouble.
    2. With lupulibre, you installed the 2 packages that add support for both the old and a newer version of the wl driver (which appears to successfully support your device), but did not do that when you ran lupuplus.
The 2 packages fix the problem you are having. Please install the broadcom driver package I posted on page 100 and either of the "arch_update" packages I posted on pages 100 & 101, then try again. You should not see eth1, but only wlan0 as the wifi device.
Richard
Last edited by rerwin on Thu 12 Apr 2012, 22:42, edited 1 time in total.

User avatar
playdayz
Posts: 3799
Joined: Fri 25 Apr 2008, 18:57

#1549 Post by playdayz »

volhut, it would be a miracle if this updated Intel video driver for Lucid from Ubuntu Lucid Updates made any difference to Stellarium. You would need to restart the X-server after installing the pet.

User avatar
jim3630
Posts: 791
Joined: Mon 14 Feb 2011, 02:21
Location: Northern Nevada

#1550 Post by jim3630 »

rerwin wrote: Please install the broadcom driver package I posted on page 100 and either of the "arch_update" packages I posted on pages 100 & 101, then try again. You should not see eth1, but only wlan0 as the wifi device.
Richard
Richard thanks.

Volhout
Posts: 547
Joined: Sun 28 Dec 2008, 08:41

#1551 Post by Volhout »

playdayz wrote:volhut, it would be a miracle if this updated Intel video driver for Lucid from Ubuntu Lucid Updates made any difference to Stellarium. You would need to restart the X-server after installing the pet.
The intel driver did not fix it. I am going to read through Pesamu's advice first. But I am not sure if the problems I have relate to his work on Qt. Since it works on other hardware on LupuLibre, on Nvidia HW, Qt should not be the problem.

UPDATE: when I use Xvesa on 1024x768x24 the Stellarium 1.10.6 SFS works on my system. It is slow (graphics), but it works. Using Xorg on the same settings 1024x768x24 does not work, neither does the native setting for my system 1280x1024x24.
I did not know Xvesa supported OpenGL (via Xorg-High ?)

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

#1552 Post by James C »

playdayz wrote:TEASER

Don't know what will come of it, but it boots and connects, and reboots and creates and uses a pupsave.

Might as well give it a try, but I agree with Iguleder that x86_64 is the way of the future.

Iguleder wrote:My advice to you, playdayz: make a x86_64 flavor of this kernel. :wink:
It's most certainly possible and appears to work pretty darn well.
Attachments
Precise Puppy k-3.10 x86_64.png
(27.41 KiB) Downloaded 1072 times

User avatar
Aitch
Posts: 6518
Joined: Wed 04 Apr 2007, 15:57
Location: Chatham, Kent, UK

#1553 Post by Aitch »

Volhout

I had a box with brookdale 845G video which gave all sorts of problems
I think I cured it by adding mesa and going into bios and resetting the default video memory size to match the video...I got good speed and stability afterwards - though I also came across a lot of 'this patch isn't working' posts when searching....there were kernel problems too, apparently, so look for patches for your kernel

Aitch :)

User avatar
playdayz
Posts: 3799
Joined: Fri 25 Apr 2008, 18:57

#1554 Post by playdayz »

I agree with Iguleder that x86_64 is the way of the future.
I agree also, James C. But it won't be me who does it ;-) I am using the kernel from racy 5.3. One thing I am interested in is whether it makes a difference whether a kernel is built-in with Woof or added later manually. I am building it in with Woof.

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

#1555 Post by James C »

playdayz wrote: One thing I am interested in is whether it makes a difference whether a kernel is built-in with Woof or added later manually. I am building it in with Woof.
Got a feeling it'll go much smoother using Woof.... :)

Anyway, it'll give us a new release to experiment with.Might as well go for it.

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

#1556 Post by bigpup »

playdayz wrote:
I agree with Iguleder that x86_64 is the way of the future.
I agree also, James C. But it won't be me who does it ;-) I am using the kernel from racy 5.3. One thing I am interested in is whether it makes a difference whether a kernel is built-in with Woof or added later manually. I am building it in with Woof.
Playdayz,

Do not do it! In no way should you proceed! You have better things to do! What are you wasting your time for! Total wast! Who needs it! Who wants it! What are you thinking!

GOT YOU FIRED UP TO DO IT?
I HOPE SO!!!!!!!!! :D :D :D :D :D :D :D :D :D :D :D :D
PLEASE! PLEASE! PLEASE! PLEASE! :) :) :) :) :) :) :) :)
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
jim3630
Posts: 791
Joined: Mon 14 Feb 2011, 02:21
Location: Northern Nevada

#1557 Post by jim3630 »

bigpup wrote:
playdayz wrote:
I agree with Iguleder that x86_64 is the way of the future.
I agree also, James C. But it won't be me who does it ;-) I am using the kernel from racy 5.3. One thing I am interested in is whether it makes a difference whether a kernel is built-in with Woof or added later manually. I am building it in with Woof.
Playdayz,

Do not do it! In no way should you proceed! You have better things to do! What are you wasting your time for! Total wast! Who needs it! Who wants it! What are you thinking!

GOT YOU FIRED UP TO DO IT?
I HOPE SO!!!!!!!!! :D :D :D :D :D :D :D :D :D :D :D :D
PLEASE! PLEASE! PLEASE! PLEASE! :) :) :) :) :) :) :) :)
1+

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

#1558 Post by bigpup »

playdayz wrote:
Downloaded vlc-1.1.7.-full-lucid52 from PPM.
It seems to work OK, but did get this message after the install check.
Problem?
I don't think so. Sometimes PPM misses dependencies that are really there. If it works it's OK. There is also a 1.1.10. This vlc 2.0 is for me working in quick testing -> http://www.murga-linux.com/puppy/viewtopic.php?t=76271
If I run VLC 1.1.7 from the console. I also get these error messages:
# vlc
VLC media player 1.1.7 The Luggage (revision exported)
Blocked: call to unsetenv("DBUS_ACTIVATION_ADDRESS")
Blocked: call to unsetenv("DBUS_ACTIVATION_BUS_TYPE")
[0x8103834] main interface error: no suitable interface module
[0x8067564] main libvlc error: interface "globalhotkeys,none" initialization failed
[0x8067564] main libvlc: Pokretanje VLC-a s polaznim su
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

#1559 Post by bigpup »

There is this warning in the topic for VLC 2.0.0.sfs:
EDIT: the vlc sfs also works in the new Slacko beta but if are using
qt-473 in slacko the qt-480 in the vlc sfs will clobber it and the
programs in slacko that used qt-473 won't work any longer.
Is this something to worry about if using in Lucid 5.2.8-005?
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
playdayz
Posts: 3799
Joined: Fri 25 Apr 2008, 18:57

#1560 Post by playdayz »

EDIT: the vlc sfs also works in the new Slacko beta but if are using
qt-473 in slacko the qt-480 in the vlc sfs will clobber it and the
programs in slacko that used qt-473 won't work any longer.

Is this something to worry about if using in Lucid 5.2.8-005?
Not really. Lucid does not have a separate Qt package like Slacko does.

User avatar
chrome307
Posts: 708
Joined: Thu 15 Jan 2009, 11:00

#1561 Post by chrome307 »

Thanks to all for continuing to support this Puppy :)

futwerk
Posts: 397
Joined: Sat 07 May 2011, 22:04

#1562 Post by futwerk »

no problem, Playdayz, here is the new version. A few more new backgrounds.
Attachments
pupap12,2x1b.png
http://www.mediafire.com/?7v1msw26s6chb
(89.62 KiB) Downloaded 2109 times
pupap12,2x1a.png
http://www.mediafire.com/?7v1msw26s6chb
(88.09 KiB) Downloaded 1900 times
pupap12,2x1.png
http://www.mediafire.com/?7v1msw26s6chb
(85.83 KiB) Downloaded 2074 times
pupap12,2c.png
http://www.mediafire.com/?7v1msw26s6chb
(75.34 KiB) Downloaded 1873 times
pupap12,2b.png
http://www.mediafire.com/?7v1msw26s6chb
(76.89 KiB) Downloaded 2063 times
pupap12,2.png
http://www.mediafire.com/?7v1msw26s6chb
(72.46 KiB) Downloaded 1883 times
pupse26,1cx2.png
http://www.mediafire.com/?7v1msw26s6chb
(186.96 KiB) Downloaded 1887 times

User avatar
prehistoric
Posts: 1744
Joined: Tue 23 Oct 2007, 17:34

#1563 Post by prehistoric »

It may be late in the game to report this, but I've tested 5.2.8.005 on a number of my collected computers. (An unkind acquaintance with an aviation background refers to them as "hanger queens".) It worked well on virtually all, but I got diverted into chasing problems with Fatdog 5.21 and video drivers before I came back here. My concerns are not with this release, but with the future.

Lucid Puppy 5.2.8.005 works amazingly well, but I keep running into problems with embedded graphics chips and exits from the X window system on some machines. If someone has added off-board video cards, the console video may be on the wrong device. Other problems are just plain weird, like video which works with 4 GB of RAM, but fails with 8 GB, a sign of timing problems in shared video memory. Such problems have been around Linux machines from the beginning, and I'm not demanding that every video problem be solved. I'm also not terribly interested in solutions like magic keystrokes to switch virtual consoles, etc. (as with Gentoo). Even if I can remember them when I know that I need them newbies are helpless in these circumstances. This is not simply a problem with Lupu. I've had some very frustrating experiences with Ubuntu getting me to the point where I can almost use it, then going to video which prevents me from doing anything.

First, could we have a simple option to restrict video to something which won't cause unintelligible video on exit long enough to get set up? Second, when we have the system initially coming up with some kind of video able to display a desktop, could we use that to set up a save file before we exit? I've been doing that by copying a save file from another installation, then mounting it and deleting everything inside except the lost+found folder. (I'm using an ext3 save file.) This is found on shutdown, and current contents are saved, even if the console video is foobar. If no such file is created, everything works as intended via the console, provided the console output is intelligible. If an empty save file is created, the system saves on shutdown, and comes up ready to continue configuration, even if you can't see what it does on shutdown.

User avatar
darkcity
Posts: 2534
Joined: Sun 23 May 2010, 19:16
Location: near here
Contact:

#1564 Post by darkcity »

A couple of people have reported sound problems with 5.28 using intel chipsets and module snd_hda_intel

here is the thread if anybody knows something about this-
http://murga-linux.com/puppy/viewtopic.php?t=74392

humblesoul
Posts: 32
Joined: Fri 06 Apr 2012, 20:19

#1565 Post by humblesoul »

Re: video in 528

Same problem on two different laptops. Inititial boot looks great but first request to restart x always borks it. Always goes to xorg wizard, probe fails as does choose, even vesa is iffy, if x returns at all it's like looking at the screen through vaseline with no success in trying to return it to it's initial glory.

Have avoided this by declining the initial request to restart x and going about my business. Restarting x later causes no such problems, even before creating a save file.

What is the default video driver it boots to?

This laptop: Generic PnP Monitor (1366x768@60Hz)
Mobile Intel(R) 4 Series Express Chipset Family
Mobile Intel(R) 4 Series Express Chipset Family

Can't remember the other, sorry. This is a dell, the other an older compaq. Not a complaint as I'm working around it, just a heads up.

Post Reply