(old)Puppy Linux Discussion Forum

There is a newer release here:
http://www.murga-linux.com/puppy/viewto ... 846#710846

Lighthouse 64 6.01 B release notes | ISOs | SFS add-ons | What is an SFS?

Please refer to latest release notes for news, features, bugs, etc. To eliminate the startup music, click the File System icon --> Startup. Then drag-n-drop the login-audio icon into the nearby DisabledItems folder, selecting Move when prompted.

Also please re-size any screenshots to 600 pixels wide or less and wrap descriptions to keep posts from scrolling horizontally. Larger images can be linked. Thanks!

[Edit 2013.5.11]: The Remaster Lighthouse CD in the Setup menu doesn't work yet; will be fixed for the next release.

A frugal install is recommended, (with a new save file due to the new kernel and Xorg.) You can type ram at the LiveCD boot menu, then at shutdown you'll be able to save your session to a new save file.

Getting Started and System Requirements | Display drivers in LH64

To run Firefox as root, click Menu -> Setup -> Choose Default Browser -> Firefox (root). However I don't recommend doing so. Much safer to just run FF as default user spot, saving to the Downloads folder, then click on the Downloads desktop icon and move files elsewhere as needed.

With large downloads, it is best to use wget in a terminal, or click Menu -> Internet -> Pwget downloader and copy and paste in the URL.

-TaZoC

From the 515 thread where you announced this one...

tazoc wrote:I tried to update to KDE 4.9.3.sfs but it was sluggish and Qt-4.8 didn't work properly with ROX-Filer, so I updated the earlier KDE 4.6.5-F to G which includes Qt-4.7.

Will you release the KDE 4.9.3 sfs along with the QT 4.8 on the LHP side for those of us who dont want to bother with rox?
I've been trying to get away from using it as my normal file manager... and a clean break might be whats needed.

I was hoping to get time this weekend to try to build KDE 4.10.1 from Alien's Ktown repo... but sadly some things came up and I wont be able to. I'm away the next two weekends... but hopefully one of these days I'll get around to it.
sigh... I always have so many things I want work on and not enough time... I just need to win the lottery already so I can focus more on this stuff. haha

Q5sys wrote:Will you release the KDE 4.9.3 sfs along with the QT 4.8 on the LHP side for those of us who dont want to bother with rox?
I've been trying to get away from using it as my normal file manager... and a clean break might be whats needed.

They are at http://www.lhpup.org/testing/L64-601/

Qt-4.8.2 is included in 4_KDE-4.9.3-x86_64-3.sfs, however a separate Qt-4.8.2 SFS is also there. The KDE SFS requires Gvfs-1.12.3-x86_64-2.sfs at http://www.lhpup.org/sfs/601-x86_64

I wasn't happy with that build of KDE-4.9.3 so I'm using 4.6.5 myself...
-TaZoC

I should begin by saying that the system is in the tradition of prior LightHouse64s; namely very responsive and fully featured.

The opening FirstTUN tuility is very useful as well as is a good launch for newb as well as experienced users. It is a great intuitive manner to give the system a single place to address much/most of its needs for OOTB. And the traditional Update desktop service is also reachable via the FristRUN, if needed. A great single screen. Thanks for maintaining this version.

I've been having problems with video issues on a desktop which has motherboard's built-in nVidia adapter.

Problems (each of these yields a system with no possible way to get to the console)

1. The system does not wake up after leaving it overnight.
2. Booting with "lhp pfix=sfsauto noveau caused the system to lose video after hour of use.

Attempted to resolve by booting again with noveau parm and using Update to get nViidia's support. Then, I Got this message when using desktop's Update and selecting nVidia (shown below).

Anyone else with nVidia on the MB? Or any advice to get a system which has stable video and will resume after sitting overnight?

The Update subsystem ALSO offers the get_nVidia system addition also. Could I be using the wrong path to alleviate the problem?

I did read the help information available.

gcmartin wrote:I did read the help information available.

3 things:

#1 Like every Nvidia driver package before... you have to disable the Nouveau driver before installing the full Nvidia package.

#2 the get nvidia package is a script for compiling the newest driver. Like every puppy in existance you need the devx sfs loaded in order to compile anything. also see #1 You need the kernel sources as well since you are trying to compile a kernel module. Compiling graphics on puppy has always required the devx and the kernel surce. This is nothing new.

Also, make sure your trying to install the correct driver for the nvidia hardware you have! I know in the previous LHP thread you were having problems with the ATI driver working because you were installing the wrong driver.
Check the Nvidia website to check to see what driver you need.

Edit: Spelling and Grammar correction.

gcmartin wrote:Booting with "lhp pfix=sfsauto noveau caused the system to lose video after hour of use.

Hi gcmartin,
Thank you for the screen shots and kind words! Both screens indicated that nouveau module is still loaded.

