LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Closed Thread
 
Search this Thread
Old 12-02-2009, 09:19 AM   #676
adamk75
Senior Member
 
Registered: May 2006
Posts: 3,091

Rep: Reputation: 396Reputation: 396Reputation: 396Reputation: 396

Quote:
Originally Posted by onebuck View Post
Hi,



I know, about to throw things back!



I appreciate another pair of eyes!

I think I see the problem. Or at least one problem...

Code:
(II) Loading /usr/lib64/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="FireGL - ATI Technologies Inc."
You installed fglrx on this installation at one point and you still have parts of it left over.

You need to remove fglrx completely, and I suggest reinstalling xorg-server and then trying again. Then pastebin your new /var/log/Xorg.0.log file.

Adam
 
Old 12-02-2009, 10:20 AM   #677
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 11,138
Blog Entries: 3

Rep: Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405
Hi,

Quote:
Originally Posted by adamk75 View Post
I think I see the problem. Or at least one problem...

Code:
(II) Loading /usr/lib64/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="FireGL - ATI Technologies Inc."
You installed fglrx on this installation at one point and you still have parts of it left over.

You need to remove fglrx completely, and I suggest reinstalling xorg-server and then trying again. Then pastebin your new /var/log/Xorg.0.log file.

Adam
Yes, sometime ago. I thought that had been removed. Staring me in the face.

I keep written system logs for all work done on the machines to prevent this type of error. Oversight!

I removed all the stale files/packages. Double checked.

I also removed and reinstalled the xorg-server packages. The '/var/log/packages/mesa-7.5.1-x86_64-1' package is from '-current' because;

Quote:
changelog -current;
x/mesa-7.5.1-x86_64-1.txz: Upgraded.
Fixed install script to add glxinfo and other programs that were part
of previous Mesa patches. I was under the impression that these no longer
built, and had been deprecated upstream. Thanks to Adam Kirchhoff for
setting me straight on that.
glxinfo_pastebin

Xorg.0.log_pastebin

 
Old 12-02-2009, 10:34 AM   #678
adamk75
Senior Member
 
Registered: May 2006
Posts: 3,091

Rep: Reputation: 396Reputation: 396Reputation: 396Reputation: 396
We're making progress. The correct libglx.so file is back, but it's still complaining about a too old libdri.a, which just has me confused. Can you show the output of 'dmesg | grep drm' and 'lsmod | grep radeon'. And, while we're at it, can you grep for 'radeon' from the .config file for your kernel build? Probably 'grep -i radeon /usr/src/linux-2.6.32-rc7/.config'

EDIT:

Also, what's the output of 'ls -l /usr/lib64/xorg/modules/extensions/libdri*' ?

2nd EDIT:

Wait... Why are you disabling dri and dri2 in your xorg.conf file? That's very likely the source of this problem. Please remove those two lines and restart X. Also switch back to the EXA AccelMethod while you're editing your xorg.conf file.

Adam

Last edited by adamk75; 12-02-2009 at 10:44 AM.
 
Old 12-02-2009, 11:48 AM   #679
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 11,138
Blog Entries: 3

Rep: Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405
Hi,

Quote:
Originally Posted by adamk75 View Post
We're making progress. The correct libglx.so file is back, but it's still complaining about a too old libdri.a, which just has me confused. Can you show the output of 'dmesg | grep drm' and 'lsmod | grep radeon'. And, while we're at it, can you grep for 'radeon' from the .config file for your kernel build? Probably 'grep -i radeon /usr/src/linux-2.6.32-rc7/.config'

EDIT:

Also, what's the output of 'ls -l /usr/lib64/xorg/modules/extensions/libdri*' ?

2nd EDIT:

Wait... Why are you disabling dri and dri2 in your xorg.conf file? That's very likely the source of this problem. Please remove those two lines and restart X. Also switch back to the EXA AccelMethod while you're editing your xorg.conf file.

