Bug #675330 “[Maverick] rtl819xSE worked 100% in Lucid. After 10...” : Bugs : linux package : Ubuntu

Revision history for this message

William Ray Yeager (wyeager) wrote on 2010-11-14:

#1

Output from uname, version, dmesg and lspci commands as requested. Edit (148.5 KiB, text/plain)
AcpiTables.txt Edit (301.8 KiB, text/plain; charset="utf-8")
AlsaDevices.txt Edit (521 bytes, text/plain; charset="utf-8")
AplayDevices.txt Edit (281 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (56.7 KiB, text/plain; charset="utf-8")
Card0.Amixer.values.txt Edit (1.5 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.0.txt Edit (6.5 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (121.5 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.8 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (531 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (14.3 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (629 bytes, text/plain; charset="utf-8")
PciMultimedia.txt Edit (588 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.8 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.4 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (124 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (116.4 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (264.5 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (188.2 KiB, text/plain; charset="utf-8")

Fabio Marconi (fabiomarconi) on 2010-11-16

affects:

ubuntu → linux (Ubuntu)

Revision history for this message

Fabio Marconi (fabiomarconi) wrote on 2010-11-16:

#2

Hello
can you please try with the latest updated mainline kernel that contain many fixes?
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.37-rc2-maverick/
Thanks
Fabio

Changed in linux (Ubuntu):
status:	New → Incomplete

Revision history for this message

William Ray Yeager (wyeager) wrote on 2010-11-17:

#3

New system logs with new kernel and new driver Edit (187.7 KiB, text/plain)

I'm now running mainline kernel 2.6.37-rc2 with the current Realtek driver. The driver I had been using under the Ubuntu kernel from the repository was 2.6.0015.0127.2010. The current driver from Realtek is 2.6.0018.1025.2010. I'll run this for another day or so and let you know if there are any random connectivity lapses. So far so good.

Revision history for this message

Manoj Iyer (manjo) wrote on 2010-11-17:

#4

The driver was not updated in Maverick, it is the same driver that is available in Lucid.

Revision history for this message

italomaia (italo-maia) wrote on 2010-11-22:

#5

I have this same problem in my CCE notebook. This card:

06:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8191SEvA Wireless LAN Controller (rev 10)

Didn't try it in Lucid, tough.

Revision history for this message

Fabio Marconi (fabiomarconi) wrote on 2010-11-22:

#6

Hello italomaia
can you please try with the latest updated mainline kernel that contain many fixes?
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.37-rc2-maverick/
Thanks
Fabio

Revision history for this message

William Ray Yeager (wyeager) wrote on 2010-11-22:

#7

I've been having a hard time testing this issue under the mainline kernel as there are some other, unrelated stability issues. The random wireless connectivity drops, unfortunately, do seem to be happening still. One big difference, however, was that I was no longer able to successfully reload the driver as a workaround. Under the mainline kernel when I rmmod && modprobe the operation just hangs indefinitely.

One thing I didn't mention in my original post: it seems that the connection only drops while idle. I haven't had problems with it dropping mid-download or while streaming radio. It does drop sometimes while watching streaming video though. I don't know if this happens during or between buffering events.

Is there something else I should test?

Thank you for your help,

William

Fabio Marconi (fabiomarconi) on 2010-11-22

tags:	added: regression-release upstream-tested removed: needs-upstream-testing regression-potential
Changed in linux (Ubuntu):
status:	Incomplete → Confirmed

Revision history for this message

Geoff (fosberry) wrote on 2011-03-11:

#8

Download full text (4.8 KiB)

I've observed something similar, along with a serious regression between the 2.6.35-22-generic kernel and 2.6.35-27-generic.

When I boot with 2.6.35-22-generic, the wireless is mostly usable, and I can often fix it simply by turning off and then back on wireless networking in Network Manager.

With 2.6.35-27-generic, however, it is much worse. After a fresh boot, the network stops working when simply opening my web browser (which typically is restoring 30-40 tabs). And then toggling wireless doesn't seem to fix it, either.

When I have problems in 2.6.35-22-generic,I'd see trace like this in the system log:
Mar 11 12:23:26 purcell kernel: [ 465.663870] ===>rtl8192se_link_change():ieee->iw_mode is 2
Mar 11 12:23:26 purcell kernel: [ 465.720728] =====>rtl8192_set_chan()====ch:1
Mar 11 12:23:26 purcell kernel: [ 465.839173] =====>rtl8192_set_chan()====ch:2
Mar 11 12:23:26 purcell kernel: [ 465.950197] =====>rtl8192_set_chan()====ch:3
Mar 11 12:23:26 purcell kernel: [ 466.069926] =====>rtl8192_set_chan()====ch:4
Mar 11 12:23:26 purcell kernel: [ 466.188502] =====>rtl8192_set_chan()====ch:5
Mar 11 12:23:26 purcell kernel: [ 466.299549] =====>rtl8192_set_chan()====ch:6
Mar 11 12:23:26 purcell kernel: [ 466.418044] =====>rtl8192_set_chan()====ch:7
Mar 11 12:23:26 purcell kernel: [ 466.527829] =====>rtl8192_set_chan()====ch:8
Mar 11 12:23:26 purcell kernel: [ 466.637588] =====>rtl8192_set_chan()====ch:9
Mar 11 12:23:27 purcell kernel: [ 466.748674] =====>rtl8192_set_chan()====ch:10
Mar 11 12:23:27 purcell kernel: [ 466.867169] =====>rtl8192_set_chan()====ch:11
Mar 11 12:23:27 purcell kernel: [ 466.978247] =====>rtl8192_set_chan()====ch:12

but often the problem resolved itself reasonably quickly, so it was mostly usable.

With 2.6.35-27-generic, however, I also see lots of lines like this:
Mar 11 12:12:01 purcell kernel: [ 255.633584] rtl819xSE:No more TX desc@1, ring->idx = 0,idx = 0, skblen = 0x44 queuelen=0
Mar 11 12:12:02 purcell kernel: [ 256.628638] rtl819xSE:No more TX desc@1, ring->idx = 0,idx = 0, skblen = 0x44 queuelen=0
Mar 11 12:12:03 purcell kernel: [ 257.628675] rtl819xSE:No more TX desc@1, ring->idx = 0,idx = 0, skblen = 0x44 queuelen=0
Mar 11 12:12:04 purcell kernel: [ 258.636168] rtl819xSE:No more TX desc@1, ring->idx = 0,idx = 0, skblen = 0x44 queuelen=0
Mar 11 12:12:05 purcell kernel: [ 259.633734] rtl819xSE:No more TX desc@1, ring->idx = 0,idx = 0, skblen = 0x44 queuelen=0
Mar 11 12:12:06 purcell kernel: [ 260.631212] rtl819xSE:No more TX desc@1, ring->idx = 0,idx = 0, skblen = 0x44 queuelen=0
Mar 11 12:12:07 purcell kernel: [ 261.637029] rtl819xSE:No more TX desc@1, ring->idx = 0,idx = 0, skblen = 0x44 queuelen=0

Sometimes the set_chan messages might be interspersed with the above like this:
Mar 11 12:11:59 purcell kernel: [ 253.637275] rtl819xSE:No more TX desc@1, ring->idx = 0,idx = 0, skblen = 0x44 queuelen=0
Mar 11 12:12:00 purcell kernel: [ 253.975369] rtl819xSE:No more TX desc@6, ring->idx = 0,idx = 0, skblen = 0x18 queuelen=0
Mar 11 12:12:00 purcell kernel: [ 253.975380] rtl819xSE:No more TX desc@6, ring->idx = 0,idx = 0, skblen = 0x18 queuelen=0
Mar 11 12:12:00 purcell kernel: [ 253.975389] ===>...

I've observed something similar, along with a serious regression between the 2.6.35-22-generic kernel and 2.6.35-27-generic.

When I boot with 2.6.35-22-generic, the wireless is mostly usable, and I can often fix it simply by turning off and then back on wireless networking in Network Manager.

With 2.6.35-27-generic, however, it is much worse. After a fresh boot, the network stops working when simply opening my web browser (which typically is restoring 30-40 tabs). And then toggling wireless doesn't seem to fix it, either.

When I have problems in 2.6.35-22-generic,I'd see trace like this in the system log:
Mar 11 12:23:26 purcell kernel: [  465.663870] ===>rtl8192se_link_change():ieee->iw_mode is 2
Mar 11 12:23:26 purcell kernel: [  465.720728] =====>rtl8192_set_chan()====ch:1
Mar 11 12:23:26 purcell kernel: [  465.839173] =====>rtl8192_set_chan()====ch:2
Mar 11 12:23:26 purcell kernel: [  465.950197] =====>rtl8192_set_chan()====ch:3
Mar 11 12:23:26 purcell kernel: [  466.069926] =====>rtl8192_set_chan()====ch:4
Mar 11 12:23:26 purcell kernel: [  466.188502] =====>rtl8192_set_chan()====ch:5
Mar 11 12:23:26 purcell kernel: [  466.299549] =====>rtl8192_set_chan()====ch:6
Mar 11 12:23:26 purcell kernel: [  466.418044] =====>rtl8192_set_chan()====ch:7
Mar 11 12:23:26 purcell kernel: [  466.527829] =====>rtl8192_set_chan()====ch:8
Mar 11 12:23:26 purcell kernel: [  466.637588] =====>rtl8192_set_chan()====ch:9
Mar 11 12:23:27 purcell kernel: [  466.748674] =====>rtl8192_set_chan()====ch:10
Mar 11 12:23:27 purcell kernel: [  466.867169] =====>rtl8192_set_chan()====ch:11
Mar 11 12:23:27 purcell kernel: [  466.978247] =====>rtl8192_set_chan()====ch:12

but often the problem resolved itself reasonably quickly, so it was mostly usable.

With 2.6.35-27-generic, however, I also see lots of lines like this:
Mar 11 12:12:01 purcell kernel: [  255.633584] rtl819xSE:No more TX desc@1, ring->idx = 0,idx = 0, skblen = 0x44 queuelen=0
Mar 11 12:12:02 purcell kernel: [  256.628638] rtl819xSE:No more TX desc@1, ring->idx = 0,idx = 0, skblen = 0x44 queuelen=0
Mar 11 12:12:03 purcell kernel: [  257.628675] rtl819xSE:No more TX desc@1, ring->idx = 0,idx = 0, skblen = 0x44 queuelen=0
Mar 11 12:12:04 purcell kernel: [  258.636168] rtl819xSE:No more TX desc@1, ring->idx = 0,idx = 0, skblen = 0x44 queuelen=0
Mar 11 12:12:05 purcell kernel: [  259.633734] rtl819xSE:No more TX desc@1, ring->idx = 0,idx = 0, skblen = 0x44 queuelen=0
Mar 11 12:12:06 purcell kernel: [  260.631212] rtl819xSE:No more TX desc@1, ring->idx = 0,idx = 0, skblen = 0x44 queuelen=0
Mar 11 12:12:07 purcell kernel: [  261.637029] rtl819xSE:No more TX desc@1, ring->idx = 0,idx = 0, skblen = 0x44 queuelen=0

Sometimes the set_chan messages might be interspersed with the above like this:
Mar 11 12:11:59 purcell kernel: [  253.637275] rtl819xSE:No more TX desc@1, ring->idx = 0,idx = 0, skblen = 0x44 queuelen=0
Mar 11 12:12:00 purcell kernel: [  253.975369] rtl819xSE:No more TX desc@6, ring->idx = 0,idx = 0, skblen = 0x18 queuelen=0
Mar 11 12:12:00 purcell kernel: [  253.975380] rtl819xSE:No more TX desc@6, ring->idx = 0,idx = 0, skblen = 0x18 queuelen=0
Mar 11 12:12:00 purcell kernel: [  253.975389] ===>rtl8192se_link_change():ieee->iw_mode is 2
Mar 11 12:12:00 purcell kernel: [  254.037687] =====>rtl8192_set_chan()====ch:1
Mar 11 12:12:00 purcell kernel: [  254.047766] rtl819xSE:No more TX desc@6, ring->idx = 0,idx = 0, skblen = 0x3e queuelen=0
Mar 11 12:12:00 purcell kernel: [  254.047774] rtl819xSE:No more TX desc@6, ring->idx = 0,idx = 0, skblen = 0x3e queuelen=0
Mar 11 12:12:00 purcell kernel: [  254.154752] =====>rtl8192_set_chan()====ch:2
Mar 11 12:12:00 purcell kernel: [  254.164822] rtl819xSE:No more TX desc@6, ring->idx = 0,idx = 0, skblen = 0x3e queuelen=0
Mar 11 12:12:00 purcell kernel: [  254.164829] rtl819xSE:No more TX desc@6, ring->idx = 0,idx = 0, skblen = 0x3e queuelen=0
Mar 11 12:12:00 purcell kernel: [  254.266940] =====>rtl8192_set_chan()====ch:3
Mar 11 12:12:00 purcell kernel: [  254.277012] rtl819xSE:No more TX desc@6, ring->idx = 0,idx = 0, skblen = 0x3e queuelen=0
Mar 11 12:12:00 purcell kernel: [  254.277022] rtl819xSE:No more TX desc@6, ring->idx = 0,idx = 0, skblen = 0x3e queuelen=0
Mar 11 12:12:00 purcell kernel: [  254.384154] =====>rtl8192_set_chan()====ch:4
Mar 11 12:12:00 purcell kernel: [  254.394227] rtl819xSE:No more TX desc@6, ring->idx = 0,idx = 0, skblen = 0x3e queuelen=0
Mar 11 12:12:00 purcell kernel: [  254.394235] rtl819xSE:No more TX desc@6, ring->idx = 0,idx = 0, skblen = 0x3e queuelen=0

At one point I tried getting and building a driver from the realtek site with -27, but I saw the same errors. Reverting to -22 is *much* better. The connection still drops sometimes (and I've not detected a pattern to it yet), but it is mostly usable. On -27, I find it unusable.

I'm running Maverick 10.10 on a Thinkpad T510.

Revision history for this message

William Ray Yeager (wyeager) wrote on 2011-05-04:

#9

I upgraded to Natty in hopes that issues with the realtek driver would be resolved. Unfortunately, the intermittent connections persist. I have now switched to using ndiswrapper with M$ Windows drivers. I now have no problems with my wifi connection. The problem seems to lie with the native linux driver.

Revision history for this message

filsd (filsdd) wrote on 2011-05-18:

#10

I have this problem to!
How can I resolve it?

Revision history for this message

William Ray Yeager (wyeager) wrote on 2011-05-18:

#11

@filsd: There are a few good forum threads that will help you:

https://help.ubuntu.com/community/WifiDocs/Driver/Ndiswrapper
http://ubuntuforums.org/showthread.php?t=1267961&page=12

Revision history for this message

Jose Marquez (ubuntu-hackwater) wrote on 2011-06-28:

#12

@filsd: The latest Realtek drivers seem to do the trick. I posted the driver package they sent me on page 14 of the forum thread William Ray Yeager links to: http://ubuntuforums.org/showthread.php?t=1267961&page=14

Revision history for this message

filsd (filsdd) wrote on 2011-06-28:

#13

Thanks Jose and William. But some people have kernel lockups and this is my workstation. Having a working machine is way more important than WiFi =P. Nice to know that on 11.10 this will be fixed.

Until 11.10, I can use wired cabes. =)

Revision history for this message

penalvch (penalvch) wrote on 2012-03-31:

#14

William Ray Yeager, thank you for reporting this and helping make Ubuntu better. This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? 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 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.

Changed in linux (Ubuntu):
status:	Confirmed → Incomplete

Revision history for this message

Mario Ss (mariost6) wrote on 2012-03-31: Re: [Bug 675330] Re: [Maverick] rtl819xSE worked 100% in Lucid. After 10.10 upgrade became only 80% stable.

#15

Download full text (4.7 KiB)

I am no longer using Ubuntu. But I believe the problem was caused by using
wicd instead of NM. On earlier versions it was possible as much as i
remember.

On Sat, Mar 31, 2012 at 5:07 AM, Christopher M. Penalver <
<email address hidden>> wrote:

> William Ray Yeager, thank you for reporting this and helping make Ubuntu
> better. This bug was reported a while ago and there hasn't been any
> activity in it recently. We were wondering if this is still an issue?
> 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 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.
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/675330
>
> Title:
> [Maverick] rtl819xSE worked 100% in Lucid. After 10.10 upgrade became
> only 80% stable.
>
> Status in “linux” package in Ubuntu:
> Incomplete
>
> Bug description:
> After upgrading from 10.04 to 10.10 I noticed that I'd loose my wifi
> connection unpredictably. This never happened with 10.04. I'd revert
> to Lucid but there are several improvements in 10.10 that I enjoy.
> Sometimes it happens as soon as 10 minutes after connection and
> sometimes I can stay connected for hours with no issues. Hard
> ethernet connection works just fine. At first I'd reboot the machine
> to regain connectivity but then I discovered that all I had to do was
> rmmod and modprobe the r8192se_pci module. Thank you for your help!
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.10
> Package: linux-image-2.6.35-22-generic 2.6.35-22.35
> Regression: Yes
> Reproducible: Yes
> ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
> Uname: Linux 2.6.35-22-generic i686
> AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
> Architecture: i386
> ArecordDevices:
> **** List of CAPTURE Hardware Devices ****
> card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: wyeager 1959 F.... pulseaudio
> /dev/snd/pcmC0D0p: wyeager 1959 F...m pulseaudio
> CRDA: Error: [Errno 2] No such file or directory
> Card0.Amixer.info:
> Card hw:0 'Intel'/'HDA Intel at 0xf2620000 irq 46'
> Mix...

I am no longer using Ubuntu. But I believe the problem was caused by using
wicd instead of NM. On earlier versions it was possible as much as i
remember.

On Sat, Mar 31, 2012 at 5:07 AM, Christopher M. Penalver <
christopher.penalver@gmx.com> wrote:

> William Ray Yeager, thank you for reporting this and helping make Ubuntu
> better. This bug was reported a while ago and there hasn't been any
> activity in it recently. We were wondering if this is still an issue?
> 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 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.
>
> ** Changed in: linux (Ubuntu)
>       Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/675330
>
> Title:
>  [Maverick] rtl819xSE worked 100% in Lucid. After 10.10 upgrade became
>  only 80% stable.
>
> Status in “linux” package in Ubuntu:
>   Incomplete
>
> Bug description:
>  After upgrading from 10.04 to 10.10 I noticed that I'd loose my wifi
>  connection unpredictably.  This never happened with 10.04.  I'd revert
>  to Lucid but there are several improvements in 10.10 that I enjoy.
>  Sometimes it happens as soon as 10 minutes after connection and
>  sometimes I can stay connected for hours with no issues.  Hard
>  ethernet connection works just fine.  At first I'd reboot the machine
>  to regain connectivity but then I discovered that all I had to do was
>  rmmod and modprobe the r8192se_pci module.  Thank you for your help!
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 10.10
>  Package: linux-image-2.6.35-22-generic 2.6.35-22.35
>  Regression: Yes
>  Reproducible: Yes
>  ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
>  Uname: Linux 2.6.35-22-generic i686
>  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
>  Architecture: i386
>  ArecordDevices:
>   **** List of CAPTURE Hardware Devices ****
>   card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
>     Subdevices: 1/1
>     Subdevice #0: subdevice #0
>  AudioDevicesInUse:
>   USER        PID ACCESS COMMAND
>   /dev/snd/controlC0:  wyeager    1959 F.... pulseaudio
>   /dev/snd/pcmC0D0p:   wyeager    1959 F...m pulseaudio
>  CRDA: Error: [Errno 2] No such file or directory
>  Card0.Amixer.info:
>   Card hw:0 'Intel'/'HDA Intel at 0xf2620000 irq 46'
>     Mixer name : 'Conexant CX20561 (Hermosa)'
>     Components : 'HDA:14f15051,17aa20ff,00100000'
>     Controls      : 14
>     Simple ctrls  : 7
>  Card29.Amixer.info:
>   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30,
> fw 7XHT22WW-1.04'
>     Mixer name : 'ThinkPad EC 7XHT22WW-1.04'
>     Components : ''
>     Controls      : 1
>     Simple ctrls  : 1
>  Card29.Amixer.values:
>   Simple mixer control 'Console',0
>     Capabilities: pswitch pswitch-joined penum
>     Playback channels: Mono
>     Mono: Playback [on]
>  Date: Sun Nov 14 14:04:38 2010
>  HibernationDevice: RESUME=UUID=3c111303-1405-4e62-9a87-acccf37d48be
>  MachineType: LENOVO 7454CTO
>  ProcCmdLine: root=UUID=fac571b4-c6fe-4a98-b8d6-43349f2a4af2 ro quiet
> splash
>  ProcEnviron:
>   LANGUAGE=
>   PATH=(custom, user)
>   LANG=en_US.UTF-8
>   SHELL=/bin/bash
>  RelatedPackageVersions: linux-firmware 1.38
>  SourcePackage: linux
>  WpaSupplicantLog:
>
>  dmi.bios.date: 08/12/2009
>  dmi.bios.vendor: LENOVO
>  dmi.bios.version: 6DET57WW (3.07 )
>  dmi.board.name: 7454CTO
>  dmi.board.vendor: LENOVO
>  dmi.board.version: Not Available
>  dmi.chassis.asset.tag: No Asset Information
>  dmi.chassis.type: 10
>  dmi.chassis.vendor: LENOVO
>  dmi.chassis.version: Not Available
>  dmi.modalias:
> dmi:bvnLENOVO:bvr6DET57WW(3.07):bd08/12/2009:svnLENOVO:pn7454CTO:pvrThinkPadX200:rvnLENOVO:rn7454CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
>  dmi.product.name: 7454CTO
>  dmi.product.version: ThinkPad X200
>  dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/675330/+subscriptions
>

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-05-31:

#16

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

Changed in linux (Ubuntu):
status:	Incomplete → Expired

Ubuntu
linux package

[Maverick] rtl819xSE worked 100% in Lucid. After 10.10 upgrade became only 80% stable.

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntulinux package

[Maverick] rtl819xSE worked 100% in Lucid. After 10.10 upgrade became only 80% stable.

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package