Lighthouse Pup 5.00 G 185M

[tazoc]

Béèm,
Make a backup copy of /sbin/pup_event_frontend_d just in case...

Place into Line 27 (before LANG=C)

Code: Select all

OLDLANG=$LANG

Copy and paste this replacing the entire format_size_func that begins at line 115

Code: Select all

format_size_func() {
 [ ! $SIZE ] && SIZE=0
 if [ $SIZE -gt 1048576 ];then #1024*1024
  SIZE="`LANG=$OLDLANG dc $SIZE 1048576 \/ p`" #100613
  SIZE="`LANG=$OLDLANG printf "%.1f" $SIZE`GB" #100613
 else
  if [ $SIZE -gt 99 ];then
   SIZE="`LANG=$OLDLANG expr $SIZE \/ 1024`MB" #100613
  else
   SIZE="`LANG=$OLDLANG dc $SIZE 1024 \/ p`" #100613
   SIZE="`LANG=$OLDLANG printf "%.1f" $SIZE`MB" #100613
  fi
 fi
 [ "$SIZE" = "0.0MB" ] && SIZE="0"
}

Save your changes, right-click on a drive icon | Run Desktop Icon Manager | tick Re-align existing icons | OK and restart X. This was all with nl_BE locale, and it worked for me.

If not, restore the file we edited and change !#/bin/ash to !#/bin/bash and repeat the last two steps. (re-align icons, restart X)
-TazOC

[Barburo]

My save file is ext 3 (.3fs). It is saved in an ext3 partition.
I did the scan check on it that you suggested and it changed many blocks. Reran until clear.
On exit a message about needing to recover the journal (large file).
Rebooted with pfix=fsck and when the check started on the save file I got several messages like "in use by another program?" and other errors - finally a kernel panic. Just re booted with fsck again and all went well and the system tray applet correctly shows 1.5gigs, 1.1 available.
Not sure how/why this happened but will continue with testing.
B.

[ICPUG]

OK - I've finally got round to trying to get my Intel 855 integrated graphics working with a proper driver, not VESA.

I'm using Lighthouse 500a at the moment.

Following Tazoc's excellent data , which I misinterpreted, I tried using a kernel parameter of i810.modeset=1 and i810.modeset=0. Both failed with the following error messages in the xorg log:

...
loading driver: intel
...
No kernel modesetting driver detected
unloading driver: intel
...

(Thank you - thank you - Tazoc for allowing us to recover from the black screen without a reset and giving us access to the error log! This is a nice touch which the other Puppy developers would do well to copy)

It seems to be looking for something, cannot find it so unloads the video driver. No wonder we get a black screen!

I've done some googling today.

The intel driver now used in Puppy MUST have kernel mode setting (KMS)operational. I cannot quite determine whether KMS is on by default or not. As Tazoc says it seems as if it should be but according to:
https://wiki.ubuntu.com/X/KernelModeSetting
VESA does not work with KMS and yet it works without the kernel parameter nomodeset.

It would be nice to know what the Intel driver is looking for when it says no kernel modesetting driver detected and perhaps we could supply it.

OK - the best post I have found that discusses this problem is this one:
https://wiki.ubuntu.com/X/Bugs/Lucidi8xxFreezes

Various workarounds are presented but the most reported successes elsewhere is to run the kernel parameter i915.modeset=1. Trust me not to try this last night but I thought I needed i810 because I had an 855 chip and the i810 driver worked before!

I have only seen 1 failure reported with this option but being a pessimist I want to assume that I am going to get a failure and I have a query for Tazoc:

When you run the Xorg wizard and select 'choose' (a driver) you are presented with a list which includes intel. presumably this is the standard intel driver. If I wanted to add the old i810.so driver can I add it to this list somehow? If so, how and where must the driver files be located to be picked up?

Why do I want to do this?

Well, even those succeeding with i915.modeset=1 have reported some problems with video playback. i810 driver has worked in the past but failed for me with Quirky. I am beginning to wonder if this is because KMS was enabled and i810 is definitely a non KMS driver.

What I want to try is to use the i810 driver but disable KMS by using the kernel parameter nomodeset.

[Béèm]

Béèm,
Make a backup copy of /sbin/pup_event_frontend_d just in case...

-TazOC

Etc......
I did several locale changes from fr_BE to nl_BE and vice versa.
I see the desktop drive icon size do stick now.

Thank for your clear instructions.

Bernard

[tazoc]

OK - I've finally got round to trying to get my Intel 855 integrated graphics working with a proper driver, not VESA.

I'm using Lighthouse 500a at the moment.

What I want to try is to use the i810 driver but disable KMS by using the kernel parameter nomodeset.

ICPUG,
intel (in the xf86-video-intel package) is the current driver, formerly known as i810, and the old i810 driver won't work with xorg-xserver 1.7.7 in Lighthouse 5.00. (Quirky's xserver is 1.7.1.) From /usr/doc/xf86-video-intel-2.11.0/README:

xf86-video-intel
Open-source X.org graphics driver for Intel graphics
http://www.intellinuxgraphics.com/

What is xf86-video-intel
------------------------
The xf86-video-intel module is an open-source 2D graphics driver for
the X Window System as implemented by X.org. It supports a variety of
Intel graphics chipsets including:

i810/i810e/i810-dc100,i815,
i830M,845G,852GM,855GM,865G,
915G/GM,945G/GM/GME,946GZ
G/GM/GME/Q965,
G/Q33,G/Q35,G41,G/Q43,G/GM/Q45
PineView-M (Atom N400 series)
PineView-D (Atom D400/D500 series)

So I think your best bet is choosing intel in xorgwizard. I'm guessing it uses the i830 kernel module, which has no kernel line options (modinfo i830 in a terminal) and neither does the i810 kernel module. That's why i810.modeset=1 ( or =0) has no effect. The message you saw does not necessarily indicate a problem for the driver. It simply means that the kernel module won't set video modes, but Xorg can still do that. My ATI RS780 (using Xorg radeon) has hardware accelerated 2D & 3D working even though the Xorg.0.log states "[KMS] drm report modesetting isn't supported." By the way, my testing indicates that the kernel options xforcevesa nomodeset don't preclude Xorg and xorgwizard from using another driver; they just keep the kernel (KMS) from setting a video mode before Xorg itself gains control.

I wish Intel had better drivers for your graphics chip. From this chart it appears that 2D Acceleration and DRI should work, (although it doesn't mention the 855 specifically) but probably not Mesa 3D.

I did several locale changes from fr_BE to nl_BE and vice versa.
I see the desktop drive icon size do stick now.

Thank for your clear instructions.

You're welcome! Glad it's working--thanks to the fix by BK.
-TazOC

[tazoc]

Here is the proprietary nVidia 195 driver PET package for Lighthouse Pup 5.00, tested in LHP 5.00B with a GeForce 6200 AGP card installed on an Intel P4@1.7GHz desktop. Includes nvidia-settings control center, full GLX/3D support and updated Lighthouse Video Wizard. Will not work in Quirky/Lucid or other Puppies as it was compiled with xorg-xserver 1.7.7 and mesa-7.8.1. Good idea to boot LHP with pfix=ram first to try it out with your hardware, especially if you have a full install.

You'll need at least 90M free space, and one of these Supported Chipsets to use the pet.

[Edit 21 June: Updated libwfb.so and once installed, the driver can be selected or changed in xorgwizard, Option 5--NVIDIA cards. Be sure to backup your pupsave before installing this pet. Can be uninstalled with Puppy Package Manager, though it may be necessary to reboot when switching from the proprietary driver back to an Xorg driver.]

NVIDIA-195.36.31-LHP-k2.6.33.2-xserver-1.7.7.pet 30M md5.txt

Thanks to Jim1911 for testing and providing his logs with report-video to debug this driver.

-TazOC

[Jim1911]

Hi tazoc,

Sorry, you new nvidia 195 pet doesn't work with my NVIDIA Geforce 8400 GS 512MB card which that driver does support. It appears to install properly and does install the NVIDIA x server settings tool. Upon restartX it takes you to a command line, as does xwin. Xorgconf autoconfiguration returns you to command line. Only by using nvidea to select "nv" or xorgconfig to select "nv" works. The new driver cannot be selected, editing the conf file to say "nvidia" doesn't work either.

Thanks,
Jim

[tazoc]

Hi Jim,
Thank you for trying it. I'm working on an update with a better uninstaller and removed the pet from the post for now. If you still have the old version installed it would be help me if you could edit the configuration from the command line to enable the nvidia driver with mp /etc/X11/xorg.conf, <Ctrl>+<S> to save <Ctrl>+<Q> to quit and type xwin <Enter>. Still at the command line, type report-video <Enter>. Then to post the logs, switch back to nv with xorgwizard and attach /tmp/root/report-video-full.gz to your post.
Thank you,
TazOC

[Jim1911]

Hi Jim,
Thank you for trying it. I'm working on an update with a better uninstaller and removed the pet from the post for now. If you still have the old version installed it would be help me if you could edit the configuration from the command line to enable the nvidia driver with mp /etc/X11/xorg.conf, <Ctrl>+<S> to save <Ctrl>+<Q> to quit and type xwin <Enter>. Still at the command line, type report-video <Enter>. Then to post the logs, switch back to nv with xorgwizard and attach /tmp/root/report-video-full.gz to your post.
Thank you,
TazOC

My pleasure.

[tazoc]

Thanks, Jim, the X log indicated the nvidia kernel module was not found. That would be expected if you ran xorgwizard before report-video--I'll change it so the NVIDIA driver can be installed with xorgwizard.

(The following might help me, but don't worry if you can't do it now; I'll continue testing some changes to the PET here and post when its ready.)

Can you re-install the pet, selecting "Normal Yes change the driver in the Device Section".
When it finishes, open a terminal and paste in the following (I think all at once is OK):

Code: Select all

echo "`df -m / |tail -n1|tr -s ' ' | cut -d ' ' -f4`" MB Free
ls -Al /lib/modules/2.6.33.2/kernel/drivers/video/nvidia.ko
lsmod | grep 'nvidia'
depmod -a
sync
rmmod nouveau
rmmod ttm
rmmod drm_kms_helper
rmmod drm
rmmod i2c_algo_bit
rmmod agpgart
modprobe agpgart
modprobe i2c-core
modprobe nvidia

Please copy and paste the above results into a post.

If the ls -Al... outputs a line with size, date and ends with nvidia.ko,
and the last modprobe nvidia returns empty (it worked), then restart X, without running xorgwizard and if X still won't start, please repeat the report-video from the CL again, doing that before running xorgwizard and post the new report-video-full.gz.
Thanks,
TazOC

[ICPUG]

Thanks for the info Tazoc, re the Intel driver.

Here are the results of my further tests (with 5.0.0a).

My laptop has the Intel 855 chipset and a Synaptics touchpad.

Without any kernel boot parameters I get the black screen if I select choose XOrg autoconfigure or choose the intel driver. It eventually goes to the command line which allows recovery via the Xorgwizard and selection of vesa driver (nice touch Tazoc).

I setup my frugal install to have a kernel parameter i915.modeset=1

If I choose Probe from the Xorg setup it fails and you have to shut down the PC to recover.

If I choose XOrg autoconfigure it works! Also my touchpad allows me to tap a mouse click, which surprised me.

If I choose Xorg and choose intel it works. This time the touchpad does NOT allow me to tap a mouse click, as expected. Using the mouse config wizard I select enable touchpad tapping. I reboot. The xorg.conf file has changed so that maxtaptime is 220 BUT I still cannot tap a click. I appreciate this is not an intel driver problem. I just wanted to report that it would seem the xorg.conf is not being fully recognised (although it does have intel as its driver).

Summary:
1) With Intel855 you must have the kernel parameter i915.modeset=1 and you must autoconfigure Xorg or select the intel driver.
2) I still don't understand when Xorg uses an xorg.conf file and when it doesn't!

Note: i915.modeset=1 also gets Ubuntu 10.4 to boot up.

Tazoc - even though I have solved my problem without the need of the i810 driver i am still interested in where the drivers in the choose list are located and how the list is created - just so I understand the workings of this Puppy.

[Jim1911]

Hi TazOC,

This is the output of the code you wanted to run. Still doesn't work and had to revert back to nv. The attached report was run before I ran xorgwizard again. I did use the ppm to uninstall the pet before I installed it again.

Hope this helps,
Jim

Code: Select all

For Console QuickStart type-> phelp <Enter>  Software versions-> ver <Enter>
<root> ~
bash-3.00# echo "`df -m / |tail -n1|tr -s ' ' | cut -d ' ' -f4`" MB Free
752 MB Free
<root> ~
bash-3.00# ls -Al /lib/modules/2.6.33.2/kernel/drivers/video/nvidia.ko
-rw-r--r-- 1 root root 10815854 2010-06-13 01:20 /lib/modules/2.6.33.2/kernel/drivers/video/nvidia.ko
<root> ~
bash-3.00# lsmod | grep 'nvidia'
nvidia               9841383  0 
agpgart                19112  1 nvidia
i2c_core               11701  2 nvidia,i2c_i801
<root> ~
bash-3.00# depmod -a
<root> ~
bash-3.00# sync
<root> ~
bash-3.00# rmmod nouveau
ERROR: Module nouveau does not exist in /proc/modules
<root> ~
bash-3.00# rmmod ttm
ERROR: Module ttm does not exist in /proc/modules
<root> ~
bash-3.00# rmmod drm_kms_helper
ERROR: Module drm_kms_helper does not exist in /proc/modules
<root> ~
bash-3.00# rmmod drm
ERROR: Module drm does not exist in /proc/modules
<root> ~
bash-3.00# rmmod i2c_algo_bit
ERROR: Module i2c_algo_bit does not exist in /proc/modules
<root> ~
bash-3.00# rmmod agpgart
ERROR: Module agpgart is in use by nvidia
<root> ~
bash-3.00# modprobe agpgart
<root> ~
bash-3.00# modprobe i2c-core
<root> ~
bash-3.00# modprobe nvidia

[tazoc]

Tazoc - even though I have solved my problem without the need of the i810 driver i am still interested in where the drivers in the choose list are located and how the list is created - just so I understand the workings of this Puppy.

Sure, xorgwizard scans the directories drivers, drivers-backup and drivers-alternate in /usr/lib/xorg/modules/. The code is in LHP's /usr/sbin/xorgwizard-puppy, search for my comment date code 100515 (YYMMDD).

LHP's xorgwizard is actually 3 files:

* xorgwizard the front end (text mode) menus for commonly used (Option 2 calls xorgwizard-puppy) and proprietary drivers (if installed) and an Options/Tools menu,

* xorgwizard-puppy, based on Woof/Quirky's xorgwizard and

* xorgwizard-puppy-alt (see below)

The Autoconfigure option in LHP's xorgwizard creates a skeleton xorg.conf with a hardware profile comment #PuppyHardwareProfile=${PROFILECHIP}${PROFILEMONITOR}" using the short script /usr/sbin/xorgwizard-puppy-alt from BK's blog a while back. With recent hardware Xorg will even start without any xorg.conf at all, though /usr/bin/xwin still checks for at least the skeleton file, and keyboard layouts and other input devices still need it to save their configuration. Proprietary drivers also need xorg.conf.

Hi TazOC,

This is the output of the code you wanted to run. Still doesn't work and had to revert back to nv. The attached report was run before I ran xorgwizard again. I did use the ppm to uninstall the pet before I installed it again.

Hope this helps,
Jim

Yes, the new X log in report-video-full indicated libwfb.so (from the NVIDIA package) failed to load. I rebuilt the pet with the version of that library from xorg-xserver. Should work now... crossing my fingers. I updated my earlier post with new links and more info.
-TazOC

[tazoc]

Here is the proprietary ATI Catalyst 10.6 driver PET package for Lighthouse Pup 5.00. Includes catalyst control center, full GLX/3D support and updated Lighthouse Video Wizard. Will not work in Quirky/Lucid or other Puppies as it was compiled with xorg-xserver 1.7.7 and mesa-7.8.1. Good idea to boot LHP with pfix=ram first to try it out with your hardware, especially if you have a full install.

You'll need at least 120M free space, and one of these Supported Chipsets to use the pet.

Be sure to backup your pupsave before installing this pet. Can be uninstalled with Puppy Package Manager, though it may be necessary to reboot when switching from the proprietary driver back to an Xorg driver.

ATI_Catalyst-10.6-LHP-k2.6.33.2-xserver-1.7.7.pet 34M md5.txt

Part of the size is 13M of Qt4 libs used by the CCC--which looks and feels more refined than it was in Catalyst 9.9. For me this Catalyst also fixed an annoying bug with the graphics in the Stellarium add-on when used with the Xorg radeon driver and DRI, so now I can enjoy Stellarium with hardware acceleration.

-TazOC

[Jim1911]

Hi TazOC,

The new Nvidia driver is working great. It did trash my test save file, however, it worked great with a new save file. Nice that running xorgwizard will now provide the latest driver as a selection.

Thank you for this driver and all of the other cool software that you keep adding to Lighthouse.

Jim

[ICPUG]

Many, many thanks Tazoc for the explanation of the workings of Xorg wizard in LHP. That should keep me busy for a while in improving my education.

This LHP is going to be a fixture on my laptop now as the Puppy to use when you want a bit more than the basic Puppy (in my case Wine, Open Office and the ability to play as many video codecs as possible).

[Q5sys]

so I take about a month off and i'm left in the dust. lol
Guess I need try to catch up on whats been done through the A version into the B version.
TazOC, any ideas on when the KDE expansion will be completed? A bunch of my apps use a ton of KDE libs, just looking forward to when I can jump in the deep end with v5 and splash around with it.
(no rush, just curious)

[tazoc]

so I take about a month off and i'm left in the dust. lol
Guess I need try to catch up on whats been done through the A version into the B version.
TazOC, any ideas on when the KDE expansion will be completed? A bunch of my apps use a ton of KDE libs, just looking forward to when I can jump in the deep end with v5 and splash around with it.
(no rush, just curious)

Hi Q5sys,
Sure, I found that KDE 4 was unstable with the radeon Xorg driver, on my hardware, at least--and I wasn't sure if that was the cause or if something else amiss. But since I compiled the ATI Catalyst driver and switched over to it, KDE 4 is now very stable, even with desktop effects and shadows enabled. The last piece I've been working on is the latest Moblock IP range blocking packages, that work well with KDE. It requires an updated iptables which is in the base ISO. So I'm debugging LHP 5.00 C with hplip-3.9.12 HP Scanner Driver (thanks to Jim1911), iptables-1.4.7, libnl-1.1 (thanks to BK), Flash-10.1.53.64, atk-1.30.0, gslapt-0.5.3b, PPM from Spup 0.2, SeaMonkey 2.05 and a few bugfixes. I hope to release that next week and then Mariner and a large KDE 4.4.4 SFS with many updates.
-TazOC

[Q5sys]

Sure, I found that KDE 4 was unstable with the radeon Xorg driver, on my hardware, at least--and I wasn't sure if that was the cause or if something else amiss. But since I compiled the ATI Catalyst driver and switched over to it, KDE 4 is now very stable, even with desktop effects and shadows enabled. The last piece I've been working on is the latest Moblock IP range blocking packages, that work well with KDE. It requires an updated iptables which is in the base ISO. So I'm debugging LHP 5.00 C with hplip-3.9.12 HP Scanner Driver (thanks to Jim1911), iptables-1.4.7, libnl-1.1 (thanks to BK), Flash-10.1.53.64, atk-1.30.0, gslapt-0.5.3b, PPM from Spup 0.2, SeaMonkey 2.05 and a few bugfixes. I hope to release that next week and then Mariner and a large KDE 4.4.4 SFS with many updates.
-TazOC

Sweet, I'll work with than then and move forward. I compilied the newest intel driver for A... but that was back before we figured out the problem. Once I get C up and running I'll recompile it and if everything works smoothly, i'll upload it for everyone who is using Intel Gfx.

[tazoc]

I compilied the newest intel driver for A... but that was back before we figured out the problem. Once I get C up and running I'll recompile it and if everything works smoothly, i'll upload it for everyone who is using Intel Gfx.

That sounds good, what website has the source you used? Was it http://intellinuxgraphics.org/install.html and http://xorg.freedesktop.org/archive/ind ... r/?C=M;O=D? If and when you recompile the Intel drivers it would be great if you could make a few notes to share in case you're away and we might want to repeat the task.
Thanks,
TazOC