Messages in this thread | | | From | Paul Kreiner <> | Subject | Re: 2.4.10ac10, cdrecord 1.9-6, Mitsumi CR-4804TE: lock up burning too large image | Date | Sun, 21 Oct 2001 23:48:15 -0600 |
| |
> Ok. I updated to 1.10 from redhat rawhide, but as said it didn't work at all > with 2.2 ("failed to mmap /dev/null" or something) so I went back to 1.9. I > could retry now that I've updated the machine in question to 2.4. (I can > also see if the 2.2 /dev/null error reproduces if you are interested.) I'll > retry too large image with 1.10 and report back to you, but I fear it is a > kernel bug.
I believe I ran into this same cdrecord "fail to mmap /dev/null" issue before. The fix (aside from upgrading your kernel to 2.4.x) is to pass "fs=0" to cdrecord. According to the docs, this disables the in-memory FIFO.
Cheers, Paul Kreiner - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |