Last edit: Daniel Siboska on April 9, 2006 16:31 (4762 days, 12 hours and 24 minutes ago) (diff)
I915gmm.Gratiswiki.Dk | RecentChanges | Preferences | GratisWiki
How to install Debian sarge
Trying to install Debian 3.1r0 (sarge) can be a bit tricky.
For sure you will want to use "enhanced mode" as bios setting for the ATA ports.
The problem is that the default installer (using kernel 2.6.8) will not recognize the disks because it does not work with the controller.
How can you still install Debian 3.1?
- Install guide for debian sarge
- (A pseudo solution is to use the Debian testing installer (etch))
PATA as main (root) disk
- Use combined mode in BIOS, and your disk will be detected by the installer and you'll be able to install debian sarge on it. (unconfirm?) (there are some issue with the CD drive not getting recognized, will look into this; Daniel). After successful installation one can compile a custom kernel (with ahci an piix) and switch back to "enhanced mode".
SATA as main (root) disk (on SATA port 1 or 2) and CD/DVD-ROM on PATA port
- If you manage to install Debian sarge on a SATA disk (eg. by using a PCI SATA card) you'll probably want to connect the SATA disk to port 1 and boot a kernel that has ahci support. The trick here is to boot a kernel from a floppy/PATA drive but use your SATA disk as root (/), and once you've got your system up and running, install the ahci enabled kernel on the SATA disk.
- "Combined mode" in the bios will not help here. But another way is to use "SATA only" mode. This means that you will loose support for the CD-ROM on the PATA port. Therefore you could use an external USB CD-ROM drive for installing Debian sarge. After installation create a custom kernel (>=2.6.12) or install the 2.6.12 kernel-image from the testing archive. Now switch back to "enhanced mode" and boot with the new kernel. The problem is that you have to change some configs to make this work. Can anybody help here? After rebooting the 2.6.12 kernel (image from debian testing) I get "Kernel panic - not syncing: Attempted to kill init!"
Daniel answers: It sounds as if you got the root (/) set to the wrong/missing partition. If you're using GRUB, check to see that hd0 or whatever you're booting from is the correct disk (you can use cat in GRUB's command prompt).
GratisWiki hostes af HOW