Thanks Ross. I'd like to elaborate on the two name changes I mentioned. 1) hd0 vs. hd1 - during the whole install hd1 is the drive used for /boot and / partitions and grub menu.lst which BTW is good :-). GRUB menu.lst, remapping in it, and device.map correspond to d-I names however new kernel device names are exchanged, i.e., hd0 becomes hd1 and hd1 becomes hd0. I had to remove map command and uniformly replace hd1 with hd0. BTW I use windows XP boot to switch to GRUB. I do not think it should matter though. 2) d-I names as eth0 and eth1 ieee1394 and then Broadcom on-board NIC as eth2, loads tg3, and configures IP properly (static IP address). The NIC works (I checked on alt term) and everything is OK until it gets to apt configuration where it cannot read from the mirror (arizona...). I had to disable loading ieee1394 by specifying rubbish as driver parameters (I did not know any better way) and thereby making Broadcom NIC the only one and eth0 of course. Everything went smoothly. Of course I made expert install. Sorry if this is not the right place to file this report and please feel free to forward it appropriately. Anyway, have wonderful holidays, Latchezar Dimitrov > -----Original Message----- > From: Ross Boylan [mailto:RossBoylan@stanfordalumni.org] > Sent: Wednesday, December 28, 2005 1:10 AM > To: Latchezar Dimitrov > Cc: debian-boot@lists.debian.org; Ross Boylan > Subject: Re: Device name discrepancies > > On Tue, Dec 27, 2005 at 02:27:12PM -0500, Latchezar Dimitrov wrote: > > Initial device names often differ from after base install > ones, e.g. > > hd0 and hd1, eth0 and eth2 in my case. > > > > This may mislead to driver issues (as I was misled in eth case) and > > cause wasting a lot of time since actually there is no driver issue > > and therefore nothing published. > > > > My suggestion is to put forward: "If experiencing problem(s) with a > > device/device driver first make sure the device names > before and after > > base install are the same" and some advice to manual work. > > > > Thanks, > > > > Latchezar Dimitrov > > > Since someone encountering problems is probably after the > base install, they won't necessarily know what things were > like before hand. > > Perhaps there is a way to record configuration information beforehand > (automatically) so that someone could refer to it later. I'm > not sure how feasible this is, as one would need to know not > only the devices but which physical hardware was attached. > > The best solution is to keep the names stable. If that's not > possible, it does seem like a good idea to alert people to > the possibility that names might change. > > Ross >
Attachment:
device.map
Description: device.map
Attachment:
ORIG.menu.lst
Description: ORIG.menu.lst