mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Reg Clemens <reg@dwf.com>
Cc: rlrevell@joe-job.com, reg@dwf.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 08:18:06 -0800	[thread overview]
Message-ID: <20060307081806.0af1d2c4.rdunlap@xenotime.net> (raw)
In-Reply-To: <200603070823.k278NE9o006674@deneb.dwf.com>

On Tue, 07 Mar 2006 01:23:14 -0700 Reg Clemens wrote:

> > On Mon, 2006-03-06 at 20:40 -0700, Reg Clemens wrote:
> > > 
> > > Anyone working this problem? 
> > 
> > Why don't you try to narrow it down some?
> > 
> 
> For what its worth, this is a D945GNT

I have one of the 3 variants of that board.

> It has ICH7 series Video/Sound/Ethernet on board.
> The Video works in vesa mode, but not in native mode.
> The sound is not recognized.

The HD (high-definition) audio driver works for me.
Are you using a vendor/distro kernel or roll-your-own?

> The ethernet is recognized by some kernels, but does not work.

Maybe try the latest e1000 driver from
  http://sourceforge.net/projects/e1000/

> It has ATA and SATA which both work.
> 
> My sound card is a Nvidia 6600, it works fine with 2.6.11.
> 
> At the moment I run with a 2.6.11 kernel, an ethernet card and a Soundblaster.
> Other than the Onboard hardware not being supported, things work with the
> 2.6.11 kernel.  this PCI error only occurs with later kernels.

Can you post the complete boot log instead of one line of it?

> I could play halfsies to determine just when the PCI error starts, but
> another responder had noted that he had similar problems after some
> 'large PCI changes'  (Im sure he mentioned what version they occurred
> in, but it would take some searching to find his e-mail)

---
~Randy

  parent reply	other threads:[~2006-03-07 16:16 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 [this message]
2006-03-07 18:20       ` Reg Clemens
2006-03-07 18:46         ` Randy.Dunlap
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=20060307081806.0af1d2c4.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®