From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Reg Clemens <reg@dwf.com>
Cc: reg@dwf.com, rlrevell@joe-job.com, torvalds@osdl.org,
linux-kernel@vger.kernel.org, reg@deneb.dwf.com
Subject: Re: vmlinuz-2.6.16-rc5-git8 still nogo with Intel D945 Motherboard
Date: Tue, 7 Mar 2006 10:46:46 -0800 [thread overview]
Message-ID: <20060307104646.9b2e193d.rdunlap@xenotime.net> (raw)
In-Reply-To: <200603071820.k27IKSsm003595@deneb.dwf.com>
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
next prev parent reply other threads:[~2006-03-07 18:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 3:40 Reg Clemens
2006-03-07 3:48 ` Lee Revell
2006-03-07 8:23 ` Reg Clemens
2006-03-07 16:13 ` Lee Revell
2006-03-07 16:18 ` Randy.Dunlap
2006-03-07 18:20 ` Reg Clemens
2006-03-07 18:46 ` Randy.Dunlap [this message]
2006-03-07 19:32 ` Reg Clemens
2006-03-07 20:00 ` Randy.Dunlap
2006-03-07 20:22 ` Reg Clemens
2006-03-07 21:55 ` Randy.Dunlap
2006-03-07 18:38 ` Reg Clemens
2006-03-07 18:50 ` Lee Revell
2006-03-07 4:01 ` Randy.Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060307104646.9b2e193d.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=reg@deneb.dwf.com \
--cc=reg@dwf.com \
--cc=rlrevell@joe-job.com \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®