LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   Getting problem with rhine family lan card (https://www.linuxquestions.org/questions/linux-hardware-18/getting-problem-with-rhine-family-lan-card-435230/)

alok.rhct 04-14-2006 06:25 PM

Getting problem with rhine family lan card
 
hi,
thanks for giving attention..
i have a problem regarding my lan card(i.e of suercom Ethernet adaptar). I have two lan card as one for internet connection and second for home networking. My second nic is not detected. I have tried it by the rhine II driver supported by RHEL4(Kernel 2.6).

I also tried to compile the driver rhinefet.tgz as

cd /usr/local
tar xzvf /tmp/rhinefet.tgz
it shows as:
Makefile
kcompat.h
rhine_cfg.h
rhine.h
rhine_proc.h
rhine_wol.h
rhine_main.c
rhine_proc.c
rhine_wol.c
linux.txt

But i am not getting the file named rhinefet.o or rhinefet.ko(as linux.txt says)were i cd and execute commend make.

My configuration are:
945 intel motherboard
80 Gb SATA hdd2
1 gb RAM
RHEL4 os

This is the best of my knowledge.

Will any one help me how to proceed(i.e to install the driver). it will realy a great help.

Thanks in advance.

bathory 04-15-2006 11:41 AM

Did you try to use the common via-rhine driver to see if it works? Try:
Code:

modprobe via-rhine
If that doesn't work, then run "make" in the directory you extracted the driver source and watch for any errors.
If there are no errors try to load the driver into the kernel (it should be rhinefet.ko since you use a 2.6 kernel):
Code:

insmod rhinefet.ko

alok.rhct 04-15-2006 03:38 PM

hi bathory,
i have tried modprobe via-rhine by command system-config-network.but it don't work.

I have also tried make command . i am getting lots of error. and their is no file named as rhinefet.ko. can u tell me how will i get this file.

bathory 04-15-2006 04:53 PM

You should post the errors you get, to help you build the driver. Also the exact model of your nic would also help to identify the correct driver. Run
Code:

lspci
to find out what your nic model is.

alok.rhct 04-15-2006 05:20 PM

after executing make i got lots of warning and error as :

warning: /usr/local/rhine_mail.c:59: warning:`MODULE_PARM_` is deprecated (declerad at include/linux/module.h:552).
many no of times, and;

ERROR as:
/usr/local/rhine_main.c:1211:error:union has no member named`ethernet`
make[2]:***[/usr/local/rhine_main.o]ERROR 1
make[1]:***[_module_/usr/local]ERROR 2
leavind directory
make: *** [default]Error 2

hope, this will help u more .please help me.
Thanks

alok.rhct 04-15-2006 05:28 PM

After running lspci i got output as:

04:00.0 Ethernet controller:VIA Technologies,Inc.Vt6105 [Rhine-III] (rev 8b) and:

04:00.0 Ethernet controller:Intel Corp.: Unknown device 27dc (rev 01)

I have to Card. which one of the above two is working i don't know.
will u help me.

bathory 04-17-2006 02:19 AM

I've tried to compile the latest driver in 2.6.16.5 and 2.6.15.6 kernels just for testing and it failed. But it compiles fine in 2.6.8 and 2.4.31 kernels. So I guess it's not compatible with the newest kernels. I think that the via-rhine module included with your kernel should work. What happens when you modprobe it? What is the output of "dmesg"?
Also for the Intel nic try:
Code:

modprobe e100
or
modprobe e1000

to see if it works.

alok.rhct 04-17-2006 11:18 PM

after running modprobe via-rhine in dmsg i foun entry as:
via-rhine.c:v1.10-LK1.2.0-2.6 June-10-2004 Written by Donald Becker
eth0: VIA RHine III at 0x50001000, 00:02:44:af:c8:fd, IRQ11.
eth0: MII PHY found at address 1, status 0x7849 advertising 05e1 Link 000.

No entry for Eht1.

the name of my ehternet adaptar which i got from my p is

SURECOM Ep-320X-V/V1 32bit PCI 10/100M EHTERNET adapter

bathory 04-18-2006 02:25 AM

So your rhine nic works and it gets the eth0 interface. Doing a little search it seems that surecom uses via chipsets, so you're set. As for eth1 try to modprobe the intel modules (e100 or e1000) and watch dmesg output.

alok.rhct 04-24-2006 08:59 PM

i have tried modprobe e1000 &modprobe e100 but no result for eht1.

One thing i missed to tell u that my intel adapter is comming up insted of suercom adapter because when i execute command ifconfig it shows the address as 61.16.224.250 , which is of my intel NIC.(as it is connected to internet).

Noe what next to do?

bathory 04-25-2006 02:09 AM

Quote:

i have tried modprobe e1000 &modprobe e100 but no result for eht1.
What is the output of dmesg and lsmod? As for the output of ifconfig, it shows that the IP is assigned to the eth0 device. It could be the rhine nic that comes up and not the intel.

alok.rhct 04-26-2006 05:14 AM

yeh u r write. my intel adaptar is not working. now tell me what to do to detect the adapter name Intel(R) pro/100 ve .
this was the o/p of lspci
04:00.0 Ethernet controller: VIA Technologies, Inc. VT6105 [Rhine-III] (rev 8b)
04:08.0 Ethernet controller: Intel Corp.: Unknown device 27dc (rev 01)

the o/p of dmesg are
divert: not allocating divert_blk for non-ethernet device lo
divert: allocating divert_blk for eth0
eth0: VIA Rhine III at 0x50001000, 00:02:44:af:c8:fd, IRQ 11.
eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 0021.
divert: not allocating divert_blk for non-ethernet device sit0

bathory 04-26-2006 09:40 AM

for intel run:
Code:

modprobe e100

alok.rhct 04-26-2006 09:13 PM

i have trid modprobe e100. it run sussecfully but the entry of dmesg are same as previous(i.e no entry for eth1).
what to do next?

Can u tell me from where i got the driver for Intel(R) Pro/100 Ve for kernel(2.6)?

bathory 04-27-2006 02:39 AM

Quote:

Can u tell me from where i got the driver for Intel(R) Pro/100 Ve for kernel(2.6)?
The driver is already included in your kernel modules (the e100 module). If "modprobe e100" works with no errors try to assign IP address to see what happens:
Code:

ifconfig eth1 192.168.0.10 netmask 255.255.255.0 up
If you get no such device, perhaps you have to play with your BIOS settings (set or unset PnP) to see if lspci recognizes your Intel nic correctly.
You can also take a look here to see how you can build the driver and how to debug it.

Regards


All times are GMT -5. The time now is 12:00 AM.