Submitted 23-Sep-00 by Bruce LaZerte: > ** Reply to message from Bruce LaZerte <[EMAIL PROTECTED]> on Fri, 22 Sep 2000 > 12:21:24 -0400 > Well I went ahead and did it anyway and the results are not tooooo bad. :) > 1) supermount is missing. Anybody know where I can get a supermount patch? One place is http://www.geocities.com/SiliconValley/Lab/8144/supermount.html > 2) USB interface modprobe error message during boot. Since I don't use USB I > didn't include any of the relevant code. Maybe I should put it back in the base > code? Whichever module it's trying to load, you could add to modules.conf aliased to off. > 3) CD-RW is not detected during boot up and I get a menu asking me whether to > keep trying to find it at next boot, or not. Could this be a supermount problem > as well? Or perhaps because I stripped out all the SCSI code? It's an ATAPI > CD-RW but aren't these translated into pseudo-scsi devices somewhere? You do need SCSI support for it. From memory, in addition to the ide-scsi module, you need the sg and sr_mod modules (or build them into the kernel). The sg module is used for burning and other lowlevel access, and sr_mod is needed for accessing SCSI CD-ROMs which is what the kernel is told to treat it as when you pass hdx=ide-scsi as a boot option. (replace hdx with your device, of course) > By the way, I've been told in a newsgroup that both Slackware and Debian > distributions use only plain vanilla kernels and official ftp.kernel.org > patches. As far as I can tell, only Slackware provides KDE (& Gnome). So if > you need to be at the bleeding edge and apply patches, maybe one of those > two distributions would be a better choice than Mandrake. I haven't used slack, but the vanilla kernel and no KDE is part of the Debian philosophy. The problem really is that all patches assume that they are the only patch that will be applied. Once you get more than a few, you frequently start running into conflicts. Patching something as complicated as the kernel, it is a safe bet that you will have to tinker with the patch to make it apply, especially if it wasn't written specifically for the patch level you are using. That said, I have had times that a patch applied cleanly and compiled fine, clean applications and failed compiles, and instances in which I spent days going through .rej files (and the corresponding original files) to put together a patch for the patch. That last is certainly time consuming, but it is really the only way to get some patches to apply. For example, the most recent supermount patch for 2.2 kernels is for 2.2.16, expect problems applying it to 2.2.17 or 2.2.18pre? -- Anton Graham GPG ID: 0x18F78541 <[EMAIL PROTECTED]> RSA key available upon request Do not meddle in the affairs of the undead, for you are crunchy and good with ketchup.
Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
