well, all the packages were installed and the machine booted just fine. the only problem is this is installed as a guest in VirtualBox and there is apparently no kernel dev package for the newly installed kernel so I can’t build the guest additions and am stuck in 640x480 mode lol!
so I reverted back to a previous state and things are back to normal. I guess I will wait for milestone 1. 
On 2014-04-19 18:06, wolfi323 wrote:
> Right, that’s what I said.
> But the point is, that even “zypper up” would show some (most) updates
> on Factory.
And miss the downgrades, packages removals, and downgrades.
> Factory is constantly updated, not once every few months as you wrote.
> But I guess with “updates” you meant patches in the update repo, right?
Certainly, I mean patches. The ones that the OP says he is not getting,
only the test updates.
And these will not appear in months.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Correct.
And I never said anything else.
Certainly, I mean patches. The ones that the OP says he is not getting,
only the test updates.
The OP said he is not getting any updates, not even with “zypper up”.
From his first post:
[HR][/HR]
Of course there is. But you have to install them manually just as with any released version.
There’s kernel-source, kernel-devel, and kernel-xxx-devel in Factory for every kernel-xxx in Factory.
And there are ready-made VirtualBox guest tools packages in Factory which should get installed automatically, but maybe they were just not installed?
Those are:
virtualbox-guest-kmp-xxx, virtualbox-guest-x11, virtualbox-guest-tools.
But I don’t know whether they work right now. They did when I last installed Factory.
It might be of course that they are not yet built for the current kernel.
Btw, when the vbox video driver is not available, most likely fbdev is used. You should be able to set the resolution in YaST->System->Boot Loader->Boot Loader Options then, fbdev should respect this for the graphical mode as well. 
well zypper said there was no package when I tried to install it. the kernel that was installed was a rc. when I get a chance I will try again
Hm?
Factory contains kernel 3.14.0, and the package is dated Apr. 13th.
The 13.2 repo has an rc (3.14rc5), but it also contains the devel packages for that.
I guess you removed/disabled the 13.2 repos, but still had the 3.14.rc5 kernel installed.
In that case you should have just uninstalled it (zypper rm kernel-desktop-3.14.rc5).
On openSUSE two kernels are being kept installed by default, so if you upgrade your kernel to a newer version (i.e. 3.14.0 from Factory), the older one (i.e. 3.14.rc5 from Mileston0 in this case) is still installed as well afterwards.
actually I didn’t disable the 13.2 repos, I just added the factory repo thinking the ones from the factory would override anything that was older. obviously not. I’m not used to having to remove older kernels manually although I know how. I can’t remember now if I removed the VirtualBox guest additions that came pre-installed and replaced them with the PUEL versions or not. I don’t think I did but I have 52 guests and it’s hard to remember what I did to what. as I said, I will give this a whirl when I get a little time to reinstall the files from the factory repo and start again 
On Sat, 19 Apr 2014 18:16:01 GMT
LKJ <LKJ@no-mx.forums.opensuse.org> wrote:
>
> wolfi323;2637957 Wrote:
> > Hm?
> > Factory contains kernel 3.14.0, and the package is dated Apr. 13th.
> >
> > The 13.2 repo has an rc (3.14rc5), but it also contains the devel
> > packages for that.
> > I guess you removed/disabled the 13.2 repos, but still had the
> > 3.14.rc5 kernel installed.
> > In that case you should have just uninstalled it (zypper rm
> > kernel-desktop-3.14.rc5).
> > On openSUSE two kernels are being kept installed by default, so if
> > you upgrade your kernel to a newer version (i.e. 3.14.0 from
> > Factory), the older one (i.e. 3.14.rc5 from Mileston0 in this case)
> > is still installed as well afterwards.
>
> actually I didn’t disable the 13.2 repos, I just added the factory
> repo thinking the ones from the factory would override anything that
> was older. obviously not. I’m not used to having to remove older
> kernels manually although I know how. I can’t remember now if I
> removed the VirtualBox guest additions that came pre-installed and
> replaced them with the PUEL versions or not. I don’t think I did but
> I have 52 guests and it’s hard to remember what I did to what. as I
> said, I will give this a whirl when I get a little time to reinstall
> the files from the factory repo and start again
>
>
Factory does override the older stuff - or at least it does for me. I
now have kernel 3.14.0 installed although, when I boot, the message says
that the version is 3.14.0-rc7. This is a frequent irritant with kernel
updates and I’ve no idea why the message doesn’t get changed.
–
Graham P Davis, Bracknell, Berks.
openSUSE 13.2-m0 (64-bit); KDE 4.13.0; AMD Phenom II X2 550 Processor;
Kernel: 3.14.0; Video: nVidia GeForce 210 (using nouveau driver);
Sound: ATI SBx00 Azalia (Intel HDA)
On 2014-04-19 18:06 (GMT) wolfi323 composed:
> LKJ;2637954 Wrote:
>> well zypper said there was no package when I tried to install it. the
>> kernel that was installed was a rc. when I get a chance I will try again
>>
> Hm?
> Factory contains kernel 3.14.0, and the package is dated Apr. 13th.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
thank you. I didn’t think I was making it up. I am running the 64bit version but I think I’ll wait for the repos to clear up.
No, I guess you are really booting kernel 3.14.0-rc7.
Run “uname -a” to check.
There was a bug in grub2 that it sorts the rc kernels in the wrong order, so it thinks that 3.14.0-rc7 is newer than 3.14.0 and boots that.
You should be able to choose 3.14.0 in “Advanced Options”.
This got fixed recently, but I don’t know whether the fix is in Factory already:
https://bugzilla.novell.com/show_bug.cgi?id=827531
Maybe uninstall 3.14.0-rc7 to fix the issue.
Yes, you are right. For 32bit there’s only kernel-default and kernel-ec2 in the repo (with the corresponding devel packages).
But for 64bit everything seems to be ok.
On Sun, 20 Apr 2014 09:26:02 GMT
wolfi323 <wolfi323@no-mx.forums.opensuse.org> wrote:
>
> Cloddy;2638046 Wrote:
> > On Sat, 19 Apr 2014 18:16:01 GMT
> > Factory does override the older stuff - or at least it does for me.
> > I now have kernel 3.14.0 installed although, when I boot, the
> > message says that the version is 3.14.0-rc7. This is a frequent
> > irritant with kernel updates and I’ve no idea why the message
> > doesn’t get changed.
> No, I guess you are really booting kernel 3.14.0-rc7.
>
> Run “uname -a” to check.
>
> There was a bug in grub2 that it sorts the rc kernels in the wrong
> order, so it thinks that 3.14.0-rc7 is newer than 3.14.0 and boots
> that.
> You should be able to choose 3.14.0 in “Advanced Options”.
You’re right, it is booting rc7. Pity the kernel doesn’t use a
similar version numbering to, say, KDE so that it would have been
something like 3.13.97.
>
> This got fixed recently, but I don’t know whether the fix is in
> Factory already:
> https://bugzilla.novell.com/show_bug.cgi?id=827531
>
> Maybe uninstall 3.14.0-rc7 to fix the issue.
>
The fix isn’t in yet and I think I’ll leave rc7 where it is so that I
can see when the cured grub2 arrives.
Thanks for your help.
–
Graham P Davis, Bracknell, Berks.
openSUSE 13.2-m0 (64-bit); KDE 4.13.00; AMD Phenom II X2 550 Processor;
Kernel: 3.14.0; Video: nVidia GeForce 210 (using nouveau driver);
Sound: ATI SBx00 Azalia (Intel HDA)