[9fans] ethernet detection problems

[9fans] ethernet detection problems

[Ray Amberg]

Hello,

I've recently installed Plan 9 as part of an extra credit research project 
for my introductory operating systems class.  Looking forward to messing 
with it, but at the moment I'm having a problem getting either one of two 
ethernet controllers detected.  Neither of them are being detected.

I have an on-board ethernet controller using the SiS900 chipset, and a 
Linksys WPC11 Wireless card.  After installing Plan 9, and running 
ipconfig, I got the message telling me that /net/ether0 doesn't exist.  I 
read the Network Configuration wiki, and the manpage for plan9.ini, so I 
tried getting the on-board chipset detected first with the following 
addition to plan9.ini:

 	ether0=type=83815 ea=myethernetaddress

This didn't seem to work, as there was still no /net/ether0.  So I tried 
the linksys card:

 	ether0=type=wavelan essid=myessid

Note: "myethernetaddress" and "myessid" not actually written in plan9.ini, 
just used for clarity.

This didn't create /net/ether0 either.

I'm not sure what other information to provide, but I would be glad to 
provide upon request.  Thanks in advance for any help.

Sincerely,
Ray Amberg

Re: [9fans] ethernet detection problems

[Russ Cox]

For the SIS900, try applying the following changes to
/sys/src/9/pc/ether83815.c and then recompile the
kernel, copy it to 9fat, and boot it.

% diff -c /n/dump/2005/1106/sys/src/9/pc/ether83815.c /sys/src/9/pc/ether83815.c
/n/dump/2005/1106/sys/src/9/pc/ether83815.c:81,86 -
/sys/src/9/pc/ether83815.c:81,87

  enum {				/* Variants */
  	Nat83815	= (0x0020<<16)|0x100B,
+ 	Sis900 = (0x0630<<16)|0x1039,	/* untested */
  };

  typedef struct Ctlr Ctlr;
/n/dump/2005/1106/sys/src/9/pc/ether83815.c:841,846 -
/sys/src/9/pc/ether83815.c:842,848
  			continue;

  		case Nat83815:
+ 		case Sis900:
  			break;
  		}

%

Similarly, the following patch may make your WPC-11 start
working (if not, please send us the "net" lines that get
printed by the "pci" command).

% diff -c /n/dump/2005/1106/sys/src/9/pc/etherwavelan.c
/sys/src/9/pc/etherwavelan.c
/n/dump/2005/1106/sys/src/9/pc/etherwavelan.c:87,92 -
/sys/src/9/pc/etherwavelan.c:87,93
  	int did;
  } wavelanpci[] = {
  	0x1260, 0x3873,	/* Intersil Prism2.5 */
+ 	0x1737,	0x0019,	/* Linksys WPC-11 untested */
  };

  static Ctlr *ctlrhead, *ctlrtail;
%

Russ

Re: [9fans] ethernet detection problems

[Federico Benavento]

hi,

I use Andrey's driver for the sis 900.

http://pages.cpsc.ucalgary.ca/~mirtchov/lanlp9/sis900/ethersis.c

On 11/6/05, Ray Amberg <ramberg@cs.ucr.edu> wrote:
> Hello,
>
> I've recently installed Plan 9 as part of an extra credit research project
> for my introductory operating systems class.  Looking forward to messing
> with it, but at the moment I'm having a problem getting either one of two
> ethernet controllers detected.  Neither of them are being detected.
>
> I have an on-board ethernet controller using the SiS900 chipset, and a
> Linksys WPC11 Wireless card.  After installing Plan 9, and running
> ipconfig, I got the message telling me that /net/ether0 doesn't exist.  I
> read the Network Configuration wiki, and the manpage for plan9.ini, so I
> tried getting the on-board chipset detected first with the following
> addition to plan9.ini:
>
>         ether0=type=83815 ea=myethernetaddress
>
> This didn't seem to work, as there was still no /net/ether0.  So I tried
> the linksys card:
>
>         ether0=type=wavelan essid=myessid
>
> Note: "myethernetaddress" and "myessid" not actually written in plan9.ini,
> just used for clarity.
>
> This didn't create /net/ether0 either.
>
> I'm not sure what other information to provide, but I would be glad to
> provide upon request.  Thanks in advance for any help.
>
> Sincerely,
> Ray Amberg
>


