PCI vs PCMCIA?

Hi,
sorry for the neewbie question: is PCI and PCMCIA the same thing? I want to connect the Belkin 802.11g F5D7000 PCI in the Pismo slot? will work without problems or I need some sort of adapter? I have these options for going WiFi, What card do you recommend for the Pismo?
a) Belkin F5D7000
b) Aztech WL830PC
c) D-Link AIR DWL-650
Thanks in advance..
PS: English isn't my first language, sorry...

imactor,
You have several ways to add WiFi to your Pismo, but these are the most convenient:
1. Buy a WiFi CardBus PC card for the PCMCIA/CardBus slot on the left side of the Pismo. As Tom stated, PCI cards are for desktop computers.
2. Buy the original Apple AirPort card that fits in a slot under the keyboard. You can only find these used (not new) and are limited to 802.11b 11Mbps speeds; no other card will work in this slot.
Here is what the card looks like:
http://eshop.macsales.com/item/Apple/M7600LLE/
Here is how it is installed:
http://docs.info.apple.com/article.html?artnum=50028
Now if you decide to buy a CardBus PC card, these are the things to consider:
- WiFi PC cards use a variety of wireless chipsets but only one chipset is compatible with Apple's onboard AirPort software and these cards use the "Broadcom" chipset. In addition, you must be running at least OSX 10.2.6 or newer and AirPort 3.1.1 or newer. There are not very many of these cards available but if you go to the link below, you may find one of these cards new or used in your part of the world:
http://bcm-specs.sipsolutions.net/Chipsets
- Or, you can use a third-party wireless driver like Orangeware's Wireless Driver for Mac. It supports PC cards that use the Atheros chipset and they have a very long list of cards which will work.
http://www.orangeware.com/endusers/wirelessformac.html
The Aztech WL830PC you listed will work with the Orangeware driver; as far as I know, the other cards have no drivers for the Mac.

Similar Messages

Modem on PCI TO PCMCIA adapter not working.

Hello,
I'm new here so please be gentle if im asking about something obvious. Like i wrote in subject i have problems on my desktop PC (not laptop) with my pcmcia Huwaei 870 modem wich is inserted into PCI TO PCMCIA adapter (Ricoh). On Windows(same machine - desktop PC) and on my laptop(old Acer) where i have Slack every things work magical fine but on my desktop Arch don't. Settings on both machines looks alike. Below some logs from Arch (desktop PC) just after when I pluged my modem.
kernel.log
Jun 21 11:20:33 arch pcmcia_socket pcmcia_socket0: pccard: CardBus card inserted into slot 0
Jun 21 11:20:33 arch pci 0000:04:00.0: reg 10 32bit mmio: [0x000000-0x000fff]
Jun 21 11:20:33 arch pci 0000:04:00.0: supports D1 D2
Jun 21 11:20:33 arch pci 0000:04:00.0: PME# supported from D0 D1 D2 D3hot
Jun 21 11:20:33 arch pci 0000:04:00.0: PME# disabled
Jun 21 11:20:33 arch pci 0000:04:00.1: reg 10 32bit mmio: [0x000000-0x0000ff]
Jun 21 11:20:33 arch pci 0000:04:00.1: supports D1 D2
Jun 21 11:20:33 arch pci 0000:04:00.1: PME# supported from D0 D1 D2 D3hot
Jun 21 11:20:33 arch pci 0000:04:00.1: PME# disabled
Jun 21 11:20:33 arch ohci_hcd 0000:04:00.0: enabling device (0000 -> 0002)
Jun 21 11:20:33 arch ohci_hcd 0000:04:00.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
Jun 21 11:20:33 arch ohci_hcd 0000:04:00.0: setting latency timer to 64
Jun 21 11:20:33 arch ohci_hcd 0000:04:00.0: OHCI Host Controller
Jun 21 11:20:33 arch ohci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 8
Jun 21 11:20:40 arch ohci_hcd 0000:04:00.0: USB HC takeover failed! (BIOS/SMM bug)
Jun 21 11:20:40 arch ohci_hcd 0000:04:00.0: can't setup
Jun 21 11:20:40 arch ohci_hcd 0000:04:00.0: USB bus 8 deregistered
Jun 21 11:20:40 arch ohci_hcd 0000:04:00.0: PCI INT A disabled
Jun 21 11:20:40 arch ohci_hcd 0000:04:00.0: init 0000:04:00.0 fail, -16
Jun 21 11:20:40 arch ohci_hcd: probe of 0000:04:00.0 failed with error -16
Jun 21 11:20:40 arch ehci_hcd 0000:04:00.1: enabling device (0000 -> 0002)
Jun 21 11:20:40 arch ehci_hcd 0000:04:00.1: PCI INT A -> GSI 22 (level, low) -> IRQ 22
Jun 21 11:20:40 arch ehci_hcd 0000:04:00.1: EHCI Host Controller
Jun 21 11:20:40 arch ehci_hcd 0000:04:00.1: new USB bus registered, assigned bus number 8
Jun 21 11:20:40 arch ehci_hcd 0000:04:00.1: irq 22, io mem 0x130001000
Jun 21 11:20:40 arch ehci_hcd 0000:04:00.1: startup error -19
Jun 21 11:20:40 arch ehci_hcd 0000:04:00.1: USB bus 8 deregistered
Jun 21 11:20:40 arch ehci_hcd 0000:04:00.1: PCI INT A disabled
Jun 21 11:20:40 arch ehci_hcd 0000:04:00.1: init 0000:04:00.1 fail, -19
errors.log
Jun 21 11:22:06 arch ohci_hcd 0000:04:00.0: USB HC takeover failed! (BIOS/SMM bug)
Jun 21 11:22:06 arch ohci_hcd 0000:04:00.0: can't setup
Jun 21 11:22:06 arch ohci_hcd 0000:04:00.0: init 0000:04:00.0 fail, -16
Jun 21 11:22:06 arch ehci_hcd 0000:04:00.1: startup error -19
Jun 21 11:22:06 arch ehci_hcd 0000:04:00.1: init 0000:04:00.1 fail, -19
messages.log
Jun 21 11:23:33 arch pcmcia_socket pcmcia_socket0: pccard: CardBus card inserted into slot 0
Jun 21 11:23:33 arch pci 0000:04:00.0: PME# supported from D0 D1 D2 D3hot
Jun 21 11:23:33 arch pci 0000:04:00.0: PME# disabled
Jun 21 11:23:33 arch pci 0000:04:00.1: PME# supported from D0 D1 D2 D3hot
Jun 21 11:23:33 arch pci 0000:04:00.1: PME# disabled
Jun 21 11:23:33 arch ohci_hcd 0000:04:00.0: enabling device (0000 -> 0002)
Jun 21 11:23:33 arch ohci_hcd 0000:04:00.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
Jun 21 11:23:33 arch ohci_hcd 0000:04:00.0: OHCI Host Controller
Jun 21 11:23:33 arch ohci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 8
Jun 21 11:23:39 arch ohci_hcd 0000:04:00.0: USB bus 8 deregistered
Jun 21 11:23:39 arch ohci_hcd 0000:04:00.0: PCI INT A disabled
Jun 21 11:23:39 arch ohci_hcd: probe of 0000:04:00.0 failed with error -16
Jun 21 11:23:39 arch ehci_hcd 0000:04:00.1: enabling device (0000 -> 0002)
Jun 21 11:23:39 arch ehci_hcd 0000:04:00.1: PCI INT A -> GSI 22 (level, low) -> IRQ 22
Jun 21 11:23:39 arch ehci_hcd 0000:04:00.1: EHCI Host Controller
Jun 21 11:23:39 arch ehci_hcd 0000:04:00.1: new USB bus registered, assigned bus number 8
Jun 21 11:23:39 arch ehci_hcd 0000:04:00.1: irq 22, io mem 0x130001000
Jun 21 11:23:39 arch ehci_hcd 0000:04:00.1: USB bus 8 deregistered
Jun 21 11:23:39 arch ehci_hcd 0000:04:00.1: PCI INT A disabled
dmesg.log
nothing here
If You need more info (log or something) just type and i will send all.
This is my PC machine:
- ASUS M3A78 PRO
- AMD Phenom 4x2GHz
- 4GB ram
- 250GB Sata II disk
- pcmcia adapter is Ricoh RL5C475 CardBus Controller
This modem is my only way to connect with net so please help (my laptop is down and i hate MS software)
Ps.
Sorry for my poor english , i hope You understand all (or enough to help me )

Noone knows ? I think it's a bug in kernel. I'll wait and we see .

Has anyone gotten the FBUS PCMCIA card to work on a PCI to PCMCIA adapter board?

I have lots of success with the PCMCIA card in laptop PCMCIA slots, but no luck with the PCMCIA card in a desktop PC with a Quatech PCD-B/PCI-E PCI adapter for PCMCIA boards. I am thinking that my problem resides with the adapter board but I would like to know if anyone has had success with the FBUS series 2 PCMCIA card with a PCI to PCMCIA adapter. I got a WinXP SP2 IBM ThinkCentre desktop. Thanks

We have ever used some PCMCIA to PCI adaptors, they are working properly with NI PCMCIA-FBUS card as well as NI-FBUS software.
I'd like to recommend the single CardBus PCMCIA slot adaptor from Elan Digital System:
http://www.elandigitalsystems.com/adapter/pci.php
We have used the adaptor in a Dell Dimension desktop, running XP SP2, and NI-FBUS Configurator 3.1.1 runs well.
Another adaptor is a long card, which is Gigabyte GA-MPCI, it works well with some old desktops, but the length of the card is about twice of the card of Elan Digital System; it might not fit your requirement.
Hope it helps.

What kind of "PCI to PCMCIA" adaptor do I need?

I have been logging data from analytical balances to a laptop running LabVIEW through a "4 port PCMCIA RS-232 Interface board". I would like to know if I can still use this card in a normal desktop PC by a "16-bit PCMCIA-PCI adaptor". Thanks.

There are "PCI to PCMCIA" PCI cards, but I personally would just get a 4 port PCI RS-232 card. Your application won't know the difference and you won't have to worry about incompatibilities between the PCI card and the PCMCIA card.
If you do decide to go with the adapter, just google PCMCIA to PCI adapter and you'll get plenty of results.
Ed
Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

Anybody had experience with Audigy2 PCMCIA + PCMCIA to PCI adapter?

I have been using my Audigy 2 ZS (PCMCIA) on a laptop as a media center for a looong time, but the laptop died and I'm using a cheap desktop for it.
The built-in soundcard lacks luster and I want to use my Audigy in it, but I'll be needing a PCI to PCMCIA adapter. Because the Audigy 2 ZS was so picky about the Cardbus adapter it was connected to, I want to know of other peoples' experiences on doing the same thing.
Has anyone else connected their Audigy 2 ZS - laptop into a desktop using a PCMCIA-to-PCI adapter? Which brand/model and how did it work out?
Thank you.

Sonnet seems to be the most Mac friendly and, as I recall, they answer customer questions very quickly. Try:
http://www.sonnettech.com/

No ISA slot available in PC. How can I use PCI-85 Modbus Plus card with Lookout?

