| Unit193 | pablocastellanos: http://bugs.debian.org/765971 | 01:12 |
|---|---|---|
| pablocastellanos | Unit193: Thank you | 01:12 |
| EHeM | Recommendations of where to ask about a problematic (bug) behavior with GRUB where I'm highly uncertain where the true problem lies? Almost certainly it is inherited from vanilla Debian, but I'm unsure where the actual problematic behavior is. | 17:15 |
| n4dir | well: here? | 17:17 |
| EHeM | I'm trying to get a Raspberry PI to boot -> U-Boot -> GRUB, problem is it appears U-Boot's implementation of the UEFI boot protocol is rather limited; no support for EFI variables, no support for multiple boot targets; hence `{update|install}-grub` pretty well must overwrite /boot/efi/EFI/BOOT, instead of creating /boot/efi/EFI/devuan. | 17:20 |
| n4dir | I for sure can't answer that question. I'd also try the raspberry forum and the IRC channel (assuming they have one) | 17:21 |
| EHeM | I *really* need GRUB since I'm loading something more interesting than a pure kernel (actually loading both Linux kernel and Xen). | 17:23 |
| n4dir | To me it looks as if in this channel Raspberry is not mentioned very often. Hence i'd *also* try the mentioned channels. Perhaps the devuan forum too, at least it is not temporary, as IRC is. But else just wait, perhaps try again, and good luck :-) | 17:25 |
| EHeM | Right now I'm reading this as a GRUB bug inherited from Debian. I believe this flavor of boot setup is close to what SuSE uses (EFI is available on multiple platforms, so is a great common point for boot processes). | 17:28 |
| golinux | How about trying #devuan-arm? | 17:29 |
| golinux | EHeM: ^^^ | 17:30 |
| EHeM | I doubt that is the right channel, this seems to center more on GRUB than on ARM. | 17:32 |
| unixbsd | hi guys | 19:27 |
| clort | hi unixbsd | 20:03 |
| unixbsd | hi clort | 20:12 |
| bbuccianti | hi! | 20:46 |
| gnarface | hi bbuccianti, if you have any questions just ask | 20:57 |
| EHeM | Hmm, and upon looking at more documentation I see something which hints at what the actual issue was... | 21:14 |
| gnarface | EHeM: your use case is rare | 21:16 |
| gnarface | EHeM: a while back someone was talking about doing this in #pinebook or #pinephone on irc.pine64.org though. if you can find them, they may have made some progress (nobody needs grub for arm hardware and nobody needs u-boot for raspberry pi hardware, so there's only a few fringe people trying this i think | 21:18 |
| gnarface | ) | 21:18 |
| gnarface | EHeM: although, if you're going through all this trouble just to get Xen running on a rpi, you might want to consider a different virtualization solution because even if you can get it to work it's unlikely to be worth it unless this project is specifically Xen related | 21:23 |
| gnarface | EHeM: (para-virtualization solutions like linux-vservers might seem like more trouble at first but in the long run, the lower resource load pays for itself) | 21:24 |
| EHeM | gnarface: Resource load isn't an issue. | 22:42 |
| EHeM | If no one ever bothers to accomplish the goal, of course only fringe people will try it since no one will have gotten through to the end. | 22:45 |
| EHeM | There is also a major advantage to another person trying distinct approaches since it means more coverage, more bugs found, and more bugs hopefully squashed. | 22:46 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!