linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: <linuxppc-dev@lists.linuxppc.org>, harry eaton <bumpelo@home.com>
Subject: Re: No video or console with 2.4.10 on Tanzania
Date: Mon, 31 Dec 2001 00:04:23 +0100	[thread overview]
Message-ID: <20011230230423.20339@smtp.noos.fr> (raw)
In-Reply-To: <000901c19168$de54a4c0$6400a8c0@hwrd1.md.home.com>


>
>> I'm trying to upgrade to a 2.4.x based kernel, but it's not working.
>> Everything appears to stop after "arch: exit" is displayed, but
>> in fact the whole booting process continues fine, except nothing
>> is ever sent again to the screen. The log file reveals:
>> ...
>> Fixups for bus 01
>> Unknown bridge resource 0: assuming transparent
>> ...
>> PCI:00:11.0:Resource 0: 81000000-81ffffff (f=3D200)
>> PCI:Cannot allocate resource region 0 of device 00:11.0
>> ...
>> PCI: Failed to allocate resource 0 (8000-7ffffff) for 00:11.0
>>
>> plus other similar message about devices 00:10.0 and 00:0e.0
>>
>> I've tried Benh's latest from ppckernel.org, also the bitkeeper 2.4 =
>> stable,
>> plus a few others, even rolling my own minimal kernel from the 2.4.10
>> source tree in the latest YDL distribution. They all do the same thing.
>>
>> This is on my Starmax 4160 (Tanzania) system. I use the built-in video
>> (ATI 264 vt) and it all works great with 2.2 kernels.

Please, send me the complete boot log under both 2.2 and 2.4, and the
result of lspci -vv (run as root) on both kernels.

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2001-12-30 23:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-30 19:33 No video or console with 2.4.10 on Tanzania harry eaton
2001-12-30 23:04 ` Benjamin Herrenschmidt [this message]

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=20011230230423.20339@smtp.noos.fr \
    --to=benh@kernel.crashing.org \
    --cc=bumpelo@home.com \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).