Kernel panic with Cucumber Linux 1.1 beta 3 installed on GPT partitions.
I got a kernel panic with Cucumber Linux 1.1 beta 3 installed on GPT partitions. I installed Cucumber Linux on a USB hard drive triple booting with two installs of Lubuntu. I used the updated 4.9.77 kernel. Also, when I tried to install grub to /dev/sdb I got the following message.
/sbin/grub-bios-setup: warning: this GPT partition label contains no BIOS Boot Partition: embedding won't be possible. /sbin/grub-bios-setup: warning: embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged. /sbin/grub-bios-setup: error: will not proceed with blocklists. Also, I couldn't get a wired Internet connection to work when I chrooted into the installation even though I followed the directions on the Cucumber wiki. |
As a person who has used Slackware, I do like the concept of a old style distro with no dependency resolution. I know that the idea of one that has stronger security updates is quite positive. Cucumber Linux just needs to be able to work on more setups to have a chance to dethrone Slackware as the king of no dependency resolution distros which use text pages in its initialization. I don't know if it can get the man power to take off as a distro, but I commend the BDFL for trying.
|
Quote:
When you go to install Grub now, it will succeed. As a sidenote, if you ever move this BIOS boot partition it will be necessary to reinstall Grub to the MBR. Quote:
|
I did as suggested. I put the BIOS boot partition on sdb7, and the root partition on sdb8, but I still get the kernel panic after getting the message "error: no symbol table". Do I have to make an initrd? If so, how is that done?
|
Quote:
Is there any way you could post more of the stack trace from the kernel panic? Could you please additionally post your grub.cfg (/boot/grub/grub.cfg)? Also, what filesystem are you using for the root partition, and do you have a separate /boot partition (the /boot partition and the BIOS boot partition are two different partitions)? |
The following is the stack trace.
Code:
warm_slowpath_null+0x1d/0x20 Code:
### BEGIN /etc/grub.d/00_header ### |
Okay. It looks like your grub.cfg was created using grub-mkconfig, which doesn't work properly with Cucumber Linux. During the installation, the installer asks you if you want to install a new grub.cfg. When you select yes here, it installs a custom grub.cfg. Using this custom config is the only method of booting Cucumber Linux that is officially supported.
In your case, you should be able to fix the problem by replacing the contents of your grub.cfg with: Code:
set default="0" |
I changed the entries in grub.cfg as suggested and then chrooted and entered "grub-install /dev/sdb" . But, I still get the kernel panic with the same stack trace as before.
|
From my experience, a distro has to have a package to make an initrd in order to get people to install it with an encrypted root directory and on a USB hard drive that is not an sda or hda hard drive. I had used Slackware and I couldn't get it to run on my USB hard drive unless I made an initrd with the suggested modules.
|
All times are GMT -5. The time now is 12:44 PM. |