The time now is Tue 24 Apr 2018, 14:23
All times are UTC - 4 |
Author |
Message |
battleshooter

Joined: 14 May 2008 Posts: 1381 Location: Australia
|
Posted: Sun 08 Feb 2009, 20:55 Post subject:
|
|
Hi Mark,
I deleted libglx.so and it's target, and replaced them with yours. Rebooted and was given a black screen just before entering X. Waited about 5 minutes and then forced a reboot. Right now I'm using another pup-save I had on the drive.
|
Back to top
|
|
 |
MU

Joined: 24 Aug 2005 Posts: 13648 Location: Karlsruhe, Germany
|
Posted: Sun 08 Feb 2009, 21:01 Post subject:
|
|
hm, you can reboot again.
X should recognize that it did not exit properly, and drop you to console.
There you could try again, or type:
rm -f /usr/X11R7/lib/xorg/modules/extensions/libglx.so
xwin
This would delete it.
I actually have no idea, why it fails.
Just to be certain, do you have this folder?
/usr/X11R7/lib/dri/
It should contain:
i810_dri.so
i915_dri.so
i965_dri.so
When X started, type:
lsmod
Look, if that shows a module loaded, like "i915".
For now, I must say goodnight, but will try to help you again tomorrow evening.
Mark
_________________ my recommended links
|
Back to top
|
|
 |
battleshooter

Joined: 14 May 2008 Posts: 1381 Location: Australia
|
Posted: Sun 08 Feb 2009, 21:09 Post subject:
|
|
Quote: | Just to be certain, do you have this folder?
/usr/X11R7/lib/dri/
It should contain:
i810_dri.so
i915_dri.so
i965_dri.so |
I have the folder and all 3 files. I'm going to try and restart now. Thanks for all your help Mark. Have a good night sleep.
|
Back to top
|
|
 |
battleshooter

Joined: 14 May 2008 Posts: 1381 Location: Australia
|
Posted: Sun 08 Feb 2009, 21:35 Post subject:
|
|
Oddly enough X didn't seem aware it didn't exit correctly. Skipping the console it led me directly to the black screen.
Typing lsmod, I couldn't seem to find i915.
I attached a screen shot of the modules loaded. I can't seem to copy and paste urxvt.
Battleshooter
Description |
|
Filesize |
114.98 KB |
Viewed |
1150 Time(s) |

|
|
Back to top
|
|
 |
MU

Joined: 24 Aug 2005 Posts: 13648 Location: Karlsruhe, Germany
|
Posted: Mon 09 Feb 2009, 02:29 Post subject:
|
|
what really makes me wonder is, that libglx.so from the original xorg gives a black screen.
I had a similar issue yesterday in Puppy 4.12, creating Ati drivers.
The problem was, that there was missing a symlink
/usr/X11R7/lib/dri
In this puplet here, it is a folder.
Maybe you miss
/usr/X11R7/lib/modules/dri
If that does not exist, type:
Code: | ln -s /usr/X11R7/lib/dri /usr/X11R7/lib/modules/dri |
------------
Else, I could imagine a conflict with one of the files installed from the nvidia sfs.
I would try to boot from CD, create a savefile.
Then add in /mnt/home these files:
Xorg-7.4-video-input-apps-i686-wow_411.sfs
Mesa-7.2-i686-wow_411.sfs
Then add them in the bootmanager and reboot, so that they get mounted.
If it works, you know, that something is wrong with your full installation.
---------------------
One other idea:
When X gives a black screen with the original libglx.so in your full installation, power off the computer.
Boot from CD, and look, if a /var/log/xorg.0.log was created on your harddrive.
Attach it here, also /var/log/messages and /tmp/xerrs.txt.
All from the harddrive, not from the current CD system.
Maybe they include a hint.
Mark
_________________ my recommended links
|
Back to top
|
|
 |
