Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #264672 > unrolled thread
| Started by | "Rick Thomas" <rick.thomas@pobox.com> |
|---|---|
| First post | 2023-12-13 03:10 +0100 |
| Last post | 2023-12-16 02:10 +0100 |
| Articles | 3 on this page of 23 — 12 participants |
Back to article view | Back to linux.debian.user
Is it safe to install Bookworm on a new machine now? "Rick Thomas" <rick.thomas@pobox.com> - 2023-12-13 03:10 +0100
Re: Is it safe to install Bookworm on a new machine now? Greg Wooledge <greg@wooledge.org> - 2023-12-13 03:30 +0100
Re: Is it safe to install Bookworm on a new machine now? "Rick Thomas" <rick.thomas@pobox.com> - 2023-12-13 04:00 +0100
The bug (was: Is it safe to install Bookworm on a new machine now?) Stefan Monnier <monnier@iro.umontreal.ca> - 2023-12-13 05:10 +0100
Re: The bug (was: Is it safe to install Bookworm on a new machine now?) David Wright <deblis@lionunicorn.co.uk> - 2023-12-13 05:50 +0100
Re: The bug (was: Is it safe to install Bookworm on a new machine now?) <tomas@tuxteam.de> - 2023-12-13 06:40 +0100
Re: The bug (was: Is it safe to install Bookworm on a new machine now?) Geert Stappers <stappers@stappers.nl> - 2023-12-13 07:30 +0100
Re: The bug John Crawley <john@bunsenlabs.org> - 2023-12-13 08:40 +0100
Re: The bug Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-12-13 14:50 +0100
Re: The bug Stefan Monnier <monnier@iro.umontreal.ca> - 2023-12-13 16:00 +0100
Re: The bug <tomas@tuxteam.de> - 2023-12-13 16:20 +0100
Re: The bug Greg Wooledge <greg@wooledge.org> - 2023-12-13 16:40 +0100
Re: The bug Pocket <pocket@columbus.rr.com> - 2023-12-13 17:50 +0100
Re: The bug <tomas@tuxteam.de> - 2023-12-14 06:50 +0100
Re: The bug Kevin Price <kp@osnanet.de> - 2023-12-14 22:30 +0100
Re: The bug Stefan Monnier <monnier@iro.umontreal.ca> - 2023-12-15 15:50 +0100
Re: The bug Kevin Price <kp@osnanet.de> - 2023-12-15 16:20 +0100
Re: The bug Greg Wooledge <greg@wooledge.org> - 2023-12-13 16:20 +0100
Re: The bug Tixy <tixy@yxit.co.uk> - 2023-12-13 18:10 +0100
Re: The bug (was: Is it safe to install Bookworm on a new machine now?) "Gareth Evans" <donotspam@fastmail.fm> - 2023-12-13 06:40 +0100
Re: Is it safe to install Bookworm on a new machine now? Kevin Price <kp@osnanet.de> - 2023-12-14 18:50 +0100
Re: Is it safe to install Bookworm on a new machine now? John Crawley <john@bunsenlabs.org> - 2023-12-15 05:40 +0100
Re: Is it safe to install Bookworm on a new machine now? John Crawley <john@bunsenlabs.org> - 2023-12-16 02:10 +0100
Page 2 of 2 — ← Prev page 1 [2]
| From | Kevin Price <kp@osnanet.de> |
|---|---|
| Date | 2023-12-14 18:50 +0100 |
| Message-ID | <HKY0p-dzAd-13@gated-at.bofh.it> |
| In reply to | #264672 |
Rick: Am 13.12.23 um 02:47 schrieb Rick Thomas: > Is there a netinst iso that I can use to safely install Bookworm (stable) on a new PC? Possibly yes, but please read on. > If so, where can I download it from? Please always use official sources: https://www.debian.org/CD/ > If not, how much longer is it likely to be before one exists? My worst guess is 12.5, in a few months from now. But 12.4 might likely work perfectly fine for you, out of the box. If not, you can make 12.4 work for you right now. Here are some of my findings, assumptions, and educated guesses for you regarding "the bug". Hoping to help you, no guarantees. Any risks are yours, as always. "The bug" (Bug#1057967 & Bug#1057969) occurs only in kernel version 6.1.66-1 (package -6.1.0-15, released with bookworm 12.4). No other debian kernel version has this bug. It might not affect you, and it can be remedied/worked around. If it does affect you, it won't fry your filesystem, but the computer won't run properly under this kernel, causing a lots of problems, making your computer largely unusable during this runtime. I don't see any great danger in giving it a shot, if you're reasonably careful to understand, and prepare for what might go wrong. (The much more dangerous kernel would be its predecessor, 6.1.64-1, package 6.1.0-14, which was briefly released in bookworm 12.3, and very quickly retracted. It might toast your ext4 filesystem. (Bug#1057843) For that very reason, no official 12.3 media were ever publically released. See the latest messages at https://www.debian.org/News/2023/ ) "The bug" (Bug#1057967, Bug#1057969) is within the kernel module cfg80211, which is used for Wifi in general, regardless of your adapter's specific WiFi driver. If your computer has WiFi, even if you don't intend to use it, debian (including installer) will by default try to load the appropriate driver modules, which will pull in cfg80211. In case of the non-free broadcom-sta driver, binary "wl.ko" is known to trigger the bug in cfg80211 in 6.1.66-1/6.1.0-15, which then causes lots of problems during runtime. Whether any other WiFi drivers trigger this bug as well, IDK. The _free_ broadcom driver (see https://wiki.debian.org/bcm43xx ) doesn't seem to trigger this for me, YMMV. Non-free drivers are not shipped in official bookworm media, but if you actively choose non-free during the installation process or later, broadcom-sta might then be installed, triggering "the bug". Don't confuse this with non-free firmware. This is indeed shipped in official bookworm media, but most likely won't trigger "the bug". In your case, I'd try the bookworm 12.4 installer straight. By chance, everything might turn out well. If promblems occur that look like "the bug", I'd try one or more of the following possible remedies/workarounds, each of which _might_ suffice, but might cause some error messages or other issues. As soon as you've updated to 6.1.67-1 (6.1.0-16, about to come), any remedies/workarounds should be safe to be reverted. Maybe try the least inconvenient ones first. I haven't tested all of them. * Avoid "non-free". "non-free-firmware" should be O. K. * Turn off your physical RF kill switch. * Physically remove your WiFi adapter. * Blacklist "cfg80211". * Blacklist "wl". * Use bookworm 12.2 installer media, but not netinst, without internet access. Do not allow kernel updates, until 6.1.67-1/6.1.0-16 is available. Presumably some of the folks in this list/thread might come up with even more possible remedies/workarounds. Again: no guarantees. Some of the above is not confirmed or tested. All you do is at your own risk. But I hope I could help you understand "the bug" and how to possibly avoid it, giving you more confidence in what you're attempting to do. Please feel free to ask any further questions to this list, and any reports I'd welcome here. -- Kevin Price
[toc] | [prev] | [next] | [standalone]
| From | John Crawley <john@bunsenlabs.org> |
|---|---|
| Date | 2023-12-15 05:40 +0100 |
| Message-ID | <HL89r-dFDY-1@gated-at.bofh.it> |
| In reply to | #264740 |
On 15/12/2023 02:48, Kevin Price wrote: > > "The bug" (Bug#1057967 & Bug#1057969) occurs only in kernel version > 6.1.66-1 (package -6.1.0-15, released with bookworm 12.4). No other > debian kernel version has this bug. It might not affect you, and it can > be remedied/worked around. If it does affect you, it won't fry your > filesystem, but the computer won't run properly under this kernel, > causing a lots of problems, making your computer largely unusable during > this runtime. > --- > As soon as you've > updated to 6.1.67-1 (6.1.0-16, about to come), any remedies/workarounds > should be safe to be reverted. > --- > Presumably some of the folks in this list/thread might come > up with even more possible remedies/workarounds. If you don't want to wait for 6.1.67-1 to arrive in Bookworm stable, it is available in bookworm-proposed-updates [1][2], so one workaround would be to temporarily add that repository [3] to apt sources before upgrading. Debian point release 12.4 has just gone out, so right now there are relatively few other packages in bookworm-proposed-updates which might have complicated the situation. That workaround seems to have worked for me today, FWIW. [1] https://tracker.debian.org/news/1485406/accepted-linux-signed-amd64-61671-source-into-proposed-updates/ [2] https://wiki.debian.org/StableProposedUpdates [3] deb https://deb.debian.org/debian stable-proposed-updates main contrib non-free non-free-firmware -- John
[toc] | [prev] | [next] | [standalone]
| From | John Crawley <john@bunsenlabs.org> |
|---|---|
| Date | 2023-12-16 02:10 +0100 |
| Message-ID | <HLrlM-dRIy-5@gated-at.bofh.it> |
| In reply to | #264770 |
On 15/12/2023 13:39, John Crawley wrote: > If you don't want to wait for 6.1.67-1 to arrive in Bookworm stable, it is available in bookworm-proposed-updates [1][2], so one workaround would be to temporarily add that repository [3] to apt sources before upgrading. Debian point release 12.4 has just gone out, so right now there are relatively few other packages in bookworm-proposed-updates which might have complicated the situation. > > [1] https://tracker.debian.org/news/1485406/accepted-linux-signed-amd64-61671-source-into-proposed-updates/ > > [2] https://wiki.debian.org/StableProposedUpdates > > [3] deb https://deb.debian.org/debian stable-proposed-updates main contrib non-free non-free-firmware > 6.1.67-1 is now available from stable-updates, a possibly better option than stable-proposed-updates. https://lists.debian.org/debian-stable-announce/2023/12/msg00002.html -- John
[toc] | [prev] | [standalone]
Page 2 of 2 — ← Prev page 1 [2]
Back to top | Article view | linux.debian.user
csiph-web