Mohamed Omar

Results 9 comments of Mohamed Omar

I am using last Kubuntu 22.04 with latest kernel ,also I made sure that latest linux-firmware package is installed. Also I tried with ubuntu ,debian , fedora,archlinux , All has...

Thanks bro for replying ,Unfortunately it is not fixed ! IDK if Changes which were added in 4.15 caused this issue until now ! https://kernelnewbies.org/Linux_4.15

Tried to put 3 props in GRUB_CMDLINE_LINUX_DEFAULT (one by one ) but unfortunately it is not fixed !

**Without Charger :** upower -i /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: TKBSS model: NS2P3SZMC4WR power supply: yes updated: Fri 12 Aug 2022 11:14:18 PM EET (88 seconds ago) has history: yes has...

I found this : https://linux-hardware.org/?probe=14ac6c1f51&log=upower Same battery model and it doesn't have this issue ! then something else should be the cause.

hello pro I found the cause : It is if statment was added in 4.19.86 kernel https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/drivers/acpi/acpica/evregion.c?id=v4.19.86&id2=v4.19.85

I tried to remove it , Thanks God battery is working now . [0001-Bypass-for-fixing-Toshiba-battery.patch.txt](https://github.com/xanmod/linux/files/9610561/0001-Bypass-for-fixing-Toshiba-battery.patch.txt) Do you see any better solution if yes please add it to xanmod kernel ? ![Screenshot_20220920_205916](https://user-images.githubusercontent.com/93285839/191342156-cf9389e4-c824-4467-bcc8-eb3b3a3a3283.png)

ok issue relates to ACPI_ADR_SPACE_SYSTEM_MEMORY , idk how ! here is patch [0001-ACPI-Bypass-for-my-toshiba-power-issue.patch.txt](https://github.com/xanmod/linux/files/9614826/0001-ACPI-Bypass-for-my-toshiba-power-issue.patch.txt)

In your env(mine is noob) , modify flush_timeout in OutStream class in iostream.py as u like , I am using py 3.11 ![image](https://github.com/ipython/ipykernel/assets/93285839/b6498c0b-5ccf-4a6e-8217-1cbb9cf9ceae) kate anaconda3/envs/noob/lib/python3.11/site-packages/ipykernel/iostream.py and return it again after...