Migrating to SLED11-SP2

I’ve decided to open this thread to clarify the issues only briefly mentioned in SLED documents, notably
SUSE_SLED-SP2-migration, a product to migrate to SUSE_SLED Service Pack 2.
Migration is covered in Novell documents referring to on-line update, whereas update from the DVD lacks such steps.

Having read, after updating SLED11-SP1 to SP2 via DVD, about a migration tool
http://forums.suse.com/showthread.php?916-HP-Notebook-Owners-Update-to-SLED-11-SP2/page3, after updating SLED11-SP1 to SP2 via DVD,
I checked the state of upgrading, and faced a couple of conflicts in the transaction that must be solved manually.

Installed product:SUSE_SLED-11.2-1.513.i586 obsoletes SUSE_SLED-SP2-migration provided by product:SUSE_SLED-SP2-migration-11.1.-1.6.i586

  • downgrade of product:SUSE_SLED-11.2-1.513.i586 to product:SUSE_SLED-11.1.-1.206.i586
  • do not install product:SUSE_SLED-SP2-migration-11.1-1.6.i586

product:SUSE_SLED-11.2-1.513.i586 requires sled-release=11.2-1.513, but this requirement cannot be provided

  • downgrade of product:SUSE_SLED-11.2-1.513.i586 to product:SUSE_SLED-11.1.-1.206.i586
  • do not install product:SUSE_SLED-SP2-migration-11.1-1.6.i586
  • break product:SUSE_SLED-11.2-1.513.i586 by ignoring some of its dependencies

At this point questions as to migration process in finalising update from SP1 to SP2 arise:

  1. Do we actually need to install product:SUSE_SLED-SP2-migration?
  2. Is updating completed without installing SUSE_SLED-SP2-migration package or not?
  3. Will downgrading of product:SUSE_SLED-11.2-1.513.i586 to product:SUSE_SLED-11.1.-1.206.i586, as YaST suggests, in fact downgrade the system SP2 (_SLED-11.2) back to SP1 (_SLED-11.1)?

If this is clear for SLED pundits, could someone share his/her expertise in resolving the above conflicts?
Thanks

Lliner

Do you mean ‘without a migration tool’?

You don’t say exactly what is you’ve done prior to encountering the problems you mention.

Have a look at
http://www.novell.com/support/kb/doc.php?id=7010200
there’s a section “Procedure for upgrading from SLES / SLED 11 SP1” and then two further sections, one on how to do it online with patches and the migration tool and how to do it from the DVD. The section “Update via using a SLE 11 SP2 installation media” doesn’t mention applying all outstanding updates before attempting to upgrade to SP2, but I’d advise doing so.

Hi, Mike, thank you for rely.

I think you are right, “without”, as no SUSE_SLED-SP2-migration is mentioned in Document
http://www.novell.com/support/kb/doc.php?id=7010200, chapter referring to
“3) Update by booting from a SLES/SLED 11 SP2 media”.

So having successfully updated through the DVD option ‘–>Select “Update an Existing System”’,
then as there were no SP2 repositories installed (maybe because I did update off-line),
I refresed repositories in Zypper and updated the patches. For example, Kernel is upgarded to 3.0.34-0.7.9, etc.
The system rebooted successfully. I saw no major problems, as the system works, eccept some
packages failing (Cheese, Virtualbox, WMvare and some conflicting packages in clamtk, with clamv working).

As no extra instructions in http://www.novell.com/support/kb/doc.php?id=7010200
for update via DVD are listed, I decided that I was already working in SP2.

My concern appeared after I searched for “SP2” in ‘Available’, the SP2-Migration tool, I learnt from Arnaudk93 post “HP Notebook Owners Update to SLED 11 SP2”.

VirtualBox and VMWare probably just need to have their kernel modules rebuilt. There is no package called clamtk in either SLED or SLE-SDK so presumably you installed that yourself, maybe you need to re-install it or something. I would expect Cheese to still work.

What’s the output of

$ cat /etc/novell-release $ zypper lr -u

