On Sun, 21 Feb 2010, Juha Heinanen wrote:

> Cristian Ionescu-Idbohrn writes:
>
>   I also tried the uvesafb thing (with variations), found on the same page,
>   but no dice :(  Errors:
>
>   dmesg:[    0.000000] Kernel command line: 
> BOOT_IMAGE=/boot/vmlinuz-2.6.32-trunk-686 
> root=UUID=3a698373-fa59-4797-8f33-64bd23cdee17 ro video=uvesafb 
> acpi_osi=Linux nosplash
>   dmesg:[    1.416132] uvesafb: Intel Corporation, Intel(r)Poulsbo Graphics 
> Controller, Hardware Version 0.0, OEM: Intel(r)Poulsbo Graphics Chip 
> Accelerated VGA BIOS, VBE v3.0
>   dmesg:[    1.432749] uvesafb: VBIOS/hardware supports DDC2 transfers
>   dmesg:[    1.445338] uvesafb: monitor limits: vf = 60 Hz, hf = 47 kHz, clk 
> = 69 MHz
>   dmesg:[    1.445604] uvesafb: scrolling: redraw
>   dmesg:[    1.445682] uvesafb: cannot reserve video memory at 0x3f800000
>   dmesg:[    1.445779] uvesafb: probe of uvesafb.0 failed with error -5
>
>   dmesg.0:[   12.749141] uvesafb: Intel Corporation, Intel(r)Poulsbo Graphics 
> Controller, Hardware Version 0.0, OEM: Intel(r)Poulsbo Graphics Chip 
> Accelerated VGA BIOS, VBE v3.0
>   dmesg.0:[   12.765943] uvesafb: VBIOS/hardware supports DDC2 transfers
>   dmesg.0:[   12.778535] uvesafb: monitor limits: vf = 60 Hz, hf = 47 kHz, 
> clk = 69 MHz
>   dmesg.0:[   12.778800] uvesafb: scrolling: redraw
>   dmesg.0:[   12.778879] uvesafb: cannot reserve video memory at 0x3f800000
>   dmesg.0:[   12.778978] uvesafb: probe of uvesafb.0 failed with error -5
>
> perhaps the problems are due to your 2.6.32 kernel.  what is written on
> the page works on debian lenny with 2.6.30 kernel from backports.

You may be right.  Found some traces indicating that:

        http://bbs.archlinux.org/viewtopic.php?pid=678831#p678831

Looks like a kernel regression then.

On the other hand, it might just be me.  I may have missed something.
Come to think of it.  Do I need to tell the kernel on the cmdline to not
use all RAM (reserve some RAM for video)?

On the same thread (see above), I found some info about another (Intel
closed source, of course, what else could one expect?) driver, IEGD, for
which Intel doesn't advertize gma500 compatibility, but others do:

        
http://www.nanoant.com/linux/compiling-kernel-iegd-10x-module-for-any-linux-distribution


Cheers,

-- 
Cristian

_______________________________________________
Debian-eeepc-devel mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/debian-eeepc-devel

Reply via email to