Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

howtos:slackware:kernel_huge_for_generic [2020/01/02 18:43 (UTC)]
slackjeff created
howtos:slackware:kernel_huge_for_generic [2020/01/03 08:46 (UTC)] (current)
alienbob Some minor layout and language improvements, and an alternative commandline shown as tip.
Line 1: Line 1:
 ====== How to switch from Kernel Huge to Generic? ====== ====== How to switch from Kernel Huge to Generic? ======
  
-At the end of this recipe the user will be able to switch from Kernel ​huge to Kernel Generic on Slackware, and enjoy its benefits. +At the end of this recipe the user will be able to switch from Kernel ​Huge to Kernel Generic on Slackware, and enjoy its benefits. 
-You may be wondering what benefit ​to realize is exchange. The benefits of switching from Huge to Generic are:+You may be wondering what benefit ​you get from this change. The benefits of switching from Huge to Generic are:
  
   * More fluidity and faster boot, due to Generic loading only the modules your machine needs.   * More fluidity and faster boot, due to Generic loading only the modules your machine needs.
   * The modules are not embedded, thus giving better flexibility.   * The modules are not embedded, thus giving better flexibility.
  
-So what is Kernel Huge for? Simple, because it has huge support for many drivers, it is ideal for use in installing the system. Thus allowing to reach a larger number of machines.+So what is Kernel Huge for? Simple, because it has huge support for many drivers, it is ideal for use in installing the system. Thus allowing to support ​a larger number of machine types.
 After installation Huge is no longer needed, which is why we should make the switch. After installation Huge is no longer needed, which is why we should make the switch.
  
Line 14: Line 14:
 Login as root, every process will be done by the superuser, after that we will execute the command '​mkinitrd_command_generator.sh'​ which is present in ///​usr/​share/​mkinitrd//​ Login as root, every process will be done by the superuser, after that we will execute the command '​mkinitrd_command_generator.sh'​ which is present in ///​usr/​share/​mkinitrd//​
  
-**<​code>​ +<​code>​ 
-/​usr/​share/​mkinitrd/​mkinitrd_command_generator.sh**+/​usr/​share/​mkinitrd/​mkinitrd_command_generator.sh
 </​code>​ </​code>​
  
-The output will be from the mkinitrd command with the modules necessary for the operation of your machine. Example:+The output will be an example''​mkinitrd'' ​command-line with the all the modules necessary for booting ​your machine. Example:
  
 <​code>​ <​code>​
Line 38: Line 38:
 </​code>​ </​code>​
  
-Copy the entire line where it starts with the command '​mkinitrd -c -k ....' and right after that paste it into your terminal. The mkinitrd command will be executed and will have output in this format:+Copy the entire line where it starts with the command ​''​'​mkinitrd -c -k ...''​' and right after that paste it into your terminal. The ''​mkinitrd'' ​command will be executed and will have output in this format:
  
 <​code>​ <​code>​
-**mkinitrd -c -k 4.4.172 -f ext4 -r /dev/sda1 -m usb-storage:​ehci-hcd:​ehci-pci:​xhci-pci:​ohci-pci:​xhci-hcd:​uhci-hcd:​hid:​\ usbhid:​i2c-hid:​hid_generic:​hid-cherry:​hid-logitech:​hid-logitech-dj:​\ hid-logitech-hidpp:​hid-lenovo:​hid-microsoft:​hid_multitouch:​jbd2:​mbcache:​\ ext4 -u -o /​boot/​initrd.gz**+mkinitrd -c -k 4.4.172 -f ext4 -r /dev/sda1 -m usb-storage:​ehci-hcd:​ehci-pci:​xhci-pci:​ohci-pci:​xhci-hcd:​uhci-hcd:​hid:​\ usbhid:​i2c-hid:​hid_generic:​hid-cherry:​hid-logitech:​hid-logitech-dj:​\ hid-logitech-hidpp:​hid-lenovo:​hid-microsoft:​hid_multitouch:​jbd2:​mbcache:​\ ext4 -u -o /​boot/​initrd.gz
  
 OK: /​lib/​modules/​4.4.172/​kernel/​drivers/​usb/​storage/​usb-storage.ko added. OK: /​lib/​modules/​4.4.172/​kernel/​drivers/​usb/​storage/​usb-storage.ko added.
Line 53: Line 53:
 </​code>​ </​code>​
  
-After that we will enter in lilo the information needed for Kernel Generic to be able to load, you can do this manually or you can simply run the command: '/​usr/​share/​mkinitrd/​mkinitrd_command_generator.sh'​ with the -l option then pass the full path to the location of vmlinuz-generic.+<note tip>Tip: the following command will automatically execute the ''​mkinitrd''​ commandline so that you do not have to copy and paste it yourself:​\\ 
 +<​code>​$(/​usr/​share/​mkinitrd/​mkinitrd_command_generator.sh -r)</​code></​note>​ 
 + 
 +After that we will enter in lilo the information needed for Kernel Generic to be able to load, you can do this manually or you can simply run the command: ​''​'/​usr/​share/​mkinitrd/​mkinitrd_command_generator.sh''​' with the "-l" ​option then pass the full path to the location of vmlinuz-generic.
  
 <​code>​ <​code>​
-**/​usr/​share/​mkinitrd/​mkinitrd_command_generator.sh -l \ /​boot/​vmlinuz-generic-4.4.172** +/​usr/​share/​mkinitrd/​mkinitrd_command_generator.sh -l \ /​boot/​vmlinuz-generic-4.4.172
-</​code>​+
  
-<​code>​ 
 image = /​boot/​vmlinuz-generic-4.4.172 image = /​boot/​vmlinuz-generic-4.4.172
   initrd = /​boot/​initrd.gz   initrd = /​boot/​initrd.gz
Line 68: Line 69:
 </​code>​ </​code>​
  
-Now let's add the information ​in lilo.conf present in: /​etc/​lilo.conf Add the information in the last line lilo.conf It is extremely important that you do NOT delete the Kernel Huge call, always leave it in case of tragedy with your system. . This for a possible rescue.+Now let's add this information ​to "/​etc/​lilo.conf"​. ​Add the block of text above (starting with "image =") at the end of lilo.confIt is extremely important that you do NOT delete the Kernel Huge call, always leave it in case of tragedy with your system. . This for a possible rescue.
  
-Change the label to a better name like KGeneric ​or something, this label is responsible for appearing on the Lilo screen. With a better name it is easier for you to identify ​him. After you have done the whole process run lilo for the new settings ​to be loaded:+Change the label to a better name like "​Generic" ​or something. This label will be appearing on the Lilo screen. With a better name it is easier for you to identify ​your new boot selection. After you have done the whole process ​you need to run '''​lilo''' ​for the new configuration ​to be saved:
  
 <​code>​ <​code>​
-**lilo**+lilo
  
 Warning: LBA32 addressing assumed Warning: LBA32 addressing assumed

In Other Languages
QR Code
QR Code howtos:slackware:kernel_huge_for_generic (generated for current page)