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.
|
 |
06-04-2005, 01:11 PM
|
#1
|
LQ Newbie
Registered: Jun 2005
Distribution: mepis, mdk
Posts: 5
Rep:
|
command line problem
After a very short idle time when at the command line (tty) either $ or #, I get "ABORTED IN=eth) OUT=MAC=OO:6:7b ............... and is repeated over and over until I type RET, which brings me back to the $ or # prompt. This does not happen in Konsole. Not major but very annoying. Can someone shed some light on my little problem? Thanks in advance
|
|
|
06-04-2005, 01:17 PM
|
#2
|
Member
Registered: Nov 2004
Distribution: Mepis
Posts: 84
Rep:
|
I think that's from firewall (Guarddog), see if you can turn the log off.
|
|
|
06-04-2005, 01:27 PM
|
#3
|
LQ Newbie
Registered: Jun 2005
Distribution: mepis, mdk
Posts: 5
Original Poster
Rep:
|
Thanks, how would I go about turning the log off?
|
|
|
06-04-2005, 01:41 PM
|
#4
|
Member
Registered: Nov 2004
Distribution: Mepis
Posts: 84
Rep:
|
start guarddog (from kmenu or type guarddog in "run command")
there's a Logging tab, check over there to have logging turned off.
|
|
|
06-04-2005, 01:59 PM
|
#5
|
LQ Newbie
Registered: Jun 2005
Distribution: mepis, mdk
Posts: 5
Original Poster
Rep:
|
Guess I'm thick as a board , AdrianTM. I have the logging window up but still don't see anywhere to turn logging off.
|
|
|
06-04-2005, 02:18 PM
|
#6
|
Member
Registered: Nov 2004
Distribution: Mepis
Posts: 84
Rep:
|
then maybe it's something else....
|
|
|
06-04-2005, 02:32 PM
|
#7
|
Senior Member
Registered: Dec 2004
Location: Olympia, WA, USA
Distribution: Fedora, (K)Ubuntu
Posts: 4,187
|
It's an error message from your network, telling you that your ethernet controler (eth) cannot connect to the device with the specified MAC.
I'd suspect that you've recently replaced your controler, and didn't remove the older connection. (Just a guess.)
Anyhow, review your network connnection settings -- you've got something wrong there.
Oh, the message is displayed on the console, but should also be in the log files in /var/logs/.
|
|
|
06-05-2005, 12:25 AM
|
#8
|
LQ Newbie
Registered: Jun 2005
Distribution: mepis, mdk
Posts: 5
Original Poster
Rep:
|
I'm still dead in the water. No controller replaced .... This is a new
MEPIS 3.3.1 install on a new pentium IV, ADSL. Network Interfaces....
STATUS ...Network status lo ip: 127.0.0.1 eth0 ip: 192.168.165
MISC ... Start lo at system boot
Configure DNS....use DHCP for DNS
eth0.....Configure eth0 Network Start at system boot
$ dmesg | less, I get
INDOW=97 Res=0x00 RST URGP=0, there after I get the ABORTED
IN=etho OUT=MAC=00:06:76 ...... repeated many times. Is this any
help in pinning down my problem? Maybe it would be best if I
reinstall and hope for a fix?
|
|
|
06-05-2005, 12:40 AM
|
#9
|
Member
Registered: Nov 2004
Distribution: Mepis
Posts: 84
Rep:
|
check this out
I don't think reinstalling would solve anything. Try to turn Guarddog completly off to see if that's the cause.
I personally don't use Guarddog, one of the first thing to do was to remove it and install Firestarter which I find easier to understand. Also I don't think this is a capital problem.
|
|
|
06-05-2005, 01:18 AM
|
#10
|
LQ Newbie
Registered: Jun 2005
Distribution: mepis, mdk
Posts: 5
Original Poster
Rep:
|
Ok Adrian, I'm going to go with Firestarter. Thanks for your time. It's much appreciated.
Cheers
|
|
|
All times are GMT -5. The time now is 01:11 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
|
|