Activity log for bug #95343

Date Who What changed Old value New value Message
2007-03-24 05:24:00 funkadelic bug added bug
2007-03-24 05:58:00 funkadelic description I somehow got this card working for one boot by toggling the checkbox in Admin> Network off and then on again. After reboot, my router is still detected in Network, but it no longer works and I no longer see ra0 in network monitor. The toggling trick no longer works, either. lspci -v output: 02:04.0 Network controller: RaLink RT2561/RT61 802.11g PCI Subsystem: Linksys WMP54G ver 4.1 Flags: bus master, slow devsel, latency 32, IRQ 18 Memory at fead0000 (32-bit, non-prefetchable) [size=32K] Capabilities: <access denied> This card was working flawlessly in Herd 4 if that helps. It has never worked with network manager (roaming mode). ProblemType: Bug Architecture: i386 Date: Sat Mar 24 01:19:41 2007 DistroRelease: Ubuntu 7.04 Uname: Linux bozo-desktop 2.6.20-12-generic #2 SMP Wed Mar 21 20:55:46 UTC 2007 i686 GNU/Linux I got this card working by toggling the checkbox in Admin> Network off and then on again. After reboot, my router is still detected in Network, but it no longer works and I no longer see ra1 in network monitor. If I toggle the checkbox again, it sometimes works. lspci -v output: 02:04.0 Network controller: RaLink RT2561/RT61 802.11g PCI Subsystem: Linksys WMP54G ver 4.1 Flags: bus master, slow devsel, latency 32, IRQ 18 Memory at fead0000 (32-bit, non-prefetchable) [size=32K] Capabilities: <access denied> This card was working flawlessly in Herd 4 if that helps. It has never worked with network manager (roaming mode). ProblemType: Bug Architecture: i386 Date: Sat Mar 24 01:19:41 2007 DistroRelease: Ubuntu 7.04 Uname: Linux bozo-desktop 2.6.20-12-generic #2 SMP Wed Mar 21 20:55:46 UTC 2007 i686 GNU/Linux
2007-03-24 05:58:00 funkadelic title Ralink wifi card works then fails after reboot in Feisty Beta Ralink wifi card works but must be reset each boot
2007-04-01 01:15:10 Tony Rick bug added attachment 'syslog' (syslog with wifi card startup failure)
2007-04-04 00:15:13 Brian Murray None: status Unconfirmed Needs Info
2007-04-04 00:15:13 Brian Murray None: assignee brian-murray
2007-04-04 00:15:13 Brian Murray None: statusexplanation Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information. Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), 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' 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!
2007-04-04 12:11:51 KaT bug added attachment 'dmesg.log' (dmesg.log)
2007-04-04 12:13:28 KaT bug added attachment 'lspci-vvnn.log' (lspci-vvnn.log)
2007-04-05 16:21:28 chris_van_ackeren marked as duplicate 78037
2008-01-24 18:24:22 oponek changed duplicate marker 78037 134660