Bug#944257: linux-image-5.3.0-1-amd64: Does not wake up after suspend-to-RAM
Package: src:linux Version: 5.3.7-1 Severity: important Dear Maintainer, * What led up to the situation? Upgrade to 5 kernel * What exactly did you do (or not do) that was effective (or ineffective)? Upgrade to 5.1, 5.2 and 5.3 kernel * What was the outcome of this action? System still does not wake up after suspend to RAM * What outcome did you expect instead? Normal wake-up -- Package-specific info: ** Version: Linux version 5.3.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 9.2.1 20191008 (Debian 9.2.1-9)) #1 SMP Debian 5.3.7-1 (2019-10-19) ** Command line: BOOT_IMAGE=/boot/vmlinuz-5.3.0-1-amd64 root=UUID=99607924-e7e4-49c3-902e-6fabdeb450f1 ro quiet ** Tainted: WOE (12800) * Taint on warning. * Out-of-tree module has been loaded. * Unsigned module has been loaded. ** Kernel log: [ 101.442927] OOM killer disabled. [ 101.443013] PM: Marking nosave pages: [mem 0x-0x0fff] [ 101.443014] PM: Marking nosave pages: [mem 0x00058000-0x00058fff] [ 101.443014] PM: Marking nosave pages: [mem 0x0009d000-0x000f] [ 101.443016] PM: Marking nosave pages: [mem 0xc4a7f000-0xc4aa9fff] [ 101.443017] PM: Marking nosave pages: [mem 0xce3ae000-0xcfffdfff] [ 101.443120] PM: Marking nosave pages: [mem 0xc000-0x] [ 101.443449] PM: Basic memory bitmaps created [ 101.443490] PM: Preallocating image memory... done (allocated 784530 pages) [ 101.738515] PM: Allocated 3138120 kbytes in 0.29 seconds (10821.10 MB/s) [ 101.738515] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 101.740910] printk: Suspending console(s) (use no_console_suspend to debug) [ 101.741064] wlan0: deauthenticating from --- by local choice (Reason: 3=DEAUTH_LEAVING) [ 101.741186] azx_single_send_cmd: 15 callbacks suppressed [ 102.345654] ACPI: EC: interrupt blocked [ 102.364395] ACPI: Preparing to enter system sleep state S4 [ 102.368754] ACPI: EC: event blocked [ 102.368755] ACPI: EC: EC stopped [ 102.368755] PM: Saving platform NVS memory [ 102.368970] Disabling non-boot CPUs ... [ 102.369264] IRQ 130: no longer affine to CPU1 [ 102.370282] smpboot: CPU 1 is now offline [ 102.374004] smpboot: CPU 2 is now offline [ 102.376929] IRQ 127: no longer affine to CPU3 [ 102.376933] IRQ 129: no longer affine to CPU3 [ 102.377951] smpboot: CPU 3 is now offline [ 102.382146] PM: Creating hibernation image: [ 102.581977] PM: Need to copy 778090 pages [ 102.581980] PM: Normal pages needed: 778090 + 1024, available pages: 3353232 [ 102.382709] PM: Restoring platform NVS memory [ 102.382792] ACPI: EC: EC started [ 102.383874] Enabling non-boot CPUs ... [ 102.383945] x86: Booting SMP configuration: [ 102.383946] smpboot: Booting Node 0 Processor 1 APIC 0x2 [ 102.385740] CPU1 is up [ 102.385782] smpboot: Booting Node 0 Processor 2 APIC 0x1 [ 102.387629] CPU2 is up [ 102.387672] smpboot: Booting Node 0 Processor 3 APIC 0x3 [ 102.389050] CPU3 is up [ 102.391319] ACPI: Waking up from system sleep state S4 [ 102.403587] ACPI: EC: interrupt unblocked [ 102.403814] pcieport :00:1c.0: Intel SPT PCH root port ACS workaround enabled [ 102.404092] pcieport :00:1c.2: Intel SPT PCH root port ACS workaround enabled [ 102.543326] usb usb1: root hub lost power or was reset [ 102.543328] usb usb2: root hub lost power or was reset [ 102.544365] ACPI: EC: event unblocked [ 102.554978] sd 1:0:0:0: [sda] Starting disk [ 102.855353] snd_hda_codec_generic hdaudioC0D2: Unable to sync register 0x2f0d00. -5 [ 102.855478] snd_hda_codec_generic hdaudioC0D2: Unable to sync register 0x2f0d00. -5 [ 102.870645] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 102.872165] ata2.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [ 102.872171] ata2.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [ 102.872887] ata2.00: ACPI cmd ef/10:09:00:00:00:a0 (SET FEATURES) succeeded [ 102.873686] ata2.00: supports DRM functions and may not be fully accessible [ 102.878752] ata2.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [ 102.878758] ata2.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [ 102.879469] ata2.00: ACPI cmd ef/10:09:00:00:00:a0 (SET FEATURES) succeeded [ 102.880264] ata2.00: supports DRM functions and may not be fully accessible [ 102.883745] ata2.00: configured for UDMA/133 [ 102.903241] usb 1-5: reset full-speed USB device number 2 using xhci_hcd [ 103.129017] snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x1f0e00. -5 [ 103.129363] snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x1f0e00. -5 [ 103.179256] usb 1-7: reset full-speed USB device number 3 using xhci_hcd [ 103.260446] psmouse serio1: synaptics: queried max coordinates: x [..5712], y [..4780] [ 103.291681] psmouse serio1: synaptics: queried min coordinates: x [1232..], y [1074..] [ 103.455152] usb 1-8: reset high-speed USB device number 4 using xhci_hcd [ 103.611731] PM:
Bug#814074: taskcoach: It fails to launch (dependence or miscofiguration related to zope.interface)
Package: taskcoach Version: 1.4.3-1 Severity: normal Dear Maintainer, Hereby I include the output: == Traceback (most recent call last): File "/usr/bin/taskcoach", line 72, in start() File "/usr/bin/taskcoach", line 63, in start app = application.Application(options, args) File "/usr/lib/python2.7/dist-packages/taskcoachlib/patterns/singleton.py", line 29, in __call__ class_.instance = super(Singleton, class_).__call__(*args, **kwargs) File "/usr/lib/python2.7/dist- packages/taskcoachlib/application/application.py", line 117, in __init__ self.initTwisted() File "/usr/lib/python2.7/dist- packages/taskcoachlib/application/application.py", line 159, in initTwisted from twisted.internet import wxreactor File "/usr/lib/python2.7/dist-packages/twisted/__init__.py", line 55, in _checkRequirements() File "/usr/lib/python2.7/dist-packages/twisted/__init__.py", line 42, in _checkRequirements raise ImportError(required + ".") ImportError: Twisted requires zope.interface 3.6.0 or later. == python-zope.interface 4.1.3-1 is installed In another machine, same version of taskcoach (and also same distribution: debian stretch) is installed and working. Thanks a lot, Wenceslao -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages taskcoach depends on: ii fonts-dejavu 2.35-1 ii libxss1 1:1.2.2-1 ii python 2.7.11-1 ii python-chardet 2.3.0-1 ii python-dateutil 2.4.2-1 ii python-keyring 7.3-1 ii python-lockfile 1:0.10.2-2 ii python-pyparsing 2.0.3+dfsg1-1 ii python-squaremap 1:1.0.4-2 ii python-twisted-core 15.5.0-4 ii python-wxgtk3.0 3.0.2.0+dfsg-1+b1 ii python-wxversion 3.0.2.0+dfsg-1 ii python-xdg 0.25-4 ii x11-utils7.7+3 ii xdg-utils1.1.1-1 Versions of packages taskcoach recommends: ii libavahi-compat-libdnssd1 0.6.32~rc+dfsg-1 ii libgnome-2-0 2.32.1-5 ii python-notify 0.1.1-4 Versions of packages taskcoach suggests: ii espeak 1.48.04+dfsg-2 pn python-kde4 -- no debconf information
Bug#741023: xpra attach :100 leads to 'segmentation fault'
Hi, You are probably right. The jessie xpra package suggests to install python-pyopencl (which I installed). If I uninstall it (even reinstalling xpra), xpra works Best Wenceslao On 11/03/14 01:57, Antoine Martin wrote: On 11/03/14 07:15, Dmitry Smirnov wrote: Hi Wenceslao, Please avoid using HTML formatting (it doesn't look good in bug report) and use only plain-text emails. On Mon, 10 Mar 2014 14:05:23 Wenceslao González-Viñas wrote: It works!!! How can the problem be fixed (not temporarily)? Please try with --opengl=no (it will probably work). No, that's unlikely. OpenGL and OpenCL are totally different things. It looks to me like the opencl package installed is not the one that the module was built against. -- Wenceslao González-Viñas e-mail: w...@unav.es http://fisica.unav.es/gmm/ FAX:+34 948.425.740 phn:+34 948.425.600 ext: 806500 / 806603 Depto. Física y Matemática Aplicada Facultad de Ciencias Universidad de Navarra c/Irunlarrea 1 E-31008 Pamplona, Navarra, Spain -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741023: xpra attach :100 leads to 'segmentation fault'
I removed the /tm/xpra and reinstalled xpra 0.11.4 I removed all the old
lock files of Xwindow and I killed the Xorg-for-Xpra processes. I put
the xpra.conf with debugging.
I put 'xpra start :20' giving rise to the attached file :20.log
After setting
DISPLAY=:20 xterm
I put 'xpra attach :20' and I get the error message copied on the
attached file errormessage.txt
If after that I put 'xpra stop :20' I get the error message: 'connection
failed: [Errno 111] Connection refused'
Thanks in advanced !
On 08/03/14 04:25, Dmitry Smirnov wrote:
On Sat, 8 Mar 2014 07:56:26 Antoine Martin wrote:
From the log files that are provided, the poster's error is that there
is an X11 server already running on the display he is trying to start.
That's what the error message says, almost word for word:
Make sure an X server isn't already running
If we trust reporter I think he claims that computer was rebooted just prior
he reproduced the problem...
There might be other problems too, but they are occluded by this one.
Indeed.
--
Wenceslao González-Viñas
e-mail: w...@unav.es
http://fisica.unav.es/gmm/
FAX:+34 948.425.740
phn:+34 948.425.600 ext: 806500 / 806603
Depto. Física y Matemática Aplicada
Facultad de Ciencias
Universidad de Navarra
c/Irunlarrea 1
E-31008 Pamplona, Navarra, Spain
2014-03-10 11:44:22,886 netifaces loaded sucessfully
2014-03-10 11:44:22,886 successfully loaded socket C library from libc.so.6
2014-03-10 11:44:22,887 get_interface_index()
2014-03-10 11:44:22,887 iface_index()=-1
2014-03-10 11:44:22,887 AvahiPublisher('Xpra ssh :20', 22, '_xpra._tcp.', '', '', ['username=', 'display=:20', 'mode=ssh'], -1)
X.Org X Server 1.15.0
Release Date: 2013-12-27
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.12-1-amd64 x86_64 Debian
Current Operating System: Linux telcontar 3.11-2-amd64 #1 SMP Debian 3.11.10-1 (2013-12-04) x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.11-2-amd64 root=UUID=e042172f-0b96-4096-bf15-78423f411bb8 ro quiet
Build Date: 06 February 2014 03:20:45PM
xorg-server 2:1.15.0-2 (http://www.debian.org/support)
Current version of pixman: 0.32.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: /home//.xpra/Xorg.:20.log, Time: Mon Mar 10 11:44:22 2014
(++) Using config file: /etc/xpra/xorg.conf
(==) Using system config directory /usr/share/X11/xorg.conf.d
setversion 1.4 failed: Permission denied
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension SECURITY
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension Present
Initializing built-in extension DRI3
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension SELinux
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
setversion 1.4 failed: Permission denied
2014-03-10 11:44:23,194 X11 extension Composite event_base=0
2014-03-10 11:44:23,194 X11 extension DAMAGE event_base=91
2014-03-10 11:44:23,195 ewmh selection owner for WM_S0: 0
2014-03-10 11:44:23,195 compositing window manager _NEW_WM_CM_S0: 0
2014-03-10 11:44:23,195 _call(True,built-in method XGetWindowProperty of xpra.x11.bindings.window_bindings.X11WindowBindings object at 0x7fab543b71e0,(365L, '_NET_SUPPORTING_WM_CHECK', 'WINDOW'),{}) _NET_SUPPORTING_WM_CHECK
2014-03-10 11:44:23,195 Missing property _NET_SUPPORTING_WM_CHECK (window)
2014-03-10 11:44:23,195 _NET_SUPPORTING_WM_CHECK for screen 0: None
2014-03-10 11:44:23,196 found XRandR extension version 1.4
2014-03-10 11:44:23,199 X11 extension Composite event_base=0
2014-03-10 11:44:23,199 ServerBase.__init__()
2014-03-10 11:44:23,199 ServerCore.__init__()
2014-03-10 11:44:23,199 initializing packet handlers
2014-03-10 11:44:23,199 ServerBase.__init__
Bug#741023: xpra attach :100 leads to 'segmentation fault'
You are right, I now do 'export DISPLAY=:0'
and after 'xpra attach :20' I get the error message in the attached
file with the final 'segmentation fault' ...
On 10/03/14 12:21, Antoine Martin
wrote:
On 10/03/14 17:53, Wenceslao
Gonzlez-Vias wrote:
/usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display
The client application requires access to your local display.
You are either trying to run it from a non graphical login, or you
have changed the DISPLAY environment variable.
(more than likely the latter)
--
Wenceslao Gonzlez-Vias
e-mail: w...@unav.es
http://fisica.unav.es/gmm/
FAX:+34 948.425.740
phn:+34 948.425.600 ext: 806500 / 806603
Depto. Fsica y Matemtica Aplicada
Facultad de Ciencias
Universidad de Navarra
c/Irunlarrea 1
E-31008 Pamplona, Navarra, Spain
xpra client version 0.11.4
2014-03-10 12:28:52,611 cyxor loaded
2014-03-10 12:28:52,612 importing ('Keyboard',) from
xpra.platform.xposix.keyboard (required=True)
2014-03-10 12:28:52,613 Keyboard=class
'xpra.platform.xposix.keyboard.Keyboard'
2014-03-10 12:28:52,613 importing ('do_ready', 'do_init', 'ClientExtras',
'get_native_tray_menu_helper_classes', 'get_native_tray_classes',
'get_native_system_tray_classes', 'get_native_notifier_classes', 'system_bell')
from xpra.platform.xposix.gui (required=False)
2014-03-10 12:28:52,613 do_ready=function do_ready at 0x7f0162ce6398
(unchanged)
2014-03-10 12:28:52,613 do_init=function do_init at 0x7f0162ce62a8 (unchanged)
2014-03-10 12:28:52,613 ClientExtras=class
'xpra.platform.xposix.gui.ClientExtras'
2014-03-10 12:28:52,613 get_native_tray_menu_helper_classes=function
get_native_tray_menu_helper_classes at 0x7f0162ce6410 (unchanged)
2014-03-10 12:28:52,613 get_native_tray_classes=function
get_native_tray_classes at 0x7f0162ce6848
2014-03-10 12:28:52,613 get_native_system_tray_classes=function
get_native_system_tray_classes at 0x7f0162ce68c0
2014-03-10 12:28:52,613 get_native_notifier_classes=function
get_native_notifier_classes at 0x7f0162ce67d0
2014-03-10 12:28:52,613 system_bell=function system_bell at 0x7f0162ce6938
2014-03-10 12:28:52,687 loading codecs
2014-03-10 12:28:52,687 codec_import_check('PIL', 'Python Imaging Library',
'PIL', 'PIL', ('Image',))
2014-03-10 12:28:52,687 PIL found, will check for ('Image',) in PIL
2014-03-10 12:28:52,687 found PIL : module 'PIL' from
'/usr/lib/python2.7/dist-packages/PIL/__init__.pyc'
2014-03-10 12:28:52,692 codec_import_check('enc_vpx', 'vpx encoder',
'xpra.codecs.vpx', 'xpra.codecs.vpx.encoder', ('Encoder',))
2014-03-10 12:28:52,692 xpra.codecs.vpx found, will check for ('Encoder',) in
xpra.codecs.vpx.encoder
2014-03-10 12:28:52,693 found enc_vpx : module 'xpra.codecs.vpx.encoder' from
'/usr/lib/python2.7/dist-packages/xpra/codecs/vpx/encoder.so'
2014-03-10 12:28:52,693 codec_import_check('dec_vpx', 'vpx decoder',
'xpra.codecs.vpx', 'xpra.codecs.vpx.decoder', ('Decoder',))
2014-03-10 12:28:52,693 xpra.codecs.vpx found, will check for ('Decoder',) in
xpra.codecs.vpx.decoder
2014-03-10 12:28:52,693 found dec_vpx : module 'xpra.codecs.vpx.decoder' from
'/usr/lib/python2.7/dist-packages/xpra/codecs/vpx/decoder.so'
2014-03-10 12:28:52,693 codec_import_check('enc_x264', 'x264 encoder',
'xpra.codecs.enc_x264', 'xpra.codecs.enc_x264.encoder', ('Encoder',))
2014-03-10 12:28:52,693 xpra.codecs.enc_x264 found, will check for
('Encoder',) in xpra.codecs.enc_x264.encoder
2014-03-10 12:28:52,694 found enc_x264 : module
'xpra.codecs.enc_x264.encoder' from
'/usr/lib/python2.7/dist-packages/xpra/codecs/enc_x264/encoder.so'
2014-03-10 12:28:52,694 codec_import_check('enc_nvenc', 'nvenc encoder',
'xpra.codecs.nvenc', 'xpra.codecs.nvenc.encoder', ('Encoder',))
2014-03-10 12:28:52,694 cannot import enc_nvenc (nvenc encoder): No module
named nvenc
2014-03-10 12:28:52,694 xpra was probably built with the option:
--without-enc_nvenc
2014-03-10 12:28:52,694 cannot import nvenc: No module named nvenc.encoder
2014-03-10 12:28:52,694 codec_import_check('csc_swscale', 'swscale colorspace
conversion', 'xpra.codecs.csc_swscale',
'xpra.codecs.csc_swscale.colorspace_converter', ('ColorspaceConverter',))
2014-03-10 12:28:52,694 xpra.codecs.csc_swscale found, will check for
('ColorspaceConverter',) in xpra.codecs.csc_swscale.colorspace_converter
2014-03-10 12:28:52,695 av pixel mode AV_PIX_FMT_0RGB is not available
2014-03-10 12:28:52,695 av pixel mode AV_PIX_FMT_BGR0 is not available
2014-03-10 12:28:52,695 swscale pixel formats: {'YUV422P':
xpra.codecs.csc_swscale.colorspace_converter.CSCPixelFormat object at
0x7f01570e6e40, 'BGR':
xpra.codecs.csc_swscale.colorspace_converter.CSCPixelFormat object at
0x7f01570e6d20, 'BGRX
Bug#741023: xpra attach :100 leads to 'segmentation fault'
It works!!! How can the problem be fixed (not temporarily)? Thanks again! On 10/03/14 14:00, Antoine Martin wrote: On 10/03/14 18:34, Wenceslao Gonzlez-Vias wrote: 2014-03-10 12:28:52,699 cannot import csc_opencl (OpenCL colorspace conversion): /usr/lib/python2.7/dist-packages/pyopencl/_cl.so: symbol clRetainDevice, version OPENCL_1.2 not defined in file libOpenCL.so.1 with link time reference This looks suspicious and could be the cause. It looks like the version the opencl module was compiled against is not the same as the version you have installed. You could verify this by (temporarily) deleting xpra's xpra/codecs/csc_opencl directory. If that doesn't do it, please get a gdb backtrace. -- Wenceslao Gonzlez-Vias e-mail: w...@unav.es http://fisica.unav.es/gmm/ FAX:+34 948.425.740 phn:+34 948.425.600 ext: 806500 / 806603 Depto. Fsica y Matemtica Aplicada Facultad de Ciencias Universidad de Navarra c/Irunlarrea 1 E-31008 Pamplona, Navarra, Spain -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#741023: xpra attach :100 leads to 'segmentation fault'
Package: xpra Version: 0.11.4+dfsg-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? As stated in the subject * What exactly did you do (or not do) that was effective (or ineffective)? I did 'xpra start :100' (previously I make sure there is not a X lock file, I reinstalled xorg, I rebooted system, etc). I tried also with versions 0.11.2 and 0.12.0 * What was the outcome of this action? I attach the files :100.log and Xorg.:100.log * What outcome did you expect instead? Xpre work properly *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES, LC_CTYPE=es_ES (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages xpra depends on: ii libavcodec54 6:9.11-1 ii libc6 2.18-4 ii libgtk2.0-0 2.24.22-1 ii libswscale2 6:9.11-1 ii libvpx1 1.3.0-2 ii libx11-6 2:1.6.2-1 ii libx264-133 2:0.133.2339+git585324f-2+b1 ii libxcomposite11:0.4.4-1 ii libxdamage1 1:1.1.4-1 ii libxext6 2:1.3.2-1 ii libxfixes31:5.0.1-1 ii libxrandr22:1.4.2-1 ii libxtst6 2:1.2.2-1 ii python2.7.5-5 ii python-gtk2 2.24.0-3+b1 ii x11-xserver-utils 7.7+2 ii xserver-xorg-input-void 1:1.4.0-1+b3 ii xserver-xorg-video-dummy 1:0.3.7-1+b2 Versions of packages xpra recommends: ii openssh-client1:6.5p1-4 ii python-avahi 0.6.31-4 ii python-gtkglext1 1.1.0-9.1 ii python-imaging2.3.0-2 ii python-netifaces 0.8-3+b1 ii python-webm 0.2.2-2.1 ii ssh-askpass 1:1.2.4.1-9 Versions of packages xpra suggests: ii gstreamer0.10-plugins-bad 0.10.23-7.2 ii gstreamer0.10-plugins-good 0.10.31-3+nmu2 ii gstreamer0.10-plugins-ugly 0.10.19-2+b3 ii openssh-server 1:6.5p1-4 pn pulseaudio none pn pulseaudio-utilsnone ii python-dbus 1.2.0-2+b2 ii python-gst0.10 0.10.22-3 ii python-pyopencl 2013.2-1 -- no debconf information _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running (EE) Fatal server error: (EE) Cannot establish any listening sockets - Make sure an X server isn't already running(EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at /home/XXX/.xpra/Xorg.:100.log for additional information. (EE) (EE) Server terminated with error (1). Closing log file. 2014-03-07 13:50:52,593 2014-03-07 13:50:52,594 Xvfb command has terminated! xpra cannot continue 2014-03-07 13:50:52,594 2014-03-07 13:50:52,594 removing socket /home/XXX/.xpra/YYY-100 [ 15751.822] _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed [ 15751.822] _XSERVTransMakeAllCOTSServerListeners: server already running [ 15751.822] (EE) Fatal server error: [ 15751.822] (EE) Cannot establish any listening sockets - Make sure an X server isn't already running(EE) [ 15751.822] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 15751.822] (EE) Please also check the log file at /home/XXX/.xpra/Xorg.:100.log for additional information. [ 15751.822] (EE) [ 15751.822] (EE) Server terminated with error (1). Closing log file.
Bug#741023: xpra attach :100 leads to 'segmentation fault'
I am unable to reproduce it in my laptop (same jessie and with 0.12.1). BTW, I tried with the version IN DEBIAN (both jessie and sid) in my workplace computer, which is the one is giving the problem and I reported this bug). I will remove (on Monday) the configuration files in /etc and try again with the jessie version. Do you think it may help? Thanks, Wenceslao On 03/07/2014 05:59 PM, Dmitry Smirnov wrote: I'm unable to reproduce this. On Fri, 7 Mar 2014 16:16:15 Wenceslao González-Viñas wrote: I tried also with versions 0.11.2 and 0.12.0 0.12.0 is not in Debian and not even released yet so my guess is that you might have broken/incompatible Xpra configuration files in /etc/xpra or in ~/.xpra... Also it may help if you try to disable pulseaudio. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#622842: brcm80211 not setting correct country code?
Neither I am a programmer nor I am having much time. If it only weren't latter, it wouldn't be fair to ask to other people to fix the problem. Of course, I am ready to test patches (although I did only once, I hope to be able to do it again...). Thank you any way from your suggestion. Whom I should ask for help? Otherwise, waiting till someone (who is programmer, has time and is willing to share drivers) having the same problem could be too long Best regards, Wenceslao El 05/11/11 07:27, Jonathan Nieder escribió: Hi, Wenceslao González-Viñas wrote: From your last post concerning this bug, I did not get what should be the procedure from now on. I would suggest looking at the driver code, adding printk calls to find out what it reads from the NVRAM (to confirm Ben's hypothesis), and if it is blank, coming up with a better behavior and proposing it in the form of a rough patch to the linux-wireless list. If you are not a programmer or lack time, that's okay; in that case the best thing to do is just to be ready to test patches if someone else embarks on that same adventure. Hope that helps, and sorry I don't have anything more helpful to provide. Regards, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#622842: brcm80211 not setting correct country code?
Unfortunately I do not control it . Thank you anyway, Wenceslao El 05/11/11 14:28, Uwe Kleine-König escribió: hI, On Wed, May 11, 2011 at 08:52:51AM +0200, Wenceslao González-Viñas wrote: Neither I am a programmer nor I am having much time. If it only weren't latter, it wouldn't be fair to ask to other people to fix the problem. Of course, I am ready to test patches (although I did only once, I hope to be able to do it again...). Thank you any way from your suggestion. Whom I should ask for help? Otherwise, waiting till someone (who is programmer, has time and is willing to share drivers) having the same problem could be too long If you control the access point, switch to a lower channel. 1-11 should work. Best regards Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#622842: brcm80211 not setting correct country code?
Dear Ben and all, From your last post concerning this bug, I did not get what should be the procedure from now on. Should the bug be reported to another package ? Or, is there something which is lacking that does not depend on you or other debian maintainers (eg. firmware or non-free packages)? I thought that the bug was going to be fixed in next release of kernel (or crda or another package related to the problem), but the fact is that the problem is still there. Is it convenient that I give more information? and in that case, what information ?? Well, thank you for all your help, Wenceslao Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#622842: brcm80211 not setting correct country code?
After iw reg set EU I do not get any answer in dmesg log. and if I do (after) : iw reg get , I get: country 98: (2402 - 2472 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 17) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5600 @ 40), (N/A, 20), DFS (5650 - 5710 @ 40), (N/A, 20), DFS So, something is not working properly. Thanks and best regards, Wenceslao Arend van Spriel ar...@broadcom.com ha escrito: On 04/30/2011 07:04 AM, Ben Hutchings wrote: I looked at the driver source code and there is certainly an attempt to use a country code from NVRAM. But maybe it hasn't actually been read from NVRAM at the point this is done. 'US' seems to be the default if the country code is blank. Ben. Please refer to the information on wireless.kernel.org: http://wireless.kernel.org/en/users/Drivers/brcm80211#Regulatory_Implementation You could investigate whether the NVRAM/SROM country code is indeed blank or really configured with 'US'. For the driver itself channel 13 can be used as long as your access point is transmitting beacons, because it is regarded as a passive channel. Reading the logs listed in bug #622842 I would suggest running the following command after loading the brcm80211 driver: $ iw set reg EU You should see following in the log: Apr 30 10:05:22 myhost kernel: [ 3967.072332] cfg80211: Calling CRDA for country: EU Gr. AvS Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#622842: brcm80211 not setting correct country code?
I do not understand. I did of course as root. The rule in udev was not defined, though. I defined it , I restarted it , but no change. It does not matter if I use EU, ES or whatever. ?? Anyway, I think that is not iw / udev or similar problem as if I put a ralink stick, it works perfectly with regulatory domains and so. I think is a problem with driver ... (as hardware worked in MSW7) Best and thanks again, Wenceslao Arend van Spriel ar...@broadcom.com ha escrito: On 04/30/2011 10:38 AM, Wenceslao González-Viñas wrote: After iw reg set EU I do not get any answer in dmesg log. I assume you did this as root or used sudo. You may have to check whether you have the proper udev rules in place. See http://wireless.kernel.org/en/developers/Regulatory/CRDA#Letting_the_kernel_call_CRDA and if I do (after) : iw reg get , I get: country 98: (2402 - 2472 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 17) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5600 @ 40), (N/A, 20), DFS (5650 - 5710 @ 40), (N/A, 20), DFS So, something is not working properly. I get country US (after iw reg set EU). I tried 'iw reg set ES' after that and another message showed up in the log: [ 1613.052044] cfg80211: Calling CRDA for country: EU [ 1845.365115] cfg80211: Pending regulatory request, waiting for it to be processed... It seems cfg80211 expects CRDA to respond to the country setting for EU. I am not familiar what modules are involved in this usage scenario. Gr. AvS Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#622842: brcm80211 not setting correct country code?
Dear Ben, If you want, I could try with this modified of wireless-regdb ... Just tell me how to obtain it . Best and thanks again, Wenceslao Ben Hutchings b...@decadent.org.uk ha escrito: On Sat, 2011-04-30 at 13:30 +0200, Arend van Spriel wrote: On 04/30/2011 10:38 AM, Wenceslao González-Viñas wrote: After iw reg set EU I do not get any answer in dmesg log. I assume you did this as root or used sudo. You may have to check whether you have the proper udev rules in place. See http://wireless.kernel.org/en/developers/Regulatory/CRDA#Letting_the_kernel_call_CRDA They are. and if I do (after) : iw reg get , I get: country 98: (2402 - 2472 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 17) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5600 @ 40), (N/A, 20), DFS (5650 - 5710 @ 40), (N/A, 20), DFS So, something is not working properly. I get country US (after iw reg set EU). I tried 'iw reg set ES' after that and another message showed up in the log: [ 1613.052044] cfg80211: Calling CRDA for country: EU [ 1845.365115] cfg80211: Pending regulatory request, waiting for it to be processed... It seems cfg80211 expects CRDA to respond to the country setting for EU. I am not familiar what modules are involved in this usage scenario. I added 'EU' to wireless-regdb in Debian for backward-compatibility. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#622842: brcm80211 not setting correct country code?
So, then this means that the problem is still there ... ... What else could I try? Wenceslao Ben Hutchings b...@decadent.org.uk ha escrito: On Sat, 2011-04-30 at 15:48 +0200, Wenceslao González-Viñas wrote: Dear Ben, If you want, I could try with this modified of wireless-regdb ... Just tell me how to obtain it . [...] I did that before uploading the first version, so you already have it. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#622842: firmware-brcm80211: not getting an associated point
Dear all, After installing CRDA I am not able to have regulatory domain = EU in brcm80211 .Consequently, I cannot connect to any 2.472 GHz wifi. The dmesg log is the following (from just before modprobe brcm80211 in a way that you can see the good regulatory domain for cfg80211 !!!; see specially [ 76.098256]): [ 57.916230] cfg80211: Calling CRDA to update world regulatory domain [ 58.003989] cfg80211: World regulatory domain updated: [ 58.003994] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 58.003998] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 58.004021] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 58.004025] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 58.004028] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 58.004031] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 58.004171] cfg80211: Calling CRDA for country: EU [ 58.009303] cfg80211: Regulatory domain changed to country: EU [ 58.009308] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 58.009312] cfg80211: (2402000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm) [ 58.009315] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (N/A, 2000 mBm) [ 58.009318] cfg80211: (525 KHz - 533 KHz @ 4 KHz), (N/A, 2000 mBm) [ 58.009321] cfg80211: (549 KHz - 571 KHz @ 4 KHz), (N/A, 2700 mBm) [ 75.961782] brcm80211: module is from the staging directory, the quality is unknown, you have been warned. [ 75.967427] brcm80211 :03:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17 [ 75.967435] brcm80211 :03:00.0: setting latency timer to 64 [ 76.012899] Found chip type AI (0x13814313) [ 76.016022] Changing max_res_mask to 0x [ 76.016024] Changing min_res_mask to 0x200d [ 76.022133] Applying 4313 WARs [ 76.023030] wlc_bmac_attach:: deviceid 0x4727 nbands 1 board 0x51a macaddr: 88:25:2c:4e:9e:34 [ 76.097426] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 76.098256] wl_set_hint: Sending country code US to MAC80211 [ 76.098263] wl0: Broadcom BCM43xx 802.11 MAC80211 Driver (1.82.8.0) (Compiled at 04:19:31 on Apr 7 2011) [ 76.098566] cfg80211: Calling CRDA for country: US [ 76.110176] cfg80211: Current regulatory domain intersected: [ 76.110180] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 76.110184] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm) [ 76.110187] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (N/A, 1700 mBm) [ 76.110191] cfg80211: (525 KHz - 533 KHz @ 4 KHz), (N/A, 2000 mBm) [ 76.110194] cfg80211: (549 KHz - 560 KHz @ 4 KHz), (N/A, 2000 mBm) [ 76.110197] cfg80211: (565 KHz - 571 KHz @ 4 KHz), (N/A, 2000 mBm) -- Thank you for your help. Wenceslao Wenceslao González-Viñas w...@fisica.unav.es ha escrito: Here it is: result from lspci -vv: - 03:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01) Subsystem: Broadcom Corporation Device 051a Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 10 Region 0: Memory at d030 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=2 PME- Capabilities: [58] Vendor Specific Information: Len=78 ? Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+ Address: Data: Capabilities: [d0] Express (v1) Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s 4us, L1 unlimited ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 4us, L1 64us ClockPM+ Surprise- LLActRep+ BwNot- LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk
Bug#622842: firmware-brcm80211: not getting an associated point
In Spain (PC - City company). It is a Dell Inspiron M101z (service tag CHL0SM1) . BTW, in Windows 7, it worked perfectly. But I removed it installing Debian Wheezy. Best and thanks, Wenceslao Ben Hutchings b...@decadent.org.uk ha escrito: On Fri, 2011-04-29 at 16:48 +0200, Wenceslao González-Viñas wrote: Dear all, After installing CRDA I am not able to have regulatory domain = EU in brcm80211 .Consequently, I cannot connect to any 2.472 GHz wifi. The dmesg log is the following (from just before modprobe brcm80211 in a way that you can see the good regulatory domain for cfg80211 !!!; see specially [ 76.098256]): [...] It looks like the device has a country code of US. It could be that the driver is not reading the country code correctly, though. Where did you buy this hardware? Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. -- Wenceslao González-Viñas e-mail: w...@fisica.unav.es http://fisica.unav.es/~wens/ (personal) http://fisica.unav.es/gmm/ (group) FAX:+34 948.425.649 phn:+34 948.425.600 ext:6385 / 6603 Depto. Física y Matemática Aplicada Facultad de Ciencias Universidad de Navarra c/Irunlarrea s/n E-31080 Pamplona, Navarra, Spain Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#622842: firmware-brcm80211: not getting an associated point
Here it is: result from lspci -vv: - 03:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01) Subsystem: Broadcom Corporation Device 051a Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 10 Region 0: Memory at d030 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=2 PME- Capabilities: [58] Vendor Specific Information: Len=78 ? Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+ Address: Data: Capabilities: [d0] Express (v1) Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s 4us, L1 unlimited ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 4us, L1 64us ClockPM+ Surprise- LLActRep+ BwNot- LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt- Capabilities: [100 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 14, GenCap+ CGenEn- ChkCap+ ChkEn- Capabilities: [13c v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb:Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0:Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb:Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff Status: NegoPending- InProgress- Capabilities: [160 v1] Device Serial Number 00-00-2c-ff-ff-4e-88-25 Capabilities: [16c v1] Power Budgeting ? --- and result from dmesg: [ 330.205983] brcm80211: module is from the staging directory, the quality is unknown, you have been warned. [ 330.212186] brcm80211 :03:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17 [ 330.212195] brcm80211 :03:00.0: setting latency timer to 64 [ 330.268237] Found chip type AI (0x13814313) [ 330.271328] Changing max_res_mask to 0x [ 330.271330] Changing min_res_mask to 0x200d [ 330.277446] Applying 4313 WARs [ 330.278330] wlc_bmac_attach:: deviceid 0x4727 nbands 1 board 0x51a macaddr: 88:25:2c:4e:9e:34 [ 330.283578] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht' [ 330.285363] wl_set_hint: Sending country code US to MAC80211 [ 330.285371] wl0: Broadcom BCM43xx 802.11 MAC80211 Driver (1.82.8.0) (Compiled at 04:19:31 on Apr 7 2011) [ 330.365121] ADDRCONF(NETDEV_UP): wlan0: link is not ready -- By the way, before I used 'modprobe cfg80211 ieee80211_regdom=EU' . Perhaps the problem comes from that and line (dmesg) 330.285363 ? I need channel 13 ... Best regards and thanks, Wenceslao maximilian attems m...@stro.at ha escrito: reassign 622842 linux-2.6 stop On Fri, Apr 15, 2011 at 09:07:30AM +0200, Wenceslao wrote: Package: firmware-brcm80211 Version: 0.29 Severity: important module brcm80211 is not getting the associated point of a wifi, although it is properly detected. With a usb wifi stick (a ralink one) is detecting and attaching properly. so you properly know the module and report against firmware, *woow*. attach relevant dmesg or lspci output unless proven as currently this can be close right away. kind regards -- maks Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian
Bug#622842: firmware-brcm80211: not getting an associated point
Package: firmware-brcm80211 Version: 0.29 Severity: important module brcm80211 is not getting the associated point of a wifi, although it is properly detected. With a usb wifi stick (a ralink one) is detecting and attaching properly. Best regards and thank you, Wenceslao -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash firmware-brcm80211 depends on no packages. firmware-brcm80211 recommends no packages. Versions of packages firmware-brcm80211 suggests: ii initramfs-tools 0.98.8 tools for generating an initramfs ii linux-image-2.6.38-2-amd64 [l 2.6.38-3 Linux 2.6.38 for 64-bit PCs -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609860: pm-utils: pm-hibernate not able to wake-up
Dear Michael, Answers inside your email. Thank you very much. Best regards, Wenceslao Michael Biebl bi...@debian.org ha escrito: On 13.01.2011 07:45, W.GV wrote: Package: pm-utils Version: 1.3.0-3 Severity: important pm-* work except pm-hibernate, which seems to hibernate. After booting up system does not detects the information to wake-up. So, grub and kernel starts as if has been a shutdown before (except recovering journals in ext3 filesystems ...) What is your swap partition, how big is it, how big is your RAM? (cat /proc/swaps ; cat /proc/meminfo). cat /proc/swaps FilenameTypeSizeUsedPriority /dev/sda2 partition 1980408 0 -1 RAM : 2GB ... but you can see the full output: cat /proc/meminfo MemTotal:1990884 kB MemFree: 734188 kB Buffers: 127572 kB Cached: 737880 kB SwapCached:0 kB Active: 541352 kB Inactive: 557456 kB Active(anon): 233708 kB Inactive(anon):69072 kB Active(file): 307644 kB Inactive(file): 488384 kB Unevictable: 0 kB Mlocked: 0 kB SwapTotal: 1980408 kB SwapFree:1980408 kB Dirty: 2652 kB Writeback: 0 kB AnonPages:233384 kB Mapped: 126604 kB Shmem: 69396 kB Slab: 109496 kB SReclaimable: 91652 kB SUnreclaim:17844 kB KernelStack:2168 kB PageTables:16728 kB NFS_Unstable: 0 kB Bounce:0 kB WritebackTmp: 0 kB CommitLimit: 2975848 kB Committed_AS: 977256 kB VmallocTotal: 34359738367 kB VmallocUsed: 355684 kB VmallocChunk: 34359350584 kB HardwareCorrupted: 0 kB HugePages_Total: 0 HugePages_Free:0 HugePages_Rsvd:0 HugePages_Surp:0 Hugepagesize: 2048 kB DirectMap4k: 10240 kB DirectMap2M: 2017280 kB Do you use the default Debian kernel with initramfs? Yes What does cat /etc/initramfs-tools/conf.d/resume say? Does it point to the correct partition? cat /etc/initramfs-tools/conf.d/resume RESUME=UUID=9b880a94-8d79-434d-81f2-789d2cc7c532 This is not a partition of the system (as seen in fstab or in /dev/disk/by-uuid/ ) . Could it be the MBR ... so the disk instead of a partition ? How could I know if this is correct? If it is not should I just edit etc/initramfs-tools/conf.d/resume and change accordingly? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609860: pm-utils: pm-hibernate not able to wake-up
Dear Michael, It works!!! So, the bug should be changed to something that initramfs-tools do not detect automatically the resume point ? In any case, just if it is of some help I attach the output you asked me: ! ls -al /dev/disk/by-uuid/ total 0 drwxr-xr-x 2 root root 140 Jan 14 06:16 . drwxr-xr-x 6 root root 120 Jan 14 06:16 .. lrwxrwxrwx 1 root root 10 Jan 14 06:16 46fd6395-d041-49c1-b428-b58f5b5e4db3 - ../../sda6 lrwxrwxrwx 1 root root 10 Jan 14 06:16 b14b1c9e-dbe2-4e3d-a203-025f0f54d9a0 - ../../sda5 lrwxrwxrwx 1 root root 10 Jan 14 06:16 b752bad2-f935-4375-807c-1a51d1fe759a - ../../sda1 lrwxrwxrwx 1 root root 10 Jan 14 06:16 b7b5b460-aea5-46ff-8715-15d1a8e8f367 - ../../sda2 lrwxrwxrwx 1 root root 10 Jan 14 06:16 fe44fc76-c077-4915-a4d6-e83e08de9035 - ../../sda7 Thanks again and my best regards, Wenceslao Michael Biebl bi...@debian.org ha escrito: On 14.01.2011 06:49, Wenceslao González-Viñas wrote: cat /etc/initramfs-tools/conf.d/resume RESUME=UUID=9b880a94-8d79-434d-81f2-789d2cc7c532 This is not a partition of the system (as seen in fstab or in /dev/disk/by-uuid/ ) . Could it be the MBR ... so the disk instead of a partition ? How could I know if this is correct? If it is not should I just edit etc/initramfs-tools/conf.d/resume and change accordingly? If /dev/disk/by-uuid/9b880a94-8d79-434d-81f2-789d2cc7c532 does not point to /dev/sda2, then you found your problem. Could you show me the output of ls -al /dev/disk/by-uuid/ Try to set RESUME=/dev/sda2 and run update-initramfs -u to re-generate the initramfs. Then please try if you can successfully hibernate/thaw. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#594561: State of the bug 594561
Ok!, I did more or less the things you told me. I was not able to patch the source in a standard way; but I changed the source code by hand, I recompile the kernel and I used the resulting module with insmod rt2870.ko ieee80211_regdom=EU Please note that I did not reinstall compiled kernel (so I had to use insmod instead your suggested modprobe) and that the module to use was rt2870 (and not 2860). Of course I patched from 2860 folder since the files were common. Now it works perfect ! So, you were right !!! Many thanks! My question now is how, and when this will become automatized in the kernel which comes from the debian distribution ? Thanks again and happy new year! Wenceslao Ben Hutchings b...@decadent.org.uk ha escrito: On Thu, 2010-12-23 at 16:33 +0100, Wenceslao González-Viñas wrote: I patched same file as before and i get the following error. I attach original and rejection file.. patch rt2870sta.ko 0001-rt28x0-Add-ieee80211_regdom-module-parameter-mimicki.patch [...] Why are you trying to patch the module? You need to patch its source code, following the instructions at http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#594561: State of the bug 594561
Ok! I didn't understand this in your last email (I thought it was two step thing and the first was what I did). It does not seem easy. I will try and say ... Thanks, Wenceslao Ben Hutchings b...@decadent.org.uk ha escrito: On Thu, 2010-12-23 at 16:33 +0100, Wenceslao González-Viñas wrote: I patched same file as before and i get the following error. I attach original and rejection file.. patch rt2870sta.ko 0001-rt28x0-Add-ieee80211_regdom-module-parameter-mimicki.patch [...] Why are you trying to patch the module? You need to patch its source code, following the instructions at http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605622: reconsideration of bug status
I think that this bug should be labelled as important. Thanks, Wenceslao Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#594561: State of the bug 594561
Dear Ben, Module crc_ccitt was already loaded. (anyway I removed and loaded again). After insmod rt2870sta it gave same error and kern.log gave: rt2870sta: module has no symbols (stripped?) Thanks and sorry not to cc to bug error address in previous email. Best, Wenceslao Ben Hutchings b...@decadent.org.uk ha escrito: [Please remember to reply-to-all, including the bug address.] On Sun, 2010-11-28 at 10:42 +0100, Wenceslao González-Viñas wrote: Dear Ben, thank you very much! In fact there is some problem: It gives this error: insmod: error inserting 'rt2870sta.ko': -1 Invalid module format There should be some more information in the kernel log; please report that. Actually, first try running 'modprobe crc_ccitt' before the insmod command. Could this be due to that I updated the system. Now, I have kernel: Linux box 2.6.32-5-amd64 #1 SMP Sat Oct 30 14:18:21 UTC 2010 x86_64 GNU/Linux [...] I don't think so. Whenever we do make an incompatible change, we increase the 'ABI version' which is the number that appears after the upstream version above, i.e. currently 5. We have not made such a change since package version 2.6.32-12 released in May. It's quite possible that I made a mistake here but it worked for me. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#594561: State of the bug 594561
Here it is the output of dmesg (attached). Best, Wenceslao Ben Hutchings b...@decadent.org.uk ha escrito: On Sun, 2010-11-28 at 21:20 +0100, Wenceslao González-Viñas wrote: Dear Ben, Module crc_ccitt was already loaded. (anyway I removed and loaded again). After insmod rt2870sta it gave same error and kern.log gave: rt2870sta: module has no symbols (stripped?) Sorry, I ran 'strip' on this file to remove unnecessary data. I forgot that it removes too much from kernel modules. I've put a fixed version up at the same URL. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. Este mensaje ha sido enviado desde https://webmail.unav.es [ 4685.815040] rt2870sta: module is from the staging directory, the quality is unknown, you have been warned. [ 4685.821411] rtusb init --- [ 4685.821655] === pAd = c9001149c000, size = 502256 === [ 4685.821658] -- RTMPAllocAdapterBlock, Status=0 [ 4685.823263] usbcore: registered new interface driver rt2870 [ 4685.839920] usb 1-8: firmware: requesting rt3070.bin [ 4686.112855] -- RTMPAllocTxRxRingMemory, Status=0 [ 4686.114489] --RTUSBVenderReset [ 4686.114614] --RTUSBVenderReset [ 4686.393575] 1. Phy Mode = 0 [ 4686.393579] 2. Phy Mode = 0 [ 4686.393582] NVM is Efuse and its size =2d[2d0-2fc] [ 4686.405449] [ 4686.405450] Block 0:3070 0101 2200 a72d [ 4686.407946] Block 0:ddfb [ 4686.410571] Block 1: 0511 0002 [ 4686.413195] Block 1: 0110 0330 [ 4686.415695] Block 2: 0005 [ 4686.418194] Block 2: [ 4686.420694] Block 3: 0707 0707 0707 [ 4686.423194] Block 3:0707 0707 0707 0707 [ 4686.425695] Block 4: [ 4686.428195] Block 4: c5ff [ 4686.430693] Block 5:a5b5 627a 3a50 012a [ 4686.433193] Block 5: [ 4686.435693] Block 6: [ 4686.438192] Block 6: [ 4686.440692] Block 7: 6688 6688 [ 4686.443191] Block 7: 6688 6688 [ 4686.445692] Block 8:0112 0200 4000 [ 4686.448192] Block 8:083a a701 0101 0201 [ 4686.450690] Block 9:0103 060a 0200 [ 4686.453190] Block 9:4000 0001 0209 0043 [ 4686.455690] Block a:0101 8000 09e1 0004 [ 4686.458189] Block a:0700 05ff 0507 [ 4686.460689] Block b:0281 0200 0700 0105 [ 4686.463188] Block b:0002 0002 0507 0202 [ 4686.465688] Block c:0200 0700 0305 0002 [ 4686.468189] Block c:0002 0507 0204 0200 [ 4686.470687] Block d:0700 0505 0002 0002 [ 4686.473187] Block d:0507 0206 0200 [ 4686.475686] Block e:6152 696c 6b6e 2020 [ 4686.478185] Block e:6957 6572 656c 7373 [ 4686.480686] Block f:3120 6e31 2020 2020 [ 4686.483185] Block f:2e31 3030 [ 4686.485685] Block 10:0112 0200 4000 [ 4686.488186] Block 10:148f 3070 0001 0706 [ 4686.490684] Block 11:0108 060a 0200 [ 4686.493184] Block 11:4000 0001 0209 0020 [ 4686.495684] Block 12:0101 8000 09e1 0004 [ 4686.498182] Block 12:0200 0608 0a50 0507 [ 4686.500682] Block 13:0281 0200 0700 0105 [ 4686.503182] Block 13:0002 0002 [ 4686.505682] Block 14: [ 4686.508182] Block 14: [ 4686.510681] Block 15: [ 4686.513181] Block 15: [ 4686.515681] Block 16: 003f [ 4686.518305] Block 16: [ 4686.520805] Block 17:6000 a270 a2ff 7060 [ 4686.523305] Block 17:ffa2 ffa2 [ 4686.525805] Block 18:0304 0409 [ 4686.528305] Block 18: [ 4686.530803] Block 19: [ 4686.533303] Block 19: [ 4686.535803] Block 1a: [ 4686.538302] Block 1a: [ 4686.540802] Block 1b: [ 4686.543302] Block 1b: [ 4686.545802] Block 1c: [ 4686.548302] Block 1c: [ 4686.550801] Block 1d: [ 4686.553300] Block 1d: [ 4686.555800] Block 1e:030e 0052 0061 006c [ 4686.558549] Block 1e:0069 006e 006b [ 4686.561049] Block 1f:031e 0038 0030 0032 [ 4686.563548] Block 1f:002e 0031 0031 0020 [ 4686.566048] Block 20:006e 0020 0057 004c [ 4686.568549] Block 20:0041 004e [ 4686.571047] Block 21:0304 0409 [ 4686.573547] Block 21: [ 4686.576050] Block 22: 0308 0031 002e [ 4686.578546] Block 22:0030 [ 4686.581046] Block 23: [ 4686.583545] Block 23: [ 4686.586046] Block 24: [ 4686.588546] Block 24: [ 4686.591044] Block 25: [ 4686.593545] Block 25: [ 4686.596048] Block 26: [ 4686.598543] Block 26: [ 4686.601043] Block 27: [ 4686.603542] Block 27: [ 4686.606042] Block 28:
Bug#594561: State of the bug 594561
Hereby I attach new output, Wenceslao Ben Hutchings b...@decadent.org.uk ha escrito: On Sun, 2010-11-28 at 22:38 +0100, Wenceslao González-Viñas wrote: Here it is the output of dmesg (attached). Sorry, but there's something I missed - there are two different ways of reading the ROM. I have put yet another version at the same URL, which will read the ROM in the other way. Please load it and report the new log messages. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. -- Este mensaje ha sido enviado desde https://webmail.unav.es [ 8695.930670] rt2870sta: module is from the staging directory, the quality is unknown, you have been warned. [ 8695.937697] rtusb init --- [ 8695.937909] === pAd = c90011336000, size = 502256 === [ 8695.937912] -- RTMPAllocAdapterBlock, Status=0 [ 8695.940195] usbcore: registered new interface driver rt2870 [ 8695.948338] usb 1-8: firmware: requesting rt3070.bin [ 8696.220278] -- RTMPAllocTxRxRingMemory, Status=0 [ 8696.221828] --RTUSBVenderReset [ 8696.221953] --RTUSBVenderReset [ 8696.500913] 1. Phy Mode = 0 [ 8696.500917] 2. Phy Mode = 0 [ 8696.500920] NVM is Efuse and its size =2d[2d0-2fc] [ 8696.512787] [ 8696.512789] Block 0:3070 0130 0101 0001 [ 8696.515285] Block 0:2200 2d22 a72d 00a7 [ 8696.517785] Block 1:ddfb 00dd [ 8696.520411] Block 1: [ 8696.522784] Block 2: [ 8696.524783] Block 2: [ 8696.526783] Block 3: [ 8696.528783] Block 3: [ 8696.530783] Block 4: [ 8696.532783] Block 4: [ 8696.534782] Block 5: [ 8696.536782] Block 5: [ 8696.538907] Block 6: [ 8696.541406] Block 6:0511 0205 0002 [ 8696.543906] Block 7: 10ff 0110 0001 [ 8696.546408] Block 7: 3000 0330 0003 [ 8696.548905] Block 8: 00ff [ 8696.551405] Block 8: 0500 0005 [ 8696.553905] Block 9: [ 8696.556404] Block 9: ff00 00ff [ 8696.558904] Block a: 0700 0707 0007 [ 8696.561404] Block a:0707 0707 0707 0007 [ 8696.563903] Block b:0707 0707 0707 0007 [ 8696.566402] Block b:0707 0707 0707 0007 [ 8696.568902] Block c: 00ff [ 8696.571402] Block c: 00ff [ 8696.573902] Block d: 00ff [ 8696.576402] Block d: c5ff 00c5 [ 8696.578901] Block e:a5b5 7aa5 627a 0062 [ 8696.581401] Block e:3a50 2a3a 012a 0001 [ 8696.583901] Block f: 00ff [ 8696.586399] Block f: 00ff [ 8696.588775] Block 10: [ 8696.590774] Block 10: [ 8696.592774] Block 11: [ 8696.594774] Block 11: [ 8696.596773] Block 12: [ 8696.598772] Block 12: [ 8696.600773] Block 13: [ 8696.602773] Block 13: [ 8696.604773] Block 14: [ 8696.606772] Block 14: [ 8696.608771] Block 15: [ 8696.610771] Block 15: [ 8696.612771] Block 16: [ 8696.614771] Block 16: [ 8696.616770] Block 17: [ 8696.618770] Block 17: [ 8696.620894] Block 18: [ 8696.622894] Block 18: [ 8696.624894] Block 19: [ 8696.626894] Block 19: [ 8696.629018] Block 1a: [ 8696.631518] Block 1a: [ 8696.634018] Block 1b: [ 8696.636520] Block 1b: 5500 0055 [ 8696.639017] Block 1c: 88aa 6688 0066 [ 8696.641517] Block 1c: 88aa 6688 0066 [ 8696.644039] Block 1d: 88aa 6688 0066 [ 8696.646516] Block 1d: 88aa 6688 0066 [ 8696.649140] Block 1e: [ 8696.651140] Block 1e: [ 8696.653265] Block 1f: [ 8696.655264] Block 1f: [ 8696.657265] Block 20: [ 8696.659264] Block 20: [ 8696.661264] Block 21: [ 8696.663263] Block 21: [ 8696.665389] Block 22: [ 8696.667388] Block 22: [ 8696.669387] Block 23: [ 8696.671387] Block 23: [ 8696.673387] Block 24: [ 8696.675386] Block 24: [ 8696.677386] Block 25: [ 8696.679386] Block 25: [ 8696.681510] Block 26: [ 8696.683510] Block 26: [ 8696.685510] Block 27: [ 8696.687761] Block 27: [ 8696.689760] Block 28: [ 8696.691759] Block 28: [ 8696.693759] Block 29:
Bug#594561: State of the bug 594561
Could someone tell me what is the state of this bug? What can I do to help to fix the problem? Thank you very much in advanced, best regards, Wenceslao PS: I am using testing (squeeze) Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#594561: Fwd: Re: Bug#594561: 594561 should be reopened
Dear Ben, Do you need more information from my side in order to fix the problem? I see that the bug is reopened, but I do not know how I can help to solve it ... Best, Wenceslao Este mensaje ha sido enviado desde https://webmail.unav.es ---BeginMessage--- I tried in another computer (same kernel and so on ...) and happened the same.. In this case ralink was on wlan1 ls -l /sys/class/net/wlan1/device/*/driver lrwxrwxrwx 1 root root 0 Oct 4 06:35 /sys/class/net/wlan1/device/1-1:1.0/driver - ../../../../../../bus/usb/drivers/rt2870 Best, Wenceslao Ben Hutchings b...@decadent.org.uk ha escrito: On Sun, 2010-10-03 at 22:29 +0200, Wenceslao González-Viñas wrote: readlink /sys/class/net/wlan0/device/driver ../../../../../bus/usb/drivers/usb Oh, sorry, make that: ls -l /sys/class/net/wlan0/device/*/driver Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. Este mensaje ha sido enviado desde https://webmail.unav.es ---End Message---
Bug#594561: 594561 should be reopened
Dear all, Bug n. 594561 is not fixed in version linux-2.6/2.6.32-23 (testing). The kernel detects the Wifi stick , but only same channels as before and nothing about freq. 2.472 ... Sorry for not reporting before, as it was impossible for me to check until now. Best regards, Wenceslao Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#594561: 594561 should be reopened
In fact, I think that it is a variant (rt3070) of rt2870. But anyway, I just connect the wifi stick to the computer (after updating kernel and rebooting). It starts to blink and detects the wifi signal, but not the needed channel (13). I type: iwlist wlan0 frequency and in the answer there is only frequencies below 2.462 (so same channels as before). BTW, it is a wifi USB stick, not a pci device ... Thanks for everything. Wenceslao Ben Hutchings b...@decadent.org.uk ha escrito: On Sun, 2010-10-03 at 20:37 +0200, Wenceslao González-Viñas wrote: Dear all, Bug n. 594561 is not fixed in version linux-2.6/2.6.32-23 (testing). The kernel detects the Wifi stick , but only same channels as before and nothing about freq. 2.472 ... Please explain how you are testing this. Sorry for not reporting before, as it was impossible for me to check until now. I just tested on a Ralink PCI device with the rt2860sta driver, which shares the channel selection code with rt2870sta. I can select channel 13 / frequency 2.472 GHz now. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#594561: firmware-ralink: fails to detect APs at frequency 2.472GHz
*dp*ic*isc*ip* alias: usb:v14B2p3C28d*dc*dsc*dp*ic*isc*ip* alias: usb:v14B2p3C06d*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p002Dd*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p002Cd*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p002Bd*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p0017d*dc*dsc*dp*ic*isc*ip* alias: usb:v0B05p1742d*dc*dsc*dp*ic*isc*ip* alias: usb:v0B05p1732d*dc*dsc*dp*ic*isc*ip* alias: usb:v0B05p1731d*dc*dsc*dp*ic*isc*ip* alias: usb:v177Fp0302d*dc*dsc*dp*ic*isc*ip* alias: usb:v0789p0164d*dc*dsc*dp*ic*isc*ip* alias: usb:v0789p0163d*dc*dsc*dp*ic*isc*ip* alias: usb:v0789p0162d*dc*dsc*dp*ic*isc*ip* alias: usb:v083Ap7512d*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p0039d*dc*dsc*dp*ic*isc*ip* alias: usb:v07B8p2770d*dc*dsc*dp*ic*isc*ip* alias: usb:v07B8p2870d*dc*dsc*dp*ic*isc*ip* alias: usb:v148Fp2870d*dc*dsc*dp*ic*isc*ip* alias: usb:v148Fp2770d*dc*dsc*dp*ic*isc*ip* depends:usbcore,crc-ccitt staging:Y vermagic: 2.6.32-5-amd64 SMP mod_unload modversions parm: mac:rt28xx: wireless mac addr (charp) dmesg - [ 419.572015] usb 1-7: new high speed USB device using ehci_hcd and address 6 [ 419.721989] usb 1-7: New USB device found, idVendor=083a, idProduct=a701 [ 419.721994] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 419.721998] usb 1-7: Product: 802.11 n WLAN [ 419.722001] usb 1-7: Manufacturer: Ralink [ 419.722004] usb 1-7: SerialNumber: 1.0 [ 419.722140] usb 1-7: configuration #1 chosen from 1 choice [ 419.724643] === pAd = c9001114e000, size = 502256 === [ 419.724647] -- RTMPAllocAdapterBlock, Status=0 [ 419.777871] usb 1-7: firmware: requesting rt3070.bin [ 419.802850] usb 1-7: firmware file rt3070.bin request failed (-2) [ 419.802855] ERROR! NICLoadFirmware failed, Status[=0x0001] [ 419.802858] rt28xx Initialized fail! [ 419.836241] usb 1-7: firmware: requesting rt3070.bin [ 419.839037] usb 1-7: firmware file rt3070.bin request failed (-2) [ 419.839042] ERROR! NICLoadFirmware failed, Status[=0x0001] [ 419.839048] rt28xx Initialized fail! [ 419.839380] usb 1-7: firmware: requesting rt3070.bin [ 419.843020] usb 1-7: firmware file rt3070.bin request failed (-2) [ 419.843026] ERROR! NICLoadFirmware failed, Status[=0x0001] [ 419.843033] rt28xx Initialized fail! [ 419.854873] usb 1-7: firmware: requesting rt3070.bin [ 419.858756] usb 1-7: firmware file rt3070.bin request failed (-2) [ 419.858762] ERROR! NICLoadFirmware failed, Status[=0x0001] [ 419.858768] rt28xx Initialized fail! [ 479.965042] usb 1-7: firmware: requesting rt3070.bin [ 479.968119] usb 1-7: firmware file rt3070.bin request failed (-2) [ 479.968125] ERROR! NICLoadFirmware failed, Status[=0x0001] [ 479.968132] rt28xx Initialized fail! [ 713.978047] usb 1-7: firmware: requesting rt3070.bin [ 713.981339] usb 1-7: firmware file rt3070.bin request failed (-2) [ 713.981345] ERROR! NICLoadFirmware failed, Status[=0x0001] [ 713.981352] rt28xx Initialized fail! THANK YOU for everything. Kind regards, Wenceslao Ben Hutchings b...@decadent.org.uk ha escrito: On Fri, 2010-08-27 at 17:28 +0200, Wenceslao González-Viñas wrote: I installed in fact both (without putting them in automatic loading after boot). With both drivers happen the same. I may be wrong, but I tried very much to do in such a way they do not interfere. In the case of Debian compliant was the non-free section of Squeeze (testing), version 0.26. [...] That is the version of the *firmware* package, firmware-ralink. The driver is in the *kernel* package, linux-image-2.6.32-5-686 (and similarly named packages for different processor types). Please ensure you have that kernel package installed and uninstall Ralink's driver. Then reboot and test whether the frequency 2.472 GHz is supported. To confirm that you are using the right driver, please send the output of these commands: readlink /sys/class/net/wlan0/device/driver /sbin/modinfo rt2870sta dmesg Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#594561: firmware-ralink: fails to detect APs at frequency 2.472GHz (2)
: usb:v0DF6p002Dd*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p002Cd*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p002Bd*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p0017d*dc*dsc*dp*ic*isc*ip* alias: usb:v0B05p1742d*dc*dsc*dp*ic*isc*ip* alias: usb:v0B05p1732d*dc*dsc*dp*ic*isc*ip* alias: usb:v0B05p1731d*dc*dsc*dp*ic*isc*ip* alias: usb:v177Fp0302d*dc*dsc*dp*ic*isc*ip* alias: usb:v0789p0164d*dc*dsc*dp*ic*isc*ip* alias: usb:v0789p0163d*dc*dsc*dp*ic*isc*ip* alias: usb:v0789p0162d*dc*dsc*dp*ic*isc*ip* alias: usb:v083Ap7512d*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p0039d*dc*dsc*dp*ic*isc*ip* alias: usb:v07B8p2770d*dc*dsc*dp*ic*isc*ip* alias: usb:v07B8p2870d*dc*dsc*dp*ic*isc*ip* alias: usb:v148Fp2870d*dc*dsc*dp*ic*isc*ip* alias: usb:v148Fp2770d*dc*dsc*dp*ic*isc*ip* depends:usbcore,crc-ccitt staging:Y vermagic: 2.6.32-5-amd64 SMP mod_unload modversions parm: mac:rt28xx: wireless mac addr (charp) dmesg - [ 71.208021] usb 1-7: new high speed USB device using ehci_hcd and address 6 [ 71.358274] usb 1-7: New USB device found, idVendor=083a, idProduct=a701 [ 71.358279] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 71.358283] usb 1-7: Product: 802.11 n WLAN [ 71.358286] usb 1-7: Manufacturer: Ralink [ 71.358289] usb 1-7: SerialNumber: 1.0 [ 71.358428] usb 1-7: configuration #1 chosen from 1 choice Thanks again, Wenceslao Ben Hutchings b...@decadent.org.uk ha escrito: On Fri, 2010-08-27 at 17:28 +0200, Wenceslao González-Viñas wrote: I installed in fact both (without putting them in automatic loading after boot). With both drivers happen the same. I may be wrong, but I tried very much to do in such a way they do not interfere. In the case of Debian compliant was the non-free section of Squeeze (testing), version 0.26. [...] That is the version of the *firmware* package, firmware-ralink. The driver is in the *kernel* package, linux-image-2.6.32-5-686 (and similarly named packages for different processor types). Please ensure you have that kernel package installed and uninstall Ralink's driver. Then reboot and test whether the frequency 2.472 GHz is supported. To confirm that you are using the right driver, please send the output of these commands: readlink /sys/class/net/wlan0/device/driver /sbin/modinfo rt2870sta dmesg Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#594561: firmware-ralink: fails to detect APs at frequency 2.472GHz
*ic*isc*ip* alias: usb:v14B2p3C07d*dc*dsc*dp*ic*isc*ip* alias: usb:v07D1p3C11d*dc*dsc*dp*ic*isc*ip* alias: usb:v07D1p3C09d*dc*dsc*dp*ic*isc*ip* alias: usb:v2019pED06d*dc*dsc*dp*ic*isc*ip* alias: usb:v14B2p3C28d*dc*dsc*dp*ic*isc*ip* alias: usb:v14B2p3C06d*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p002Dd*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p002Cd*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p002Bd*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p0017d*dc*dsc*dp*ic*isc*ip* alias: usb:v0B05p1742d*dc*dsc*dp*ic*isc*ip* alias: usb:v0B05p1732d*dc*dsc*dp*ic*isc*ip* alias: usb:v0B05p1731d*dc*dsc*dp*ic*isc*ip* alias: usb:v177Fp0302d*dc*dsc*dp*ic*isc*ip* alias: usb:v0789p0164d*dc*dsc*dp*ic*isc*ip* alias: usb:v0789p0163d*dc*dsc*dp*ic*isc*ip* alias: usb:v0789p0162d*dc*dsc*dp*ic*isc*ip* alias: usb:v083Ap7512d*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p0039d*dc*dsc*dp*ic*isc*ip* alias: usb:v07B8p2770d*dc*dsc*dp*ic*isc*ip* alias: usb:v07B8p2870d*dc*dsc*dp*ic*isc*ip* alias: usb:v148Fp2870d*dc*dsc*dp*ic*isc*ip* alias: usb:v148Fp2770d*dc*dsc*dp*ic*isc*ip* depends:usbcore,crc-ccitt staging:Y vermagic: 2.6.32-5-amd64 SMP mod_unload modversions parm: mac:rt28xx: wireless mac addr (charp) dmesg - [ 1280.308022] usb 1-7: new high speed USB device using ehci_hcd and address 11 [ 1280.457583] usb 1-7: New USB device found, idVendor=083a, idProduct=a701 [ 1280.457588] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1280.457592] usb 1-7: Product: 802.11 n WLAN [ 1280.457595] usb 1-7: Manufacturer: Ralink [ 1280.457598] usb 1-7: SerialNumber: 1.0 [ 1280.457728] usb 1-7: configuration #1 chosen from 1 choice [ 1291.558512] rt2870sta: module is from the staging directory, the quality is unknown, you have been warned. [ 1291.565018] rtusb init --- [ 1291.565073] usbcore: registered new interface driver rt2870 [ 1291.566856] === pAd = c90011223000, size = 502256 === [ 1291.566860] -- RTMPAllocAdapterBlock, Status=0 [ 1291.603487] usb 1-7: firmware: requesting rt3070.bin [ 1291.885517] -- RTMPAllocTxRxRingMemory, Status=0 [ 1291.887041] --RTUSBVenderReset [ 1291.887166] --RTUSBVenderReset [ 1292.169749] 1. Phy Mode = 0 [ 1292.169753] 2. Phy Mode = 0 [ 1292.169756] NVM is Efuse and its size =2d[2d0-2fc] [ 1292.242864] 3. Phy Mode = 0 [ 1292.248738] RTMPSetPhyMode: channel is out of range, use first channel=1 [ 1292.248743] MCS Set = 00 00 00 00 00 [ 1292.309104] rt28xx_init, Status=0 [ 1292.310601] 0x1300 = 00073200 [ 1297.383818] ===rt_ioctl_giwscan. 2(2) BSS returned, data-length = 370 [ 1302.776005] wlan0: no IPv6 routers present [ 1318.108113] ===rt_ioctl_giwscan. 4(4) BSS returned, data-length = 698 [ 1348.108101] ===rt_ioctl_giwscan. 5(5) BSS returned, data-length = 929 Finally I run this: iwlist wlan0 channel wlan0 11 channels in total; available frequencies : Channel 01 : 2.412 GHz Channel 02 : 2.417 GHz Channel 03 : 2.422 GHz Channel 04 : 2.427 GHz Channel 05 : 2.432 GHz Channel 06 : 2.437 GHz Channel 07 : 2.442 GHz Channel 08 : 2.447 GHz Channel 09 : 2.452 GHz Channel 10 : 2.457 GHz Channel 11 : 2.462 GHz Current Frequency:2.412 GHz (Channel 1) So, I cannot get 2.472GHz freq Thanks, Wenceslao Why did you do that? Do you still think firmware-ralink is a driver? It is not. You do need firmware-ralink installed. Reinstall it and run those commands again. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. Este mensaje ha sido enviado desde https://webmail.unav.es -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#594561: firmware-ralink: fails to detect APs at frequency 2.472GHz
Package: firmware-ralink Version: 0.26 Severity: important I recently bought a Wifi stick (SMCWUSBS-N3) which uses the chip Ralink RT3070, because they say it works in Linux. I tried to install the driver (through firmware-ralink package and through compiling the driver ralink offers in their website) and finally it is detected (thanks to posts in internet ... those drivers are not working out of the box). The problem is that I cannot see my AP (which is in 2.472GHz; channel 13). I can see the AP (and connect to it) at the same position in another computer (internal wifi) and, in the same computer and stick with Windows 7 (now completely removed ;-) ). After some days of work, I obtain the following information: the stick is only capable (under my conf. in Debian) to see 11 channels in the 2.4GHz range (NOT including 2.472GHz). Also the APs detected (neighbours) are with signals much weaker than in the same computer and stick and position in Windows 7. Another thing that could help the diagnosis is that iw is not detecting any interface or device. Current conf. of computer: Debian Squeeze Linux Kernel 2.6.32-5 Network-Manager I blacklist in modprobe.d through specific files: rt2800(usb,lib), rt2x00, etc Sorry for not providing all the information, but I am in another computer so I cannot access now the logs. If you think something specific is needed I can put in pendrive and submit here. I checked the internet and although this has been seen some times the solutions they give are not working Thanks a lot for the help !! Wenceslao -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=es_ES, LC_CTYPE=es_ES (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#594561: firmware-ralink: fails to detect APs at frequency 2.472GHz
Hello, to tell you the truth I was scared at looking at the http://thread.gmane.org/gmane.linux.debian.devel.kernel/54624/ . The reason is that probably you are right, but unfortunately I am no such an expert to get a solution from the thread. I am looking in the packages repositories of debian an I am not able to find crda. On the other hand in the package contents search the 80211 stuff is related to linux headers, which I have installed. One thing that might help is that when I used iw list before, I got something like nl80211 not found. After that, I thought that one module should be loaded. I loaded mac80211. I checked it was (and I got mac and cfg). Now, when I type iw list, I got nothing (neither error nor result). Everything and what you told me makes me feel that the solution is nearby and easy; but I don't know how to go on ... Thanks a lot, Wenceslao El 08/27/10 10:15, Uwe Kleine-König escribió: Hello, On Fri, Aug 27, 2010 at 09:29:22AM +0200, Wenceslao wrote: Package: firmware-ralink Version: 0.26 Severity: important I recently bought a Wifi stick (SMCWUSBS-N3) which uses the chip Ralink RT3070, because they say it works in Linux. I tried to install the driver (through firmware-ralink package and through compiling the driver ralink offers in their website) and finally it is detected (thanks to posts in internet ... those drivers are not working out of the box). The problem is that I cannot see my AP (which is in 2.472GHz; channel 13). I can see the AP (and connect to it) at the same position in another computer (internal wifi) and, in the same computer and stick with Windows 7 (now completely removed ;-) ). After some days of work, I obtain the following information: the stick is only capable (under my conf. in Debian) to see 11 channels in the 2.4GHz range (NOT including 2.472GHz). Also the APs detected (neighbours) are with signals much weaker than in the same computer and stick and position in Windows 7. Another thing that could help the diagnosis is that iw is not detecting any interface or device. Current conf. of computer: Debian Squeeze Linux Kernel 2.6.32-5 Network-Manager I blacklist in modprobe.d through specific files: rt2800(usb,lib), rt2x00, etc Sorry for not providing all the information, but I am in another computer so I cannot access now the logs. If you think something specific is needed I can put in pendrive and submit here. I checked the internet and although this has been seen some times the solutions they give are not working This might be related to http://thread.gmane.org/gmane.linux.debian.devel.kernel/54624/ ? Any news there? Best regards Uwe -- Wenceslao González-Viñas e-mail: w...@fisica.unav.es http://fisica.unav.es/~wens/ (personal) http://fisica.unav.es/gmm/ (group) FAX:+34 948.425.649 phn:+34 948.425.600 ext:6385 / 6603 Depto. Física y Matemática Aplicada Facultad de Ciencias Universidad de Navarra c/Irunlarrea s/n E-31080 Pamplona, Navarra, Spain -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#594561: firmware-ralink: fails to detect APs at frequency 2.472GHz
I installed in fact both (without putting them in automatic loading after boot). With both drivers happen the same. I may be wrong, but I tried very much to do in such a way they do not interfere. In the case of Debian compliant was the non-free section of Squeeze (testing), version 0.26. Wenceslao El 08/27/10 17:20, Ben Hutchings escribió: On Fri, Aug 27, 2010 at 09:29:22AM +0200, Wenceslao wrote: Package: firmware-ralink Version: 0.26 Severity: important I recently bought a Wifi stick (SMCWUSBS-N3) which uses the chip Ralink RT3070, because they say it works in Linux. I tried to install the driver (*through firmware-ralink package* and through compiling the driver ralink offers in their website) and finally it is detected (thanks to posts in internet ... those drivers are not working out of the box). [...] So far as I know, channel limits are imposed by the driver, not the firmware. Since you are using the driver from Ralink, not from Debian, you have not (yet) found a bug in Debian. There is a version of the driver (rt2870sta) included in our packages of Linux 2.6.32, which are available in unstable, testing and lenny-backports. This has combined support for both RT2870 and RT3070 controllers. Please remove Ralink's version of the driver, install one of those packages and test whether the bug exists in this version of the driver. Ben. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#450586: virtualbox-ose do not upgrades properly
Package: virtualbox-ose
Version: 1.5.2-dfsg-2_i386
After I upgraded virtualbox-ose (and virtualbox-ose-source) to version
1.5.2-dfsg-2 from 1.5.0-dfsg2-2, the guest (MS-WXP) does not start
anymore. The virtualbox command of starting the guest gives the
following error:
-
The VirtualBox support driver which is running is from a different
version of VirtualBox. You can correct this by stopping all running
instances of VirtualBox and reinstalling the software..
VBox status code: -11 (VERR_VERSION_MISMATCH).
Result Code:
0x80004005
Component:
Console
Interface:
IConsole {1dea5c4b-0753-4193-b909-22330f64ec45}
I am using Debian GNU/Linux testing with Kernel 2.6.15a #1 SMP
PREEMPT and libc6 2.6.1-1+b1 ; arch: i386
Thanks a lot,
Wenceslao
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
