Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #246026 > unrolled thread

Re: system lock up, not sure if related to "your system is too slow"

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: system lock up, not sure if related to "your system is too slow" Johann Klammer <klammerj@a1.net> - 2022-03-07 19:20 +0100
    Re: system lock up, not sure if related to "your system is too slow" songbird <songbird@anthive.com> - 2022-03-08 03:20 +0100
      Re: system lock up, not sure if related to "your system is too slow" Jörg-Volker Peetz <jvpeetz@web.de> - 2022-03-08 10:10 +0100
        Re: system lock up, not sure if related to "your system is too slow" Greg Wooledge <greg@wooledge.org> - 2022-03-08 13:30 +0100
          Re: system lock up, not sure if related to "your system is too slow" songbird <songbird@anthive.com> - 2022-03-08 16:30 +0100
        Re: system lock up, not sure if related to "your system is too slow" songbird <songbird@anthive.com> - 2022-03-08 18:00 +0100
          Re: system lock up, not sure if related to "your system is too slow" Jörg-Volker Peetz <jvpeetz@web.de> - 2022-03-10 11:30 +0100
            Re: system lock up, not sure if related to "your system is too slow" songbird <songbird@anthive.com> - 2022-03-10 15:20 +0100
              Re: system lock up, not sure if related to "your system is too slow" Jörg-Volker Peetz <jvpeetz@web.de> - 2022-03-10 19:50 +0100
                Re: system lock up, not sure if related to "your system is too slow" songbird <songbird@anthive.com> - 2022-03-11 07:10 +0100
              Tiny fonts, was Re: system lock up, not sure if related to "your  system is too slow" David Wright <deblis@lionunicorn.co.uk> - 2022-03-14 02:10 +0100
                Re: Tiny fonts, was Re: system lock up, not sure if related to  "your system is too slow" songbird <songbird@anthive.com> - 2022-03-14 05:40 +0100

#246026 — Re: system lock up, not sure if related to "your system is too slow"

On 03/06/2022 09:10 PM, songbird wrote:
> Johann Klammer wrote:
> ...
>> Likely the xorg video driver.
>> Try installing the alternatives possible for your hardware.
>> avoid the closed source nvidias.
>> They've had the hard lock ups since about 2000.
>> nouveau and framebuffer ones will probably work.
> 
> 
>   hi, thanks for the hints, i just have the built in GPU for the CPU:
> 
> 
> # lscpu
> Architecture:            x86_64
>   CPU op-mode(s):        32-bit, 64-bit
>   Address sizes:         39 bits physical, 48 bits virtual
>   Byte Order:            Little Endian
> CPU(s):                  8
>   On-line CPU(s) list:   0-7
> Vendor ID:               GenuineIntel
>   BIOS Vendor ID:        Intel(R) Corporation
>   Model name:            Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz
>     BIOS Model name:     Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz
>     CPU family:          6
>     Model:               158
>     Thread(s) per core:  1
>     Core(s) per socket:  8
>     Socket(s):           1
>     Stepping:            13
>     CPU max MHz:         4900.0000
>     CPU min MHz:         800.0000
>     BogoMIPS:            7200.00
>     Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mc
>                          a cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss 
>                          ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art
>                           arch_perfmon pebs bts rep_good nopl xtopology nonstop_
>                          tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cp
>                          l vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid ss
>                          e4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes 
>                          xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_f
>                          ault invpcid_single ssbd ibrs ibpb stibp ibrs_enhanced 
>                          tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase t
>                          sc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed a
>                          dx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsa
>                          ves dtherm ida arat pln pts hwp hwp_notify hwp_act_wind
>                          ow hwp_epp md_clear flush_l1d arch_capabilities
> Virtualization features: 
>   Virtualization:        VT-x
> Caches (sum of all):     
>   L1d:                   256 KiB (8 instances)
>   L1i:                   256 KiB (8 instances)
>   L2:                    2 MiB (8 instances)
>   L3:                    12 MiB (1 instance)
> NUMA:                    
>   NUMA node(s):          1
>   NUMA node0 CPU(s):     0-7
> 
> 
>   the following shows installed:
> 
> 
> # dpkg -l | grep video-intel
> 
> ii  xserver-xorg-video-intel             2:2.99.917+git20210115-1           amd64        X.Org X server -- Intel i8xx, i9xx display driver
> 
> 
> # uname -a
> Linux rant 5.16.0-3-amd64 #1 SMP PREEMPT Debian 5.16.11-1 (2022-02-25) x86_64 GNU/Linux
> 
> 
> songbird
> 
xserver-xorg-video-intel
update that one. if that doesn't help, 
try 
xserver-xorg-video-fbdev
and as alast try
xserver-xorg-video-vesa
(you may have to edit /etc/X11/xorg.conf and possibly mess with kernel 
modesetting, initrd and bootime parameters to get an acceptable resolution)
you'll lose all `acceleration' as usual.
but it might run more stable.
no internet or video but ok for text processing(mcedit/pico/nano/vim but not openoffice)

[toc] | [next] | [standalone]

#246038

Johann Klammer wrote:
...
> xserver-xorg-video-intel
> update that one. if that doesn't help, 

  already at the most current version in unstable.  i can
reinstall it without any problem.  all done.


> try 
> xserver-xorg-video-fbdev

  same as above.


> and as alast try
> xserver-xorg-video-vesa

  same as above.


> (you may have to edit /etc/X11/xorg.conf and possibly mess with kernel 
> modesetting, initrd and bootime parameters to get an acceptable resolution)
> you'll lose all `acceleration' as usual.
> but it might run more stable.
> no internet or video but ok for text processing(mcedit/pico/nano/vim but not openoffice)

  it hasn't been terribly unstable, just a once in a while hard
lock up.  i'd like to figure out which part is the problem and
not wonder which it might be.

  one reason i run testing is to find issues before they go into
stable.  unfortunately, i'm not as well versed in this sort of
debugging as i'd like to be so i get to learn some new things.  :)

  if i have to get source code and compile it locally with certain
flags for debugging or whatever that is ok with me just so long
as it gets me further along in figuring out what this specific
problem is and what chunk of code it is coming from.


  songbird

[toc] | [prev] | [next] | [standalone]

#246044

As far as I know, the xserver-xorg-video-intel is deprecated for modern Intel 
CPUs. With an Intel Core i7 7700 the kernel `modesetting` works well here:

Something like

Section "Device"
   Identifier  "Intel Graphics"
   Driver      "modesetting"
EndSection

in `/etc/X11/xorg.conf.d/20-modesetting.conf` or `/etc/X11/xorg.conf`.

Keep just the `xserver-xorg-video-dummy` on the system for dependencies.
And for video acceleration the package `intel-media-va-driver`.

Regards,
Jörg.

[toc] | [prev] | [next] | [standalone]

#246051

On Tue, Mar 08, 2022 at 10:07:19AM +0100, Jörg-Volker Peetz wrote:
> As far as I know, the xserver-xorg-video-intel is deprecated for modern
> Intel CPUs. With an Intel Core i7 7700 the kernel `modesetting` works well
> here:
> 
> Something like
> 
> Section "Device"
>   Identifier  "Intel Graphics"
>   Driver      "modesetting"
> EndSection
> 
> in `/etc/X11/xorg.conf.d/20-modesetting.conf` or `/etc/X11/xorg.conf`.
> 
> Keep just the `xserver-xorg-video-dummy` on the system for dependencies.
> And for video acceleration the package `intel-media-va-driver`.

You shouldn't even need to create that xorg.conf.d snippet.  It should
just work automatically.

You *will* however most likely need to install some non-free firmware
packages, e.g. firmware-misc-nonfree .

unicorn:~$ sudo dmesg | grep -i firmware
[...]
[   10.387158] i915 0000:00:02.0: firmware: direct-loading firmware i915/kbl_dmc_ver1_04.bin
[   10.387505] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)

