| 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
| ||
|
Date: Fri, 29 Sep 2006 16:32:09 -0700 From: Greg KH <greg@...ah.com> To: Olaf Hering <olaf@...fle.de> Cc: linux-kernel@...r.kernel.org Subject: Re: [PATCH 44/47] PCI: enable driver multi-threaded probe On Wed, Sep 27, 2006 at 08:51:24PM +0200, Olaf Hering wrote: > On Mon, Sep 25, Greg KH wrote: > > > Use at your own risk!!! > > I havent debugged it, but it seems to reorder the driver probing, offb > vs. nvidiafb (-bad, +good): > > -Using unsupported 1024x768 NVDA,Display-A at 90020000, depth=8, pitch=1024 > -PCI: Unable to reserve mem region #2:10000000@...00000 for device 0000:0a:00.0 > -nvidiafb: cannot request PCI regions > +nvidiafb: Device ID: 10de0141 > +nvidiafb: CRTC0 analog found > +nvidiafb: CRTC1 analog found > +nvidiafb: Found OF EDID for head 1 > +nvidiafb: EDID found from BUS1 > +nvidiafb: EDID found from BUS2 > +nvidiafb: CRTC 0 appears to have a CRT attached > +nvidiafb: Using CRT on CRTC 0 > Console: switching to colour frame buffer device 128x48 > -fb0: Open Firmware frame buffer device on /pci@0,f0000000/NVDA,Parent@...VDA,Display-A@0 > +nvidiafb: PCI nVidia NV14 framebuffer (64MB @ 0x90000000) Hm, is things just getting registered out of order, so the wrong video device is used by the kernel? Or by userspace? thanks, greg k-h - 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