Lucid Puppy 5.2 Official Release JAN 5 2011

[playdayz]

Here is a nightly build of Chromium 10 from today JAN 06.

http://distro.ibiblio.org/pub/linux/dis ... -Lucid.pet[/url]

seems to install but doesn't start Is there something else I need to install?

Open a terminal and enter

Code: Select all

# /usr/lib/chrome-linux/chrome

and see what it says. It might not run on certain processors.

[playdayz]

It is listing 2 lupu-save.2fs files,which are the same, and I only have 1 save file on the system. How can I fix this so I don't have to choose during bootup? This a frugal install using grub4dos,

Perhaps it is a grub4dos issue. You might try that thread.
http://www.murga-linux.com/puppy/viewto ... 01&t=62566

[mikeslr]

No biggie. But Opening pfind also opens fbpanel configuration. This is a fresh-install, including a new SaveFile.
Per my prior posts, you might rightly guess that I've set up internet, changed the Wallpaper, and used fbpanel configuration to reconfigure the launcher's displayed. (Added mtpaintsnapshot.sh, and removed "Select default browser.") If you've followed DaveS' thread regarding Opera_mnt_home and Opera_extra_distros, I installed the later (having already installed the former on another Puplet) and also wrote desktop file & created symlink to use his FoxyFun pet (firefox from mnt/home installed in another Puplet) from Lucid 520.
Discussiom & links on this thread:
http://www.murga-linux.com/puppy/viewtopic.php?t=63393
None of the foregoing should have altered the relationship between pfind and fbpanel configuration.

mikeslr

[Dave_B]

I have a full install of Lucid Puppy 5.2 on my Compaq n410c and it works great - I haven't found anything to complain about (and I've looked). Lots of things fixed!

Do you have an internet keyboard? Are your sound keys working?

Yes, I have an internet keyboard and no, the volume keys do not work. Neither do the volume control buttons on the front edge of the laptop. I have always used the volume control on the task bar and Retrovol when needed, so I don't miss the key/button controls.
Dave

Compaq N410c 1.2 GHz PIII, 1gig ram, dinky hard drive.

[Jades]

Just a quick note to let say that I've managed to successfully upgrade that lupusave I was having problems with on Merlin (Pentium D) earlier from 511 to 520. Haven't encountered any problems so far.

[Lobster]

Open a terminal and enter

Code: Select all

# /usr/lib/chrome-linux/chrome

and see what it says. It might not run on certain processors

Once the pet is set up
the browse icon tries to activate chrome-linux
and not the above which is the correct reference
Change the icon parameters by right clicking
and Chromium works (for me anyways)

[eztuxer]

Lucid Puppy uses Openbox as default window manager(':!:')(':o')
Now you tell me. So I've been using Openbox for days and didn't know it.
Well, now I am impressed.(':D'), This may be the best Puppy, ever.

I'll go back and mark by "problems" solved.(':oops:')

Same goes for me. lol

[BHINTZ]

I am able to put my laptop (dell latitude d410) into suspend, but must manually reestablish the wireless internet connection upon waking. I must use the network wizard as SNS does not connect. The necessary data is stored, but I must load it and go through to basic routine. I have installed the acpitool pet and made a shortcut suspend icon.

Fluppy wakes up and automatically connects, but I don't know how to use that as a model to set up 5.2.

Any help would be appreciated. Everything else has worked like a charm including VirtualBox 4.0.

[Lobster]

and Chromium works (for me anyways)

or not.

There I was changing settings and was pleased with having changed the fonts
(it is hidden beyond beyond in a scroll bar access point) when Google Chrome crashed.
Crashed and took the whole system with it. Crashed and gave me a Black screen of Death.
Now Google make big of the fact that if a process in Chrome goes down it does not effect the whole system. You did bad to my Puppy!
I guess that crash protection applies only to browsing. Handle with care. Google did evil to me.

Apart from that I was very impressed with the new Chrome nightly release. Thanks for providing the pet.

Chrome error reporting
http://code.google.com/p/chromium/issues/entry

[bigpup]

and Chromium works (for me anyways)

or not.

There I was changing settings and was pleased with having changed the fonts
(it is hidden beyond beyond in a scroll bar access point) when Google Chrome crashed.
Crashed and took the whole system with it. Crashed and gave me a Black screen of Death.
Now Google make big of the fact that if a process in Chrome goes down it does not effect the whole system. You did bad to my Puppy!
I guess that crash protection applies only to browsing. Handle with care. Google did evil to me.

