SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Alright. Assume I already have my initrd.gz. Why can't I just make grub.cfg writable and manually edit it to modify the line? I've already done it adding to the line the kernel parameters edd=off and noapic.
Alright. Assume I already have my initrd.gz. Why can't I just make grub.cfg writable and manually edit it to modify the line?
yes you can do that, but the first debian update that runs update-grub will undo your edit. Slackware doesn't update the /boot/grub/grub.cfg when updating the system, but debian does. It should pick up the initrd.gz when update-grub is rerun
Quote:
I've already done it adding to the line the kernel parameters edd=off and noapic.
Those also will go away when debian updates the kernel. Edit /etc/default/grub and add it to the
Code:
GRUB_CMDLINE_LINUX=" edd=off noapic"
run update-grub
Last edited by colorpurple21859; 07-02-2020 at 01:40 PM.
I tried with the initrd.gz made as in post #27 and I tried with the one made as in post #35 both cases resulting in Kernel panic (same message).
@colorpurple21859: I read the posts you suggested in post #32. But they assume you recompile the kernel, a work I am not willing to do.
In the eMMC there are two partitions which are not shown by cfdisk. One of them is EFI, I think. When I ran the installer I was surprised it had found an NTFS partition with size 512MB. That is one of the "hidden" partitions. One thing: are we sure the kernel panic message is caused by the eMMC thing? What remains true is that both arch linux and debian had no problem with the eMMC.
EDIT: I have a second machine with 14.2 running on it, in case that is helpful.
This probably will never happen, but maybe Slackware could provide a choice? LILO / GRUB , ELILO/GRUB (UEFI) - without having to manually go in and install GRUB instead of LILO/ELILO. Just a thought.
This probably will never happen, but maybe Slackware could provide a choice? LILO / GRUB , ELILO/GRUB (UEFI) - without having to manually go in and install GRUB instead of LILO/ELILO. Just a thought.
Volkerdi himself told me lilo can't manage eMMC. I think if elilo can he would have told me.
I'll run the installer and after having run lsmod I'll use gpm (general purpose mouse) to paste the output into a file. Only thing is I don't know where gmp will be in the file system (I installed it).
This is the output of 'uname -r' run while running the installer:
Code:
4.4.14-smp
Does it match the kernel version?
Of course it does: I looked into the slackware /boot directory and the names of the images include '4.4.14-smp'. I did exactly what you said but still the same kernel panic message.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.