public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Riccardo <riccardo@kaffe.org>
To: Brad Boyer <flar@allandria.com>
Cc: linux-m68k@vger.kernel.org
Subject: Re: vmlinuz-2.6.29-1-11May on IIfx
Date: Fri, 15 May 2009 10:32:46 +0200	[thread overview]
Message-ID: <F7CDF992-412A-11DE-9D14-00050249ADE1@kaffe.org> (raw)
In-Reply-To: <20090514210912.GA4292@cynthia.pants.nu>

Hi Brad,

On Thursday, May 14, 2009, at 11:09  PM, Brad Boyer wrote:

>> booting into 2.6.26 I see the driver used is the mac8390. From dmesg 
>> of
>> 2.6.26
>>
>> [42949395.010000] mac8390.c: v0.4 2001-05-15 David Huggins-Daines
>> <dhd@debian.org> and others
>> [42949395.030000] eth0: Memory length resource for slot A not found,
>> probing
>> [42949395.040000] eth0: EtherNet card in slot A (type apple)
>> [42949395.050000] MAC 00:80:ad:13:7c:d0 IRQ 57, 32 KB shared memory at
>> 0xfaad0000,  32-bit access.
>
> Did this ethernet card work in an older kernel? The card type detection
> in mac8390.c is partially based on guesses and just trying different
> cards, as I remember. It's possible that it's detecting the wrong type,
> particularly since it isn't finding all the NuBus ROM resources it is
> expecting to be present on this card type. I suspect that it's not
> accessing the card correctly. Both the error messages are that the
> card isn't in a sane state based on what the driver tried to do.

maybe I did not express myself clearly: in 2.6.29 the card doesn't work 
and I typed the error message manually,

I then rebooted into 2.6.26, where the card still worked, and pasted 
its dmesg.

Riccardo


  parent reply	other threads:[~2009-05-15  8:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-14 17:35 vmlinuz-2.6.29-1-11May on IIfx Riccardo
2009-05-14 21:09 ` Brad Boyer
2009-05-15  8:14   ` Michael Schmitz
2009-05-15  9:26     ` Riccardo
2009-05-15  8:32   ` Riccardo [this message]
2009-05-15 10:28     ` Finn Thain
2009-05-17  6:10       ` Brad Boyer
2009-05-17  8:29         ` Geert Uytterhoeven
2009-05-17  6:11     ` Brad Boyer

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=F7CDF992-412A-11DE-9D14-00050249ADE1@kaffe.org \
    --to=riccardo@kaffe.org \
    --cc=flar@allandria.com \
    --cc=linux-m68k@vger.kernel.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