[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Link /lib/modules/2.6.12-1-686-smp/build does not exist (or is not a link)
- From: "Matthew Tippett" <mtippett at ati dot com>
- Date: Sat, 24 Sep 2005 17:43:55 -0400
Regarding modelines, a safe default that most people do not consider is to remove all sync ranges and modelines and let the detection magic happen - it should work without issues most of the time.
Regards... Matthew
--
Blackberry-Sent
Matthew Tippett
Engineering Manager, Linux Software Engineering
ATI Technologies Inc.
Ph: +1 905 882 2600 x8014 Cell: +1 416 671 0673
-----Original Message-----
From: Mathieu Malaterre <mmalater at nycap dot rr dot com>
To: Manuel Bilderbeek <manuel at msxnet dot org>
CC: flavio-fglrx at stanchina dot net <flavio-fglrx at stanchina dot net>
Sent: Sat Sep 24 16:58:13 2005
Subject: Re: [fglrx] Link /lib/modules/2.6.12-1-686-smp/build does not exist (or is not a link)
Manuel Bilderbeek wrote:
Mathieu Malaterre wrote:
Hello there,
I have just updated my debian system today, and it made the switch to
xorg. Unfortunately I am not able to compile fglrx anymore due to
missing kernel-headers for 2.6.12. I am doing:
They're not missing:
linux-headers-2.6.12-1 - Common architecture-specific header files for
Linux kernel 2.6.12
But I used the kernel sources (linux-source) and got the kernel module
working perfectly with the Debian stock 2.6.12 kernel and the
instructions on Flavio's site. :)
So, the packages with kernel headers and sources got renamed.
Might be nice to add that to Flavio's site also.
Manuel, thanks a bunch ! You saved me a lot of time.
So yes indeed the name changed (I still don't know how you figured out
that).
Anyway after compilation the screen was still black with the message:
"Cannot Display This Video Mode". This has nothing to do with fglrx, but
since I found the solution I thought it might help others:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=319944;msg=10
Indeed I had wrong freqencies, copying the one from /var/log/Xorg.0.log
into xorg.conf did the trick.
Mathieu