Page 3 of 3

Re: Mepis11 WIRED networking pooched

Posted: Sat Jun 14, 2014 12:15 am
by uncle mark
The more I think about this the more I think the best approash may be to boot a live disk and copy these configs over from the live disk to the installed OS. If anybody has any additional thoughts, I'm all ears. If nobody jumps up and yells NO!! DON'T!!!, I think that's what I try in the morning.

Re: Mepis11 WIRED networking pooched

Posted: Sat Jun 14, 2014 12:19 am
by uncle mark
dolphin_oracle wrote:I haven't used M11, but aren't those entries defining a static IP? maybe if you just remove entries so the line looks like

Code: Select all

iface eth0 inet dhcp
that should allow network manager to do its thing. leave networkmanager config with managed = false, this is the correct default entry.

that's how the interface should look in MX anyway. Not sure about M11 and if you used mnetwork to set things up.
So you're suggesting I coment out all the lines except 'iface eth0 inet dhcp'?

Re: Mepis11 WIRED networking pooched

Posted: Sat Jun 14, 2014 7:15 am
by dolphin_oracle
if eth0 is your NIC, then yes.

Re: Mepis11 WIRED networking pooched

Posted: Sat Jun 14, 2014 9:36 am
by uncle mark
dolphin_oracle wrote:if eth0 is your NIC, then yes.
No change no joy.

Re: Mepis11 WIRED networking pooched

Posted: Sat Jun 14, 2014 9:43 am
by Stevo
What about copying over the interfaces file from the Live session? I also am under the impression that manually editing the interfaces file is only necessary if you are running without some sort of connection manager, be it network-manager, wicd, or something else.

Re: Mepis11 WIRED networking pooched

Posted: Sat Jun 14, 2014 10:19 am
by uncle mark
What is the apt-get command that one uses to export a list of installed programs, and the command to install the programs from that list? I may have to admit defeat and reinstall.

Re: Mepis11 WIRED networking pooched

Posted: Sat Jun 14, 2014 10:24 am
by uncle mark
Stevo wrote:What about copying over the interfaces file from the Live session? I also am under the impression that manually editing the interfaces file is only necessary if you are running without some sort of connection manager, be it network-manager, wicd, or something else.
I posted that same thought last night. Can't hurt at this point.

Like I said before, I can reinstall (saving home) if necessary. They only thing I need to do is get the list of installed programs with the apt-get command that I can then use to reinstall what I've got currently. Otherwise, my home is fully backed up, in case saving home were to go TU.

Re: Mepis11 WIRED networking pooched

Posted: Sat Jun 14, 2014 10:46 am
by uncle mark
Stevo wrote:What about copying over the interfaces file from the Live session? I also am under the impression that manually editing the interfaces file is only necessary if you are running without some sort of connection manager, be it network-manager, wicd, or something else.
That fixed it. And I saw why when I was comparing the interfaces files. I have to run, but will post back with what turned out to be the difference, in case somebody can learn from this.

Thanks to all. I'll be punching the thanks buttons when I get back.

Re: Mepis11 WIRED networking pooched

Posted: Sat Jun 14, 2014 11:51 am
by uncle mark
Here's what I found for tose that have been playing along.

Here is the first stanza of the borked interfaces file:

Code: Select all

# lo should ALWAYS be enabled!
auto lo
iface lo inet loopback

# DO NOT EDIT BELOW THIS LINE
#auto eth0
#allow-hotplug eth0
iface eth0 inet dhcp
  address 192.168.79.1
  netmask 255.255.255.0
  broadcast 192.168.79.255
  gateway 192.168.79.1
And here is the stanza from the live dvd, which worked when copied over:

Code: Select all

# lo should ALWAYS be enabled!
auto lo
iface lo inet loopback

# DO NOT EDIT BELOW THIS LINE
auto eth0
#allow-hotplug eth0
#iface eth0 inet dhcp
#  address 192.168.79.1
#  netmask 255.255.255.0
#  broadcast 192.168.79.255
#  gateway 192.168.79.1
The key seems to be that 'auto eth0' was commented out in the borken file, but was enabled -- and everything else commented out -- in the good one.

Now how it got that way is still a mystery. I had a modem go flaky on me, and in the process of getting the replacement up and running I did wire directly to the modem, bypassing the router. I also had trouble getting connectivity through the router, before finally being able to run the router's setup routine from a different machine. So something in networkmanager and/or mnetwork rewrote the interfaces file during that porcess, it seems.

Thanks again to all. Your feedback helped me think this through, got me pointed in the right direction, and allowed me to zero in on the offending entries. Left to my own devices, I very well would have gone down the wrong path.

Re: Mepis11 WIRED networking pooched

Posted: Tue Jul 15, 2014 12:27 pm
by AlanMartin
Dear Uncle Mark, etc.,
Glad to see how you resolved the Wireless problem. I, too, have been beating my brains out trying to get a wireless connection, but to no avail.
The PC is an aged HP Laptop; Compaq nx9020; to which I have added some more memory.
My Home PC is an HP D51C/P2 that has no wireless facilities, and none planed - due to its dence affiliation with the floor!
It too is loaded with M11, but has its own problems.
As an idle interest, I compared the the two interfaces, and they are as diffrent as was noted in the Forum.
I tried loading the nx9020 with a live copy of M11, and lo and behold, wireless would not work, nor would the configure.
I woken up this morning with a great idea to test the laptop with another distro, this being Knoppix 7.0.5, a Live Disc from LinuxUser issue 123., Jan, 2013. Seemed reluctant to load, but got there.
Found the trigger-spot, and was asked for a password for a network named (which I recognised), so entered the p/w, AND I WAS IN!!!!!.

I will have another go at getting the wireless woking with M11 and the different interface files.