lspci is a command to list all PCI devices.

# lspci -vv

displays detailed information about the PCI devices.

Enter TERMINAL

lspci -v | less

00:00.0 Host bridge: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface (rev 01)
Flags: bus master, fast devsel, latency 0
Memory at f8000000 (32-bit, prefetchable) [size=64M]
Capabilities:
Kernel driver in use: agpgart-intel
Kernel modules: intel-agp

00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01)
Subsystem: Compaq Computer Corporation Device 00b8
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at f0000000 (32-bit, prefetchable) [size=128M]
Memory at fc400000 (32-bit, non-prefetchable) [size=512K]
Capabilities:
Kernel driver in use: i915
Kernel modules: i915

00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01)
Subsystem: Compaq Computer Corporation Device 00b8
Flags: bus master, medium devsel, latency 0, IRQ 16
I/O ports at 2440 [size=32]
:
NOW FOR THE WIFI:

ENTER TERMINAL

lsusb -v | less

00:00.0 Host bridge: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface (rev 01)
Flags: bus master, fast devsel, latency 0
Memory at f8000000 (32-bit, prefetchable) [size=64M]
Capabilities:
Kernel driver in use: agpgart-intel
Kernel modules: intel-agp

00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01)
Subsystem: Compaq Computer Corporation Device 00b8
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at f0000000 (32-bit, prefetchable) [size=128M]
Memory at fc400000 (32-bit, non-prefetchable) [size=512K]
Capabilities:
Kernel driver in use: i915
Kernel modules: i915

00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01)
Subsystem: Compaq Computer Corporation Device 00b8
Flags: bus master, medium devsel, latency 0, IRQ 16
I/O ports at 2440 [size=32]
:

Descobrindo qual hardware vc tem na sua máquina.

  digitar no console : > lspci

Caso queira listar I/O e IRQ dos dispositivos, digitar : lspci -v

  OBS : para ver mensagens do Kernel : dmesg

 Caso queira somente placa de som digite : lspci |grep -i audio

Para inspecionar os dispositivos usb ativos no sistema vc digita : lsusb. As informações detalhadas estão armazenadas no arquivo /proc/bus/usb/devices.

Estos días me preguntaron qué tarjeta de sonido tenía mi PC (alguien tuvo un problema de sonido similar al que tuve cuando instalé Ubuntu en mi HP Mini) y mi respuesta fue: “ehhh…. ya te digo” y fue ahí cuando descubrí los siguientes comandos:

lspci

Lista los dispositivos PCi conectados a tu equipo (tarjetas de sonido, video, red, etc…)

hwinfo

Muestra todos los dispositivos de tu computador

lsusb

Muestra los dispositivos USB conectados.

Espero le sea útil a alguien.

Up the Irons!!

Trafiłem ostatnio na dość ciekawy problem dla kernela 2.6.16.46 na maszynie z płytą główna Gigabyte G31M-S2L. Płyta ta posiada zintegrowaną kartę graficzną na układzie Intela, GMA 3100. Przy próbie konfiguracji środowiska graficznego Xorg w archaicznej już wersji 6.9.0, w zależności od konfiguracji sprzętowej, występuje problem ze zmianą rozdzielczości. Standardowym driverem (!) jaki jest “wyłapywany” to ten pochodzący od urządzenia frame buffer. Narzędzia lspci, dmidecode nie pokazują żadnych konkretnych informacji o sprzęcie, co do którego mógłbym użyć odpowiedniego sterownika. Jedynym rozwiązaniem, i to nie w 100% obchodzącym problem, jest użycie drivera vesa. Nie rozwiązuje on jednak 100% przypadków problemu, gdyż dla lekko zmodyfikowanej konfiguracji sprzętowej (RAM, monitor) Xorg wyrzuca signal 11 ze ślicznie wyglądającymi zrzutami pamięci.

This little command saved me a ton of time and searching back in Ubuntu 8.04 when I needed to know what wireless card I had.  I found out by running the command:

lspci|grep -i “wireless”

What It Does

