Bug#875621: Still not fixed

From	Martin Garton <garton@gmail.com>
Newsgroups	linux.debian.bugs.dist, linux.debian.kernel
Subject	Bug#875621: Still not fixed
Date	2018-09-22 16:10 +0200
Message-ID	<wAQLE-5tZ-11@gated-at.bofh.it> (permalink)
References	<wxQyt-5LR-5@gated-at.bofh.it> <wyiuJ-5li-7@gated-at.bofh.it> <wyiuJ-5li-7@gated-at.bofh.it> <uoYgi-4Sp-7@gated-at.bofh.it> <wyiuJ-5li-7@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw

As an additional data point, in case it's of any help, I can add that I 
also have problems due to CONFIG_RMI4_SMB being disabled. I'm using a 
Thinkpad X1 Carbon 6th generation machine.

I have rebuilt my kernel with CONFIG_RMI4_SMB enabled and everything is 
fine.

If there are still machines that have issues with this option enabled, 
isn't there a way to enable CONFIG_RMI4_SMB in the kernel and use module 
blacklisting wherever that module causes problems?

This would seem to be a reasonable way to make things work for everyone 
without anyone having to recompile kernels or kernel modules.

-- 
Martin.

Back to linux.debian.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Bug#875621: Still not fixed Han Boetes <hboetes@gmail.com> - 2018-09-14 09:20 +0200
  Bug#875621: Still not fixed Ben Hutchings <ben@decadent.org.uk> - 2018-09-15 15:10 +0200
    Bug#875621: Still not fixed Martin Garton <garton@gmail.com> - 2018-09-22 16:10 +0200

csiph-web