Lighthouse Pup 4.43 Gu2 215M

[abushcrafter]

Q5sys,
Hmm, the new Xorg.0.log looks better.

(II) AIGLX: Loaded and initialized /usr/X11R7/lib/dri/i965_dri.so

...up until this part

(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(EE) config/hal: couldn't initialise context: unknown error (null)
Backtrace:
0: X(xorg_backtrace+0x34) [0x8123994]
1: X(xf86SigHandler+0x46) [0x80b0596]
2: [0xffffe400]
3: /usr/lib/libdbus-1.so.3 [0xb7dde126]
4: X [0x80a1f9e]
5: X(WakeupHandler+0x58) [0x80896b8]
6: X(WaitForSomething+0x1c3) [0x81214e3]
7: X(Dispatch+0x7f) [0x80859bf]
8: X(main+0x3be) [0x806c3fe]
9: /lib/libc.so.6(__libc_start_main+0xe5) [0xb7aaf6a5]
10: X [0x806b931]

Fatal server error:
Caught signal 11. Server aborting

I wonder if the Xorg-related files in Mariner SFS are conflicting with MU's xorg-1.6.3 upgrade. When you installed MU's pet in Gu1 was Mariner not loaded yet by chance? I'm thinking if you install his pet after booting with 'pfix=ram', restart X, if that works, then shut down making a new pupsave--and then load Mariner... or is that what you tried already?

Otherwise I just can't figure out why it would work in Gu1 but not Gu2. Weird, well at least Gu1 works.
-TazOC

Pets can replace files but sfss can't.

[fyujj]

Also is it possible to have two instances of the panel with different functions in each panel?

Thanks in advance
Greg.

You can do that with ROX-Panel.
I don't know what's managing the desktop icons in JWM or IceWM in Lighthouse pup because I'm a new user so I don't know if it will mess something. But running ROX-Pinboard and its panel(s) works fine usually in IceWM for instance.
For help, open ROX-Filer, click on the Help icon on the menu bar, then open the manual and search for the Panel entry. You can configure the panel options by right-clicking on a ROX-Filer's window background and choosing Options...>Panel.
There's more detail also at http://sblinux.org/antix/index.html#rox

As for myself, thank you guys for LHP, it's so well set-up.
I wrote about how problematic rp-pppoe can be to connect and asked for it to be replaced by pppoeconf at http://www.murga-linux.com/puppy/viewto ... 917#407917 .
I'm using PuppyBrowser instead of Seamonkey now because SM seemed to use a lot of CPU but I'll install nVidia's prop driver to see if it gets better.

- edit - ROX-Panel doesn't need ROX-Pinboard to run, it runs by itself. See 'rox -h' for all options.
- edit2 - installing nVidia driver's .pet dropped down a lot the CPU use when using Seamonkey.

[tazoc]

Hi all puppy lgh is performing so well and I am now trying to use wine to install a usb webcam but wine flashes up a box which says error and stops installing the driver is it possible to get puppy to look at the driver and convert it somehow to linux driver.

I don't think so; I would be surprised if Wine could set up a Linux driver like that. I think it only interfaces with display and certain audio drivers. There is a custom version of MPlayer, Mplayer-extra-libs and a pet for v4l that might work natively in Linux. edoc suggested it on Mar 11-12th but I haven't tried it Lighthouse:

I loaded MPlayer-extra-libs.pet from here:
http://www.murga-linux.com/puppy/viewtopic.php?t=26511

Then I loaded http://minipc.org/ipup/download/MPlayer-1.0rc2.pet

Then I loaded Xorg7.3-v4l-extension-0.1.1.pet from this thread:
http://www.murga-linux.com/puppy/viewto ... 407#271407

edoc,

After installing this dotpet, it needs to be enabled. Open /etc/X11/xorg.conf in Geany.
In Section "Module" add this line

Code: Select all

Load  "v4l"

OK, are you using the v4l or v4l2 driver? Did the v4l2 driver require editing xorg.conf also?
TazOC

[tazoc]

Pets can replace files but sfss can't.

That's generally true, except that SFS can include scripts launched from /Autostart or /Startup that can update or replace files.

Q5sys,
Hmm, the new Xorg.0.log looks better.

(II) AIGLX: Loaded and initialized /usr/X11R7/lib/dri/i965_dri.so

...up until this part

(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(EE) config/hal: couldn't initialise context: unknown error (null).

I've done some more testing with xorg-1.6.3-upgrade-vesa-intel-2.8.1-mesa-7.5.1-02.pet and found that it works if '/etc/init.d/dbus stop' is entered in a terminal after installing the pet but before running xorgwizard. You'll probably need to turn off the execute bits on '/etc/init.d/dbus' also to prevent problems after rebooting. Apparently the new Xorg needs some combination of dbus and hal or none at all. Puppy 4.3.1 doesn't have '/etc/init.d/dbus' so it works OK. LHP Base has dbus but not hal.

Now here's the interesting part. If the KDE SFS and Mariner SFS are loaded, then this is not a problem because the KDE SFS has all of the hal and dbus components that Xorg-1.6.3-intel is looking for! So if you are running LHP Base, stop dbus when installing the xorg-intel pet as I did above, and if you have Mariner and KDE SFS (included in the Mariner ISO) enabled in boot manager and rebooted, then the pet should install without any intervention. If you've disabled dbus prior to installing the KDE SFS you should make it executable again after enabling Mariner and KDE SFS's or KDE apps like K3b won't run. If you use JWM you'll also want to upgrade pixman with this pet which eliminates the black icons in JWM. Instead a few icons have white backgrounds but they look much better on my system.

The xorg-intel pet should only be installed if you have Intel graphics because it will break the proprietary ATI/nVidia drivers in Mariner and cannot be uninstalled with Puppy Package Manager.
-TazOC

[Newuser]

Thats a shame I felt it was worth asking it makes you want to learn how to write drivers in linux just to be the one that did it first if you see what I mean. Maybe someone will be one day able to compile linux drivers using code from the windows driver.

[tazoc]

Newuser,
I hear that, yes maybe you or someone at Wine will be able to that at some point and yes it was a good question. I understand 'ndiswrapper' allows some Windows network drivers to work in Linux.
TazOC

[Q5sys]

Thats a shame I felt it was worth asking it makes you want to learn how to write drivers in linux just to be the one that did it first if you see what I mean. Maybe someone will be one day able to compile linux drivers using code from the windows driver.

Hey thats what the Open Source community is all about, find a fix for something, and share it with everyone else so we can all benefit together. You can check to see if the driver has been done for any other linux distro. If it exists on a single linux platform... it may be able to be converted (if you can get the source) to work on puppy.

I wonder if the Xorg-related files in Mariner SFS are conflicting with MU's xorg-1.6.3 upgrade. When you installed MU's pet in Gu1 was Mariner not loaded yet by chance? I'm thinking if you install his pet after booting with 'pfix=ram', restart X, if that works, then shut down making a new pupsave--and then load Mariner... or is that what you tried already?

Otherwise I just can't figure out why it would work in Gu1 but not Gu2. Weird, well at least Gu1 works.
-TazOC

Ive tried it with No SFS's loaded and with just the mariner SFS, nothing changed. I thought that something in an SFS might have been conflicting, but disregarded that after testing multiple times in both situations resulted in the same outcome

I've done some more testing with xorg-1.6.3-upgrade-vesa-intel-2.8.1-mesa-7.5.1-02.pet and found that it works if '/etc/init.d/dbus stop' is entered in a terminal after installing the pet but before running xorgwizard. You'll probably need to turn off the execute bits on '/etc/init.d/dbus' also to prevent problems after rebooting. Apparently the new Xorg needs some combination of dbus and hal or none at all. Puppy 4.3.1 doesn't have '/etc/init.d/dbus' so it works OK. LHP Base has dbus but not hal.

I'll have to play around with that later this week when I get the chance.

Now here's the interesting part. If the KDE SFS and Mariner SFS are loaded, then this is not a problem because the KDE SFS has all of the hal and dbus components that Xorg-1.6.3-intel is looking for! So if you are running LHP Base, stop dbus when installing the xorg-intel pet as I did above, and if you have Mariner and KDE SFS (included in the Mariner ISO) enabled in boot manager and rebooted, then the pet should install without any intervention. If you've disabled dbus prior to installing the KDE SFS you should make it executable again after enabling Mariner and KDE SFS's or KDE apps like K3b won't run. If you use JWM you'll also want to upgrade pixman with this pet which eliminates the black icons in JWM. Instead a few icons have white backgrounds but they look much better on my system.

First off... I have both the Mariner and KDE SFS's loaded. So if that was the sole deciding factor... i think i'd be in running order already. Oh but wait... this insanity gets better...
here is the really peculiar part. When I upgraded to Gu2, I started with a new save file. Decided it was time to start with a fresh file and clean out the cobwebs. I actually made 3 at the same time. Standard save file, a base save file (one thats just been made but has nothing changed), and a test save file so I can tinker. These are actually just the same initial save file that was copied and renamed. That way if when Im testing I destroy it I can delete test.2fs and remake it with the copy of Base.2fs.
All that is just setting the stage though. I have been unable to get the intel drivers to load and run properly in them. However today on a whim, I decided to try my old save file (thats 2gb in size from my F and then Gu1 install) in Gu2. And go figure... it works flawlessly.
So the issue apparently isnt as much of a Gu2 issue, as it is... something in my old save file that makes the Xorg-Intel pet work, thats not in my new save files obviously because they are new. What that might be... is a very long list indeed. But its given me a new avenue for me to look down to try to figure it out. With that in mind, are there any files anywhere you'd like me to pull out to take a look at?

The xorg-intel pet should only be installed if you have Intel graphics because it will break the proprietary ATI/nVidia drivers in Mariner and cannot be uninstalled with Puppy Package Manager.
-TazOC

This has been my experience on every Puppy version I have tried to install the Xorg-Intel Pet on. Except 2. Gu1 and Gu2. In LHP-F I wasnt able to uninstall, however on both of the G versions I have been able to. I dont know why I have been able to, but I have. Thats why Ive been able to do so much testing quickly, I havent had to create a new save file every time i've installed it. Not sure if there was a PETGET update of any kind, but 'at least on my system' I can install and uninstall the Xorg-Intel pet on a whim. Perhaps another oddity of my system/install.

[Barburo]

Hi TazOC,
Thanks for pointing me to MU's
xorg-1.6.3-upgrade-vesa-intel-2.8.1-mesa-7.5.1-02.pet
As I always load the KDE and Mariner .sfs files it worked immediately.
How nice to see the screen at the correct resolution!
Still working on wifi - Both wlan0 (Intel Chipset) and ra0 (Buffalo dongle) interfaces are recognized but I still have problems with both drivers. New wifi dongle may be the way to go. Happier now.
B.

[ImmigrantUS]

Please help to fix a Full install.
PC - 533 MHz AMD K6-2, 256 MB SD RAM, 30 GB HD.
All went well - Partitioned HD with stock Puppy CD - only one Linux partition ext 4 (bootable) + SWAP 500 MB. Install into HD, Grub too. The only strange thing was that could not unmount CD-ROM, told me it's probably no media in drive... So, killed it, rebooted into kernel panic, no initrd.gz file found...

What to do?

Thank you all responders in advance!

[01micko]

TazOC

Joe has posted the latest snap of JWM.. jwm-478 (direct link to source http://joewing.net/programs/jwm/snapsho ... 78.tar.bz2 )

It works!

Cheers

[tazoc]

Hi ImmigrantUS,
On the reboot, did the CD-ROM boot or GRUB? If CD-ROM, remove it. If GRUB, check your /boot/grub/menu.lst; here is my entry:

Code: Select all

title Lighthouse Linux 4.43 (full on sda8)
root (hd0,7)
kernel /boot/vmlinuz root=/dev/sda8 pmedia=atahd loglevel=3 pfix=fsck
savedefault

Personally I much prefer the frugal installation. See pros and cons here.
Here is my GRUB entry for a frugal installation:

Code: Select all

title Lighthouse Linux 4.43 (frugal on sda9)
root (hd0,8)
kernel /lhp443/vmlinuz pmedia=atahd pdev1=sda9 psubdir=lhp443 pfix=fsck
initrd /lhp443/initrd.gz
savedefault

-TazOC

[tazoc]

TazOC

Joe has posted the latest snap of JWM.. jwm-478 (direct link to source http://joewing.net/programs/jwm/snapsho ... 78.tar.bz2 )

Thank you 01micko, LHP444 is in a very early stage, with an updated glibc-2.11 and I will try your new jwm-478-i486.pet for Lucid Puppy with that.
-TazOC

[ImmigrantUS]

@ Tazoc: After install I'm booting from HD, GRUB MBR.
I edited menu.lst file to your suggestions:

Code: Select all

title Lighthouse Linux 4.43 (full on sda1)
root (hd0,0)
kernel /boot/vmlinuz root=/dev/sda1 pmedia=atahd loglevel=3 pfix=fsck
savedefault

Trying to boot now gives Error 15 file not found. Press any key to continue....

? still remains - what to do? Should I reformat as ext3 (instead of ext4)?
Is specs of this PC too low? (amd K6-2 533 MHz, 256 MB SDRAM, 30 GB HD)

P.s. I can't go with frugal install... PC is for neighbors' kids for unsupervised use, and two of them (PCs:) were already damaged physically (ports, keyboards, mice) - you want me to tell them to be very careful with this boot CD, not to scratch it, or brake?? You try it. Not me, need solid bootable system.

[tazoc]

@ Tazoc: After install I'm booting from HD, GRUB MBR.
I edited menu.lst file to your suggestions:

Code: Select all

title Lighthouse Linux 4.43 (full on sda1)
root (hd0,0)
kernel /boot/vmlinuz root=/dev/sda1 pmedia=atahd loglevel=3 pfix=fsck
savedefault

Trying to boot now gives Error 15 file not found...
? still remains - what to do? Should I reformat as ext3 (instead of ext4)?
Is specs of this PC too low? (amd K6-2 533 MHz, 356 MB SD RAM, 30 GB HD)

If it boots off the CD and loads Lighthouse OK then the specs should be fine, at least for the Window Managers in the base ISO; KDE might be real slow.

First try deleting the line 'savedefault'. You can test that at the GRUB menu by pressing the 'e' to edit (or maybe 'd' to delete I can't remember) then <Enter> and 'b' to boot. That change is only for that boot. If it works, open menu.lst and make the change permanent. If that doesn't help, I don't know why you're getting Error 15. I'm not sure if formatting with ext3 would help, either should work, I think. Boot off the CD and open sda1 with Pmount Drives. There should be about 20 items (folders and symlinks) in there. Open /boot and make sure vmlinuz is in there.

GRUB errors can be tough to diagnose. Does this PC have more than one hd? Do any of the other entries in GRUB work?

To clarify, the frugal install can be booted with GRUB as the entry in my earlier post shows, also may need to delete 'savedefault', once the files on the CD are copied to the hd. This allows multiple frugal installs of puplets all on the same partition, one in each folder, one-level deep. No CD needed once it works in GRUB. That is how I typically run LHP and Puppy.
TazOC

[ImmigrantUS]

@Tazoc: I checked Boot folder on sda1, and vmlinuz file is right next to Grub folder. Removed line 'savedefault' from menu.lst file and on reboot kernel panic returned, the same as before...
PC has only one HD, set as Cable Select on master end.
Not sure how to check "Do any of the other entries in GRUB work?" - Blue Grub menu comes on boot, starts to boot in 3 seconds (as I set it in menu.lst), clicking on "Install Grub to MBR" shows some activity, clicking other options too. Guess it does something...

If Frugal install can be done without booting every time from CD, than I sure can use it. I did not get it from my previous reading... Will read more on that now. Thank you for your help!

[Q5sys]

Tazoc,

Ive decided to push aside the Intel issue for now, and work on it later. Instead of messing with that now I'm going back to my attempt to be able to run the drives through the wbar program.

I was looking through /sbin/pup_event_frontend_d and I found this @ line 233

Code: Select all

  if [ ! -d ${HOME}/.pup_event/drive_${ONEDRVNAME} ];then
   mkdir ${HOME}/.pup_event/drive_${ONEDRVNAME}
   cp -af /usr/local/bin/drive_all ${HOME}/.pup_event/drive_${ONEDRVNAME}/AppRun

my question is... what is the purpose of the /root/.pup_event/ dir? All those icons seem to do for me is open up the puppy drive mounter, whether they are mounted or not.
lastly on this... why is this repeated again at 268?

EDIT:
I'm attaching what im working with so far. Its the mount, umount, functions4puppy4, and pup_event_frontend_d files that I canabalized from BoxPup, and the same files from LHP that i've tried to edit to add this functionatlity into. My additions/alterations are bracketed before and after by:
###000###000###000###000###000###000###000###000###

However here is the problem. I can edit the mount, umount, and pup_event_frontend_d files without issue, however once I add that three sections of code to functions4puppy4. I get a system where nothing will mount. And Puppy Driver Mounter wont do anything, it'll load but it'll show no drives at all, and when I try to exit X I get a /sys/ does not exist error
I dont see how my alterations would have caused that... but obviously they did, since there are no other changes. Any ideas?

[Pete22]

Hello Puppy friends:

I'm sorry that I was not quick enough to update from f to gu1.

I have a fugal install so I don't have the iso. When I go to the message about updating the sfs, I I only see a link with information about changing from gu1 to gu2.

I have tried to do several things but none of them have worked.

I have never done this updating procedure before and I keep getting mixed up
But I have really tried to find the updater for f to gu1. So where do I find this files?

I know where my files are. They are at mnt/home. If I can get the right file and put in there I think I can go from f to gu1 and then from gu1 to gu2. Or am I totally mixed up?

Would a kind lhp pro help this lhis newbee get up to speed?

Pete22

[Q5sys]

Would a kind lhp pro help this lhis newbee get up to speed?

One of these other guys will have to help you out with that. For myself, I burn the new ISO, format my usb stick, install the new system, then drag my SFS files and save file over to the newly installed system and reboot.

[tazoc]

Hello Puppy friends:

I'm sorry that I was not quick enough to update from f to gu1.

I have a fugal install so I don't have the iso. When I go to the message about updating the sfs, I I only see a link with information about changing from gu1 to gu2.

I know where my files are. They are at mnt/home. If I can get the right file and put in there I think I can go from f to gu1 and then from gu1 to gu2. Or am I totally mixed up?
Pete22

Hi Pete22,
Beginning with a frugal install of 4.43F go here http://www.lhpup.org/release/lhp443/inside-iso/443Gu1/, d/l the files and open the Inside-ISO-readme. That will get you from F to Gu1. When you've completed that and used the included click-to-verify, go to http://www.lhpup.org/release/lhp443/inside-iso/443Gu2/ and do the same for updating Gu1 to Gu2. Then you will have the base LHP updated to Gu2.

Gu1 and Gu2 use the same 'G' SFS add-ons. So if you use add-ons or had the Mariner ISO d/l the 'G' SFS xdelta3 files for the SFS add-ons that you had for 4.43F and use this procedure to update them to G and your all set.

I recommend booting Gu2 with 'pfix=ram' and backing up your pupsave prior to running Gu2 with a new or existing pupsave.
TazOC

[tazoc]

my question is... what is the purpose of the /root/.pup_event/ dir? All those icons seem to do for me is open up the puppy drive mounter, whether they are mounted or not.
lastly on this... why is this repeated again at 268?

It's a ROXapp like /root/my-roxapps/Edit-SFS. An executable folder in ROX-Filer defined by the files inside, AppRun and AppInfo.xml. To see them right-click on the dir | Look Inside. The AppInfo.xml defines the custom menu for the right-click and what you see when choosing properties and the hover tool-tip. I think it is repeated because the first one creates a partition icon and the second creates an icon for the entire drive if no partitions on the drive have icons.

I also get Pmount when clicking on the ~.pup_event/ dir, not sure yet why.

However here is the problem. I can edit the mount, umount, and pup_event_frontend_d files without issue, however once I add that three sections of code to functions4puppy4. I get a system where nothing will mount. And Puppy Driver Mounter wont do anything, it'll load but it'll show no drives at all, and when I try to exit X I get a /sys/ does not exist error
I dont see how my alterations would have caused that... but obviously they did, since there are no other changes. Any ideas?

In functions4puppy4 remove the extra '{' at line 126 and 172. Make sure your new mount and umount have the executable permissions set.

If I get this working, I'll send you my files. I'm making a symlink in /usr/bin/ named vbar pointing to /usr/bin/wbar. That way we can keep the two wbar processes separate and kill/restart vbar without killing wbar.
-TazOC