Well, I see parts of both (Grub and LILO) bootloaders installed.
Do you remember, which one do you installed and configured during installation? what does Code:
ls -l /media/boot/grub And what is the output of Code:
cat /media/etc/lilo.conf Please, wrap the outputs into tags . It helps a lot to read your posts. |
Hi Teufel ,
> Well, I see parts of both (Grub and LILO) bootloaders installed. > Do you remember, which one do you installed and configured during installation? The last one, LILO. > what does > Code: > > ls -l /media/boot/grub > > shows? > Code:
total 32 > Code: > > cat /media/etc/lilo.conf > > command? > Code:
# LILO configuration file > Please, wrap the outputs into tags . It helps a lot to read your posts. OK, now better ? Thanks, see you. |
mount /dev/sda1 and post what is on it.
|
What might be there? It's a swap. I doubt ls will show anything on swap partition:
Code:
Device Boot Start End Blocks Id System Since you are using huge kernel it shouldn't be a kernel module issue (assuming you are using Live media with the same kernel). And I see that you have both Grub and Lilo installed. It might cause a mess. Your lilo.conf seems fine, and points to correct partition, so I'd suggest to chroot into your installation from live media and run "lilo" once more. Keep in mind, you have to run "lilo" command on every lilo.conf changes. Exit chroot, shut down PC (do not forget to detach any usb sticks that attached, they might change drives enumeration order) and try to boot. Added: How to chroot: Boot with your media, open terminal and run as root: Code:
mount /dev/sda2 /mnt http://i.imgur.com/paEx2nQ.jpg select "Skip" option. And at this stage: http://i.imgur.com/Y6uB7fg.jpg select "MBR". When liloconfig exited (cursor at command line starts to blinking), continue with "lilo" and "exit" Using this ISO I installed Slackware and booted. |
Misread the partition table was looking for the efi patition and if there is an elilo configuration file and if so what was in it.
|
.deleted.
|
> Today, 03:34 AM #18
> colorpurple21859 Hi colorpurple21859 , > > mount /dev/sda1 and post what is on it. For me, /dev/sda1 is my Linux swap partition. I try with /dev/sda2 which is my Linux root partition. Code:
total 180 ---------- Post added 01-12-15 at 03:40 PM ---------- > Today, 04:19 AM #19 > Teufel Hi Teufel , > > What might be there? It's a swap. I doubt ls will show anything on swap partition: > Code: > > Device Boot Start End Blocks Id System > /dev/sda1 2048 4196351 2097152 82 Linux swap > Yes, correct. > @xavi_slacky > Since you are using huge kernel it shouldn't be a kernel module issue (assuming you are using Live media with the same kernel). > And I see that you have both Grub and Lilo installed. It might cause a mess. > Your lilo.conf seems fine, and points to correct partition, so I'd suggest to chroot into your installation from live media and run "lilo" once more. Keep in mind, you have to run "lilo" command on every lilo.conf changes. > Exit chroot, shut down PC (do not forget to detach any usb sticks that attached, they might change drives enumeration order) and try to boot. > > Added: > How to chroot: > Boot with your media, open terminal and run as root: > Code: > > mount /dev/sda2 /mnt > mount -t proc none /mnt/proc > mount -o bind /dev /mnt/dev > mount -o bind /sys /mnt/sys > chroot /mnt /bin/bash > liloconfig > lilo > exit > > When running liloconfig, at this stage: > http://i.imgur.com/paEx2nQ.jpg > select "Skip" option. > And at this stage: > http://i.imgur.com/Y6uB7fg.jpg > select "MBR". > When liloconfig exited (cursor at command line starts to blinking), continue with "lilo" and "exit" > I don't get LILO ncurses menu. > Using this ISO I installed Slackware and booted. I following yours step to step but I get same initial issue. More ideas ? Thanks, see you. |
You could try running pkgtool from the chroot and try to reinstall lilo.
|
How new is your system? Do you know if it is UEFI or is it BIOS based? If it is UEFI, we'll work on ELILO, if it is BIOS based, we'll work on regular LILO. Knowing this should help us better help you.
Also, did you do a full install of Slackware? |
> Today, 04:05 PM #23
> JackHair Hi JackHair , > > You could try running pkgtool from the chroot and try to reinstall lilo. I try running pkgtool from chroot but, I don't know install LILO from USB stick installation. How can I install it from pkgtool on chroot ? Thanks, see you. ---------- Post added 01-12-15 at 05:21 PM ---------- > Today, 04:06 PM #24 > bassmadrigal Hi bassmadrigal , > > How new is your system? Do you know if it is UEFI or is it BIOS based? If it is UEFI, we'll work on ELILO, if it is BIOS based, we'll work on regular LILO. Knowing this should help us better help you. > Is an X64 bit. I have UEFI BIOS boot option. How can I install ELILO ? > Also, did you do a full install of Slackware? Yes. Thanks, see you. |
I try running pkgtool from chroot but, I don't know install LILO from USB stick installation.
How can I install it from pkgtool on chroot ? Thanks, see you. In pkgtool go to "setup" then in the list find lilo (or elilo if you have an uefi mobo). |
If you aren't forcing UEFI right now and are doing a BIOS emulation, it may be easier to just stick with BIOS and using LILO. If you decide to stick with this route, what happens if you do the following (after booting off the Slackware install disc)?
Code:
mount /dev/sda2 /mnt If the lilo test seems to run fine without any errors (there might be a warning about LBA32, which you can safely ignore), then you can go ahead and run lilo without any arguments. If you're not sure if the output is an error or not, feel free to paste it here and we can let you know. If this doesn't work, you may already be running in UEFI mode, but if you didn't partition for /boot/efi, then you're going to run into problems. See the README_UEFI.TXT on using UEFI on Slackware. http://slackbuilds.org/mirror/slackw...EADME_UEFI.TXT Also, this may be considered nitpicking, but it is much easier to see what you're replying to if you encase it in quote tags (square brackets [word] around the word (replace word with quote) at the start and square brackets around the word with a fordward slash in front of it at the close [/word]). To me, it is a bit jarring to see the > greater than symbol on a forum (since I hardly even see it in email anymore thanks to gmail). Quote:
|
liloconfig doesn't show ncurses menu? Did you really run it from chroot?
You can install Grub instead of LILO, I replaced LILO with Grub using the same Slint ISO. And I created here exactly the same partitions layout: sda1 is swap and sda2 is root (/). Try this when booted into Slint live system: Code:
mount /dev/sda2 /mnt If you can't install Grub, it might be due to inconsistent Slint ISO. Anyway, try the code above. |
Well xavi_slacky, as you used a Slint installer, I assume that I ought you some support or after sales service ;)
First, please confirm that :
Code:
lsblk -o name,type,model,size,fstype,mountpoint,label,uuid As others have pointed out, to make the text you copy here easier to read, please place the results of the command inside code tags. In the same vein, when you quote another post, please use the quote tags. |
> Today, 05:30 PM #26
> JackHair Hi JackHair , > > In pkgtool go to "setup" then in the list find lilo (or elilo if you have an uefi mobo). Which list ? Thanks, see you. ---------- Post added 01-12-15 at 09:34 PM ---------- > Today, 05:57 PM #27 > bassmadrigal Hi bassmadrigal , > > If you aren't forcing UEFI right now and are doing a BIOS emulation, it may be easier to just stick with BIOS and using LILO. If you decide to stick with this route, what happens if you do the following (after booting off the Slackware install disc)? > > Code: > > mount /dev/sda2 /mnt > mount -o bind /dev /mnt/dev > mount -o bind /proc /mnt/proc > mount -o bind /sys /mnt/sys > chroot /mnt > lilo -vt #this just does a test run of everything to show you any warnings that may crop up post the output of this > Code:
/ [To install, type setup] # mount /dev/sdb2 /mnt/ Thanks, see you. |
All times are GMT -5. The time now is 11:40 AM. |