Is this likely to fix bug 6077 Thomas?

If not then I won't mess around with that computer.

(In reply to comment #1)
> Is this likely to fix bug 6077 Thomas?
> 
> If not then I won't mess around with that computer.

Not directly, unless it gets fixed as a "side-effect" of all other fixes...

But I left comments on 6077 on stuff to test...

Using:

shlomif@lap:~$ uname -r
3.3.8-desktop-2.mga2

From updates_testing on Mageia 2, everything appears to be in working order: KDE, LXDE, VLC playing video+sound, claws-mail, wifi, Samba, the works.

My x86-64 Acer laptop's spec is:

I also have an Acer Aspire 5738DZG laptop with the following specs:

    Intel Pentium(R) Dual-Core CPU T4300 @ 2.10GHz. (x86-64).
    ATI Mobility Radeon⢠HD 4570 (r700)
    15.6×´ 3D HD LCD Screen.
    3 GB Memory
    320 GB Hard Disk Drive.
    âDVD Super Multi DL driveâ
    Acer Nplify⢠802.11b/g/n.

Regards,

-- Shlomi Fish

CC: (none) => shlomif

tmb please take a look here:
https://bugs.mageia.org/show_bug.cgi?id=6935

CC: (none) => tolhildan_123

All kernel flavours boot ok in virtualbox, Mageia 2 i586

Testing on MGA2, i586.

I will report back tomorrow.

CC: (none) => wassi

Testing complete for the kernel-desktop-3.3.8-2.mga2-1-1.mga2 on Mageia release 2 (Official) for x86_64 ,for me it's Ok ,nothing to report.


Laptop Asus K73S ,Intel Core i3-2350M, 2.3GHz

Kernel 3.3.8-desktop-2.mga2 on a 4-processor x86_64

CC: (none) => geiger.david68210

Tested kernel-desktop-3.3.8-2.mga2 on i586 (Dell Latitude D820 laptop - only standard drivers)

Infrastructure OK: install (kernel-desktop, kernel-desktop-latest, kernel-doc, kernel-userspace-headers, perf), boot, sound, wifi, usb.

Comment: trying to load perf from rpmdrake I got: "Rpmdrake or one of its priority dependencies needs to be updated first. Rpmdrake will then restart" (I did not go farther, installed perf from commandline urpmi).

Did about an hours production work (fully customized KDE environment) on the thus installed system: nothing abnormal observed.

Some items of the Dell Latitude specifications
    Core Duo T2400 CPU @ 1.83 GHz
    NVIDIA Quadro NVS 120 graphics solution with 512MB TurboCache
    (Intel 945GM/GMS, 943/940GML controller)
    Dell Wireless 1390 WLAN (802.11b/g 54Mbps) (Intel 3945ABG)
    Bluetooth radio (Toshiba stack)

CC: (none) => juergen.harms

Testing complete on MGA2, i586.

SRPM: kernel-3.3.8-2.mga2.src.rpm

What was tested: only kernel-desktop; boot, sound, wifi, bluetooth, usb, card reader all ok, used for several hours without problems

What was not tested: suspend, fingerprint reader

System: Laptop Thinkpad L510
Intel Core 2 Duo T6570 / 2.10 GHz
Intel GMA 4500MHD Dynamic Video Memory Technology 5.0
RTL 8191SEvB Wireless LAN Controller
HDA Intel (ALC 269 Analog) Sound card

Summary: Everything OK, nothing to report.

My virtual box kernel modules did not get installed.

systemctl status virtualbox.service
virtualbox.service - LSB: VirtualBox Linux kernel module
          Loaded: loaded (/etc/rc.d/init.d/virtualbox)
          Active: active (exited) since Fri, 10 Aug 2012 05:03:08 -0400
         Process: 1132 ExecStart=/etc/rc.d/init.d/virtualbox start (code=exited, status=0/SUCCESS)
          CGroup: name=systemd:/system/virtualbox.service

# rpm -q --scripts virtualbox-kernel-3.3.8-desktop-2.mga2
postinstall scriptlet (using /bin/sh):
/usr/sbin/dkms install --binary -m virtualbox -v 4.1.18-1.mga2 -k 3.3.8-desktop-2.mga2 --rpm_safe_upgrade
/usr/sbin/dkms status -m virtualbox -v 4.1.18-1.mga2

# /usr/sbin/dkms install --binary -m virtualbox -v 4.1.18-1.mga2 -k 3.3.8-desktop-2.mga2 --rpm_safe_upgrade
dkms.conf: Error! No 'DEST_MODULE_LOCATION' directive specified.
dkms.conf: Error! No 'PACKAGE_NAME' directive specified.
dkms.conf: Error! No 'PACKAGE_VERSION' directive specified.

Error! Bad conf file.
Your dkms.conf is not valid.

"lsmod|grep vb" has no output.

CC: (none) => davidwhodgins

No problem so far on my work Mageia 2 64 bits system, with nvidia drivers.

tmb, any comment to comment #10?

(In reply to comment #10)
> My virtual box kernel modules did not get installed.
> 
> systemctl status virtualbox.service
> virtualbox.service - LSB: VirtualBox Linux kernel module
>           Loaded: loaded (/etc/rc.d/init.d/virtualbox)
>           Active: active (exited) since Fri, 10 Aug 2012 05:03:08 -0400
>          Process: 1132 ExecStart=/etc/rc.d/init.d/virtualbox start
> (code=exited, status=0/SUCCESS)
>           CGroup: name=systemd:/system/virtualbox.service
> 
> # rpm -q --scripts virtualbox-kernel-3.3.8-desktop-2.mga2
> postinstall scriptlet (using /bin/sh):
> /usr/sbin/dkms install --binary -m virtualbox -v 4.1.18-1.mga2 -k
> 3.3.8-desktop-2.mga2 --rpm_safe_upgrade
> /usr/sbin/dkms status -m virtualbox -v 4.1.18-1.mga2
> 
> # /usr/sbin/dkms install --binary -m virtualbox -v 4.1.18-1.mga2 -k
> 3.3.8-desktop-2.mga2 --rpm_safe_upgrade
> dkms.conf: Error! No 'DEST_MODULE_LOCATION' directive specified.
> dkms.conf: Error! No 'PACKAGE_NAME' directive specified.
> dkms.conf: Error! No 'PACKAGE_VERSION' directive specified.
> 
> Error! Bad conf file.
> Your dkms.conf is not valid.
> 
> "lsmod|grep vb" has no output.


Hm, how did you get into this? did you uninstall any of the 3.3.8 series kernels before this happend ?

Testing complete on MAG2, x86_64, everything seems ok (sound, driver fgrlx, boot, suspend)

No problems.

I've seen no problems, and would validate the update, but I think
bug 7025 opened for comment 10, needs to be fixed first, otherwise
people will not be able to run VirtualBox guests.

I have done simple tests now also on a 64-bit partition  on my desktop (kernel-server-3.3.8-2, standard drivers only). I have not been able to do extensive testing in everyday production, but the system installs well, and rapid checking of the interface to the periphery are all satisfactory

(In reply to comment #13)
> (In reply to comment #10)
> > My virtual box kernel modules did not get installed.
> > # /usr/sbin/dkms install --binary -m virtualbox -v 4.1.18-1.mga2 -k
> > 3.3.8-desktop-2.mga2 --rpm_safe_upgrade
> > dkms.conf: Error! No 'DEST_MODULE_LOCATION' directive specified.
> > dkms.conf: Error! No 'PACKAGE_NAME' directive specified.
> > dkms.conf: Error! No 'PACKAGE_VERSION' directive specified.
> > 
> > Error! Bad conf file.
> > Your dkms.conf is not valid.
> > 
> > "lsmod|grep vb" has no output.

> Hm, how did you get into this? did you uninstall any of the 3.3.8 series
> kernels before this happend ?

No uninstalls involved. After seeing the attachment posted to
https://bugs.mageia.org/show_bug.cgi?id=7087#c1
I'm wondering if there is a problem with dkms itself, such that the
files are getting deleted from the source dir, prior to getting
properly installed.

Seems strange version numbering Thomas, is the extra 'mga2' intended?

-3.3.8-2.mga2-1-1.mga2

I've taken bug 7025 off of the depends on list, as I cannot recreate the
problem, even by starting with a clean install, and then installing the
relevant packages in the same order as shown by my syslog.

I think we can validate this once Thomas has responded to the query in comment 18.

Whiteboard: (none) => feedback

For comment 18, its intended.

Thats how we fool rpm/urpmi to never upgrade (rpm -U) a kernel, thus removing the previous one, and potentially break users systems if the new kernel would not work... instead we force an install (rpm -i)

Basically we stick the real version and release as part of name (the first part "3.3.8-2.mga2") to show exactly what kernel it is, and the second part "1-1.mga2" is the version rpm reads/compares, always version 1, release 1 (meaning rpm/urpmi never sees an updated one).

And to finally top it of we have the kernel-*-latest that uses the real version "3.3.8" and release "2.mga2" that pulls the specially named kernels so people gets automatic updates :)



One thig that still is missing before I can push this kernel is the fglrx update for mga2 (bug 7086) still needs i586 validation as I will push prebuilt modules as part of / at the same time as the kernel update..

> Basically we stick the real version and release as part of name (the first part
> "3.3.8-2.mga2") to show exactly what kernel it is, and the second part
> "1-1.mga2" is the version rpm reads/compares, always version 1, release 1
> (meaning rpm/urpmi never sees an updated one).

I understand (in both senses of the word) - clever (the french would say "futé"). I looked back: this trick has already been used in Mageia 1. Once you realise, quite evident - but not evident for the naive user who tries to understand the listing provided when he does an update

In the long run: can a solution be conceived that is more transparent - easier to understand by the non-specialist? OK, something in the package should tell urpmi that packages with preceding versions must not be removed: the trick hides this instruction in the syntax of the splitting off of the version part of the package name.

Would it make sense to make urpmi understand that packages with a given pattern in their name (in the kernel example: starting by kernel and not kernel-*-latest) should avoid removing their predecessor? Is kernel the only envisageable case where this problem might occur (with other words: do I suggest finding a general solution for a very isolated problem)? - An approach might, for instance, be: have a file in /etc/urpmi/... that contains regular expressions which contain such patterns?

Sorry, this is slightly off-topic for a bugzilla report.

Thanks for the explanation Thomas:)

nvidia I think you mean for bug bug 7086 btw

You can maybe discuss that further on the ML Juergen


Validating this one then.

Comment 0 for advisory and srpms

Could sysadmin please push from core/updates_testing to core/updates when bug 7086 has been validated.

Thanks!

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs
Whiteboard: feedback => mga2-32-OK mga2-64-OK

(In reply to comment #22)
> > Basically we stick the real version and release as part of name (the first part
> > "3.3.8-2.mga2") to show exactly what kernel it is, and the second part
> > "1-1.mga2" is the version rpm reads/compares, always version 1, release 1
> > (meaning rpm/urpmi never sees an updated one).
> 
> I understand (in both senses of the word) - clever (the french would say
> "futé"). I looked back: this trick has already been used in Mageia 1. Once you

Oh, it's actaully way older :)

I introduced it in Mandriva main kernel on:
Fri Aug 24 2007 with 2.6.22.3-1mdv2008.0

and before that in kernel-tmb series as of:
Mon May  1 2006 with 2.6.16.11-4mdk

> 
> Would it make sense to make urpmi understand that packages with a given pattern
> in their name (in the kernel example: starting by kernel and not
> kernel-*-latest) should avoid removing their predecessor? Is kernel the only
> envisageable case where this problem might occur (with other words: do I
> suggest finding a general solution for a very isolated problem)? - An approach
> might, for instance, be: have a file in /etc/urpmi/... that contains regular
> expressions which contain such patterns?

It already does support it with /etc/urpmi/inst.list,
but it was decided that it was not safe enough...

If a beginner tries to install a rpm manually, reading on the net that rpm -U is the way to install a new package, it would break the install, and that we want to avoid as much as possible, as a non-booting system tends to be harder to fix due to a broken kernel, than fixing other stuff. So we opted for better safe than sorry...

but this is indeed OT for this BR :)

(In reply to comment #23)
> Thanks for the explanation Thomas:)
> 
> nvidia I think you mean for bug bug 7086 btw


yep, nvidia not fglrx, thanks for correcting :)

Update pushed:
https://wiki.mageia.org/en/Support/Advisories/MGASA-2012-0237

Status: NEW => RESOLVED
Resolution: (none) => FIXED