Since Beta has been delayed...

I was holding off of installing M5 until Beta was released. However since Beta has been delayed, I was going to

  1. install M5
  2. bring it up to M5++ standards per this post
    Experiences with 12.1 MS5 ++

Two questions

  1. should I bring things up to M5++ standards? Any others out there with experience with “++”?
  2. how does one enable systemd by default in M5++?

cheers

On 22.09.2011 17:26, gavinto wrote:
>
> I was holding off of installing M5 until Beta was released. However
> since Beta has been delayed, I was going to
> 1) install M5
> 2) bring it up to M5++ standards per this post
> ‘Experiences with 12.1 MS5 ++’ (http://tinyurl.com/3r2lg3j)
>
> Two questions
> 1) should I bring things up to M5++ standards? Any others out there
> with experience with “++”?

Why not?

> 2) how does one enable systemd by default in M5++?

Systemd is enabled by default.

And it works quite nicely already.
It’s improved a lot lately.

Vahis

http://waxborg.servepics.com
openSUSE 11.2 (x86_64) 2.6.31.14-0.8-default “Evergreen” main host
openSUSE 12.1 Milestone 5 (x86_64) 3.1.0-rc6-2-desktop in VBox
openSUSE 11.4 (i586) 3.0.4-43-desktop “Tumbleweed” in EeePC 900

> 2) how does one enable systemd by default in M5++?

Systemd is enabled by default.

And it works quite nicely already.
It’s improved a lot lately.

Thanks for the quick response. For some reason I was under the impression that systemd wasn’t default in M5.

On 22.09.2011 18:46, gavinto wrote:
>
>>
>>> 2) how does one enable systemd by default in M5++?
>>
>> Systemd is enabled by default.
>>
>> And it works quite nicely already.
>> It’s improved a lot lately.
>
>
> Thanks for the quick response. For some reason I was under the
> impression that systemd wasn’t default in M5.
>
>

Systemd became default rcently. Not sure if it was exactly M5 or after
some update. But it’s been that for some time now.

The system can also boot via systemv as a boot option.

Vahis

http://waxborg.servepics.com
openSUSE 11.2 (x86_64) 2.6.31.14-0.8-default “Evergreen” main host
openSUSE 12.1 Milestone 5 (x86_64) 3.1.0-rc6-2-desktop in VBox
openSUSE 11.4 (i586) 3.0.4-43-desktop “Tumbleweed” in EeePC 900

On 09/22/2011 11:20 AM, Vahis wrote:
>
> Systemd became default rcently. Not sure if it was exactly M5 or after some
> update. But it’s been that for some time now.
>
> The system can also boot via systemv as a boot option.

Having systemd as default depended on what iso was used to install. The DVDs
were last, but a ‘zypper up’ with the factory repos enabled will get you systemd
as a default. The F5 options in the GRUB screen let you choose which one to use.

After an upgrade, the only problem I had was with the sound as only the dummy
output device was enabled. It turned out to be a permissions problem. The real
problem may already be solved, but an easy work around is to add your users to
the audio group.

By default the M5 system is set to SysV at your Grub boot at start up.
To enable systemd, press the " F5 " key and select Systemd.

You still have to add " init=/bin/systemd " (without the quotations) to the options line.
I set it permanently via Yast → System → Yast boot loader

Milestone 6 will have systemd set up by default.

Ah, so that confirms my recollection.
So…does what is in factory now have systemd as default? (i.e. if I do a zypper dup using Factory repos, what happens)

On 09/22/2011 02:16 PM, gavinto wrote:
>
> Ah, so that confirms my recollection.
> So…does what is in factory now have systemd as default? (i.e. if I do
> a zypper dup using Factory repos, what happens)

You will get systemd by default. The initial GRUB screen will have an F5 option
that defaults to systemd, but it will let you choose System V or just plain
init. The last one can be used as a rescue login.

After two 12.1 attempts, including MS5, that left me with the same decision (wait for the beta), I decided to give 12.1MS5++ a go. After 1300 updates, 72 new packages, 5 removes and 2 arch changes, I was surprised at the results. Although a bit rough-edged, even for a milestone, the operating result was superb! (My optimism for 12.1 is now re-kindled!).

Problems (In order of observation, not importance)

  1. The background of the login screen was black. (While this is primarily cosmetic, my ongoing experiences with Intel “black screens” remain negative to black backgrounds).

  2. The login panel was unusually large (and black)

  3. (Most significant) On first boot, performance was poor (read: bad!), and became progressively worse. The culprit was tracker, which is always a bit of a drag post-boot, but was using 3.0 GB (yes, 3 gigs) and growing, and swap was not used. After some time, killing tracker freed the memory, and returned to normal ops. Subsequent boots have manifested much shorter lags.

I suspect the initial tracker activity might have been due to including my full 11,4 openSUSE, a Ubuntu install and a Mint platform in fstab.

  1. I reverted the desktop to “fallback mode”. I still prefer Gnome as in Gnome 2, though I was pleasantly surprised that fallback mode was quicker than the “new, improved” version.

  2. I customized the default desktop (via gnome-tweak-tool) to a more comfortable view. It turned out to be more than aesthetic: the customized desktop (clearlooks, Raleigh, etc) is absolutetly smooth without delays. (As to why, I have no idea, so I backed off everything I changed, and the slow erratic behavior returned).

So far, it is a keeper for my test platform. Kernel 3.1rc6 is already installed (the same I run on three openSUSE platforms. Next test is to upgrade Xorg, primarily for the Intel Arrandale/Ironlake (Intel GMA HD) graphics facility. LibreOffice will be updated to 3.4.2 as well.

Will post further.

:slight_smile:

I think, that this 5 milestone is quit good. Thanks. I have the only problem with nomodeset parameter with booting. I hope, that final version will solve it.

Hi All,

Have complained enough so I must say something good. Finally got an nVidia driver to work – 285.03. Two fixes:

  1. Installed the 12.1 MS5++ (see #1 above)
  2. Booted up in safe mode and used nvidia-config to set things up.
  3. Upon another reboot I was Finally able to get a Desktop without using “nomodeset x11failsafe”.

Thanks,
Chuck
P.S.
Card is nVidia 7300 LE

On 09/22/2011 04:46 PM, petrherynk wrote:
>
> I think, that this 5 milestone is quit good. Thanks. I have the only
> problem with nomodeset parameter with booting. I hope, that final
> version will solve it.

Have you files a bug with the complete logs when if fails? If not, then no
developed even knows about your problem, and it will never be fixed.

On Thu, 22 Sep 2011 22:09:59 +0000, Larry Finger wrote:

> On 09/22/2011 04:46 PM, petrherynk wrote:
>>
>> I think, that this 5 milestone is quit good. Thanks. I have the only
>> problem with nomodeset parameter with booting. I hope, that final
>> version will solve it.
>
> Have you files a bug with the complete logs when if fails? If not, then
> no developed even knows about your problem, and it will never be fixed.

I reported this problem with nVidia and Radeon chips a while ago.
https://bugzilla.novell.com/show_bug.cgi?id=716648


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