LinuxQuestions.org
Page 2 of 3 1 2 3
Show 50 post(s) from this thread on one page

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   upgrading kernel with uefi bios (https://www.linuxquestions.org/questions/slackware-14/upgrading-kernel-with-uefi-bios-4175633661/)

mrapathy 07-10-2018 07:55 PM
Quote:
Originally Posted by Poprocks (Post 5877963)
Could you run ls -l in the same directory.
sorry could you please be more specific?

Poprocks 07-10-2018 08:10 PM
Code:
cd /boot/efi/EFI/Slackware
ls -la

mrapathy 07-10-2018 08:18 PM
Code:
bash-4.3$ cd /boot/efi/EFI/Slackware/
bash-4.3$ ls -la
total 32648
drwxr-xr-x 2 root root    1024 Jul 10 17:05 .
drwxr-xr-x 5 root root    1024 Jul  3 17:07 ..
-rwxr-xr-x 1 root root    468 Jul 10 17:02 elilo.conf
-rwxr-xr-x 1 root root  239720 Apr  1  2016 elilo.efi
-rwxr-xr-x 1 root root 7630144 Jul  9 12:23 vmlinuz
-rwxr-xr-x 1 root root 7630144 Jul 10 01:55 vmlinuz-old
-rwxr-xr-x 1 root root 8962384 Jul 10 17:00 vmlinuz-tv
-rwxr-xr-x 1 root root 8962384 Jul 10 17:01 vmlinuz-tv2

Poprocks 07-10-2018 10:42 PM
I honestly don't know, sorry. I don't see anything wrong with your elilo.conf. I feel like something went wrong on the kernel build. Try running "file vmlinuz*" in your /boot/efi/EFI/Slackware directory just to do a sanity check...

mrapathy 07-10-2018 11:00 PM
bash-4.3$ cd /boot/efi/EFI/Slackware/
bash-4.3$ file vmlinuz*
vmlinuz: Linux kernel x86 boot executable bzImage, version 4.4.14 (root@hive64) #2 SMP Fri Jun 24 13:38:27 CDT 2016, RO-rootFS, swap_dev 0x7, Normal VGA
vmlinuz-old: Linux kernel x86 boot executable bzImage, version 4.4.14 (root@hive64) #2 SMP Fri Jun 24 13:38:27 CDT 2016, RO-rootFS, swap_dev 0x7, Normal VGA
vmlinuz-tv: Linux kernel x86 boot executable bzImage, version 4.17.2 (root@RoughRider2) #1 SMP Tue Jul 10 15:32:27 CDT 2018, RO-rootFS, swap_dev 0x8, Normal VGA
vmlinuz-tv2: Linux kernel x86 boot executable bzImage, version 4.17.2 (root@RoughRider2) #1 SMP Tue Jul 10 15:32:27 CDT 2018, RO-rootFS, swap_dev 0x8, Normal VGA
bash-4.3$

Didier Spaier 07-11-2018 11:51 AM
I also think that the issue is rather with you kernel building that with the boot loader.

You can check doing this:
  • Boot with a working (genuine) kernel.
  • Run liloconfig with standard options.
  • Edit /etc/lilo.conf as you did for elilo.conf
  • Set you firmware to boot in legacy mode
  • Check that the alternate kernels work
You can put lilo in the MBR as in UEFI mode it is not used at all, so you should be able to boot in Legacy or UEFI mode as you like.

mrapathy 07-11-2018 01:12 PM
I have win10 which if I understand correctly needs uefi bios enabled. I was using legacy mode and had no trouble with kernelwhile legacy bios was enabled.

Didier Spaier 07-11-2018 01:41 PM
Was it with the same custom kernels?
  • If no, try tentatively to check your custom kernels
  • If yes, try to use grub instead of elilo.

mrapathy 07-11-2018 01:51 PM
It was with the same kernel version. I reinstalled slackware and win10 after changing bios to uefi. I used same kernel file and patch. I think I will try grub.

mrapathy 07-11-2018 07:17 PM
I installed grub and my kernel seems to be working now. somewhat disappointed elilo didnt work out for me. you guys seem to install kernels so effortlessly with elilo, in fact easier than using legacy bios and lilo though I was well familiar with legacy bios and lilo.

phalange 07-11-2018 07:29 PM
Quote:
Originally Posted by mrapathy (Post 5878296)
I installed grub and my kernel seems to be working now. somewhat disappointed elilo didnt work out for me. you guys seem to install kernels so effortlessly with elilo, in fact easier than using legacy bios and lilo though I was well familiar with legacy bios and lilo.
Honestly, I don't very often hear anyone say "GRUB solved my problem." That's good that it works though. I was totally new to elilo when I started using Slackware but I've really come to like it.

linuxtinker 07-11-2018 07:33 PM
This might be a little late but I use this script to update my kernel all I do is feed it kernel version number .Also it replaces the old kernel if you wanted to keep the old one it just needs a little modification..



makeboot.sh :
Code:
cd ~
cd /boot
./mkini.sh $1
echo Made Initrd Moving to EFI Directory
cd /boot/efi/EFI/Slackware/
echo copying vmlinuz-generic-$1
cp /boot/vmlinuz-generic-$1 ./vmlinuz-generic
echo copying new initrd.gz
cp /boot/initrd.gz ./initrd.gz

cd ~
my elilo.conf

Code:

chooser=simple
delay=1
timeout=1
#
image=vmlinuz-generic
        label=vmlinuz-generic
        initrd=initrd.gz
        read-only
        append="root=UUID=dd19f790-27af-44c2-9a29-5ab7bc2cfcbd vga=normal ro"

laprjns 07-11-2018 07:36 PM
Your elilo.conf has /dev/sda6 as your root file system. After reinstalling both Window 10 and Slackware are you sure that it still being detected as /dev/sda6. I believe grub uses UUID instead of the kernel name for device naming. I have seen several problems on multiboot system when I don't use persistent device names (i.e UUID) in my elilo.conf file. One of my hopes for Slackware 15 is that they go to persistent device naming in both eliloconfig and fstab.

mrapathy 07-11-2018 08:18 PM
My root device is sda6 though maybe UUID use would fix things.

Things are running ok with grub installed now. I got the custom kernel I made to boot.

mrapathy 07-11-2018 10:24 PM
I managed to find this thread on LQ Slackware section
https://www.linuxquestions.org/quest...mb-4175617952/
elilo does not boot >8mb kernel

I am using Slackware 14.2 and the custom kernel I want to boot are bigger than 8mb. My default kernel is 4.4.14 Huge which is 7.3mb my custom kernel is 8.5mb and 8.6mb

anyone know a fix?
just tried booting generic kernel and it loaded only to give me a kernel panic which is something I havent had before its not great but its progress.
couldnt load vfs on block 8,6


All times are GMT -5. The time now is 05:22 AM.
Page 2 of 3 1 2 3
Show 50 post(s) from this thread on one page