My application is to communicate with two Modicon PLCs using Modicon's ModBus Plus (PCI based PCI-85) network card inside my PC, and using Lookout as an SCADA software. Since there is no ISA slot available in new PCs, I can not use Modicon's ISA-85 Modbus Plus networc card. But Lookout does not support PCI based PCI-85 card, how can I use PCI-85 card then, with Lookout? Why doesn't Lookout support it? I asked the following question from from the Modicon's representative about it:
If I purchase Modbus Plus Driver Suite CD (SWMXDS001, 05, or 10 etc),will I be able to use Lookout SCADA software (by the way, it supports standard MB+ prtocol) for my application? If yes, can I use any version of an
y of the ISA, PCI, or PCMCIA based MB+ card?
His answer was:
The Modbus Plus Driver Suite will talk to any version of card, PCMCIA, ISA, and PCI. The question now is will the SCADA package you are
planning on using be able to talk to the Modbus Plus Driver Suite? You must contact National Instruments and ask them if they support Modbus Plus, and if
they used the MB+ system developement kit to develop their product. Or if they wrote their own MB+ drivers, do they work with Modicon hardware?

Hi,
currently Lookout does not support the PCI-85 card. The only card supported for Modbus Plus is SA-85. Please see for further information:
Where can I Find Drivers for Communicating to PLCs, RTUs, and Other Industrial Hardware?
How to configure the SA-85 card for Modbus Plus
Hope this helps
Roland

PCMCIA-FBus Series 2 is not recognized under Windows XP

I'm trying to get a PCMCIA-FBus Series 2 card work under Windows XP Professional SP2 toghether with an Elan P111 PCI to PCMCIA Adapter, but when I plug in the card Windows does not recognize it - I only get a "pcmcia unknown_manufacturer" message and no driver is installed.
I've tried to install the driver manually, but then I get an error code 10, Device could not be started.
The Computer is a Dell Optiplx 740, AMP Athlon 64 X2 3800+. NI-Configurator v3.1, v3.1.1 and v3.2.1 have been tested. The Elan P111 driver is PSeries v5.07.08.

Hi,
I am not sure whether this PCI-PCMCIA adapter works well with Windows XP SP2. I suggest that you also contact the adapter manufacturer for the compatibility issue.
We did do some test on Elan PCI-PCMCIA adapter, but I am sorry that we are unable to make verifications on all kinds of hardware and software combination. There exists the possibilities that the adapter does not work on some PC's.
Another suggestion that you can try is to install the PCI-PCMCIA adapter driver on a clean Dell Optiplx 740 (Windows XP SP2 without Microsoft hotfix ). I think this can help you identify whether there are compatibility problems between the adapter and system.
Regards
Feilian (Vince) Shen

PCMCIA acquisition problem (indicator refresh)

Hi!
I use LV 8.2 and DAQmx 8.3 drivers on laptop with NI DAQCard-6036E (PCMCIA). As a demostration I eclose acquisition.vi as attachment. Everything works fine if samples per channel is set to 500 or more (sampling rate is 1000 all the time), but when samples per channel is set to 100, indicators are refreshd every fifth iteration of while loop (if you run acquisition.vi you will noticed thah while watching loop index indicator whitch is increasing by 5). I also run this VI with other cards like USB or PCI and it works fine (indicators are refresh everyiteration of loop). I have this problem only with PCMCIA card.
I hope that somebody can help me because it is crucial for the project that I developed.
Thank you in advance!
Andrej
Attachments:
acquisition.vi ‏34 KB

Hi Andrej,
Thank you for posting to the NI forums. This is the expected default behavior for your device, and in general, all of our PCMCIA devices. Unlike our PCI devices, PCMCIA devices do not support DMA – they are interrupt driven. The default interrupt to trigger the onboard data fetch into RAM is setup to occur when the onboard memory is more than half full. You can change this setting to fetch the data when the onboard memory is simply “not empty”.
This is described in the following Knowledge Base article.
Data Updates Very Slowly at Low Sample Rates in NI-DAQmx With PCMCIA DAQCards
I hope this helps! Please post back if you have further questions.
Ed W.
Applications Engineer
National Instruments

