| 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
| ||
|
Message-Id: <200609290017.34412.luke@dashjr.org> Date: Fri, 29 Sep 2006 00:17:32 +0000 From: Luke-Jr <luke@...hjr.org> To: Alan Cox <alan@...rguk.ukuu.org.uk>, "Mark Knecht" <markknecht@...il.com> Cc: linux-kernel@...r.kernel.org Subject: Re: PCI bridge missing On Thursday 28 September 2006 21:39, you wrote: > Anyway, maybe you haven't cold booted the machine and could try that? It's been cold-booted a few times, though I can't guarantee that for each kernel I tried. On Thursday 28 September 2006 23:14, Alan Cox wrote: > Ar Iau, 2006-09-28 am 16:24 -0500, ysgrifennodd Luke-Jr: > > However, this bridge is completely ignored and unseen by Linux. It does > > not show up in lspci or dmesg (as far as I can tell) at all. The > > daughterboard is plugged in, and the PCI cards on it are powered. > > lspci -vvxxx would be interesting Will do tomorrow. > Linux on PC assumes the BIOS did the work needed pci=nobios doesn't bypass that assumption? (I tried that too) > so if there is some custom "enabler" driver in the Windows for it that might > explain problems. Some old Debian (2.2) manual at least implied it worked at one point. That's where I compared the lspci from. So this would be a regression, a hardware failure, or a misconfiguration. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists