Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
UVesaFB - The Successor to VesaFB-TNG (Bootsplash)
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3, 4, 5, 6, 7, 8, 9  Next  
Reply to topic    Gentoo Forums Forum Index Other Things Gentoo
View previous topic :: View next topic  
Author Message
JoKo
Tux's lil' helper
Tux's lil' helper


Joined: 16 May 2004
Posts: 141
Location: Xanthi, Greece

PostPosted: Mon Aug 20, 2007 10:20 pm    Post subject: Reply with quote

Hi,

I've just started using uvesafb in my AMD64 machine. So far it seems to start fine:
Code:
uvesafb: NVIDIA Corporation, G70 Board - p347h2  , Chip Rev   , OEM: NVIDIA, VBE v3.0
uvesafb: VBIOS/hardware doesn't support DDC transfers
uvesafb: no monitor limits have been set, default refresh rate will be used
uvesafb: scrolling: redraw
uvesafb: framebuffer at 0xd0000000, mapped to 0xffffc20010100000, using 10240k, total 262144k


However, I can't get the maximum resolution of my Apple 23" (1920x1200).

The output of
Code:
cat /sys/bus/platform/drivers/uvesafb/uvesafb.0/vbe_modes
is this:

Code:
640x400-8, 0x0100
640x480-8, 0x0101
800x600-8, 0x0103
1024x768-8, 0x0105
1280x1024-8, 0x0107
320x200-16, 0x010e
320x200-32, 0x010f
640x480-16, 0x0111
640x480-32, 0x0112
800x600-16, 0x0114
800x600-32, 0x0115
1024x768-16, 0x0117
1024x768-32, 0x0118
1280x1024-16, 0x011a
1280x1024-32, 0x011b
320x200-8, 0x0130
320x400-8, 0x0131
320x400-16, 0x0132
320x400-32, 0x0133
320x240-8, 0x0134
320x240-16, 0x0135
320x240-32, 0x0136
640x400-16, 0x013d
640x400-32, 0x013e
1600x1200-8, 0x0145
1600x1200-16, 0x0146
1400x1050-8, 0x0147
1400x1050-16, 0x0148


So, no widescreen resolutions?
Back to top
View user's profile Send private message
i92guboj
Moderator
Moderator


Joined: 30 Nov 2004
Posts: 10127
Location: Córdoba (Spain)

PostPosted: Mon Aug 20, 2007 10:34 pm    Post subject: Reply with quote

JoKo wrote:
Hi,

I've just started using uvesafb in my AMD64 machine. So far it seems to start fine:
Code:
uvesafb: NVIDIA Corporation, G70 Board - p347h2  , Chip Rev   , OEM: NVIDIA, VBE v3.0
uvesafb: VBIOS/hardware doesn't support DDC transfers
uvesafb: no monitor limits have been set, default refresh rate will be used
uvesafb: scrolling: redraw
uvesafb: framebuffer at 0xd0000000, mapped to 0xffffc20010100000, using 10240k, total 262144k


However, I can't get the maximum resolution of my Apple 23" (1920x1200).

The output of
Code:
cat /sys/bus/platform/drivers/uvesafb/uvesafb.0/vbe_modes
is this:

Code:
640x400-8, 0x0100
640x480-8, 0x0101
800x600-8, 0x0103
1024x768-8, 0x0105
1280x1024-8, 0x0107
320x200-16, 0x010e
320x200-32, 0x010f
640x480-16, 0x0111
640x480-32, 0x0112
800x600-16, 0x0114
800x600-32, 0x0115
1024x768-16, 0x0117
1024x768-32, 0x0118
1280x1024-16, 0x011a
1280x1024-32, 0x011b
320x200-8, 0x0130
320x400-8, 0x0131
320x400-16, 0x0132
320x400-32, 0x0133
320x240-8, 0x0134
320x240-16, 0x0135
320x240-32, 0x0136
640x400-16, 0x013d
640x400-32, 0x013e
1600x1200-8, 0x0145
1600x1200-16, 0x0146
1400x1050-8, 0x0147
1400x1050-16, 0x0148


