1 |
Mick schrieb: |
2 |
> # dmesg | grep uvesafb |
3 |
> Kernel command line: root=/dev/sda3 video=uvesafb:1024x768-32@64,ywrap,mtrr:4 |
4 |
> splash=silent,fadein,theme:emergence quiet CONSOLE=/dev/tty1 |
5 |
> uvesafb: ATI Technologies Inc., V380, 01.00, OEM: ATI RV380, VBE v2.0 |
6 |
> uvesafb: protected mode interface info at c000:5884 |
7 |
> uvesafb: pmi: set display start = c00c5918, set palette = c00c5964 |
8 |
> uvesafb: pmi: ports = b010 b016 b054 b038 b03c b05c b000 b004 b0b0 b0b2 b0b4 |
9 |
> uvesafb: no monitor limits have been set, default refresh rate will be used |
10 |
> uvesafb: VBE state buffer size cannot be determined (eax=0x0, err=0) |
11 |
> uvesafb: scrolling: ywrap using protected mode interface, yres_virtual=1536 |
12 |
> uvesafb: framebuffer at 0xd0000000, mapped to 0xf8880000, using 6144k, total |
13 |
> 16384k |
14 |
|
15 |
Looks okay, but i don't know much about ATI cards! |
16 |
|
17 |
> fbset gives me bash: command not found. Should have I emerged something here? |
18 |
> Can't remember seeing this in the wiki article, as in it wasn't a must for fb |
19 |
> splash to work (I think). |
20 |
|
21 |
It just gives some info about the framebuffer, i think it is not |
22 |
necessary. If you want it just do an "emerge fbset". It is a small utility. |
23 |
|
24 |
I am not an expert here, but what are the other strange errors the new |
25 |
kernel is giving you, which you have mentioned before. |
26 |
|
27 |
Can you post the output of |
28 |
"cat /sys/devices/platform/uvesafb.0/vbe_modes" |
29 |
|
30 |
> although the quality of the image is poor (it looks sort of pixelated) |
31 |
|
32 |
What do you mean by this? I will attach a grab of a 1024x768 framebuffer |
33 |
image with the livecd-2007.0 theme, which looks okay here! |
34 |
|
35 |
What about trying a higher frequency, i have 75Hz here! Or is your |
36 |
monitor not capable of this frequency? |
37 |
|
38 |
Regards, |
39 |
|
40 |
Daniel |