I've been trying to get my Dell Latitude E6400 to connect with a Linux distro and I keep running into problems.

I was able to get it working with Linux Lite, but the installation failed.

So then I tried Anti-X at the suggestion of this forum, and I'm getting another error:

Could not connect to wicd's D-Bus interface.

Here are some stats:

$ lspci
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection (rev 03)
00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03)
00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03)
00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
03:01.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba)
03:01.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04)
03:01.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 21)
0c:00.0 Network controller: Broadcom Limited BCM4322 802.11a/b/g/n Wireless LAN Controller (rev 01)
master@antix1:~
$
master@antix1:~
$ lsusb
Bus 002 Device 003: ID 0781:5575 SanDisk Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 005: ID 413c:8156 Dell Computer Corp. Wireless 370 Bluetooth Mini-card
Bus 003 Device 004: ID 413c:8158 Dell Computer Corp. Integrated Touchpad / Trackstick
Bus 003 Device 003: ID 413c:8157 Dell Computer Corp. Integrated Keyboard
Bus 003 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
master@antix1:~
$
master@antix1:~
$ ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:24:e8:c3:a5:33 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 22 memory 0xf6ae0000-f6b00000

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 10 bytes 580 (580.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 10 bytes 580 (580.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::226:5eff:fe4c:b4c1 prefixlen 64 scopeid 0x20<link>
ether 00:26:5e:4c:b4:c1 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 17 base 0xc000

master@antix1:~
$
master@antix1:~
$ iwconfig
wlan0 IEEE 802.11 ESSIDff/any
Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm
Retry short limit:7 RTS thrff Fragment thrff
Power Managementff

eth0 no wireless extensions.

lo no wireless extensions.

Here is the wicd log from /var/log/wicd:

$ sudo cat wicd.log
2019/02/25 13:07:33 :: ---------------------------
2019/02/25 13:07:33 :: wicd initializing...
2019/02/25 13:07:33 :: ---------------------------
2019/02/25 13:07:33 :: wicd is version 1.7.4 961
2019/02/25 13:07:33 :: did not find backend in configuration, setting default external
2019/02/25 13:07:33 :: setting backend to external
2019/02/25 13:07:33 :: trying to load backend external
2019/02/25 13:07:33 :: successfully loaded backend external
2019/02/25 13:07:33 :: trying to load backend external
2019/02/25 13:07:33 :: successfully loaded backend external
2019/02/25 13:07:34 :: Automatically detected wireless interface wlan0
2019/02/25 13:07:34 :: did not find wireless_interface in configuration, setting default wlan0
2019/02/25 13:07:34 :: setting wireless interface wlan0
2019/02/25 13:07:34 :: automatically detected wired interface eth0
2019/02/25 13:07:34 :: did not find wired_interface in configuration, setting default eth0
2019/02/25 13:07:34 :: setting wired interface eth0
2019/02/25 13:07:34 :: did not find wpa_driver in configuration, setting default wext
2019/02/25 13:07:34 :: setting wpa driver wext
2019/02/25 13:07:34 :: did not find always_show_wired_interface in configuration, setting default False
2019/02/25 13:07:34 :: did not find use_global_dns in configuration, setting default False
2019/02/25 13:07:34 :: setting use global dns to False
2019/02/25 13:07:34 :: did not find global_dns_1 in configuration, setting default None
2019/02/25 13:07:34 :: did not find global_dns_2 in configuration, setting default None
2019/02/25 13:07:34 :: did not find global_dns_3 in configuration, setting default None
2019/02/25 13:07:34 :: did not find global_dns_dom in configuration, setting default None
2019/02/25 13:07:34 :: did not find global_search_dom in configuration, setting default None
2019/02/25 13:07:34 :: setting global dns
2019/02/25 13:07:34 :: global dns servers are None None None
2019/02/25 13:07:34 :: domain is None
2019/02/25 13:07:34 :: search domain is None
2019/02/25 13:07:34 :: did not find auto_reconnect in configuration, setting default True
2019/02/25 13:07:34 :: setting automatically reconnect when connection drops True
2019/02/25 13:07:34 :: did not find debug_mode in configuration, setting default False
2019/02/25 13:07:34 :: did not find wired_connect_mode in configuration, setting default 1
2019/02/25 13:07:34 :: did not find signal_display_type in configuration, setting default 0
2019/02/25 13:07:34 :: did not find should_verify_ap in configuration, setting default 1
2019/02/25 13:07:34 :: did not find dhcp_client in configuration, setting default 0
2019/02/25 13:07:34 :: Setting dhcp client to 0
2019/02/25 13:07:34 :: did not find link_detect_tool in configuration, setting default 0
2019/02/25 13:07:34 :: did not find flush_tool in configuration, setting default 0
2019/02/25 13:07:34 :: did not find sudo_app in configuration, setting default 0
2019/02/25 13:07:34 :: did not find prefer_wired in configuration, setting default False
2019/02/25 13:07:34 :: did not find show_never_connect in configuration, setting default True
2019/02/25 13:07:34 :: Wireless configuration file not found, creating...
2019/02/25 13:07:34 :: Wired configuration file not found, creating a default...
2019/02/25 13:07:34 :: Creating wired profile for wired-default
2019/02/25 13:07:34 :: dhclient.conf.template not found, copying...
2019/02/25 13:07:34 :: chmoding configuration files 0600...
2019/02/25 13:07:34 :: chowning configuration files root:root...
2019/02/25 13:07:34 :: Using wireless interface...wlan0
2019/02/25 13:07:34 :: Using wired interface...eth0
2019/02/25 13:07:36 :: hidden
2019/02/25 13:07:36 :: hidden
2019/02/25 13:07:39 :: Autoconnecting...
2019/02/25 13:07:39 :: No wired connection present, attempting to autoconnect to wireless network
2019/02/25 13:07:41 :: hidden
2019/02/25 13:07:41 :: hidden
2019/02/25 13:07:41 :: hidden
2019/02/25 13:07:41 :: hidden
2019/02/25 13:07:41 :: hidden
2019/02/25 13:07:41 :: hidden
2019/02/25 13:07:41 :: Unable to autoconnect, you'll have to manually connect
2019/02/25 13:07:44 :: Autoconnecting...
2019/02/25 13:07:44 :: No wired connection present, attempting to autoconnect to wireless network
2019/02/25 13:07:46 :: hidden
2019/02/25 13:07:46 :: hidden
2019/02/25 13:07:46 :: hidden
2019/02/25 13:07:46 :: hidden
2019/02/25 13:07:46 :: hidden
2019/02/25 13:07:46 :: hidden
2019/02/25 13:07:46 :: hidden
2019/02/25 13:07:46 :: hidden
2019/02/25 13:07:46 :: hidden
2019/02/25 13:07:46 :: Unable to autoconnect, you'll have to manually connect
2019/02/25 13:07:49 :: Autoconnecting...
2019/02/25 13:07:49 :: No wired connection present, attempting to autoconnect to wireless network
2019/02/25 13:07:51 :: hidden
2019/02/25 13:07:51 :: hidden
2019/02/25 13:07:51 :: hidden
2019/02/25 13:07:51 :: hidden
2019/02/25 13:07:51 :: hidden
2019/02/25 13:07:51 :: hidden
2019/02/25 13:07:51 :: hidden
2019/02/25 13:07:51 :: hidden
2019/02/25 13:07:51 :: hidden
2019/02/25 13:07:51 :: hidden
2019/02/25 13:07:51 :: Unable to autoconnect, you'll have to manually connect
2019/02/25 13:07:54 :: Autoconnecting...
2019/02/25 13:07:54 :: No wired connection present, attempting to autoconnect to wireless network
2019/02/25 13:07:56 :: hidden
2019/02/25 13:07:56 :: hidden
2019/02/25 13:07:56 :: hidden
2019/02/25 13:07:56 :: hidden
2019/02/25 13:07:56 :: hidden
2019/02/25 13:07:56 :: hidden
2019/02/25 13:07:56 :: hidden
2019/02/25 13:07:56 :: hidden
2019/02/25 13:07:56 :: hidden
2019/02/25 13:07:56 :: hidden
2019/02/25 13:07:56 :: hidden
2019/02/25 13:07:56 :: hidden
2019/02/25 13:07:56 :: hidden
2019/02/25 13:07:56 :: hidden
2019/02/25 13:07:56 :: Unable to autoconnect, you'll have to manually connect
2019/02/25 13:11:14 :: Autoconnecting...
2019/02/25 13:11:14 :: No wired connection present, attempting to autoconnect to wireless network
2019/02/25 13:11:15 :: hidden
2019/02/25 13:11:16 :: Unable to autoconnect, you'll have to manually connect

All depends on what you did or did not do when installing wicd. Menu item #2 in this guide should be consulted, it will show how to reload dbus after proper configuration.

Thanks for the help. I went through the steps in the guide you referenced but when I try to start the wicd daemon I get this message:

Not starting wicd daemon. Please edit /etc/default/wicd first. (warning)

Here is the /etc/default/wicd file: How should I edit it!

# Start the daemon by default, let the user disable it.
# Use "no" (without quotes) to make /etc/init.d/wicd *NOT* start the WICD daemon.
START_DAEMON=no

# By default don't kill connections on daemon shutdown, see
# https://bugs.debian.org/816076 and
# https://bazaar.launchpad.net/~wicd-d...l/revision/851
DAEMON_ARGS="--keep-connection"

Change the other line as follows:

1 members found this post helpful.

THANK YOU! It's finally working.