Hi, I've tried to find out the meanings of all the WMI entries you have,
but none seems to be related.
I heard it's possible that maybe WiFi has to be enabled under Windows in
this case. Something I would try as the last chance.
--
You received this bug notification because you are a member of
Hi. Happy New Year. Any news for me? Am re-sending logs, just in case.
--Anatoly
=
Attached are two automatically generated files and one text file I
copied screens to after running dmsg, just in case.
On 12/26/19 7:22 PM, You-Sheng Yang wrote:
> Hi, sorry for not
Hi. Attached are two automatically generated files and one text file I
copied screens to after running dmsg, just in case. Have fun ;)
On 12/26/19 7:22 PM, You-Sheng Yang wrote:
> Hi, sorry for not being clear as I could. Please refer to
>
Hi, sorry for not being clear as I could. Please refer to
https://www.howtogeek.com/196655/how-to-configure-the-grub2-boot-
loaders-settings/ , detailed steps are:
1. To blacklist wmi module:
$ gksu gedit /etc/default/grub
Then edit the line beginning with "GRUB_CMDLINE_LINUX_DEFAULT="
Hi.
On 12/25/19 11:13 PM, You-Sheng Yang wrote:
> Hi, didn't find something directly related from above WMI events. Could
> you try following to kernel parameters sets separately:
>
> 1. "module_blacklist=wmi": this will disable wmi completely
That seemed to work
> 2. "wmi.debug_event=1
Hi, didn't find something directly related from above WMI events. Could
you try following to kernel parameters sets separately:
1. "module_blacklist=wmi": this will disable wmi completely
2. "wmi.debug_event=1 wmi.debug_dump_wdg=1": this will enable wmi debug
info.
--
You received this bug
On 12/24/19 9:06 PM, You-Sheng Yang wrote:
> What's inside other wmi_bus-PNP0C14* folders?
/sys/class/wmi_bus/wmi_bus-PNP0C14\:01
7430019A-DCE9-4548-BAB0-9FDE0935CAFF device
FCB424F1-075A-4E0E-BFC4-62F3E71771FA subsystem
7FF47003-3B6C-4E5E-A227-E979824A85D1
E2BE5EE3-42DA-49DB-8378-1F5247388202
What's inside other wmi_bus-PNP0C14* folders?
By previous experience, BIOS vendor may implement some WMI interface
that can be used to control anything they want. Somehow such interfaces
could be misused on Linux as they're mostly designed for Windows. For
example,
There is more:
~$ sudo ls /sys/class/wmi_bus/wmi_bus-PNP0C14\:00
05901221-D566-11D1-B2F0-00A0C9062910
6A4B54EF-A5ED-4D33-9455-B0D9B48DF4B3
7EEF04FF-4328-447C-B5BB-D449925D538D device uevent
2651D9FD-911C-4B69-B94E-D0DED5963BD7
7364651A-132F-4FE7-ADAA-40C6C7EE2E3B
On 12/24/19 8:25 PM, You-Sheng Yang wrote:
>> What's the message?
> For bug status management. Never mind.
>
> [3.768689] iwlwifi :02:00.0: Detected Intel(R) Wireless-AC 9260
> 160MHz, REV=0x324
> [3.775535] iwlwifi :02:00.0: reporting RF_KILL (radio disabled)
> [3.777850]
> What's the message?
For bug status management. Never mind.
[3.768689] iwlwifi :02:00.0: Detected Intel(R) Wireless-AC 9260 160MHz,
REV=0x324
[3.775535] iwlwifi :02:00.0: reporting RF_KILL (radio disabled)
[3.777850] iwlwifi :02:00.0: Applying debug destination
What's the message?
On 12/23/19 10:23 PM, Po-Hsu Lin wrote:
> ** Changed in: linux (Ubuntu)
> Status: Incomplete => Confirmed
>
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1857307
Title:
Wireless wouldn't turn on.
Status in linux package in
Hello,
Thank you for getting back to me. I am reporting on 19.10, PCI
wireless.
1. Here the rfkill output:
$ sudo rfkill unblock all
$ sudo rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
2. There is no any special switch but F8 key which I suppose
Hello,
let's focus on 19.10, you're reporting an issue for the PCI wireless card
(Wireless-AC 9260) in your system or the USB D-Link card?
Can you try the following steps to see if it helps:
1. run command "rfkill unblock all"
2. or to flip the wifi switch (if any)
3. check you BIOS
15 matches
Mail list logo
