Re: [9fans] Fileserver question

Re: [9fans] Fileserver question

[forsyth]

[-- Attachment #1: Type: text/plain, Size: 578 bytes --]

you're right about the ne2000 and the file server.
the file server device set is a fairly small subset
of the cpu/terminal support, based on what has been
used to build file servers.  since
those are typically built to give some degree of
performance, ne2000/8390-based things might not
be the cards of choice.  one way or another that
device support will improve, but that doesn't do you
a lot of good now.

in ether82557.c make sure it reads
		if(bmcr & 0x2000)
			ether->mbps = 100;
		else
			ether->mbps = 10;
and specifically that the else isn't missing.


[-- Attachment #2: Type: message/rfc822, Size: 2422 bytes --]

From: Sam Ducksworth <sam@ducksworth.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Fileserver question
Date: Thu, 16 Aug 2001 15:50:55 -0700 (PDT)
Message-ID: <Pine.BSF.4.33.0108161542240.43051-100000@lucifer.ducksworth.com>

well i spoke too soon. now i am having problems
with the network card. first i had a ne2000 card
in it, but after looking at the fs src i do not
see a driver for the ne2000. next i changed the
plan9.ini and installed a i82557 compatable intel
card that was in my terminal.

the fs kernel detects the card and boots fine but
nothing works. i noticed the following during boot:

ether0: i82557: 0Mbps port 0xe400 irq 12: 0002630325a0
               ^^^^^^
i even did like the man page said and tried to force
it using the '10BASE-T' option in the plan9.ini file.

--sam

> the trailing '0' was the problem. finally, i have
> a real file server...thanks!

Re: [9fans] Fileserver question

[jmk]

yes, at the moment some cards require that, we only do chip setup
at boot time. usually it's not a problem as the cards don't hop around
from switch to switch and we usually boot over the network, so if the
cable's not connected you find out pretty quickly.

we've been doing some work recently to allow insertion and removal
of pc cards and this will utimately require the ethernet drivers to
deal with link going up and down.

On Thu Aug 16 22:26:22 EDT 2001, martin@Princeton.EDU wrote:
> jmk@plan9.bell-labs.com wrote:
> > 
> >         ether0: i82557: 0Mbps port 0xe400 irq 12: 0002630325a0
> >                        ^^^^^^
> > 
> > that means the driver did not detect link on the card when it
> > initialised. check the cable - check the lights on the back of the
> > card.
> 
> Does this mean that you have to have the cable connected when the system
> boots, or can you subsequently connect a cable and make it happy?
> 
> I remember seeing this message once and thinking that the card in
> question (which was of dubious origin) was bad.
> 
> Martin

Re: [9fans] Fileserver question

[Sam Ducksworth]

okay i added the on liner and recompiled. that fixed the
problem. i am now installing the dist files on my fs.
thanks!

> Have you installed Paul Lustgarten's fix for the i82557 speed
> negotation?  It's a one-liner that he posted recently.
>
> Ethernet speed negotiation doesn't seem to be standardised properly or
> else there are just a lot of buggy cards.  I find things work better
> if I connect my Ethernet cards to switches rather than hubs (but don't
> plug an Intel card into an Intel switch; that really doesn't work!).
>
>

--sam

Re: [9fans] Fileserver question

[Martin Harriss]

jmk@plan9.bell-labs.com wrote:
> 
>         ether0: i82557: 0Mbps port 0xe400 irq 12: 0002630325a0
>                        ^^^^^^
> 
> that means the driver did not detect link on the card when it
> initialised. check the cable - check the lights on the back of the
> card.

Does this mean that you have to have the cable connected when the system
boots, or can you subsequently connect a cable and make it happy?

I remember seeing this message once and thinking that the card in
question (which was of dubious origin) was bad.

Martin

Re: [9fans] Fileserver question

[jmk]

	ether0: i82557: 0Mbps port 0xe400 irq 12: 0002630325a0
	               ^^^^^^

that means the driver did not detect link on the card when it
initialised. check the cable - check the lights on the back of the
card.

Re: [9fans] Fileserver question

[Sam Ducksworth]

well i spoke too soon. now i am having problems
with the network card. first i had a ne2000 card
in it, but after looking at the fs src i do not
see a driver for the ne2000. next i changed the
plan9.ini and installed a i82557 compatable intel
card that was in my terminal.

the fs kernel detects the card and boots fine but
nothing works. i noticed the following during boot:

ether0: i82557: 0Mbps port 0xe400 irq 12: 0002630325a0
               ^^^^^^
i even did like the man page said and tried to force
it using the '10BASE-T' option in the plan9.ini file.

--sam

> the trailing '0' was the problem. finally, i have
> a real file server...thanks!

Re: [9fans] Fileserver question

[Sam Ducksworth]

the trailing '0' was the problem. finally, i have
a real file server...thanks!

> i don't understand how you would get some of the output and then fail,
> but
> 	scsi0=type=ncr53c8xx0
> shouldn't have a '0' on the end.
>

--sam

Re: [9fans] Fileserver question

[jmk]

On Thu Aug 16 13:01:22 EDT 2001, sam@ducksworth.com wrote:
> i am trying to get a fileserver set up and am having a
> bit of a problem. seems the scsi card is not being recognized
> correctly. i have a PCI based Symbios 53c810alv scsi card. To
> check the card i have put it and the attached drive in a linux
> box to verify the hardware.
> 
> I have built 2 fs kernels. One with Eric's idefs patch and one
> without. They both give the same results. Here is what i get
> from the boot messages:
> 
> sd53c8xx: SYM53C810ALV rev. 0x12 intr=11 command=2000017
> 
> sd53c8xx: bios scntl3(03) stest2(00)
> 
> ...
> 
> scsi#0: ncr53c8xx0: port 0 Failed to INIT controller
> 
> after i get the command prompt i enter in the config commands
> (very simple i might add) and when i issue the 'end' command the
> box panics, vomits on the screen and quickly reboots.
> 
> here is my plan9.ini for the fs:
> 
> bootfile=fd0!dos!9pcfs
> ether0=type=ne2000 port=0x340 irq=10 nodummyrr
> nvr=fd!0!plan9.nvr
> scsi0=type=ncr53c8xx0
> 
> 
> --sam

i don't understand how you would get some of the output and then fail,
but
	scsi0=type=ncr53c8xx0
shouldn't have a '0' on the end.

[9fans] Fileserver question

[Sam Ducksworth]

i am trying to get a fileserver set up and am having a
bit of a problem. seems the scsi card is not being recognized
correctly. i have a PCI based Symbios 53c810alv scsi card. To
check the card i have put it and the attached drive in a linux
box to verify the hardware.

I have built 2 fs kernels. One with Eric's idefs patch and one
without. They both give the same results. Here is what i get
from the boot messages:

sd53c8xx: SYM53C810ALV rev. 0x12 intr=11 command=2000017

sd53c8xx: bios scntl3(03) stest2(00)

...

scsi#0: ncr53c8xx0: port 0 Failed to INIT controller

after i get the command prompt i enter in the config commands
(very simple i might add) and when i issue the 'end' command the
box panics, vomits on the screen and quickly reboots.

here is my plan9.ini for the fs:

bootfile=fd0!dos!9pcfs
ether0=type=ne2000 port=0x340 irq=10 nodummyrr
nvr=fd!0!plan9.nvr
scsi0=type=ncr53c8xx0


--sam