> -----Original Message-----
> From: Pablo Manalastas [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, July 11, 2000 7:58 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [plug] cd & cdr support
>
> When compiling a new kernel, I use the following general rule,
> and it works very nicely for me:
>
> If you have the hardware NOW, then build the driver into the kernel.
> If you expect to have the hardware in the future, then compile
> the driver as a module. Otherwise, you do not even need to consider
> the driver at all.
>
> Building both IDE and SCSI support into the kernel (or as modules)
> is alright. The kernel is unusually intelligent enough to sort things
> out for itself.
>
I really had a nightmare with my Fireport SCSI Controller. Para nga akong
nagevaluate ng product. It took me a week to figure out the problem. I just
don't know if I really figured out the problem. When I built the SCSI
support into the kernel, 100% I won't be able to cd write. Errors like fifo,
track size unknown, 0x2, CHECK CONDITION, and others hex numbers, are
displayed by cdrecord's log. Inakusahan ko pa ang cdrecord, so I upgraded to
the bleeding edge version, but still, no luck. So, I just tried compiling
the ncr scsi support as a module, and you know, everything went fine. Pero,
I'm still doubtful. Hindi dapat kasi ganito ang behavior. I just don't know
with previous kernel version. I'm using 2.2.16 kasi. Pero, ok na siya.
And FYI, the SCSI emulation stuff in the kernel are for IDE CD WRITERS only.
And I'm using gcombust as an x frontend for cdrtools. I like it. It's better
than xcdroast. It has a multi-session support.
-
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