HardInfo shows your video card is: GeForce 6150SE

It is not listed in Nvidia-glx-310.40-supported.txt for Nvidia-310.40 driver, so might need to use getnvidia-0.8-64.pet to compile with Devx.

As indicated in the release notes, please boot with lhp blacklist=nouveau (careful with spelling, nouveau has 2 'u'.)

If still no luck, type lhp nomodeset pfix=vesa at the boot menu. Either method will ensure that the nouveau kernel module is not loaded--required for the Nvidia driver to work.

Attempted to resolve by booting again with noveau parm and using Update to get nViidia's support. Then, I Got this message when using desktop's Update and selecting nVidia (shown below.)

As Q5sys noted, getnvidia-0.8-64.pet from shinobar compiles the driver from Nvidia's web site and requires the Devx-L64_601.sfs loaded first. It will not work on first boot, must save your session first. All of the status messages in the dialog must end with '- OK'.

Please look at this thread:
http://www.murga-linux.com/puppy/viewtopic.php?t=72405

Hope that helps,
TaZoC

tazoc wrote:HardInfo shows your video card is: GeForce 6150SE

It is not listed in Nvidia-glx-310.40-supported.txt for Nvidia-310.40 driver, so might need to use getnvidia-0.8-64.pet to compile with Devx.

Since this is now the 2nd time within the past year that this has come up in the Lighthouse Thread... Let this be a reminder to EVERYONE.
Check to see if your hardware is supported by the drivers in the repo before you install it!
Installing a driver that does not support your hardware will not work.
TazOC has supplied this information on his website and it can also be found on the offical Nvidia website.

Also please read the release notes TazOC has provided. You may find the answer to your question in there! http://www.lhpup.org/release-lhp.htm

Love using xfce 4.10. Started up nice, and after going to wizard-puppy was able to get a
video driver that worked great on the first try. The new start up music was a surprise.

I notice several issues:

1- When I pull a link from the menu on to the desktop, it is removed from the menu.

2- I can close firefox by using the x in the top right hand corner. if I have more than one
window up. If I don't, I have to use the file menu and press quit.

3-I don't see the sensor plugin in the set of XFCE panel plugins, but I know one is available.

It just keeps getting better and better.

Pete

nvidia driver needs to be updated. Bug allows an attacker to run remote code on the system as root.

This vulnerability has been present since NVIDIA driver version 195.22. The overflow is fixed in 304.88, 310.44, 313.30, and all drivers newer than those versions.

http://www.kb.cert.org/vuls/id/771620

I'm busy the rest of this week and next so I doubt I'll have time to build it. I just got back from being away for a while... and I've got a ton of things to catch up on at work.

Anyone else noticing high CPU usage from /usr/libexec/gvfsd-metadata?
it's burning at 100% on one core of my quad core chip.

I see high cpu useage at times. I did not check to see what file was doing it.
I will try and watch that file now.


;pete

Hard Info Report
Video Info Report

Obligatory Screen capture: (click for full resolution : 3840x2160 pixels)


Couple Things,

1.) Why does SuperKaramba only see 2 cores? Is it limited to physical cores and not total cores? Htop, and gkrellm both show 4 cores.

2.) When trying to make my first save file it refused to read my ext4 drive. It read my first 5 ntfs drives... but wouldnt read my 6th drive which was an ext4. Thats where I wanted to save my save file (yes I know I can move it later), but it means I cant use ext4 for the file system in my save file.

3.) Flash gives some glitches every once in a while. A flash image will 'bleed through' onto other tabs.
I've noticed this in Opera, Firefox, and Chrome

4.) Finally got 601 set up properly now. gvfs still seems to be running VERY high at times.
Built the latest Nvidia Short Branch Driver and got a kernel mismatch gcc error (said current gcc was 3.7 and kernel was built with 3.6). Driver works well though. http://puppy-linux.org/lhp601/lhp601-error.jpg

SFS Package Nvidia 313.30 LHP 601 Driver
MD5 = 94b13d9127eb57bf73e5e5b16c4786b0

5.) I've got a bunch of packages to upload when I get time later. Hopefully by tomorrow evening I'll have them all uploaded and I'll post links.

6.) This is still multi-lib right? I haven't peeked under the hood yet... but I was contemplating trying to build the latest toolchain, so I'd need to know that before I even bother to get started.

Hi TaZoC,

Sorry, it's taken me so long to take a look at your latest. I've really enjoyed checking it out. I keep being amazed at the superior quality of your distributions and this one is hard to beat.

Thanks for continuing support for Bibletime and theWord. I have been able to get Bible Analyzer and e-Sword to work also. You may want to include installers for them as well as for theWord.

I've noted two problems:
1. The nvidia driver cannot find the kernel although devx is installed.
2. Any actions that access drives takes an unusual amount of time. For example clicking on drives using KDE desktop took about 1.5 minutes. I encountered the same problem with Fatdog64-600 and it is apparently hardware dependent. I think that Jamesbond corrected the problem by replacing "blkid" with "disktype" although he may have made other changes.

Thank you again for another super distribution.
Jim

Jim1911 wrote:1. The nvidia driver cannot find the kernel although devx is installed.
2. Any actions that access drives takes an unusual amount of time. For example clicking on drives using KDE desktop took about 1.5 minutes. I encountered the same problem with Fatdog64-600 and it is apparently hardware dependent. I think that Jamesbond corrected the problem by replacing "blkid" with "disktype" although he may have made other changes.

Thank you again for another super distribution.
Jim

Hi Jim,
Thank you for the feedback and support.

#1 - Please try getnvidia-0.8-64:
http://www.murga-linux.com/puppy/viewtopic.php?t=72405

I think I should remove the pre-compiled Nvidia-glx-310.40-k3.7.10-L64-1.pet from Lighthouse Update if that is what you tried. Keep in mind neither will work if your card is not on the http://www.lhpup.org/download/update/L6 ... ported.txt

#2 - I haven't been able to reproduce. I'm assuming you're using KDE-4.6.5 SFS. I did observe similar problems with the KDE-4.9.3 in testing only. I will ask Jamesbond what his fix was.

@Q5sys,
Lighthouse64 has no multilib/compat32 compiler pkgs. Wine is 32-bit but not multilib, only 32-bit. The toolchain in the devx is straight from Slackware64-14.0 and only 64-bit.

Thanks for the Nvidia SFS. I can't test it, only have AMD video, anyone else can try it?

I will work on the other bugs you found. Yes, Sidebar only sees 2 cores, more won't fit in the graphics. You can disable or delete the symlink in /Startup (or /Autostart in KDE.)

Gvfs is uses way too many processes, but not CPU usage for me. Maybe it chokes on ntfs? I don't really know enough about it. If you don't need KDE or Xfce, then unload the Gvfs SFS. Openbox doesn't need it.

Regards,
TaZoC

tazoc wrote:#2 - I haven't been able to reproduce. I'm assuming you're using KDE-4.6.5 SFS. I did observe similar problems with the KDE-4.9.3 in testing only. I will ask Jamesbond what his fix was.

The problem with excess time to examine drives was also observed using jwm and other WM. It is probably a hardware dependent problem, although other users with similar hardware should have the same problem.

Regards,
Jim

Jim1911 wrote:

tazoc wrote:#2 - I haven't been able to reproduce. I'm assuming you're using KDE-4.6.5 SFS. I did observe similar problems with the KDE-4.9.3 in testing only. I will ask Jamesbond what his fix was.

The problem with excess time to examine drives was also observed using jwm and other WM. It is probably a hardware dependent problem, although other users with similar hardware should have the same problem.

Regards,
Jim

Do you mean 'Drives' the program in the menu... or opening a drive in Rox?
If you mean the 'Drives' Program, then i can confirm this as well. Ill debug later when i get home.
I figured it was just me with my millions hdisks for why it was slow.

Q5sys wrote:

Jim1911 wrote:

tazoc wrote:#2 - I haven't been able to reproduce. I'm assuming you're using KDE-4.6.5 SFS. I did observe similar problems with the KDE-4.9.3 in testing only. I will ask Jamesbond what his fix was.

The problem with excess time to examine drives was also observed using jwm and other WM. It is probably a hardware dependent problem, although other users with similar hardware should have the same problem.

Regards,
Jim

Do you mean 'Drives' the program in the menu... or opening a drive in Rox?
If you mean the 'Drives' Program, then i can confirm this as well. Ill debug later when i get home.
I figured it was just me with my millions hdisks for why it was slow.

Drives program and also the time that it takes to access any drives ie. Using JWM or any other WM, it takes excessive amount of time for drive icons to show, also true with the program pmount. As I stated before the same problem occurred with Fatdog64-600 and Jamesbond corrected the problem. See here.

Regards,
Jim

tazoc wrote:#1 - Please try getnvidia-0.8-64:
http://www.murga-linux.com/puppy/viewtopic.php?t=72405

I think I should remove the pre-compiled Nvidia-glx-310.40-k3.7.10-L64-1.pet from Lighthouse Update if that is what you tried. Keep in mind neither will work if your card is not on the http://www.lhpup.org/download/update/L6 ... ported.txt

It does not work, I get an error message that makes no sense because I have plenty of ram and swap space.

Jim,
Try the nvidia sfs i posted on the first page. let me know if it works for you.

Q5sys wrote:Jim,
Try the nvidia sfs i posted on the first page. let me know if it works for you.

Sorry, I can't get it to work. Also, I downloaded and tried to compile the latest driver "310.44" for my card and had no success with that either, since there appears to be a kernel mismatch.

Regards,
Jim