From: Christian <evilninja@gmx.net>
To: linuxppc-dev@ozlabs.org
Cc: "Brian V. Madzarevic" <Brian.Madzarevic@uav.com>
Subject: Re: 2.6.11 prep image on radstone ppc4a not booting
Date: Sat, 12 Mar 2005 17:34:07 +0100 [thread overview]
Message-ID: <423319FF.8090906@gmx.net> (raw)
In-Reply-To: <A79EE6739F2C7348A857541FB5CD92D6011566F6@asimail1.rb.uav.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Brian V. Madzarevic wrote:
> Setting PCI interrupts for a "Blackhawk (Powerstack)"
> PCI: Cannot allocate resource region 0 of device 0000:00:0b.1
[...]
i don't know about these, hopefully the ppc gurus could explain these
messages.
> Linux Tulip driver version 1.1.13 (May 11, 2002)
> tulip0: EEPROM default media type Autosense.
- --^
did you try the de4x5 driver instead of the tulip one? if not...
> CONFIG_NET_TULIP=y
> # CONFIG_DE2104X is not set
> CONFIG_TULIP=y
> # CONFIG_TULIP_MWI is not set
> # CONFIG_TULIP_MMIO is not set
> # CONFIG_TULIP_NAPI is not set
> # CONFIG_DE4X5 is not set
- ----^
here it is ;)
could be worth a try.
Christian.
- --
BOFH excuse #80:
That's a great computer you have there; have you considered how it would
work as a BSD machine?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCMxn/C/PVm5+NVoYRAk1mAKCKCWXxlrHg031uktVx4BxtEMwePACg4hDq
muiR9Exk06I4vS0Xb4L4S3w=
=dqrh
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-03-12 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 18:11 2.6.11 prep image on radstone ppc4a not booting Brian V. Madzarevic
2005-03-12 16:34 ` Christian [this message]
2005-03-18 15:59 ` Sven Luther
2005-03-18 16:37 ` 2.6.11 prep powerstack and sym53c8xx brokeness (was Re: 2.6.11 prep image on radstone ppc4a not booting) Sven Luther
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=423319FF.8090906@gmx.net \
--to=evilninja@gmx.net \
--cc=Brian.Madzarevic@uav.com \
--cc=linuxppc-dev@ozlabs.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).