On Wed, 13 Mar 2013 19:02:42 -0000, Ted Byers wrote:

Are you sure there are no gotchas?

Of course you are right to be careful. I'd never recommend you upgrade so soon on a mission critical machine. So far, the only issue I hit was the dead network post install, but that's easily sorted. Been running it almost a week now. And can't fault it. Boot time is really improved too. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Thu, Mar 14, 2013 at 11:40 AM, Ruediger Meier wrote:

...

So far, the only issue I hit was the dead network post install, but that's easily sorted.

Actually dead network is almost the worst thing which could happen if your machine is a remote one. In my case 9/10 machines are remote ones.

It seemed to sort itself out after I tinkered a bit.... This is what happened on my system with a 12.3 install last night: - Immediately after install, I had no WiFi networking (well supported Atheros chipset WiFi, so I know it's not a driver issue) - Open YaST > Networking - Switched from ifup to NetworkManager - YaST complained that Networking was not started - Opened NetworkManager, and defined my WiFi config - It attempted to connect and kind of did. Very unstable connection that constantly dropped - I rebooted - On restart, I got a popup asking for my WiFi password (even though I entered and saved it in the earlier config step) - WiFi started working normally. I'm not sure what exact combination of steps I did that got it working, but... those steps do need to be done locally. If you're over a remote connection with WiFi, you're not going to have a lot of fun. I didn't seem to have any issues with wired network - this worked OK from install. C. -- openSUSE 12.2 x86_64, KDE 4.10 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

C wrote:

On Thu, Mar 14, 2013 at 11:40 AM, Ruediger Meier wrote:

...

...

So far, the only issue I hit was the dead network post install, but that's easily sorted. Actually dead network is almost the worst thing which could happen if your machine is a remote one. In my case 9/10 machines are remote ones.

It seemed to sort itself out after I tinkered a bit.... This is what happened on my system with a 12.3 install last night:

- Immediately after install, I had no WiFi networking (well supported Atheros chipset WiFi, so I know it's not a driver issue) - Open YaST > Networking - Switched from ifup to NetworkManager - YaST complained that Networking was not started - Opened NetworkManager, and defined my WiFi config - It attempted to connect and kind of did. Very unstable connection that constantly dropped - I rebooted - On restart, I got a popup asking for my WiFi password (even though I entered and saved it in the earlier config step) - WiFi started working normally.

I'm not sure what exact combination of steps I did that got it working, but... those steps do need to be done locally. If you're over a remote connection with WiFi, you're not going to have a lot of fun.

I didn't seem to have any issues with wired network - this worked OK from install.

C.

I have a ThinkPad E520 with a Realtek WiFi chip. Any issues with those? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org