Re: amd64 installation images
On Tue, Sep 07, 2004 at 04:38:00PM +0200, Goswin von Brederlow wrote: > > If I get the idea correctly, this is what happens basically: > > 1) kernel and initrd get loaded > > 2) modules from initrd are loaded as far as they are needed to get > > additional software (packages, modules) from the net. > > Additional software is called a "component" afaik. Those are the > udebs. Some components contain kernel modules like the disk drivers, > others the programs to partition the disk or install base. > > 3) the installer starts and loads any modules needed to do the > > install (SCSI/SATA/PATA/whatever drivers primarily) from the net > > Actualy it installs the extra components containing the kernel modules > and then a component with the full discover data file that then also > runs discover again with all modules present. Ok, so one of the components needs to contain 3ware 9xxx drivers, as well as 7/8xxx. The head node of my cluster, which should be arriving RSN, has all its disks connected to the 3ware card. -- #define X(x,y) x##y Peter Cordes ; e-mail: X([EMAIL PROTECTED] , des.ca) "The gods confound the man who first found out how to distinguish the hours! Confound him, too, who in this place set up a sundial, to cut and hack my day so wretchedly into small pieces!" -- Plautus, 200 BC
Re: amd64 installation images
Sven Mueller <[EMAIL PROTECTED]> writes: > Goswin von Brederlow [u] wrote on 06/09/2004 21:04: > >> Sven Mueller <[EMAIL PROTECTED]> writes: >>> >>>I am planning to deploy the amd64/pure64 version of Debian on a new >>>system. However while investigating the netinst images at >>>http://debian-amd64.alioth.debian.org/debian-installer/daily/netboot/ >>>I noticed that the initrd misses something I would need in there: the >>>3ware 3w-.ko and/or 3w-9xxx.ko kernel modules. >>> >>>Would it be possible to add those to the initrd? It seems that the >>>3ware 9000 series is pretty popular among AMD64 users. >>> >> The netboot images have no disk or cdrom drivers at all and don't >> need >> any. They are ment for pure network installs and download exra modules >> over the net. > > Hm? I'm sorry I don't really understand what you say. Or at least I'm > not certain I do. How do the netboot images work, if they don't have > any cdrom drivers? > 1) If they don't access the cdrom itself (apart from loading the initrd > perhaps), why do the images include any packages at all? If what you > said is correct, those packages can't be accessed, so they would be > a waste of storage. That is the reason that the netboot doesn't contain any packages and it is only 4MB big. > 2) How do they store whatever they load of the net? In a ramdisc? tmpfs or ramdisk depending on the architecture and kernel. > I must admit I never dissected any netboot image before, and I > obviously can't try the amd64 image yet, since I don't have the > hardware yet. But I am eager to learn, so what is the mechanism behind > the netboot images? What do they load to which destination during each > step of the boot and installation process? > > If I get the idea correctly, this is what happens basically: > 1) kernel and initrd get loaded > 2) modules from initrd are loaded as far as they are needed to get > additional software (packages, modules) from the net. Additional software is called a "component" afaik. Those are the udebs. Some components contain kernel modules like the disk drivers, others the programs to partition the disk or install base. > 3) the installer starts and loads any modules needed to do the > install (SCSI/SATA/PATA/whatever drivers primarily) from the net Actualy it installs the extra components containing the kernel modules and then a component with the full discover data file that then also runs discover again with all modules present. > 4) destination media get's partitioned and mounted > 5) the real installation starts Which again are just some components being run. > Is that more or less right? Yep. > cu, > sven MfG Goswin
Re: amd64 installation images
Goswin von Brederlow [u] wrote on 06/09/2004 21:04: Sven Mueller <[EMAIL PROTECTED]> writes: I am planning to deploy the amd64/pure64 version of Debian on a new system. However while investigating the netinst images at http://debian-amd64.alioth.debian.org/debian-installer/daily/netboot/ I noticed that the initrd misses something I would need in there: the 3ware 3w-.ko and/or 3w-9xxx.ko kernel modules. Would it be possible to add those to the initrd? It seems that the 3ware 9000 series is pretty popular among AMD64 users. The netboot images have no disk or cdrom drivers at all and don't need any. They are ment for pure network installs and download exra modules over the net. Hm? I'm sorry I don't really understand what you say. Or at least I'm not certain I do. How do the netboot images work, if they don't have any cdrom drivers? 1) If they don't access the cdrom itself (apart from loading the initrd perhaps), why do the images include any packages at all? If what you said is correct, those packages can't be accessed, so they would be a waste of storage. 2) How do they store whatever they load of the net? In a ramdisc? I must admit I never dissected any netboot image before, and I obviously can't try the amd64 image yet, since I don't have the hardware yet. But I am eager to learn, so what is the mechanism behind the netboot images? What do they load to which destination during each step of the boot and installation process? If I get the idea correctly, this is what happens basically: 1) kernel and initrd get loaded 2) modules from initrd are loaded as far as they are needed to get additional software (packages, modules) from the net. 3) the installer starts and loads any modules needed to do the install (SCSI/SATA/PATA/whatever drivers primarily) from the net 4) destination media get's partitioned and mounted 5) the real installation starts Is that more or less right? cu, sven
Re: amd64 installation images
Sven Mueller <[EMAIL PROTECTED]> writes: > Hi. > > I am planning to deploy the amd64/pure64 version of Debian on a new > system. However while investigating the netinst images at > http://debian-amd64.alioth.debian.org/debian-installer/daily/netboot/ > I noticed that the initrd misses something I would need in there: the > 3ware 3w-.ko and/or 3w-9xxx.ko kernel modules. > > Would it be possible to add those to the initrd? It seems that the > 3ware 9000 series is pretty popular among AMD64 users. > > cu, > sven The netboot images have no disk or cdrom drivers at all and don't need any. They are ment for pure network installs and download exra modules over the net. MfG Goswin
amd64 installation images
Hi. I am planning to deploy the amd64/pure64 version of Debian on a new system. However while investigating the netinst images at http://debian-amd64.alioth.debian.org/debian-installer/daily/netboot/ I noticed that the initrd misses something I would need in there: the 3ware 3w-.ko and/or 3w-9xxx.ko kernel modules. Would it be possible to add those to the initrd? It seems that the 3ware 9000 series is pretty popular among AMD64 users. cu, sven