The lspci command shows you your computer’s hardware interfaces (SATA controllers, wireless cards, etc.).  The standard output it gives you can be a little hard to read, so I piped it to grep.  The grep command allows you to search through a file or a program’s output for a line with a string in it that you specify.  The -i option tells grep to ignore case.  The string at the end finishes the command by telling grep what to look for in lspci’s output.  So, the full command runs lspci, sends the output to grep, which searches through the output to find the string “wireless”, regardless of case.

Why It’s Useful

This command is amazingly useful, especially in Arch Linux.  Arch doesn’t give you a GUI by default and you need to install X with the right drivers.  If you replace “wireless” with “VGA”, you’ll know what you need.

… which may be bad at the start, but isn’t so if you really know how powerful Linux is. In this case, you don’t really need to acquire a cpu-z-like software, unless of course you’re freaked out by the command line (which we’ll use in this case).  Linux (at least those that use kernel versions 2.6 and above) have quite  an array of commands that lets you acquire most info that cpu-z will give you on a Window$ box, sometimes less, sometimes more. These commands are especially useful in cases like (this was my case a week ago, that’s why I had to find out about them) there’s no graphical interface for you since you’re either remotely doing administration or the server just doesn’t have any graphical server/service installed.

To list information about the CPU enter the command

cat /proc/cpuinfo

To list your PCI devices type the command

lspci

To acquire information about your installed memory/RAM sticks or modules, one command to do this is

sudo dmidecode —type 17

To check your hard drives, the following commands give you loads of info

cat /proc/diskstats | egrep "^\s?+8"
df -hT
ls -lh /dev/disk/by-path/
ls -lh /dev/disk/by-id/
ls -lh /dev/disk/by-uuid/
cat /proc/scsi/scsi

you then can find out disk info by running the following on each node listed (device name in third column):

sudo fdisk -l /dev/NODE (e.g. sudo fdisk -l /dev/sda, if you have SCSI drives)

There are quite a lot more commands to get information about the hardware you are running, without shutting it/them down so you can open them up and check the hardware yourself. Or you won’t have to grab your hardware’s manual (whether locally or online) just to get info about your hardware. Good especially for sys ads like me.

Acabo de ver en rm -rf una interesante referencia a un sitio web que nos permite ver el listado de los dispositivos/controladores linux instalados en nuestra máquina. La consigna es muy sencilla; en una terminal tipeamos:

lspci -n

El resultado es algo más o menos como ésto:

Salida del comando lspci -n

Acto seguido, copiamos y pegamos directamente en la caja de texto que se encuentra en ésta página y le damos click al botón verificar. Inmediatamente obtendremos una lista del hardware relacionado con la información que proporcionamos, los controladores disponibles y su compatibilidad.

En mi caso, ha funcionado más que bien.

Hoy vamos a hablar del Acer TravelMate2490, un portátil para cuarentones gordos,como todos los de la serie TravelMate -aclaración: excepto mi padre.

Un vecino tiene un portátil desde hace unos seis meses, uno de estos 2490, que le llegó por herencia o algo así, infectado de VirusVista. Dice que no le gusta, que por favor le ponga algo más potable: un inXPerience, un Mierbuntu (éste a quedado demasiado forzado, pero la cuestión es despreciarlo todo…), o lo que sea, y que encasadelherrerocuchillodepalo y que para eso me paga. O algo así.

Finalmente, un buen día, nos ponemos a ello… La instalación no tiene nada de especial y ya hay manuales para tontos (o tambien aquí, que no se diga), el problema real es la tarjeta wifi. La Broadcom Corporation BCM4401-B0 100Base-TX,según lspci.

No encontré forma de ponerlo (lo más parecido una BCM4318 en Debian, que más que ayudarme me jodio, aunque afortunadamente todo se pudo “arreglar”) de manera “nativa” en linux, así que miré el tema de ndiswrapper. Al final, lo tuve que instalar APeTeando con una conexión ethernet desde el pasillo de una casa “ajena” (muy guapa, por cierto) y bajo presión, ya que me fue imposible compilar el tar.gz (siempre me daba errores).

Mire éste manual (tambien para tontos), y todo parecía muy fácil:

user@ubuntu:~$ sudo su

