noncontingous DMA segments with mc0 at obio

khymazeotrope.org wrote:
> Oh, that's almost certainly unrelated then. This
problem has nothing to
> do with whether a monitor is attached. I remember you
mentioning this
> problem now... someone else mentioned that NetBSD may
have a problem
> with the screen size that's reported when you don't
have a monitor hooked
> up--and that seems like a likely explanation to me.
Serial console seems
> like your best bet for figuring this one out. For
example, if NetBSD
> thinks your screen resolution is 0x0 when you don't
have a monitor,
> it's likely that the code that tries to write to the
screen will crash.

I am sorry if I was unclear - I was not trying to imply the
problem was 
with video.  My troubleshooting had been very rudimentary
thus far.  All 
I had time to do was pull it out of my rack (detaching from
network) so 
that I could connect a monitor.  My assumption was that I
had an 
intermittent booting problem.  However, it always
"worked fine" with a 
monitor, but I could not telnet/ssh in when it went back on
the shelf. 
This is consistent with the mc0 problem mentioned.  I never
tested 
network connectivity when I had a monitor attached.

Tim
-- 
Tim & Alethea
christtrek.org

khymazeotrope.org wrote:
> BTW, not being able to boot without a monitor is a
long-standing
> problem. There's a thread from 1996 about the same
thing:
> http://mail-index.netbsd.org/port-mac68k/1996/01/26
/0007.html
> 
> Most of the responses seem to suggest just wiring up a
jumper so the
> Mac thinks there's a monitor attached (or plug in a
Mac->VGA adapter,
> which'll have the same effect). It's possible that the
problem you're
> running into now isn't the same as the one people were
having back
> then... so running monitor-less was working for you
with NetBSD 2.1?

I have several VGA adapters I use for this purpose with my
old Macs.  I 
tried the paper clip trick once with a IIsi and couldn't get
it to work, 
and in fact, the IIsi later refused to boot at all.  I might
have killed 
it somehow...

Tim

-- 
Tim & Alethea
christtrek.org

On Thu, Dec 14, 2006 at 01:27:03AM -0600, Tim & Alethea
Larson wrote:
> I am sorry if I was unclear - I was not trying to imply
the problem was 
> with video.  My troubleshooting had been very
rudimentary thus far.  All 

Right, I understand... but what I meant was that the
presence or absence
of video was unlikely to affect whether the ethernet driver
could allocate
its memory or not. If you didn't see the "receive DMA
buffer not
contiguous!" message when booting with a monitor, the
problem you're
having when booting without a monitor is probably unrelated
to the
ethernet.

> I had time to do was pull it out of my rack (detaching
from network) so 
> that I could connect a monitor.  My assumption was that
I had an 
> intermittent booting problem.  However, it always
"worked fine" with a 
> monitor, but I could not telnet/ssh in when it went
back on the shelf. 
> This is consistent with the mc0 problem mentioned.  I
never tested 
> network connectivity when I had a monitor attached.

Hmm, how do you know it worked fine with a monitor attached
if you didn't
test network connectivity? And how do you know that only the
network is
the only thing that's the problem when booting without a
monitor? Maybe
it's crashed and waiting at the debugger prompt or
something... I'm just
saying that at least from what I've heard so far, I don't
think you're
seeing this mc0 problem. And as I mentioned, the mc0 problem
seems to
have happened post-3.x, i.e., NetBSD 3.1 doesn't have this
problem.

Anyways, when you get a chance, see if you can try serial
console... getting some more facts about what's happening
will be more
useful than speculating about the cause 
-- 
Name: Dave Huang         |  Mammal, mammal / their names are
called /
INet: khymazeotrope.org |  they raise a paw / the bat, the cat
/
FurryMUCK: Dahan         |  dolphin and dog / koala bear and
hog -- TMBG
Dahan: Hani G Y+C 31 Y++ L+++ W- C++ T++ A+ E+ S++ V++ F-
Q+++ P+ B+ PA+ PL++

khymazeotrope.org wrote:
> Right, I understand... but what I meant was that the
presence or absence
> of video was unlikely to affect whether the ethernet
driver could allocate
> its memory or not. If you didn't see the "receive
DMA buffer not
> contiguous!" message when booting with a monitor,
the problem you're
> having when booting without a monitor is probably
unrelated to the
> ethernet.

