Tiny Core Extensions > TCE 2.x

wicd

<< < (5/9) > >>

bmarkus:
Just tested WICD on 2.8.1 desktop without any wireless hardware. It works as expected and can manage wired Ethernet interface.

After issuing 'sudo wicd-start' command, you must see dbus-daemon running with the 'ps' command. If not, this is a dbus issue. If it is there, check wicd log in /var/log/wicd.

BTW, which TC version is used and what is the installation type? Are all components up to date?

Miller:
Hi Bela

I'm using TC 2.8.1 as a fresh install (yesterday) onto a SD card. This card is sdb1. I have all extensions installed to /mnt/sdb1/tce/optional
The TC install is just your default type with nothing customised or hacked.

Yes all components are up to date. At your suggestion concering the dbus subsytem, I removed all 9 dbus files from the tce optional directory. ie  dbus, dbus-python & dbus-glib (.tcz, .tcz.dep & .tcz.md5.txt variants) I replaced these extensions with older versions from Dec 2009 repository. Now wicd appears to be behaving itself!

It's getting close to midnight in this part of the world so I had best be away.

I will run the checks you suggest tomorrow and report back. Thanks for all your assistance. Much obliged.

Best

Miller.

Jason W:
The dbus and other extensions no longer start the service with the /usr/local/tce.installed startup script.  This is being done to pave the way for recursive dependencies, and we can't have our cake and eat it too when it comes to recursion vs. controlling the order of dependency loading, which was necessary to have the startup scripts start daemons for some extensions. 

The scripts in /usr/local/etc/init.d are now being used to start daemons, and those start commands can be placed in bootlocal.sh. 

"/usr/local/etc/init.d/dbus start" would be the command.

bmarkus:
Jason

WICD and DBUS installed just recently from the repo starts fine and works expected on my machines, so Miller's problem is not related to this change. Atleast as I see at the moment.

Lets wait for the report.

cefcom:
Hi all:
I get the same error as Miller regarding the wicd-client output in both of my laptops (Acer Aspire One D150 with a Broadcomm wlan card, the wl module loaded and a Dell Inspiron 9100).  I used the latest tc 2.8.1 version default install on an usb (=sdb1) with persistent tce and home.  Desktop is FLWM.

Tried what Jason suggested, but keep getting same error.

Cefcom

Navigation

[0] Message Index

[#] Next page

[*] Previous page