Jump to content

Activation of LAN in LE2005/MVA2006 [solved]

satelliteuser083

By satelliteuser083
in Networking

 Share

Recommended Posts

satelliteuser083 Awesome

satelliteuser083

Posted
Posted (edited)

I'd like to get to the bottom of this strange problem with my laptop/OS (Tosh-Sat-Pro-4600/LE2005&MVA2006), but need some advice. When I first boot the system following a SHUTDOWN, the LAN-connection is never made. To achieve this I have to RESTART the system and the LAN then comes up alright; normally, I don't even bother to sign-in the first time but restart immediately at the prompt. This problem has been around ever since I went on to broadband (about a year); it appears to be a combination of hardware and software, because:

 

a> the same OS's (LE2005 and MVA2006) work correctly on my desktop, i.e. LAN comes up first time, and

b> using Suse 10.1 on the Tosh the LAN comes up first time, too.

 

It would seem that something is reset on SHUTDOWN which is NOT reset on RESTART. I've also noticed, on a few occasions when the system has 'frozen' and I've had to do a manual RESET, that the LAN has come up correctly immediately (no need for a RESTART).

 

I know that this is a long shot, but has anyone else had similar experiences with network-connections and, if so, have you managed to solve them?

 

Thanks.

Edited by satelliteuser083
Link to comment
Share on other sites
arctic Platinum

arctic

Posted
Posted

You should not have to reboot the system in order to re/start the networking device. Try next time from a terminal as root user

 

ifup eth0

 

if eth0 is your networking device. If it has a different "callsign" (e.g. eth1) change accordingly. You can find out the correct "callsign" by running

 

ifconfig

 

If it REALLY fails, then it was (most likely) unable to load the needed module at startup.

Link to comment
Share on other sites
ianw1974 Platinum

ianw1974

Posted
Posted

I've only had problems with wireless interfaces when using ndiswrapper this way. Regardless of having the alias in /etc/modprobe.conf which should have taken care of loading the module when the respective eth0, eth1, wlan0 or whatever was called.

 

In the end, I added the particular module (in this case ndiswrapper) to /etc/modprobe.preload and it sorted my interface loading probs at bootup.

 

Doesn't sound the same as yours though, as yours does come up on a reboot. Which is rather odd.

Link to comment
Share on other sites
pmpatrick Mandriva Guru

pmpatrick

Posted
Posted

Add this to the end of your /etc/rc.d/rc.local file and see if it helps:

 

ifdown eth0

ifup eth0

 

rc.local is the last init script to run. I agree with arctic's observation that the nic driver may not have fully loaded at the time when the network attempts to start up. By restarting the network at the end of the boot process, you can get around this potential problem. The above assumes your network interface is eth0 which may not be the case if you are using a wireless connection.

Link to comment
Share on other sites
satelliteuser083 Awesome

satelliteuser083

Posted
  • Author
Posted (edited)

Sadly, none of the suggestions has had any affect. However, I vaguely remember reading something about a log-file, which keeps details of processes/modules etc that are started/killed at startup, shutdown (and, presumeably, restart). Could someone tell where this file is kept? Perhaps I can glean some info from it, relating to this problem. Also, I know a little about the various runtime levels set by the system, but could do with more detail. Could someone help me out with a site, manual or something like that? Thanks

Edited by satelliteuser083
Link to comment
Share on other sites
pmpatrick Mandriva Guru

pmpatrick

Posted
Posted (edited)

You can get all your boot messages that the kernel generated by opening a console immediately after booting and running:

 

$ demsg

 

To save to a text file for easier viewing run:

 

$ demsg > demsg.txt

 

A running log of this output can be found in /var/log/boot.log.

 

Just to rule this out, try passing these boot parameters by hiting the Esc key as soon as you see the lilo boot selection screen which will take you to the boot prompt. At the prompt type:

 

linux noapic nolapic acpi=off

 

The first word "linux" refers to the lilo entry you are booting which is "linux" by default in mandriva. If you normally boot a different entry, use that name instead. All the available lilo boot selections will be printed out on the top of the screen just above the boot prompt. See if this has any effect on your network problem. This will disable acpi which has been known to cause problems with certain nics in the past.

 

To verify that it is a module loading problem, after booting and the network not coming up, run as root:

 

# lsmod

 

that will list all the loaded modules. See if you can find your nic module in the output.

 

If you nic module is loaded, check the output of:

 

# ifconfig

 

and post back here. Also, check your network config file which is:

 

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

 

and post that here as well.

Edited by pmpatrick
Link to comment
Share on other sites
satelliteuser083 Awesome

satelliteuser083

Posted
  • Author
Posted (edited)

The first boot, following a shutdown, produced the following results/outputs (BTW, eth1 is DOWN):

 

demsg (both as user and root) gave:

bash: demsg: command not found

 

then:

[root@localhost bin]# ifconfig

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:719 errors:0 dropped:0 overruns:0 frame:0
	  TX packets:719 errors:0 dropped:0 overruns:0 carrier:0
	  collisions:0 txqueuelen:0
	  RX bytes:54898 (53.6 KiB)  TX bytes:54898 (53.6 KiB)

 

/etc/sysconfig/network-scripts/ifcfg-eth1 contained:

DEVICE=eth1
BOOTPROTO=dhcp
ONBOOT=yes
HWADDR=00:00:39:4a:74:8d
METRIC=10
MII_NOT_SUPPORTED=no
USERCTL=yes
IPV6INIT=no
IPV6TO4INIT=no
PEERDNS=yes
DHCP_CLIENT=dhclient
NEEDHOSTNAME=yes
PEERDNS=yes
PEERYP=no
PEERNTPD=no

 

I then restarted the machine, which produced (eth1 is now UP):

bash: demsg: command not found (as above)

 

but this time:

[root@localhost bin]# ifconfig

eth0	  Link encap:Ethernet  HWaddr 00:02:2D:33:30:17
	  inet6 addr: fe80::202:2dff:fe33:3017/64 Scope:Link
	  UP 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:11 Base address:0x100

eth1	  Link encap:Ethernet  HWaddr 00:00:39:4A:74:8D
	  inet addr:192.168.1.100  Bcast:192.168.1.255  Mask:255.255.255.0
	  inet6 addr: fe80::200:39ff:fe4a:748d/64 Scope:Link
	  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
	  RX packets:352 errors:0 dropped:0 overruns:0 frame:0
	  TX packets:1092 errors:0 dropped:0 overruns:0 carrier:0
	  collisions:0 txqueuelen:1000
	  RX bytes:350733 (342.5 KiB)  TX bytes:69095 (67.4 KiB)
	  Interrupt:11

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:796 errors:0 dropped:0 overruns:0 frame:0
	  TX packets:796 errors:0 dropped:0 overruns:0 carrier:0
	  collisions:0 txqueuelen:0
	  RX bytes:60793 (59.3 KiB)  TX bytes:60793 (59.3 KiB)

 

/etc/sysconfig/network-scripts/ifcfg-eth1 had not changed (probably to be expected??).

 

One final section:

 

lsmod (following first boot):

