| View previous topic :: View next topic |
| Author |
Message |
snakeo2
Veteran
Joined: 01 Jan 2006
Posts: 1237
|
 Posted: Sat Nov 07, 2009 4:20 pm Post subject: Need help with ati drivers |
 |
|
Hello,
Since my previous post did not get me anywhere, I've decided to give it another try. I recently switched from nvidia based video card to ati and now xorg complaings about "no screen found". I dont have a livecd with gui so it's very hard for me to copy and paste errors, so im writing what i see on my screen. I'm a little confused because there is so much information regarding drivers, from radeon, to fglrx to vesa to xf86-video-ati that im not quite sure which one to use. My video card is an MSI R4650, PCIe 1GB. If anyone an either point me to a nice tutorial that I can follow or provide me with the necessary steps to get xorg working I would greatly appreciated. Also, what options do I need to enable on my kernel to ensure everything goes smoothly. Here is more information, in my make.conf i have the following which I believe is relevant:
input_devices="keyboard mouse evdev"
video_cards="fglrx fbdev vesa radeon"
I have also added "hal" to use flags.
_________________
Gigabyte MA790X-UD4P Motherboard
AMD Phenom II X4 940 Black Edition
MSI ATI R4650 PCIe2
250GB SATA Drive
4GB Corsair DDR2 |
|
| Back to top |
|
 |
gsoe
Apprentice
Joined: 10 Dec 2006
Posts: 289
Location: Denmark
|
| Posted: Sat Nov 07, 2009 5:47 pm Post subject: |
|
|
The HD 4650 is not supported by the radeon driver yet, but if you make sure you use vesa as driver, you should get a usable screen. When you have that, you can always proceed to get the fglrx (ati-drivers) working. Use this skeleton xorg.conf: | Code: | less /etc/X11/xorg.conf
Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Default Screen" 0 0
EndSection
Section "Device"
Identifier "Standard Video Card"
Driver "vesa"
EndSection
Section "Screen"
Device "Standard Video Card"
Identifier "Default Screen"
DefaultDepth 24
EndSection
|
EDIT: By the way, you need both "hal" and "dbus" in your USE flags, and you should make sure that you start them at boot: | Code: | rc-update add hald default
rc-update add dbus default |
I'm not quite sure if anything's needed in the kernel config to get the "vesa" driver working, but it can't hurt to set | Code: | -> Device drivers
-> Graphics support
-> <M> /dev/agpgart
-> <M> whatever chipset you have
-> <M> Direct Rendering Manager
-> <M> ATI Radeon |
Then you can load the modules before you start X using the /etc/modules.autoload.d/kernel-2.6 file. Do not compile these options into the kernel, as you shouldn't use them for the fglrx drivers.
To get your keyboard working with evdev, you should configure hal, then you don't need the "keybord" and "mouse". Copy this file into /etc/hal/fdi/policy/10-keymap.fdi | Code: | newpc linux # cat /etc/hal/fdi/policy/10-keymap.fdi
<?xml version="1.0" encoding="ISO-8859-1"?> <!-- -*- SGML -*- -->
<deviceinfo version="0.2">
<device>
<match key="info.capabilities" contains="input.keymap">
<append key="info.callouts.add" type="strlist">hal-setup-keymap</append>
</match>
<match key="info.capabilities" contains="input.keys">
<merge key="input.xkb.rules" type="string">base</merge>
<!-- If we're using Linux, we use evdev by default (falling back to
keyboard otherwise). -->
<merge key="input.xkb.model" type="string">keyboard</merge>
<match key="/org/freedesktop/Hal/devices/computer:system.kernel.name"
string="Linux">
<merge key="input.xkb.model" type="string">evdev</merge>
</match>
<merge key="input.xkb.layout" type="string">dk</merge>
<merge key="input.xkb.variant" type="string">nodeadkeys</merge>
</match>
</device>
</deviceinfo>
|
and edit the "dk" in the line | Code: | | <merge key="input.xkb.layout" type="string">dk</merge> |
to your language. Omit the | Code: | | <merge key="input.xkb.variant" type="string">nodeadkeys</merge> |
line if you don't need any xkb.variant.
Finally restart hal: | Code: | | /etc/init.d/hald restart |
|
|
| Back to top |
|
|
snakeo2
Veteran
Joined: 01 Jan 2006
Posts: 1237
|
| Posted: Sat Nov 07, 2009 7:07 pm Post subject: |
|
|
Thanks a lot for your suggestion
both hald and dbus were already added to start at boot
I made the changes you suggested to my xorg.conf fle
Im recompiling the kernel right now and i noticed that /dev/agpgart does not give the option to compile a (M). I can only set it to compile as (*). With regards to the chipset, once I get to /dev/agpgart, I only have three options and not sure which one is mine.
Intel 440LX/BX/GX, I8xx and E7x05
SIS Chipset support
VIA Chipset support.
My moherboard is a Gigabyte MA790X-UDP4P.
_________________
Gigabyte MA790X-UD4P Motherboard
AMD Phenom II X4 940 Black Edition
MSI ATI R4650 PCIe2
250GB SATA Drive
4GB Corsair DDR2 |
|
| Back to top |
|
|
gsoe
Apprentice
Joined: 10 Dec 2006
Posts: 289
Location: Denmark
|
| Posted: Sat Nov 07, 2009 7:23 pm Post subject: |
|
|
| Quote: | | Im recompiling the kernel right now and i noticed that /dev/agpgart does not give the option to compile a (M) |
I think that's something to do with other selected options. If you get into the help screen at | Code: | | < > /dev/agpgart (AGP Support) ---> |
you'll see this at the bottom: | Code: | | Selected by: GART_IOMMU && X86_64 && PCI |
Try checking out those settings (you can search for them in menuconfig by entering a "/" and then type the name).
Only having the three options under /dev/agpgart is strange, I'm clueless....
But anyhow the vesa driver should work without agpgart and DRI, I think.
EDIT: You do have support for modules in your kernel, don't you? | Code: | | [*] Enable loadable module support ---> |
|
|
| Back to top |
|
|
snakeo2
Veteran
Joined: 01 Jan 2006
Posts: 1237
|
| Posted: Sat Nov 07, 2009 7:41 pm Post subject: |
|
|
Yes module support (*) is enabled. Not sure I follow this:
"Selected by: GART_IOMMU && X86_64 && PCI
Try checking out those settings (you can search for them in menuconfig by entering a "/" and then type the name). " Now I'm having problems mounting my /boot partition /dev/sdb1. I get the following error "mount:unknown filesystem type 'ext2"...not sure why and i need to copy the bzImage to /boot or it wont boot next time i reboot.
_________________
Gigabyte MA790X-UD4P Motherboard
AMD Phenom II X4 940 Black Edition
MSI ATI R4650 PCIe2
250GB SATA Drive
4GB Corsair DDR2 |
|
| Back to top |
|
|
snakeo2
Veteran
Joined: 01 Jan 2006
Posts: 1237
|
| Posted: Sat Nov 07, 2009 7:47 pm Post subject: |
|
|
sorry to bother, but i have one more question
"Then you can load the modules before you start X using the /etc/modules.autoload.d/kernel-2.6 file. Do not compile these options into the kernel, as you shouldn't use them for the fglrx drivers. " How do i know which modules I need to add to that file? in other words what command can i run that will tell me the modules i should add to modules.autoload? thanks in advance.
_________________
Gigabyte MA790X-UD4P Motherboard
AMD Phenom II X4 940 Black Edition
MSI ATI R4650 PCIe2
250GB SATA Drive
4GB Corsair DDR2 |
|
| Back to top |
|
|
snakeo2
Veteran
Joined: 01 Jan 2006
Posts: 1237
|
| Posted: Sat Nov 07, 2009 8:01 pm Post subject: |
|
|
it turns out i dont have this file " /etc/hal/fdi/policy/10-keymap.fdi". Also, i just ran startx and it crashed. looking at /var/log/xorg.0.log i can see the following errors:
By the way im using x server 1.6.3.901
(EE) problem parsing the config file
(EE) Error parsing the config file
fatal server error:
no screen found
i keep reading about migrating to modular xorg and im wondering if that is something i need to do. also, how about emerging xorg-x11?
_________________
Gigabyte MA790X-UD4P Motherboard
AMD Phenom II X4 940 Black Edition
MSI ATI R4650 PCIe2
250GB SATA Drive
4GB Corsair DDR2 |
|
| Back to top |
|
|
gsoe
Apprentice
Joined: 10 Dec 2006
Posts: 289
Location: Denmark
|
| Posted: Sat Nov 07, 2009 8:07 pm Post subject: |
|
|
| Quote: | | How do i know which modules I need to add to that file? |
Somewhere in menuconfig's help screen it is usually told what the module name will be. Example: If you choose help option when the /dev/agpgart option is highlighted you'll get this somewhere in the screen: | Code: | | To compile this driver as a module, choose M here: the module will be called agpgart. |
|
|
| Back to top |
|
|
gsoe
Apprentice
Joined: 10 Dec 2006
Posts: 289
Location: Denmark
|
| Posted: Sat Nov 07, 2009 8:14 pm Post subject: |
|
|
| Quote: | | (EE) problem parsing the config file |
You have a problem with the syntax of the xorg.conf file. Did you by accident include this | Code: | | less /etc/X11/xorg.conf |
in the file? You shouldn't, that's just the command showing the contents of the file.
| Quote: | | it turns out i dont have this file " /etc/hal/fdi/policy/10-keymap.fdi" |
No, that file doesn't exist by default, you put it there yourself. |
|
| Back to top |
|
|
snakeo2
Veteran
Joined: 01 Jan 2006
Posts: 1237
|
| Posted: Sat Nov 07, 2009 8:18 pm Post subject: |
|
|
got it. however, as i mentioned above, i do not have the option to compile /dev/agpgart as a (M). I went ahead and added it to modules.autoload anyways. I restarted and it loaded module agpgart, but still no x server.
_________________
Gigabyte MA790X-UD4P Motherboard
AMD Phenom II X4 940 Black Edition
MSI ATI R4650 PCIe2
250GB SATA Drive
4GB Corsair DDR2 |
|
| Back to top |
|
|
gsoe
Apprentice
Joined: 10 Dec 2006
Posts: 289
Location: Denmark
|
| Posted: Sat Nov 07, 2009 8:23 pm Post subject: |
|
|
| Can you try starting X, then post the contents of the /var/log/Xorg.0.log file? |
|
| Back to top |
|
|
snakeo2
Veteran
Joined: 01 Jan 2006
Posts: 1237
|
| Posted: Sat Nov 07, 2009 8:26 pm Post subject: |
|
|
in what section of the xorg.conf file would this be
"Code: less /etc/X11/xorg.conf"
_________________
Gigabyte MA790X-UD4P Motherboard
AMD Phenom II X4 940 Black Edition
MSI ATI R4650 PCIe2
250GB SATA Drive
4GB Corsair DDR2 |
|
| Back to top |
|
|
gsoe
Apprentice
Joined: 10 Dec 2006
Posts: 289
Location: Denmark
|
| Posted: Sat Nov 07, 2009 8:30 pm Post subject: |
|
|
| Quote: | in what section of the xorg.conf file would this be
"Code: less /etc/X11/xorg.conf" |
It shouldn't be in the file at all. Neither should | Code: | | newpc linux # cat /etc/hal/fdi/policy/10-keymap.fdi |
be in that file. |
|
| Back to top |
|
|
snakeo2
Veteran
Joined: 01 Jan 2006
Posts: 1237
|
| Posted: Sat Nov 07, 2009 8:41 pm Post subject: |
|
|
Ok, i looked and neither of those lines of code are in the xorg.conf file. i went ahead and ran "startx" and this are the errors and warning im getting.
1. parse error on line 10 of section files in file /etc/X11/xorg.conf
ignoring obsolete keyword "RgbPath"
2. parse error on line 51 of section monitor file in /etc/X11/xorg.conf
"Horizync" is not a valid keyword in this section
(EE) Problem parsing the config file
(EE) Error parsing the config file
fatal server error:
no screen found
/var/log/Xorg.0.log
same errors as the ones listed above. Additionally:
(WW) xf86CloseConsole: KDSETMODE failed: Bad File descriptor
(WW) xf86CloseConsole: VT_GETMODE failed: Bad file descriptor
_________________
Gigabyte MA790X-UD4P Motherboard
AMD Phenom II X4 940 Black Edition
MSI ATI R4650 PCIe2
250GB SATA Drive
4GB Corsair DDR2 |
|
| Back to top |
|
|
gsoe
Apprentice
Joined: 10 Dec 2006
Posts: 289
Location: Denmark
|
| Posted: Sun Nov 08, 2009 1:25 am Post subject: |
|
|
| Quote: | 2. parse error on line 51 of section monitor file in /etc/X11/xorg.conf
"Horizync" is not a valid keyword in this section
|
That's the error: I think you should spell it: Horizsync.
If you have a fairly modern monitor, you don't need anything else than the skeleton xorg.conf file i posted, try that to work around your problems.
Did you check in Xorg.0.log that the vesa driver is in fact loaded? |
|
| Back to top |
|
|
snakeo2
Veteran
Joined: 01 Jan 2006
Posts: 1237
|
| Posted: Sun Nov 08, 2009 2:09 am Post subject: |
|
|
ok, i fixed the typo and now that error about horizsync is gone. I opened /var/log/Xorg.0.log and there is nothing about either loading or failing to load the vesa driver. The error im getting now is:
Undefined screen "default screen" referenced by serverlayout default layout. I'm contemplating doing the following a system update but would like to get x working first. Do i need to emerge the vesa driver?
_________________
Gigabyte MA790X-UD4P Motherboard
AMD Phenom II X4 940 Black Edition
MSI ATI R4650 PCIe2
250GB SATA Drive
4GB Corsair DDR2 |
|
| Back to top |
|
|
VoidMage
Watchman
Joined: 14 Oct 2006
Posts: 6196
|
| Posted: Sun Nov 08, 2009 2:30 am Post subject: |
|
|
Please, start with putting your xorg.conf in a pastebin,
it's really hard to divine your errors without a working crystal ball (mine's still out of order),
to diagnose them, we need to see that config file. |
|
| Back to top |
|
|
snakeo2
Veteran
Joined: 01 Jan 2006
Posts: 1237
|
| Posted: Sun Nov 08, 2009 6:58 pm Post subject: |
|
|
Ok, I finally was able to download the livedvd. here is a copy of my xorg.conf file:
Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Detault Screen" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
Option "OffTime" "20"
EndSection
Section "Files"
RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib64/xorg/modules"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/OTF"
FontPath "/usr/share/fonts/Type1/"
FontPath "/usr/share/fonts/CID/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/75dpi/"
EndSection
Section "Module"
Load "extmod"
Load "dbe"
Load "record"
Load "xtrap"
Load "dri"
Load "glx"
Load "freetype"
Load "type1"
EndSection
Section "InputDevice"
Identifier "Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "Protocol" "IMPS/2"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "MultiSync LCD1765"
Horizsync 31.5 - 64.3
VertRefresh 50 - 100
VendorName "NEC"
ModelName "Monitor Model"
Option "DPMS"
EndSection
Section "Device"
Identifier "Standard Video Card"
Driver "vesa"
VendorName "ATI Technologies Inc"
BoardName "R4650 [Radeon HD 4650]"
BusID "PCI:1:0:0"
Option "AddARGBGLXVisuals" "True"
Option "DPMS" "TRUE"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1024x768""1280x1024""1024x768""800x600""640x480"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Depth 24
Modes "1024x768""1280x1024""1024x768""800x600""640x480"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x1024""1024x768""800x600""640x480"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Section "Extensions"
Option "Composite" "Enable"
EndSection
the output of /var/log/Xorg.0.log is really big and I cant figure out how to copy the entire log without having to scroll down page by page which is very tedious but more importantly can leave parts of the log out. Does anyone know how to copy the entire log without scrolling down one page at a time? Thanks to everyone.
_________________
Gigabyte MA790X-UD4P Motherboard
AMD Phenom II X4 940 Black Edition
MSI ATI R4650 PCIe2
250GB SATA Drive
4GB Corsair DDR2 |
|
| Back to top |
|
|
VoidMage
Watchman
Joined: 14 Oct 2006
Posts: 6196
|
| Posted: Sun Nov 08, 2009 8:12 pm Post subject: |
|
|
Obviously, when you were modifying the file, you didn't really know, what you were doing.
"Detault Screen" would be a typo if not for the fact it's nowhere defined.
Things like 'Identifier' are just labels, their value doesn't really matter.
You've defined "MultiSync LCD1765" identifier, then you've never used it.
Put in in 'ServerLayout', replacing "Detault Screen" typo.
Decide if you want open or closed driver.
As hal/dbus are running, make sure evdev driver is emerged and
remove (comment out) 'InputDevice' sections and 'InputDevice' lines in 'ServerLayout'.
And there's always pastebin (and wgetpaste). |
|
| Back to top |
|
|
snakeo2
Veteran
Joined: 01 Jan 2006
Posts: 1237
|
| Posted: Sun Nov 08, 2009 10:00 pm Post subject: |
|
|
Voidmage
Thanks for the suggestions. In all honesty, I dont really know what I'm doing when it comes to x server. As far as which driver I want, i'll settle for the one that works. I've read that closed drivers can be a problem so for now I would settle for the open driver. Here is my xorg.conf file with the edits you suggested:
Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "MultiSync LCD 1765" 0 0
#InputDevice "Mouse0" "CorePointer"
#InputDevice "Keyboard0" "CoreKeyboard"
Option "OffTime" "20"
EndSection
#Section "InputDevice"
Identifier "Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
EndSection
#Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "Protocol" "IMPS/2"
Option "ZAxisMapping" "4 5 6 7"
EndSection
I will try "startx" and report back. thanks again for the help.
_________________
Gigabyte MA790X-UD4P Motherboard
AMD Phenom II X4 940 Black Edition
MSI ATI R4650 PCIe2
250GB SATA Drive
4GB Corsair DDR2 |
|
| Back to top |
|
|
VoidMage
Watchman
Joined: 14 Oct 2006
Posts: 6196
|
| Posted: Sun Nov 08, 2009 10:16 pm Post subject: |
|
|
Of course this won't work - "comment out the section"
means "comment each line from section start to matching 'EndSection'".
Also: most recent monitors (especially LCD) don't need sync values
in xorg.conf - see if it works without.
Set the name of video driver to "radeon'. |
|
| Back to top |
|
|
snakeo2
Veteran
Joined: 01 Jan 2006
Posts: 1237
|
| Posted: Sun Nov 08, 2009 10:26 pm Post subject: |
|
|
is this what you mean?
#Section "InputDevice"
#Identifier "Keyboard"
#Driver "kbd"
#Option "CoreKeyboard"
#Option "XkbRules" "xorg"
#Option "XkbModel" "pc105"
EndSection#
_________________
Gigabyte MA790X-UD4P Motherboard
AMD Phenom II X4 940 Black Edition
MSI ATI R4650 PCIe2
250GB SATA Drive
4GB Corsair DDR2 |
|
| Back to top |
|
|
VoidMage
Watchman
Joined: 14 Oct 2006
Posts: 6196
|
| Posted: Sun Nov 08, 2009 11:10 pm Post subject: |
|
|
More like this
| Code: |
#Section "InputDevice"
#Identifier "Keyboard"
#Driver "kbd"
#Option "CoreKeyboard"
#Option "XkbRules" "xorg"
#Option "XkbModel" "pc105"
#EndSection
|
'#' in this file is a "till end of line" comment, not a block one. |
|
| Back to top |
|
|
snakeo2
Veteran
Joined: 01 Jan 2006
Posts: 1237
|
| Posted: Sun Nov 08, 2009 11:16 pm Post subject: |
|
|
As I mentioned above, I could not compile agpgart as (M) so I'm wondering if there has something to do with x not working.
-*- /dev/agpgart (AGP Support) ---> │ │
│ │ <M> Direct Rendering Manager (XFree86 4.1.0 and higher DRI suppor│ │
│ │ < > Lowlevel video output switch controls │ │
│ │ <*> Support for frame buffer devices ---> │ │
│ │ [*] Backlight & LCD device support ---> │ │
│ │ Display device support ---> │ │
│ │ Console display driver support --->
--- /dev/agpgart (AGP Support) │ │
│ │ < > Intel 440LX/BX/GX, I8xx and E7x05 chipset support │ │
│ │ < > SiS chipset support │ │
│ │ < > VIA chipset support
eselect opengl list
Available OpenGL implementations:
[1] ati
[2] xorg-x11 *
when i run startx..i get the following error:
startx
/etc/host.conf: line 24: bad command `mdns off'
hostname: Unknown host
xauth: creating new authority file /root/.serverauth.11015
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
Fatal server error:
Cannot establish any listening sockets - Make sure an X server isn't already running
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
giving up.
xinit: No such file or directory (errno 2): unable to connect to X server
xinit: No such process (errno 3): Server error.
lsmod | grep "drm\|radeon\|agp"
radeon 358096 1
drm 167872 2 radeon
i2c_core 25216 2 drm,i2c_piix4
_________________
Gigabyte MA790X-UD4P Motherboard
AMD Phenom II X4 940 Black Edition
MSI ATI R4650 PCIe2
250GB SATA Drive
4GB Corsair DDR2 |
|
| Back to top |
|
|
VoidMage
Watchman
Joined: 14 Oct 2006
Posts: 6196
|
| Posted: Mon Nov 09, 2009 12:22 am Post subject: |
|
|
In reverse order:
see what's the problem with /etc/conf.d/hostname
remove the invalid command from /etc/host.conf
as for agpart, just guessing, but to build it as a module,
you need to build things that depend on it as modules too and
it seems that you've builtin something there - enter that option
and set it to module
Are you sure the server isn't already running ? |
|
| Back to top |
|
|
|
Desktop Environments