So, no widescreen resolutions?


Read the previous page.

Gusar wrote:
manwe_ wrote:
Any ideas how to get non-vesa resolutions? Like 1280x800 and 1920x1200.
Why do you assume that a vesa driver can produce non-vesa resolutions?

The only possibility would be a hack that programs a new resolution into the vbios, like with intel, but no one has done that for nvidia (if it's even possible).


star.dancer wrote:
manwe_ wrote:
Any ideas how to get non-vesa resolutions? Like 1280x800 and 1920x1200.
...
Not assume, I was just hoping for. 1024x768 on 24" widescreen looks just a bit crappy :?

I know what you are saying, unfortunately this is not possible. I even reformatted my awesome Vampire them for 1280x800 before I realized it wouldn't work. I am sure someone (likely spock!) will come up with a clever solution one day... for example, doesn't Ubuntu's splashy work on widescreens?

In case you don't read through patches, here is the "Caveats and Limitations" section from spocks patch:
Code:
+2. Caveats and limitations
+--------------------------
+
+uvesafb is a _generic_ driver which supports a wide variety of video
+cards, but which is ultimately limited by the Video BIOS interface.
+The most important limitations are:
+
+- Lack of any type of acceleration.
+
+- A strict and limited set of supported video modes.  Often the native
+  or most optimal resolution/refresh rate for your setup will not work
+  with uvesafb, simply because the Video BIOS doesn't support the
+  video mode you want to use.  This can be especially painful with
+  widescreen panels, where native video modes don't have the 4:3 aspect
+  ratio, which is what most BIOS-es are limited to.
+
+- Adjusting the refresh rate is only possible with a VBE 3.0 compliant
+  Video BIOS.  Note that many nVidia Video BIOS-es claim to be VBE 3.0
+  compliant, while they simply ignore any refresh rate settings.

Oh, on a final note, check out the kamikaze sources in the custom-kernels overlay or in the forums, this includes the uvesafb patch, CFS, and Suspend2!

_________________
Gentoo Handbook | My website
Back to top
View user's profile Send private message
JoKo
Tux's lil' helper
Tux's lil' helper


Joined: 16 May 2004
Posts: 141
Location: Xanthi, Greece

PostPosted: Tue Aug 21, 2007 6:17 am    Post subject: Reply with quote

I see. I guess I'll have to use 1024x768 for now...
Back to top
View user's profile Send private message
96140
Retired Dev
Retired Dev


Joined: 23 Jan 2005
Posts: 1324

PostPosted: Tue Aug 21, 2007 7:24 am    Post subject: Reply with quote

--

Last edited by 96140 on Fri Sep 13, 2013 9:11 am; edited 1 time in total
Back to top
View user's profile Send private message
s4e8
Apprentice
Apprentice


Joined: 29 Jul 2006
Posts: 215

PostPosted: Fri Aug 24, 2007 2:50 am    Post subject: Reply with quote

Found a bug in v86d, report corrupt mode list if both mode list and name strings in video ROM.
Code:

--- /tmp/v86d-0.1/v86_common.c  2007-08-08 01:33:15.000000000 +0800
+++ v86d-0.1/v86_common.c       2007-08-23 10:52:39.000000000 +0800
@@ -52,6 +52,7 @@
                /* Mode list is in the buffer, we're good. */
                if (t < bufend) {
                        ib->mode_list_ptr = t - lbuf;
+                       buf += 512;

                /* Mode list is in the ROM. We copy as much of it as we can
                 * to the task buffer. */
@@ -70,14 +71,15 @@
                        ib->mode_list_ptr = 512;
                        *td = 0xffff;

+                       buf = (u8 *)td+2;
+                       fsize -= 2;
                /* Mode list is somewhere else. We're seriously screwed. */
                } else {
                        ulog("Can't retrieve mode list from %x\n", t);
                        ib->mode_list_ptr = 0;
+                       buf += 512;
                }

-               buf += 512;
-
                vbeib_get_string(oem_string_ptr);
                vbeib_get_string(oem_vendor_name_ptr);
                vbeib_get_string(oem_product_name_ptr);
Back to top
View user's profile Send private message
StifflerStealth
l33t
l33t


Joined: 03 Jul 2002
Posts: 960

PostPosted: Sat Aug 25, 2007 10:43 pm    Post subject: Reply with quote

Someone mentioned ubuntu splashy, but that is only a program like Gensplash. It displays pretty graphics, but not control the framebuffer resolution like vesafb/vesafb-tng/uvesafb do.

Cheers.
Back to top
View user's profile Send private message
zendal
n00b
n00b


Joined: 30 Nov 2002
Posts: 23
Location: Amberg, Germany

PostPosted: Wed Aug 29, 2007 2:50 pm    Post subject: Reply with quote

gentoo-sources-2.6.22-r5 is the latest stable version on AMD64 is there a new patch for it?
I tried it before with previous version and all I got was a black screen for 1280x1024.
Can someone give some more instructions for us make menuconfig users.
Back to top
View user's profile Send private message
ccgoo
n00b
n00b


Joined: 19 Jul 2007
Posts: 43

PostPosted: Wed Sep 05, 2007 3:45 am    Post subject: Reply with quote

I have a different problem from resolutions.

uvesafb works fine on my amd64 system. My command line is "video=uvesafb:1024...", uvesafb is built in kernel and I use CONFIG_INITRAMFS_SOURCE="/boot/initramfs" in my kernel config and no initrd parameter in command line.

But when I want to enter text mode without framebuffer. Occured the problem!
I remove "video=uvesafb:1024..." from my kernel boot command in order to enter text mode, as what I do with vesafb, but still I saw the penguin, and get the fb console. If I dmesg, I could see uvesafb get loaded.

Why, and how to enter text mode. Why removing "video=uvesafb:1024..." can work with vesafb, but not uvesafb.
And btw, I don't want add initrd parameter in my kernel command line.

Can anyone help me? 3x.
Back to top
View user's profile Send private message
ccgoo
n00b
n00b


Joined: 19 Jul 2007
Posts: 43

PostPosted: Wed Sep 05, 2007 6:30 pm    Post subject: Reply with quote

OK, I asked spock, and got the answer.
To disable uvesafb, you should use "video=uvesafb:off", but not remove the video mode from command line.
Back to top
View user's profile Send private message
kha0s
n00b
n00b


Joined: 11 Feb 2007
Posts: 21
Location: Lisbon, PT

PostPosted: Thu Sep 13, 2007 3:52 pm    Post subject: Reply with quote

What's up? I kinda off share zendal's question, i.e, will the gentoo-sources-2.6.22-r1 patch work against gentoo-sources-2.6.22-r5 (current stable release)?

Cheers
_________________
Who will guard the guards?
Back to top
View user's profile Send private message
swimmer
Veteran
Veteran


Joined: 15 Jul 2002
Posts: 1291
Location: Netherlands

PostPosted: Thu Sep 13, 2007 4:21 pm    Post subject: Reply with quote

Did you try it? It worked at least with 2.6.22-gentoo-r4 ...

Greetz
swimmer
Back to top
View user's profile Send private message
federico
Advocate
Advocate


Joined: 18 Feb 2003
Posts: 3270
Location: Italy, Milano

PostPosted: Thu Sep 13, 2007 11:13 pm    Post subject: Reply with quote

dR0PS wrote:
I get this message (GFX is an NVIDIA6600GT, a K8T800Pro Chip, CPU an winchester64bitAMD)
Code:
v86d[384]: segfault at 0000000000000000 rip 0000000000400ac2 rsp 00007fff03052640 error 6
uvesafb: Getting VBE info block failed (eax=0x4f00, err=-3)
uvesafb: vbe_init() failed with -22
uvesafb: probe of uvesafb.0 failed with error -22
maybe my gfx is not supported ?
dmesg, similar to

what I'm not quiet sure about of is if i have to completely remove vesafb?
or should it stay in there. The inkernel deps let me choose both!

some hints?

thx, dR0PS


I have the same error, any hint ?!?

Code:

uvesafb: Getting VBE info block failed (eax=0x4f00, err=0)
uvesafb: vbe_init() failed with -22
uvesafb: probe of uvesafb.0 failed with error -22


I have patched a grsec kernel with the instruction on spock's page

Federico
_________________
Sideralis www.sideralis.org
Pic http://blackman.amicofigo.com/gallery
Arduino http://www.arduino.cc
Chi aveva potuto aveva spaccato
2000 pezzi buttati là
Molti saluti,qualche domanda
Semplice come musica punk
Back to top
View user's profile Send private message
splat_ed
n00b
n00b


Joined: 27 Jul 2007
Posts: 3
Location: Somewhere where the flat caps and whippets roam

PostPosted: Sat Sep 15, 2007 12:34 pm    Post subject: Reply with quote

I'm getting a similar error in my dmesg:

Code:
 , , , OEM , VBE 3.0
Getting mode info block for mode 0x4956 failed (eax=0x14f, err=0)
vbe_init() failed with -22
proble of uvesafb.0 failed with error -22


Poking around reveals that I do not have a uvesafb.0 directory or file in /sys/bus/platform/drivers/uvesafb/
This could be the problem... any thoughts :?:

Hardware: Pico-ITX motherboard (PX10000) with VIA CX700M2 onboard graphics.
Procedure followed: Fresh install of Gentoo using minimum cd & gentoo-handbook.
After emerging gentoo-sources, I downloaded the vesa-tng patch and reversed it, then downloaded and patched the uvesafb patch. I then followed the instructions to the letter (set-up kernel, emerge klibc, emerge v86d, re-configure kernel, make) then carried on with the handbook, changing the grub line to
kernel /boot/kernel-2.6.22-gentoo-r5 root=/dev/hdc3 video=uvesafb:1024x768-32,mtrr:3,ywrap

(For some strange reason, my IDE HDD is detected on hdc while DVD drive is hdd... not a problem per se, just odd. There are no other drives)
_________________
Knowledge is power, Power corrupts;
Study hard... be evil
Back to top
View user's profile Send private message
s4e8
Apprentice
Apprentice


Joined: 29 Jul 2006
Posts: 215

PostPosted: Tue Sep 18, 2007 2:55 pm    Post subject: Reply with quote

check my previous post. your problem is the v86d buffer overwritten bug.
It doesn't fix in the newer rc release since my post.
Back to top
View user's profile Send private message
splat_ed
n00b
n00b


Joined: 27 Jul 2007
Posts: 3
Location: Somewhere where the flat caps and whippets roam

PostPosted: Tue Sep 18, 2007 11:02 pm    Post subject: Probably a silly question... Reply with quote

Okay I'm going to try with your edits again tomorrow night but I do have a question - how do I go about the install? I downloaded the .tar.bz2 from Spock's site, untarred and edited the file but what do I do next?

I have used linux a bit but this hacking about with files is a first for me... I assume I need to copy the source somewhere and run make & make install (I tried re-tarring the files, chucking 'em in the distfiles folder and running the ebuild... MD5 Checksum errors :D )
Is another option to make a patch file and get the ebuild to pull it in?

Time to learn programming me-thinks and more about how Linux/Gentoo actually works.

Thanks for any prompts, it all helps us learn

EDIT: I've been reading around and think I can do this... I'll try to make a patch and modify the ebuild tonight... procedure got from googling "create linux patch" and from Gentoo-Wiki
_________________
Knowledge is power, Power corrupts;
Study hard... be evil
Back to top
View user's profile Send private message
s4e8
Apprentice
Apprentice


Joined: 29 Jul 2006
Posts: 215

PostPosted: Wed Sep 19, 2007 1:13 pm    Post subject: Reply with quote

save my patch to /tmp/v86d.diff, any run follow commands:
Code:

cd /tmp
tar xvjf /usr/portage/distfiles/v86d-0.1.tar.bz2
patch -p0 -l < v86d.diff
cd v86d-0.1
./configure --default
make
make insall

You can verify this patch under VMWare Workstation 6.
VMWare VESA interface suffered this problem too.
Back to top
View user's profile Send private message
splat_ed
n00b
n00b


Joined: 27 Jul 2007
Posts: 3
Location: Somewhere where the flat caps and whippets roam

PostPosted: Wed Sep 19, 2007 7:43 pm    Post subject: Reply with quote

Okay, I've got it working (sort of) :?

s4e8: That worked a treat, thanks (I also tried the ebuild way - kept a copy of that saved as well)

Now my current problem is that the screen doesn't refresh. I have to swap terminals (Ctrl+Alt+F2 then back to F1) to get the screen to update when typing in commands. The machine hasn't frozen as I can type commands and they will still be run, just I can't see any output.

Here's my dmesg output:
Code:
uvesafb: ?, , , OEM: VIA CX700?, VBE v3.0
uvesafb: protected mode interface info at c000:aab4
uvesafb: pmi: set display start = c00cab02, set palette = c00cab73
uvesafb: VBIOS/hardware supports DDC2 transfers
uvesafb: monitor limits: vf = 75 Hz, hf = 80 kHz, clk = 140MHz
uvesafb: scrolling: ywrap using protected mode interface, yres_virtual=4050
uvesafb: mode switch failed (eax=0x14f, err=0). Trying again with default timings
uvesafb: framebuffer at 0xa0000000, mapped to 0xf8880000, using 16200k, total 131072k


The "mode switch failed line" appears 3 times before the "framebuffer at..." line and 4 times afterwards.

I'm using video=uvesafb:1024x768-32,mtrr:3,ywrap in grub

I've tried disabling uvesafb (video=uvesafb:off) and everything works fine. The screen freezing starts as Lo is started.
_________________
Knowledge is power, Power corrupts;
Study hard... be evil
Back to top
View user's profile Send private message
kha0s
n00b
n00b


Joined: 11 Feb 2007
Posts: 21
Location: Lisbon, PT

PostPosted: Wed Sep 19, 2007 9:27 pm    Post subject: Reply with quote

Just to say that yesterday I managed to successfully install uvesafb using gentoo-sources-2.6.22-r5 (the latest stable release). Because the links for the gentoo-sources patches didn't work for me, I had to go with the revert patching strategy you can read about here and here. I thought that, despite the very concise HOWTO you can find in the Official Site a step-by-step guide addressing the revert patching approach could proof useful. Here it goes then:

1 - Start by downloading vesafb-tng-1.0-rc2-2.6.20-rc2.patch into /usr/src/linux/.

2 - Now REVERSE that patch out of your kernel so that you can create a clean slate for uvesafb:
Code:
cd /usr/src/linux/
cat vesafb-tng-1.0-rc2-2.6.20-rc2.patch | patch -p1 -R

3 - Download uvesafb-0.1-rc3-2.6.23-rc3.patch and, just like before, place it in /usr/src/linux/.

4 - Apply the uvesafb patch:
Code:
cat uvesafb-0.1-rc3-2.6.23-rc3.patch | patch -p1

5 - Pop up menuconfig:
Code:
make menuconfig

6 - Set the following, brand new, uvesafb related options:
Code:
Location:
x     -> Device Drivers
x       -> Connector - unified userspace <-> kernelspace linker --->
            Prompt: Connector - unified userspace <-> kernelspace linker
               Action: ENABLE_builtIN <*>
               Module_Name:   cn (cn.ko)
               Search String:   "CONNECTOR"
                  SELECT: Report process events to userspace   "PROC_EVENTS"

Code:
Location:
x     -> Device Drivers
x       -> Graphics support
            Prompt: Userspace VESA VGA graphics support
               Action: ENABLE_builtIN <*>
               Module_Name:   N/A
               Search String:   "FB_UVESA"

7 - Exit menuconfig, selecting "Yes" when it politely asks if you want to save your new kernel configuration.
Compile your kernel:
Code:
make -j2

8 - It's now necessary to re-emerge "klibc".
Code:
emerge klibc
Spock explains why:
Quote:
This step is important even if you already have klibc installed. klibc has to be compiled against a patched kernel tree

9 - Emerge "v86d" (userspace helper that runs x86 code in an emulated environment). You may need to unmask it:
Code:
echo "sys-apps/v86d" >> /etc/portage/package.keywords
emerge v86d

10 - Pay yet another visit to menuconfig and set the following:
Code:
Location:
x     -> General setup
          Prompt: Initial RAM filesystem and RAM disk (initramfs/initrd) support
               Action: ENABLE_builtIN <*>
               Module_Name:   N/A
               Search String:   "BLK_DEV_INITRD"
               
            Prompt: Initramfs source file(s)
               Action: TYPEIN_"/usr/share/v86d/initramfs"
               Module_Name:   N/A
               Search String:   "INITRAMFS_SOURCE"

11 - At last compile the definite version of your kernel and install it:
Code:
make -j2
make modules_install
cp -pv arch/i386/boot/bzImage /boot/kernel-x86-2.6.22-gentoo-r5

12 - Make sure you properly setup /boot/grub/grub.conf. Here's mine as an example:
Code:
title=Gentoo Linux
kernel /kernel-x86-2.6.22-gentoo-r5 root=/dev/sda7 video=uvesafb:1024x768-32@60,mtrr:3,ywrap splash=silent,fadein,theme:livecd-2007.0, fbcon=scrollback:128K quiet CONSOLE=/dev/tty1
initrd /splash-livecd-2007.0-1024x768
In case you used "vesafb-tng" before, DON'T FORGET of changing video=vesafb to video=uvesafb in the kernel line!

13 - Now take a deep breath, cross your fingers until the knuckles go white, and reboot the system:
Code:
reboot


That's it!


In order to gauge the scrolling speed difference between "vesafb-tng" and "uvesafb", I created a little test that consisted in timing how long it took for completely displaying a 1MB word-list file. Here are my results:
Code:
time cat scroll_bench.txt

Code:
                     vesafb-tng        uvesafb
      1st cat      00:00:59.615   00:01:00.461
      2nd cat      00:00:59.499   00:01:00.384
      3rd cat      00:00:59.484   00:01:00.359


As you may see, "vesafb-tng" actually managed to be slightly faster than "uvesafb". Nevertheless I must point out that my ASUS W3J (Mobility Radeon X1600) had the fastest "vesafb-tng" scrolling speed I've ever seen! I've tried "vesafb-tng" before in two other machines, and the scrolling speeds were turtle-like. On those systems, I'm pretty sure "uvesafb" will make the difference!
If you want to gauge your "uvesafb" speed, feel free to download scroll_bench.zip. It would be nice if everyone posted their results here (don't forget to include the graphics card model).

I'm also doing a reprise of my favorite splash themes. I'll post them here when I finish the polishing up procedure!

Cheers
_________________
Who will guard the guards?
Back to top
View user's profile Send private message
xraver
Veteran
Veteran


Joined: 20 Aug 2003
Posts: 1083
Location: Halberstadt

PostPosted: Sat Oct 13, 2007 2:09 pm    Post subject: Reply with quote

uvesafb works for me, but only in 8Bit.
cat /sys/bus/platform/drivers/uvesafb/uvesafb.0/vbe_modes |grep 1440:

1440x900-8, 0x0164


How can ist work in 32Bit Mode?
I have add -32 oder -16 - but nothing work.

dmesg |grep uvesafb:

Command line: root=/dev/sda2 video=uvesafb:1440x900-16,mtrr:3,ywrap quiet CONSOLE=/dev/tty1 splash=verbose,theme:livecd-2007.0
Kernel command line: root=/dev/sda2 video=uvesafb:1440x900-16,mtrr:3,ywrap quiet CONSOLE=/dev/tty1 splash=verbose,theme:livecd-2007.0
uvesafb: NVIDIA Corporation, G80 Board - p356h01 , Chip Rev   , OEM: NVIDIA, VBE v3.0
uvesafb: VBIOS/hardware doesn't support DDC transfers
uvesafb: no monitor limits have been set, default refresh rate will be used
uvesafb: scrolling: redraw
uvesafb: framebuffer at 0xf9000000, mapped to 0xffffc20003500000, using 6144k, total 14336k
Back to top
View user's profile Send private message
96140
Retired Dev
Retired Dev


Joined: 23 Jan 2005
Posts: 1324

PostPosted: Sat Oct 13, 2007 3:27 pm    Post subject: Reply with quote

--

Last edited by 96140 on Fri Sep 13, 2013 9:01 am; edited 1 time in total
Back to top
View user's profile Send private message
n3Cre0
Tux's lil' helper
Tux's lil' helper


Joined: 16 Jan 2007
Posts: 129

PostPosted: Sun Oct 14, 2007 11:30 am    Post subject: Reply with quote

I got it to work using 2.6.23 gentoo sources (uvesafb patch included) but I get some errors I would like to know more about.

I compiled it into my kernel.
And start gentoo witht this line in grub
Quote:
kernel /boot/gentoo/vmlinuz root=/dev/hda4 real_root=/dev/hda4 video=uvesafb:1024x768-32,mtrr:3,ywrap CONSOLE=/dev/tty1 splash=verbose,theme:livecd-2007.0


Dmesg gives me this
Quote:
# grep -i uvesa /var/log/dmesg
uvesafb: (C) 1988-2005, ATI Technologies Inc. M26-C01.00, M26-C01.00, 01.00, OEM: ATI ATOMBIOS(C) 1988-2005, ATI Technologies Inc. M26-C01.00, VBE v3.0
uvesafb: protected mode interface info at c000:ae4a
uvesafb: pmi: set display start = c00caed8, set palette = c00caf18
uvesafb: VBIOS/hardware supports DDC2 transfers
uvesafb: monitor limits: vf = 60 Hz, hf = 49 kHz, clk = 68 MHz
uvesafb: scrolling: ywrap using protected mode interface, yres_virtual=4096
uvesafb: mode switch failed (eax=0x34f, err=0). Trying again with default timings.
uvesafb: mode switch failed (eax=0x34f, err=0). Trying again with default timings.
uvesafb: mode switch failed (eax=0x34f, err=0). Trying again with default timings.
uvesafb: framebuffer at 0xd0000000, mapped to 0xf8880000, using 16384k, total 16384k
uvesafb: mode switch failed (eax=0x34f, err=0). Trying again with default timings.


I got a widescreen with res 1280x800, reading this thread I can't get widescreen resolutions (at least, I don't have that vbe "option"), so I boot with 1024x768.

I just would like to know how I can get rid of
Quote:
uvesafb: mode switch failed (eax=0x34f, err=0). Trying again with default timings.


It works, I just don't want those 'semi-errors'
_________________
OS: Linux 2.6.26 i686 Gentoo v2.0.0 Sound: HDA Intel
CPU: Intel(R) Pentium(R) M processor 1.73GHz (GenuineIntel)
Disk: 95.23GB Video: ATI Radeon Mobility X700 XL with Catalyst 8.08 RAM: 1011MB
Back to top
View user's profile Send private message
swimmer
Veteran
Veteran


Joined: 15 Jul 2002
Posts: 1291
Location: Netherlands

PostPosted: Sun Oct 14, 2007 2:26 pm    Post subject: Reply with quote

n3Cre0 wrote:
[...]
I got a widescreen with res 1280x800, reading this thread I can't get widescreen resolutions (at least, I don't have that vbe "option"), so I boot with 1024x768.
[...]

You can in case you have Intel 855 / 865 / 915 chipsets ...
Then you can use sys-apps/915resolution to modify the vbe-modes first and afterwards load uvesafb as a module. You can achieve that even for 965 chipsets if you patch (easily done) 915resolution ...

The steps in detail:

1. Emerge sys-apps/915resolution and modify /etc/conf.d/915resolution to your needs
2. eselect rc add 915resolution boot
3. Configure uvesafb as a module and recompile/install kernel & modules
4. Create a file /etc/modules.d/uvesafb with a line similar like that: "options uvesafb mode=1280x800-32 mtrr=3 scroll=ywrap vbemode=348"
5. Load uvesafb via /etc/conf.d/local.start with "modprobe uvesafb"

HTH
swimmer
Back to top
View user's profile Send private message
n3Cre0
Tux's lil' helper
Tux's lil' helper


Joined: 16 Jan 2007
Posts: 129

PostPosted: Mon Oct 15, 2007 5:26 pm    Post subject: Reply with quote

n3Cre0 wrote:

Quote:
# grep -i uvesa /var/log/dmesg
uvesafb: (C) 1988-2005, ATI Technologies Inc. M26-C01.00, M26-C01.00, 01.00, OEM: ATI ATOMBIOS(C) 1988-2005, ATI Technologies Inc. M26-C01.00, VBE v3.0
uvesafb: protected mode interface info at c000:ae4a
uvesafb: pmi: set display start = c00caed8, set palette = c00caf18
uvesafb: VBIOS/hardware supports DDC2 transfers
uvesafb: monitor limits: vf = 60 Hz, hf = 49 kHz, clk = 68 MHz
uvesafb: scrolling: ywrap using protected mode interface, yres_virtual=4096
uvesafb: mode switch failed (eax=0x34f, err=0). Trying again with default timings.
uvesafb: mode switch failed (eax=0x34f, err=0). Trying again with default timings.
uvesafb: mode switch failed (eax=0x34f, err=0). Trying again with default timings.
uvesafb: framebuffer at 0xd0000000, mapped to 0xf8880000, using 16384k, total 16384k
uvesafb: mode switch failed (eax=0x34f, err=0). Trying again with default timings.


swimmer wrote:

You can in case you have Intel 855 / 865 / 915 chipsets ...


Anyways, noone having these kind of errors? :(
_________________
OS: Linux 2.6.26 i686 Gentoo v2.0.0 Sound: HDA Intel
CPU: Intel(R) Pentium(R) M processor 1.73GHz (GenuineIntel)
Disk: 95.23GB Video: ATI Radeon Mobility X700 XL with Catalyst 8.08 RAM: 1011MB
Back to top
View user's profile Send private message
swimmer
Veteran
Veteran


Joined: 15 Jul 2002
Posts: 1291
Location: Netherlands

PostPosted: Mon Oct 15, 2007 11:41 pm    Post subject: Reply with quote

Hmpf - I apologize for not reading carefully :-/

swimmer
Back to top
View user's profile Send private message
PsichoD
n00b
n00b


Joined: 09 Jul 2006
Posts: 12

PostPosted: Wed Oct 17, 2007 12:42 am    Post subject: Reply with quote

n3Cre0 wrote:
n3Cre0 wrote:

Quote:
# grep -i uvesa /var/log/dmesg
uvesafb: (C) 1988-2005, ATI Technologies Inc. M26-C01.00, M26-C01.00, 01.00, OEM: ATI ATOMBIOS(C) 1988-2005, ATI Technologies Inc. M26-C01.00, VBE v3.0
uvesafb: protected mode interface info at c000:ae4a
uvesafb: pmi: set display start = c00caed8, set palette = c00caf18
uvesafb: VBIOS/hardware supports DDC2 transfers
uvesafb: monitor limits: vf = 60 Hz, hf = 49 kHz, clk = 68 MHz
uvesafb: scrolling: ywrap using protected mode interface, yres_virtual=4096
uvesafb: mode switch failed (eax=0x34f, err=0). Trying again with default timings.
uvesafb: mode switch failed (eax=0x34f, err=0). Trying again with default timings.
uvesafb: mode switch failed (eax=0x34f, err=0). Trying again with default timings.
uvesafb: framebuffer at 0xd0000000, mapped to 0xf8880000, using 16384k, total 16384k
uvesafb: mode switch failed (eax=0x34f, err=0). Trying again with default timings.


swimmer wrote:

You can in case you have Intel 855 / 865 / 915 chipsets ...


Anyways, noone having these kind of errors? :(


Same thing here with ATI Mobile x1400. It works fine on my other, NVIDIA based, laptop.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Other Things Gentoo All times are GMT
Goto page Previous  1, 2, 3, 4, 5, 6, 7, 8, 9  Next
Page 3 of 9

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum