I had a grub.cfg issue and fixed it, using 0,1 to orient it properly.
insmod ext2
set root=(hd0,1)
menuentry "GNU/Linux, Linux 3.13.3-lfs-7.5" {
linux /boot/vmlinuz-3.13.3-lfs-7.5 root=/dev/sdb1 ro
}
It was (hd0,2), which didn't work.
However, if I boot with "root=/sdb1 ro" it just fr
On 08/23/2014 09:15 AM, Ronnie van Aarle wrote:
One last thing, there is no need to change your kernel modules from
linked to builtin. They are stored in /boot/modules and if you see the
four penquins, this means grub is setup right and your system has
acces to that path.
I never see fou
On Sat, Aug 23, 2014 at 06:19:07PM +0200, Ronnie van Aarle wrote:
> I just googled grub configuration to make sure.
>
For the last time, please do NOT top post on this list.
> Unless you explicitly embed the grub menu configuration options in the grub
> image, grub loads its configuration file
I just googled grub configuration to make sure.
Unless you explicitly embed the grub menu configuration options in the grub
image, grub loads its configuration file from /boot/grub/grub.cnf.
This means that system bios provides access to the storage device
containing the boot files.
Hardware dev
Ronnie van Aarle wrote:
One last thing, there is no need to change your kernel modules from linked
to builtin. They are stored in /boot/modules and if you see the four
penquins, this means grub is setup right and your system has acces to that
path.
Op 23 aug. 2014 14:44 schreef "Ronnie van Aarle"
On Sat, Aug 23, 2014 at 03:15:46PM +0200, Ronnie van Aarle wrote:
> One last thing, there is no need to change your kernel modules from linked
> to builtin. They are stored in /boot/modules and if you see the four
> penquins, this means grub is setup right and your system has acces to that
> path.
One last thing, there is no need to change your kernel modules from linked
to builtin. They are stored in /boot/modules and if you see the four
penquins, this means grub is setup right and your system has acces to that
path.
Op 23 aug. 2014 14:44 schreef "Ronnie van Aarle"
het volgende:
> If your
If your udev and devtempfs are funtioning correcty, you might want to check
the mountpoints in /etc/fstab. You can boot debian and enter fdisk -l to
see how it is configured there to get a clue but still you need to sort out
the right path descriptors yourself, because when you run the kernel from
In /var/log on your usb drive you can find several logs. Those also include
error messages. Most common boot issues are allready solved and you can
find solutions on the forums.
Op 23 aug. 2014 07:56 schreef "Patrick Kennedy" het
volgende:
> Speaking of not compiling in things as modules, when I
Speaking of not compiling in things as modules, when I do the following
after "make defconfig" -
cat .config | grep =m
I see quite a few modules. Should I replace all =m with =y ? I mean,
obviously, I tried that too, but it doesn't fix my boot problem. When my
LFS boots, it says: Error: unknow
Oh!
On Thu, Aug 21, 2014 at 10:24 PM, Hazel Russman
wrote:
> On Thu, 21 Aug 2014 21:59:08 +0800
> Patrick Kennedy wrote:
>
> > Okay, it crashed and burned gloriously, and I botched the grub to
> > boot. ;-)
> >
> > After some studies on grub, I can now boot my distro Debian from the
> > prima
On Thu, 21 Aug 2014 21:59:08 +0800
Patrick Kennedy wrote:
> Okay, it crashed and burned gloriously, and I botched the grub to
> boot. ;-)
>
> After some studies on grub, I can now boot my distro Debian from the
> primary hard drive via grub commands...very cool. I can also attempt
> to boot my
Okay, it crashed and burned gloriously, and I botched the grub to boot. ;-)
After some studies on grub, I can now boot my distro Debian from the
primary hard drive via grub commands...very cool. I can also attempt to
boot my LFS from auxiliary hard drive, and it starts to boot up, and I see
four
13 matches
Mail list logo
