Skip navigation.
Home
Now Shipping Version 7.0

mepis network assistant problems


Posts: 13

Hello, just installed beta4 and can access the net with my laptop no problem. However the settings won't stay and I have to manually configure mepis network assistant every time i reboot. Under general I choose automatic, wireless is eth1 with my essid , but under interface I have to constantly change from eth0 to eth1 and try and set it to start at boot but it keeps reverting back to eth0 and it unchecks the boxes.I have hit apply and OK. Is there a file somewhere I can manually set this thing up? Is this a permission problem? Maybe a bug of some sort. It's a minor annoyance.
Thx in advance.

Details

Make and model of laptop

What wireless card? Is it built-in?

What network card? I assume the network card came with the laptop.

Often a boot cheat code or BIOS upgrade may help this type of problem. You may want to boot with acpi=off

Mike

Use the wiki http://www.mepis.org/docs
great forum http://www.mepislovers.com

I seem to recall there was a

I seem to recall there was a bug in it. Jon du Quesne reported about it outside the forum. His findings:

But I found a solution

I booted into my 6.0-1 partition and copied the following files:
/etc/mepis-network/wireless/default
/etc/network/interfaces

I copied them from my "old" installation to the new beta4 partition. I rebooted AND IT WORKED. I then went into synaptic for the "First Official Update". Upon reboot... wireless did not work. One of the tools that had been updated was the Mepis Network Utilities.

So I made yet another copy of the above two files and then I compared them. This is what I found. The only (main) difference was in the /etc/mepis-network/wireless/default file. Here's what I found:
# diff default.6.0-1 default.6.0-4-beta4
7c7
< IF_WIRELESS_FREQ="2.437G"
---
> > IF_WIRELESS_FREQ="2.437 GHzG"

It might help you, or wait for the next mepis-network upgrade, which will be available soon, no doubt.
Newbie or not Newbie, there's always a question

Update your packages...

I had a similar problem with the new adapters that were added to later betas (ra0, rausb0).

The issue turned out to be Synaptic not replacing /etc/network/interfaces
and /etc/network/if-pre-up.d/00mepis-wireless with the new versions of those files when updating from one beta to the next. IOW, it was still broken after updating to beta 4 via Synaptic. A new update from Warren fixed it for my adapter.

If you use Synaptic (KMenu>System>Package Manager (Synaptic), then press Reload, Mark all Upgrades and Press Apply, you'll get a new mepis-network-6.0 package that fixes the issues (overwrites the old files so that your settings are retained and applied).

You could just update that one package (mepis-network-6.0) and get the fix, too.

I'm assuming that your issue is the same one I saw with my adapter (the symptoms sound the same with it not saving your settings,even in beta 4). If so, the updated mepis-network-6.0 package that Warren uploaded after beta 4 came out should fix it.

Jim C.

thx for the responses

I have the new updates, so I tried rebooting and low and behold it worked??? However if I go into mepis network assistant the settings are still off (regarding the diffence between eth0 and eth1 and no box checked for start at boot), and its set to manual still, only thing i did different was added my user account to dhcp?

I'd let warren know...

Perhaps the fixes may have messed up something else (even though they fixed the problem with the newer ra0/rausb0 adapters that were added). That's just speculation on my part.

I'd send an e-mail to dev at mepis.org about it and include a link to this thread.

Jim C.

Jon Du Quesne's picture

Thanks Carlops

Thanks carlops for posting my stuff. I just got home from a relaxing day off with friends, and was waiting to see if there were any responses to this from the "insiders" before I posted anymore. Thanks for letting others know so that perhaps they can provide additional information.

One of the things I did not ask about (and I cannot remember the solution for) is the issue of eth0 and eth1 "changing places". It turns out that wireless still works. As a matter of fact, one funny thing that happened during my testing of beta4 last night is both interfaces started and both had the SAME IP ADDRESS. Mind you, I had no wired access. My system seemed to work just fine Smiling

But do you remember the solution to "pegging" a particular interface to eth0 or eth1? Was it a matter of placing the MAC address for each interface into a particular file? My poor brain doesn't remember (sob) Sad

Jon

SimplyMEPIS Value CD: $17.95
Amount saved not buying Windows Vista Ultimate: $399
Experience gained learning Mepis and helping others: Priceless

Jon, I looked it up for you

Jon, I looked it up for you (you scratch other people's back and I scratch yours....). It is in this thread: http://www.mepis.org/node/10770

Cheers

Newbie or not Newbie, there's always a question

Jon Du Quesne's picture

Thanks Carlops (again)

Thanks again Carlops. You Da Man Smiling

Since I'm at work and can't do any Linux stuff here I will have to look later. But yes, that's the link. I shall check it out later and see what happens!

Jon

SimplyMEPIS Value CD: $17.95
Amount saved not buying Windows Vista Ultimate: $399
Experience gained learning Mepis and helping others: Priceless

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.