Thanks very much for the information, I suspected something along these lines. The reason I didn't install it with the same boot order was to have a free check to do anything with the linux install and the boot loaders, and I didn't want to hurt the windows partition. As I am running trials with the installer, it doesn't matter that much at this point (as I'm like erasing and reinstalling debian every other day), but I'll now do it properly :)
Thank you again, I am grateful that there are people willing to spend the time to educate me. Best regards, Remi Butaud On Tue, 29 Mar 2005 12:23:26 -0500, Lennart Sorensen <[EMAIL PROTECTED]> wrote: > On Sun, Mar 27, 2005 at 03:19:02PM +0200, Remi Butaud wrote: > > Debian-installer-version: > > http://debian-amd64.alioth.debian.org/debian-installer/2005-03-24/monolithic/mini.iso > > uname -a: Linux owl 2.6.8-10-amd64-k8 #1 Tue Mar 15 17:25:19 CET 2005 > > x86_64 GNU/Linux > > > > Date: March - 27, 2005 > > Method: netinstall from > > ftp://mirror.switch.ch/mirror/debian-amd64/pure64 testing main contrib non-f > > ree > > and > > http://debian-amd64.alioth.debian.org/pure64 testing main contrib non-free > > (some packages were not available from the switch mirror or the > > network was choppy) > > > > > > Machine: Custom machine, Asus K8N-E Deluxe Motherboard > > Processor: AMD64 3200+ > > Memory: 2x512 MB Cordair Xmms > > Root Device: IDE : /dev/hda1 (secondary devices on /dev/sda /dev/sdb : sata) > > Root Size/partition table: > > > > # <file system> <mount point> <type> <options> <dump> <pass> > > proc /proc proc defaults 0 0 > > /dev/hda1 / ext3 defaults,errors=remount-ro 0 1 > > /dev/hda6 /home ext3 defaults 0 2 > > /dev/hda7 /linux32 ext3 defaults 0 2 > > /dev/hda8 /windows vfat defaults 0 2 > > /dev/hda5 none swap sw 0 0 > > /dev/hdc /media/cdrom0 iso9660 ro,user,noauto 0 0 > > /dev/hdd /media/cdrom1 iso9660 ro,user,noauto 0 0 > > /dev/fd0 /media/floppy0 auto rw,user,noauto 0 0 > > Note : the SATA disks are not mounted yet (WinXP) > > (mount -t ntfs /dev/sda1 /xproot does the trick) > > > > Output of lspci and lspci -n: > > lspci > > 0000:00:00.0 Host bridge: nVidia Corporation: Unknown device 00e1 (rev a1) > > 0000:00:01.0 ISA bridge: nVidia Corporation: Unknown device 00e0 (rev a2) > > 0000:00:01.1 SMBus: nVidia Corporation: Unknown device 00e4 (rev a1) > > 0000:00:02.0 USB Controller: nVidia Corporation: Unknown device 00e7 (rev > > a1) > > 0000:00:02.1 USB Controller: nVidia Corporation: Unknown device 00e7 (rev > > a1) > > 0000:00:02.2 USB Controller: nVidia Corporation: Unknown device 00e8 (rev > > a2) > > 0000:00:05.0 Bridge: nVidia Corporation: Unknown device 00df (rev a2) > > 0000:00:08.0 IDE interface: nVidia Corporation: Unknown device 00e5 (rev a2) > > 0000:00:0a.0 IDE interface: nVidia Corporation: Unknown device 00e3 (rev a2) > > 0000:00:0b.0 PCI bridge: nVidia Corporation: Unknown device 00e2 (rev a2) > > 0000:00:0e.0 PCI bridge: nVidia Corporation: Unknown device 00ed (rev a2) > > 0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge > > 0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge > > 0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge > > 0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge > > 0000:01:00.0 VGA compatible controller: ATI Technologies Inc Radeon > > R350 [Radeon 9800 Pro] > > 0000:01:00.1 Display controller: ATI Technologies Inc Radeon R350 > > [Radeon 9800 Pro] (Secondary) > > 0000:02:09.0 Multimedia audio controller: Creative Labs SB Audigy (rev 03) > > 0000:02:09.1 Input device controller: Creative Labs SB Audigy > > MIDI/Game port (rev 03) > > 0000:02:09.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port > > 0000:02:0b.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 > > Host Controller (rev 80) > > 0000:02:0c.0 RAID bus controller: Silicon Image, Inc. (formerly CMD > > Technology Inc) SiI 3114 [SATALink/SATARaid] Serial ATA Controller > > (rev 02) > > > > lspci -n > > lspci -n > > 0000:00:00.0 0600: 10de:00e1 (rev a1) > > 0000:00:01.0 0601: 10de:00e0 (rev a2) > > 0000:00:01.1 0c05: 10de:00e4 (rev a1) > > 0000:00:02.0 0c03: 10de:00e7 (rev a1) > > 0000:00:02.1 0c03: 10de:00e7 (rev a1) > > 0000:00:02.2 0c03: 10de:00e8 (rev a2) > > 0000:00:05.0 0680: 10de:00df (rev a2) > > 0000:00:08.0 0101: 10de:00e5 (rev a2) > > 0000:00:0a.0 0101: 10de:00e3 (rev a2) > > 0000:00:0b.0 0604: 10de:00e2 (rev a2) > > 0000:00:0e.0 0604: 10de:00ed (rev a2) > > 0000:00:18.0 0600: 1022:1100 > > 0000:00:18.1 0600: 1022:1101 > > 0000:00:18.2 0600: 1022:1102 > > 0000:00:18.3 0600: 1022:1103 > > 0000:01:00.0 0300: 1002:4e48 > > 0000:01:00.1 0380: 1002:4e68 > > 0000:02:09.0 0401: 1102:0004 (rev 03) > > 0000:02:09.1 0980: 1102:7003 (rev 03) > > 0000:02:09.2 0c00: 1102:4001 > > 0000:02:0b.0 0c00: 1106:3044 (rev 80) > > 0000:02:0c.0 0104: 1095:3114 (rev 02) > > > > > > > > Base System Installation Checklist: > > [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it > > > > Initial boot worked: [O] > > Configure network HW: [E] > > Config network: [O] > > Detect CD: [O] > > Load installer modules: [O] > > Detect hard drives: [O] > > Partition hard drives: [O] > > Create file systems: [O] > > Mount partitions: [O] > > Install base system: [O] > > Install boot loader: [O] > > Reboot: [O] > > > > Comments/Problems: > > > > When detecting the network HW (embedded nForce 3 controler), I had > > only 2 NIC detected, the two firewire ports (as eth0 and eth1). I had > > to exit from the installer, execute a shell command: #modprobe > > forcedeth > > and then back into the installer. I was wondering why the initial > > kernel didn't have the forcedeth module instaled or whether it was a > > problem with the detection of the nForce 3 controler. > > > > Another thing that is a bit annoying, and that may be due to my own > > lack of knowledge, is the boot utility (either grub or lilo) which > > doesn't do what I would like it to. > > I was usually starting another OS on /dev/sda1, with the Bios boot > > device being the associated SATA disk. I started installing debian on > > a PATA disk, at /dev/hda1, and I changed the boot sequence in the BIOS > > to go for IDE0 as primary disk. > > The installer does detect that there's another OS installed, and puts > > it in the boot menu, but trying to start it form the boot loader > > doesn't work. Of course, if I revert to having the SATA disk as > > primary boot from the Bios I can boot on /dev/sda1 - but I can't boot > > my debian, of course. > > I did that because I didn't want the boot loader to mess up with the > > other OS (which I cannot afford to lose) but that was certainly a bad > > idea. I'd appreciate any thought on the subject. > > > > Here is the automatic grub generated menu.lst I'm not sure about the (hd1,0) > > > > # This entry automatically added by the Debian installer for a non-linux OS > > # on /dev/sda1 > > title Microsoft Windows XP Professional > > root (hd1,0) > > savedefault > > makeactive > > chainloader +1 > > Well since windows thinks it is on hardisk 0, partition 0 in it's > boot.ini, it won't boot this way unless you do mapping of the drives > too. The installer has no way to know that. > > If you had NOT changed the drive order before installing and had > installed the boot loader to the MBR of the windows drive, everything > should just have worked. Changing drive orders around on a system > already in use is simply asking for trouble since you will for sure > confuse the boot loaders already installed. > > You have to decide what drive is going to be the boot drive, and then > install the whole system with the drives in those positions. If you > don't want to reinstall windows, you have to leave it as it was when > windows was installed, and then install linux with the drives in that > position. > > Len Sorensen > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]