atapicam issues
I have 2 systems running 8.0 installed from the same CD. One of them shows 2 PASS devices as expected and camcontrol devlist shows the appropriate devices. They work as expected. The other does not show any PASS devices and camcontrol devlist shows nothing. Doing a kldload atapicam installs the PASS devices and then camcontrol works properly. Why would that system require atapicam to be manually added? That module was not loaded on the working system. I installed it there first by accident but it had no detrimental effect. I don't find any reference to atapi or atapicam in the various rc files.___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: atapicam issues
On Sat, May 22, 2010 at 10:20 PM, Doug Hardie bc...@lafn.org wrote: I have 2 systems running 8.0 installed from the same CD. One of them shows 2 PASS devices as expected and camcontrol devlist shows the appropriate devices. They work as expected. The other does not show any PASS devices and camcontrol devlist shows nothing. Doing a kldload atapicam installs the PASS devices and then camcontrol works properly. Why would that system require atapicam to be manually added? That module was not loaded on the working system. I installed it there first by accident but it had no detrimental effect. I don't find any reference to atapi or atapicam in the various rc files.___ atapicam is loaded from /boot/loader.conf as most hardware kernel mods are. AFAIK, something would have needed to changed on your working system the behavior you report. Perhaps you followed the handbook's instructions about cd burning long ago and forgot you edited the config? http://www.freebsd.org/doc/en/books/handbook/creating-cds.html -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: atapicam issues
On 22 May 2010, at 20:47, Adam Vande More wrote: On Sat, May 22, 2010 at 10:20 PM, Doug Hardie bc...@lafn.org wrote: I have 2 systems running 8.0 installed from the same CD. One of them shows 2 PASS devices as expected and camcontrol devlist shows the appropriate devices. They work as expected. The other does not show any PASS devices and camcontrol devlist shows nothing. Doing a kldload atapicam installs the PASS devices and then camcontrol works properly. Why would that system require atapicam to be manually added? That module was not loaded on the working system. I installed it there first by accident but it had no detrimental effect. I don't find any reference to atapi or atapicam in the various rc files.___ atapicam is loaded from /boot/loader.conf as most hardware kernel mods are. AFAIK, something would have needed to changed on your working system the behavior you report. Perhaps you followed the handbook's instructions about cd burning long ago and forgot you edited the config? http://www.freebsd.org/doc/en/books/handbook/creating-cds.html Both machines were installed from the same CD over old Windows systems. They were installed within a few days of each other. loader.conf only has console=comconsole. Reading through the handbook page above it indicates that atapicam needs to be loaded in /boot/loader.conf. I'll add that to both machines. Makes me wonder why the one worked. kldstat showed it was not loaded.___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: atapicam issues
On Sat, May 22, 2010 at 11:01 PM, Doug Hardie bc...@lafn.org wrote: Both machines were installed from the same CD over old Windows systems. They were installed within a few days of each other. loader.conf only has console=comconsole. Reading through the handbook page above it indicates that atapicam needs to be loaded in /boot/loader.conf. I'll add that to both machines. Makes me wonder why the one worked. kldstat showed it was not loaded. Well I assumed the hardware is identical but is it a scsi optical drive in the one worked? -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: atapicam issues
On 22 May 2010, at 21:05, Adam Vande More wrote: On Sat, May 22, 2010 at 11:01 PM, Doug Hardie bc...@lafn.org wrote: Both machines were installed from the same CD over old Windows systems. They were installed within a few days of each other. loader.conf only has console=comconsole. Reading through the handbook page above it indicates that atapicam needs to be loaded in /boot/loader.conf. I'll add that to both machines. Makes me wonder why the one worked. kldstat showed it was not loaded. Well I assumed the hardware is identical but is it a scsi optical drive in the one worked? Hardware is fairly identical but not completely. Drives are both IDE. There are no SCSI cards on either machine. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 5.3 ata / atapicam issues (update)
Hello, I think time has come to fill a problem report. I did started a initial one, which is attached to this mail. Can you read through the attached PR and comment its contents, please? Rob schrieb: Hope this helps someone. I'm not at all sure where/what the problem is but I'll be happy to run on the embedded controller for the time being. (while PIO 4 != DMA 133, reliability/functionality is king!) Neither have I an idea what going on here, but after having upgraded a few PCs from 4.10 to 5.3, I empirically deduced following conclusions: 1) The problems is since 5.3, not with any 4.X. 2) Such problems occur when the media (harddisk in my case) are capable of doing a higher speed than the motherboard. For example, harddisk can do maximum UDMA100, but motherboard can maximum handle UDMA66. In such cases I need hw.ata.ata_dma=0 in loader.conf, which slows down the speed to PIO4. Without the hw.ata.ata_dma=0, I get various results, which can be 'kernel panic at bootup after installation' on one PC, to 'odd crashing of X for no good reason' on another PC. When the maximum speeds of harddisk and motherboard match, there's no problem, eventhough they may both operate at a lower than maximum speed. Something really uggly has entered the code of 5.3, with respect to disk speed matching, I believe. Regards, Rob. __ Do you Yahoo!? Yahoo! Mail - 250MB free storage. Do more. Manage less. http://info.mail.yahoo.com/mail_250 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] SEND-PR: -*- send-pr -*- SEND-PR: Lines starting with `SEND-PR' will be removed automatically, as SEND-PR: will all comments (text enclosed in `' and `'). SEND-PR: SEND-PR: Please consult the following URL if you are not sure how to SEND-PR: fill out a problem report: SEND-PR: http://www.freebsd.org/doc/en/articles/problem-reports/ SEND-PR: SEND-PR: Note that the Synopsis field is mandatory. SEND-PR: SEND-PR: Please note that (unless you state otherwise) if your report SEND-PR: includes a patch then it will be taken under the same license as SEND-PR: the one on the file(s) you want to change. SEND-PR: SEND-PR: BE ADVISED THAT FREEBSD PROBLEM REPORTS ARE PUBLIC INFORMATION AND SEND-PR: WILL BE PUBLISHED AS-IS ON THE PROJECT'S MAILING LISTS AND WEB SITES. SEND-PR: DO NOT SUBMIT ANY INFORMATION YOU DO NOT WANT MADE PUBLIC. SEND-PR: SEND-PR: If you wish to submit a problem report confidentially, then contact SEND-PR: the FreeBSD bugmaster ([EMAIL PROTECTED]) to arrange for a SEND-PR: relevant developer to be contacted. SEND-PR: SEND-PR: For sensitive security issues, consider contacting the FreeBSD SEND-PR: security officer team ([EMAIL PROTECTED]) directly. SEND-PR: SEND-PR: Choose from the following categories: SEND-PR: SEND-PR: advocacy alpha amd64 bin conf docs SEND-PR: gnu i386 ia64 java kern misc SEND-PR: ports powerpc sparc64 standards threads usb SEND-PR: www SEND-PR: To: [EMAIL PROTECTED] From: Daniel S. Haischt [EMAIL PROTECTED] Reply-To: Daniel S. Haischt [EMAIL PROTECTED] Cc: X-send-pr-version: 3.113 X-GNATS-Notify: Submitter-Id: current-users Originator:Daniel S. Haischt Organization: Daniel S. Haischt IT Consulting Confidential: no Synopsis: FreeBSD 5.3 ATA unreliability if using ATAPICAM Severity: serious Priority: high Category: kern Class: sw-bug Release: FreeBSD 5.3-STABLE i386 Environment: System: FreeBSD abyssone.abyssworld.de 5.3-STABLE FreeBSD 5.3-STABLE #0: Thu Jan 20 13:07:40 CET 2005 root@:/usr/obj/usr/src/sys/ABYSSONE i386 * PI 233 MMX with an additional Promise PDC20269 UDMA133 controller * ATA 100/133 IDE cable * IBM disk: 78533MB IC35L080AVVA07-0/VA4OA52A [170197/15/63] at ata2-master UDMA100 * Plextor CDROM drives + CDRW PLEXTOR CD-R PREMIUM/1.05 at ata3-master UDMA33 + DVDROM PLEXTOR DVD-ROM PX-116A2 0100/1.00 at ata3-slave UDMA66 Description: This problem report is a synthesis of several issues posted to the FreeBSD questions mailing list! The ATA issues were reported numeros times by people using a Promise PDC20269 UDMA133 controler, so I will stick with that controller. If using the just mentioned controller, especially the 2nd IDE channel, it was observed that during boot time this particular hardware configuration may cause the following issues: * Interrupt Storms * READ_DMA timed out * Kernel Panics To trace the issue, the following hardware configurations has been tested: Configuration #1 (success): * harddrive attached to IDE channel #1 * no device attached to IDE channel #2 Configuration #2 (failure): * harddrive attached to IDE channel #1 * CDROM drive(s) attached to IDE channel #2 Configuration #3 (failure): * no device attached to IDE channel #1 * harddrive
Re: 5.3 ata / atapicam issues (update)
--- Daniel S. Haischt wrote: Can you read through the attached PR and comment its contents, please? It's a little too technical for me, but let me add the components of one of my trouble PCs: atapci0: VIA 82C596B UDMA66 controller ad0: 43979MB IBM-DTLA-307045/TX6OA50C [89355/16/63] at ata0-master PIO4 acd0: CDROM CRD-8520B/1.00 at ata1-master PIO4 The harddisk can do UDMA100, but if I let FreeBSD 5.3 sort it out by itself, the kernel panics at bootup. Modifying loader.conf, forces my fast harddisk to operate at PIO4 mode, which is far from optimum; it should at least be able to operate at UDMA66 !! FreeBSD 5.3 is not capable of solving this properly. This observation I could not find in your PR report. Regards, Rob. __ Do you Yahoo!? All your favorites on one personal page Try My Yahoo! http://my.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 ata / atapicam issues (update)
--- Rob [EMAIL PROTECTED] wrote: --- Daniel S. Haischt wrote: Can you read through the attached PR and comment its contents, please? It's a little too technical for me, but let me add the components of one of my trouble PCs: atapci0: VIA 82C596B UDMA66 controller ad0: 43979MB IBM-DTLA-307045/TX6OA50C [89355/16/63] at ata0-master PIO4 acd0: CDROM CRD-8520B/1.00 at ata1-master PIO4 The harddisk can do UDMA100, but if I let FreeBSD 5.3 sort it out by itself, the kernel panics at bootup. Modifying loader.conf, forces my fast harddisk to operate at PIO4 mode, which is far from optimum; it should at least be able to operate at UDMA66 !! FreeBSD 5.3 is not capable of solving this properly. This observation I could not find in your PR report. Forgot to mention another PC with a brandnew Winchester Harddisk of 80 Gb (sorry I don't have the specs handy) and on the motherboard a chipset of atapci0: VIA 82C596 ATA66 controller This combination does boot, but X always crashes. Modifying the loader.conf again solves this problem. Rob. __ Do you Yahoo!? The all-new My Yahoo! - Get yours free! http://my.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
5.3 ata / atapicam issues (update)
Greetings, Just an update I pulled out the Promise adapter and connected my disk to the primary embedded IDE controller (max speed PIO 4) Left the atapi CDRW drive as a SLAVE on the secondary controller. Next, I tried ripping an audio CD with cdda2wav, and to my surprise, it was successful. The system did report several messages during the ripping process, like. Feb 3 00:11:33 arabian kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left ) LBA=136492211 Feb 3 00:11:34 arabian kernel: ad0: FAILURE - READ_DMA timed out Feb 3 00:11:39 arabian kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left ) LBA=136414323 Feb 3 00:11:39 arabian kernel: ad0: FAILURE - READ_DMA timed out Feb 3 00:12:05 arabian kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left ) LBA=137621267 Feb 3 00:12:05 arabian kernel: ad0: FAILURE - READ_DMA timed out Feb 3 00:12:11 arabian kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left ) LBA=137543379 Feb 3 00:12:11 arabian kernel: ad0: FAILURE - READ_DMA timed out but it was successful. I disabled all ATA DMA (hw.ata.ata_dma=0 my in loader.conf) and tried to rip the disk again. It completed without a single error. Further, I was able to burn 5 CDs on the same drive at ridiculous speeds (48X reported by cdrecord) without a single issue. Hope this helps someone. I'm not at all sure where/what the problem is but I'll be happy to run on the embedded controller for the time being. (while PIO 4 != DMA 133, reliability/functionality is king!) If there's any way I can help solve this issue just say how! Kind regards -- Randall D. DuCharme (Radio AD5GB) Powered by FreeBSD! The Power to Serve ___ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 ata / atapicam issues (update)
Hope this helps someone. I'm not at all sure where/what the problem is but I'll be happy to run on the embedded controller for the time being. (while PIO 4 != DMA 133, reliability/functionality is king!) Neither have I an idea what going on here, but after having upgraded a few PCs from 4.10 to 5.3, I empirically deduced following conclusions: 1) The problems is since 5.3, not with any 4.X. 2) Such problems occur when the media (harddisk in my case) are capable of doing a higher speed than the motherboard. For example, harddisk can do maximum UDMA100, but motherboard can maximum handle UDMA66. In such cases I need hw.ata.ata_dma=0 in loader.conf, which slows down the speed to PIO4. Without the hw.ata.ata_dma=0, I get various results, which can be 'kernel panic at bootup after installation' on one PC, to 'odd crashing of X for no good reason' on another PC. When the maximum speeds of harddisk and motherboard match, there's no problem, eventhough they may both operate at a lower than maximum speed. Something really uggly has entered the code of 5.3, with respect to disk speed matching, I believe. Regards, Rob. __ Do you Yahoo!? Yahoo! Mail - 250MB free storage. Do more. Manage less. http://info.mail.yahoo.com/mail_250 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
