This past weekend I and Mike Conners discovered where the inability of the Sony Vaio to connect to the 'Net happens. I still need serious help from those who know Slackware better than do I to determine why, and how to resolve the problem.
No one's reponded to my thread on linuxquestions.org and I know this area has many linux experts (kernel, modules, and networking). If no one here knows the solution, perhaps someone can point me to an appropriate guru. Mike and I had the Dell (which works just fine with dynamic IP address wireless access and static IP address ethernet access) and the Sony running side-by-side and invoked 'wicd-client -n' simultaneously on both while tailing /var/log/messages on each. The Dell's log showed: Apr 14 09:35:36 caddis dhcpcd[3096]: version 5.2.12 starting Apr 14 09:35:36 caddis kernel: [ 1946.368876] ADDRCONF(NETDEV_CHANGE) : wlan0: link becomes ready Apr 14 09:35:36 caddis dhcpcd[3096]: wlan0: broadcasting for a lease Apr 14 09:35:36 caddis dhcpcd[3096]: wlan0: offered 10.5.70.151 from 10.5.70.1 Apr 14 09:35:36 caddis dhcpcd[3096]: wlan0: acknowledged 10.5.70.151 from 10.5.70.1 Apr 14 09:35:36 caddis dhcpcd[3096]: wlan0: checking for 10.5.70.151 Apr 14 09:35:42 caddis dhcpcd[3096]: wlan0: leased 10.5.70.151 for 14 400 seconds Apr 14 09:35:42 caddis dhcpcd[3096]: forked to background, child pid 3127 Apr 14 09:38:36 caddis ntpd[1671]: Listen normally on 5 wlan0 10.5.70.151 UDP 123 Apr 14 09:38:36 caddis ntpd[1671]: Listen normally on 6 wlan0 fe80::223:14ff:fe68:98e0 UDP 123 Apr 14 09:38:36 caddis ntpd[1671]: Deleting interface #3 eth0, 192.168.55.2#123, interface stats: received=0, sent=0, dropped=0, active_time=2101 secs Apr 14 09:38:36 caddis ntpd[1671]: peers refreshed It is after dhcpcd forked to the background that ntpd was invoked and deleted the eth0 interface. On the Sony when dhcpcd forked to the background everything stopped. No further messages because ntpd was not invoked. What might prevent ntpd from being called on the Sony? This seems to be the key issue and I've no idea how to trace it further toward the source. _Someone_ must have the insight and experience to point me toward a fix. TIA, Rich _______________________________________________ slackware mailing list [email protected] https://mailman.lug.org.uk/mailman/listinfo/slackware _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
