SCIENTIFIC-LINUX-USERS Archives

January 2010

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Troy Dawson <[log in to unmask]>
Reply To:
Troy Dawson <[log in to unmask]>
Date:
Thu, 14 Jan 2010 10:05:29 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (84 lines)
Akemi Yagi wrote:
> On Thu, Jan 14, 2010 at 5:38 AM, Dusan Bruncko <[log in to unmask]> wrote:
>>        Hi,
>>
>> My problem:
>> up to now I am  still using ipw3845 driver, no look to the fact, that this
>> one is obsolete, and people use iwl3945. Of course I can able to use both
>> drivers,
>> but the wireless situation is not stable now, time to time I am out from
>> wi-fi
>> connection (seems to randomly).
>> My present kernel is 2.6.18-164.10.1.el5. When I booting all is ok., after
>> some time (randomly) no. The dmesg gave nothing, in really to restart wi-fi
>> I must to switch-off and switch-on wi-fi hard key. I think, that the problem
>> can be connect with iwl3945 behaviour and maybe some crashing with  ipw3945,
>> I do not know...
>> Unfortunately I cannot make rmmod for iwl... drivers if I use ipw3945, and
>> from another side, if I do not use ipw3945, my using iwl... is still not
>> stable.
>> I have Toshiba, Qosmio, G30-155.
>>
>> Can you look no this problem, please?
>>
>> I asked Akima Yagi already and he proposed me to make firstly:
>>
>> for BUSID in $(/sbin/lspci | awk '{ IGNORECASE=1 } /net/ { print $1
>> for cmdsubst> }'); do /sbin/lspci -s $BUSID -m; /sbin/lspci -s $BUSID -n;
>> done
>> 02:00.0 "Ethernet controller" "Intel Corporation" "82573L Gigabit Ethernet
>> Controller" "Toshiba America Info Systems" "Unknown device 0001"
>> 02:00.0 0200: 8086:109a
>> 05:00.0 "Network controller" "Intel Corporation" "PRO/Wireless 3945ABG
>> [Golan] Network Connection" -r02 "Intel Corporation" "Unknown device 1041"
>> 05:00.0 0280: 8086:4222 (rev 02)
> 
> That information confirms that the e1000e and iwl3945 drivers should
> be used with the
> 2.6.18-164.10.1.el5 kernel (quoting Alan).
> 
> This is how you find this out: go to the ELRepo FAQ page at
> http://elrepo.org/tiki/FAQ .
> 
> FAQ Number 4 provides a detailed description on how to identify the
> driver through  the Vendor:Device ID pair.  In your case, it is
> 8086:109a for the ethernet controller and 8086:4222 for the wireless
> device.
> 
> The command:
> 
> grep -i 8086 /lib/modules/*/modules.alias | grep -i 109a
> 
> returns (among other things)
> 
> /lib/modules/2.6.18-164.10.1.el5/modules.alias:alias
> pci:v00008086d0000109Asv*sd*bc*sc*i* e1000e
> 
> Likewise, the other pair gives you iwl3945.
> 
> I realize you have [tried] both ipw3945 and iwl3945. Now that you are
> running the current kernel, I think you should use iwl3945. Make sure
> you have the correct firmware installed.
> 
> Akemi

To make sure you have the correct firmware

   yum install iwlwifi-3945-ucode.noarch
   rpm -qa | grep iwl | sort

Also, you should completely get rid of the ipw3945 stuff, or it will 
keep creeping in and messing things up.

   /etc/rc.d/init.d/ipw3945d stop
   yum remove "*ipw3945*"

It would be a good idea to reboot after this.

Troy
-- 
__________________________________________________
Troy Dawson  [log in to unmask]  (630)840-6468
Fermilab  ComputingDivision/LSCS/CSI/USS Group
__________________________________________________

ATOM RSS1 RSS2