Live desktop freezes/unfreeze

[Member Robin]

Helpful

Up

1

::

Please check your dmesg output first. Maybe there is a hint. E.g. sometimes bad USB devices block with constantly repeated failure the desktop.

Open roxterm and enter

sudo dmesg

or

sudo dmesg | tail -n60

Output might possibly show something like:

[1409103.383391] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
[1409103.383396] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 50 f8 d8 00 00 20 00
[1409103.383399] blk_update_request: I/O error, dev sdb, sector 5306584 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
[1409106.228631] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
[1409106.228638] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 50 f8 d8 00 00 20 00
[1409106.228642] blk_update_request: I/O error, dev sdb, sector 5306584 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0
[1409107.737126] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
[1409107.737134] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 50 f8 d8 00 00 20 00
[1409107.737140] blk_update_request: I/O error, dev sdb, sector 5306584 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
[1409113.725036] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
[1409113.725045] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 50 f8 d8 00 00 20 00
[1409113.725050] blk_update_request: I/O error, dev sdb, sector 5306584 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
[1409115.535652] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
[1409115.535672] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 50 f8 d8 00 00 20 00
[1409115.535681] blk_update_request: I/O error, dev sdb, sector 5306584 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0
[1409117.052082] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
[1409117.052090] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 50 f8 d8 00 00 20 00
[1409117.052096] blk_update_request: I/O error, dev sdb, sector 5306584 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
[1409117.168673] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
[1409117.168683] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 fe 24 00 00 00 40 00
[1409117.168688] blk_update_request: I/O error, dev sdb, sector 16655360 op 0x0:(READ) flags 0x80700 phys_seg 8 prio class 0
[1409122.659306] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
[1409122.659314] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 50 f8 d8 00 00 20 00
[1409122.659320] blk_update_request: I/O error, dev sdb, sector 5306584 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
[1409123.876888] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
[1409123.876896] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 50 f8 d8 00 00 20 00
[1409123.876902] blk_update_request: I/O error, dev sdb, sector 5306584 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0
[1409124.313159] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
[1409124.313167] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 50 f8 d8 00 00 20 00
[1409124.313173] blk_update_request: I/O error, dev sdb, sector 5306584 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
[1409126.527040] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
[1409126.527049] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 fd 6b 70 00 00 10 00
[1409126.527055] blk_update_request: I/O error, dev sdb, sector 16608112 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0
[1514091.502722] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
[1514091.502727] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 4a 97 68 00 00 20 00
[1514091.502730] blk_update_request: I/O error, dev sdb, sector 4888424 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
[1515193.248659] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
[1515193.248665] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 71 ab b8 00 00 20 00
[1515193.248669] blk_update_request: I/O error, dev sdb, sector 7449528 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0
[1569681.664940] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
[1569681.664948] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 f5 e1 b8 00 00 20 00
[1569681.664953] blk_update_request: I/O error, dev sdb, sector 16114104 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
[1684970.926098] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
[1684970.926106] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 50 ef f0 00 00 20 00
[1684970.926111] blk_update_request: I/O error, dev sdb, sector 5304304 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
[1872226.144953] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
[1872226.144961] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 fd 6e 70 00 00 20 00
[1872226.144967] blk_update_request: I/O error, dev sdb, sector 16608880 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
[1872226.234773] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
[1872226.234781] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 4a ec d0 00 00 20 00
[1872226.234788] blk_update_request: I/O error, dev sdb, sector 4910288 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
[1882244.186208] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
[1882244.186216] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 f3 e6 a8 00 00 20 00
[1882244.186222] blk_update_request: I/O error, dev sdb, sector 15984296 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
[1882247.156629] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist.
[1912483.941745] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
[1912483.941754] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 71 ab b8 00 00 20 00
[1912483.941760] blk_update_request: I/O error, dev sdb, sector 7449528 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0

This e.g. is known to cause desktop freezes for a couple of seconds up to a couple of minutes.

Windows is like a submarine. Open a window and serious problems will start.

[Member Jovi Fly]

Helpful

Up

0

::

Robin wrote:

Please check your dmesg output first. Maybe there is a hint. E.g. sometimes bad USB devices block with constantly repeated failure the desktop.

Open roxterm and enter

sudo dmesg

This e.g. is known to cause desktop freezes for a couple of seconds up to a couple of minutes.

It print a lot of lines saying the same except for the heading numbers:

[ 2645.720046] (In a green font) Wistron_btns (in an orange font) Unknown key code 10 (In a white font)

What could that mean?

Sorry for replaying so late, i didnt see that the reply opened a new page in the post…

EDIT:

I have found some links googling the answer from dmesg,

https://forums.linuxmint.com/viewtopic.php?t=238714
The user who writte the post have the same exact laptop model than mine

https://bugs.launchpad.net/linuxmint/+bug/1578358
This one is more recent, and decided to add “wistron_btns” to the blacklist

https://bugzilla.kernel.org/show_bug.cgi?id=42852
In this post the OP talks about how fight with the same problem

https://lwn.net/Articles/150579/
And here, the user throw some light into the source of the problem

https://forums.linuxmint.com/viewtopic.php?t=236043&start=20
Special mention to the user “Laugh2” in this post, who tested severals Linux distros using the same laptop model that i have. (Looks like we share the same issue and it could be the cause of jerkiness in the majority of the distros the he/she tried to install)

After read all this post, Looks like the problem comes from the keymap of wistron for the keyboard, as our model have a specifics buttons to toggle some functions. But i still dont know how i should procced

• This reply was modified 3 months, 4 weeks ago by Jovi Fly.

[Moderator caprea]

Helpful

Up

1

::

On the live boot screen there’s a box, where you can write boot parameters.
Could you try to add there
blacklist=wistron_btns

[Member Jovi Fly]

Helpful

Up

0

::

Done, the laptop is in the live desktop right now, and… IT´S FULLY FUNTIONAL! It solved the problem! But it make me doubt if this it´s the only way, because it disable some specifics buttons and leds from the laptop. Nevermind i never used them so i dont care too much.

Used again dmesg to check the output and… well… i see too much red lines, but at least the O.S. work as it should.

I cant thank you enough caprea, robin, anticapitalista and pun, i´m really gratefull for help me in this journey.

One last thing if is not too much. Should i worry of the errors that this dmesg display?

Attachments:

1. dmseg.odt

[Moderator caprea]

Helpful

Up

0

::

I’m not sure if this blacklisting will go over to an installed system, if you decide to have antiX installed.
There are easy ways to blacklist the module on an installation ,though.
Also, it still seems worth trying a different kernel, it may handles the wistron module better and might reduces the MTRR errors from dmesg which probably relate to the handling of the RAM.

[Member Jovi Fly]

Helpful

Up

0

::

Could be nice to know how to install a different kernel, but a more recent one or older? Because the error seems to keep in the lastest versions, and use older versions seems counterproductive. Also what happen with the RAM?

Right now i´m trying to format an old IDE HD i have from my chilhood laptop (Windows Millenium) to install AntiX, it also acts like a phantom, one times is recogniced by the system, and others dont. It´s that or guess how to reduce the partition´s size of the actual hard disk (came by default with XP) to have a dual booting in emergency situations.

[Moderator caprea]

Helpful

Up

0

::

To install the kernel on an installed system
menu > control-centre > Software > Package Installer > kernel
The one that is installed per default on 32bit is the oldest kernel. You can give the 4.19 or also the 5.10 kernel a try.
After installation reboot.The system now automatically boots to the newest version. If you have to fall back to any older kernel you can do this over the “advanced options” on the boot screen of the installed system.As long as you wont uninstall any kernel you can always fall back to them.

Normally it’s possible to install another kernel on the live usb-stick, but in your case it wont work I guess because you either boot from DVD or from stick with the help of the DVD and the usb and DVD have to have the same kernel for this.

To shrink a windows XP partition it sure is the best to use the XP system.

Please tell us if the module wistron_bts is still blacklisted on the installed system or if we need to blacklist it.

[Member Jovi Fly]

Helpful

Up

0

::

First of all, sorry. Yesterday was my birthday and I have been out of /home all the day.

Have for sure i´ll try more recent kernels once the installation ends. Also i´ll advise you about the wistron module.

Thanks so much for this tips so well explained and easy understandable caprea! 😀

I have so much questions regard x32 bits systems browser capabilities nowdays, but i dont want to abuse of your kindness. So instead bother you with tons of questions, could you point me where cloud i find the right posts please?

[Moderator Brian Masinick]

Helpful

Up

0

::

@Jovi Fly: I hope you enjoyed your birthday.

32-bit systems are not very well supported by most Linux distributions, yet antiX is an excellent exception.
Please feel free to ask about 32-bit things and we also seek feedback on our 32-bit implementation so we can keep it working as well as possible.

--
Brian Masinick

[Member Jovi Fly]

Helpful

Up

0

::

caprea wrote:

To install the kernel on an installed system
menu > control-centre > Software > Package Installer > kernel
The one that is installed per default on 32bit is the oldest kernel. You can give the 4.19 or also the 5.10 kernel a try.

Nice, i´ll try them once i can connect to my wi-fi network ( Either by running the laptop’s wireless network card(if i can) or with an external antenna)

After installation reboot. The system now automatically boots to the newest version. If you have to fall back to any older kernel you can do this over the “advanced options” on the boot screen of the installed system.As long as you wont uninstall any kernel you can always fall back to them.

Good good, nice feature! I´ll save this tip, thanks!

To shrink a windows XP partition it sure is the best to use the XP system.

I tried, but from windows i couldn´t shrink the system´s partition, at least not in XP. Neither via minitool wizard partition or similars.

BUT.. I could using the gparted from Live Desktop! Now i have a 20GB Partition for WinXP, 15 GB partition for AntiX and 3GB for Swap!

Please tell us if the module wistron_bts is still blacklisted on the installed system or if we need to blacklist it.

Well after installation the Desktop works pretty fluid, as should work. Also I selected the “Save changes from Live Desktop” option at the final when installing, so i suppose it conserved it blacklisted?

[Author]

Posts