Lucid Puppy 5.1.1 Release - This is the official release

[ICPUG]

Query for Playdayz

Regarding the init script that executes on startup.

Is the Lucid design philosopy to take that which is provided via woof or could we tinker with it to provide a Lucid specific experience?

I ask this because there are some features implemented in other init scripts that could be useful, such as these examples:

- Shinobar's mod to allow add on sfs files to be stored in the same location as the Puppy files in a frugal install.
- when using a live CD give an option whether the sfs file is transferred to hard drive from the CD and not do it automatically.
- speed the frugal boot process by searching the psubdir location directly (when psubdir is used) rather than search everwhere and then ignore anything outside psubdir.

[rcrsn51]

Still can't find the driver database for cups 1.4.3

I believe that you are looking for the collection of PPD files. Strictly speaking, these are not printer drivers.

Like I said in my previous post, CUPS 1.4.3 does not need to keep a permanent store of Gutenprint PPD files. That's why you can't find them. When you select a printer, CUPS generates the matching PPD file on the fly, then transfers it to /etc/cups/ppd.

[shinobar]

there are some features implemented in other init scripts that could be useful, such as these examples:.

thanks for your interest. I like to add some information.

• Shinobar's mod to allow add on sfs files to be stored in the same location as the Puppy files in a frugal install.
  This is implemented in Puppy-4.3JP first and now woof 20Jul2010 and later also has. Lupu-222 too? i have not yet tested on lupu.
  See Barry's Blog.
• when using a live CD give an option whether the sfs file is transferred to hard drive from the CD and not do it automatically.
  The automatical copy of sfs is removed on Puppy-4.2, the last community edition, but Barry brings back at Puppy 4.3.
• speed the frugal boot process by searching the psubdir location directly (when psubdir is used) rather than search everwhere and then ignore anything outside psubdir.
  Maybe Puppy-4.3JP and later, unique on Japanese editions.

See Puppy Linux 431JP release note section 'Differences from original version', item 2, for the detail.

[JonT]

trying Luci222: no problems with apps, though I'm likely not as thorough as some. Pcd, Pmusic and psync worked fine. I was not able to determine if 915resolution works properly, but I get 1024x768x24 normally and don't miss not getting the max 32 bit color depth.

In the tiny details dept: It might be "nice" if moving the second psync window didn't erase the underlying one. Also, mainly for the benefit of newer users, shouldn't there be an "Exit to prompt" item in the icewm menu item as exists in jwm and is referred to in "Setup"? Maybe merely relabel "Logout"?

Apparently not a problem for most, for me Luci222 fails often (unrecoverable black screen) on reboot or anything that involves restarting X, such as switching from jwm to icewm. Sure did make trying to test 915resolution a pain. Lucid 5.10 is good in this respect though not perfect. Only "intel 845" knows why ...

Seamonkey had the refresh problem when ovelapping the taskbar overlap initially, but not after a reboot. I think firefox did the same on Lucid 510.

... with thanks.

[Karl Godt]

CUPS generates the matching PPD file on the fly

So it's in the air ?
not becomming rude is difficult sometimes

[playdayz]

Query for Playdayz

Regarding the init script that executes on startup.

Is the Lucid design philosopy to take that which is provided via woof or could we tinker with it to provide a Lucid specific experience?

Hey ICPUG, In general the design philosophy is too stay as close as possible to Woof. In a sense Lucid Puppy is a show piece for the Woof Puppy Builder. Also, the Woof code has been very well-tested and refined, which imho an "official" build of Puppy should be. Obviously, we don't follow Woof entirely in booting to the desktop--but you might be surprised at how few changes in the code that involves--three lines added to xorgwizard, the initial abbreviated xorgwizard on first boot (which Barry suggested btw), and the switcheroo between xorg-setup and xorgwizard on first boot. Some of our changes have already filtered back into Woof so one shouldn't think that no forward motion is taking place. We also added the Browser Chooser and Quickpet, etc., but these are simple programs that are added rather than modifications to the system code. Barry does incorporate modifications to the system code of Woof suggested by other people and they reach us that way also. Thanks.

Lucid Puppy is definitely more conservative than someone can be with a derivative of course, which I think it appropriate. I have become more conservative myself as I understand more and more how much Puppy evolved as a "whole," that is, with a lot of inter-dependent code--such that making changes can have unexpected repercussions.

[playdayz]

Apparently not a problem for most, for me Luci222 fails often (unrecoverable black screen) on reboot or anything that involves restarting X, such as switching from jwm to icewm. Sure did make trying to test 915resolution a pain. Lucid 5.10 is good in this respect though not perfect. Only "intel 845" knows why ...

This worries me since there is a new 915resolution--can other Intel graphics users test please.

[rcrsn51]

CUPS generates the matching PPD file on the fly

So it's in the air ?

The PPD file is generated from the XML database that you have already discovered.

Are you having trouble installing a particular printer? What make and model?

[Edit] "On the fly" is an expression meaning "immediately, while you wait".

[jemimah]

915resolution only affects Xvesa. Xorg doesn't use it at all.

[James C]

Luci-222 live pfix=ram on a different Intel box. Booted to the correct resolution (1440x900) and working sound and internet. Installed Xorg_High and Firefox.



VIDEO REPORT: Lucid Puppy, version 222

Chip description:
Intel Corporation 82865G Integrated Graphics Controller

Driver used by Xorg:


Video mode used by Xorg:
Resolution: Depth:

...the above also recorded in /tmp/report-video
#


# glxgears
2287 frames in 5.0 seconds
2258 frames in 5.0 seconds
2138 frames in 5.0 seconds
2265 frames in 5.0 seconds
2071 frames in 5.0 seconds
3957 frames in 5.0 seconds
3986 frames in 5.0 seconds
4224 frames in 5.0 seconds
4217 frames in 5.0 seconds
4207 frames in 5.0 seconds
4167 frames in 5.0 seconds
4044 frames in 5.0 seconds
3968 frames in 5.0 seconds
4280 frames in 5.0 seconds


--OpenGL-
Vendor : Tungsten Graphics, Inc
Renderer : Mesa DRI Intel(R) 865G GEM 20091221 2009Q4 x86/MMX/SSE2
Version : 1.3 Mesa 7.7.1
Direct Rendering : Yes


-Computer-
Processor : 2x Intel(R) Pentium(R) 4 CPU 2.60GHz
Memory : 2593MB (129MB used)
Operating System : Puppy Linux 0.22
User Name : root (root)
Date/Time : Wed 01 Sep 2010 10:49:49 AM GMT-8
-Display-
Resolution : 1440x900 pixels
OpenGL Renderer : Mesa DRI Intel(R) 865G GEM 20091221 2009Q4 x86/MMX/SSE2
X11 Vendor : The X.Org Foundation


Changed window managers and restarted x a couple of times, no problems.In general, everything is working.

[rjbrewer]

915resolution only affects Xvesa. Xorg doesn't use it at all.

????

In order to use Xorg in Fluppy or Luci on my Inspiron-intel855gm graphics; I must use i915.modeset=1 fix.

Is this not a 915 resolution problem?

[pemasu]

Is here question of this patch ? Looks like it affects only certain intel GM
graphics.
http://www.murga-linux.com/puppy/viewto ... 799#223799

For Intel graphics devices which need a vbios hack to enable their true resolutions, here is the "915resolution" utility.
Puppy 4.1 alphas already have this utility modified to support the Intel 945GM chipset in the Acer Aspire One, but this version has been patched further to support the G33 (GMA3100) Intel chipset, device id 29c0:8086.

UPDATE Sep 25 2008: G33 support now includes device id 29b0:8086.
UPDATE Oct 13 2008: support added for GM965, device id 2a00:8086.
UPDATE Dec 11 2009: ArchLinux patches added by Barry, then modified by me to support GM45 (GMA 4500MHD) device id 2a40:8086.
UPDATE May 31 2010: support added for GMA3150 (N10 Pineview) device id a010:8086.
UPDATE August 28 2010: support added for GMA X3100, device ID's 8086:2a01 and 8086:2a02. I have identified these two devices in the source code as part of the "GM965" chipset family.

