Custom ISO network issue

Please provide additional details.
Which OS and version are you running Cubic in?
Which OS and version are you customizing in Cubic?
What is the original ISO you downloaded to customize?

I am running Ubuntu 20.10 (Groovy Gorilla) on my host and i try to customize Ubuntu 20.10 in Cubic

I downloaded the Ubuntu 20.10 iso.

For my first try, i have an issue with the iso generation so i solved it with the solution in this thread : https://answers.launchpad.net/cubic/+question/692621

So i used also the ubuntu 20.04.1 iso.

I tried to customize the 20.04 and there is no problems with networks but settings disappeared.

What kinds of customizations did you do?
Did you install any network related packages (for example drivers)?
Did you change any network settings or configurations while customizing?
Did you install any extensions?

Also, let me know if you did an upgrade or if you installed new kernels?

I post you the script that i have done to customize :

add-apt-repository main
add-apt-repository universe
add-apt-repository multiverse
add-apt-repository restricted

# Désinstallation de composants inutiles
apt-get -y purge thunderbird gnome-mines gnome-sudoku gnome-mahjongg aisleriot remmina shotwell totem rhythmbox cheese cheese-common snapd transmission-gtk gnome-calendar

#Installation de logiciels
apt-get -y install idle3 thonny jupyter-notebook gimp python3-matplotlib python3-scipy gedit-plugins pdftk dub ocaml-nox vlc git curl ghc apache2 apache2-utils mysql-common mysql-server php7.4 php7.4-mysql php-common php7.4-cli php7.4-common

#Installation de librairies python
cd ~
pip3 install folium

# Mise à jour

apt-get -y autoremove
apt-get update
apt-get -y upgrade

#Installation de filius
cd /home
dpkg -i *.deb
rm *.deb
cd ~

#Nettoyage
apt clean

I don't install network related packages and i don't change settings.
I install extensions on Firefox (privacy badger, ad block, no script and disconnect) et copy the config folder in etc/skel
I also put config folder of filius, jupyter notebook and logisim in etc/skel.
I add two dektop files in /usr/share/applications

I don't install new kernels.

That all seems pretty normal.

Do you get the same result if you create a new project in Cubic, but do not make any customizations inside Cubic's terminal, and just generate the ISO?

I have just tested and i have the same issue.
On the boot, i can show the message initramfs decoding failed.
Can it be linked to the issue ?

If you get the message iniramfs failed, you wouldn't be able to boot into the ISO?
I think this would be a separate issue.

You can paste stuff @ https://pastebin.com/ and link the URL for your paste here.

Hi,

I take the liberty of answering because this problem was diagnosed with Cubic PPA and me. Look at it, it's a bug that doesn't impact. It is necessary to change the compression format on the initramfs side.

https://answers.launchpad.net/cubic/+question/692720

On your network issue do you use NetworkManager ? Networkd ? Netpla ? etc...

Regards

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835660

@Cubic PPA

I am able to boot even i have the message initramfs failed.

Johnny, i have shown the thread but my compression is gzip yet.

I use NetworkManager.

What stuff do you need ? boot.log ? syslog ?

Grégory,

------------------------------------------------------------------------
TEST 1 (Using Cubic version: 2020.12-18-experimental)
------------------------------------------------------------------------

1) I installed Ubuntu 20.10 in VirtualBox.
2) I did not install any updates.
3) I added the universe repository.
4) I installed Cubic version 2020.12-18-experimental.

5) Then I launched Cubic, and chose to customize ubuntu-20.10-desktop-amd64.iso.
6) I did ~not~ make any changes on Cubic's Terminal page; I simply clicked Next.
7) I also did not make any changes on Cubic's options page; I simply clicked Generate.
8) Cubic produced an ISO called "ubuntu-20.10.0-2020.12.14-desktop-amd64.iso".
9) I moved this ISO to my host machine, and shut-down the virtual machine.

10) I added the new ISO ("ubuntu-20.10.0-2020.12.14-desktop-amd64.iso") as a disk to VirtualBox, and booted into it.
11) I was able to boot successfully into the Live environment successfully.
12) I was also able to access the Internet from the customized live ISO.
13 Additionally, all of the icons at the right of the Top Bar were visible, including the Network icon.

------------------------------------------------------------------------
TEST 2 (Using Cubic version: 2020.10-35-release)
------------------------------------------------------------------------

1) I installed Ubuntu 20.10 in VirtualBox.
2) I did not install any updates.
3) I added the universe repository.
4) I installed Cubic version 2020.10-35-release.

5) Then I launched Cubic, and chose to customize ubuntu-20.10-desktop-amd64.iso.
6) I did ~not~ make any changes on Cubic's Terminal page; I simply clicked Next.
7) I also did not make any changes on Cubic's options page; I simply clicked Generate.
8) I experienced know bug Bug #1905098, where the ISO failed to generate.
9) I applied the work-around using "ubuntu-18.04.4-desktop-amd64.iso" (see https://bugs.launchpad.net/cubic/+bug/1905098/comments/8).
10) This time, Cubic produced an ISO called "ubuntu-20.10.0-2020.12.14-desktop-amd64.iso".
11) I moved this ISO to my host machine, and shut-down the virtual machine.

12) I added the new ISO ("ubuntu-20.10.0-2020.12.14-desktop-amd64.iso") as a disk to VirtualBox, and booted into it.
13) I was able to boot successfully into the Live environment successfully.
14) I was also able to access the Internet from the customized live ISO.
15) Additionally, all of the icons at the right of the Top Bar were visible, including the Network icon.

------------------------------------------------------------------------
TEST 3 (Using the ISO generated in TEST 2)
------------------------------------------------------------------------

To test if the networking icon in the top bar is not present if Ubuntu doesn't detect networking hardware on the machine,...

1) I removed the network adapter in VirtualBox.
2) I was able to boot successfully into the Live environment successfully.
3) I was also not able to access the Internet from the customized live ISO.
4) However, all of the icons at the right of the Top Bar were still present, including the Network icon.
5) Ubuntu displayed a message "activation of network connection failed".
6) The networking icon displayed three dots above indicating a broken connection, but it was still there.

Grégory,

Based on my tests above, I do not think Cubic is causing your networking icons to not display.
It is possible that some software you are installing is changing your system in some unexpected way.
Perhaps you can try a test like #1 or #2 above, where you do *not* make *any* changes on Cubic's Terminal page.
(The software you listed in comment # 6 doesn't look like it should cause any issues, but we can't know for sure until you have eliminate that possibility).

Also, do you know if your hardware requires a specific Linux kernel for networking to work? May be the correct kernel needs to be installed. Or you perhaps you need to install specific drivers for your networking hardware? (If so, this is a little tricky if you are not running the exact same kernel on your host machine as you have setup on your custom OS).

Hi,

I run the test2 and it works...in my VirtualBox Machine. So, indeed, it's not a problem with Cubic.
It's really strange.

When i customize an Ubuntu 20.04, without changing anything, i don't have this network issue but it appears with the 20.10.
With the original iso, there is no problem.

It's probably a driver issue but i don't which one.
I'm going to look for it but if i won't find, i will stay with 20.04.

Thank you for everything.
The problem is not totally solved so i don't change the status.

Grégory

Grégory,

On of the issues people run into with drivers is that when a driver is installed, it is installed for the ~current~ running kernel.
In Cubic, this kernel is shown at the top right of the Terminal page.
Any drivers installed will be installed for that kernel.

If you have updated or upgraded Ubuntu in Cubic's Terminal page, it is possible a newer kernel was installed.
This kernel may be used when you boot into the live ISO, and it ~will~ be used when you boot into your customized OS, after installing it to a computer. At this point, the newer kernel will not find the drivers (which were installed for an older kernel).

I think the drivers (modules) get installed to /usr/lib/modules. If you look at this directory, you can can see they are kernel specific. If you must install a driver for a kernel that is different than the one Cubic shows at the top right, you should place the correct files to the matching module directory. This requires a bit of manual work.

However, there are two easier approaches:

1. Make sure you have manually installed the same kernel in Cubic as you are running on your host machine.
    See https://answers.launchpad.net/cubic/+question/688169 for instructions.

...or...

2. Updrade your host machine to a newer kernel (and reboot), and then upgrade the customized OS inside Cubic to the same newer kernel. This way, both will match.

Then install your drivers inside Cubic and everything will match.

To make sure the live ISO also boots using the same kernel (and is able to use the drivers), select that same kernel on Cubic's Kernel tab on the Options page.

Also, since you are customizing Ubuntu 20.10 and you are experiencing Bug #1905098, I suggest using the experimental version of Cubic which has this bug fix.

See https://bugs.launchpad.net/cubic/+bug/1905098/comments/12 for instructions.

(Although this is in the experimental branch, it is working really well and has been quite stable in my testing).

(Keep a copy of your current cubic.conf as backup, in case you need to switch back to the release version of cubic. If you do have to switch back, just replace the "experimental" cubic.conf with your backed-up cubic.conf).

Thank you very much !

I finally solved my problem and it was a driver problem.
I need to install the package linux-generic and it install by dependencies linux-image-modules and everything is fine now.
I have the network.

And the initramfs issue disappeared too.

I am going to try the experimental version to avoid the bug.

Excellent!