| Summary: | No Framebuffer Console after updating to udev-182, kmod-7 and consolekit-0.4.5-r3 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | mummenschanz <mummenschanz> |
| Component: | [OLD] Core system | Assignee: | OpenRC Team <openrc> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | pacho, udev-bugs |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
dmesg log
kernel config |
||
|
Description
mummenschanz
2012-03-29 06:50:28 UTC
Created attachment 307051 [details]
kernel config
Seems more like a configuration problem, than a real bug. When are you loading modules from FRAMEBUFFER_CONSOLE and DRM_I915 ? Hi, thanks for the fast reply. I've compiled both FRAMEBUFFER_CONSOLE and DRM_I915 as modules. To ensure they are loaded in the right sequence I've put modules="fbcon" in my /etc/conf.d/modules but this didn't change anything. How can I see when exactly those modules are being loaded? Thanks Dieter (In reply to comment #3) > Hi, > > thanks for the fast reply. I've compiled both FRAMEBUFFER_CONSOLE and > DRM_I915 as modules. To ensure they are loaded in the right sequence I've > put modules="fbcon" in my /etc/conf.d/modules but this didn't change > anything. How can I see when exactly those modules are being loaded? Is the /etc/init.d/modules service run at boot? It looks like it is: gonzo / # rc-update add modules boot * rc-update: modules already installed in runlevel `boot'; skipping or do I have to add the service as default? (In reply to comment #5) > It looks like it is: > > gonzo / # rc-update add modules boot > * rc-update: modules already installed in runlevel `boot'; skipping > > or do I have to add the service as default? It should do fine in the boot runlevel. I guess this is an openrc problem (since the kernel says nothing about loading the fbcon module). Please set rc_logger="YES" in /etc/rc.conf, reboot then attach /var/log/rc.log. (In reply to comment #7) > Please set rc_logger="YES" in /etc/rc.conf, reboot then attach > /var/log/rc.log. Also check if this is still valid with udev-189 Comment #7 and Comment #8 (try with 197-r3) -> RESOLVED, TEST-REQUEST Reopen once tested and the requested log has been provided |