Module				  Size  Used by
cpufreq_ondemand		5052  0 
cpufreq_conservative	 6116  0 
cpufreq_powersave	   1280  0 
speedstep_ich		   3756  0 
speedstep_lib		   3364  1 speedstep_ich
freq_table			  3460  1 speedstep_ich
raw					 6592  1 
md5					 3584  1 
ipv6				  234016  8 
snd_seq_dummy		   2532  0 
snd_seq_oss			31136  0 
snd_seq_midi_event	  5696  1 snd_seq_oss
snd_seq				46960  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device		  6828  3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss			48960  0 
snd_mixer_oss		  16896  1 snd_pcm_oss
snd_intel8x0		   29408  3 
snd_ac97_codec		 83900  1 snd_intel8x0
snd_pcm				79784  4 snd_pcm_oss,snd_intel8x0,snd_ac97_codec
snd_timer			  20548  3 snd_seq,snd_pcm
snd_page_alloc		  8392  2 snd_intel8x0,snd_pcm
snd					46116  13 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_intel8x0,snd_ac
97_codec,snd_pcm,snd_timer
soundcore			   7008  1 snd
parport_pc			 32612  1 
lp					 10024  0 
parport				31976  2 parport_pc,lp
ipt_IFWLOG			  2788  1 
ipt_psd				43428  1 
ip_set_iptree		   5544  2 
ipt_REJECT			  4256  4 
ipt_LOG				 6272  7 
ipt_state			   1312  12 
ipt_pkttype			 1184  4 
ipt_set				 1920  2 
ipt_CONNMARK			1696  0 
ipt_MARK				1984  0 
ipt_ROUTE			   4260  0 
ipt_connmark			1216  0 
ipt_owner			   2432  0 
ipt_recent			  9292  0 
ipt_iprange			 1312  0 
ipt_physdev			 1744  0 
ipt_multiport		   2112  0 
ipt_conntrack		   1792  0 
iptable_mangle		  2016  0 
ip_set_portmap		  3840  0 
ip_set_macipmap		 3780  0 
ip_set_ipmap			3872  0 
ip_set_iphash		   5924  0 
ip_set				 18876  11 ip_set_iptree,ipt_set,ip_set_portmap,ip_set_macipmap,ip_set_ipmap,ip_set_iphash
ip_nat_irc			  1824  0 
ip_nat_tftp			 1216  0 
ip_nat_ftp			  2560  0 
iptable_nat			20212  3 ip_nat_irc,ip_nat_tftp,ip_nat_ftp
ip_conntrack_irc	   70352  1 ip_nat_irc
ip_conntrack_tftp	   3088  1 ip_nat_tftp
ip_conntrack_ftp	   71408  1 ip_nat_ftp
ip_conntrack		   40824  9 ipt_state,ipt_conntrack,ip_nat_irc,ip_nat_tftp,ip_nat_ftp,iptable_nat,ip_conntra
ck_irc,ip_conntrack_tftp,ip_conntrack_ftp
iptable_filter		  2080  1 
ip_tables			  20416  20 ipt_IFWLOG,ipt_psd,ipt_REJECT,ipt_LOG,ipt_state,ipt_pkttype,ipt_set,ipt_CONNMARK
,ipt_MARK,ipt_ROUTE,ipt_connmark,ipt_owner,ipt_recent,ipt_iprange,ipt_physdev,ip
t
_multiport,ipt_conntrack,iptable_mangle,iptable_nat,iptable_filter
af_packet			  16392  0 

***************************************at this point the order is different...
serial_cs			   7720  1 
eepro100			   27184  0 
mii					 4704  1 eepro100
floppy				 55444  0 
***************************************... up to here, then everything is again the same

orinoco_cs			  6472  1 
orinoco				39376  1 orinoco_cs
hermes				  8256  2 orinoco_cs,orinoco
pcmcia				 20648  8 serial_cs,orinoco_cs
yenta_socket		   20328  5 
rsrc_nonstatic		 11200  1 yenta_socket
pcmcia_core			43300  5 serial_cs,orinoco_cs,pcmcia,yenta_socket,rsrc_nonstatic
ide_cd				 37988  0 
loop				   14504  0 
nls_iso8859_1		   3680  2 
nls_cp850			   4480  2 
vfat				   10592  2 
fat					45980  1 vfat
supermount			 31956  1 
intel_agp			  20636  1 
agpgart				29032  1 intel_agp
hw_random			   4244  0 
nvram				   7400  0 
toshiba				 4024  0 
usblp				  10976  0 
tsdev				   5984  0 
uhci_hcd			   29136  0 
usbcore			   108348  3 usblp,uhci_hcd
evdev				   7648  0 
ext3				  124744  1 
jbd					48568  1 ext3

 

here are the differences(these modules are in a different order;is this significant??):

af_packet			  16392  2
eepro100			   27184  0
mii					 4704  1 eepro100
floppy				 55444  0
serial_cs			   7720  1
orinoco_cs			  6472  1

 

Sorry for the mass of data, but I hope that it helps

Edited by satelliteuser083
Link to comment
Share on other sites
pmpatrick Mandriva Guru

pmpatrick

Posted
Posted

My bad, that was a typo; the command should be "dmesg"not "demsg".

However, I dont think you need to look there as it appears you have two nics battling it out, eth0 and eth1. One is a standard nic using eepro100 module and the other I think is using the orinoco module which is for wireless nics.

Does any of this make sense to you re your hardware?

I think we want to stop the orinoco driver from loading. You may also have another network confguration file, ifcfg-eth0 along with ifcfg-eth1.

 

Drivers are generally loaded from one of two confguration files, /etc/modprobe.conf and /etc/modprobe.preload. Modprobe.conf is the more likely one. Open the file and look for a line that starts with:

 

alias eth0

 

and put a # in front of that line to comment it out. That will stop the orinoco driver from loading. If you want, you can post the entire modprobe.conf file. Try rebooting and run ifconfig again. That will tell you what interfaces are there.

The problem is that the first network interface loaded is designated eth0 and the system may insist on designating the former eepro eth1 interface as eth0. Post back with your results and we'll try to sort it out. If you're not using the wireless orinico nic in linux, it shouldn't be any problem to properly configure your regular nic.

Link to comment
Share on other sites
satelliteuser083 Awesome

satelliteuser083

Posted
  • Author
Posted (edited)

Thanks. I checked both /etc/modprobe.conf and /etc/modprobe.preload, there's no mention of eth0, so its driver would appear to be loaded (or at least an attempt made) somewhere else. I also checked /etc/modprobe.devfs, no mention there of either eth0 or eth1.

 

Interestingly, there is also no mention of the wireless-connection (eth0) in MCC->Hardware, although this nic IS offered for setup in MCC->Network&Internet->New Connection->Wireless Connection (eth0: Intersil PRISM2 11 Mbps). :unsure:

 

Here are the relevant parts of dmesg.txt (as suggested) for both situations, eth1 DOWN and eth1 UP (simply searching on 'eth').

 

eth1 DOWN:

Linux version 2.6.12-12mdk (apatard@n1.mandriva.com) (gcc version 4.0.1 (4.0.1-5mdk for Mandriva Linux release 2006.0)) #1 Fri Sep 9 18:15:22 CEST 2005

eth0: OEM i82557/i82558 10/100 Ethernet, 00:00:39:4A:74:8D, IRQ 11.
 Board assembly 000000-000, Physical connectors present: RJ45
 Primary interface chip i82555 PHY #1.
 General self-test: passed.
 Serial sub-system self-test: passed.
 Internal registers self-test: passed.
 ROM checksum self-test: passed (0x04f4518b).
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
NET: Registered protocol family 17
eth1: no IPv6 routers present

 

and eth1 UP

Linux version 2.6.12-12mdk (apatard@n1.mandriva.com) (gcc version 4.0.1 (4.0.1-5mdk for Mandriva Linux release 2006.0)) #1 Fri Sep 9 18:15:22 CEST 2005

orinoco 0.15rc2STA (David Gibson <hermes@gibson.dropbear.id.au>, Pavel Roskin <proski@gnu.org>, et al)
orinoco_cs 0.15rc2STA (David Gibson <hermes@gibson.dropbear.id.au>, Pavel Roskin <proski@gnu.org>, et al)
eth0: Hardware identity 0005:0002:0001:0002
eth0: Station identity  001f:0001:0006:000e
eth0: Firmware determined as Lucent/Agere 6.14
eth0: Ad-hoc demo mode supported
eth0: IEEE standard IBSS ad-hoc mode supported
eth0: WEP supported, 104-bit key
eth0: MAC address 00:02:2D:33:30:17
eth0: Station name "HERMES I"
eth0: ready
eth0: index 0x01: Vcc 3.3, irq 11, io 0x0100-0x013f
cs: memory probe 0xa0000000-0xa0ffffff: excluding 0xa0000000-0xa00fffff
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.html
eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw@saw.sw.com.sg> and others
PCI: Found IRQ 11 for device 0000:02:08.0
eth1: OEM i82557/i82558 10/100 Ethernet, 00:00:39:4A:74:8D, IRQ 11.
 Board assembly 000000-000, Physical connectors present: RJ45
 Primary interface chip i82555 PHY #1.
 General self-test: passed.
 Serial sub-system self-test: passed.
 Internal registers self-test: passed.
 ROM checksum self-test: passed (0x04f4518b).
NET: Registered protocol family 17
eth0: New link status: Disconnected (0002)
ip_tables: (C) 2000-2002 Netfilter core team
ip_conntrack version 2.1 (4091 buckets, 32728 max) - 260 bytes per conntrack
ipt_recent v0.3.1: Stephen Frost <sfrost@snowman.net>.  http://snowman.net/projects/ipt_recent/
netfilter PSD loaded - (c) astaro AG
IFWLOG: register target
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
parport0: irq 7 detected
lp0: using parport0 (polling).
lp0: console ready
PCI: Found IRQ 11 for device 0000:00:1f.5
PCI: Sharing IRQ 11 with 0000:00:1f.6
PCI: Sharing IRQ 11 with 0000:02:0d.1
PCI: Setting latency timer of device 0000:00:1f.5 to 64
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=192.168.1.255 LEN=138 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=631 DPT=631 LEN=118 
intel8x0_measure_ac97_clock: measured 50251 usecs
intel8x0: clocking to 48000
hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hdc: drive_cmd: error=0x04 { AbortedCommand }
ide: failed opcode was: 0xec
hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hdc: drive_cmd: error=0x04 { AbortedCommand }
ide: failed opcode was: 0xec
hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hdc: drive_cmd: error=0x04 { AbortedCommand }
ide: failed opcode was: 0xec
NET: Registered protocol family 10
Disabled Privacy Extensions on device c03c5760(lo)
IPv6 over IPv4 tunneling driver
eth1: freeing mc frame.
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=77 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=57 
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=77 TOS=0x00 PREC=0x00 TTL=255 ID=1 DF PROTO=UDP SPT=5353 DPT=5353 LEN=57 
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=77 TOS=0x00 PREC=0x00 TTL=255 ID=2 DF PROTO=UDP SPT=5353 DPT=5353 LEN=57 
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=111 TOS=0x00 PREC=0x00 TTL=255 ID=3 DF PROTO=UDP SPT=5353 DPT=5353 LEN=91 
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=111 TOS=0x00 PREC=0x00 TTL=255 ID=4 DF PROTO=UDP SPT=5353 DPT=5353 LEN=91 
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=224.0.0.251 LEN=111 TOS=0x00 PREC=0x00 TTL=255 ID=5 DF PROTO=UDP SPT=5353 DPT=5353 LEN=91 
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=192.168.1.255 LEN=44 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=32770 DPT=7741 LEN=24 
spurious 8259A interrupt: IRQ7.
eth1: freeing mc frame.
eth0: no IPv6 routers present

eth1: no IPv6 routers present
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=192.168.1.255 LEN=138 TOS=0x00 PREC=0x00 TTL=64 ID=1 DF PROTO=UDP SPT=631 DPT=631 LEN=118 
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=192.168.1.255 LEN=138 TOS=0x00 PREC=0x00 TTL=64 ID=2 DF PROTO=UDP SPT=631 DPT=631 LEN=118 
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=192.168.1.255 LEN=138 TOS=0x00 PREC=0x00 TTL=64 ID=3 DF PROTO=UDP SPT=631 DPT=631 LEN=118 
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=192.168.1.255 LEN=138 TOS=0x00 PREC=0x00 TTL=64 ID=4 DF PROTO=UDP SPT=631 DPT=631 LEN=118 
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=192.168.1.255 LEN=138 TOS=0x00 PREC=0x00 TTL=64 ID=5 DF PROTO=UDP SPT=631 DPT=631 LEN=118 
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=192.168.1.255 LEN=138 TOS=0x00 PREC=0x00 TTL=64 ID=6 DF PROTO=UDP SPT=631 DPT=631 LEN=118 
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=192.168.1.255 LEN=138 TOS=0x00 PREC=0x00 TTL=64 ID=7 DF PROTO=UDP SPT=631 DPT=631 LEN=118 
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=192.168.1.255 LEN=138 TOS=0x00 PREC=0x00 TTL=64 ID=8 DF PROTO=UDP SPT=631 DPT=631 LEN=118 
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=192.168.1.255 LEN=138 TOS=0x00 PREC=0x00 TTL=64 ID=9 DF PROTO=UDP SPT=631 DPT=631 LEN=118 
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=192.168.1.255 LEN=138 TOS=0x00 PREC=0x00 TTL=64 ID=10 DF PROTO=UDP SPT=631 DPT=631 LEN=118 
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=192.168.1.255 LEN=44 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=32778 DPT=7741 LEN=24 
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=192.168.1.0 LEN=28 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=ICMP TYPE=8 CODE=0 ID=7449 SEQ=0 
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=192.168.1.255 LEN=28 TOS=0x00 PREC=0x00 TTL=64 ID=255 DF PROTO=ICMP TYPE=8 CODE=0 ID=7449 SEQ=0 
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=192.168.1.255 LEN=138 TOS=0x00 PREC=0x00 TTL=64 ID=11 DF PROTO=UDP SPT=631 DPT=631 LEN=118 
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=192.168.1.255 LEN=138 TOS=0x00 PREC=0x00 TTL=64 ID=12 DF PROTO=UDP SPT=631 DPT=631 LEN=118 
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=192.168.1.255 LEN=138 TOS=0x00 PREC=0x00 TTL=64 ID=13 DF PROTO=UDP SPT=631 DPT=631 LEN=118 
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=192.168.1.255 LEN=138 TOS=0x00 PREC=0x00 TTL=64 ID=14 DF PROTO=UDP SPT=631 DPT=631 LEN=118 
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=192.168.1.255 LEN=138 TOS=0x00 PREC=0x00 TTL=64 ID=15 DF PROTO=UDP SPT=631 DPT=631 LEN=118 
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=192.168.1.255 LEN=138 TOS=0x00 PREC=0x00 TTL=64 ID=16 DF PROTO=UDP SPT=631 DPT=631 LEN=118 
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=192.168.1.255 LEN=138 TOS=0x00 PREC=0x00 TTL=64 ID=17 DF PROTO=UDP SPT=631 DPT=631 LEN=118 
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=192.168.1.255 LEN=138 TOS=0x00 PREC=0x00 TTL=64 ID=18 DF PROTO=UDP SPT=631 DPT=631 LEN=118 
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=192.168.1.255 LEN=138 TOS=0x00 PREC=0x00 TTL=64 ID=19 DF PROTO=UDP SPT=631 DPT=631 LEN=118 
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=192.168.1.255 LEN=138 TOS=0x00 PREC=0x00 TTL=64 ID=20 DF PROTO=UDP SPT=631 DPT=631 LEN=118 
eth1: no IPv6 routers present
eth1: freeing mc frame.
Shorewall:net2all:DROP:IN=eth1 OUT= MAC= SRC=192.168.1.100 DST=192.168.1.255 LEN=138 TOS=0x00 PREC=0x00 TTL=64 ID=21 DF PROTO=UDP SPT=631 DPT=631 LEN=118 
eth1: no IPv6 routers present

 

