Re: [9fans] Intel Pro/100 S Desktop Network Adapter

Re: [9fans] Intel Pro/100 S Desktop Network Adapter

[rsc]

> I'm installed plan9 from download, and recompiled kernel without usb
> (because network and usb in the same time freeze my computer -
>  VIA KT133 with ATA100 and Athlon 1000MHz).

Unrelated to your ether problems, but if you apply the USB fix we
posted to 9fans, does your computer still freeze?  We think the
fix works on all chipsets, even VIA.

If you run

	snoopy >/dev/null &

does your network card start working?

Russ

Re: [9fans] Intel Pro/100 S Desktop Network Adapter

[Rolandas Naujikas]

My net card work now, when I fix pci.c to dont fix BIOS pcirouting table
(It route irq=11 -> 10, and net card loose interrupts).

Rolandas

P.S. Weekend I will try with USB enabled.

On Thu, May 09, 2002 at 11:44:52PM -0400, rsc@plan9.bell-labs.com wrote:
> > I'm installed plan9 from download, and recompiled kernel without usb
> > (because network and usb in the same time freeze my computer -
> >  VIA KT133 with ATA100 and Athlon 1000MHz).
>
> Unrelated to your ether problems, but if you apply the USB fix we
> posted to 9fans, does your computer still freeze?  We think the
> fix works on all chipsets, even VIA.
>
> If you run
>
> 	snoopy >/dev/null &
>
> does your network card start working?
>
> Russ
>

Re: [9fans] Intel Pro/100 S Desktop Network Adapter

[Rolandas Naujikas]

1. Award Modular BIOS v6.00PG - W6330MS V3.2 (MSI K7T Pro2A with KT133 chipset)
2. See below:
---
pcirouting: BIOS workaround: PCI.0.7.2 at pin 4 irq 11 -> 10
---
After patching kernel by disabling next line in pci.c, there was additional line
---
pcirouting: BIOS workaround: PCI.0.7.3 at pin 4 irq 11 -> 10
---
3. See below:
--- pci ---
0.0.0:	06.00.00 1106/0305   0
0.1.0:	06.04.00 1106/8305   0
0.10.0:	02.00.00 8086/1229  11 0:df021000 4096 1:0000dc01 64 2:df000000 131072
0.13.0:	04.01.00 1102/0002   9 0:0000e001 32
0.13.1:	09.80.00 1102/7002   0 0:0000e401 16
0.7.0:	06.01.00 1106/0686   0
0.7.1:	01.01.8a 1106/0571 255 4:0000d001 16
0.7.2:	0c.03.00 1106/3038  10 4:0000d401 32
0.7.3:	0c.03.00 1106/3038  10 4:0000d801 32
0.7.4:	06.00.00 1106/3057   0
0.8.0:	04.00.00 109e/0350   5 0:df020008 4096
1.0.0:	03.00.00 10de/0110  10 0:dc000000 16777216 1:d0000008 134217728
--- pci ---

Rolandas

On Fri, May 10, 2002 at 12:35:17AM -0400, David Gordon Hogan wrote:
> > My net card work now, when I fix pci.c to dont fix BIOS pcirouting table
> > (It route irq=11 -> 10, and net card loose interrupts).
>
> 1.  What is your BIOS?
>
> 2.  What was the exact "pcirouting" message, with
> all the numbers?
>
> 3.  Could you please run "grep . '$#'/pci/*ctl" and
> mail me the results?
>

Re: [9fans] Intel Pro/100 S Desktop Network Adapter

[David Gordon Hogan]

> 3.  Could you please run "grep . '$#'/pci/*ctl" and
> mail me the results?

Sorry, I've gone dyslexic.  I mean "grep . '#$'/pci/*ctl".
If the command "pci" exists on your system, you can
just run that instead.

Re: [9fans] Intel Pro/100 S Desktop Network Adapter

[David Gordon Hogan]

> My net card work now, when I fix pci.c to dont fix BIOS pcirouting table
> (It route irq=11 -> 10, and net card loose interrupts).

1.  What is your BIOS?

2.  What was the exact "pcirouting" message, with
all the numbers?

3.  Could you please run "grep . '$#'/pci/*ctl" and
mail me the results?

Re: [9fans] Intel Pro/100 S Desktop Network Adapter

[Rolandas Naujikas]

Finally I found the root of problem.
By hazard I seed on boot screen and I found line
pcirouting: BIOS workaround: ??? at pin ?? irq 11 -> 10
But my net card use irq=11 and driver loose interrupts.
So I commented next line "southbridge->set(sbpci, m[0], pci->intl);"
and voila - all work.

If someone need more information to correct this for future, I could submit.

I'm impressed in plan9 and I'm learning this beast.

Rolnas

On Thu, May 09, 2002 at 07:27:31AM +0200, Rolandas Naujikas wrote:
>
> I'm installed plan9 from download, and recompiled kernel without usb
> (because network and usb in the same time freeze my computer -
>  VIA KT133 with ATA100 and Athlon 1000MHz).
> The net card is
>
> "Intel PRO/100 S Desktop Adapter (with 3DES, 168-bit, Encryption)".
>
> Chip is exactly 82550EY (by looking at card). I don't found any label about
> 82555 for physical connection.
>
> RolNas
>
> P.S. Looking at /sys/src/9/pc/ether82557.c i found,
> if autonegotation succeed, than i cannot override media speed (type).
>
> On Wed, May 08, 2002 at 07:39:53PM -0400, jmk@plan9.bell-labs.com wrote:
> >
> > I'm puzzled. If the PCI device ID is 1229 the card should be
> > recognised OK and work. I'm sure I've used 82550 chips without
> > problem, I don't think it's the driver that's at fault.
> > What is the card connected to?
> >
> > On Wed May  8 19:14:19 EDT 2002, rolnas@delfi.lt wrote:
> > > I bought this net card instead Acorp L-100 with RTL8139C.
> > > But network doesn't work also.
> > >
> > > This is i82550 as pci device 8086/1229 rev 0x0C
> > >  (by looking in plan9 sources this revision is not supported).
> > > Physical device is i82555 with code 7.
> > >
> > > All this information from FreeBSD driver and looking at card.
> > >
> > > I newbie to Plan9, but very interesting in this,
> > > after much time spend to make work, i don't want leave.
> > >
> > > Rolandas aka RolNas
> > >
> > > P.S. ip/ping to itself work,
> > >  but /net/arp show WAIT state for external machines.

Re: [9fans] Intel Pro/100 S Desktop Network Adapter

[Rolandas Naujikas]

I'm installed plan9 from download, and recompiled kernel without usb
(because network and usb in the same time freeze my computer -
 VIA KT133 with ATA100 and Athlon 1000MHz).
The net card is

"Intel PRO/100 S Desktop Adapter (with 3DES, 168-bit, Encryption)".

Chip is exactly 82550EY (by looking at card). I don't found any label about
82555 for physical connection.

RolNas

P.S. Looking at /sys/src/9/pc/ether82557.c i found,
if autonegotation succeed, than i cannot override media speed (type).

On Wed, May 08, 2002 at 07:39:53PM -0400, jmk@plan9.bell-labs.com wrote:
>
> I'm puzzled. If the PCI device ID is 1229 the card should be
> recognised OK and work. I'm sure I've used 82550 chips without
> problem, I don't think it's the driver that's at fault.
> What is the card connected to?
>
> On Wed May  8 19:14:19 EDT 2002, rolnas@delfi.lt wrote:
> > I bought this net card instead Acorp L-100 with RTL8139C.
> > But network doesn't work also.
> >
> > This is i82550 as pci device 8086/1229 rev 0x0C
> >  (by looking in plan9 sources this revision is not supported).
> > Physical device is i82555 with code 7.
> >
> > All this information from FreeBSD driver and looking at card.
> >
> > I newbie to Plan9, but very interesting in this,
> > after much time spend to make work, i don't want leave.
> >
> > Rolandas aka RolNas
> >
> > P.S. ip/ping to itself work,
> >  but /net/arp show WAIT state for external machines.

Re: [9fans] Intel Pro/100 S Desktop Network Adapter

[jmk]

I'm puzzled. If the PCI device ID is 1229 the card should be
recognised OK and work. I'm sure I've used 82550 chips without
problem, I don't think it's the driver that's at fault.
What is the card connected to?

On Wed May  8 19:14:19 EDT 2002, rolnas@delfi.lt wrote:
> I bought this net card instead Acorp L-100 with RTL8139C.
> But network doesn't work also.
>
> This is i82550 as pci device 8086/1229 rev 0x0C
>  (by looking in plan9 sources this revision is not supported).
> Physical device is i82555 with code 7.
>
> All this information from FreeBSD driver and looking at card.
>
> I newbie to Plan9, but very interesting in this,
> after much time spend to make work, i don't want leave.
>
> Rolandas aka RolNas
>
> P.S. ip/ping to itself work,
>  but /net/arp show WAIT state for external machines.

[9fans] Intel Pro/100 S Desktop Network Adapter

[Rolandas Naujikas]

I bought this net card instead Acorp L-100 with RTL8139C.
But network doesn't work also.

This is i82550 as pci device 8086/1229 rev 0x0C
 (by looking in plan9 sources this revision is not supported).
Physical device is i82555 with code 7.

All this information from FreeBSD driver and looking at card.

I newbie to Plan9, but very interesting in this,
after much time spend to make work, i don't want leave.

Rolandas aka RolNas

P.S. ip/ping to itself work,
 but /net/arp show WAIT state for external machines.