On Tue, 07 Mar 2006 11:20:28 -0700 Reg Clemens wrote:
>
> > I meant, narrow it down by identifying the change that broke it.
> > "Somewhere between 2.6.11 and 2.6.15" is not helpful.
>
> Yes, I can do that, but not till this evening.
>
> > The HD (high-definition) audio driver works for me.
> > Are you using a vendor/distro kernel or roll-your-own?
>
> Im building my own kernels.
>
> > Maybe try the latest e1000 driver from
> > http://sourceforge.net/projects/e1000/
>
> Ill give that a shot, but again probably not till this evening.
>
> > Can you post the complete boot log instead of one line of it?
>
> Sure.
> In fact, Ill give you two, first the bad boot from 2.6.16, then a
> good boot from 1.6.11 just in case you need something to compare
> against.
>
> Here they are, In the bad boot, the lines of interest are between
> lines 115 and 120, and start with PCI: Cannot and PCI: Failed .
Both boot logs contains the Cannot messages.
The "bad" log also contains:
Mar 7 10:58:41 deneb kernel: PCI: Failed to allocate mem resource #6:20000@48000000 for 0000:01:00.0
Is device 0:01:00.0 your Nvidia video card?
Is there an updated NVRM driver for it (guessing from your OK boot log)
for 2.6.15 or later?
I suppose an lspci might help. I dunno.
---
~Randy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
