Türkiye
Az konuş, çok çalış..

Forum

Bildirimler
Tümünü temizle

Archman i3-WM 2020-06 Kararlı Sürüm hazır  

Sayfa 2 / 2
  RSS
PliSsK
(@plissk)
Meraklı Kullanıcı

I forgot to remove the db.lck with sudo!

CevapAlıntı
Gönderildi : 31/10/2020 5:19 pm
PliSsK
(@plissk)
Meraklı Kullanıcı

Got it all working, many thanks! The final command sudo pacman-key --refresh-keys got an error 'A specified local key could not be updated from a keyserver', but running a system update worked ok.

CevapAlıntı
Gönderildi : 31/10/2020 6:08 pm
alicavus
(@alicavus)
Üye Moderator

@plissk , I have forgot to put sudo before each command

sudo pacman -Syy
sudo pacman -S archlinux-keyring
sudo rm -R /etc/pacman.d/gnupg/
sudo rm -R /root/.gnupg/ 
sudo gpg --refresh-keys
sudo pacman-key --init
sudo pacman-key --populate archlinux
sudo pacman-key --refresh-keys 

Also take a look of the post of @tulliana :

Gönderen: @tulliana

Archman Linux, Facilitated Terminal commands:

sudo pacman -S ==> pac
sudo pacman -Ss ==> pacs
sudo pacman -Syy ==>
pacu
sudo pacman -Syyu ==> update
sudo rm /var/lib/pacman/db.lck ==> unlock
sudo reflector --verbose --latest 15 --sort rate --save /etc/pacman.d/mirrorlist ==> mirrors
sudo reflector --verbose --latest 15 --sort rate --save /etc/pacman.d/mirrorlist && sudo pacman -Syyu ==> upgrade
sudo pacman -Scc ==> clean
sudo pacman -R ==> remove
sudo pacman -Qi ==> info
yay -S packagename ==> aur packagename
yay -S packagename --noconfirm ==> aurno packagename

So in case of database lock we can use:

unlock
CevapAlıntı
Gönderildi : 31/10/2020 6:10 pm
PliSsK
(@plissk)
Meraklı Kullanıcı

@alicavus Thanks very much for your help! I should have figured out the sudo myself earlier, you can't remove any system files without using it. Cheers.

CevapAlıntı
Gönderildi : 01/11/2020 6:27 pm
PliSsK
(@plissk)
Meraklı Kullanıcı
Gönderen: @alicavus

@plissk

Permanently adding undetected resolutions

Once a suitable resolution is found using xrandr, the mode can be permanently added by creating an entry in /etc/X11/xorg.conf.d/:

/etc/X11/xorg.conf.d/10-monitor.conf

Section "Monitor"
    Identifier "VGA1"
    Modeline "1280x1024_60.00"  109.00  1280 1368 1496 1712  1024 1027 1034 1063 -hsync +vsync
    Option "PreferredMode" "1280x1024_60.00"
EndSection

Section "Screen"
    Identifier "Screen0"
    Monitor "VGA1"
    DefaultDepth 24
    SubSection "Display"
        Modes "1280x1024_60.00"
    EndSubSection
EndSection

Section "Device"
    Identifier "Device0"
    Driver "intel"
EndSection

Replace intel with the right driver, e.g. nvidia. When the X server is restarted, you should be able to set the new resolution.

If this does not work for you, try removing the Screen and Device sections and just leaving the Monitor section. [3]

Sorry to be a pain, but I reinstalled Archman on my computer and wasn't able to get to permanently change the screen resolution using the 10-monitor.config file method above. The screen resolution on rebooting was improved but it was part way between the low res it starts with and the high res of my display. I tried it with all 3 sections and just the monitor section. Cheers.

CevapAlıntı
Gönderildi : 04/11/2020 9:08 pm
alicavus
(@alicavus)
Üye Moderator

@plissk

When in GRUB menu hit the key c and enter in command mode. Enter the word videoinfo (if your loader is older try vbeinfo)
The GRUB will print all available screen modes. If the output of command is too large enter the command pager=1 and try again. Note somewhere optimal one (i.e. 1900x1080x32)
Press Escape key and return to normal boot menu. Start Archman OS.
Open /etc/default/grub with your favorite text editor as root/elevated access. Navigate to:

# 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=auto

# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep

If one of lines starting with GRUB_GFXMODE or GRUB_GFXPAYLOAD_LINUX is commented (starting with #) uncomment it (remove #).
Change GRUB_GFXMODE=auto with optimal mode for GRUB (which we are noted before) i.e.

GRUB_GFXMODE="1900x1080x32" 

 Save and exit the editor.

Open terminal and execute:

sudo grub-mkonfig -o /boot/grub/grub.cfg

Reboot the system. If there is a problem check any log file .xsession-error*, see dmesg -k and systemd journal for errors. Try with solutions previosly addressed here.

CevapAlıntı
Gönderildi : 05/11/2020 7:56 pm
PliSsK
(@plissk)
Meraklı Kullanıcı
Gönderen: @alicavus

@plissk

When in GRUB menu hit the key c and enter in command mode. Enter the word videoinfo (if your loader is older try vbeinfo)
The GRUB will print all available screen modes. If the output of command is too large enter the command pager=1 and try again.

Note somewhere optimal one (i.e. 1900x1080x32)
Press Escape key and return to normal boot menu. Start Archman OS.
Open /etc/default/grub with your favorite text editor as root/elevated access. Navigate to:

# 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=auto

# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep

If one of lines starting with GRUB_GFXMODE or GRUB_GFXPAYLOAD_LINUX is commented (starting with #) uncomment it (remove #).
Change GRUB_GFXMODE=auto with optimal mode for GRUB (which we are noted before) i.e.

GRUB_GFXMODE="1900x1080x32" 

 Save and exit the editor.

Open terminal and execute:

sudo grub-mkonfig -o /boot/grub/grub.cfg

Reboot the system. If there is a problem check any log file .xsession-error*, see dmesg -k and systemd journal for errors. Try with solutions previosly addressed here.

Thanks for input. All I got with videoinfo in grub command line was one line of text about colours, nothing more. No screen resolutions.

/etc/default/grub was pretty empty, none of those lines were present, so I added both of them, and ran grub-mkconfig, and it didn't do anything unfortunately.

CevapAlıntı
Gönderildi : 08/11/2020 4:12 am
alicavus
(@alicavus)
Üye Moderator

@plissk

Gönderen: @plissk

Thanks for input. All I got with videoinfo in grub command line was one line of text about colours, nothing more. No screen resolutions.

/etc/default/grub was pretty empty, none of those lines were present, so I added both of them, and ran grub-mkconfig, and it didn't do anything unfortunately.

This is not OK. It seems Calamares is crashed during installation proccess.

/usr/share/calamares/modules/grubcfg.conf

# Write lines to /etc/default/grub (in the target system) based
# on calculated values and the values set in the *defaults* key
# in this configuration file.
#
# Calculated values are:
#   - GRUB_DISTRIBUTOR,   branding module, *bootloaderEntryName*
#   - GRUB_ENABLE_CRYPTODISK, based on the presence of filesystems
#     that use LUKS
#   - GRUB_CMDLINE_LINUX_DEFAULT, adding LUKS setup and plymouth
#     support to the kernel.

---
# If set to true, always creates /etc/default/grub from scratch even if the file
# already existed. If set to false, edits the existing file instead.
overwrite: true

# Default entries to write to /etc/default/grub if it does not exist yet or if
# we are overwriting it.
#
defaults:
    GRUB_TIMEOUT: 5
    GRUB_DEFAULT: "saved"
    GRUB_DISABLE_SUBMENU: true
    GRUB_TERMINAL_OUTPUT: "console"
    GRUB_DISABLE_RECOVERY: true
    GRUB_CMDLINE_LINUX_DEFAULT: "quiet scsi_mod.use_blk_mq=1"

Result of this should be:

/etc/default/grub

GRUB_TIMEOUT=5
GRUB_DEFAULT="saved"
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_DISABLE_RECOVERY=true
GRUB_CMDLINE_LINUX_DEFAULT="quiet scsi_mod.use_blk_mq=1"

We should inspect calamares logs to tell what was going wrong.

CevapAlıntı
Gönderildi : 09/11/2020 5:30 pm
tulliana
(@tulliana)
Üye Admin
Gönderen: @plissk

@alicavus thanks very much for your help. I created the config file for the display and it worked fine. I am unable to correct the signature error though. Any sudo pacman command results in an error to unlock the database. This wasn't happening before, I was able to install packages individually. I was unclear whether the first command was sudo pacman -Syy or -Reason (edited?) but neither worked. Trying to install archlinux-keyring resulted in a similar error.  I was suggested to remove /var/lib/pacman/db.lck but that wasn't possible either as it was write protected, permission denied. Similarly, trying to remove gnupg failed as permission denied. Any ideas please? It would be greatly appreciated. Worst case I can reinstall as sudo pacman was working before, evidently something has happened! Cheers.

You can unlock it with sudo /var/lib/pacman/db.lck or just the unlock command

 

http://archman.org - Bizi bilen iyi bilir, bilmeyen de kendi gibi bilir.!

CevapAlıntı
Gönderildi : 20/11/2020 4:09 pm
Sayfa 2 / 2
Paylaş:
Translate »