View Full Version : Continued driver issues
HighHo
06-01-2007, 04:10 AM
For around the last 4/5 driver releases I have had no luck with the propriety drivers for an X800SE. I have viewed many posts and possible solutions already over the months with no luck. The following output from my Xorg.0.log file seems to be the only notable issues:
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmGetBusid returned ''
To explain the issue a little further the drivers install fine, the aticonfig program works and all seems fine, I then restart and end up with 2 black screens, and the computer hard locks. I can disable DRI and they will load, but thats kind of pointless and the open source drivers work just fine for desktop use.
If anyone has any further ideas please let me know. It will save me buying a new card for a little while longer, at least currently that seems my only option for accelerated 3D in linux.
Thanks,
Alex.
Etano
06-01-2007, 04:32 AM
Same problem here. I am using the X1300 w/ an amd64. Please help.
Michael
06-01-2007, 06:58 AM
What does your xorg.conf look like?
the-me
06-01-2007, 07:13 AM
Sounds not like a fglrx issue.
I think you've forgot to install the libstdc++5 libary.
HighHo
06-01-2007, 07:27 AM
libstdc++5 is installed.
xorg.conf is as follows:
Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "aticonfig-Screen[0]" 0 0
Screen "aticonfig-Screen[1]" Above "aticonfig-Screen[0]"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
EndSection
Section "Files"
# path to defoma fonts
FontPath "/usr/share/fonts/X11/misc"
FontPath "/usr/share/fonts/X11/cyrillic"
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/share/fonts/X11/100dpi"
FontPath "/usr/share/fonts/X11/75dpi"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection
Section "Module"
Load "i2c"
Load "bitmap"
Load "ddc"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "vbe"
EndSection
Section "ServerFlags"
Option "AIGLX" "off"
EndSection
Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "fr"
EndSection
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection
Section "Monitor"
Identifier "aticonfig-Monitor[0]"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Monitor"
Identifier "aticonfig-Monitor[1]"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]"
Driver "fglrx"
BusID "PCI:3:0:0"
EndSection
Section "Device"
Identifier "aticonfig-Device[1]"
Driver "fglrx"
BusID "PCI:3:0:0"
Screen 1
EndSection
Section "Screen"
Identifier "aticonfig-Screen[0]"
Device "aticonfig-Device[0]"
Monitor "aticonfig-Monitor[0]"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "aticonfig-Screen[1]"
Device "aticonfig-Device[1]"
Monitor "aticonfig-Monitor[1]"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Section "DRI"
Mode 0666
EndSection
Section "Extensions"
Option "Composite" "Disable"
EndSection
Michael
06-01-2007, 07:35 AM
Does it work for you if you make a dummy xorg.conf that is very simple?
HighHo
06-01-2007, 07:51 AM
I just tried a nice simple config, setup for 1 display, removing un needed modules and font paths. Still results in black screen and a hardlock.
xunilos
06-01-2007, 01:47 PM
I just tried a nice simple config, setup for 1 display, removing un needed modules and font paths. Still results in black screen and a hardlock.
I thought I had this same problem, but it turned out the black screen was just console 7 - the screen that the X server normally runs on. I hit Alt-F1 and got back to my login console, and everything was fine. My problem turned out to be that I hadn't installed compat-libstdc++-33 (Fedora 6).
Just a suggestion.
HighHo
06-01-2007, 01:56 PM
Thanks, I can however confirm that this is not the problem. The system is completely unresponsive to switching console or restating X (ctrl + alt + backspace). I can only reset the computer from the power switch once X has started using the fglrx driver with DRI.
xunilos
06-01-2007, 02:27 PM
Sorry that didn't help. I'm having problems too, with the 8.37 driver, on Fedora 6, with an X1300. Initially I was seeing the same "drmOpenDevice" messages in my Xorg.0.log. Then I remembered I upgraded the kernel after installing the drivers. I re-ran the ATI installer, did a "modprobe fglrx", and the drmOpenDevice calls started working again.
However, I still have another problem: I've run aticonfig --initial --dtop horizontal, but my 2nd head stays stubbornly dark. I've also tried aticonfig --initial=dual-head --screen-layout=left, same thing.
The really frustrating thing is, this worked once, but I don't know what I changed.
EDIT: I should also note that the 2nd head works in console mode.
Here's my xorg.conf:
# Xorg configuration created by pyxf86config
Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "aticonfig-Screen[0]" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
EndSection
Section "Module"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection
Section "Monitor"
Identifier "aticonfig-Monitor[0]"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Device"
Identifier "Videocard0"
Driver "vesa"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]"
Driver "fglrx"
Option "DesktopSetup" "horizontal"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "aticonfig-Screen[0]"
Device "aticonfig-Device[0]"
Monitor "aticonfig-Monitor[0]"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
hobophobe
06-04-2007, 07:49 AM
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmGetBusid returned ''
I'm on debian sid with an X800 pro and get the same thing except 'result is' was 6 with xserver 1.3.0 and 7 with 1.1.1; as the driver works fine for me on 1.1.1 I'm assuming the above is not the source of the difficulties.
What distro/version do you use? Is this on xserver 1.3.0 or others too?
I get the same results with DRI disabled.
My experience is as follows:
For xserver 1.1.1 (currently in debian testing) fglrx 8.37.6 works fine.
On 1.3.0 I get the same as you: 'freeze' and blank screen which makes my monitor say 'no signal' and shut off.
If I boot in recovery console mode and then continue the boot gnome loads up fine as usual, but if I log out or attempt to restart it locks up as it does on normal boot.
Also, in comparing my working Xorg.0.log for 1.1.1 and the broken one from 1.3.0 I notice that the 1.3.0 suggests it thinks I have an extra monitor?
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"(II) Module already built-in
(II) fglrx(0): Connected Display1: CRT on primary DAC [crt1]
(II) fglrx(0): Display1: No EDID information from DDC.
(II) fglrx(0): Display1: Failed to get EDID information.
(II) fglrx(0): Connected Display2: DFP on internal TMDS [tmds1]
(II) fglrx(0): Display2 EDID data ---------------------------
I assume this shouldn't be a cause of your problems since you mentioned running a dual head setup.
Hopefully we can nail down where this problem is coming from and submit a bug report to the appropriate project.
-Adam
HighHo
06-15-2007, 02:48 AM
Sorry for my late responce I have just moved country!
The issue occured for me on Gentoo AMD64 and Kubuntu on both 32 & 64bit. I belive that on all occations I have been using Xorg-server 1.3.0 although hard to be sure what I was using when the issues all started :)
Just to add a little more about the card in use, its a radeon X800GT 256MB PCIE using the R423 core.
karthikrg
06-20-2007, 03:33 AM
Dear ppl,
Please check this out. I have run into similar problems too with my x1800 and no solution so far.. [:(]
http://www.phoronix.com/forums/showthread.php?p=9433&posted=1#post9433
HighHo
06-20-2007, 12:43 PM
One thing I notice I have in common with our systems is that we both have Nforce 430 chipset/6100 onboard graphics.
Huenengrab
06-20-2007, 03:41 PM
I didn't use fglrx for a long time now. But I'm curious and maybe I stumbled on something there. Both of your xorg.confs seem to have two "Devices". Maybe you could try booting with one of the commented out?
HighHo
06-20-2007, 04:22 PM
Already tried with the simple config file mentioned on a previous post, using 1 device results in the same effect as using 2 Devices/Screens/Mointers.
Thanks regardless for taking the time to post a suggestion.
HighHo
karthikrg
06-21-2007, 12:04 AM
hmm.. even i was given a similar reasoning by someone else on some forum.. saying the problem may be with the chipset driver and not with the graphics driver.. i donno for sure but
neways all versions till 8.32.5 worked great for me. Problems started with 8.33.6 in which, I heard they did some major rewrite..
bitnick
07-04-2007, 03:59 PM
I have had two problems with hard hangs when starting X. One that leads to black screen and one that leads to the monitor getting no signal and shutting off.
The solutions that worked for me were
1) Black screen with sync signal: Change AGP Aperture Size setting in BIOS from 64M to 128M (guess if this one took some time to figure out!).
2) No monitor signal: Set <Option "AGPFastWrite" "0"> in the Device section of xorg.conf.
Perhaps one of these will do the trick. I'm running the open source radeon driver on a Radeon X800 (R420).
Arvid
karthikrg
07-05-2007, 12:22 AM
but bitnick.. we are having problems with fglrx and not the OSS radeon driver.. my card (MSI X1800XT VT-2D-512E) does not support Radeon and so i have to use fglrx for gfx acceleration..
bitnick
07-05-2007, 07:55 AM
Absolutely! But if this is an AGP issue then perhaps it's worth a try anyway? If you're all running PCIe cards then I guess my advice isn't worth the pap.. ehm, cyberspace space it is written on. ;)
Arvid
karthikrg
07-06-2007, 01:01 AM
Doesnt work... have been breaking my head on this from the past 6 months.. hope ATI soon pulls out a fix
HighHo
07-20-2007, 11:43 AM
Would just like to report that my issues are now solved with the 8.39.4 driver! Now just to await the hotfix for the annoying "testing use only" and i will be very happy (for a little while anyway). :)
LWilder
07-20-2007, 12:51 PM
well at least got yours working. am still getting the same 3 errors of dlopen and fglrx drv paths not being seen !!! if only i did not pay hi price for this ATI X1900XT, would be nice to replace it w/ something that works 3D.
stil hanging onto the ATI vapor dreams...
lw
vBulletin® v3.8.4, Copyright ©2000-2009, Jelsoft Enterprises Ltd.