Warning: Can't synchronize with repository "(default)" (No changeset 96d22ec3fa3ef6de3ea8dc0d7d398adc9aa071cf in the repository). Look in the Trac log for more information.

Ticket #684 (closed defect: fixed)

Opened 12 months ago

Last modified 12 months ago

fsodeviced-0.11 fails to register rfkill controlled devices

Reported by: jama Owned by: mickey
Priority: major Milestone: cornucopia-0.11
Component: cornucopia/fsodevice Version: 0.11
Keywords: Cc:

Description

fsodeviced-0.11.3 was supposed to fix this, but I can still see this issue with it on om-gta02

Attaching logs from fsousaged and fsodeviced

Attachments

fsodeviced.log​ (24.4 KB) - added by jama 12 months ago.
fsousaged.log​ (4.4 KB) - added by jama 12 months ago.

Change History

Changed 12 months ago by jama

Changed 12 months ago by jama

comment:1 Changed 12 months ago by jama

SHR root@gjama ~ $ mdbus2 -s org.freesmartphone.ousaged /org/freesmartphone/Usage org.freesmartphone.Usage.ListResources? (['Display', 'Accelerometer', 'CPU', 'UsbHost?'],)

SHR root@gjama ~ $ rfkill list 0: gta02-pm-bt: Bluetooth

Soft blocked: no Hard blocked: no

1: ar6000: Wireless LAN

Soft blocked: no Hard blocked: no

2: hci0: Bluetooth

Soft blocked: no Hard blocked: no

After boot ar6000 is Soft blocked and can be unblocked by rfkill (as work around until fsodeviced is fixed)

comment:2 Changed 12 months ago by morphis

It's only the kernel26_rfkill plugin which has this problem and it's now really fixed with SRCREV fb8ce7ea9b4d88696795430ef397cf502306b8b8 and later with 0.11.4

comment:3 Changed 12 months ago by jama

  • Status changed from new to closed
  • Resolution set to fixed

Tested and confirmed, Thanks!

Note: See TracTickets for help on using tickets.