Re: NM 0.7.0.100 and Slackware



On Mon, 2009-04-06 at 10:05 +0200, Sasa Ostrouska wrote:
> Hi folks,
> 
> First let me introduce myself, I'm new in here, my name is Sasa
> Ostrouska and I'm a packager of the
> project droplinegnome.org . Its a gnome version for Slackware. Said
> that, we are trying to release now
> the 2.26.x gnome series , but I have some troubles getting NM to work.
> I have few questions:
> 
> 1) Is there some support for Slackware distro in NM ? I saw there is a
> rc.networkmanager script but it
> seems to be not the most apropriate thingy for now.

There used to be support, and it might still work.  Right now, about all
that should be necessary to fix up is the init script and
src/backends/NetworkManagerSlackware.c

> 2) Where is possible to have some help , maybe an irc channel, or its
> better to write here ?

freenode, #nm

> 3) Up to now I found a wiki on ubuntu.com saying how to debug NM. So
> issueing the command below:
> 
> NM_SERIAL_DEBUG=1 NetworkManager --no-daemon 2>&1 | tee /tmp/nm-serial.txt
> 
> I got this so far:
> 
> NetworkManager: <info>  starting...
> -- Error received: File exists
> -- Original message: type=0x14 length=56 flags=<REQUEST,ACK,ATOMIC>
> sequence-nr=1238949083 pid=4199323
> NetworkManager: <WARN>  nm_generic_enable_loopback(): error -17
> returned from rtnl_addr_add():
> Sucess
> 
> NetworkManager: <info>  (eth0): new Ethernet device (driver: 'sky2')
> NetworkManager: <info>  (eth0): exported as
> /org/freedesktop/Hal/devices/net_00_13_77_af_1f_59
> NetworkManager: <info>  (wlan0): driver supports SSID scans (scan_capa 0x01).
> NetworkManager: <info>  (wlan0): new 802.11 WiFi device (driver: 'ath5k_pci')
> NetworkManager: <info>  (wlan0): exported as
> /org/freedesktop/Hal/devices/net_00_21_63_92_af_f6
> NetworkManager: <info>  Trying to start the supplicant...
> NetworkManager: <info>  Trying to start the system settings daemon...
> NetworkManager: <info>  (eth0): device state change: 1 -> 2
> NetworkManager: <info>  (eth0): bringing up device.
> NetworkManager: <info>  (eth0): preparing device.
> NetworkManager: <info>  (eth0): deactivating device (reason: 2).
> NetworkManager: <info>  Setting system hostname to
> 'localhost.localdomain' (no default device)
> NetworkManager: <info>  (wlan0): device state change: 1 -> 2
> NetworkManager: <info>  (wlan0): bringing up device.
> NetworkManager: <info>  (wlan0): preparing device.
> NetworkManager: <info>  (wlan0): deactivating device (reason: 2).
> NetworkManager: supplicant_interface_acquire: assertion `mgr_state ==
> NM_SUPPLICANT_MANAGER_STATE_IDLE' failed
> NetworkManager: <info>  (eth0): carrier now ON (device state 2)
> NetworkManager: <info>  (eth0): device state change: 2 -> 3
> 
> The NM is built by myself, and I used the following options for configure:
> 
> configure --with-distro=slackware \
> 	          --with-docs \
> 	          --with-dbus-sys=/etc/dbus-1/system.d \
> 	          --with-dhcp-client=dhcdbd \
> 	          --with-pppd-plugin-dir=/etc/ppp/plugins \
> 	          --with-resolvconf=/etc/resolv.conf \
> 	          --with-system-ca-path=/etc/ssl/certs \
> 	          --with-crypto=gnutls
> 
> Seems that its missing just some configuration files, which probably
> are not created in the correct way for Slackware during the install
> phase.

Do you have wpa_supplicant installed?  Is it correctly set up for dbus
service activation?  You'll want a file
called /usr/share/dbus-1/system-services/fi.epitest.hostap.WPASpplicant.service that looks like this:

[D-BUS Service]
Name=fi.epitest.hostap.WPASupplicant
Exec=/usr/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -u -f /var/log/wpa_supplicant.log
User=root

> Also would be good to know if I need to set up some policys for
> PolicyKit to make it work the right way ?

No, as long as you're running PolicyKit 0.7 or greater, the existing
policy file should be OK.

Let me know if you have any more questions!

Dan




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]