IRC channel logs
2026-02-12.log
back to list of logs
<rrq>is uefi boot of hurd possible? I have a "Surface Go" to test on/with but I'm not sure it has "legacy boot" <youpi>theorically, yes, but probably some pieces are missing <rrq>ok; I'll explore it a bit ... also actually just found an instruction for forcing USB boot in legacy mode on it. So I have 2 lines of attack :) <azeem>do you have an idea why that would be cause I don't see it <azeem>youpi: nevermind, I think it was a thinko in his test script <youpi>azeem: I have no idea either <azeem>12:31 < azeem> youpi: nevermind, I think it was a thinko in his test script <azeem>they ran killall postgres in a loop to trigger signal issues, but with the above patch, that now only sends a signal to the main process, not the other 30 <yang3>Hello, is HP Compaq 8710p compatible with hurd? It has integrated CD/DVD Rom and C2D CPU? <yang3>Or is it only IBM ThinkPads, which are compatible? <azeem>there's no hardware compatibility database, so you will have to see for yourself, and potentionally fix things up <rrq>does anyone have Hurd amd64 booting on a UEFI boot platform? <rrq>I'm getting an mboot load issue with /lib/ld-x86-64.so.1 ... and as I use syslinux boot equipment, I first want to explore the bug-in-syslinux option; so checking if someone has it booting and starting when using grub (efi)? <damo22>i think some legacy bios services would be missing in uefi mode <rrq>.. hmm that load error came from having only 2G RAM. It went away with 4G RAM. Apparently ld-x86-64.so.1 wants to be loaded at 0x01000000 (and up). <rrq>thus, it's starting...though I don't get serial console output <rrq>yes. I deleted the log; maybe it was 0x10000000 (?) <rrq>right. yes; so then I'm not sure why it stopped the load error when I gave it 4G RAM... I may need to use gdb setup