Christian, Thank you for your reply. I have done this with the one on the CD, and the disk works to load the drivers during the install. The problem is at the end of the install, after its done partitioning and done copying everything over, it copies over the extra modules. However, I would think there would be a problem if there was just a BOOT driver, so I created both. Next I am going to try editing the current drvblock.img on the CD and replacing it back onto the CD with everything left there except for a few I won't be using so there is enough room. However, again, I don't know how I will take care of the module without the BOOT, as the original drvblock.img doesn't contain non-BOOT modules. I guess they are copied over during the install in an RPM. Looking on this list, the only mention of driver disks had been during Trustix 1.5, and none with the 2 series, however I may be wrong. This is what leads me to believe that its in the installer, since the 2 series. I will file a bug report, where do I do that? I just hope I can get a working system by Friday... my customer is getting very antsy.
Thanks, Jason On Wed, 2005-03-09 at 03:30, Christian Haugan Toldnes wrote: > (Mar 08 2005 18:48) Jason C. Greb wrote: > > Can anyone help me? I have to get everything setup and finished by > > Friday, and I have already been working on it for about a week now. I am > > soo close to getting it cracked, but I seem to have come across this > > issue. I have done the stuff manually, but that does not seem to work. I > > am thinking it runs more commands after that that I don't see. > > Hi Jason > > Are you having problems with the official driver disks? like with: > http://http.trustix.org/pub/trustix/releases/trustix-2.2/i586/images/drvblock.img > > If so it should be reported as a bug in the installer for TSL-2.2. > > If the problem only occurs with customized driver disks, there must be a > problem with the customization or creation of the disk. > > I'm almost ashamed to say this but as far as I remember every success > story about driver disks on Trustix have been something like this: > > 1: grab the latest driver disk from http.trustix.org > 2: grab the latest kernel source rpm (must correspond to the one on the CD) > 3: get the -BOOT config file from ./configs in the source tree and place > it as ./.config > 4: insert the new driver code into the tree to replace the old driver > code. > 5: make oldconfig dep modules (remember stack protection issues) > 6: loopback mount the driver disk > 7: unzip modules.cz > 8: replace the driver with the one you just compiled > 9: wrap the driver disk back up. > > The reason I feel ashamed is that we really really really should have > made a mkbootdisk script that at least handles points [1,6-9], so that > people could do this more easily. I actually looked into it once, and > the task is very much something that can be done with moderate > programmin skills (preferably in bash or python, anyone? ;) ) > > Anyway, the procedure I just described should get you going. > > > kind regards > > > c -- Jason C. Greb <[EMAIL PROTECTED]> ElectroNerdz, Inc. _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
