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
Genone
Retired Dev
Retired Dev


Joined: 14 Mar 2003
Posts: 9013
Location: beyond the rim

PostPosted: Thu Jul 12, 2007 11:24 pm    Post subject: Reply with quote

star.dancer wrote:
Genone wrote:
Crap, first this thread gets me all excited about hgher resolutions on my box, and then I have to read that it requires a initrd, which is a no go for me :(


Why can't you use an initrd? Just wondering.

It's not that I can't, I just don't want that additional level of complexity in the boot process. And I don't care about all the fancy splash stuff anyway, I'd just be interested in the higher resolutions.
Back to top
View user's profile Send private message
ToeiRei
Veteran
Veteran


Joined: 03 Jan 2005
Posts: 1156
Location: Austria

PostPosted: Fri Jul 13, 2007 7:10 am    Post subject: Reply with quote

Hello star.dancer,

I have followed your howto here, but the kernel refuses to compile. Here's the error message:

Quote:
pavilion linux # genkernel --menuconfig --gensplash=livecd-2007.0 kernel
* Gentoo Linux Genkernel; Version 3.4.8
* Running with options: --menuconfig --gensplash=livecd-2007.0 kernel

* Linux Kernel 2.6.22-gentoo-r1 for x86...
* kernel: >> Running mrproper...
* config: Using config from /etc/kernels/kernel-config-x86-2.6.22-gentoo-r1
* Previous config backed up to .config.bak
* >> Running oldconfig...
* kernel: >> Cleaning...
* config: >> Invoking menuconfig...


*** End of Linux kernel configuration.
*** Execute 'make' to build the kernel or try 'make help'.

* >> Compiling 2.6.22-gentoo-r1 bzImage...
* ERROR: Failed to compile the "bzImage" target...

* -- Grepping log... --

2. MMConfig (PCI_GOMMCONFIG)
3. Direct (PCI_GODIRECT)
> 4. Any (PCI_GOANY)
choice[1-4?]: 4
PCI Express support (PCIEPORTBUS) [Y/n/?] y
Root Port Advanced Error Reporting support (PCIEAER) [Y/n/?] y
--
SCSI media changer support (CHR_DEV_SCH) [N/m/y/?] n
*
* Some SCSI devices (e.g. CD jukebox) support multiple LUNs
*
Probe all LUNs on each SCSI device (SCSI_MULTI_LUN) [N/y/?] n
Verbose SCSI error reporting (kernel size +=12K) (SCSI_CONSTANTS) [N/y/?] n
--
*
* InfiniBand support
*
InfiniBand support (INFINIBAND) [N/m/y/?] n
*
* EDAC - error detection and reporting (RAS) (EXPERIMENTAL)
*
EDAC core system error reporting (EXPERIMENTAL) (EDAC) [N/m/y/?] n
--
CC ipc/util.o
CC ipc/msgutil.o
CC ipc/msg.o
CC fs/fcntl.o
ipc/msg.c: In function 'sys_msgctl':
ipc/msg.c:390: warning: 'setbuf.qbytes' may be used uninitialized in this function
ipc/msg.c:390: warning: 'setbuf.uid' may be used uninitialized in this function
ipc/msg.c:390: warning: 'setbuf.gid' may be used uninitialized in this function
ipc/msg.c:390: warning: 'setbuf.mode' may be used uninitialized in this function
CC ipc/sem.o
CC fs/ioctl.o
ipc/sem.c: In function 'sys_semctl':
ipc/sem.c:861: warning: 'setbuf.uid' may be used uninitialized in this function
ipc/sem.c:861: warning: 'setbuf.gid' may be used uninitialized in this function
ipc/sem.c:861: warning: 'setbuf.mode' may be used uninitialized in this function
--
CC drivers/ide/ide-io.o
CC fs/sysfs/group.o
LD fs/sysfs/built-in.o
CC fs/udf/balloc.o
fs/udf/balloc.c: In function 'udf_table_new_block':
fs/udf/balloc.c:747: warning: 'goal_eloc.logicalBlockNum' may be used uninitialized in this function
--
CC drivers/ide/setup-pci.o
CC drivers/ide/ide-dma.o
CC fs/udf/partition.o
CC fs/udf/super.o
fs/udf/super.c: In function 'udf_fill_super':
fs/udf/super.c:1359: warning: 'ino.partitionReferenceNum' may be used uninitialized in this function
--
CC drivers/pci/pci-driver.o
CC drivers/pnp/card.o
CC drivers/pci/search.o
CC drivers/pnp/driver.o
drivers/pci/search.c: In function 'pci_find_slot':
drivers/pci/search.c:99: warning: 'pci_find_device' is deprecated (declared at include/linux/pci.h:477)
drivers/pci/search.c: At top level:
drivers/pci/search.c:434: warning: 'pci_find_device' is deprecated (declared at drivers/pci/search.c:241)
drivers/pci/search.c:434: warning: 'pci_find_device' is deprecated (declared at drivers/pci/search.c:241)
--
CC drivers/scsi/scsi_lib.o
CC drivers/video/fbcmap.o
CC drivers/scsi/scsi_scan.o
CC drivers/video/fbsysfs.o
CC drivers/video/modedb.o
drivers/video/modedb.c:1033: error: redefinition of '__kcrctab_fb_destroy_modelist'
drivers/video/modedb.c:943: error: previous definition of '__kcrctab_fb_destroy_modelist' was here
drivers/video/modedb.c:1033: error: redefinition of '__kstrtab_fb_destroy_modelist'
drivers/video/modedb.c:943: error: previous definition of '__kstrtab_fb_destroy_modelist' was here
drivers/video/modedb.c:1033: error: redefinition of '__ksymtab_fb_destroy_modelist'
drivers/video/modedb.c:943: error: previous definition of '__ksymtab_fb_destroy_modelist' was here
make[2]: *** [drivers/video/modedb.o] Error 1
make[1]: *** [drivers/video] Error 2
--
LD drivers/scsi/pcmcia/built-in.o
LD drivers/scsi/scsi_mod.o
LD drivers/scsi/sd_mod.o
LD drivers/scsi/sr_mod.o
LD drivers/scsi/built-in.o
make: *** [drivers] Error 2
--
LD net/ipv4/built-in.o
LD net/built-in.o
* Gentoo Linux Genkernel; Version 3.4.8
* Running with options: --menuconfig --gensplash=livecd-2007.0 kernel

* ERROR: Failed to compile the "bzImage" target...

* -- End log... --


Any ideas?

Rei
_________________
Blog | btrfs | Please stand by - The mailer daemon is busy burning your messages in hell...
Back to top
View user's profile Send private message
soroh6
Apprentice
Apprentice


Joined: 07 Nov 2002
Posts: 231

PostPosted: Fri Jul 13, 2007 9:45 am    Post subject: Reply with quote

Remove or comment the EXPORT_SYMBOL_GPL(blah blah) line that gets added with the patch. I forget what file it's in off hand, sorry.
_________________
:: soroh -*~
Back to top
View user's profile Send private message
ToeiRei
Veteran
Veteran


Joined: 03 Jan 2005
Posts: 1156
Location: Austria

PostPosted: Fri Jul 13, 2007 10:02 am    Post subject: Reply with quote

EXPORT_SYMBOL_GPL() is added in drivers/video/modedb.c - but you were stating in your howto that one of those should remain. There's only one in the result file.

Rei

Update:
It's working now. - Good job!
For genkernel, I think the parameter --initramfs-overlay=/path/to/v86d/initramfs should play nice...
_________________
Blog | btrfs | Please stand by - The mailer daemon is busy burning your messages in hell...
Back to top
View user's profile Send private message
Bones McCracker
Veteran
Veteran


Joined: 14 Mar 2006
Posts: 1569
Location: U.S.A.

PostPosted: Fri Jul 13, 2007 12:01 pm    Post subject: Reply with quote

Please correct me if these assumptions (?) are wrong.

I use a single 512 KB ramdisk for the initrd. My understanding is the RAM allocated to this is released after the boot process?

Code:
title=Gentoo (graphical)
root (hd0,0)
kernel /vmlinuz ro root=/dev/hda5 lapic vga=791 video=vesafb:mtrr:3,ywrap splash=silent,theme:livecd-2007.0 CONSOLE=/dev/tty1 ramdisk_size=512 5
initrd /fbsplash-livecd-2007.0-1024x768


From what I'm hearing here, I would be able to do the same with uvesafb?

Thanks.
Back to top
View user's profile Send private message
star.dancer
Tux's lil' helper
Tux's lil' helper


Joined: 18 Sep 2004
Posts: 93

PostPosted: Fri Jul 13, 2007 7:56 pm    Post subject: Reply with quote

ToeiRei wrote:
Hello star.dancer,

I have followed your howto here, but the kernel refuses to compile. Here's the error message:
Code:

drivers/video/modedb.c:1033: error: redefinition of '__kcrctab_fb_destroy_modelist'
drivers/video/modedb.c:943: error: previous definition of '__kcrctab_fb_destroy_modelist' was here
drivers/video/modedb.c:1033: error: redefinition of '__kstrtab_fb_destroy_modelist'
drivers/video/modedb.c:943: error: previous definition of '__kstrtab_fb_destroy_modelist' was here
drivers/video/modedb.c:1033: error: redefinition of '__ksymtab_fb_destroy_modelist'
drivers/video/modedb.c:943: error: previous definition of '__ksymtab_fb_destroy_modelist' was here



I think you forgot to delete the second entry. This shows that there are two "EXPORT_SYMBOL_GPL(fb_destroy_modelist)" lines in modedb.c. After patching the kernel, there will be one at the very end of the file and there will be one just after the function "fb_destroy_modelist". As the compile error indicates, you will find them on lines 943 and 1033. Have another look at drivers/video/modedb.c, maybe you forgot to save the file or something after deleting one of them (I do that sometimes :) In any case, I'd bet my best shoes there are two of them in there if you are getting that error.
Back to top
View user's profile Send private message
soroh6
Apprentice
Apprentice


Joined: 07 Nov 2002
Posts: 231

PostPosted: Fri Jul 13, 2007 8:17 pm    Post subject: Reply with quote

ToeiRei wrote:
EXPORT_SYMBOL_GPL() is added in drivers/video/modedb.c - but you were stating in your howto that one of those should remain. There's only one in the result file.

Rei

Update:
It's working now. - Good job!
For genkernel, I think the parameter --initramfs-overlay=/path/to/v86d/initramfs should play nice...


star.dancer wrote:
I think you forgot to delete the second entry. This shows that there are two "EXPORT_SYMBOL_GPL(fb_destroy_modelist)" lines in modedb.c. After patching the kernel, there will be one at the very end of the file and there will be one just after the function "fb_destroy_modelist". As the compile error indicates, you will find them on lines 943 and 1033. Have another look at drivers/video/modedb.c, maybe you forgot to save the file or something after deleting one of them (I do that sometimes :) In any case, I'd bet my best shoes there are two of them in there if you are getting that error.


There is only one:

Code:
$ grep EXPORT_SYMBOL_GPL uvesafb-0.1-rc2-2.6.22-rc6.patch
+EXPORT_SYMBOL_GPL(fb_destroy_modelist);


The one the patch adds needs to be removed.
_________________
:: soroh -*~
Back to top
View user's profile Send private message
star.dancer
Tux's lil' helper
Tux's lil' helper


Joined: 18 Sep 2004
Posts: 93

PostPosted: Fri Jul 13, 2007 8:47 pm    Post subject: Yay Reply with quote

To celebrate this joyous uvesafb day, I made a vampire splash screen! (I made a similar one a few years ago but lost the files for it.) You are welcome to use it, just don't tell anyone where I got the pictures from!

Download my vampire splash here!

Code:
cd /etc/splash
tar -zxvf ~/Desktop/Vampire.tar.gz
genkernel --gensplash=Vampire all
gedit /boot/grub/grub.conf


Change the theme name to "Vampire" in grub.conf! Don't forget to check out those scary terminal windows too! This is only 1024x768 and 1200x800 right now (that was the quality of the original pictures).

ps. if you want the boot messages to show up, just uncomment the text lines in the .cfg files. I don't need a message telling me my computer is starting, just a vampire!
Back to top
View user's profile Send private message
tranquilcool
Veteran
Veteran


Joined: 25 Mar 2005
Posts: 1051

PostPosted: Sat Jul 14, 2007 5:48 am    Post subject: Reply with quote

for those who can't wait for a prepatched kernel with uvesafb do this for
2.6.22 kernels patched with vesafb-tng;

get the vesafb-tng patch from spock website,
reverse it,
then
patch your kernel with uvesafb from the same website.
compile and install following the indications on the site.
_________________
this is a strange strange world.


Last edited by tranquilcool on Sun Jul 15, 2007 8:26 am; edited 1 time in total
Back to top
View user's profile Send private message
soroh6
Apprentice
Apprentice


Joined: 07 Nov 2002
Posts: 231

PostPosted: Sat Jul 14, 2007 4:40 pm    Post subject: Reply with quote

I'll make a patch for gentoo-sources-2.6.22 on Sunday night or Monday, I have to go out of town now. :)

Edit: Managed to make the patch before I left, it's on the first post, for gentoo-sources-2.6.22-r1. I also added the uvesafb version to the filename of the patches.

@star.dancer: I linked your Vampire theme in the first post.

_________________
:: soroh -*~
Back to top
View user's profile Send private message
swimmer
Veteran
Veteran


Joined: 15 Jul 2002
Posts: 1291
Location: Netherlands

PostPosted: Sun Jul 15, 2007 12:25 am    Post subject: Reply with quote

I'm afraid the link for the gentoo-sources-2.6.22-r1 patch does not work :-/

Thx for your great work anyway!
swimmer
Back to top
View user's profile Send private message
star.dancer
Tux's lil' helper
Tux's lil' helper


Joined: 18 Sep 2004
Posts: 93

PostPosted: Sun Jul 15, 2007 2:53 pm    Post subject: Reply with quote

swimmer wrote:
I'm afraid the link for the gentoo-sources-2.6.22-r1 patch does not work :-/


Try it again, it seems to be working for me.
Back to top
View user's profile Send private message
spock_
Retired Dev
Retired Dev


Joined: 13 Jun 2003
Posts: 84
Location: Poland, Earth

PostPosted: Sun Jul 15, 2007 3:29 pm    Post subject: Reply with quote

I had a quick look at this thread and thought that I should clarify a few things:

  • vesafb is loaded earlier than uvesafb/vesafb-tng/nvidiafb/whateverfb, therefore it's better for the splash screen: with vesafb the video mode switch does indeed happen earlier than with any other fb driver. However, this DOES NOT mean that the splash screen will be displayed at an earlier stage. It will only appear after the fb driver and fbcon are initialized. If you're bothered by the messages displayed while still in text mode when not using vesafb, use the quiet kernel command line parameter to suppress them.

  • ywrap or ypan are used in the kernel command line, but the driver says it's using redraw: ywrap/ypan are only available on x86.

  • Does v86d have to be included in an initrd?: Yes, it does, unless you want to compile uvesafb as a module.

  • uvesafb requires an initrd, which adds complexity to the boot process: uvesafb only needs the initrd as a storage mechanism to hold the v86d executable. It does not require any special scripts or the use of genkernel. In fact, it doesn't even require an initrd something line in GRUB/LILO -- you can just use CONFIG_INITRAMFS_SOURCE="/usr/src/v86d-0.1/misc/initramfs" in your kernel config and forget that there is an initrd involved :)

  • The framebuffer splash, CONSOLE=/dev/tty1 etc are independent of the fb driver (people often confuse fbsplash and the fbdev layer, but please note that these are two completely different things)

_________________
"In the beginning the Universe was created. This has made a lot of people very angry and been widely regarded as a bad move."
Back to top
View user's profile Send private message
dR0PS
Tux's lil' helper
Tux's lil' helper


Joined: 27 Feb 2005
Posts: 116
Location: DE/Hamburg

PostPosted: Sun Jul 22, 2007 3:44 pm    Post subject: Reply with quote

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
_________________

~x86 gentoo / zen-sources 2.6.36-zen1
Back to top
View user's profile Send private message
Mantaar
Apprentice
Apprentice


Joined: 17 May 2007
Posts: 219

PostPosted: Mon Jul 23, 2007 11:38 am    Post subject: Reply with quote

spock_ wrote:
I had a quick look at this thread and thought that I should clarify a few things:

  • uvesafb requires an initrd, which adds complexity to the boot process: uvesafb only needs the initrd as a storage mechanism to hold the v86d executable. It does not require any special scripts or the use of genkernel. In fact, it doesn't even require an initrd something line in GRUB/LILO -- you can just use CONFIG_INITRAMFS_SOURCE="/usr/src/v86d-0.1/misc/initramfs" in your kernel config and forget that there is an initrd involved :)

While this is absolutely true and in fact the way I'm doing it myself, people who have a separate /usr partition should copy their initramfs to /boot and point the kernel there.

I'm using uvesafb exclusively now though it requires me to use an initramfs where I wouldn't do that usually... but the much faster console makes up for it ;) - finally I can run my console @1400x1050 without waiting half an hour for a manpage to roll up the screen. Very nice work :)
_________________
Error compiling committee.c: too many arguments to function.
Back to top
View user's profile Send private message
manwe_
Guru
Guru


