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

Bug#235418: Various blocking problems installing on a RAID server -- d-i snapshot of 23/02/2004



* Alessandro Polverini <alex@nibbles.it> [2004-02-29 10:52]:
> 1) I have a davicom network card, the system used the "tulip" driver
> for it, but it didn't work since the right driver is "dmfe".
> This is valid during the install phase as well as on the newly
> installed system, i.e.: discover use the wrong driver for the net card.

Can you try new images from
http://gluck.debian.org/cdimage/testing/sarge_d-i/ and report whether
they load the right module.  Can you also boot with linux26 and check
if the right module is loaded there.

> 2) During the install, the installer nicely prompted me to choose the
> network card between eth0 and eth1, but I had no clue to which one was
> what. It would be _very_ helpful if it was possible to have some more

A description is displayed now.

> 3) In a similar way, when grub asks on which device to install, I'm
> totally blind on knowing if hd0 is the ide this and hd1 the raid one
> or viceversa. Having some more informations like the size of the disk,

You can use standard device names (/dev/sda...) now.

> 5) Discover correctly loads the piix module for the ide controller, but
> loads it _after_ ide-detect and this is wrong, for two reasons:
> - on kernels 2.4.x that works but the disk are used without DMA and
>   so are so slow to be almost unusable. See below with problems with
>   related problems with hdparm
> - on kernels 2.6.x that does not work b/c the ide-detect module keeps
>   the irq of the controller and the piix driver can't even start

Can you check if this is still being done?

> 6) hdparm is unable to set disk parameters during the boot because the
> IDE drivers are loaded by discover _after_ hdparm starts, so hdparm
> finds no ide drives on the systems and aborts

Hmm, that's quiet stupid.  I suppose this is still there... can you
check and confirm?

> 7) the installation correctly uses the "megaraid2" driver for my raid
> controller but the driver "megaraid" is not used on the initrd image, 
> so, after the reboot, the old and limited driver is used on the system
> instead.

So there's a megaraid and a megaraid2 driver, and the old megaraid
driver is used for the initrd?  Is this still true?
-- 
Martin Michlmayr
tbm@cyrius.com



Reply to: