Wireless (RTL8180L) works in 6.06, not in 7.10 (neither in 8.04)

[mortsahl]

Computer: MSI Mega 180

When using the 6.06 Live CD, configuring the my wi-fi card "just works".

When using the 7.10 Live CD, nothing I can do, even after installing, will get the wi-fi to be recognized.

lspci -vvnn in Dapper 6.06 gives:
01:07.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8180L 802.11b MAC [10ec:8180] (rev 20)
 Subsystem: Actiontec Electronics Inc Unknown device [1668:6109]

[Zameer Manji (zmanji)]

You will need to provide some more information before this bug can be solved. I think that your wireless card is not being detected by the kernel. So I'm asking you to run the following commands in a terminal and attach the resulting files here or paste them here.

uname -a > uname-a.log
cat /proc/version_signature > proc_version_signature.log
sudo lspci -vvnn > lspci-vvnn.log
dmesg > dmesg.log

These commands will allow some one to figure out what model/version your wireless card is and what drivers need to use it.

[mortsahl (mortsahl)]

The following is the requested output from an MSI Mega 180 running 6.06.
Everything works as expected.
The ESSID is detected, the DNS Servers and Search Domains are
automatically detected.

On 7.10 ... there is no wireless detection and even when I supply all
the correct values, the wireless still isn't detected.

sja@politico:~$ uname -a > uname-a.log
sja@politico:~$ cat *log
Linux politico 2.6.15-51-386 #1 PREEMPT Thu Dec 6 20:20:49 UTC 2007 i686
GNU/Linux

sja@politico:~$ cat /proc/version_signature > proc_version_signature.log
cat: /proc/version_signature: No such file or directory

sja@politico:~$ sudo lspci -vvnn >lspci-vvnn.log
Password:
sja@politico:~$ cat ls*log
0000:00:00.0 0600: 10de:01e0 (rev a2)
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Region 0: Memory at d0000000 (32-bit, prefetchable) [size=64M]
        Capabilities: [40] AGP version 2.0
                Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64-
HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4
                Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP+ GART64- 64bit- FW-
Rate=x4
        Capabilities: [60] #08 [2001]

0000:00:00.1 0500: 10de:01eb (rev a2)
        Subsystem: 1462:7960
        Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-

0000:00:00.2 0500: 10de:01ee (rev a2)
        Subsystem: 1462:7960
        Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-

0000:00:00.3 0500: 10de:01ed (rev a2)
        Subsystem: 1462:7960
        Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-

0000:00:00.4 0500: 10de:01ec (rev a2)
        Subsystem: 1462:7960
        Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-

0000:00:00.5 0500: 10de:01ef (rev a2)
        Subsystem: 1462:7960
        Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-

0000:00:01.0 0601: 10de:0060 (rev a4)
        Subsystem: 1462:7960
        Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Capabilities: [48] #08 [01e1]

0000:00:01.1 0c05: 10de:0064 (rev a2)
        Subsystem: 1462:7960
        Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVS...

[Zameer Manji (zmanji)]

Please go to your terminal and type iwconfig and paste the output.

[mortsahl (mortsahl)]

lo no wireless extensions.

eth0 no wireless extensions.

wlan0 802.11b linked ESSID:"ACTIONTEC"
          Mode:Managed Frequency:2.452 GHz Access Point:
00:20:E0:02:50:E1
          Bit Rate=11 Mb/s Sensitivity=80/85
          Retry:on Fragment thr:off
          Power Management:off
          Link Quality=99/100 Signal level=-33 dBm Noise level=-255
dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

sit0 no wireless extensions.

On Sat, 2008-02-02 at 21:23 +0000, Zameer Manji wrote:
> Please go to your terminal and type iwconfig and paste the output.
>

[Zameer Manji (zmanji)]

It seems your card is being detected and placed as wlan0. If 'ACTIONTEC' is not your essid, please run the following commands.

iwconfig essid "linksys" (replace linksys with your essid name)
dhclient wlan0
ping www.google.com
ping 64.233.187.99

Please paste the output here. These commands are manually trying to set your network settings and the ping commands is to see if it works or not.

[mortsahl (mortsahl)]

ACTIONTEC is my essid

(again, all of this on 6.06 and everything works)

On Sat, 2008-02-02 at 22:48 +0000, Zameer Manji wrote:
> It seems your card is being detected and placed as wlan0. If 'ACTIONTEC'
> is not your essid, please run the following commands.
>
> iwconfig essid "linksys" (replace linksys with your essid name)
> dhclient wlan0
> ping www.google.com
> ping 64.233.187.99
>
> Please paste the output here. These commands are manually trying to set
> your network settings and the ping commands is to see if it works or
> not.
>

[Jouni Mettala (jouni-mettala)]

Please paste output of
dhclient wlan0
Thanks

[mortsahl (mortsahl)]

Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

Listening on LPF/wlan0/00:0d:f0:12:4d:77
Sending on LPF/wlan0/00:0d:f0:12:4d:77
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPOFFER from 192.168.1.1
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.2 -- renewal in 35713 seconds.

On Sat, 2008-02-02 at 23:57 +0000, Jouni Mettala wrote:
> Please paste output of
> dhclient wlan0
> Thanks
>

[Jouni Mettala (jouni-mettala)]

After dhclient your wireless gets ip. If wireless still doesn't work please paste output of
ping www.google.com
ping 64.233.187.99
only one or few lines of each.

I don't know why it's not working automatically. It looks more like network-manager bug than kernel one.

[mortsahl (mortsahl)]

Again, the dumps I've provided are from 6.06 where everything does work.

If needed, I can install 7.10 again (where it doesn't work) and provide
the same info.

On Sun, 2008-02-03 at 00:50 +0000, Jouni Mettala wrote:
> After dhclient your wireless gets ip. If wireless still doesn't work please paste output of
> ping www.google.com
> ping 64.233.187.99
> only one or few lines of each.
>
> I don't know why it's not working automatically. It looks more like
> network-manager bug than kernel one.
>

[Jouni Mettala (jouni-mettala)]

Please give same info with 7.10 live. You don't need to install it.

Or even better if you could use development version Hardy Heron Alpha 4 live. You don't need to install it either. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at [WWW] http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

ps. Please don't quote all what we are writing. All comments are saved in launchpad. You have link to this bug in emails from this bug.

[mortsahl (mortsahl)]

Booted with Hardy Heron Alpha 4 live cd. Went to System->Administration->Network ... up comes the Network Settings dialog. The only device options displayed are Wired connection and Point to point connection ... Wireless is not an option so I can't attempt to set it up and run the previous tests.

[Jouni Mettala (jouni-mettala)]

Please run following commands in Hardy Alpha 4 live and attach the logs.

sudo lspci -vvnn > lspci-vvnn.log
dmesg > dmesg.log
iwconfig > iwconfig.log

[mortsahl (mortsahl)]

lspci-vvnn.log ...

00:00.0 Host bridge [0600]: nVidia Corporation nForce2 AGP (different version?) [10de:01e0] (rev a2)
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Latency: 0
 Region 0: Memory at d0000000 (32-bit, prefetchable) [size=64M]
 Capabilities: [40] AGP version 2.0
  Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4
  Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=x1
 Capabilities: [60] HyperTransport: Host or Secondary Interface
  Command: WarmRst+ DblEnd-
  Link Control: CFlE- CST- CFE- <LkFail- Init+ EOC- TXO- <CRCErr=0
  Link Config: MLWI=8bit MLWO=8bit LWI=8bit LWO=8bit
  Revision ID: 0.16

00:00.1 RAM memory [0500]: nVidia Corporation nForce2 Memory Controller 1 [10de:01eb] (rev a2)
 Subsystem: Micro-Star International Co., Ltd. Unknown device [1462:7960]
 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-

00:00.2 RAM memory [0500]: nVidia Corporation nForce2 Memory Controller 4 [10de:01ee] (rev a2)
 Subsystem: Micro-Star International Co., Ltd. Unknown device [1462:7960]
 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-

00:00.3 RAM memory [0500]: nVidia Corporation nForce2 Memory Controller 3 [10de:01ed] (rev a2)
 Subsystem: Micro-Star International Co., Ltd. Unknown device [1462:7960]
 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-

00:00.4 RAM memory [0500]: nVidia Corporation nForce2 Memory Controller 2 [10de:01ec] (rev a2)
 Subsystem: Micro-Star International Co., Ltd. Unknown device [1462:7960]
 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-

00:00.5 RAM memory [0500]: nVidia Corporation nForce2 Memory Controller 5 [10de:01ef] (rev a2)
 Subsystem: Micro-Star International Co., Ltd. Unknown device [1462:7960]
 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-

00:01.0 ISA bridge [0601]: nVidia Corporation nForce2 ISA Bridge [10de:0060] (rev a4)
 Subsystem: Micro-Star International Co., Ltd. Unknown device [1462:7960]
 Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Latency: 0
 Capabilities: [48] HyperTransport: Slave or Primary Interface
  Command: BaseUnitID=1 UnitCnt=15 MastHost- DefDir-
  Link Control 0: CFlE- CST- CFE- <LkFail- Init+ EOC+ TXO- <CRCErr=0
  Link Config 0: MLWI=8bit MLWO=8bi...

[Jouni Mettala (jouni-mettala)]

Part of reporter's lspci -vvnn in 8.04

01:07.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8180L 802.11b MAC [10ec:8180] (rev 20)
 Subsystem: Actiontec Electronics Inc Unknown device [1668:6109]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Latency: 32 (8000ns min, 16000ns max), Cache Line Size: 32 bytes
 Interrupt: pin A routed to IRQ 11
 Region 0: I/O ports at 9000 [size=256]
 Region 1: Memory at df000000 (32-bit, non-prefetchable) [size=256]
 Capabilities: [50] Power Management version 2
  Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0-,D1+,D2+,D3hot+,D3cold+)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-