Joined: 01 Feb 2006
Posts: 564
Location: Kraków/Cracow, Poland

PostPosted: Tue Jul 24, 2007 1:45 pm    Post subject: Reply with quote

Any ideas how to get non-vesa resolutions? Like 1280x800 and 1920x1200.

Code:
$ cat /sys/bus/platform/drivers/uvesafb/uvesafb.0/vbe_modes
640x400-8, 0x0100
640x480-8, 0x0101
800x600-8, 0x0103
1024x768-8, 0x0105
320x200-16, 0x010e
320x200-32, 0x010f
640x480-16, 0x0111
640x480-32, 0x0112
800x600-16, 0x0114
800x600-32, 0x0115
1024x768-16, 0x0117
1024x768-32, 0x0118
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

$ dmesg | grep uvesafb:\
uvesafb: NVIDIA Corporation, G72 Board - e462h1  , Chip Rev   , OEM: NVIDIA, VBE v3.0
uvesafb: VBIOS/hardware supports DDC2 transfers
uvesafb: monitor limits: vf = 76 Hz, hf = 83 kHz, clk = 170 MHz
uvesafb: scrolling: redraw
uvesafb: framebuffer at 0xc0000000, mapped to 0xffffc20000600000, using 6144k, total 65536k
Back to top
View user's profile Send private message
Gusar
Advocate
Advocate


Joined: 09 Apr 2005
Posts: 2643
Location: Slovenia

PostPosted: Tue Jul 24, 2007 2:15 pm    Post subject: Reply with quote

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).
Back to top
View user's profile Send private message
manwe_
Guru
Guru


Joined: 01 Feb 2006
Posts: 564
Location: Kraków/Cracow, Poland

PostPosted: Tue Jul 24, 2007 2:22 pm    Post subject: Reply with quote

Gusar wrote:
Why do you assume that a vesa driver can produce non-vesa resolutions?

Not assume, I was just hoping for. 1024x768 on 24" widescreen looks just a bit crappy :?
Back to top
View user's profile Send private message
Bitspyer
Apprentice
Apprentice


Joined: 17 Dec 2002
Posts: 204
Location: Mainz, Germany

PostPosted: Thu Jul 26, 2007 2:43 pm    Post subject: Reply with quote

Hmmm...

When trying uvesafb with my Lenovo T60 and ATI x1400 there is nothing than strange paintings on my screen.... Since when X starts, everything is OK.

Also, the current patch from spocks Page doesn't work with 2.6.22-r1 gentoo-sources.

Only the patch from here (http://www2.incith.com/~incith/uvesafb-0.1-rc2-gentoo-2.6.22-r1.diff.bz2) works... Don't know why....
_________________
Der Weg zur Dunklen Seite... Schneller er ist, verführerischer, leichter.
Back to top
View user's profile Send private message
Mantaar
Apprentice
Apprentice


Joined: 17 May 2007
Posts: 219

PostPosted: Thu Jul 26, 2007 9:29 pm    Post subject: Reply with quote

Bitspyer wrote:

Only the patch from here (http://www2.incith.com/~incith/uvesafb-0.1-rc2-gentoo-2.6.22-r1.diff.bz2) works... Don't know why....

The reason for that is quite obvious: The gentoo-sources package contains a vesa-fb system already patched and Spock's uvesafb patchset is intended for use against a vanilla kernel (get it from kernel.org or via `emerge vanilla-sources'). You can also revert the vesafb-tng patch (get it off Spock's website or find it in $PORTDIR/sys-kernel/gentoo-sources/files and add -R to the options for `patch' to revert a patch) and try applying the uvesavfb patch afterwards.

The patch you pointed to seems to make this obsolete as it's one that would apply against a gentoo-sources kernel...
_________________
Error compiling committee.c: too many arguments to function.
Back to top
View user's profile Send private message
star.dancer
Tux's lil' helper
Tux's lil' helper


Joined: 18 Sep 2004
Posts: 93

PostPosted: Tue Jul 31, 2007 3:02 pm    Post subject: Reply with quote

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!
Back to top
View user's profile Send private message
eatnumber1
n00b
n00b


Joined: 13 Jan 2007
Posts: 55
Location: New York

PostPosted: Sun Aug 05, 2007 6:52 am    Post subject: Reply with quote

hmm, i'm running x86 and have ywrap on my command line, but am still getting redraw... any help?

Code:
uvesafb: Intel Corporation, Intel(r) 82945GM Chipset Family Graphics Controller, Hardware Version 0.0, OEM: Intel(r) 82945GM Chipset Family Graphics Chip Accelerated VGA BIOS, VBE v3.0
uvesafb: VBIOS/hardware supports DDC2 transfers
uvesafb: monitor limits: vf = 61 Hz, hf = 48 kHz, clk = 65 MHz
uvesafb: scrolling: redraw
uvesafb: framebuffer at 0xd0000000, mapped to 0xf8a00000, using 6144k, total 7872k

Code:
title=Gentoo: Normal
root (hd0,0)
kernel /boot/vmlinuz root=/dev/sda3 video=uvesafb:1024x768-32@50,mtrr:4,ywrap max_loop=64
Back to top
View user's profile Send private message
eatnumber1
n00b
n00b


Joined: 13 Jan 2007
Posts: 55
Location: New York

PostPosted: Sun Aug 05, 2007 7:10 am    Post subject: Reply with quote

It seems that the x86d daemon has support for x86 accelerated emulation, and ATM the ebuild does not activate this on x86 machines. I filed a bug with a fix for this, lets hope that it gets put into portage.
http://bugs.gentoo.org/show_bug.cgi?id=187779
Back to top
View user's profile Send private message
Manii
n00b
n00b


Joined: 06 Aug 2007
Posts: 1

PostPosted: Mon Aug 06, 2007 5:29 am    Post subject: Reply with quote

manwe_ wrote:
Any ideas how to get non-vesa resolutions? Like 1280x800 and 1920x1200.


I'm using uvesafb on my debian sytem (dell latitude d820) and it's doing 1920x1200 quite fine (didn't work with vesafb-tng...)

Code:

video=uvesafb:1920x1200-32,mtrr:3,ywrap
Back to top
View user's profile Send private message
p4r0l3
n00b
n00b


Joined: 12 Jan 2006
Posts: 26

PostPosted: Tue Aug 14, 2007 4:49 pm    Post subject: Reply with quote

I've got uvesafb working, however no matter which theme I use, the progress bar never works.

Here is my /etc/lilo.conf
Code:

image=/boot/vmlinuz-2.6.22-kamikaze5
   label=gentoo
   read-only
   root=/dev/sda3
   append="usbhid.mousepoll=2 udev video=uvesafb:1024x768-32@60,mtrr:3,ywrap splash=silent,fadein,theme:gentoo quiet console=tty1"
   initrd = /boot/uvesafb-gentoo

Any ideas on how to fix this?
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 2 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