Login
Username:

Password:

Remember me



Lost Password?

Register now!
Main Menu
Who's Online
3 user(s) are online (1 user(s) are browsing Forum)

Members: 2
Guests: 1

trekiej, mordesku, more...

Browsing this Thread:   1 Anonymous Users



« 1 2 3 (4)


Re: VIA Nic Driver

Joined:
2004/10/30 17:13
From Ireland
Group:
Member
Posts: 2648
Offline
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.

Posted on: 5/23 7:05
Transfer the post to other applications Transfer


Re: VIA Nic Driver

Joined:
1/26 19:00
From Hungary
Group:
Member
Posts: 12
Offline
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:>

Posted on: 5/25 8:47
Transfer the post to other applications Transfer


Re: VIA Nic Driver

Joined:
2004/10/30 17:13
From Ireland
Group:
Member
Posts: 2648
Offline
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.

Posted on: 5/25 17:45
Transfer the post to other applications Transfer



« 1 2 3 (4)



You can view topic.
You cannot start a new topic.
You cannot reply to posts.
You cannot edit your posts.
You cannot delete your posts.
You cannot add new polls.
You cannot vote in polls.
You cannot attach files to posts.
You cannot post without approval.

[Advanced Search]


Search
Top Posters
1 paolone
paolone
4365
2 magorium
magorium
4095
3 phoenixkonsole
phoenixkonsole
3893
4 nikolaos
nikolaos
3694
5 deadwood
deadwood
2923
6 ncafferkey
ncafferkey
2648
7 mazze
mazze
2214
8 clusteruk
clusteruk
2111
9 Kalamatee
Kalamatee
2024
10 damocles
damocles
1789
© 2004-2017 AROS Exec