Sponsored Content
Special Forums Hardware Does this hardware works with Linux Post 302986374 by Corona688 on Thursday 24th of November 2016 11:00:46 AM
Old 11-24-2016
Linux's relationship with hardware is very different than the relationship of Microsoft with hardware vendors. Linux doesn't know, or even care really, what model a motherboard is. It just scans the plug-and-play bus to get the list of devices, and checks whether it has drivers for them or not. This has always meant that "compatibility lists" for Linux are going to be very incomplete. Without buying and testing every possible motherboard on the planet, how would we ever know?

There is probably at least partial support for most PC hardware on the market, though, and workarounds for a lot of the rest, or eventual fixes. The biggest showstoppers are liable to be graphics related, as the drivers for those are always going to be proprietary, it seems, and fixes mean "bugging the vendor for a new version". Search for these motherboard models plus "linux" or "ubuntu" to see if any linux users have reported problems and/or workarounds for them. Absence of evidence is not evidence of absence, but until some other linux user buys it and tries it out and reports their success or failure, conclusive evidence will be scarce to none.

Last edited by Corona688; 11-24-2016 at 12:06 PM..
 

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Script works on Solaris, not on Linux

I'm in the same boat as Barbus - same exercis (https://www.unix.com/shell-programming-scripting/43609-processes-users.html) The following script works on a solaris server I have access to. It doesn't however, work on the companies Linux machine. Any idea what's up? I have very little shell... (0 Replies)
Discussion started by: Silverhood
0 Replies

2. Shell Programming and Scripting

Script works on Solaris, not on Linux

I'm in the same boat as Barbus - same exercis (https://www.unix.com/shell-programming-scripting/43609-processes-users.html) The following script works on a solaris server I have access to. It doesn't however, work on the companies Linux machine. Any idea what's up? I have very little shell... (1 Reply)
Discussion started by: Silverhood
1 Replies

3. Programming

fcntl works in linux but not in mac os x

Hi, Unless I am missing some serious differences in Mac and linux in terms of C programming, I dont know why this would happen. Please take a look at the following piece of code fragment: bool add_input_to_db(Cons *new_data) { // Set the attributes of the lock struct flock fl =... (3 Replies)
Discussion started by: newhere
3 Replies

4. UNIX for Dummies Questions & Answers

Linux on custom hardware

I would like to configure a bare minimum Linux with internet browser on a system with Flash & RAM (but no harddisk or any other nonvolatile storage). Please advise. (5 Replies)
Discussion started by: rherb
5 Replies

5. Shell Programming and Scripting

awk -F works on Linux, but not on Solaris

Hello, I found this command works on Linux: $ echo `uptime` | awk -F "load average: " '{ print $2 }' 1.60, 1.53, 1.46 but got error on Solaris: $ echo `uptime` | awk -F "load average: " '{ print $2 }' awk: syntax error near line 1 awk: bailing out near line 1 $ which awk... (2 Replies)
Discussion started by: seafan
2 Replies

6. Shell Programming and Scripting

sed works on Linux and Unix does not work

Hi, I use this command in Linux but if I run the same command does not work in freebsd. Follow the below command: Linux works: sed -e '1731a\' -e '####' squid.conf > squid2.conf ; sed -e '1731a\' -e 'acl TESTE_ip src 192.168.1.1/255.255.255.255' squid2.conf > squid.conf ; sed -e... (7 Replies)
Discussion started by: andreirp
7 Replies

7. Shell Programming and Scripting

Script works with Linux not with Solaris

Hi I have the following script which works in Linux shell but gives issues with Sun OS Solaris 5.10, What i am trying to achieve here is we have a list of file names in list.txt file and we parse each file at a time for a particular pattern and copt next 4 lines after we hit the pattern to a... (6 Replies)
Discussion started by: Yugendra
6 Replies

8. Shell Programming and Scripting

Why statement works in LINUX and not UNIX?

Hello, I have a ksh script that uses code below. For some reason it works under linux but fails in unix. Any idea why? if ]; then ... Thanks (9 Replies)
Discussion started by: rdogadin
9 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:18 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy