Sponsored Content
Special Forums Hardware identify wireless network card Post 302543283 by h@foorsa.biz on Saturday 30th of July 2011 02:01:29 PM
Old 07-30-2011
Did you try lspci -v?
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Lucent/Orinoco Wireless card problems

Im running mandrake 9.0 and i just got a Lucent/orinoco PC24E-H-FC. I beleive it was originaly made by lucent but then made by Orinoco.. But anyways i just cant get connected. Ive tried 3 differemt drivers. My wireless access point router is a Linksys. I just cant figure this out ive talked on... (3 Replies)
Discussion started by: jason1234
3 Replies

2. Linux

wireless card for mandrake 9.1 hp laptop

I just recently bought a HP Pavilion zt3020us and it had came with an internal WiFi NIC (Intel(R) PRO/Wireless LAN 2100 3B Mini PCI Adapter) and I was wondering where I could go to find a device driver for it under Mandrake 9.1 Linux. (2 Replies)
Discussion started by: N0C717
2 Replies

3. Windows & DOS: Issues & Discussions

Problem with wireless card

I have a wireless setup in my house and i connect my laptop thru the wireless setup .. The problem is that one of my other friends has a wireless setup too and his wireless signal comes to my house too .. The effect is that it drops my service after sometime and connects to it .. then drops... (3 Replies)
Discussion started by: DPAI
3 Replies

4. Linux

Wireless network card performance

I am running FC4: Linux maincomp 2.6.13-1.1532_FC4smp I recently changed the OS from windows XP, and have a feeling that for some reason my wireless network card is slower on Fedora Core 4. The Belkin PCI 802.11b card was automatically detected and configured by FC4 when I installed the OS,... (0 Replies)
Discussion started by: dangral
0 Replies

5. Linux

Wireless card won't pick up network

I'm trying to get my wireless card up. I've been at it for a while now and something just isn't quite working right. I'm not getting any wireless signal. I'm using FC4 with a stack 16 kernel and ndiswrappr to load my drivers. here are the outputs that i get. Alittle bit about my... (3 Replies)
Discussion started by: byblyk
3 Replies

6. Solaris

Installing RT2500 Wireless network card

I need to install a driver for my RT2500 PCI wireless network card on my Solaris 10. So I went to the ralink website (the manufacturer of the network card), and downloaded the linux (well supposedly the unix driver) binary file. Burned it to dvd, and copied from the dvd to my solaris computer.... (3 Replies)
Discussion started by: Xannen
3 Replies

7. Linux

wireless card

Ive been fooling around on my spare laptop and put different cores of Fedora on and the computer uses an ibm a/b/g card but the os wont recognize the card and doesnt have the software fore it is there anyway to get the software for the card on the comp or should i buy a card that the os knows? (7 Replies)
Discussion started by: Texasone
7 Replies

8. IP Networking

use one wireless card for two pc's

I'm not what this is called so I don't exactly know what to search for to do my homework.:D But I have two IBM T40's and only one wireless internet card. I don't have to money to buy another wireless card, so my question is this: Can I use the card on one system and use an ethenet cable linked... (2 Replies)
Discussion started by: Texasone
2 Replies

9. Red Hat

Dlink Dwl-g630 Wireless card

Hello, I'm extremely new to Linux. I've been a windows admin for years stupid me, should have got into Linux way back. So now playing catch up. I was hoping someone could help me get started. I've been online reading but getting confused a lot of info and very different from windows. I... (0 Replies)
Discussion started by: kidsusuki
0 Replies

10. Programming

Turn ON/OFF Wireless Card

Hi all, In my program, I am trying to use ioctl to turn on/off the wireless card, using SIOCSIFFLAGS (I am new to it but somebody said it is the most traditional way). However, it seems that I didn't set the flag correctly since the wireless is always on (I have root permission). If any one... (2 Replies)
Discussion started by: tetelee
2 Replies
lspci(8)							Linux PCI Utilities							  lspci(8)

