12,1 m3

I did a factory update today from m2 and my system now shows m3. There were about 1,200 updates - although I used kernel rc5 rather than rc6 in view of the reported problems.

Everything seems fine and I haven’t hit any problems. I even added gnome shell (although I am a kde user). I have never really liked gnome (or used it much) in the past but gnome shell looks quite impressive.

So a likely way in to 12.1 M3 “early” would be install from factory-tested iso file (or 12.1 M2 or 11.4), then zypper dup. I doubt if there’s anything that must have kernel 3.0 yet, so even the Kernel:stable (from Index of /repositories/Kernel:/stable/standard) is probably going to do until 3.0 is deemed fixed.

This is a working round, with the Net Build 132 CD go direct to 12.1 M3! The trick is to :

  • Hit F4 Source HTTP option change the repo - “distribution/12.1/repo” to “factory/repo”
  • During install, select “kernel-vanilla” via Software Manager, using the “details” button

The attempt to re-exec the kernel crashed with watchdog interverning,
interesting as my machine had run Kernel:Head rc6 this week under Tumbleweed
without such an issue.

Reboot, after Bios select the Vanilla option in GRUB and continue
with 1st Configuration. After that disable the 12.1 M2 repos and add
the factory ones.

#  cat /etc/issue
Welcome to openSUSE 12.1 "Asparagus" Milestone 3  - Kernel \r (\l).
# uname -a
Linux fir 3.0.0-rc6-2-vanilla #1 SMP Wed Jul 6 22:58:01 UTC 2011
(56e99da) x86_64 x86_64 x86_64 GNU/Linux
# zypper lr
# | Alias                              | Name
  | Enabled | Refresh
--+------------------------------------+----------------------------------+---------+--------
1 | Updates-for-openSUSE-12.1-12.1-0   | Updates for openSUSE 12.1
12.1-0 | No      | Yes
2 | openSUSE-12.1-12.1-0               | openSUSE-12.1-12.1-0
  | No      | Yes
3 | openSUSE-12.1-NonOSS-Add-on_12.1-0 | Factory non OSS
  | Yes     | Yes
4 | repo-debug                         | openSUSE-12.1-Debug
  | No      | Yes
5 | repo-debug-update                  | openSUSE-12.1-Update-Debug
  | No      | Yes
6 | repo-non-oss                       | openSUSE-12.1-Non-Oss
  | No      | Yes
7 | repo-oss                           | Factory OSS
  | Yes     | Yes
8 | repo-source                        | openSUSE-12.1-Source
  | No      | Yes

# zypper up
Loading repository data...
Reading installed packages...

Nothing to do.

A net efficient install (for once)!!! :slight_smile:
Now can install a working oS kernel from the repos at Index of /repositories/Kernel:

Using kde-4.7rc with an enabled unstable repo :
Index of /repositories/KDE:/Unstable:/SC/openSUSE_Factory
breaks my login, some issue with kdm-greeter in the moment …

robopensuse wrote:

>
> So a likely way in to 12.1 M3 “early” would be install from
> factory-tested iso file (or 12.1 M2 or 11.4), then zypper dup. I doubt
> if there’s anything that must have kernel 3.0 yet, so even the
> Kernel:stable (from ‘Index of /repositories/Kernel:/stable/standard’
> (http://download.opensuse.org/repositories/Kernel:/stable/standard/)) is
> probably going to do until 3.0 is deemed fixed.
>
I updated today 9from 12.1 ms2 to ms3) and system now shows 12.1 ms3. This
solved part of my switch to root problems. sudo and su - now work. kdesu
still does not work. From command line:

Code

@linux-nc4k:~> kdesu dolphin
It asks for password,
I type it in and press Enter.
It comes right back to my command line:
@linux-nc4k:~>]
/Code

Also set up kmail in Kontact. It appears to work. but contacts does not show
Knode shows as separate folders instead of being under a main folder called
usenet.
Has any one else seen this. Will check bugzilla.

Also install Nvidia driver the hard way after I followed the procedure I
found on the form. Onlt thing I noticed in the write is the say to Blacklist
Nouveau in nvidia.conf (it already was), but there is also a 50-nvidia.conf
file there. Nouveau was not in it. When I look at what I was running
MyComputer showed nv.

Here’s what it shows now:
OS: Linux 3.0.0-rc6-2-desktop x86_64
Current user: xxxxxxxx@linux-nc4k
System: openSUSE 12.1 Milestone 3 (x86_64)
KDE: 4.6.5 (4.6.5)

Display Info:
Vendor: nVidia Corporation
Model: GeForce 8400 GS (0x0404)
2D driver: nvidia
3D driver: NVIDIA 275.19

Only other thing I had to do was change the permissions on
the Nvidia X-Server Icon to get it to work. It shows correct driver, and
monitor and resolution.

this message is being sent fro 12.1 MS3


Russ
openSUSE 12.1 MS3(3.0.0-rc6-2-desktop)|KDE Platform Version 4.6.5 (4.6.5)|
Intel core2duo 2.5 MHZ,|8GB DDR3|GeForce 8400GS (NVIDIA-Linuxnvidia-xconfig-
x86_64-270.41.06)

No, not a greeter issue, but something creating the new user directory structure. Kde-4.7 run fine now after some trying …

The kernel retention feature documented in openSUSE Lizards - Improved Kernel Package Retention in 12.1 is working nice for me.

So I think enabling retention of latest & running kernel on kernel updates makes sense by default, so created a feature request - FATE#312647 - Preserve Running Kernel On Kernel Update by Default

upscope wrote:

> robopensuse wrote:
>
>>
>> So a likely way in to 12.1 M3 “early” would be install from
>> factory-tested iso file (or 12.1 M2 or 11.4), then zypper dup. I doubt
>> if there’s anything that must have kernel 3.0 yet, so even the
>> Kernel:stable (from ‘Index of /repositories/Kernel:/stable/standard’
>> (http://download.opensuse.org/repositories/Kernel:/stable/standard/))
>> is probably going to do until 3.0 is deemed fixed.
>>
> I updated today 9from 12.1 ms2 to ms3) and system now shows 12.1 ms3.
> This solved part of my switch to root problems. sudo and su - now work.
> kdesu still does not work. From command line:
>
> Code
> -----------
> @linux-nc4k:~> kdesu dolphin
> It asks for password,
> I type it in and press Enter.
> It comes right back to my command line:
> @linux-nc4k:~>]
> /Code
> ---------
>
> Also set up kmail in Kontact. It appears to work. but contacts does not
> show Knode shows as separate folders instead of being under a main
> folder called usenet.
> Has any one else seen this. Will check bugzilla.
>
> Also install Nvidia driver the hard way after I followed the procedure I
> found on the form. Onlt thing I noticed in the write is the say to
> Blacklist Nouveau in nvidia.conf (it already was), but there is also a
> 50-nvidia.conf file there. Nouveau was not in it. When I look at what I
> was running MyComputer showed nv.
>
> Here’s what it shows now:
> OS: Linux 3.0.0-rc6-2-desktop x86_64
> Current user: xxxxxxxx@linux-nc4k
> System: openSUSE 12.1 Milestone 3 (x86_64)
> KDE: 4.6.5 (4.6.5)
>
> Display Info:
> Vendor: nVidia Corporation
> Model: GeForce 8400 GS (0x0404)
> 2D driver: nvidia
> 3D driver: NVIDIA 275.19
>
> Only other thing I had to do was change the permissions on
> the Nvidia X-Server Icon to get it to work. It shows correct driver, and
> monitor and resolution.
>
> this message is being sent fro 12.1 MS3
>
Kontact issue solved: The bar for the summary column icons was pulled all
the way to the left side. It apparently installed like this or I moved it
and did not know it.

Russ
openSUSE 12.1 MS3(3.0.0-rc6-2-desktop)|KDE Platform Version 4.6.5 (4.6.5)|
Intel core2duo 2.5 MHZ,|8GB DDR3|GeForce 8400GS (NVIDIA-Linux-
x86_64-275-19)

Currently I have the only repo which is “factory-tested”. Just did a “zypper dup” and I had to remove a bunch of libreoffice packages to meet dependencies.

Finally, I did a zypper up > “Nothing to report”.


uname -r

I got:


3.0.0-rc5-2-desktop

How come I don’t have kernel 3.0.0-rc7-(x?) yet? Ditto for M3.

Factory tested is a rolling release repo

If you want Milestone you need factory, but they are awaiting a fix on the current v3 kernel

factory is rolling release - reporting currently as 12.1 M3
factory-tested updates automatically from factory again rolling (now should be reporting 12.1 M3), when basic QA tests succeed eg) kernel boots, X11 starts & zypper can update packages. Just checking now and it’s updated.

The official 12.1 M3 is basically a snapshot, with the repo’s set to distribution/12.1 and all the usual installation media available. It was the kernel 3.0rc6 failing the QA test for factory-tested by oops-ing on boot which held up 12.1 M3 release.

You can update 12.1 M3 at a later point, by switching the repo’s to factory-tested like you can update to factory, See openSUSE:Factory-tested - openSUSE

Try again, I see kernel-desktop-3.0.rc7-2.1.x86_64.rpm in the repo at http://download.opensuse.org/factory-tested/repo/oss/
The repo mirror you use probably hadn’t finished updating, factory-tested was stuck on July 9th, it’s now updated July 19th.

On 07/19/2011 09:36 AM, robopensuse wrote:
>
> factory is rolling release

wrong. factory is the single repo holding the currently
prospective/planned software for the next openSUSE release, 12.1

it is not a “rolling release” (like Debian is a rolling release),
instead it is simply a work in progress and not yet ‘released’ as an
openSUSE product. (which is why it is diescussed in this
“pre-release/beta” forum rather than the only “rolling release”
currently produced by the community as Tumbleweed, which has its own
forum and code source (factory tested)…


DD
Caveat-Hardware-Software
openSUSE®, the “German Engineered Automobiles” of operating systems!

Effectively, it’s a rolling release for development & testing, featuring mostly package updates. So if looking at how it actually works and is used, rather than paper work, it’s rolling towards 12.1, and will become 12.2 in November.

Right now it’s just bumped from 12.1 M2 to 12.1 M3 and will bump up again in future. Packages tend to be worked on in OBS development repos, and they have to be submitted to factory to become part of openSUSE. So for instance Tumbleweed can only take package updates out of those already submittted and available from factory. Where Factory & Fedora Rawhide, or Debian Sid (unstable) differ from the rolling releases you mention, is that things are allowed to break there.

Mentioning Debian is interesting, because actually 11.4 is as much a rolling release as say Debian “Lenny” was. Presumably you could set your repo list to Index of /distribution/openSUSE-stable. Furthermore the “upgrade” to factory or factory-tested is very similar to how you move to Debian “Sid”, in fact the Fate feature was named “Support Debian like distribution upgrade” which was done for 11.2 IIRC. What differs is our repo lists indicate a fixed version, whereas the apt sources list on a Debian stable box encourage the use of a “stable” label rather than codename or version number.

Installing 12.1 M2 you did not have a rolling release, you were stuck without updates. To bump versions, after 12.1 M3 is out, you can do a distro upgrade.
But that’s not a rolling release, that’s rather like the Debian model, with stable release acquiring patches only, then bumping up with one big change.

Factory, Factory Tested & Tumbleweed are far more roller’s in character than is a release like Debian Stable.

I think you made a typo there. The final, stable release of 12.1 will be in November.

On 07/19/2011 12:36 PM, pilotgi wrote:
>
> I think you made a typo there

more errors in fact than just that one typo…
his “factory is a rolling release” continues to have no basis in fact.

factory contains the code base for a development process which includes
several milestone and release candidate snapshots, leading up to one
non-rolling release in November (of 12.1), and then a one time,
different release of a new version (12.2) some 8 months later…

all the while, the only “rolling release” from the openSUSE code base
will continue to be the release named Tumbleweed, available in the
Tumbleweed (not factory) repos…


DD
Caveat-Hardware-Software
openSUSE®, the “German Engineered Automobiles” of operating systems!

@roboopensuse,

zypper up > “opensuse 12.1 is to be re-installed”

1031 packages to be upgraded, 28 new, 1 to remove, etc

kernel-desktop-3.0.0-rc7-2.2.x86_64.rpm

After reboot, Grub menu shows “12.1 MS3 kernel-3.0.0.rc7-2.1.x86_64.desktop” as default and 12.1 MS3 (failsafe), 11.4 and other OS’s.

Hitting 12.1 MS3 (default) only shows the first part of the login page with a white horizontal band, but the second part shows just the gecko on a green opensuse theme, no login boxes, no mouse cursor.

Reboot into 12.1 MS3 with boot code 3 in order to re-install Grub for the 11.4 install per instructions from caf4926.

Now, after reboot from Grub menu directly into 12.1 MS3, I only see the first part of the login page and there are no login boxes in the second part.

Any ideas or suggestions? Thanks a lot for your help.

PS:

After re-installing Grub into 11.4 I am able to boot into 11.4, Windows and other Linux OS’s but not 12.1 M3.

When I downloaded and installed M3 from “http://download.opensuse.org/distribution”, the same problem occurred. No login boxes. After reboot, there’s a blinking hyphen on a black screen. I had to add “nomodeset” to the boot option in the Grub menu as well as the kernel boot option in /boot/grub/menu.lst in order to be able to log in, because my PC has a Nvidia card.

Are you using gdm (GNOME) or kdm (KDE)? It sounds like you can log in non-graphically, so the messed up display is either an X issue or somethingt weird in the graphical login manager. I use KDE but wasn’t upgrading, but clean install from “Build 132” with tweaks to work round the kernel issue.

Coolo’s released 12.1 M3! Not quite a week delay, and it ships with 3.0rc7 - Index of /distribution/12.1-Milestone3/iso ( Skeptics can read the announcement [opensuse-factory] Milestone3](http://lists.opensuse.org/opensuse-factory/2011-07/msg00324.html) themselves).

If you installed with earlier build Index of /distribution by chaning the /distribution/12.1/repo/oss (non-oss) entries, the 12.1 Milestone 3, directory doesn’t have a repo anyway here, just the iso’s so you’ld be editting the repo’s anyway to factory or factory-tested.

There was another kernel bug which has delayed 3.0 release - How to ruin Linus’s vacation - [LWN subscriber-only content till 26th July] there’s less interesting coverage on the usual news sites. Basically under “stress” it was possible for files to temporrily “disappear”, so if you did a “cp -a” it might miss 1 or 2. Finally justifies my paranoid usage or rsync -Sax & rsync -cSax for verfification of large copies.