[Jean-Baptiste Lallement (jibel)]

closing linux-source-2.6.22 because it still exists in newer release.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Sam (sam-machinescience)]

I have the same problem. RTL8180 works fine in 6.06 but not in 8.04. In 6.06 I found the following,
/proc/net/rtl8180
/sys/bus/pci/drivers/rtl8180

It would be great to get any advice!
Sam

[Jean-Baptiste Lallement (jibel)]

Sam, please include the following additional information, as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

[aguitel (aguitel-gmail)]

in 8.04.1 it is working for me

On 9/25/08, Sam <email address hidden> wrote:
> I have the same problem. RTL8180 works fine in 6.06 but not in 8.04. In 6.06
> I found the following,
> /proc/net/rtl8180
> /sys/bus/pci/drivers/rtl8180
>
> It would be great to get any advice!
> Sam
>
> --
> Wireless (RTL8180L) works in 6.06, not in 7.10 (neither in 8.04)
> https://bugs.launchpad.net/bugs/188390
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

[Sam (sam-machinescience)]

I am running 8.04.1 and it still does not seem to be working. Did you do
anything special to set it up?

Sam

On Thu 25 Sep 08, aguitel wrote:
> in 8.04.1 it is working for me
>
> On 9/25/08, Sam <email address hidden> wrote:
> > I have the same problem. RTL8180 works fine in 6.06 but not in 8.04. In 6.06
> > I found the following,
> > /proc/net/rtl8180
> > /sys/bus/pci/drivers/rtl8180
> >
> > It would be great to get any advice!
> > Sam
> >
> > --
> > Wireless (RTL8180L) works in 6.06, not in 7.10 (neither in 8.04)
> > https://bugs.launchpad.net/bugs/188390
> > You received this bug notification because you are a direct subscriber
> > of a duplicate bug.
> >
>
> --
> Wireless (RTL8180L) works in 6.06, not in 7.10 (neither in 8.04)
> https://bugs.launchpad.net/bugs/188390
> You received this bug notification because you are a direct subscriber
> of the bug.

[Jean-Baptiste Lallement (jibel)]

Sam one reason could be some irq conflict, it would help a lot if you could provide the information requested above. BTW you can read https://help.ubuntu.com/community/DebuggingIRQProblems to investigate your problem.

[aguitel (aguitel-gmail)]

sorry about my post

i am running many version's of ubuntu and in intrepid (8.10) it is
working the chipset realtek RTL8180l

sorry

On Thu, Sep 25, 2008 at 6:57 PM, Jean-Baptiste Lallement
<email address hidden> wrote:
> Sam one reason could be some irq conflict, it would help a lot if you
> could provide the information requested above. BTW you can read
> https://help.ubuntu.com/community/DebuggingIRQProblems to investigate
> your problem.
>
> --
> Wireless (RTL8180L) works in 6.06, not in 7.10 (neither in 8.04)
> https://bugs.launchpad.net/bugs/188390
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

[Sam (sam-machinescience)]

Did you install the ndiswrapper or do anything non-standard?

Sam

On Fri 26 Sep 08, aguitel wrote:
> sorry about my post
>
> i am running many version's of ubuntu and in intrepid (8.10) it is
> working the chipset realtek RTL8180l
>
> sorry
>
> On Thu, Sep 25, 2008 at 6:57 PM, Jean-Baptiste Lallement
> <email address hidden> wrote:
> > Sam one reason could be some irq conflict, it would help a lot if you
> > could provide the information requested above. BTW you can read
> > https://help.ubuntu.com/community/DebuggingIRQProblems to investigate
> > your problem.
> >
> > --
> > Wireless (RTL8180L) works in 6.06, not in 7.10 (neither in 8.04)
> > https://bugs.launchpad.net/bugs/188390
> > You received this bug notification because you are a direct subscriber
> > of a duplicate bug.
> >
>
> --
> Wireless (RTL8180L) works in 6.06, not in 7.10 (neither in 8.04)
> https://bugs.launchpad.net/bugs/188390
> You received this bug notification because you are a direct subscriber
> of the bug.

[aguitel (aguitel-gmail)]

in 8.04.1 i install ndiswrapper to work with this chipset

On Fri, Sep 26, 2008 at 5:29 PM, Sam <email address hidden> wrote:
> Did you install the ndiswrapper or do anything non-standard?
>
> Sam
>
> On Fri 26 Sep 08, aguitel wrote:
>> sorry about my post
>>
>> i am running many version's of ubuntu and in intrepid (8.10) it is
>> working the chipset realtek RTL8180l
>>
>> sorry
>>
>> On Thu, Sep 25, 2008 at 6:57 PM, Jean-Baptiste Lallement
>> <email address hidden> wrote:
>> > Sam one reason could be some irq conflict, it would help a lot if you
>> > could provide the information requested above. BTW you can read
>> > https://help.ubuntu.com/community/DebuggingIRQProblems to investigate
>> > your problem.
>> >
>> > --
>> > Wireless (RTL8180L) works in 6.06, not in 7.10 (neither in 8.04)
>> > https://bugs.launchpad.net/bugs/188390
>> > You received this bug notification because you are a direct subscriber
>> > of a duplicate bug.
>> >
>>
>> --
>> Wireless (RTL8180L) works in 6.06, not in 7.10 (neither in 8.04)
>> https://bugs.launchpad.net/bugs/188390
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>
> --
> Wireless (RTL8180L) works in 6.06, not in 7.10 (neither in 8.04)
> https://bugs.launchpad.net/bugs/188390
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[penalvch (penalvch)]

mortsahl, thank you for reporting this and helping make Ubuntu better. Hardy desktop reached EOL on May 12, 2011.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue on a supported release? If so, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in a supported release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]