[QUOTE=mikewillis;5766]VirtualBox and VMWare probably just need to have their kernel modules rebuilt.[/QUOTE] Here my understanding of migration stops short: IBM treat “The goal of migration is to allow you to continue to work in the current version or the product with projects that you developed in previous versions”, so either my system migration is not complete, or Novell use another meaning for this word? (OpenSUSE Glossary in Russian gives Migration as transfer of (applications & data)

[QUOTE=mikewillis;5766]There is no package called clamtk in either SLED or SLE-SDK so presumably you installed that yourself, maybe you need to re-install it or something. [/QUOTE] Yes, I installed ClamTk, a handy GUI front-end for ClamAV, Version : 4.41-1.3 Vendor: openSUSE Build Service. I believed that if clamav 0.96 is part of SLED11-SP2, its front-end serves as inalienable part.

[QUOTE=mikewillis;5766] I would expect Cheese to still work. [/QUOTE] I’d rather it worked. But according to Cheese manual FAQ “3. As Cheese uses the gstreamer backend, it is most likely because gstreamer is not detecting the webcam (or gstreamer has become corrupt).” Testing with gstreamer produces the same result: Rainbow vertical colours in place of picture.

$ cat /etc/novell-release SUSE Linux Enterprise Desktop 11 (i586) VERSION = 11 PATCHLEVEL = 2

[CODE]
$ zypper lr -u

| Alias | Name | Enabled | Refresh | URI

—±--------------------------------------------------±--------------------------------------------------±--------±--------±--------------------------------------------------------------------------------------------------
1 | ATI-Driver-HP-BNB-SLE11-SP2 | ATI-Driver-HP-BNB-SLE11-SP2 | No | No | http://www2.ati.com/suse/hp/bnb/2012/sle11sp2
2 | Broadcom-Driver-HP-BNB-SLE11-SP2 | Broadcom-Driver-HP-BNB-SLE11-SP2 | Yes | Yes | http://www.broadcom.com/docs/linux_sta/repo/HP/bnb/2012/sle11sp2
3 | DISK-PKG | DISK-PKG | No | Yes | dir:///usr/local/packgs
4 | Essentials | Essentials | Yes | Yes | http://pmbs.links2linux.org/download/Essentials/SLE-11-SP2/
5 | LSI-Driver-HP-BNB-SLE11-SP2 | LSI-Driver-HP-BNB-SLE11-SP2 | Yes | Yes | http://www.lsi.com/sep/Pages/SML/HP/NL/hp/bnb/2012/sle11sp2
6 | SUSE-Linux-Enterprise-Desktop-11-SP2 11.2.2-1.193 | SUSE-Linux-Enterprise-Desktop-11-SP2 11.2.2-1.193 | Yes | No | cd:///?devices=/dev/sr0
7 | VALIDITYINC-Driver-HP-BNB-SLE11-SP2 | VALIDITYINC-Driver-HP-BNB-SLE11-SP2 | Yes | Yes | http://www.validityinc.com/uploads/hp/bnb/2012/sle11sp2
8 | nu_novell_com:SLE11-SP1-Debuginfo-Pool | SLE11-SP1-Debuginfo-Pool | No | Yes | https://nu.novell.com/repo/$RCE/SLE11-SP1-Debuginfo-Pool/sle-11-i586?credentials=NCCcredentials
9 | nu_novell_com:SLE11-SP1-Debuginfo-Updates | SLE11-SP1-Debuginfo-Updates | No | Yes | https://nu.novell.com/repo/$RCE/SLE11-SP1-Debuginfo-Updates/sle-11-i586?credentials=NCCcredentials
10 | nu_novell_com:SLE11-SP2-Debuginfo-Core | SLE11-SP2-Debuginfo-Core | No | Yes | https://nu.novell.com/repo/$RCE/SLE11-SP2-Debuginfo-Core/sle-11-i586?credentials=NCCcredentials
11 | nu_novell_com:SLE11-SP2-Debuginfo-Updates | SLE11-SP2-Debuginfo-Updates | No | Yes | https://nu.novell.com/repo/$RCE/SLE11-SP2-Debuginfo-Updates/sle-11-i586?credentials=NCCcredentials
12 | nu_novell_com:SLED11-Extras | SLED11-Extras | No | Yes | https://nu.novell.com/repo/$RCE/SLED11-Extras/sle-11-i586?credentials=NCCcredentials
13 | nu_novell_com:SLED11-SP1-HP-BNB-Updates | SLED11-SP1-HP-BNB-Updates | No | Yes | https://nu.novell.com/repo/$RCE/SLED11-SP1-HP-BNB-Updates/sle-11-i586?credentials=NCCcredentials
14 | nu_novell_com:SLED11-SP1-Pool | SLED11-SP1-Pool | Yes | Yes | https://nu.novell.com/repo/$RCE/SLED11-SP1-Pool/sle-11-i586?credentials=NCCcredentials
15 | nu_novell_com:SLED11-SP1-Updates | SLED11-SP1-Updates | Yes | Yes | https://nu.novell.com/repo/$RCE/SLED11-SP1-Updates/sle-11-i586?credentials=NCCcredentials
16 | nu_novell_com:SLED11-SP2-Core | SLED11-SP2-Core | Yes | Yes | https://nu.novell.com/repo/$RCE/SLED11-SP2-Core/sle-11-i586?credentials=NCCcredentials
17 | nu_novell_com:SLED11-SP2-HP-BNB-Updates | SLED11-SP2-HP-BNB-Updates | Yes | Yes | https://nu.novell.com/repo/$RCE/SLED11-SP2-HP-BNB-Updates/sle-11-i586?credentials=NCCcredentials
18 | nu_novell_com:SLED11-SP2-Updates | SLED11-SP2-Updates | Yes | Yes | https://nu.novell.com/repo/$RCE/SLED11-SP2-Updates/sle-11-i586?credentials=NCCcredentials [/CODE]
DISK-PKG repo is used for ad-hoc installation of uploaded packages, while working off-line.

[QUOTE=LLiner;5770]Here my understanding of migration stops short: IBM treat “The goal of migration is to allow you to continue to work in the current version or the product with projects that you developed in previous versions”, so either my system migration is not complete, or Novell use another meaning for this word? (OpenSUSE Glossary in Russian gives Migration as transfer of (applications & data)
[/QUOTE]
I think migration means what you think it means. Neither VMWare nor VirtualBox are part of SLED though, so I doubt the SLED migration process takes them in to account.
In my experience both VMware and VirtualBox will need their kernel modules re-built after any kernel update, not just Service Pack update. I use VMWare Workstation and have a script run during boot that checks whether the VMWare modules need to be rebuilt

# check if vmware modules are built for current kernel, if not then rebuild them if [ -z "$(find /lib/modules/$(uname -r) -name vmmon.ko)" ];then vmware-modconfig --console --install-all fi
I have it as part of some other scripts that run during boot but I expect it would work if put in /etc/init.d/boot.local (You might need to change /lib to /lib64 for 64bit system, not sure don’t have access to one to check just now.)

Ah, what you describe is not the same as Cheese not working as you originally indicated. Cheese is working, it just doesn’t see your webcam. Did it see this webcam with SP1? What’s the make/model/usbid of your webcam? To get usbid you can use

$ lsusb

You have the SP2-Core and SP2-Updates repos set up and /etc/novell-release says you’re using SP2, so looks to me like you’ve successfully upgraded but just have a few niggles to sort out.

Many thanks, Mike for a very good news:

lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 05c8:0403 Cheng Uei Precision Industry Co., Ltd (Foxlink) Webcam Bus 006 Device 002: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical

Also, From dmesg:

[CODE]
[ 4.313208] usb 1-5: New USB device found, idVendor=05c8, idProduct=0403
[ 4.313250] usb 1-5: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[ 4.313282] usb 1-5: Product: HP Webcam [2 MP Fixed]
[ 4.313314] usb 1-5: Manufacturer: Foxlink
[ 4.313346] usb 1-5: SerialNumber: 200909240102

[ 7.988136] Linux video capture interface: v2.00
[ 8.052989] uvcvideo: Found UVC 1.00 device HP Webcam [2 MP Fixed] (05c8:0403)
[ 8.070447] input: HP Webcam [2 MP Fixed] as /devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5:1.0/input/input6
[ 8.070592] usbcore: registered new interface driver uvcvideo
[ 8.070633] USB Video Class driver (v1.1.0) [/CODE]

From Linux UVC driver and tools http://www.ideasonboard.org/uvc/#devices
I can see that 05c8:0403 (Foxlink) Webcam is listed as supported UVC (USB Video Cam) device.
In SLED11-SP1 it worked OK, and previous pictures remain in the Cheese folder.

What I also noticed missing rpmlib(CompressedFileNames) <= 3.0.4-1, rpmlib(PayloadFilesHavePrefix) <= 4.0-1, rpmlib(PayloadIsLzma) <= 4.4.2-1
required by the installed package Cheese 2.28.1-2.10.1,
whereas I have rpm-4.4.2.3-37.50.6 installed.
May be I need to update Cheese to 2.32.0 for Suse 11.4?

Do you mean vboxdrv?
I am not sure, if I can apply relevant commands, as my Virtual box packages now are listed as uninstalled!

As far as VMWare is concerned, in case I decide to ditch it for the disk space sake, how can I regain the space allocated for it while VMWare is not active?

Many thanks in advance. Your replies are always substantiative and to the point.

Lliner

I suspect attempting to update Cheese to to 2.32 will just create more problems. If you run

$ zypper verify
that will check that all package dependencies are met and if they’re not it will attempt to fix them. You could try using v4l1compat with Cheese. Check if the file
/usr/lib/libv4l/v4l1compat.so exists (if you’re using 64bit change /usr/lib to /usr/lib64) and if it doesn’t install the libv4l package. You can then try running cheese like this

$ LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so cheese

Possibly, I don’t have a machine with VirtualBox installed on to check.

I’m not sure what you mean by that. Where are they listed as being uninstalled?

Well if you just uninstall it then you’ll get the disk space back that’s used by the actual program. I expect uninstalling it probably leaves behind any Virtual Machines you’ve created though. Assuming you won’t want to use them in future or you have a backup copy you could simply delete them. I don’t know where they are, probably depends on which VMWare product you’re using (Server, Workstation, Other) I use VMWare workstation and can’t remember what the default location is as I don’t use it. If you run

$ find / -name "*.vmx"

that should find them.

Thank you, Mike,

I did verification, with one Problem remaining: encode2mpeg-0.6.4-0.pm.1.1.noarch requires transcode. Unfortunately, I could not find satisfactory package transcode in packman or http://http://software.opensuse.org/package so far.

The file /usr/lib/libv4l/v4l1compat.so exists (I have 32bit).
Unfortunately, neither

$ LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so cheese, nor

$ LD_PRELOAD=/usr/lib/libv4l/v4l2convert.so cheese work for my cheese.

The fact remains that during updating to SLED11-SP2 (maybe in the following verification) all packages with virtualbox were deleted (YaST Software Manager History says so), so I need to reinstall them.

Lliner

Just to add more info:

[QUOTE=LLiner;5807] …during updating to SLED11-SP2 (maybe in the following verification) all packages with virtualbox were deleted.
[/QUOTE]
-because the verifier requested downgrading the newly installed kernel 3.0.34 to the previous one, 2.6.32.54. And I opted to uninstall virtualbox for the sake of updating to SP2 first. Now, when I try to install Virtualbox 4.1.2 again, YaST Program Manager proposes to downgrade kernel to 2.6.32.54:mad:

[QUOTE=LLiner;5812]Just to add more info:

-because the verifier requested downgrading the newly installed kernel 3.0.34 to the previous one, 2.6.32.54. And I opted to uninstall virtualbox for the sake of updating to SP2 first. Now, when I try to install Virtualbox 4.1.2 again, YaST Program Manager proposes to downgrade kernel to 2.6.32.54:mad:[/QUOTE]

Please inform SUSE and create a new case for this defect. This is what I do.

I’ve just reported a Software Defect (bug) at http://support.novell.com/additional/bugreport.html. Is it what I need to do? This is my first report.

[QUOTE=LLiner;5812]
-because the verifier requested downgrading the newly installed kernel 3.0.34 to the previous one, 2.6.32.54. And I opted to uninstall virtualbox for the sake of updating to SP2 first. Now, when I try to install Virtualbox 4.1.2 again, YaST Program Manager proposes to downgrade kernel to 2.6.32.54:mad:[/QUOTE]

Try getting VirtualBox 4.1.18. I just installed that without problem.

I just found VirtualBox 4.1.2 (http://download.virtualbox.org/virtualbox/4.1.2/) and was able to install VirtualBox-4.1-4.1.2_73507_sles11.0-1.x86_64.rpm without problem too.

Where did you get your VirtualBox package from and exactly what are you doing to try and install it?

[QUOTE=mikewillis;5822]I just found VirtualBox 4.1.2 (http://download.virtualbox.org/virtualbox/4.1.2/) and was able to install VirtualBox-4.1-4.1.2_73507_sles11.0-1.x86_64.rpm without problem too.
Where did you get your VirtualBox package from and exactly what are you doing to try and install it?[/QUOTE]

I got VirtualBox from the same download site last August. Now I cannot say for sure which version I downloaded for my SLED11- Suse 11.3 or SLES11 (this has always been a dilemma for me).

Similarly, I am going to save the package on hard disk and install via YaST from HardDisk repository.
I think SLES11 version (-4.1.18) is the right choice for SLED11-SP2 (i586, 32 bit)?

Thanks.
Lliner

The two packages I was able to install are VirtualBox-4.1-4.1.18_78361_sles11.0-1.x86_64.rpm and VirtualBox-4.1-4.1.2_73507_sles11.0-1.x86_64.rpm You’re using 32bit so if I were you I’d get the SLES11 i386 version from https://www.virtualbox.org/wiki/Linux_Downloads

Download it and to install it become root then run

$ zypper in /path/to/where/you/saved/VirtualBox-4.1-4.1.18_78361_sles11.0-1.i586.rpm

If it doesn’t install, post all the output of the zypper command here (wrap it in CODE tags for readability)

Thank you very much, Mike!
Everything (I think) is OK, VirtualBox for SLES11 has installed.:o

[CODE]> rpm -q VirtualBox-4.1
VirtualBox-4.1-4.1.18_78361_sles11.0-1

[/CODE]
And previously installed virtual machines are seen it it, with one (Windows) even working.

[CODE]Retrieving package VirtualBox-4.1-4.1.18_78361_sles11.0-1.i586 (1/1), 62.3 MiB (126.5 MiB unpacked)
Installing: VirtualBox-4.1-4.1.18_78361_sles11.0-1 [done]
Additional rpm output:
[COLOR="#FF0000"] warning: /var/cache/zypp/packages/tmpRPMcache/VirtualBox-4.1-4.1.18_78361_sles11.0-1.i586.rpm: Header V4 DSA signature: NOKEY, key ID 98ab5139[/COLOR]
Creating group ‘vboxusers’. VM users must be member of that group!

No precompiled module for this kernel found – trying to build one. Messages
emitted during module compilation will be logged to /var/log/vbox-install.log.

Stopping VirtualBox kernel modules…done
Uninstalling old VirtualBox DKMS kernel modules…done
Trying to register the VirtualBox kernel modules using DKMS…failed
(Failed, trying without DKMS)
Recompiling VirtualBox kernel modules…done
Starting VirtualBox kernel modules…done [/CODE]
BTW, what does the red warning mean?

And a minor isue: Why in YaST Software Manager VirtualBox version is shown in red? (And more other package versions)
From the Manager’s tip: “It is highlighted red if the version installed is no longer being made available in any configured repository.”

Thanks

Llliner

It means zypper was unable to verify the signature on the package. If you want to be able to verify the signature you need to import the relevant key. There’s insurrection on this on https://www.virtualbox.org/wiki/Linux_Downloads

Never noticed that before (I very rarely use YaST for package management), but I think the relevant part of that last line is ‘any configured repository’. The VirtualBox package you’ve got installed isn’t in any of your configured repositories and so YaST indicates that by showing the version number in red. I see the same thing.