Re: [9fans] Hardware detection problems

Re: [9fans] Hardware detection problems

[Charles Forsyth]

i said `perhaps they've changed the FA312 since i last bought it'.
i then noticed to my horror that it was over a year ago i did that
driver.  where did the time go?  i'll try buying a current one in case
it's different.  they do that.  alternatively, it might be that timing
or access details were somehow wrong from the start.

Re: [9fans] Hardware detection problems

[Jack Johnson]

Charles Forsyth wrote:
> driver.  where did the time go?  i'll try buying a current one in case
> it's different.  they do that.

Poor NetGear.  They never seem to recognize a good thing when they build it.

I'm a big fan of the (now defunct) FA310, which started with me buying a
couple on a whim, loving their performance (especially with netatalk),
then purchasing a few more only to find the chipset changed, and now
nearly unable to find a card still in production that uses the DEC chipset.

But, even the latter revisions of their DEC clone chipset card were OK,
but then they swapped the whole line out for the FA312, which pales in
comparison.

So now it looks like 3Com for me.  I've had nothing but grief with Intel
and multicast.

Are there cards you would prefer to shun with Plan 9?

-Jack

[9fans] FA312 Ethernet card (was: Hardware detection problems)

[Richard Powell]

Charles Forsyth wrote:
> i said `perhaps they've changed the FA312 since i last bought it'.
> i then noticed to my horror that it was over a year ago i did that
> driver.  where did the time go?  i'll try buying a current one in case
> it's different.  they do that.  alternatively, it might be that timing
> or access details were somehow wrong from the start.
>

Charles,

The suggestion to use the 'ea' option in my plan9.ini file work great.  Thanks for the help!

I found the recipt for my card, I bought it in Dec. 2000.  So, save your money, my card may be older
than yours!  If you do make any driver changes, I'll be happy to try it for you.  In the mean time,
if I can figure anything out I'll let you know.

Richard

Re: [9fans] Hardware detection problems

[Charles Forsyth]

not having the driver configured would indeed stop it from being recognised!
i'd forgotten it wasn't in by default.

as to the ethernet address:
i've got the spec for the chip but that doesn't always help with the eeprom
bits, which vary a bit.  that's why i implemented only the variant i could test,
although i knew there was another for SiS900.
perhaps they've changed the FA312 since i last bought it.  i'll get another
shortly to see.   meanwhile, you could try the method suggested
by plan9.ini(8) for the SiS:

          83815
               National Semiconductor DP83815-based adapters, notably
               the Netgear FA311, Netgear FA312, and various SiS
               built-in controllers such as the SiS900.  On the SiS
               controllers, the ethernet address is not detected prop-
               erly; specify it with an ea= attribute.

Re: [9fans] Hardware detection problems

[C H Forsyth]

>>additional ether0 messages.  It is a Netgear FA312, which is mentioned
>>in the supported hardware list.

can you say which vendor and device IDs show up in the BIOS inventory?
actually, if you've got the system running, you could try the pci command
as well.

Re: [9fans] Hardware detection problems

[Richard Powell]

C H Forsyth wrote:
>>>additional ether0 messages.  It is a Netgear FA312, which is mentioned
>>>in the supported hardware list.
>>
>
> can you say which vendor and device IDs show up in the BIOS inventory?
> actually, if you've got the system running, you could try the pci command
> as well.
>

Once I rebuilt the kernel with the driver included in the config, I now
see this message at boot up:
#l0: 83815 100mbps port 0xCC00 irq 10:  FFFFFFFFFFFF

I tried modifying the srom() function in ether83815.c, to get more info.
It looks like all F's is what is being read from the eeprom into the
"srom" array.  I started to compare it to the linux driver, but not
having the spec sheet for the chip makes it hard to know the details.

Here is the output from the pci command.  0.13.0 is the FA312 ethernet
card.  0.19.0 is the HPT370 ATA-100 chip.

0.0.0:  06.00.00 1106/0391   0
0.1.0:  06.04.00 1106/8391   0
0.13.0: 02.00.00 100b/0020  10 0:0000cc01 256 1:e3000000 4096
0.19.0: 01.80.00 1103/0004  11 0:0000d001 16 1:0000d401 16 2:0000d801 16
3:0000dc01 16 4:0000e001 256
0.7.0:  06.01.00 1106/0686   0
0.7.1:  01.01.8a 1106/0571 255 4:0000c001 16
0.7.2:  0c.03.00 1106/3038   4 4:0000c401 32
0.7.3:  0c.03.00 1106/3038   4 4:0000c801 32
0.7.4:  06.00.00 1106/3057   0
1.0.0:  03.00.00 10de/0110   3 0:e0000000 16777216 1:d8000008 134217728


Here is how Linux shows it:

lspci
00:00.0 Host bridge: VIA Technologies, Inc. VT8371 [KX133] (rev 02)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8371 [KX133 AGP]
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South]
(rev 22)
00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 10)
00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 10)
00:07.3 USB Controller: VIA Technologies, Inc. USB (rev 10)
00:07.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]
(rev 30)
00:0d.0 Ethernet controller: National Semiconductor Corporation DP83815
(MacPhyter) Ethernet Controller
00:13.0 Unknown mass storage controller: Triones Technologies, Inc.
HPT366 / HPT370 (rev 03)
01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX]
(rev a1)

lspci -n
00:00.0 Class 0600: 1106:0391 (rev 02)
00:01.0 Class 0604: 1106:8391
00:07.0 Class 0601: 1106:0686 (rev 22)
00:07.1 Class 0101: 1106:0571 (rev 10)
00:07.2 Class 0c03: 1106:3038 (rev 10)
00:07.3 Class 0c03: 1106:3038 (rev 10)
00:07.4 Class 0600: 1106:3057 (rev 30)
00:0d.0 Class 0200: 100b:0020
00:13.0 Class 0180: 1103:0004 (rev 03)
01:00.0 Class 0300: 10de:0110 (rev a1)

Re: [9fans] Hardware detection problems

[jmk]

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

The code hooks are all there for additional controllers
(devata.c:/^atalegacy).
Some glue needs to be added to devsd.c:/^sdreset.

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

From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Hardware detection problems
Date: Sun, 15 Sep 2002 22:56:22 -0400
Message-ID: <47bebdfdcae207cee647848023ec0e30@plan9.bell-labs.com>

If you know the ports and interrupts,
it might suffice just to add the appropriate
probes.

Russ

Re: [9fans] Hardware detection problems

[Russ Cox]

If you know the ports and interrupts,
it might suffice just to add the appropriate
probes.

Russ

Re: [9fans] Hardware detection problems

[Russ Cox]

For the FA312, you'll have to recompile your kernel.
Add
	ether83815
with the other ethernet drivers in /sys/src/9/pc/pcdisk
and then run
	cd /sys/src/9/pc
	mk 'CONF=pcdisk'

and follow the directions on the wiki for installing
the kernel to 9fat and trying it out.

Not sure about the IDE chipset.  Maybe we don't
look for more than two controllers.  Does it require
special setup in, say, Linux?

Russ

Re: [9fans] Hardware detection problems

[Richard Powell]

Russ Cox wrote:
> For the FA312, you'll have to recompile your kernel.
> Add
> 	ether83815
> with the other ethernet drivers in /sys/src/9/pc/pcdisk
> and then run
> 	cd /sys/src/9/pc
> 	mk 'CONF=pcdisk'
>
> and follow the directions on the wiki for installing
> the kernel to 9fat and trying it out.
>
> Not sure about the IDE chipset.  Maybe we don't
> look for more than two controllers.  Does it require
> special setup in, say, Linux?
>
> Russ

Russ,

Thanks for the info on the etehrnet card, I'll give it a try.  As for
the IDE issue, the 2.4 Linux kernels (and Windows XP) include a driver
for the HPT3xx chipsets.  However, the 2.2 Linux kernel did detect the
devices and treated them as generic PC compatible IDE ports.  Even
Windows 98 could use them in a "compatibility mode" until the driver was
installed, all be it slower than with the correct driver.  I'll poke
around in the source to see if I can find anything relevant.

Thanks again,
Richard

[9fans] Hardware detection problems

[Richard Powell]

Greetings,

I'm new to Plan 9.  I just downloaded plan9.ios.bz2 to try it out.  I
can boot it and run rio, but I'm having a few hardware detection and/or
configuration problems.

I have a mother board with four IDE ports, two ATA-66 ports on a VIA
KX133 chipset and two ATA-100 ports on a HPT370 chip on the PCI buss.  I
wanted to install Plan 9 on the primary drive of IDE-3, but the two
drives on the HPT370 chip are not detected.  I was able to install and
boot Plan 9 by recabling the disk to the primary master slot (sdC0).  I
know the HPT370 is not on the officially supported hardware list, but I
thought the drives would at least be detected and maybe work in PIO mode.

Also, I don't think my ethernet card is being detected because there is
no /net/ether0 file.  The boot loader prints a line for ether0 with a
port number and IRQ, but after loading the kernel there are no
additional ether0 messages.  It is a Netgear FA312, which is mentioned
in the supported hardware list.

It does seem to detect the USB ports and ISA sound card.

Is there some trick I'm missing or am I just out of luck?

Thanks for any tips!
Richard Powell



plan9.ini file:

bootfile=sdC0!9fat!9pcdisk
bootdisk=local!#S/sdC0/fs
*nomp=1
distname=plan9
partition=new
#console=0
ether0=type=83815
monitor=multisync135
vgasize=1280x1024x32
mouseport=ps2
audio0=type=ess1688
installurl=http://204.178.31.2/magic/9down4e/compressed/1031888044.uvvc86ygkwyv5x3vz3r7u72ae3f4ndq5



Hardware Configuration:

800Mhz Athlon (Not OC)
Abit KA7-100 Mother-board - Via KX133 chipset + HPT370
Multi-boot using GRUB: Windows XP, Windows 98SE, Red Hat 7.3, Scyld
Beowulf, and Plan 9
256MB Crucial PC-133 SDRAM
MAXTOR D740 (80GB ATA-133)
IBM DTLA-307020 (20GB ATA-100)
HP CD-Writer Plus 9100i
Asus AGP-V7100 (GeForce 2MX 32MB)
Turtle Beach Malibu
Netgear FA312 10/100 Ethernet