kernel updating despite unchecked "download and install" choice

Note that this does not happen in the server install, only the desktop.

Please, you give more information because it's probably that not be a bug.

I'm adding a doc that shows their current process.

There's no question that if updates are still happening when "download and install updates" isn't selected, I need to reproduce this bug.

Is the driver in use a dkms driver? Could you also attach the install logs or at least a good part of it (after sanitizing any personal information)?

Attached are the instructions we use to install Ubuntu for AMD, using AMD-RAID RAIDXpert2 drivers. It is a RAID device and it uses the AMD-RAID device as the boot RAID Virtual Disk. To get around the kernel being updated during the installation, our work around is to disconnect the Ethernet cable during the installation. But after the OS is installed, we are still seeing it being updated.
No our driver does not support dkms.

I think I see what is happening here. The last few steps of install involve setting up the mirror, updating the apt cache and installing the kernel, langpacks, and other bits for the installed system; doing so while being online *will* make use of the network, and since you're updating the apt cache, you will also get the new packages if you are trying to install anything.

This is different than the "update" process -- updates are not being retrieved, but the kernel is being installed along with other things (as above, langpacks for instance) that are not otherwise available if the installed system is truly offline. I also think this is behavior we'd want to keep; while not everything is being updated, we're at least making sure the most critical pieces of the system are as up to date as possible while we do the installation.

Now, there is no question that this is being an issue while installing the AMD-RAID driver for this bug report. I'm just not sure how to fix this.

Is there a way to run pre-install and post-install scripts from in the chroot instead of in the live session? Depending on what these scripts do, the process might then pick up the right header files to install the driver.

Also, please attach /var/log/syslog from the live-session (or /var/log/installer/syslog after the install has completed, from the installed disk). For the live-session, you will want to retrieve it just before trying to reboot to the installed system.

It would also be useful to start the installer in "debug" mode before getting the logs: you can do this by hitting F6 then Esc at the boot splash (before selecting "Try and install"), and adding "debug-ubiquity" to the command-line at the bottom, just before the "---".

The logs here will provide us with more information to what exactly is happening during the install.