Adam
Code:
# dmesg | grep drm
[drm] Initialized drm 1.1.0 20060810
[drm] radeon defaulting to kernel modesetting.
[drm] radeon kernel modesetting enabled.      
[drm] radeon: Initializing kernel modesetting.
[drm] register mmio base: 0xC0100000          
[drm] register mmio size: 65536               
[drm] GPU reset succeed (RBBM_STATUS=0x00000140)
[drm:rs400_gart_adjust_size] *ERROR* Forcing to 32M GART size (because of ASIC bug ?)
[drm] Generation 2 PCI interface, using max accessible memory                        
[drm] radeon: VRAM 128M                                                              
[drm] radeon: VRAM from 0x78000000 to 0x7FFFFFFF                                     
[drm] radeon: GTT 32M                                                                
[drm] radeon: GTT from 0x80000000 to 0x81FFFFFF                                      
[drm] radeon: irq initialized.                                                       
[drm] Detected VRAM RAM=128M, BAR=128M                                               
[drm] RAM width 128bits DDR                                                          
[drm] radeon: 128M of VRAM memory ready                                              
[drm] radeon: 32M of GTT memory ready.
[drm] GART: num cpu pages 8192, num gpu pages 8192
[drm] radeon: 3 quad pipes, 1 z pipes initialized.
[drm] radeon: cp idle (0x10000C03)
[drm] Loading R300 Microcode
[drm] radeon: ring at 0x0000000080000000
[drm] ring test succeeded in 1 usecs
[drm] radeon: ib pool ready.
[drm] ib test succeeded in 0 usecs
[drm] Panel ID String: AUO
[drm] Panel Size 1280x800
[drm] Radeon Display Connectors
[drm] Connector 0:
[drm]   VGA
[drm]   DDC: 0x68 0x68 0x68 0x68 0x68 0x68 0x68 0x68
[drm]   Encoders:
[drm]     CRT1: INTERNAL_DAC2
[drm] Connector 1:
[drm]   LVDS
[drm]   DDC: 0x1a0 0x1a0 0x1a0 0x1a0 0x1a0 0x1a0 0x1a4 0x1a4
[drm]   Encoders:
[drm]     LCD1: INTERNAL_LVDS
[drm] fb mappable at 0xC8040000
[drm] vram apper at 0xC8000000
[drm] size 4096000
[drm] fb depth is 24
[drm]    pitch is 5120
fb0: radeondrmfb frame buffer device
[drm] Initialized radeon 2.0.0 20080528 for 0000:01:05.0 on minor 0
Code:
# lsmod | grep radeon
radeon                563649  1
ttm                    35604  1 radeon
drm_kms_helper         21947  1 radeon
drm                   151510  3 radeon,ttm,drm_kms_helper
i2c_algo_bit            4935  1 radeon
i2c_core               17737  4 radeon,drm,i2c_algo_bit,i2c_piix4
Code:
# grep -i radeon .config
CONFIG_DRM_RADEON=m
CONFIG_FB_RADEON=m
CONFIG_FB_RADEON_I2C=y
CONFIG_FB_RADEON_BACKLIGHT=y
# CONFIG_FB_RADEON_DEBUG is not set
CONFIG_DRM_RADEON_KMS=y
Code:
# ls -l /usr/lib64/xorg/modules/extensions/libdri*
-rwxr-xr-x 1 root root   961 2009-08-03 19:40 /usr/lib64/xorg/modules/extensions/libdri.la
-rwxr-xr-x 1 root root 40552 2009-08-03 19:40 /usr/lib64/xorg/modules/extensions/libdri.so
-rwxr-xr-x 1 root root   967 2009-08-03 19:40 /usr/lib64/xorg/modules/extensions/libdri2.la
-rwxr-xr-x 1 root root 12984 2009-08-03 19:40 /usr/lib64/xorg/modules/extensions/libdri2.so
I have reverted my xorg.conf with the dri & dri2 disable removed. Switched back to the EXA AccelMethod.

This was done during some trouble shooting and failure to revert. I also believe that the failure to remove stale files and package(s) was part of the problem. The mesa package has been upgraded from '-current';

Quote:
'-current changelog';

+--------------------------+
Sat Sep 19 17:16:06 CDT 2009
x/mesa-7.5.1-x86_64-1.txz: Upgraded.
Fixed install script to add glxinfo and other programs that were part
of previous Mesa patches. I was under the impression that these no longer
built, and had been deprecated upstream. Thanks to Adam Kirchhoff for
setting me straight on that.
+--------------------------+
Xorg.0.log_pastebin

