adding custom module - other aproach
Hi again
Being determined to get it done, I decided to go via the "modify existing
cd image" way, as described at
http://wiki.debian.net/index.cgi?DebianInstallerModify
Here is what I did:
* compiled a 2.6.8-1-386 kernel, exactly the same config as sarge kernel,
except my custom scsi module is extra.
* installed this kernel on my prototype box (vmware if that matters).
* downloaded linux-kernel-di-i386-2.6-0.69
* added my module to modules/i386/scsi-extra-modules.
* fakeroot debian/rules binary.
If I unpack the resulting scsi-extra-modules-2.6.8-1-386-di_0.69_i386.udeb
there is my shiny module.
Now I donwload, mount, and rsync the contents of sarge-netinst.iso to a
custom folder.
I replace the stock scsi-extra-modules-2.6.8-1-386-di_0.69_i386.udeb with
my own udeb.
Then I fix all the md5-sums: md5sum `find -follow -type f` > md5sum.txt.
[note: Besides this, I also had to fix the md5sum of my new udeb in
dists/sarge/main/debian-installer/binary-i386/Packages and
dists/sarge/main/debian-installer/binary-i386/Packages.gz. Could someone
add this the webpage?? ]
Then I generate an ISO.
The resulting installer won't find any harddisks, but after manually
insmodding the modules, it does.
So far so good.
My theory behind this is, that by providing a custom scsi-extra udeb,
the installer kernel can recognize my controller (which is true).
Also, I assume this udeb will also be used for installing the kernel
onto the /target (right??).
When the installer install the kernel, it bails out when creating the
initrd (no module "arcsmr").
ANyone?
--
* *** Dick Visser TIENHUIS Networking
** * * Marco Polostraat 234-3 P: +31206843731
* * *** 1056 DP Amsterdam F: +31208641420
* * * * The Netherlands M: +31622698108
* ** * IP-phone (SIP)/email: dick@tienhuis.nl
* * * PGP-key: http://www.tienhuis.nl/gpg.txt
* * * Stream: mms://vsdev.tienhuis.nl/stream2
*** ***
Reply to: