[Clevo W253EU] Turn on bluetooth with Fn+F12 not working

[Antoine Sibold]

With my Clevo W253EU laptop, after installing Ubuntu 14.04 LTS, I cannot turn on Bluetooth with Fn+F12 as usual. I have tested other versions of Ubuntu the results are:
Ubuntu 12.04.LTS it works
Ubuntu 12.04.1 LTS it works
Ubuntu 12.04.2 LTS it works
Ubuntu 12.04.3 LTS it does not working
Ubuntu 12.04.4 LTS it does not working

Upstream post: http://marc.info/?l=linux-acpi&m=142227943520605&w=2

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-24-generic 3.13.0-24.47
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: sibold 1910 F.... pulseaudio
CurrentDesktop: Unity
Date: Thu May 22 09:31:55 2014
HibernationDevice: RESUME=UUID=135e9bbf-c0ff-411b-a1d8-e28de2b970ab
InstallationDate: Installed on 2014-05-17 (4 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=88147625-e531-4dd3-a5a1-fe593a977841 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-24-generic N/A
 linux-backports-modules-3.13.0-24-generic N/A
 linux-firmware 1.127.2
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/09/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W240EU/W250EUQ/W270EUQ
dmi.board.vendor: CLEVO CO.
dmi.board.version: V3.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd05/09/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.name: W240EU/W250EUQ/W270EUQ
dmi.product.version: Not Applicable
dmi.sys.vendor: CLEVO CO.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Antoine Sibold (antoine-sibold-r)]

All our clients with this machine will be affected in the future 500 Machines

[penalvch (penalvch)]

Antoine Sibold, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available (3.15-rc6) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-3.15-rc6

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Antoine Sibold (antoine-sibold-r)]

Hopefully i have done right
I have tested the latest rc kernel for Ubuntu release Trusty not for utopic

[penalvch (penalvch)]

Antoine Sibold, the next step is to fully commit bisect from Ubuntu 12.04.2 to 12.04.3 in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[Antoine Sibold (antoine-sibold-r)]

I have tested the following Kernels:
3.5.0-51 OK
3.8.0-29 Fails

[Dominique Hausser (dominique-hausser)]

With Ubuntu 14.04 LTS kernel
Linux 3.13.0-29-generic #52-Ubuntu SMP Wed May 28 12:42:47 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Fn+F12 is still not working.

I use a workaround to enable Blutooth describded here (sorry it is in french) : http://www.swisslinux.org/forum/viewtopic.php?pid=19401#p19401 comment #13

[penalvch (penalvch)]

Dominique Hausser, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Dominique Hausser (dominique-hausser)]

OK, i'll do my best as an end user and not a well trained computer developper.
As i am not with my laptop, i'll do that as soon as possible.

Have a nice day
Dominique Hausser (depuis Androïd 4.2.2)

"Christopher M. Penalver" <email address hidden> a écrit :

>Dominique Hausser, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
>ubuntu-bug linux
>
>For more on this, please read the official Ubuntu documentation:
>Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
>Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
>Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
>
>When opening up the new report, please feel free to subscribe me to it.
>
>Thank you for your understanding.
>
>Helpful bug reporting tips:
>https://wiki.ubuntu.com/ReportingBugs
>
>--
>You received this bug notification because you are subscribed to the bug
>report.
>https://bugs.launchpad.net/bugs/1322068
>
>Title:
> Turn on bluetooth with Fn+F12 not working
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322068/+subscriptions

[Dominique Hausser (dominique-hausser)]

Bug created https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327228

[Antoine Sibold (antoine-sibold-r)]

Are the informations i have given not suffisant to find the problem?
I am not a developper so i am not familiar with kernel bissect.
Best regards

[penalvch (penalvch)]

Antoine Sibold, at this point no, as a bisect would need to occur. Feel free to read the article, and post back where exactly you may have gotten stuck.

[Antoine Sibold (antoine-sibold-r)]

last good Linux kernel in 12.04.2 --> 12.10 Quantal is 3.5.0-52.79 --> to the last kernel after last ubdate of 12.04.2
first bad Linux kernel in 12.04.3 --> 13.04 Raring is 3.8.0-19.28 --> to the first used kernel in release of 12.04.3

That means the first kernel at release of 12.04.03 is the faulty kernel !

Is there more to do?

[Antoine Sibold (antoine-sibold-r)]

Sorry one more question

Are there other Kernels between 3.5.0-52.79
and
3.8.0-19.28?

[penalvch (penalvch)]

Antoine Sibold:

"Is there more to do?"

Yes.

"Are there other Kernels between 3.5.0-52.79 and 3.8.0-19.28?"

Yes.

[Antoine Sibold (antoine-sibold-r)]

To understand what is to do i have followed the explications in your document.

With the command

git clone git://kernel.ubuntu.com/ubuntu/ubuntu-maverick.git

i get the following error message

fatal remote error : access denied or reposetory not exported

Ihave also tried the command

git clone git://kernel.ubuntu.com/ubuntu/ubuntu-raring.git

I've got the same error message

What can i do to provide the necessary informations?
Thanks for your hhelp

[penalvch (penalvch)]

Antoine Sibold, as per http://kernel.ubuntu.com/git?p=ubuntu-archive/ubuntu-maverick.git;a=summary one would want to execute:
git clone git://kernel.ubuntu.com/ubuntu-archive/ubuntu-maverick.git

As well, no need exists to change the Status until the commit has been identified.

[Antoine Sibold (antoine-sibold-r)]

Thank you for your help. Now i have another question. In your exemple the bad and the good Kernel are located in the same Ubuntu Release Maverick.
Our problem is located in two different releases. Quanntal and Raring. How can i clone two differents repository in one local repository?

Thank you for your help?

[Michel-Ekimia (michel.ekimia)]

Hi Antoine can you add in both cases (latest working and first non working) the results of : "modinfo iwlwifi" to the bugreport ?

[Antoine Sibold (antoine-sibold-r)]

I had a moment to do some work on bisect.

First i get the orecise tree with the command
$ git clone git://kernel.ubuntu.com/ubuntu/ubuntu-precise.git
Now i have a local repository "ubuntu-precise"

I have also obtained a full list of the tagged versions with the command
$ git tag -l Ubuntu-*

The last good Kernel 3.5.0-52.79 (Ubuntu-lts-3.5.0-52.79)
and the first bad Kernel 3.8.0-19.28 (Ubuntu-lts-3.8.0-19.28)
i have identified, are in the list provided by the command mentionned before

What are now the next steps to do it is not clear for me.
Thanks a lot for your help

[Michel-Ekimia (michel.ekimia)]

Hello Antoine, any update on this. it seems you have done what's needed.

We have some customers that ask for buying recently the Why W253EU and the 14.04 compatibility is a blocking point now.

[Antoine Sibold (antoine-sibold-r)]

As mentionned before (comment wrote on 2014-08-13) i need help for the next steps.
Can somebody help me

Thanks a lot !!!

[Antoine Sibold (antoine-sibold-r)]

Sorry its me again,

But we have now more than 300 customers concerned by the problem mentionned above.
Is there really nobody which can help us ?

Any contribution will be really appreciated !

Thanks a lot !

[Michel-Ekimia (michel.ekimia)]

@Antoine : did you try some of the debugging tips here :

https://wiki.ubuntu.com/Hotkeys/Troubleshooting

[penalvch (penalvch)]

Ekimia, what needs to happen is what was already requested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322068/comments/7 . Debugging tips are useless here in comparison to a bisect.

[Antoine Sibold (antoine-sibold-r)]

I had some more time to investigate on bisect.

First i get the the quantal tree with the command
$ git clone git://kernel.ubuntu.com/archive-ubuntu/ubuntu-quantal.git
Now i have a local repository "ubuntu-quantal"

I have also obtained a full list of the tagged versions of quantal tree with the command
$ git tag -l Ubuntu-*

If i understand it right the last kernel release in that tree is 3.5.0-9.9 after for exeample 3.5.0-51.76

I get also the raring tree with the command
$ git clone git://kernel.ubuntu.com/archive-ubuntu/ubuntu-raring.git
Now i have a local repository "ubuntu-raring"

