(old)Puppy Linux Discussion Forum

Posted: **Mon 07 Feb 2011, 23:50**

_Mark_ wrote:Hey ttuuxxx

Found a bit of a typo in the logout screen you missed a c out of switch, on the switch to jwm button

thanks mark I'll look at it

ttuuxxx

Posted: **Tue 08 Feb 2011, 01:19**

Hi ttuuxxx,

ttuuxxx wrote:...Hmm I never had rox look like that, are you sure you didn't reconfigure it?

Only as I usually do:

Rox in 214x-top6:
http://i51.tinypic.com/2cy8f5.png

Rox in Puppy Studio 3.3:
http://i54.tinypic.com/5oegd1.png

...AHA!!! It's that Max Width --> Small Icons setting.

Boosted it to 250 and now it is usable.

Are you sure you don't have a pupsave from 2.14R?

Yes, there is no other 214 pup_save on this machine. I named it specifically, "pup_save-214xtop6.3fs". All other pup_save's are within psubdir's. boxpup-421-retro's pup_save is the only other pup_save the 214x-top6 init sequence detects the presence of. There are 27 other pup_save's in this partition, besides 214x-top6's and boxpup's, but 214x-top6 evidently stops looking after it finds boxpup's, which is the next Puppy alphabetically.

Another noticed flaw: the pup_events collection of scripts...whichever is the responsible one...is drawing the drive icons too close to the bottom edge when Rox->Options->Pinboard->Icon grid step is set to Coarse. The drive labels are covered over by the taskbar, see above-linked screenshot. If I drag them up so the labels are visible, the icons drop back down again upon next reboot.

I can definitely notice the difference in speed with which Rox loads a partition's contents for display, and speed of PFind and find, between kernel 2.6.18.1 and 2.6.33.2. But then, all my disks on this machine are SATA 150 --I've gotten rid of all my SCSI gear. It stands to reason that the driver has been improved.

Best,
SHS

Posted: **Tue 08 Feb 2011, 16:18**

Hi,

Been awhile since I tried a new Puppy, couldn't resist with all your improvements listed.

using Pfix=ram it loaded like a champion, and I found network perfectly, as actually posting from 214xt6 here.

Don't know where to list possible bug, but could not locate the "Left Hand" mouse switch button, could be my system as using a KVM system switcher but other Pups have had the left hand switch.
Great job, works fast on this custom 933 P3, w512, rtl netcrd

PostScript_1
Just noticed clock is wrong and no menu way to set it, also looking at loaded modules Hiawatha had started on initial load

PostScript_2
WoW!!! shutdown Cups and Webserver _ 276 Mb of free mem as a pfix ram full load
I think I'll move this SFS into my exe install dir

Thank You - thank you
jay

Posted: **Tue 08 Feb 2011, 19:25**

Most snipped.

efiguy wrote: 1 Just noticed clock is wrong and no menu way to set it

Menu -> Desktop -> Set date and time

Posted: **Tue 08 Feb 2011, 20:55**

efiguy wrote:1b ..., also looking at loaded modules Hiawatha had started on initial load

Easiest, non-destructive, way to stop it from starting at every boot is to remove Exec-permissions of /etc/rc.d/init.d/hiawatha.run:

Code: Select all

chmod 644 /etc/rc.d/init.d/hiawatha.run

Cheers

/
MHHP

Posted: **Sun 13 Feb 2011, 03:27**

I've took one of the backgrounds in 2.14x made a system link, added lots of code to the gtk theme and came up with menu background in the menu. do you guys like it?
also added arrows, blue and green
ttuuxxx

Posted: **Sun 13 Feb 2011, 03:35**

Nice.

Posted: **Sun 13 Feb 2011, 03:50**

it also works in rox

, so it works with rox in jwm also.
ttuuxxx

Posted: **Sun 13 Feb 2011, 04:35**

ttuuxxx
That is the sharpest looking menu I’ve seen since we started playing around JWM themes way back when. But, that grey taskbar has gotta go. LOL

Posted: **Sun 13 Feb 2011, 23:54**

Nice one, ttuuxxx

!

Care to share the gtk theme-hack

?

Cheers

/
MHHP

Posted: **Mon 14 Feb 2011, 05:04**

MinHundHettePerro wrote:Nice one, ttuuxxx !

Care to share the gtk theme-hack ?

