schlinki

oh and...just out of curiosity.

what is hotplugging?

is it a piece of program that probes certain addresses if a device is present?

..mhm yeah i know i should read some docs..

omg, i just rebooted and... IT WORKS! : )

it took me some time to find out what i did differently, and indeed, anon, it was just selecting LAN connection instead of Cable. (this shot in the dark was worth 10 points :)) But weird, it used to be Cable before and worked fine..

Anyways, thank you guys for your help. I've probably also learned a few things about my Mandrake.

This is a board to recommend.

hmm no. didnt work either. im getting kinda depressed. and i dont want to reinstall whole OS because of that problem...

Where this line in red  is coming from?

# cat /etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE=eth0

BOOTPROTO=dhcp

ONBOOT=yes

MII_NOT_SUPPORTED=no

WIRELESS_ENC_KEY=""

NEEDHOSTNAME=yes

Untitled 1

<{POST_SNAPBACK}>

oh sorry. i must have pasted it accidentally. its the name of the textfille in gedit where i pasted output.

devires : no hardware problem because it works fine now. (after using mcc for config)

hehe good thing im stuck to programming java app today, i can answer almost in realtime. : )

after disabling hotplugging it said bringing up interface eth0 [ OK ] during boot. however, eth0 wasnt up, and i still had no connection. btw, what is hotplugging anyway? : )

everytime after reboot i go to the MCC, but i wonder why "Manage Connections" always shows there is no connection. its as if it didnt make a permanent entry in startup scripts or something..

and yes, board has onboard-gigabit-ethernet, but ive disabled it in bios. (to avoid going through register-your-new-network-card-procedure with my isp. (i still had to reactivate windows though))

nope

neither ping nor website works.

(unknown host...)

so its really not lying (sadly).

# /etc/init.d/network status
Configured devices:
lo eth0
Currently active devices:
lo

# ifconfig eth0
eth0   Link encap:Ethernet  HWaddr (mac here, correct)
         inet addr:(ip here, correct)  Bcast: (bcast here, correct)  Mask:255.255.255.0
         inet6 addr: (also correct) Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:41042 errors:0 dropped:0 overruns:0 frame:0
         TX packets:3571 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:5231795 (4.9 Mb)  TX bytes:737756 (720.4 Kb)
         Interrupt:16 Base address:0x1000

ifconfig eth0 after connecton up is basically the above..

/etc/sysconfig/network-scripts/ifcfg-eth0

contains the same things after boot (not connected) and after connection made.

see posting #3 this thread. ive pasted them before. :)

(and doublechecked now)

it seems this is a weird problem?

concerning my update done to the computer : ive upgraded to athlon 64 cpu. but i doubt this has something to do with it, since everything else (really everything) runs fine.

# /etc/init.d/network restart
Shutting down loopback interface:                               [  OK  ]
Setting network parameters:                                     [  OK  ]
Bringing up loopback interface:                                 [  OK  ]
Bringing up interface eth0:                                     [FAILED]

and therefore

# ifconfig eth0
eth0: error fetching interface information: Device not found

and

# /etc/init.d/network status
Configured devices:
lo eth0
Currently active devices:
lo

thats the log-output i get when configuring via mdk configuration tool.. dunno maybe itll help

15:20:20 drakconnect[5152]: ### Program is starting ### 
15:20:32 drakconnect[5152]: launched command: /sbin/chkconfig --add internet 
15:20:32 drakconnect[5152]: modified file /etc/sysconfig/network 
15:20:32 drakconnect[5152]: modified file /etc/sysconfig/network-scripts/ifcfg-eth0 
15:20:32 drakconnect[5152]: written eth0 interface configuration in /etc/sysconfig/network-scripts/ifcfg-eth0 
15:20:32 drakconnect[5152]: writing host information to /etc/hosts 
15:20:32 drakconnect[5152]: created file /etc/hosts 
15:20:32 drakconnect[5152]: launched command: /sbin/chkconfig --add internet 
15:20:32 drakconnect[5152]: modified file /etc/sysconfig/network 
15:20:32 drakconnect[5152]: modified file /etc/sysconfig/network-scripts/ifcfg-eth0 
15:20:32 drakconnect[5152]: written eth0 interface configuration in /etc/sysconfig/network-scripts/ifcfg-eth0 
15:20:32 drakconnect[5152]: writing host information to /etc/hosts 
15:20:32 drakconnect[5152]: created file /etc/hosts

nope ifup eth0 didnt work.

and the init scripts look.. well enigmatic to me. :unsure:

still i can easily bring up eth0 through mandrake computer configuration..

is there some logfile to see what exactly goes wrong during boot?

boot.log doesnt give me more than what ive seen on bootscreen.

Welcome to the board.

thank you.

result while being connected to net :

# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=yes
MII_NOT_SUPPORTED=no
WIRELESS_ENC_KEY=""
NEEDHOSTNAME=yes
Untitled 1

and result after reboot (no connection) :

# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=yes
MII_NOT_SUPPORTED=no
WIRELESS_ENC_KEY=""
NEEDHOSTNAME=yes

hmm looks pretty much the same..

hello,

im sure you people can help me.

problem :

well it was pretty cool that mandrake (10.0) still runs after upgrading cpu and motherboard, the only problem i have now is, that it wont start eth0 at boot time.

(boot message : bringing up eth0 ... [failed])

i have a cable connection which is always on and i can always start the net trough system / configuration / configure your computer ... add new connection.

it runs without any problem. but when i reboot i have to do this again.

so my question is :

if it cannot be done with those nice gui tools, what are the config files to look at?

my guess is that it expects the network card (which is the same as in the old mb btw.) on some different location (maybe wrong pci-slot?).

how can i tell him to use the new config and forget the old?

thanks for reading and hopefully for replies.

-s.