public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Peter Wächtler" <pwaechtler@loewe-komp.de>
To: Adam Harvey <matlhdam@iinet.net.au>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.14 fails to boot on a MediaGX
Date: Thu, 15 Nov 2001 10:19:53 +0100	[thread overview]
Message-ID: <3BF388B9.33CFDBDB@loewe-komp.de> (raw)
In-Reply-To: <E163y2Z-0004OH-00@the-village.bc.nu> <01111513115600.00812@blackbox.local>

Adam Harvey wrote:
> 
> On Wed, 14 Nov 2001 19:17, Alan Cox wrote:
> > Ok on my box it boots fine. As an experiment can you build a kerne with no
> > PCI support (Im not saying it'll be useful production wise but it will tell
> > me if its a PCI issue)
> 
> And, interestingly enough, it does boot with PCI switched off.
> 
> Given that it's a somewhat unusual motherboard, I'm pretty willing to just
> put an ISA network card in there and write it off as flaky hardware, but it's
> odd that it boots under 2.2 with PCI support on.
> 

What kind of motherboard and peripherals are you using?
AKAIK the mediagx only supports one external pci busmaster and only
on a specific "device".

We are using mediaGXm on ETX and had problems with the wiring of the
TVIA CyberPro5050 (combined video+audio controller, audio as busmaster)

Then there are also tweaks in the PCI IDE configuration for mediaGX.
Did you enable that?

  reply	other threads:[~2001-11-15  9:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-13 14:00 2.4.14 fails to boot on a MediaGX Adam Harvey
2001-11-13 23:29 ` Alan Cox
2001-11-14  4:32   ` Adam Harvey
2001-11-14 11:17     ` Alan Cox
2001-11-15  5:11       ` Adam Harvey
2001-11-15  9:19         ` Peter Wächtler [this message]
2001-11-15 16:47           ` Adam Harvey
2001-11-15  6:14       ` Christer Weinigel

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=3BF388B9.33CFDBDB@loewe-komp.de \
    --to=pwaechtler@loewe-komp.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matlhdam@iinet.net.au \
    /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