SL 5.4 E17 Spin x86: WiFi (Wicd) problem [Solved]

[joost]

http://gitweb.sabayon.org/?p=overlay.gi ... 8eb806ade2

it compiled fine against our tree.
Adding it to Limbo.

From trunk:

Gentoo

If you want add the daemon in your init, you can use the script in daemon/data/init.d/gentoo:

cp data/daemon/data/init.d/gentoo /etc/init.d/exaltd
rc-update add exaltd default

The init script is here:
http://trac.enlightenment.org/e/browser ... t.d/gentoo

[Fitzcarraldo]

Thanks. I'll try it this evening and report back.

[micia]

This post is powered by Exalt

Here is what I did to make it work:

1) Added Limbo and:

Code: Select all

equo install exalt

(quite unpredictable)

2) following:

From trunk:

Gentoo

If you want add the daemon in your init, you can use the script in daemon/data/init.d/gentoo:

cp data/daemon/data/init.d/gentoo /etc/init.d/exaltd
rc-update add exaltd default

The init script is here:
http://trac.enlightenment.org/e/browser ... t.d/gentoo

I downloaded the script in /home/micia/gentoo, I executed in a console, as root:

Code: Select all

mv /home/micia/gentoo /etc/init.d/exaltd
chmod ugo+x /etc/init.d/exaltd
rc-update del NetworkManager default
rc-update add exaltd default


3) reboot to an enlightenment session

4) In the new session:
main-menu->Settings->Modules, I loaded the module: System->Connection Manager
right click on the panel -> Shelf bottom -> Contents, Select Connection Manager, Add Gadget.

5) Here is the pretty unpredictable part, Exalt complains about missing connman, checking the rc.log I see:

Code: Select all

 * Starting Exalt daemon ...
 * start-stop-daemon: /usr/local/sbin/exalt-daemon does not exist
 [ !! ]


So, after setting up manually my wireless with the good old iwconfig, ifconfig and dhclient, I did:

Code: Select all

equo install connman
rc-update add connman default


6) reboot to an enlightenment session.

7) I have my beautiful Exalt gadget that works just fine, it is fast and quite usable.

So, it seems that, ironically with my first post, Exalt (at least this version) is a frontend for connman, and it works Way better than connman-gnome.
And it also seems that the script pointed out by joost is not useful for this version of Exalt, at least not if you have connman...

Also, Fitzcarraldo, it looks like that for adding the systray to the panel, you have to go, after the procedure that I went into, on the panel and right-click->Shelf Bottom->Contents and Add the systray gadget.
Sorry for my clumsy procedure, this is just my second time on Enlightenment

[joost]

I noticed that the daemon gets installed here: /usr/sbin/exalt-daemon
So you will have to modify the init script.

Later I will work all this into the ebuild.

Code: Select all

#!/sbin/runscript
# Copyright 1999-2006 Gentoo Foundation
# Distributed under the terms of the GNU General Public License, v2 or later


depend() {
    need dbus hald
}


start() {
    ebegin "Starting Exalt daemon"
        start-stop-daemon --start --exec /usr/sbin/exalt-daemon \
        --pidfile /var/run/exaltd.pid
        eend $?
}

stop() {
    ebegin "Stopping Exalt daemon"
        start-stop-daemon --stop --exec /usr/sbin/exalt-daemon  \
        --pidfile /var/run/exaltd.pid
        eend $?
}

restart() {
    svc_stop
        svc_start
}


/etc/dbus-1/system.d/exalt.conf

Code: Select all

 <!DOCTYPE busconfig PUBLIC
 "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
 "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
 <busconfig>
      <policy user="root">
      <allow own="org.e.Exalt"/>
                <allow send_destination="org.e.Exalt"/>
                <allow send_interface="org.e.Exalt"/>
        </policy>
        <policy at_console="true">
                <allow send_destination="org.e.Exalt"/>
                <allow send_interface="org.e.Exalt"/>
        </policy>
        <policy context="default">
                <!-- <deny own="org.e.Exalt"/> -->
                <!-- <deny send_destination="org.e.Exalt"/> -->
                <!-- <deny send_interface="org.e.Exalt"/> -->
                <allow own="org.e.Exalt"/>
                <allow send_destination="org.e.Exalt"/>
                <allow send_interface="org.e.Exalt"/>
        </policy>
  </busconfig>


//Edit:
It looks like exalt is indeed a connman GUI. The steps above taken (written in trunk README) did not work for me. However using connman made it all work here.

So the proposal would be this:
Remove wicd
Add connman and exalt

Found an image on the web, this is how it looks:

[micia]

I tried the step posted above by joost too:

1) changed the /etc/init.d/exaltd
2) added /etc/dbus-1/system.d/exalt.conf


they were all added from a copy&paste of the ones provided by joost.

3) removed connman from startup services

but it spelled disaster:
rc.log reported the correct and successful launch of Exaltd.
connman was still needed for the applet to stop complaining, so I launched the service.

Code: Select all

/etc/init.d/connman start


The applet refused to connect with this error:

Code: Select all

Could not execute remote operation:
Connetti al servizio di rete
Server Error OperationAborted: Operation Aborted


The Italian part of the message can be translated as:

Code: Select all

Connect to the Network


Removing the /etc/dbus-1/system.d/exalt.conf file and rebooting did not work, everything was still the same, the only way was to remove the Exaltd service from startup.

I think that connman should be added as a dependency in this case...


(Also, I noticed that PCLinuxOS E17 uses, as a burning application, simpleburn, since there are just a few GTK burning applications alternatives that don't depend heavily on Gnome, I think that it could be a good add to E17 too.
But this is really off topic.
the home is:
http://simpleburn.tuxfamily.org/
I was able to find only the 1.4 ebuild here:
https://github.com/nightmorph/overnight/blob/master/app-cdr/simpleburn/simpleburn-1.4.0.ebuild
)

[Fitzcarraldo]

Nice work, you two! Super quick, detailed replies. Thanks.

I should be working, but, after reading your replies, I couldn't resist firing up the SL 5.4 E17 Spin LiveCD again for another tinker. This stuff is terribly addictive.

I have not tried to install Exalt yet, but am embarrassed to say that I got nm-applet working easily.

There was no need to install a Systray on a Shelf, micia, the nm-applet icon loaded in a spare Systray on Shelf 5 in the right hand corner of the screen. After giving up on Wicd last night and trying to launch nm-applet, my mistake was to run nm-applet as root user instead of under my user name. All I needed to do just now to get WiFi working was:

1. Boot the LiveCD.

2. Open a Terminal and enter the following command as a normal user:

Code: Select all

nm-applet

3. Click on the nm-applet icon and enter the WPA passkey and a wallet password.

4. Open a Terminal, log-in as root user and lower the MTU:

Code: Select all

ifconfig wlan0 mtu 1464

Anyway, I'm going to re-install the SL 5.4 E17 Spin to the HDD tonight and have a play with Exalt based on your investigations, as its look and feel are tailored to E17 and I remember it working nicely in Elive. (Oh, and I'll uninstall Wicd. )

[joost]

http://gitweb.sabayon.org/?p=overlay.gi ... 55259eb3d6

added connman dep.
I think there is no reason to keep it in Limbo. I will bump it and add it to the main repository.

[joost]

If you want connman on E17 avoid using Limbo for the moment.

I was bumping EFL ( http://www.enlightenment.org/p.php?p=ne ... news_id=25 ) wich recently made it into Portage. I also needed to rebuild enlightenment:0.17 (taken from enlightenment overlay) and believe it or not, but it is exactly the e_modules_connman module that fails to compile! aarrghh.

So the version in Limbo is without this.
Hopefully this gets fixed soon, until then I can only keep it separated in Limbo.

[joost]

Another update on this.

I ended up removing the enlightenment overlay and add x11-wm/enlightenment-0.16.999.54504 (new snapshot) to our overlay. And YaY! it compiled fine!

Adding it all to Limbo now.

[joost]