I’m starting this thread for openSUSE-13.1 release candidate-2, which was released today. There is an announcement of the release here: openSUSE News and per that, one can download 13.1 RC2 for testing here: software.opensuse.org: Download openSUSE 13.1 RC2
Per the release announcement for openSUSE-13.1 RC2 the changes in this update are not very big or ground shaking. This is a sign of openSUSE 13.1 maturing quickly, and SuSE-GmbH and the openSUSE community contributors are focused on bug fixing.
Testing
openSUSE 13.1 will have to stand up right in a proud tradition of great stability so it will need a final serious workout before we release it upon the world! We wrote about testing a while ago, and we urge you to check out that article and help out!
We ask you to give some extra attention to:
btrfs
! > - livecd’s and usb live sticks
– these did not work in RC1, which was in part because this is hard to test automatically. We have some tests set up but manual testing is really needed to ensure the live images work well. > - Secure Boot/UEFI
. If you have a machine with Secure Boot and UEFI and 12.3 didn’t work for you, please, test this 13.1 RC2. With this RC2 we added a fix related with the alignment of certificates that can cause fails on some UEFI firmware. >
Problems which appear to be bugs should be reported here on bugzilla: Bugzilla Main Page You can use your openSUSE forum user name and password when logging on to bugzilla. There is guidance on raising bug reports on openSUSE here: openSUSE:Submitting bug reports - openSUSE
I downloaded the live gnome.iso and used SuSE studio to copy to a usb disk
I booted using secure boot enabled and my live Gnome usb stick booted to the gnome shell without any problem. Yea!!
the gui yast software manager dies. the terminal yast software manager works. bluetooth works is why I am tinking of moving from the kde desktop to te gnome desktop
I read on the openSUSE mailing list Bluetooth will not work with KDE on the final release and only after the fact install might bluetooth get fixed in KDE. That means it will be broken in all KDE ISO images of openSUSE 13.1. I am downloading the KDE RC2 LiveDVD image right now.
So I am up and running openSUSE 13.1 RC2 Live KDE. Same network problem as RC1, but being wiser, I am up faster. Art work still the same as openSUSE 12.3 I see and the Live setup provides little disk space to do anything real on my laptop. But a setup that starts is always good.
On 10/31/2013 02:26 PM, Oscar2007 wrote:
>
> Question: RC1 plus more last weekly updates(via yast,zypper) =RC2?
> Because today no update available when running zypper up.
Hmm… I’m ver’y confused. RC1 worked a-ok. I downloaded : openSUSE-13.1-KDE-Live-Build0084-x86_64.iso. I was surprised when I booting up live. 281 updates? I gone further and installed on my HP 6730B laptop HD. After 22 minuters I gave up. No network. Maybe I have a bad day. Writing this on my main Desktop whit 13.1 RC1.
Can anyone explain this mess whit new network devices ( ex enps3so, enso5 ) that have to be seen into and reboot? Not a winner for new users.
So, my situation now about RC2 (obtained by zypper up to RC1):
Missing more community important repos for 13.1 (libdvdc, packman, nvidia, webcam drivers, LibreOffice)
Because pt. 1, for my missing 4 libraries need for vlc updates (for packman factory repo) and missing pdftk-qgui (from packman factory repository)
VERY BAD: My webcam NOT see (webcam driver missing?, nvidia driver missing?, kernel broken?)
Not make a call in KDE Telepathy (Not capable account found. …you have configured support …audio/video…etc.)
Missing tcpmdump and sopcast (need to TV-Maxe for good working)
ifup are default, so booting are slow (choice Networkmanager)
Bluegriffon closed when try to selected with mouse any menu (bug!)
Warning error on boot:
Thursday, October 31, 2013 07:17:29 PM ACPI Warning 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \PMIO 1 (20130517/utaddress-251)
Thursday, October 31, 2013 07:17:29 PM ACPI Warning 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIO 2 (20130517/utaddress-251)
Thursday, October 31, 2013 07:17:29 PM ACPI Warning 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPR2 1 (20130517/utaddress-251)
Thursday, October 31, 2013 07:17:29 PM ACPI Warning 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \GPIO 2 (20130517/utaddress-251)
Thursday, October 31, 2013 07:17:29 PM ACPI Warning 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \GPR2 1 (20130517/utaddress-251)
Thursday, October 31, 2013 07:17:29 PM ACPI Warning 0x0000000000000540-0x000000000000054f SystemIO conflicts with Region \GPIO 2 (20130517/utaddress-251)
Thursday, October 31, 2013 07:17:29 PM ACPI Warning 0x0000000000000540-0x000000000000054f SystemIO conflicts with Region \GPR2 1 (20130517/utaddress-251)
Thursday, October 31, 2013 07:17:29 PM ACPI Warning 0x000000000000f040-0x000000000000f05f SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20130517/utaddress-251)
Thursday, October 31, 2013 07:17:29 PM WARNING! power/level is deprecated; use power/control instead
Thursday, October 31, 2013 09:51:56 PM 2013-10-31T19:21:04.319522+02:00 mozilla-suse hp-systray: hp-systray[1441]: error: option -s not recognized
So, when the above will be resolved, I have a perfect system.
I know that most of the points listed above do not effectively related basis openSUSE system and I think after the official release will be resolve most. Anyway, most important problems for me from mentioned above are: no webcam, telepahty problem and absence nvidia driver.
The Toshiba is already a dual-boot W8 (preinstalled) and 12.3 (which work somehow with WiFi and 800x600 resolution).
Prior to doing anything with 13.1RC2 I enabled the LAN adapter and made sure SecureBoot (and UEFI, of course) was enabled. Trying to boot my Toshiba with the LAN adapter enabled under 12.3 would make 12.3 lock up when loading the kernel.
The plan is to do a fresh install of 13.1 when it is released - thus permanently deleting any 12.3 and corresponding data and /home volume. However, I though it would be interesting to see how upgrading 12.3 will work out.
Upgrading the existing 12.3 that is installed in a dual-boot fashion with W8:
Booting off the DVD worked straigh off the bat! Beautiful! Also, I have full resolution on my internal screen (1920x1080) - which demonstrates that Intel HD Graphics 4600 is properly supported.
The installation/upgrade itself seems to execute according to rules and plans.
**Then the system reboots in order to complete configuration:
UNREADABLE FONTS. I am unable to get the autoconfiguration to commence.
**
As I made notes when installing, I can supply detailed info on what I did to get here (including photos of the unreadable screen), but I remember having read about a similar case which - if my memory serves me right - did work out. I’ll try to dig that one up and get back with what was required to remedy this (if I am able to resolve this, that is ;)).
However, it is clear that the modification of the existing Grub-2 menu failed in this case.
On 2013-10-31 20:26, Oscar2007 wrote:
>
> Question: RC1 plus more last weekly updates(via yast,zypper) =RC2?
> Because today no update available when running zypper up.
For factory/beta/RC/tumbleweed, updating means “zypper dup”.
And yes, you get RC2.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
On 2013-10-31 21:06, Oscar2007 wrote:
> Anyway, most important problems for me from mentioned
> above are: no webcam, telepahty problem and absence nvidia driver.
nvidia driver is not be created till after release.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
On 10/31/2013 03:38 PM, Carlos E. R. wrote:
> On 2013-10-31 21:06, Oscar2007 wrote:
>> Anyway, most important problems for me from mentioned
>> above are: no webcam, telepahty problem and absence nvidia driver.
>
> nvidia driver is not be created till after release.
I just enabled the webcam in my custom-built kernel (3.12-rc5) for the first
time, and installed Skype from their web site. The camera is working perfectly
in 13.1-RC2.
Be aware that this is in the most optimistic schedule. At this moment we see
that the basic support to recognize bluetooth adapters is working on one
system, but not on the other.
Please people, it has been written everywhere that Bluetooth in KDE is not yet functional, but somehow are people missing that message…
“till after release.” So what is the meaning to ask users to test on real hardware instead of VM machines asked on opensuses homepage?
Now i’m changing to winter tyres, testing kernel 3.12 -RC…on my workshop PC.and AMD Radeon driver. I can reproduce the result as published on [Phoronix] Linux 3.12 Can Change AMD’s Catalyst Performance](Linux 3.12 Can Change AMD's Catalyst Performance - Phoronix) after get the network functionalling on opensuse. The prop software from AMD is still deliver on my 13.1 installation in concurrence.
I came in after walk with the dogs. After feeding them i was to shutdown my laptop testing 13.1 RC2.
I had a alarm from my server has shutdown. -__What? From 1993 and running OS/2 forward I have always my own servers at home. I haven’t had a problem sins 2004 when i migrated from Novell Netware 5.x to SuSe. >:) Reading the crash logs…
