Debian-Installer: FAQ



Note

Before attempting an installation or reporting a problem, remember to check the [http://www.debian.org/devel/debian-installer/errata errata] page to see if your problem is already well known.

It might also be worthwhile to check [http://www.debian.org/devel/debian-installer/ports-status this page] to see the status of the DebianInstaller on different architectures and with different installation methods.

Finally, if you are experiencing problems with an older version of the installer, please try a more recent version (such as the [http://www.debian.org/devel/debian-installer/ latest beta] or [http://cdimage.debian.org/pub/cdimage-testing/daily/ daily build]), as your problem might already be solved.



List of questions

  1. Hardware is detected at install time but not after reboot.
  2. Why use DHCP automatically?
  3. I don't agree that DHCP should run automatically.
  4. Why not use an existing installer from another distro?
  5. Will there be a graphical installer?
  6. Will there be support for software RAID?
  7. How do I install using LVM?
  8. Is Serial ATA (SATA) hardware supported?
  9. How can I add support for a driver for which I have the sources?
  10. Is the 2.6 version of the Linux kernel supported?
  11. How to install with boot floppies + netinst.iso mounted as a loop device in the ramdisk from a ext2 partition?
  12. How can I create boot iso with my own set of packages?
  13. How can I build the DebianInstaller

  14. What is the difference between the different DHCP clients?
  15. After installation, my machine just keeps rebooting!
  16. Problems with ide-scsi module
  17. Why do I have to choose twice which mirror to use?
  18. Why doesn't the installer automatically choose an optimized kernel?
  19. How about SMP support?
  20. Why isn't the installed system configured to use the language I chose during installation?
  21. Why isn't X configured to use the keyboard I chose during installation?
  22. When I run the DebianInstaller, my keyboard doesn't work!

  23. Why isn't my NIC supported by DebianInstaller, I know the "tg3" driver supports it!

  24. There seems to be errors reading the CD!
  25. How can I install sid (unstable) with DebianInstaller?

  26. Why do I have to choose between ru and ru_RU in keymap chooser? Why choosing ru_RU gives unreadable messages after loading fresh Debian? (Beta 4).
  27. How do I copy d-i (log)files to a remote host using ssh?



Question 1: The installer detects my ethernet card and loads the proper modules for it, but when I reboot, no drivers are loaded (the card doesn't work).

Answer: This is most probably a known problem with discover-data. The problem will go away once discover-data is upgraded to a more recent version. This should have already happened now, so if you see the problem, let us know.


Question 2: Why does DebianInstaller always use DHCP? I want a static address!

Answer: There are currently two different ways of configuring a static IP setup:

  1. Run in normal mode and wait when the DHCP step is performed, if it fails you are given the option of configuring a static setup.
  2. Boot the installer in expert mode ("boot: expert"), and you will be able to configure a static address, and many other things besides. (Press F2 in boot screen for more information.)


Question 3: But DHCP shouldn't run automatically, it breaks on my system/gets the wrong information/is not what I want.

Answer: DebianInstaller is targeting a larger base of users than have historically installed Debian, including users who don't know what DHCP or static IP addresses are. Thus default behavior is chosen to use DHCP.

You can force static network configulation by providing boot parameter netcfg/use_dhcp=false at the boot prompt. (Press F7 in boot screen for more information.)


Question 4: Why are you doing this? Why not use Anaconda/PGI/whatever? Why reinvent the wheel?

Answer: We're doing this because it's time. Debian has been burdened with a sub-par installer for a full decade, and it's time to change all that. Debian's installer needs to work on more platforms and more types of install media than any other. We need to support installs to S/390 mainframes that have only a teletype console. We need to support installs to m68k boxes that boot from floppies, as well as to netbooting Sun hardware.

And yes, we want to support flashy easy installs on Intel clones booting from CD (and USB sticks). And many more; all the currenly targeted installation methods are listed [http://www.debian.org/devel/debian-installer/ports-status here].

PGI can't do this. Anaconda can't do this. Only a system designed from the ground up to be completly modular and highly flexible can do so. DebianInstaller is that installer.


Question 5: Is the DebianInstaller going to be graphical in nature? / Is there any prebuilt/downloadable graphical DebianInstaller?

Answer: The DebianInstaller will not be graphical by nature, but modularity is a key in its design. It would allow the use of different kinds of frontends, including those of a graphical nature.

There is a project underway to create a GTK frontend to the installer. For more information on the current status of this frontend see [http://www.debian.org/devel/debian-installer/gtk-frontend here]. Unfortunately the project hasn't seen much activity lately.


Question 6: Will the DebianInstaller support creating and installing to software RAID devices?

Answer: Latest sid_images are know to have RAID 0, 1, ?5?, but won't work for boot now with grub unpatched ([http:''/bugs.debian.org/cgi-bin/bugreport.cgi?bug=251905 #251905]).

.


Question 7: How do I install using LVM? Is there any more information about using the LVM installer? LVM installation doesn't work!

Answer: As of beta3 or later, LVM is fairly straightforward to configure using the menu item in the partitioner titled "Configure the Logical Volume Manager". Please note that it will probably help a lot if you know some [http://www.tldp.org/HOWTO/LVM-HOWTO/ LVM terminology] - it's recommended that you know the following three concepts: volume group (VG), physical volume (PV) and logical volume (LV) and how these relate to each other.

On Beta4, there are two bugs that currently make installation of LVM less than ideal ([http://bugs.debian.org/237466 237466] and [http://bugs.debian.org/239068 239068]). Currently partman won't let you build an LVM on top of a RAID device ([http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=251905 #251905]).

Also please note that LVM support was scheduled to change from being based on ["LVM1"] to based on ["LVM2"] (more information [http://bugs.debian.org/224661 here]). ["LVM2"] is based upon the device-mapper which is patched into Debian packaged 2.4 kernels (since 2.4.23) and available in ["vanilla"] 2.6 ["kernel"]s. Thus you might want to use daily builds in order to get a more "future-proof" system (additionally, the device-mapper provides the foundation for software RAID and other goodies).


Question 8: Is installation on SATA harddrives supported by DebianInstaller?

Answer: There are currently three options for SATA users:

  1. Get the [http://www.debian.org/devel/debian-installer/ latest beta] or [http://cdimage.debian.org/pub/cdimage-testing/daily/ daily build] of the DebianInstaller, the 2.4.25 kernel includes some support for SATA. This is expected to improve later as the kernel package used in the installer is updated to 2.4.26-2 or later where the SATA drivers have been included (as announced [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=246053 here]).

  2. Install using the Linux 2.6 kernel which should have support for your SATA hardware (boot the installer with "linux26").
  3. See if you can change your SATA settings in the BIOS from somethink like "Native mode" to "Compability mode" (might be labeled differently)

For a list of supported chipsets and thier status of support you may want to be assisted by [http://www.linuxmafia.com/faq/Hardware/sata.html]


Question 9: DebianInstaller does not include a driver for my xyz network card, but I have (tarball) driver sources. What are the steps for building that driver? Do the steps include the phrase, "Assume you have kernel-headers?" Do you think you'll be able to include kernel-headers for the installer's kernel image(s) in the CD image, so we don't have to sneaker-net them around?

Answer: It's possible to do this, but we do not yet have good end-user docs explaining how to do so. We're waiting for an end user to accomplish it and write them from experience. We're glad to help you through the process when you mail us at debian-boot@lists.debian.org (do not forget to add lspci -v output).


Question 10: Will there be support for Linux 2.6 kernels?

Answer: Boot with "linux26" for rather experimental support.


Question 11: How to install with boot floppies + netinst.iso mounted as a loop device in the ramdisk from a ext2 partition?

Answer: Find boot+initrd floppies, make an init that copies the netinst.iso into a ramdisk and pivot_root's to the iso and runs the iso's init.


Question 12: How can I create boot iso with my own set of packages?

Answer: see ?DebianInstallerModify


Question 13: How can I build the DebianInstaller?

Answer: see ?DebianInstallerBuild


Question 14: What's the difference between dhcp-client and dhcpcd ?

Context: I'm testing beta 3 of the Debian-Installer http://www.debian.org/devel/debian-installer/ .

When I install debian on a fresh machine and select "testing" and, inside tasksel, choose only

  [*] Broadband internet connection

, then it removes "dhcp-client" and installs "dhcpcd".

Why ? "dhcp-client" was working fine during the previous net-install.

Answer: Well dhcpcd conflicts with dhcp-client .. you might want to fill a wishlist bug for tasksel to better include already provided dhcp-client: [http://bugs.debian.org bug tracking system]


Question 15: Why after installer tells me its finished and reboot it ejects the cdrom and then after the machine start up, it enters the welcome debian screen, but then it keep rebooting?

Answer: ??? I think it is caused by watchdog timer enabled. Once you logged in, unload the module (eg. i810-tco). Then disable watchdog module from "hotplug" configuration file.


Question 16: Why does the installer ask for the ide-scsi module to install the system, when it clearly can use the normal ide-cd module to do this? Why is the ide-scsi module not included on the cd install, and where can we get it (I have tried the cd drivers boot floppy, no good)?

Answer: ???


Question 17: Why do I have to choose twice which mirror to use (at installation and later when base-config is performed)?

Answer: This is a known bug and it's being worked on (see bug number [http://bugs.debian.org/220269 220269] for the current status).


Question 18: Why doesn't the installer automatically choose the appropriate kernel to install (for example an i686 kernel instead of the generic i386)?

Answer: This is bug [http://bugs.debian.org/237529 237529] and it should be fixed by now. If you still see this problem in a recent installer, please reopen that bug and include the content of /proc/cpuinfo and which kernel version should be installed for your processor.


Question 19: What about SMP support?

Answer: The installer itself does not need any SMP support and will not boot with an SMP enabled kernel since it merely needs to install the system to your machine.

When the system is being installed, it would be nice if SMP was automatically detected and the appropriate kernel was chosen though (which would mean that SMP was enabled when you boot into your newly installed Debian system).

There is currently a bug filed against the DebianInstaller, requesting this feature. You can see it's current status by looking at [http://bugs.debian.org/246483 the bug report].


Question 20: Why isn't the installed system configured to use the language I chose during installation?

Answer: This problem will likely remain until bugs [http://bugs.debian.org/237387 237387] and [http://bugs.debian.org/244475 244475] are fixed. If you still experince problems with an installer version which is released after these two are fixed, please reopen the appropriate bug.


Question 21: Why isn't X configured to use the keyboard I chose during installation?

Answer: This is a known problem, to check if it has been fixed or to track it's progress, see bug report [http://bugs.debian.org/238778 238778].


Question 22: When I run the DebianInstaller, my keyboard doesn't work!

Answer: This seems to be especially common on laptops. Try booting with no APIC and no local APIC support ("boot: linux noapic nolapic").


Question 23: Why isn't my NIC supported by DebianInstaller, I know the "tg3" driver supports it!

Answer: As tg3 contains firmware which does not seem to meet the requirements of DFSG (the Debian Free Software Guidelines), a decision has been made to remove the driver from debian packaged kernels (more information [http://lists.debian.org/debian-devel/2004/04/msg05149.html here] and [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=239952 here]). The tg3 driver is currently still in the 2.4 kernels though, so a workaround would be to make an installation with 2.4 and then compile your own version of the 2.6 kernel which includes the tg3 driver.


Question 24: There seems to be errors reading the CD!

Answer: First of all, check that the ["MD5"]-sum of the ISO file you downloaded is correct. If you are positive that the CD is correct, it could be that the CD-ROM is old and/or flaky when using DMA. Try disabling DMA for the CD-ROM (by booting with "linux ide=nodma"), unfortunately this boot option is currently broken (see bug [http://bugs.debian.org/226057 226057]).


Question 25: How can I install sid (unstable) with DebianInstaller?

Answer: You have to use a sid (unstable) version of the DebianInstaller which can be found [http://cdimage.debian.org/pub/cdimage-testing/sid_d-i/ here].


Question 26: Why do I have to choose between ru and ru_RU in keymap chooser? Why choosing ru_RU gives unreadable messages after loading fresh Debian? (Beta 4).

Answer: ???


Question 27: How do I copy d-i (log)files to a remote host using ssh?

Answer: You need the network-console installer module:

  1. Start the installer in expert mode (or medium priority)
  2. At Load installer components select network-console from the list

  3. Select Continue installation remotely using SSH from the menu to configure sshd.

  4. Go to ["VT2"] and edit /'/etc/passwd'/; copy the line for user installer; in the copied line, change the username (first field) and change /'/bin/network-console to /bin/sh'/ (last field)

  5. From the remote system, you should now be able to copy files from d-i by executing e.g. /'ssh <username>@<ip-address> "cat /var/log/syslog" >syslog'/ using the same password you entered while configuring sshd


List of changes

  • FJP -- 2004-July-12
    • Added info on copying files using ssh
  • Osamu -- 2004-June-18
    • Added info on DHCP/FIX IP issue
  • AlexeyS -- 2004-June-06
    • Added question 26 about ru_RU
  • DavidH -- 2004-05-09
    • Answered sid question
  • DavidH -- 2004-05-06
    • Added CD-ROM read errors question
  • DavidH -- 2004-05-05
    • Added X keyboard question
    • Added dead keyboard question
    • Added missing tg3 driver question
    • Corrected question numbering
  • DavidH -- 2004-05-03
    • Added more information to LVM question
    • Added 3 more questions (locales, SMP, auto-kernel selection)
    • Changed layout a bit, added more text to initial Note