devices considered down when up and viceversa

Bug #587093 reported by lukyluke
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned
rutilt (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: rutilt

My usb DLink DWL G122 that at lsusb is seen as:

Bus 001 Device 020: ID 07d1:3c0f D-Link System
is not correctly used by the module
rt2800usb that is loaded when I insert it.

I tryed several other possibilities:
rt2870sta through realtech
rt2870sta through ndiswrapper.

None of the previous work
the rt2800usb correctly sees the devices but cannot control it properly.
After a lot of messing around I just discovered that when I ask the utility to turn the device off the ligth switches on.

The same happens through a
sudo ifconfig wlan1 down

So it looks like the drive simply misinterpret the on-off status of the dongle.

I found another report with the same exact symptoms

http://www.linuxforums.org/forum/wireless-internet/157433-please-help-rt2800-no-scan-results.html

I think that the bug is related more to either ifconfig of rt2800usb but I did not find any way to submit the bug for those packages.

My best regards
Description: Ubuntu 10.04 LTS
Release: 10.04

wlan1 IEEE 802.11bgn ESSID:off/any
          Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
          Tx-Power=13 dBm
          Retry long limit:7 RTS thr:off Fragment thr:off
          Encryption key:off
          Power Management:on

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: rutilt 0.18-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Sat May 29 02:12:37 2010
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4)
ProcEnviron:
 LANG=it_IT.utf8
 SHELL=/bin/bash
SourcePackage: rutilt

Revision history for this message
lukyluke (luca-tagliacozzo) wrote :
Changed in rutilt (Ubuntu):
status: New → Invalid
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi lukyluke,

If you could also please 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.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.