glxinfo_pastebin

EDIT: side note; I've had to re-boot. System lock up and rasterized screen. Now when I exit the DE my screen is rasterized. After the re-boot the screen console is OK, I'm still in 'KDE' for now.

Last edited by onebuck; 12-02-2009 at 11:52 AM. Reason: side note
 
Old 12-02-2009, 12:10 PM   #680
adamk75
Senior Member
 
Registered: May 2006
Posts: 3,091

Rep: Reputation: 396Reputation: 396Reputation: 396Reputation: 396
OK, the current problem is that you are using a KMS enabled kernel (since you updated to 2.6.32-rc7) but not a KMS enabled libdrm and xf86-video-ati. The quick fix is to boot with the radeon.modeset=0 kernel option. That will should get 3D acceleration going, but will disable kernel modesetting. This is essentially what you should have had after a clean install of Slackware 13.0.

Adam
 
Old 12-02-2009, 01:20 PM   #681
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 11,138
Blog Entries: 3

Rep: Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405
Hi,

Quote:
Originally Posted by adamk75 View Post
OK, the current problem is that you are using a KMS enabled kernel (since you updated to 2.6.32-rc7) but not a KMS enabled libdrm and xf86-video-ati. The quick fix is to boot with the radeon.modeset=0 kernel option. That will should get 3D acceleration going, but will disable kernel modesetting. This is essentially what you should have had after a clean install of Slackware 13.0.

Adam
No Joy! I switched to 'radeon.modeset=0' and the screen was rastered for the 2.6.32-rc7 kernel after a boot.

Switched to the '2.6.30.5' kernel;

glxinfo_pastebin
Xorg.0.log_pastebin

Code:
(WW) RADEON(0): LCD DDC Info Table found!
(II) RADEON(0): [drm] Initialized kernel GART heap manager, 29884416
&
(WW) RADEON(0): DRI init changed memory map, adjusting ...
(WW) RADEON(0):   MC_FB_LOCATION  was: 0x7fff7800 is: 0x7fff7800
(WW) RADEON(0):   MC_AGP_LOCATION was: 0xffffffc0 is: 0x81ff8000
 
Old 12-02-2009, 03:22 PM   #682
adamk75
Senior Member
 
Registered: May 2006
Posts: 3,091

Rep: Reputation: 396Reputation: 396Reputation: 396Reputation: 396
Alright, well the 2.6.30.5 kernel, you appear to be back to a stock installation of Slackware 13.0, at least. Both your log file and glxinfo show that 3D acceleration is enabled and working.

I'm not sure what you mean by your screen being rastered under 2.6.32-rc7, but it sounds like KMS was still enabled. Can you boot that kernel again, this time with the 'nomodeset' option to the kernel. Does that show the same problem? If you boot into 2.6.32-rc7 without any special kernel options, but don't start X, you get a high resolution console? Is the screen rastered in that case?

Adam
 
Old 12-02-2009, 04:07 PM   #683
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 11,138
Blog Entries: 3

Rep: Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405
Hi,
Quote:
Originally Posted by adamk75 View Post
Alright, well the 2.6.30.5 kernel, you appear to be back to a stock installation of Slackware 13.0, at least. Both your log file and glxinfo show that 3D acceleration is enabled and working.

I'm not sure what you mean by your screen being rastered under 2.6.32-rc7, but it sounds like KMS was still enabled. Can you boot that kernel again, this time with the 'nomodeset' option to the kernel. Does that show the same problem? If you boot into 2.6.32-rc7 without any special kernel options, but don't start X, you get a high resolution console? Is the screen rastered in that case?

Adam

Yes, I'm back to a stock install now. I've booted the 2.6.32-rc7 kernel with 'nomodeset'. Still rastered. Nothing but scan lines.

I'll try the boot for the '2.6.32-rc7' again without setting to see if things remain rastered scan lines (unreadable). Looks like the wrong scan clock which seems to be a driver issue.

I've got 'vga = 773' for the console. Boots to a normal readable console. When a switch from 'X' via ctrl-alt-f1 then screen is rastered. Switching back and the 'X' session is normal.

Off to try the 2.6.32-rc7 again.
 
Old 12-02-2009, 04:31 PM   #684
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 11,138
Blog Entries: 3

Rep: Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405
Hi,

No Joy with '2.6.32-rc7'.

I'll stick with trouble shooting the '2.6.30.5' kernel.

Adam, I really appreciate the time you have given towards my issue(s).
 
Old 12-02-2009, 04:35 PM   #685
adamk75
Senior Member
 
Registered: May 2006
Posts: 3,091

Rep: Reputation: 396Reputation: 396Reputation: 396Reputation: 396
Wait, with the 2.6.20-rc7 kernel you are using vga=773? When using KMS, you should not pass any vga= option to the kernel. Can you try without that?
 
Old 12-02-2009, 05:07 PM   #686
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 11,138
Blog Entries: 3

Rep: Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405Reputation: 1405
Hi,

That's in the '/etc/lilo.conf' file. I'll comment it out then try again.

I just tested the '2.6.30.5' after setting;

Code:
'/etc/X11/xorg.conf';

Section "Monitor"
        DisplaySize       330   210     # mm
        Identifier   "Monitor0"
        VendorName   "AUO"
        ModelName    "1c74"
#        DisplaySize 338 211             #mm
EndSection
Set to the lower value to see what happens. I 'startx' and things are OK. Exit the first time and OK. 'startx' again then raster thus image torn. Exit then 'startx' blind and things are good.

I think it's still a driver problem.
 
Old 12-06-2009, 03:31 AM   #687
memoryic
LQ Newbie
 
Registered: Dec 2009
Posts: 5

Rep: Reputation: 1
ATI fglrx on slakware 13 freezes laptop

Greetings to the community. This is my first post.

I have spend the last couple of weeks trying to enable 3D on my Toshiba Satellite A300-22W laptop. lspci reports
Quote:
01:00.0 VGA compatible controller: ATI Technologies Inc Mobility Radeon HD 3400 Series
I have just installed a fresh copy of Slackware 13, and followed the steps below
Quote:
1) sh ati-driver-installer-9-8-x86.x86_64.run --buildpkg Slackware/All
2) installpkg fglrx-module-8.64-x86_64-1_kernel_2.6.29.6.tgz fglrx-x740_64a-8.64-x86_64-1.tgz
3) aticonfig --initial
4) cp /etc/ati/amdpcsdb.default /etc/ati/amdpcsdb
5) rmmod radeon
6) rmmod drm
7) depmod -a
8) modprobe fglrx
fglrx module loads with no complains
Quote:
bash-3.1# lsmod | grep fglrx
fglrx 1989404 0
agpgart 29256 2 intel_agp,fglrx
bash-3.1#
xorg.conf is auto-generated by aticonfig as following
Quote:
bash-3.1# cat /etc/X11/xorg.conf
Section "ServerLayout"
Identifier "aticonfig Layout"
Screen 0 "aticonfig-Screen[0]-0" 0 0
EndSection

Section "Files"
EndSection

Section "Module"
EndSection

Section "Monitor"
Identifier "aticonfig-Monitor[0]-0"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection

Section "Device"
Identifier "aticonfig-Device[0]-0"
Driver "fglrx"
BusID "PCI:1:0:0"
EndSection

Section "Screen"
Identifier "aticonfig-Screen[0]-0"
Device "aticonfig-Device[0]-0"
Monitor "aticonfig-Monitor[0]-0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

bash-3.1#
My problem is than when I run startx, the computer totally freezes with a (well known to all ATI-hang threads) minus to the top-left corner.
/var/log/Xorg.log is emty.
I have also try to update to the current Xorg
Quote:
bash-3.1# Xorg -version

X.Org X Server 1.7.1
Release Date: 2009-10-23
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.29.6-smp i686
Current Operating System: Linux darkstar 2.6.29.6-smp #1 SMP Tue Dec 1 22:16:07 EET 2009 i686
Kernel command line: BOOT_IMAGE=jkar_kernel ro root=811 vt.default_utf8=0
Build Date: 06 December 2009 10:23:36AM

Current version of pixman: 0.15.20
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
bash-3.1#
2D graphics with "radeon" driver (or when I rm xorg.conf works fine).