Cheers /
MHHP

I'm still working on it, but I was just going to add it to the next release, Probably in a day or two

, well a new Firefox is out and The default layout bugs me so I'll revert it to the older look.
ttuuxxx

Posted: **Mon 14 Feb 2011, 09:34**

ttuuxxx wrote:I've took one of the backgrounds in 2.14x made a system link, added lots of code to the gtk theme and came up with menu background in the menu. do you guys like it?

Hooo-eeey, I don't suppose you could transplant that into l0wt3ch's MyCrossover icewm theme, as supplied in Puppy Studio 3.3?

Posted: **Mon 14 Feb 2011, 15:37**

MinHundHettePerro wrote:
To answer your question:
I've been thinking about how to upgrade the kernel to sfs ver. >=3.1 (proper, 214 has some 3.1rc[1|2]), and also whether it would be feasible to upgrade the kernel to 2.6.18.8. Kernel 2.6.18.1 that was used for 214[-|r|X], 216(1) and 217(1) were patched by BK and all the links to the original, complete, sources, patches and all, seemed dead (puptrix.org, e.g.); I had some patched sources of K2.6.18.1 stashed away, and ttuuxxx provided some more at his smokey01 repo.
Regardless, I wanted to (at least in the first go at it) keep all the original BK-patches to the kernel, so as not to risk loosing any support for older hardware that was working, thus I manually patched BK's K2.6.18.1 (already patched with sfs-3.1rc?) with sfs-3.4.

AFAIK, BK's K2.6.18.8 was compiled way later than the K2.6.18.1 used in the original 2-series puppies, in a woof attempt at pup218, and judging from the file name of the patched sources, there could be some patches omitted from this later version.

I have started looking into how to upgrade the kernel in 214X to K2.6.18.8, while ensuring all the original patches are preserved (comparing the patched sources of kernels used in 214/216 and BK's 2.6.18.8 with vanilla sources of 2.6.18.1 and 2.6.18. - might have a go at it in a week or two.

OTOH, if someone has a link to (or can provide) the complete kernel sources of K2.6.18.1 (of puppy 214 or 216), patches and all, I would be very much obliged .

Cheers /
MHHP

Hi MHHP,

I agree that's the right approach to achieve maximum compatibility with old hardware and keep the 214X kernel original essence.

I also tried to find the individual kernel patches by their name, but I had no luck. I could not find the loglevel, via, dpath or ksize patches.

I just found newer unionfs releases for 2.6.18.X but as I described in the upgrade process I have to test those versions, and hope the Unix socket problem is solved and track any other inconsistency.

Did you have any luck with the patches sources? How is the compare process going on?

Greetings,
clarf

Posted: **Mon 14 Feb 2011, 17:56**

Hey ttuuxxx, since the topic of how to boot 214x on a frugal install seems to appear over and over again maybe you can add MHHP's example GRUB to the first post where your download files are. Bc PSUBDIR doesn't work people who are used to using current versions are not sure how to boot. Just a thought to clear up some confusion that keeps happening.... Or else get psubdir to work..

#
title Puppy 214X
rootnoverify (hd0,4)
kernel /puppy_214XRC5P/vmlinuz root=/dev/ram0 PMEDIA=idehd PDEV1=hda5 PUPMODE=12 DEV1FS=ext2 SFSFILE=ext2,hda5,/puppy_214XRC5P/pup_214X.sfs ZDRV=ext2,hda5,/puppy_214XRC5P/zdrv_214X.sfs PUPSAVE=ext2,hda5,/puppy_214XRC5P/pup_save-214XRC5P.rfs
initrd /puppy_214XRC5P/initrd.gz
#

Posted: **Mon 14 Feb 2011, 21:16**

sinc wrote:Hey ttuuxxx, since the topic of how to boot 214x on a frugal install seems to appear over and over again maybe you can add MHHP's example GRUB to the first post where your download files are. Bc PSUBDIR doesn't work people who are used to using current versions are not sure how to boot. Just a thought to clear up some confusion that keeps happening.... Or else get psubdir to work..

#
title Puppy 214X
rootnoverify (hd0,4)
kernel /puppy_214XRC5P/vmlinuz root=/dev/ram0 PMEDIA=idehd PDEV1=hda5 PUPMODE=12 DEV1FS=ext2 SFSFILE=ext2,hda5,/puppy_214XRC5P/pup_214X.sfs ZDRV=ext2,hda5,/puppy_214XRC5P/zdrv_214X.sfs PUPSAVE=ext2,hda5,/puppy_214XRC5P/pup_save-214XRC5P.rfs
initrd /puppy_214XRC5P/initrd.gz
#

Hello

!
Perhaps even more instructive, are the following posts by vg1: post_1, post_2 and post_3.

(On a sidenote, in my quoted boot stanza above; my pupsave-file having the extension .rfs is not a typo (I am using a reiserfs-formatted pupsave, which is only implemented in my own initrd.gz), everybody else should use .2fs or .3fs.)

Cheers

/
MHHP

Posted: **Mon 14 Feb 2011, 21:49**

clarf wrote:Hi MHHP,

I agree that's the right approach to achieve maximum compatibility with old hardware and keep the 214X kernel original essence.

I also tried to find the individual kernel patches by their name, but I had no luck. I could not find the loglevel, via, dpath or ksize patches.

I just found newer unionfs releases for 2.6.18.X but as I described in the upgrade process I have to test those versions, and hope the Unix socket problem is solved and track any other inconsistency.

Did you have any luck with the patches sources? How is the compare process going on?

Greetings,
clarf

Hello, clarf

!
I've started diffing the available sources (original, pup216, pup214 ...) and tracking down the files that were patched by the different patches. I think it should be possible to reverse engineer the patches for the ksize-, dpath- and via-patches, as I have patched sources with one, two and three of these patches applied respectively.
The loglevel patch is, from what I gather, sometimes also called the printk.c patch, and is described well in Iguleders kernel compile instructions, where it's called lower_verbosity-patch

.

Anyway, I'm still onto it, (but, have strayed away the last few days, trying to install CRUX

) and think it should be doable. A helluva job it seems, but I'm enjoying it

.

Cheers

/
MHHP

Posted: **Tue 15 Feb 2011, 15:31**

ttuuxxx
added lots of code to the gtk theme and came up with menu background in the menu. do you guys like it?

Hey Jeff looks great !
as you know I have been forked from puppy current for a few years

and by you using 214 basically you are keeping a fork going too

our methods differ but the fact is we have updated
a puppy version.Since then I have moved on to a" new base system"

I would hope that you could repeat the JWM theme against
any official JWM versions that way any work you do here and
improve the looks might get added to the mainstream JWM

*ADDED 2-18-2011 info I would like to try your JWM with the backgrounds in the menu
it looks cool

Joe

Posted: **Mon 21 Feb 2011, 00:30**

Been away from the puppy scene for a while but back and just seen 214x top6 (why top???) which looks nice but...

Tried to install it as a frugal to a laptop and it doesn't see the hard drive (a sata drive). So I tried it in another box with ide drives and it sees them okay. Then I tried other versions of 214x back to 214X6 and none of them recognise the laptop hard drive!
Tried puppy 412 and lupu 520 and they all see the sata drive just fine.
What's going on?

Posted: **Mon 21 Feb 2011, 05:29**

Hello Guys, i am running the 2.14 distro from live cd in mi laptop, is a toshiba satellite a10. But can not recognise the wireless adapter, a dlink usb adapter, model DWA-110 with chipset RT73 (reference this in a blog), i have the driver for windows but am a noobie in linux world and i do not know how to install.

Can you help me in the instalation process?

Thank you very much.

Posted: **Mon 21 Feb 2011, 06:24**

Foroweb wrote:i have the driver for windows but am a noobie in linux world and i do not know how to install.

Please don't use that kludgey Windows-driver workaround. It's quite unhelpful to the Linux community.

The D-Link DWA-110 is supported by the rt73 Linux driver, but the standard rt73 driver in the Puppy 2.x series is too old to support that particular device ID (07D1:3C07).
Your solution is to install the upgraded rt73 Ralink driver from here -
http://www.murga-linux.com/puppy/viewto ... 232#316232
After installing that dotpet, reboot.

(old)Puppy Linux Discussion Forum

Classic Pup 2.14X -- Updated 2 series

Classic Pup 2.14X -- Updated 2 series

Re: Classic Pup 2.14X -- Updated 2 series

Re: Classic Pup 2.14X -- Updated 2 series

214 doesnt see my sata drives