| 1 |
So basically I need to redo my kernel config to make sure that I am only |
| 2 |
using vesafb. Easy enough I suppose. |
| 3 |
|
| 4 |
-----Original Message----- |
| 5 |
From: Chris Gianelloni [mailto:wolf31o2@g.o] |
| 6 |
Sent: Thursday, September 08, 2005 2:17 PM |
| 7 |
To: gentoo-catalyst@l.g.o |
| 8 |
Subject: RE: [gentoo-catalyst] gensplash |
| 9 |
|
| 10 |
On Thu, 2005-09-08 at 13:59 -0500, Kessler, Paul wrote: |
| 11 |
> Ok I got past the error by making sure CONFIG_FB_VESA_TNG=y in my |
| 12 |
kernel |
| 13 |
> config. Everything got put where it should be. I did notice a warning |
| 14 |
> that said I might have to pass this to the kernel: |
| 15 |
|
| 16 |
Actually, you do *not* want VESA_TNG, but the *normal* vesafb, |
| 17 |
otherwise, you need to use video= rather than vga=, and catalyst does |
| 18 |
*not* do this for you automatically. |
| 19 |
|
| 20 |
> vga=791 splash=silent,theme:livecd-2005.1 CONSOLE=/dev/tty1 quiet |
| 21 |
|
| 22 |
Catalyst does this automatically. We do not use VESAFB-tng, because it |
| 23 |
is not cross-architecture compatible. |
| 24 |
|
| 25 |
> Sure enough when I booted the latest build I got the message about |
| 26 |
> passing a bad number again. Should I be passing this like to the |
| 27 |
kernel |
| 28 |
> in the stage2 spec, and if so under livecd/bootargs? |
| 29 |
|
| 30 |
Nope. |
| 31 |
|
| 32 |
-- |
| 33 |
Chris Gianelloni |
| 34 |
Release Engineering - Strategic Lead/QA Manager |
| 35 |
Games - Developer |
| 36 |
Gentoo Linux |
| 37 |
|
| 38 |
-- |
| 39 |
gentoo-catalyst@g.o mailing list |
Archives