No X at boot when no network available? (Fedora 16)
I'd appreciate help troubleshooting a problem I'm experiencing with F16 (or Fedora 16).
When the network is available, the system boots up to the gnome login screen (to choose a username to log in with).
When the network is not available, the system will be apparently idle for a while after the same old message (that I get on every boot, network or no):
Failed to start LSB: Builds and install new kmods from akmod packages [FAILED]
See 'systemctl status akmods.service' for details.
After several seconds (I want to say >30), the screens will seem to show X starting up (and I get that pointlessly annoying "AMD Unsupported Hardware" in the lower right corner), but instead of the window offering me which user to log in as, it goes black and comes back a few times before it finally goes back to the terminal-style view with the new messages of:
Starting SYSV: Grant or revoke access to X for the ATI Exte... Events Daemon...
Started SYSV: Grant or revoke access to X for the AT...l Events Daemon [ OK ]
Starting SYSV: Late init script for live image....
Starting firstboot configuration program (graphical mode)...
Starting /etc/rc.d/rc.local Compatibility...
Note: I see these messages because I hit ESCAPE during the boot process.
This problem is 100% repeatable. Reboot with the cable unplugged- problem. Reboot with the cable plugged in- boot and login are fast and smooth as usual.
Any help? I'd like to be able to run even without an internet connection, but I don't know where to begin troubleshooting.
I hope im not stating the obvious, but clearly your akmod is rebuilding your xorg drivers/config at boot. Not just at Kernel change, but also at every boot.
This would be the beginning of your search, look up where it states that akmod should reconfigure. I cant help you there but im sure other people on this forum can. (and in any other case, the internet!)
Also it is time to upgrade
fedora 16 is almost at End Of Life ( about 13 DAYS )
fedora 18 is the current
I'm not sure what would have caused that, nor really how to fix it. I guess I can look into that, but I don't see how that puts the presence of a network connection on the critical path to be successfully able to get into X and log in.... Am I missing something? I'm not very Linux savvy these days (not that I ever was that savvy to begin with!)...
I've had fairly unsatisfactory experiences in the past with upgrading to the latest with Fedora. ...but you're right, perhaps I should start looking to see if F17 is mature enough. I'll probably look at F18 when F19 comes out.
Thanks in advance for any help you can give with my issue! (or just helping my understanding of how the presence/absence of a network connection can affect successfully getting into X)
It is only supposed to do that IF the kernel has changed
did you by chance edit it or the boot line in the bootloder
I don't see why akmod driver rebuilding (or trying to rebuild) on every boot requires a network connection.
Many thanks for your help!
|All times are GMT -5. The time now is 06:57 PM.|