(old)Puppy Linux Discussion Forum

I used the delta to create 5406.iso then burned the iso to a dvd.
Booted dvd and did a frugal install to the hard drive with universal
installer.
Booted up frugal install and installed kdegames with ppm, works.
Installed devx,kernelsource and compiled proprietary nvidia driver.
Installed pets and an sfs, chromium says flash outdated,fixed with
getflash.
Copied pvr firmware to /lib/firmware.
Several reboots along the way.
Ran remaster live cd, then burned the remaster.iso to a dvd.
Booted up remastered live dvd, here I am.

video-info-glx 1.5.1 Sun3Mar 2013 on Slacko Puppy 5.4.0.6 Linux3.4.17-PAE i686
0.0 VGA compatible controller: nVidia CorporationG84[GeForce 8600 GT](rev a1)
oem: NVIDIA
product: G84 Board - p402h00 Chip Rev
X Server: Xorg Driver: nvidia
X.Org version: 1.12.3
dimensions: 1440x900 pixels (373x231 millimeters)
depth of root window: 24 planes
direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce 8600 GT/PCIe/SSE2
OpenGL version string: 3.3.0 NVIDIA 310.32
Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
Core 0: @1603 1: @1603 2: @1603 3: @1603 MHz
# glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
302 frames in 5.0 seconds = 60.311 FPS
300 frames in 5.0 seconds = 59.918 FPS
300 frames in 5.0 seconds = 59.918 FPS

Everything is working well,chromium doesn't give flash outdated
warning,kdegames works, life is good

Hi Mick

Notice that the Broadcom WL driver is no longer included in Slacko 5.4.0.6 - is this a deliberate omission??

It works fine if it is loaded....

Cheers
peebee

most likely it is the famous glitch in the old mouse
that produce an error. So forget all about it sorry

peebee wrote:Hi Mick

Notice that the Broadcom WL driver is no longer included in Slacko 5.4.0.6 - is this a deliberate omission??

It works fine if it is loaded....

Cheers
peebee

Mistake .. only affects the 4G version. Uploading a new delta shortly.. It will be from 5.4.0.5 >> 5.4.0.6.1

Apologies for inconvenience but I had major corruption of my woof tree on a woof upgrade. No idea of the cause but a downgrade of woof, then a reupgrade fixed it.

Hey Mick

At last I managed to set up GRPS connection via my old SE k750i (connected via USB cable), because I wanted to test network_tray's ability of changing tray icon.
Spent some time trying different combinations, restarting X and digging inside modemiconset* script, until I downloaded network_tray source code and looking into it I got "feeling" (still don't know C) that probably it somehow depends on Frisbee.
So in the end I launched Frisbee and indeed - the icon has changed instantly! (screenshot)
And it looks really cool!
I just wonder, or rather do not fully understand why there's a need to launch Frisbee, to enjoy that feature..?
There's also possibility that I'm doing something wrong - I'm not a "network guy" btw.

Ah, the "splash-screen mess in chars" somehow survived and it's still there.

* modemiconset - I don't know if that really matters, but while playing with it I found that if the script is called without arguments, it spits out "[: too many arguments" error.
It's because my number in /etc/wvdial.conf is *99# - wrapping all "$FIRSTDIGIT" vars in double quotes has fixed that "problem".

Greetings!

***************************************

Delta for the 4G version with wl bug is reuploaded!

See main post

***************************************

SFR

I put in isolinux.bin from lupu 5.2.5. I don't have later atm, but I could use the one from my Slackware install, it is likely much later. The one I used is attached. It's real gz .

I agree it would be a nice feature if the icons switching to phones for the net tray icon would be nice accross the board. It's a work in progress but likely not to make final.

Hi Mick,

Playing with your latest PAE version, works great on my hardware.

Thanks,
Jim

Thanks Jim.

-----

Here is isolinux.bin from my slackware install.

Hi Mick,

I tried the non pae on my Dell D430,

I installed three different wine and in all of them I had one program theWord that would not minimize it would just reopen right away and the other program BibleAnalyzer would minimize and could not reopen it at all.

oldyeller wrote:Hi Mick,

I tried the non pae on my Dell D430,

I installed three different wine and in all of them I had one program theWord that would not minimize it would just reopen right away and the other program BibleAnalyzer would minimize and could not reopen it at all.

Did you try the one from PPM?

01micko wrote:

oldyeller wrote:Hi Mick,

I tried the non pae on my Dell D430,

I installed three different wine and in all of them I had one program theWord that would not minimize it would just reopen right away and the other program BibleAnalyzer would minimize and could not reopen it at all.

Did you try the one from PPM?

Sorry about that I guess I should have said so right off the bat, But yes I did,

1.4.1 and 1.5.20

01micko wrote: I put in isolinux.bin from lupu 5.2.5. I don't have later atm, but I could use the one from my Slackware install, it is likely much later. The one I used is attached.

Hmm, the one you attached is the "bug-free" version indeed (ISOLINUX 4.03, same as in Lupu-528.005).
But in the ISO I have built from 5.4.0.5 + delta is the old version. That's odd...

The one from Slackware is even newer (4.05) and it works too.

Greetings!

SFR, yes it is weird.. in my woof tree is the new one, but the old one did get used! I'll check the build script, maybe it is stored elsewhere after initial run of woof.

--- haha... look at this
but.. in 3builddistro...
So now i know..

Hi Mick,

I'm not having the problem with the PAE version using Wine along with BibleAnalyzer and eSword that oldyeller reported using the non-PAE version. However, theWord does have the problem. Also, Bibletime is working fine.

Cheers,
Jim

Jim and oldyeller.

It is possible that it's a JWM issue. scsijon reckons that 692 (that is used in this version) is unstable.

You can try 691 attached.

01micko wrote:Jim and oldyeller.

It is possible that it's a JWM issue. scsijon reckons that 692 (that is used in this version) is unstable.

You can try 691 attached.

Hi Mick tried 691 with wine from ppm and still get the same results as before.

Manual upgrade from 5.4.0.5 to 5.4.0.6 on the old P4 test box. Everything looking good so far.

# report-video
VIDEO REPORT: Slacko Puppy, version 5.4.0.6

Chip description:
VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02)