unicorn:~$ dpkg -L firmware-misc-nonfree | grep i915/kbl_dmc_ver1_04.bin
/lib/firmware/i915/kbl_dmc_ver1_04.bin

(That's from my system, which is not necessarily the same model of Intel
onboard graphics as the OP's, but all of the modern Intel graphics chipsets
need non-free firmware for acceleration to work.)

[toc] | [prev] | [next] | [standalone]

#246065

Greg Wooledge wrote:
...
> You shouldn't even need to create that xorg.conf.d snippet.  It should
> just work automatically.

   removing the xserver-xorg-video-intel package left me with a
command line only system.  so i had to reinstall that.


> You *will* however most likely need to install some non-free firmware
> packages, e.g. firmware-misc-nonfree .
>
> unicorn:~$ sudo dmesg | grep -i firmware
> [...]
> [   10.387158] i915 0000:00:02.0: firmware: direct-loading firmware i915/kbl_dmc_ver1_04.bin
> [   10.387505] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
>
> unicorn:~$ dpkg -L firmware-misc-nonfree | grep i915/kbl_dmc_ver1_04.bin
> /lib/firmware/i915/kbl_dmc_ver1_04.bin
>
> (That's from my system, which is not necessarily the same model of Intel
> onboard graphics as the OP's, but all of the modern Intel graphics chipsets
> need non-free firmware for acceleration to work.)

  i didn't have firmware-misc-nonfree installed so now that is
so perhaps that will help.  thanks.


  songbird

[toc] | [prev] | [next] | [standalone]

#246071

Jörg-Volker Peetz wrote:
> As far as I know, the xserver-xorg-video-intel is deprecated for modern Intel 
> CPUs. With an Intel Core i7 7700 the kernel `modesetting` works well here:
>
> Something like
>
> Section "Device"
>    Identifier  "Intel Graphics"
>    Driver      "modesetting"
> EndSection
>
> in `/etc/X11/xorg.conf.d/20-modesetting.conf` or `/etc/X11/xorg.conf`.
>
> Keep just the `xserver-xorg-video-dummy` on the system for dependencies.
> And for video acceleration the package `intel-media-va-driver`.

  i did install the dummy package and uninstalled the intel
but that did not leave me with a system that booted to the
desktop so i put it back.


  songbird

[toc] | [prev] | [next] | [standalone]

#246150

songbird wrote on 08/03/2022 16:35:
> Jörg-Volker Peetz wrote:
>> As far as I know, the xserver-xorg-video-intel is deprecated for modern Intel
>> CPUs. With an Intel Core i7 7700 the kernel `modesetting` works well here:
>>
>> Something like
>>
>> Section "Device"
>>     Identifier  "Intel Graphics"
>>     Driver      "modesetting"
>> EndSection
>>
>> in `/etc/X11/xorg.conf.d/20-modesetting.conf` or `/etc/X11/xorg.conf`.
>>
>> Keep just the `xserver-xorg-video-dummy` on the system for dependencies.
>> And for video acceleration the package `intel-media-va-driver`.
> 
>    i did install the dummy package and uninstalled the intel
> but that did not leave me with a system that booted to the
> desktop so i put it back.
> 
> 
>    songbird
> 
Did you take a look into `dmesg -l err` and `Xorg.log` in this case?

Regards,
Jörg.

[toc] | [prev] | [next] | [standalone]

#246159

Jörg-Volker Peetz wrote:
>songbird wrote:
... 
>>    i did install the dummy package and uninstalled the intel
>> but that did not leave me with a system that booted to the
>> desktop so i put it back.
>> 
> Did you take a look into `dmesg -l err` and `Xorg.log` in this case?

  no, i didn't, too hard for me to see or sit to squint at the 
screen to be able to read.  the login prompt and screen fonts
are so small that i type it all in by memory and can usually 
get it right.  i used to have it set up where all the terminal 
fonts would come up with a big enough font that i'd not have 
that problem, but i've not been dealing much with the raw 
terminal screens enough to do it on this system yet.


  songbird

[toc] | [prev] | [next] | [standalone]

#246169

songbird wrote on 10/03/2022 14:44:
> Jörg-Volker Peetz wrote:
>> songbird wrote:
> ...
>>>     i did install the dummy package and uninstalled the intel
>>> but that did not leave me with a system that booted to the
>>> desktop so i put it back.
>>>
>> Did you take a look into `dmesg -l err` and `Xorg.log` in this case?
> 
>    no, i didn't, too hard for me to see or sit to squint at the
> screen to be able to read.  the login prompt and screen fonts
> are so small that i type it all in by memory and can usually
> get it right.  i used to have it set up where all the terminal
> fonts would come up with a big enough font that i'd not have
> that problem, but i've not been dealing much with the raw
> terminal screens enough to do it on this system yet.
> 
> 
>    songbird
> 
Maybe this website can help with the console font size:

https://www.linux.com/topic/desktop/how-change-your-linux-console-fonts/

Regards,
Jörg.

[toc] | [prev] | [next] | [standalone]

#246185

Jörg-Volker Peetz wrote:
...
> Maybe this website can help with the console font size:
>
> https://www.linux.com/topic/desktop/how-change-your-linux-console-fonts/

  interesting...

  after trying various things out and getting various fonts installed
i found that simply changing /etc/default/console-setup did not make
the changes effective for the linux virtual terminals, but running:

# dpkg-reconfigure console-setup

would.  in nosing around i found comments about some things being
required made available in other locations so that they could be
used during early boot stage so it now makes sense as to why just
changing the file doesn't do everything you need.  (/etc/console-setup 
contains the files needed).


  songbird

[toc] | [prev] | [next] | [standalone]

#246291 — Tiny fonts, was Re: system lock up, not sure if related to "your system is too slow"

On Thu 10 Mar 2022 at 08:44:10 (-0500), songbird wrote:
> Jörg-Volker Peetz wrote:

> > Did you take a look into `dmesg -l err` and `Xorg.log` in this case?
> 
>   no, i didn't, too hard for me to see or sit to squint at the 
> screen to be able to read.  the login prompt and screen fonts
> are so small that i type it all in by memory and can usually 
> get it right.  i used to have it set up where all the terminal 
> fonts would come up with a big enough font that i'd not have 
> that problem, but i've not been dealing much with the raw 
> terminal screens enough to do it on this system yet.

The trick I use to workaround this problem is:

. When the grub screen appears, press "E" instead of Return,

. Look at the Grub script that appears (you don't need to be
  able to actually /read/ it).

. The bottom line is the initrd line, preceded by a comment line,
  The third line from the bottom is the kernel line.

. Press <Down> enough times to reach the bottom (you can just see
  the cursor appear below the bottom line), then <Up> twice, followed
  by <Left>. That puts the cursor at the end of the kernel line.

. Type <Space> video=1280x720

. Type Ctrl-X to boot.

For 1280x720, you could try 1920x1080, or 960x540, according
to how large you want the characters. With a screen having
a wide aspect ratio, you might try 1600x900, 800x450, and
so on (ie native resolution ÷ small integer).

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#246297 — Re: Tiny fonts, was Re: system lock up, not sure if related to "your system is too slow"

David Wright wrote:
...
> For 1280x720, you could try 1920x1080, or 960x540, according
> to how large you want the characters. With a screen having
> a wide aspect ratio, you might try 1600x900, 800x450, and
> so on (ie native resolution ÷ small integer).

  thank you, i've already got that taken care of by the
what i wrote in the other message.  it wasn't enough to
just change the font, but rerunning the configure step
which copied the relevant files to /etc/<someplace> so
they were available during early boot stage.

  i've not had any more lock ups recently but i'm also
running a different kernel now so perhaps it was a bug in
there someplace that got squashed.  for that i would need
some kind of way to trace everything that is running and
put it in a log that persists, but not so much that it
plugs up my entire system.  i'm hoping it's just fixed and
gone, but ...


  songbird

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web