I have also obtained a full list of the tagged versions of raring tree with the command
$ git tag -l Ubuntu-*

If i understand right the first kernel release in the raring tree after 3.5.0-9.9 is 3.7.0-0.1

I have build and tested tested booth kernels
3.5.0-9.9 is ggod (FN+F12 enables Bluetooth)
3.7.0-0.1 (3.7.0-0.1-rc3) is bad (FN +F12 does not enable Bluetooth)

Does this means i have found the two adjacent kernel versions the Good and The Bad one.

Dear M Penalver please confirm and tell me what is to do now
Thanks in advance

[penalvch (penalvch)]

Antoine Sibold, looks good so far. You would want to continue following the article until the specific commit causing the regression is identified.

[Antoine Sibold (antoine-sibold-r)]

As the two kernel versions are located in two different local repositories (raring and quantal), how can i merge the two trees?
Does i need to do this?

In the Maverick example the good and the bad kernel versions are located in the same local repository (tree).

Thanks for answering

[penalvch (penalvch)]

Antoine Sibold, you would want to switch to bisecting the mainline kernel as outlined in the article.

[Antoine Sibold (antoine-sibold-r)]

Sorry its me again

Why and how switching to mainline kernel as the Good and Bad kernels are identified?

Thanks for your help

[Antoine Sibold (antoine-sibold-r)]

I have made the following bissect start in the local raring dpository

git bisect start Ubuntu-3.7.0-0.3 Ubuntu-3.5.0-5.5

Answer:

Bisecting: a merge base must be tested
[..........] Linux 3.5-rc7

What is to do now?

Thanks for your help

[penalvch (penalvch)]

Antoine Sibold, that is covered verbatim in the article.

[Antoine Sibold (antoine-sibold-r)]

Its me again

Bisecting: a merge base must be tested
[..........] Linux 3.5-rc7

What is the exact meaning of this result?

What do you mean by is covered verbatim in the article ? where can i find this article?

Thanks for your help

[Antoine Sibold (antoine-sibold-r)]

Its me again.

Sorry but english is not my mother tongue.
Some more compréhension questions:

Cloning an ubuntu release kernel can be achived by
git clone git://kernel.ubuntu.com/ubuntu/ubuntu-<release codename>.git ?

Creating a build environment for ubuntu release kernels can be achived by
 sudo apt-get build-dep linux-image-$(uname -r)?

Building the ubuntu-kernel kan b achived by
fakeroot debian/rules clean
fakeroot debian/rules binary-headers binary-generic?

Cloning a Main Release kernel can be achived by
git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git ?

How can y create a mainline kernel environment?
How can i Build and install a mainline kernel to test in the mainline bisect?

Thank You for your help

[Antoine Sibold (antoine-sibold-r)]

CAN REALLY NOBODY ANSWER MY QUESTIONS ! !

THE ARTICLE ABOUT BISECTING KERNELS IS FOR ME NOT 100 % CLEAR !!!

PROBABLY I'N NOT THE ONLY ONE

IF IT WAS I WOULD NOT ASKING QUESTIONS !!!

THANK YOU FOR YOUR HELP

[penalvch (penalvch)]

Antoine Sibold, please do not type in all caps. It's perceived as obnoxious, and quite unnecessary.

Despite this, please see the section of the article previously provided to you -> https://wiki.ubuntu.com/Kernel/KernelBisection#Bisecting:_a_merge_base_must_be_tested .

[Antoine Sibold (antoine-sibold-r)]

Sorry for that but I had no reaction before that.

Now i can tell you that exactly this section is dificult for me to understand.
What is to do to test a merge base for example Linux 3.5-rc7. I block here.

Thank you for your help

[Antoine Sibold (antoine-sibold-r)]

I have read the section mentioned above and it is question of commit bisecting the mainline kernel.
Sorry but i have not found a chapter describing this process.

Are mainline kernels and upstream kernels the same.

If this is the case i can apply the descriptions in chapter Commit bisecting upstream kernel versions

Thanks in advance for your answer

[Battant (mparchet)]

apport information

[Battant (mparchet)]

