Porteus does not start on ThinClient not always

Get help with MATE specific problems
Post Reply
alubypass
White ninja
White ninja
Posts: 6
Joined: 12 Sep 2019, 14:01
Distribution: Porteus 4

Porteus does not start on ThinClient not always

Post#1 by alubypass » 18 Sep 2019, 18:28

Hello, folks,
I noticed another problem.
I am using a Fujitsu Futro S540 ThinClient with Porteus 4 Mate in the 64 bit version. I noticed the following problem. Every second start of the ThinClient does not start the ThinClient anymore. It expresses itself in the fact that the power lamp lights up, but the screen remains black. After dragging the BIOS battery the ThinClient starts with Porteus without any problems. But if I start the computer after two more starts, the screen is black again.
Enclosed the logs, from the client:

grep over all logs that contains errors:

dmesg

Code: Select all

[    0.078513] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
[    0.920501] REISERFS warning (device loop11): sh-2006 read_super_block: bread failed (dev loop11, block 2, size 4096)
[    0.920512] REISERFS warning (device loop11): sh-2006 read_super_block: bread failed (dev loop11, block 16, size 4096)
[    0.968844] REISERFS warning (device loop17): sh-2006 read_super_block: bread failed (dev loop17, block 16, size 4096)
[    0.982512] REISERFS warning (device loop19): sh-2006 read_super_block: bread failed (dev loop19, block 2, size 4096)
[    0.982519] REISERFS warning (device loop19): sh-2006 read_super_block: bread failed (dev loop19, block 16, size 4096)
[    0.995757] REISERFS warning (device loop21): sh-2006 read_super_block: bread failed (dev loop21, block 16, size 4096)
[    2.796410] i915 0000:00:02.0: Direct firmware load for i915/glk_dmc_ver1_04.bin failed with error -2
[    2.796414] i915 0000:00:02.0: Failed to load DMC firmware i915/glk_dmc_ver1_04.bin. Disabling runtime power management.
syslog

Code: Select all

Sep 17 15:13:33 porteus kernel: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
Sep 17 15:13:33 porteus kernel: i915 0000:00:02.0: Failed to load DMC firmware i915/glk_dmc_ver1_04.bin. Disabling runtime power management.
Sep 17 15:15:27 porteus kernel: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
Sep 17 15:15:27 porteus kernel: i915 0000:00:02.0: Failed to load DMC firmware i915/glk_dmc_ver1_04.bin. Disabling runtime power management.
Sep 17 15:30:54 porteus kernel: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
Sep 17 15:30:55 porteus kernel: i915 0000:00:02.0: Failed to load DMC firmware i915/glk_dmc_ver1_04.bin. Disabling runtime power management.
Here starts the part after dragging the BIOS battery

Code: Select all

Jan  1 01:00:17 porteus kernel: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
Jan  1 01:00:18 porteus kernel: i915 0000:00:02.0: Failed to load DMC firmware i915/glk_dmc_ver1_04.bin. Disabling runtime power management.
Jan  1 01:08:36 porteus kernel: REISERFS warning (device loop11): sh-2006 read_super_block: bread failed (dev loop11, block 2, size 4096)
Jan  1 01:08:36 porteus kernel: REISERFS warning (device loop11): sh-2006 read_super_block: bread failed (dev loop11, block 16, size 4096)
Jan  1 01:08:36 porteus kernel: REISERFS warning (device loop17): sh-2006 read_super_block: bread failed (dev loop17, block 16, size 4096)
Jan  1 01:08:36 porteus kernel: REISERFS warning (device loop19): sh-2006 read_super_block: bread failed (dev loop19, block 2, size 4096)
Jan  1 01:08:36 porteus kernel: REISERFS warning (device loop19): sh-2006 read_super_block: bread failed (dev loop19, block 16, size 4096)
Jan  1 01:08:36 porteus kernel: REISERFS warning (device loop21): sh-2006 read_super_block: bread failed (dev loop21, block 16, size 4096)
Jan  1 01:08:36 porteus kernel: i915 0000:00:02.0: Direct firmware load for i915/glk_dmc_ver1_04.bin failed with error -2
Jan  1 02:08:39 porteus kernel: print_req_error: I/O error, dev loop26, sector 0
Jan  1 02:08:39 porteus kernel: print_req_error: I/O error, dev loop26, sector 0
Jan  1 02:08:39 porteus kernel: Buffer I/O error on dev loop26, logical block 0, async page read
Jan  1 02:08:39 porteus kernel: print_req_error: I/O error, dev loop26, sector 0
Jan  1 02:08:39 porteus kernel: Buffer I/O error on dev loop26, logical block 0, async page read
Jan  1 02:08:39 porteus kernel: print_req_error: I/O error, dev loop26, sector 0
Jan  1 02:08:39 porteus kernel: Buffer I/O error on dev loop26, logical block 0, async page read
Jan  1 02:08:39 porteus kernel: print_req_error: I/O error, dev loop26, sector 0
Jan  1 02:08:39 porteus kernel: Buffer I/O error on dev loop26, logical block 0, async page read
Jan  1 02:08:39 porteus kernel: print_req_error: I/O error, dev loop26, sector 0
Jan  1 02:08:39 porteus kernel: Buffer I/O error on dev loop26, logical block 0, async page read
Jan  1 02:08:39 porteus kernel: print_req_error: I/O error, dev loop26, sector 0
Jan  1 02:08:39 porteus kernel: Buffer I/O error on dev loop26, logical block 0, async page read
Jan  1 02:08:39 porteus kernel: print_req_error: I/O error, dev loop26, sector 24
Jan  1 02:08:39 porteus kernel: Buffer I/O error on dev loop26, logical block 3, async page read
Do you have any idea why the ThinClient is causing these problems and how to narrow down the problem?

Thank you very much for your help !

Post Reply