| Summary: | bootsplash oopses on boot with kernel 2.6.5-r1 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Evan Langlois <evan> |
| Component: | [OLD] Core system | Assignee: | Michal Januszewski (RETIRED) <spock> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Evan Langlois
2004-05-09 00:30:16 UTC
Yup, bootsplash currently works only with vesafb. Try enabling DEV_BLK_INITRD and DEV_BLK_RAM (set them both to 'y' in the 'Block devices config section) to avoid bootsplash oopses. Please let us know about the results. CONFIG_BLK_DEV_RAM and CONFIG_BLK_DEV_INITRD are both set to 'Y' (as shown). I don't think there are DEV_BLK_ options. Anything else that could be causing a kernel panic? You're right, I'm sorry I didn't notice you had these options enabled. The problem you're experiencing is probably caused by the CONFIG_REGPARM option - bootsplash ebuilds warn not to enable it. OK, I'm assuming this is fixed by turning off the REGPARM option. If it isn't, please reopen. turning off REGPARM fixed it! Thanks! I'm still having this same behavior here: CONFIG_BLK_DEV_RAM and CONFIG_BLK_DEV_INITRD are set to Y and CONFIG_REGPARM is NOT SET. Also, the "silent" images are never showed... Tell me what info you need about my system - It's pretty much the same thing as Evans'... Ok, please redirect all non-REGPARM-related problems to bug #47014, which seems to be about the same problem you're describing here. Please stay tuned, I'm working on some means to help us identify the root of these problems. |