Re: ATA CD-R problems, still...

2000-01-16 Thread Bryan Liesner

On Sun, 16 Jan 2000, Brian Fundakowski Feldman wrote:

Can you try this patch to src/usr.sbin/burncd, and see if things work
after that?  Thanks! (BTW, there's also an extra feature in there, hope
you don't mind :)


Yes, I burned a full 650MB onto a CD-R disk. No problems at all.  And
I see just changing the definition of BLOCKS from 32 to 16 did the
trick.  I thought there was going to be a lot of digging into the
ATAPI driver to get this fixed.  

Thanks!

Bryan




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: ATA CD-R problems, still...

2000-01-16 Thread Soren Schmidt

It seems Bryan Liesner wrote:
 On Sun, 16 Jan 2000, Brian Fundakowski Feldman wrote:
 
 Can you try this patch to src/usr.sbin/burncd, and see if things work
 after that?  Thanks! (BTW, there's also an extra feature in there, hope
 you don't mind :)
 
 
 Yes, I burned a full 650MB onto a CD-R disk. No problems at all.  And
 I see just changing the definition of BLOCKS from 32 to 16 did the
 trick.  I thought there was going to be a lot of digging into the
 ATAPI driver to get this fixed.  

There really wasn't any functional changes to the driver, but there was
to the util :)
It is sad though that there still are so many crappy drives be made :(

However I've committed the fix...


-Søren


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: ATA CD-R problems, still...

2000-01-16 Thread Bryan Liesner

On Mon, 17 Jan 2000, Soren Schmidt wrote:

There really wasn't any functional changes to the driver, but there was
to the util :)
It is sad though that there still are so many crappy drives be made :(

However I've committed the fix...


-Søren


Now if we can only get my crappy tape drive to probe...  :)

Are future commits going to address that?  


Bryan





To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



ATA CD-R problems, still...

2000-01-08 Thread Brian Fundakowski Feldman

Well, I don't know about anyone else out there having the problems I'm
having, but I might as well ask.  I'm using the ATA driver with the
following bugfix applied, otherwise the same.

Index: atapi-cd.c
===
RCS file: /usr2/ncvs/src/sys/dev/ata/atapi-cd.c,v
retrieving revision 1.33
diff -u -r1.33 atapi-cd.c
--- atapi-cd.c  2000/01/07 12:01:00 1.33
+++ atapi-cd.c  2000/01/08 18:50:42
@@ -966,9 +966,12 @@
break;
 
 case CDRIOCCLOSEDISK:
-   if (!(cdp-flags  F_WRITTEN) || !(cdp-flags  F_DISK_OPEN)) {
+   if (!(cdp-flags  F_DISK_OPEN)) {
error = EINVAL;
printf("acd%d: sequence error (nothing to close)\n", cdp-lun);
+   }
+   else if (!(cdp-flags  F_WRITTEN)) {
+cdp-flags = ~(F_DISK_OPEN | F_TRACK_OPEN);
}
else {
error = acd_close_disk(cdp);

The problem manifests itself by now allowing me to write anything on
any of my disks.  Actually, it won't let me write data.  Here is an
example direct from vty0 (blank lines removed):

{"/home2/tmp"}$ mkdir foo
{"/home2/tmp"}$ cd foo
{"/home2/tmp/foo"}$ dd if=/dev/zero bs=1m count=50 of=foo.iso
50+0 records in
50+0 records out
52428800 bytes transferred in 4.582966 secs (11439928 bytes/sec)
{"/home2/tmp/foo"}$ burncd -s 2 data foo.iso fixate
next writeable LBA 49652
writing from file foo.iso
acd0: WRITE_BIG - ILLEGAL REQUEST asc=10 ascq=00 error=00
only wrote 0 of 65536 bytes
fixating CD, please wait..
{"/home2/tmp/foo"}$

As you can see, I got an ILLEGAL REQUEST error printf().  The drive,
which worked previously (in wormcontrol(8) days), is acd0 in the
dmesg which follows.

Copyright (c) 1992-2000 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 4.0-CURRENT #3: Sat Jan  8 21:17:33 EST 2000
[EMAIL PROTECTED]:/usr/src/sys/compile/GREEN
Timecounter "i8254"  frequency 1193182 Hz
CPU: AMD-K6(tm) 3D processor (350.80-MHz 586-class CPU)
  Origin = "AuthenticAMD"  Id = 0x58c  Stepping = 12
  Features=0x8021bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX
  AMD Features=0x8800SYSCALL,3DNow!
real memory  = 134217728 (131072K bytes)
avail memory = 124481536 (121564K bytes)
Preloaded elf kernel "kernel" at 0xc02f9000.
Preloaded elf module "vesa.ko" at 0xc02f909c.
Preloaded elf module "usb.ko" at 0xc02f9138.
Preloaded elf module "joy.ko" at 0xc02f91d4.
VESA: v3.0, 4096k memory, flags:0x1, mode table:0xc02dc102 (122)
VESA: NVidia
md0: Malloc disk
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: AcerLabs M1541 (Aladdin-V) PCI host bridge on motherboard
pci0: PCI bus on pcib0
pcib1: AcerLabs M5243 PCI-PCI bridge at device 1.0 on pci0
pci1: PCI bus on pcib1
ohci0: AcerLabs M5237 (Aladdin-V) USB controller mem 0xebfef000-0xebfe irq 10 at 
device 2.0 on pci0
usb0: OHCI version 1.0, legacy support
usb0: AcerLabs M5237 (Aladdin-V) USB controller on ohci0
usb0: USB revision 1.0
uhub0: AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
alpm0: AcerLabs M15x3 Power Management Unit at device 3.0 on pci0
isab0: AcerLabs M1533 portable PCI-ISA bridge at device 7.0 on pci0
isa0: ISA bus on isab0
ata-pci0: AcerLabs Aladdin ATA-33 controller port 0xffa0-0xffaf irq 0 at device 15.0 
on pci0
ata-pci0: Busmastering DMA supported
ata0 at 0x01f0 irq 14 on ata-pci0
ata1 at 0x0170 irq 15 on ata-pci0
pci0: unknown card (vendor=0x10d9, dev=0x0531) at 16.0 irq 11
ata-pci1: HighPoint HPT366 ATA-66 controller port 
0xd800-0xd8ff,0xddc8-0xddcb,0xddd0-0xddd7 irq 9 at device 18.0 on pci0
ata-pci1: Busmastering DMA supported
ata2 at 0xddd0 irq 9 on ata-pci1
ata-pci2: HighPoint HPT366 ATA-66 controller port 
0xda00-0xdaff,0xddf8-0xddfb,0xdde0-0xdde7 irq 9 at device 18.1 on pci0
ata-pci2: Busmastering DMA supported
ata3 at 0xdde0 irq 9 on ata-pci2
vga-pci0: NVidia Riva TNT graphics accelerator mem 
0xcc00-0xccff,0xef00-0xefff irq 0 at device 20.0 on pci0
smbus0: System Management Bus on alsmb0
smb0: SMBus general purpose I/O on smbus0
sbc0: Soundblaster 16 at port 0x220-0x22f irq 5 drq 1 flags 0x16 on isa0
sbc0: setting card to irq 5, drq 1, 6
pcm0: SB DSP 4.13 on sbc0
atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0
atkbd0: AT Keyboard irq 1 on atkbdc0
psm0: PS/2 Mouse irq 12 on atkbdc0
psm0: model IntelliMouse, device ID 3
vga0: Generic ISA VGA at port 0x3b0-0x3df iomem 0xa-0xb on isa0
sc0: System console on isa0
sc0: VGA 16 virtual consoles, flags=0x200
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
sio2: not probed (disabled)
sio3: not probed (disabled)
ppc0 at port 0x378-0x37f irq 7 drq 3 on isa0
ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
plip0: PLIP network interface on ppbus 0
lpt0: 

Re: ATA CD-R problems, still...

2000-01-08 Thread Bryan Liesner

On Sat, 8 Jan 2000, Brian Fundakowski Feldman wrote:

Well, I don't know about anyone else out there having the problems I'm
having, but I might as well ask.  I'm using the ATA driver with the
following bugfix applied, otherwise the same.


At the risk of sounding like an AOLer, me too.   Prior to the most
recent changes incorporating burncd, I was able to write to my HP
8250i using wormcontrol.  Never burned a coaster, it was very
reliable.  Now when I use burncd, I get WRITE_BIG errors, and then
the driver tries endlessly to reset.  The only way out is to hit the
big red reset button. 

-Bryan




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: ATA CD-R problems, still...

2000-01-08 Thread Brian Fundakowski Feldman

On Sat, 8 Jan 2000, Bryan Liesner wrote:

 On Sat, 8 Jan 2000, Brian Fundakowski Feldman wrote:
 
 Well, I don't know about anyone else out there having the problems I'm
 having, but I might as well ask.  I'm using the ATA driver with the
 following bugfix applied, otherwise the same.
 
 
 At the risk of sounding like an AOLer, me too.   Prior to the most
 recent changes incorporating burncd, I was able to write to my HP
 8250i using wormcontrol.  Never burned a coaster, it was very
 reliable.  Now when I use burncd, I get WRITE_BIG errors, and then
 the driver tries endlessly to reset.  The only way out is to hit the
 big red reset button. 

To add a little bit to that, on the side-note area...  Okay, first of
all, the reason it keeps resetting is that when the timeout() is
called (which resets the controller, see ata{,pi}_reset()), the timer
which fires is in the kernel proper (!) and as such takes over all
control of the CPU.  E.g. you won't get your processes run very much
(to make an understatement).  I have been able to get a Ctrl+Alt+Del
in at the right time (between the timer being set and being fired)
to get the box rebooted, otherwise I have the same problem as you.
   Now, failing to address why the hardware is failing, there really
needs to be a better way to reset controllers.  Why don't we have
timers fire in their own kthread, one per timeout()?  I think that
this would be a very useful change, and an important one that could
be implemented before the "feature freeze" for 4.0.  Does anyone
have a better idea regarding that?
   But, don't let me take the focus away from the CD-R issue.  It's
pretty important to be able to figure out why some CD-Rs no longer
work (obviously, Soren's work :)

 -Bryan

-- 
 Brian Fundakowski Feldman   \  FreeBSD: The Power to Serve!  /
 [EMAIL PROTECTED]`--'



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message