wow
Joined: 29 Jun 2006 Posts: 1036 Location: Peru
|
Posted: Mon 09 Feb 2009, 03:54 Post subject:
|
|
battleshooter wrote: | I'm not sure what's wrong but I can't seem to get glxgears working. I get the message:
Code: |
Xlib: extension "GLX" missing on display ":0.0"
Error: couldn't get an RGB, Double-buffered visual |
|
Xorg.0.log wrote: | (EE) intel(0): [dri] I830CheckDRIAvailable failed: glx not loaded |
Ok, I google it and found that it would be a problem with the xf86-video-intel driver. So I need to update xf86-video-intel, libdrm, drm kernel modules and Mesa to their latest stable versions or download everything from git (bleeding edge, unstable) make some .pets or an ISO (plus bugfixes and few goodies).
If you have the knowledge, please go ahead and install those packages from source.
I configured X with Code: | ./configure --build=i686-pc-linux-gnu --prefix=/usr/X11R7 --libdir=/usr/X11R7/lib --includedir=/usr/X11R7/include --sysconfdir=/etc --localstatedir=/var |
And Mesa . . . hmm . . . i can't remember at the moment.
_________________

|
Back to top
|
|
 |
battleshooter

Joined: 14 May 2008 Posts: 1381 Location: Australia
|
Posted: Mon 09 Feb 2009, 17:06 Post subject:
|
|
Quote: | Ok, I google it and found that it would be a problem with the xf86-video-intel driver. |
So, I guess that's the final diagnosis and there's nothing to be done except compile the new packages from source.
Quote: | If you have the knowledge |
I've done some compiling before, but doing Xorg is way over my head. Rather intimidating I guess I'll just wait till the next ISO update or whatever comes. It's not like I'll die not being able to play Paintball I might consider having ago one day, but it'll be a steep learning curve.
@ Mark
Quote: | what really makes me wonder is, that libglx.so from the original xorg gives a black screen. |
Actually, I completely forgot about that. A while back I tested the official Puppy 4 with my laptop and I was given completely screwed graphics. So that would explain why the original libglx was so disastrous. Sorry I didn't bring it up, I forgot.
Battleshooter
|
Back to top
|
|
 |
panzerpuppy
Joined: 02 Oct 2007 Posts: 632
|
Posted: Tue 10 Feb 2009, 03:15 Post subject:
|
|
MU wrote: | I actually tried the new Ati catalyst driver 9.1.
It compiled, but the fglrx kernelmodule would not load.
dmesg and googe told be, that this is, because in the kernels .config this must be set:
Code: | #
# Bus options (PCI etc.)
#
CONFIG_PCI_MSI=y |
Unfortunately, this seems to make it incompatible with wows kernel.
I had to replace the modules in intrd.gz with the recompiled ones.
There are several complains about this in the phoronix forum, so I hope, they will release a version without this option.
I have not yet decided, which kernel I'll use for newyearspup final tomorrow.
If I succeed to compile a patched wine that supports pixelshaders with that catalyst driver, I would use the new kernel.
If not, this had to wait for newyearspup03 in 3 months.
I would not like, to break compatibility with wows kernel...
Wine anyway seems not to compile with the typedefs I had to add.
Mark |
Do these drivers (9.1) work at all in Puppy? I run the official installer,the driver installs OK,then an aticonfig --initial -f and restart X. After that, I get a black screen and I'm forced to do a soft system reboot to get to the commandline.
Catalyst 8.11 produces the same issue. (8.12 works)
|
Back to top
|
|
 |
wow
Joined: 29 Jun 2006 Posts: 1036 Location: Peru
|
Posted: Tue 10 Feb 2009, 12:23 Post subject:
|
|
I downloaded drm-2.4.4 from git, xf86-video-intel-2.6.1 and Mesa-7.3 (libs, glut, demos).
libdrm and xf86-video-intel configured with:
Code: | ./configure --build=i686-pc-linux-gnu --prefix=/usr/X11R7 --libdir=/usr/X11R7/lib --includedir=/usr/X11R7/include --localstatedir=/var --sysconfdir=/etc --disable-static --disable-maintainer-mode --enable-shared |
Mesa 7.3:
Code: | ./configure --build=i686-pc-linux-gnu --prefix=/usr/X11R7 --libdir=/usr/X11R7/lib --includedir=/usr/X11R7/include --localstatedir=/var --sysconfdir=/etc --disable-static --disable-maintainer-mode --enable-shared --with-dri-driverdir=/usr/X11R7/lib/dri |
Mesa asks for dri2proto, downloading it right now, I'll try to test this new intel driver today (I don't have the hardware to, but some friends have it) and make dotpets later.
_________________

