@ncafferkey

It hangs only if the cable is plugged in.
Without the cable startnet finishes and I can ping localhost ip.

AHI uses the void.audio.
How can I disable for example the usb driver? Trident shows a pciusb.device, but I can't find it in devs/drivers.

I tested with the same build on a machine with the exact same PCI ID for the NIC, but I couldn't reproduce your problem.

One possibility is that another device that uses the same IRQ has a buggy driver that doesn't share IRQs well (or even rhine.device itself could have an IRQ problem). Can you disable as many other drivers as possible and retest? E.g. sound, USB, ATA etc.

Also, I tested without any Ethernet cable plugged in, so please do the same.

@lazi

Thanks for the info. I'll dig out my VIA motherboard and have a look.

@ncafferkey

Aros is a nightly build i386 ABIV0 2017-05-01

Version said this:
Kickstart 51.51
Workbench 40.0

If you mean IRQ, then PCI tool shows IRQ: 10 (A)
Bar0: I/O at 0x2000 (size 0x100)
Bar1: Memory at 0xd0000400 (size 0x100)

@lazi

What version of AROS are you using? Does PCITool show an interrupt number for the device?

Hi!

Here is a VT6102/VT6103 [Rhine-II] Vendor: 0x1106 Prod: 0x3065 Rev:0x78
Fujitsu Amilo notebook.

Added the rhine.device (0.3) in network preferences and saved.
After launch startnet the machine freezes.

Any help?

According to the previous post (although it's a bit old) there
are a rtl8139 driver. I am curious if so ? Can anybody confirm
if it's working or not ?

I just downloaded the latest nightly to fire up in qemu here at work, and I noticed that the rtl8139 driver has made an appearance too.

This is fantastic, I have a box of those!

Looks like I can finally get networking sorted in a native AROS install. I know what I'm doing when I get home!

I've checked, the driver doesn't power up the NIC.
Fab says you need to pci_outb(0x00, base+0x83) for this. However i would advice to consult Linux source code, it contains explanation of this register. It allows to do nice things like wakeup on LAN. Probably AROS could support it.
However this would involve creating a mechanism by means of which exec.library would tell the drivers that it's about to shut down. Drivers should take appropriate actions then according to user's preferences (for example Rhine driver would set up WOL).
I don't know how it is to be done in MorphOS 1.5. I know only that it has Shutdown() call in exec.library.

Is the driver (and the new updated arosTCP) being built in the nightlies?

Dammy