--
Federico G. Benavento

Re: [9fans] ethernet detection problems

[Charles Forsyth]

> + 	0x1737,	0x0019,	/* Linksys WPC-11 untested */

that worked for me for at least a year.  i hadn't realised it wasn't
part of the normal driver.

Re: [9fans] ethernet detection problems

[Russ Cox]

> If it properly reflects the actual boot method, we could
> write a trivial script "bootmethod" and hide those knowledge
> concerning /srv in there, maybe?
>
>         % bootmethod
>         kfs #S/sdC0/fs

I don't understand how this would be used.
Knowing where the root file system came from
is not a very common need.

Russ

Re: [9fans] ethernet detection problems

[YAMANASHI Takeshi]

> You can figure out which one you're using by ls -l /srv.
> If there is a /srv/fscons, you are using fossil.  If there
> is a /srv/kfs.cmd you are using kfs.

Does /env/bootargs reflect the modification typed in
by user at boot time, or is a mere copy from plan9.ini?

If it properly reflects the actual boot method, we could
write a trivial script "bootmethod" and hide those knowledge
concerning /srv in there, maybe?

	% bootmethod
	kfs #S/sdC0/fs
-- 
"on travel, off the network ... and a fossil in my pocket"

Re: [9fans] ethernet detection problems

[jmk]

On Fri Nov 25 01:01:48 EST 2005, benavento@gmail.com wrote:
> > > % diff -c /n/dump/2005/1106/sys/src/9/pc/ether83815.c
> > /sys/src/9/pc/ether83815.c
> > > /n/dump/2005/1106/sys/src/9/pc/ether83815.c:81,86 -
> > > /sys/src/9/pc/ether83815.c:81,87
> > >
> > >   enum {        /* Variants */
> > >     Nat83815  = (0x0020<<16)|0x100B,
> > > +   Sis900 = (0x0630<<16)|0x1039, /* untested */
> > >   };
> > >
> 
> hmm, this didn't work for me either that's why I'm still using
> Andrey's driver. Now seing the code closely I think I know
> where the problem is, I haven't tested it yet, but I think this will work.
> 
>  Sis900 = (0x0900<<16)|0x1039,
> 
> --
> Federico G. Benavento

If you look in /lib/pci, (0x0900<<16)|0x1039 would seem to be
the logical choice.

--jim

Re: [9fans] ethernet detection problems

[Russ Cox]

You built the pc kernel, but that's the pc terminal kernel
that mounts its root file system over the network.
You need to build one of the bigger kernels that can
boot from local disk.  These include copies of either kfs
(pcdisk) or fossil (pcf) in the kernel image so that they
can be used to mount the local disk to provide the root.

To build one of these, cd /sys/src/9/pc; mk 'CONF=pcf'
(or 'CONF=pcdisk').  Sorry for not mentioning that before.

You can figure out which one you're using by ls -l /srv.
If there is a /srv/fscons, you are using fossil.  If there
is a /srv/kfs.cmd you are using kfs.

Russ

Re: [9fans] ethernet detection problems

[Federico Benavento]

> > % diff -c /n/dump/2005/1106/sys/src/9/pc/ether83815.c
> /sys/src/9/pc/ether83815.c
> > /n/dump/2005/1106/sys/src/9/pc/ether83815.c:81,86 -
> > /sys/src/9/pc/ether83815.c:81,87
> >
> >   enum {        /* Variants */
> >     Nat83815  = (0x0020<<16)|0x100B,
> > +   Sis900 = (0x0630<<16)|0x1039, /* untested */
> >   };
> >

hmm, this didn't work for me either that's why I'm still using
Andrey's driver. Now seing the code closely I think I know
where the problem is, I haven't tested it yet, but I think this will work.

 Sis900 = (0x0900<<16)|0x1039,

--
Federico G. Benavento

[9fans] ethernet detection problems

[Ray Amberg]

Hello everyone,

Sorry if this is going outside the thread.  I finally got time to attempt 
the fixes to the ethernet detection problems for the Sis900 and the WPC-11 
wireless ethernet cards.  Still, no luck.  Here's my log of events (it was 
my first kernel recompile, so not sure if I did everything right):

1. Added the lines of code to ether83815.c, as described in Cox's message
below, and saved.
2. Compiled the kernel with the following commands:
 	% cd /sys/src/9/pc
 	% mk 'CONF=pc'
 	[many lines of compiling here omitted.  A file 9pc created]
 	% cp 9pc /386
 	% 9fat:
 	% cp 9pc /n/9fat/my9pc
3. Edited plan9.ini and changed the bootfile to point to my9pc. Also made 
sure that plan9.ini defined ether0 to 83815, and included the ea=address 
flag.
4. Restarted computer

At the boot, it found my9pc and loaded it, but a couple of things were 
different.  First, there was no longer an option to boot 'local', only 
'tcp' or 'il'.  I attempted tcp, but I received an error about 
/net/ether0 not existing, then a panic, and a cpu0: exit.

After fixing plan9.ini to boot the original kernel image, I attempted the 
same process with the etherwavelan.c file, and changing plan9.ini to define 
ether0=wavelan essid=myid, recompiling again, but the results were the 
same.

On request, here is the output of the 'net' portions of the 'pci' command:
 	[...]
 	0.4.0:	net  02.00.00 1039/0900   5 0:00009801 256 1:e5000000 4096
 	0.8.0:	net  02.80.00 14e4/4301   5 0:e4800000 8192
 	[...]

I will try Benevento's suggestion to use the driver located at 
http://pages.cpsc.ucalgary.ca/~mirtchov/lanlp9/sis900/ethersis.c , but in 
the meantime this is where I am.  Any suggestions would be appreciated. 
Thanks again for the previous responses.

Ray

Russ Cox wrote:
> For the SIS900, try applying the following changes to
> /sys/src/9/pc/ether83815.c and then recompile the
> kernel, copy it to 9fat, and boot it.
>
> % diff -c /n/dump/2005/1106/sys/src/9/pc/ether83815.c 
/sys/src/9/pc/ether83815.c
> /n/dump/2005/1106/sys/src/9/pc/ether83815.c:81,86 -
> /sys/src/9/pc/ether83815.c:81,87
>
>   enum {        /* Variants */
>     Nat83815  = (0x0020<<16)|0x100B,
> +   Sis900 = (0x0630<<16)|0x1039, /* untested */
>   };
>
>   typedef struct Ctlr Ctlr;
> /n/dump/2005/1106/sys/src/9/pc/ether83815.c:841,846 -
> /sys/src/9/pc/ether83815.c:842,848
>         continue;
>
>       case Nat83815:
> +     case Sis900:
>         break;
>       }
>
> %
>
> Similarly, the following patch may make your WPC-11 start
> working (if not, please send us the "net" lines that get
> printed by the "pci" command).
>
> % diff -c /n/dump/2005/1106/sys/src/9/pc/etherwavelan.c
> /sys/src/9/pc/etherwavelan.c
> /n/dump/2005/1106/sys/src/9/pc/etherwavelan.c:87,92 -
> /sys/src/9/pc/etherwavelan.c:87,93
>     int did;
>   } wavelanpci[] = {
>     0x1260, 0x3873, /* Intersil Prism2.5 */
> +   0x1737, 0x0019, /* Linksys WPC-11 untested */
>   };
>
>   static Ctlr *ctlrhead, *ctlrtail;
> %
>
> Russ
>