| View previous topic :: View next topic |
| Author |
Message |
jakamaka
Apprentice
Joined: 17 Jun 2004
Posts: 266
Location: My self-sustainable fusion of thought
|
 Posted: Sat Jun 19, 2004 7:40 pm Post subject: xserver crashes with ati radeon fglrx |
 |
|
hi uhm, i did a fresh install of gentoo today
everything went fine, i succesfully rebooted into my gentoo system
during the install i already installed xfree86
when i rebooted in gentoo the first thing i did was the install of my ati drivers (using emerge ati-drivers), then i rebooted once more
after that i ran fglrxconfig and configured my ati card (i have a ati radeon 9600 pro)
then i tested my xserver and it crashed, i get the following error >
| Quote: | (WW) fglrx: No matching Device section for instance (BusID PCI :2:0:1) found
FATAL : Module fglrx not found
[drm] failed to load kernel module "fglrx"
(EE) fglrx(0) : DRIScreenInit failed !
(WW) fglrx(0) : Failed to setup unite-combining range (0x0000000,0x8000000)
xterm: fatal IO error 32 (Broken pipe) or Killclient on X server ":0.0"
waiting for system to shut down |
so my ati driver doesn't work, do i have to install kernel modules or something ?
i'm wonderring also is this is correct; when the xserver starts, it says | Quote: | Xfree86 version 4.3.0.1
Release Date : 15 August 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.6.5-gentoo i686 [ELF] |
the thing is i'm using a linux 2.6.7 kernel and not a 2.6.5
any help would be appreciated, can anyone tell me exacly what to do to get my xserver working properly with ati radeon support, and for that do i first have to uninstall the ati driver ? ......
_________________
It would be more interesting to learn from children, than try to teach them how to behave, how to live and how to function. - U.G. Krishnamurti |
|
| Back to top |
|
 |
