Re: [gentoo-user] Dumb `lspci -F` question...

2005-10-29 Thread Stroller 


On Oct 28, 2005, at 5:41 pm, Christoph Gysin wrote:


Stroller wrote:
Do you have any references on this, please? I'm obviously using 
different search terms from you, because I can't find anything about 
this bug on Google.


search term:
bug lspci -F :


Thank you.

I have now emerged pciutils-2.2.0-r1  it resolves the problem - it 
reads -x ouput produced both by itself  by the previous version of 
pciutils (2.1.11-r3) on my other machine.


I have opened a bug to say pciutils-2.2.0-r1 works for me. If anyone 
else can confirm then that'd be great.

http://bugs.gentoo.org/show_bug.cgi?id=110769

Stroller.

--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Dumb `lspci -F` question...

2005-10-28 Thread Christoph Gysin 

Stroller wrote:
Can anyone explain to me how to use this, please? Try as I might I don't 
seem to be getting it right.


Seems to be a bug in lspci. It works here like it should.

I have tried this on a couple of machines. The output produced by `lspci 
-x` _looks_ reasonable - I've attached foo.txt.


The difference to my output is the leading zeros.


:00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host 
bridge (rev 03)

  ^
The following will work:

$ lspci -x | sed 's/^://'  foo.txt
$ lspci -F foo.txt

Nonetheless this seems like a bug and should be fixed. Could you file a bug and 
reference it here?


Christoph
--
echo mailto: NOSPAM !#$.'*'|sed 's. ..'|tr * !#:2 [EMAIL PROTECTED]
--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Dumb `lspci -F` question...

2005-10-28 Thread Christoph Gysin 

Christoph Gysin wrote:
Nonetheless this seems like a bug and should be fixed. Could you file a 
bug and reference it here?


Searching google turns out that it has already been fixed. Update to the latest 
pciutils will fix the issue.


Christoph
--
echo mailto: NOSPAM !#$.'*'|sed 's. ..'|tr * !#:2 [EMAIL PROTECTED]
--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Dumb `lspci -F` question...

2005-10-28 Thread Holly Bostick 
Christoph Gysin schreef:
 Christoph Gysin wrote:
 
 Nonetheless this seems like a bug and should be fixed. Could you
 file a bug and reference it here?
 
 
 Searching google turns out that it has already been fixed. Update to
 the latest pciutils will fix the issue.
 

Why search Google and not b.g.o itself, or packages.gentoo.org? Either
manually or-- if you use Firefox-- using the Firefox b.g.o search
engine? Seems like a waste of effort to have to filter irrelevant hits
from Google when one already knows that the status of the issue will be
recorded on b.g.o (if a bug was filed and resolved) or
packages.gentoo.org (in the Changelog for the revision/update to pciutils).

Just wondering.

Holly

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Dumb `lspci -F` question...

2005-10-28 Thread Christoph Gysin 

Holly Bostick wrote:

Why search Google and not b.g.o itself, or packages.gentoo.org? Either
manually or-- if you use Firefox-- using the Firefox b.g.o search
engine? Seems like a waste of effort to have to filter irrelevant hits
from Google when one already knows that the status of the issue will be
recorded on b.g.o (if a bug was filed and resolved) or
packages.gentoo.org (in the Changelog for the revision/update to pciutils).


Because this is a pciutils issue, and has nothing to do with gentoo. The 
Changelog will only report a revision bump.
Actually I did search b.g.o first, but there were no relevant results. Google 
turned out that debian had patched this some time ago, and now it is already 
included upstream.


Christoph
--
echo mailto: NOSPAM !#$.'*'|sed 's. ..'|tr * !#:2 [EMAIL PROTECTED]
--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Dumb `lspci -F` question...

2005-10-28 Thread Stroller 


On Oct 28, 2005, at 10:44 am, Christoph Gysin wrote:


Christoph Gysin wrote:
Nonetheless this seems like a bug and should be fixed. Could you file 
a bug and reference it here?


Searching google turns out that it has already been fixed. Update to 
the latest pciutils will fix the issue.


Hi,

Do you have any references on this, please? I'm obviously using 
different search terms from you, because I can't find anything about 
this bug on Google.


I've just run esync  am only offered the same version of pciutils that 
I already have - 2.1.11-r5. If you can provide a link to the pciutils 
bug then I'll request a version bump with b.g.o. (I'd also like to know 
more about this so I can advise my customers, should I request a `lspci 
-x` output from them).


Stroller.

--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Dumb `lspci -F` question...

2005-10-28 Thread Christoph Gysin 

Stroller wrote:
Do you have any references on this, please? I'm obviously using 
different search terms from you, because I can't find anything about 
this bug on Google.


search term:
bug lspci -F :

... brings us to:
http://www.google.ch/search?q=bug+%22lspci+-F%22+%22%3A%22+

... where hit number 3 leads us to:
http://packages.debian.org/changelogs/pool/main/p/pciutils/pciutils_2.1.11-15.1/changelog

... which says:
* fix lspci -F for new or old lspci -x format (closes: #261536)
 based on patch by Ben Pfaff

... where #261536 is a link to:
http://bugs.debian.org/261536

I've just run esync  am only offered the same version of pciutils that 
I already have - 2.1.11-r5. If you can provide a link to the pciutils 
bug then I'll request a version bump with b.g.o. (I'd also like to know 
more about this so I can advise my customers, should I request a `lspci 
-x` output from them).


The newest release is still masked by keyword. To unmask:

# mkdir -p /etc/portage
# echo sys-apps/pciutils ~x86  /etc/portage/package.keywords
# emerge -avt sys-apps/pciutils

Christoph
--
echo mailto: NOSPAM !#$.'*'|sed 's. ..'|tr * !#:2 [EMAIL PROTECTED]
--
gentoo-user@gentoo.org mailing list

[gentoo-user] Dumb `lspci -F` question...

2005-10-27 Thread Stroller 
Reading the lspci manpage I can across an interesting  potentially 
useful flag:


   -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.

Can anyone explain to me how to use this, please? Try as I might I 
don't seem to be getting it right.


I would have thought that the correct way to handle this would be:
  $ lspci -x  foo.txt

But the results I get are not helpful:

  $ lspci -F foo.txt
  $ lspci -F foo.txt -vv
  $ lspci -F foo.txt -vvv
  $ lspci -F foo.txt -vt
  -[00]-
  $ lspci -F foo.txt -t
  -[00]-

I have tried this on a couple of machines. The output produced by 
`lspci -x` _looks_ reasonable - I've attached foo.txt.


Stroller.

:00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host 
bridge (rev 03)
00: 86 80 90 71 06 01 10 22 03 00 00 06 00 40 00 00
10: 08 00 00 f8 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00

:00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP 
bridge (rev 03)
00: 86 80 91 71 1f 00 20 02 03 00 04 06 00 80 01 00
10: 00 00 00 00 00 00 00 00 00 01 01 40 f0 00 a0 22
20: 00 f0 f0 f7 f0 ff 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 8c 00

:00:02.0 CardBus bridge: Texas Instruments PCI1450 (rev 03)
00: 4c 10 1b ac 07 00 10 02 03 00 07 06 20 a8 82 00
10: 00 00 00 50 a0 00 00 02 00 02 05 b0 00 00 00 20
20: 00 f0 3f 20 00 00 40 20 00 f0 7f 20 00 40 00 00
30: fc 40 00 00 00 44 00 00 fc 44 00 00 0b 01 00 05
40: 14 10 30 01 01 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

:00:02.1 CardBus bridge: Texas Instruments PCI1450 (rev 03)
00: 4c 10 1b ac 07 00 10 02 03 00 07 06 20 a8 82 00
10: 00 00 10 50 a0 00 00 02 00 06 09 b0 00 00 80 20
20: 00 f0 bf 20 00 00 c0 20 00 f0 ff 20 00 48 00 00
30: fc 48 00 00 00 4c 00 00 fc 4c 00 00 0b 02 c0 05
40: 14 10 30 01 01 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

:00:03.0 Ethernet controller: 3Com Corporation 3c556B CardBus [Tornado] 
(rev 20)
00: b7 10 56 60 17 00 10 02 20 00 00 02 08 50 80 00
10: 01 18 00 00 00 14 10 e8 00 10 10 e8 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 b7 10 56 63
30: 00 00 00 00 50 00 00 00 00 00 00 00 0b 01 0a 0a

:00:03.1 Communication controller: 3Com Corporation Mini PCI 56k Winmodem 
(rev 20)
00: b7 10 07 10 13 00 10 02 20 00 80 07 08 50 00 00
10: 01 20 00 00 00 1c 10 e8 00 18 10 e8 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 b7 10 59 61
30: 00 00 00 00 50 00 00 00 00 00 00 00 0b 01 0a 0a

:00:05.0 Multimedia audio controller: Cirrus Logic CS 4614/22/24 
[CrystalClear SoundFusion Audio Accelerator] (rev 01)
00: 13 10 03 60 06 00 10 04 01 00 01 04 00 40 00 00
10: 00 00 10 e8 00 00 00 e8 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 14 10 53 01
30: 00 00 00 00 40 00 00 00 00 00 00 00 0b 01 04 18

:00:07.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02)
00: 86 80 10 71 0f 00 80 02 02 00 80 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

:00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
00: 86 80 11 71 05 00 80 02 01 80 01 01 00 40 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 1c 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

:00:07.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01)
00: 86 80 12 71 05 00 80 02 01 00 03 0c 00 40 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 21 1c 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 04 00 00

:00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
00: 86 80 13 71 03 00 80 02 03 00 80 06 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

:01:00.0 VGA compatible controller: S3 Inc. 86C270-294 Savage/IX-MV (rev 11)
00: 33 53 12 8c 07 00 30 02 11 00 00 03 08 40 00 00
10: 00 00 00 f0 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 14 10 7f 01
30: 00 00 00 00 dc 00 00 00 00 00 00 00 0b 01 04 ff

:02:00.0 Network controller: RaLink Ralink RT2500 802.11 Cardbus Reference 
Card (rev 01)
00: 14 18 01 02 06 00 10 04