[SOLVED] update-grub is picking up Huge first, advance boot listing will not boot generic kernel gets panic.
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.
Let's not exaggerate All you had to do was follow the link, where it says;
Code:
Instructions
Copy the file 09_slackware_linux into the directory
/etc/grub.d/
and mark it executable.
well that didn't work, it worked but it the kernel didn't.
process of elimination #2
add some kind of custom line to whichever add in config files held in /etc/grub.d
steps needed to be taken.
1. figure out what to write
2. figure out which config file it goes in.
echo 'Loading Linux 4.4.38 ...'
linux /boot/vmlinuz-generic-4.4.38 root=/dev/sda6 ro
so this too does not explain why I got a kernel panic. but if I reboot and select generic right now I think that is a premature idea/action at this minute.
The grub menuentry for a Slackware generic kernel needs a linux line (pointing to the kernel) and an initrd line (the initrd.gz). E.g.,
Code:
linux /boot/vmlinuz-generic-4.4.38 root=/dev/sda6 ro
initrd /boot/initrd-4.4.38.gz
The Slackware generic kernel won't boot without an initrd. I've never needed to manually edit grub files for this; the grub-mkconfig works it out if you name the files sensibly (I suppose, it may find them some other way).
Quote:
Originally Posted by BW-userx
so taking from your two post, this one and the other above it. modding of the "custom" config files held within /etc/default need to be done?
which one and what is added to make that work?
if you do not mind me asking.
On booting, grub will only read your configuration from /boot/grub/grub.cfg
You are supposed to make any changes inside /etc/grub.d and /etc/default/grub, and then run grub-mkconfig -o /boot/grub/grub.cfg to update grub.cfg
# grub-mkconfig -o /boot/grub/grub.cfg
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-huge-4.4.38
Found initrd image: /boot/initrd-4.4.38.gz
Found linux image: /boot/vmlinuz-huge
Found linux image: /boot/vmlinuz-generic-4.4.38
Found initrd image: /boot/initrd-4.4.38.gz
Found linux image: /boot/vmlinuz-generic
done
and here's the relevant updated part from /boot/grub/grub.cfg
Code:
echo 'Loading Linux 4.4.38 ...'
linux /boot/vmlinuz-generic-4.4.38 root=/dev/mapper/cryptvg-root ro
echo 'Loading initial ramdisk ...'
initrd /boot/initrd-4.4.38.gz
There shouldn't be any problems with that part. Depending on your needs, you might need to edit templates in /etc/grub.d and also set the default boot option in /etc/defaults/grub (i.e., GRUB_DEFAULT). Again, nothing will actually happen until you run grub-mkconfig -o /boot/grub/grub.cfg (and regenerate your /boot/grub/grub.cfg).
The grub menuentry for a Slackware generic kernel needs a linux line (pointing to the kernel) and an initrd line (the initrd.gz). E.g.,
Code:
linux /boot/vmlinuz-generic-4.4.38 root=/dev/sda6 ro
initrd /boot/initrd-4.4.38.gz
The Slackware generic kernel won't boot without an initrd. I've never needed to manually edit grub files for this; the grub-mkconfig works it out if you name the files sensibly.
On booting, grub will only read your configuration from /boot/grub/grub.cfg
You are supposed to make any changes inside /etc/grub.d and /etc/default/grub, and then run grub-mkconfig -o /boot/grub/grub.cfg to regenerate an updated grub.cfg
still analyzing this I have not looked into the /etc/default/grub to mod it yet. thanks for the important part it got a have the initrd too when using the "generic" kernel.
I could ask why?
if the huge works on its own, and within other distros the kernel do not need an extra initrd but here it does, why question. But,
I will forbade that question.
I just put this line grub-mkconfig -o /boot/grub/grub.cfg in wrapper script and called it, update-grub put it in /usr/bin
chmod +x /usr/bin/update-grub
just run update-grub
done saves typing.
this is better /boot/initrd-4.4.38.gz
than
/boot/initrd-generic-4.4.38.gz
I ask because I am still looking at this code in the drop in slackwareGrub2 config off of github
let me tinker with this thing on that default/grub initrd thing.
# grub-mkconfig -o /boot/grub/grub.cfg
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-huge-4.4.38
Found initrd image: /boot/initrd-4.4.38.gz
Found linux image: /boot/vmlinuz-huge
Found linux image: /boot/vmlinuz-generic-4.4.38
Found initrd image: /boot/initrd-4.4.38.gz
Found linux image: /boot/vmlinuz-generic
done
and here's the relevant updated part from /boot/grub/grub.cfg
Code:
echo 'Loading Linux 4.4.38 ...'
linux /boot/vmlinuz-generic-4.4.38 root=/dev/mapper/cryptvg-root ro
echo 'Loading initial ramdisk ...'
initrd /boot/initrd-4.4.38.gz
There shouldn't be any problems with that part. Depending on your needs, you might need to edit templates in /etc/grub.d and also set the default boot option in /etc/defaults/grub (i.e., GRUB_DEFAULT). Again, nothing will actually happen until you run grub-mkconfig -o /boot/grub/grub.cfg (and regenerate your /boot/grub/grub.cfg).
(root@SlackO⚡️/boot)>># update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-generic-4.4.38
Found initrd image: /boot/initrd-4.4.38.gz
Found linux image: /boot/vmlinuz-huge-4.4.38
Found linux image: /boot/vmlinuz-huge-4.4.38
Found initrd image: /boot/initrd-4.4.38.gz
Found linux image: /boot/vmlinuz-huge
Found linux image: /boot/vmlinuz-generic-4.4.38
Found initrd image: /boot/initrd-4.4.38.gz
Found linux image: /boot/vmlinuz-generic
Found Windows 10 (loader) on /dev/sda1
Found unknown Linux distribution on /dev/sda5
Found Slackware Linux (Slackware 14.2) on /dev/sda6
done
What is the difference between a “generic” kernel and the “huge” kernel which has been installed as the default kernel?
The “huge” kernel is essentially a kernel which has every hardware driver built in which you might need for a successful installation of your computer. Think of storage and (wired) network drivers, filesystem and encryption drivers and a lot more. All these built-in drivers result in a big kernel image (hence the name “huge”). When this kernel boots it will use up a lot your RAM (relatively speaking… with 1 GB of RAM you will not really be troubled by a few MB less RAM).
The “generic” kernel on the other hand, is a kernel which has virtually no drivers built in. All drivers will be loaded into RAM on demand. This will make your kernel's memory consumption lower and the boot process a bit faster. The smaller size allows for the use of an initial RAM disk or “initrd”. An initial RAMdisk is required in certain configurations, like software RAID, or a fully encrypted hard drive.
For now, you need to remember that a “huge” kernel will not support an intial RAM disk, but the “generic” kernel will. We go for maximum flexibility and use a “generic” kernel.
I'm not aware of any big benefits, but I prefer to run a modular kernel that only loads what my system needs, as opposed to having it all baked in. I can't see any problem with running the huge kernel, although if you encrypt your root partition, you need an initrd anyway.
I'm not aware of any big benefits, but I prefer to run a modular kernel that only loads what my system needs, as opposed to having it all baked in. I can't see any problem with running the huge kernel, although if you encrypt your root partition, you need an initrd anyway.
yeahhhhhh I just added the tag -generic- to it to be a reminder that it was made from the generic kernel but that didn't work due to the way the script is written to only pick up a initrd that it's name is formed to match initrd-(ver-number).gz w/o a name for it ie, huge or generic just a version number.
i unerstand that using a kernel that only runs what one needs it to load, anything else is overkill.
just that having the added need for a initrd due to a custom kernel if you think about it long enough you should see that even the huge is a custom kernel too. it does not need a initrd to get the sys booted but the generic kernel does need a initrd.
maybe just maybe it is because the supplied generic is not actually curtailed to ones system because it is not reconfigured to the systems hardware per se' it is only having less modules loaded within it .
now I've moved on to working on getting this grub video mode / theme thing working
just that having the added need for a initrd due to a custom kernel if you think about it long enough you should see that even the huge is a custom kernel too. it does not need a initrd to get the sys booted but the generic kernel does need a initrd.
maybe just maybe it is because the supplied generic is not actually curtailed to ones system because it is not reconfigured to the systems hardware per se' it is only having less modules loaded within it .
Technically, any kernel is a "custom" kernel because someone had to go through the kernel options and select what they wanted compiled into the kernel and what they wanted built as modules. However, in the context of a distro, a "stock" kernel is a custom kernel that is provided by distro maintainer for that distro. In that case, huge and generic are both stock kernels and not really custom in the way it is normally seen in the Linux world.
In actuality, there is no such thing as a generic or huge kernel. These are Slackware terms used to indicate whether things are generally built into the kernel (huge) or compiled as modules (generic). You can easily take the generic config Pat provides, make a few modifications (like adding your filesystem to the kernel and any required hardware support), and not need an initrd anymore (for a lot of cases -- however, there are specific cases that will always need an initrd, like using UUID for booting or LVM and/or encryption).
And you can tailor a kernel to your system (shrink it down so it only supports the hardware you have), but it typically doesn't provide much of a noticeable improvement, and the majority of people seem to think it isn't worth the time and effort.
Technically, any kernel is a "custom" kernel because someone had to go through the kernel options and select what they wanted
that was my point, agreed:
Quote:
Originally Posted by bassmadrigal
compiled into the kernel and what they wanted built as modules. However, in the context of a distro, a "stock" kernel is a custom kernel that is provided by distro maintainer for that distro. In that case, huge and generic are both stock kernels and not really custom in the way it is normally seen in the Linux world.
agreed:
Quote:
Originally Posted by bassmadrigal
In actuality, there is no such thing as a generic or huge kernel. These are Slackware terms used to indicate whether things are generally built into the kernel (huge) or compiled as modules (generic).
agreed:
Quote:
Originally Posted by bassmadrigal
You can easily take the generic config Pat provides, make a few modifications (like adding your filesystem to the kernel and any required hardware support), and not need an initrd anymore (for a lot of cases -- however, there are specific cases that will always need an initrd, like using UUID for booting or LVM and/or encryption).
And you can tailor a kernel to your system (shrink it down so it only supports the hardware you have), but it typically doesn't provide much of a noticeable improvement, and the majority of people seem to think it isn't worth the time and effort.
yep I've been down that road before. My luck with recompiling a kernel is non existent at the time of writing this.
side question.
what are are all of these little pictures I am starting to see on the bottom of the post in the users side bar?
penguins and such. I got three now when I only had one.
you got a windows a penguin and a cloud.
I got a ? and penguin and a cloud
some of my post got a penguin head a penguin and a cloud.
if that cloud looking thing is suppose to be a cloud
side question.
what are are all of these little pictures I am starting to see on the bottom of the post in the users side bar?
penguins and such. I got three now when I only had one.
you got a windows a penguin and a cloud.
I got a ? and penguin and a cloud
some of my post got a penguin head a penguin and a cloud.
if that cloud looking thing is suppose to be a cloud
If you hover over them, it should give an indication of what they mean.
But essentially, the first is what OS that user is posting from. It is based on their browser's useragent. There's discussions on the forum on how to get Slackware to be detected (since Pat doesn't use a custom useragent for Slackware's browsers, it can't be detected as Slackware and only shows up as Linux). The second is whether or not that person is online (question mark is online, and no question mark is offline -- I don't know why it is that way). The final one allows you to give people reputation (similar to clicking the "Did you find this post helpful?" link at the end of other's posts), but allows you to write a comment that only the poster can see. I believe it gives you more reputation than just clicking the yes, but I haven't tried to verify it.
If you hover over them, it should give an indication of what they mean.
I did and clicked on all of them, only one gave results for reputation points.
Quote:
Originally Posted by bassmadrigal
But essentially, the first is what OS that user is posting from. It is based on their browser's useragent.
I am using slack and I get a ? question mark ?
Quote:
Originally Posted by bassmadrigal
There's discussions on the forum on how to get Slackware to be detected (since Pat doesn't use a custom useragent for Slackware's browsers, it can't be detected as Slackware and only shows up as Linux).
belay my last.
Quote:
Originally Posted by bassmadrigal
The second is whether or not that person is online (question mark is online, and no question mark is offline -- I don't know why it is that way).
wait , now belay my second reply about the question mark.
Quote:
Originally Posted by bassmadrigal
The final one allows you to give people reputation (similar to clicking the "Did you find this post helpful?" link at the end of other's posts), but allows you to write a comment that only the poster can see. I believe it gives you more reputation than just clicking the yes, but I haven't tried to verify it.
that refers to my first reply
don't be scared give it a click it is rather impressive to say the least.
I did and clicked on all of them, only one gave results for reputation points.
I didn't say "click", I said hover. The tooltips that come up provide your answer. In your case, it shows that you're using linux, you're online, and I can give you reputation.
For me, it shows I am using windows_10, I'm online, and I can view my reputation for that post.
The only clickable one is the last icon, which on your own posts, allows you view your reputation for that post, and for other posts, allows you to give the author reputation and provide a comment.
I didn't say "click", I said hover. The tooltips that come up provide your answer. In your case, it shows that you're using linux, you're online, and I can give you reputation.
For me, it shows I am using windows_10, I'm online, and I can view my reputation for that post.
The only clickable one is the last icon, which on your own posts, allows you view your reputation for that post, and for other posts, allows you to give the author reputation and provide a comment.
Quote:
Originally Posted by bassmadrigal
I believe it gives you more reputation than just clicking the yes, but I haven't tried to verify it.
I was just skimming looking for key words. sorry but one can still click on them that rep one woo hoo it gives you feedback
I was just skimming looking for key words. sorry but one can still click on them that rep one woo hoo it gives you feedback
While technically anything is clickable, the first two aren't links, so clicking on them does nothing.
And as for the reputation, I believe clicking on the link to "Add to ${USER}'s reputation" will provide more reputation than just clicking on the "yes" at the bottom of posts when it asks if you found the post helpful. Clicking "yes" will definitely add one point to that user's reputation, but I believe clicking on the icon will give ten points, but I don't know any easy way to find out without asking someone to manually click on the links and have me check my reputation before and after (plus, I don't really care enough about reputation to bother).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
All you had to do was follow 
