Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 46678 - "Processor type and features ---> Use register arguments" breaks bootsplash
Summary: "Processor type and features ---> Use register arguments" breaks bootsplash
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High trivial (vote)
Assignee: Michal Januszewski (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-03 04:08 UTC by Christoph Brill (egore) (RESIGNED)
Modified: 2004-04-04 13:27 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Brill (egore) (RESIGNED) 2004-04-03 04:08:58 UTC
If i use Processor type and features  ---> Use register arguments in kernel options, i can no longer use a bootsplash image during boot (works after /etc/init.d/bootsplash start, so maybe it's an issue with initrd). Maybe add a comment to the bootsplash ebuild.

Reproducible: Always
Steps to Reproduce:
Comment 1 Heinrich Wendel (RETIRED) gentoo-dev 2004-04-03 05:17:20 UTC

*** This bug has been marked as a duplicate of 46677 ***
Comment 2 Christoph Brill (egore) (RESIGNED) 2004-04-03 08:33:40 UTC
Hmm, if you read the text you would realize this is NOT a duplicate (IMHO). If the note goes into the ebuild for bootsplash, you are wrong. If the note goes into kernel ebuild, i am wrong and this is a duplicate. I'm not sure where the note should go, please comment on this.
Comment 3 Michal Januszewski (RETIRED) gentoo-dev 2004-04-04 13:27:19 UTC
egore: you're right. These two bugs, though related, are not about the same thing. 
I've added a note about Bootsplash not working with CONFIG_REGPARM enabled to the latest bootsplash ebuild (-r13). I've also started tracing the problem in the bootsplash code and it appears to be more kernel-related than bootsplash-related, so I dropped it for now. We'll see if the problem is fixed in the post-2.6.5 kernels.