VIA Cicada VT6122 Gigabit LAN and Debian
Anyone got that thing working? Can see the actual card in dmesg. . But i have no net. . Im comfused. . .
Anyone got that thing working?
Can see the actual card in dmesg.. But i have no net..
Im comfused..
Can see the actual card in dmesg.. But i have no net..
Im comfused..
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
Can you give us a little more information?
Is this Debian Woody, Sarge, or Sid?
Are you connected to the internet by broadband or DSL?
Did you have internet access during the installation process, when the apt repositories were set up?
When you type in ifconfig in a terminal window, as root user, do you get any eth0 output lines? You should see output something like;
eth0 Link encap:Ethernet HWaddr 00:14:2A:E9:8F:0C
inet addr:192.168.1.47 Bcast:255.255.255.255 Mask:255.255.255.0
inet6 addr: fe80::214:2aff:fee9:8f0c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1264 errors:0 dropped:0 overruns:0 frame:0
TX packets:1328 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:972422 (949.6 KiB) TX bytes:296788 (289.8 KiB)
Interrupt:17
Is this Debian Woody, Sarge, or Sid?
Are you connected to the internet by broadband or DSL?
Did you have internet access during the installation process, when the apt repositories were set up?
When you type in ifconfig in a terminal window, as root user, do you get any eth0 output lines? You should see output something like;
eth0 Link encap:Ethernet HWaddr 00:14:2A:E9:8F:0C
inet addr:192.168.1.47 Bcast:255.255.255.255 Mask:255.255.255.0
inet6 addr: fe80::214:2aff:fee9:8f0c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1264 errors:0 dropped:0 overruns:0 frame:0
TX packets:1328 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:972422 (949.6 KiB) TX bytes:296788 (289.8 KiB)
Interrupt:17
Quote:I connect directly to the net via rj45. No DLS or similar.. Just standard ethernet..
Well, DSL connects via ethernet, as well. So, you are connected to broadband via ethernet (the connection is always active)?
The problem is one of two possible issues.
1. The incorrect module is loaded for the card, which is possible.
2. The system is not set up for auto DHCP.
If you are running the Gnome display manager, go to;
System-->Aministration-->Networking. Does this show the card to be active?
Click on the ethernet connection that shows, then "edit" to edit the connection. Click on the box to check of DHCP. Finish the process and see if you get an IP address. If not, try typing into a root console'
ifup eth0
Then see if it works. if not reboot the system and see if it comes up at boot.
Well, DSL connects via ethernet, as well. So, you are connected to broadband via ethernet (the connection is always active)?
The problem is one of two possible issues.
1. The incorrect module is loaded for the card, which is possible.
2. The system is not set up for auto DHCP.
If you are running the Gnome display manager, go to;
System-->Aministration-->Networking. Does this show the card to be active?
Click on the ethernet connection that shows, then "edit" to edit the connection. Click on the box to check of DHCP. Finish the process and see if you get an IP address. If not, try typing into a root console'
ifup eth0
Then see if it works. if not reboot the system and see if it comes up at boot.
If you have a fixed IP address (static), then of course, you have to tell Debian what the values are. From the article How To Set Up A Linux Network, read the following information from the "At Home" portion of the document;
Quote:On Windows PCs, go toStart/Settings/Control Panels/Networking
and get into the TCP/IP properties for the NIC where you can enter an IP address for the PC, a subnet mask, and possibly a default gateway (if you have a broadband Internet connection). When you enter an IP address into the TCP/IP properties like this it's called a "static" IP address because it won't change unless you change it.
Then you can go to the Debian network utility and add the values, configuring the network as a static connection.
Quote:No dsl.. fiber all the way to my socket..
I'm not sure what you mean by this, but either you have DSL (where the ethernet cable runs from the system to a DSL modem), or if via broadband, the CAT5 cable runs to the modem, which is connected to your broadband cable.
Quote:On Windows PCs, go toStart/Settings/Control Panels/Networking
and get into the TCP/IP properties for the NIC where you can enter an IP address for the PC, a subnet mask, and possibly a default gateway (if you have a broadband Internet connection). When you enter an IP address into the TCP/IP properties like this it's called a "static" IP address because it won't change unless you change it.
Then you can go to the Debian network utility and add the values, configuring the network as a static connection.
Quote:No dsl.. fiber all the way to my socket..
I'm not sure what you mean by this, but either you have DSL (where the ethernet cable runs from the system to a DSL modem), or if via broadband, the CAT5 cable runs to the modem, which is connected to your broadband cable.
Ok, then this is as far as I can take this thread without you telling us how exactly you are connected to the Internet.
Understand that we can't speculate what is wrong without knowing your exact situtation.
The article I referenced covers most of the bases for the various situations and using Debian to connect at home, work or on a private network.
If you are connecting to a network from work, or say from a dorm room or appartment complex which has a building/system wide Internet connection using a fixed ISP address, then perhaps you should consult the IT/LAN administrator to discuss how to connect and if using other than a supported OS setup works. I can only speculate on your situation, but this just results in too little information and wasted posts on both ends.
Either way, let us know what progess that you make.
Understand that we can't speculate what is wrong without knowing your exact situtation.
The article I referenced covers most of the bases for the various situations and using Debian to connect at home, work or on a private network.
If you are connecting to a network from work, or say from a dorm room or appartment complex which has a building/system wide Internet connection using a fixed ISP address, then perhaps you should consult the IT/LAN administrator to discuss how to connect and if using other than a supported OS setup works. I can only speculate on your situation, but this just results in too little information and wasted posts on both ends.
Either way, let us know what progess that you make.