I wasn't implying that video did affect ethernet.  I did not
check for 
DMA error messages.  What I know is that I couldn't log in
remotely, 
which _happened_ to coincide with being headless.  I think
it unlikely 
that being headless is the problem, as that's how the
machine has run 
for most of the past year under 2.1, and I hadn't heard of
anyone else 
with that problem in 3.x either.  But I could be wrong...

> Hmm, how do you know it worked fine with a monitor
attached if you didn't
> test network connectivity? And how do you know that
only the network is
> the only thing that's the problem when booting without
a monitor? Maybe

Again, as my assumption was simply an intermittent booting
problem, 
"worked fine" meant that it did in fact boot. 
Beyond that I hadn't had 
time to diagnose.

> Anyways, when you get a chance, see if you can try
serial
> console... getting some more facts about what's
happening will be more
> useful than speculating about the cause 

This is true.  The problem is finding the time, and then
seeing if I 
remember how to do a serial console, and then hoping I can
find the 
cable to do it with.  


Tim

-- 
Tim & Alethea
christtrek.org

On Thu, Dec 14, 2006 at 06:11:34PM -0600, Tim & Alethea
Larson wrote:
> This is true.  The problem is finding the time, and
then seeing if I 
> remember how to do a serial console, and then hoping I
can find the 
> cable to do it with.  

Yeah, I understand  I'll see
if I can find some time over the weekend
to try booting without a monitor on my Centris 660av...
-- 
Name: Dave Huang         |  Mammal, mammal / their names are
called /
INet: khymazeotrope.org |  they raise a paw / the bat, the cat
/
FurryMUCK: Dahan         |  dolphin and dog / koala bear and
hog -- TMBG
Dahan: Hani G Y+C 31 Y++ L+++ W- C++ T++ A+ E+ S++ V++ F-
Q+++ P+ B+ PA+ PL++

Hauke Fath wrote:
> I see the same on my Quadra 840AV - plus it doesn't
recognize any Nubus
> cards, maybe a problem with memory-mapping Nubus space.

Mine IDs the Farallon and Radius cards in it, but doesn't 
configure/install them.  Just to clarify what you meant by
"recognize".

> Since there are probably not too many AV machines out
there running NetBSD,
> the issues look like bit rot. The AV Macs are supported
since 1.5 or
> earlier.

Is there anyone around that would like to work on
AV-specific issues but 
is lacking a machine to work with?  I can keep my eyes open.


Tim
-- 
Tim & Alethea
christtrek.org

khymazeotrope.org wrote:
> On Sun, Dec 10, 2006 at 11:16:00PM -0600, Tim &
Alethea Larson wrote:
>> Could this be why the 3.1 upgrade on my 840 has
been having problems???
> 
> I don't know; what problems are you having? If you get
a message during
> boot about "mc0: receive DMA buffer not
contiguous! Try compiling with
> "options MC_RXDMABUFS=2"", and the
onboard ethernet doesn't work, then
> you've run into this problem. If not, then it's
something unrelated.

This is, in fact, the message I'm getting at boot.  (Plain
as day; I 
just hadn't bothered to watch it closely before.)  So it
does explain 
why I was unable to telnet/ssh into it.  Is there a simple
fix or am I 
best off falling back to 2.1?

Tim
-- 
Tim & Alethea
christtrek.org

On Thu, Dec 28, 2006 at 05:38:33AM -0600, Tim & Alethea
Larson wrote:
>  Is there a simple fix or am I best off falling back to
2.1?

Current and 4.0_BETA should be ok.

Martin

Martin Husemann wrote:
> On Thu, Dec 28, 2006 at 05:38:33AM -0600, Tim &
Alethea Larson wrote:
>>  Is there a simple fix or am I best off falling
back to 2.1?
> 
> Current and 4.0_BETA should be ok.

Was the patch you'd mentioned previously committed?

Tim

-- 
Tim & Alethea
christtrek.org

On Thu, Dec 28, 2006 at 07:02:50AM -0600, Tim & Alethea
Larson wrote:
> Was the patch you'd mentioned previously committed?

Yes, and pulled up to netbsd-4 on 2006/12/15.

Martin