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, and there's no way around 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!
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
On 6/29/07, David Kramer david@thekramers.net wrote:
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, and there's no way around 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...
Your experience is just like mine. I've made both iwl and ipw drivers work. I'd say for getting it going the first time, here's what you should do. Try ipw3945. That means in /etc/modules.d/blacklist, you need to add iwl3945 to make sure it does not load. If it doesn ipw won't work.
Second, turn off NetworkManager, at least temporarily.
/sbin/service NetworkManager stop
Third, Find out if the regulatory deamon runs. If you type this and it is running, you should see this (pasted in)
# /sbin/ipw3945d ipw3945d - regulatory daemon Copyright (C) 2005-2006 Intel Corporation. All rights reserved. version: 1.7.22 2007-06-29 10:30:31: ERROR: ipw3945d already running. If ipw3945d is not running then you need to remove '/var/run/ipw3945d.pid' and try again.
If it says there is no device, it means the module did not load. Load it manually after making sure the iwl3945 and mac80211 modules are no longer loaded. (use /sbin/lsmod to see them and /sbin/rmmod to get rid of them)
/sbin/modprobe ipw3945
THen try to start the daemon again.
Then type /sbin/iwlist scan to see if there are wireless routers around. If there are, run
system-config-network
and go through the steps of setting up a new wireless device. The critical part is the last one, where you put in the wireless server's name and if you can, set the channel. That gui has a way to activate it. It is the same thing as /sbin/ifup eth1 that you were trying. I suspect /sbin/ifup eth1 did not work for you before because the network scripts were not configured. You can study the output of that setup by reading the files it creates in /etc/sysconfig/network-scripts. Look at ifcg-eth1. That will be customized for the current access point. To use others, I "cp ifcg-eth ifcfg-othersite" and then edit that file. Leave the device as eth1, change the essid. after that, /sbin/ifup othersite does the trick. I have never had success with system-config-network when adding more wlreless points. Don't bother.
If that works, then you can consider running NetworkManager again and launching the nm-applet to have a gui way to do this.
Honestly, I've wasted many hours on this and I promise this is the best, most dependable way to get it started. I think the secret was to blacklist iwl3945. After I did that, everything worked 20000% better
I sincerely hope this helps
pj
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!
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Brian Millett wrote:
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.
My BIOS is A6 (from April), and it does not suspend. I spent two whole nights trying different quirk options. They never should have changed the power management software in the state it's in.
I hate that I have this brand new laptop and I have to run an older version of Fedora on it, but I've tried all I can try. Hopefully Fedora 8 will be better.
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.
Your script was very helpful. Thanks. More on that later
Paul Johnson wrote:
Your experience is just like mine. I've made both iwl and ipw drivers work. I'd say for getting it going the first time, here's what you should do. Try ipw3945. That means in /etc/modules.d/blacklist, you need to add iwl3945 to make sure it does not load. If it doesn ipw won't work.
I uninstalled the iwl stuff. Nothing I read explicitly said so, but my instincts told me they were mutually exclusive.
Second, turn off NetworkManager, at least temporarily. /sbin/service NetworkManager stop
I never had it enabled. What does it do?
Third, Find out if the regulatory deamon runs. If you type this and it is running, you should see this (pasted in)
# /sbin/ipw3945d ipw3945d - regulatory daemon Copyright (C) 2005-2006 Intel Corporation. All rights reserved. version: 1.7.22 2007-06-29 10:30:31: ERROR: ipw3945d already running. If ipw3945d is not running then you need to remove '/var/run/ipw3945d.pid' and try again.
Got this problem fixed with Brian Millett's script.
and go through the steps of setting up a new wireless device. The critical part is the last one, where you put in the wireless server's name and if you can, set the channel. That gui has a way to activate it. It is the same thing as /sbin/ifup eth1 that you were trying. I suspect /sbin/ifup eth1 did not work for you before because the network scripts were not configured. You can study the output of that setup by reading the files it creates in /etc/sysconfig/network-scripts. Look at ifcg-eth1. That will be customized for the current access point. To use others, I "cp ifcg-eth ifcfg-othersite" and then edit that file. Leave the device as eth1, change the essid. after that, /sbin/ifup othersite does the trick.
My old laptop is running SUSE. They have a tool called SCPM, System Configuration Profile Manager, that lets you store and retrieve different config files for different environments. I was wondering how you would do this in Fedora. While I'm sure your suggestion isn't the official way it's supposed to be done, that sounds like it would work, and work well and predictably. I'll bring it into work Monday and try that.
I have never had success with system-config-network when adding more wlreless points. Don't bother.
I find system-config-network highly unpredictable. It's the first Fedora program I learned to hate ;)
If that works, then you can consider running NetworkManager again and launching the nm-applet to have a gui way to do this.
Likewise, the man pages for NetworkManager are about two paragraphs long. I guess I'll have to just save all my config files and try it and see what it does.
Honestly, I've wasted many hours on this and I promise this is the best, most dependable way to get it started. I think the secret was to blacklist iwl3945. After I did that, everything worked 20000% better
I sincerely hope this helps
Yes. Everything is working now. But it took the hints posted on no less than three emails to get the whole picture. In addiition to Paul's and Brian's suggestions, I found a third post from a related thread suggesting putting "alias eth1 ipw3945" in /etc/modprobe.conf. I never thought to check for that, because I couldn't imagine a scenario where the install didn't do that for me, but I guess I was wrongt.
Thank you both for your suggestions. I would rather have gotten suspend working in F7 than revoert to FC6, but at least I have Fc6 working, and as soon as I migrate my configuration over from the old laptop, I might even have domestic tranquility again.
On 6/30/07, David Kramer david@thekramers.net wrote:
Brian Millett wrote:
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.
My BIOS is A6 (from April), and it does not suspend. I spent two whole nights trying different quirk options. They never should have changed the power management software in the state it's in.
You mean you have a D820 that can suspend and resume with FC7. I upgraded to their newest bios (A7) and still get no resume.
I find it impossible to believe that you can make it work, given that the vbetool program was accidentally omitted from pm-utils. I've tried the quirks approach and in /var/log/pm-suspend.log, I see "vbetool not found" all over the place. You can get newer pm-utils here: http://koji.fedoraproject.org/koji/buildinfo?buildID=8378
Can you please give a few more details on how you are making the suspend work? I have Nvidia and use their proprietary driver, so that's one difference. I've tried the nv driver and it doesn't resume either.
I've even gone so far as booting into runlevel 3, removing modules and processes for ipw3945 and nvidia, and running pm-suspend with various quirks. I don't get errors anymore after finding pm-utils with vbetool, but I still can't wake up the damn computer.
The ipw3945d rpm I found on freshrpms installs the same kind of init script as you posted in your mail, so I've got that part covered.
So how are you doing it??
pj
ps, I see:
# cat /var/log/pm-suspend.log Mon Jul 2 04:18:22 CDT 2007: running suspend hooks. ===== Mon Jul 2 04:18:22 CDT 2007: running hook: /usr/lib/pm-utils/sleep.d/00clear ===== ===== Mon Jul 2 04:18:22 CDT 2007: running hook: /usr/lib/pm-utils/sleep.d/01grub ===== ===== Mon Jul 2 04:18:22 CDT 2007: running hook: /usr/lib/pm-utils/sleep.d/05led ===== ===== Mon Jul 2 04:18:22 CDT 2007: running hook: /usr/lib/pm-utils/sleep.d/10NetworkManager ===== ===== Mon Jul 2 04:18:23 CDT 2007: running hook: /usr/lib/pm-utils/sleep.d/20video ===== kernel.acpi_video_flags = 0 ===== Mon Jul 2 04:18:23 CDT 2007: running hook: /usr/lib/pm-utils/sleep.d/49bluetooth ===== ===== Mon Jul 2 04:18:23 CDT 2007: running hook: /usr/lib/pm-utils/sleep.d/50modules ===== ===== Mon Jul 2 04:18:23 CDT 2007: running hook: /usr/lib/pm-utils/sleep.d/55battery ===== ===== Mon Jul 2 04:18:23 CDT 2007: running hook: /usr/lib/pm-utils/sleep.d/60sysfont ===== ===== Mon Jul 2 04:18:23 CDT 2007: running hook: /usr/lib/pm-utils/sleep.d/65alsa ===== ===== Mon Jul 2 04:18:23 CDT 2007: running hook: /usr/lib/pm-utils/sleep.d/90clock ===== ===== Mon Jul 2 04:18:24 CDT 2007: running hook: /usr/lib/pm-utils/sleep.d/94cpufreq ===== ===== Mon Jul 2 04:18:24 CDT 2007: running hook: /usr/lib/pm-utils/sleep.d/95led ===== ===== Mon Jul 2 04:18:24 CDT 2007: running hook: /usr/lib/pm-utils/sleep.d/99video ===== Mon Jul 2 04:18:24 CDT 2007: done running suspend hooks.