Another install, same old problem with a twist. Every install I’ve made has
had been real battle. The 20140820 image got all the way through this time.
I did an upgrade install from 13.1 with the DVD. This time, it complained
about not having a network connection but then proceeded to have the alx
driver installed in the kernel by the time it re-booted. I updated via
zypper dup then went to work on the network.
This time, it picked up the fixed ip and default routing settings I set
manually while the instance was running 13.1 but it ignored the SSID I had
set up for the wireless and tried to connect to another SSID that the
neighbor runs. Selecting the one I wanted - which was the strongest signal
shown by the scan - it established a connection. I had to re-enter the pass
phrase but it carried over all the other settings from 13.1.
Then the fun began. For some reason, the routing kept getting messed up.
For a while, the system used the wired connection then it would randomly
switch to using the wireless route. Got to be a real hassle until
disconnected one or the other devices. Never saw that with 12.3/13.1. I’ll
dig more into the routing tables and see if I can spot the tie up. I do NOT
see the problem if I go the wicked route, just using NetworkManager
NetworkManager is about the only real problem I’ve had with 13.2 so far but
this will be a show stopper for laptops which routinely have wired/wireless
devices on board.
same / similar experience after upgrading also, only tried networking with NetworkManager, no change in settings were made after update
if both wired and wireless connections were available at boot time, problems occurred as described
also if either connection was disturbed then the OS froze solid, only recourse was a hard reboot
if only one connection was available at kde boot time, NetworkManager worked as normal
as the user only uses the laptop for wireless internet, the update was deemed acceptable
perhaps there is no interest now in developing NetworkManager further and that wicked is the new deal
just in passing, is there a network gui front end for wicked
on another pc, Networkmanager can be used but only for one session without having to manually reset the network
> same / similar experience after upgrading also, only tried networking
> with NetworkManager, no change in settings were made after update
>
> if both wired and wireless connections were available at boot time,
> problems occurred as described
Sounds familiar. Physical disconnect of either one left the remaining path
working just fine (on boot or after things got confused).
> also if either connection was disturbed then the OS froze solid, only
> recourse was a hard reboot
As above, removing either connection by any means cleared the other
connection. That included pulling the plug or hitting the maanual “off”
switch. Using the NetwirkManager widget to disconnect the device also
worked - once you got its’ attention.
> if only one connection was available at kde boot time, NetworkManager
> worked as normal
>
> as the user only uses the laptop for wireless internet, the update was
> deemed acceptable
I get acceptable switching between input devices by forcing the other to
disconnect (or disabled state). My gripe with this is a function of being a
creature of habit - I ha had one heck of a time specifying manual/fixed ip
addresses under NetworkManager. Maybe just me, but I still can’t figure out
the new dialog boxes. Why do programmers (yeah, including me) insist on
fixing what ain’t broke??
> perhaps there is no interest now in developing NetworkManager further
> and that wicked is the new deal
>
> just in passing, is there a network gui front end for wicked
> on another pc, Networkmanager can be used but only for one session
> without having to manually reset the network
I’ll try to figure that out.
> sorry this is of no help
Even negative results add to knowledge of a problem. Thanks