From owner-freebsd-questions Mon Sep 4 17:26:56 2000 Delivered-To: freebsd-questions@freebsd.org Received: from stjohn.stjohn.ac.th (stjohn.stjohn.ac.th [202.21.144.1]) by hub.freebsd.org (Postfix) with ESMTP id D7D4037B422 for ; Mon, 4 Sep 2000 17:26:48 -0700 (PDT) Received: from granite.impoffice.ac.th ([203.151.134.100]) by stjohn.stjohn.ac.th (8.9.3/8.9.3) with SMTP id HAA20198; Tue, 5 Sep 2000 07:21:48 +0700 (GMT) Message-Id: <3.0.6.32.20000905072848.0088ed00@stjohn.stjohn.ac.th> X-Sender: mcrogerm@stjohn.stjohn.ac.th X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Tue, 05 Sep 2000 07:28:48 +0700 To: Kent Stewart From: Roger Merritt Subject: Re: mounting ATAPI cdroms Cc: freebsd-questions@FreeBSD.ORG In-Reply-To: <39B4094F.AE80D7C2@urx.com> References: <20000904180850.A5141@lpthe.jussieu.fr> <86snrgug13.fsf@linum.cofc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:42 PM 9/4/00 -0700, you wrote: > > >Allan Strand wrote: >> >> Have the problems with mounting ATAPI CDROMs been resolved in the >> stable branch? >> >> I did a fresh cvsup last night (9/3/00), made world and a new kernel >> this morning, and I am still unable to mount my CDRW drive. >> Potentially this is a problem with my hardware, although the drive is >> able to write CDROMs and play music CDs. If mounting CDROMS is >> working for everyone else, then I'll suspect my hardware. > >>From http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/ata/atapi-cd.c >it was fixed on 25 August 2000. The mounting error made it look like >an audio cd was being mounted. The messages were >> : > : RRIP without PX field? >> : > : Aug 25 03:59:15 jade /kernel: RRIP without PX field? >> : > : Aug 25 03:59:15 jade /kernel: RRIP without PX field? > >If you are still seeing these, then you didn't install your kernel :). > >Kent > Clearly I've missed something here. I did a cvsup and rebuilt world on 3 Sep and my CD-ROM still isn't being detected at all. From dmesg (I did a verbose boot if more is needed): pci0: on pcib0 atapci0: port 0xffa0-0xffaf,0x374-0x377,0x170-0x177, 0x3f4-0x3f7,0x1f0-0x1f7 irq 0 at device 0.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xffa0 ata0: mask=03 status0=50 status1=50 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xffa8 ata1: mask=03 status0=50 status1=00 ata1: mask=03 status0=50 status1=00 ata1: devices = 0x1 ata1: at 0x170 irq 15 on atapci0 isab0: at device 1.0 on pci0 isa0: on isab0 pci0: (vendor=0x1039, dev=0x0009) at 1.1 pcib2: at device 2.0 on pci0 ... ata0-master: DMA limited to UDMA33, non-ATA66 compliant cable ata0-master: success setting UDMA2 on SiS chip ad0: ATA-4 disk at ata0 as master ad0: 4126MB (8452080 sectors), 8944 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad0: piomode=4 dmamode=2 udmamode=4 cblid=0 Creating DISK ad0 Creating DISK wd0 ata1-master: success setting UDMA2 on SiS chip ad2: ATA-2 disk at ata1 as master ad2: 3077MB (6303024 sectors), 6253 cyls, 16 heads, 63 S/T, 512 B/S ad2: 16 secs/int, 1 depth queue, UDMA33 ad2: piomode=4 dmamode=2 udmamode=2 cblid=0 Creating DISK ad2 Creating DISK wd2 Mounting root from ufs:/dev/ad0s1a ad0s1: type 0xa5, start 63, end = 8452079, size 8452017 : OK In my configuration file I've got: # ATA and ATAPI devices #device ata0 at isa? port IO_WD1 irq 14 #device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID #Static device numbering # Comment out 1 Sep 00 14:50 # IDE devices -- Incompatible with ATA devices above #device wdc0 at isa? port IO_WD1 irq 14 #device wd0 at wdc0 drive 0 #device wd1 at wdc0 drive 1 #device wdc1 at isa? port IO_WD2 irq 15 #device wd2 at wdc1 drive 0 #device wd3 at wdc1 drive 1 #options IDE_DELAY=8000 # Be optimistic about Joe IDE device # IDE CD-ROM & CD-R/RW driver - requires wdc controller #device wcd I had also tried this by uncommenting the lines for ata0 and ata1, but it didn't seem to make any difference. I don't see any provision in LINT for setting flags. At the moment of writing I'm in the process of building a 4.1-RELEASE, but from what you said above it isn't going to do me any good. This is so frustrating! -- Roger It's is not, it isn't ain't, and it's it's, not its, if you mean it is. If you don't, it's its. Then too, it's hers. It isn't her's. It isn't our's either. It's ours, and likewise yours and theirs. -- Oxford University Press, Edpress News To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message