TO the sticky: Numeric IDs in one step?

TO the sticky:
My wireless doesn’t work - a primer on what I should do next
Section 2 b)

I guess it would be easier for the user if she/he would just use one command instead of /sbin/lspci and than /sbin/lspci -n and compare both outputs to find the right section that inhales the hexadecimal numeric IDs for the wireless LAN/wireless/WLAN/bluetooth/… devices.

What do you (all and especially the sticky’s author, dear Larry Finger) think of alternatives like:

/sbin/lspci -nn

e.g.->

...]
02:07.0 Network controller [0280]: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection [8086:4220] (rev 05)
...]

or

/sbin/lspci -nn -v

...]
02:07.0 Network controller [0280]: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection [8086:4220] (rev 05)
	Subsystem: Intel Corporation Samsung P35 integrated WLAN [8086:2731]
	Flags: bus master, medium devsel, latency 32, IRQ 20
	Memory at b8002000 (32-bit, non-prefetchable) [size=4]
	Capabilities: <access denied>
	Kernel driver in use: ipw2200
...]

or

sudo /sbin/lspci -nn -v

and type root password

...]
02:07.0 Network controller [0280]: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection [8086:4220] (rev 05)
	Subsystem: Intel Corporation Samsung P35 integrated WLAN [8086:2731]
	Flags: bus master, medium devsel, latency 32, IRQ 20
	Memory at b8002000 (32-bit, non-prefetchable) [size=4]
	Capabilities: [dc] Power Management version 2
	Kernel driver in use: ipw2200
...]

Regards
Martin Seidler
(pistazienfresser)[/size][/size]

Very usefull. Thank you Martin!!!;):slight_smile:

On 04/05/2011 05:36 AM, pistazienfresser wrote:
>
> TO the sticky:
> ‘My wireless doesn’t work - a primer on what I should do next’
> (http://tinyurl.com/47ukyyh)
> Section 2 b)
>
> I guess it would be easier for the user if she/he would just use one
> command instead of /sbin/lspci and than /sbin/lspci -n and compare both
> outputs to find the right section that inhales the hexadecimal numeric
> IDs for the wireless LAN/wireless/WLAN/bluetooth/… devices.
>
> What do you (all and especially the sticky’s author, dear Larry Finger)
> think of alternatives like:
>
>
> Code:
> --------------------
> /sbin/lspci -nn
> --------------------
>
> e.g.->
>
> Code:
> --------------------
> …]
> 02:07.0 Network controller [0280]: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection [8086:4220] (rev 05)
> …]
> --------------------
>
> or
>
> Code:
> --------------------
> /sbin/lspci -nn -v
> --------------------
>

I like this one, but it should be ‘/sbin/lspci -nnv’. The arguments do not have
to be split.

Unfortunately, I cannot edit the sticky. Someone else will have to do it.

So it would be something like:

…]
(2) Determine what device you have.

(a) If it is a USB adapter, …]
(b) If it is a PCI device, you should enter the command

/sbin/lspci -nnv

in a
terminal. The output will look like:


00:00.0 Host bridge [0600]: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller [8086:2590] (rev 03)
	Subsystem: Samsung Electronics Co Ltd Device [144d:c01a]
	Flags: bus master, fast devsel, latency 0
	Capabilities: <access denied>
	Kernel driver in use: agpgart-intel

00:02.0 ...
.... snip ...]

02:05.0 Ethernet controller [0200]: Broadcom Corporation BCM4401-B0 100Base-TX [14e4:170c] (rev 02)
	Subsystem: Samsung Electronics Co Ltd Device [144d:c01a]
	Flags: bus master, fast devsel, latency 32, IRQ 22
	Memory at b8000000 (32-bit, non-prefetchable) [size=8]
	[virtual] Expansion ROM at 84000000 [disabled] [size=64]
	Capabilities: <access denied>
	Kernel driver in use: b44

02:07.0 Network controller [0280]: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection [8086:4220] (rev 05)
	Subsystem: Intel Corporation Samsung P35 integrated WLAN [8086:2731]
	Flags: bus master, medium devsel, latency 32, IRQ 20
	Memory at b8002000 (32-bit, non-prefetchable) [size=4]
	Capabilities: <access denied>
	Kernel driver in use: ipw2200

02:09.0  ...
.... snip ...]

A recent computer will have lots of connections to the PCI bus, which is why I snipped out a number of entries from my machine. The PCI wireless device here is the 2200BG from Intel. To identify surely your wireless device the PCI vendor and product ID codes are really needed. For the Intel 2200BG, these data are *8086:4220*[/size][/size] .
Also it is informative to know the driver that this device is currently using. When you post a request for help, please include both or just copy and paste the whole paragraph for the wireless device.

(c) If you cannot find a wireless ...]

Should code tags been used in this passage (and maybe in the rest of the sticky, too) or not? Have you had any users copying the ''s in the past?
(I once copied and pasted the “#” for a root’s terminal…:shame:/:/lol!)

Regards
Martin
(pistazienfresser)[/size]

On 04/05/2011 02:04 PM, pistazienfresser wrote:
>
> Should code tags been used in this passage (and maybe in the rest of
> the sticky, too) or not? Have you had any users copying the ''s in the
> past?
> (I once copied and pasted the “#” for a root’s
> terminal…:shame:/:/lol!)

Code tags should probably be used. I’m not sure how many people copy and paste.

IMHO, using the “-v”-switch in order to (only) determine which PCI-device is present gives a lot of extra information not needed in most cases.

Additionally, filtering the output for the section needed would have to be done by the user and we know what happens then:

a) $USER posts all of the output, meaning we get > 95% stuff not related to a wireless PCI device

b) $USER only posts the last few lines (= what can be seen in the terminal without scrolling)

c) $USER doesn’t post any information but something like “this is a lot of output, what next?”

I have already given up in recommending to use the script from framp (which would do this and a lot more automatically, but hey, why doing something the easy way if one can go the complicated way? After all, this is linux and so it HAS to be complicated ;-)), so if you really want to have information from $USER by giving her/him commands she/he enters into a terminal, then think about SNR and maybe a good way of filtering the output.

In a nutshell:

/sbin/lspci -nnk

or

/sbin/lspci -nnk | grep -A2 -i net

as a normal user gives you -in most cases- the information needed (by using “-k” even with some extra information if a driver already exists on the system) without a lot of extra “noise” (and if that one is really needed, one could still ask for “-v”).

Just my 2¢

Thanks a lot, Akoellh.

Akoellh’s variant of changing that sticky seems to me being better suited than my original proposal.

In my personal opinion that leaves the question which of Akoellh’s proposed commands to include:

/sbin/lspci -nnk

or

/sbin/lspci -nnk | grep -A2 -i net

or

  • both (maybe one of them in a Footnote?)

Being not so experienced myself I would guess that it would be easier for (a even lesser experienced) user to find a line/paragraph in a bigger output than to bring the second command correct into a terminal emulator/terminal application/‘terminal’[1].
My thoughts on that are:

  • Do many beginners realty know how to type a “|”?
  • Would a longer command just scare the users?
  • Copy-and-Past to a ‘terminal’ has its own difficulties[2]

What do you all

  • Akoellh and other experienced users but also the beginners as targeted ‘consumers’ of that sticky -
    think of that?

Regards
Martin
(pistazienfresser)

[1]
Or however those ‘windows through the graphical environment’/'applications to use a Command Line Interface (CLI) in a graphical environment# like GNOME terminal or konsole should be called.

[2]
Because the key-combinations [v]+[Control] and [c]+[Control] will not work in this ‘terminal’ the way most users may expect (being used to a graphical environment/an other operating system).

Actually, Akoellh’s suggestion of using @framp’s script is best. That way,
we get all the information in a very compact fashion. The sticky should advocate
getting that script, running it, and posting the output at openSUSE’s pastebin site.

Perhaps we could even get that script into some package that is officially part
of openSUSE, or at least at Packman. @framp - If you read this, would that be OK?
Is the script licensed under GPL, of some other suitable license?

Pls keep in mind this script tries to solve 2 problems:

No1: Get information for the people who try to help (NWCollect)
No2: Detect common misconfigurations and provide help to fix them (NWEliza)

I think it’s easier to write a 10 liner script to collect the info about the ID. Just let me know and I’ll provide this script.