i810fb on FC2 help
Michael
stuff at dustsmoke.com
Wed Jul 14 21:22:13 UTC 2004
Can somebody explain how to use this i810fb driver? I can't for the life
of me get it to work. I don't have any problems using vesafb on other
systems but the i810 E graphics controller doesn't seem to be supported on
this Dell GX110.
If I do something like this,
kernel /vmlinuz-2.6.6-1.435.2.3 ro root=LABEL=/ rhgb quiet
video=i810fb:vram:4,xres:1024,yres:768,bpp:16,hsync1:30,hsync2:70,vsync1:50,vsync2:160,accel,mtrr
It kind of just ignores it the same way it does with everything else (of
course since it does not seem to load the module, what am I doing wrong
there)
-------------------------------------------------
binfmt_misc 7176 1
ipv6 184672 12
parport_pc 19392 1
lp 8236 0
parport 29640 2 parport_pc,lp
autofs4 12932 0
sunrpc 109924 1
3c59x 30504 0
floppy 47440 0
sg 27680 0
scsi_mod 91984 1 sg
microcode 4768 0
dm_mod 32800 0
uhci_hcd 24472 0
button 4632 0
battery 6924 0
asus_acpi 8984 0
ac 3340 0
ext3 103656 2
jbd 40728 1 ext3
---------------------------------------------------
So if I manually modprobe it
modprobe i810fb vram=4 xres=1024 yres=768 bpp=16 hsync1=30 hsync2=70
vsync1=50 vsync2=160 accel=1 mtrr=1
it comes back with;
---------------------------------------------------
I810FB: fb0 : Intel(R) 810E Framebuffer Device v0.9.0
I810FB: Video RAM : 4096K
I810FB: Monitor : H: 30-70 KHz V: 50-160 Hz
I810FB: Mode : 1024x768-16bpp at 86Hz
----------------------------------------------------
which is great and all.... but that is all it seems to do, nor do I want
to do that every time I boot the computer. If I do something like fbset -a
1024x768-75 or anything I pick..... Screen goes blank and comes back with
the exact same thing I already have.. (nothing)
So for the most part I think I don't understand this, and my monitor seems
pretty crazy but those are the values I got from xorg.conf when I select
this Dell monitor model (which is fine under X) So what would I do here,
can somebody explain how I 'should' be able to get this working the same
way I do with vesa compatabale chipsets where all I really have to do is
add vga=0x371 and everything is fine and dandy. (I don't grasp their
documentation either, it doesn't seem to work when I follow exactly what
they say to do)
Thanks
-Mike
More information about the fedora-list
mailing list