- This topic has 25 replies, 3 voices, and was last updated Jan 7-6:37 am by andfree.
-
Posts
-
andfree
Hi. As I can see here, kernel 4.9 is reaching EOL in January. Any idea what should the users of old hardware do?
- This topic was modified 4 months, 1 week ago by andfree.
sybok
I would suggest to install and test the next LTS kernel available in antiX, i.e. 4.19 (EOL: Dec. 2024).
If it works well, then continue using it instead of 4.9.If it does not, you may search the forum for more details because I know similar question appeared in the past.
The consensus was that using older kernel may not be critically unsafe.Also, if there is a sufficient response indicating a high demand, you may ask for help with the situation.
One could politely ask @anticapitalista if he would be willing to make an antiX-build for 4.14 (EOL: Jan 2024)… but I am unsure whether a one-year postponement would be worth the effort.Suggested reading:
https://kernel.org/category/releases.html
https://www.antixforum.com/forums/topic/reasons-for-a-kernel-upgrade/I would suggest to install and test the next LTS kernel available in antiX, i.e. 4.19 (EOL: Dec. 2024).
If it works well, then continue using it instead of 4.9.Thank you. I installed the 4.19.202 kernel, but it doesn’t seem to make use of the whole screen.
The attached photo is cut up & down, and it doesn’t clarify what I say.
I mean that only a part in the middle of the screen is used, the rest is all black.- This reply was modified 4 months, 1 week ago by andfree.
- This reply was modified 4 months, 1 week ago by andfree.
Attachments:
sybok
I noticed that you mention kernel 4.19.202 and a newer version 4.19.0-256 is available.
Also, please make sure you installed an antiX kernel (an example package name ‘linux-image-4.19.202-antix*’).If this is already correct or after it is sorted out, then I would reboot to the older kernel 4.9 (when restarted, select advanced antiX options in the boot menu) and determine the monitor setting that works well either by starting arandr (available in antiX control centre) and exploring the current settings OR simply execute
xrandr
in terminal.
Then reboot to the 4.19 and attempt to duplicate the settings you want to achieve, again using arandr or series of below commands (with appropriately modified parameters):xrandr --listactivemonitors cvt 1280 960 60 xrandr --newmode '1280x960_60.00' 101.25 1280 1360 1488 1696 960 963 967 996 -hsync +vsync xrandr --addmode VGA-0 1152x864_60.00 xrandr --output VGA-0 --mode 1152x864_60.00The above example was used on my old 4:3 monitor (resolution 1280:960).
‘cvt’ is no longer available/installed on my system, nevertheless I guess it is ‘xcvt’ (judging from ‘apt-cache search cvt’).If it fails, then please post output of ‘inxi -Gxxx’ and do search forum; similar issues were already dealt with in the past.
E.g. a search with keywords ‘set resolution monitor’ points to several threads including
https://www.antixforum.com/forums/topic/asus-eeepc-900-antix21-display-resoluton-problem/
https://www.antixforum.com/forums/topic/antix-will-not-set-the-native-monitor-resolution/- This reply was modified 4 months, 1 week ago by sybok. Reason: newer kernel, forum links
Thanks a lot. I installed linux-image-4.19.0-256-antix.1-486-smp, but the problem still remains.
About the older kernel 4.9:
$ xrandr Screen 0: minimum 320 x 200, current 1024 x 768, maximum 4096 x 4096 VGA-1 disconnected primary (normal left inverted right x axis y axis) LVDS-1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.00*+ 800x600 59.86 640x480 59.38 720x400 59.55 640x400 59.95 640x350 59.77 TV-1 disconnected (normal left inverted right x axis y axis)When I start arandr, I see an “LVDS-1” on the upper left part of the window.
About the newer kernel 4.19:
$ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 640 x 480, current 640 x 480, maximum 640 x 480 default connected 640x480+0+0 0mm x 0mm 640x480 60.00*When I start arandr, I see a “default” on the upper left part of the window.
Could you help me to make the appropriate modifications to the parameters of the commands, please?
sybok
I guess that the fact that ‘xrandr’ does not display additional resolutions, this may be the case for further reading in the suggested threads.
Perhaps, one need to modify the grub setting related to VESA as mentioned there.Anyway, the modified commands/parameters should be something such as:
xrandr --newmode '1024x768_60.00' <these parameters were determined from output of the command 'cvt 1024 768 60'!> xrandr --addmode VGA-0 1024x768_60.00 xrandr --output VGA-0 --mode 1024x768_60.00If you have ‘cvt’ installed/available and the output returns an error, then you definitely need a different approach.
Many thanks for your help.
If you have ‘cvt’ installed/available and the output returns an error, then you definitely need a different approach.
I’m afraid that this is the case.
$ xrandr --listactivemonitors xrandr: Failed to get size of gamma for output default Monitors: 1 0: +default 640/169x480/127+0+0 default $ cvt 1024 768 60 # 1024x768 59.92 Hz (CVT 0.79M3) hsync: 47.82 kHz; pclk: 63.50 MHz Modeline "1024x768_60.00" 63.50 1024 1072 1176 1328 768 771 775 798 -hsync +vsync $ xrandr --newmode '1024x768_60.00' 63.50 1024 1072 1176 1328 768 771 775 798 -hsync +vsync xrandr: Failed to get size of gamma for output default $ xrandr --addmode VGA-0 1024x768_60.00 xrandr: Failed to get size of gamma for output default xrandr: cannot find output "VGA-0" $ xrandr --output VGA-0 --mode 1024x768_60.00 xrandr: Failed to get size of gamma for output default warning: output VGA-0 not found; ignoring $ inxi -Gxxx Graphics: Device-1: NVIDIA NV17M [GeForce4 420 Go] vendor: Toshiba driver: rivafb v: kernel arch: Kelvin bus-ID: 01:00.0 chip-ID: 10de:0175 class-ID: 0300 Display: server: X.Org v: 1.20.11 driver: X: loaded: fbdev,nouveau unloaded: modesetting,vesa alternate: nv gpu: rivafb display-ID: :0.0 screens: 1 Screen-1: 0 s-res: 640x480 s-dpi: 96 s-size: 169x127mm (6.65x5.00") s-diag: 211mm (8.32") Monitor-1: default res: 640x480 hz: 60 size: N/A modes: N/A OpenGL: renderer: llvmpipe (LLVM 11.0.1 128 bits) v: 4.5 Mesa 20.3.5 compat-v: 3.1 direct render: Yessybok
Please, try the commands again with ‘VGA-0’ (my monitor) replaced by ‘default’; the output of ‘xrandr –listactivemonitors’ indicates that yours is named ‘default’
I did not stress that this description/identifier may need to be modified as well in my previous post.sybok
@andfree: Sent me a private-message with failed ‘xrandr’ commands, the error was mostly
xrandr: Failed to get size of gamma for output default
xrandr: Configure crtc 0 failedI guess the above failures of ‘xrandr’ indicate another approach is needed and searching the forum for similar issues/problems reported is probably the best way to go. You could also private-message someone (based on the suggested forum-search/reading) who seems more knowledgeable than me and could point you to a better direction.
Comment on not being able to post:
The forum has experienced some instability in the last few days (I was unable to load the main-page and/or reply and @andfree to post it).
If you cannot post, sometimes, the reason is a spam/code-filter and some characters need to be modified/edited. Posting the code/commands/output in a TXT file (even scripts may need the extension to be renamed to ‘txt’ from e.g. ‘sh’) can circumvent it.Test. I’ll edit this post later.
$ xrandr --newmode '1024x768_60.00' 63.50 1024 1072 1176 1328 768 771 775 798 -hsync +vsync xrandr: Failed to get size of gamma for output default $ xrandr --addmode default 1024x768_60.00 xrandr: Failed to get size of gamma for output default $ xrandr --output default --mode 1024x768_60.00 xrandr: Failed to get size of gamma for output default xrandr: Configure crtc 0 failed- This reply was modified 4 months, 1 week ago by andfree.
sybok
You can also perform a general web-search with the keywords being as below
NVIDIA "NV17M" "GeForce" debianOne of the results is
https://www.antixforum.com/forums/topic/second-monitor-no-image/
with (almost) the same graphics card.Please, modify (probably you have to private-message a moderator if you no longer can) the title of the topic to a more appropriate version reflecting the graphics issues with 4.19.
E.g. “4.9 EOL, Nvidia GeForce4 issues with 4.19”.- This reply was modified 4 months, 1 week ago by sybok. Reason: Suggesting title modification
caprea
Please try to add the bootparameter
nouveau.modeset=1Please try to add the bootparameter
nouveau.modeset=1Thank you. But, how to do this? Have I modify a file or add the parameter at the grub screen. I tried the latter, but I couldn’t find how to save the modification.
See the next post.
- This reply was modified 4 months, 1 week ago by andfree.
- This reply was modified 4 months, 1 week ago by andfree.
Out of topic:
Test. I’ll edit this post later.
When I try to edit that post, a “403 Forbidden” message appears again, as yesterday, when I couldn’t post at all. Now I have no problem to post, I only can’t edit that one post (there’s no serious reason to do so, the initial purpose for both of the posts was just to test if I can post).
- You must be logged in to reply to this topic.
