IRC channel logs

2020-10-14.log

back to list of logs

<Zambonifofex> https://usercontent.irccloud-cdn.com/file/J0Bui1gC/20201013_193508.jpg
***Server sets mode: +nt
<damo22>Zambonifofex: did you try sd0s1 instead of hd0s1?
<Zambonifofex>That is exactly what I did!
<damo22>did it work?
<Zambonifofex>Check the last image I shared! (Yes.)
<Zambonifofex>damo22: I feel like I should be more appreciative of your advice, because if I had not figured it out by myself, it’d have been really important and useful to me!
<damo22>ok cool
<Zambonifofex>Sometimes I feel like the most “difficult” kinds of problems I hae tried to solve (“difficult” exclusively in terms of time spent on them) turned out to be really small changes.
<youpi>gnu_srs: well, we can build libdrm "for conveniency", but it won't actually work this way
<youpi>as soon as a structure passed to an ioctl contains a pointer, it will break
<rekado>Zambonifofex: did you dd the Guix-generated disk image to your hard disk? Was there more to be done after that?
<rekado>Zambonifofex: did you dd the Guix-generated disk image to your hard disk? Was there more to be done after that?
<Zambonifofex>rekado: Yeah, just `dd` worked. All I have to do now is to press “e” on GRUB and modify “hd0s1” to “sd0s1”, then press F10 to boot.
<Zambonifofex>More precisely, I (1) used `qemu-img` to convert the Guix image from the download page to raw format, (2) stored in a flash drive as a regular file, (3) `dd` Arch Linux to a different flash drive, (4) boot from the Arch flash drive, (5) mount the Guix flash drive, (6) `dd` Guix onto the hard disc from Arch.
<Zambonifofex>Ah, also, I had to disable “secure boot” and change modes to “CSM OS” on my BIOS/setup.
<Zambonifofex>Hopefully that all makes sense! 🤔 😅
<rekado>Zambonifofex: thanks! I’ll see if I can build it directly in raw format and dd it onto a spare disk.
<Pellescours>I am trying to launch the kernel in x64 bits and I have a strange error. The program crash at instruction: mov %cr4, %eax
<Pellescours>I don't understand why the processor would refuses to read a register
<Pellescours>I am using qemu and gdb
<jrtc27>if it says %eax then it's not 64-bit?
<jrtc27>mov with control registers is always 64-bit in long mode and ignores REX.W
<jrtc27>what exception do you get?
<Pellescours>This append when I tried to change to 64 mode, I was still in 32 bit mode
<Pellescours>I have this with gdb:
<Pellescours>Python Exception <class 'gdb.MemoryError'> Cannot access memory at address 0x41000010:
<Pellescours>#0 boot_entry () at ../x86_64/boothdr.S:85
<Pellescours>otherwise in qemu I have the CPU register values