Bug 20155 - partway through upgrade from Mga5 to Mga6 ERROR: 'script' failed for dkms-broadcom-wl-6.30.223.271-45.mga6.nonfree.x86_64"
: partway through upgrade from Mga5 to Mga6 ERROR: 'script' failed for dkms-br...
Status: NEW
Product: Mageia
Classification: Unclassified
Component: RPM Packages
: Cauldron
: x86_64 Linux
: release_blocker Severity: normal
: ---
Assigned To: Kernel and Drivers maintainers
:
:
:
: 6sta2
:
:
  Show dependency treegraph
 
Reported: 2017-01-21 22:39 CET by Marja van Waes
Modified: 2017-03-12 20:52 CET (History)
11 users (show)

See Also:
Source RPM: broadcom-wl
CVE:
Status comment:


Attachments
upgrade of 5.1 to m6-sta2 i586 (224.78 KB, application/octet-stream)
2017-03-06 20:26 CET, ben mcmonagle
Details

Description Marja van Waes 2017-01-21 22:39:17 CET
+++ This bug was initially created as a clone of Bug #20111 +++

Which is about a different "'script' failed" issue, but this issue emerged in it.

https://bugs.mageia.org/show_bug.cgi?id=20111#c14


(In reply to Marja van Waes from comment #14)

> (In reply to ben mcmonagle from comment #11)
> > Created attachment 8876 [details]
> > 5.1 to mga6 sta report.bug.xz
> 
> [marja@localhost Downloads]$ xzcat 20111report.bug.xz |grep DrakX
> * second stage install running (DrakX v17.71)
> [marja@localhost Downloads]$ xzcat 20111report.bug.xz |grep script | grep
> failed
> * urpmi error: ERROR: 'script' failed for glibc-6:2.22-21.mga6.x86_64
> * urpmi error: ERROR: 'script' failed for glibc-6:2.22-21.mga6.x86_64
> * urpmi error: ERROR: 'script' failed for
> dkms-broadcom-wl-6.30.223.271-45.mga6.nonfree.x86_64
> %triggerin(postfix-1:2.10.3-5.mga5.x86_64) scriptlet failed, exit status 127
> %triggerin(systemd-217-11.2.mga5.x86_64) scriptlet failed, exit status 127
> %post(dkms-broadcom-wl-6.30.223.271-45.mga6.nonfree.x86_64) scriptlet
> failed, exit status 1
> [marja@localhost Downloads]$ 
> 
> (a separate bug report is needed for the dkms-broadcom-wl scriptlet failure)
> 

IINM this is the needed part from the logs:

dkms-minimal-2.0.19-37.mga6.noarch
dkms-2.0.19-37.mga6.noarch
+ /usr/sbin/dkms --rpm_safe_upgrade add -m broadcom-wl -v 6.30.223.271-45.mga6.nonfree
+ /usr/sbin/dkms --rpm_safe_upgrade build -m broadcom-wl -v 6.30.223.271-45.mga6.nonfree

Error! Your kernel devel files for kernel 4.9.2-desktop-1.mga6 cannot be found at
/lib/modules/4.9.2-desktop-1.mga6/build or /lib/modules/4.9.2-desktop-1.mga6/source.
%post(dkms-broadcom-wl-6.30.223.271-45.mga6.nonfree.x86_64) scriptlet failed, exit status 1
dkms-broadcom-wl-6.30.223.271-45.mga6.nonfree.x86_64
Comment 1 Rémi Verschelde 2017-03-06 10:23:17 CET
Can this issue still be reproduced using current sta2 ISOs for an upgrade?
Comment 2 ben mcmonagle 2017-03-06 20:26:43 CET
Created attachment 9032 [details]
upgrade of 5.1 to m6-sta2 i586
Comment 3 Martin Whitaker 2017-03-12 12:39:54 CET
This is happening because the installer is running kernel 4.9.3 but is installing kernel 4.9.13. The dkms build called by the postinstall script will only succeed if the kernel versions are the same.

@Ben, was this the final sta2 ISO? I see kernel 4.9.4 when I run that (which doesn't help of course - I'm just curious about the discrepancy).
Comment 4 ben mcmonagle 2017-03-12 19:58:43 CET
(In reply to Martin Whitaker from comment #3)

> 
> @Ben, was this the final sta2 ISO? I see kernel 4.9.4 when I run that (which
> doesn't help of course - I'm just curious about the discrepancy).

Yes

> This is happening because the installer is running kernel 4.9.3 but is
> installing kernel 4.9.13. The dkms build called by the postinstall script
> will only succeed if the kernel versions are the same.

ok.

after upgrade wifi is not working.
drakroam is unable to correct/connect so cannot configure. (cannot find network)
running configure network from MCC does work. but need to change network encryption from open to correct pre shared key option.
password is already entered.
does not need to add any packages to complete network connection.
Comment 5 Martin Whitaker 2017-03-12 20:52:42 CET
(In reply to ben mcmonagle from comment #4)
> after upgrade wifi is not working.
> drakroam is unable to correct/connect so cannot configure. (cannot find
> network)
> running configure network from MCC does work. but need to change network
> encryption from open to correct pre shared key option.
> password is already entered.
> does not need to add any packages to complete network connection.

If the dkms build fails during installation, it should get rerun automatically when you first boot the upgraded system (although this may be unreliable at the moment due to bug 17194). But maybe there's something the post-install script should do after the dkms build that didn't happen because the dkms build failed.

Note You need to log in before you can comment on or make changes to this bug.