Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 87003 - fglrx fails to load with error: FATAL: Error inserting fglrx (/lib/modules/2.6.11-ck2/video/fglrx.ko): No such device
Summary: fglrx fails to load with error: FATAL: Error inserting fglrx (/lib/modules/2....
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High minor (vote)
Assignee: X11 External Driver Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-28 10:57 UTC by Peter Parkanyi
Modified: 2007-04-01 21:58 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
/proc/pci (pci,3.73 KB, text/plain)
2005-03-28 10:58 UTC, Peter Parkanyi
Details
lspci (lspci,1.46 KB, text/plain)
2005-03-28 10:59 UTC, Peter Parkanyi
Details
My xorg.conf created with fglrxconfig - comments removed (xorg.conf,4.15 KB, text/plain)
2005-03-28 11:04 UTC, Peter Parkanyi
Details
lspci output (1,958 bytes, text/plain)
2005-09-13 00:38 UTC, Alex Bogak
Details
full 'dmesg' output (1,11.66 KB, text/plain)
2005-09-13 06:29 UTC, Alex Bogak
Details
.config listing (.config,28.97 KB, text/plain)
2005-09-13 22:25 UTC, Alex Bogak
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Parkanyi 2005-03-28 10:57:26 UTC
I emerged ati-drivers version 8.10.19 today but when i tried to insert the module fglrx i get this error from modprobe:
FATAL: Error inserting fglrx (/lib/modules/2.6.11-ck2/video/fglrx.ko): No such device

I've already had an ATI configured xorg.conf file before, so i modified it for the new driver. However when i tried to start the X with command startx i got this error:

X Window System Version 6.8.2
Release Date: 9 February 2005
X Protocol Version 11, Revision 0, Release 6.8.2
Build Operating System: Linux 2.6.10-ck5 i686 [ELF] 
Current Operating System: Linux petykooz 2.6.11-ck2 #1 Sat Mar 26 20:48:46 CET 2005 i686
Build Date: 14 March 2005
	Before reporting problems, check http://wiki.X.Org
	to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Mon Mar 28 20:48:54 2005
(==) Using config file: "/etc/X11/xorg.conf"
Using vt 8
(WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found
(EE) No devices detected.

Fatal server error:
no screens found

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.1.log" for additional information.

XIO:  fatal IO error 104 (Connection reset by peer) on X server ":1.0"

      after 0 requests (0 known processed) with 0 events remaining.


However in the xorg.cong i've included the line:
BusID "PCI:1:0:0"
to the correct section.

Reproducible: Always
Steps to Reproduce:
1.emerge ati-drivers
2.modprobe fglrx
3.startx




Portage 2.0.51.19 (default-linux/x86/2004.3, gcc-3.4.3-20050110,
glibc-2.3.4.20050125-r1, 2.6.11-ck2 i686)
=================================================================
System uname: 2.6.11-ck2 i686 AMD Athlon(tm) 
Gentoo Base System version 1.4.16
Python:              dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb  9 2005, 11:43:35)]
dev-lang/python:     2.3.4-r1
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.4
sys-devel/binutils:  2.15.92.0.2-r1
sys-devel/libtool:   1.5.10-r4
virtual/os-headers:  2.6.8.1-r1, 2.6.8.1-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-march=athlon-xp -O3 -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=athlon-xp -O3 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache cvs digest distcc distlocks noauto
notitles sfperms"
GENTOO_MIRRORS="http://gentoo.mirror.icd.hu/ http://ftp.heanet.ie/pub/gentoo/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 3dnow X acpi alsa apm avi berkdb bitmap-fonts cdr crypt cups curl
directfb divx4linux emboss esd fam fbcon flac font-server foomaticdb fortran
gdbm gif gpm gtk gtk2 icq imagemagick imlib java jpeg junit libg++ libwww mad
mikmod mmx mmx2 motif mp3 mpeg msn mysql ncurses nls nobcel norhino noxalan
oggvorbis opengl oss pam pdflib perl png python quicktime readline samba sdl
slang spell sse ssl svga tcpd tiff truetype truetype-fonts type1-fonts xml2 xmms
xv xvid zlib video_cards_radeon"
Unset:  ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY
Comment 1 Peter Parkanyi 2005-03-28 10:58:38 UTC
Created attachment 54696 [details]
/proc/pci

The 'cat /proc/pci' output.
Comment 2 Peter Parkanyi 2005-03-28 10:59:12 UTC
Created attachment 54697 [details]
lspci

