MEPIS This forum is for the discussion of MEPIS Linux. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
11-29-2006, 02:39 PM
|
#1
|
Member
Registered: Jun 2006
Location: Oz
Distribution: Mandriva 10.0,10.1,10.2,2006,Mepis 6.0,Opensuse10.2,Puppy 2.14
Posts: 250
Rep:
|
Problem affecting connection -Reboot needed
Anyone had a similar problem?
I have a connection problem with the internet and local network. Either they both connect or they both do not.
It sometimes connects straight away , sometimes on the second boot , sometimes the third or fourth time I boot my computer. Never any more
My setup is, A linux machine and a windows machine on a separate network card (eth1) and the Linux machine is the gateway that connects to the main server through Eth0
Anyone got any sugestions please? I've fiddled inside Guarddog quite a bit to try and fix.this Nothing seems to affect the results and it is variable between connect first time or if not reboot up to 3 times more. Its not a consistent number or increment that I can recognise anyway.
Last edited by tytower; 02-20-2007 at 04:06 PM.
|
|
|
12-03-2006, 09:52 AM
|
#2
|
Member
Registered: Mar 2006
Distribution: Lilidog!
Posts: 347
Rep:
|
To find out if it is Guarddog, just shut it down for a few trial runs, and see if everything works. do this in turn with every application in the direct line, and one you find out what is causing the problem, we can work on finding a more direct solution.
|
|
|
12-20-2006, 03:08 PM
|
#3
|
Member
Registered: Jun 2006
Location: Oz
Distribution: Mandriva 10.0,10.1,10.2,2006,Mepis 6.0,Opensuse10.2,Puppy 2.14
Posts: 250
Original Poster
Rep:
|
Did the above but unsuccessful
I noticed in the kernal log that errors were reported as follows
Its a lengthy file so Ive taken out what did not seem inportant.
Note the errors at the end seem to be continuing to be reported and this is with the network properly connected
Lines 7 and 8 concern me . I know the AC97 driver isn't loaded as mu board is one with built in sound and the disk for installation of the driver is only in windows .exe format The sound however works fine anyway and there are no other sound cards installed
Can anyone help with explanations?
Dec 21 06:55:13 localhost kernel: [ 43.413486] eth0: SiS 900 PCI Fast Ethernet at 0xd400, IRQ 3, 00:0a:e6:13:51:86.
Dec 21 06:55:13 localhost kernel: [ 43.533868] 8139too Fast Ethernet driver 0.9.27
Dec 21 06:55:13 localhost kernel: [ 44.329324] eth1: RealTek RTL8139 at 0xcf884f00, 00:40:f4:98:8d:c5, IRQ 4
Dec 21 06:55:13 localhost kernel: [ 44.329330] eth1: Identified 8139 chip type 'RTL-8100B/8139D'
Dec 21 06:55:13 localhost kernel: [ 44.371822] 8139cp: 10/100 PCI Ethernet driver v1.2 (Mar 22, 2004)
Dec 21 06:55:13 localhost kernel: [ 46.448289] eth1: link up, 100Mbps, full-duplex, lpa 0x45E1
Dec 21 06:55:13 localhost kernel: [ 47.544459] MC'97 1 converters and GPIO not ready (0x1)
Dec 21 06:55:13 localhost kernel: [ 47.824158] ac97 codec read TIMEOUT [0x54/0x1c0d4]!!!
Dec 21 06:55:13 localhost kernel: [ 49.853777] cdrom: open failed.
Dec 21 06:55:13 localhost kernel: [ 51.138686] eth0: Media Link On 100mbps half-duplex
Dec 21 06:55:13 localhost kernel: [ 57.130811] eth0: Media Link Off
Dec 21 06:55:22 localhost kernel: [ 67.118382] eth0: Media Link On 100mbps half-duplex
Dec 21 06:55:59 localhost kernel: [ 103.367953] 10.16.26.9 sent an invalid ICMP type 3, code 0 error to a broadcast: 10.16.26.255 on eth0
Dec 21 06:56:30 localhost kernel: [ 134.325949] 10.16.26.9 sent an invalid ICMP type 3, code 0 error to a broadcast: 10.16.26.255 on eth0
Dec 21 06:57:01 localhost kernel: [ 165.286730] 10.16.26.9 sent an invalid ICMP type 3, code 0 error to a broadcast: 10.16.26.255 on eth0
Dec 21 06:57:32 localhost kernel: [ 196.251114] 10.16.26.9 sent an invalid ICMP type 3, code 0 error to a broadcast: 10.16.26.255 on eth0
Dec 21 06:58:03 localhost kernel: [ 227.213509] 10.16.26.9 sent an invalid ICMP type 3, code 0 error to a broadcast: 10.16.26.255 on eth0
Dec 21 06:58:34 localhost kernel: [ 258.172673] 10.16.26.9 sent an invalid ICMP type 3, code 0 error to a broadcast: 10.16.26.255 on eth0
Dec 21 06:58:40 localhost kernel: [ 265.067848] ABORTED IN=eth0 OUT= MAC=00:0a:e6:13:51:86:00:a0:ac:06:a2:56:08:00 SRC=10.16.26.9 DST=10.16.26.10 LEN=40 TOS=0x00 PREC=0x00 TTL=63 ID=95 PROTO=TCP SPT=9877 DPT=3549 SEQ=1792 ACK=218368364 WINDOW=0 RES=0x00 RST URGP=0
Dec 21 06:59:05 localhost kernel: [ 289.132790] 10.16.26.9 sent an invalid ICMP type 3, code 0 error to a broadcast: 10.16.26.255 on eth0
Dec 21 06:59:36 localhost kernel: [ 320.095113] 10.16.26.9 sent an invalid ICMP type 3, code 0 error to a broadcast: 10.16.26.255 on eth0
Dec 21 07:00:07 localhost kernel: [ 351.054588] 10.16.26.9 sent an invalid ICMP type 3, code 0 error to a broadcast: 10.16.26.255 on eth0
Dec 21 07:00:38 localhost kernel: [ 382.026578] 10.16.26.9 sent an invalid ICMP type 3, code 0 error to a broadcast: 10.16.26.255 on eth0
Dec 21 07:01:06 localhost kernel: [ 410.888573] ABORTED IN=eth0 OUT= MAC=00:0a:e6:13:51:86:00:a0:ac:06:a2:56:08:00 SRC=10.16.26.9 DST=10.16.26.10 LEN=40 TOS=0x00 PREC=0x00 TTL=63 ID=1325 PROTO=TCP SPT=9877 DPT=5168 SEQ=29324 ACK=353247437 WINDOW=0 RES=0x00 RST URGP=0
Dec 21 07:01:07 localhost kernel: [ 411.887252] ABORTED IN=eth0 OUT= MAC=00:0a:e6:13:51:86:00:a0:ac:06:a2:56:08:00 SRC=10.16.26.9 DST=10.16.26.10 LEN=40 TOS=0x00 PREC=0x00 TTL=63 ID=1326 PROTO=TCP SPT=9877 DPT=5174 SEQ=2399 ACK=365674462 WINDOW=0 RES=0x00 RST URGP=0
Dec 21 07:01:09 localhost kernel: [ 412.988495] 10.16.26.9 sent an invalid ICMP type 3, code 0 error to a broadcast: 10.16.26.255 on eth0
Dec 21 07:01:40 localhost kernel: [ 443.948597] 10.16.26.9 sent an invalid ICMP type 3, code 0 error to a broadcast: 10.16.26.255 on eth0
Dec 21 07:02:11 localhost kernel: [ 474.940739] 10.16.26.9 sent an invalid ICMP type 3, code 0 error to a broadcast: 10.16.26.255 on eth0
Dec 21 07:02:23 localhost kernel: [ 487.419323] ABORTED IN=eth0 OUT= MAC=00:0a:e6:13:51:86:00:a0:ac:06:a2:56:08:00 SRC=10.16.26.9 DST=10.16.26.10 LEN=40 TOS=0x00 PREC=0x00 TTL=63 ID=1855 PROTO=TCP SPT=9877 DPT=5185 SEQ=1047 ACK=449333077 WINDOW=0 RES=0x00 RST URGP=0
Dec 21 07:02:23 localhost kernel: [ 487.419794] ABORTED IN=eth0 OUT= MAC=00:0a:e6:13:51:86:00:a0:ac:06:a2:56:08:00 SRC=10.16.26.9 DST=10.16.26.10 LEN=40 TOS=0x00 PREC=0x00 TTL=62 ID=1856 PROTO=TCP SPT=9877 DPT=5185 SEQ=1047 ACK=449333078 WINDOW=0 RES=0x00 RST URGP=0
Dec 21 07:02:23 localhost kernel: [ 487.430079] ABORTED IN=eth0 OUT= MAC=00:0a:e6:13:51:86:00:a0:ac:06:a2:56:08:00 SRC=10.16.26.9 DST=10.16.26.10 LEN=40 TOS=0x00 PREC=0x00 TTL=62 ID=1860 PROTO=TCP SPT=9877 DPT=5185 SEQ=1047 ACK=449333251 WINDOW=0 RES=0x00 RST URGP=0
Dec 21 07:02:23 localhost kernel: [ 487.433157] ABORTED IN=eth0 OUT= MAC=00:0a:e6:13:51:86:00:a0:ac:06:a2:56:08:00 SRC=10.16.26.9 DST=10.16.26.10 LEN=40 TOS=0x00 PREC=0x00 TTL=62 ID=1861 PROTO=TCP SPT=9877 DPT=5185 SEQ=1047 ACK=449333424 WINDOW=0 RES=0x00 RST URGP=0
Dec 21 07:02:23 localhost kernel: [ 487.433571] ABORTED IN=eth0 OUT= MAC=00:0a:e6:13:51:86:00:a0:ac:06:a2:56:08:00 SRC=10.16.26.9 DST=10.16.26.10 LEN=40 TOS=0x00 PREC=0x00 TTL=62 ID=1862 PROTO=TCP SPT=9877 DPT=5185 SEQ=1047 ACK=449333597 WINDOW=0 RES=0x00 RST URGP=0
Dec 21 07:02:23 localhost kernel: [ 487.434062] ABORTED IN=eth0 OUT= MAC=00:0a:e6:13:51:86:00:a0:ac:06:a2:56:08:00 SRC=10.16.26.9 DST=10.16.26.10 LEN=40 TOS=0x00 PREC=0x00 TTL=62 ID=1863 PROTO=TCP SPT=9877 DPT=5185 SEQ=1047 ACK=449333770 WINDOW=0 RES=0x00 RST URGP=0
Dec 21 07:02:23 localhost kernel: [ 487.434528] ABORTED IN=eth0 OUT= MAC=00:0a:e6:13:51:86:00:a0:ac:06:a2:56:08:00 SRC=10.16.26.9 DST=10.16.26.10 LEN=40 TOS=0x00 PREC=0x00 TTL=62 ID=1864 PROTO=TCP SPT=9877 DPT=5185 SEQ=1047 ACK=449333943 WINDOW=0 RES=0x00 RST URGP=0
Dec 21 07:02:42 localhost kernel: [ 505.902099] 10.16.26.9 sent an invalid ICMP type 3, code 0 error to a broadcast: 10.16.26.255 on eth0
Dec 21 07:03:13 localhost kernel: [ 536.863042] 10.16.26.9 sent an invalid ICMP type 3, code 0 error to a broadcast: 10.16.26.255 on eth0
Dec 21 07:03:44 localhost kernel: [ 567.822833] 10.16.26.9 sent an invalid ICMP type 3, code 0 error to a broadcast: 10.16.26.255 on eth0
Dec 21 07:04:15 localhost kernel: [ 598.789814] 10.16.26.9 sent an invalid ICMP type 3, code 0 error to a broadcast: 10.16.26.255 on eth0
Dec 21 07:04:46 localhost kernel: [ 629.747951] 10.16.26.9 sent an invalid ICMP type 3, code 0 error to a broadcast: 10.16.26.255 on eth0
Last edited by tytower; 12-20-2006 at 03:12 PM.
|
|
|
12-29-2006, 02:40 PM
|
#4
|
Member
Registered: Jun 2006
Location: Oz
Distribution: Mandriva 10.0,10.1,10.2,2006,Mepis 6.0,Opensuse10.2,Puppy 2.14
Posts: 250
Original Poster
Rep:
|
Still wasting 5,10 or 15 minutes with this each time I boot .
I have reinstalled about 3 times to no avail.
Guarddog on or off no diff and closing each application I could did not stop either
I installed Ubuntu 6.10 on another drive and it loads perfectly each time I start it
Got me beat
|
|
|
02-20-2007, 04:02 PM
|
#5
|
Member
Registered: Jun 2006
Location: Oz
Distribution: Mandriva 10.0,10.1,10.2,2006,Mepis 6.0,Opensuse10.2,Puppy 2.14
Posts: 250
Original Poster
Rep:
|
Well OK Iĺl close this now I suppose
Nobody else seems to have the same problem and nobody has an answer
I found that on reinstall number 4 that if I restarted the network from the Mepis tweaks it would often connect properly so it is a connection problem related to my machine and my distro
|
|
|
03-05-2007, 09:59 PM
|
#6
|
Member
Registered: Mar 2007
Location: canada
Distribution: SimplyMEPIS 6.5 final
Posts: 104
Rep:
|
Re: Problem affecting connection -Reboot needed
Using Ethernet (ADSL or PPPoE), to connect to the internet is relatively easy with Mepis, because when the distribution, begins to run, it tries to detect all the network interfaces in the computer.
So after the whole boot process has finished and you have passed the login screen (where you have entered the apropiate password), you will be looking at your desktop.
To finish setting up your internet connection, you must click: Kmenu > Internet > Connection > ADSL/PPPoE configuration, and follow the different screens, where you will be asked for some ISP information (like your username and password). Complete that section and a few seconds later, you will be surfing the Internet.
Here is a link to networking basics. Taken from the MEPIS wiki. http://www.mepis.org/docs/en/index.php/Networking
Here is some stuff you can type into knosole.
ifconfig - main configuration utility for network interfaces. Please read man ifconfig for full documentation.
ifup interface - bring up the specified interface. For example:
ifup eth0 - command that brings up the ethernet port
ifup wlan0 - command that brings up the wireless port
ifdown interface - the opposite of 'ifup' it brings down the interface.
iwconfig - wireless network connection utility. Check out man iwconfig for full documentation. Here are a few useful iwconfig commands (NOTE: your wireless card could be referred to by one of several names on your system. eth0, ath0, and wlan0 are common. Wherever you see one of those, substitute your adapter's name):
iwconfig - by itself, iwconfig will display your wireless status
iwconfig eth0 essid any - this command connects eth0 to any AP in range
iwconfig wlan0 essid foo - connects wlan0 to AP with essid "foo"
iwconfig eth0 key off - clears out the WEP key
iwconfig ath0 key 12345678901 - sets ath0's WEP key to 12345678901
iwlist - another wireless ethernet utility. See man iwlist for complete information. Some useful commands:
iwlist wlan0 scanning - shows properties of all wireless networks within range of wlan0.
iwlist ath0 bitrate - shows the current speed of communications on ath0.
Hopefully this will get you on the right track.
|
|
|
03-08-2007, 09:05 AM
|
#7
|
Member
Registered: Mar 2007
Location: canada
Distribution: SimplyMEPIS 6.5 final
Posts: 104
Rep:
|
Re; Nobody else seems to have the same problem
Quote:
Originally Posted by tytower
Well OK Iĺl close this now I suppose
Nobody else seems to have the same problem and nobody has an answer
I found that on reinstall number 4 that if I restarted the network from the Mepis tweaks it would often connect properly so it is a connection problem related to my machine and my distro
|
I should have asked you on my first post which version of MEPIS are you using? Let me know which version and maybe I can help a bit more.
|
|
|
All times are GMT -5. The time now is 11:19 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|