On Sat 18 Feb 2023 at 09:17:43 (+0800), lsg wrote: > On 2/17/23 22:29, Brian wrote: > > There isn't much you can do about this. It is usually a temporary > > issue thats happens after Linux kernel updates. The installer is > > now out of step. It gets automatically fixed after some time. > > > Thanks! i've thought updating iso image and hard disk installer are > automatic > > it's very frustrating, i've never been so disappointed with debian > > it will be easier if i can determine if they match by matching file > name of iso file with that of vmlinuz and initrd pair (their file > names shall all include same version number) > > i have successfully used bullseye hard disk installation method for > i386 about one month ago, i don't know why it doesn't work this time
I'm not really interested in actually installing an OS at the moment, so I stopped the debian-installer when it gets to the partitioner. What I need to know is how far /you/ got before you received the error you paraphrased as: "No kernel modules found", probably due to kernel mismatch (BTW, it really helps to report error messages precisely.) Here's what I did, and it all worked perfectly (as far as the partitioner step): I downloaded the files you did (here with their SHA256): e482910626b30f9a7de9b0cc142c3d4a079fbfa96110083be1d0b473671ce08d debian-11.6.0-amd64-netinst.iso 7f161a705077f231d282dc4a8961f17c5d4a6182877ca930eca280958f86dfe9 firmware-11.6.0-amd64-netinst.iso and these from http://ftp.us.debian.org/debian/dists/bullseye/main/installer-amd64/current/images/hd-media/ b00b339f8b1aada1841d86650377dd8e7299eaa7f34d0bbf21deb561467015cd vmlinuz ab34a60082dee4b18fe3c1e6131cd27e876d6877a3b81c6490814f0a594608ef initrd.gz Note to Charles: that happens to be the same kernel as on the ISOs, but you must use the hd-media's initrd. I assume that's because it knows how to look for the .iso file. You can't just extract it from the netinst ISO. OK. I placed these four files into /boot on a regular Debian machine. I intended to check both ISOs, so I hid one by appending -hidden to the filename: firmware-11.6.0-amd64-netinst.iso-hidden Next, I edited the file /boot/grub/grub.cfg and added a few lines at the end. You can see where they go by the BEGIN/END and 40: ### BEGIN /etc/grub.d/40_custom ### # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. menuentry "Install Debian via HTTP" { search --no-floppy --label --set=root swan05 linux /boot/vmlinuz initrd /boot/initrd.gz } ### END /etc/grub.d/40_custom ### OK, I use LABELs, and this Debian system's root filesystem is on /dev/sda5 with the LABEL swan05. If you only have a UUID, then that line will become: search --no-floppy --fs-uuid --set=root 12345678-abcd-fedc-0000-1234567890ab or whatever the root filesystem's UUID is. Then I rebooted the system, and when Grub started (blue screen), I downarrow'd to Install Debian via HTTP and pressed Return. A few seconds, and many messages, later I got: ┌───────────────────────────┤ [!!] Select a language ├────────────────────────────┐ │ │ │ Choose the language to be used for the installation process. The selected │ │ language will also be the default language for the installed system. │ │ │ As I say, I went as far as the partitioner. With no firmware for wifi, I had to skip out of configuring the network. I then rebooted to my Debian system, juggled the ISOs' names to: /boot/debian-11.6.0-amd64-netinst.iso-hidden /boot/firmware-11.6.0-amd64-netinst.iso rebooted, and repeated the exercise, with a working wifi network this time. I stopped again at the partitioner step. All that took about fifteen or twenty minutes, but that might be because I've done it before, and the extra grub.cfg lines are in my backups. Cleanup: the extra files in /boot do no harm unless you're short of space. The extra menu will disappear whenever Grub is reconfigured: kernel update, or grub update. Just ignore it. Cheers, David.
