View previous topic :: View next topic |
Author |
Message |
SarahS93 l33t
Joined: 21 Nov 2013 Posts: 730
|
Posted: Sun Mar 29, 2020 12:10 am Post subject: running terminal without x in 2560x1440 - very slow screen |
|
|
i do run a system without any x server in 2560x1440.
the boot screen runs very slow, only 10 lines in a second or so.
if i logged in and than run the filemanager mc, i can see how the screen build up from top to bottom in a second.
to i need any special driver or configuration?
here is my grub config (i do run grub-2.04-r1) Code: | set timeout=5
set default=0
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
menuentry "kernel-4.9.210-x86_64-gentoo-r1" {
linux /kernel-4.9.210-x86_64-gentoo-r1 \
rootfstype=btrfs \
crypt_root=/dev/nvme0n1p2 \
real_root=/dev/mapper/root \
root_trim=yes \
net.ifnames=0 \
ro
initrd /initramfs-4.9.210-gentoo.img
set gfxpayload=2560x1440x32
} |
|
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54785 Location: 56N 3W
|
Posted: Sun Mar 29, 2020 12:45 am Post subject: |
|
|
SarahS93,
Post your output
Put dmesg onto a pastebin
Put your kernel .config onto a pastebin.
It all depends on your GPU, which the first command will tell, the console driver in use, which dmesg will tell.
The kernel .config will hep to choose a better console driver ... maybe.
If you use a binary blob driver in Xorg, we need to know, as that restricts the options. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
SarahS93 l33t
Joined: 21 Nov 2013 Posts: 730
|
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54785 Location: 56N 3W
|
Posted: Wed Apr 01, 2020 9:40 pm Post subject: |
|
|
SarahS93,
Your out would be really good.
I can get it out of dmesg but scanning dmesg with Mk1 eyeball is rather error prone.
Code: | [ 0.284983] pci 0000:00:02.0: [8086:3e92] type 00 class 0x030000 | tells that you have an Intel UHD Graphics 630 (Desktop) graphics card.
There may be another graphics card too. If so I missed it.
Code: | [ 0.651405] uvesafb: failed to execute /sbin/v86d | was removed a long time ago, so uvesafb is broken.
You may as well remove it from your kernel because /sbin/v86d isn't going to be fixed.
Your console is running on Code: | [ 0.877439] fb0: VESA VGA frame buffer device | which will do scrolling by redrawing the entire screen.
That's slow, as you noticed.
I would expect your system to be using intelfb for the console as provided by the DRM system.
Maybe your Code: | # Linux/x86 4.9.210-gentoo Kernel Configuration | is too old?
As its a LTS kernel, it gets security updates but drivers for new hardware are not backported. 4.9 is just over 3 years old.
Update to 5.4 if you can. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
Tony0945 Watchman
Joined: 25 Jul 2006 Posts: 5127 Location: Illinois, USA
|
Posted: Thu Apr 02, 2020 3:03 am Post subject: |
|
|
NeddySeagoon wrote: | Maybe your Code: | # Linux/x86 4.9.210-gentoo Kernel Configuration | is too old?
As its a LTS kernel, it gets security updates but drivers for new hardware are not backported. 4.9 is just over 3 years old.
Update to 5.4 if you can. |
I'm running 4.9.217 as the backup kernel on my server. I recently dropped 4.4.X as the Mate applets multiplied like bunny rabbits with no other change.
It does seem the OP is quite a few security udates behind. One or two come out weekly.
Running 4.14.174 (stable amd64) on the server and 5.4.28 on the workstations.
Server hardware is only two or three years old. One workstation is one year old, the other is eleven years old. |
|
Back to top |
|
|
SarahS93 l33t
Joined: 21 Nov 2013 Posts: 730
|
Posted: Wed Apr 08, 2020 10:36 pm Post subject: |
|
|
i do now run with kernel 5.4.28. all oke. the terminal without x runs now much better.
dmesg |grep intel
[ 1.243525] fb0: switching to inteldrmfb from VESA VGA
is this oke?
in the terminal without x, if run there midnight commer i do have some questionmakrs.
in a terminal window in x the questionmarks are not there. how can i fix this? |
|
Back to top |
|
|
krinn Watchman
Joined: 02 May 2003 Posts: 7470
|
Posted: Thu Apr 09, 2020 10:31 am Post subject: |
|
|
SarahS93 wrote: | in the terminal without x, if run there midnight commer i do have some questionmakrs.
in a terminal window in x the questionmarks are not there. how can i fix this? |
When you get ? reather than the symbol, it's a localization problem, something for https://wiki.gentoo.org/wiki/Localization/Guide
But if it's already set correctly, all you should have to do is enabling it in console too with unicode="yes" in /etc/rc.conf |
|
Back to top |
|
|
Tony0945 Watchman
Joined: 25 Jul 2006 Posts: 5127 Location: Illinois, USA
|
Posted: Thu Apr 09, 2020 1:58 pm Post subject: |
|
|
I had that question mark problem running "make menuconfig" in a VT instead of an xterm. I fixed it with: Code: | #test if running on a bare VT
if [ "$TERM" = linux ]; then
TERM=xterm #so make munuconfig will display correctly
fi
|
The problem relates to terminal encoding. My fix was a quick fix for the specific problem.
Yours, I feel, definitely is with terminal encoding. You'll have to dig further for a general solution.
Perhaps an international character set will help.
EDIT: spelling
Last edited by Tony0945 on Thu Apr 09, 2020 6:39 pm; edited 1 time in total |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54785 Location: 56N 3W
|
Posted: Thu Apr 09, 2020 6:37 pm Post subject: |
|
|
SarahS93,
Code: | [ 1.243525] fb0: switching to inteldrmfb from VESA VGA | is good. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
SarahS93 l33t
Joined: 21 Nov 2013 Posts: 730
|
Posted: Sat Apr 18, 2020 1:23 am Post subject: |
|
|
on an other computer i run now kernel 5.4.28 too.
the system have a nvidia gpu card.
i dont use the nvida-drivers anymore.
nouveau driver is in use now.
dmesg |grep VESA
Code: | [ 0.737271] fb0: VESA VGA frame buffer device
[ 0.741650] fb0: switching to nouveaufb from VESA VGA |
in kde there are no problems with midnight commander in the programm konsole
in the terminal (strg f1) i have the questionmark problem too.
and i have the problem that i can not run my favorite skin too.
i become allways the message that i do not run a 256 color terminal.
with " export TERM=xterm-256color" and than mc i can run mc with my fav. skin.
but the questionmark problem is not gone.
unicode="yes" is set in /etc/rc.conf
what should i have into the /etc/conf.d/consolefont file? |
|
Back to top |
|
|
|