--- Paul E Condon <[EMAIL PROTECTED]> wrote: > On Thu, Oct 16, 2003 at 03:27:32PM -0700, Sidney > Brooks wrote: > > > > --- Paul E Condon <[EMAIL PROTECTED]> wrote: > > > On Thu, Oct 16, 2003 at 01:48:01PM -0700, Sidney > > > Brooks wrote: > > > > Without going through the whole thread, my problem > > seems to be that I have created a new kernel that > will > > let me use CD writing, but I have not been able to > get > > my computer to use this new kernel. The kernel is > in > > the form ... .deb. > > > > > > > Yes, I think I recall that you did have a bootable > kernel that did not > make cdrecord work. Now you have also a kernel that > you hope has > features that make cdrecord work, but you don't know > for sure because > you can't boot it and check. > > You have a .config of your new kernel. If you can > get the .config that > was used to produce your bootable kernel, you can > diff compare the two > .config files. Look for differences that are NOT > things that you know > you put there for cdrecord. These are things that > are needed for your > computer, but are not part of the default .config . > Add these to the > .config that already has your special stuff for > cdrecord. > > HTH, or maybe you've already done that. > > Are you switching kernel versions in the process of > debugging cdrecord > functionality? Try, instead, simply switching kernel > versions without > mucking about with cdrecord. For this first switch, > you should use a > debian pre-packaged kernel. If you can't get your > hardware working at > the desired kernel version level with a prepackaged > kernel, come back > to the list with a new problem about pre-packaged > kernel. > > When you do get desired kernel version working in > prepackage, try > rebuilding that level using the config file that > comes with it. Use > make-kpkg for this. If you succeed, you know that > you can build > ^ > kernels the debian way, and that kernels that you > build actually > work. -Then-, edit the config with all the good > stuff for cdrecord and > build again. > > If that doesn't boot and work, there is a conflict > between what you > think you need for cdrecord and what you think you > need for > booting. It is possible that a compromise between > the two lists will > not break either booting or cdrecording. > > Since a simple leap to the target system that you > thought would do > cdrecord didn't work, you have to move in smaller > steps, and see which > config option(s) kill your ability to boot. Maybe > theyr'e not really > needed for cdrecord in your particular case. > > Also, look for fumble fingers mistakes. I have a > tendency to type > /deb/ ... when I really want /dev/ ... > ^
Because of the suggestions above, I think that I have found the problem. However, I do not know how to solve it. I went through the .config file and compared it with the instructions in the CDRW-WritinguHOWTO. The following line was missing. ATA/IDE: CONFIG_BLK_DEV_IDESCSI=m (turn on SCSI emulation) I then went back to make xconfig to create a new kernel. THE CHOICE SCSI EMULATION SUPPORT WAS GRAYED OUT. There was no way in which I could bring it up. Surely, kernel 2.4.22 can support CD writing. But, what is the trick? sidney __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]