(old)Puppy Linux Discussion Forum

Manual frugal install on the trusty old Athlon XP box....... no problems. Ext3 savefile on an Ext3 partition.

# report-video
Report Video 1.4 - Thu 31 Jan 2013 on Slacko Puppy 5.4.0.1 - Linux 3.0.60-4g i686

Chip description:
0.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev c1)
oem: NVidia
product: NV18 () Board Chip Rev A2

X Server: Xorg Driver used: nouveau

X.Org version: 1.12.3
dimensions: 1440x900 pixels (380x238 millimeters)
depth of root window: 24 planes

...the above also recorded in /tmp/root/ as report-video,
and archived with xorg.conf and Xorg.0.log as report-video-full.gz
# glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
1130 frames in 5.0 seconds = 225.837 FPS
1347 frames in 5.0 seconds = 269.217 FPS
1515 frames in 5.0 seconds = 302.738 FPS
1895 frames in 5.0 seconds = 378.990 FPS
1897 frames in 5.0 seconds = 379.394 FPS

More after further testing......

Did manual frugal install on Dell D430 with Toshiba usb hd

everything doing good so far gtkdialog is working great installed Manna and wbar

Report Vedio

Report Video 1.4 - Thu 31 Jan 2013 on Slacko Puppy 5.4.0.1 - Linux 3.0.60-4g i686

Chip description:
2.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)
oem: Intel(r) 82945GM Chipset Family Graphics Chip Accelerated VGA BIOS
product: Intel(r) 82945GM Chipset Family Graphics Controller Hardware Version 0.0

X Server: Xorg Driver used: intel

X.Org version: 1.12.3
dimensions: 1024x768 pixels (270x203 millimeters)
depth of root window: 24 planes

Cheers

James C wrote:Guess I'm lucky to have not experienced the "BUG" but I'll test for other things.

oldyeller wrote: have not seen the "BUG" here either maybe it is because of my anti-bug repellent

Ah, you lucky fellows - the BUG is cunning, elusive beast!
So far, only me had "privilege" to see its true, hideous face and I'll never be the same.
Hides in NTFS, doesn't like syncing.


@Mick:

Changelog wrote:bugfix perms on /tmp were 777 not 1777, SFR, master_wrong

Are you sure the fix is included in 5.4.0.1?
Looks the same as in 5.4:
- pristine boot: 777
- pmedia=ataflash: 777
- pmedia=atahd: 1777
BTW, does anyone can confirm this, because somehow I'm loosing faith in credibility of my experiences.

ROX Audio-CD fix works great.

Thanks & Greetings!

SFR wrote:@Mick:

Changelog wrote:bugfix perms on /tmp were 777 not 1777, SFR, master_wrong

Are you sure the fix is included in 5.4.0.1?
Looks the same as in 5.4:
- pristine boot: 777
- pmedia=ataflash: 777
- pmedia=atahd: 1777
BTW, does anyone can confirm this, because somehow I'm loosing faith in credibility of my experiences.

Hmmm... what I thought was the fix mustn't be! I'll have another go for next version. Thanks!

EDIT... no it's a woof thing! I think when you first boot one of the init scripts changes it to 1777, but in woof/3builddistro I came across this line (@line 2137)I'll report to Barry to change it to 1777.

Purely for testing purposes, booting live cd....ext3 savefile and main Slacko sfs on NTFS hdd partition.No problems yet.

# report-video
Report Video 1.4 - Thu 31 Jan 2013 on Slacko Puppy 5.4.0.1 - Linux 3.0.60-4g i686

Chip description:
d.0 VGA compatible controller: nVidia Corporation C61 [GeForce 7025 / nForce 630a] (rev a2)
oem: NVIDIA
product: MCP61 - mcp61-86 Chip Rev

X Server: Xorg Driver used: nouveau

X.Org version: 1.12.3
dimensions: 1366x768 pixels (361x203 millimeters)
depth of root window: 24 planes

...the above also recorded in /tmp/root/ as report-video,
and archived with xorg.conf and Xorg.0.log as report-video-full.gz
# glxgears
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 55
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 56
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 59
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 58
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
5220 frames in 5.0 seconds = 1043.875 FPS
5793 frames in 5.0 seconds = 1158.582 FPS
5687 frames in 5.0 seconds = 1137.099 FPS
5715 frames in 5.0 seconds = 1142.843 FPS
5665 frames in 5.0 seconds = 1133.000 FPS

-Computer-
Processor : 4x AMD Athlon(tm) II X4 620 Processor
Memory : 2854MB (454MB used)
Machine Type : Physical machine
Operating System : Puppy Linux
User Name : root (root)
Date/Time : Thu Jan 31 17:24:43 2013
-Display-
Resolution : 1366x768 pixels
OpenGL Renderer : Gallium 0.4 on NV4C
X11 Vendor : The X.Org Foundation
-Audio Devices-
Audio Adapter : HDA-Intel - HDA NVidia

Here is a table of the IO Bug so far..

IO Bug at google docs

Hi 01micko. I 've done the first test on a machine with an AMD Athlon 1.2 GHz, 512 MB RAM, ATI Rage 128 graphic card, Intergraph 19sd5 screen. Usually running live on different machines, I always check to use the video wizard. The test started bad, it would not start X. I followed the options in the video wizard, and ended up in a shell with xorg.conf: two active 'Devices' are listed, Card1 with driver 'r128', and Card2 with driver 'vesa'. Last line gives PuppyHardwareProfile=ATI_RAGE12819sd95, so 'r128' should be the correct driver.
Back in the ordinary wizard window:

• Resolution: x pixels
• Horizontal frquency: KHz
• Refresh frequency: Hz
• Video driver: modesetting

After choosing 'vesa' instead, I was sent back to the setup page, set 1280x1024, chose 'test', and got a dialog window that told me X was working, entered 'xwin', and got a window. Incorrect size, does not fill the screen, way over past the left side. Running PupControl-Settings-Basic Settings, I was told that 'vesa' is running, and I should run the Video Wizard to find an xorg driver instead! Instead I rebooted, and started without choosing the video wizard option, set 1280x1024, and it opened normally, but with a window that does not fill the screen, and is off center. After running the xorgwizard several times and trying all the ATI drivers listed, it suddenly loaded a window normally, with the r128 driver. My ZTE MF636 USB modem did not connect. There is of course the possibility that the machine is not 100%, but the ordinary Slacko-5.4 started without any issues on this machine. I'll set up some other machines for testing.
BTW: 'The Focus Model (sloppy or click)' setting is listed twice in the ~/.JWMRC, I definitely hate the new jwm window buttons cursors, and the option to set larger buttons is missing in jwm-config.

tallboy

Hello tallboy,

Thanks for testing. Part of your X problems is my fault. I should have left the "modesetting" driver in the alternate location so it doesn't try to load. It does conflict with some drivers. Anyway, that was almost certainly a typo because I have been through that routine many many times and know I didn't forget it. This kernel is only temporary too as I reckon the kernel video drivers are better in k3.2x and 3.4x.

As for jwm cursors, I'll see if there is some configuration to turn therm off. I don't think it matters about 2 focus entries in JWMRC, this file is not read by jwm but used to generate the ~/.jwmrc. As long as jwm -p isn't returning anything we are good. I'll address the button sizing, it is now dependant on the height of the title bar.

Cheers

I did a no, no a my computer Dell D430 today and made a NTFS partition and did a frugal install of slacko 5.4.0.1.

created a savefile with a ext2 file in it and increased by 8gb Installed wbar and Manna along with wine and BibleAnaylzer. rebooted and twice and everything is still working so far.

I made a button on jwm taskbar works,

The only thing I have ever notice with slacko and any puppy besides lupu is that when I use a different resolution so that things are bigger I only get the screen in a smaller window and does not fill the screeen. I don't know if this would be a bug or not, but I don't think so maybe a different driver.

Report Video 1.4 - Fri 1 Feb 2013 on Slacko Puppy 5.4.0.1 - Linux 3.0.60-4g i686

Chip description:
2.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)
oem: Intel(r) 82945GM Chipset Family Graphics Chip Accelerated VGA BIOS
product: Intel(r) 82945GM Chipset Family Graphics Controller Hardware Version 0.0

X Server: Xorg Driver used: intel
X.Org version: 1.12.3
dimensions: 1024x768 pixels (270x203 millimeters)
depth of root window: 24 planes

Cheers

Been running both installs periodically today....... no problems evident yet.
Nice wallpaper too.

I have downloaded and used the Firefox version of 5.4. Both the Firefox 17.0 and the update 18.0.1 behave strangely, so I would like to use a Seamonkey. The ones listed in the original ppm are v.2.12.1 at 88 Mb, and v.2.14 at 90 Mb, both from the slackware-14.0-official repo.
Is there a smaller puppy version suitable for Slacko 5.4? I only need the browser. If not, will there be one in the next version? Or a Surfer? I don't like Opera, but I'll burn a CD now to try it.

tallboy

tallboy

It is recommended to get seamonkey from the updates manager (see Setup > System menu). PPM quotes the size uncompressed, it's about 23M download. I don't compile it any more as it's too big for me. That's what swayed me to Opera, only 13M pet. You can update the database in PPM and then updates manager shows the very latest from slackware's changelog, bug fixes and security fixes. It is still under development and soon I hope to add a button to update the database form there. Seamonkey I think is at 2.15.1 now, You can check to see if your database needs updating by comparing the changelog (button) with the packages offered in the gui.

o1micko, thank you.
I already updated the ppm, but forgot to save it. Seamonkey was 2.19.x. I tested it, but as you say, it was BIG!

tallboy

The updates manager now can update, it does it so fast that it should do it on every startup! At maximum it will only have to deal with 30 or so packages. Just click the button and in seconds it updates, have to restart the gui manually though. This saves the kludge though of updating PPM if you want to keep seamonkey/firefox updated. Slackware release very quickly after mozilla announces.

The gui is fully gettexted too so translators, if you want to add translations feel free, and I'll add them to the package, it's not so much to translate so can be in the default package.

EDIT: SORRY, package is broken .. if you have it uninstall it! updates_mgr-0.4.pet

01micko wrote:As long as jwm -p isn't returning anything we are good

Well, I'd better run it then! The files don't exist. Machine: P4 1.8 GHz, 768 Mb RAM, xorg noveau for GeForce2 MX200. It has the jwm v.590 linked from this thread.

Trying to get the Slacko 5.4 Opera version to load X, produced the same negative result as reported for the test version in the same machine. The 'modesetting' driver is present in /usr/lib/x/drivers-alternate/. AMD Athlon 1.2 GHz, 512 MB RAM, ATI Rage 128.

Yes, 5.4 has a non fatal bug with jwm, 5.4.0.1 has the fix.

As for rage 128.. are you using a 1366x768 monitor? If so it is a pain to get going, I have one, uses the mach64 xorg driver (the modesetting driver is ok in /usr/lib/x/drivers-alternate, where it is supposed to be). You may need to use xrandr manually to achieve 1280x720 resolution which I do. This bug is solved in next woof (see Barry's Blog).

James C wrote:Been running both installs periodically today....... no problems evident yet.
Nice wallpaper too.

Yes I might use that wallpaper in final but I think different icons.. suggestions anyone?

hey micko

no hangs on 5401 (ext2, 2fs), system has been up 1day 19hrs

Been running your 00 version and have notice 01 is out and now downloaded..

Can I continue to use the 00 save-session with 01? Will 01 recognize and use it?

Thanks for your hard work.

gcmartin wrote:Been running your 00 version and have notice 01 is out and now downloaded..

Can I continue to use the 00 save-session with 01? Will 01 recognize and use it?

Thanks for your hard work.

As long as you didn't install any drivers it should be no problem.