RE: 3.1, megaraid2 install cd
The alternative, which is how I proceeded, was the following:
...
6. Complete base system install, install grub, DON'T reboot
7. Change to VC2 - The rest is done here
8. mount -t proc dummy /target/proc
9. chroot /target
10. edit /etc/apt/sources.list to use unstable
11. install kernel 2.6.10 or later (kernel-image-2.6.11-9-em64t-p4-smp right now)
12. add 'megaraid_mbox' to /etc/mkinitrd/modules
13. make a new initrd to include the scsi driver: 'mkinitrd -o <filename> <kernel-version>'
14. reboot, and run with it (make sure grub is set to use the newly created initrd)
15. change /etc/apt/sources.list back to sarge, or use apt-pinning to track kernel image also
A few (I remember 2) packages get pulled in as dependencies from sid, but I have had no problems, and at the time I looked at the differences in the sarge and sid packages, they were trivial.
Joel Johnson
-----Original Message-----
From: John Madden [mailto:jmadden@ivytech.edu]
Sent: Fri 6/17/2005 1:57 PM
To: Joel Johnson
Cc: debian-amd64@lists.debian.org; Joel Johnson
Subject: Re: 3.1, megaraid2 install cd
Ok, the whole thing *does* work after some hacking around with it and loading the
megaraid2 module manually. The problem I had with the mirror was that my network
port had been disabled by our network folks. :)
After the first boot, I noticed that the installer had still installed the 2.6.8
kernel however, so the box still wouldn't boot on its own. Back to the 3.1pre
boot disc, mount up the installed partition, chroot, apt-get install all of the
necessary devel utils, build a custom kernel, and *then* it's good to go. It's
quite a convoluted mess, but it's enough until a more up-to-date boot ISO is
available.
John
--
John Madden
UNIX Systems Engineer
Ivy Tech Community College of Indiana
jmadden@ivytech.edu
Reply to: