126 entries in 0.756s
trinque: teaser fact: busybox is *half* the size of
grub-2 by LoC
bvt: re efi, i only had a one machine with it, used in-kernel efi stub and efibootmgr (configuration tool, not loader), did not use
grub there
dorion_road: I can see it, I think I read about lilo in the logs, then have stuck with since following the gentoo handbook a few years back, apart from one public toilet efi laptop where I went with
grub.
mircea_popescu: afaik everyone who uses lilo loves lilo and everyone who uses
grub loves
grub. allegedly the former's more fully featured while the later's more narrowly construed.
dorion_road: mircea_popescu
grub may be required if EFI systems are supported. I don't know if lilo is worth saving or if
grub for everything is the better choice.
mircea_popescu: you don't specifically want both lilo and
grub, or do you ?
dorion_road: The starting point is for the bios and bootloader code to be owned by someone under V. Coreboot, LILO and
GRUB (for EFI support) come under V to be beat into human use.
mircea_popescu: other than that, from what i've seen i believe he's probably right, lilo setup possibly fucked your
grub at some juncture. it'd be great to extract the juncture if at all possible.
a111: Logged on 2019-02-10 20:00 mod6: Well, during the information gathering of my blog post, I went to boot back into my never-has-failed me Gentoo installation on my 500Gb SSD. And now I'm getting: "Welcome to
GRUB! \n error no such device: e45d853f-... \n error: unknown filesystem \n Entering rescue mode... \n
grub rescue>" which doesn't let me boot by selecting: linux (hd0,1)/<kernel_name> root=(hd0,3) \n boot different than the normal gr
trinque: I give even odds the lilo step of the script trashed your
grub. one would love to know why.
mod6: files backed up. ok, well, i've re-run `
grub-install /dev/sda &&
grub-mkconfig -o /boot/
grub/
grub.cfg`. we'll see if this resolves it.
mod6: Well, during the information gathering of my blog post, I went to boot back into my never-has-failed me Gentoo installation on my 500Gb SSD. And now I'm getting: "Welcome to
GRUB! \n error no such device: e45d853f-... \n error: unknown filesystem \n Entering rescue mode... \n
grub rescue>" which doesn't let me boot by selecting: linux (hd0,1)/<kernel_name> root=(hd0,3) \n boot different than the normal gr
☟︎ ascii_lander: oh btw i should note, i did not end up having to use
grub trinque: for
grub also, drivers, others
mp_en_viaje: xgamma does nothing. /sys/class/backlight doesn't exist. ye olde
grub trick (GRUB_CMDLINE_LINUX="acpi_backlight=vendor") does nothing.
a111: Logged on 2017-11-17 06:10 mircea_popescu: a v-root for proper box software (bios,
grub, etc) very much in order also, twinned with box standard.
mircea_popescu: a v-root for proper box software (bios,
grub, etc) very much in order also, twinned with box standard.
☟︎ BingoBoingo: The last time I did that there was a
grub with the worms
CompanionCube: any particular reason for lilo over syslinux or
grub?
shinohai: Looks like a half woman/ half
grub emerging from a pond full of shit
phf: err, not hurd, of course,
grub phf: i gave up because integrated intel card and ati card combination required some fancy
grub PEEK/POKE combination, and i didn't want to do
grub ascii_field: resets, tries
grub diddle via simulated keyboard, then proceeds
trinque: that one makes the
grub config file
n6: I still need grub2-mkconfig -o /boot/
grub/
grub.cfg ?
trinque: I think what happened here is that
grub may have switched the default target
trinque: mircea_popescu: mod6: this leads me to believe that the default for
grub has changed
n6: do I need grub2-mkconfig -o /boot/
grub/
grub.cfg ?
trinque: n6: dpaste ls /usr/lib/
grub/*
n6: grub2-install: error: /usr/lib/
grub/pc/modinfo.sh doesn't exist. Please specify --target or
trinque: if I add pc to
grub platforms
n6: ls: cannot access /etc/defaults/
grub: No such file or directory
trinque: but that appears to pertain to the generation of
grub's config, not its installation
trinque: the other place you might've would've been /etc/defaults/
grub n6: I think only edited the grub_platform file to try efi
trinque: your
grub may have all kinds of knobs twiddled depending on what you did to try efi
n6: rub2-install: error: /usr/lib/
grub/usr/lib/
grub/i386-pc/modinfo.sh/modinfo.sh doesn't exist. Please specify --target or --directory. is what im getting.
trinque: how does
grub refer to the system architecture? how does ....
n6: I still only have /usr/lib/
grub/i386-pc/modinfo.sh
n6: so the grub_platform? or you mean another place?
n6: trinque: I still cant get modinfo.sh in an efi folder after changing grub_platforms file and emerge
grub again
n6: no i'm going to stick with the guide and do
grub trinque: n6: that var referencing
grub n6: I'm still running into the same error here "grub2-install: error: /usr/lib/
grub/x86_64-efi/modinfo.sh doesn't exist. Please specify --target or --directory."
decimation:
grub struck me as being about 50x more complex than it needed to be
trinque: what's wrong with
grub 0.9.whatever
trinque: the fail mode of lilo is worse than the fail mode of
grub n6: Yes lilo but not sure how to set it up to replace
grub in this spot
n6: What is regular
grub?
n6: How do I boot without
grub?
jurov: the GRUB_PLATFORMS looks like compile-time setting
jurov: tried to re-merge
grub?
n6: I built the turd to see if it might work, but it still wont let me
grub anything.
mod6: omg and we have
grub that works...
mod6: trinque and I tried to get my thing to work from
grub> for hours one night, perhaps a few different times. if it was simple, we'd have resolved it. it's probably my dumb POS box.
jurov: i do. but some people become enraged upon encountering
grub> prompt
trinque: that should at least clear the
grub hurdle
jurov:
grub can be problematic in any distro
jurov: end up at the
grub> prompt upon reboot << for example this is you're 90% there, use the prompt to find the kernel and boot, then reconfigure
grub from the running system
mod6: <+nubbins`> you can't get a bash prompt? << for instance on my POS box that I bought for $129.00 an x86_64 core2duo, I can't even install the os. All i can do is boot the livecd, do the chroot stuff, and then end up at the
grub> prompt upon reboot. when it comes to my instance in AWS, i've had better luck, but doing stuff for me is so time consuming. in this case, i need to get gcc recompiled with patches to see if we can get past this error we
mod6: Update on gentoo build on physical box: so trinque & I worked on trying to get this
Grub situtation figured out for quite a while lastnight. Seems that maybe something with grub2 doesn't like my hardware.
Grub 0.9x is no longer supported... so I dunno.
mod6: well, after an `ls` at the
grub prompt anyway.
mod6: i'll try it out. i hosed up my
grub; haven't had a chance to tinker/rebuild yet.
danielpbarron: i ran into issues with
grub as well; ended up using the older version
mod6: <+mircea_popescu> mod6 was working on getting one together but im sure he can use help << yeah, certainly on testing. i bought a pos box to use to build a physical gentoo box guide. i messed up something now
grub is unhappy. I havne't been able to take a decent look at it since sunday morning.
mod6: meanwhile, I'm nearly there with this gentoo install on this pos box. i did something funky i think, at the end of lastnight
grub was screwed up. need to figure that out.
mircea_popescu: <mats> how is it possible this has escaped audit all this time << welcome to the wunderbar world of FOSS, aka a chunk of raw meat in the sun, festering with a million
grub eyes
mod6: Alright I've got a Gentoo AMD64 uclibc hardened booted successfully. I basically just had a few minor tweaks to make to the notes; i.e., uclibc version doens't install
grub by default, there is no /etc/locale.gen by default. That kinda thing.