Created attachment 8986 [details]
install report.bug

Comment on attachment 8986 [details]
install report.bug


Thanks for remembering to attach report.bug.xz :-)

Unfortunately, it is not from the upgrade, but from the privious install (read the second "Please note!" here:
https://wiki.mageia.org/en/Triage_guide#Traditional_installer )

It is from the original install :-( :

* getFile install/stage2/VERSION on disk://sda13/M 5.1/Mageia-5.1-x86_64-DVD/Mageia-5.1-x86_64-DVD.iso
* second stage install running (DrakX v16.106)

Do you still have /root/drakx/report.bug from the date & time of the upgrade?

If so, please compress & attach it.

What exactly do you mean with "re-initialise wifi"?

Could you please run, as root:

    journalctl -ab1 > journal.txt

and attach journal.txt to this report, too?

Thanks :-)

CC: (none) => marja11
Attachment 8986 is obsolete: 0 => 1

Created attachment 8989 [details]
correct report.bug.xz

try this one

Created attachment 8990 [details]
journal .txt

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

> 
> What exactly do you mean with "re-initialise wifi"?
> 
> Could you please run, as root:
> 
>     journalctl -ab1 > journal.txt
> 
> and attach journal.txt to this report, too?
> 
> Thanks :-)
 done.

re-initialise wifi.

at install configuration, wifi is not able to be configured as broadcom-ssb package does not appear to support BCM4311 module.

upon reboot and login to desktop, wifi is not enabled.
run drakroam: does not detect my wifi network which is not hidden.
invoke MCC, => set up a new network interface.
choose "wifi".
choose my network, which is now found.
change wireless setting "encryption mode" to "wpa/wpa2 preshared key"
make no other changes and accept all other defaults except "allow user to manage connection" 
connect to network

When grepping for "failed" in report.bug.xz, I see:

Installation failed:
%post(dkms-broadcom-wl-6.30.223.271-45.mga6.nonfree.x86_64) scriptlet failed, exit status 1

Assigning to the kernel & drivers maintainers

@ kernel maintainers
There are 24 "kernel Call Traces" in the journal. Should a separate bug report for them be filed?

CC: (none) => isobuild
Assignee: bugsquad => kernel
Summary: after upgrade Broadcom BCM4311 wifi needs to be re-initialised => after upgrade Broadcom BCM4311 wifi needs to be re-initialised [(%post(dkms-broadcom-wl-6.30.223.271-45.mga6.nonfree.x86_64) scriptlet failed,]
Source RPM: (none) => broadcom-wl-6.30.223.271-45.mga6

@ Ben 

Does this still happen with an upgrade to 6RC ?

Keywords: (none) => NEEDINFO

(In reply to Marja van Waes from comment #7)
> @ Ben 
> 
> Does this still happen with an upgrade to 6RC ?

yes, (i586)

The kernel traces does not matter, they are from a 4.4.30 kernel, but mga6 has a 4.9.xx, if they still happend with 4.9.18-2 or newer, then file a separate bug.

And if you want it to report it against mga5, then you must reproduce the traces with the 4.4.55-1.mga5 kernel...


the dkms build failure comes from dkms seeing installer kernel and tries to build against that, but obviously fails as it inställs a different kernel and devel files... somewhat matching the failing of rebuilding dkms-nvidia* at install time for the same issue.

Anyway, there has been a lot of fixes since the stuff installed in comment 3, so new logs need to be provided....

But you could wait until ennael provides new RC isos... iirc she planned to start with them yesterday...

CC: (none) => tmb

Note than we can check for the DURING_INSTALL variable and then do nothing in order to prevent such error...
And/or prevent the scriptlet to ever fail

CC: (none) => thierry.vignaud

Akien is right, this is a duplicate of bug 20155

*** This bug has been marked as a duplicate of bug 20155 ***

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