IRC has let me know that d-i needs the symlinks in the original ISO are needed,
rufus breaks these and I missed it on https://wiki.debian.org/DebianInstall.
Thanks anyway, I guess.
I have retried with
https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-dvd/debian-testing-amd64-DVD-1.iso
and hit the same issue. Image was written with dd and definitely contains
firmware-iwlwifi_20230210-1_all.deb
I'd also like to note
https://bugs.debian.org/cgi-bin/bugreport.cgi?bu
Adam Baxter (2023-03-06):
> IRC has let me know that d-i needs the symlinks in the original ISO
> are needed, rufus breaks these and I missed it on
> https://wiki.debian.org/DebianInstall.
What about a syslog file with D-I Bookworm Alpha 2 and an image that's
written correctly (i.e. non-broken sy
Source: installation-guide
Followup-For: Bug #1031738
Control: tags -1 patch
Please note: the patch previously offered here isn't suitable; it turns out
that the param limits described in it (32 for Linux, 128 for User Mode Linux)
apply only to the number of argument items that are passed to the '
Processing control commands:
> tags -1 patch
Bug #1031738 [src:installation-guide] installation-guide: documentation about
limits to kernel boot parameters is outdated
Ignoring request to alter tags of bug #1031738 to the same tags previously set
--
1031738: https://bugs.debian.org/cgi-bin/bugr
Package: installation-reports
Severity: normal
Boot method: USB
Image version:
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/11.6.0+nonfree/amd64/iso-cd/firmware-11.6.0-amd64-netinst.iso
Date: 2023-03-02
Machine: Fujitsu LIFEBOOK U9312
Partitions:
Filesystem
On 2023-03-06 08:55 +0100, Cyril Brulebois wrote:
> Fab Stz (2023-03-06):
>> Package: installation-reports
>> Severity: normal
>>
>> I couldn't try on the real system which is an iMac 9.1 (because I don't have
>> physical access to it presently), but there is no package shipping these
>> firmware
Package: installation-reports
Severity: important
Tags: d-i
X-Debbugs-Cc: j...@dpets.uk
Boot method: USB
Image version:
https://gemmei.ftp.acc.umu.se/images/bookworm_di_alpha2/amd64/iso-cd/debian-bookworm-DI-alpha2-amd64-netinst.iso
Date: <6 March 2023>
Machine: Ideapad 5 14
Partitions:
Disk
Hello John,
On 06/03/2023 at 18:19, John Talbut wrote:
It is not clear where to install it but wherever I try I come up with
a message "Unable to install GRUB in /dev/sda" (or the equivalent in
other partitions).
/dev/sda is the USB stick which contains the installer. You cannot
install GR
package: installation reports Boot method: Image version: Data: Machine: External use hdc 1 2 with dual boot windows
I tested it without it as main Output from lspci -knn (or lspci -nn): Basic
system installation checklist: [O] = OK, [E] = Error (describe below), [ ]
= did not try Initial boot:
Hi Dennis,
And thanks for your report.
Dennis van Dok (2023-03-06):
> Using a netboot install image with non-free firmware; the wireless
> card was not detected during the installation so I used the wired
> network adapter instead.
If you have a few minutes to spare, it would be helpful to know
I am installing on an Asus PN51-E1 which includes the Mediatek MT7921e
wifi device.
I came across this bug while trying to install from
https://cdimage.debian.org/cdimage/bookworm_di_alpha2/ netinst iso on
a USB stick.
I see the same error, but what I was trying to debug when I arrived at
this bu
Jamie Wilkinson (2023-03-07):
> I am installing on an Asus PN51-E1 which includes the Mediatek MT7921e
> wifi device.
>
> I came across this bug while trying to install from
> https://cdimage.debian.org/cdimage/bookworm_di_alpha2/ netinst iso on
> a USB stick.
>
> I see the same error, but what
I think I've figured out why we see these errors.
I restarted an Expert mode installation with the latest nightly DI
https://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/
dated
2023-03-07 04:13 size 758M
I ran through the installation to "load installer components from
i
Jamie Wilkinson (2023-03-07):
> I think I've figured out why we see these errors.
I don't think you did.
> So I think the problem here is that the firmware udebs are not
> unpacked before hardware detection starts.
Those are firmware debs, not firmware udebs. And no, they shouldn't be
unpacked
15 matches
Mail list logo