Re: Fw: Re: 2.6.12-rc2-mm2

[Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>]

I didn't see any activity on this.  Did I miss it, or did it
get resolved somehow?

On Tue, 2005-04-12 at 15:12 -0600, Bjorn Helgaas wrote:
> On Tue, 2005-04-12 at 22:43 +0200, Michael Thonke wrote:
> > Okay I irgnored all the ACPI messages blowing ower my screen.
> > The NVidia PCIe 6600GT doesn't work, i tried it with an ATI PCIe X800pro
> > but the same result both
> > graphic adapters won't work.
> 
> OK, let's see if we can figure out more specifically what's broken.
> 
> A 2.6.12-rc2 dmesg log from a previous post included this:
> 
> 	nvidia: module license 'NVIDIA' taints kernel.
> 	ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 16 (level, low) -> IRQ 169
> 	PCI: Setting latency timer of device 0000:04:00.0 to 64
> 
> The 2.6.12-rc2-mm2 dmesg from that post doesn't mention nvidia.  Was
> the nvidia module loaded (check with "lsmod")?  Does it produce any
> dmesg output when it loads?  Does the output of "lspci -vvs04:00.0"
> look different between 2.6.12-rc2 and 2.6.12-rc2-mm2?
> 
> > The Marvell sometimes not work after boot.
> > The driver sk98lin 8.16.2.3 loaded normally, but I can't get them up
> > with ifconfig.
> 
> What sort of error do you see when the Marvell doesn't work?  The
> previous dmesg logs both contain this:
> 
> 	sk98lin: Network Device Driver v8.15.1.3
> 	(C)Copyright 1999-2005 Marvell(R).
> 	ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 17 (level, low) -> IRQ 201
> 	PCI: Setting latency timer of device 0000:02:00.0 to 64
> 	eth0: Marvell Yukon 88E8053 Gigabit Ethernet Controller
> 	      PrefPort:A  RlmtMode:Check Link State
> 
> When it doesn't work, is there something different logged?
> 



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click