[opensuse-factory] Milestone5 observations
Because I had to install a new server this morning, I figured I might as well try out M5 and see how it goes. These are just observations, the server will be reinstalled and prepared for production today and tomorrow, so no follow-ups or "try this and that". Context: Software: M5 IA32, NET iso, repo=factory. Hardware - Proliant server, dual Intel 32bit-only Xeon, 2Gb RAM. Installation on 4-drive RAID5 SCSI array behind Compaq Smart-Array. 1. on booting the NET iso, I noticed the text-version of the boot menu flash past, visible for 1-2 seconds. 2. the popup window saying "loading linux kernel" went immediately to 100%, then stayed there, flashing every now and then, then went back to 0% before switching to textmode to continue boot-up. 3. license was first displayed in German. 4. "Suggested partitioning": No automatic proposal possible. I did a rescan disks, but that didn't change anything. I then partitioned the array manually, tried rescan again, no change. Diags: http://jessen.ch/files/neon-hwinfo.txt http://jessen.ch/files/neon-lspci-v.txt http://jessen.ch/files/neon-y2logs.tar.gz /Per -- Per Jessen, Zürich (22.9°C) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Per Jessen wrote:
4. "Suggested partitioning": No automatic proposal possible. I did a rescan disks, but that didn't change anything. I then partitioned the array manually, tried rescan again, no change.
See bug 531568. -- Per Jessen, Zürich (22.8°C) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Samstag 15 August 2009 schrieb Per Jessen:
Because I had to install a new server this morning, I figured I might as well try out M5 and see how it goes. These are just observations, the server will be reinstalled and prepared for production today and tomorrow, so no follow-ups or "try this and that".
Context: Software: M5 IA32, NET iso, repo=factory. Hardware - Proliant server, dual Intel 32bit-only Xeon, 2Gb RAM. Installation on 4-drive RAID5 SCSI array behind Compaq Smart-Array.
1. on booting the NET iso, I noticed the text-version of the boot menu flash past, visible for 1-2 seconds.
2. the popup window saying "loading linux kernel" went immediately to 100%, then stayed there, flashing every now and then, then went back to 0% before switching to textmode to continue boot-up. Both of them are known.
3. license was first displayed in German.
Huh? No idea where the problem should come from. You didn't select any language? Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Stephan Kulow wrote:
3. license was first displayed in German.
Huh? No idea where the problem should come from. You didn't select any language?
Nope - I hadn't changed any setting up until then. Keyboard and language were both US English. /Per -- Per Jessen, Zürich (25.9°C) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Samstag 15 August 2009 schrieb Per Jessen:
3. license was first displayed in German.
I saw it now too - the problem seems to be that there is no match for "en_US" license, so he picks the first the tar and that happens to be .de Did you file a bug? Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thursday 20 Aug 2009 13:01:15 Stephan Kulow wrote:
Am Samstag 15 August 2009 schrieb Per Jessen:
3. license was first displayed in German.
I saw it now too - the problem seems to be that there is no match for "en_US" license, so he picks the first the tar and that happens to be .de
Did you file a bug?
Greetings, Stephan
MS5 obs Grub you can not choose en_GB as a language Network setup (this one is still in existence since 10.0 at least) when yast attempts to configure the network it fails every time it seems not to be able to set the gateway IP the nameserver IP DHCP fails to get an address with the failures yast just whinges and continues with out network not checking for updates , Once i go in and edit things by hand every thing is rosey dhcp finds an address the Correct gateway and nameservers are detected fine The ATI thing (Grrrrrrrrrrrr) needed to use "radeon.modeset=0" once the first reboot was over to get any graphics at all . Then did the check for updates Vast amounts after updates reboot no graphics no keyboard no mouse , Had to boot into runlevel 3 and run a " zypper up" another 800+Mb update then keyboard and mouse back but still need the "radeon.modeset=0" thing to get any graphics output . It seems from what i read i may now be running MS6 is that right if so then the ATI bugs are still alive and kicking hard not had chance yet to play with anything else it was getting too late and an early start was called for hell of a lot to do in the next few weeks before the schools go back. Pete .
Peter Nikolic wrote:
MS5 observations
Network setup (this one is still in existence since 10.0 at least) when yast attempts to configure the network it fails every time it seems not to be able to set the gateway IP the nameserver IP DHCP fails to get an address with the failures
Peter, are you seriously suggesting that YaST network setup has not been working since 10.0 ?? I can't exactly confirm that - the only network config problem I have had is when I do an installation over ssh+nfs and then change the network address during stage2. Mea culpa really. /Per -- Per Jessen, Zürich (17.4°C) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Saturday 22 August 2009 12:18:41 Per Jessen wrote:
Peter, are you seriously suggesting that YaST network setup has not been working since 10.0 ??
Not really sure where this one is coming from, network configuration during network install has been working fine since as long as I can remember. -- “Experience is the name everyone gives to their mistakes.” ☘ Oscar Wilde -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Saturday 22 Aug 2009 12:05:45 Graham Anderson wrote:
On Saturday 22 August 2009 12:18:41 Per Jessen wrote:
Peter, are you seriously suggesting that YaST network setup has not been working since 10.0 ??
Not really sure where this one is coming from, network configuration during network install has been working fine since as long as I can remember. not talking about netinstall dont do them so i cant say .
On Saturday 22 Aug 2009 11:18:41 Per Jessen wrote:
Peter Nikolic wrote:
MS5 observations
Network setup (this one is still in existence since 10.0 at least) when yast attempts to configure the network it fails every time it seems not to be able to set the gateway IP the nameserver IP DHCP fails to get an address with the failures
Peter, are you seriously suggesting that YaST network setup has not been working since 10.0 ?? I can't exactly confirm that - the only network config problem I have had is when I do an installation over ssh+nfs and then change the network address during stage2. Mea culpa really.
/Per I can totally and completely safely say that altohu it sets up the drivers for the network card ok and always has done that for the longest time it has failed completely to enable the network correctly and so left it in a state of WTF i then end up having to set things up manually and reboot to get networking working correctly .
When doing an install it gets to the checking for updates part then just fails saying network unreachable till i sort it by hand . This has been so since 10.0 for certain and maybe prior to that but that is going back tooooo far to remember now , As it happens it is not a problem for me i know it is going to happen and can fix it easily but for people that are not as comfortable with Linux / Yast it could be a real PITA Pete .
Peter Nikolic wrote:
On Saturday 22 Aug 2009 11:18:41 Per Jessen wrote:
Peter, are you seriously suggesting that YaST network setup has not been working since 10.0 ?? I can't exactly confirm that - the only network config problem I have had is when I do an installation over ssh+nfs and then change the network address during stage2. Mea culpa really.
/Per
I can totally and completely safely say that altohu it sets up the drivers for the network card ok and always has done that for the longest time it has failed completely to enable the network correctly and so left it in a state of WTF i then end up having to set things up manually and reboot to get networking working correctly.
Bugreport#, please. Do you have anything special or unusual in your network?
When doing an install it gets to the checking for updates part then just fails saying network unreachable till i sort it by hand . This has been so since 10.0 for certain and maybe prior to that but that is going back tooooo far to remember now. As it happens it is not a problem for me i know it is going to happen and can fix it easily but for people that are not as comfortable with Linux / Yast it could be a real PITA
I don't do any checking for updates, but for me, YaST has configured the network just fine since at least 8.x. With DHCP, DNS etc. /Per -- Per Jessen, Zürich (15.6°C) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sunday 23 Aug 2009 13:42:23 Per Jessen wrote:
Peter Nikolic wrote:
On Saturday 22 Aug 2009 11:18:41 Per Jessen wrote:
Peter, are you seriously suggesting that YaST network setup has not been working since 10.0 ?? I can't exactly confirm that - the only network config problem I have had is when I do an installation over ssh+nfs and then change the network address during stage2. Mea culpa really.
/Per
I can totally and completely safely say that altohu it sets up the drivers for the network card ok and always has done that for the longest time it has failed completely to enable the network correctly and so left it in a state of WTF i then end up having to set things up manually and reboot to get networking working correctly.
Bugreport#, please. Do you have anything special or unusual in your network?
Not even sure what to put in a bug report on this one althou it has plaged me for some time i have never found anything in the logs to base a report on other than how it actually appears here Not that i am aware of i use suse 10.0 as a firewall / router on a dedicated PC that connects via WiFi to my connection , I then use a local nameserver on the machine with an IP of 192.168.3.1 , All internal IP's are 192.168.3.xx the external is 192.168.0.103 (i piggy back on a friends connection with permission saves me the need for a landline and the associated charges) i use an internal Nameserver as i find it better than using the one on his router If i connect a windBloWs machine to the network it finds everything straight away (which is somewhat Ercksome) so it obviousley works .
I don't do any checking for updates, but for me, YaST has configured the network just fine since at least 8.x. With DHCP, DNS etc.
/Per
Humm well i get asked to check for updates during the later stages of the install seems there may be a modicum of inconsistancy in the install procedure maybe depending on the choices made at various stages hope to get a new HDDfor this box next week so i will try a MS6 install from new see what happens then as i say it was the same on MS5 so .. your guess is a good as mine on this one right now . Pete .
Peter Nikolic wrote:
Not even sure what to put in a bug report on this one althou it has plaged me for some time i have never found anything in the logs to base a report on other than how it actually appears here
You could always swap out into a console and check your network config. Interface definition, routing, name-server etc. Just use Crlt-Alt-F1. I have my doubts about YaST being to blame here, but if you want to pursue the issue, I think your network config at the time of failure is the first thing to look at.
Not that i am aware of i use suse 10.0 as a firewall / router on a dedicated PC that connects via WiFi to my connection , I then use a local nameserver on the machine with an IP of 192.168.3.1. All internal IP's are 192.168.3.xx the external is 192.168.0.103 (i piggy back on a friends connection with permission saves me the need for a landline and the associated charges) i use an internal Nameserver as i find it better than using the one on his router
Doesn't sound particularly unusual, no. /Per -- Per Jessen, Zürich (15.6°C) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Monday 24 Aug 2009 11:59:02 Per Jessen wrote:
Peter Nikolic wrote:
Not even sure what to put in a bug report on this one althou it has plaged me for some time i have never found anything in the logs to base a report on other than how it actually appears here
You could always swap out into a console and check your network config. Interface definition, routing, name-server etc. Just use Crlt-Alt-F1. I have my doubts about YaST being to blame here, but if you want to pursue the issue, I think your network config at the time of failure is the first thing to look at.
Not that i am aware of i use suse 10.0 as a firewall / router on a dedicated PC that connects via WiFi to my connection , I then use a local nameserver on the machine with an IP of 192.168.3.1. All internal IP's are 192.168.3.xx the external is 192.168.0.103 (i piggy back on a friends connection with permission saves me the need for a landline and the associated charges) i use an internal Nameserver as i find it better than using the one on his router
Doesn't sound particularly unusual, no.
/Per HI .
I meant to add that when it auto configures the network it always seems to get the IP address of the router at my friends house which does not work thru my firewall router . One of these days i will get round to finding the spanner in the works Pete .
Stephan Kulow wrote:
Am Samstag 15 August 2009 schrieb Per Jessen:
3. license was first displayed in German.
I saw it now too - the problem seems to be that there is no match for "en_US" license, so he picks the first the tar and that happens to be .de
Did you file a bug?
Just did now - https://bugzilla.novell.com/show_bug.cgi?id=533026 -- Per Jessen, Zürich (26.1°C) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (4)
-
Graham Anderson -
Per Jessen -
Peter Nikolic -
Stephan Kulow