Problems with PCMCIA-GPIB card

Hi all
I am using a PCMCIA-GPIB with driver version 2.2 on a Windows XP with a PCI-to-PCMCIA Adapter from Ricoh (device manager says: Ricoh R/RL/RT/RC/5C475II,R5C520 or compatible cardbus controller).
The Win XP detects the card without any problems and there are no resource conflicts.
However, I cannot communicate with GPIB devices and the NI-488.2 Troubleshooting Wizard says:
1. NI-488.2 Software Presence = verified
2. GPIB Hardware Presence =
And then a new screen: "The trouble shooting wizard has detect that no GPIB interfaces are configured on your system"
Can someone help me? There are no resource conflicts and I have also tried changing the PCI slot. The same problem also occurred when I installed the card in an
other computer.
Regards,
Juan"

I have tested a RICOH PCMCIA to PCI Adapter card. The PCMCIA to PCI Adapter card was tested using different operating systems (Win2000,XP,98,95) and using a Micron computer PIII 650 processor. When testing under the XP environment, with service pack 1, NI's device drivers Version 1.7 failed to load. (Code 10) Ni's driver version 1.7 was then removed and NI's device driver Version 2.2 was loaded. I did not experience any commutation problem as long as I used the standard NI calls. I did experience a problem with NI’s IBDIAG function call which is not supported under Version 2.2.
I would recommend that you get the latest service pack for XP and NI’s device driver Version 2.2.

Problems with GPIB-PCMCIA card

Hi all
I am using a PCMCIA-GPIB with driver version 2.2 on a Windows XP with a PCI-to-PCMCIA Adapter from Ricoh (device manager says: Ricoh R/RL/RT/RC/5C475II,R5C520 or compatible cardbus controller).
The Win XP detects the card without any problems and there are no resource conflicts.
However, I cannot communicate with GPIB devices and the NI-488.2 Troubleshooting Wizard says:
1. NI-488.2 Software Presence = verified
2. GPIB Hardware Presence =
And then a new screen: "The trouble shooting wizard has detect that no GPIB interfaces are configured on your system"
Can someone help me? There are no resource conflicts and I have also tried changing the PCI slot. The same problem also occurred when I installed the card in
another computer.
Regards,
Juan"

Hello Juan,
the first thing I would do is to check that the board is working OK. You will need a laptop to test it.
Once this is confirmed (if not, contact NI for a repair), it can be safely attributed to some incompatibility with the adapter.
At that point, I would check with Ricoh as they may have an updated driver for their board that fixes the issue, or they may have an idea on what's going on. Another thing would be to check your PCs BIOS configuration and see if any setting may help into solving the incompatibility (PCI settings, IRQs, bus-mastering, etc..)
As side suggestions, although I don't feel this will be the issue:
a)it's always advisable to use the latest version on the driver software -NI-488.2-, available at the web
b)check for an updat
e to the motherboard's BIOS at the manufacturer's site.
Regards,
JorgeM.

Error 10452 When i test an Individual Channel in MAX

I am Using an AI-16E-4 DAQ Card and When i test an individual channel (nonreferenced single ended) in MAX, i get error 10452 - Error occurred at AI Control. When I try to test the panels, i get a message that says "The Device is Not responding to the first IRQ level," but MAX still displays data acquired by the DAQ Card. I am using the PCMCIA Card on a PCI to PCMCIA Adapter on my desktop - could that have anything to do with the problem?

Hi,
This knowledgebase may be able to help with this issue:
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/14dfb1a1788d1f3286256e4d007ca783?OpenDocument
I hope this helps,
Andrew A
Applications Engineer
National Instruments

I have configuration file for VECTOR CAN and want to port to NI CAN card

Hello,
I have CAN analyzer with for Vecror CAN card. Now I want to use the NI CAN analyzer for the same application. What are all teh files that can be compatible with NI CAN card. I have .dbc
.asc
.ccp files with me, please suggest on having the same with NI CAN card.

laxmi,
The NI-CAN Channel API (available on PCI, PXI, PCMCIA interfaces), can directly import and allow you read/write data with channels defined in .DBC files. .DBC is somewhat of a de-facto standard in the industry. You can play around with this functionality without the CAN interface, simply download and install the NI-CAN driver software (http://joule.ni.com/nidu/cds/fn/p/sn/n23:3239/lang/en) and you can import the DBC files into the Data Neighborhood branch in Measurement and Automation Explorer.
.CCP is used with CAN Calibration Protocol and supported in our ECU Measurement and Automation toolkit. This is a separate toolkit available for use with NI CAN interfaces (including USB).
http://sine.ni.com/nips/cds/view/p/lang/en/nid/201975
You can download and evaluate it for free here:
http://joule.ni.com/nidu/cds/fn/p/sn/n23:2.17.3237/q/ecu/sb/navsRel/lang/en
Hope this helps!
--Paul Mandeltort
Automotive and Industrial Communications Product Marketing

MSI Mega Sky Aerial

Hi just wondering if anyone knows if the MSI Mega Sky Aerial is weather proof.....
please reply.

Yes, i have coverage. I wrote, that with default aerial i have around 65/15 signal. I am few km (maybe 5km) from broadcaster (i found thiw word in dictionary, hope is ok) and i can see it (no obstacles in way).
As i wrote, if i use default antenna, i have bad signal, so sometimes i have drop-outs and "colored squares".
If i use any other antenna, signal is worst than bad, can't tune anything.
Of course i tryed moving with aerial, every place when aerial can stand.. I am trying this around 3 months!
I asked in some local forum, if anyone tested dvbt here. They answered to me something like this: yes, works perfectly.
But noone have MegaSky 580 (some internal pci cards, pcmcia cards, some usb keys from pinnacle or hauppage or technisat or other), but few of them using same aerials, that i bought (smaller passive Technisat or bigger Technisat with ampfilier)!
So, from my eyes looks like MegaSky 580 is "not very successful product".
If you have any hint what other i can do, so say it. But i think i tryed anything.
And i'm not saying about horrible software called PrestoPVR - "Blue screen of death" is every day when i trying to use it..
I have one more thing. I found, that is two different models of MegaSky 580 (different producer or technology, different drivers, different sign).
First is "DTV USB MINI" and second is "PC-DTV Receiver". I have "DTV USB MINI".
If you don't trust me, look here (driver download): http://www.msi.com.tw/program/support/driver/dvr/spt_dvr_detail.php?UID=624&kind=6
Maybe is "DTV USB MINI" model crap and MSI started to produce new version with differend technology..
Anyway, my MegaSky 580 is really unusable.
(p.s. sorry for my bad english, i'm not a native english speaker)

TV@nywhere A/D NB : Bad DVB-t video/sound

Hi all.
just bought a TV@nywhere A/D NB for use with an old notebook i own (acer aspire 1662wlmi/P4 @ 3Ghz/1GB ram/Ati mobility9700 64Mb ram).
The radio and and the analog Tv works like a charm but the DVB-t video is very crapy.Is keeps losing a lot of frames,mostly it freezes and the audio is not contitious.I tryed to use drivers for compatible cards but it does the same.
Am i missing something (a codec maybe) ? I have installed (some months before the cards purchase) the ccc codec and also the nimo codec package.Is there any chance that these codecs interfere withe the codecs the Viewer uses for DVB-t video ?
I am thinking that maybe the VGA is old and slow but i would like to have your opinions...
Thanks alot.

nope , it isn't.And i say so because with the very same antenna (central bulding antenna) and with the same cable it worked fine at my media center pc through a pci to pcmcia adapter.It worked with both MSI and Lifeview drivers/apps.
At this media center i have installed also the above mendioned codec packs.No need to do anything more than the driver and apps installations.Scan for channels and that was it....Worked.

Connecting Solaris 8 (Intel) to Network

I just received Solaris 8 for the Intel platform and was able to successfully install it on a Intel pc but I'm not able to connect the pc to my home network. The pc has a Linksys Etherfast 10/100 lan card and I really don't know where to start. Could anyone please explain in general terms what I must do to connect a Solaris 8 pc to a network?

DOCUMENT ID: 1105-02
SYNOPSIS: Adding Network Support to Solaris
OS: Solaris/SunOS
PLATFORM: Intel
OS VERSION: 2.x
TECH AREA: Network
PRODUCT: Config
KEYWORDS: add network card adapter install file directory adding host nic
driver
DESCRIPTION:
When a workstation is placed in service without a network card, or none
is recognized during initial software installation, several files and
directories will not be available to the operating system if future
networking support is desired.
SOLUTION:
Solaris will not presume upon any particular network configuration if it
is unable to identify supported network hardware at the factory default
addresses. Hence, the installation scripts will not prompt the user for
network-specific configuration items like ip address, netmasks, hardware
settings, subnets, etc.
All of these can be added by hand after the machine has had Solaris
installed on it.
Workaround - Adding support for a network card to an existing system
To add network support to a Solaris workstation previously installed
without a supported network card driver requires adding/changing certain
files in the OS according to which network card is to be added. A
network card that is listed in the Hardware Compatibility List for that
platform (x86, Sparc, or PowerPC) must also be present on the system bus
and identified by the operating system to reside at supported addresses.
The following instructions for identifying a card will apply to x86 and
PowerPC platforms, for the most part. For the Sparc platforms the Open
Boot Prom is able to identify any SBUS card and, in future versions, any
PCI or PCMCIA (PC Card) device that is installed. Note also, that for
PCI devices, some ISA, MCA and EISA devices, as well as some PCMCIA
devices - the addresses, IRQs, memory, and DMA resources will be
assigned by the BIOS or a configuration utility and the driver will be
able to read the info for the device when it is loaded. Check the
Driver Configuration Guide for how to configure your particular device.
First, identify the make and model of your network card and write down
which addresses it occupies in terms of interrupt vector (IRQ), port
address range, DMA channel (if any), and shared memory address range.
Then find the driver configuration file in the /kernel/drv sub-directory
and examine this file to make sure that the addresses on the card will
be seen. For example, on Solaris 2.4 and earlier, the SMC (WD) Model
8003 or 8013 configuration file is /kernel/drv/smc.conf. It should look
similar to the following:
#ident "@(#)smc.conf 1.8 93/04/02 SMI"
# Factory default setting.
name="smc" class="sysbus" intr=5,3 ioaddr=0x280
reg=0x280,0xD0000,0x2000;
This means that the factory default for this card is at interrupt 3,
priority 5 and port address 280 hex, at memory address D0000 hex with an
8k memory range.
If you are instead using a supported 3COM or token-ring adapter, the
driver names for these are "el.conf" & "elx.conf" for 3COM,
or "tr" for
token- ring. Note that as of Solaris 2.5 some drivers that are unique
to a platform (i.e. - not common to all the Solaris platforms, like
ISA), will be found in /platform/{PLATFORM_NAME}/kernel/drv instead of
/kernel/drv. For the x86 you use i86pc in place of {PLATFORM_NAME}.
Secondly, when logged in as root, bring the driver into service. Do
this by typing drvconfig, devlinks, and touch /reconfigure at successive
"#" prompts. Type "prtconf" to test for the existence of the
0th
instance of the driver.
Workaround - Configuring the system to use the network card
You are now ready to modify the filesystem as required. Ensure that the
following directories, files, named-pipes, and symbolic links are
present and have the designated permissions, owner, and group. Those
with a file size of zero can sim

PCI vs PCMCIA?

Similar Messages

Maybe you are looking for