RealTek RTL8100 BL NIC Driver

View: New views
7 Messages — Rating Filter:   Alert me  

RealTek RTL8100 BL NIC Driver

by Brad Klinghagen :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I'm configuring a new firewall appliance (an Acrosser AR-M9952 network
appliance/embedded PC), and it uses the RealTek RTL8100 BL NIC driver. To
try and determine what NIC driver to use, I consulted their website which
indicated that for all the various OSes, the driver for rtl8100 xL and
rtl8139 xl are the same. So based on that I thought to try either 8139cp.o
or 8139too.o (along with crc32.o and mii.o ) modules. Initially I loaded
both (8139cp and 8139too), and the system gave a message indicating to try
8139too.o module, which is what I've done.

 

The system goes through the boot up process fine, and it seems to load the
drivers because each of the NICs (three of them) are identified by ETH0,
ETH1, ETH2, their MAC addresses, and assigned IRQs.

 

To assign IP addresses, ETH0 uses DHCP to pick up a static IP from my ISP,
and the other two have static IPs.  DHCP never picks up the address from the
ISP, and when I try to ping any of the IP addresses from the system itself,
a message appears stating that it I entered an invalid argument.

 

Is there another module I'm supposed to use (like r8169.o), or am I out of
luck. It would seem if the Realtek driver is the same for either NIC (8139
or 8100), it would seem to me that the 8139.o module should work - but I'm
probably over simplifying things.

 

If there isn't a driver available, do I have any options that would allow me
to use this new appliance?

 

Thanks for any assistance.

bpk

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
------------------------------------------------------------------------
leaf-user mailing list: leaf-user@...
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/

Re: RealTek RTL8100 BL NIC Driver

by Erich Titl :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Brad

Brad Klinghagen wrote:

> I'm configuring a new firewall appliance (an Acrosser AR-M9952 network
> appliance/embedded PC), and it uses the RealTek RTL8100 BL NIC driver. To
> try and determine what NIC driver to use, I consulted their website which
> indicated that for all the various OSes, the driver for rtl8100 xL and
> rtl8139 xl are the same. So based on that I thought to try either 8139cp.o
> or 8139too.o (along with crc32.o and mii.o ) modules. Initially I loaded
> both (8139cp and 8139too), and the system gave a message indicating to try
> 8139too.o module, which is what I've done.
>
>  
>
> The system goes through the boot up process fine, and it seems to load the
> drivers because each of the NICs (three of them) are identified by ETH0,
> ETH1, ETH2, their MAC addresses, and assigned IRQs.
>
>  
>
> To assign IP addresses, ETH0 uses DHCP to pick up a static IP from my ISP,
> and the other two have static IPs.  DHCP never picks up the address from the
> ISP, and when I try to ping any of the IP addresses from the system itself,
> a message appears stating that it I entered an invalid argument.

It might help if you posted the original error along with the output of
lsmod and dmesg.

>
>  
>
> Is there another module I'm supposed to use (like r8169.o), or am I out of
> luck. It would seem if the Realtek driver is the same for either NIC (8139
> or 8100), it would seem to me that the 8139.o module should work - but I'm
> probably over simplifying things.

yes, the Realtek page suggests that. They also say, that the driver is
in the current kernel distribution

>
>  
>
> If there isn't a driver available, do I have any options that would allow me
> to use this new appliance?

A quick check might be to load a current knoppix disk and see if it can
use the NICs. If it can't chances are they are badly supported. I looked
at the 8139too source, they reference the 8100B model, so this should work.

cheers

Erich


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
------------------------------------------------------------------------
leaf-user mailing list: leaf-user@...
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/

Re: RealTek RTL8100 BL NIC Driver

by Robert K Coffman Jr. -Info From Data Corp. :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I've run into one situation where dhcpcd would not pull an address from the
ISP and pump worked fine.  Perhaps you are running into something like that
rather than a driver problem?



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
------------------------------------------------------------------------
leaf-user mailing list: leaf-user@...
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/

Parent Message unknown Re: RealTek RTL8100 BL NIC Driver

by Erich Titl :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Brad


Brad Klinghagen wrote:
> I've attached system messages, log files, configuration data, and error
> messages. Let me know if you need more.

I looked first at your lsmod output

Module Size  Used by    Not tainted
usbcore                51820   0
ext2                   29728   0 (unused)
wd1100                  2300   0 (unused)
ipt_ipp2p               5908   0 (unused)
ipt_state                272   0 (unused)
ipt_helper               400   0 (unused)
ipt_conntrack            692   0 (unused)
ipt_REDIRECT             480   0 (unused)
ipt_MASQUERADE          1024   0 (unused)
ip_nat_irc              1704   0 (unused)
ip_nat_ftp              2152   0 (unused)
iptable_nat            14388   2 [ipt_REDIRECT ipt_MASQUERADE ip_nat_irc
ip_nat_ftp]
ip_conntrack_irc        2484   1
ip_conntrack_ftp        3132   1
ip_conntrack           16548   2 [ipt_state ipt_helper ipt_conntrack
ipt_REDIRECT ipt_MASQUERADE ip_nat_irc ip_nat_ftp iptable_nat
ip_conntrack_irc ip_conntrack_ftp]
8139too                11944   0
mii                     1820   0 [8139too]
crc32                   2620   0 [8139too]
vfat                    8492   2
isofs                  15732   0 (unused)
ide-detect               132   0 (unused)
ide-cd                 26748   0
ide-disk               11372   3
ide-core               88280   3 [ide-detect ide-cd ide-disk]
cdrom                  25568   0 [ide-cd]

Unless you are running on a WRAP or anything similat to it, you don't
need the wd1100 driver but either a watchdog specific for this
board/chipset or softdog.

>
> As I looked over the files, it seems the 8139too.o module is allowing the
> NICs to work at some level; each NIC has the MAC address assigned, IRQ
> interrupts. When I execute 'ip addr' the system indicates each of the
> interfaces are up. When I try to ping eth1 on the firewall from the firewall
> I get the enclosed message in pingResults.

1: lo: <LOOPBACK> mtu 16436 qdisc noop
     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop
     link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
3: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast qlen 1000
     link/ether 00:02:b6:35:d7:a9 brd ff:ff:ff:ff:ff:ff
4: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
     link/ether 00:02:b6:35:d7:a8 brd ff:ff:ff:ff:ff:ff
     inet 10.0.0.1/24 brd 10.0.0.255 scope global eth1
5: eth2: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
     link/ether 00:02:b6:35:d7:a7 brd ff:ff:ff:ff:ff:ff
     inet 10.0.2.1/24 brd 10.0.2.255 scope global eth2

This shows eth0 down probably because dhcp failed. The other ethernet
adapters appear to be up.

8139too Fast Ethernet driver 0.9.26
eth0: RealTek RTL8139 at 0xd0046000, 00:02:b6:35:d7:a9, IRQ 5
eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
eth1: RealTek RTL8139 at 0xd0048000, 00:02:b6:35:d7:a8, IRQ 10
eth1:  Identified 8139 chip type 'RTL-8100B/8139D'
eth2: RealTek RTL8139 at 0xd004a000, 00:02:b6:35:d7:a7, IRQ 11
eth2:  Identified 8139 chip type 'RTL-8100B/8139D'

The driver appears to find the interfaces.

but, as mentioned before....

wd1100.c: unknown model value 1, trying anyway
wd1100.c: Can not find bridge device.

please get rid of the wd1100 stuff, it is _not_ a SC1100

>
> I also tried restarting one of my desktop computers, which gets it's IP
> address from the firewall via dnsmasq. The desktop never received an IP
> address from the firewall.

No surprise, you cannot even access your own interfaces as the
pingresults show.

In the config files I could not see any obvious problem

The only thing I could see is

Linux version 2.4.31 (root@enterprise) (gcc version 3.3.3) #1 Thu Aug 18
21:03:20 CEST 2005

This is not the current bering-uClibc kernel. Is it possible that you
mixed kernels and modules?

cheers

Erich

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
------------------------------------------------------------------------
leaf-user mailing list: leaf-user@...
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/

Parent Message unknown Re: RealTek RTL8100 BL NIC Driver

by Erich Titl :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message



Brad Klinghagen wrote:
> I'm obviously missing something regarding burning the CD. I tried again with
> both CD images. The _usb_...img (I uncompressed the file) version burned a
> blank CD again, and with _iso_....bin I couldn't even get Nero to burn the
> image because of unrecognized format (which makes sense because it is a .bin
> extension). Why not just have the image in .iso format or compressed iso.gz?

Just rename it to whatever.iso, I have no clue what the .bin extension
is good for, possibly for some Windoze based browser.

And please keep traffic on the list

Erich





-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
------------------------------------------------------------------------
leaf-user mailing list: leaf-user@...
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/

Parent Message unknown Re: RealTek RTL8100 BL NIC Driver

by Erich Titl :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Brad

Brad Klinghagen wrote:
> If it ain't syslinux, then I know I downloaded the most recent versions of
> the modules -

Yes, but your kernel was not the latest and greatest.

I ended up downloading them straight from the website. The
> only way I could have the wrong kernel is that one of the packages is older.
> Is it the modules.lrp and moddb.lrp that I need to ensure are the latest and
> greatest?

They just have to match the kernel, which in your case was 2.4.31, the
modules themselves may not even have changed version numbers.

You _must_ use kernel and modules from the same release, don't worry too
much about the syslinux release.

cheers

Erich



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
------------------------------------------------------------------------
leaf-user mailing list: leaf-user@...
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/

Parent Message unknown Re: RealTek RTL8100 BL NIC Driver

by Erich Titl :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Brad

Brad Klinghagen wrote:
> I copied the Linux file from the floppy disk generated by the pre-packaged
> download file and I executed syslinux from the floppy (after installing
> hdsupp). When I booted my system (not my target, but the pseudo-duplicate),
> then entered the command uname -a, the version of Linux was 2.4.34? Is that
> the latest version?

Yes it is

Erich

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
------------------------------------------------------------------------
leaf-user mailing list: leaf-user@...
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/