Realtek Networkcard is not working

The Compal Networkcard of my Notebook is not working with the two moduls
8139too and 8139cp. At the window Hardware-Information under yast is it
displayed. At ifconfig -a it is displayed, but at the switch and the
notebook the connection lamp doesn´t light. But when I use Windows it
works.
I don´t know how to activate the networkcard.
It is an Compal CL56 or Bullman VK6 Notebook

Thanks

chris393@gmx.de adjusted his/her tinfoil beanie to post:

> The Compal Networkcard of my Notebook is not working with the two
> moduls 8139too and 8139cp. At the window Hardware-Information under
> yast is it displayed. At ifconfig -a it is displayed, but at the
> switch and the notebook the connection lamp doesn´t light. But when I
> use Windows it works.
> I don´t know how to activate the networkcard.
> It is an Compal CL56 or Bullman VK6 Notebook
>
> Thanks

Can you post the result of ifconfig -a please?

Also are you using a wifi card at the same time?


--
Mark
Twixt hill and high water
N. Wales, UK
Novell Support Forums SysOp

Hallo Mark,

there are no packets recieved and sent. I tried it with DHCP and static
IP. But no connection and no packets ...
At eth0 the WIFI intel 2200 works, but i don´t use it at home.

I have a log of the network restart and ifconfig -a

Thank you

Chris

linux:/ # rcnetwork restart
Shutting down network interfaces:
eth0 device: Intel Corporation PRO/Wireless 2200BG (rev 05)
eth0 No configuration found for eth0
Nevertheless the interface will be shut down.
eth0 configuration: done
eth1 device: Realtek Semiconductor Co., Ltd. RTL-
8139/8139C/8139C+ (rev 10)
eth1 configuration: eth-id-00:02:3f:09:7a:1d done
Shutting down service network . . . . . . . . . . . . . done.
Hint: you may set mandatory devices in /etc/sysconfig/network/config
Setting up network interfaces:
lo
lo IP address: 127.0.0.1/8 done
eth0 device: Intel Corporation PRO/Wireless 2200BG (rev 05)
eth0 No configuration found for eth0
unused
eth1 device: Realtek Semiconductor Co., Ltd. RTL-
8139/8139C/8139C+ (rev 10)
eth1 configuration: eth-id-00:02:3f:09:7a:1d
eth1 (DHCP) . . . . . no IP address yet... backgrounding.
waiting
Setting up service network . . . . . . . . . . . . . . done.
linux:/ # ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:0E:35:1A:B0:9C
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:10 Base address:0xe000 Memory:d0000000-d0000fff

eth1 Link encap:Ethernet HWaddr 00:02:3F:09:7A:1D
inet6 addr: fe80::202:3fff:fe09:7a1d/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:10 Base address:0xa000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:116 errors:0 dropped:0 overruns:0 frame:0
TX packets:116 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:9113 (8.8 Kb) TX bytes:9113 (8.8 Kb)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

chris393@gmx.de adjusted his/her tinfoil beanie to post:

> Hallo Mark,
>
> there are no packets recieved and sent. I tried it with DHCP and
> static IP. But no connection and no packets ...
> At eth0 the WIFI intel 2200 works, but i don´t use it at home.
>
> I have a log of the network restart and ifconfig -a
>
> Thank you
>
> Chris

Hi Chris,

What happens if you take down eth0 and eth1 and then just try and bring
eth1 up on its own:

ifdown eth0
ifdown eth1
ifup eth1

try that with DHCP and static please see if it makes any difference,
just trying all combinations to see if it is a settings or maybe a nic
driver problem, one more thing to think of as well is: have tou got
*both* interfaces set in the firewall as "external"?

HTH
--
Mark
Twixt hill and high water
N. Wales, UK
Novell Support Forums SysOp

baskitcaise adjusted his/her tinfoil beanie to post:

Just another question from me, what is the kernel version you have now
please?

uname -a

will show all theat is needed.

Thanks.

--
Mark
Twixt hill and high water
N. Wales, UK
Novell Support Forums SysOp

I know now, why the network don´t work. The Linux Modul can´t activate the
chipset, but if I use the Bios for Network-booting it works.
The 2.4 kernel don´t works without the booting trick too.
But the Windows driver activate the chipset. But it´s ok because I know now
what to do.
Thank you for help.
Chris
P.S. I use the new 10.0 suse Kernel 2.6.13.15

> baskitcaise adjusted his/her tinfoil beanie to post:
>
> Just another question from me, what is the kernel version you have now
> please?
>
> uname -a
>
> will show all theat is needed.
>
> Thanks.
>
> --
> Mark
> Twixt hill and high water
> N. Wales, UK
> Novell Support Forums SysOp
>

chris393@gmx.de adjusted his/her tinfoil beanie to post:

> I know now, why the network don´t work. The Linux Modul can´t
> activate the chipset, but if I use the Bios for Network-booting it
> works. The 2.4 kernel don´t works without the booting trick too.
> But the Windows driver activate the chipset. But it´s ok because I
> know now what to do.
> Thank you for help.
> Chris
> P.S. I use the new 10.0 suse Kernel 2.6.13.15

Thanks for the feedback Chris.


--
Mark
Twixt hill and high water
N. Wales, UK
Novell Support Forums SysOp