Date: Tue, 10 Feb 2009 17:57:43 +0000 From: "Bruce M. Simpson" <bms@FreeBSD.org> To: Robert Noland <rnoland@FreeBSD.org> Cc: "S.N.Grigoriev" <serguey-grigoriev@yandex.ru>, Markus Hitter <mah@jump-ing.de>, freebsd-stable@freebsd.org Subject: Re: Unhappy Xorg upgrade Message-ID: <4991C017.8080903@FreeBSD.org> In-Reply-To: <1234246034.1524.27.camel@ferret.2hip.net> References: <329181233306971@webmail57.yandex.ru> <985A59F2-20CC-4779-A000-018E52B5BFA9@jump-ing.de> <101781233319948@webmail36.yandex.ru> <4983A3AE.90804@FreeBSD.org> <498F901A.7000900@FreeBSD.org> <1234159237.23838.3.camel@ferret.2hip.net> <4990835A.3020303@FreeBSD.org> <1234208586.1524.17.camel@ferret.2hip.net> <4990BC99.1070108@FreeBSD.org> <1234246034.1524.27.camel@ferret.2hip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert Noland wrote: > ... > Ok, lets try another test... There is a scanpci util in the > libpciaccess port. We don't install it, but it does get built. Build > the port and run scanpci -v as root from the console. That should poke > all the pci devices on the box and tell you about them. See if that is > able to trigger the issue. > Well spotted. I saw this tool in "locate" output and was going to try it the other day, although I saw it didn't get installed, so assumed it was historical. Yes, This immediately triggered the issue without even running X on a fresh boot.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4991C017.8080903>