[sudo] password for user:

root@ubuntu:/# aptitude install ndiswrapper-common ndiswrapper-modules-1.9 ndiswrapper-utils-1.9

root@ubuntu:/# ndiswrapper -i nuestrodriver.inf

(nuestrodriver.inf es un archivo de los drivers de la tarjeta que hemos bajado anteriormente…)

root@ubuntu:/# ndiswrapper -l

… y todo debería de salir bien. Y, en éste caso, no es así. Me detectaba el driver (creo: “Driver instaled“) pero nada de nada.

Pruebo (como dice el manual):

root@ubuntu:/# lshw -C network | grep module

Sí, “module=ssb”. Intento la solución propuesta:

root@ubuntu:/# rmmod ssb

root@ubuntu:/# rmmod ndiswrapper

root@ubuntu:/# modprobe ndiswrapper

Y me dice que el modulo está en uso por sb4 o algo así (lo digo de memoria…). He probado con varios drivers diferentes (lo más parecido que he podido encontrar) y nada.

Con todo, mientras escribo ésto, parece que “se ha arreglado“.Al final, he desactivado el controlador de hardware de la tarjeta (supongo que el último que yo había instalado, atheros nosequé ¬¬) y funciona! :S

Bueno, en realidad he echo más cosas que no recuerdo… así que la solución (para lxs que tengan el mismo problema) es: metedle mano a todo lo que podaís, lo que no provoca un KernelPanic te hace más fuerte.

Cosas de la vida.

No post anterior falamos de reconhecimento de Hardware no Arch Linux, mas nem todos usam o Arch Linux e por aqui gostamos de ser democráticos.

Para os usuários de outras distribuições que não o Arch Linux a coisa fica um pouco mais complicada, mas um pouquinho só.

Tempos dois comandos responsáveis pelo reconhecimento, o lspci que reconhece seu hardware de um modo geral e o lsusb que reconhece todo hardware ligado a sua máquina através de portas usb.

Veja o exemplo do meu lspci:

00:00.0 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge
00:00.1 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge
00:00.2 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge
00:00.3 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge
00:00.4 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge
00:00.5 PIC: VIA Technologies, Inc. CN896/VN896/P4M900 I/O APIC Interrupt Controller
00:00.6 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Security Device
00:00.7 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237/VX700 PCI Bridge
00:02.0 PCI bridge: VIA Technologies, Inc. CN896/VN896/P4M900 PCI to PCI BridgeController (rev 80)
00:03.0 PCI bridge: VIA Technologies, Inc. CN896/VN896/P4M900 PCI to PCI BridgeController (rev 80)
00:0f.0 IDE interface: VIA Technologies, Inc. VT8237A SATA 2-Port Controller (rev 80)
00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 07)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0)
00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8237A PCI to ISA Bridge
00:11.7 Host bridge: VIA Technologies, Inc. VT8251 Ultra VLINK Controller
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 7c)
00:13.0 PCI bridge: VIA Technologies, Inc. VT8237A Host Bridge
00:13.1 PCI bridge: VIA Technologies, Inc. VT8237A PCI to PCI Bridge
01:00.0 VGA compatible controller: VIA Technologies, Inc. CN896/VN896/P4M900 [Chrome 9 HC] (rev 01)
06:01.0 Audio device: VIA Technologies, Inc. VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) (rev 10)
07:04.0 FLASH memory: ENE Technology Inc ENE PCI Memory Stick Card Reader Controller
07:04.1 SD Host controller: ENE Technology Inc ENE PCI SmartMedia / xD Card Reader Controller
07:04.3 FLASH memory: ENE Technology Inc ENE PCI Secure Digital / MMC Card Reader Controller

Confesso a vocês que nunca entendi direito o lspci, em geral o que faço é conforme vou usando o computador e identifico drivers que não estão rodando direito como o vídeo que está mais lento, som que não fala entre outros, venho aqui e procuro alguma coisa que se pareça com uma placa de vídeo, mas no meu caso é muito tentativa e erro também.

Um exemplo do lsusb é:

Bus 005 Device 004: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
Bus 005 Device 003: ID 0402:5602 ALi Corp. Video Camera Controller
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 15ca:00c3 Textech International Ltd. Mini Optical Mouse
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Veja que este é mais simples por termos menos linhas, dá até para identificar uma placa wireless, uma camêra de vídeo e um mouse.

Como falei para vocês, não entendo tão bem do lspci como gostaria e se alguem puder contribuir com o pouco que disponibilizei neste artigo, sinta-se à vontade.

Agradeço a todos

Qual é a primeira coisa que devemos fazer logo após a formatação do computador?

A instalação dos drivers.

E é claro, como tudo no Linux este é mais um problema para os iniciantes.

No Arch Linux em especial este é um problema bem simples de se resolver. Assim como em outras distribuições, nós temos sim o lspci e o lsusb (todas as distribuições tem, falarei deles em posts posteriores) porém os pensadores do Arch Linux pensaram em algo mais humano e simples que uma lista de driver que ninguem sabe o que é.

O hwd!

O hwd é um programa, até onde eu sei, específico para Arch Linux e tem como papel reconhecer o seu hardware de modo mais simples, se você quiser ele até gera o seu xorg.

Inicialmente vamos instala-lo:

pacman -S hwd

Após a sua instalação para verificar o seu reconhecimento de hardware apenas digite

hwd -s

E em poucos instantes na sua tela terá uma lista do seu hardware detalhadinha com o que é o que, e na minha opinião isto é muito menos confuso que um monte de texto um em baixo do outro (Se quiser saber do que eu estou falando digite lspci no console).

O hwd -s roda o hwd em reconhecimento simples de hardware, dizendo exatamente o que é o que, porém também temos o reconhecimento mais complexo com o hwd -e.

Outra coisa bem interessante do hwd é que ele fala um pouco sobre seu sistema com o hwd -y, isto é fala do tamanho de partições como / e /home, espaço utilizado e espaço livre.

Como eu disse acima o hwd também gera o xorg.

No Arch Linux quando você acaba de formatar a máquina, por ser uma distribuição minimalista ele não traz nada instalado, nem o X, nem um kde, nada.

Então nos instalamos o X com o pacman -S xorg, porém não temos um arquivo xorg configurado na instalação, e por isso a importancia do hwd gerar um xorg a partir do reconhecimento do seu hardware.

O hwd -x gerar um arquivo chamado xorg.conf.vesa e lhe deixa o papel de copia-lo como xorg.conf em /etc/X11.

Já o comando hwd -xa lhe poupa até este trabalho, mas tome cuidado, não saia substituindo seu xorg.conf por aí.

Outra opção muito importante e útil é o comando hwd -u. Existem situações que o pessoal lá do desenvolvimento do xorg, precisa mudar o layout do arquivo xorg, isto é retirar alguma opção, incluir outras quem sabe.

É o comando hwd -u que vai lhe atualizar o modelo do arquivo xorg.conf a ser gerado de acordo com o xorg atual, assim o xorg gerado pelo hwd será sempre válido. Lembre-se de estar conectado a internet antes de executar esta opção.

Bom, este artigo foi bem simples e rápido pois segue os padrões da minha falta de tempo. Peço desculpas por isto.

Agradeço aos Leitores.

System-Hardware Informations

Linux

FreeBSD

A fine installazione questo è ciò che restituisce il comando lspci:

root@tc1100:~# lspci
00:00.0 Host bridge: Intel Corporation 82855PM Processor to I/O Controller (rev 03)
00:01.0 PCI bridge: Intel Corporation 82855PM Processor to AGP Controller (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 81)
00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 01)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC’97 Audio Controller (rev 01)
00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC’97 Modem Controller (rev 01)
01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 420 Go 32M] (rev a3)
02:05.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05)
02:06.0 CardBus bridge: Texas Instruments PCI1620 PC Card Controller (rev 01)
02:06.1 CardBus bridge: Texas Instruments PCI1620 PC Card Controller (rev 01)
02:06.2 System peripheral: Texas Instruments PCI1620 Firmware Loading Function (rev 01)
02:07.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T (rev 01)

apple-command (c) by arguera

Is there any ‘MacOsX’ish counterpart for Linux’ “lsmod”, “lspci”, and the such?
Yes, there is! “kexstat” and “ioreg” could possibly do the trick. Check here for more information!

Finally, ever wondered about how to mount a Debian ISO image and get packets installed from there, so to spare a CD/DVD?
You can do it, just by following these instructions!

xdpyinfo – you can check resolutions
xrandr – check current screen resolution and refresh rate
lspci or lshw – check what is your graphic card
gtf – generate modeline for xorg.conf

I recently received a HP Compaq 2710p and I’m quite surprised by the performance of this convienent tablet.

After using it for a few weeks, I can say that it works well with GNU/Linux (Arch Linux in particular).  There are a few issues, however:

• Use of the stylus occasionally conflicts with the default mouse.
• Brightness of the screen is fixed (unchangeable) upon resume from suspend (both from disk and RAM).

Here is some information about the devices within the computer.

[antony@ARCH ~]$ lspci
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network Connection (rev 03)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HBM (ICH8M-E) LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
02:09.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05)
02:09.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22)
02:09.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 12)
10:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61)

[antony@ARCH ~]$ lsusb
Bus 007 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0001
Bus 006 Device 001: ID 1d6b:0001
Bus 004 Device 003: ID 0461:4d17 Primax Electronics, Ltd
Bus 004 Device 002: ID 08ff:2580 AuthenTec, Inc.
Bus 004 Device 001: ID 1d6b:0001
Bus 005 Device 001: ID 1d6b:0001
Bus 003 Device 004: ID 049f:0081 Compaq Computer Corp.
Bus 003 Device 003: ID 04b4:6560 Cypress Semiconductor Corp. CY7C65640 USB-2.0 "TetraHub"
Bus 003 Device 001: ID 1d6b:0002
Bus 001 Device 004: ID 03f0:171d Hewlett-Packard
Bus 001 Device 001: ID 1d6b:0001 
[antony@ARCH ~]$ uname -a
Linux ARCH 2.6.27-rc9 #2 SMP PREEMPT Thu Oct 9 00:58:03 EDT 2008 i686 Intel(R) Core(TM)2 Duo CPU U7600 @ 1.20GHz GenuineIntel GNU/Linux
[antony@ARCH ~]$ df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda5              15G  2.3G   12G  17% /
none                 1009M     0 1009M   0% /dev/shm
/dev/sda2              92M   15M   73M  17% /boot
/dev/sda6              15G  1.3G   13G  10% /home

I’ve kept the system relatively lightweight. Some applications that work well with this computer are:

• mutt: imap gmail access
• audacious: music
• pidgin: instant messenger
• wget: download manager
• uxterm: terminal
• firefox: browser
• dosbox: games
• dwm: window manager
• bash: shell
• netcfg: network manager

This computer is really convienent to carry around because it is so lightweight.  Soon, I will upgrade to Xorg 7.4 and see if the wacom driver has improved.

Someone comes into #Fedora and asks how to get their wireless card working and don’t know their chipset.  You need to see the output of lspci.  Someone else comes into Fedora and can’t find out why their second hard drive isn’t showing up.  You need to see the output of dmesg.  The problem is, pasting these things into a high-volume IRC channel is not ideal.

Fedora Unity hosts FPaste, which is an easy to use pastebin.

The user must find a way to copy the output from the console to this website and paste the URL back into the channel.   But for many users this is not ideal – especially for those running without X.

What we need is a simple utility than could do something like:

lspci | fpaste

Where the output could get piped into a script to submit to fpaste.org and output the URL back to console.  This would save a lot of time and hassle for end-users in #fedora.

Any takers?

—-

Update:

Possible solution in Comments.  Patch-work done by daMaestro.  Big thanks!

Here are some useful commands that you can use to find (almost) every information that you want to know about your system from the command line. Most of this commands can be run as non-privileged user, but more information can be obtained if (and should be) run as root.:

General system information:

# uname -a

Process information:

# top

(Shift-M to order the list by memory use)

Memory information:

# free -m

BIOS information:

# dmidecode | less
Read more >>