Post comments and experience reports in this thread.
The network is messed up.
My first install was on my desktop, and that went reasonably well.
My second install was on an older laptop that I use for testing 32 bit installs.
The network tests failed.
The network did not start after reboot.
The logs showed “dhcpcd” errors. But “dhcpcd” is supposed to only be used with “ifup” mode, and the Yast configuration showed that the network was supposed to be in NetworkManager mode.
NetworkManager was never run, as best I can tell.
It looks as if the system runs in “ifup” mode, no matter how it is configured.
I eventually had to go to Yast network settings, change to “ifup” mode, disable ethernet, code in the WiFi parameters to be able to use the network. Presumably, connecting an ethernet cable would have worked, too. Without disabling ethernet, it was routing Internet connections through the ethernet interface (which was not connected), instead of through the wireless interface.
I’ll post a bug report tomorrow. It’s getting too late now.
Install from the Gnome Live CD was almost flawless.
Only issue I noticed during setup, (this was with a active wireless connection). The screen ‘Clock and Time Zone’ where you see the world map.
It correctly identified me in UK
But the Red dot marker was by Hudson Bay Canada.
GRUB2 Radeon graphics disasters persist
(https://bugzilla.novell.com/show_bug.cgi?id=803026)
This was not much of a problem when only GRUB2 was hit but now it
affects the whole session.
–
Graham P Davis, Bracknell, Berks.
openSUSE 12.3-RC2 (64-bit); KDE 4.10.00; AMD Phenom II X2 550 Processor;
Video: nVidia GeForce 210 (using nouveau driver);
Sound: ATI SBx00 Azalia (Intel HDA); Wireless: BCM4306
notice the same here no network manager and ifup doesn’t seem to connect to anything
Folks
It’s helpful if you state what media version (DVD Live CD) and if using CD is it (gnome or kde)
If DVD what desktop you loaded and is it the latest revision of the DVD?
On Fri, 01 Mar 2013 13:06:01 GMT
kc1di-qrp <kc1di-qrp@no-mx.forums.opensuse.org> wrote:
>
> nrickert;2530964 Wrote:
> > The network is messed up.
> >
> > My first install was on my desktop, and that went reasonably well.
> >
> > My second install was on an older laptop that I use for testing 32
> > bit installs.
> >
> > The network tests failed.
> > The network did not start after reboot.
> >
> > The logs showed “dhcpcd” errors. But “dhcpcd” is supposed to only
> > be used with “ifup” mode, and the Yast configuration showed that the
> > network was supposed to be in NetworkManager mode.
> >
> > NetworkManager was never run, as best I can tell.
> >
> > It looks as if the system runs in “ifup” mode, no matter how it is
> > configured.
> >
> > I eventually had to go to Yast network settings, change to “ifup”
> > mode, disable ethernet, code in the WiFi parameters to be able to
> > use the network. Presumably, connecting an ethernet cable would
> > have worked, too. Without disabling ethernet, it was routing
> > Internet connections through the ethernet interface (which was not
> > connected), instead of through the wireless interface.
> >
> > I’ll post a bug report tomorrow. It’s getting too late now.
>
> notice the same here no network manager and ifup doesn’t seem to
> connect to anything
>
>
Ditto. What’s really annoying me is that I recall finding a way to get
Network Manager started in RC1 but now I can’t remember what it was.
Also, Network Management -launched from the icon in the Systray - isn’t
a lot of help; just says "Network Manager isn’t running. Please start
it! How??? Same nonsense in Yast; says to check whether knetworkmanager
is running and to start it if it isn’t. Again: HOW! As I heard someone
say years ago about some software, “about as user-friendly as a cornered
rat!”
–
Graham P Davis, Bracknell, Berks.
openSUSE 12.3-RC2 (64-bit); KDE 4.10.00; AMD Phenom II X2 550 Processor;
Video: nVidia GeForce 210 (using nouveau driver);
Sound: ATI SBx00 Azalia (Intel HDA); Wireless: BCM4306
I installed using the 32 bit DVD image. I did not use “automatic configuration” though that is probably not related.
The DVD image was used from a USB. The iso was “openSUSE-12.3-DVD-Build0095-i586.iso”
I’m using KDE, but that seems unrelated to the problem.
Bug report submitted:
Bug 806993 System is configured for NetworkManager, but behaves as “ifup”
More details can be found in the bug report. This is likely a systemd problem. I see it as a show stopper. However, it is possible that it has a very simple fix.
On 03/01/2013 02:06 PM, kc1di-qrp wrote:
> notice the same here no network manager and ifup doesn’t seem to
> connect to anything
Same here.
Plus: xfce can not login as user, only as root. That is solved by an
update, but with no network it was impossible.
Yast said that network manager was enabled, but that was false, there
was no applet in the taskbar. I had to change to ifup traditional
method, and my configuration was there, written up from install time.
But it failed to setup the default route, neither via dhcp or the manual
tab. It wanted to install smpppd, but that failed, no network.
After several trials, I found out that a “rcnetwork restart” worked.
Then yast network setup succeded, installed updates, xfce as user works
again.
Restored .thunderbird directory from backup, and here I am
–
Cheers/Saludos
Carlos E. R. (12.3 Dartmouth test at Minas-Anor)
The problem was listed in most annoying bugs and the update works for me. Though exactly it was impossible without a net connection. Though luckily I had access to ethernet and just setup a normal ifup/dhclient deal. For some reason ifup works for me but the source of the network manager problem evades me. Mine has something to do with the name server.
https://en.opensuse.org/openSUSE:Most_annoying_bugs_12.3_dev
Still more on the network problem.
For the system that I installed using the DVD image, the network functions with “ifup” even if the configuration says “NetworkManager”
I have since installed on another box, using the live KDE image (64bit).
For the system installed using the live image, the network functions with “NetworkManager” even if the configuration says “ifup”.
There’s probably a small simple change to switch between “ifup” and “NetworkManager”, but Yast is not making that change. The change is only being made by the folk who prepare the isos.
I’ll add this observation to the bug report.
KDE4 install to real (not VM) partition from x64 DVD.
Desktop icons do not resize (using Menu>ConfigureDesktop), even after all updates applied, and the big walpaper and icon download. Stuck in giant size (I change desktop resolution for eyesight reason). Tried (from default/install 48 size) to 32 and 22 … no change occurs, even after reboot.
Everything else seems to work, even VLC (from Packman), iScan, Wine, Ktorrent.
Loaded LIVE DISK and it is working great with network easily set up and surfing as I type this. I typed in the password for wifi and it started easily. Icons and all look normal on screen resolution of 1366 x 768 and the desktop video effects work fine as well.
APPER updated files OK as I set up the live system. i am running this LIVE, not installed. The scroll function for the track pad does not seem to work though I have not tried to specifically set it up. OK, it works fine after I set the scroll to right edge setting.
LOOKS GOOD!
LENOVO G570
8 GB RAM, Intel video chip set,
Atheros 9285 chip set for wifi
i3 Intel cpu
On Fri, 01 Mar 2013 15:06:02 GMT
nrickert <nrickert@no-mx.forums.opensuse.org> wrote:
> The DVD image was used from a USB. The iso was
> “openSUSE-12.3-DVD-Build0095-i586.iso”
> I’m using KDE, but that seems unrelated to the problem.
I used the 64-bit DVD (build0094) on a USB, KDE, and had to configure
with ifup.
It has been pointed out that this is referred to in the release notes,
and we always read those from cover to cover, don’t we? Ahem.
############
4. System Upgrade
4.1. systemd: Activating NetworkManager with a network.service Alias Link
By default, you use the YaST Network Settings dialog (yast2 network) to activate NetworkManager. If you want to activate NetworkManager, proceed as follows.
The NETWORKMANAGER sysconfig variable in /etc/sysconfig/network/config to activate NetworkManager has been replaced with a systemd network.service alias link, which will be created with the
systemctl enable NetworkManager.service
command. It causes the creation of a network.service alias link pointing to the NetworkManager.service, and thus deactivates the /etc/init.d/network script. The command
systemctl -p Id show network.service
allows to query the currently selected network service.
To enable NetworkManager, use:
First, stop the running service:
systemctl is-active network.service &&
systemctl stop network.service
Enable the NetworkManager service:
systemctl --force enable NetworkManager.service
Start the NetworkManager service (via alias link):
systemctl start network.service
To disable NetworkManager, use:
Stop the running service:
systemctl is-active network.service &&
systemctl stop network.service
Disable the NetworkManager service:
systemctl disable NetworkManager.service
Start the /etc/init.d/network service:
systemctl start network.service
To query the currently selected service, use:
systemctl -p Id show network.service
It returns “Id=NetworkManager.service” if the NetworkManager service is
enabled, otherwise “Id=network.service” and /etc/init.d/network is
acting as the network service.
#########
Simple!
Am I alone in thinking it a bit ironic that this comes under “system
upgrade?”
–
Graham P Davis, Bracknell, Berks.
openSUSE 12.3-RC2 (64-bit); KDE 4.10.00; AMD Phenom II X2 550 Processor;
Video: nVidia GeForce 210 (using nouveau driver);
Sound: ATI SBx00 Azalia (Intel HDA); Wireless: BCM4306
Hardly.
At least Yast could point us to the release notes, instead of making a change that doesn’t work.
That is a strange place to put it. That would explain why I only skimmed through that, and paid little attention. I was, after all, doing a full install.
This is going to confuse a lot of people. Best would be for Yast to do the magic incantations. Failing that, it should at least refer the user to the release notes and admit that a change via Yast won’t do anything.
In any case, thanks for that post. I’m about to give that a try.
Well, that worked perfectly. Thanks again.
On 03/01/2013 07:26 PM, nightwishfan wrote:
>
> robin_listas;2531085 Wrote:
>> Plus: xfce can not login as user, only as root. That is solved by an
>> update, but with no network it was impossible.
> The problem was listed in most annoying bugs and the update works for
> me. Though exactly it was impossible without a net connection. Though
> luckily I had access to ethernet and just setup a normal ifup/dhclient
> deal. For some reason ifup works for me but the source of the network
> manager problem evades me. Mine has something to do with the name
> server.
>
> https://en.opensuse.org/openSUSE:Most_annoying_bugs_12.3_dev
Network not starting on installation will be a nightmare for us here.
From the little I read there and some bugzillas, they have abandoned
hope till 13.1
–
Cheers/Saludos
Carlos E. R. (12.3 Dartmouth test at Minas-Anor
On 03/01/2013 10:16 PM, nrickert wrote:
>
> Cloddy;2531131 Wrote:
>> Simple!
> Hardly.
Indeed.
YaST should work, period.
> At least Yast could point us to the release notes, instead of making a
> change that doesn’t work.
which you can not read with no network…
–
Cheers/Saludos
Carlos E. R. (12.3 Dartmouth test at Minas-Anor
This NetworkManager issue is a most unwelcome change in RC2. I did fresh default KDE installs of the 32-bit DVD iso for 12.3 beta1, beta2, RC1, and RC2 on a ThinkPad X-41 using a wired ethernet connection. In the first three cases, networking functioned correctly both during installation and afterwards. During installation, the network connection test succeeded, and the on-line update worked. After installation, NetworkManager was in the tray, and easily set up secure wireless connection to a hidden access point.
During the RC2 installation, the network connection test failed, but the subsequent on-line update worked (?!?) After installation finished, NetworkManager had all the troubles others have described. ifup did get a wired connection working. I used the procedure in post #14 above to activate NetworkManager. That was not needed in beta1, beta2, or RC1.
What changed between RC1 and RC2 to make such a mess?
Regards,
Howard
With RC1, the network defaulted to using NetworkManager, whether installed from DVD or live.
With RC2, the network defaults to “ifup” if installed from the DVD.
Defaulting to NetworkManager is the safer default.