Re: "options atapicam" and/or "device ATA_CAM" in kernel config?
"b. f." writes: > The handbook does contain some oblique and scattered references to the > new code, or at least to constructs that are common to both the old > and the new code, but the addition of a brief discussion of the > differences between the new and old ATA code in the handbook -- i.e., > the kernel and userland components that are now obsolete, and their > replacements -- might be of some help to users. The primary author of > the new code did add some material to various notes and manpages, but > he has been very busy writing and debugging code, and English is not > his first language, so others will have to supplement his efforts. > Perhaps you could ask for some additions on the freebsd-doc mailing > list? I started writing some additions as soon as I noticed the issue. They won't be sufficient, since I don't yet have a 9.x system, but they'll be a start. ___ 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: "options atapicam" and/or "device ATA_CAM" in kernel config?
> Now I think I'll try to rebuild the kernel with "options ATA_CAM" and drop > "device atapicam". > > This question needs to be better resolved in time for FreeBSD 9.0-RELEASE. > > I cross-post this message to freebsd-curr...@freebsd.org so the developers > will see it. FreeBSD users want to be able to burn CDs and DVDs, and since > SCSI hardware has fallen out of style, I can say very few if any FreeBSD 9.0 > users will have an actual SCSI CD or DVD drive. The new CAM(4) is not just for SCSI devices (and SCSI, as it is usually used now, does not deal only with the old parallel SCSI devices). Despite the fact that most CD and DVD drives will now appear as cdX devices, and cd(4) is full of references to SCSI, most CD and DVD drives should be supported. And while burncd(8) will not work with the new interface, other software in ports should -- for example, sysutils/cdrtools and sysutils/cdrtools-devel, as was mentioned before. b. ___ 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: "options atapicam" and/or "device ATA_CAM" in kernel config?
> On 11/27/11, Lowell Gilbert wrote: > > "b. f." writes: > >>> > > What is the role of "options atapicam" and "device ATA_CAM" in kernel > >>> > > config file? > >>> > > Are they redundant? Kernel will build with both these options, but > >>> > > will it make things go awry? Is ATA_CAM deprecated? > >> They are redundant and incompatible. atapicam is deprecated, and > >> ATA_CAM is the new default on FreeBSD 9 and 10. Unless you have some > >> special requirements, you should use ATA_CAM on recent versions of > >> FreeBSD, because it usually performs better than the old ATA code, and > >> has added functionality. > > Ah. My apologies to anyone I confused with my incorrect comments. > > I must say that I'm thoroughly disappointed that my searches through the > > official documentation didn't turn up anything related to this. Even the > > Handbook, with extensive practical descriptions of how to use this > > functionality, doesn't mention that its advice is irrelevant to anything > > past 8.x. > The handbook does contain some oblique and scattered references to the > new code, or at least to constructs that are common to both the old > and the new code, but the addition of a brief discussion of the > differences between the new and old ATA code in the handbook -- i.e., > the kernel and userland components that are now obsolete, and their > replacements -- might be of some help to users. The primary author of > the new code did add some material to various notes and manpages, but > he has been very busy writing and debugging code, and English is not > his first language, so others will have to supplement his efforts. > Perhaps you could ask for some additions on the freebsd-doc mailing > list? > b. Now I see it's "options ATA_CAM" or "device atapicam". It looks like I inadvertently transposed "device" and "options" in subject line. Now I think I'll try to rebuild the kernel with "options ATA_CAM" and drop "device atapicam". This question needs to be better resolved in time for FreeBSD 9.0-RELEASE. I cross-post this message to freebsd-curr...@freebsd.org so the developers will see it. FreeBSD users want to be able to burn CDs and DVDs, and since SCSI hardware has fallen out of style, I can say very few if any FreeBSD 9.0 users will have an actual SCSI CD or DVD drive. Tom ___ 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: "options atapicam" and/or "device ATA_CAM" in kernel config?
On 11/27/11, Lowell Gilbert wrote: > "b. f." writes: > >>> > > What is the role of "options atapicam" and "device ATA_CAM" in kernel >>> > > config file? >>> >>> > > Are they redundant? Kernel will build with both these options, but >>> > > will it make things go awry? Is ATA_CAM deprecated? >> >> They are redundant and incompatible. atapicam is deprecated, and >> ATA_CAM is the new default on FreeBSD 9 and 10. Unless you have some >> special requirements, you should use ATA_CAM on recent versions of >> FreeBSD, because it usually performs better than the old ATA code, and >> has added functionality. > > Ah. My apologies to anyone I confused with my incorrect comments. > > I must say that I'm thoroughly disappointed that my searches through the > official documentation didn't turn up anything related to this. Even the > Handbook, with extensive practical descriptions of how to use this > functionality, doesn't mention that its advice is irrelevant to anything > past 8.x. The handbook does contain some oblique and scattered references to the new code, or at least to constructs that are common to both the old and the new code, but the addition of a brief discussion of the differences between the new and old ATA code in the handbook -- i.e., the kernel and userland components that are now obsolete, and their replacements -- might be of some help to users. The primary author of the new code did add some material to various notes and manpages, but he has been very busy writing and debugging code, and English is not his first language, so others will have to supplement his efforts. Perhaps you could ask for some additions on the freebsd-doc mailing list? b. ___ 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: "options atapicam" and/or "device ATA_CAM" in kernel config?
"b. f." writes: >> > > What is the role of "options atapicam" and "device ATA_CAM" in kernel >> > > config file? >> >> > > Are they redundant? Kernel will build with both these options, but will >> > > it make things go awry? Is ATA_CAM deprecated? > > They are redundant and incompatible. atapicam is deprecated, and > ATA_CAM is the new default on FreeBSD 9 and 10. Unless you have some > special requirements, you should use ATA_CAM on recent versions of > FreeBSD, because it usually performs better than the old ATA code, and > has added functionality. Ah. My apologies to anyone I confused with my incorrect comments. I must say that I'm thoroughly disappointed that my searches through the official documentation didn't turn up anything related to this. Even the Handbook, with extensive practical descriptions of how to use this functionality, doesn't mention that its advice is irrelevant to anything past 8.x. ___ 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: "options atapicam" and/or "device ATA_CAM" in kernel config?
> > > What is the role of "options atapicam" and "device ATA_CAM" in kernel > > > config file? > > > > Are they redundant? Kernel will build with both these options, but will > > > it make things go awry? Is ATA_CAM deprecated? They are redundant and incompatible. atapicam is deprecated, and ATA_CAM is the new default on FreeBSD 9 and 10. Unless you have some special requirements, you should use ATA_CAM on recent versions of FreeBSD, because it usually performs better than the old ATA code, and has added functionality. > > Lowell Gilbert responds: > > > As far as I can see, ATA_CAM isn't currently documented. > > Just ignore it. This is bad advice, for the reasons mentioned above. It is briefly documented in /usr/src/sys/conf/NOTES, and you can find more information about it in the commit logs of the source repository, and the mailing lists. For example: http://svnweb.FreeBSD.org/base?view=revision&revision=195534 ... http://svnweb.FreeBSD.org/base?view=revision&revision=200171 http://svnweb.FreeBSD.org/base?view=revision&revision=220982 http://svnweb.FreeBSD.org/base?view=revision&revision=216088 http://lists.freebsd.org/pipermail/freebsd-current/2009-June/008574.html http://lists.freebsd.org/pipermail/freebsd-current/2011-April/024110.html ... > > So I can say good riddance to ATA_CAM. According to burncd man page, ATA_CAM > is incompatible with burncd, also burncd was deprecated in FreeBSD 9.0. As I wrote above, you probably do _not_ want to discard ATA_CAM on recent versions of FreeBSD. burncd is deprecated because it does not work with ATA_CAM, and no one has volunteered to rewrite it yet. You can use a port like sysutils/cdrtools or sysutils/cdrtools-devel instead. > > > I am trying to burn a CD (or DVD) on a SATA DVD-RW drive, but cdrtools > > > don't work. Why not? Specifically, what fails? Does your kernel include the necessary bits, like ATA_CAM? Have you asked the cdrtools port maintainer for help, and sent him a verbose listing of any errors you encounter? There were some recent CAM changes that broke some ports like audio/cdparanoia, but these ports will probably be fixed soon. ... > > > Also, how do I build and install a kernel to some name other than > > > /boot/kernel, and not build all modules in duplicate? I think we answered these questions in the other recent thread. ... > I don't want to upgrade FreeBSD on older computer because of shortage of disk > space and only 256 MB RAM. Portupgrading everything would be too gruesomely > slow, in addition to likely running short of disk space. You can use a faster computer to build packages for your slower computer, or use packages from the FreeBSD mirrors. You can also use tools like devel/ccache to speed builds, although this requires more disk space. Building ports in a swap-backed memory file system like mdmfs or tmpfs can also help, although you have to be careful when RAM is limited. You could work around your disk space limitations by using a removable drive for builds, or a network-based files system like nfs. And if you have a number of slower computers of the same type, you can speed up builds by having the computers work together, with something like devel/distcc. b. ___ 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: "options atapicam" and/or "device ATA_CAM" in kernel config?
"Thomas Mueller" writes: > > What is the role of "options atapicam" and "device ATA_CAM" in kernel > > config file? > > Are they redundant? Kernel will build with both these options, but will it > > make things go awry? Is ATA_CAM deprecated? Lowell Gilbert responds: > As far as I can see, ATA_CAM isn't currently documented. > Just ignore it. So I can say good riddance to ATA_CAM. According to burncd man page, ATA_CAM is incompatible with burncd, also burncd was deprecated in FreeBSD 9.0. > > I am trying to burn a CD (or DVD) on a SATA DVD-RW drive, but cdrtools > > don't work. > > Also, how do I build and install a kernel to some name other than > > /boot/kernel, and not build all modules in duplicate? > > > > I might want to try kernels with some differences in options, but with the > > same modules. > > NetBSD and Linux make it easy to choose a non-default name for the kernel, > > so I can have multiple kernels and choose one at boot. > The usual way is to have a separate config file for each, although you > can come up with other ways if you feel like being clever. The config > files support an include functionality, so working through the files is > pretty easy. I would likely keep separate config files, especially when disk space is abundant as on a 3 TB hard drive. > As for leaving out modules, there are a number of options documented for > make.conf(5) and src.conf(5) that give you various kinds of control. > > In Linux, beginning with kernels 2.6.*, cdrtools work without the ATA-SCSI > > dance. > You don't say what version of FreeBSD you're on. I'm still using > RELENG_8, so I may be missing some choices for later versions, where I > understand that the CAM code has been significantly reworked. I forgot to mention the FreeBSD version: 9.0, now RC2, started with BETA1 on this computer. I have FreeBSD 8.2 on my older computer, ATA, no SATA. I once burned a CD with burncd after NetBSD cdrecord couldn't find the drive. But I burned other CDs with cdrecord in Linux. I don't want to upgrade FreeBSD on older computer because of shortage of disk space and only 256 MB RAM. Portupgrading everything would be too gruesomely slow, in addition to likely running short of disk space. Tom ___ 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: "options atapicam" and/or "device ATA_CAM" in kernel config?
"Thomas Mueller" writes: > What is the role of "options atapicam" and "device ATA_CAM" in kernel config > file? > > Are they redundant? Kernel will build with both these options, but will it > make things go awry? Is ATA_CAM deprecated? As far as I can see, ATA_CAM isn't currently documented. Just ignore it. > I am trying to burn a CD (or DVD) on a SATA DVD-RW drive, but cdrtools don't > work. > > Also, how do I build and install a kernel to some name other than > /boot/kernel, and not build all modules in duplicate? > > I might want to try kernels with some differences in options, but with the > same modules. > > NetBSD and Linux make it easy to choose a non-default name for the kernel, so > I can have multiple kernels and choose one at boot. The usual way is to have a separate config file for each, although you can come up with other ways if you feel like being clever. The config files support an include functionality, so working through the files is pretty easy. As for leaving out modules, there are a number of options documented for make.conf(5) and src.conf(5) that give you various kinds of control. > In Linux, beginning with kernels 2.6.*, cdrtools work without the ATA-SCSI > dance. You don't say what version of FreeBSD you're on. I'm still using RELENG_8, so I may be missing some choices for later versions, where I understand that the CAM code has been significantly reworked. ___ 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"
"options atapicam" and/or "device ATA_CAM" in kernel config?
What is the role of "options atapicam" and "device ATA_CAM" in kernel config file? Are they redundant? Kernel will build with both these options, but will it make things go awry? Is ATA_CAM deprecated? I am trying to burn a CD (or DVD) on a SATA DVD-RW drive, but cdrtools don't work. Also, how do I build and install a kernel to some name other than /boot/kernel, and not build all modules in duplicate? I might want to try kernels with some differences in options, but with the same modules. NetBSD and Linux make it easy to choose a non-default name for the kernel, so I can have multiple kernels and choose one at boot. In Linux, beginning with kernels 2.6.*, cdrtools work without the ATA-SCSI dance. Tom ___ 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 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: atapicam issues
On Sat, May 22, 2010 at 11:01 PM, Doug Hardie 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 20:47, Adam Vande More wrote: > On Sat, May 22, 2010 at 10:20 PM, Doug Hardie 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 10:20 PM, Doug Hardie 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"
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: Am I back? Re: kernel fault trying to add atapicam...
On Tue, Nov 27, 2007 at 08:12:08AM +0100, Roland Smith wrote: > On Mon, Nov 26, 2007 at 05:35:46PM -0800, Gary Kline wrote: > > > > Folks (to the whole list, but esp'ly Messrs Smith [NL & AU], > > [[ ... ]] > > Can you post or mail your kernel config? > I can sed you mine if that helps. > > > Could it be as simple as Not having done a make clean > > before doing a make buildkernel? > > It is recommended to clean out /usr/obj before starting a new build. I'll try this first, then rebuild 6.2 and try to reboot. So far, I haven't touched the kernel configuration file except for adding atapicam. Willl send, off-list, if same fault hang up during boot. ...But IIRC, *not* haviing removed the /usr/obj tree has caused problems before. gary > > > I don't burn // copy audio > > discs that often and haven't ever copied a DVD; I just want these > > new utilities to work. > > You could try burncd, which doesn't require the speudo-SCSI stuff. But > I've heard a lot of grumbling about it on the list over the years. > > Roland > -- > R.F.Smith http://www.xs4all.nl/~rsmith/ > [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] > pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) -- Gary Kline [EMAIL PROTECTED] www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Am I back? Re: kernel fault trying to add atapicam...
On Mon, Nov 26, 2007 at 05:35:46PM -0800, Gary Kline wrote: > > Folks (to the whole list, but esp'ly Messes Smith [NL & AU], > > I'll believe that my ISDN link is working when/if I see this > echoed from the -questions list. I was busy rebuilding my 6.2 > GENERIC kernel after having added > > ^device atapicam > Lest I stray *too* far OT, I'll share the results of my 3rd > kernel rebuild on this Dell. It crapped out; it hung after > printing out the sio0 line. I had to powercycle and went in by > typing "8" (??) and by hand booting /boot/kernel.old. I tried > twice more by removing part of the additions to GENERIC. Same; > the new kernel still hung. > Here are the sizes of the new kernel (with atapicam) and > the old. > > -r-xr-xr-x 1 root wheel 7206901 Nov 23 21:00 kernel > -r-xr-xr-x 1 root wheel 4001279 Apr 9 2007 kernel > > I realize that drivers can require a lot of space, but not > over 1.2 megs. Att any rate, the newer kernel hangs. > > I will upgrade to the newest 6.2 and try to get the audio > toys functioning. But does anybody know where I fouled up? Can you post or mail your kernel config? I can sed you mine if that helps. > Could it be as simple as Not having done a make clean > before doing a make buildkernel? It is recommended to clean out /usr/obj before starting a new build. > I don't burn // copy audio > discs that often and haven't ever copied a DVD; I just want these > new utilities to work. You could try burncd, which doesn't require the speudo-SCSI stuff. But I've heard a lot of grumbling about it on the list over the years. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpNHWuOL0r6B.pgp Description: PGP signature
Am I back? Re: kernel fault trying to add atapicam...
Folks (to the whole list, but esp'ly Messes Smith [NL & AU],
I'll believe that my ISDN link is working when/if I see this
echoed from the -questions list. I was busy rebuilding my 6.2
GENERIC kernel after having added
^device atapicam
72 hours ago when my feed slowed, then stopped. It `sputtered'
a couple times over the next several hours. By 03:35 I was
convinced that every thing on my LAN was working perfectly.
My ISP said it was my ISDN line; they called the local telco.
Turned out that the telco would have to "roll a truck". Which
may have already happened since I saw blinking LED's on my router.
((*))
Lest I stray *too* far OT, I'll share the results of my 3rd
kernel rebuild on this Dell. It crapped out; it hung after
printing out the sio0 line. I had to powercycle and went in by
typing "8" (??) and by hand booting /boot/kernel.old. I tried
twice more by removing part of the additions to GENERIC. Same;
the new kernel still hung.
Here are the sizes of the new kernel (with atapicam) and
the old.
-r-xr-xr-x 1 root wheel 7206901 Nov 23 21:00 kernel
-r-xr-xr-x 1 root wheel 4001279 Apr 9 2007 kernel
I realize that drivers can require a lot of space, but not
over 1.2 megs. Att any rate, the newer kernel hangs.
I will upgrade to the newest 6.2 and try to get the audio
toys functioning. But does anybody know where I fouled up?
Could it be as simple as Not having done a make clean
before doing a make buildkernel? I don't burn // copy audio
discs that often and haven't ever copied a DVD; I just want these
new utilities to work.
Thanks, people,
gary
--
Gary Kline [EMAIL PROTECTED] www.thought.org Public Service Unix
http://jottings.thought.org http://transfinite.thought.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Problem with atapicam on FreeBSD 6.2-RELEASE-p5 causes system-freeze
Hi all, I'm using FreeBSD 6.2-RELEASE-p5, with the standard SMP kernel found in / usr/src/sys/i386/conf/SMP, when i 'kldload atapicam' i get the following error message which just makes no sense to me: WARNING - PREVENT_ALLOW taskqueue timeout - completing request directly xptioctl: put device pass0 in your kernel config file xptioctl: pass driver is not in the kernel Right after I get this error message, it starts repeating again and again, and the system is no more useable. Then I installed the normal GENERIC kernel without SMP support, and the same thing happens, same error message. Then i tried to compile "device atapicam" directly into the kernel, which makes the system hang at boot time, while recognizing the cdrom. The standard SMP kernel "includes" the GENERIC kernel in which the line "device pass" can be found, that means pass must be allready in the kernel. Please have a look at the output from dmesg and kldstat -v here (link) http://nopaste.info/52ef292281.html I searched the web for similar error messages, and found a message pointing this problem to hald, so i disabled hald to see if that chances anything. And it did, while 'kldload atapicam' i'm not getting the above error message anymore, but 'camcontrol devlist' doesnt show anything and cdrecord -scanbus ends up in the following errormessage: Cdrecord-Clone 2.01 (i386-unknown-freebsd6.2) Copyright (C) 1995-2004 Jÿÿrg Schilling cdrecord: Error 0. Cannot open SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. cdrecord: For possible transport specifiers try 'cdrecord dev=help'. I checked with 'kldstat', and it showed atapicam. Since my mainboard has just one ide port onboard(rest is S-ATA), i have to use a pcie ide-controller "Promise Technology, Inc. PDC20268 (Ultra100 TX2)" on which my dvdwriter(acd0) is connected to. Any help or suggestion is really appreciated. Thanks in advance, greeting Stefan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: atapicam trouble
On Tuesday 17 October 2006 05:47, Johan Johansen wrote: > Actually, on my system I can do mount_udf /dev/acd0 and copy a 3GB > file, I just tried. My problem is adding CAM support, which the > handbook tells me I have to use to burn dvd. > > johan > > > I'm unable to copy a file from a udf-mounted DVD regardless of whether > > atapicam is loaded or not, so I'm not sure if atapicam is just making > > a problem more apparent or what. Are you able to do so? > > > > Thanks, > > Josh > > > > On 10/16/06, Johan Johansen <[EMAIL PROTECTED]> wrote: > > > I still have the same problem as below, even when running 6.2-BETA2 > > > from a FreeSBIE - cd. I wonder if this could have to do with badly > > > supportet motherboard, ASUS P5B, since I dont see any temp-readings > > > with sysctl. cpuTemp and MBTemp are displayed under bios-config. > > ___ Look in /boot/kernel and see if atapikam.ko is there. It should be. If it is, you can use 'atapicam_load="YES"' in /boot/loader.conf to load atapicam at boot. You can use 'kldload atapicam.ko' to just load it while system is running to see if it works before going any further. You can use kldstat to varify that it's loaded. Below is the output of kldstat from one of my systems: # kldstat Id Refs AddressSize Name 1 15 0xc040 5cae28 kernel 21 0xc09cb000 59f4 snd_atiixp.ko 32 0xc09d1000 22b88sound.ko 41 0xc09f4000 4ae8 atapicam.ko 51 0xc09f9000 5a78 if_fwip.ko 61 0xc09ff000 59f00acpi.ko 72 0xc4f2f000 16000linux.ko 81 0xc504a000 2000 rtc.ko Hope this will help you guys a bit. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: atapicam trouble
Actually, on my system I can do mount_udf /dev/acd0 and copy a 3GB file, I just tried. My problem is adding CAM support, which the handbook tells me I have to use to burn dvd. johan > > I'm unable to copy a file from a udf-mounted DVD regardless of whether > atapicam is loaded or not, so I'm not sure if atapicam is just making > a problem more apparent or what. Are you able to do so? > > Thanks, > Josh > > On 10/16/06, Johan Johansen <[EMAIL PROTECTED]> wrote: > > > > > > I still have the same problem as below, even when running 6.2-BETA2 from > > a FreeSBIE - cd. I wonder if this could have to do with badly supportet > > motherboard, ASUS P5B, since I dont see any temp-readings with sysctl. > > cpuTemp and MBTemp are displayed under bios-config. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: atapicam trouble
Johan, I have a PR submitted for this problem. I do not think it is particular to Asus P5B boards, as I tried a Gigabyte DS3 board and it had the same problem. PR is here: http://www.freebsd.org/cgi/query-pr.cgi?pr=103602 I'm unable to copy a file from a udf-mounted DVD regardless of whether atapicam is loaded or not, so I'm not sure if atapicam is just making a problem more apparent or what. Are you able to do so? Thanks, Josh On 10/16/06, Johan Johansen <[EMAIL PROTECTED]> wrote: I still have the same problem as below, even when running 6.2-BETA2 from a FreeSBIE - cd. I wonder if this could have to do with badly supportet motherboard, ASUS P5B, since I dont see any temp-readings with sysctl. cpuTemp and MBTemp are displayed under bios-config. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: atapicam trouble
I still have the same problem as below, even when running 6.2-BETA2 from a FreeSBIE - cd. I wonder if this could have to do with badly supportet motherboard, ASUS P5B, since I dont see any temp-readings with sysctl. cpuTemp and MBTemp are displayed under bios-config. Another "funny" thing, if I read disk-data with smartmontools, smartctl -a /dev/ad10 [irq19: re0 uhci3++] starts using a hole cpu for itself, and only a reboot helps. mvh > > I run 6.1-STABLE-200607 on my brand new box with > Intel Core 2 Duo E6600 2 x 2,40 GHz cpu (beautiful piece of machinery) > > I can use my dvd-devices with atapicd, but atapicam do not work. > > kldload atapicam causes an interrupt storm, I guess. > I tried to take out atapicd from the kernel after reading > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/73675 > In fact, I removed ataraid atapifd atapist too, without any luck. > > Here is output from top -S a few seconds after kldload atapicam > > last pid: 600; load averages: 0.24, 0.24, 0.11 > up > 0+00:02:36 11:27:53 > 88 processes: 5 running, 64 sleeping, 19 waiting > CPU states: 0.0% user, 0.0% nice, 0.0% system, 43.8% interrupt, 56.2% idle > Mem: 22M Active, 9604K Inact, 28M Wired, 15M Buf, 1943M Free > Swap: 4070M Total, 4070M Free > > PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND >11 root1 171 52 0K 8K RUN1 2:03 99.26% idle: cpu1 >12 root1 171 52 0K 8K RUN0 1:54 62.26% idle: cpu0 >22 root1 -64 -183 0K 8K CPU0 0 0:09 36.41% irq16: > uhci0+ >31 root1 -68 -187 0K 8K WAIT 1 0:01 0.00% irq19: re0 > uhci3++ > > Could anyone point me in a direction too solve this, please? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: atapicam trouble ()
At Sun, 10 Sep 2006 it looks like Josh Carroll composed: > Neither disabling atapicam nor atapicd works on my Core2Duo system. I > don't know whether it's related to the new IDE controllers (JMicron > 363 and Intel ICH8) or a similar problem to what you're reporting. The > best I can do is about 3MB/s with atapicd and DMA disabled and also > with atapicam. Both have problems reading files from a DVD, I end up > getting READ_BIG errors from the kernel. Sure would like to be able to > use this DVD drive in FreeBSD! :) > > Josh > ahh, took a break and using the drive to test a Solaris-10 install, been years since I tried this... had to go find an old Intel nic just to get networking up... I'm a glutten for punishment! Then I forgot to "copy" /etc/nsswitch.dns on top of /etc/nsswitch.conf and for the life of me could not get "OUT" on to the Internet... (giggle) If that atapicam attempt on my part did not blow Xorg out of the water and leave me at 800x600 I'd never be painfully beating myself with Solaris-10 now! Downloaded "pkg-get" so things are bearable! (grin) -- Bill Schoolcraft <<<<*>>>> http://wiliweld.com <*> " If you turn your headlights on while going the speed of light, does anything happen? " ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: atapicam trouble (me too)
Neither disabling atapicam nor atapicd works on my Core2Duo system. I don't know whether it's related to the new IDE controllers (JMicron 363 and Intel ICH8) or a similar problem to what you're reporting. The best I can do is about 3MB/s with atapicd and DMA disabled and also with atapicam. Both have problems reading files from a DVD, I end up getting READ_BIG errors from the kernel. Sure would like to be able to use this DVD drive in FreeBSD! :) Josh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: atapicam trouble (me too)
At Sun, 10 Sep 2006 it looks like Johan Johansen composed: > > I run 6.1-STABLE-200607 on my brand new box with > Intel Core 2 Duo E6600 2 x 2,40 GHz cpu (beautiful piece of machinery) > > I can use my dvd-devices with atapicd, but atapicam do not work. > > kldload atapicam causes an interrupt storm, I guess. > I tried to take out atapicd from the kernel after reading > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/73675 > In fact, I removed ataraid atapifd atapist too, without any luck. > > Here is output from top -S a few seconds after kldload atapicam > > last pid: 600; load averages: 0.24, 0.24, 0.11 > up > 0+00:02:36 11:27:53 > 88 processes: 5 running, 64 sleeping, 19 waiting > CPU states: 0.0% user, 0.0% nice, 0.0% system, 43.8% interrupt, 56.2% idle > Mem: 22M Active, 9604K Inact, 28M Wired, 15M Buf, 1943M Free > Swap: 4070M Total, 4070M Free > > PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND >11 root1 171 52 0K 8K RUN1 2:03 99.26% idle: cpu1 >12 root1 171 52 0K 8K RUN0 1:54 62.26% idle: cpu0 >22 root1 -64 -183 0K 8K CPU0 0 0:09 36.41% irq16: > uhci0+ >31 root1 -68 -187 0K 8K WAIT 1 0:01 0.00% irq19: re0 > uhci3++ > > Could anyone point me in a direction too solve this, please? I was just messing with this with a very good PLEXTOR DVD-RW drive, tried to rebuild the kernel with only "device atapicam" and there was some issues, for some strange reason, the system wedged, then tried to read the drive's contents at boot time, and then I lost my X resolution upon booting back into KDE, I was there with only what amounted to 800x600 (actually something weirder than that) and could NOT restore my X session, tried to reconfigure X -- nada. The machine is triple booted with three different drives, X worked fine on the other variants -- I thought the integrated video_chip went bad, that was not the case, just 6.1 was bad, that was a bittersweet relief. When I did try to start X in the beginning the whole system wedged, could not understand why just adding the "device atapicam" line to a new kernel would do this, something got corrupted. I was getting "perfect" config files with "Xorg -configure" and no matter what, nothing now. Isn't 6.2 coming out soon? > > mvh > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- Bill Schoolcraft <<<<*>>>> http://wiliweld.com <*> " If you turn your headlights on while going the speed of light, does anything happen? " ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
atapicam trouble
I run 6.1-STABLE-200607 on my brand new box with Intel Core 2 Duo E6600 2 x 2,40 GHz cpu (beautiful piece of machinery) I can use my dvd-devices with atapicd, but atapicam do not work. kldload atapicam causes an interrupt storm, I guess. I tried to take out atapicd from the kernel after reading http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/73675 In fact, I removed ataraid atapifd atapist too, without any luck. Here is output from top -S a few seconds after kldload atapicam last pid: 600; load averages: 0.24, 0.24, 0.11up 0+00:02:36 11:27:53 88 processes: 5 running, 64 sleeping, 19 waiting CPU states: 0.0% user, 0.0% nice, 0.0% system, 43.8% interrupt, 56.2% idle Mem: 22M Active, 9604K Inact, 28M Wired, 15M Buf, 1943M Free Swap: 4070M Total, 4070M Free PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND 11 root1 171 52 0K 8K RUN1 2:03 99.26% idle: cpu1 12 root1 171 52 0K 8K RUN0 1:54 62.26% idle: cpu0 22 root1 -64 -183 0K 8K CPU0 0 0:09 36.41% irq16: uhci0+ 31 root1 -68 -187 0K 8K WAIT 1 0:01 0.00% irq19: re0 uhci3++ Could anyone point me in a direction too solve this, please? mvh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ATAPICAM in the FreeBSD manual
Hi. In the FreeBSD manual on '17.6.9 Using the ATAPI/CAM Driver', it only talks about rebuilding the kernel with "device atapicam". I think it should mention that it actually is possible to just add 'atapicam_load="YES"' to /boot/loader.conf. Perhaps I have missed or overlooked something and in that case just ignore my message, but otherwise I think it would improve the manual. I for one just rebuild the kernel the other day just to enable the ATAPI/CAM driver, but had I known it could be loaded from loader.conf, I wouldn't have rebuild it. Best and kind regards, Rico ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATAPICAM
On Tuesday 11 July 2006 14:16, Beni wrote: > On Tuesday 11 July 2006 18:33, Chris Maness wrote: > > How do I load atapicam at boot time. I tried to have it load the same > > way I have the sound modules load, and it doesn't work. After the > > system is up and running I can load just fine. > > Why don't you add "device atapicam" to your kernel and rebuild the kernel ? > It should take care of loading it at boot too. > > Beni. > ___ Or, you could put 'atapicam_load="YES"' in /boot/loader.conf and save the kernel for another time. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATAPICAM
On Tuesday 11 July 2006 18:33, Chris Maness wrote: > How do I load atapicam at boot time. I tried to have it load the same > way I have the sound modules load, and it doesn't work. After the > system is up and running I can load just fine. Why don't you add "device atapicam" to your kernel and rebuild the kernel ? It should take care of loading it at boot too. Beni. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ATAPICAM
How do I load atapicam at boot time. I tried to have it load the same way I have the sound modules load, and it doesn't work. After the system is up and running I can load just fine. Thanks, Chris Maness ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Will adding ATAPICAM confuse my SCSI R/W CDROM?
In the last episode (Mar 24), Oliver Iberien said: > This may be a silly question, but I wanted to make sure: > > I have a SCSI R/W CD-ROM drive and an IDE DVD read-only drive. There > have been times with linux where enabling SCSI emulation made the > actual SCSI drive unavailable to k3b. I just want to make sure that > adding ATAPICAM won't somehow get in the way of the actual SCSI > device. Will it? At worst it may shuffle the device number if the atapi drive gets probed first. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Will adding ATAPICAM confuse my SCSI R/W CDROM?
This may be a silly question, but I wanted to make sure: I have a SCSI R/W CD-ROM drive and an IDE DVD read-only drive. There have been times with linux where enabling SCSI emulation made the actual SCSI drive unavailable to k3b. I just want to make sure that adding ATAPICAM won't somehow get in the way of the actual SCSI device. Will it? Oliver ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: no cd* devices appear in /dev [was Re: device atapicam not enabled in GENERIC kernel for FreeBSD 6.0-RELEASE]
On Monday 06 March 2006 14:11, Duane Whitty wrote: > > On Monday March 6 2006 16:09 > > David J Brooks <[EMAIL PROTECTED]> > >wrote > > > > This reminds me to ask: I have > > ATAPICAM enable in my kernal, > > specifically so that k3b can find my > > dvd+rw ... but no cd* devives appear > > in /dev, and k3b cannot find anything > > no matter where I tell it to look .. > > I must be overlooking something, but > > what? > > Hi, > > look at man 4 atapicam. The examples > section lists the other devices you > need configured in the kernel. > > Hope this helps, > > --Duane Thanks. That and the 'make showinfo' in sysutils/k3b that I somehow missed the first trip 'round have it all working smoothly. -- Sure God created the world in only six days, but He didn't have an established userbase. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: no cd* devices appear in /dev [was Re: device atapicam not enabled in GENERIC kernel for FreeBSD 6.0-RELEASE]
> On Monday March 6 2006 16:09 > David J Brooks <[EMAIL PROTECTED]> >wrote > > This reminds me to ask: I have > ATAPICAM enable in my kernal, > specifically so that k3b can find my > dvd+rw ... but no cd* devives appear > in /dev, and k3b cannot find anything > no matter where I tell it to look .. > I must be overlooking something, but > what? Hi, look at man 4 atapicam. The examples section lists the other devices you need configured in the kernel. Hope this helps, --Duane ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: device atapicam not enabled in GENERIC kernel for FreeBSD 6.0-RELEASE
On Sunday 05 March 2006 22:24, Duane Whitty wrote: > On Sunday 05 March 2006 17:31, Kris > > Kennaway wrote: > > On Sun, Mar 05, 2006 at 05:12:36PM > > -0400, Duane Whitty wrote: > > > On Saturday 04 March 2006 17:30, > > > Kris > > > > > > Kennaway wrote: > > > > On Sat, Mar 04, 2006 at > > > > 05:26:37PM > > > > > > -0400, Duane Whitty wrote: > > > > > Hi, > > > > > > > > > > Just wondering if anyone has > > > > > any information/opinion as to > > > > > why device atapicam is not > > > > > enabled by default in the > > > > > GENERIC kernel. > > > > > > > > It's not an appropriate default, > > > > since it modifies the way the ata > > > > subsystem works in ways the > > > > maintainer does not wish to > > > > support, > > > > > > Sorry, but do you mean the ata > > > subsystem maintainer or the > > > atapicam maintainer? > > > > The former. > > > > > Is atapicam part of the base? > > > > Yes. > > > > > I was > > > under the impression it implements > > > an abstracted SCSI interface over > > > the ata device subsystem but maybe > > > I'm not adequately understanding > > > what's really happening. > > > > As the name suggests, it provides a > > CAM front-end to the devices, which > > is the same front-end used by the > > SCSI devices, so tools that expect to > > use CAM can work on the ATA devices > > too. > > Ah, ok -- CAM -- common access method. > I'm getting this > > > > Just an observation but it seems as > > > though there is a great deal of use > > > being made of the atapicam > > > subsystem. I noticed for instance > > > that in addition to /dev/cd0 that > > > /dev/pass0 and /dev/da0 also did > > > not show up until I rebuilt with > > > atapicam or did I just miss them? > > > > The equivalent devices have different > > names under atapicam than ata, but > > why do you think they are necessary? > > because I misunderstood what umass > needed and I inappropriately > generalized on the basis of one port > (k3b) > > > > Unless I'm wrong doesn't this mean > > > that usb drives and those types of > > > devices need the atapicam > > > subsystem? > > > > I suspect you're wrong. > > > > Kris > > Hi, > > Thanks Kris. Your suspicions were > correct. I was wrong. I re-read the > man pages for da, pass, and umass, and > nowhere did it say I needed atapicam. > So thanks for pointing me in the right > direction. > > I rebooted with the GENERIC kernel, > plugged in my usb memory device, and > everything worked great. > > The k3b port required this and I suppose > I generalized when I should not have. > > Again, much thanks. > > --Duane > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" This reminds me to ask: I have ATAPICAM enable in my kernal, specifically so that k3b can find my dvd+rw ... but no cd* devives appear in /dev, and k3b cannot find anything no matter where I tell it to look .. I must be overlooking something, but what? -- Sure God created the world in only six days, but He didn't have an established userbase. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: device atapicam not enabled in GENERIC kernel for FreeBSD 6.0-RELEASE
On Sunday 05 March 2006 17:31, Kris Kennaway wrote: > On Sun, Mar 05, 2006 at 05:12:36PM -0400, Duane Whitty wrote: > > On Saturday 04 March 2006 17:30, > > Kris > > > > Kennaway wrote: > > > On Sat, Mar 04, 2006 at > > > 05:26:37PM > > > > -0400, Duane Whitty wrote: > > > > Hi, > > > > > > > > Just wondering if anyone has > > > > any information/opinion as to > > > > why device atapicam is not > > > > enabled by default in the > > > > GENERIC kernel. > > > > > > It's not an appropriate default, > > > since it modifies the way the ata > > > subsystem works in ways the > > > maintainer does not wish to > > > support, > > > > Sorry, but do you mean the ata > > subsystem maintainer or the > > atapicam maintainer? > > The former. > > > Is atapicam part of the base? > > Yes. > > > I was > > under the impression it implements > > an abstracted SCSI interface over > > the ata device subsystem but maybe > > I'm not adequately understanding > > what's really happening. > > As the name suggests, it provides a > CAM front-end to the devices, which > is the same front-end used by the > SCSI devices, so tools that expect to > use CAM can work on the ATA devices > too. > Ah, ok -- CAM -- common access method. I'm getting this > > Just an observation but it seems as > > though there is a great deal of use > > being made of the atapicam > > subsystem. I noticed for instance > > that in addition to /dev/cd0 that > > /dev/pass0 and /dev/da0 also did > > not show up until I rebuilt with > > atapicam or did I just miss them? > > The equivalent devices have different > names under atapicam than ata, but > why do you think they are necessary? > because I misunderstood what umass needed and I inappropriately generalized on the basis of one port (k3b) > > Unless I'm wrong doesn't this mean > > that usb drives and those types of > > devices need the atapicam > > subsystem? > > I suspect you're wrong. > > Kris > Hi, Thanks Kris. Your suspicions were correct. I was wrong. I re-read the man pages for da, pass, and umass, and nowhere did it say I needed atapicam. So thanks for pointing me in the right direction. I rebooted with the GENERIC kernel, plugged in my usb memory device, and everything worked great. The k3b port required this and I suppose I generalized when I should not have. Again, much thanks. --Duane ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: device atapicam not enabled in GENERIC kernel for FreeBSD 6.0-RELEASE
On Sun, Mar 05, 2006 at 05:12:36PM -0400, Duane Whitty wrote: > On Saturday 04 March 2006 17:30, Kris > Kennaway wrote: > > On Sat, Mar 04, 2006 at 05:26:37PM > -0400, Duane Whitty wrote: > > > Hi, > > > > > > Just wondering if anyone has any > > > information/opinion as to why > > > device atapicam is not enabled by > > > default in the GENERIC kernel. > > > > It's not an appropriate default, > > since it modifies the way the ata > > subsystem works in ways the > > maintainer does not wish to support, > > Sorry, but do you mean the ata subsystem > maintainer or the atapicam maintainer? The former. > Is atapicam part of the base? Yes. > I was > under the impression it implements an > abstracted SCSI interface over the ata > device subsystem but maybe I'm not > adequately understanding what's really > happening. As the name suggests, it provides a CAM front-end to the devices, which is the same front-end used by the SCSI devices, so tools that expect to use CAM can work on the ATA devices too. > Just an observation but it seems as > though there is a great deal of use > being made of the atapicam subsystem. > I noticed for instance that in addition > to /dev/cd0 that /dev/pass0 > and /dev/da0 also did not show up until > I rebuilt with atapicam or did I just > miss them? The equivalent devices have different names under atapicam than ata, but why do you think they are necessary? > Unless I'm wrong doesn't this mean that > usb drives and those types of devices > need the atapicam subsystem? I suspect you're wrong. Kris pgpZSkTkMS5Zd.pgp Description: PGP signature
Re: device atapicam not enabled in GENERIC kernel for FreeBSD 6.0-RELEASE
On Saturday 04 March 2006 17:30, Kris Kennaway wrote: > On Sat, Mar 04, 2006 at 05:26:37PM -0400, Duane Whitty wrote: > > Hi, > > > > Just wondering if anyone has any > > information/opinion as to why > > device atapicam is not enabled by > > default in the GENERIC kernel. > > It's not an appropriate default, > since it modifies the way the ata > subsystem works in ways the > maintainer does not wish to support, Sorry, but do you mean the ata subsystem maintainer or the atapicam maintainer? > and often contains bugs. > > Kris Hi, Thanks Kris. Is atapicam part of the base? I was under the impression it implements an abstracted SCSI interface over the ata device subsystem but maybe I'm not adequately understanding what's really happening. Just an observation but it seems as though there is a great deal of use being made of the atapicam subsystem. I noticed for instance that in addition to /dev/cd0 that /dev/pass0 and /dev/da0 also did not show up until I rebuilt with atapicam or did I just miss them? Unless I'm wrong doesn't this mean that usb drives and those types of devices need the atapicam subsystem? Thanks for your patience and help. Best regards, --Duane ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: device atapicam not enabled in GENERIC kernel for FreeBSD 6.0-RELEASE
On Sat, Mar 04, 2006 at 05:26:37PM -0400, Duane Whitty wrote: > Hi, > > Just wondering if anyone has any > information/opinion as to why > device atapicam is not enabled by > default in the GENERIC kernel. It's not an appropriate default, since it modifies the way the ata subsystem works in ways the maintainer does not wish to support, and often contains bugs. Kris pgpKb3qUkLkmg.pgp Description: PGP signature
device atapicam not enabled in GENERIC kernel for FreeBSD 6.0-RELEASE
Hi, Just wondering if anyone has any information/opinion as to why device atapicam is not enabled by default in the GENERIC kernel. Does this apply to releases other than 6? Thanks in advance, --Duane ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATAPICAM?
Vulpes Velox wrote: On Thu, 23 Feb 2006 22:06:22 -0800 Chris Maness <[EMAIL PROTECTED]> wrote: How do I load atapicam at boot time? I can load it with no problems after the system has started, but I if I ad the line atapicam_load="YES" in /*boot*/loader.conf, the kernel turns to fried chicken at boot time. Is there a secrete recipe ;o) to get this to work correctly. I have found there are some chipsets atapicam does not like. Not tried it recently, but I have seen similar problems with a Promise PDC20268 card under a old relen_5. Thanks for the reply. After investigation I think it was loading the sound modules at boot time that actually causes intermittent problems. Is there a way to automatically load all of the kernel modules at the end of the boot sequence. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATAPICAM?
On Thu, 23 Feb 2006 22:06:22 -0800 Chris Maness <[EMAIL PROTECTED]> wrote: > How do I load atapicam at boot time? I can load it with no > problems after the system has started, but I if I ad the line > atapicam_load="YES" in /*boot*/loader.conf, the kernel turns to > fried chicken at boot time. Is there a secrete recipe ;o) to get > this to work correctly. I have found there are some chipsets atapicam does not like. Not tried it recently, but I have seen similar problems with a Promise PDC20268 card under a old relen_5. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATAPICAM?
Kris Kennaway wrote: On Fri, Feb 24, 2006 at 06:49:34AM -0800, Chris Maness wrote: Kris Kennaway wrote: On Thu, Feb 23, 2006 at 10:06:22PM -0800, Chris Maness wrote: How do I load atapicam at boot time? I can load it with no problems after the system has started, but I if I ad the line atapicam_load="YES" in /*boot*/loader.conf, the kernel turns to fried chicken at boot time. "Fried chicken" isn't a technical term I'm familiar with ;-) Kris And the kernel himself holding the heart of the FreeBSD operating system. You can either make funny jokes or you can describe your problem better so that someone can help you :-) Kris OK, seriously, when I added the module at boot time through the fore mentioned method the system hung just after it detected the ata hard drives. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATAPICAM?
> Date: Fri, 24 Feb 2006 01:18:21 -0500 > From: Kris Kennaway <[EMAIL PROTECTED]> > Subject: Re: ATAPICAM? > To: Chris Maness <[EMAIL PROTECTED]> > Cc: freebsd-questions@freebsd.org > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="us-ascii" > > On Thu, Feb 23, 2006 at 10:06:22PM -0800, Chris Maness wrote: > > How do I load atapicam at boot time? I can load it with no problems > > after the system has started, but I if I ad the line atapicam_load="YES" > > in /*boot*/loader.conf, the kernel turns to fried chicken at boot time. > > "Fried chicken" isn't a technical term I'm familiar with ;-) > > Kris man kfc (... or was that MFC?) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATAPICAM?
On Thu, Feb 23, 2006 at 10:06:22PM -0800, Chris Maness wrote: > How do I load atapicam at boot time? I can load it with no problems > after the system has started, but I if I ad the line atapicam_load="YES" > in /*boot*/loader.conf, the kernel turns to fried chicken at boot time. "Fried chicken" isn't a technical term I'm familiar with ;-) Kris pgpLPrPCfP3l6.pgp Description: PGP signature
ATAPICAM?
How do I load atapicam at boot time? I can load it with no problems after the system has started, but I if I ad the line atapicam_load="YES" in /*boot*/loader.conf, the kernel turns to fried chicken at boot time. Is there a secrete recipe ;o) to get this to work correctly. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: AtapiCam not recognizing philips cd burner
Jason Cox <[EMAIL PROTECTED]> writes: > Whilew trying to get CD burning working under FreeBSD 6.0 (and > 6.1-PreRelease), I keep getting the following error in my dmesg and cd1 > is never created. The drive is a Philips CDRW4012P. It shows up > as /dev/acd1 and reports correctly in dmesg. However, once atapicam > tries to query it, it just repeats the follwoing (output from dmesg with > boot -v): Start with some more basic information, like how it is recognized at boot, and whether it works *without* ATAPICAM. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
AtapiCam not recognizing philips cd burner
Hello all, Whilew trying to get CD burning working under FreeBSD 6.0 (and 6.1-PreRelease), I keep getting the following error in my dmesg and cd1 is never created. The drive is a Philips CDRW4012P. It shows up as /dev/acd1 and reports correctly in dmesg. However, once atapicam tries to query it, it just repeats the follwoing (output from dmesg with boot -v): ata1: reiniting channel .. ata1: reset tp1 mask=03 ostat0=50 ostat1=00 ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: reset tp2 stat0=00 stat1=00 devices=0xc acd0: setting PIO4 on ICH5 chip acd0: setting UDMA33 on ICH5 chip acd1: setting PIO4 on ICH5 chip acd1: setting UDMA33 on ICH5 chip ata1: reinit done .. (probe8:ata1:0:1:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe8:ata1:0:1:0): CAM Status: SCSI Status Error (probe8:ata1:0:1:0): SCSI Status: Check Condition (probe8:ata1:0:1:0): ILLEGAL REQUEST asc:20,0 (probe8:ata1:0:1:0): Invalid command operation code (probe8:ata1:0:1:0): (probe8:ata1:0:1:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe8:ata1:0:1:0): ILLEGAL REQUEST asc:20,0 (probe8:ata1:0:1:0): Invalid command operation code Unretryable error (probe8:ata1:0:1:0): error 22 (probe8:ata1:0:1:0): Unretryable Error I have looked all over the internet and everywhere says it should have been fixed in 4.7. Any advice on what else to try? Jason ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
AtapiCam Failing on CD Burner
Hello all, Whilew trying to get CD burning working under FreeBSD 6.0 (and 6.1-PreRelease), I keep getting the following error in my dmesg and cd1 is never created. The drive is a Philips CDRW4012P. It shows up as /dev/acd1 and reports correctly in dmesg. However, once atapicam tries to query it, it just repeats the follwoing (output from dmesg with boot -v): ata1: reiniting channel .. ata1: reset tp1 mask=03 ostat0=50 ostat1=00 ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: reset tp2 stat0=00 stat1=00 devices=0xc acd0: setting PIO4 on ICH5 chip acd0: setting UDMA33 on ICH5 chip acd1: setting PIO4 on ICH5 chip acd1: setting UDMA33 on ICH5 chip ata1: reinit done .. (probe8:ata1:0:1:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe8:ata1:0:1:0): CAM Status: SCSI Status Error (probe8:ata1:0:1:0): SCSI Status: Check Condition (probe8:ata1:0:1:0): ILLEGAL REQUEST asc:20,0 (probe8:ata1:0:1:0): Invalid command operation code (probe8:ata1:0:1:0): (probe8:ata1:0:1:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe8:ata1:0:1:0): ILLEGAL REQUEST asc:20,0 (probe8:ata1:0:1:0): Invalid command operation code Unretryable error (probe8:ata1:0:1:0): error 22 (probe8:ata1:0:1:0): Unretryable Error I have looked all over the internet and everywhere says it should have been fixed in 4.7. Any advice on what else to try? Jason ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: atapicam load question
On Saturday 21 January 2006 14:26, Fabian Keil wrote: > dick hoogendijk <[EMAIL PROTECTED]> wrote: > > When I "kldload atapicam" the permissions in /etc/devfs.conf for cd0 > > are _not_ honored. (I want cd0 to have 0666) > > When I put atapicam_load="YES" in /boot/loader.conf the permissions > > are set the way I want them. > > > > I would like to make the choice for atapicam later if posssible, so my > > question is: why are the permissions not honored by devfs.conf when it > > creates a /dev/cd0 device after a "kldload" ? > > /etc/devfs.conf is for boot-time configuration only. Not true, you just need to restart devfs. > What you're looking for is /etc/devfs.rules. > > Fabian Dan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: atapicam load question
dick hoogendijk <[EMAIL PROTECTED]> wrote: > When I "kldload atapicam" the permissions in /etc/devfs.conf for cd0 > are _not_ honored. (I want cd0 to have 0666) > When I put atapicam_load="YES" in /boot/loader.conf the permissions > are set the way I want them. > > I would like to make the choice for atapicam later if posssible, so my > question is: why are the permissions not honored by devfs.conf when it > creates a /dev/cd0 device after a "kldload" ? /etc/devfs.conf is for boot-time configuration only. What you're looking for is /etc/devfs.rules. Fabian -- http://www.fabiankeil.de/ signature.asc Description: PGP signature
atapicam load question
Hi, When I "kldload atapicam" the permissions in /etc/devfs.conf for cd0 are _not_ honored. (I want cd0 to have 0666) When I put atapicam_load="YES" in /boot/loader.conf the permissions are set the way I want them. I would like to make the choice for atapicam later if posssible, so my question is: why are the permissions not honored by devfs.conf when it creates a /dev/cd0 device after a "kldload" ? -- dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 6.0 ++ The Power to Serve ___ 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: > ad0: 43979MB > [89355/16/63] > at ata0-master PIO4 > acd0: CDROM 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: 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]"
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: ad0: 43979MB [89355/16/63] at ata0-master PIO4 acd0: CDROM 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)
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 [170197/15/63] at ata2-master UDMA100 * Plextor CDROM drives + CDRW at ata3-master UDMA33 + DVDROM 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 Confi
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]"
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]"
5.3 and atapicam....
Greetings, I seem to have made a small amount of progress with my atapicam boggle. I was able to get a kernel with the atapicam driver configured to boot by taking the drive off of the 2nd channel of my PDC20269-based atapter and configure it as a slave on the 2nd channel of my motherboard's embedded controller. I was even able to 'rip' a disk using cdda2wav. I attempted to rip a 2nd one but it failed with an I/O error. A dmesg reveals... cd9660: RockRidge Extension acd0: WARNING - READ_CD read data overrun 61152>2352 cd9660: RockRidge Extension acd0: timeout waiting for ATAPI ready acd0: timeout waiting for ATAPI ready acd0: timeout waiting for ATAPI ready acd0: timeout waiting for ATAPI ready acd0: READ_BIG trying to write on read buffer acd0: WARNING - removed from configuration (cd1:ata1:0:0:0): cddone: got error 0x16 back (cd1:ata1:0:0:0): lost device (probe0:ata1:0:0:0): Lost target 0??? vm_fault: pager read error, pid 988 (cp) vm_fault: pager read error, pid 988 (cp) vm_fault: pager read error, pid 997 (cp) vm_fault: pager read error, pid 997 (cp) . . . . . vm_fault: pager read error, pid 997 (cp) vm_fault: pager read error, pid 997 (cp) vm_fault: pager read error, pid 997 (cp) vm_fault: pager read error, pid 997 (cp) vm_fault: pager read error, pid 997 (cp) vm_fault: pager read error, pid 997 (cp) (cd1:ata1:0:0:0): removing device entry I don't seem to be able to bring the device back online with any combination of args with either atacontrol or camcontrol. I also find it strange that I could not access the drive with it attached to the motherboard's PRIMARY controller port. I'm beginning to think this may be some sort of funky I/O conflict or something. Going down for a reboot -- 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 interrupt storm (atapicam) and I/O error
Daniel I wonder if you can mount a CD with a GENERIC kernel? I also wonder if you can avoid the "interrupt storm" with your custom kernel but by disabling atapi dma? (hw.ata.atapi_dma="0" in /boot/loader.conf) If this kernel boots, can you mount a CD? If you get some free time and feel like messing around with it, I'd be curious what you find. Regards -- Randall D. DuCharme (Radio AD5GB) Powered by FreeBSD! The Power to Serve --- On Fri 01/28, Daniel S. Haischt < [EMAIL PROTECTED] > wrote: From: Daniel S. Haischt [mailto: [EMAIL PROTECTED] To: Cc: freebsd-questions@freebsd.org Date: Fri, 28 Jan 2005 14:38:14 +0100 Subject: Re: 5.3 interrupt storm (atapicam) and I/O error oops, did forget the tixt file ...Daniel S. Haischt schrieb:> I don't know whether this is related to your issue,> but on one of my boxes I am also getting an interrupt> storm with atapicam enabled.> > On FreeBSD 5.2.1 I did not experience any interrupt> storm issues, even if using the same hardware configuration.> > Have a look at the attached text file for a detailed> description ...> > Olivier Certner schrieb:> >> Hi,>>>> Could you give a look at my post dated 04/01/2005 entitled "Freeze >> with CAM (using KsCD)"? Maybe we have fallen on the same kind of bug >> concerning atapicam.>>>> If you have KDE, maybe you should try to reproduce the problem I had. >> I've no time to test your scenario (the one with the EIDE drive, I >> don't have SCSI) now, but I'll try to reproduce it at the beginning of >> next week, in order to see if the freeze happens also on my computer.>>>> Hope this will help us to progress on our issues.>>>> >>> Regards,>>>> Olivier>> >>> ___>> >>> freebsd-questions@freebsd.org mailing list>> >>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions>> To >>> unsubscribe, send any mail to >> "[EMAIL PROTECTED]"> > >>> -- Mit freundlichen Gruessen / With kind regardsDAn.I.El >>> S. HaischtWant a complete signature??? Type at a shell >>> prompt:$ > finger -l [EMAIL PROTECTED]Hello,recently I >>> updated one of my FreeBSD boxes tov 5.3. This box got a builtin >>> Promise PDC20269UDMA133 controller. Actually it's a controllerwith >>> two IDE channels.So far if using the GENERIC kernel that >>> comeswith FreeBSD, I do not experience any problems.If using >>> my own customized kernel I am gettingthe following error message while >>> booting thesystem:8< 8<8<---8<-8<-Interrupt storm detected on "irq10: atapci1";throtteling interrupt source:>8>8>8--->8->8-After some trail-and-error based investigations,I did figure out that if I don't plugin any deviceinto IDE channel two, the just described errordoes not occur.So it has something to do with IDE channel two.As an additional note - The controller worksunder Linux, FreeBSD 5.3 (GENERIC) and FreeBSD5.2.1 (custom kernel).Any hints on how to solve this issue would begreatly appreciated. ___freebsd-questions@freebsd.org mailing listhttp://lists.freebsd.org/mailman/listinfo/freebsd-questionsTo unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ 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 interrupt storm (atapicam) and I/O error
Hello, attached you will find a copy of my custom kernel config which did work without any issue under FreeBSD 5.2.1. As outlined earlier if using this config on FreeBSD 5.3-RELEASE I am getting an interrupt storm while booting the system. The following hardware configuration *won't* cause an interrupt storm on FreeBSD 5.3 if using the Promise PDC20269 controller: * harddrive attached to IDE channel #1 * no device attached to channel #2 The following hardware configuration *will* cause an interrupt storm on FreeBSD 5.3 if using the Promise PDC20269 controller: Config #1: * harddrive attached to IDE channel #1 * CDROM or CDRW attached to channel #2 Config #2: * CDROM or CDRW attached to channel #1 * harddrive attached to IDE channel #2 Jason Henson schrieb: On 01/28/05 08:38:14, Daniel S. Haischt wrote: oops, did forget the tixt file ... Daniel S. Haischt schrieb: I don't know whether this is related to your issue, but on one of my boxes I am also getting an interrupt storm with atapicam enabled. On FreeBSD 5.2.1 I did not experience any interrupt storm issues, even if using the same hardware configuration. Have a look at the attached text file for a detailed description ... Olivier Certner schrieb: Hi, Could you give a look at my post dated 04/01/2005 entitled "Freeze with CAM (using KsCD)"? Maybe we have fallen on the same kind of bug concerning atapicam. If you have KDE, maybe you should try to reproduce the problem I had. I've no time to test your scenario (the one with the EIDE drive, I don't have SCSI) now, but I'll try to reproduce it at the beginning of next week, in order to see if the freeze happens also on my computer. Hope this will help us to progress on our issues. Regards, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions- [EMAIL PROTECTED]" -- Mit freundlichen Gruessen / With kind regards DAn.I.El S. Haischt Want a complete signature??? Type at a shell prompt: $ > finger -l [EMAIL PROTECTED] Hello, recently I updated one of my FreeBSD boxes to v 5.3. This box got a builtin Promise PDC20269 UDMA133 controller. Actually it's a controller with two IDE channels. So far if using the GENERIC kernel that comes with FreeBSD, I do not experience any problems. If using my own customized kernel I am getting the following error message while booting the system: 8<8<8<---8<-8<- Interrupt storm detected on "irq10: atapci1"; throtteling interrupt source: >8>8>8--->8->8- After some trail-and-error based investigations, I did figure out that if I don't plugin any device into IDE channel two, the just described error does not occur. So it has something to do with IDE channel two. As an additional note - The controller works under Linux, FreeBSD 5.3 (GENERIC) and FreeBSD 5.2.1 (custom kernel). Any hints on how to solve this issue would be greatly appreciated. How about a copy of your custom changes to the kernel? Also did you get a response from Søren Schmidt <[EMAIL PROTECTED]>, he wrote and maintains the ata stuff iirc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Mit freundlichen Gruessen / With kind regards DAn.I.El S. Haischt Want a complete signature??? Type at a shell prompt: $ > finger -l [EMAIL PROTECTED] # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.369.2.2 2002/12/31 05:35:45 scottl Exp $ machine i386 #cpuI486_CPU cpu I586_CPU #cpuI686_CPU ident ABYSSONE maxusers512 #To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" #Default places to look for devices. #makeoptionsDEBUG=-g#Build kernel with gdb(1) debug symbols options INET#InterNETworking options INET6
Re: 5.3 interrupt storm (atapicam) and I/O error
On Saturday 29 January 2005 05:30, ad5gb wrote: > Greetings, > > Not sure what to think about this yet but it definitely has something to do > with having my ATAPI CD connected to the 2nd channel of my Promise Ultra > 133 TX2 adapter (PDC20269). If I disconnect the cable from channel 2 the > kernel will boot with atapicam enabled. I don't seem to be able to use my > motherboard's embedded EIDE controller with the Promise adapter installed. > I don't see any obvious I/O or interrupt conflicts, but I also don't have > too much control over it with this old SuperMicro mainboard. > > Seems odd to me though, since this all worked on 5.2.1. Open for > suggestions, but for now I'm going to try to track down the SCSI I/O error > problem so I can get some CD burning done (critical system backups) and > then I'll see if I can try to figure out if this is an EIDE driver issue or > a atapicam issue. > > If anyone comes up with anything in the meantime... please YELL! > > > Kind regards > > -- > Randall D. DuCharme (Radio AD5GB) > > Powered by FreeBSD! > The Power to Serve > > > > --- On Fri 01/28, Daniel S. Haischt < [EMAIL PROTECTED] > > wrote: From: Daniel S. Haischt [mailto: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Cc: freebsd-questions@freebsd.org > Date: Fri, 28 Jan 2005 14:37:21 +0100 > Subject: Re: 5.3 interrupt storm (atapicam) and I/O error > > I don't know whether this is related to your issue,but on one of my > boxes I am also getting an interruptstorm with atapicam > enabled.On FreeBSD 5.2.1 I did not experience any > interruptstorm issues, even if using the same hardware > configuration.Have a look at the attached text file for a > detaileddescription ...Olivier Certner schrieb:> Hi,> > > Could you give a look at my post dated 04/01/2005 entitled "Freeze > with CAM > (using KsCD)"? Maybe we have fallen on the same kind of bug > concerning > atapicam.> > If you have KDE, maybe you should > try to reproduce the problem I had. I've no > time to test your > scenario (the one with the EIDE drive, I don't have SCSI) > now, but > I'll try to reproduce it at the beginning of next week, in order to > > see if the freeze happens also on my computer.> > Hope this will > help us to progress on our issues.> > Regards,> > > Olivier> ___ > I am also having a shitload of problems on my newly installed 5.3 box (which was a happy camper under 4.x. I have a promise tx2 100 board. there are a pair of disks with a geom stripe over them, Under heavy i/o the system either freezes or crashes. I will have some time later next week to investigate but I am really inclined to use the time to revert to 4.11. ___ 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 interrupt storm (atapicam) and I/O error
Here's a quick 'diff' of the kernel configs. This might be ugly so if you want it in a different format, just let me know. Note that my 'production' kernel is an SMP kernel which 'includes' my 'base' kernel file. It simply consists of... include ARABIAN options SMP options PREEMPTION Haven't heard from Soren (yet) Many thanks! --- GENERIC Sun Oct 24 18:02:52 2004 +++ ARABIAN Sat Jan 29 23:06:56 2005 @@ -19,10 +19,8 @@ # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.413.2.6.2.2 2004/10/24 18:02:52 scottl Exp $ machinei386 -cpuI486_CPU -cpuI586_CPU cpuI686_CPU -ident GENERIC +ident ARABIAN # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. @@ -45,8 +43,8 @@ optionsGEOM_GPT# GUID Partition Tables. optionsCOMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] optionsCOMPAT_FREEBSD4 # Compatible with FreeBSD4 -optionsSCSI_DELAY=15000# Delay (in ms) before probing SCSI -optionsKTRACE # ktrace(1) support +optionsSCSI_DELAY=5000 # Delay (in ms) before probing SCSI +#options KTRACE # ktrace(1) support optionsSYSVSHM # SYSV-style shared memory optionsSYSVMSG # SYSV-style message queues optionsSYSVSEM # SYSV-style semaphores @@ -56,13 +54,25 @@ # output. Adds ~128k to driver. optionsAHD_REG_PRETTY_PRINT# Print register bitfields in debug # output. Adds ~215k to driver. + +optionsAHC_ALLOW_MEMIO # Allow PCI mem mapped I/O. + + optionsADAPTIVE_GIANT # Giant mutex is adaptive. device apic# I/O APIC +# Firewall support. +options IPFIREWALL +options IPFIREWALL_VERBOSE +options IPFIREWALL_VERBOSE_LIMIT=100 +options IPDIVERT +#optionsIPSTEALTH +#optionsTCP_DROP_SYNFIN + # Bus support. Do not remove isa, even if you have no isa slots device isa -device eisa +#deviceeisa device pci # Floppy drives @@ -71,32 +81,35 @@ # ATA and ATAPI devices device ata device atadisk # ATA disk drives -device ataraid # ATA RAID drives +#deviceataraid # ATA RAID drives device atapicd # ATAPI CDROM drives -device atapifd # ATAPI floppy drives -device atapist # ATAPI tape drives +#deviceatapifd # ATAPI floppy drives +#deviceatapist # ATAPI tape drives optionsATA_STATIC_ID # Static device numbering +# FOR CDRECORD to work with ATAPI device. +device atapicam # This might be the booger! + # SCSI Controllers -device ahb # EISA AHA1742 family +#deviceahb # EISA AHA1742 family device ahc # AHA2940 and onboard AIC7xxx devices -device ahd # AHA39320/29320 and onboard AIC79xx devices -device amd # AMD 53C974 (Tekram DC-390(T)) -device isp # Qlogic family -device mpt # LSI-Logic MPT-Fusion +#deviceahd # AHA39320/29320 and onboard AIC79xx devices +#deviceamd # AMD 53C974 (Tekram DC-390(T)) +#deviceisp # Qlogic family +#devicempt # LSI-Logic MPT-Fusion #devicencr # NCR/Symbios Logic device sym # NCR/Symbios Logic (newer chipsets + those of `ncr') device trm # Tekram DC395U/UW/F DC315U adapters -device adv # Advansys SCSI adapters -device adw # Advansys wide SCSI adapters -device aha # Adaptec 154x SCSI adapters -device aic # Adaptec 15[012]x SCSI adapters, AIC-6[23]60. -device bt # Buslogic/Mylex MultiMaster SCSI adapters - -device ncv # NCR 53C500 -device nsp # Workbit Ninja SCSI-3 -device stg # TMC 18C30/18C50 +#deviceadv # Advansys SCSI adapters +#deviceadw # Advansys wide SCSI adapters +#deviceaha # Adaptec 154x SCSI adapters +#deviceaic # Adaptec 15[012]x SCSI adapters, AIC-6[23]60. +#devicebt # Buslogic/Mylex MultiMaster SCSI adapters + +#devicencv # NCR 53C500 +#devicen
Re: 5.3 interrupt storm (atapicam) and I/O error
On 01/28/05 08:38:14, Daniel S. Haischt wrote: oops, did forget the tixt file ... Daniel S. Haischt schrieb: I don't know whether this is related to your issue, but on one of my boxes I am also getting an interrupt storm with atapicam enabled. On FreeBSD 5.2.1 I did not experience any interrupt storm issues, even if using the same hardware configuration. Have a look at the attached text file for a detailed description ... Olivier Certner schrieb: Hi, Could you give a look at my post dated 04/01/2005 entitled "Freeze with CAM (using KsCD)"? Maybe we have fallen on the same kind of bug concerning atapicam. If you have KDE, maybe you should try to reproduce the problem I had. I've no time to test your scenario (the one with the EIDE drive, I don't have SCSI) now, but I'll try to reproduce it at the beginning of next week, in order to see if the freeze happens also on my computer. Hope this will help us to progress on our issues. Regards, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions- [EMAIL PROTECTED]" -- Mit freundlichen Gruessen / With kind regards DAn.I.El S. Haischt Want a complete signature??? Type at a shell prompt: $ > finger -l [EMAIL PROTECTED] Hello, recently I updated one of my FreeBSD boxes to v 5.3. This box got a builtin Promise PDC20269 UDMA133 controller. Actually it's a controller with two IDE channels. So far if using the GENERIC kernel that comes with FreeBSD, I do not experience any problems. If using my own customized kernel I am getting the following error message while booting the system: 8<8<8<---8<-8<- Interrupt storm detected on "irq10: atapci1"; throtteling interrupt source: >8>8>8--->8->8- After some trail-and-error based investigations, I did figure out that if I don't plugin any device into IDE channel two, the just described error does not occur. So it has something to do with IDE channel two. As an additional note - The controller works under Linux, FreeBSD 5.3 (GENERIC) and FreeBSD 5.2.1 (custom kernel). Any hints on how to solve this issue would be greatly appreciated. How about a copy of your custom changes to the kernel? Also did you get a response from Søren Schmidt <[EMAIL PROTECTED]>, he wrote and maintains the ata stuff iirc. ___ 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 interrupt storm (atapicam)
Greetings, I seem to have made a little progress with the atapicam driver. It seems if I force PIO mode (hw.ata.atapi_dma="0" in /boot/loader.conf) a kernel with the atapicam device will boot. I still cannot access a disk in the drive however either via the acdx device or the new cdx device provided by the atapicam driver. Perhaps you could try adding that line in your /boot/loader.conf and see if it cures your problem -- Randall D. DuCharme (Radio AD5GB) Powered by FreeBSD! The Power to Serve --- On Fri 01/28, Olivier Certner < [EMAIL PROTECTED] > wrote: From: Olivier Certner [mailto: [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Date: Fri, 28 Jan 2005 10:05:30 +0100 Subject: Re: 5.3 interrupt storm (atapicam) and I/O error Hi, Could you give a look at my post dated 04/01/2005 entitled "Freeze with CAM (using KsCD)"? Maybe we have fallen on the same kind of bug concerning atapicam. If you have KDE, maybe you should try to reproduce the problem I had. I've no time to test your scenario (the one with the EIDE drive, I don't have SCSI) now, but I'll try to reproduce it at the beginning of next week, in order to see if the freeze happens also on my computer. Hope this will help us to progress on our issues. Regards, Olivier___freebsd-questions@freebsd.org mailing listhttp://lists.freebsd.org/mailman/listinfo/freebsd-questionsTo unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ 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 interrupt storm (atapicam) and I/O error
Greetings, Not sure what to think about this yet but it definitely has something to do with having my ATAPI CD connected to the 2nd channel of my Promise Ultra 133 TX2 adapter (PDC20269). If I disconnect the cable from channel 2 the kernel will boot with atapicam enabled. I don't seem to be able to use my motherboard's embedded EIDE controller with the Promise adapter installed. I don't see any obvious I/O or interrupt conflicts, but I also don't have too much control over it with this old SuperMicro mainboard. Seems odd to me though, since this all worked on 5.2.1. Open for suggestions, but for now I'm going to try to track down the SCSI I/O error problem so I can get some CD burning done (critical system backups) and then I'll see if I can try to figure out if this is an EIDE driver issue or a atapicam issue. If anyone comes up with anything in the meantime... please YELL! Kind regards -- Randall D. DuCharme (Radio AD5GB) Powered by FreeBSD! The Power to Serve --- On Fri 01/28, Daniel S. Haischt < [EMAIL PROTECTED] > wrote: From: Daniel S. Haischt [mailto: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Date: Fri, 28 Jan 2005 14:37:21 +0100 Subject: Re: 5.3 interrupt storm (atapicam) and I/O error I don't know whether this is related to your issue,but on one of my boxes I am also getting an interruptstorm with atapicam enabled.On FreeBSD 5.2.1 I did not experience any interruptstorm issues, even if using the same hardware configuration.Have a look at the attached text file for a detaileddescription ...Olivier Certner schrieb:> Hi,> > Could you give a look at my post dated 04/01/2005 entitled "Freeze with CAM > (using KsCD)"? Maybe we have fallen on the same kind of bug concerning > atapicam.> > If you have KDE, maybe you should try to reproduce the problem I had. I've no > time to test your scenario (the one with the EIDE drive, I don't have SCSI) > now, but I'll try to reproduce it at the beginning of next week, in order to > see if the freeze happens also on my computer.> > Hope this will help us to progress on our issues.> > Regards,> > Olivier> ___ > freebsd-questions@freebsd.org mailing list> http://lists.freebsd.org/mailman/listinfo/freebsd-questions> To unsubscribe, send any mail to "[EMAIL PROTECTED]"-- Mit freundlichen Gruessen / With kind regardsDAn.I.El S. HaischtWant a complete signature??? Type at a shell prompt:$ > finger -l [EMAIL PROTECTED]___freebsd-questions@freebsd.org mailing listhttp://lists.freebsd.org/mailman/listinfo/freebsd-questionsTo unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ 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 interrupt storm (atapicam) and I/O error
Greetings, My problem might be slightly different than yours. My system hangs during the boot process whenever I boot a kernel with atapicam enabled. A can't do anything but reboot the box at that point. Maybe this is a good time to learn to use the kernel debugger. When I get home this evening I'll try a few more things. This problem didn't happen in 5.2.1. Thanks! -- Randall D. DuCharme (Radio AD5GB) Powered by FreeBSD! The Power to Serve --- On Fri 01/28, Olivier Certner < [EMAIL PROTECTED] > wrote: From: Olivier Certner [mailto: [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Date: Fri, 28 Jan 2005 10:05:30 +0100 Subject: Re: 5.3 interrupt storm (atapicam) and I/O error Hi, Could you give a look at my post dated 04/01/2005 entitled "Freeze with CAM (using KsCD)"? Maybe we have fallen on the same kind of bug concerning atapicam. If you have KDE, maybe you should try to reproduce the problem I had. I've no time to test your scenario (the one with the EIDE drive, I don't have SCSI) now, but I'll try to reproduce it at the beginning of next week, in order to see if the freeze happens also on my computer. Hope this will help us to progress on our issues. Regards, Olivier___freebsd-questions@freebsd.org mailing listhttp://lists.freebsd.org/mailman/listinfo/freebsd-questionsTo unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ 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 interrupt storm (atapicam) and I/O error
oops, did forget the tixt file ... Daniel S. Haischt schrieb: I don't know whether this is related to your issue, but on one of my boxes I am also getting an interrupt storm with atapicam enabled. On FreeBSD 5.2.1 I did not experience any interrupt storm issues, even if using the same hardware configuration. Have a look at the attached text file for a detailed description ... Olivier Certner schrieb: Hi, Could you give a look at my post dated 04/01/2005 entitled "Freeze with CAM (using KsCD)"? Maybe we have fallen on the same kind of bug concerning atapicam. If you have KDE, maybe you should try to reproduce the problem I had. I've no time to test your scenario (the one with the EIDE drive, I don't have SCSI) now, but I'll try to reproduce it at the beginning of next week, in order to see if the freeze happens also on my computer. Hope this will help us to progress on our issues. Regards, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Mit freundlichen Gruessen / With kind regards DAn.I.El S. Haischt Want a complete signature??? Type at a shell prompt: $ > finger -l [EMAIL PROTECTED] Hello, recently I updated one of my FreeBSD boxes to v 5.3. This box got a builtin Promise PDC20269 UDMA133 controller. Actually it's a controller with two IDE channels. So far if using the GENERIC kernel that comes with FreeBSD, I do not experience any problems. If using my own customized kernel I am getting the following error message while booting the system: 8<8<8<---8<-8<- Interrupt storm detected on "irq10: atapci1"; throtteling interrupt source: >8>8>8--->8->8- After some trail-and-error based investigations, I did figure out that if I don't plugin any device into IDE channel two, the just described error does not occur. So it has something to do with IDE channel two. As an additional note - The controller works under Linux, FreeBSD 5.3 (GENERIC) and FreeBSD 5.2.1 (custom kernel). Any hints on how to solve this issue would be greatly appreciated. ___ 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 interrupt storm (atapicam) and I/O error
I don't know whether this is related to your issue, but on one of my boxes I am also getting an interrupt storm with atapicam enabled. On FreeBSD 5.2.1 I did not experience any interrupt storm issues, even if using the same hardware configuration. Have a look at the attached text file for a detailed description ... Olivier Certner schrieb: Hi, Could you give a look at my post dated 04/01/2005 entitled "Freeze with CAM (using KsCD)"? Maybe we have fallen on the same kind of bug concerning atapicam. If you have KDE, maybe you should try to reproduce the problem I had. I've no time to test your scenario (the one with the EIDE drive, I don't have SCSI) now, but I'll try to reproduce it at the beginning of next week, in order to see if the freeze happens also on my computer. Hope this will help us to progress on our issues. Regards, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Mit freundlichen Gruessen / With kind regards DAn.I.El S. Haischt Want a complete signature??? Type at a shell prompt: $ > finger -l [EMAIL PROTECTED] ___ 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 interrupt storm (atapicam) and I/O error
Hi, Could you give a look at my post dated 04/01/2005 entitled "Freeze with CAM (using KsCD)"? Maybe we have fallen on the same kind of bug concerning atapicam. If you have KDE, maybe you should try to reproduce the problem I had. I've no time to test your scenario (the one with the EIDE drive, I don't have SCSI) now, but I'll try to reproduce it at the beginning of next week, in order to see if the freeze happens also on my computer. Hope this will help us to progress on our issues. Regards, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
5.3 interrupt storm (atapicam) and I/O error
Greetings, I've recently returned to FreeBSD (x86) after my Ultra 30 died. I've had good results with the 5.2* and 5.3 releases until I tried to copy an audio cd with cdda2wav. I'm a bit 'out-of-touch' with the changes to FBSD over the last 4 years or so and am hoping someone can point me straight. First... I tried cdda2wav on the disk in my SCSI CD drive attached to a 2940 controller. Got a boatload of messages like the following which eventually resulted in a hung process. cmd finished after 0.175s timeout 300s 1/ 1/ 1/ 51495 54573%cdda2wav: Input/output error. ReadStandard10: scsi sendcmd: retryable error CDB: 28 00 00 02 36 4F 00 00 1A 00 status: 0x0 (GOOD STATUS) resid: 53248 cmd finished after 0.174s timeout 300s 1/ 1/ 1/ 51496 54573%cdda2wav: Input/output error. ReadStandard10: scsi sendcmd: retryable error CDB: 28 00 00 02 36 68 00 00 0C 00 status: 0x0 (GOOD STATUS) resid: 24576 So I thought I'd try enabling atapicam and trying to use my EIDE CD drive but the system hangs on boot with a message about an "interrupt storm" (throttling input). I tried to disable the 'atapicd' device but it didn't seem to help. Hoping someone has the magic potion for this.. Many thanks! -- 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: atapicam error message
"Galanaki, Dimitrios" <[EMAIL PROTECTED]> writes: > I am referring to the standard non-critical kernel error message: > > cd0: Attempt to query device size failed: NOT READY, Medium not present Not only is it non-critical, it's not an error message. > This occurs when one compiles the device atapicam to access the atapi CD > through the SCSI interface. > In addition to this message there is a very > annoying 30 something second delay. 15 seconds, perhaps? As in options SCSI_DELAY=15000# Delay (in ms) before probing SCSI in the GENERIC kernel? You can cut down that delay safely unless you have other, slow, SCSI devices. > 1) Does anyone know the origin of this message? > 2) How do I get rid of it without having to put a CD in the tray before a > boot? Why bother? It's a boot-time informational message, and it's correct. There are lots of other messages about the state of the system when you boot, too; I suppose it would be possible to come up with a way to provide for a less verbose boot (the same way that you can currently request a *more* verbose set of boot messages), but the utility of such a "feature" is low enough that no one has been inspired to provide it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
atapicam error message
Hello All, I am referring to the standard non-critical kernel error message: cd0: Attempt to query device size failed: NOT READY, Medium not present This occurs when one compiles the device atapicam to access the atapi CD through the SCSI interface. In addition to this message there is a very annoying 30 something second delay. 1) Does anyone know the origin of this message? 2) How do I get rid of it without having to put a CD in the tray before a boot? I have been google about this problem for quite a while but with not much luck, so any information would be appreciated. D. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Do I need atapicam?
On Sun, Jan 02, 2005 at 10:59:05AM -0500, Trey Sizemore wrote: > I'm running 5.3-RELEASE and want to use k3b for CD burning. I have an > IDE CD burner and IDE DVD drive. Do I need to have atapicam loaded in > the kernel? Has this been depricated in 5.3? I notice the following in > my GENERIC kernel config: > > [snip] > > Do I need to add a line for atapicam in my GENERIC file and rebuild the > kernel? Yes. You can't kldload atapicam. You need a 'device atapicam' line in your kernel config file, then rebuild, install and reboot the kernel. > Cheers, > Trey Regards, -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Do I need atapicam?
I'm running 5.3-RELEASE and want to use k3b for CD burning. I have an IDE CD burner and IDE DVD drive. Do I need to have atapicam loaded in the kernel? Has this been depricated in 5.3? I notice the following in my GENERIC kernel config: salamander# cat /sys/i386/conf/GENERIC | grep atapi device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives And trying to load atapicam results in: salamander# kldload atapicam kldload: can't load atapicam: No such file or directory Do I need to add a line for atapicam in my GENERIC file and rebuild the kernel? Thanks. -- Cheers, Trey --- "This wasn't just plain terrible, this was fancy terrible. This was terrible with raisins in it." -- Dorothy Parker 10:58AM up 18:11, 0 users, load averages: 0.09, 0.08, 0.07 FreeBSD salamander.thesizemores.net 5.3-RELEASE i386 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cdparanoia and atapicam question
On Tue, 7 Dec 2004 19:26:33 -0500, Dev Tugnait <[EMAIL PROTECTED]> wrote: > Post your dmesg. Copyright (c) 1992-2004 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.10-RELEASE #2: Sat Dec 4 14:03:29 GMT 2004 [EMAIL PROTECTED]:/usr/src/sys/compile/MANTOY Timecounter "i8254" frequency 1193182 Hz CPU: Intel Pentium III (933.03-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x68a Stepping = 10 Features=0x387fbff real memory = 1140785152 (1114048K bytes) avail memory = 1103495168 (1077632K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor motherboard: 2 CPUs cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00178011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc04de000. netsmb_dev: loaded Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 8 entries at 0xc00fdd20 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 agp0: mem 0xf000-0xf3ff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 10 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xd000-0xd00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xd400-0xd41f irq 12 at device 7.2 on pci0 usb0: 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 ums0: Logitech USB Receiver, rev 1.10/9.10, addr 2, iclass 3/1 ums0: 5 buttons and Z dir. uhci1: port 0xd800-0xd81f irq 12 at device 7.3 on pci0 usb1: 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 pci0: (vendor=0x1106, dev=0x3057) at 7.4 pcm0: port 0xdc00-0xdc1f irq 10 at device 11.0 on pci0 pcm0: dc0: <82c169 PNIC 10/100BaseTX> port 0xe400-0xe4ff mem 0xf800-0xf8ff irq 11 at device 12.0 on pci0 dc0: Ethernet address: 00:02:e3:08:0b:e2 miibus0: on dc0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto orm0: at iomem 0xc-0xc7fff on isa0 pmtimer0 on isa0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: 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: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 IPsec: Initialized Security Association Processing. IP Filter: v3.4.31 initialized. Default = block all, Logging = disabled SMP: AP CPU #1 Launched! ad0: 19092MB [38792/16/63] at ata0-master UDMA100 acd0: CD-RW at ata1-master PIO4 Mounting root from ufs:/dev/ad0s3a cd0 at ata1 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 16.000MB/s transfers cd0: cd present [227290 x 2048 byte records] ad0: UDMA ICRC error reading fsbn 0 (ad0 bn 0; cn 0 tn 0 sn 0) retrying ad0: UDMA ICRC error reading fsbn 0 (ad0 bn 0; cn 0 tn 0 sn 0) retrying ad0: UDMA ICRC error reading fsbn 0 (ad0 bn 0; cn 0 tn 0 sn 0) retrying ad0: UDMA ICRC error reading fsbn 0 (ad0 bn 0; cn 0 tn 0 sn 0) falling back to PIO mode ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cdparanoia and atapicam question
Post your dmesg. * Robert Dormer ([EMAIL PROTECTED]) wrote: > On Mon, 6 Dec 2004 09:22:50 -0500, Dev Tugnait <[EMAIL PROTECTED]> wrote: > > What is the output from cdparanoia -vsQ > > If you are trying to rip them to your harddis and cant figurecdparanoia use > > a frontend to it like grip. > > can't figure out what the problem would be, judging from this > > cdparanoia III release 9.8 (March 23, 2001) > (C) 2001 Monty <[EMAIL PROTECTED]> and Xiphophorus > FreeBSD porting (c) 2003 > Simon 'corecode' Schubert <[EMAIL PROTECTED]> > > Report bugs to [EMAIL PROTECTED] > http://www.xiph.org/paranoia/ > > Checking /dev/cd0 for cdrom... > Could not stat /dev/cd0: No such file or directory > > Checking /dev/cd1 for cdrom... > Could not stat /dev/cd1: No such file or directory > > Checking /dev/cd2 for cdrom... > Could not stat /dev/cd2: No such file or directory > > Checking /dev/cd3 for cdrom... > Could not stat /dev/cd3: No such file or directory > > Checking /dev/acd0 for cdrom... > Could not stat /dev/acd0: No such file or directory > > Checking /dev/acd1 for cdrom... > Could not stat /dev/acd1: No such file or directory > > Checking /dev/acd2 for cdrom... > Could not stat /dev/acd2: No such file or directory > > Checking /dev/acd3 for cdrom... > Could not stat /dev/acd3: No such file or directory > > Checking /dev/wcd0 for cdrom... > Could not stat /dev/wcd0: No such file or directory > > Checking /dev/wcd1 for cdrom... > Could not stat /dev/wcd1: No such file or directory > > Checking /dev/wcd2 for cdrom... > Could not stat /dev/wcd2: No such file or directory > > Checking /dev/wcd3 for cdrom... > Could not stat /dev/wcd3: No such file or directory > > Checking /dev/mcd0 for cdrom... > Could not stat /dev/mcd0: No such file or directory > > Checking /dev/mcd1 for cdrom... > Could not stat /dev/mcd1: No such file or directory > > Checking /dev/mcd2 for cdrom... > Could not stat /dev/mcd2: No such file or directory > > Checking /dev/mcd3 for cdrom... > Could not stat /dev/mcd3: No such file or directory > > Checking /dev/cd0c for cdrom... > > CDROM model sensed: SONY CD-RW CRX175A1 5YS3 > > Checking for ATAPICAM... > Drive is ATAPI (using ATAPICAM) > > Checking for MMC style command set... > Drive is MMC style > Setting default read size to 26 sectors (61152 bytes). > > Verifying CDDA command set... > Expected command set reads OK. > > Table of contents (audio tracks only): > tracklength begincopy pre ch > === > 1.17952 [03:59.27]0 [00:00.00]no no 2 > 2.17653 [03:55.28]17952 [03:59.27]no no 2 > 3.21082 [04:41.07]35605 [07:54.55]no no 2 > 4.20363 [04:31.38]56687 [12:35.62]no no 2 > 5.25660 [05:42.10]77050 [17:07.25]no no 2 > 6.19267 [04:16.67] 102710 [22:49.35]no no 2 > 7.19900 [04:25.25] 121977 [27:06.27]no no 2 > 8.17848 [03:57.73] 141877 [31:31.52]no no 2 > 9.20285 [04:30.35] 159725 [35:29.50]no no 2 > 10.26970 [05:59.45] 180010 [40:00.10]no no 2 > 11.20310 [04:30.60] 206980 [45:59.55]no no 2 > TOTAL 227290 [50:30.40](audio only) > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" +--==/\/\==--+ (__) FreeBSD | <[EMAIL PROTECTED]> |\\\'',) The |Kernel ESCAFLOWNE | \/ \ ^Power | Web http://unixdaemon.org | .\._/_)To +--==\/\/==--+ Serve [ We've switched the bath sponge with a tribble. ] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cdparanoia and atapicam question
On Mon, 6 Dec 2004 09:22:50 -0500, Dev Tugnait <[EMAIL PROTECTED]> wrote: > What is the output from cdparanoia -vsQ > If you are trying to rip them to your harddis and cant figurecdparanoia use a > frontend to it like grip. can't figure out what the problem would be, judging from this cdparanoia III release 9.8 (March 23, 2001) (C) 2001 Monty <[EMAIL PROTECTED]> and Xiphophorus FreeBSD porting (c) 2003 Simon 'corecode' Schubert <[EMAIL PROTECTED]> Report bugs to [EMAIL PROTECTED] http://www.xiph.org/paranoia/ Checking /dev/cd0 for cdrom... Could not stat /dev/cd0: No such file or directory Checking /dev/cd1 for cdrom... Could not stat /dev/cd1: No such file or directory Checking /dev/cd2 for cdrom... Could not stat /dev/cd2: No such file or directory Checking /dev/cd3 for cdrom... Could not stat /dev/cd3: No such file or directory Checking /dev/acd0 for cdrom... Could not stat /dev/acd0: No such file or directory Checking /dev/acd1 for cdrom... Could not stat /dev/acd1: No such file or directory Checking /dev/acd2 for cdrom... Could not stat /dev/acd2: No such file or directory Checking /dev/acd3 for cdrom... Could not stat /dev/acd3: No such file or directory Checking /dev/wcd0 for cdrom... Could not stat /dev/wcd0: No such file or directory Checking /dev/wcd1 for cdrom... Could not stat /dev/wcd1: No such file or directory Checking /dev/wcd2 for cdrom... Could not stat /dev/wcd2: No such file or directory Checking /dev/wcd3 for cdrom... Could not stat /dev/wcd3: No such file or directory Checking /dev/mcd0 for cdrom... Could not stat /dev/mcd0: No such file or directory Checking /dev/mcd1 for cdrom... Could not stat /dev/mcd1: No such file or directory Checking /dev/mcd2 for cdrom... Could not stat /dev/mcd2: No such file or directory Checking /dev/mcd3 for cdrom... Could not stat /dev/mcd3: No such file or directory Checking /dev/cd0c for cdrom... CDROM model sensed: SONY CD-RW CRX175A1 5YS3 Checking for ATAPICAM... Drive is ATAPI (using ATAPICAM) Checking for MMC style command set... Drive is MMC style Setting default read size to 26 sectors (61152 bytes). Verifying CDDA command set... Expected command set reads OK. Table of contents (audio tracks only): tracklength begincopy pre ch === 1.17952 [03:59.27]0 [00:00.00]no no 2 2.17653 [03:55.28]17952 [03:59.27]no no 2 3.21082 [04:41.07]35605 [07:54.55]no no 2 4.20363 [04:31.38]56687 [12:35.62]no no 2 5.25660 [05:42.10]77050 [17:07.25]no no 2 6.19267 [04:16.67] 102710 [22:49.35]no no 2 7.19900 [04:25.25] 121977 [27:06.27]no no 2 8.17848 [03:57.73] 141877 [31:31.52]no no 2 9.20285 [04:30.35] 159725 [35:29.50]no no 2 10.26970 [05:59.45] 180010 [40:00.10]no no 2 11.20310 [04:30.60] 206980 [45:59.55]no no 2 TOTAL 227290 [50:30.40](audio only) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cdparanoia and atapicam question
What is the output from cdparanoia -vsQ If you are trying to rip them to your harddis and cant figurecdparanoia use a frontend to it like grip. * Robert Dormer ([EMAIL PROTECTED]) wrote: > Hello all, > > I'm trying to get some CDs of mine onto the hard drive, using > cdparanoia. All of the relevant ATAPICAM options are in the kernel. > However, when I fire it up, it just sits there and does nothing. > Nothing meaning no recording, no timing out, nothing. It won't even > respond to kill -9. I've also tried camcontrol with the test unit > ready option, same response. Anyone know what's going on or what I'm > missing? > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" +--==/\/\==--+ (__) FreeBSD | <[EMAIL PROTECTED]> |\\\'',) The |Kernel ESCAFLOWNE | \/ \ ^Power | Web http://unixdaemon.org | .\._/_)To +--==\/\/==--+ Serve [ We've switched the bath sponge with a tribble. ] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
cdparanoia and atapicam question
Hello all, I'm trying to get some CDs of mine onto the hard drive, using cdparanoia. All of the relevant ATAPICAM options are in the kernel. However, when I fire it up, it just sits there and does nothing. Nothing meaning no recording, no timing out, nothing. It won't even respond to kill -9. I've also tried camcontrol with the test unit ready option, same response. Anyone know what's going on or what I'm missing? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Two Questions ( atapicam related and scheduler related)
On 2004-10-18 16:21, Thomas Moyer <[EMAIL PROTECTED]> wrote: > I been following the progress of the 5.3 release and I thought they were > changing the shceduler from SCHED_4BSD to SCHED_ULE? Also I recently > acquired a DVD+-RW and was wondering if I should stick with using burncd > and growisfs with the standard /dev/acd0 or should I switch to using > atapicam? Is there any sort of a performance gain? What are the > advantages and disadvantages of both? FYI, Using burncd has been broken for me in -CURRENT since early June. The process reaches the stage of fixating, but then my kernel panics with a message for `illegal phase'. I didn't really *need* to write CD-ROMs until today, and I finally tried atapicam with cdrecord. It works like a charm here. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Two Questions ( atapicam related and scheduler related)
I been following the progress of the 5.3 release and I thought they were changing the shceduler from SCHED_4BSD to SCHED_ULE? Also I recently acquired a DVD+-RW and was wondering if I should stick with using burncd and growisfs with the standard /dev/acd0 or should I switch to using atapicam? Is there any sort of a performance gain? What are the advantages and disadvantages of both? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: atapicam, cdrecord, and my gaping clue deficiency
On Friday 15 October 2004 21:35, Peter Seebach wrote: > In message <[EMAIL PROTECTED]>, FreeBsdBeni writes: > >I'm having _exactly_ the same problem... :-( Mine is a Pioneer DVR-107D, > >firmware v1.18 on a 5.2.1-REL-p11. > > > >dmesg : > >cd1 at ata1 bus 0 target 0 lun 0 > >cd1: Removable CD-ROM SCSI-0 device > >cd1: 16.000MB/s transfers. > > > >I got the same reply from mr. Schilling and I haven't found any solution > >yet... Could it be something with the drives/firmware ? > > What's your motherboard? Mine's a SuperMicro X5DE8-GG. Mainboard : Medion MD 8088 (MSI MS-7048) Chipset : Intel 865PE And - unfortunately - all works fine under WinXP... > And... With FreeBSD 5.3beta7, it works fine. Ok, will wait for the official 5.3 release in the next days then. > I found one other reference to problems with the ServerWorks CSB6 chipset > under FreeBSD 5.2.1. > > Anyway, upgrading to 5.3beta7 made my problem go away, as well as my > mysterious bus errors. (And before anyone says "bad memory", yes, I know; > I ran memtest for a day, ran burnMMX and burnP6 several times at once for > a day, and the machine has ECC, and has no events in the event log.) I've had no memory problems so far either. Beni. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: atapicam, cdrecord, and my gaping clue deficiency
In message <[EMAIL PROTECTED]>, FreeBsdBeni writes: >I'm having _exactly_ the same problem... :-( Mine is a Pioneer DVR-107D, >firmware v1.18 on a 5.2.1-REL-p11. >dmesg : >cd1 at ata1 bus 0 target 0 lun 0 >cd1: Removable CD-ROM SCSI-0 device >cd1: 16.000MB/s transfers. >I got the same reply from mr. Schilling and I haven't found any solution >yet... Could it be something with the drives/firmware ? What's your motherboard? Mine's a SuperMicro X5DE8-GG. And... With FreeBSD 5.3beta7, it works fine. I found one other reference to problems with the ServerWorks CSB6 chipset under FreeBSD 5.2.1. Anyway, upgrading to 5.3beta7 made my problem go away, as well as my mysterious bus errors. (And before anyone says "bad memory", yes, I know; I ran memtest for a day, ran burnMMX and burnP6 several times at once for a day, and the machine has ECC, and has no events in the event log.) (I can't do any more testing, I'm afraid, as the machine has been shipped away, now that it's working.) -s ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: atapicam, cdrecord, and my gaping clue deficiency
On Friday 15 October 2004 05:32, Peter Seebach wrote: > Hardware: SuperMicro X5DE8-GG motherboard, dual Xeon 2.8Ghz, 2GB memory. > Using onboard SCSI controller for disks, onboard IDE for DVD burner. DVD > burner is a Pioneer DVR-108. > > Software: cdrecord and/or cdrecord-ProDVD. > > Problem: CD burning Always Fails. Failure mode is 100% repeatable and > consistent: > > cdrecord: Input/output error. write_g1: scsi sendcmd: retryable error > CDB: 2A 00 00 00 01 55 00 00 1F 00 > status: 0x2 (CHECK CONDITION) > Sense Bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 Sense Key: 0x [], Segment 0 > Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0 > Sense flags: Blk 0 (not valid) > cmd finished after 0.000s timeout 40s > write track data: error after 698368 bytes > Sense Bytes: 70 00 02 00 00 00 00 0E 00 00 00 00 04 08 00 00 00 00 > > Mr. Schilling says "Install a non-defective kernel." I am assuming that > this doesn't mean "some other OS". > > Googling around on the CDB bytes turns up lots of people with cabling > problems, especially on SCSI busses. > > Googling around on FreeBSD and 698368 turns up someone who needed the > P1003_1B option added to a kernel. (It's now just the _KPOSIX option, and > it's already in there.) > > I got as far as putting in the atapicam and related devices. This happens > whether or not I leave the atapicd driver in place. (dmesg output below is > without.) > > I enclose dmesg and config file as attachments for perusal. I am Very > Worried by the observation that the CD is claiming a 3.300MB/sec transfer > rate: > > cd0 at ata0 bus 0 target 0 lun 0 > cd0: Removable CD-ROM SCSI-0 device > cd0: 3.300MB/s transfers > Hi, I'm having _exactly_ the same problem... :-( Mine is a Pioneer DVR-107D, firmware v1.18 on a 5.2.1-REL-p11. dmesg : cd1 at ata1 bus 0 target 0 lun 0 cd1: Removable CD-ROM SCSI-0 device cd1: 16.000MB/s transfers. I got the same reply from mr. Schilling and I haven't found any solution yet... Could it be something with the drives/firmware ? Beni. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: atapicam, cdrecord, and my gaping clue deficiency
In message <[EMAIL PROTECTED]>, Peter Seebach write s: >Problem: CD burning Always Fails. Failure mode is 100% repeatable and >consistent: A followup: I have an HP "DVD Writer dvd630i". 1. If I install only the DVD Writer dvd630i, as a master, the kernel panics and won't boot. 2. If I install both drives, with the HP as slave, the HP comes up at 33MB/sec and the Pioneer at 66MB/sec. In that configuration, the HP burns CDs just fine, but the Pioneer doesn't. So I'd just put the HP in the system. But it won't boot with just the HP! The last thing it says is "ata1-slave: interrupt failed." This is odd, 'cuz the drive's set for master, and there is no slave. ??? -s ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
atapicam, cdrecord, and my gaping clue deficiency
Hardware: SuperMicro X5DE8-GG motherboard, dual Xeon 2.8Ghz, 2GB memory. Using onboard SCSI controller for disks, onboard IDE for DVD burner. DVD burner is a Pioneer DVR-108. Software: cdrecord and/or cdrecord-ProDVD. Problem: CD burning Always Fails. Failure mode is 100% repeatable and consistent: cdrecord: Input/output error. write_g1: scsi sendcmd: retryable error CDB: 2A 00 00 00 01 55 00 00 1F 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Sense Key: 0x [], Segment 0 Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 0.000s timeout 40s write track data: error after 698368 bytes Sense Bytes: 70 00 02 00 00 00 00 0E 00 00 00 00 04 08 00 00 00 00 Mr. Schilling says "Install a non-defective kernel." I am assuming that this doesn't mean "some other OS". Googling around on the CDB bytes turns up lots of people with cabling problems, especially on SCSI busses. Googling around on FreeBSD and 698368 turns up someone who needed the P1003_1B option added to a kernel. (It's now just the _KPOSIX option, and it's already in there.) I got as far as putting in the atapicam and related devices. This happens whether or not I leave the atapicd driver in place. (dmesg output below is without.) I enclose dmesg and config file as attachments for perusal. I am Very Worried by the observation that the CD is claiming a 3.300MB/sec transfer rate: cd0 at ata0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 3.300MB/s transfers This is almost certainly incorrect; it should be ATA66, and I have an 80-pin cable. I'm not *totally* hopeless: # cat /boot/loader.conf hw.ata.atapi_dma="1" but I can't tell whether that's fixed anything. My hypothesis is that I have somehow failed to persuade the kernel to Really And Truly do DMA on this device, and that it's fallen back on a pathetically slow and inappropriate PIO mode. Clues will be gratefully appreciated; also, since I've seen other people with similar problems, if I can find a fix, I will write about it and put lots of happy Google-friendly keywords in it so fewer people will ask in the future. Dmesg output: --- Copyright (c) 1992-2004 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 5.2.1-RELEASE #0: Thu Oct 14 20:07:13 EDT 2004 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/JPC Preloaded elf kernel "/boot/kernel/kernel" at 0xc09e8000. MPTable: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2800.12-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf25 Stepping = 5 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 2147483648 (2048 MB) avail memory = 2080739328 (1984 MB) FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0: Assuming intbase of 0 ioapic1: Assuming intbase of 16 ioapic2: Assuming intbase of 32 ioapic3: Assuming intbase of 48 ioapic0 irqs 0-15 on motherboard ioapic1 irqs 16-31 on motherboard ioapic2 irqs 32-47 on motherboard ioapic3 irqs 48-63 on motherboard Pentium Pro MTRR support enabled npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pcibios: BIOS version 2.10 Using $PIR table, 11 entries at 0xc00f4a20 pcib0: at pcibus 0 on motherboard pci0: on pcib0 pcib0: slot 8 INTA routed to irq 28 pcib0: slot 9 INTA routed to irq 26 pcib0: slot 10 INTA routed to irq 30 pcib0: slot 10 INTB routed to irq 31 pcib0: slot 11 INTA routed to irq 29 pcib0: slot 15 INTA routed to irq 17 pcib1: at device 6.0 on pci0 pci1: on pcib1 pcib1: slot 8 INTA routed to irq 22 pcib1: slot 9 INTA routed to irq 23 pcib1: slot 9 INTB routed to irq 18 pcib1: slot 9 INTC routed to irq 19 fwohci0: port 0xa800-0xa87f mem 0xfc8ff000-0xfc8ff7ff irq 22 at device 8.0 on pci1 fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channel is 8. fwohci0: EUI64 00:11:06:00:00:00:50:66 fwohci0: Phy 1394a available S400, 3 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:11:06:00:50:66 sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) ohci0: mem 0xfc8fd000-0xfc8fdfff irq 23 at device 9.0 on pci1 usb0: OHCI version 1.0 usb0: on ohci0 usb0: USB revision 1.0 uhub0: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered
Re: ATAPICAM - cdrecord will not recognize my DVD burner
--- Matt Navarre <[EMAIL PROTECTED]> wrote: > > > > device atapicam > > You also need > > devicecd Thank you for the info! I didn't think it was no longer a kernel conf option since I didn't see it in the NOTES file (replacement for LINT??) and thought it should have been loaded as a module instead. I'm compiling a new kernel now. Thanks again everyone, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATAPICAM - cdrecord will not recognize my DVD burner
--- Fabian Keil <[EMAIL PROTECTED]> wrote: > On Sunday 19 September 2004 14:55, BSDjunkie wrote: > > > I have been using cdrecord since I built my > system. I > > have an Asus A7N8X delux motherboard, AMD 3200+ > cpu, > > 2G of ram and (2) 15,000 rpm scsi drives. > > > > I recently bought a Toshiba DVD+r/-r burner, which > I > > replaced my DVDr/CDRW drive with. > > > > The new drive is detected at bootup: > > > > acd0: DVDR at > ata0-master > > PIO4 > > Do you later see lines like: > > cd0 at ata0 bus 0 target 0 lun 0 > cd1 at ata1 bus 0 target 0 lun 0 > cd2 at ata1 bus 0 target 1 lun 0? > > If not, you probably need to add > > device atapicam > > to your kernel configuration. > > > However, cdrecord --scanbus no longer can see the > > drive through scsi emulation. > > What does it see? > > Regards > Fabian > Other than what I mention in my post, there's nothing more detected at boot-up. I'll see if there's an option atapicam that I can include in my kernel config file. Thank you for the advice. Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATAPICAM - cdrecord will not recognize my DVD burner
On Sunday 19 September 2004 09:51, Fabian Keil wrote: > On Sunday 19 September 2004 14:55, BSDjunkie wrote: > > I have been using cdrecord since I built my system. I > > have an Asus A7N8X delux motherboard, AMD 3200+ cpu, > > 2G of ram and (2) 15,000 rpm scsi drives. > > > > I recently bought a Toshiba DVD+r/-r burner, which I > > replaced my DVDr/CDRW drive with. > > > > The new drive is detected at bootup: > > > > acd0: DVDR at ata0-master > > PIO4 > > Do you later see lines like: > > cd0 at ata0 bus 0 target 0 lun 0 > cd1 at ata1 bus 0 target 0 lun 0 > cd2 at ata1 bus 0 target 1 lun 0? > > If not, you probably need to add > > device atapicam You also need devicecd So it will attach to the DVD burner. See the handbook on adding atatpicam to your kernel: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html#ATAPICAM > > to your kernel configuration. > > > However, cdrecord --scanbus no longer can see the > > drive through scsi emulation. > > What does it see? > > Regards > Fabian > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" -- "We all enter this world in the same way: naked, screaming, and soaked in blood. But if you live your life right, that kind of thing doesn't have to stop there." -- Dana Gould ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATAPICAM - cdrecord will not recognize my DVD burner
On Sunday 19 September 2004 14:55, BSDjunkie wrote: > I have been using cdrecord since I built my system. I > have an Asus A7N8X delux motherboard, AMD 3200+ cpu, > 2G of ram and (2) 15,000 rpm scsi drives. > > I recently bought a Toshiba DVD+r/-r burner, which I > replaced my DVDr/CDRW drive with. > > The new drive is detected at bootup: > > acd0: DVDR at ata0-master > PIO4 Do you later see lines like: cd0 at ata0 bus 0 target 0 lun 0 cd1 at ata1 bus 0 target 0 lun 0 cd2 at ata1 bus 0 target 1 lun 0? If not, you probably need to add device atapicam to your kernel configuration. > However, cdrecord --scanbus no longer can see the > drive through scsi emulation. What does it see? Regards Fabian ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ATAPICAM - cdrecord will not recognize my DVD burner
FreeBSD Enthusiasts, I have been using cdrecord since I built my system. I have an Asus A7N8X delux motherboard, AMD 3200+ cpu, 2G of ram and (2) 15,000 rpm scsi drives. I recently bought a Toshiba DVD+r/-r burner, which I replaced my DVDr/CDRW drive with. The new drive is detected at bootup: acd0: DVDR at ata0-master PIO4 However, cdrecord --scanbus no longer can see the drive through scsi emulation. I tried to load the cam module, but it is already loaded. I am using 5.2.1-RELEASE-p9. Any pointers in the right direction are appreciated. Thanks for your consideration, Mark Withers ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATAPICAM FreeBSD 5.2.1
Hi, Derrick Edwards wrote: Good day to all. I have been going crazy trying to get K3b to work. Everytime I attempt to burn a cd, the system freezes and reboots. I have been on the formus for a month now trying to find a soulution. Seems a lot of other people are having the same issue, and all theses guys are pointing to atapicam. I reinstalled 4.10 for testing and k3b works perfectly. Is atapicam really the problem as I suspect? If so, will this be fixed prior to 5.3 release. Apologize in advance if this is a silly question. Thanks for your assistance, please let me know if you need additional info. Derrick ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" When you are burning are you using SCSI, IDE or both in a combination? I have had some problems (on 5.2.1-RELEASE-p5) with using a SCSI CD-reader in combination with my NEC 1100 burner. If I start K3B it freezes my system, but if I removed my SCSI CD-reader the problem went away. But the I only had my IDE NEC 1100 burner left. Note that I had a Hard drive as well attached too my SCSI controller card and that did not cause in my eye's any problems. Perhaps you are having a similar problem? But then again I don't think that my problems is directly related too yours. Thanks Mattias Björk ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATAPICAM FreeBSD 5.2.1
On Tue, 27 Jul 2004 18:40:19 -0400 Derrick Edwards <[EMAIL PROTECTED]> wrote: > Good day to all. I have been going crazy trying to get K3b to work. > Everytime I attempt to burn a cd, the system freezes and reboots. I have been > on the formus for a month now trying to find a soulution. Seems a lot of > other people are having the same issue, and all theses guys are pointing to > atapicam. I reinstalled 4.10 for testing and k3b works perfectly. Is > atapicam really the problem as I suspect? If so, will this be fixed prior to > 5.3 release. Apologize in advance if this is a silly question. > Thanks for your assistance, please let me know if you need additional info. > Derrick FYI, on my system FreeBSD 5.2-CURRENT #0: Wed May 26 02:08:58 EEST 2004 I have no such problems. It is a VIA KT400/8235 (and also on an 8237) with a Plextor PX 708A DVD+RW burner. Have you contacted k3b maintainer ? I found him to be very helpful. -- IOnut Unregistered ;) FreeBSD "user" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ATAPICAM FreeBSD 5.2.1
Good day to all. I have been going crazy trying to get K3b to work. Everytime I attempt to burn a cd, the system freezes and reboots. I have been on the formus for a month now trying to find a soulution. Seems a lot of other people are having the same issue, and all theses guys are pointing to atapicam. I reinstalled 4.10 for testing and k3b works perfectly. Is atapicam really the problem as I suspect? If so, will this be fixed prior to 5.3 release. Apologize in advance if this is a silly question. Thanks for your assistance, please let me know if you need additional info. Derrick ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Reading from ATAPICAM DVD
I am attempting to use DVD::RIP to rip a DVD (or a piece of one). It tries to execute "tcprobe -H 10 -i /dev/cd0c" and fails with the error: [fileinfo.c:118] file read error: Invalid argument The code is "(read(fdes, buf, bytes)". (The value of bytes is 4.) I also log a system error of: dscheck(#cd/2): b_bcount 5 is not on a sector boundary (ssize 2048) Is this an ATAPICAM or ATA issue or is it required that reads start at a sector boundary? I assume that this code at least works on Linux systems and I had always assumed that, even though the disk must start a transfer at a sector boundary, the driver buffered the data to make it appear as a byte stream. Maybe I'm confused. Any suggestions on this are appreciated as I want to get a better idea of what is happening before a report the problem. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ATAPICAM - Sony AIT SDX-420 ATAPI tape drive on FreeBSD 5.2.1
I have added a Sony SDX-420 ATAPI tape drive to a FreeBSD 5.2.1-RELEASE system. The following is part of the kernel build: # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicam # SCSI peripherals device scbus # SCSI bus (required for SCSI) device sa # Sequential Access (tape etc) device cd # CD dmesg includes: GEOM: create disk ad0 dp=0xc43f8760 ad0: 114473MB [232581/16/63] at ata0-master UDMA100 GEOM: create disk cd0 dp=0xc44e7600 sa0 at ata1 bus 0 target 0 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 3.300MB/s transfers SMP: AP CPU #1 Launched! cd0 at ata1 bus 0 target 1 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 3.300MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present A dump appears to work: monster# mt rew monster# dump -ua0 -b64 /usr DUMP: WARNING: should use -L when dumping live filesystems! DUMP: Date of this level 0 dump: Mon Jun 14 18:45:49 2004 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/ad0s1f (/usr) to /dev/sa0 DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 1668552 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: DUMP: 1800569 tape blocks on 1 volume DUMP: finished in 262 seconds, throughput 6872 KBytes/sec DUMP: level 0 dump on Mon Jun 14 18:45:49 2004 DUMP: Closing /dev/sa0 DUMP: DUMP IS DONE But restore does this: monster# mt rew monster# restore -t -b 64 Mount tape volume 2 Enter ``none'' if there are no more tapes otherwise enter tape name (default: /dev/sa0) none Tape read error while trying to resynchronize continue? [yn] y continuation failed: Bad file descriptor I have tried quite a number of differing things... Any hints or suggestions welcome. Ray Newman Message sent at 07:13 PM on 14 Jun 2004 by PUP::RAYMOND. Id: 368387. Message sent at 07:31 PM on 14 Jun 2004 by PUP::RAYMOND. Id: 368396. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ATAPICAM - Sony AIT SDX-420 ATAPI tape drive on FreeBSD 5.2.1
I have added a Sony SDX-420 ATAPI tape drive to a FreeBSD 5.2.1-RELEASE system. The following is part of the kernel build: # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicam # SCSI peripherals device scbus # SCSI bus (required for SCSI) device sa # Sequential Access (tape etc) device cd # CD dmesg includes: GEOM: create disk ad0 dp=0xc43f8760 ad0: 114473MB [232581/16/63] at ata0-master UDMA100 GEOM: create disk cd0 dp=0xc44e7600 sa0 at ata1 bus 0 target 0 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 3.300MB/s transfers SMP: AP CPU #1 Launched! cd0 at ata1 bus 0 target 1 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 3.300MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present A dump appears to work: monster# mt rew monster# dump -ua0 -b64 /usr DUMP: WARNING: should use -L when dumping live filesystems! DUMP: Date of this level 0 dump: Mon Jun 14 18:45:49 2004 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/ad0s1f (/usr) to /dev/sa0 DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 1668552 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: DUMP: 1800569 tape blocks on 1 volume DUMP: finished in 262 seconds, throughput 6872 KBytes/sec DUMP: level 0 dump on Mon Jun 14 18:45:49 2004 DUMP: Closing /dev/sa0 DUMP: DUMP IS DONE But restore does this: monster# mt rew monster# restore -t -b 64 Mount tape volume 2 Enter ``none'' if there are no more tapes otherwise enter tape name (default: /dev/sa0) none Tape read error while trying to resynchronize continue? [yn] y continuation failed: Bad file descriptor I have tried quite a number of differing things... Any hints or suggestions welcome. Ray Newman ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Trouble with atapicam and DVD+RW
On Wed, Mar 24, 2004 at 12:15:33AM -0500, Ed Alley wrote: > > Thanks for the hints. I'm new to DVDs and didn't realize that one DVD > media is not necessarily the same as another; or the fact that the little > "-" or "+" on the label means something important. (:->) > Have a look to http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-dvds.html all you need to know is covered. Marc ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Trouble with atapicam and DVD+RW
On Wed, Mar 24, 2004 at 12:15:33AM -0500, Ed Alley wrote: > > > Andrew Gould wrote; > > > The description of the DVD burner states "DVD+RW". Are you sure it can > > burn DVD-R's? > > OOPS ;) > > > Andrew also wrote: > > > A couple of us have experienced difficulties with Memorex media. Consider > > testing another brand. > > I feel silly... Been there, done that! Welcome to the club.;-) > > Well, I went out to Office Max and bought a pack of HP dvd+rw DVDs, tried > them out and the burner worked perfectly. I promptly burnt 3GB of > back-up without a problem!!! > > Thanks for the hints. I'm new to DVDs and didn't realize that one DVD > media is not necessarily the same as another; or the fact that the little > "-" or "+" on the label means something important. (:->) > > Ed Alley > Indeed, the devil IS in the details. Best regards, Andrew Gould ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Trouble with atapicam and DVD+RW
> Andrew Gould wrote; > The description of the DVD burner states "DVD+RW". Are you sure it can > burn DVD-R's? OOPS ;) > Andrew also wrote: > A couple of us have experienced difficulties with Memorex media. Consider > testing another brand. I feel silly... Well, I went out to Office Max and bought a pack of HP dvd+rw DVDs, tried them out and the burner worked perfectly. I promptly burnt 3GB of back-up without a problem!!! Thanks for the hints. I'm new to DVDs and didn't realize that one DVD media is not necessarily the same as another; or the fact that the little "-" or "+" on the label means something important. (:->) Ed Alley ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
