1 |
Mick schrieb: |
2 |
> On Wednesday 02 April 2008, Daniel Pielmeier wrote: |
3 |
>> Mick schrieb: |
4 |
>>> # dmesg | grep uvesafb |
5 |
>>> Kernel command line: root=/dev/sda3 |
6 |
>>> video=uvesafb:1024x768-32@64,ywrap,mtrr:4 |
7 |
>>> splash=silent,fadein,theme:emergence quiet CONSOLE=/dev/tty1 |
8 |
>>> uvesafb: ATI Technologies Inc., V380, 01.00, OEM: ATI RV380, VBE v2.0 |
9 |
>>> uvesafb: protected mode interface info at c000:5884 |
10 |
>>> uvesafb: pmi: set display start = c00c5918, set palette = c00c5964 |
11 |
>>> uvesafb: pmi: ports = b010 b016 b054 b038 b03c b05c b000 b004 b0b0 b0b2 |
12 |
>>> b0b4 uvesafb: no monitor limits have been set, default refresh rate will |
13 |
>>> be used uvesafb: VBE state buffer size cannot be determined (eax=0x0, |
14 |
>>> err=0) uvesafb: scrolling: ywrap using protected mode interface, |
15 |
>>> yres_virtual=1536 uvesafb: framebuffer at 0xd0000000, mapped to |
16 |
>>> 0xf8880000, using 6144k, total 16384k |
17 |
>> Looks okay, but i don't know much about ATI cards! |
18 |
> |
19 |
>> Can you post the output of |
20 |
>> "cat /sys/devices/platform/uvesafb.0/vbe_modes" |
21 |
> |
22 |
> This is what I get, there's no 1280x1024 available: |
23 |
> ========================================== |
24 |
> 320x200-8, 0x0182 |
25 |
> 320x200-15, 0x010d |
26 |
> 320x200-16, 0x010e |
27 |
> 320x200-24, 0x010f |
28 |
> 320x200-32, 0x0120 |
29 |
> 320x240-8, 0x0192 |
30 |
> 320x240-15, 0x0193 |
31 |
> 320x240-16, 0x0194 |
32 |
> 320x240-24, 0x0195 |
33 |
> 320x240-32, 0x0196 |
34 |
> 400x300-8, 0x01a2 |
35 |
> 400x300-15, 0x01a3 |
36 |
> 400x300-16, 0x01a4 |
37 |
> 400x300-24, 0x01a5 |
38 |
> 400x300-32, 0x01a6 |
39 |
> 512x384-8, 0x01b2 |
40 |
> 512x384-15, 0x01b3 |
41 |
> 512x384-16, 0x01b4 |
42 |
> 512x384-24, 0x01b5 |
43 |
> 512x384-32, 0x01b6 |
44 |
> 640x350-8, 0x01c2 |
45 |
> 640x350-15, 0x01c3 |
46 |
> 640x350-16, 0x01c4 |
47 |
> 640x350-24, 0x01c5 |
48 |
> 640x350-32, 0x01c6 |
49 |
> 640x400-8, 0x0100 |
50 |
> 640x400-15, 0x0183 |
51 |
> 640x400-16, 0x0184 |
52 |
> 640x400-24, 0x0185 |
53 |
> 640x400-32, 0x0186 |
54 |
> 640x480-8, 0x0101 |
55 |
> 640x480-15, 0x0110 |
56 |
> 640x480-16, 0x0111 |
57 |
> 640x480-24, 0x0112 |
58 |
> 640x480-32, 0x0121 |
59 |
> 800x600-8, 0x0103 |
60 |
> 800x600-15, 0x0113 |
61 |
> 800x600-16, 0x0114 |
62 |
> 800x600-24, 0x0115 |
63 |
> 800x600-32, 0x0122 |
64 |
> 1024x768-8, 0x0105 |
65 |
> 1024x768-15, 0x0116 |
66 |
> 1024x768-16, 0x0117 |
67 |
> 1024x768-24, 0x0118 |
68 |
> 1024x768-32, 0x0123 |
69 |
> ========================================== |
70 |
> |
71 |
>>> although the quality of the image is poor (it looks sort of pixelated) |
72 |
>> What do you mean by this? I will attach a grab of a 1024x768 framebuffer |
73 |
>> image with the livecd-2007.0 theme, which looks okay here! |
74 |
>> |
75 |
>> What about trying a higher frequency, i have 75Hz here! Or is your |
76 |
>> monitor not capable of this frequency? |
77 |
> |
78 |
> What I mean is that when if fades in it creates artifacts on the screen (is |
79 |
> this a matter of uvesafb not having acceleration?). Also the background |
80 |
> image when I press F2 is not clear. It looks as if it is a smaller |
81 |
> resolution stretched over a larger screen. |
82 |
|
83 |
What about the silent screen does it also look unclear or just the |
84 |
verbose screen. |
85 |
|
86 |
I don't have any artifacts here and the picture is clear, even with the |
87 |
connected TV where i only get 1024x768. |
88 |
|
89 |
I think I can't help you any further here. Maybe you could contact the |
90 |
maintainer of uvesafb, splashutils (spock@g.o). Probably he could |
91 |
help you, although he seems busy with other things at the moment. |
92 |
|
93 |
Regards, |
94 |
|
95 |
Daniel |
96 |
-- |
97 |
gentoo-user@l.g.o mailing list |