You need to add the debian definition as a menu-entry in the
grub-bootloader section of your config.scm system definition file and
the do another "guix system reconfigure" which will reconfigure grub as
part of the reconfigure.
For example I did something similar here (you will need to change the
linux and linux arguments to match yours (src:
https://codeberg.org/ghiknt/notebook-whk-name/src/branch/wip-org-mode-conversion/cookbook/debian-to-guix/index.org#headline-19
)...
|(bootloader (bootloader-configuration (bootloader grub-bootloader)
(targets '("/dev/vda")) (menu-entries ;; Add additional boot entries
(list (menu-entry ;; VPS Debian 12 - values taken from (label
"debian") ;; its grub.cfg (linux "/boot/vmlinuz-6.1.0-41-amd64")
(linux-arguments '("root=UUID=9a4a0c40-862e-45a3-8c13-e732e6e052e0
ro net.ifnames=0 biosdevname=0 quiet")) (initrd
"/boot/initrd.img-6.1.0-41-amd64"))))))|
Cheers,
W
On 2/16/26 21:54, Eduardo Mercovich wrote:
"Dear all.
I started my migration tu guix, and thanks to everyone's advice it is
going relatively smooth. More than that, I am really starting to learn
guix as OS. Thank you all very much. :)
I noted some UX issues and will report them, with possible alleviating
actions, in another thread so in this one will focus on an unexpected
issue I found that could be relevant to other new, non guix specialist
people and may have non trivial consequences.
The path to guixdom I choose was -thanks to Ekaitz great suggestion-
to have a dual boot installation for a while. So used the weekend for
that and after doing a backup I used 'parted' to resize my current
Debian partition, made 200 Gb of space for guix, followed the
installation and could boot on guix. Congratulations! Except that
along with these great news I found that the new grub ignored the
other, existing and already working partition that could be booted (an
old Debian).
So now I can boot on guix, mount and access that partition, even read
and write it, but cannot boot from there to work (yes, you can imagine
my emotional state right now, ending Monday, sorry if my words
transpire that). ;D
Parted shows this info:
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
Modelo: Samsung SSD 970 EVO Plus 500GB (nvme)
Disco /dev/nvme0n1: 500GB
Tamaño de sector (lógico/físico): 512B/512B
Tabla de particiones: msdos
Banderas de disco:
Número Inicio Fin Tamaño Tipo Sistema de ficheros Banderas
1 1049kB 269GB 269GB primary ext4
3 269GB 483GB 215GB primary arranque
2 483GB 500GB 16,8GB extended
5 483GB 500GB 16,8GB logical linux-swap(v1) swap
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
We can see the 500 Gb ssd disk, with 4 partitions:
1. Debian (269 Gb)
2. I have no idea (16 Gb)
3. Guix (215 Gb)
5. Swap, created by Debian (16 Gb)
The (I think) relevant section of the old /boot/grub/grub.cfg is:
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class
gnu --class os $menuentry_id_option
'gnulinux-simple-6fe52b2e-dd43-4a9b-b5e9-4c05fdc5975f' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
search --no-floppy --fs-uuid --set=root
6fe52b2e-dd43-4a9b-b5e9-4c05fdc5975f
echo 'Loading Linux 4.19.0-27-amd64 ...'
linux /boot/vmlinuz-4.19.0-27-amd64
root=UUID=6fe52b2e-dd43-4a9b-b5e9-4c05fdc5975f ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-4.19.0-27-amd64
}
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
Rounding up: the partition is there, I can access it's information
(including the grub.cfg file and everything), but I don't know in
which file I have to add what information in guix, or what command to
run after to update grub, so as to be able to have a working dual boot
machine.
I really searched on the web and read a lot of the manual (which is
clear, but doesn't allow me to define what to do because it seems I
still don't really understand enough some fundamental ideas), but for
my life I still can't find that precise information.
I would be very grateful if anyone can point me in any useful direction.
As always, thanks a lot for sharing time and passion. :)
Best...
