PCI IDE Cards

I just got a good deal on a 320GB Seagate Barracuda HD. My only limitation is the 128GB limit my Mac sees it as.
After looking here: http://lowendmac.com/macdan/05/1024.html
bI figured a PCI IDE card would be the best choice for my G3. So I could split it into 2 partitions with Panther on the first partition and 9 on the second.
My question is, are the PCI cards plug and play without drivers (like the hard drive) or do I need a "Mac-Specific" card or Mac drivers to use it with my hard drive?

The 128 GB limitation applies to the onboard IDE controller, and not to an ATA-133 controller card that supports 48-bit logical block addressing, which enables recognition of large drives. If connected to an ATA-133 controller card, partitioning the 320 GB drive is your choice, although I prefer to partition larger drives for the ease/speed of routine disk maintenance. The Acard AEC-6280M ATA-133 controller card for Macs is consistently priced lowest here.
Sonnet and SIIG also market Mac controller cards, but whichever brand that you choose to purchase, it must be the Mac version, because the PC versions of these cards aren't compatible. Bootable controller cards must be firmware-based and not driver-based. The card's ROM is read at boot, so that connected drive(s) are functional. If the controller card required a driver to be read from the hard drive, the sequence for doing so couldn't occur, because the hard drive isn't recognized until the controller card (to which it's connected) is recognized.

Similar Messages

PCI IDE cards and K9N Diamond Motherboards

I was thinking of getting a K9N motherboard, and I wanted to know if it will be compatible with a PCI IDE expander card. Has anybody tried this, and if so did it work?

they are compatible. i remember someone already trying this with a k9 mobo.

K9A2 Platinum Cannot Use RAID and PCI IDE card [SOLVED]

Hello,
I am trying to do the following set-up on my K9A2 Platinum, using a Phenom 9600 processor:
- 2xSATA2 250GB Seagate drives on Promise T3 SATA controller (to be used as RAID 1 devices)
- 1xSATA DVD-RW on Sb600
- 2xIDE DVD-RW on onboard IDE
- One PCI HiPoint RocketRAID ATA100 card (operating in IDE mode) on PCI slot 2 with 1xIDE 40GB hard disk (my Linux partition)
On the BIOS I have enabled the Extra RAID function, in order to enable Promise to work as RAID.
The system POSTs as follows:
- Initial detection (CPU, RAM e.tc)
- RocketRAID gets initialized and detects the IDE disk attached (40GB)
- Promise RAID tries to detect the disks (the RAID array) and the whole system hangs.
I've tried to relocate the two SATA hard disks to the SB600 controller (SATA 1&2 ports), but the same thing happens (after changing the BIOS to disable extra RAID function and enable RAID mode on onboard SATA SB600). The only way to POST the machine, is to remove the RocketRAID PCI card, but this way I can no longer boot my Linux disk.
Using BIOS 1.2 and 1.3beta 2 (sent to me by MSI support).
Any help is greatly appreciated.

Thanks for the replies.
Now, I'm going to surprise you: I managed to make both cards (the Promise and HighPoint) work together! Read how...
Somehow, I got the impression that the problems I had were either caused by the BIOS or the hard disks (the SATA ones). I flashed the motherboard back to the official 1.2, doing a complete BIOS reset (removed the battery) and tried again without the RocketRAID card installed. This time, the Promise BIOS (which btw is an earlier version from the one the 1.3b2 BIOS had) reported that the one SATA drive was malfunctioning (and it was a sealed brand-new Seagate). Removed the drive, installed it on SB600 and SeaTools indeed reported that it was failing (it didn't manage to pass even the quick test...).
Now I was curious: could it be that this - together with the beta BIOS - was the cause of my problems? I installed the other SATA disk to Promise T3 (the red socket) and the controller detected it, but all I could do is to set it up as a RAID 0 array (which pretty much does nothing). Next, I installed the RocketRAID also together with the IDE Linux disk and the system detected both disks; I can boot Linux fine and enter both the RocketRAID BIOS and Promise T3 BIOS. I can delete and recreate the array in Promise T3 as I please, but due to the fact that I only have one SATA disk now, I get limited options (RAID 0 and JBOD).
Is it safe to assume that since the Promise BIOS is working with the RocketRAID installed, that my SATA RAID controller is working?
Tomorrow, I shall return the SATA drive to the store I bought it and get a replacement, so that I can set up my RAID 1.
The plan is to have Linux boot from the IDE (I've never managed to set up a Linux disk to boot from RAID) where Windows Server 2003 will boot from RAID.
Will keep you posted about the progress I make.
BTW Bas, I'm sorry I couldn't make out much of your brainstorming
Regarding the Promise controller: the board has a Promise chip right above the SATA ports, which has the number 42819 on it. I can also verify that both SB600 RAID and Promise T3 RAID have EXACTLY the same BIOS menu interface (the only differences are the texts "ATi SB600" and "Promise T3" on the menus, plus that the SB600 has also an option to securely erase the drives which Promise does not have). Are you suggesting that the SB600 RAID is actually the Promise T3? I do not know if it would be possible to have BOTH RAID controllers (SB600 and T3) working at the same time (I do not have enough disks to try...).

PCI IDE BusMaster ??? For what use?

Hi to all,
This should be an interpretation problem of the description found in the manual for the "PCI IDE BusMaster" feature in the BIOS. The manual says: "Set this option to Enabled to specify that the IDE controller on the PCI local
bus has bus mastering capability. Setting options: Disabled, Enabled.". So my question is: Does this feature gets into action when its enabled and an IDE controller (wich I don't have) is plugged into one of the PCI slots or the feature acts on the onboard IDE controller ICH5 ??? Maybe it is better to have it always enabled.

Unless you are using a PCI IDE card, leave it disabled. I leave it disabled and my Promise IDE card enables it on it's own.
There is a good, if somewhat dated, description on this web site.

Neo2 Platinum discovery - BIOSes above 1.5 don't like internal IDE cards

I upgraded my BIOS tonight from 1.5 to 1.B only to discover my system wouldn't boot. I thought it was a problem with my SATA drive, so I disconnected all my other drives, and it worked. Because I was having several other problems with this BIOS, even when it was working, I downgraded to 1.9, but the same thing happened: with all my hard drives connected, my system wouldn't boot into Windows. After the DMI prefetch check, it just sat there like a lame goose. I disconnected my hard drives one by one to see which was the culprit, only to discover that the two drives connected to my Promise internal ATA100 IDE card were causing the problem. If those two drives were not connected, the machine booted normally, but when they were connected, the machine hung at start up.
I proceeded to try this for 1.8 and 1.7 with the same results. Only 1.5 seemed to work with my IDE card. I switched around PCI slots, turned off my ethernet slots (I was intermittently getting a Realtek ethernet jack error, which would also prevent me from loading up. This even happened in 1.5, but disabling that got rid of the problem. I use wireless anyway.)
Anyone know why this is the case? I suppose that it is not inherently PCI IDE cards that the BIOSes don't like, but the existence of hard drives on external channels. Because if I disconnect the hard drives from the card, there is no problem, and the OS boots normally.
I have heard of one other person in this forum having this problem, but I don't have the luxury of plugging my extra hard drives in internally.
Thanks in advance for the help/experience.

Quote
Thanks for that guide :-) Found it
Changing the agp voltage to 1.60 (From 1.50) had no effect
The Os is reused (working correctly on any other p.c), any time I try to clean install a new Windows Xp I get "Files not found" errors when it comes to installing any software it extracted to my drive
So far as I know the Nvidia Ide sw driver is not loaded, however it's one of those things I wouldn't know where to look to check pre-os
Chnaging to LBA from auto had no effect on my problem
All in all this has me stumped
(Edit: Congratulations on hitting the big 5000 posts )
Sorry nothing seems to work . I'm stumped too since you have had this rig running .
If you have warranty still valid perhaps you should have the board replaced .
Didn't notice I rounded the 5K

K9vgm-v problem with pci ide controller card

My problem is with a promise ultra100 tx2 pci ide controller card that I got with a western digital hard drive a year or 2 back. I can plug the card in with no hard drives attached to it, boot into windows, update the drivers, etc. but when I plug either of my hard drives into the card, it goes to a black screen directly after the screen the promise controller brings up after the main msi bios screen.
It's my understanding that this problem is caused because the ide controller card can't inject its bios into the option rom of the motherboard. I've tried disabling as many other features that I can in the bios to clear up some space in the option rom, but so far no luck. I made sure I have the latest MSI bios, but I am 1 or 2 revisions behind on the promise controller card bios, because I don't have a floppy drive and I can't get any bootable cds to work.
If need be, I can get a new ide controller card, but I would rather not, because this one works just fine, and I am pretty short on cash. I am also worried that this same problem will happen with other controller cards that I pick up. Any advice on how to get this thing working?
P.S. - is there any way to get this board to boot from a USB key? My only options in the bios for booting to USB are USB-FDD, USB-ZIP, and USB-CDROM.
-MSI k9vgm-v
-phoenix rev 1.2 (I think. Can't remember. Whatever liveupdate says is the newest)
-AMD Athlon 64 3200+
-512 MB Wintec Ampo memory
-onboard video
-Enermax 370watt noisetaker
3.3v 30A
5v 32A
12v 1 14A
12v 2 13A
-ide hard drive as primary master (windows drive)
DVD-RW as primary slave
ide hard drive as secondary master (raid drive 1)
ide hard drive on ide controller card primary master (raid drive 2)
ide hard drive on ide controller card secondary master (raid drive 3)
-Windows XP Pro SP2

"My problem is with a promise ultra100 tx2 pci ide controller card that I got with a western digital hard drive a year or 2 back. I can plug the card in with no hard drives attached to it, boot into windows, update the drivers, etc. but when I plug either of my hard drives into the card, it goes to a black screen directly after the screen the promise controller brings up after the main msi bios screen."
That means reboot cycle?
Have you tried with more powerfull PSU?
"P.S. - is there any way to get this board to boot from a USB key? My only options in the bios for booting to USB are USB-FDD, USB-ZIP, and USB-CDROM."
USB-FDD, USB-ZIP or in HDD area.. depend how will be detected your USB key.
"It's my understanding that this problem is caused because the ide controller card can't inject its bios into the option rom of the motherboard. I've tried disabling as many other features that I can in the bios to clear up some space in the option rom, but so far no luck. I made sure I have the latest MSI bios, but I am 1 or 2 revisions behind on the promise controller card bios, because I don't have a floppy drive and I can't get any bootable cds to work."
Could be...
"If need be, I can get a new ide controller card, but I would rather not, because this one works just fine, and I am pretty short on cash. I am also worried that this same problem will happen with other controller cards that I pick up. Any advice on how to get this thing working?"
"-phoenix rev 1.2 (I think. Can't remember. Whatever liveupdate says is the newest)"
Check the exact version. Latest version is 1.6, if there is an conflict that raid card unable to register property like(No enough Space to copy PCI Option ROM or similar) a new bios can help.

PCI IDE or SATA Card for HD

I've got a 450Mhz B&W G3 and I'm looking to replace the hard drive because the 30 gig in it is really loud. I've done some searching through here and online, seems people are still recommending the ACARD AEC-6280M card. Finding a google result that isn't a few years old is difficult.
Is this still the only card anyone recommends? I won't be touching OS 8 or 9, and won't ever have anything older than 10.3 on the computer. I think $55 is too much to spend, and I wouldn't even recycle it in another computer in the future.
So my question is, are their any cheaper IDE cards that work? How about SATA, perhaps those are more Mac compatable? The PCI bus is a standardized bus, so is the lack of Mac support all to blame on Apple?

I don't think the Acard AEC-6260M supports 48-bit LBA, so there would be the same practical limit of using a 120 GB drive or smaller. Assuming that his G3-450 has the Rev. 2 motherboard, the onboard IDE controller can handle the same capacity drive. For pre-B&W G3 Macs, those cards are the best deal out there. As for hard drives, this Seagate 120 GB is also a good deal, assuming that they're able to replenish their stock. It's getting more difficult to find relatively small hard drives (less than 160 GBs) now, as the need for mega-sized drives to store audio and/or video files has become commonplace.

Startup gets 'Network cable unplugged' on mini-PCI wireless card

I recently installed a Netgear DG834GT wireless router and now have an intermittent problem connecting my Tecra 9100 to it. If the 9100 has been shutdown for a while (like overnight), when I restart I always get 'Network cable unplugged' for the wireless connection. Rebooting a number of times (anything from 3 upwards) I eventually get connected to the router and all then works fine for hours. Even a quick restart at this point (i.e. once the wireless card has connected) does not cause a problem but as soon as I leave the machine shutdown for a length of time it fails again at reboot.
There are no errors in the Event log.
I am using the built in mini-PCI wireless card and have already upgraded to the latest driver.
Any ideas gratefully recieved, at the moment each morning is a 20-30 minute frustration of rebooting trying to get my connection working.
(Running Win2K Professional)

Checking other boards for help (Netgear etc.) it seems that the 'Network cable unplugged' is a common message when wireless connectivity is failing. However, to prove the point, I have disabled the other LAN card (for which I was also getting 'network cable unplugged' but as expected since it was). I still get the same issue with the wireless card, although now the reboots are slightly more predictable - it normally seems to succeed on the third reboot. I guess disabling the other card has changed the startup timing slightly and in that way made things slightly better.
Again, any other suggestions gratefully received. As this seems to be a timing issue at startup, I am suspicious that one of the other things that runs at that time is causing the problem.

Startup gets 'Network cable unplugged' on mini-PCI wireless card (again)

Reposting as previous topic has been locked although has not been resolved. Original post below, please see previous post for more details
I recently installed a Netgear DG834GT wireless router and now have an intermittent problem connecting my Tecra 9100 to it. If the 9100 has been shutdown for a while (like overnight), when I restart I always get 'Network cable unplugged' for the wireless connection. Rebooting a number of times (anything from 3 upwards) I eventually get connected to the router and all then works fine for hours. Even a quick restart at this point (i.e. once the wireless card has connected) does not cause a problem but as soon as I leave the machine shutdown for a length of time it fails again at reboot.
There are no errors in the Event log.
I am using the built in mini-PCI wireless card and have already upgraded to the latest driver.
Any ideas gratefully recieved, at the moment each morning is a 20-30 minute frustration of rebooting trying to get my connection working.
(Running Win2K Professional)

More info : I have found that this is time related rather than related to the number of reboots. It always fails on the first reboot after being shut down for a period of time. At this point, however long I wait the connection never comes up. However, if I wait a few minutes and then reboot, the second reboot will always successfully establish the connection.
On this basis, the problem has become slightly less annoying as I have a workaround - boot once, wait a few minutes and reboot. That being said, any information on how I can isolate this further (e.g. tracing what is running at startup) would be gratefully recieved.

Problem with KTV3 and PCI USB card extension from QTEC type 13068

Hello all,
I have been trying to make work a PCI USB card extension from QTEC type 13068. This card allows to give 4 USB ports more.
My problem is that oinly 2 ports are working and WINXP SP1 is saying that there are not enough ressources for all the PCI functions. However there is enough free IRQ. Even using this card alone on the mainboard give the same error.
I am using a KTV3 (MS-6712 VER:1.0A) and I have no idear why this is happening. Could it be a bad interaction between the BIOS and the card? wall Or WIN XP? angryfire
All comments and ideas to try are welcome especially from those who have this QTEC card.
Regards.

What operating system are you using? The card requires SP1 for XP and SP4 for 2000. If you have these, try to uninstal the cardl and let Windows reinstall the card on start-up.

Does NI DAQmx driver support PCI 6527 Card

In my application i am using PCI 6527 Isolated DIO Card. In the examples from LabVIEW 7.0, i refered the following VIs
1. Write Dig Chan.vi
2. Write Dig Port.vi
using DAQ 7 Driver.
There it gives a list of devices that can run these examples. The list does not contains PCI 6527.
Can I use DAQmx Example VIs with PCI 6527 Card?
Please suggest me what driver to use with 6527 Card (Traditional DAQ or DAQmx).

Hello partners,
I'm using NI DAQmx 9.7 in a machine hosting a Windows 7, but always when I tried to run the application I got this error.:
CAN'T LOCATE THE DRIVER ERROR 10240
Does you have any idea why could I'm facing this problem ? Previously I was using the original driver NI DAQ 7.4.4 (Legacy) in a machine hosting a Windows XP.
Other point perhaps here isn't the best place to start this new post, but I couldn't find how to post a new topic on the site.. My apologies, i'm waiting for any solution or advice
Best Regards
Josias Junior

Maximum number of PCI-6602 cards in 1 computer?

Is it possible to have 4 PCI-6602 cards in 1 computer?
Are there any DMA channels or IRQ limitations we need
to worry about?
Our computer will have 1 graphics card in the AGP slot,
possibly a PCI NIC ethernet card and possibly a PCI
based sound card. It will also have an IDE controller
with 2 hard drives and 1 CDRW.
The PCI-6602 manual seems to imply that if you are
using more than 3 counter channels that you must
use the slower Interrupt based transfer mode which
has a maximum transfer rate specified as 2000
Reading/second. If there are 4 PCI-6602 boards in
the same computer and all 8 of the channels are
used on each board does that mean the total
transfer rate is still 2000 Readings/sec? Or
wo
uld the total transfer rate be 8000 Readings/Sec
since there are 4 PCI-6602's (2000 Readings/Sec
for each of the 4 PCI-6602's)?

Hello;
The only concern you need to have is the number of IRQs available. As far as DMA channels, as the PCI bus itself has only 3 DMA channels available, all the devices that use DMA will share those 3 channels. But, as IRQs can't be shared, the number of counters you will be able to use will be the exact number of available IRQs you still have on your machine.
As far as transfer rate, the maximum transfer rate will be 2000 Readings/sec, regardless the number of counters you are using.
Hope this helps.
Filipe

Can't get PCI VXI card to initialize on CentOS 5 (Fedora Core 5)

I am trying to configure a pci-vxi card on our new machine. We have an Intel MB (DG965WH) and the Q6600 Core2 Quad processor. The OS is CentOS 5 (Fedora Core 5) with kernel 2.6.18-53.1.4.el5.
I have read all the other posts concerning Fedora Core 5 and have modified the source code to fix the compile errors in the driver. The following lists the output I am getting:
when running make:
make -C /lib/modules/2.6.18-53.1.4.el5/build SUBDIRS=/usr/local/nivxi/src KBUILD_VERBOSE=0 modules
make[1]: Entering directory `/usr/src/kernels/2.6.18-53.1.4.el5-i686'
CC [M] /usr/local/nivxi/src/vxi.o
CC [M] /usr/local/nivxi/src/vxi_kernel.o
CC [M] /usr/local/nivxi/src/pci_io.o
CC [M] /usr/local/nivxi/src/mutex.o
CC [M] /usr/local/nivxi/src/vxiTimer.o
LD [M] /usr/local/nivxi/src/vximod.o
Building modules, stage 2.
MODPOST
WARNING: could not find /usr/local/nivxi/src/.nivxi.o.cmd for /usr/local/nivxi/src/nivxi.o
CC /usr/local/nivxi/src/vximod.mod.o
LD [M] /usr/local/nivxi/src/vximod.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.18-53.1.4.el5-i686'
Kernel module built successfully and placed in ../sys/
Use /usr/local/nivxi/src/../sys/load_vxi to load it.
When running load_vxi:
NI-VXI device driver located in "/usr/local/nivxi/sys"
When running vxiinit:
Unable to initialize hardware
dmesg output:
VXI: initialized
[drm] Initialized drm 1.0.1 20051102
ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 177
[drm] Initialized i915 1.8.0 20060929 on minor 0
VXI: unloaded
VXI: initialized
From /var/log/messages:
Dec 21 09:55:02 lion kernel: VXI: unloaded
Dec 21 09:55:07 lion kernel: VXI: initialized
No matter what I do I cannot get vxiinit to initialize the device. The device itself is listed
in the /dev directory as vxi0 where "0" is the number zero. On another machine we have
running CentOS 4.5 the device is listed as vxiO. where "O" is the capital letter O. The
device works fine on this machine.
I am not sure what I should try next. Any suggestions would be greatly appreciated.
Thanks,
Greg

Howdy Greg,
I've been researching your issue extensively over the past day and unfortunately
found your Fedora distribution has not been officially tested and verified for
functionality (assuming you're using a MXI 2, check out the VIX for Linux page). That
being said, I was able to find some other Discussion Forum posts dealing with
hacking VXI to work on Fedora. I know you said you read up on this, but I
wanted to post them anyways just in case.
VXI
Drivers on Fedora Core 5
- This is quite a long post dealing with similar errors to
what you are seeing
NI-VXI for Linux Hangs on SMP/Hyperthreaded Machines with APIC
Enabled
- A KnowledgeBase article linked in the previous thread
Fedora
Core 5 - kernel 2.6.20 -NIKAL 1.5 How To
- This one is kind of a long shot since it's for our MultifunctionDAQ drivers
and not VXI, but check it out anyways to see if it gives you any ideas.
Let me know how these worked for you and if you have any
follow up questions. Good luck.
Sincerely,
Chris G in AE
Sincerely,
Chris G in AE

[SOLVED] kernel crash with PCI wifi card

HI,
I id install and start to use arch just two weeks ago :-)
I was able to solve problems until now.
I am not sure if this is problem of arch kernel, maybe it will be general.
I did insert PCI wifi card to my PC with arch. Card is Z-COM XI-626 : LAST LINE:
lspci
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5)
00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5)
00:1c.6 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 7 (rev b5)
00:1c.7 PCI bridge: Intel Corporation 82801 PCI Bridge (rev b5)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation H67 Express Chipset Family LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
03:00.0 IDE interface: VIA Technologies, Inc. VT6415 PATA IDE Host Controller
04:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
06:00.0 PCI bridge: ASMedia Technology Inc. ASM108x PCIe to PCI Bridge Controller (rev 01)
07:00.0 Network controller: Intersil Corporation ISL3874 [Prism 2.5]/ISL3872 [Prism 3] (rev 01)
It start to work very nicely, I could connect to the network with NetworkManager in gnome.
BUT
after while connection is not working.
the is in message LOG:
Dec 6 07:53:09 localhost NetworkManager[686]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Dec 6 07:53:09 localhost NetworkManager[686]: <info> Activation (wlan0) Stage 4 of 5 (IP6 Configure Timeout) complete.
Dec 6 07:53:09 localhost NetworkManager[686]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Dec 6 07:53:10 localhost NetworkManager[686]: <info> (wlan0): device state change: ip-config -> activated (reason 'none') [70 100 0]
Dec 6 07:53:10 localhost NetworkManager[686]: <info> Policy set 'Auto moje_wifi' (wlan0) as default for IPv4 routing and DNS.
Dec 6 07:53:10 localhost NetworkManager[686]: <info> Activation (wlan0) successful, device activated.
Dec 6 07:53:10 localhost NetworkManager[686]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Dec 6 07:53:10 localhost dbus[661]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Dec 6 07:53:10 localhost dbus[661]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dec 6 08:02:58 localhost kernel: [ 1889.872241] Pid: 0, comm: swapper Tainted: G C 3.1.4-1-ARCH #1
Dec 6 08:02:58 localhost kernel: [ 1889.872243] Call Trace:
Dec 6 08:02:58 localhost kernel: [ 1889.872244] <IRQ> [<ffffffff810c6cfd>] __report_bad_irq+0x3d/0xe0
Dec 6 08:02:58 localhost kernel: [ 1889.872252] [<ffffffff810c713d>] note_interrupt+0x14d/0x210
Dec 6 08:02:58 localhost kernel: [ 1889.872255] [<ffffffff810c5079>] handle_irq_event_percpu+0xc9/0x2a0
Dec 6 08:02:58 localhost kernel: [ 1889.872257] [<ffffffff810c5298>] handle_irq_event+0x48/0x70
Dec 6 08:02:58 localhost kernel: [ 1889.872259] [<ffffffff810c7a7a>] handle_fasteoi_irq+0x5a/0xe0
Dec 6 08:02:58 localhost kernel: [ 1889.872262] [<ffffffff81016992>] handle_irq+0x22/0x40
Dec 6 08:02:58 localhost kernel: [ 1889.872265] [<ffffffff8140d01a>] do_IRQ+0x5a/0xe0
Dec 6 08:02:58 localhost kernel: [ 1889.872268] [<ffffffff81409c6e>] common_interrupt+0x6e/0x6e
Dec 6 08:02:58 localhost kernel: [ 1889.872269] <EOI> [<ffffffff8131d3aa>] ? poll_idle+0x3a/0x80
Dec 6 08:02:58 localhost kernel: [ 1889.872273] [<ffffffff8131d383>] ? poll_idle+0x13/0x80
Dec 6 08:02:58 localhost kernel: [ 1889.872275] [<ffffffff8131d756>] cpuidle_idle_call+0xc6/0x350
Dec 6 08:02:58 localhost kernel: [ 1889.872277] [<ffffffff81013229>] cpu_idle+0xc9/0x120
Dec 6 08:02:58 localhost kernel: [ 1889.872280] [<ffffffff813e6912>] rest_init+0x96/0xa4
Dec 6 08:02:58 localhost kernel: [ 1889.872282] [<ffffffff8194fc15>] start_kernel+0x3bf/0x3cc
Dec 6 08:02:58 localhost kernel: [ 1889.872285] [<ffffffff8194f347>] x86_64_start_reservations+0x132/0x136
Dec 6 08:02:58 localhost kernel: [ 1889.872287] [<ffffffff8194f140>] ? early_idt_handlers+0x140/0x140
Dec 6 08:02:58 localhost kernel: [ 1889.872289] [<ffffffff8194f44d>] x86_64_start_kernel+0x102/0x111
Dec 6 08:03:05 localhost NetworkManager[686]: <info> (wlan0): roamed from BSSID 00:19:0A:01:1A:66 (moje_wifi) to (none) ((none))
Dec 6 08:03:05 localhost kernel: [ 1896.943757] wlan0: interrupt delivery does not seem to work
Dec 6 08:03:07 localhost kernel: [ 1898.942477] wlan0: interrupt delivery does not seem to work
Dec 6 08:03:10 localhost kernel: [ 1902.180399] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:12 localhost kernel: [ 1904.179118] wlan0: interrupt delivery does not seem to work
Dec 6 08:03:14 localhost kernel: [ 1906.177838] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:16 localhost kernel: [ 1908.176557] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:18 localhost kernel: [ 1910.175277] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:20 localhost kernel: [ 1912.173997] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:22 localhost kernel: [ 1914.172716] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:24 localhost kernel: [ 1916.171436] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:26 localhost kernel: [ 1918.170157] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:28 localhost kernel: [ 1920.168875] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:30 localhost kernel: [ 1922.167595] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:32 localhost kernel: [ 1924.166315] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:32 localhost kernel: [ 1924.279547] ------------[ cut here ]------------
Dec 6 08:03:32 localhost kernel: [ 1924.279553] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x257/0x260()
Dec 6 08:03:32 localhost kernel: [ 1924.279555] Hardware name: System Product Name
Dec 6 08:03:32 localhost kernel: [ 1924.279556] NETDEV WATCHDOG: wifi0 (hostap_pci): transmit queue 0 timed out
Dec 6 08:03:32 localhost kernel: [ 1924.279558] Modules linked in: fuse ext2 mbcache snd_hda_codec_hdmi orinoco_pci orinoco cfg80211 snd_hda_codec_realtek i915 drm_kms_helper drm i2c_i801 hostap_pci hostap i2c_algo_bit i2c_core eeepc_wmi asus_wmi sparse_keymap rfkill psmouse pci_hotplug serio_raw snd_hda_intel mei(C) snd_hda_codec iTCO_wdt iTCO_vendor_support snd_hwdep snd_pcm snd_timer snd evdev r8169 mii pcspkr intel_agp intel_gtt button video lib80211 wmi processor soundcore snd_page_alloc btrfs zlib_deflate crc32c libcrc32c hid_a4tech usbhid hid sd_mod ahci pata_acpi libahci pata_via libata xhci_hcd ehci_hcd scsi_mod usbcore
Dec 6 08:03:32 localhost kernel: [ 1924.279599] Pid: 0, comm: swapper Tainted: G C 3.1.4-1-ARCH #1
Dec 6 08:03:32 localhost kernel: [ 1924.279600] Call Trace:
Dec 6 08:03:32 localhost kernel: [ 1924.279602] <IRQ> [<ffffffff81061b9f>] warn_slowpath_common+0x7f/0xc0
Dec 6 08:03:32 localhost kernel: [ 1924.279610] [<ffffffff81025047>] ? intel_pmu_enable_all+0xa7/0x110
Dec 6 08:03:32 localhost kernel: [ 1924.279612] [<ffffffff81061c96>] warn_slowpath_fmt+0x46/0x50
Dec 6 08:03:32 localhost kernel: [ 1924.279615] [<ffffffff8107e472>] ? __queue_work+0xe2/0x490
Dec 6 08:03:32 localhost kernel: [ 1924.279617] [<ffffffff81364377>] dev_watchdog+0x257/0x260
Dec 6 08:03:32 localhost kernel: [ 1924.279620] [<ffffffff81071e61>] run_timer_softirq+0x131/0x440
Dec 6 08:03:32 localhost kernel: [ 1924.279622] [<ffffffff81364120>] ? qdisc_reset+0x50/0x50
Dec 6 08:03:32 localhost kernel: [ 1924.279624] [<ffffffff8101c139>] ? read_tsc+0x9/0x20
Dec 6 08:03:32 localhost kernel: [ 1924.279626] [<ffffffff810691c0>] __do_softirq+0xb0/0x270
Dec 6 08:03:32 localhost kernel: [ 1924.279629] [<ffffffff81096158>] ? tick_dev_program_event+0x48/0x110
Dec 6 08:03:32 localhost kernel: [ 1924.279631] [<ffffffff8109623f>] ? tick_program_event+0x1f/0x30
Dec 6 08:03:32 localhost kernel: [ 1924.279634] [<ffffffff8140c76c>] call_softirq+0x1c/0x30
Dec 6 08:03:32 localhost kernel: [ 1924.279637] [<ffffffff81016a15>] do_softirq+0x65/0xa0
Dec 6 08:03:32 localhost kernel: [ 1924.279639] [<ffffffff810696ce>] irq_exit+0x9e/0xc0
Dec 6 08:03:32 localhost kernel: [ 1924.279641] [<ffffffff8140d10e>] smp_apic_timer_interrupt+0x6e/0x99
Dec 6 08:03:32 localhost kernel: [ 1924.279643] [<ffffffff8140afde>] apic_timer_interrupt+0x6e/0x80
Dec 6 08:03:32 localhost kernel: [ 1924.279644] <EOI> [<ffffffff81279e9b>] ? intel_idle+0xcb/0x120
Dec 6 08:03:32 localhost kernel: [ 1924.279649] [<ffffffff81279e7d>] ? intel_idle+0xad/0x120
Dec 6 08:03:32 localhost kernel: [ 1924.279651] [<ffffffff8131d756>] cpuidle_idle_call+0xc6/0x350
Dec 6 08:03:32 localhost kernel: [ 1924.279654] [<ffffffff81013229>] cpu_idle+0xc9/0x120
Dec 6 08:03:32 localhost kernel: [ 1924.279657] [<ffffffff813e6912>] rest_init+0x96/0xa4
Dec 6 08:03:32 localhost kernel: [ 1924.279659] [<ffffffff8194fc15>] start_kernel+0x3bf/0x3cc
Dec 6 08:03:32 localhost kernel: [ 1924.279662] [<ffffffff8194f347>] x86_64_start_reservations+0x132/0x136
Dec 6 08:03:32 localhost kernel: [ 1924.279664] [<ffffffff8194f140>] ? early_idt_handlers+0x140/0x140
Dec 6 08:03:32 localhost kernel: [ 1924.279666] [<ffffffff8194f44d>] x86_64_start_kernel+0x102/0x111
Dec 6 08:03:32 localhost kernel: [ 1924.279668] ---[ end trace 6f3b132eb24e1d2e ]---
Dec 6 08:03:32 localhost kernel: [ 1924.279669] wifi0 Tx timed out! Resetting card
Dec 6 08:03:32 localhost kernel: [ 1924.279694] hostap_pci: wifi0: resetting card
Dec 6 08:03:34 localhost kernel: [ 1926.278267] wifi0 Tx timed out! Resetting card
Dec 6 08:03:36 localhost kernel: [ 1928.163754] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:36 localhost kernel: [ 1928.276987] wifi0 Tx timed out! Resetting card
Dec 6 08:03:38 localhost kernel: [ 1930.162473] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:38 localhost kernel: [ 1930.222552] hostap_pci: wifi0: already resetting card - ignoring reset request
Dec 6 08:03:38 localhost kernel: [ 1930.262615] hostap_pci: wifi0: already resetting card - ignoring reset request
Dec 6 08:03:38 localhost kernel: [ 1930.262619] wifi0: Port type setting to 1 failed
Dec 6 08:03:38 localhost kernel: [ 1930.275703] wifi0 Tx timed out! Resetting card
Dec 6 08:03:40 localhost kernel: [ 1932.261129] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:40 localhost kernel: [ 1932.261131] wifi0: MAC port 0 enabling failed
Dec 6 08:03:40 localhost kernel: [ 1932.261150] hostap_pci: wifi0: resetting card
Dec 6 08:03:43 localhost kernel: [ 1934.463052] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:43 localhost kernel: [ 1934.463064] hostap_pci: wifi0: already resetting card - ignoring reset request
Dec 6 08:03:45 localhost kernel: [ 1936.461771] wifi0: interrupt delivery does not seem to work
Dec 6 08:03:45 localhost kernel: [ 1936.501864] hostap_pci: wifi0: already resetting card - ignoring reset request
Dec 6 08:03:45 localhost kernel: [ 1936.501866] wifi0: Port type setting to 1 failed
Dec 6 08:03:45 localhost kernel: [ 1936.521925] wifi0: MAC port 0 enabling failed
Dec 6 08:04:13 localhost kernel: [ 1964.923031] hostap_pci: wlan0: resetting card
Dec 6 08:04:15 localhost kernel: [ 1967.125469] wlan0: interrupt delivery does not seem to work
Dec 6 08:04:15 localhost kernel: [ 1967.125474] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:04:17 localhost kernel: [ 1969.124179] wifi0: interrupt delivery does not seem to work
Dec 6 08:04:17 localhost kernel: [ 1969.164257] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:04:17 localhost kernel: [ 1969.164259] wlan0: Port type setting to 1 failed
Dec 6 08:04:17 localhost kernel: [ 1969.184273] wlan0: MAC port 0 enabling failed
Dec 6 08:06:13 localhost kernel: [ 2084.846529] hostap_pci: wlan0: resetting card
Dec 6 08:06:15 localhost kernel: [ 2087.048638] wlan0: interrupt delivery does not seem to work
Dec 6 08:06:15 localhost kernel: [ 2087.048649] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:06:17 localhost kernel: [ 2089.047356] wifi0: interrupt delivery does not seem to work
Dec 6 08:06:17 localhost kernel: [ 2089.087406] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:06:17 localhost kernel: [ 2089.087407] wlan0: Port type setting to 1 failed
Dec 6 08:06:17 localhost kernel: [ 2089.107404] wlan0: MAC port 0 enabling failed
Dec 6 08:08:13 localhost kernel: [ 2204.769302] hostap_pci: wlan0: resetting card
Dec 6 08:08:15 localhost kernel: [ 2206.971827] wlan0: interrupt delivery does not seem to work
Dec 6 08:08:15 localhost kernel: [ 2206.971832] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:08:17 localhost kernel: [ 2208.970532] wifi0: interrupt delivery does not seem to work
Dec 6 08:08:17 localhost kernel: [ 2209.010630] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:08:17 localhost kernel: [ 2209.010634] wlan0: Port type setting to 1 failed
Dec 6 08:08:19 localhost kernel: [ 2211.009274] wlan0: interrupt delivery does not seem to work
Dec 6 08:08:19 localhost kernel: [ 2211.009275] wlan0: MAC port 0 enabling failed
Dec 6 08:10:13 localhost kernel: [ 2324.691574] hostap_pci: wlan0: resetting card
Dec 6 08:10:15 localhost kernel: [ 2326.891711] wlan0: interrupt delivery does not seem to work
Dec 6 08:10:15 localhost kernel: [ 2326.891716] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:10:17 localhost kernel: [ 2328.890393] wifi0: interrupt delivery does not seem to work
Dec 6 08:10:17 localhost kernel: [ 2328.930472] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:10:17 localhost kernel: [ 2328.930473] wlan0: Port type setting to 1 failed
Dec 6 08:10:17 localhost kernel: [ 2328.950482] wlan0: MAC port 0 enabling failed
Dec 6 08:12:13 localhost kernel: [ 2444.616669] hostap_pci: wlan0: resetting card
Dec 6 08:12:15 localhost kernel: [ 2446.818212] wlan0: interrupt delivery does not seem to work
Dec 6 08:12:15 localhost kernel: [ 2446.818218] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:12:17 localhost kernel: [ 2448.816887] wifi0: interrupt delivery does not seem to work
Dec 6 08:12:17 localhost kernel: [ 2448.856917] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:12:17 localhost kernel: [ 2448.856919] wlan0: Port type setting to 1 failed
Dec 6 08:12:17 localhost kernel: [ 2448.876938] wlan0: MAC port 0 enabling failed
Dec 6 08:14:13 localhost kernel: [ 2564.540113] hostap_pci: wlan0: resetting card
Dec 6 08:14:15 localhost kernel: [ 2566.741388] wlan0: interrupt delivery does not seem to work
Dec 6 08:14:15 localhost kernel: [ 2566.741394] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:14:17 localhost kernel: [ 2568.740062] wifi0: interrupt delivery does not seem to work
Dec 6 08:14:17 localhost kernel: [ 2568.780120] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:14:17 localhost kernel: [ 2568.780121] wlan0: Port type setting to 1 failed
Dec 6 08:14:17 localhost kernel: [ 2568.800135] wlan0: MAC port 0 enabling failed
Dec 6 08:16:13 localhost kernel: [ 2684.463514] hostap_pci: wlan0: resetting card
Dec 6 08:16:15 localhost kernel: [ 2686.664525] wlan0: interrupt delivery does not seem to work
Dec 6 08:16:15 localhost kernel: [ 2686.664530] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:16:17 localhost kernel: [ 2688.663241] wifi0: interrupt delivery does not seem to work
Dec 6 08:16:17 localhost kernel: [ 2688.703314] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:16:17 localhost kernel: [ 2688.703315] wlan0: Port type setting to 1 failed
Dec 6 08:16:17 localhost kernel: [ 2688.723340] wlan0: MAC port 0 enabling failed
Dec 6 08:18:13 localhost kernel: [ 2804.386357] hostap_pci: wlan0: resetting card
Dec 6 08:18:15 localhost kernel: [ 2806.587699] wlan0: interrupt delivery does not seem to work
Dec 6 08:18:15 localhost kernel: [ 2806.587704] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:18:17 localhost kernel: [ 2808.586422] wifi0: interrupt delivery does not seem to work
Dec 6 08:18:17 localhost kernel: [ 2808.626468] hostap_pci: wlan0: already resetting card - ignoring reset request
Dec 6 08:18:17 localhost kernel: [ 2808.626471] wlan0: Port type setting to 1 failed
Dec 6 08:18:19 localhost kernel: [ 2810.625118] wlan0: interrupt delivery does not seem to work
Dec 6 08:18:19 localhost kernel: [ 2810.625121] wlan0: MAC port 0 enabling failed
please, have anybody idea what is wrong?
thanks for help / tips ...
Last edited by jancici (2012-03-21 08:47:06)

okay, I did blacklist hostap_pci, I did find out that with orinoco_pci module it is more stable
BUT
sometimes it hang up with same error message
Dec 6 23:03:45 localhost kernel: [ 2465.908317] ------------[ cut here ]------------
Dec 6 23:03:45 localhost kernel: [ 2465.908324] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x257/0x260()
Dec 6 23:03:45 localhost kernel: [ 2465.908326] Hardware name: System Product Name
Dec 6 23:03:45 localhost kernel: [ 2465.908328] NETDEV WATCHDOG: eth1 (orinoco_pci): transmit queue 0 timed out
Dec 6 23:03:45 localhost kernel: [ 2465.908329] Modules linked in: fuse ext2 mbcache snd_hda_codec_hdmi snd_hda_codec_realtek orinoco_pci orinoco r8169 cfg80211 mii
i915 drm_kms_helper drm snd_hda_intel evdev snd_hda_codec mei(C) i2c_algo_bit rfkill intel_agp psmouse wmi i2c_i801 i2c_core intel_gtt snd_hwdep snd_pcm button proc
essor video snd_timer snd soundcore snd_page_alloc btrfs zlib_deflate crc32c libcrc32c hid_a4tech usbhid hid sd_mod ahci pata_acpi libahci xhci_hcd pata_via libata e
hci_hcd scsi_mod usbcore
Dec 6 23:03:45 localhost kernel: [ 2465.908365] Pid: 0, comm: kworker/0:1 Tainted: G C 3.1.4-1-ARCH #1
Dec 6 23:03:45 localhost kernel: [ 2465.908366] Call Trace:
Dec 6 23:03:45 localhost kernel: [ 2465.908368] <IRQ> [<ffffffff81061b9f>] warn_slowpath_common+0x7f/0xc0
Dec 6 23:03:45 localhost kernel: [ 2465.908375] [<ffffffff81025047>] ? intel_pmu_enable_all+0xa7/0x110
Dec 6 23:03:45 localhost kernel: [ 2465.908378] [<ffffffff81061c96>] warn_slowpath_fmt+0x46/0x50
Dec 6 23:03:45 localhost kernel: [ 2465.908381] [<ffffffff810f1743>] ? perf_ctx_unlock+0x23/0x30
Dec 6 23:03:45 localhost kernel: [ 2465.908383] [<ffffffff81364377>] dev_watchdog+0x257/0x260
Dec 6 23:03:45 localhost kernel: [ 2465.908386] [<ffffffff81071e61>] run_timer_softirq+0x131/0x440
Dec 6 23:03:45 localhost kernel: [ 2465.908388] [<ffffffff81364120>] ? qdisc_reset+0x50/0x50
Dec 6 23:03:45 localhost kernel: [ 2465.908390] [<ffffffff8101c139>] ? read_tsc+0x9/0x20
Dec 6 23:03:45 localhost kernel: [ 2465.908392] [<ffffffff810691c0>] __do_softirq+0xb0/0x270
Dec 6 23:03:45 localhost kernel: [ 2465.908395] [<ffffffff81096158>] ? tick_dev_program_event+0x48/0x110
Dec 6 23:03:45 localhost kernel: [ 2465.908397] [<ffffffff8109623f>] ? tick_program_event+0x1f/0x30
Dec 6 23:03:45 localhost kernel: [ 2465.908400] [<ffffffff8140c76c>] call_softirq+0x1c/0x30
Dec 6 23:03:45 localhost kernel: [ 2465.908403] [<ffffffff81016a15>] do_softirq+0x65/0xa0
Dec 6 23:03:45 localhost kernel: [ 2465.908404] [<ffffffff810696ce>] irq_exit+0x9e/0xc0
Dec 6 23:03:45 localhost kernel: [ 2465.908407] [<ffffffff8140d10e>] smp_apic_timer_interrupt+0x6e/0x99
Dec 6 23:03:45 localhost kernel: [ 2465.908409] [<ffffffff8140afde>] apic_timer_interrupt+0x6e/0x80
Dec 6 23:03:45 localhost kernel: [ 2465.908410] <EOI> [<ffffffff81279e9b>] ? intel_idle+0xcb/0x120
Dec 6 23:03:45 localhost kernel: [ 2465.908415] [<ffffffff81279e7d>] ? intel_idle+0xad/0x120
Dec 6 23:03:45 localhost kernel: [ 2465.908417] [<ffffffff8131d756>] cpuidle_idle_call+0xc6/0x350
Dec 6 23:03:45 localhost kernel: [ 2465.908419] [<ffffffff81013229>] cpu_idle+0xc9/0x120
Dec 6 23:03:45 localhost kernel: [ 2465.908422] [<ffffffff813f8944>] start_secondary+0x202/0x209
Dec 6 23:03:45 localhost kernel: [ 2465.908424] ---[ end trace 58cac98ca8b4102b ]---
Dec 6 23:03:45 localhost kernel: [ 2465.908433] eth1: Tx timeout! ALLOCFID=0128, TXCOMPLFID=03eb, EVSTAT=808b
maybe I need some more modern card, something with atheros chipset ...

How do I configure my PCI-GPIB cards so that one is a controller and the other is a device being controlled by the first card

I have 2 PC's, both fitted with PCI-GPIB cards. One will be the system controller and the other will be a device on the GPIB bus. How do I configure both cards using LabWindows/CVI v7.0 to achieve this ? What commands are used to send and receive the data ?

Hi Pete,
For the controller board you don't really need to do anything. By default the GPIB interface is configured as controller.
The non-controller can be configured in MAX. Right-click on the interface, uncheck the ono-controller box and change the primary address. It is usually a good idea to set these parameters programatically. Use ibpad to set the primary address and ibrsc to release system control.
For the controller you can use a device descriptor (using ibdev) or a board descriptor (ibfind).
You can only open a reference to the non-controller board using ibfind (ibfind("gpib0"), for example). This will open a board reference. You cannot use a device reference because that implies that the board is capable of addressing the bus. On
ly the system controller can.
Here are some links I found on the web on this subject:
Passing GPIB Control -- System Controller vs. Controller In Charge
Tutorial: Programmatic File Transfers over the GPIB
Example: Using a C Program as a GPIB Non-Controller with LabVIEW as the GPIB Controller
Example: Serial Polling Between Two Computers (Controller and Non-controller)
Hope this helps.
DiegoF
National Instruments.

PCI IDE Cards

Similar Messages

Maybe you are looking for