Silly me, the answer was right there in the Debian forums if I knew where to look.
It was as you guessed, Guardian, to do with the initrd. The thing is, the DVD image initrd contains more modules than the netboot one. The pertinent ones here being SATA drivers. So I followed the advice in the 9th post in that thread and it worked like a charm.
I was trying to get this exact setup and I've been tearing my hair out, turns out the solution is quite simple:
The initrd for the netboot image does not contain any ide or sata drivers and they are meant to be retrieved during a regular install, I'm not sure exactly whether they are just not present on the DVD or the installer does not detect or expect them if you are using a mirror of the DVD ( or any install cd ). However there is a solution and that is to make your own initrd.gz with the drivers present.
I've adapted here from
http://wiki.openvz.org/Modifying_initrd_image
http://ubuntuforums.org/archive/index.php/t-423963.html
First I got the initrd.gz for the netboot and off the netboot install cd, but I think the DVD initrd.gz should be fine then:
mkdir netboot-initrd-dir
mkdir cd-initrd-dir
gunzip netboot-initrd
gunzip cd-initrd
cd netboot-initrd-dir
cpio -i < ../netboot-initrd
cd ../cd-initrd-dir
cpio -i < ../cd-initrd
Now you will have two directories with the contents of both inird.gz files, you can see what driver files are in each one by:
find ./netboot-initrd-dir -iname *.ko
find ./cd-initrd-dir -iname *.ko
you should notice that there is a lot more from the one on the cd, in particular the ide and sata drivers. You can probably be more precise with this is you need to have a smaller image, but I managed to get away with:
cp -nr cd-initrd-dir/lib/modules/2.6.32-5-486/kernel/* netboot-initrd->dir/lib/modules/2.6.32-5-486/kernel/
now you just have to put it back together with:
cd netboot-initrd-dir
find . | cpio -H newc -o > ../new-netboot-initrd
cd ../
gzip ./new-netboot-initrd
Now you should be able to take that file and stick it in your tftp directory under initrd.gz or similar and it will now detect your disks!
Hope that helps you out.
maynim
Best Answer
https://www.tecmint.com/fix-unable-to-locate-package-error-in-debian-9/
To start with, it seems you might need to fix your
apt
sources before you can start installing packages such asgnome-core
. This is true even if you installed from the Debian 9 netinstall. I can only think this a bug in this version of the netinstall image. Sorry, this is Debian. Other distributions are available, which may be more popular and better tested.You want something very similar to the instructions https://www.maketecheasier.com/build-lightweight-linux-for-low-end-laptop/
You should be able to use the DVD1 you already downloaded, instead of doing a netinstall, although immediately do an update. (Only DVD1 is bootable, the others are used as Repositories.)
Untick everything except the bottom one "standard system utilities".
After installing and logging in to the command line, it suggests
apt-get install xorg sudo iceweasel pulseaudio
@sourcejedi says:
pulseaudio
, becausegnome-core
depends on it.apt
configuration,gnome-core
will indirectly installxserver-xorg
anyway. It is a "recommended" dependency of thegdm3
package.firefox-esr
, so you don't need to installiceweasel
instead.gnome-core
also includesgnome-software
, so you can use GNOME Software to install Firefox afterwards anyway :-).sudo
, you can install it, but you will also need to add your user to the sudo group. The alternative is just not to set any root password when the installer asks you, then it will set upsudo
for your main user automatically and not enable theroot
account.Then instead of the LXDE option, where it says
apt-get install lxde
, you should use:apt-get install gnome-core
.This should give you a basic Gnome desktop without games, office etc.
@sourcejedi says: I would have some concern that installing
gnome-core
will startgdm
immediately, hiding your command line and any possible error messages. To be on the safe side, I recommend switching to TTY2 by pressing ctrl+alt+F2, before you installgnome-core
. Then you would be able to switch back to TTY2 and check for errors.