Summary: | fglrx fails to load with error: FATAL: Error inserting fglrx (/lib/modules/2.6.11-ck2/video/fglrx.ko): No such device | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Peter Parkanyi <rhapsodhy> |
Component: | Current packages | Assignee: | X11 External Driver Maintainers <x11-drivers> |
Status: | RESOLVED WONTFIX | ||
Severity: | minor | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
/proc/pci
lspci My xorg.conf created with fglrxconfig - comments removed lspci output full 'dmesg' output .config listing |
Description
Peter Parkanyi
2005-03-28 10:57:26 UTC
Created attachment 54696 [details]
/proc/pci
The 'cat /proc/pci' output.
Created attachment 54697 [details]
lspci
The 'lspci' output
Please look at what your assigning bugs to Created attachment 54699 [details]
My xorg.conf created with fglrxconfig - comments removed
Sorry. I've forgotten to specify the kernel versions i tried with: 2.6.{10,11}-ck Another thing: this is NOT a notebook. This is a simple desktop PC. The VGA card is : Sapphire Radeon 9600 128Mb TVOut DVI Somehow I have a feeling that it's not supposed to detect it as a mobility... This was working with the previous driver version? Also, are you building any AGP drivers in-kernel? Neither worked with previous versions. In the kernel there are : agpgart + nvidia gart(compiled in) Direct rendering manager(compiled in) + ati radeon driver(module) framebuffer stuff + radeon driver(new, compiled in) The PCI ID database reports it as a Mobility, so apparently it's either incorrect or Sapphire re-used the same ID -- http://pciids.sourceforge.net/iii/?i=10024e51. But that may not matter. I don't really understand why you're compiling all this stuff into your kernel when ati-drivers is supplying it. That may be causing some problems. For example: Direct rendering manager(compiled in) + ati radeon driver(module) That stuff shouldn't be in your kernel at all if you're using ati-drivers. thank you, i'll try it ! I compiled either agpgart + nvidia gart, and drm + radeon as modules. Then remerged the ati-drivers, modules-update, and modprobe fglrx. But i get the same error :( Donnie meant that you shouldn't compile DRI/Radeon driver at all. Those are to be used instead of fglrx if you don't want 3D acceleration on modern cards. Have you tried changing your xorg.conf to use 'BusID "PCI:1:0:1"' instead of 'BusID "PCI:1:0:0"' ? The warning given during startup seems to indicate that may give you some results... 1:0:1 is a fake secondary device required for Windows to do dual-head. #12: Is it problem if the drm components are in module, but they aren't in kernel ? I don't think so. Anyway, I tried without it, but fglrx still fails to load. Have you seen my xorg.conf ? If you take a look at it, you will see there's no line in it like: BusID "PCI:1:0:1" but the line: BusID "PCI:1:0:0" is included in the correct 'Device' section. Donnie: I realize that, I just didn't know if that warning was normal or not. I looked through my Xorg again (I use ATI) and I found it, so my bad. Peepy: I was just suggesting that you should try it, but now that I've looked at my config again I know that won't do anything. I really don't see any reason for it to fail except for that weird mis-detection...to me that indicates a possible hardware problem that the new drivers may be picky about... ATI released a new driver a few days ago. You might try emerging that. It is masked so you will need: emerge sync ACCEPT_KEYWORDS="~x86" emerge ati-drivers This will give you version 8.14.13-r1 ATI released a new driver a few days ago. You might try emerging that. It is masked so you will need: emerge sync ACCEPT_KEYWORDS="~x86" emerge ati-drivers This will give you version 8.14.13-r1 I have an ATI Radeon X800 XL card and this was the first ATI driver that recognised my card. I have similar problem. I use HP ze4508ea laptop. It has built-in Ati Radeon Mobility 320 (U1) graphics chip. ati-drivers reports that it supports it, but I can't even "modprobe fglrx" because of an error that is this bug for: "fglrx fails to load with error: FATAL: Error inserting fglrx (/lib/modules/2.6.12-10-r1/video/fglrx.ko): No such device" I use ati-drivers 8.4.13-r2, I have fresh 2005.1 gentoo installation with Xorg 6.8.2 installed. Use flags are "gnome gtk gtk2 qt -kde X" Any ideas for solving this? Thanks P.S I use correct BusID, and with "radeon" driver instead "fglrx" X loads fine but with no acceleration whatsoever. Attach your `dmesg` after a driver failure please. sure thing. When I try 'modprobe fglrx' I get FATAL: Error inserting fglrx (/lib/modules/2.6.12-gentoo-r10/video/fglrx.ko): No such device right after that, 'dmesg' has this tailed: fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel. [fglrx] Maximum main memory to use for locked dma buffers: 143 MBytes [fglrx:firegl_init] *ERROR* Device not found! K, attach your `lspci` output as well. Created attachment 68332 [details]
lspci output
Completely disable DRM from kernel. and/or attach the dmesg output I have no DRM compiled whether inside kernel or as module and 'dmesg' output can be seen in comment #20 Sorry, I mean the full dmesg Created attachment 68357 [details]
full 'dmesg' output
Sure thing.
ok, now I need the kernel .config (sorry I know I'm asking lots of stuf..) Created attachment 68426 [details]
.config listing
missing GART support from what I can see, build it as module and please use the latest p.masked driver. echo =media-video/ati-drivers-8.16.20* -* >> /usr/portage/package.keywords What do you mean by GART? and I did upgrade to 8.16.20, all effects are still happening. AGP gart, w/out the module can't work (you need the igp one probably) Got it. If you take a look inside .config, you'll see CONFIG_AGP=y Is that what you mean? If you do, I have it compiled into kernel, not as module. And ATI's readme says NOT to compile DRM at all, not even as module. # CONFIG_AGP_ATI is not set Should Well, here's an excerpt from ATI's Release Notes: "Note: In order to use the fglrx internal AGP support, you have to make sure that the kernel agpgart support is not active, i.e. it is not compiled into the kernel and the kernel modules are not loaded. If the fglrx kernel module detects that the kernel agpgart support is active, it will automatically use that even if its internal AGP support is requested in order to avoid conflicts that can cause problems under some circumstances" So whats the point of making 'CONFIG_AGP_ATI' to 'y' ?? I'd suggest you to use the kernel agp gart module and not rely on the internal one. Old; file a new bug if you have issues w/ current x11-drivers/ati-drivers and *supported* kernels. |