I started to run out of ideas...
Thank you for your time.
 
Old 12-06-2009, 03:59 AM   #688
kaz2100
Senior Member
 
Registered: Apr 2005
Location: Penguin land, with apple, no gates
Distribution: Debian testing woody(32) sarge etch lenny squeeze(+64) wheezy jessie
Posts: 1,433

Rep: Reputation: 83
Hya,

Self reply to my post.

Since then, something went wrong again, similar to my this thread. (Debian squeeze, after update)
As suggested, I tried "X -configure", which did not work for a while, then worked perfect! (with OpenGL renderer) Glxgears is smooth again.

Happy Penguins!


memoryic: Have you tried different version ATI driver? Once upon a time in the past, some version worked, while some did not.
 
Old 12-06-2009, 04:46 AM   #689
memoryic
LQ Newbie
 
Registered: Dec 2009
Posts: 5

Rep: Reputation: 1
memoryic: Have you tried different version ATI driver?

Hi Kaz, I have originly tried 9.1.1 and also 9.8 - same result, X window freezes
ati-driver-installer-9-11-x86.x86_64.run
ati-driver-installer-9-8-x86.x86_64.run

You 've mentioned you 've manage to get 3D (Glxgears), Which rendered/version are you using?
thanx.

oups! I 've tried X -configure. here is the output log
Quote:
bash-3.1# cat /usr/local/var/log/Xorg.0.log

X.Org X Server 1.7.1
Release Date: 2009-10-23
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.29.6-smp i686
Current Operating System: Linux darkstar 2.6.29.6-smp #1 SMP Tue Dec 1 22:16:07 EET 2009 i686
Kernel command line: BOOT_IMAGE=jkar_kernel ro root=811 vt.default_utf8=0
Build Date: 06 December 2009 10:23:36AM

Current version of pixman: 0.15.20
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/usr/local/var/log/Xorg.0.log", Time: Sun Dec 6 12:55:52 2009
(II) Loader magic: 0x81d9a20
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 6.0
X.Org XInput driver : 7.0
X.Org Server Extension : 2.0
(--) using VT number 7

(--) PCI:*(0:1:0:0) 1002:95c4:1179:ff1e rev 0, Mem @ 0xc0000000/268435456, 0xd6300000/65536, I/O @ 0x00005000/256, BIOS @ 0x????????/131072
Missing output drivers. Configuration failed.

bash-3.1#
i2c is loaded
Quote:
bash-3.1# lsmod | grep i2c
i2c_i801 8784 0
i2c_core 20496 1 i2c_i801
bash-3.1#


Any ideas? Do I need to pass X extra parameters for the fglrx?

Last edited by memoryic; 12-06-2009 at 05:05 AM.
 
Old 12-07-2009, 07:05 AM   #690
kaz2100
Senior Member
 
Registered: Apr 2005
Location: Penguin land, with apple, no gates
Distribution: Debian testing woody(32) sarge etch lenny squeeze(+64) wheezy jessie
Posts: 1,433

Rep: Reputation: 83
Hya,

I do not think that your problem is same as my current problem. I have Xpress 200M, you have HD3400.

Once upon a time, when ATI used to support Xpress 200M, some of drivers worked, while some did not. So, you should try all available ones, (do not forget to uninstall whatever non-functional one) This is all I can suggest.

Happy Penguins!
 
  


Closed Thread

Tags
3d, acceleration, ati, enabling, fglrx, glx, intel, nvidia, s3, savage, slackware, via, video, x11, xorg


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
enabling hardware acceleration PennyroyalFrog Linux - Newbie 5 02-26-2010 11:21 AM
xorg-x11 7.0 and exa acceleration jtshaw Linux - Software 0 12-19-2005 07:42 AM
3d acceleration and X11 bspus Linux - Newbie 3 09-06-2005 06:05 AM
Problem Enabling 3D Hardware acceleration. mir_sheely Linux - Hardware 0 06-14-2004 12:37 PM
Audigy Sound card and enabling 3D acceleration for GeoForce3 ti 500 heavyarmor4ever Linux - Newbie 1 01-03-2003 09:27 PM


All times are GMT -5. The time now is 04:08 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration