[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#305336: ASUS - K8N-E Deluxe Install Report / Using Debian Installer RC3

reassign 305336 discover1-data
retitle 305336 Please list forcedeth driver for 10de:00df

On Tuesday 19 April 2005 13:41, Remi Butaud wrote:
> Errors:
> -----
> 1. Configure Network Interface : the nvidia nforce3 ethernet
> integrated controler is not detected, only the two firewires are
> (ethernet over ieee1394). So I have to get out of the installer
> (different console, or exit through the menu) and type
> modprobe forcedeth

Reassigning this report to discover1-data to add this info.
0000:00:05.0 Bridge: nVidia Corporation: Unknown device 00df (rev a2)
0000:00:05.0 0680: 10de:00df (rev a2)

Current entry in discover1-data:
10de00df        unknown unknown CK8S Ethernet Controller
Please change to:
10de00df        ethernet forcedeth CK8S Ethernet Controller

> 2. Reboot
> The first disk in the BIOS is the SATA (/dev/sda1) which is where
> winXP lives. I install debian on the /dev/hda1 (PATA) disk, but the
> bootloader somehow gets installed in the /dev/hda1 MBR, so when it
> reboots, it reboots to window (/dev/sda1) and not linux.

It does not "somehow" get installed there... The dialog for GRUB says that 
GRUB will be installed "to the MBR of the first hard drive" by default.

> If I change the order of the disk drives in the BIOS to get the disk
> on /dev/hda1 as first HD instead of /dev/sda1, the settings in the
> grub bootloader are wrong, and it won't let me boot windows.
> So I have to change those settings from :
> title           Microsoft Windows XP Professional
> root            (hd1,0)
> savedefault
> makeactive
> chainloader     +1

I think just changing to 'root (hd0,0)' should work as well.

> to:
> title           Microsoft Windows XP Professional
> root            (hd1,0)
> savedefault
> map (hd0) (hd1)
> map (hd1) (hd0)
> makeactive
> chainloader     +1
> That does the trick.
> I also have to mention that if I change the order of disk drives in
> the BIOS before installing, it doesn't work either (same situation as
> installing then changing the disk order).

That is because changing the order of drives in the BIOS does not change 
their "physical" order.


Reply to: