Re: My ATAPI CD not come ready
It seems Alex wrote: Mike, I couldn't find your fix in the commit logs - perhaps someone else committed it? Do you have the revision number? The problem still persists: ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ad0: 6194MB TOSHIBA MK6409MAV [13424/15/63] at ata0-master using UDMA33 acd0: CDROM UJDA150 at ata1-master using BIOSPIO I have it on my list, but remember the error is harmless thus not at the top of my list (yet). -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My ATAPI CD not come ready
Mike Smith wrote: JFWIW, this sounds like something that I "fixed" in the old wd driver, where a device 'echoed' on the bus after it was deselected. Increasing the timeout between deselecting the device and trying to talk again to the bus was, AFAIR, the workaround then. Mike, I couldn't find your fix in the commit logs - perhaps someone else committed it? Do you have the revision number? The problem still persists: ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ad0: 6194MB TOSHIBA MK6409MAV [13424/15/63] at ata0-master using UDMA33 acd0: CDROM UJDA150 at ata1-master using BIOSPIO Alex It seems Alex wrote: OK - here's the part relevant to ata: ata-pci0: Intel PIIX4 ATA-33 controller port 0xfcf0-0xfcff at device 1.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xfcf0 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0 at 0x01f0 irq 14 on ata-pci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xfcf8 ata1: mask=03 status0=00 status1=00 ata1: mask=03 status0=00 status1=00 ata1: devices = 0xc Here it sees two devices, apparently you cdrom is reacting both on master AND slave addresses :( ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed But when we try to talk to it it fails... ata0-master: success setting up UDMA2 mode on PIIX4 chip But when we try to talk to it it fails... Any ideas? I'll try to come up with a patch that solves this... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My ATAPI CD not come ready
JFWIW, this sounds like something that I "fixed" in the old wd driver, where a device 'echoed' on the bus after it was deselected. Increasing the timeout between deselecting the device and trying to talk again to the bus was, AFAIR, the workaround then. It seems Alex wrote: OK - here's the part relevant to ata: ata-pci0: Intel PIIX4 ATA-33 controller port 0xfcf0-0xfcff at device 1.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xfcf0 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0 at 0x01f0 irq 14 on ata-pci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xfcf8 ata1: mask=03 status0=00 status1=00 ata1: mask=03 status0=00 status1=00 ata1: devices = 0xc Here it sees two devices, apparently you cdrom is reacting both on master AND slave addresses :( ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed But when we try to talk to it it fails... ata0-master: success setting up UDMA2 mode on PIIX4 chip But when we try to talk to it it fails... Any ideas? I'll try to come up with a patch that solves this... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My ATAPI CD not come ready
At 22:01 01/25/2000 +0100, you wrote: It seems Tom Embt wrote: Don't mean to butt in here, I haven't really been following the thread - but I may have found a workaround/clue. I have a Sony CDU-55E (ooold 2x) on secondary master of the PIIX4 on my BP6. By going into the BIOS (the section of it where you would set CHS numbers, LBA, etc) and changing the secondary master device from "none" to "auto", I have gone from: BTW, this was on a kernel from around 20:00 GMT Jan 25 Interesting... What version is you ata-all.c ?? its damn close to the commit I just made, that should fix that problem... -Søren That was with 1.43 I just updated all the files in /usr/src/sys/dev/ata (ata-all.c v1.44) and made a new kernel. While rebooting I set the BIOS back to "none" and watched FreeBSD boot. No error :) - then I rebooted to kernel.old (1.43) without touching the BIOS and the error came back. Looks like you got it. Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My ATAPI CD not come ready
Soren Schmidt wrote: It seems Alex wrote: You need to update.. OK - I've just updated. Here goes again: ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ad0: 6194MB TOSHIBA MK6409MAV [13424/15/63] at ata0-master using UDMA33 acd0: CDROM UJDA150 at ata1-master using PIO4 Mounting root from ufs:/dev/ad0s2a I wouldn't be surprised if ATAPI_CMD_IDENTIFY failed on ata1-master, but why does it say ata1-slave? It's a notebook PC, so unfortunately I'm not sure how it's all connected. Apparently it thinks something is there, could you mail me a complete verbose bootlog (dmesg) please, and I'll try to figure out what is going wrong.. OK - here's the part relevant to ata: ata-pci0: Intel PIIX4 ATA-33 controller port 0xfcf0-0xfcff at device 1.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xfcf0 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0 at 0x01f0 irq 14 on ata-pci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xfcf8 ata1: mask=03 status0=00 status1=00 ata1: mask=03 status0=00 status1=00 ata1: devices = 0xc ata1 at 0x0170 irq 15 on ata-pci0 ... (delay) ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ata0-master: success setting up UDMA2 mode on PIIX4 chip ad0: TOSHIBA MK6409MAV/F5.01 A ATA-4 disk at ata0 as master ad0: 6194MB (12685680 sectors), 13424 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad0: piomode=4 dmamode=2 udmamode=2 cblid=0 Creating DISK ad0 Creating DISK wd0 ata1-master: piomode=4 dmamode=2 udmamode=-1 dmaflag=1 ata1-master: success setting up PIO4 mode on generic chip acd0: UJDA150/1.02 CDROM drive at ata1 as master acd0: read 4134KB/s (4134KB/s), 128KB buffer, PIO4 acd0: Reads: CD-R, CD-RW, CD-DA acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm photo disc loaded, unlocked Mounting root from ufs:/dev/ad0s2a ad0s1: type 0xb, start 63, end = 5322239, size 5322177 : OK ad0s2: type 0xa5, start 5322240, end = 12685679, size 7363440 : OK Any ideas? Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My ATAPI CD not come ready
It seems Alex wrote: OK - here's the part relevant to ata: ata-pci0: Intel PIIX4 ATA-33 controller port 0xfcf0-0xfcff at device 1.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xfcf0 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0 at 0x01f0 irq 14 on ata-pci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xfcf8 ata1: mask=03 status0=00 status1=00 ata1: mask=03 status0=00 status1=00 ata1: devices = 0xc Here it sees two devices, apparently you cdrom is reacting both on master AND slave addresses :( ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed But when we try to talk to it it fails... ata0-master: success setting up UDMA2 mode on PIIX4 chip But when we try to talk to it it fails... Any ideas? I'll try to come up with a patch that solves this... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My ATAPI CD not come ready
I have the same problem: [anders@enterprise:anders] $ dmesg | grep ata ata-pci0: Intel PIIX3 ATA controller port 0xffa0-0xffaf at device 7.1 on pci0 ata0 at 0x01f0 irq 14 on ata-pci0 ata-isa0: already registered as ata0 ata0-slave: ata_command: timeout waiting for intr ata0-slave: identify failed -- Anders Andersson[EMAIL PROTECTED] Sanyusan International AB http://www.sanyusan.se/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My ATAPI CD not come ready
It seems Anders Andersson wrote: I have the same problem: [anders@enterprise:anders] $ dmesg | grep ata ata-pci0: Intel PIIX3 ATA controller port 0xffa0-0xffaf at device 7.1 on pci0 ata0 at 0x01f0 irq 14 on ata-pci0 ata-isa0: already registered as ata0 ata0-slave: ata_command: timeout waiting for intr ata0-slave: identify failed Could I please have a complete dmesg from that ?? -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My ATAPI CD not come ready
On Tue, Jan 25, 2000 at 09:40:11AM +0100, Anders Andersson wrote: I have the same problem: [anders@enterprise:anders] $ dmesg | grep ata ata-pci0: Intel PIIX3 ATA controller port 0xffa0-0xffaf at device 7.1 on pci0 ata0 at 0x01f0 irq 14 on ata-pci0 ata-isa0: already registered as ata0 ata0-slave: ata_command: timeout waiting for intr ata0-slave: identify failed -- Anders Andersson [EMAIL PROTECTED] Sanyusan International AB http://www.sanyusan.se/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message With current cvsupped an hour ago, I am seeing this. With current about a month old things are perfect. (and have been for many months on ata driver) Hardware is SMP (2*PIII-450) BX chipset motherboard, second bus has IDE hard disk as primary and atapi CD as secondary.I have never prior to this seen a failure to probe. The primary drive runs fine. I get exactly the same error message on the recent kernel. Normal (correct boot messages) Jan 25 20:08:13 rose /kernel: Copyright (c) 1992-1999 The FreeBSD Project. Jan 25 20:08:13 rose /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Jan 25 20:08:13 rose /kernel: The Regents of the University of California. All rights reserved. Jan 25 20:08:13 rose /kernel: FreeBSD 4.0-CURRENT #1: Tue Dec 28 17:21:58 CST 1999 Jan 25 20:08:13 rose /kernel: [EMAIL PROTECTED]:/usr/src/sys/compile/ROSE Jan 25 20:08:13 rose /kernel: Timecounter "i8254" frequency 1193182 Hz Jan 25 20:08:13 rose /kernel: CPU: Pentium III/Xeon (451.02-MHz 686-class CPU) Jan 25 20:08:13 rose /kernel: Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Jan 25 20:08:13 rose /kernel: Features=0x387fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,PN,MMX,FXSR,XMM Jan 25 20:08:13 rose /kernel: real memory = 268423168 (262132K bytes) Jan 25 20:08:13 rose /kernel: avail memory = 256626688 (250612K bytes) Jan 25 20:08:13 rose /kernel: Programming 24 pins in IOAPIC #0 Jan 25 20:08:13 rose /kernel: FreeBSD/SMP: Multiprocessor motherboard Jan 25 20:08:13 rose /kernel: cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee0 Jan 25 20:08:13 rose /kernel: cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee0 Jan 25 20:08:13 rose /kernel: io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Jan 25 20:08:13 rose /kernel: Preloaded elf kernel "kernel" at 0xc03a. Jan 25 20:08:13 rose /kernel: Pentium Pro MTRR support enabled Jan 25 20:08:13 rose /kernel: md0: Malloc disk Jan 25 20:08:13 rose /kernel: npx0: math processor on motherboard Jan 25 20:08:13 rose /kernel: npx0: INT 16 interface Jan 25 20:08:13 rose /kernel: pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard Jan 25 20:08:13 rose /kernel: pci0: PCI bus on pcib0 Jan 25 20:08:13 rose /kernel: pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0 Jan 25 20:08:13 rose /kernel: pci1: PCI bus on pcib1 Jan 25 20:08:13 rose /kernel: vga-pci0: Matrox model 051f graphics accelerator irq 16 at device 0.0 on pci1 Jan 25 20:08:13 rose /kernel: isab0: Intel 82371AB PCI to ISA bridge at device 4.0 on pci0 Jan 25 20:08:13 rose /kernel: isa0: ISA bus on isab0 Jan 25 20:08:13 rose /kernel: ata-pci0: Intel PIIX4 ATA controller at device 4.1 on pci0 Jan 25 20:08:13 rose /kernel: ata-pci0: Busmastering DMA supported Jan 25 20:08:13 rose /kernel: ata0 at 0x01f0 irq 14 on ata-pci0 Jan 25 20:08:13 rose /kernel: ata1 at 0x0170 irq 15 on ata-pci0 Jan 25 20:08:13 rose /kernel: pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 4.2 Jan 25 20:08:13 rose /kernel: Timecounter "PIIX" frequency 3579545 Hz Jan 25 20:08:13 rose /kernel: intpm0: Intel 82371AB Power management controller at device 4.3 on pci0 Jan 25 20:08:13 rose /kernel: intpm0: I/O mapped e800 Jan 25 20:08:13 rose /kernel: intpm0: intr IRQ 9 enabled revision 0 Jan 25 20:08:13 rose /kernel: smbus0: System Management Bus on intsmb0 Jan 25 20:08:13 rose /kernel: smb0: SMBus general purpose I/O on smbus0 Jan 25 20:08:13 rose /kernel: intpm0: PM I/O mapped e400 Jan 25 20:08:13 rose /kernel: bktr0: BrookTree 848A irq 19 at device 9.0 on pci0 Jan 25 20:08:13 rose /kernel: iicbb0: I2C generic bit-banging driver on bti2c0 Jan 25 20:08:13 rose /kernel: iicbus0: Philips I2C bus on iicbb0 master-only Jan 25 20:08:13 rose /kernel: smbus1: System Management Bus on bti2c0 Jan 25 20:08:13 rose /kernel: smb1: SMBus general purpose I/O on smbus1 Jan 25 20:08:13 rose /kernel: bktr0: Hauppauge Model 60104 C VM Jan 25 20:08:13 rose /kernel: bktr0: Detected a MSP3400C-C6 at 0x80 Jan 25 20:08:13 rose /kernel: Hauppauge WinCast/TV, Philips PAL I tuner, msp3400c stereo. Jan 25 20:08:13 rose /kernel: fxp0: Intel EtherExpress Pro 10/100B Ethernet irq 16 at device 10.0 on pci0 Jan 25 20:08:13 rose /kernel: fxp0: Ethernet address 00:90:27:3c:03:4d Jan 25 20:08:13 rose /kernel: fxp0: supplying EUI64: 00:90:27:ff:fe:3c:03:4d Jan 25 20:08:13 rose
Re: My ATAPI CD not come ready
At 09:47 01/25/2000 +0100, Soren Schmidt wrote: It seems Anders Andersson wrote: I have the same problem: [anders@enterprise:anders] $ dmesg | grep ata ata-pci0: Intel PIIX3 ATA controller port 0xffa0-0xffaf at device 7.1 on pci0 ata0 at 0x01f0 irq 14 on ata-pci0 ata-isa0: already registered as ata0 ata0-slave: ata_command: timeout waiting for intr ata0-slave: identify failed Could I please have a complete dmesg from that ?? -Søren Don't mean to butt in here, I haven't really been following the thread - but I may have found a workaround/clue. I have a Sony CDU-55E (ooold 2x) on secondary master of the PIIX4 on my BP6. By going into the BIOS (the section of it where you would set CHS numbers, LBA, etc) and changing the secondary master device from "none" to "auto", I have gone from: SMP: AP CPU #1 Launched! ata1-master: ata_command: timeout waiting for intr ata1-master: identify failed ad0: 9671MB disk IBM-DTTA-351010 at ata0 as master mode UDMA33 Mounting root from ufs:/dev/ad0s1a to: SMP: AP CPU #1 Launched! ad0: 9671MB disk IBM-DTTA-351010 at ata0 as master mode UDMA33 acd0: CDROM CD-ROM CDU55E at ata1 as master mode PIO0 Mounting root from ufs:/dev/ad0s1a I stumbled upon this quite by accident, but maybe it'll be of some help to somebody... BTW, this was on a kernel from around 20:00 GMT Jan 25 Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My ATAPI CD not come ready
It seems Tom Embt wrote: Don't mean to butt in here, I haven't really been following the thread - but I may have found a workaround/clue. I have a Sony CDU-55E (ooold 2x) on secondary master of the PIIX4 on my BP6. By going into the BIOS (the section of it where you would set CHS numbers, LBA, etc) and changing the secondary master device from "none" to "auto", I have gone from: BTW, this was on a kernel from around 20:00 GMT Jan 25 Interesting... What version is you ata-all.c ?? its damn close to the commit I just made, that should fix that problem... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My ATAPI CD not come ready
It seems Alex wrote: Speaking of identify failed, I get the following: ata-pci0: Intel PIIX4 ATA-33 controller port 0xfcf0-0xfcff at device 1.1 on pci0 ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ... ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ad0: 6194MB disk TOSHIBA MK6409MAV at ata0 as master mode UDMA33 acd0: CDROM UJDA150 at ata1 as master mode PIO4 You need to update.. -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My ATAPI CD not come ready
Soren Schmidt wrote: It seems Alex wrote: Speaking of identify failed, I get the following: ata-pci0: Intel PIIX4 ATA-33 controller port 0xfcf0-0xfcff at device 1.1 on pci0 ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ... ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ad0: 6194MB disk TOSHIBA MK6409MAV at ata0 as master mode UDMA33 acd0: CDROM UJDA150 at ata1 as master mode PIO4 You need to update.. OK - I've just updated. Here goes again: ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ad0: 6194MB TOSHIBA MK6409MAV [13424/15/63] at ata0-master using UDMA33 acd0: CDROM UJDA150 at ata1-master using PIO4 Mounting root from ufs:/dev/ad0s2a I wouldn't be surprised if ATAPI_CMD_IDENTIFY failed on ata1-master, but why does it say ata1-slave? It's a notebook PC, so unfortunately I'm not sure how it's all connected. Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My ATAPI CD not come ready, (.. and no sound with cmi8330)
Last weekend i tried patches from Soren Schmidt to reactivate my old cdrom which went away after the ata-update around the 18. January. This patches completely broke ata support for me (that means the kernel did not boot anymore). Of course i reported this one or two days later. Now an equivalent variant (while loop instead of goto in ata_getparam , ata-all.c,v 1.43) is committed and surprise, the new kernel does not boot anymore. The following i had to write down to paper: ata0-slave: ata_command: timeout waiting for intr ata0-slave: identify failed ata0-master: timeout waiting to give command=ec s=90 e=00 ata0-master: identify failed no way to mount root .. After booting with a 17. January-Kernel i reverted the retry logic in ata_getparam and had a kernel that booted again but did not recognize my cdrom drive, here are lines from dmesg (some lines show detection of the on board soundcard but this is not related to it, i get the same result when i patch sound/isa/mss.c and sound/isa/sbc.c to switch the card to sb-mode): Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (262.36-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! ata-pci0: SiS 5591 ATA-33 controller port 0x4000-0x400f,0x2000-0x2003,0x8040-0x8047,\ 0xcc880a4-0xcc880a7,0x2143200-0x2143207 \ irq 0 at device 1.1 on pci0 ata0 at 0x01f0 irq 14 on ata-pci0 pcm0: CMI8330 at port 0x530-0x537,0x388-0x38f irq 5 drq 0 on isa0 device_probe_and_attach: pcm0 attach returned 6 unknown0: CMI8330/C3D Audio Adapter at port 0x330-0x331 irq 9 on isa0 unknown1: CMI8330/C3D Audio Adapter at port 0x200-0x207 on isa0 unknown2: CMI8330/C3D Audio Adapter at port 0x220-0x22f irq 10 drq 1,5 on isa0 and now the failure in detection of the ata0-slave: ata_command(scp, device, command, 0, 0, 0, 0, 0, ATA_WAIT_INTR) returned with 0, but ata_wait(scp, device, ATA_S_READY|ATA_S_DSC|ATA_S_DRQ) returned with nonzero value, and so ata_getparam with -1. At last ad0 was made successfully: ad0: 14664MB disk IBM-DJNA-351520 at ata0 as master mode UDMA33 -- Fritz Heinrichmeyer mailto:[EMAIL PROTECTED] FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://www-es.fernuni-hagen.de/~jfh To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My ATAPI CD not come ready, (.. and no sound with cmi8330)
It seems F. Heinrichmeyer wrote: Last weekend i tried patches from Soren Schmidt to reactivate my old cdrom which went away after the ata-update around the 18. January. This patches completely broke ata support for me (that means the kernel did not boot anymore). Of course i reported this one or two days later. I was under the impression that it was something else that caused it not to boot, you didn't tell me back then it was because of the ata driver, oh well... Now an equivalent variant (while loop instead of goto in ata_getparam , ata-all.c,v 1.43) is committed and surprise, the new kernel does not boot anymore. I suggest you try out the 1.44 version that has been committed since and let me know what that brings. At any rate I'd be interested in a full verbose dmesg from the machine... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My ATAPI CD not come ready
It seems Alex wrote: You need to update.. OK - I've just updated. Here goes again: ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ad0: 6194MB TOSHIBA MK6409MAV [13424/15/63] at ata0-master using UDMA33 acd0: CDROM UJDA150 at ata1-master using PIO4 Mounting root from ufs:/dev/ad0s2a I wouldn't be surprised if ATAPI_CMD_IDENTIFY failed on ata1-master, but why does it say ata1-slave? It's a notebook PC, so unfortunately I'm not sure how it's all connected. Apparently it thinks something is there, could you mail me a complete verbose bootlog (dmesg) please, and I'll try to figure out what is going wrong.. -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My ATAPI CD not come ready
Hi At Sun, 23 Jan 2000 18:51:25 +0100 (CET), Soren Schmidt [EMAIL PROTECTED] wrote: I updated to today's -current from -stable. My ATAPI CD-ROM drive doesn't probed, and is seemed to be halted. (The tray is locked, won't open, and the LED keeps being on.) This is fixed in the next update, due as soon as I get time Thank you for fixing, but still not probed. What can I do for your work? --kernel config-- # ATA and ATAPI devices device ata0at isa? port IO_WD1 irq 14 device ata1at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives #device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering #optionsATA_ENABLE_ATAPI_DMA#Enable DMA on ATAPI devices --boot -v log-- : : ata-pci0: Intel PIIX4 ATA-33 controller port 0xf000-0xf00f at device 7.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xf000 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=00 status1=00 ata0: devices = 0x4 ata0 at 0x01f0 irq 14 on ata-pci0 : ata-isa0: already registered as ata0 : ata0-master: ata_command: timeout waiting for intr ata0-master: identify failed : : To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My ATAPI CD not come ready
It seems Motomichi Matsuzaki wrote: Thank you for fixing, but still not probed. What can I do for your work? ata-pci0: Intel PIIX4 ATA-33 controller port 0xf000-0xf00f at device 7.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xf000 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=00 status1=00 ata0: devices = 0x4 ata0 at 0x01f0 irq 14 on ata-pci0 : ata-isa0: already registered as ata0 : ata0-master: ata_command: timeout waiting for intr That has me worried, what make/version is the drive ?? -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My ATAPI CD not come ready
At Tue, 25 Jan 2000 08:29:32 +0100 (CET), Soren Schmidt [EMAIL PROTECTED] wrote: Thank you for fixing, but still not probed. ata-pci0: Intel PIIX4 ATA-33 controller port 0xf000-0xf00f at device 7.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xf000 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=00 status1=00 ata0: devices = 0x4 ata0 at 0x01f0 irq 14 on ata-pci0 : ata-isa0: already registered as ata0 : ata0-master: ata_command: timeout waiting for intr That has me worried, what make/version is the drive ?? wdc says: wdc0: unit 0 (atapi): CD-ROM CDU77E-NE/1.2g, removable, accel, dma,iordy -- Motomichi Matsuzaki [EMAIL PROTECTED] Dept. of Biological Science, Faculty of Sciences, Univ. of Tokyo, Japan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My ATAPI CD not come ready
It seems Motomichi Matsuzaki wrote: Hi. I updated to today's -current from -stable. My ATAPI CD-ROM drive doesn't probed, and is seemed to be halted. (The tray is locked, won't open, and the LED keeps being on.) Mother board: ABIT BH6 CD-ROM drive: ATAPI [CDU77E-NE] on primary-master other ATAs: none It worked fine on -stable. I tried to use 'obsolete' wdc/wcd driver, it works fine. This is fixed in the next update, due as soon as I get time -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