Apart from that I was very impressed with the new Chrome nightly release. Thanks for providing the pet.

What do you expect from a nightly release. They are all Alpha or at best beta versions of the program. You are testing for them, so let them know about your issues.

[James C]

I also upgraded the frugal install on the P4 test box from 519 to 520, no problems. Everything appears to be working correctly.

[Lobster]

What do you expect from a nightly release. They are all Alpha or at best beta versions of the program. You are testing for them, so let them know about your issues.

I expect no evil towards Puppys
Have let them know . . . tried to keep my issues out of the report . . .
http://code.google.com/p/chromium/issue ... l?id=68831

Thanks guys

Puppy Linux
Do know evil? Do not 'know evil'. Do good.

[ilanrab]

This ***IS*** the official release of Lucid 5.2. It is the exact same as the Lupu-520 RC so if you downloaded that you already have it

Congratulations to everyone, on a task well done! Puppy Lupu-520 has been released. Good work!

I found the 520RC version stable and ready to go. The installation of 520RC, in my case, involved:
- Copying the vmlinuz, initrd.gz, and lupu-520.sfs files to the 1st partition on the 16GB Flash drive; The drive whose installation I described in previous posts, here .
- I rebooted the flash drive based system, and it came up as expected.
- On shutdown I allowed the system to create a new save file, in the subdirectory on the 2nd partition of the flash drive. The save file sits alongside the 1st two save files that exist there already. I can use any one of the three, as required.

I booted this flash drive on three pieces of hardware: a Dell netbook (inspirion 1010), a Dell Desktop with 512MB RAM (DHP Optiplex GX270), and a Dell Latitude D400. Lupu-520RC ran just about perfectly well on all three pieces of H/W. The only exception was the .laptop; Dell Latitude D400. The muted volume issue was still there. The muted volume, on boot, was not a problem on the first two Dells, but it did show up on the laptop. Running "retroval" and changing the volume level, was the workaround for me.
In summary. For my situation this system was definitely ready to go, and its release earlier today, was right on the mark.

Congratulations, again.

Cheers,

[wuwei]

Great hand of applause to micko and his team.

Puppy 520 is a masterpiece.

This is obviously not only my opinion; www.murga-linux.com was not accessable yesterday afternoon probably due to a lot of traffic, and distrowatch has this to say for the last 7 days...

[James C]

I just did another full install of 520..... this time on the old P4 test box. Once again, no problems at all.
Installed Xorg-High, SeaMonkey 2.0.11, Chromium 7.0.517.44 and VLC....everything is working correctly.

[nooby]

I have had problem getting Lupu to boot reliably since many versions back.

I've tested different things to add to the kernel boot line in menu.lst

and now I think I have found one that do help.

rootdelay=8

I need to test more but what do you guys say. What does that actually do and would that help be have reliable boot of Lupu520?

[ICPUG]

Did a search nooby and found (paraphrased a bit):

The purpose of the rootdelay kernel parameter is to cause the kernel to delay for the specified number of seconds before mounting the root device. This allows slow devices to be discovered before the mount takes place. If the mount is attempted before the device is found then an error message results (unable to mount root file system).

This was found here
https://bugs.archlinux.org/task/10483

It seems to be a problem with usb devices on the Ubuntu forums.

[nooby]

I try to test now and then today and the following days.

The no boot are so unpredictable. Some days it almost never boot and on other times it boots on first or second or third try.

Could it have to do with which OS I used the day before?

Such should be lost when the RAM get out? What else can it be? I have a gut feeling that is some IRQ thing that goes bonk and that is random if it does or not due to two services competing to get that particular IRQ?

Sometimes it helps to add Debug to the kernel line as if that one makes a small delay so I thought the rootdelay=8 seconds would give it enough time to decide on what to do next. But I wish I could create some error message that could be interpreted, Now it just sit there and wait for something. Most likely it is some kernel panic because the only way to get out is to do hard reboot.

[sm6lod]

nooby,
FWIW. I have had problems with Reboot since I started to use Puppy. Nowdays I always shut down totally before I boot up again.

[tasmod]

An initrd.gz with a small line addition during startup that shows Version 5.2

Just replace the initrd.gz you already have.

Helps somewhat when testing various other versions as well.