** Changed in: ubiquity (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899678
Title:
No wifi after installation - does not work with secure boot enabled
To
Ok. It's been a long weekend after the release...
I dont see and lines on the sed output that match the modinfo wl.
Double checking dmesg the last lines say
Lockdown: modprobe: unsigned module loading is restricted; see man
kernel_lockdown.7
As a confirmation that the iso install was ok I rein
On Thu, Oct 22, 2020 at 08:35:48AM -, fossfreedom wrote:
> modinfo wl returns a sig_key signature
Ok, but is that value also in the output of mokutil --list-enrolled? You
didn't say.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
The full terminal session is in modprobe.txt but in summary the bcmwl-
kernel-source reinstall was simply:
apt --reinstall install bcmwl-kernel-source
This is a full ISO installation - no extra packages added/nor removed
modinfo wl returns a sig_key signature
The output of the mokutil sed i
Other things to check:
- that after install, a 'modinfo wl' shows it's signed (sig_key, signature,
etc)
- that the sig_key: field in the 'modinfo wl' output matches one of the keys
in the output of: mokutil --list-enrolled | sed -n -e'/X509v3 Subject Key
Identifier:/,/X509v3 Authority Key Ide
What exact commands did you run to force the reinstall bcmwl-kernel-
source? Having MOK generated on ubiquity install, and again after a
reinstall of bcmwl-kernel-source, is concerning; unless you purged quite
a few packages, the MOK should persist.
--
You received this bug notification because
To clarify - the modprobe was not a live-session - this was after a
full disk install.
So - I MOK enrolled after the ubiquity install - no wifi on first
logon. Modprobe wl gave the not permitted error.
I then manually connected and force a reinstall of bcmwl-kernel-source
and subsequently on boo
If you are trying to do the modprobe during the live session, it is
expected that this will not succeed. It's only after MOK enrollment
that these locally-signed modules will be allowed to be loaded by the
kernel under SecureBoot.
If the modprobe works post-reboot and post-MOK-enrollment, then th
ok - just done a fresh entire disk install whilst testing the .2 ISO.
See attached modprobe.txt (for the modprobe - I think you meant 'wl' so
I did that as well.)
I followed up by connecting to the network (RJ45) and reinstalling
bcmwl-kernel-source
I saw the same wl message as per modprobe.
On
and what happens (in dmesg and stdout/stderr) when you try to manually
load the module with 'sudo modprobe bcmwl'?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899678
Title:
No wifi after installa
oddly I don't see anything - see dmesg.txt
However software-properties-gtk says its in use (see software-
properties-gtk.png)
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1899678/+attachment/5425196/+files/dmesg.txt
--
You received this bug notifica
** Attachment added: "software-properties-gtk.png"
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1899678/+attachment/5425197/+files/software-properties-gtk.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
What does dmesg show on the installed system regarding loading of the
bcmwl module?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899678
Title:
No wifi after installation - does not work with secur
'fraid shim-signed with the new 20201021 ISO doesn't do the trick.
I've also tried to delete all the existing mok keys and do a clean
install
so boot and use the "Install Ubuntu Budgie" option. Chose UK and
London. Selected 3rd party checkbox and entered "password" twice for
the secure password
** Attachment added: "mok2.txt"
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1899678/+attachment/5425158/+files/mok2.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899678
Title:
No w
New shim-signed is now on the latest images (20201021).
I'm still not clear what happened when enabling Broadcom from the
installer since it all looks fine to me. Perhaps you could try and let
us know what doesn't work with detailed steps to reproduce? (but
hopefully it does work)
--
You receive
Correct - I ticked the third party checkbox - I needed to-do that so
that I could then enter the secure boot password.
On Wed, 21 Oct 2020 at 12:40, Iain Lane <1899...@bugs.launchpad.net> wrote:
>
> I think the second part (apt install not showing the prompt on next
> boot) is fixed with shim-sign
Just to say - after installation - I was prompted on reboot to enter
my MOK password. So entering the password was accepted and then an
auto-boot took me to the normal login manager - and subsequent login.
On Wed, 21 Oct 2020 at 13:05, David Mohammed wrote:
>
> Correct - I ticked the third party
I think the second part (apt install not showing the prompt on next
boot) is fixed with shim-signed 1.45 as indicated by Andy in comment #8.
But I'm not quite sure about your initial part where the installer
didn't do the same. I can make that happen if I tick to install
proprietary drivers and th
Yeah, fossfreedom, can you tell us what you ticked on the 'install third
party drivers' page?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899678
Title:
No wifi after installation - does not work
Oct 20 17:23:15 ubuntu-budgie ubiquity: /sbin/update-secureboot-policy: 44: 3:
Bad file descriptor#015
Oct 20 17:23:15 ubuntu-budgie ubiquity: Done.#015
looks like when 3rd party drivers box is not ticked (and mok enrolment
pin not configured), and broadcom driver is attempted to be installed,
an
This may be caused by
https://bugs.launchpad.net/ubuntu/+source/mokutil/+bug/1869187.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899678
Title:
No wifi after installation - does not work with sec
Hi Dimitri,
the last time I tested secure boot installation was at 20.04 on this
particular laptop. All was ok at that time.
enc are the installer tarball and the mok results. TIA
** Attachment added: "installation.tar"
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1899678/+attach
** Attachment added: "mok.txt"
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1899678/+attachment/5424745/+files/mok.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899678
Title:
No wif
btw, what is the state of MOK? i.e.
$ sudo mokutil --list-enrolled
$ ls /var/lib/shim-signed
$ ls /var/lib/shim-signed/mok/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899678
Title:
No wifi aft
Can you open bug report against ubiquity with like $ ubuntu-bug ubiquity
?
that would collect all the installer logs, which will help to
investigate this.
Or can you please attach /var/log/installer as a tarball? do check for
any sensitive info there, or feel free to mark this bug report private.
26 matches
Mail list logo