Wedge_
Advocate
Joined: 08 Aug 2002
Posts: 3614
Location: Scotland
|
| Posted: Sat Jun 19, 2004 7:55 pm Post subject: |
|
|
First, check that the /usr/src/linux symlink is pointing to your 2.6.7 kernel sources. When you emerge ati-drivers, it compiles a kernel module against the kernel in /usr/src/linux, so if the link is wrong, it builds the module for the wrong kernel and you can't use it. Once you've done that, you need to load the driver module (it's just called "fglrx") before you start X, otherwise 3D acceleration won't work. This is what's producing these error messages: | Code: | FATAL : Module fglrx not found
[drm] failed to load kernel module "fglrx"
(EE) fglrx(0) : DRIScreenInit failed ! |
To have the module loaded automatically on bootup, do | Code: | | echo "fglrx" >> /etc/modules.autoload.d/kernel-2.6 |
| Quote: | Build Operating System: Linux 2.6.5-gentoo i686 [ELF]
the thing is i'm using a linux 2.6.7 kernel and not a 2.6.5 |
That line just tells you the kernel that was in use when you emerged X. It doesn't matter if you're using a newer kernel now.
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ |
|
| Back to top |
|
|
jakamaka
Apprentice
Joined: 17 Jun 2004
Posts: 266
Location: My self-sustainable fusion of thought
|
| Posted: Sat Jun 19, 2004 8:03 pm Post subject: |
|
|
| Wedge_ wrote: | First, check that the /usr/src/linux symlink is pointing to your 2.6.7 kernel sources. When you emerge ati-drivers, it compiles a kernel module against the kernel in /usr/src/linux, so if the link is wrong, it builds the module for the wrong kernel and you can't use it. Once you've done that, you need to load the driver module (it's just called "fglrx") before you start X, otherwise 3D acceleration won't work. This is what's producing these error messages: | Code: | FATAL : Module fglrx not found
[drm] failed to load kernel module "fglrx"
(EE) fglrx(0) : DRIScreenInit failed ! |
To have the module loaded automatically on bootup, do | Code: | | echo "fglrx" >> /etc/modules.autoload.d/kernel-2.6 |
| Quote: | Build Operating System: Linux 2.6.5-gentoo i686 [ELF]
the thing is i'm using a linux 2.6.7 kernel and not a 2.6.5 |
That line just tells you the kernel that was in use when you emerged X. It doesn't matter if you're using a newer kernel now. |
k thx, but uhm how do i check if /usr/src/linux symlink is pointing to the 2.6.7 kernel sources and if it's not how do create this link ?
_________________
It would be more interesting to learn from children, than try to teach them how to behave, how to live and how to function. - U.G. Krishnamurti |
|
| Back to top |
|
|
Wedge_
Advocate
Joined: 08 Aug 2002
Posts: 3614
Location: Scotland
|
| Posted: Sat Jun 19, 2004 8:27 pm Post subject: |
|
|
Do this: | Code: | | ls -l /usr/src/linux |
That should produce something similar to this: | Code: | lrwxrwxrwx 1 root root 30 Jun 14 19:47 /usr/src/linux -> /usr/src/linux-2.6.7-rc3-love2
|
What you need to check is that the version number at the end (ie "2.6.7-rc3-love2" in my example) matches the output of "uname -r". If it does, then the link is correct. If it's wrong, you can fix it by doing this: | Code: | rm -f /usr/src/linux
ln -s /usr/src/linux-`uname -r` /usr/src/linux |
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ |
|
| Back to top |
|
|
jakamaka
Apprentice
Joined: 17 Jun 2004
Posts: 266
Location: My self-sustainable fusion of thought
|
| Posted: Sat Jun 19, 2004 8:42 pm Post subject: |
|
|
ah k
thanks for the help
really appreciate it
_________________
It would be more interesting to learn from children, than try to teach them how to behave, how to live and how to function. - U.G. Krishnamurti |
|
| Back to top |
|
|
Zyne
Guru
Joined: 08 Jun 2004
Posts: 334
|
| Posted: Sat Jun 19, 2004 10:00 pm Post subject: |
|
|
ok, I may be wrong here, but I think the fact that your fglrx isn't working, is because you pointed it to the wrong BusID...
| Code: |
(WW) fglrx: No matching Device section for instance (BusID PCI :2:0:1) found |
this pretty much means that you don't have a device on BusID 2:0:1
mine for instance is on BusID 2:0:0 (I think)
what you could try to do, is comment the line with the BusID. I've done it with my XF86Config-4, and it seems to work 
I just finished installing the ati-drivers a few days ago, and I must say everything worked immediately after fiddling around with the XF86Config-4 file. I had the same problem you have now (the one with the fglrx not found), but that was quickly resolved once I found out what was wrong (the BusID in my case)
btw could you also check what modules you have running?
run lsmod, and post your results.
I get this for my comp:
| Code: |
philip@vubserver / $ lsmod
Module Size Used by
fglrx 212516 7
ndiswrapper 72768 0
|
edit:
oh, and another thing. add fglrx to /etc/modules.autoload.d/kernel-2.6, so that it autoloads on startup (that's how I fixed it) |
|
| Back to top |
|
|
jakamaka
Apprentice
Joined: 17 Jun 2004
Posts: 266
Location: My self-sustainable fusion of thought
|
| Posted: Sun Jun 20, 2004 11:04 am Post subject: |
|
|
| Zyne wrote: | ok, I may be wrong here, but I think the fact that your fglrx isn't working, is because you pointed it to the wrong BusID...
| Code: |
(WW) fglrx: No matching Device section for instance (BusID PCI :2:0:1) found |
this pretty much means that you don't have a device on BusID 2:0:1
mine for instance is on BusID 2:0:0 (I think)
what you could try to do, is comment the line with the BusID. I've done it with my XF86Config-4, and it seems to work
I just finished installing the ati-drivers a few days ago, and I must say everything worked immediately after fiddling around with the XF86Config-4 file. I had the same problem you have now (the one with the fglrx not found), but that was quickly resolved once I found out what was wrong (the BusID in my case)
btw could you also check what modules you have running?
run lsmod, and post your results.
I get this for my comp:
| Code: |
philip@vubserver / $ lsmod
Module Size Used by
fglrx 212516 7
ndiswrapper 72768 0
|
edit:
oh, and another thing. add fglrx to /etc/modules.autoload.d/kernel-2.6, so that it autoloads on startup (that's how I fixed it) |
ooh man 
the fact is in gentoo my x didn't work at all, so o thought > i install the ati-drivers, then they didn't work either so i tried the things wedge told me > but the thing is, everything was fine
but it still didn't work
now because i couldn't do anything with gentoo, 'cause i couldn't get x working, it put fedora back on (slow os, but it works fine),
so ur telling me if i did the things u told me there might be a good chance gentoo x would have worked ?
goddamned :s
_________________
It would be more interesting to learn from children, than try to teach them how to behave, how to live and how to function. - U.G. Krishnamurti |
|
| Back to top |
|
|
jakamaka
Apprentice
Joined: 17 Jun 2004
Posts: 266
Location: My self-sustainable fusion of thought
|
| Posted: Sun Jun 20, 2004 11:08 am Post subject: |
|
|
but hey, this is what i'm gonna do > i'm gonna install gentoo again today('cause yesterdag it took about 6 hours, with a lot of reading, it is possible that i can install it in less.
it doesn't matter, 'cause i got to study for my exams, so i won't be bored
and i'll post the results this evening...
_________________
It would be more interesting to learn from children, than try to teach them how to behave, how to live and how to function. - U.G. Krishnamurti |
|
| Back to top |
|
|
Zyne
Guru
Joined: 08 Jun 2004
Posts: 334
|
| Posted: Sun Jun 20, 2004 11:51 am Post subject: |
|
|
| seikura wrote: |
so ur telling me if i did the things u told me there might be a good chance gentoo x would have worked ?
|
well.. Gentoo x is working fine over here...
I had it running without 3D renderer, and managed to get it running with 3D renderer after a few changes to the XF86Config-4
I did use he xf86config though to create a working XF86Config file. then I built on that one to create my XF86Config-4
btw good luck with your exams... I'm having my last one on friday :p |
|
| Back to top |
|
|
jakamaka
Apprentice
Joined: 17 Jun 2004
Posts: 266
Location: My self-sustainable fusion of thought
|
| Posted: Sun Jun 20, 2004 12:09 pm Post subject: |
|
|
lol thx, my last one is on tuesday
but uhm, do u got to have a working xf86config file or is it possible to get x working with a xf86config-4 file ?
'cause i couldn't get x working with regular xf86config(maybe i was too lazy to change resolution and bit color) , so i thought to install the fglrx drivers instead
but uhm, i read somewhere that there were some problems with built-in gentoo drivers, the radeonfb drivers tend to give conflicts with a 2.6.7 kernel .... (don't know for sure, but i thought i've seen it somewhere)
_________________
It would be more interesting to learn from children, than try to teach them how to behave, how to live and how to function. - U.G. Krishnamurti |
|
| Back to top |
|
|
Zyne
Guru
Joined: 08 Jun 2004
Posts: 334
|
| Posted: Sun Jun 20, 2004 12:33 pm Post subject: |
|
|
it's my experience that it's easier to begin with a working XF86Config, and work your way up from there...
adding direct3Drendering basically means you just gotta add a few lines, and replace the default driver in the XF86Config.
I would highly suggest to get Xfree to work without fglrx, and then move on to installing fglrx. That was the easiest solution for me...
running xf86config in console will give you a nice wizard to go through. You can set all resolutions and refresh rates there. |
|
| Back to top |
|
|
jakamaka
Apprentice
Joined: 17 Jun 2004
Posts: 266
Location: My self-sustainable fusion of thought
|
| Posted: Sun Jun 20, 2004 12:39 pm Post subject: |
|
|
| Zyne wrote: | it's my experience that it's easier to begin with a working XF86Config, and work your way up from there...
adding direct3Drendering basically means you just gotta add a few lines, and replace the default driver in the XF86Config.
I would highly suggest to get Xfree to work without fglrx, and then move on to installing fglrx. That was the easiest solution for me...
running xf86config in console will give you a nice wizard to go through. You can set all resolutions and refresh rates there. |
yeah i know how to configure X, and that's what i did before fglrx, but maybe u can give me some hints for the settings ?
But the fact that doesn't work either could the fact that my BUS is not set properly as u said earlier in this thread > so if i change that setting, than it should work, either way, i'm getting myself a nvidia card, i'm sick of this nonsens, every linuxdistro i've tried it was a shitty way to get there(exept for fedora, but u don't have 3d support either)
and u say i have to replace the default driver in the XF86Config
does the XF86Config-4 file do that or something ?
'cause in the manual they don't say anything about adding a few linux here and there
according to them it should all work 
I have some experience with fedora and there i had to replace the driver section (in the x.org config file with the driver/identifer lines from the XF86Config-4 file) and it worked fine
u see, even the ati users are affected by the monopoly of Gates'Microshit,
Ati prolly just doesn't see the point of spending money for decent workhours or decent programmers who make decent fglrx drivers ... 
_________________
It would be more interesting to learn from children, than try to teach them how to behave, how to live and how to function. - U.G. Krishnamurti |
|
| Back to top |
|
|
Wedge_
Advocate
Joined: 08 Aug 2002
Posts: 3614
Location: Scotland
|
| Posted: Sun Jun 20, 2004 1:10 pm Post subject: |
|
|
| Zyne wrote: | ok, I may be wrong here, but I think the fact that your fglrx isn't working, is because you pointed it to the wrong BusID...
| Code: | | (WW) fglrx: No matching Device section for instance (BusID PCI :2:0:1) found |
this pretty much means that you don't have a device on BusID 2:0:1
mine for instance is on BusID 2:0:0 (I think) |
No, it means that there is no section in the config for the secondary device on the card. The primary will be on 2:0:0 and is presumably getting detected correctly. That message appears in most configurations, but you can ignore it. The "(WW)" prefix indicates a warning, not an error. fglrxconfig does sometimes get the BusID for the primary device wrong (ie it'll use 2:0:1 instead of 2:0:0) so some people need to set it manually.
| seikura wrote: | | but uhm, i read somewhere that there were some problems with built-in gentoo drivers, the radeonfb drivers tend to give conflicts with a 2.6.7 kernel .... (don't know for sure, but i thought i've seen it somewhere) |
The radeonfb drivers often cause problems when used with the ATI fglrx driver, such as screen corruption or system hangs when switching between X and the console. It's better to use the VESA fb driver instead.
As for creating a config file, fglrxconfig should give you a good starting point. Change the "Driver" setting to "vesa" temporarily, and see if it starts up like that. If it does, then your config is basically OK, and you can then change the driver back to "fglrx" and check if 3D accel is working.
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ |
|
| Back to top |
|
|
jakamaka
Apprentice
Joined: 17 Jun 2004
Posts: 266
Location: My self-sustainable fusion of thought
|
| Posted: Sun Jun 20, 2004 1:26 pm Post subject: |
|
|
ah k
so i first configure x without fglrx drivers(mark vesa driver, temporary) see if this works, if not, change the BusID if it's set wrong
then i install the fglrxdrivers and replace the vesadriver with fglrx and then i test to see if my 3d acceleration works
will try , hope it works, but it shall work eventually...
_________________
It would be more interesting to learn from children, than try to teach them how to behave, how to live and how to function. - U.G. Krishnamurti |
|
| Back to top |
|
|
Wedge_
Advocate
Joined: 08 Aug 2002
Posts: 3614
Location: Scotland
|
| Posted: Sun Jun 20, 2004 1:29 pm Post subject: |
|
|
The BusID should be detected OK, going by what you posted earlier. The message that Zyne mentioned is normal, don't worry if you see it.
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ |
|
| Back to top |
|
|
jakamaka
Apprentice
Joined: 17 Jun 2004
Posts: 266
Location: My self-sustainable fusion of thought
|
| Posted: Sun Jun 20, 2004 2:01 pm Post subject: |
|
|
| Wedge_ wrote: | | The BusID should be detected OK, going by what you posted earlier. The message that Zyne mentioned is normal, don't worry if you see it. |
ah k, then i'll do what i mentioned without the BusID
but uhm, with my first install i did the things u told me like the symlink
but still it got the same error message
'cause when gentoo booted i could see when it began to load modules that ii 'failed to load fglrx' 
prolly i didn't set the symlink correctly
the thing is why i'm asking so much 'cause i don't want to mess up my x server completely...
i know some people who have had that several times , and it's not funny, luckily for gentoo u can uninstall x(i thought) 'cause in several distros it's not that easy
_________________
It would be more interesting to learn from children, than try to teach them how to behave, how to live and how to function. - U.G. Krishnamurti |
|
| Back to top |
|
|
Wedge_
Advocate
Joined: 08 Aug 2002
Posts: 3614
Location: Scotland
|
| Posted: Sun Jun 20, 2004 2:28 pm Post subject: |
|
|
OK, if the module still won't load, you need to find out why it's doing that. After running "modprobe fglrx", run the "dmesg" command. Near the end of the output, there should be 2 or 3 lines that start with "fglrx:". They should tell you what the error actually is. Post them here if you're not sure.
_________________
Per Ardua Ad Astra
The Earth is the cradle of the mind, but we cannot live forever in a cradle - Konstantin E. Tsiolkovsky
Gentoo Radeon FAQ |
|
| Back to top |
|
|
jakamaka
Apprentice
Joined: 17 Jun 2004
Posts: 266
Location: My self-sustainable fusion of thought
|
| Posted: Sun Jun 20, 2004 3:02 pm Post subject: |
|
|
| Wedge_ wrote: | | OK, if the module still won't load, you need to find out why it's doing that. After running "modprobe fglrx", run the "dmesg" command. Near the end of the output, there should be 2 or 3 lines that start with "fglrx:". They should tell you what the error actually is. Post them here if you're not sure. |
again thx for the help
will do
_________________
It would be more interesting to learn from children, than try to teach them how to behave, how to live and how to function. - U.G. Krishnamurti |
|
| 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
|
|
Desktop Environments