Requested by /etc/X11/xorg.conf:
Resolution (widthxheight, in pixels): 1024x768
Depth (bits, or planes): 24
Modules requested to be loaded: dbe

Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): intel
Loaded modules: dbe dri dri2 extmod fb glx kbd mouse record

Actual rendering on monitor:
Resolution: 1024x768 pixels (270x203 millimeters)
Depth: 24 planes

...the above also recorded in /tmp/report-video
# glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
378 frames in 5.0 seconds = 75.464 FPS
376 frames in 5.0 seconds = 75.144 FPS
376 frames in 5.0 seconds = 75.143 FPS
376 frames in 5.0 seconds = 75.144 FPS
376 frames in 5.0 seconds = 75.143 FPS
376 frames in 5.0 seconds = 75.143 FPS

-Computer-
Processor : Intel(R) Pentium(R) 4 CPU 2.80GHz
Memory : 2592MB (213MB used)
Machine Type : Physical machine
Operating System : Slacko Puppy - 5.4.0.6
User Name : root (root)
Date/Time : Sun 03 Mar 2013 11:19:59 PM CST
-Display-
Resolution : 1024x768 pixels
OpenGL Renderer : Mesa DRI Intel(R) 865G x86/MMX/SSE2
X11 Vendor : The X.Org Foundation
-Audio Devices-
Audio Adapter : ICH4 - Intel ICH5
-Input Devices--Computer-
Processor : Intel(R) Pentium(R) 4 CPU 2.80GHz
Memory : 2592MB (213MB used)
Machine Type : Physical machine
Operating System : Slacko Puppy - 5.4.0.6
User Name : root (root)
Date/Time : Sun 03 Mar 2013 11:19:59 PM CST
-Display-
Resolution : 1024x768 pixels
OpenGL Renderer : Mesa DRI Intel(R) 865G x86/MMX/SSE2
X11 Vendor : The X.Org Foundation
-Audio Devices-
Audio Adapter : ICH4 - Intel ICH5

Good evening/morning, mick!
How many back issues will the present delta fix (just one, I suspect?).
Have loaded an earlier 5.3 release onto a friend's laptop to dual boot. What are the chances of a successful update by re-installing as a FULL. pfix= ram, etc, etc?

Evening here

I would back up the personal data and do a clean install, after testing pfix=ram of course. Because of Slackware moving to "kmod" (module-init-tools has not been developed in 3 years) for kernel module loading there is a rocky road to tread in upgrading from 5.3 to 5.4 (soon to be 5.5). I'll do a delta from 5.4.0.5 when ready.

All that said, if you have backed up there is no harm in trying but first read THIS page. There will be a new page with even more comprehensive tips and work arounds for known issues on release of 5.5.

Thanks for your speedy response, mick! I guess this information may be of assistance to quite a few folks, maybe worth repeating de temps en temps?
Your notes in your link are especially helpful regarding wireless issues; have had 'no connect' and' disappearing connection' features crop up frequently. Not saving the WPA Key can also be distracting, requiring finding the router(!) and up-ending it to read the key.
Personally, I took the precaution of lifting the floorboards during my last move and hard-wiring networking throughout. I also set my Key to something more memorable than the one supplied, but editing the router config is beyond most regular folks and can cause havoc if they hit the wrong key...