1 |
Mick schrieb: |
2 |
> On Sunday 30 March 2008, Daniel Pielmeier wrote: |
3 |
>> Mick schrieb: |
4 |
>>> Hi All, |
5 |
>>> |
6 |
>>> I've just compiled kernel-2.6.24-gentoo-r3 which comes with uvesa and |
7 |
>>> thought of using it on a box of mine. However, amidst other weird and |
8 |
>>> wonderful errors that the new kernel gives me on this box, I have |
9 |
>>> completely failed to get uvesafb to work. |
10 |
>>> |
11 |
>>> When it boots up it comes up with these errors: |
12 |
>>> ===================================================== |
13 |
>>> * Setting framebuffer console images |
14 |
>>> Can't open cfg file //etc/splash/emergence/640x480.cfg |
15 |
>>> No 8bpp silent picture specified in the theme |
16 |
>>> No 8bpp verbose picture specified in the theme |
17 |
>>> * Failed to set background image on tty1 |
18 |
>>> ===================================================== |
19 |
>>> |
20 |
>>> Meanwhile the penguins and fonts on the boot console are shown in some |
21 |
>>> impossibly large size. My kernel line is: |
22 |
>>> |
23 |
>>> kernel /kernel-2.6.24-gentoo-r3 root=/dev/sda3 \ |
24 |
>>> video=uvesafb:1280x1024-32@60,ywrap,mtrr:4, \ |
25 |
>>> splash=silent,fadein,theme:emergence quiet CONSOLE=/dev/tty1 |
26 |
>>> initrd /boot/fbsplash-emergence-1280x1024 |
27 |
>>> |
28 |
>>> Any ideas? |
29 |
>> Just a shot in the dark are you using any kind of tv-out? |
30 |
>> |
31 |
>> I had this problem with tv-out. I specified a resolution of 1280x1024. |
32 |
>> When I connect my tv to my box the maximal resolution possible is |
33 |
>> 1024x768 because the tv-encoder does not offer higher resolutions. So |
34 |
>> instead of switching to the next greatest resolution of 1024x768 the |
35 |
>> uvesafb driver switches to smallest resolution of 640x480. This |
36 |
>> resolution is not available in the emergence theme thus the splash fails! |
37 |
>> |
38 |
>> If you have a problem like this there are existing patches whto the |
39 |
>> kernel which are fixing this issue! |
40 |
>> |
41 |
>> What does "cat /sys/devices/platform/uvesafb.0/vbe_modes" say? |
42 |
> |
43 |
> Thanks Daniel, I am not using tvout, just a LCD monitor. You're right, |
44 |
> there's no 1280x1024 in the above file! Changed it to 1024x768 and it works, |
45 |
> although the quality of the image is poor (it looks sort of pixelated). |
46 |
> |
47 |
> What controls what resolutions exist in that file? |
48 |
|
49 |
Output of /usr/src/linux/Documentation/fb/uvesafb.txt |
50 |
|
51 |
... snip .... |
52 |
|
53 |
2. Caveats and limitations |
54 |
-------------------------- |
55 |
|
56 |
uvesafb is a _generic_ driver which supports a wide variety of video |
57 |
cards, but which is ultimately limited by the Video BIOS interface. |
58 |
The most important limitations are: |
59 |
|
60 |
- Lack of any type of acceleration. |
61 |
- A strict and limited set of supported video modes. Often the native |
62 |
or most optimal resolution/refresh rate for your setup will not work |
63 |
with uvesafb, simply because the Video BIOS doesn't support the |
64 |
video mode you want to use. This can be especially painful with |
65 |
widescreen panels, where native video modes don't have the 4:3 aspect |
66 |
ratio, which is what most BIOS-es are limited to. |
67 |
- Adjusting the refresh rate is only possible with a VBE 3.0 compliant |
68 |
Video BIOS. Note that many nVidia Video BIOS-es claim to be VBE 3.0 |
69 |
compliant, while they simply ignore any refresh rate settings. |
70 |
|
71 |
..... snip ..... |
72 |
|
73 |
4. The sysfs interface |
74 |
---------------------- |
75 |
|
76 |
uvesafb provides several sysfs nodes for configurable parameters and |
77 |
additional information. |
78 |
|
79 |
Driver attributes: |
80 |
|
81 |
/sys/bus/platform/drivers/uvesafb |
82 |
- v86d (default: /sbin/v86d) |
83 |
Path to the v86d executable. v86d is started by uvesafb |
84 |
if an instance of the daemon isn't already running. |
85 |
|
86 |
Device attributes: |
87 |
|
88 |
/sys/bus/platform/drivers/uvesafb/uvesafb.0 |
89 |
- nocrtc |
90 |
Use the default refresh rate (60 Hz) if set to 1. |
91 |
|
92 |
- oem_product_name |
93 |
- oem_product_rev |
94 |
- oem_string |
95 |
- oem_vendor |
96 |
Information about the card and its maker. |
97 |
|
98 |
- vbe_modes |
99 |
A list of video modes supported by the Video BIOS along with their |
100 |
VBE mode numbers in hex. |
101 |
|
102 |
- vbe_version |
103 |
A BCD value indicating the implemented VBE standard. |
104 |
|
105 |
..... snip ..... |
106 |
|
107 |
|
108 |
So this depend on the Video Bios of your card and you maybe can't do |
109 |
anything about it! |
110 |
|
111 |
Although 1280x1024 should normally work and i guess you use this |
112 |
resolution for your Desktop. How do you generate your initrd? Which card |
113 |
do you have? |
114 |
|
115 |
"dmesg | grep uvesafb" and "fbset --info -v"? |
116 |
|
117 |
Regards, |
118 |
|
119 |
Daniel |
120 |
|
121 |
-- |
122 |
gentoo-user@l.g.o mailing list |