<SiFuh>
Yes, I was testing large EFI partitions on a very old machine.
<stenur>
it was about syslinux restrictions to find kernel images beyond a special disc sector
<stenur>
i definetely had this problem last in a mindless prepared AlpineLinux VM, that i then had to repartition; it was not the actual error message which lead me there for sure
ty3r0x_ has joined #crux
ty3r0x has quit [Ping timeout: 245 seconds]
<SiFuh>
stenur: ahh I see
<SiFuh>
stenur: I saw one the other day where the iwlwifi firmware selected by the kernel was ty-a0-gf-a0-66.ucode but the wireless card wouldn't be detected but if you forced it to use the old firmware ty-a0-gf-a0-62.ucode it would work.
<stenur>
fun is the new bluetooth thing now first fails, and then, shortly before login comes up, you get a couple of lines again telling you stuff, even how long it took to "upload" the firmware, whatever
<stenur>
intel/ibt-19-32-0.sfi that was
<stenur>
yeah
<cruxbot>
[contrib.git/3.6]: lighttpd: 1.4.66
jue has joined #crux
<cruxbot>
[opt.git/3.6]: mutt: update to 2.2.7
<cruxbot>
[opt.git/3.6]: msmtp: update to 1.8.22
<cruxbot>
[opt.git/3.6]: dar: update to 2.7.7
<cruxbot>
[core.git/3.6]: libtirpc: update to 1.3.3
jue has quit [Read error: Connection reset by peer]
jue_ has joined #crux
jue_ is now known as jue
jue has quit [Read error: Connection reset by peer]
jue has joined #crux
ty3r0x_ has quit [Remote host closed the connection]
ty3r0x_ has joined #crux
ty3r0x_ has quit [Remote host closed the connection]
aardo has quit [Read error: Connection reset by peer]