[ primary (JP) ] [ secondary (FR) ]

Backported d-i images archive

This directory provides Debian GNU/Linux Stable installer ISO images with a modification by Kenshi Muto to support newer hardwares, such as SATA and Ethernet devices.

USE THEM AT YOUR OWN RISK, PLEASE.

Good News: If you're finding an image with newer kernel for Etch, you can use 'etch-and-a-half' release created by Debian etch-and-a-half team instead of mine. Let's visit Installing Debian GNU/Linux `etch-and-a-half' page!

Distribution: Etch (Debian GNU/Linux 4.0)

i386

AMD64

Distribution: Sarge (Debian GNU/Linux 3.1)

i386

AMD64

Build firm

I'm only touching i386/amd64 codes at this moment. You have to modify many things if you'd like to use this on other architectures.

FAQ (for Etch)

I succeeeded an installation with wireless card, but I no longer use it after reboot! Why?
Maybe your card needs a firmware. Although the custom installer includes these firmwares since 2.6.24 image, it won't be installed to your machine automatically (TODO). You can take the deb version via APT after adding custom-CD to /etc/apt/sources.list by "apt-cdrom add". Check linux-ubuntu-modules-2.6.* package.
Installer won't recognize my drive on Marvell IDE controller of ICH9, even it boots up installer!
Try "install acpi=off generic.all_generic_ide=1" (information from Diego).
Where is linux-headers package?
You can take it via APT after adding custom-CD to /etc/apt/sources.list by "apt-cdrom add". You can see it in pool/main directory also.
How to install it via TFTP (a.k.a netboot)?
Download both netboot.tar.gz and CD image. Set up TFTP server for netboot and Web server for exporting CD contents. On Web server, you'll do "mount -o loop /dev/cdrom /mnt/cdrom" and set up to export /mnt/cdrom to the outside. To escape Release.gpg verification (only Debian official ftpmaster can sign this file), you have to specify a special parameter, like "install debian-installer/allow_unauthenticated=true".
Are there any official security supports or technical support for your image?
No.

FAQ (for Sarge)

Where is kernel-headers package?
kernel-headers and kernel-image packages are renamed to linux-headers and linux-image since v2.6.16. My custom installer CD image contains linux-headers-* package for you. Check pool/main directory.
I can't install desktop-task or GNOME! It's a grave bug!
Unfortunately udev system conflicts against old hal package Sarge uses. And backporting hal package isn't so easy. If you succeed to build it, please tell me or upload it to backports.org.
Where is kernel-source package?
kernel-source package are renamed to linux-source. You can find linux-source ~2.6.18 from www.backports.org. At this time 2.6.19 and 2.6.20 images use my own Linux source. This source is vanilla kernel as same as one is distributed at kernel.org. So you can take kernel source from kernel.org and copy /boot/config-* to .config, then configure and build your own kernel. FYI I use "CONCURRENCY_LEVEL=2 make-kpkg --initrd --revision 2.6.20-0mtu1 --append-to-version -1-686 --rootcmd fakeroot linux_image linux_headers" with kernel-package of www.backports.org.
My ICH8 machine won't detect CD drive on Sarge!
Maybe your machine has Marvell PATA controller. Linux hasn't supported this controller yet. You may try to boot "expert" mode and load "ide-generic" manually. (I hope 2.6.20 image fixed this because it included Marvell PATA driver) USB memory boot is easier.
My machine has SATA HDD connects Intel SATA controller, but CD-ROM connects Intel PATA controller. Installer misses CD-ROM drive during the process.
Since sarge-custom-1008 version, use "atapi" boot option like linux atapi=true. This will automatically do things described below.
This is well known issue about Intel ATA driver. Try:
  1. Boot installer and choose a language.
  2. When you're asked your keyboard, push Alt+F2.
  3. Execute: 
    echo "options libata atapi_enabled=1" >> /etc/modprobe.conf
  4. Push Alt+F1 and continue the installation.
My SATA drive is recognized as /dev/sde on the installer stage, but it becomes /dev/sda after reboot. Kernel fails to load root partition.
Because the installer and regular initrd boot are using different procedure to detect devices (although udevd is used at first on both situations). Modify root partition (such as root=/dev/sde1 -> root=/dev/sda1) on GRUB interface and boot. Modify kopt= line of /boot/grub/menu.lst also and run 'update-grub'.
Installer failed to install GRUB!
Push Alt+F2 and do "chroot /target; grub-install --no-floppy /dev/sde" (replace /dev/sde with your disk device name). Then back to the installer by Alt+F1 and skip installing boot loader.
Even my device is recognized on 1st stage, it won't work after reboot (on 2nd stage). What's happen?
This is initramfs-tools's issue. Temporary solution is:
  1. Go through before installer asks about GRUB installation.
  2. Push Alt+F2 to go alternative shell.
  3. Do following process. Replace "DEVICE_MODULE_NAME" with your device driver name, such as "megaraid_sas". 
    # chroot /target
# echo "DEVICE MODULE NAME" >> /etc/initramfs-tools/modules
# update-initramfs -a -u
# exit
  4. Push Alt+F1 to go back installer screen.
  5. Install GRUB and pray.
It's better to submit a bug to initramfs-tools package if the package in unstable still hasn't the device name in hook-functions.
When I installed Sarge on my PATA disk machine, it goes an infinite loop to find the root partition.
1st stage treats PATA disk/CD as like SCSI device since 2.6.19. But 2nd stage doesn't. First solution is modifying initrd as I wrote above ("Even my device is recognized on 1st stage, it won't work after reboot (on 2nd stage). What's happen?") Second solution is, if you have only single partition for Debian system, just replace root parition name to use /dev/hda* insttead of /dev/sd* on GRUB, then modify /etc/fstab to suit.
Can I create my own installer, for example using newer kernel?
Yes, you can refer various resources from wiki.debian.org and my build-firm kit (see above link). You have to understand Debian's magic... svn, d-i, debconf, APT, kernel-package, kernel-wedge, debian-cd, and so on.
Why can't I use ipw2100/ipw2200/bcm43xx even they seem be included in kernel?
These drivers need a firmware. If you'd like to use them during the installation stage, you have to download it and put them /lib/firmware by hand before loading that drivers.
I can't build the correct image for my architecture from your repository!
My working is only for i386, and partially for amd64. If you'd like to run on other architectures, you have to modify at least d-i/packages/kernel/kernel-wedge, d-i/packages/kernel/d-i-*, d-i/installer/build/config.
Where can I your kernel configuration?
Check /boot/config-* file. It is as same as kernel .config file I used.
How to install it via TFTP (netboot)?
You can't use CD and hd-media directly for network installation via TFTP, because the configuration step is different. Use netboot.tar.gz for TFTP installation and mount CD image on your external Web server to get custom kernel and files.
Are there any security supports or technical supports for your image?
No.

Acknowledgement

Primary JP site is provided by kmuto.jp, hosted by fonfun Corporation as a community support. Secondary (and has a good bandwidth) FR mirror is provided by Emmanuel Lacour. Debian-Installer team has produced the excellent installer. Backports.org guys have relaxed me from many works.
Thank you.

Links

Copyright 2006-2007 Kenshi Muto <kmuto at debian.org>