Lighthouse 64 602 Beta2 with GIMP-2.8.4 (6-29-2013)
173 Processes?
Is it normal for GKrellM to show 173 processes?
EDIT: Powered up fresh this morning & before opening any windows it shows 132 processes. Is that normal?
Last night I looked and saw what appeared to be print processes (daemons) listed but there were no print jobs active active. Lots of "0%" entries in Pprocess, same now.
Or might that explain why I'm having trouble with VLC playing MP4 files - starting OK then audio drops out and video gets jittery then completely garbled?
Only Seamonkey was open with one Web page (this one), the main email page, and one compose page open.
EDIT: Powered up fresh this morning & before opening any windows it shows 132 processes. Is that normal?
Last night I looked and saw what appeared to be print processes (daemons) listed but there were no print jobs active active. Lots of "0%" entries in Pprocess, same now.
Or might that explain why I'm having trouble with VLC playing MP4 files - starting OK then audio drops out and video gets jittery then completely garbled?
Only Seamonkey was open with one Web page (this one), the main email page, and one compose page open.
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
Re: spacefm without gamin
yea ksnapshot uses it. I had to run the following to get it to run:tazoc wrote:Here is the spacefm file manager re-compiled to use inotify (kernel support) instead of gamin.
This Pet is only for Lighthouse64 602 and does not include the other pkg data, icons, menu entries, etc., as they are already included in 602.
http://www.lhpup.org/testing/L64-602/sp ... update.pet
Re: High core usage:
http://freebsd.1045724.n5.nabble.com/Ho ... 87726.htmlSo maybe this change to spacefm will help, at least if spacefm was responsible. There are other KDE services which may use gamin:<gam_server> is not a "system-level" service per se : it is not started via a well-defined /etc/rc.d/xxx or /usr/local/etc/rc.d script.
Contrary to that, it is a "user-level" service started on-demand by other mechanisms, most often desktop related. Like polkit stuff.
Therefore, it is not <gam_server> per se which is responsible for intensive CPU consumption, but rather whatever mechanism services higher in the stack that are launching it on their behalf to monitor files/directories activity.
polkit, akonadi, nepomuk, strigi, virtuoso, as well as apps like dolphin and konqueror.
Code: Select all
export $(dbus-launch)
@edoc, is lots of these what you refer?
Edit (Today, at 11am): I have seen lots of these as well. I have wondered if they are present from the use of one/more browsers I have. Up until you mentioned it, I had not paid much attention to this, only noting there presence without attributing it to a base element ni the system. I run 2 browsers: Chrome and FF. I used Chrome to define a LAN printer via CUPs and I have 4 add-ons in FF.
Although it probably wont happen this week, I think it would be prudent to test a full Mariner to see what and where the elements begin to show up. This would serve to identify which component is the contributor. As far as I can tell, I have NOT seen case to whether the behavior of these elements have a positive or negative system impact....but they may.
Anyone else know anything about these PID elements?
Code: Select all
o
o
o
1284 1 root S 11128 0.2 1 0.0 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
12673 1 root S 11124 0.2 0 0.0 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
13007 1 root S 11124 0.2 1 0.0 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
14519 1 root S 11124 0.2 0 0.0 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
17297 1 root S 11124 0.2 0 0.0 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
o
o
o
Although it probably wont happen this week, I think it would be prudent to test a full Mariner to see what and where the elements begin to show up. This would serve to identify which component is the contributor. As far as I can tell, I have NOT seen case to whether the behavior of these elements have a positive or negative system impact....but they may.
Anyone else know anything about these PID elements?
Last edited by gcmartin on Thu 03 Oct 2013, 14:59, edited 3 times in total.
FireFox Update 24 Doesn't Load
I'm getting a pop-up to upgrade to Firefox 24.
If I click OK it appears to run but never accomplishes anything so I close the window.
Does this update need to be done a different way?
If I click OK it appears to run but never accomplishes anything so I close the window.
Does this update need to be done a different way?
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
Yes that many processes are not anything to worry about. And they aren't 'print' processes in the way you think about 'printing' things. To explain this would be WAY beyond the scope of this thread. dbus is a very low level part of a linux distro. It's not something that can explained throughly in a simple explanation.edoc wrote:Is it normal for GKrellM to show 173 processes?
EDIT: Powered up fresh this morning & before opening any windows it shows 132 processes. Is that normal?
Last night I looked and saw what appeared to be print processes (daemons) listed but there were no print jobs active active. Lots of "0%" entries in Pprocess, same now.
Read the dbus man pagegcmartin wrote:Anyone else know anything about these PID elements?
Thanks Q5sys ...
I just remembered, I am still running under generic VESA as the problem with finding the proper video driver was set-aside for other matters when I first loaded LH64-602b.
Perhaps that is where the instability in VLC lies?
I just remembered, I am still running under generic VESA as the problem with finding the proper video driver was set-aside for other matters when I first loaded LH64-602b.
Perhaps that is where the instability in VLC lies?
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
Upgrade of FF when the offer presents itself in LH64
There is a Menu item which can assist all who need to take advantage of the FF Upgrade:
- Go to Menu>Internet>Firefox Update Help
- Click the Firefox (root) button to Open FF under the root ID (instead of Spot)
- When this FF opens, go to Help>About Firefox
- On the screen which pops up, Under the version number, FF will show the upgrade status/alert. Click if necessary.
v4l2-ctl?
I am trying to get a Dazzle DVC-100 analog to digital interface to work.
One of the steps in the Linux instructions I found is:
Console reports: "command not found"
ALSO ...
The instructions for VLC settings include \:
How should I proceed, please?
Thanks!
One of the steps in the Linux instructions I found is:
Code: Select all
v4l2-ctl --list-inputs
ALSO ...
The instructions for VLC settings include \:
However, the only Capture modes offered under Capture Device are "PVR" and "Desktop"Media -> Stream -> Capture Device:
Capture Mode = Video for Linux 2
How should I proceed, please?
Thanks!
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
Re: v4l2-ctl?
v4l2 is NOT included in LHP. And to be honest, I only know if it as a 32bit component within the 32bit compat packages.edoc wrote:I am trying to get a Dazzle DVC-100 analog to digital interface to work.
One of the steps in the Linux instructions I found is:Console reports: "command not found"Code: Select all
v4l2-ctl --list-inputs
I dont recall ever seeing a native 64bit package for it.
EDIT:
I stand corrected. You can 'try' this package. It may or may not work for you.
http://slackbones.org/pets/v4l-utils-0.8.8-x86_64-2.txz
EDIT2: After you install that run the following from the command line.
Code: Select all
ldd /usr/bin/v4l2-ctl
You are amazing!
Thanks!
The menu item appeared in Multimedia and opened the V4L2 Test Bench.
The output of your console command:
failed as "mute" is not an available "control".
Help doesn't show anything about "mute" in the audio section of v4l2-ctl
Now onward to the VLC settings ...
Thanks!
The menu item appeared in Multimedia and opened the V4L2 Test Bench.
The output of your console command:
bash-4.1# ldd /usr/bin/v4l2-ctl
linux-vdso.so.1 (0x00007fff61e00000)
libv4l2.so.0 => /usr/lib/libv4l2.so.0 (0x00007f195a9a8000)
libv4lconvert.so.0 => /usr/lib/libv4lconvert.so.0 (0x00007f195a730000)
librt.so.1 => /lib/librt.so.1 (0x00007f195a528000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007f195a220000)
libm.so.6 => /lib/libm.so.6 (0x00007f1959f20000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007f1959d08000)
libc.so.6 => /lib/libc.so.6 (0x00007f1959948000)
bash-4.1# ldd /usr/bin/v4l2-ctl
linux-vdso.so.1 (0x00007fff61e00000)
libv4l2.so.0 => /usr/lib/libv4l2.so.0 (0x00007f195a9a8000)
libv4lconvert.so.0 => /usr/lib/libv4lconvert.so.0 (0x00007f195a730000)
librt.so.1 => /lib/librt.so.1 (0x00007f195a528000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007f195a220000)
libm.so.6 => /lib/libm.so.6 (0x00007f1959f20000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007f1959d08000)
libc.so.6 => /lib/libc.so.6 (0x00007f1959948000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00007f1959728000)
libjpeg.so.8 => /usr/lib/libjpeg.so.8 (0x00007f19594e8000)
/lib64/ld-linux-x86-64.so.2 (0x00007f195abb8000)
<root> ~
libpthread.so.0 => /lib/libpthread.so.0 (0x00007f1959728000)
libjpeg.so.8 => /usr/lib/libjpeg.so.8 (0x00007f19594e8000)
/lib64/ld-linux-x86-64.so.2 (0x00007f195abb8000)
<root> ~
Code: Select all
v4l2-ctl - C mute
Help doesn't show anything about "mute" in the audio section of v4l2-ctl
Now onward to the VLC settings ...
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
OpenShot - Status
Current version is 1.43
Based on this page:
http://www.openshotvideo.com/2013_09_01_archive.html
... the best-case scenario for OpenShot 2.0 is some time in December ... maybe.
That's a long ways away ... and probably will not happen ... more like January of February according to typical major-revision history ... sigh.
Maybe I will try again to get Avidemux to play nicely ... or hope someone gets OpenShot 1.43 working for LH64-602b?
BTW: Any imminent updates to LH-64 or Raring?
Based on this page:
http://www.openshotvideo.com/2013_09_01_archive.html
... the best-case scenario for OpenShot 2.0 is some time in December ... maybe.
That's a long ways away ... and probably will not happen ... more like January of February according to typical major-revision history ... sigh.
Maybe I will try again to get Avidemux to play nicely ... or hope someone gets OpenShot 1.43 working for LH64-602b?
BTW: Any imminent updates to LH-64 or Raring?
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
Arista 2-Click Transcoder?
I have an 11g file from converting a VHS tape to AVI via a Dazzle box & VLC.
I really need to reduce that footprint!
The Arista transcoder app for Linux has been recommended as simple and reliable.
A brief review here:
http://www.makeuseof.com/tag/arista-two ... ool-linux/
Source code:
http://www.transcoder.org/downloads/
Anyone tried this in LH64-602b?
I really need to reduce that footprint!
The Arista transcoder app for Linux has been recommended as simple and reliable.
A brief review here:
http://www.makeuseof.com/tag/arista-two ... ool-linux/
Source code:
http://www.transcoder.org/downloads/
Anyone tried this in LH64-602b?
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
PuppyPin and PuppyPinLHP
Not quite sure if this is a bug or a feature.
In the default window manager of Puppy, when you drag an icon to the desktop or do some other modification, those modifications are put in the file /root/Choices/ROX-Filer/PuppyPin.
LHP does the exact same thing.
However, the file that seems to be what creates the desktop is actually /root/Choices/ROX-Filer/PuppyPinLHP. So, when you reboot, the desktop returns back to the original setup (losing your changes), unless you manually copy the PuppyPin file to the PuppyPinLHP file.
Thanks
In the default window manager of Puppy, when you drag an icon to the desktop or do some other modification, those modifications are put in the file /root/Choices/ROX-Filer/PuppyPin.
LHP does the exact same thing.
However, the file that seems to be what creates the desktop is actually /root/Choices/ROX-Filer/PuppyPinLHP. So, when you reboot, the desktop returns back to the original setup (losing your changes), unless you manually copy the PuppyPin file to the PuppyPinLHP file.
Thanks
Backlight with LHP 64 602 beta 2
My friend asked me to update her Lighthouse. Currently she has LHP 443 on her Gateway NV78. It is old and I want to update her to the x64.version.
Unfortunately this lhp 64 602 beta 2 version allows intel to turn the backlight off at start up. This does not happen with lhp 443. I also found that lupo 528 also keeps the backlight on. Is there any way to get LHP 64 602 to turn the backlight on?
I figured out that I could attach an external monitor to her laptop to change the settings. I found workarounds that are temporary, that needs to be fixed each time the computer is turned on. However my friend is not geeky enough to do it each time.
Any help would be greatly appreciated.
Pete.
Unfortunately this lhp 64 602 beta 2 version allows intel to turn the backlight off at start up. This does not happen with lhp 443. I also found that lupo 528 also keeps the backlight on. Is there any way to get LHP 64 602 to turn the backlight on?
I figured out that I could attach an external monitor to her laptop to change the settings. I found workarounds that are temporary, that needs to be fixed each time the computer is turned on. However my friend is not geeky enough to do it each time.
Any help would be greatly appreciated.
Pete.
Hi @Pete22 and @Dancytron
This is NOT a specific answer, but more of a request to understand your environment.
Would a remaster at the time of these kinds of changes automatically save these changes by selecting all and ONLY "default" answers OR is some manual intervention required to save these system state changes? (Seems that in the past, I have had some of state changes lost unless I specifically knew what and where state changes were made and made manual adjustments during the remaster in order to re-create the existing (and running) system.)
An old idea
I have asked this several years ago and @Jamesbond responded with some additions in save sessions and remaster which are very clever. But, I still have wondered if there is a tool in Puppyland, which will create an ISO from your presently running system without the user ever needing to answer questions excepting those to indicate where the target ISO is to be created. This negates any element from things missing or left out in a "Presently Running System State" of a genuine remaster to ISO. Maybe this being an option on present Puppyland Remaster utility might address this if seen as a useful means. This would make clear what the outcome would be versus the current discovery process which exist in the present tool where user review is a requirement. This requirement does not address any learning process, rather, has been a source of confusion when the outcome does NOT match what was running.
Not asking for re-write but rather an understanding of whether this is reasonable?
This is NOT a specific answer, but more of a request to understand your environment.
- System run state: Are you running LIveDVD or Frugal or Full install?
- Monitor: Once you make the changes you indicate, are you running from the laptop's monitor or the additional monitor you attach to get the desktop as you want it permanently?
- Filesystem: Upon reboot, is your filesystem changes saved in either location that existed before shutdown (for example are changes lost in PuppyPin file or the PuppyPinLHP file or both?
Would a remaster at the time of these kinds of changes automatically save these changes by selecting all and ONLY "default" answers OR is some manual intervention required to save these system state changes? (Seems that in the past, I have had some of state changes lost unless I specifically knew what and where state changes were made and made manual adjustments during the remaster in order to re-create the existing (and running) system.)
An old idea
I have asked this several years ago and @Jamesbond responded with some additions in save sessions and remaster which are very clever. But, I still have wondered if there is a tool in Puppyland, which will create an ISO from your presently running system without the user ever needing to answer questions excepting those to indicate where the target ISO is to be created. This negates any element from things missing or left out in a "Presently Running System State" of a genuine remaster to ISO. Maybe this being an option on present Puppyland Remaster utility might address this if seen as a useful means. This would make clear what the outcome would be versus the current discovery process which exist in the present tool where user review is a requirement. This requirement does not address any learning process, rather, has been a source of confusion when the outcome does NOT match what was running.
Not asking for re-write but rather an understanding of whether this is reasonable?
To answer your questions.gcmartin wrote:Hi @Pete22 and @Dancytron
This is NOT a specific answer, but more of a request to understand your environment.[
- System run state: Are you running LIveDVD or Frugal or Full install?
- Monitor: Once you make the changes you indicate, are you running from the laptop's monitor or the additional monitor you attach to get the desktop as you want it permanently?
- Filesystem: Upon reboot, is your filesystem changes saved in either location that existed before shutdown (for example are changes lost in PuppyPin file or the PuppyPinLHP file or both?
**Stuff deleted*
Frugal install on hard drive.
It is a Desktop sytem with a single monitor.
My changes are saved automatically to the PuppyPin file, but there are no changes to the PuppyPinLHP file unless I make them manually by copying PuppyPin over the top of PuppyPinLHP.
Firstly I have Precise running quite nicely on my newish HP Pavilion 4108au laptop, which is plagued with a Broadcom 4313GN wireless card. I thought to give the 64bit pups a run, but both Fatdog and the beta Lighthouse don't like playing with the Broadcom wireless.
I have got Fatdog to play after some pampering, but Lighthouse just picks it up and drops it straight away. I've followed the instructions in the FAQ and they seem to work - ie it picks up an ip but only holds it for a couple of seconds before disconnecting, that's what the on screen message says anyway.
I made a new post about this some time ago, asking how to compile the source for the Broadcom driver - however it was too hard so I abandoned that project.
I have now retried the latest Fatdog and Lighthouse (yesterday and today) with the same results - I can configure Fatdog to pick up the Broadcom by starting the wl service, but Lighthouse continually drops the connection when I try the same thing.
Any suggestions about how to get a stable wifi connection with Lighthouse?
I'm running Lighthouse live from USB, with the save file in a NTFS partition on the HDD.
I have got Fatdog to play after some pampering, but Lighthouse just picks it up and drops it straight away. I've followed the instructions in the FAQ and they seem to work - ie it picks up an ip but only holds it for a couple of seconds before disconnecting, that's what the on screen message says anyway.
I made a new post about this some time ago, asking how to compile the source for the Broadcom driver - however it was too hard so I abandoned that project.
I have now retried the latest Fatdog and Lighthouse (yesterday and today) with the same results - I can configure Fatdog to pick up the Broadcom by starting the wl service, but Lighthouse continually drops the connection when I try the same thing.
Any suggestions about how to get a stable wifi connection with Lighthouse?
I'm running Lighthouse live from USB, with the save file in a NTFS partition on the HDD.
Having a little trouble with my internal mic.
Previously using Lighthouse 514 and the mic worked out of the box. Now using 602, and I can't seem to get the thing working.
It's primarily for my Kiddo's school site. There's a little flash gig to record his answers in French so that the teacher can hear his pronunciation.
I've tried playing with the AlsaMixer, m and space to try to activate mic, capture is active, boost is up... in other words, I don't think it's the mixer. Flash settings are also correct, set to allow for the school site in all places.
It's almost like there's something missing in 602 that was in 514... like a lib or a driver.
Can anyone offer a little direction? I can still boot 514 for the time being, but I do want to get 602 mic working. I'm not quite sure how to proceed or what to look for.
Thanks in advance.
Compaq nc6400
64bit dual-core
1 gig ram, 4gig swap
514 frugal, 602 frugal
Need more info, let me know.
Eathray
Previously using Lighthouse 514 and the mic worked out of the box. Now using 602, and I can't seem to get the thing working.
It's primarily for my Kiddo's school site. There's a little flash gig to record his answers in French so that the teacher can hear his pronunciation.
I've tried playing with the AlsaMixer, m and space to try to activate mic, capture is active, boost is up... in other words, I don't think it's the mixer. Flash settings are also correct, set to allow for the school site in all places.
It's almost like there's something missing in 602 that was in 514... like a lib or a driver.
Can anyone offer a little direction? I can still boot 514 for the time being, but I do want to get 602 mic working. I'm not quite sure how to proceed or what to look for.
Thanks in advance.
Compaq nc6400
64bit dual-core
1 gig ram, 4gig swap
514 frugal, 602 frugal
Need more info, let me know.
Eathray
Hi , tazoc
Thank you for your work on LHP 602 and also to everyone helping improve it.
I used LHP 514 and also follow Fatdog releases.
I installed the ATI-13.4-3.8.7..pet from the Updates and I had no luck with my HD 7870 XT and I was expecting it since ati-13.4-3.8.7 pet didn't work for me in Fatdog 620 either ...
In the early days of FD620 , kirk was kind and compiled a 13.3b3-3.8.7 pet which worked . I kept it and -- since there are pets that work from fatdog in LHP ( I successfully installed FBReader) -- I tried to install it in LHP 602 . It did the job , even I think it did not install properly . I had always attached the Devx.sfs at first .
At that point I did a remaster and hoped to keep the working driver in the new remastered LHP. Usually it's the way I do a custom version , I don't like save files... One could lose or corrupt it...
The remastered LHP did not keep the video driver changes and I thought it could be because the pet was meant for fatdog... ( looking inside both pets I saw the structure was different ...)
Today I installed the downloaded driver from AMD site ati-catalyst-13.11-beta6-linux-x86.x86_64 and looking at the log file I executed also /lib/modules/fglrx/make_install.sh then aticonfig --initial , restarted X and there it was , the driver was working . I finally loaded Compiz sfs.
I was glad but again , doing a remastered ISO I couldn't have my custom version with the ati driver in it . Maybe it is because of the way LHP is doing the remaster or maybe it is because the driver must be implemented in a particular way and it must be done a proper pet , I don't know ...
If you have some time , could you compile one of those beta drivers in a pet for LHP 602 , please
I am not able to do it
Thank you for your work on LHP 602 and also to everyone helping improve it.
I used LHP 514 and also follow Fatdog releases.
I installed the ATI-13.4-3.8.7..pet from the Updates and I had no luck with my HD 7870 XT and I was expecting it since ati-13.4-3.8.7 pet didn't work for me in Fatdog 620 either ...
In the early days of FD620 , kirk was kind and compiled a 13.3b3-3.8.7 pet which worked . I kept it and -- since there are pets that work from fatdog in LHP ( I successfully installed FBReader) -- I tried to install it in LHP 602 . It did the job , even I think it did not install properly . I had always attached the Devx.sfs at first .
At that point I did a remaster and hoped to keep the working driver in the new remastered LHP. Usually it's the way I do a custom version , I don't like save files... One could lose or corrupt it...
The remastered LHP did not keep the video driver changes and I thought it could be because the pet was meant for fatdog... ( looking inside both pets I saw the structure was different ...)
Today I installed the downloaded driver from AMD site ati-catalyst-13.11-beta6-linux-x86.x86_64 and looking at the log file I executed also /lib/modules/fglrx/make_install.sh then aticonfig --initial , restarted X and there it was , the driver was working . I finally loaded Compiz sfs.
I was glad but again , doing a remastered ISO I couldn't have my custom version with the ati driver in it . Maybe it is because of the way LHP is doing the remaster or maybe it is because the driver must be implemented in a particular way and it must be done a proper pet , I don't know ...
If you have some time , could you compile one of those beta drivers in a pet for LHP 602 , please
I am not able to do it
- Attachments
-
- fglrx-install_log.tar.gz
- fglrx-install_log
- (826 Bytes) Downloaded 302 times
-
- Display.jpg
- Last AMD driver works
- (87.7 KiB) Downloaded 721 times