Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

Boot Screen/Log Screen - adequate font for my 12.1" screen

Message
Author
User avatar
penguin
Forum Regular
Forum Regular
Posts: 276
Joined: Wed Jan 04, 2017 3:15 pm

Boot Screen/Log Screen - adequate font for my 12.1" screen

#1 Post by penguin » Fri Nov 09, 2018 2:42 am

Just a decided to give up from my Linux MX 17.1 32 bit and to have only 64 bit versions in all my machines.

Using qt4-fsarchiver I copied my MX Linux 17.1 installed on Elitebook HP 8570W 15.6 " screen into my Lenovo X201i .
Only small thinks yo corrections on fstab. ( I have described HOW TO move your Linux from one machine to another(using qt4-fsarchiver) on my ancient posts in this forum)

But... The previous install of MX Linux 17.1 - 32 bit (installed originally) on my Lenovo X201i had a better/good reading fonts in boot/log in / log out screen (adequate for my 14 " screen on Lenovo).

Now all logs appears in a bigger fonts and messages word wraps on next rows of the screen.

How I can have a smaller fonts adequate for my 12.1" screen ?

P.S.
Just only one Warning is shown during the boot screen, but A Im not able to see it becuase it goes fast .
Will be worthy to have its utility that reads kernel/logs ( some one needs to go and hunt for this log kernel/log screens in various logs dwelled in /var/log.
The way how the read kernel messages displays in terminal with dmesg -k is not so comfortable.Anyway I think that a yad programmed utility can simplify the job.

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 2068
Joined: Wed Apr 11, 2018 5:09 pm

Re: Boot Screen/Log Screen - adequate font for my 12.1" screen

#2 Post by fehlix » Fri Nov 09, 2018 8:52 am

penguin wrote:
Fri Nov 09, 2018 2:42 am
Using qt4-fsarchiver I copied my MX Linux 17.1 installed on Elitebook HP 8570W 15.6 " screen into my Lenovo X201i .
You might try using MX Snappshot to install, and see whether this fixes the issues you mentioned.
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 9655
Joined: Sun Dec 16, 2007 1:17 pm

Re: Boot Screen/Log Screen - adequate font for my 12.1" screen

#3 Post by dolphin_oracle » Fri Nov 09, 2018 10:05 am

IIRC, you can specify the resolution grub displays in the /etc/default/grub file.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad T530 - MX-17
lenovo s21e & 100s - antiX-17, MX17(live-usb)
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
penguin
Forum Regular
Forum Regular
Posts: 276
Joined: Wed Jan 04, 2017 3:15 pm

Re: Boot Screen/Log Screen - adequate font for my 12.1" screen

#4 Post by penguin » Fri Nov 09, 2018 4:31 pm

fehlix wrote:
Fri Nov 09, 2018 8:52 am
penguin wrote:
Fri Nov 09, 2018 2:42 am
Using qt4-fsarchiver I copied my MX Linux 17.1 installed on Elitebook HP 8570W 15.6 " screen into my Lenovo X201i .
You might try using MX Snappshot to install, and see whether this fixes the issues you mentioned.
@Felix I think that with MX Snapshoot this problem cab be fixed because after snapshot one needs reinstalling through installer process.Using qt4-fsarchiver is the fastest way to move the Linux from one hdd to another one (another way is by dd command). From Windows OS, I will prefer Drive Snapshoot. On both ways, idea is simple. You make a image of the partition. Everything is identical. Also UUID. Small corrections needs to be done in fstab or nothing.

If some one do not prefer to change nothing in fstab to change lets say UUID of Swap partition... the follow command change UUID as needed
sudo tune2fs /dev/sdaX -U
example :
/dev/sda6 -U 7bcfbefa-12efb-1536-1700-f33b93f0151a
where sd6 is swap
IIRC, you can specify the resolution grub displays in the /etc/default/grub file.
Yep. Googling I found this link

Code: Select all

https://ubuntuforums.org/showthread.php?t=2284477
coljohnhannibalsmith; Hi ! If you like the GUI resolution.perhaps set in "/etc/default/grub" to match ?
Code:
xdpyinfo | grep dimensions
and edit " /etc/default/grub" line : " #GRUB_GFXMODE=640x480 " to match ( removing the starting comment character) .
And then of course propagate the change:
Code:
sudo update-grub
my screen
penguin@penguin-pc:~$ xdpyinfo | grep dimensions
dimensions: 1280x800 pixels (338x211 millimeters)
I will try to solve.

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 2068
Joined: Wed Apr 11, 2018 5:09 pm

Re: Boot Screen/Log Screen - adequate font for my 12.1" screen

#5 Post by fehlix » Fri Nov 09, 2018 8:03 pm

penguin wrote:
Fri Nov 09, 2018 4:31 pm
my screen
penguin@penguin-pc:~$ xdpyinfo | grep dimensions
dimensions: 1280x800 pixels (338x211 millimeters)
Please note this comment within /etc/default/grub:

Code: Select all

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 16624
Joined: Fri Dec 15, 2006 8:07 pm

Re: Boot Screen/Log Screen - adequate font for my 12.1" screen

#6 Post by Stevo » Fri Nov 09, 2018 8:24 pm

You can try and specify a higher resolution for GRUB in grub-customizer, too, which will make the font smaller. The font size in the login screen can be adjusted in LightDM GTK+ Greeter Settings, found in the Settings submenu.

User avatar
handy
Forum Regular
Forum Regular
Posts: 128
Joined: Mon Apr 23, 2018 2:00 pm

Re: Boot Screen/Log Screen - adequate font for my 12.1" screen

#7 Post by handy » Fri Nov 09, 2018 9:32 pm

This may provide some help:

viewtopic.php?f=23&t=46001
Clevo N'book (2014): P150SM-A
CPU: i7-4810MQ (Haswell) Speed: 2800/3800 MHz
RAM: 16 GiB 1600 MHz DDR3
GPU-1: i915
GPU-2: NVIDIA GK104M [GeForce GTX 880M] vRAM: 8GB 2500 Mhz DDR5
Storage: TOSHIBA 931.51 GiB. HGST 931.51 GiB. Crucial 223.57 GiB (M.2 SSD)

User avatar
Buck Fankers
Forum Regular
Forum Regular
Posts: 150
Joined: Sat Mar 10, 2018 9:06 pm

Re: Boot Screen/Log Screen - adequate font for my 12.1" screen

#8 Post by Buck Fankers » Sat Nov 10, 2018 3:29 am

penguin wrote:
Fri Nov 09, 2018 2:42 am
P.S.
Just only one Warning is shown during the boot screen, but A Im not able to see it becuase it goes fast .
Will be worthy to have its utility that reads kernel/logs ( some one needs to go and hunt for this log kernel/log screens in various logs dwelled in /var/log.
The way how the read kernel messages displays in terminal with dmesg -k is not so comfortable.Anyway I think that a yad programmed utility can simplify the job.
I have one small python script, that shows in the terminal dmesg lines that include phrases: 'error', 'fail', 'warning' in the line
Script also checks both Xorg logs for lines that include 'errors' and 'failed'

I was going to add few more things, but as being beginner in Linux (and Python) I don't know what other logs to look at and what keywords to search for.

If someone would like to look at it, changed it as needed and include it with MX, send me email in PM so i can send you the script. It is actually really really small short simple thing, but I find it useful seeing all error msgs concentrated on the screen. It really could be beneficial for beginners.

@penguin if you would like to use it, let me know where to send it to. Usage is as simple as running one command in the terminal: python3 mxlogs.py

User avatar
penguin
Forum Regular
Forum Regular
Posts: 276
Joined: Wed Jan 04, 2017 3:15 pm

Re: Boot Screen/Log Screen - adequate font for my 12.1" screen

#9 Post by penguin » Sat Nov 10, 2018 7:17 am

Buck Fankers wrote:
Sat Nov 10, 2018 3:29 am
penguin wrote:
Fri Nov 09, 2018 2:42 am
P.S.
Just only one Warning is shown during the boot screen, but A Im not able to see it becuase it goes fast .
Will be worthy to have its utility that reads kernel/logs ( some one needs to go and hunt for this log kernel/log screens in various logs dwelled in /var/log.
The way how the read kernel messages displays in terminal with dmesg -k is not so comfortable.Anyway I think that a yad programmed utility can simplify the job.
I have one small python script, that shows in the terminal dmesg lines that include phrases: 'error', 'fail', 'warning' in the line
Script also checks both Xorg logs for lines that include 'errors' and 'failed'

I was going to add few more things, but as being beginner in Linux (and Python) I don't know what other logs to look at and what keywords to search for.

If someone would like to look at it, changed it as needed and include it with MX, send me email in PM so i can send you the script. It is actually really really small short simple thing, but I find it useful seeing all error msgs concentrated on the screen. It really could be beneficial for beginners.

@penguin if you would like to use it, let me know where to send it to. Usage is as simple as running one command in the terminal: python3 mxlogs.py
Your script, maybe will be worthy for others too. Just copy and paste here :) .

User avatar
Buck Fankers
Forum Regular
Forum Regular
Posts: 150
Joined: Sat Mar 10, 2018 9:06 pm

Re: Boot Screen/Log Screen - adequate font for my 12.1" screen

#10 Post by Buck Fankers » Sat Nov 10, 2018 2:03 pm

penguin wrote:
Sat Nov 10, 2018 7:17 am
Just copy and paste here :) .
Somehow this never crossed my mind ;-)

For everyone, save script bellow as mxlogs.py (or whatever name you want but keep .py)
Wherever you saved it, say into downloads, open there terminal and type: python3 mxlogs.py

Right now script shows only logs from dmesg and both xorg logs, but you can 'switch' on some extra info to be shown also if you wish, just open mxlogs.py with any text editor and un-comment lines at the bottom to show extra info, that you probably don't need since most of it is already in your Conky anyway. Bottom of file looks like this and if you un-comment say mem() then you will see free and usage of memory and swap. These are just simple CLI commands but for some beginner it may be useful info. Especially for troubleshooting? Instead telling them what pieces of code to run in terminal you could tell them to just run mxlogs (with everything enabled) and copy/paste output into forum when they have some problems.
dmesg_error()
dmesg_fail()
dmesg_warning()
dmesg_disabled()
#boot_warning()
read_xorg0()
read_xorg0old()
#hwinfo_gfxcard()
#mem()
#lsblk()
#df()
#inxi()
Code to save as mxlogs.py: (edit, thanks to @baldyeti this time properly formatted)

Code: Select all

#!/usr/bin/env python

import os


def inxi():
    """ Return some basic information about computer hardware, OS, software... """
    print()
    print('===============')
    print('| Inxi -Fxxxz |   Computer information')
    print('===============')
    try:
        os.system('inxi -Fxxxz')
        print()
    except:
        print('Do you have installed: "inxi" on your system? ')


def dmesg_error():
    print('======================')
    print('| dmesg | grep error |   Shows kernel errors')
    print('======================')
    try:
        os.system('dmesg | grep error')
        print()
    except:
        print('dmesg | grep error is not working...')


def dmesg_fail():
    print('=====================')
    print('| dmesg | grep fail |   Shows kernel fails')
    print('=====================')
    try:
        os.system('dmesg | grep fail')
        print()
    except:
        print('dmesg | grep fail is not working...')


def dmesg_warning():
    print('========================')
    print('| dmesg | grep warning |   Shows kernel warnings')
    print('========================')
    try:
        os.system('dmesg | grep Warning')
        print()
    except:
        print('dmesg | grep warning is not working...')


def dmesg_disabled():
    print('======================')
    print('| dmesg | grep disabled |   Shows kernel disabled')
    print('======================')
    try:
        os.system('dmesg | grep disabled')
        print()
    except:
        print('dmesg | grep disabled is not working...')


def boot_warning():
    """ from boot file print lines that contain words: warning """
    try:
        with open('/var/log/boot', 'r') as f:
            print('===================')
            print('| boot | warnings |  "boot", Lists entries with "warning" keywords')
            print('===================')
            for line in f:
                if 'failed' in line or 'error' in line or 'warning' in line:
                    print(line, end='')
        print()
    except:
        print('Missing file: /var/log/boot')


def hwinfo_gfxcard():
    """ Info about installed graphic card """
    print('====================')
    print("| hwinfo --gfxcard |   Info about your graphic card.")
    print('====================')
    try:
        os.system('hwinfo --gfxcard')
        print()
        print()
    except:
        print('Do you have installed: "hwinfo" on your system? ')


def mem():
    """Info about memory and swap partition"""
    print('=============')
    print("|  free -h  |   Shows memory and swap info")
    print('=============')
    os.system('free -h')
    print()


def lsblk():
    """ Info about drives and partitions """
    print('=============')
    print("|   lsblk   |   List drives and partitions")
    print('=============')
    os.system('lsblk')
    print()


def df():
    """ Info about remaining free space on partitions """
    print('==========')
    print("|   df   |   How much free disk space is left for each partition?")
    print('==========')
    os.system('df')
    print()


def read_xorg0():
    """ from Xorg.0.log print lines that contain words: failed, error, (WW) """
    try:
        with open('/var/log/Xorg.0.log', 'r') as f:
            print('==============')
            print('| Xorg.0.log |  "Xorg.0.log", Lists entries with failed, error & (WW) keywords')
            print('==============')
            for line in f:
                if 'failed' in line or 'error' in line or '(WW)' in line:
                    print(line, end='')
        print()
    except:
        print('Missing file: Xorg.0.log')


def read_xorg0old():
    """ from Xorg.0.log.old print lines that contain words: failed, error, (WW) """
    try:
        with open('/var/log/Xorg.0.log.old', 'r') as f:
            print('==================')
            print('| Xorg.0.log.old |  "Xorg.0.log.old", Lists entries with failed, error & (WW) keywords')
            print('==================')
            for line in f:
                if 'failed' in line or 'error' in line or '(WW)' in line:
                    print(line, end='')
        print()
    except:
        print('Missing file: Xorg.1.log')


dmesg_error()
dmesg_fail()
dmesg_warning()
dmesg_disabled()
#boot_warning()
read_xorg0()
read_xorg0old()
#hwinfo_gfxcard()
#mem()
#lsblk()
#df()
#inxi()
print('... finished :-)')
Last edited by Buck Fankers on Sat Nov 10, 2018 2:29 pm, edited 1 time in total.

Post Reply

Return to “Hardware /Configuration”