On Saturday 06 March 2004 04:57 pm, Matthew Arnold wrote:
After much Googling, I believe that I managed to get Mt. Rainier support working on my CD-RW drive with kernel 2.6.3. I wrote a HOWTO about it because I couldn't find one anyplace else. I would appreciate it if anyone would read it and offer any corrections, clarifications, additions, etc. You can find the article at:
http://www.thehaus.net/AltOS/Linux/ht-mtrainier.shtml
Thanks in advance, Matt aka A.T. Hun
Thanks for the howto! I'm still having trouble getting it to work though... When I try copying files over, I get: cp: writing `/cdrw/doghouse.wings': No space left on device cp: cannot create regular file `/cdrw/dropship.wings': Input/output error cp: cannot create regular file `/cdrw/dropship2.wings': Input/output error cp: cannot create regular file `/cdrw/dropship2.wings~': Input/output error cp: cannot create regular file `/cdrw/dropship3.wings': Input/output error cp: cannot create regular file `/cdrw/dropship3.wings~': Input/output error This I'm doing on a fresh CD-RW, which should have half a gig available. The drive in question is a rebranded LITE-ON COMBO LTC-48161H (16x DVD read, 48x/48x/24x) which in theory is Mt. Rainier capable. On the console, I get errors such as: Mar 6 19:43:49 localhost vmunix: hdc: tray open Mar 6 19:43:49 localhost vmunix: end_request: I/O error, dev hdc, sector 6036 Mar 6 19:43:49 localhost vmunix: UDF-fs DEBUG fs/udf/inode.c:1317:udf_update_inode: bread failure Mar 6 19:43:50 localhost vmunix: hdc: tray open Mar 6 19:43:50 localhost vmunix: end_request: I/O error, dev hdc, sector 6052 Mar 6 19:43:50 localhost vmunix: UDF-fs DEBUG fs/udf/inode.c:1317:udf_update_inode: bread failure Mar 6 19:43:50 localhost kernel: UDF-fs DEBUG fs/udf/inode.c:1317:udf_update_inode: bread failure Mar 6 19:43:50 localhost kernel: hdc: tray open Mar 6 19:43:50 localhost kernel: end_request: I/O error, dev hdc, sector 6056 Mar 6 19:43:51 localhost vmunix: hdc: tray open Mar 6 19:43:51 localhost vmunix: end_request: I/O error, dev hdc, sector 6072 Mar 6 19:43:51 localhost kernel: UDF-fs DEBUG fs/udf/inode.c:1317:udf_update_inode: bread failure hdc: tray open end_request: I/O error, dev hdc, sector 6108 Mar 6 19:44:14 localhost vmunix: hdc: tray open Mar 6 19:44:14 localhost vmunix: end_request: I/O error, dev hdc, sector 6108 Mar 6 19:44:14 localhost vmunix: UDF-fs DEBUG fs/udf/inode.c:1317:udf_update_inode: bread failure hdc: tray open end_request: I/O error, dev hdc, sector 6448 Mar 6 19:44:16 localhost vmunix: hdc: tray open Mar 6 19:44:16 localhost vmunix: end_request: I/O error, dev hdc, sector 6448 Mar 6 19:44:16 localhost vmunix: UDF-fs DEBUG fs/udf/inode.c:1317:udf_update_inode: bread failure hdc: tray open end_request: I/O error, dev hdc, sector 6756 Mar 6 19:44:18 localhost vmunix: hdc: tray open Mar 6 19:44:18 localhost vmunix: end_request: I/O error, dev hdc, sector 6756 Mar 6 19:44:18 localhost vmunix: UDF-fs DEBUG fs/udf/inode.c:1317:udf_update_inode: bread failure hdc: tray open end_request: I/O error, dev hdc, sector 7688 Mar 6 19:44:20 localhost vmunix: hdc: tray open Mar 6 19:44:20 localhost vmunix: end_request: I/O error, dev hdc, sector 7688 Mar 6 19:44:20 localhost vmunix: UDF-fs DEBUG fs/udf/inode.c:1317:udf_update_inode: bread failure It could be because I'm using a 4x cdrw, but I'd think that wouldn't cause errors, it would just be slow. Anybody know what's up with this?