Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've been trying to install and run the ATI proprietary drivers and I've been having significant headaches. Any assistance would be greatly appreciated.
Running Fedora Core 10 on a Sony Vaio VGN-AX580G laptop with the Radeon x700 video card. The current kernel is 2.6.27.19-170.2.35.fc10.i386 package. I've read that you cannot have the radeon module loaded at the same time as the fglrx module but I have not yet discovered the secret to preventing the radeon module from loading. I've even gone so far as adding it to my modprobe blacklist, but it still loads. I am fairly certain this is the root of my issue. Any and all help would be greatly appreciated.
fglrxinfo output:
Code:
X Error of failed request: BadRequest (invalid request code or no such operation)
Major opcode of failed request: 143 (GLX)
Minor opcode of failed request: 19 (X_GLXQueryServerString)
Serial number of failed request: 15
Current serial number in output stream: 15
modprobe -v fglrx output:
Code:
insmod /lib/modules/2.6.27.19-170.2.35.fc10.i686/kernel/drivers/char/drm/fglrx.ko
FATAL: Error inserting fglrx (/lib/modules/2.6.27.19-170.2.35.fc10.i686/kernel/drivers/char/drm/fglrx.ko): Operation not permitted
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(II) Loading extension MIT-SCREEN-SAVER
(EE) fglrx(0): Failed to initialize ASIC in kernel.
(EE) fglrx(0): [FB] Can not get FB MC address range.
(EE) fglrx(0): Unknown EDID version 0
(EE) fglrx(0): Failed to enable interrupts.
(EE) fglrx(0): DRIScreenInit failed!
(EE) fglrx(0): XMM failed to open CMMQS connection.
(EE) Microsoft Microsoft Wireless Optical Mouse? 1.00: Read error: No such device
(WW) AllowEmptyInput is on, devices using drivers 'kbd' or 'mouse' will be disabled.
(WW) Disabling Mouse0
(WW) Disabling Keyboard0
(WW) Falling back to old probe method for fglrx
(WW) This ATI Proprietary Linux Driver does not guarantee support of video driver ABI higher than 2.0
(WW) Video driver ABI version of the X server is 4.1
(WW) fglrx(0): Failed to get kernel info
(WW) fglrx(0): board is an unknown third party board, chipset is supported
(WW) fglrx(0): Only one display is connnected,so single mode is enabled
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed! *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *
(WW) fglrx(0): ********************************************* *
(WW) fglrx(0): Option "AccelMethod" is not used
(WW) fglrx(0): Option "VendorName" is not used
(WW) fglrx(0): Option "ModelName" is not used
Last edited by vendetta007; 03-17-2009 at 08:26 AM.
Reason: typo correction
have you rebooted the computer after fglrx installation (complete reboot, not only x restart) ? If not, please try that. If this has no impact, can you post the comlete Xorg.0.log on pastebin.com.
Yes, I've tried rebooting several times and even going to runlevel 3 to try and remove the radeon driver and insert the fglrx driver. no luck in those attempts. Somehow the radeon module is required by the i2c_algo_bit module and the i2c_algo_bit module is required by the radeon module. its a weird catch 22 mess that has me confused. anyway, here is the full xorg.0.log output.
Vendetta, I have a similar problem as yours. Maybe we can help each other. I am running debian Lenny. This is the output of
Code:
$ less /var/log/Xorg.0.log |grep WW
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) The directory "/usr/X11R6/lib/X11/fonts/misc" does not exist.
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
(WW) The directory "/usr/X11R6/lib/X11/fonts/cyrillic" does not exist.
(WW) The directory "/usr/X11R6/lib/X11/fonts/100dpi/" does not exist.
(WW) The directory "/usr/X11R6/lib/X11/fonts/75dpi/" does not exist.
(WW) The directory "/usr/X11R6/lib/X11/fonts/Type1" does not exist.
(WW) The directory "/usr/X11R6/lib/X11/fonts/100dpi" does not exist.
(WW) The directory "/usr/X11R6/lib/X11/fonts/75dpi" does not exist.
(WW) fglrx(0): Failed to open DRM connection
(WW) fglrx(0): board is an unknown third party board, chipset is supported
(WW) fglrx(0): Only one display is connnected,so single mode is enabled
(WW) fglrx(0): No DRM connection for driver fglrx.
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed! *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *
(WW) fglrx(0): ********************************************* *
(WW) fglrx(0): Textured Video not supported without DRI enabled.
I have two kernels: the old 2.6.18 from the previous debian version (etch), where fglrx driver works without error (2D support but no 3D because is an older driver).
So the warnings above is from the new kernel 2.6.26-amd64 that was installed recently.
Maybe our common problem (DRI initialization failed) is because the fglrx driver is not compatible for the current kernel?
What I did is to upgrade debian etch to lenny (instead of deleting old stuff and installing everything). That is why I have the old and new kernels to boot from. Did you do something similar?
I dont want to delete the fglrx driver because of the risk of loosing functional old kernel. By the way, the new kernel is not using fglrx (the older kernel does for sure) and is a pain to scroll using firefox (slow and wavy) :-(
Running Fedora on my box and unfortunately I don't know anything about Debian. It was a fresh install but I've been keeping it updated through Yum. The kernel I'm running is 2.6.27.19. Sorry, I guess I'm not much help to you. This is my first real attempt to run a GUI on Linux. Most of the time I run my Linux CLI only.
Running Fedora on my box and unfortunately I don't know anything about Debian. It was a fresh install but I've been keeping it updated through Yum. The kernel I'm running is 2.6.27.19. Sorry, I guess I'm not much help to you. This is my first real attempt to run a GUI on Linux. Most of the time I run my Linux CLI only.
Have you managed to solve your problem? In my case I have one freaky doubt: It may be possible for me to install the fglrx-driver (I can see this package in synaptic as not yet installed) but I am freaking that if installing it along with the fglrx-kernel-src package, it will screw out the older kernel.
I Need to find this information: Does anyone know if installing the fglrx-driver package for the newest kernel, it will also overwrite the settings (deleting the older fglrx) in the older kernel? This is the question is keeping me from acting. Thanks if someone can inform me.
I installed fglrx with ati-installer from ATI webpage on debian squeeze; this way everything went fine.
I had to dist-upgrade in order to have my ath9k wireless card working, but then X badly freezes system on boot (no ctrl+alt+supr or SysReq+(R·E·I·S·U·B)); nothing is shown in any log at /var (or i couldn't see it) but this:
Code:
(EE) fglrx(0): [FB] Can not get FB MC address range.
Which is always the las logged event in kdm.0.log, I think this is related with yours.
I've found this, which seems be my problem's solution: I'm currently at job, hope this help you (and me...)
Ok, well apparently the original kernel I was running was forcing the radeon module to load at boot which is why I couldn't get around it. So, by following the instructions in this post:
I was able to get my fglrx module to load and there was much rejoicing!
the only quirk to the instructions listed in the link above is that I had to manually download the rpmfusion non-free rpm file and manually install it as well. For some reason it wouldn't automatically download and install it for me. Beyond that the instructions were perfect for me and I'm now a lot happier camper!
I hope this helps someone else down the road.
and in case the other post gets eaten at some point in time, here is a direct quote for the Fedora Core 10 section.
Code:
Howto for F10
Click this link to make sure your card is supported by this driver ( ATI cards 9250 and below are unsupported )
1. Update kernel
Code:
Code:
su
yum update kernel
reboot to the new kernel
2. Install driver ( if you previously downgraded libdrm you will need to upgrade to the F10 version first see end of post ~1 for instructions )
install the F10 rpmfusion driver
Code:
su
mv /boot/initrd-`uname -r`.img /boot/initrd-`uname -r`.img.backup
Remake initrd for the kernel (So the radeon module is not force loaded)
Code:
Code:
su -
mkinitrd -v /boot/initrd-`uname -r`.img `uname -r`
4. Edit grub.conf
Code:
Code:
su
gedit /boot/grub/grub.conf
and add this "nopat" to the kernel arguments.
Optional (in case libdrm change breaks things due to relationship with KMS):
add "nomodeset" to end of kernel arguments
5. Reboot
due to the akmod, it is *absolutely necessary* to reboot after the install, otherwise the kernel module won't be compiled.
6. Optional install compiz-fusion.
http://forums.fedoraforum.org/showpo...05&postcount=1
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.