I have recently done clean installs of 11.4 on two computers and then done clean re-installs but still have the same problem. Each time, the install was without flaw and I could download the updates, when offered, in the install process. At the end of the install I can log into KDE and everything works. However, after shutting down, on reboot, I only get a command line login. I can either login and run startx or use su and do init 3 followed by init 5. This tells me I am getting to runlevel 5 but X isn’t starting. Either of those approaches gives me the KDE login. However, after that I have to manually start the network in YAST. I also think I had had to restart CUPS but I have only got as far as installing a printer once so I can’t be absolutely sure that happened.
As I indicate, this is fully reproducible. Anyone give me a clue as to what is going on?
On 04/15/2011 12:06 PM, MikeyOT wrote:
> install was without flaw and I could download the updates, when offered,
> in the install process. At the end of the install I can log into KDE
> and everything works. However, after shutting down, on reboot, I only
> get a command line login.
sounds like something in the update (probably a new kernel) wasn’t
completely installed until the boot after the update…
i guess you now have a graphics driver conflict with the newer kernel…
which you can probably sort through with one (or some of both) of the
following, and holler if you get stuck:
It does not read to me that the install was without flaw, as you have this problem.
Have you had a completely successful install (include weeks of satisfactory operation) with openSUSE before ? I have the impression that your installation was only partially successful and failed after the 1st reboot. I have an ‘impression’ that your login to KDE after what you think was a successful install, in fact was not a complete install and everything may not have been successfully configured.
If it were me, I would redo the install with the ‘nomodeset’ boot code specified in the installation CD/DVD, and if there is a reboot I would replace that code. If this is AMD hardware, that will force the radeonhd graphics driver (instead of radeon graphics driver). If this is nVidia hardware, that will force the nv graphics driver instead of the nouveau grapics driver. If this is Intel graphic hardware that will force the FBDEV graphic driver (instead of the Intel Graphic driver).
If that does not work (ie no boot afterward) then I would try re-installing, but this time press F3 (I think) at the first cd/dvd grub splash menu (before the install starts) and select ‘safe settings’ which will install with the FBDEV driver for the entire installation process.
Thanks guys. I see there are a number of other posters with what looks like exactly the same problem (see other threads about 11.4 booting). I’ll start investigating along the lines you have all suggested. First off here are some off the top answers.
Mobo: Gigabyte 890FXA-UD5
CPU: AMD Phenom II X6 1075T
Graphics: single ASUS ENGTX470
RAM: Corsair xms3 8GB
Have been using Suse since version 8 with very few problems other than the usual scuffles with proprietary sound & graphics drivers - getting Amarok and X-Plane to work is always a hassle. 11.3 was fine with this set up and proprietary nVidia drivers - giving very high fps in X-Plane - very satisfactory indeed. I did try Kubuntu 10.10 and that was fine too. I have never had the network not starting before and as I intimated (and others have also stated elsewhere) there are a number of other services that I am having to start manually once at full runlevel 5.
I have changed /etc/sysconfig/boot:run parallel to no and that appears to work to some extent - I do now get a full runlevel 5 start and the kdm login. Having set verbose options, I see during boot that DCHP4/DCHP6 takes a really long time to start and does not appear to have started by the time kdm is up and running. Maybe I need to either give it more time? Eventually I do get the network running but by then I have usually tried one or two things in YAST so am not sure whether it started by itself or because of something I did.
A surf on the internet suggests this is a GeForce GTX 470.
Don’t forget to conduct the media check, as was suggested by gogalthorp. In particular run an md5sum check on the downloaded .iso file, and compare that md5sum to that posted on the internet. Also when burning the CD/DVD, do so at the slowest speed your burner allows to a +R or -R media (not to an RW) to a high quality media (not some bargain basement special). Also run the media check on the cd/dvd.
Support for the GTX 470 was introduced about a year ago with the 195.36.24 proprietary nvidia driver (dated 2010.04.28) and it thus should be supported in the current 271.41.03 nVidia proprietary graphic driver. Back in August last year, it was noted there was no opensource graphic driver support for the GTX 470: [Phoronix] Nouveau In Linux 2.6.36 Has NVIDIA Fermi Mode-Setting](http://www.phoronix.com/scan.php?page=news_item&px=ODQ5MQ) and if that is still the case, then you will likely need to use either the FBDEV graphic driver (which pretty much should work with all cards) or the VESA graphic driver.
And then once those are setup (which will give very poor but functional performance) you can install the proprietary nVidia driver.
Guidance can be given on this thread as to how to do that, if you don’t know the technique. Just advise!
I will look at my downloaded .iso with MD5 and run the media check on the CD I burned - I guess I’ve gotten lazy since I haven’t had a problem for some years. I always use the slowest burning rate and am coming to the end of a 50-pack of TDK CDs. I never buy the cheap or unbranded CDs.
I always have a spare box (current one is with a dual core Athlon and an ATi HD5770, which is unusual for me as I am a big nVidia fan and have had some bad experiences in the past with ATi cards. I do like to try every distro that comes out and tend to use this second box for that. It’s also my “Music” box with 64studio on ons of the drives.
Anyway, having changed the setting in sysconfig/boot, as per another thread on here, to RUN_PARALLEL=no, I find that kdm launches every time and all I need do is manually restart the network, even though it is now set to come on at boot. I also tried disabling DHCP6 to see if that made a difference but DHCP4 on its own still takes ages to start up.
Since it now seemed to be working after a fashion, I installed the nVidia prop. drivers, which installed without a hitch and rebooting got me into kdm. I restarted the network and now I can fly X-Plane with fps figure of ~200fps in the default scenery area and when I move to UK with higher antil-aliasing and details, plus full photo VFR scenery and airports loaded with planes & buildings, I still get 120- 140fps. In Windows 7 I get about half that on this same machine!
So - I am a (quite) happy bunny and will continue to try to discover the cause of my network not starting at boot. I’ll go check the CD now…