Hope that your father is doing well.
Thanks,
Jim
![Very Happy :D](./images/smilies/icon_biggrin.gif)
Yes, review the release notes if you haven't already, try Barry's report-video (I tweaked it for LHP and named it Video Reporting Tool, in the System Menu.) Also give MuppyQuickmount (File Manager/Utility Menu) a whirl. It has one minor bug--it won't repair an ext4 partition and I will fix that for the next release. If you have used TrueCrypt or Wine, see if they are OK.Anything in particular you'd like tested?
MuppyQuickmount looks good too.Video Report: Lighthouse Pup version 4.43-Gu2
Chip description:
Intel Corporation 82852/855GM Integrated Graphics Device
Intel Corporation 82852/855GM Integrated Graphics Device
(II) intel(0): Integrated Graphics Chipset: Intel(R) 855GME
852GM/855GM
Driver used by Xorg: intel
Video mode used by Xorg:
1024x768 Depth: 24
Current xrandr mode: 1024x768 60.1 + 85.0 75.0 70.1 60.0
Code: Select all
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
Code: Select all
(EE) AIGLX error: dlopen of /usr/X11R7/lib/dri/i965_dri.so failed
(/usr/X11R7/lib/dri/i965_dri.so: cannot open shared object file: No such file or directory)
When you do a frugal install, there appears to be less files on the hard drive because of the way that the frugal install works. In reality, there are the same amount of files as if you did a full hard drive install. With a frugal install it keeps most of the files packed together until the system is booted or is running, then its expanded. An example of this is the pupsave file. Its 1 file on your system, but when your system is running that one file actually consists of thousands. It just bundles everything together nicely when you are saving or shutting down.Newuser wrote:Hi everyone I have completed the frugal install and have discovered something (due to a 4 power cuts in my area) with this being a frugal installation there is less code installed on to the hard drive therefore even with a power cut the effects are minimal is this correct?
That file is in MU's Intel pet with a date stamp of 05 Sept 09. Check to see if it is missing and d/l and reinstall xorg-1.6.3-upgrade-vesa-intel-2.8.1-mesa-7.5.1-02.pet(EE) AIGLX error: dlopen of /usr/X11R7/lib/dri/i965_dri.so failed (/usr/X11R7/lib/dri/i965_dri.so: cannot open shared object file: No such file or directory)
TazOC,tazoc wrote:Hi Q5sys,
The only change for Gu2 was to /usr/sbin/xorgwizard to delete a duplicate "#card0driver" comment from xorg.conf.That file is in MU's Intel pet with a date stamp of 05 Sept 09. Check to see if it is missing and d/l and reinstall xorg-1.6.3-upgrade-vesa-intel-2.8.1-mesa-7.5.1-02.pet(EE) AIGLX error: dlopen of /usr/X11R7/lib/dri/i965_dri.so failed (/usr/X11R7/lib/dri/i965_dri.so: cannot open shared object file: No such file or directory)
and recheck /usr/X11R7/lib/dri/i965_dri.so and it's date. Restart X and run Video Reporting Tool in System Menu, then please attach /tmp/root/report-video.gz to your post. If it still isn't working, try re-running xorgwizard from CL.
-TazOC
what happens if you type in a terminal or CL/usr/X11R7/lib/dri/i965_dri.so: cannot open shared object file: No such file or directory
Code: Select all
ls -al /usr/X11R7/lib/dri/i965_dri.so
Code: Select all
bash-3.00# ls -al /usr/X11R7/lib/dri/i965_dri.so
-rwxr-xr-x 1 root root 2569640 2009-09-05 10:35 /usr/X11R7/lib/dri/i965_dri.so
Code: Select all
# This loads dri module (if present)
# Load "dri"
TazOC,tazoc wrote:Q5sys,
Thanks for the reports. The kernel is the same, 2.6.30.5. We're still gettingwhat happens if you type in a terminal or CL/usr/X11R7/lib/dri/i965_dri.so: cannot open shared object file: No such file or directoryAfter the Intel pet I get:Code: Select all
ls -al /usr/X11R7/lib/dri/i965_dri.so
Also I'd like to see the output from 'ver' in a terminal. And you can check /tmp/root/xerrs.log for any file copy/write errors immediately after installing the Intel pet. I suppose you could try disabling DRI by commenting xorg.conf like thisCode: Select all
bash-3.00# ls -al /usr/X11R7/lib/dri/i965_dri.so -rwxr-xr-x 1 root root 2569640 2009-09-05 10:35 /usr/X11R7/lib/dri/i965_dri.so
But I don't understand why i965_dri.so can't be opened. Maybe you could reboot with boot option 'pfix=fsck' to check the file systems for errors.Code: Select all
# This loads dri module (if present) # Load "dri"
-TazOC
Code: Select all
bash-3.00# ls -al /usr/X11R7/lib/dri/i965_dri.so
-rwxr-xr-x 1 root root 2569640 2009-09-05 10:35 /usr/X11R7/lib/dri/i965_dri.so
<root> ~
Code: Select all
bash-3.00# ver
Lighthouse Pup 4.43-Gu2 Mariner-4G
Linux 2.6.30.5 puppyversion=431 PUPMODE=13
PDEV1='sdb1'
DEV1FS='ext2'
PUPSFS='sdb1,ext2,/spup-443.sfs'
PUPSAVE='sdb1,ext2,/spupsave_crypta-TEST.2fs' CURRENTWM=jwm
IceWM 1.3.5, Copyright 1997-2003 Marko Macek, 2001 Mathias Hasselmann
JWM vsvn-457 by Joe Wingbermuehle
ROX-Filer 2.6.1
X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Barry Kauler has trademark claim to the name 'Puppy', aka 'Puppy Linux' and
'PuppyOS' as it relates to 'computer operating system software to facilitate
computer use and operation' under Federal and International CommonLaw and
Trademark Laws as appropriate. www.puppylinux.com/faq.htm
<root> ~
...up until this part(II) AIGLX: Loaded and initialized /usr/X11R7/lib/dri/i965_dri.so
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?(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
KDE, yes, LXDE, Openbox I think so, JWM, IceWM I don't think so, Xfce I don't knowgcoyne wrote:Also is it possible to have two instances of the panel with different functions in each panel?
Thanks in advance
Greg.