apport information

[Battant (mparchet)]

apport information

[Battant (mparchet)]

apport information

[Battant (mparchet)]

apport information

[Battant (mparchet)]

apport information

[Battant (mparchet)]

apport information

[Battant (mparchet)]

apport information

[Battant (mparchet)]

apport information

[Battant (mparchet)]

apport information

[Battant (mparchet)]

apport information

[Battant (mparchet)]

apport information

[Battant (mparchet)]

apport information

[Battant (mparchet)]

Hello,

I have send my configuration to this bugreport

Best regards

Battant

[NicoZ (nzlotyka)]

at least a solution here:
http://www.swisslinux.org/forum/viewtopic.php?id=3104&action=new

Only bad effect: when you change brightness with fn keys, it works but the bar doesn't appear anymore...

[Battant (mparchet)]

Hello,

after update from ubuntu 14.04 LTS kernel 3.5 to ubuntu 15.10 LTS kernel 4.2.0-35.I have again this problem

Could you find the bug cause at kernel level and fix it ?

If no, when I upgrade the kernel, I can't use the bluetooth internal chipset and I sould use my targus blowntoth pen to workaround.

 Best regards

Battant

[Battant (mparchet)]

Hello,

With ubuntu 16.04 LTS 64 bit and the kernel

uname -a
4.4.0-22-generic #39-Ubuntu SMP Thu May 5 16:53:32 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

The bluetooth seems work.

Best regards

Battant

[Battant (mparchet)]

Hello,

with :

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.1 LTS
Release: 16.04
Codename: xenial

and kernel

uname -r
4.4.0-45-generic 64 bit

the f12 key to turn on/off blowtoth don't work again ?

Could you help me to fix this bug

Best regards

Battant

[Battant (mparchet)]

Helo,

Here is my new configuration

uname -r
4.15.0-23-generic

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04 LTS
Release: 18.04
Codename: bionic

and Bluetooth always not working since long time

Could you help me please ?

Best regards

Battant

[penalvch (penalvch)]

Battant (mparchet), it will be helpful if you filed a new report via a terminal:
ubuntu-bug linux

Feel free to subscribe me to it.

[penalvch (penalvch)]

Antoine Sibold:

1) Does using the the following kernel boot parameters provide a WORKAROUND:
acpi_osi= acpi_backlight=legacy

2) To see if this still affects upstream, could you please test the latest mainline kernel (now 4.17-rc6) and advise to the results? Also, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available.

[Battant (mparchet)]

Helo,

Here is my new configuration

uname -r
4.15.0-23-generic

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04 LTS
Release: 18.04
Codename: bionic

and Bluetooth always not working since long time

Could you help me please ?

Best regards

Battant

[Battant (mparchet)]

ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: mparchet 3144 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-04-29 (27 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=9d6286f1-598b-46c8-a491-3e29fc732cb9 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-23-generic N/A
 linux-backports-modules-4.15.0-23-generic N/A
 linux-firmware 1.173.1
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: yes
Tags: bionic
Uname: Linux 4.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/11/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W240EU/W250EUQ/W270EUQ
dmi.board.vendor: CLEVO CO.
dmi.board.version: V3.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd11/11/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: W240EU/W250EUQ/W270EUQ
dmi.product.version: Not Applicable
dmi.sys.vendor: CLEVO CO.

[Battant (mparchet)]

apport information

[Battant (mparchet)]

apport information

[Battant (mparchet)]

apport information

[Battant (mparchet)]

apport information

[Battant (mparchet)]

apport information

[Battant (mparchet)]

apport information

[Battant (mparchet)]

apport information

[Battant (mparchet)]

apport information

[Battant (mparchet)]

apport information

[Battant (mparchet)]

apport information

[Battant (mparchet)]

apport information

[Battant (mparchet)]

apport information

[Battant (mparchet)]

apport information

[Battant (mparchet)]

apport information

[Battant (mparchet)]

Hello,

My new bug report

https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1773643

Best regards

Battant

[penalvch (penalvch)]

Battant, please stop apport-collecting to this report. Thanks!

[Launchpad Janitor (janitor)]

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