Could the firewall be having some effect or another on this?

 

BTW, in linux noapic nolapic acpi=off, what do the arguments noapic and nolapic mean?

 

Again, many thanks.

Edited by satelliteuser083
Link to comment
Share on other sites
pmpatrick Mandriva Guru

pmpatrick

Posted
Posted (edited)

This is puzzling. Please describe your hardware. Without knowing that, I'm just playing twenty questions. In particular, do you have two network cards, one wireless and the other a standard nic and what brand are they? What steps have you taken to configure these devices? Is this a laptop and is either card a pcmcia card, your lsmod output would indicate that this is a laptop with a pcmcia slot? Driver modules are loaded differently for pcmcia card devices.

I need some basic information on your hardware setup before I can help you further.

 

At this point, I'm inclined to try forcing the orinoco driver to load from moprobe.conf or modprobe.preload since everything seems to work OK when it's loaded first. Please post both those files. Your dmesg output shows that your eepro card is assigned eth0 when the orinoco driver isn't loaded and the network doesn't come up and eth1 when the orinoco driver loads first with the wireless card being assigned eth0. It's obviously a timing issue but I have no idea at this point where the orinoco driver is loading from. Hopefully, some info about your hardware will help.

 

We could try testing by removing both modules and reloading them in proper order when the network doesn't come up and see if that helps. You would do that with:

 

# rmmod orinoco

# rmmod eepro100

# modprobe orinoco

# modprobe eepro100

 

Then try and bring the network up with:

 

# ifup eth1

 

The boot codes I gave you are just that. The net effect of those boot codes is to disable acpi and apic or portions of it during the boot process. acpi/apic has been known to cause problems with certain hardware configurations. The noapic nolapic acpi=off can be thought of as a magical incantation to accompolish that.

 

apic = Advanced Programmable Interrupt Controller

acpi = Advanced Configuration and Power Interface

lapic = local apic

Edited by pmpatrick
Link to comment
Share on other sites
satelliteuser083 Awesome

satelliteuser083

Posted
  • Author
Posted

Yes, I have two built-in nics (as described by MCC->Network&Internet) [bTW, this is the situation with eth1 UP]:

eth1: Intel Corp EtherExpress PRO/100
Vendor: Intel Corp.
Description: eEtherExpress PRO/100
Media class: NETWORK_ETHERNET
Module name: eepro100
Mac Address: 00:00:39:4a:74:8d
Bus: PCI
Location on the bus: 2

eth0: Intersil PRISM2 11 Mbps Wireless Adapte
Vendor: Intersil PRISM2 11 Mbps Wireless Adapter
Description: Intersil PRISM2 11 Mbps Wireless Adapter
Media class: -
Module name: orinoco_cs
Mac Address: 00:02:2d:33:30:17
Bus: -
Location on the bus: -

In MCC-> Hardware, eth1 is described as:

Identification
Vendor: Intel Corp.
Description: EtherExpress PRO/100
Media class: NETWORK_ETHERNET

Connection
Bus: PCI
Bus PCI #: 2
PCI device #: 8
PCI function #: 0
Vendor ID: 32902
Device ID: 9289
Sub vendor ID: 32902
Sub device ID: 12307

Misc
Module: eepro100

and eth0 as:

Identification
Vendor: Intersil PRISM2 11 Mbps Wireless Adapter

Description:

Misc
Old device file: /dev/eth0
Module: orinoco_cs

I deleted eth0 (with MCC) and set eth1 up as follows:

Tab TCP/IP:
Protocol: static (Not DHCP)
IP address: 192.168.1.100
Netmask: 255.255.255.0
Gateway: 192.168.1.1 (this is the default IP of the router)
DNS Servers: 194.168.4.100 and 194.168.8.100
Search Domain: none

Tab DHCP: (all blank (grey))
# DHCP client: dhclient
# Assign host...DHCP address (selected)
# DHCP Host Name: blank
# DHCP timeout: blank
# Get DNS...DHCP: (selected)
# Get YP...DHCP (deselected)
# Get NTPD...DHCP (deselected)

Tab Options:
Start at boot (selected)
Track network card id (selected)
Network Hotplugging (deselected)

The machine is a laptop, a Toshiba Satellite Pro 4600; it has two pcmcia slots, one of which contains an IBM modem-card, Model XJ1560 FRU:04K0054).

 

PCMCIA Controller-info (from MCC->Hardware) is:

Identification
Vendor: Texas Instruments
Description: PCI1410 PC card Cardbus Controller
Media class: BRIDGE_CARDBUS

Connection
Bus: PCI
Bus PCI #: 2
PCI device #: 12
PCI function #: 0
Vendor ID: 4172
Device ID: 44112
Sub vendor ID: 16384
Sub device ID: 0

Misc
Module: yenta_socket

and [two sockets].....

Identification
Vendor: Toshiba
Description: ToPIC95 PCI to Cardbus Bridge with ZV Support
Media class: BRIDGE_CARDBUS

Connection
Bus: PCI
Bus PCI #: 2
PCI device #: 1
PCI function #: 0 [1]
Vendor ID: 4473
Device ID: 1559
Sub vendor ID: 18432 [20480]
Sub device ID: 0

Misc
Module: yenta_socket

The result of your rmmod/modprobe/ifup sequence was:

[root@localhost bin]# rmmod orinoco_cs
ERROR: Module orinoco_cs is in use
[root@localhost bin]# rmmod orinoco
ERROR: Module orinoco is in use by orinoco_cs
[root@localhost bin]# rmmod eepro100
[root@localhost bin]# modprobe orinoco
[root@localhost bin]# modprobe eepro100
[root@localhost bin]# ifup eth1

but it had no effect, eth1 stayed DOWN.

 

This is becoming a saga; many thanks for your help (and time).

 

One other thing; with all this starting/restarting, I've noticed that the machine doesn't always want to do just that (perhaps it's on the blink :unsure: ). Mostly it WILL turn-off or restart (as required) the SECOND time, occasionally it refuses to do it at all and I have to resort to a RESET. Is there any key-combination which will bring me to the log-in screen, because that ALWAYS works. Thanks.

Link to comment
Share on other sites
pmpatrick Mandriva Guru

pmpatrick

Posted
Posted (edited)

For a keyboard sequence, if you do Ctrl-Alt-Backspace, the X server will be killed and you automatically go back to the login screen. If X is locked up pretty good, sometimes that won't work. You can then try doing CtrlAlt-F1 or F2 which will take you to a virtual terminal(no X) with a command line login. Login as root and run "reboot" from the command line.

 

It seems to me that on a cold boot, your wireless card is simply not detected for some reason or another. eth0 is assigned to the first network device that your system tries to bring up and the orinoco driver is associated with that interface so that driver is loaded and associated with your intel nic which won't make it function and no other nic is detected. Later in the boot process the eepro driver is loaded but too late. It could be hardware related in that the wireless card needs time to "warm up" in order to be detected which would be the case on reboot.

 

If that's the case, removing the modules and reloading may work. A lot of times when you modprobe a module, it loads not only the module you designate but also some some subsidiary helper modules as well that it depends on. When you try to rmmod the module, it won't let you do it until you remove the helper modules first. That's the reason for the error message. If you did rmmod orinoco_cs followed by rmmod orinoco, that should have worked. But there may be other submodules associated with orinico and you have to do them in the right order. You can tell all the modules in the orinoco family by doing:

 

# lsmod | grep orinoco

 

 

If your not using the wireless nic, here's what I would suggest. Remove the eth0 interface like you did in mcc. Remove the eth1 interface in mcc. After doing that, make sure ifcfg-eth0 and ifcfg-eth1 have been deleted in /etc/sysconfig/network-scripts; if not, manually delete them. Sometimes mcc forgets to do this when you have multiple nics. Reboot and make sure the orinoco and eepro drivers are no longer loading. Check with:

 

# lsmod | grep orinoco

# lsmod | grep eepro

 

There should be no output with either command. Go back into mcc and select the option to setup a new interface>Cable or Lan. You should then come to a screen where you can select your standard intel nic to be associated with eth0 which will be the default selection. If it tries to force you to use the prism wireless card on eth0, tick the manual box and select eepro100 driver and proceed through the setup steps selecting dhcp. See if the network comes up Ok and see if it survives a reboot.

Edited by pmpatrick
Link to comment
Share on other sites
satelliteuser083 Awesome

satelliteuser083

Posted
  • Author
Posted

Still can't get eepro to go UP the first time, but at least it now sits on eth0. This is what I did:

I deleted ifcfg-eth0, ifcfg-eth1 and ifcfg-sit0 from /etc/sysconfig/network-scripts, then set-up (cable) eth0 in MCC, using 'manually load a driver' . I then restarted the session, as advised; eth0 didn't come UP but at least eepro was still eth0. Interestingly enough, although I definitely DID set gateway = 192.168.1.1, NETWORK=192.168.1.0 in ifcfg-eth0 (are NETWORK and gateway the same??):

DEVICE=eth0
BOOTPROTO=static
IPADDR=192.168.1.100
NETMASK=255.255.255.0
NETWORK=192.168.1.0
BROADCAST=192.168.1.255
ONBOOT=yes
HWADDR=00:00:39:4a:74:8d
METRIC=10
MII_NOT_SUPPORTED=yes
USERCTL=yes
IPV6INIT=no
IPV6TO4INIT=no
PEERDNS=yes
NETMASK=255.255.255.0
IPADDR=192.168.1.100

While I've been typing this I've just noticed that eth0 has come UP (on the icon, anyway), but it clearly IS'NT UP, because neither skype nor konqueror has access to the net. Strange :unsure: .

 

OK, I'm completely lost, perhaps I should just admit that the beast has beaten me. I SHUTDOWN the system (seeing that eth0 actually WASN'T UP), started it again and eepro now sits on eth1 (yes, ONE!) and is (what else?) DOWN. WOE is going on? /etc/modprobe.conf contains:

alias sound-slot-0 snd-intel8x0
install usb-interface /sbin/modprobe uhci-hcd; /bin/true
remove snd-intel8x0 /sbin/modprobe -r snd-pcm-oss; /sbin/modprobe --first-time -r --ignore-remove snd-intel8x0
install snd-intel8x0 /sbin/modprobe --first-time --ignore-install snd-intel8x0 && { /sbin/modprobe snd-pcm-oss; /bin/true; }
remove i810_audio /sbin/modprobe --first-time -r --ignore-remove i810_audio
install i810_audio /sbin/modprobe --first-time --ignore-install i810_audio
alias eth0 eepro10

I haven't got any more time to spare for this at the moment, so I'll give it a rest. Many thanks, anyway, to all who contributed, for your help ;) .

Link to comment
Share on other sites
  • 4 months later...
satelliteuser083 Awesome

satelliteuser083

Posted
  • Author
Posted

Well, I've (apparently) solved the problem :unsure: . My system - mva2006 - crashed one day and did an automatic restart; lo and behold, the network was UP on completion of boot. So I experimented a bit and came up with the following solution: when I want to SHUTDOWN I perform a RESTART with a blank floppy in the drive (boot sequence is floppy/HD/CD); when the machine attempts to restart and BIOS complains that there is no OS to boot into, I switch the machine off. When the machine is next started (floppy removed) the network is always UP :thumbs: . It may not be an ideal way of getting around the previous situation, but it seems to be working (the last 4 months, anyway).

 

Hope this may help someone out there.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
 Share
Go to topic listing
×
×
  • Create New...