Bug#467070: More info
>Chris Carr wrote:
>> Package: xserver-xorg-video-intel
>> Version: 2.1.0-2
>> Severity: important
>>
>> Apologies if this bug is filed against the wrong package. I've
>> installed KDE on an HP530 laptop, and dpkg-reconfigure xserver-xorg
>> says it does not recognise the video hardware (Intel 945GME Express
>> chipset). When chosen manually the reconfiguration completes, but x
>> does not start because /dev/agpgart does not exist.
>
>Looks like the AGP modules were not loaded or do not support your
>hardware yet. You might want to try a more recent kernel and make sure
>agpgart and intel_agp appear in lsmod (and check dmesg). If not, load
>them with modprobe.
I did modprobe them and they both loaded successfully. X still did not
start after they were loaded.
>> I added both to /etc/modules and added alias char-major-10-175
>> intel-agp to /etc/modprobe.d/aliases
>
>No need to do that. udev (or discover or whatever hardware detection
>soft) should load the AGP modules by default.
I only did this because they did not load automatically. After I did it
they did load automatically, with no errors, and X still did not start.
>> booting, but /dev/agpgart still does not exist so X still does not
start.
>
>Probably because recent intel drivers need agpgart to work. See above.
agpgart is present and successfully loaded (as is intel-agp), but X
still does not start. See above.
>Note that reportbug would have automatically attached a lot of
>information that we need to diagnose your problem... But it's pretty
>clear that the problem is that your AGP modules are not loaded or your
>kernel does not support your chipset yet. So I am just closing this
bug.
That may be premature. The kernel is 2.6.22-3, the latest in Lenny. The
chipset is several months older than this kernel, so the modules should
support it.
Is there a way to tell which kernel(s) support which chipset(s)? It
would be good if we could look up when support for this chipset was
added - if it was before 2.6.22 then this problem may be a bug, if not
then you could well be right that a newer kernel is all that is needed.
But, I will compile a totally up-to-the-minute kernel and let you know
if that solves the problem. If it does not I will reopen the bug.
>> P.S. This email address is protected by a whitelist. Emails from
>> debian.org addresses will get through, others won't. Please don't be
>> offended - I will check this thread for replies.
>
>Please don't do that. Many people take care of the Debian bugs with a
>non-debian.org address. Not being able to reach you directly is a pain.
>Even if you say you will check the thread, you probably won't actually
>do it regularly for a long time.
>And, some people may want to contact you privately in some cases too.
That's fair enough - I do submit most of my bug reports from work, and
the only reason I didn't for this one was because I was on leave and not
returning to work for several days, by which time I would have forgotten
the details. Does the BTS respect the Reply-To header? If it does I can
submit bugs from home and put my work address in there.
Regards,
CC
Reply to: