Post your experience with 12.3 Milestone 1

On Mon, 19 Nov 2012 11:28:10 GMT
Graham P Davis <cloddy@no-mx.forums.opensuse.org> wrote:

> On Sun, 18 Nov 2012 22:16:05 GMT
> Knurpht <Knurpht@no-mx.forums.opensuse.org> wrote:
>
> >
> > It’s very well possible to perform the DVD install from a 8GB USB
> > stick. Run isohybrid on the downloaded DVD iso before writing it to
> > the USB Device.
> >
> >
>
> I installed from USB stick [or pen or thumb or whatever] on both
> machines having copied the image to the drive using Imagewriter.
> Trouble is that the Bios on one machine makes it trickier than
> installing from DVD. Just as a twist, even if the DVD image was the
> correct size, the other machine probably would not boot it correctly
> due to UEFI.
>
>

Figured out how to alter the boot order to fix the DVD install on UEFI
machine. Now to see if I can make a permanent fix so as to avoid
booting umpteen times whilst trying to get BIOS to notice that I’m
hammering the escape key!


Graham P Davis, Bracknell, Berks.
openSUSE 12.2 (64-bit); KDE 4.9.3; AMD Phenom II X2 550 Processor;
Video: nVidia GeForce 210 (using nouveau driver);
Sound: ATI SBx00 Azalia (Intel HDA); Wireless: BCM4306

Installed from 32 bit dvd on hp mini 1101 with no problems. Detected all hardware and only needed to install b43 firmware post-install to get wireless working.

After some problems noted elsewhere, M1 is working fine on my UEFI
system but have hit a snag on this one. No problems with test user but
as soon as I try running my standard user on M1, it freezes. May be
related to Firefox/Flash but have no trouble on 12.2 with same windows
and tabs open. Also no bother with Flash on other machine. No messages
saved as had to resort to reset button.


Graham P Davis, Bracknell, Berks.
openSUSE 12.2 (64-bit); KDE 4.9.3; AMD Phenom II X2 550 Processor;
Video: nVidia GeForce 210 (using nouveau driver);
Sound: ATI SBx00 Azalia (Intel HDA); Wireless: BCM4306

On 11/08/2012 02:26 PM, nrickert wrote:
>
> Milestone 1 was released today (in case you missed the announcement)
>
> Two failed install attempts. Success on the third try. I’ll post
> details in a followup. This opening post is just to start the thread.
>
>
Except for one person, everyone seems to have installed the MS1 on a
non-UEFI system. Have other people tried installing on UEFI systems?

Before the last Christmas, I got such a system (ASUS F1A75-M) with
Windows 7. I tried to dual-boot with openSUSE. The documentation said
something about EFI. “Not UEFI, some fancy name for the usual BIOS”, I
thought. Installation seemingly went fine. But I could not launch
openSUSE. After a few tries, I overwrote Windows with Linux. That went
OK. But subsequent attempt to install additional distros have had mixed
results: sometimes, only the newest one is accessible; other times, only
the original openSUSE could be used. I even tried to install another
instance of openSUSE 12.2, since the audio mysteriously quit working (to
see if a fresh installation could solve the problem).

I have to read up on circumventing UEFI. The Microsoft UEFI barrier is
here.

I found - and also have other users commenting - that the DVD image is too big for a standard DVD. I don’t have a USB stick big enough. It’d probably be helpful if the download page warned that the image is oversized, to save people downloading an image they can’t write.

On 12/07/2012 05:36 AM, helen-au wrote:
> It’d
> probably be helpful if the download page warned that the image is
> oversized, to save people downloading an image they can’t write.

that is a very good suggestion! but i doubt this is the right place to
get it any attention…hmmmmm, i guess the persons who have the
privileges needed to edit that page might occasionally read in the
Wiki Forum, http://tinyurl.com/6ddyarr

but, a likely better place would be one of the mail lists…maybe the
opensuse-wiki or opensuse-project list
http://en.opensuse.org/openSUSE:Communication_channels#Mailing_lists

i must admit i’m not always certain of where the power lies in this
‘community’…but, think of these forums as users-helping-users and
about 99% of the developers elsewhere (mail list and IRC)…


dd

On Fri, 07 Dec 2012 10:14:51 GMT
“dd” <dd@home.dk> wrote:

> On 12/07/2012 05:36 AM, helen-au wrote:
> > It’d
> > probably be helpful if the download page warned that the image is
> > oversized, to save people downloading an image they can’t write.
>
> that is a very good suggestion! but i doubt this is the right place
> to get it any attention…hmmmmm, i guess the persons who have the
> privileges needed to edit that page might occasionally read in the
> Wiki Forum, http://tinyurl.com/6ddyarr
>
> but, a likely better place would be one of the mail lists…maybe the
> opensuse-wiki or opensuse-project list
> http://en.opensuse.org/openSUSE:Communication_channels#Mailing_lists
>
> i must admit i’m not always certain of where the power lies in this
> ‘community’…but, think of these forums as users-helping-users and
> about 99% of the developers elsewhere (mail list and IRC)…
>

It has been raised on the mail list but developers don’t seem too
bothered about it. Also been pointed out that the md5sums etc. don’t
match for the downloads; I raised a bug for that one. Doesn’t
seem to be thought important either. I hope M2 is better.


Graham P Davis, Bracknell, Berks.
openSUSE 12.3-M1 (64-bit); KDE 4.9.3; AMD Phenom II X2 550 Processor;
Video: nVidia GeForce 210 (using nouveau driver);
Sound: ATI SBx00 Azalia (Intel HDA); Wireless: BCM4306

Thanks, that’s useful to know as I was about to raise it. I’m on Project and Marketing but not the other lists (mailbox gets out of control).

I’m somewhat surprised that they don’t consider it an issue, as for many users it’s a real problem and they shouldn’t have hurdles before they even install! I’ll raise this on Marketing too.

Too late to edit previous post.

I checked the bug report and it is being looked at; they’re just not sure where the problem lies - clearly it isn’t being consistent, they’re not sure whether it’s some backend to the burning software or something else. I’ll take a look at my ISO and see if I can get any information, error logs or something useful.

bug here:
https://bugzilla.novell.com/show_bug.cgi?id=780558

I installed milestone 1 on a ThinkPad X41 (32-bit) replacing OpenSuSE 12.2, but keeping the /home partition. The install went well once I learned how to do it with a USB flash drive. Like most of my installs, this one failed to find a network connection during the install procedure, but I think that is a router issue, not OpenSuSE.

I installed HPLIP and ran hp-setup without problem, and can print to a network printer.

I got samba working with the network. I noticed in the Yast System Services (runlevel): Details (expert mode) the window shows near the bottom only a box labeled B. 12.2 shows boxes for run levels 1 through 5. Is this a bug, or an intended change?

In doing all the multi-media installs, there were a lot of dependency issues, mostly involving GLIBC 2.17. Will this get sorted out in the normal development work?

Best regards,
Howard

I think this is related to the move from the older sysv-init to systemd. As I understand it, they want to remove the remaining remnants of the old sysv-init, which is where the run-level concept originates.

On the multimedia - I have not tried that. I usually test milestones in a separate partition, and delay adding/testing the packman multimedia changes until the final release. I’m guessing that the packman repo for factory is oriented to what is currently in factory, rather than to the most recently released snapshot, and even then it probably lags behind a tad.

There is a bug in the way my ThinkPad X-41 resumes from suspend to RAM.

How do you make a report against 12.3 Milestone 1, like those in post #3 of this thread?

When I tried bugzilla, the forms were always for openSUSE 12.2.

Thanks,
Howard

Yes, I seem to remember that happening even though I tried to file for factory.

After posting the bug, I went back to the bug report to add a comment about the opensuse version. And there’s an information panel there where I was able to switch it to 12.3.

I still had to add a comment for the change to take effect.

The link “openSUSE Factory (12.3)” on page openSUSE:Submitting bug reports - openSUSE has been fixed. It now goes to a Bugzilla report that lists “Product openSUSE Factory” and version 12.3 milestone 1.
Howard

Today (13 Dec 2012) there were a gazillion (I think that is the technical term) updates available in Yast Online Update. I accepted them all and installed. The download took maybe an hour on a 1.4 MiB/s max DSL connection. After the download, the install took just under 30 minutes on a ThinkPad X-41: 32-bit 1.6 GB single core processor, 2GB RAM, mechanical hard drive.

After the updates, My Computer (sysinfo:/) identifies the system as openSUSE 12.3 Milestone 2 (i586)

It has a new batch of icons, so things look a bit different. First bug of note: the desktop icons do not start applications. They worked OK in milestone 1. Things start fine from the Kickoff Application Launcher.

Switching the multimedia packages to the Packman repository versions had no dependency issues, unlike milestone 1.

Howard

You did that in the middle of their preparing for M2, which does not seem to be released yet. You probably have a bit of a hybrid between M1 and M2. When M2 is released, you can probably use:


zypper dup

to bring your system fully to M2.

nrickert, thanks for the tip. 12.3 milestone 2 is on the download site today. I did zypper dup and it modified 117 packages, a 147 MB download.

Should this system now be in the same state as if I had downloaded the milestone 2 DVD and done a fresh install?

In general, for testing milestone releases, is it better to update from one release to the next, or to do a fresh install of the entire next release?

Thanks,
Howard

Yes, I noticed. I am downloading right now.

Yes, it should be pretty much the same. The installation log contents will be different, but not much else.

I guess it depends on what you are testing. I want to test how well the installation goes, and for that I need to do a fresh install from the new iso.

You might want to start a milestone 2 thread if you have any comments based on your testing. I probably won’t have time to install until tomorrow.