Re: Support for atapi cdrw as scsi in -current?
Hi, i tested your patch onn 4.5-stable with TOSHIBA SD-M1502 (master) and PIONEER DVR-103 (slave). Unfortunately the system hangs at boot time after (noperiph:atapi1:0:-1:-1): Registered SIM for ata1 Any ideas? Lutz -- Lutz Bichler Institute for Software Technology, Department of Computer Science University of the Federal Armed Forces Munich, D-85577 Neubiberg, Germany TEL/FAX: +49(0)89 6004-2261/-4447, NET: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Support for atapi cdrw as scsi in -current?
Garrett Wollman wrote: On Sat, 02 Feb 2002 20:10:20 +, [EMAIL PROTECTED] said: I noticed a patch on freebsd-scsi a while back that added a not very complete form of atapi as scsi support to the freebsd kernel. Are there plans to complete this and add it to -current sometime before -current turns into 5.0-RELEASE? Thanks for any information. I've been using it somewhat actively in the past week or so in -current. The patch as it exists needs a few changes to fit in current -current. $ camcontrol devlist TDK CDRW241040B 57S4 at scbus0 target 0 lun 0 (cd0,pass0) LITEON CD-ROM LTN526D YSR5 at scbus0 target 1 lun 0 (cd1,pass1) I don't think that ATAPICAM works well enough to use it entirely in place of the atapi-cd driver; for example, I get the following errors: atapicam0: READ_DISK_INFO - ILLEGAL REQUEST asc=0x20 ascq=0x00 error=0x04 atapicam0: READ_TOC - ILLEGAL REQUEST asc=0x24 ascq=0x00 error=0x04 However, it works well-enough to run cdrdao, which is what mattered to me, for both reading and writing on both of the afore-mentioned ATAPI devices. -GAWollman Is there a place where I can find this updated patch which will work for me in the current -current? Thanks. Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Support for atapi cdrw as scsi in -current?
On Thu, Feb 07, 2002 at 12:38 +0100, S=F8ren Schmidt wrote: =20 [ snipped ATAPI - SCSI conversion ] =20 Doesn't burncd work for you on -current ? Well, since you asked about it ... :) Back in June I told you about the progress meter bogus values in burncd and provided a patch in a private message ([EMAIL PROTECTED]) to you. After some silence I opened PR bin/30893 ([PATCH] burncd(8) progress meter) in September. This one got closed in December with a Fixed, but done differently than this patch. comment. Since I haven't seen any such fix and it was not fixed some time after your closing the PR I followed up to it in January, asking you to reopen PR bin/30893 or to apply its fix or to fix the problem in another way. The bug (talking about a few million percent completion of the job, while one hundred should suffice) is still there. Can you have one more look at http://www.freebsd.org/cgi/query-pr.cgi?pr=3D30893 please? Especially the simple and straight fix in its opening. This shouldn't take eight months to wait for or doing hard fights to get it fixed ... :( (I know you were busy back then changing jobs and moving, but the later closing wasn't appropriate without a fix.) virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s get gpg key [EMAIL PROTECTED] --=20 If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Support for atapi cdrw as scsi in -current?
It seems Gerhard Sittig wrote: On Thu, Feb 07, 2002 at 12:38 +0100, Søren Schmidt wrote: [ snipped ATAPI - SCSI conversion ] Doesn't burncd work for you on -current ? Well, since you asked about it ... :) I asked for *problems* not cosmetic issues :) The bug (talking about a few million percent completion of the job, while one hundred should suffice) is still there. Can you have one more look at http://www.freebsd.org/cgi/query-pr.cgi?pr=30893 please? Especially the simple and straight fix in its opening. This shouldn't take eight months to wait for or doing hard fights to get it fixed ... :( (I know you were busy back then changing jobs and moving, but the later closing wasn't appropriate without a fix.) It is on my TODO list, but its fairly long, and functional errors plus supporting new hardware keeps getting top priority... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Support for atapi cdrw as scsi in -current?
On Tue, Feb 05, 2002 at 08:14:22PM +0100, Thomas Quinot wrote: Is there a place where I can find this updated patch which will work for me in the current -current? Thanks. I put up updated patches at http://www.cuivre.fr.eu.org/~thomas/atapicam/ For -CURRENT, you should be using the latest one (of today) which fixes a silly line inversion. I'd be very interested in success/failuire reports on this patch, especially with ATAPI tape or floppy drives. FYI, I applied the patch to -stable and tested it using cdrdao with my plextor 1610A. Worked like a charm. -- Christopher Nielsen - Metal-wielding pyro techie [EMAIL PROTECTED] Those who are willing to trade freedom for security deserve neither freedom nor security. --Benjamin Franklin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Support for atapi cdrw as scsi in -current?
On Thu, Feb 07, 2002 at 12:38 +0100, Søren Schmidt wrote: [ snipped ATAPI - SCSI conversion ] Doesn't burncd work for you on -current ? Well, since you asked about it ... :) Back in June I told you about the progress meter bogus values in burncd and provided a patch in a private message ([EMAIL PROTECTED]) to you. After some silence I opened PR bin/30893 ([PATCH] burncd(8) progress meter) in September. This one got closed in December with a Fixed, but done differently than this patch. comment. Since I haven't seen any such fix and it was not fixed some time after your closing the PR I followed up to it in January, asking you to reopen PR bin/30893 or to apply its fix or to fix the problem in another way. The bug (talking about a few million percent completion of the job, while one hundred should suffice) is still there. Can you have one more look at http://www.freebsd.org/cgi/query-pr.cgi?pr=30893 please? Especially the simple and straight fix in its opening. This shouldn't take eight months to wait for or doing hard fights to get it fixed ... :( (I know you were busy back then changing jobs and moving, but the later closing wasn't appropriate without a fix.) virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s get gpg key [EMAIL PROTECTED] -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Support for atapi cdrw as scsi in -current?
It seems Gerhard Sittig wrote: On Thu, Feb 07, 2002 at 12:38 +0100, Søren Schmidt wrote: [ snipped ATAPI - SCSI conversion ] Doesn't burncd work for you on -current ? Well, since you asked about it ... :) I asked for *problems* not cosmetic issues :) The bug (talking about a few million percent completion of the job, while one hundred should suffice) is still there. Can you have one more look at http://www.freebsd.org/cgi/query-pr.cgi?pr=30893 please? Especially the simple and straight fix in its opening. This shouldn't take eight months to wait for or doing hard fights to get it fixed ... :( (I know you were busy back then changing jobs and moving, but the later closing wasn't appropriate without a fix.) It is on my TODO list, but its fairly long, and functional errors plus supporting new hardware keeps getting top priority... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Support for atapi cdrw as scsi in -current?
hi, there! On Tue, Feb 05, 2002 at 08:14:22PM +0100, Thomas Quinot wrote: Is there a place where I can find this updated patch which will work for me in the current -current? Thanks. I put up updated patches at http://www.cuivre.fr.eu.org/~thomas/atapicam/ For -CURRENT, you should be using the latest one (of today) which fixes a silly line inversion. I'd be very interested in success/failuire reports on this patch, especially with ATAPI tape or floppy drives. I successfully recorded data cd using cdrecord on NEC NR-7700A IDE CD-RW. dmesg follows Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.5-STABLE #0: Thu Feb 7 04:49:06 NS 2002 [EMAIL PROTECTED]:/usr/obj/usr/fbsd/RELENG_4/src/sys/husky Timecounter i8254 frequency 1193182 Hz CPU: AMD-K7(tm) Processor (503.53-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x612 Stepping = 2 Features=0x81f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,MMX AMD Features=0xc040AMIE,DSP,3DNow! real memory = 268369920 (262080K bytes) config enable apm0 config quit avail memory = 256040960 (250040K bytes) Preloaded elf kernel kernel at 0xc04af000. Preloaded userconfig_script /boot/kernel.conf at 0xc04af09c. Preloaded elf module if_ppp.ko at 0xc04af0ec. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 7 entries at 0xc00f82b0 apm0: APM BIOS on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: math processor on motherboard npx0: INT 16 interface pcib0: AMD-751 host to PCI bridge on motherboard pci0: PCI bus on pcib0 pcib1: AMD-751 PCI-PCI (1x/2x AGP) bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: NVidia Riva Ultra Vanta TNT2 graphics accelerator at 5.0 irq 11 isab0: VIA 82C686 PCI-ISA bridge at device 4.0 on pci0 isa0: ISA bus on isab0 atapci0: VIA 82C686 ATA66 controller port 0xffa0-0xffaf at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: VIA 83C572 USB controller port 0xcc00-0xcc1f irq 12 at device 4.2 on pci0 usb0: VIA 83C572 USB controller on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: VIA 83C572 USB controller port 0xd000-0xd01f irq 12 at device 4.3 on pci0 usb1: VIA 83C572 USB controller on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered chip1: VIA 82C686 ACPI interface at device 4.4 on pci0 pci0: unknown card (vendor=0x1274, dev=0x1371) at 13.0 irq 11 ed0: NE2000 PCI Ethernet (RealTek 8029) port 0xc400-0xc41f irq 5 at device 14.0 on pci0 ed0: address 00:00:01:00:fb:08, type NE2000 (16 bit) sym0: 810a port 0xd800-0xd8ff mem 0xef00-0xefff irq 10 at device 15.0 on pci0 sym0: No NVRAM, ID 7, Fast-10, SE, parity checking orm0: Option ROMs at iomem 0xc-0xc,0xd-0xd3fff on isa0 fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to deny, logging disabled ad0: 9671MB IBM-DTTA-351010 [19650/16/63] at ata0-master UDMA33 acd0: CD-RW _NEC NR-7700A at ata1-master using PIO4 (noperiph:atapi1:0:-1:-1): Registered SIM for ata1 Waiting 15 seconds for SCSI devices to settle atapicam1m: read data overrun 96/95 Mounting root from ufs:/dev/ad0s2a cd1 at atapi1 bus 0 target 0 lun 0 cd1: _NEC NR-7700A 1.01 Removable CD-ROM SCSI-0 device cd1: 3.300MB/s transfers cd1: cd present [347816 x 2048 byte records] cd0 at sym0 bus 0 target 6 lun 0 cd0: SONY CD-R CDU948S 1.0e Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: cd present [327225 x 2048 byte records] pcm0: AudioPCI ES1373-8 port 0xc800-0xc83f irq 11 at device 13.0 on pci0 /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Support for atapi cdrw as scsi in -current?
hi, there! On Thu, Feb 07, 2002 at 12:38:08PM +0100, Søren Schmidt wrote: I put up updated patches at http://www.cuivre.fr.eu.org/~thomas/atapicam/ For -CURRENT, you should be using the latest one (of today) which fixes a silly line inversion. I'd be very interested in success/failuire reports on this patch, especially with ATAPI tape or floppy drives. I successfully recorded data cd using cdrecord on NEC NR-7700A IDE CD-RW. dmesg follows Doesn't burncd work for you on -current ? I tried burncd in -stable. it works for me. but with ATAPI CAM stuff you get access to a whole bunch of neat cd recording and cd ripping tools (e.g. cdrdao) I haven't tried DAO with burncd in -current (I haven't tried DAO with ATAPI CAM stuff too but I'll try to find spare time this week to test it, I do not even know if cdrdao supports my drive). /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Support for atapi cdrw as scsi in -current?
Garrett Wollman wrote: On Sat, 02 Feb 2002 20:10:20 +, [EMAIL PROTECTED] said: I noticed a patch on freebsd-scsi a while back that added a not very complete form of atapi as scsi support to the freebsd kernel. Are there plans to complete this and add it to -current sometime before -current turns into 5.0-RELEASE? Thanks for any information. I've been using it somewhat actively in the past week or so in -current. The patch as it exists needs a few changes to fit in current -current. $ camcontrol devlist TDK CDRW241040B 57S4 at scbus0 target 0 lun 0 (cd0,pass0) LITEON CD-ROM LTN526D YSR5 at scbus0 target 1 lun 0 (cd1,pass1) I don't think that ATAPICAM works well enough to use it entirely in place of the atapi-cd driver; for example, I get the following errors: atapicam0: READ_DISK_INFO - ILLEGAL REQUEST asc=0x20 ascq=0x00 error=0x04 atapicam0: READ_TOC - ILLEGAL REQUEST asc=0x24 ascq=0x00 error=0x04 However, it works well-enough to run cdrdao, which is what mattered to me, for both reading and writing on both of the afore-mentioned ATAPI devices. -GAWollman Is there a place where I can find this updated patch which will work for me in the current -current? Thanks. Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Support for atapi cdrw as scsi in -current?
Is there a place where I can find this updated patch which will work for me in the current -current? Thanks. I put up updated patches at http://www.cuivre.fr.eu.org/~thomas/atapicam/ For -CURRENT, you should be using the latest one (of today) which fixes a silly line inversion. I'd be very interested in success/failuire reports on this patch, especially with ATAPI tape or floppy drives. Thomas. -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
