Bugzilla – Bug 406602
New KDE4 Installation fails after auto configuration and cannont be repaired nor finalised - Complete failure of Default Install of KDE4!!! Suse 11.0
Last modified: 2008-08-04 08:04:10 UTC
Local Network Installation of kde4 runs without issue, 1 HDD formatted with ex3 and /, swap,/home mount points. Software is installed without issue, user creation NOT equal to root, root password assigned o.k After all 'automatic configuration' has taken place and all hardware has been found, system re-boots to a console only login prompt. I have tried local complete DVD install with same results. I have tried to 'repair' installed system via automatic repair - no fix. I made sure creation of user was written to local /etc directory and not changed encryption defaults! 1st boot works o.k, however boot after 'automatic configuration' fails as it switches to load modules ending in Quote Starting Name Server Cache Daemon Starting mail service (Postfix) Starting SSH Starting CRON Starting powersaved: Starting smartd Starting Firewall Initialization (phase 2 of 2) Master Resource Control: runlevel 5 has been Skipped services in runlevel 5: Welcome to openSUSE 11.0 (X86-64) - Kernel 2.6.25.5.1-1.1-default (tty1). linux-5hj2 login: END QUOTE I can login at this point as either root or user - user successful login replies Have Lots of Fun!!!!!!! Installing KDE3 is NOT an OPTION I also have another 6 X_64 PC's to Install after this one ALL are X_64 CPU Have read online installation guide which ends with 'Automatic Installation" http://en.opensuse.org/Installation/11.0_DVD_Install#Completion_of_Installation Please advise how I can help with logs on the incomplete PC and how I get them OFF the PC to include in bug report This is far from fun.!
This problem appears to only be present on all AMD Athlon 64 X2 Dual Core Processors of which all but one of my PC's has a variety of Motherboards and CPU speeds. My old Intel P4 HT 3.2 is stable and installation completed o.k, however updating of previous V 10.3 presented many issues, far outside the scope of this bug.
More information ####### This issue is NOT related to Architecture what so ever############ I did try the boot option 'nohpe' with same result. This issue is related to the failure of Automatic Complete of Installation. The Automatic Completions relies on the user using AND having DHCP Services available - I am sorry the world does NOT depend on DHCP all the time. 1. I de-selected Auto config at start of Install - all went well until Network Configuration - I configured a Static IP and DNS servers and attempted to download Release Notes which failed!!!!! I continued without online update and Install finalised with 3 errors and left me with a black Login Screen. I logged in as root and started Yast2 - In the Network Config the DNS Server I entered were NOT written to the config, but the static IP was and gateway was AND you still cannot deselect - Update DNS Data via DHCP - no Interface with DHCP. I went to Software Update in Yast (text) and the update started immediately downloading updates after DNS servers were written to config. The default Installation FAILS completely when a Static IP is used AND MOSTLY in ANY situation where there are NO DHCP Services available on the Network. This is a huge error in judgement that the default install excludes the user from configuring and entering DNS Servers Manually. AND The TOTAL - non automatic AND automatic installation is dependant on DHCP services being present, hence not auto connection with my DNS Servers, no writing to config of DNS Servers even when they are enter during GUI Install. The Install appears at this time to be dependant on downloading and Installing KDE4-Post Release fix - which I assume at this point in time will complete a correct installation - more updates if it does not ---later ????? If the user elected to skip the online update during GUI install they too would have a failed installation. Personally, I would strongly urge you to specify on the Download Page something to the effect that if you do not have DHCP services available 'DO NOT DOWNLOAD' I would also strongly suggest you consider a second release of GM1 and create GM2 as soon as possible - I say this under the assumption of the Post release KDE4 online updates provides a usable installation - details will follow if this is NOT the case.
In text Yast2 as above - I went online update configuration - which did add an update server. I then ran online update and 158 updates were loaded including 4 items titled KDE4 post release updates. After reboot - default boot would not start x windows manager - possible because I added 'nohpe' to boot options as I thought this was a Hardware issue in X-64, HOWEVER ''FILSAFE' correctly booted a totally completed KDE4 GUI screen. So the current install will fail under the following 1. It is a New KDE4 System and the user manually configures network - result Static IP was written to config BUT NOT the DNS Servers. AND/OR 2. There are NO DHCP services provided by the Network 3. The user elects to not run online update during install. As I have a complete working system now I can provide logs, however I AM VERY CERTAIN of the above conditions. In Large Secure Networks NO DHCP services are available as there are many many places any-one can plug into and automatically receive a valid IP and DNS Servers - This is security 101 Please advise what logs you require in order to correct this release, happy to help, however, as embarrassing as it is - I think you should take this release down, until a 100% reliable installation can be done. I think there are far too many variables and IF's that make the difference between an Installation working OR Failing to consider the current GM release acceptable. Your thoughts and please advise which logs you require.
Correct Priority Logs available when required
Hello, could you provide yast2 logs from installation ? Thanks
Apologies for delay, original logs files in /var/log/yast lost.... Happy to re-produce faithfully and make files available with date + 5
Created attachment 229210 [details] yast2 log files It wound appear that there are multiple issues here. I would believe that these log files may not reflect reported error. I can halt autoconfig and configure manually to illustrate reported error. It is now the final belief that the reported error is indicative of a situation where the Installation Network does not provide ANY DHCP services. IE IP address AND/OR DNS Services. Please advise IF you wish me to continue installation manually and configure a static IP. In this situation IF DNS services are not provided by DHCP the install will fail.
I'm not sure what's the problem. From log: Write resolv.conf content: nameserver 123.200.191.17 Please provide briefly how-to reproduce this bug.
Created attachment 230156 [details] yast2logs 1 of 1 Apologies for delay. Again there are multiple issues more than I can could on different hardware. The lost current and now added show installation failure. 1st logs show installation failure - due to ? when auto config in ON 2nd logs show installation failure - due to ? where auto config is OFF Final thoughts are errors in determining hardware display,graphics card, sound etc, unable to duplicate DNS error in this new test hardware. Attaching yast logs again. Please advise if I can supply any other details.
*** Bug 407377 has been marked as a duplicate of this bug. ***
Created attachment 230923 [details] log files after complete install (non autoconfig) - Unable to detect monitor - user altered size and aspect only
Created attachment 230926 [details] complete /var/log directory - /yast directory is the same as preceding attachment
This report is packed with so many different issues that it is very hard to handle. I will refocus it on the DHCP problem. It appears that the KDE problem has been meanwhile addressed by an online update. Adjusting summary (Was: New KDE4 Installation fails after auto configuration and cannont be repaired nor finalised - Complete failure of Default Install of KDE4!!! Suse 11.0) Comment 11 and 12: Monitor detection? Please open separate reports for unrelated problems. Comment 7 and 8: y2start.log shows that network configuration was entered manually in linuxrc Miso, I hope you can reproduce it now.
The problem is that network is down after network card configuration in 2nd stage. This has nothing to do with DHCP/static configuration As workround do "rcnetwork restart" *** This bug has been marked as a duplicate of bug 399645 ***