It behaved differently this time: you can see that the driver was configured after startnet (the address was filled in and there was a time for the last start). That's why the CONFIG command failed by the way.

If you're using DHCP, the packet count shouldn't be zero. However, if you're using a manual configuration, you might need to do something like running ping to hopefully generate some traffic, before running the STATUS command.

I wanted to prove that the hardware is working, so I installed winxp to the machine. The installer recognized the NIC and it is working correctly.

Here is the last try with AROS:

New Shell process 1
1.AROS:> startnet
1.AROS:> Extras/Networking/Utils/SANAUtil/SANAUtil device rhine.device status
Device 'networks/rhine.device' (version 0.3), unit 0
QueryFormat: 0, DeviceLevel: 0
Address field size: 48 bits, Maximum transfer unit: 1500 bytes
Speed: 100000000 bps, HardwareType: Ethernet
Current addr: 00:14:0B:02:60:BC, Default addr: 00:14:0B:02:60:BC
Packets received: 0, Packets sent: 0
Bad Data: 0, Overruns: 0
Unknown packets received: 0, Reconfigurations: 0
Last start: Saturday 27-Aug-05 00:26:20
Special stats:
(1/0) Bad multicasts: 0
(1/1) Retries: 0
(1/2) Underruns: 0
1.AROS:> Extras/Networking/Utils/SANAUtil/SANAUtil device rhine.device CONFIG
ConfigInterface failed -- Error: Bad state
WireError: Attempt to configure twice
1.AROS:> devlist
address version rev opencnt flags name
------------------------------------------------------------
0x01096A20 41 1 25 0x4 timer.device
0x01096B50 1 3 1 0x4 pciusb.device
0x010A53E0 41 1 1 0x4 gameport.device
0x010A5500 41 2 1 0x4 keyboard.device
0x010A7680 4 5 1 0x4 usbscsi.device
0x010E5440 41 4 5 0x4 input.device
0x011A03F0 0 1 0 0x4 ahci.device
0x011A0480 41 4 1 0x4 console.device
0x011758D0 43 0 2 0x4 ata.device
0x012FFD00 4 3 1 0x4 usbstir4200.device
0x01302AF0 4 3 1 0x4 usbmoschipeth.device
0x01341970 4 3 1 0x4 usbpalm.device
0x01360190 4 3 1 0x4 usbpegasus.device
0x01301330 4 3 1 0x4 usbparallel.device
0x0135F490 4 3 1 0x4 usbraw.device
0x013B9070 1 2 1 0x4 usbrndis.device
0x013C3330 4 3 1 0x4 serialcp210x.device
0x013DECF0 4 3 1 0x4 serialpl2303.device
0x013F7650 4 3 1 0x4 usbasixeth.device
0x01675D60 4 3 1 0x4 usbbluetooth.device
0x013DE060 4 3 1 0x4 usbmodem.device
0x016753E0 4 3 1 0x4 dm9601eth.device
0x01675450 4 3 1 0x4 usbethwrap.device
0x025614A0 0 3 1 0x4 rhine.device
1.AROS:>

There's something wrong there because the current address is all zeroes and "last start" is blank. If you run "devlist", is rhine.device shown with at least one opener?

You could also try running Sanautil with CONFIG instead of STATUS to see what it says.

Here it it is:

Thanks for the info. The devices with an IRQ of 0 or 255 are potentially troublesome. Are you booting from SATA or PATA?

Could you check if any packets have been sent or received after startnet? Run this command:

Extras:networking/utilities/sanautil/sanautil DEVICE rhine.device STATUS

(That's the command path for a nightly, it might be somewhere else on a distro, e.g. SYS:System/Network/AROSTCP/C/Sanautil)

ID, descr., vendor/product, IRQ

00.00.0 Bridge 0x1106 / 0x0314 N/A
00.00.1 Bridge 0x1106 / 0x1314 N/A
00.00.2 Bridge 0x1106 / 0x2314 N/A
00.00.3 Bridge 0x1106 / 0x3208 N/A
00.00.4 Bridge 0x1106 / 0x4314 N/A
00.00.7 Bridge 0x1106 / 0x7314 N/A
00.01.0 Bridge 0x1106 / 0xb198 N/A
00.0f.0 SATA 0x1106 / 0x3149 9(B)
00.0f.1 IDE 0x1106 / 0x0571 0(A)
00.10.0 USB UHCI 0x1106 / 0x3038 10(A)
00.10.1 USB UHCI 0x1106 / 0x3038 10(A)
00.10.4 USB EHCI 0x1106 / 0x3104 5(C)
00.11.0 Bridge 0x1106 / 0x3227 N/A
00.11.5 Audio 0x1106 / 0x3059 255(C)
00.11.6 Modem 0x1106 / 0x3068 255(C)

00.12.0 Ethernet 0x1106 / 0x3065 10(A)

01.00.0 VGA 0x1106 / 0x3344 10(A)

Can you tell from PCITool what devices don't have interrupts assigned? It might be related to the problem.

Sorry for the mess...

Now the usb driver is disabled. Startnet seem not hangs anymore.
However there is no network connection be it set DHCP or manual.

At boot time after the ACPI intialization complete message, there is a line two times:
[PCIDevice] WARNING: Interrupt line is not assigned! Device may freeze or malfunction at use!

Does it means somenething in context of the problem?

I can specify some more the situation:

No cable attached:
1. Clean boot -> open shell -> ping 127.0.0.1 -> cannot open bsdsocket,,,
startnet -> system hangs

2. Clean boot -> open shell -> startnet
ping 127.0.0.1 -> works

Cable attached:
2. Clean boot -> open shell -> startnet -> system hangs


According to PCITool IRQ channel 10 is shared between the network controller, the UHCI USBs and the display adapter.