Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#5814 - Problem with binary lshwd i1.1.3-4 in repository
Attached to Project:
Arch Linux
Opened by Karolina Lindqvist (karolinali) - Friday, 10 November 2006, 16:56 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 11 November 2006, 10:57 GMT
Opened by Karolina Lindqvist (karolinali) - Friday, 10 November 2006, 16:56 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 11 November 2006, 10:57 GMT
|
DetailsThere is something wrong with lshwd in the repository. If it is compiled from source,
the output of lshwd -d becomes different, even with the same version. Example output of lshwd -d in repository: 00:00.0 0600: 8086:7190 (intel-agp) 00:01.0 0604: 8086:7191 (agpgart) 00:07.0 0601: 8086:7110 (unknown) Output of lshwd -d if same version is rebuilt from source with makepkg 00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (intel-agp) 00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (agpgart) 00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (unknown) |
This task depends upon
Closed by Jan de Groot (JGC)
Sunday, 04 February 2007, 13:20 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in -5 of lshwd: updated table files.
Sunday, 04 February 2007, 13:20 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in -5 of lshwd: updated table files.
Comment by Dan McGee (toofishes) -
Wednesday, 31 January 2007, 01:58 GMT
Is this still a bug? Seems like a one-off issue to me, I do not experience the same problems.