I downloaded the beta, and did a UEFI install. Both went well.
The only problem was that the system would not boot. This is due to bug 939411, which still has not been fixed. It is a problem if you installed to an encrypted LVM and have USB3 hardware. A needed USB3 driver is not in the “initrd” (that’s the bug).
It’s easy enough to work around, and the system is now running well.
The artwork for 42.1 is excellent (in my opinion). It is a big improvement over 13.2 artwork.
SDDM now has an entry to login to Gnome-wayland. Unfortunately, it doesn’t work. Login to standard Gnome (without wayland) also does not work from the SDDM menu. So I will probably switch to “lightdm” as I did with the earlier milestones. Thus far Plasma 5 seems to be doing fine, though my testing has been limited.
Install: fine, incl. import of users and mountpoints from previous install,
First impression: Boots quick, Plasma5 looks OK, the artwork is (IMHO) one of the best we have had.
Issue found: dual graphics on Plasma5 detected as dual screen. Side effect: started applications launch on an invisible desktop. Workaround: Configure Desktop, it will disappear on the right side of the screen, maximize through right clicking the taskmanager, move mouse out of screen, click whilst pressing Alt, move window is sight, use Display and Monitor to disable the secondary screen. I thought I’d seen this as a bug that was fixed upstream already.
Hi
Swapped repos (well repo just have oss active) to the Beta1, did a
zypper dup and all is good in the land of GNOME so far… Just needs
more package submissions… (I only have one sofar…)
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 | GNOME 3.10.1 | 3.12.44-52.18-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
Gnucash, missing from M2, is now available but one of its requirements,
Perl-Date-Manip, is missing. So near and yet . . .
Something went wrong with the Boot Loader Location. The installer just
gave Root Partition as usual on this machine and I added MBR. What I
got instead was installation on Root and an external Drive. I
remembered that this also happened on M2 but I then put it down to some
sort of finger trouble on my part. It now looks like it’s not me but
something fishy with the disk order.
Had the usual graphics trouble and freeze-up so had another hack at
installing nVidia “the hard way”. The instructions only being valid for
openSUSE versions up to 12.2 made it “the really hard way” as far as I
was concerned but after trial and error - mostly error - I succeeded
and, so far, it seems that the problem has gone away. Still a puzzle to
me why nouveau and Plasma5 don’t work together but Gnome and the
same nouveau seems to be a marriage made in heaven.
–
Graham P Davis, Bracknell, Berks.
openSUSE 13.2 (64-bit); KDE 4.14.9; AMD Phenom II X2 550 Processor;
Kernel: 4.2.0; Video: nVidia GeForce 210 (using nouveau driver);
Sound: ATI SBx00 Azalia (Intel HDA)
I did the same this evening, i.e. edited the repo and “zypper dup” from M2 with Plasma 5 up to Beta1. About 2000 changes installed, so I guess I had picked the right one.
During the package installations, the desktop and Touchpad broke but Konsole continued to the finish while surrounded by black screen. The ThinkPad’s Trackpoint and buttons carried on working though, and the reboot made it ok.
One issue, the cursor keys here now navigate the Grub screen ever so slowly with each press receiving a delayed response. New “artwork”?
At first glance Plasma 5 looked the same as on M2 (not necessarily a bad outcome), although Phonon’s speaker test now works. Hmm, still a step down from Tumbleweed’s version. Maybe further testing at the weekend might reveal some hidden gems…
Hi
I always logout and go to a tty (or run screen first). I don’t worry about grub (hidden and set to 0 delay) or plymouth (removed and blacklisted). I either use the HP’s F9 or efibootmgr -n option
You should never ever select MBR when you have multiple disks. MBR means - “MBR of the first disk” and installer may have different idea what disk is the first than you. Nor should you ever select multiple bootloader locations. The best is to explicitly select device after verifying that it is the disk you actually want.
FYI, not 100% sure, but in M2 when I selected “Install bootloader to / partition” and unchecked “Install bootloader to MBR”, the installer warned of “no place selected for stage 1 boot code” or sort of.
I’ll double-check with Beta install next weekend.
>
> Cloddy;2729599 Wrote:
> > Gnucash, missing from M2, is now available but one of its
> > requirements, Perl-Date-Manip, is missing. So near and yet . . .
> >
> Hi
> It’s currently in a ‘Blocked’ state waiting for perl-Test-Inter to
> build in the development project…
>
Thanks for the info, Malcolm.
–
Graham P Davis, Bracknell, Berks.
openSUSE 13.2 (64-bit); KDE 4.14.9; AMD Phenom II X2 550 Processor;
Kernel: 4.2.0; Video: nVidia GeForce 210 (using nouveau driver);
Sound: ATI SBx00 Azalia (Intel HDA)
>
> Cloddy;2729599 Wrote:
> >
> > Something went wrong with the Boot Loader Location. The installer
> > just gave Root Partition as usual on this machine and I added MBR.
> > What I got instead was installation on Root and an external Drive.
>
> You should never ever select MBR when you have multiple disks. MBR
> means
> - “MBR of the first disk” and installer may have different idea what
> disk is the first than you. Nor should you ever select multiple
> bootloader locations. The best is to explicitly select device after
> verifying that it is the disk you actually want.
>
I started using MBR years ago when I had trouble getting GRUB to
recognise that I had three or four bootable OS’s on the one machine; it
was the only way I found to get GRUB to do what I wanted and it’s just
become a habit - a bad one it seems.
–
Graham P Davis, Bracknell, Berks.
openSUSE 13.2 (64-bit); KDE 4.14.9; AMD Phenom II X2 550 Processor;
Kernel: 4.2.0; Video: nVidia GeForce 210 (using nouveau driver);
Sound: ATI SBx00 Azalia (Intel HDA)
For me an upgrade from MS2 to the beta rendered the YaST GUI useless. The YaST GUI itself opens, but any ‘applet’ in there does not. There is a black spinning cursor for 1-2 seconds and that is all what happens. It does not matterif I login with a IceVM, an XFCE or a Plasma 5 desktop. MS2 did not have this problem.
(running as a VM in Virtualbox 5.04 on Win7 if this matters)
The Yast bootloader page for grub2 has a place where you can set the disk order. I use that if installing to an external drive (making the external drive first in disk order). Recent experience, when installing to an external drive, is that the installer defaults to making that external drive the first in disk order.