| 1 |
On 23 August 2005 20:14, Holly Bostick wrote: |
| 2 |
> Matthias Krebs schreef: |
| 3 |
> > And as |
| 4 |
> > someone else mentioned before, vesafb-tng is not a valid kernel |
| 5 |
> > parameter, so everything after it is ignored. |
| 6 |
> |
| 7 |
> In what world is this? If you're using vesafb-tng (added to the kernel |
| 8 |
> options by the fbsplash patch which you get with the gentoo kernels, |
| 9 |
> which is no surprise, given that it was created by spock, a gentoo |
| 10 |
> developer), then it most certainly is a valid kernel parameter (and was |
| 11 |
> selected in the kernel config output that was posted in a previous message. |
| 12 |
> |
| 13 |
> If the post you're referring to was Uwe's, I don't think he meant that |
| 14 |
> the parameter was invalid, but rather that rather than using vesafb-tng, |
| 15 |
> that the OP should try "regular" vesafb, which might work where |
| 16 |
> vesafb-tng wasn't working. |
| 17 |
|
| 18 |
Nope, that was not what I meant. I meant: If you select vesafb-tng during |
| 19 |
kernel configuration, "vesafb" on the kernel command line refers to |
| 20 |
vesafb-tng. That's how it works here without *any* problem. |
| 21 |
|
| 22 |
Uwe |
| 23 |
|
| 24 |
-- |
| 25 |
95% of all programmers rate themselves among the top 5% of all software |
| 26 |
developers. - Linus Torvalds |
| 27 |
|
| 28 |
http://www.uwix.iway.na (last updated: 20.06.2004) |
| 29 |
-- |
| 30 |
gentoo-user@g.o mailing list |
Archives