[jemimah]

915resolution only affects Xvesa. Xorg doesn't use it at all.

????

In order to use Xorg in Fluppy or Luci on my Inspiron-intel855gm graphics; I must use i915.modeset=1 fix.

Is this not a 915 resolution problem?

No actually.
All the 915resolution binary does is modify what resolutions the BIOS advertises. Only Xvesa cares about the BIOS. Xorg is more sophisticated.

i915.modeset is an adjustment for the kernel - so Xorg doesn't have to figure out how to set the resolution itself.

[pemasu]

Does kernel level modesetting work in Puppies ?

[alec78]

Hi all,
Sad to report that I failed to get online with luci-222/Samsung X05 and Huawei E169G USB 3G modem.
I fired up the X05 from a dongle with luci-222 on. Hit the Connect icon on the desktop and then went through the usual routine of erasing the on board dial-up modem and then probing for the ttyUSB0 modem, only now I am getting no modem detected.
I shut down then re-booted with the E169G already inserted but no joy.
I am posting this from my old Dell Latitude LS and lupu-510.
I have either done something quite silly, or this is a big step backwards for me.
Setting up the E169G has been getting easier and easier with each evolution of Puppy, until it was a matter of just a few clicks and filling in a few boxers, thanks in the main to the great work done by rerwin.
I'll probably do a new pfix=ram install tomorrow and try again.
Cheers

[01micko]

Hi all,
Sad to report that I failed to get online with luci-222/Samsung X05 and Huawei E169G USB 3G modem.
I fired up the X05 from a dongle with luci-222 on. Hit the Connect icon on the desktop and then went through the usual routine of erasing the on board dial-up modem and then probing for the ttyUSB0 modem, only now I am getting no modem detected.
I shut down then re-booted with the E169G already inserted but no joy.
I am posting this from my old Dell Latitude LS and lupu-510.
I have either done something quite silly, or this is a big step backwards for me.
Setting up the E169G has been getting easier and easier with each evolution of Puppy, until it was a matter of just a few clicks and filling in a few boxers, thanks in the main to the great work done by rerwin.
I'll probably do a new pfix=ram install tomorrow and try again.
Cheers

alec78

You want some good news? I have the same modem . I also have access to another 3G modem to test. I will get on to this later today.

Cheers

[scsijon]

from barrys blog and maybe we should consider it for 511 especially with the 0%cpu load

regards
scsijon

-----------------------------------
Posted on 1 Sep 2010, 24:58 by technosaurus
minimp3 30kb static
I came across a very tiny mp3 player a while back and compiled it against puppy's gnu libc and libm but recently I wanted to see if I could remove even those dependencies and ended up compiling it against static dietlibc. It is only 30kb and runs in less than 500kb of RAM with 0% CPU load on my 1.6Ghz laptop. If you have ever wanted to integrate sound into the startup or just have always reliable and minimal mp3 capability, this is it.

I have posted the sources and binaries in this thread:
http://www.murga-linux.com/puppy/viewtopic.php?t=59417
----------------------------------

[Karl Godt]

luci-222 works best with my modem now , too

no plugin/plugout anymore.

the linenumbers of pupdial are the same as 218+219 , 220 is different.

218 and 219 weren`t so easy if IRCorrectly

perhaps it`s pppd or wvdial becomming better

[rjbrewer]

Couldn't get a wireless connection to last more than 1/2 hour until
I installed Pwireless2.

Not the Pwireless2 in the ppm (which I couldn't get to connect), but
the Pwireless2 from Jemimahs thread (which connected immediately).

[playdayz]

Not the Pwireless2 in the ppm (which I couldn't get to connect), but
the Pwireless2 from Jemimahs thread (which connected immediately).

I will look into changing.

Oh, something was wrong. One was 44k and the other was 254k (the one in jemimah's thread--which is now the one in the puppy-lucid repo of PPM). Thanks.