linux-kernel - Bug? Needed to use pci=assign-busses

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Mon, 27 Nov 2006 13:18:30 +0100
From:	Oyvind Kristiansen <oyvindk@...ree.com>
To:	linux-kernel@...r.kernel.org
Subject: Bug? Needed to use pci=assign-busses

Hi!
I've had to use the kernel parameter pci=assign-busses to enable a Realtek 
ethernet chip.

The chip does not show up in lspci without this kernel option.

Attached are 4 files:
-klog.txt & lspci.txt for the case that pci=assign-busses are enabled
-klog2.txt & lspci2.txt for the case that this option is not enabled

The kernel that is running is 2.6.17-10-generic and the distribution is 
Kubuntu Edgy without any patches.

Best regards,
Øyvind Kristiansen

-- 
Oyvind Kristiansen
R&D Engineer
Q-Free ASA

View attachment "klog2.txt" of type "text/plain" (20843 bytes)

View attachment "lspci.txt" of type "text/plain" (1731 bytes)

View attachment "lspci2.txt" of type "text/plain" (1639 bytes)

View attachment "klog.txt" of type "text/plain" (21500 bytes)