Iso can't boot with xanmod kernel
Bug #1849100 reported by
Paullux
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cubic |
Fix Released
|
High
|
Cubic PPA | ||
Classic |
Fix Released
|
High
|
Cubic PPA | ||
Classic-development |
Fix Released
|
High
|
Cubic PPA |
Bug Description
With Eoan Ermine, I am using xanmod kernel with cubic but the iso can't boot.
the iso is locking with :
```
BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)
```
if i choose the kernel from original iso, i can boot but it isn't personalized like i want.
description: | updated |
Changed in cubic: | |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → Cubic PPA (cubic-wizard) |
To post a comment you must log in.
Paullux,
The default kernel that you installed in the chroot will be kernel that is used once you install the OS onto a computer.
Is there a reason you need to bootstrap your ISO using a specific kernel? In other words, why do you want to "personalize" the ISO bootstrap kernel?
I'd like to uderstand what are the use cases why people would want a specific kernel to bootstrap their ISO. (The original reason there are multiple kernel choices in Cubic is so people can select the one that doesn't result in "busy box", but there might be other compelling reasons to use a specific kernel).