Calculate🐧Forum

Mouse pointer is freezing

#1

Hello to all!
I have been using Calculate 17.12.2.
Recently, my mouse pointer is freezing, and I can’t do anything. Keyboard is working, though.
Can you help me ?
It happens to me every day.
Thank you.

#2

Hi,
Try plugging the mouse into another USB connector.

#3

I have been using touchpad on my laptop.

#4

Very strange, is the system updated? Alternatively, you can try to install the kernel 4.19.0.

#5

calculate ~ # emerge @module-rebuild
— Invalid atom in /etc/portage/package.keywords/custom: sys-kernel/git-sources-4.19_rc8

Local copy of remote index is up-to-date and will be used.

* IMPORTANT: 10 news items need reading for repository ‘gentoo’.
* Use eselect news read to view new items.

Calculating dependencies… done!

Verifying ebuild manifests
Running pre-merge checks for net-wireless/broadcom-sta-6.30.223.271-r4
*
* If you are stuck using this unmaintained driver (likely in a MacBook),
* you may be interested to know that a newer compatible wireless card
* is supported by the in-tree brcmfmac driver. It has a model number
* BCM943602CS and is for sale on the second hand market for less than
* 20 USD.
*
* See https://wikidevi.com/wiki/Broadcom_Wireless_Adapters and
* https://wikidevi.com/wiki/Broadcom_BCM943602CS
* for more information.
*

Emerging binary (1 of 2) net-wireless/rtl8723de-20180901-r1::calculate
Emerging (2 of 2) net-wireless/broadcom-sta-6.30.223.271-r4::gentoo
Failed to emerge net-wireless/broadcom-sta-6.30.223.271-r4, Log file:
‘/var/calculate/tmp/portage/net-wireless/broadcom-sta-6.30.223.271-r4/temp/build.log’
Installing (1 of 2) net-wireless/rtl8723de-20180901-r1::calculate
Jobs: 1 of 2 complete, 1 failed Load avg: 1.08, 0.86, 0.71
* Package: net-wireless/broadcom-sta-6.30.223.271-r4
* Repository: gentoo
* Maintainer: eva@gentoo.org
* USE: abi_x86_64 amd64 elibc_glibc kernel_linux userland_GNU
* FEATURES: preserve-libs sandbox usersandbox
* Determining the location of the kernel source code
* Found kernel source directory:
* /usr/src/linux
* Found sources for kernel version:
* 4.19.0-rc8
* Could not find a usable .config in the kernel source directory.
* Please ensure that /usr/src/linux points to a configured set of Linux sources.
* If you are using KBUILD_OUTPUT, please set the environment var so that
* it points to the necessary object directory so that it might find .config.
* ERROR: net-wireless/broadcom-sta-6.30.223.271-r4::gentoo failed (setup phase):
* Kernel not configured; no .config found in /usr/src/linux
*
* Call stack:
* ebuild.sh, line 124: Called pkg_setup
* broadcom-sta-6.30.223.271-r4.ebuild, line 68: Called linux-mod_pkg_setup
* linux-mod.eclass, line 586: Called linux-info_pkg_setup
* linux-info.eclass, line 965: Called check_extra_config
* linux-info.eclass, line 773: Called require_configured_kernel
* linux-info.eclass, line 307: Called die
* The specific snippet of code:
* die “Kernel not configured; no .config found in ${KV_OUT_DIR}”
*
* If you need support, post the output of `emerge --info ‘=net-wireless/broadcom-sta-6.30.223.271-r4::gentoo’`,
* the complete build log and the output of `emerge -pqv ‘=net-wireless/broadcom-sta-6.30.223.271-r4::gentoo’`.
* The complete build log is located at ‘/var/calculate/tmp/portage/net-wireless/broadcom-sta-6.30.223.271-r4/temp/build.log’.
* The ebuild environment file is located at ‘/var/calculate/tmp/portage/net-wireless/broadcom-sta-6.30.223.271-r4/temp/die.env’.
* Working directory: ‘/var/calculate/tmp/portage/net-wireless/broadcom-sta-6.30.223.271-r4/homedir’
* S: ‘/var/calculate/tmp/portage/net-wireless/broadcom-sta-6.30.223.271-r4/work’

* Messages for package net-wireless/broadcom-sta-6.30.223.271-r4:

*
* If you are stuck using this unmaintained driver (likely in a MacBook),
* you may be interested to know that a newer compatible wireless card
* is supported by the in-tree brcmfmac driver. It has a model number
* BCM943602CS and is for sale on the second hand market for less than
* 20 USD.
*
* See https://wikidevi.com/wiki/Broadcom_Wireless_Adapters and
* https://wikidevi.com/wiki/Broadcom_BCM943602CS
* for more information.
*

* Messages for package net-wireless/broadcom-sta-6.30.223.271-r4:

* Could not find a usable .config in the kernel source directory.
* Please ensure that /usr/src/linux points to a configured set of Linux sources.
* If you are using KBUILD_OUTPUT, please set the environment var so that
* it points to the necessary object directory so that it might find .config.
* ERROR: net-wireless/broadcom-sta-6.30.223.271-r4::gentoo failed (setup phase):
* Kernel not configured; no .config found in /usr/src/linux
*
* Call stack:
* ebuild.sh, line 124: Called pkg_setup
* broadcom-sta-6.30.223.271-r4.ebuild, line 68: Called linux-mod_pkg_setup
* linux-mod.eclass, line 586: Called linux-info_pkg_setup
* linux-info.eclass, line 965: Called check_extra_config
* linux-info.eclass, line 773: Called require_configured_kernel
* linux-info.eclass, line 307: Called die
* The specific snippet of code:
* die “Kernel not configured; no .config found in ${KV_OUT_DIR}”
*
* If you need support, post the output of `emerge --info ‘=net-wireless/broadcom-sta-6.30.223.271-r4::gentoo’`,
* the complete build log and the output of `emerge -pqv ‘=net-wireless/broadcom-sta-6.30.223.271-r4::gentoo’`.
* The complete build log is located at ‘/var/calculate/tmp/portage/net-wireless/broadcom-sta-6.30.223.271-r4/temp/build.log’.
* The ebuild environment file is located at ‘/var/calculate/tmp/portage/net-wireless/broadcom-sta-6.30.223.271-r4/temp/die.env’.
* Working directory: ‘/var/calculate/tmp/portage/net-wireless/broadcom-sta-6.30.223.271-r4/homedir’
* S: ‘/var/calculate/tmp/portage/net-wireless/broadcom-sta-6.30.223.271-r4/work’

* Messages for package net-wireless/rtl8723de-20180901-r1:

*
* /usr/src/linux/System.map not found.
* You must manually update the kernel module dependencies using depmod.

#6

Currently, it works. Thank you.

#7

Try another USB port. If it’s in a USB 3 port, try USB 2 and vice versa.

More often than not, it’s due to excessive IRQ polling (interrupt storm). Either it’s caused by a resource conflict, or some peripheral or internal device is failing (such as the sound card or internal hard drive).

Try experimenting by disconnecting as many devices as possible in order to isolate the culprit.

Mastodon Mastodon