The 'lspci' output
Comment 3 Lance Albertson (RETIRED) gentoo-dev 2005-03-28 11:02:00 UTC
Please look at what your assigning bugs to
Comment 4 Peter Parkanyi 2005-03-28 11:04:12 UTC
Created attachment 54699 [details]
My xorg.conf created with fglrxconfig - comments removed
Comment 5 Peter Parkanyi 2005-03-28 11:06:03 UTC
Sorry. I've forgotten to specify the kernel versions i tried with: 2.6.{10,11}-ck
Comment 6 Peter Parkanyi 2005-03-29 04:37:27 UTC
Another thing: this is NOT a notebook. This is a simple desktop PC. The VGA card is : Sapphire Radeon 9600 128Mb TVOut DVI
Comment 7 Joshua Baergen (RETIRED) gentoo-dev 2005-03-30 13:27:10 UTC
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?
Comment 8 Peter Parkanyi 2005-03-31 06:02:57 UTC
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)
Comment 9 Donnie Berkholz (RETIRED) gentoo-dev 2005-03-31 11:59:03 UTC
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.
Comment 10 Peter Parkanyi 2005-04-01 07:26:54 UTC
thank you, i'll try it !
Comment 11 Peter Parkanyi 2005-04-01 08:34:34 UTC
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 :(
Comment 12 Joshua Baergen (RETIRED) gentoo-dev 2005-04-01 15:37:22 UTC
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...
Comment 13 Donnie Berkholz (RETIRED) gentoo-dev 2005-04-01 18:46:29 UTC
1:0:1 is a fake secondary device required for Windows to do dual-head.
Comment 14 Peter Parkanyi 2005-04-02 02:05:14 UTC
#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.
Comment 15 Joshua Baergen (RETIRED) gentoo-dev 2005-04-02 12:22:29 UTC
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...
Comment 16 Wilson M. Michaels 2005-06-22 15:35:05 UTC
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
Comment 17 Wilson M. Michaels 2005-06-22 19:09:08 UTC
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.
Comment 18 Alex Bogak 2005-09-11 02:11:33 UTC
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.
Comment 19 Joshua Baergen (RETIRED) gentoo-dev 2005-09-11 08:45:00 UTC
Attach your `dmesg` after a driver failure please.
Comment 20 Alex Bogak 2005-09-12 13:17:21 UTC
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!
Comment 21 Joshua Baergen (RETIRED) gentoo-dev 2005-09-12 15:26:40 UTC
K, attach your `lspci` output as well.
Comment 22 Alex Bogak 2005-09-13 00:38:13 UTC
Created attachment 68332 [details]
lspci output
Comment 23 Luca Barbato gentoo-dev 2005-09-13 00:49:44 UTC
Completely disable DRM from kernel.

and/or attach the dmesg output
Comment 24 Alex Bogak 2005-09-13 05:08:03 UTC
I have no DRM compiled whether inside kernel or as module and 'dmesg' output can
be seen in comment #20
Comment 25 Luca Barbato gentoo-dev 2005-09-13 05:27:56 UTC
Sorry, I mean the full dmesg
Comment 26 Alex Bogak 2005-09-13 06:29:35 UTC
Created attachment 68357 [details]
full 'dmesg' output

Sure thing.
Comment 27 Luca Barbato gentoo-dev 2005-09-13 12:05:11 UTC
ok, now I need the kernel .config (sorry I know I'm asking lots of stuf..)
Comment 28 Alex Bogak 2005-09-13 22:25:16 UTC
Created attachment 68426 [details]
.config listing
Comment 29 Luca Barbato gentoo-dev 2005-09-13 23:03:09 UTC
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 
Comment 30 Alex Bogak 2005-09-14 00:45:32 UTC
What do you mean by GART?

and I did upgrade to 8.16.20, all effects are still happening.
Comment 31 Luca Barbato gentoo-dev 2005-09-15 04:28:40 UTC
AGP gart, w/out the module can't work (you need the igp one probably)
Comment 32 Alex Bogak 2005-09-15 11:06:12 UTC
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.
Comment 33 Luca Barbato gentoo-dev 2005-09-19 16:22:59 UTC
# CONFIG_AGP_ATI is not set

Should
Comment 34 Alex Bogak 2005-09-27 09:37:57 UTC
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' ??
Comment 35 Luca Barbato gentoo-dev 2005-09-27 09:47:56 UTC
I'd suggest you to use the kernel agp gart module and not rely on the internal one.
Comment 36 Jakub Moc (RETIRED) gentoo-dev 2007-04-01 21:58:37 UTC
Old; file a new bug if you have issues w/ current x11-drivers/ati-drivers and *supported* kernels.