|
Back to top
|
|
 |
techtype
Joined: 16 Nov 2008 Posts: 181
|
Posted: Tue 10 Feb 2009, 15:21 Post subject:
Compiling |
|
@wow
It seems that Filefront no longer has this file: devx-Xorg74-gtk2144-r1.sfs which is linked on the first post.
Could you give a new link?
|
Back to top
|
|
 |
MU

Joined: 24 Aug 2005 Posts: 13648 Location: Karlsruhe, Germany
|
Posted: Tue 10 Feb 2009, 15:26 Post subject:
|
|
techtype
you'll find it here:
http://puppyisos.org/isos/2008-07-to-12/Puppy-4-K2.6.27.5/iso-01/
user: puppy
password: linux
Mark
_________________ my recommended links
|
Back to top
|
|
 |
battleshooter

Joined: 14 May 2008 Posts: 1381 Location: Australia
|
Posted: Tue 10 Feb 2009, 15:35 Post subject:
|
|
Quote: | I'll try to test this new intel driver today (I don't have the hardware to, but some friends have it) and make dotpets later. |
Yippee! Thanks so much Wow
|
Back to top
|
|
 |
techtype
Joined: 16 Nov 2008 Posts: 181
|
Posted: Tue 10 Feb 2009, 16:38 Post subject:
|
|
Ah, thanks Mark!
|
Back to top
|
|
 |
Leon
Joined: 22 Jun 2005 Posts: 254
|
Posted: Wed 11 Feb 2009, 04:22 Post subject:
|
|
wow wrote: | Unnamed pupplet (puppy411 kernel-2.6.27.5 Xorg-7.4 LXDE)
Subject description: just another puppy derivate
...
Default encoding for filenames in vfat partitions is UTF-8 (kernel module nls_utf8 by default)
... | wow,
From my experience the Unnamed-pupplet-puppy411-kernel-2.6.27.5 Xorg-7.4-LXDE is the only Puppy that properly displays sl_SI locale special characters in Rox. I noticed that sl_SI locale special characters in Rox are shown properly even if locale is set to en_US.
Would you be willing to explain what have you done to set this option to work?
We discussed this issue on Barry's blog.
Details:
http://puppylinux.com/blog/?viewDetailed=00556
|
Back to top
|
|
 |
wow
Joined: 29 Jun 2006 Posts: 1036 Location: Peru
|
Posted: Wed 11 Feb 2009, 17:59 Post subject:
|
|
Leon wrote: | I noticed that sl_SI locale special characters in Rox are shown properly even if locale is set to en_US.
Would you be willing to explain what have you done to set this option to work? |
Easy: Full install
You have to compile your own kernel with these options in "DOS/FAT/NT Filesystems"(kernel's .config file):
Code: | CONFIG_FAT_DEFAULT_CODEPAGE=850
CONFIG_FAT_DEFAULT_IOCHARSET="utf8" |
Install and boot your kernel.
Hard: Full install, initrd.gz and pup_4xx.sfs edit, remaster LiveCD.
Compile linux kernel with these options in "DOS/FAT/NT Filesystems"(kernel's .config file):
Code: | CONFIG_FAT_DEFAULT_CODEPAGE=850
CONFIG_FAT_DEFAULT_IOCHARSET="utf8" |
Install and boot your kernel.
Extract contents of initrd.gz and replace every kernel module in initrd/kernel/
Add nls_utf8.ko and nls_cp850.ko files to initrd/kernel/fs/nls/
Replace names(nls_cp850 and nls_utf8) in initrd/init (text file)
Instructions to edit the initrd.gz file, patch the linux kernel, make an iso with your new kernel and more help [here], [here], [and here]
_________________

|
Back to top
|
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|