Re: FC6 ipw3945 on Dell D820 not working. What's the best way?

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

 



David Kramer escribío:
> SO I bought this brand new Dell Latitude D820.  I've been trying to get
> a fully working Linux install on it for weeks.   I tried F7, but the new
> suspend mechanism doesn't work on this laptop, 

What BIOS rev do you have?  On mine (d820), It suspends after I upgraded it to A5.
For F7 to suspend, see http://people.freedesktop.org/~hughsient/quirk/ and do
not use compiz/beryl.

> it, so I installed FC6.  But with FC6, I can't get the ipw3945 wireless
> working.  I can't catch a break!
> 
> There seems to be several ways: the iwl* packages, the ipw* packages,
> with or without Network Manager...
> 
> So scanning the internets and this list, this is what I have now:
> [root@lexa ~]# uname -a
> Linux lexa.thekramers.net 2.6.20-1.2962.fc6 #1 SMP
> Tue Jun 19 19:27:14    EDT 2007 i686 i686 i386 GNU/Linux
> 
> [root@lexa ~]# rpm -qa | egrep '(3945|ieee)'
> ipw3945d-1.7.22-4.at
> ipw3945-1.2.0-18.3.fc6
> ipw3945-kmdl-2.6.20-1.2962.fc6-1.2.0-18.3.fc6
> ipw3945-ucode-1.14.2-4.at
> ieee80211-kmdl-2.6.20-1.2962.fc6-1.2.16-18.fc6
> ieee80211-1.2.16-18.fc6
> libieee1284-0.2.9-3.2.2
> 
> [root@lexa ~]# lsmod | egrep '(3945|ieee)'
> ipw3945               180000  1
> ieee80211              46188  1 ipw3945
> ieee80211_crypt         9216  1 ieee80211
> ieee1394              294681  1 ohci1394
> 
> [root@lexa ~]# ps -e | egrep '(3945|ieee)'
>  3672 ?        00:00:00 ipw3945/0
>  3674 ?        00:00:00 ipw3945/1
>  3675 ?        00:00:00 ipw3945/0
>  3676 ?        00:00:00 ipw3945/1
>  3685 pts/2    00:00:00 ipw3945d
> 
> [root@lexa ~]# egrep '(3945|ieee)' /etc/modprobe.conf
> alias eth1 ipw3945
> install ipw3945 /sbin/modprobe --ignore-install ipw3945 ;
>   sleep 0.5 ; /sbin/ipw3945d --timeout=2
> remove ipw3945 /sbin/ipw3945d --kill ;
>   /sbin/modprobe -r --ignore-remove ipw3945
> 
> [root@lexa ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth1
> # Please read /usr/share/doc/initscripts-*/sysconfig.txt
> # for the documentation of these parameters.
> TYPE=Wireless
> DEVICE=eth1
> HWADDR=00:1b:77:2c:64:c4
> BOOTPROTO=dhcp
> NETMASK=
> DHCP_HOSTNAME=lexa.thekramers.net
> IPADDR=
> DOMAIN=
> ONBOOT=no
> USERCTL=yes
> IPV6INIT=no
> PEERDNS=yes
> ESSID=DONTPANIC
> MODE=Managed
> RATE='36 Mb/s'
> CHANNEL=1
> 
> "iwconfig eth1" and "iwlist eth1 scanning" both produce good-looking
> results, but the WiFi light is flashing very quickly, and "ifconfig eth1
> up" doesn't get an IP address, nor does "dhclient eth1", which just
> keeps trying.
> 
> 
> So what am I doing wrong?
> What does the fast blinking WiFi lite mean?
> What's the difference between the iwp* packages and the iwl* packages?
> 
> Thanks.  I hope I included enough information.  I'm pretty desperate at
> this point.  This is an expensive laptop!
> 

It all looks OK, what security on the wireless station?  I also am using
NetworkManager which is great for me.  There are items that
NetworkManager-dispatch does that makes it worth wile.

I added the following init.d script to start ipw3945d at the correct time BEFORE
the NetworkManager starts.  If the network comes up and the ipw3945d is not
started, then the wireless is not activated.


#!/bin/sh
#
# ipw3945d:   ipw3945 daemon
#
# chkconfig: - 89 12
# description:  This is a daemon for starting the ipw3945 service
#
# processname: ipw3945d
# pidfile: /var/run/ipw3945d.pid
#

prefix=/sbin
exec_prefix=/sbin
sbindir=/sbin

IPW3945D_BIN=${sbindir}/ipw3945d

# Sanity checks.
[ -x $IPW3945D_BIN ] || exit 1

# Source function library.
. /etc/rc.d/init.d/functions

# so we can rearrange this easily
processname=ipw3945d
servicename=ipw3945d
pidfile=/var/run/ipw3945d.pid

RETVAL=0

start()
{
	echo -n $"Starting ipw3945 daemon: "
	daemon --check $servicename $processname --quiet --pid-file=$pidfile
	RETVAL=$?
	echo
	[ $RETVAL -eq 0 ] && touch /var/lock/subsys/$servicename
}

stop()
{
	echo -n $"Stopping ipw3945 daemon: "
	killproc -p $pidfile $servicename
	RETVAL=$?
	echo
	if [ $RETVAL -eq 0 ]; then
		rm -f /var/lock/subsys/$servicename
		rm -f $pidfile
	fi
}

# See how we were called.
case "$1" in
	start)
		start
		;;
	stop)
		stop
		;;
	status)
		status -p $pidfile $processname
		RETVAL=$?
		;;
	restart)
		stop
		start
		;;
	condrestart)
		if [ -f /var/lock/subsys/$servicename ]; then
			stop
			start
		fi
		;;
	*)
		echo $"Usage: $0 {start|stop|status|restart|condrestart}"
		;;
esac
exit $RETVAL


-- 
Brian Millett - [ Londo, "The Gathering"]
"Nice shark...pretty shark..."

-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora Magazine]     [Fedora News]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux