Re: burncd problems
On Thursday 02 June 2005 05:24 pm, Steven Friedrich wrote: > I've created a directory tree in /usr/freeBSD and it has directories for > each of my four systems; lightning, daemon, gandalf, and freakinBSD. Each > of those has subdirectories like /etc, and so on. > > I used mkisofs -R -o ~admin/cd1.iso /usr/freeBSD > > then I used vnconfig and mount to look at the image before burning it: > vnconfig -e vn0c ~admin/cd1.iso > mount_cd9660 /dev/vn0c /cdrom > > and then I burned it: > burncd data ~admin/cd1.iso fixate > > But when I try to mount the CD, using: > mount_cd9660 /dev/acd0c /cdrom > I get: > mount_cd9660: /dev/acd0c: Input/output error > > The files you hand to burncd are "image" files. Does that mean ISO images > or did I miscontrue the man page? here's the error displayed on the console acd0: READ_BIG - MEDIUM ERROR asc=0x11 ascq=0x06 error=0x00 -- i386 FreeBSD 4.11-STABLE There are 10 types of people in this world. Ones that understand binary and then, the others. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd problems
On Thursday 02 June 2005 05:24 pm, Steven Friedrich wrote: > I've created a directory tree in /usr/freeBSD and it has directories for > each of my four systems; lightning, daemon, gandalf, and freakinBSD. Each > of those has subdirectories like /etc, and so on. > > I used mkisofs -R -o ~admin/cd1.iso /usr/freeBSD > > then I used vnconfig and mount to look at the image before burning it: > vnconfig -e vn0c ~admin/cd1.iso > mount_cd9660 /dev/vn0c /cdrom > > and then I burned it: > burncd data ~admin/cd1.iso fixate > > But when I try to mount the CD, using: > mount_cd9660 /dev/acd0c /cdrom > I get: > mount_cd9660: /dev/acd0c: Input/output error > > The files you hand to burncd are "image" files. Does that mean ISO images > or did I miscontrue the man page? here's the error displayed on the console acd0: READ_BIG - MEDIUM ERROR asc=0x11 ascq=0x06 error=0x00 -- i386 FreeBSD 4.11-STABLE There are 10 types of people in this world. Ones that understand binary and then, the others. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
burncd problems
I've created a directory tree in /usr/freeBSD and it has directories for each of my four systems; lightning, daemon, gandalf, and freakinBSD. Each of those has subdirectories like /etc, and so on. I used mkisofs -R -o ~admin/cd1.iso /usr/freeBSD then I used vnconfig and mount to look at the image before burning it: vnconfig -e vn0c ~admin/cd1.iso mount_cd9660 /dev/vn0c /cdrom and then I burned it: burncd data ~admin/cd1.iso fixate But when I try to mount the CD, I get: mount_cd9660 /dev/acd0c /cdrom mount_cd9660: /dev/acd0c: Input/output error The files you hand to burncd are "image" files. Does that mean ISO images or did I miscontrue the man page? -- i386 FreeBSD 4.11-STABLE There are 10 types of people in this world. Ones that understand binary and then, the others. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
burncd problems
FBSD 4.10 keywords: burncd cdrw 700 650 device busy i have had seemingly inconsistent problems/errors with 'burncd', and i exhausted myself on it the past few days trying to prepare a bunch of CD sets. to possibly prevent others from struggling, this is some information i have found which may be helpful to others: older or cheap CDRW drives can't deal well with 700MB CDRW's. they may work, or may not. they can't track on the thinner tracks well. i would have some CDRW disks that worked flawlessly, and others that were a real pain within the same brand. some CDRW disk manufacturers are better than others it seems. Memorex 700MB disks seem to be particularly problematic for older/cheap drives. if you got an older/cheap CDRW drive, stick to 650MB, or at least avoid Memorex 700MB disks. i had trouble with Memorex 700MB disks on a Creative 8x4x32 speed drive. when i upgraded to a 48x24x48, all my problems with Memorex 700MB disks went away. acd0: CD-RW at ata1-master PIO4 acd0: CD-RW at ata1-master PIO4 it is difficult for the average user to figure out, because all you ever see is "drive busy" errors - and that doesn't tell you much. but from my reading, CD drives don't tell a driver too much, so that's all that can be said. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
burncd problems, any help would be appreciated ...
All, A few days ago I posted a message ( burncd and PIONEER DVD-RW DVR-105 ) about having problems using burncd on a 4.7-release box. After doing a bit more digging I noticed that the 5.0 release notes stated that support had been added for dvd burners and thought this may be a problem. After upgrading the system to 5.1 I tested out burncd again and encountered another problem with a similar error message. When I checked /var/log/messages I noticed this output ... Jun 17 01:34:12 hole kernel: acd0: READ_TRACK_INFO - ILLEGAL REQUEST asc=0x24 ascq=0x00 error=0x00 Jun 17 01:37:29 hole kernel: acd0: READ_TRACK_INFO - ILLEGAL REQUEST asc=0x24 ascq=0x00 error=0x00 Jun 17 02:18:33 hole kernel: acd0: REPORT_KEY - ILLEGAL REQUEST asc=0x6f ascq=0x04 error=0x00 Jun 17 02:18:40 hole kernel: acd0: READ_BIG - MEDIUM ERROR asc=0x11 ascq=0x05 error=0x00 Jun 17 02:18:41 hole kernel: acd0: REPORT_KEY - ILLEGAL REQUEST asc=0x6f ascq=0x04 error=0x00 Jun 17 02:18:41 hole kernel: acd0: READ_BIG - ILLEGAL REQUEST asc=0x21 ascq=0x00 error=0x00 Jun 17 02:18:41 hole kernel: acd0: READ_BIG - ILLEGAL REQUEST asc=0x21 ascq=0x00 error=0x00 Jun 17 02:19:54 hole kernel: acd0: REPORT_KEY - ILLEGAL REQUEST asc=0x6f ascq=0x04 error=0x00 Jun 17 02:23:40 hole su: mgrooms to root on /dev/ttyv0 Jun 17 02:29:38 hole kernel: acd0: REPORT_KEY - ILLEGAL REQUEST asc=0x6f ascq=0x04 error=0x00 Jun 17 02:31:44 hole kernel: acd0: REPORT_KEY - ILLEGAL REQUEST asc=0x6f ascq=0x04 error=0x00 Jun 17 02:32:50 hole kernel: acd0: REPORT_KEY - ILLEGAL REQUEST asc=0x6f ascq=0x04 error=0x00 Jun 17 02:32:57 hole kernel: acd0: READ_BIG - MEDIUM ERROR asc=0x11 ascq=0x05 error=0x00 Jun 17 02:32:58 hole kernel: acd0: REPORT_KEY - ILLEGAL REQUEST asc=0x6f ascq=0x04 error=0x00 Jun 17 02:33:03 hole last message repeated 2 times Jun 17 02:33:11 hole kernel: acd0: READ_BIG - MEDIUM ERROR asc=0x11 ascq=0x05 error=0x00 Jun 17 02:33:12 hole kernel: acd0: REPORT_KEY - ILLEGAL REQUEST asc=0x6f ascq=0x04 error=0x00 Jun 17 02:33:12 hole kernel: acd0: READ_BIG - ILLEGAL REQUEST asc=0x21 ascq=0x00 error=0x00 Jun 17 02:33:12 hole kernel: acd0: READ_BIG - ILLEGAL REQUEST asc=0x21 ascq=0x00 error=0x00 Jun 17 02:33:17 hole kernel: pid 72958 (vlc), uid 0: exited on signal 11 (core dumped) Jun 17 02:33:48 hole kernel: acd0: REPORT_KEY - ILLEGAL REQUEST asc=0x6f ascq=0x04 error=0x00 Jun 17 02:35:02 hole kernel: acd0: REPORT_KEY - ILLEGAL REQUEST asc=0x6f ascq=0x04 error=0x00 Jun 17 02:35:51 hole kernel: pid 72978 (vlc), uid 0: exited on signal 11 (core dumped) Jun 17 02:40:51 hole kernel: acd0: REPORT_KEY - ILLEGAL REQUEST asc=0x6f ascq=0x04 error=0x00 Jun 17 02:42:57 hole kernel: acd0: REPORT_KEY - ILLEGAL REQUEST asc=0x6f ascq=0x04 error=0x00 Jun 17 02:45:24 hole kernel: acd0: REPORT_KEY - ILLEGAL REQUEST asc=0x6f ascq=0x04 error=0x00 Jun 17 02:55:16 hole kernel: acd0: REPORT_KEY - ILLEGAL REQUEST asc=0x6f ascq=0x04 error=0x00 Jun 17 02:56:20 hole kernel: acd0: REPORT_KEY - ILLEGAL REQUEST asc=0x6f ascq=0x04 error=0x00 When searching the freebsd list archives I noticed a few other people having similar problems and a few suggestions for solutions but none seem to work in my case. Does anyone have any insite on this issue? If this is a known problem, is there anyone working on it? Can I help out in any way? Thanks in advance, -Matthew ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
