Julia64 can't connect eth0/adsl (SOLVED)

[flon]

Edited -- december 27
Go to the last post for the solution.
f
------------------------------------

... and the same happens with other distros/versions using kernel 2.6.35.

After gugling and forums for almost a week, nothing useful.

--------------------------
HardWare -- (Isadora Ok on it) :
- Intel based, DG965WH, Core2Duo 6400, DDR2=1GiB
- Communication controller: Intel Corporation 82P965/G965 HECI Controller (rev 02)
- Ethernet controller: Intel Corporation 82566DC Gigabit Network Connection (rev 02)
- ADSL modem: DSLink 260E - as router, connecting directly to Telco servers.
- no wireless, no other Eth board.

--------------------------

Some more, from julia live:

Code: Select all

mint@mint ~ $ dmesg |grep eth0
[    4.172401] e1000e 0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1) 00:19:d1:01:10:29
[    4.172405] e1000e 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
[    4.172428] e1000e 0000:00:19.0: eth0: MAC: 6, PHY: 6, PBA No: ffffff-0ff
[   58.360338] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   59.730907] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
[   59.730912] e1000e 0000:00:19.0: eth0: 10/100 speed: disabling TSO
[   59.731067] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   69.970028] eth0: no IPv6 routers present


Code: Select all

mint@mint ~ $ sudo ifconfig
eth0      Link encap:Ethernet  HWaddr 00:19:d1:01:10:29 
          inet6 addr: fe80::219:d1ff:fe01:1029/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:6129 (6.1 KB)
          Interrupt:20 Memory:51200000-51220000

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:36 errors:0 dropped:0 overruns:0 frame:0
          TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2496 (2.4 KB)  TX bytes:2496 (2.4 KB)


Code: Select all

mint@mint ~ $ nm-tool

NetworkManager Tool

State: disconnected

- Device: eth0
  Type:              Wired
  Driver:            e1000e
  State:             disconnected
  Default:           no
  HW Address:        00:19:D1:01:10:29

  Capabilities:
    Carrier Detect:  yes
    Speed:           100 Mb/s

  Wired Properties
    Carrier:         on


tia,
flon

[lauren]

Hi!
Maybe IPv4 is a better choice than IPv6, maybe there is a problem with the nameservers.
lauren

[flon]

Nothing useful?

[HarzVieh]

Nothing useful?

I am new to Mint.. but I did install Ubuntu in the past, and I have DSL modem.. not a rooter.. so I must say there is only one procedure that works in my situation so I can connect to the Internet: open terminal and type:

Code: Select all

pppoeconf

then all what comes depends on your provider, like for Username I must give numbers (well this is the difference between ISP providers.. so no one can know it all I assume) then I give #0001 because I do have just only one telephone and then I give @t-online.de ( my ISP) that's all in one line without any interruption in Username.. like this: 000000000111111111#0001@t-online.de
Then in the following window I give my password.. again this is my password the ISP give me in the beginning per post mail.
The option not connecting at boot is not working.. but if I choose connect at boot I have Internet connection right from the start..
They write, you can connect with pon and poff commands but then you are not in a "dip" group.. so I did not try that but just find out the following.. so I don't know if this is working..

On some versions of Ubuntu you do not automatically have all the permissions to run gnome-ppp if you are the first (default) user created even with though you should have all the normal administration privileges - you need to be both in the dip and the dialout groups to run it. This apparent mistake was probably done for additional security but is a nuisance. If this is the case the log file which is available from the Log button will have a line complaining about permissions for the executable file /usr/sbin/pppd.

The easiest way to get the required privileges is to do System -> Administration -> Users and Groups then unlock with your password and highlight your user name and click Properties and on the User Privileges Tab tick 'Connect to Internet using a Modem' which adds you to the dip group and 'Use Modems' which adds you to the dialout group. Neither act immediately and you need to restart or logout and back in as the same user.

If this does not work or you prefer to use a terminal then the following two commands will add YOURUSERNAME to the dip and dialup groups

Code: Select all

sudo adduser YOURUSERNAME dip
sudo adduser YOURUSERNAME dialout

[Dindja]

Your ifconfig output looks exactly the same as I was getting with a similar configuration but different hardware. The inet line is absent.
Try the tricks on http://ubuntuforums.org/showthread.php?p=10130966#post10130966

Alternatively, go to the BIOS configuration and try disabling the LAN boot ROM.

[flon]

Problem were on the module e1000e, a bug of kernel 2.6.35. Solved in 2.6.36.
This module controls Intel / Gigabit networking.

Some hardwork to a solution: get the "e1000e" source on kernel.org, do the procedings to compile it and, then, modprobe it.

sorry for the wronglish,
flon