IC Plus IP100 Fast Ethernet headache

Well, I'm having some problems to configure this damn ethernet adapter to an adsl connection. I can't find out which driver I must use for it. I want some directions before I go to a store =\. Well, I'm starting to use FreeBSD as a Desktop OS, instead of trying some lamesh!t M$ suXP.

Here is the link of the ppp.conf configuration I'm trying for adsl.

I would thank all the help.

I've already looked at:

FreeBSD/i386 6.2-RELEASE Hardware Notes

I haven't found anything yet. Sorry for my bad english :mrgreen:

BTW, this is FreeBSD 6.2.

--------------------------------------------------
"default:
set device PPPoE:ed0:ISP
enable lqr
enable tcpmssfixup

set lqrperiod 6
set mru 1492
set mtu 1492
set timeout 0
set log phase tun

nat enable yes

add default HISADDR

enable dns

set authname 715557777
set authkey 715557777"
---------------------------------------------------
I need to know what to put in the place of ed0 here, which is the "name" of the IC Plus 100IP Fast Ethernet :

" set device PPPoE:ed0:ISP"

I can't find it in the list on the "Hardware Notes"-page, the one that seems most similar is the IC Plus IP1000A wich uses the stge device. So it is probable that the device is 'stge0'.

But to find out for sure you should only have to run:

Code:

---

# dmesg | grep -e 'IC Plus 100IP'

---

But I don't know if FreeBSD recognizes your card with exacly that name so you should widen the grep a little bit if you want. Or you could just read through the dmesg with less:

Code:

---

# dmesg | less

---

Quote:

---

Originally Posted by nalg0rath

I can't find it in the list on the "Hardware Notes"-page, the one that seems most similar is the IC Plus IP1000A wich uses the stge device. So it is probable that the device is 'stge0'.

But to find out for sure you should only have to run:

Code:

---

# dmesg | grep -e 'IC Plus 100IP'

---

But I don't know if FreeBSD recognizes your card with exacly that name so you should widen the grep a little bit if you want. Or you could just read through the dmesg with less:

Code:

---

# dmesg | less

---

---

Thanks Nalgorath.

Firstly, I tried the stge driver. It really haven't worked since the IC Plus IP1000A is made by GIgabite and the IC Plus IP100 is made by IC Corps. I've seen it before i posted here =\.

I will test the dmesg :)

I will post the results around here. I hope I don't need to put some cash, since here in Brazil these things are around 40 bucks =p

c ya =D

Hello, I'm back with bad news =\

Well...

1- the command "dmesg | grep -e 'ethernet's name'" haven't shown nothing beyond the black color of my console xD;

2- as it isn't news as seen in dmesg's first command line, I tried "dmesg | less", which displayed most of my hardware and I got that line :

"pci2: <network, ethernet> at device 10.0 (no driver attached)"

Well... I think it is time to spend some money hunf =\\\\\\\

My mobo is a Abit KU8 and the ethernet device is onboard ;p, maybe it tells us all hahaha

My suspicious is that the forst command line didn't worked probably because this device is so sh!tty that FreeBSd really doesn't recognize it.

So thx you guys anyway. New ideas are welcome as mutch as points of view about the result. I'm a beginner. Sorry ;p

Well, I found something interesting here, yet I don't know how to apply these fixes. Could someone help me telling me what is this ?

kern/99064: ste driver does not support IC Plus IP100A chipsets

">Number: 99064
>Category: kern
>Synopsis: ste driver does not support IC Plus IP100A chipsets
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: change-request
>Submitter-Id: current-users
>Arrival-Date: Fri Jun 16 22:20:19 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator: Pedro Alejandro López-Valencia
>Release: 6.1-RELEASE
>Organization:
>Environment:
FreeBSD fanelia.lan 6.1-RELEASE FreeBSD 6.1-RELEASE #1: Thu Jun 15 14:12:33 COT 2006 root@:/usr/obj/usr/src/sys/LOCAL i386

>Description:
IC Plus Corp. owns the Sundance Tech ehternet chipset business since 2004. The IP100A chipset has appeared in several inexpensive network cards by D-Link and Encore (I bought one of each last week, lucky me) and as the chipset of integrated network interfaces of latest model mainboards manufactured by ABIT, ASUS and Nvidia.

The chipset manufacturer supplies its own version of the ste driver (<http://www.icplus.com.tw/pp-IP100A.html>), but it is based on 4.x code. I would like to see the fix (which is trivial as seen in the patch below) integrated in FreeBSD. Please notice that, as seen in the vendor's website mentioned above, the ST201 chipset is now known as the IC Plus Corp. IP100 chipset.


>How-To-Repeat:
Install PCI ehternet card or use mainboard with integrated ehternet chipset (e.g, ABIT KU8/KV8//AX8/NF7-S2, ASUS P4B266/P5GD1-VM, etc.). It isn't recognized by any network driver in the distributed GENERIC nor SMP kernels.

>Fix:

*** if_ste.c 2006/06/15 22:41:48 1.1
--- if_ste.c 2006/06/15 22:56:51 1.2
***************
*** 87,92 ****
--- 87,93 ----
static struct ste_type ste_devs[] = {
{ ST_VENDORID, ST_DEVICEID_ST201, "Sundance ST201 10/100BaseTX" },
{ DL_VENDORID, DL_DEVICEID_DL10050, "D-Link DL10050 10/100BaseTX" },
+ { IC_VENDORID, IC_DEVICEID_IP100A, "IC Plus Corp. IP100A 10/100BaseTX" },
{ 0, 0, NULL }
};

*** if_stereg.h 2006/06/15 22:41:48 1.1
--- if_stereg.h 2006/06/15 23:05:49 1.2
***************
*** 46,51 ****
--- 46,58 ----
#define DL_DEVICEID_DL10050 0x1002

/*
+ * IC Plus Corp. PCI device/vendor ID for the
+ * IP100A chip.
+ */
+ #define IC_VENDORID 0x13F0
+ #define IC_DEVICEID_IP100A 0x0200
+
+ /*
* Register definitions for the Sundance Technologies ST201 PCI
* fast ethernet controller. The register space is 128 bytes long and
* can be accessed using either PCI I/O space or PCI memory mapping.

>Release-Note:
>Audit-Trail:
>Unformatted:"

Should I make it in the kernel or what ?

I'm sorry for bothering you guys with all that thing.

It seems the bug is solved and in 6.3 my ethernet adapter will be accepted. Now all I have to do is wait :p

Thx for the atention. For more details :

http://ftp.cz.freebsd.org/pub/FreeBS...ats/kern/99064

Quote:

---

Originally Posted by fawz

Now all I have to do is wait

---

That or shell out $20 for an inexpensive NIC that's already supported. :)

Quote:

---

Originally Posted by anomie

That or shell out $20 for an inexpensive NIC that's already supported. :)

---

Yes, i'm working my anxiety buying a 3com 3C905B, but it isn't working... the lights aren't turning on. I will ask them for another... but that's the second time. The problem with the other one was that when I placed the ethernet my pc wasn't turning on. I heard no beeps :p. Also I know that's not my mobo dying because a Lucent modem works perfectly in this pci slot... well , since when a lucent winmodem works perfectly? Jesus... what am I talking about? :dazed:

well I will not go emo because of that

:drown:

Btw, I've just forgotten to ask :

The next in my list (looking at the existing ethernet adapters here in Rio de janeiro) is the Enconre ENL832-TX, which is supported by FreeBSD 6.2 as it says in the hardware release notes... but... I can't really find a pure tx, i just found these ones :

ENL832-TX-ICNT
ENL832-TX-EN
ENL832-TX-RENT

Now which one is supported hehehehe? I haven't found no ENL832-TX , just these ones. Anyone here knows which one really works on FreeBSD ?

BTW, anyone knows when will the 6.3 thing be released ?

I see what you mean. I ran a search for ENL832-TX on google product search and got a long list for that card (but with various different suffixes). I suspect any of those ENL832-TX cards will work. But if you don't want to take the risk, you might try the FBSD hardware mailing list:
freebsd-hardware Info Page

Be sure to read about the mailing lists here if you haven't used them before:
Resources on the Internet

I don't know when 6.3 will be released. If you are interested in tracking the -STABLE branch (I don't recommend doing that just to get a currently unsupported NIC to work), there is info on doing that here:
FreeBSD-CURRENT vs. FreeBSD-STABLE