Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
debian x86 install failed - bootloader-config
debian x86 install failed - bootloader-config
installing debian-live-10.7.0-i386-kde+nonfree.iso
Attempting to build debian on an old x86 notebook, installation fails with an informative message,
bootloader-config failed, package grub-efi-amd64 is not available.
this looks like a goof related to the fact that this is a 32bit machine, but
whatever - what do I do about it?
Attempting to build debian on an old x86 notebook, installation fails with an informative message,
bootloader-config failed, package grub-efi-amd64 is not available.
this looks like a goof related to the fact that this is a 32bit machine, but
whatever - what do I do about it?
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 132 times
Re: debian x86 install failed - bootloader-config
Are you sure it's a 32-bit machine? Have you tried booting a 64-bit live ISO image?
Perhaps try the multi-arch netinstall image: https://cdimage.debian.org/cdimage/unof ... ch/iso-cd/
Perhaps try the multi-arch netinstall image: https://cdimage.debian.org/cdimage/unof ... ch/iso-cd/
deadbang
Re: debian x86 install failed - bootloader-config
Yes, it's a 32 bit oldieHead_on_a_Stick wrote:Are you sure it's a 32-bit machine? Have you tried booting a 64-bit live ISO image?
Perhaps try the multi-arch netinstall image: https://cdimage.debian.org/cdimage/unof ... ch/iso-cd/
Re: debian x86 install failed - bootloader-config
One of the problems I'm dealing with is that the network needs "non free" firmware which is not installed. So I have to do this without network.Head_on_a_Stick wrote:Are you sure it's a 32-bit machine? Have you tried booting a 64-bit live ISO image?
Perhaps try the multi-arch netinstall image: https://cdimage.debian.org/cdimage/unof ... ch/iso-cd/
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 132 times
Re: debian x86 install failed - bootloader-config
The image to which I have linked already includes non-free firmware. Do you have a Broadcom card?
And please don't full quote unnecessarily, it degrades the readability of the thread.
EDIT: you can use the "edit" button instead of posting twice in succession.
And please don't full quote unnecessarily, it degrades the readability of the thread.
EDIT: you can use the "edit" button instead of posting twice in succession.
deadbang
Re: debian x86 install failed - bootloader-config
Yea, it's a broadcom card, the message says it needs brcm/brcmxxxxx.bin and I can load it from removable media, butHead_on_a_Stick wrote:The image to which I have linked already includes non-free firmware. Do you have a Broadcom card?
I've so far failed to guess exactly how that can be done. I tried adding the requested file to the root of the iso image, but that
has no visible effect. Unplugging the memory stick I'm installing from and inserting a new stick also seems ineffective.
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 132 times
Re: debian x86 install failed - bootloader-config
The firmware files need to be placed under a /firmware/ directory on the removable medium: https://www.debian.org/releases/stable/ ... 04.en.html
deadbang
Re: debian x86 install failed - bootloader-config
They also apparently need to be packaged in a .deb wrapper, whatever that is. The raw .bin files
are just ignored.
The incantation I found that eventually worked is to install without network, then copy the .bin file
to /lib/firmware/brcm/
reboot and the network works!
My particular card also needed a text file with a lot of parameters, which I also found.
Now for the payload: the necessary files are
-rw-r--r-- 1 root root 400864 Sep 23 01:11 brcmfmac43340-sdio.bin
-rw-r--r-- 1 root root 1620 Jul 5 2020 brcmfmac43340-sdio.txt
which can be acquired at
https://github.com/wkennington/linux-fi ... 0-sdio.bin
https://gist.github.com/spacemeowx2/3fb ... f99e7554b5
are just ignored.
The incantation I found that eventually worked is to install without network, then copy the .bin file
to /lib/firmware/brcm/
reboot and the network works!
My particular card also needed a text file with a lot of parameters, which I also found.
Now for the payload: the necessary files are
-rw-r--r-- 1 root root 400864 Sep 23 01:11 brcmfmac43340-sdio.bin
-rw-r--r-- 1 root root 1620 Jul 5 2020 brcmfmac43340-sdio.txt
which can be acquired at
https://github.com/wkennington/linux-fi ... 0-sdio.bin
https://gist.github.com/spacemeowx2/3fb ... f99e7554b5
-
- Global Moderator
- Posts: 3049
- Joined: 2017-09-17 07:12
- Has thanked: 5 times
- Been thanked: 132 times
Re: debian x86 install failed - bootloader-config
Or in the root directory, as mentioned by the same source.Head_on_a_Stick wrote:The firmware files need to be placed under a /firmware/ directory on the removable medium
This is not correct. The Debian buster installer can use raw firmware files. But I observed that its search algorithm is flawed [1] and has more chances to find firmware packages than raw firmware files. A workaround is to manually mount the filesystem containing firmwares on /media.ddyer wrote:They also apparently need to be packaged in a .deb wrapper, whatever that is. The raw .bin files are just ignored.
[1] The search for firmware files stops at the first volume which can be mounted. The search for firmware packages stops at the first volume which can be mounted and contains *.{deb,udeb,ude} files in its root or /firmware directory. My experience is that success or failure depends on the enumeration order of the installer and firmware media.
Re: debian x86 install failed - bootloader-config
Keep in mind that this interaction occurs in the middle of an raw install process, without internet access. While a file name is mentioned, no path or packagingp.H wrote: [1] The search for firmware files stops at the first volume which can be mounted. The search for firmware packages stops at the first volume which can be mounted and contains *.{deb,udeb,ude} files in its root or /firmware directory. My experience is that success or failure depends on the enumeration order of the installer and firmware media.
is mentioned. Plugging and replugging a different memory stick is going to disrupt the installation in progress. I tried a lot of combinations of putting the .bin
in various directories (/ /bfms /firmware /firmware/bfms ....) and never succeeded. I also never succeeded in ejecting and inserting media, then switching back
to the original install media.
It showed the file names it was looking for - that's indespensible, but it would help a lot if it also showed the paths it searched.
-
- Global Moderator
- Posts: 3049
- Joined: 2017-09-17 07:12
- Has thanked: 5 times
- Been thanked: 132 times
Re: debian x86 install failed - bootloader-config
I did not suggest doing this. Of course you cannot unplug the installer stick, and unplugging and replugging the firmware stick is useless. For instance you can try to swap USB ports before booting the installer so that the firmware stick is enumerated first (as /dev/sdb and the installer as /dev/sdc for example, /dev/sda being the internal drive).ddyer wrote:Plugging and replugging a different memory stick is going to disrupt the installation in progress.
As already explained, the installer looks for firmware only in / and /firmware.ddyer wrote:I tried a lot of combinations of putting the .bin
in various directories (/ /bfms /firmware /firmware/bfms ....) and never succeeded.
The only path it could show would be the destination path, which is irrelevant. See above for the search path.ddyer wrote:it would help a lot if it also showed the paths it searched.
Re: debian x86 install failed - bootloader-config
While I'm complaining about installers, two more things
Why is installing the boot loaded the very last thing? until it is installed, the system is not bootable,
and if the installation fails in any way, you have to redo the entire installation.
The step of connecting to WIFI during install seems only to be able to join
an open network - wpa always fails. Also, once connected to an open network,
dhcp always fails and the network has to be configured manually.
Why is installing the boot loaded the very last thing? until it is installed, the system is not bootable,
and if the installation fails in any way, you have to redo the entire installation.
The step of connecting to WIFI during install seems only to be able to join
an open network - wpa always fails. Also, once connected to an open network,
dhcp always fails and the network has to be configured manually.
-
- Global Moderator
- Posts: 3049
- Joined: 2017-09-17 07:12
- Has thanked: 5 times
- Been thanked: 132 times
Re: debian x86 install failed - bootloader-config
This question is flawed. The bootloader installation is not the last step.ddyer wrote:Why is installing the boot loaded the very last thing?
It is a late step because it depends on earlier steps.
Wrong. The system can be booted with any other bootloader. For instance multiboot setups require only one boot loader, not one per system.ddyer wrote:until it is installed, the system is not bootable
Wrong again. You can finish the installation, then you can repair the boot loader later.ddyer wrote:if the installation fails in any way, you have to redo the entire installation.
Re: debian x86 install failed - bootloader-config
I'm happy to hear about these options, but where can I find the necessary incantations. Afterp.H wrote:Wrong. The system can be booted with any other bootloader. For instance multiboot setups require only one boot loader, not one per system.ddyer wrote:until it is installed, the system is not bootable
Wrong again. You can finish the installation, then you can repair the boot loader later.ddyer wrote:if the installation fails in any way, you have to redo the entire installation.
installing the bootloader fails (presumably due to some screwup related to it being an old x86
machine) I'm left with a system that won't boot. Something magic I can put on a stick?
-
- Global Moderator
- Posts: 3049
- Joined: 2017-09-17 07:12
- Has thanked: 5 times
- Been thanked: 132 times
Re: debian x86 install failed - bootloader-config
There are no incantations or magic. The installer has a rescue mode which allows to reinstall the boot loader (but that will presumably fail until the failure cause is removed) or chroot into the installed system and do whatever it takes to install the boot loader.
Re: debian x86 install failed - bootloader-config
In this case, installing the bootloader failed (reported in a different thread) due to some internal problem,p.H wrote:There are no incantations or magic. The installer has a rescue mode which allows to reinstall the boot loader (but that will presumably fail until the failure cause is removed) or chroot into the installed system and do whatever it takes to install the boot loader.
not due to an io failure. So sure, retrying the installation would fail, and I still have a nonbootable system,
presumably lacking only a bootloader.
Is there a procedure - something like - put an emergency bootloader on a stick, then use it to boot
the system from the main disk?
-
- Global Moderator
- Posts: 3049
- Joined: 2017-09-17 07:12
- Has thanked: 5 times
- Been thanked: 132 times
Re: debian x86 install failed - bootloader-config
I'd rather boot the installer in rescue mode, chroot into the install system and investigate the bootloader installation failure.
With BIOS/legacy boot :
Make sure separated /boot and /usr are mounted, then
With UEFI boot :
Make sure separated /boot, /boot/efi and /usr are mounted, then
With BIOS/legacy boot :
Make sure separated /boot and /usr are mounted, then
Code: Select all
grub-install --force /dev/<internalbootdisk>
Make sure separated /boot, /boot/efi and /usr are mounted, then
Code: Select all
grub-install
efibootmgr
Re: debian x86 install failed - bootloader-config
The install, in keeping with the traditional unix philosophy, rates 1 out of 10 on the friendliness scale.p.H wrote:There are no incantations or magic. The installer has a rescue mode which allows to reinstall the boot loader (but that will presumably fail until the failure cause is removed)
When the installer failed, it offers no information at all about the reason for the failure or likely
actions to take.
In the midst of the installer (not from the live CD), how can I chroot to anywhere?or chroot into the installed system and do whatever it takes to install the boot loader.
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 132 times
Re: debian x86 install failed - bootloader-config
The error messages are on TTY4. I think there's also a log file somewhere.ddyer wrote:When the installer failed, it offers no information at all about the reason for the failure or likely
actions to take.
Use the rescue mode, as already indicated: https://www.debian.org/releases/stable/ ... 06.en.htmlddyer wrote:In the midst of the installer (not from the live CD), how can I chroot to anywhere?
deadbang
Re: debian x86 install failed - bootloader-config
That would be great if I could get to any kind of shell, which I can't. The failed installp.H wrote:I'd rather boot the installer in rescue mode, chroot into the install system and investigate the bootloader installation failure.
With BIOS/legacy boot :
Make sure separated /boot and /usr are mounted, thenWith UEFI boot :Code: Select all
grub-install --force /dev/<internalbootdisk>
Make sure separated /boot, /boot/efi and /usr are mounted, thenCode: Select all
grub-install efibootmgr
leaves the main disk in a state where the native boot loader things nothing is there.
BTW, isn't there a way to run the install process WITHOUT formatting the disk and installing
a new boot loader? The default process doesn't encourage using a pattern that would
allow user data to be preserved when a new OS is being installed.