lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 09 Oct 2013 12:05:20 +0200
From:	Bjørn Mork <bjorn@...k.no>
To:	Oliver Neukum <oliver@...kum.org>
Cc:	Dan Williams <dcbw@...hat.com>, netdev@...r.kernel.org
Subject: Re: MBIM device refusing to be enabled

Oliver Neukum <oliver@...kum.org> writes:

> I have a device which the kernel and MM (1.0) identify as MBIM.
> I can transfer the PIN, but the device refuses to be enabled.
> Any idea?

[..]

> 2013-10-09T10:49:49.930237+02:00 linux-3m4i ModemManager[566]:
> [/dev/cdc-wdm0] Received message...#012>>>>>> RAW:#012>>>>>>   length =
> 56#012>>>>>>   data   =
> 03:00:00:80:38:00:00:00:13:00:00:00:01:00:00:00:00:00:00:00:A2:89:CC:33:BC:BB:8B:4F:B6:B0:13:3E:C2:AA:E6:DF:03:00:00:00:00:00:00:00:08:00:00:00:01:00:00:00:00:00:00:00
> 2013-10-09T10:49:49.930545+02:00 linux-3m4i ModemManager[566]:
> [/dev/cdc-wdm0] Received message (translated)...#012>>>>>>
> Header:#012>>>>>>   length      = 56#012>>>>>>   type        =
> command-done (0x80000003)#012>>>>>>   transaction = 19#012>>>>>>
> Fragment header:#012>>>>>>   total   = 1#012>>>>>>   current =
> 0#012>>>>>> Contents:#012>>>>>>   status error =
> 'None' (0x00000000)#012>>>>>>   service      =
> 'basic-connect' (a289cc33-bcbb-8b4f-b6b0-133ec2aae6df)#012>>>>>>   cid
> = 'radio-state' (0x00000003)

It's a bit difficult to read these logs, but decoding the raw data
results in:

MBIM_MESSAGE_HEADER
  MessageType:  0x80000003 (MBIM_COMMAND_DONE)
  MessageLength:        56
  TransactionId:        19
MBIM_FRAGMENT_HEADER
  TotalFragments:       0x00000001
  CurrentFragment:      0x00000000
BASIC_CONNECT (a289cc33-bcbb-8b4f-b6b0-133ec2aae6df)
MBIM_CID_RADIO_STATE (3)
MBIM_STATUS_SUCCESS (0)
InformationBuffer [8]:
  HwRadioState: on
  SwRadioState: off

Which either means that the radio is disabled using rfkill, or that
there is a problem with the platform rfkill driver for your laptop.
In any case, this is the reason you cannot enable the modem.

Does "rfkill list" confirm that the radio is disabled?  Can you change
it?


Bjørn
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