NAME
lspci - list all PCI devices SYNOPSIS
lspci [options] DESCRIPTION
lspci is a utility for displaying information about all PCI buses in the system and all devices connected to them. To make use of all the features of this program, you need to have Linux kernel 2.1.82 or newer which supports the /proc/bus/pci interface. With older kernels, the PCI utilities have to use direct hardware access which is available only to root and it suffers from numerous race conditions and other problems. If you are going to report bugs in PCI device drivers or in lspci itself, please include output of "lspci -vvx". OPTIONS
-v Tells lspci to be verbose and display detailed information about all devices. -vv Tells lspci to be very verbose and display even more information (actually everything the PCI device is able to tell). The exact meaning of these data is not explained in this manual page, if you want to know more, consult /usr/include/linux/pci.h or the PCI specs. -n Show PCI vendor and device codes as numbers instead of looking them up in the PCI ID database. -x Show hexadecimal dump of first 64 bytes of the PCI configuration space (the standard header). Useful for debugging of drivers and lspci itself. -xxx Show hexadecimal dump of whole PCI configuration space. Available only for root as several PCI devices crash when you try to read undefined portions of the config space (this behaviour probably doesn't violate the PCI standard, but it's at least very stupid). -b Bus-centric view. Show all IRQ numbers and addresses as seen by the cards on the PCI bus instead of as seen by the kernel. -t Show a tree-like diagram containing all buses, bridges, devices and connections between them. -s [[<bus>]:][<slot>][.[<func>]] Show only devices in specified bus, slot and function. Each component of the device address can be omitted or set as "*" meaning "any value". All numbers are hexadecimal. E.g., "0:" means all devices on bus 0, "0" means all functions of device 0 on any bus, "0.3" selects third function of device 0 on all buses and ".4" shows only fourth function of each device. -d [<vendor>]:[<device>] Show only devices with specified vendor and device ID. Both ID's are given in hexadecimal and may be omitted or given as "*" meaning "any value". -i <file> Use <file> as PCI ID database instead of /usr/share/hwdata/pci.ids. -p <dir> Use <dir> as directory containing PCI bus information instead of /proc/bus/pci. -m Dump PCI device data in machine readable form (both normal and verbose format supported) for easy parsing by scripts. -M Invoke bus mapping mode which scans the bus extensively to find all devices including those behind misconfigured bridges etc. Please note that this is intended only for debugging and as it can crash the machine (only in case of buggy devices, but unfortunately these happen to exist), it's available only to root. Also using -M on PCI access methods which don't directly touch the hardware has no sense since the results are (modulo bugs in lspci) identical to normal listing modes. --version Shows lspci version. This option should be used standalone. PCILIB OPTIONS
The PCI utilities use PCILIB (a portable library providing platform-independent functions for PCI configuration space access) to talk to the PCI cards. The following options control parameters of the library, especially what access method it uses. By default, PCILIB uses the first available access method and displays no debugging messages. Each switch is accompanied by a list of hardware/software configurations it's supported in. -P <dir> Use Linux 2.1 style configuration access to directory <dir> instead of /proc/bus/pci. (Linux 2.1 or newer only) -H1 Use direct hardware access via Intel configuration mechanism 1. (i386 and compatible only) -H2 Use direct hardware access via Intel configuration mechanism 2. Warning: This method is able to address only first 16 devices on any bus and it seems to be very unrealiable in many cases. (i386 and compatible only) -S Use PCI access syscalls. (Linux on Alpha and UltraSparc only) -F <file> Extract all information from given file containing output of lspci -x. This is very useful for analysis of user-supplied bug reports, because you can display the hardware configuration in any way you want without disturbing the user with requests for more dumps. (All systems) -G Increase debug level of the library. (All systems) FILES
/usr/share/hwdata/pci.ids A list of all known PCI ID's (vendors, devices, classes and subclasses). /proc/bus/pci An interface to PCI bus configuration space provided by the post-2.1.82 Linux kernels. Contains per-bus subdirectories with per-card config space files and a devices file containing a list of all PCI devices. SEE ALSO
setpci(8) AUTHOR
The Linux PCI Utilities are maintained by Martin Mares <mj@ucw.cz>. pciutils-2.1.10 30 March 2002 lspci(8)
All times are GMT -4. The time now is 11:22 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy