Activity for Silent Robot
-
Silent Robot posted a comment on discussion General Discussion
i'm still working through the configuration files to see where, if it is my end, and Calamares configuration to see if a regression has crept in. I will notify as soon as i have a solution.
-
This is what i've found for your scenario: https://wiki.archlinux.org/title/Direct_modem_connection#DSL_(PPPoE)
-
Ah yes, well, i'm pleased you've resolved the issue.
-
i'm currently looking into this issue. I also noticed this happening this morning after i tested a fresh build...
-
The URL is correct for the repo. I am building from it now, packages are being pulled. Although it appears you have an older build(?) since i have not signed the packages for a while, for technical reasons. Try clearing your pacman cache: pacman -Scc then do pacman -Syy then pacman -Syu
-
Thanks i'll check, i did i update it yesterday
-
Looking at the Arch Wiki there are a few suggestions. I'll link you directly to the page that will hopefully help. If you installed the drivers from within Calamares, you could try reinstalling them in this order: pacman -S nvidia nvidia-utils Then reload the driver: modprobe nvidia Here's the page in question: https://wiki.archlinux.org/title/NVIDIA/Troubleshooting#Blackscreen_at_X_startup_/_Machine_poweroff_at_X_shutdown
-
Yes sorry, this is due to a change in the package. If you manually remove those files first then run the update again it should be fine!
-
base drivers mesa lib32-mesa xf86-video-amdgpu vulkan support vulkan-radeon or amdvlk 32-bit support lib32-vulkan-radeon or lib32-amdvlk accelerated video decoding libva-mesa-driver lib32-libva-mesa-driver mesa-vdpau lib32-mesa-vdpau experimental mesa-git lib32-mesa-git xf86-video-amdgpu-git Archwiki states: It may be necessary to symlink LibLLVM for X to start. For example, ln -s /usr/lib/libLLVM-10git.so /usr/lib/libLLVM-10svn.so
-
The easiest way would to be load the ISO in live mode. Open Panel Profiles and export the default. Save it to a USB key or Shared Folder on your host and then import it via Panel Profiles on your main machine.
-
If you are talking about the information output when you open the terminal, in your file manager press ctrl+h to show hidden files. Then, open .bashrc in your home folder root and uncomment (remove the #) from the neofetch line at the end of the file.
-
In the file manager do CTRL + H to show hidden files. You'll see a .bash directory. Within that folder are a few prompt styles which you can source from the .bashrc file. Look at your .bashrc and see where the prompt is sourced from and change it to one of the others. You'll need to close and reopen Terminal to see the change!
-
The repo is live and active. Try: sudo pacman -Syy first. Also check that the salient-os repository is in your pacman.conf file.
-
Hi, not sure what is going on there the repo is live and active
-
Hi, sorry for the late reply. I too have noticed this and am looking into why this is. I'll get back to you shortly!
-
Spanish Language system not work, only English
-
You are very welcome. I am happy it is working for you now! Thank you!
-
Do you know which audio chipset the X1 Carbon uses? That would help me narrow down a solution if it is a firmware / driver issue. Although, you may want to check in pavucontrol (audio icon in system tray), open it and make sure it is actually sourcing your audio device properly. Click the sound icon and choose Audio Mixer. Go to the Configuration tab and make sure your device is listed there. Alternately you can open a terminal and paste the following to get a list of audio devices: pactl list sinks...
-
Hi, Out of interest, which ISO did you use, XFCE or Plasma? Either way, i think i have resolved this issue now. I noticed some configurations that were conflicting with changing the locale / language settings. This 'should' be resolved now on both ISO's. I will update both ISO's and publish under a 2021-03 (March) folder in a couple of days due to the reason outlined below: (March 4th is projected release) as we are also waiting for KMPCore to be updated due to an EFI installation regression, as...
-
If you choose your language in Calamares (The installer), then it should take effect on the installed system. I have just tested by choosing Español for language and Spanish for Keyboard. It works fine for me.
-
Problems with Grub, Time and Virtualbox
-
New ISO is available now. Also remember that at around 88% Calamares is generating the initramfs for your system, this does take a little while as it is compiling it live!
-
Did you make sure to create a GPT partition table and not use an MBR partition table? "Installing for x86_64-efi platform. grub-install: error: /boot/efi doesn't look like an EFI partition." You would have to use Manual Partitioning first to create a new GPT partition table, add a 300MB or 512MB (size is your choice) FAT32 partition for /boot/efi. Then add other partitions for root/home (either one large or split partitions of your choice).
-
Lutris is a mixed bag of results. For which ever game you are trying to get working will requires some research into the best Lutris settings to get it working as expected.
-
try instead using pacman -Sy and then pacman -Syu as there have been changes to reflector since this build. I am however, working on the new builds and will update them soon.
-
I am working on the latest release at the moment using the new archsio methods. I will upload the ISO when it's ready! I will inform everyone on the discord when available!
-
in /etc/mkinitcpio.d/linux.preset needs changing either at build time or via Calamares (using the shellprocess module to replace the file) at install time from this: # # SPDX-License-Identifier: GPL-3.0-or-later # mkinitcpio preset file for the 'linux' package on archiso PRESETS=('archiso') ALL_kver='/boot/vmlinuz-linux' ALL_config='/etc/mkinitcpio.conf' archiso_image="/boot/archiso.img" to this: # # SPDX-License-Identifier: GPL-3.0-or-later # mkinitcpio preset file for the 'linux' package on archiso...
-
in /etc/mkinitcpio.d/linux.preset needs changing either at build time or via Calamares (using the shellprocess module to replace the file) at install time from this: # # SPDX-License-Identifier: GPL-3.0-or-later # mkinitcpio preset file for the 'linux' package on archiso PRESETS=('archiso') ALL_kver='/boot/vmlinuz-linux' ALL_config='/etc/mkinitcpio.conf' archiso_image="/boot/archiso.img" to this: # # SPDX-License-Identifier: GPL-3.0-or-later # mkinitcpio preset file for the 'linux' package on archiso...
-
in /etc/mkinitcpio.d/linux.preset needs changing either at build time or via Calamares (using the shellprocess module to replace the file) at install time from this: # # SPDX-License-Identifier: GPL-3.0-or-later # mkinitcpio preset file for the 'linux' package on archiso PRESETS=('archiso') ALL_kver='/boot/vmlinuz-linux' ALL_config='/etc/mkinitcpio.conf' archiso_image="/boot/archiso.img" to this: # # SPDX-License-Identifier: GPL-3.0-or-later # mkinitcpio preset file for the 'linux' package on archiso...
-
in /etc/mkinitcpio.d/linux.preset needs changing either at build time or via Calamares (using the shellprocess module to replace the file) at install time from this: # # SPDX-License-Identifier: GPL-3.0-or-later # mkinitcpio preset file for the 'linux' package on archiso PRESETS=('archiso') ALL_kver='/boot/vmlinuz-linux' ALL_config='/etc/mkinitcpio.conf' archiso_image="/boot/archiso.img" to this: # # SPDX-License-Identifier: GPL-3.0-or-later # mkinitcpio preset file for the 'linux' package on archiso...
-
in /etc/mkinitcpio.d/linux.preset needs changing either at build time or via Calamares (using the shellprocess module to replace the file) at install time from this: # # SPDX-License-Identifier: GPL-3.0-or-later # mkinitcpio preset file for the 'linux' package on archiso PRESETS=('archiso') ALL_kver='/boot/vmlinuz-linux' ALL_config='/etc/mkinitcpio.conf' archiso_image="/boot/archiso.img" to this: # mkinitcpio preset file for the 'linux' package on archiso PRESETS=('default' 'fallback') ALL_kver='/boot/vmlinuz-linux'...
-
in /etc/mkinitcpio.d/linux.preset needs changing either at build time or via Calamares (using the shellprocess module to replace the file) at install time from this: # # SPDX-License-Identifier: GPL-3.0-or-later # mkinitcpio preset file for the 'linux' package on archiso PRESETS=('archiso') ALL_kver='/boot/vmlinuz-linux' ALL_config='/etc/mkinitcpio.conf' archiso_image="/boot/archiso.img" to this: # mkinitcpio preset file for the 'linux' package on archiso PRESETS=('default' 'fallback') ALL_kver='/boot/vmlinuz-linux'...
-
in /etc/mkinitcpio.d/linux.preset needs changing either at build time or via Calamares (using the shellprocess module to replace the file) at install time from this: # # SPDX-License-Identifier: GPL-3.0-or-later # mkinitcpio preset file for the 'linux' package on archiso PRESETS=('archiso') ALL_kver='/boot/vmlinuz-linux' ALL_config='/etc/mkinitcpio.conf' archiso_image="/boot/archiso.img" to this: # mkinitcpio preset file for the 'linux' package on archiso PRESETS=('default' 'fallback') ALL_kver='/boot/vmlinuz-linux'...
-
in terminal you can do: pacupg There is no upgrade as such since Arch is a rolling distribution, it is always updated.
-
It does work in UEFI mode, but you may have to choose the first menu option. Both Arch and Salient for some reason default to the third option which will fail. (unresolved as yet). You may then get a blank screen for a while, this is normal as a checksum is being performed in the background.
-
It does work in UEFI mode, but you may have to choose the first menu option. Both Arch and Salient for some reason default to the third option which will fail. (unresolved as yet). You may then get a blank screne for a while, this is normal as a checksum is being performed in the background.
-
You need to perform these steps as outlined here: https://www.archlinux.org/news/nss3511-1-and-lib32-nss3511-1-updates-require-manual-intervention/
-
what are you using to write the image to USB? I would reccomend Rufus (in DD mode) or Etcher to perform these tasks. It looks like bad writes to me.
-
OK thanks, i'll look into what has changed.
-
ok try: sudo rm -f /etc/X11/xorg.conf and reboot. The display is getting confused somewhere. You might want to look into the beta drivers https://aur.archlinux.org/packages/nvidia-beta/ RTX i guess is not fully supported yet.
-
Please look at this package: https://aur.archlinux.org/packages/optimus-manager/ and possibly this one too: https://wiki.archlinux.org/index.php/Nvidia-xrun I can't offer much more on this since i do not use a dual graphics laptop,
-
Please look at this package: https://aur.archlinux.org/packages/optimus-manager/
-
I'm assuming you have nvidia graphics card? If you have installed and configured the nvidia drivers through nvidia-settings, then you can in terminal: sudo rm -f /etc/X11/xorg.conf Or check in /etc/X11/xorg.conf.d/20-nvidia.conf exists or not and remove that! If not then you can try: rm -f ~/.config/xfce4/xconf/xfce-perchannel-xml/displays.xml it could be that xfce and nvidia displays are in conflict.
-
You can try deleting the following file: /home/YOURUSER/.config/xfce4/xfconf/xfce-perchannel-xml/displays.xml Then reboot. It appears there might be a conflict between the display profile in the nvidia settings and what xfce sees.
-
To be fair to pamac, it is not intended to be a software store in the traditional sense you may understand them. It is primaily for showing what is installed, updates available and for installing software from either the connected repositories or by searching. Try clicking on the dotted virtical menu and refreshing the databases, then quit pamac. Then go to the System menu and choose Add Remove Software to reload it. It might be out of sync.
-
So what happens if you click on another item other than Featured on the left?
-
You mean pamac, from the system tray? The software updater / installer. If you do another: sudo reflect, then do: pacupd it will refresh the mirrors. Then open pamac and you should see packages listed.
-
This should help JD. Create a new file (as root): sudo touch /etc/modprobe.d/blacklist.conf then copy the contents here to that file: blacklist nouveau blacklist rivafb blacklist nvidiafb blacklist rivatv blacklist nv Then reboot, hopefully that helps. If you still get stuck at the boot menu press e to go into edit mode and look for the line that starts with linux. Right arrow all the way to the end and press space then enter nouveau.modeset=0 Then press F10 to coninue boot.
-
Thaks Daniel, appreciated!
-
That sounds doable. Maybe try it on a spare drive first to see if it works for you?
-
very nice :)
-
You can also install the following to get a nice GUI (depending if your device is supported), in terminal type: sudo pacman -S libratbag piper Piper is the GUI
-
I've seen this in some situations. A potential fix. Right click on the network icon in the system tray, choose edit connections, select your connection in the dialog that pops up and click the cog (or double click on the name), under the IPv6 Settings tab change the Method to Link-Local Only, then click Save.
-
Ok, let's try a manual install of the drivers. In terminal do the following: sudo pacman -S nvidia nvidia-settings nvidia-utils lib32-nvidia-utils then reboot. If you still get a blank screen use left alt + ctrl + f2 to get to a tty console. Then try sudo rm -f /etc/X11/xorg.conf.d/20-nvidia.conf and reboot again.
-
That's very strange, i'll have to try that myself on the new build and report back.
-
If you are booting in UEFI mode, you MUST have a GPT partition structure for your disk, which you can do in gparted, and a fat32 boot partition (512mb), otherwise Calamares can fail since it cannot determine the previous partition structure. However, if you are legacy booting, then you need a partition structure of msdos, which you also do in gparted by creating a new partition table (be warned, this WILL destroy all data on the drive!). My advice woul dbe to check first in gparted if you have a...
-
If you type ifconfig in the terminal it will give the names of your devices. I'm betting that enp6s0 is the name of your network adapter.
-
I don't have the ability to change desktop wallpaper SalientOS KDE
-
Impossible to update a fresh install
-
I have updated the ISOs now so you should not get the VirtualBox error any more.
-
Unfortunately, i don't have a remote repository atm, so yes, when a new ISO drops it is a fresh install, if you wish but, since arch is rolling it is not 100% required. Most changes are quite minor concerning optimisations or fixing minor niggles at this point.
-
Thank you Daniel, very much appreciated. Point 1 is useful, Point 2 shouldn't be an issue as i'm pretty sure $HOME/bin is in the path (i'll check). Point 3 is also useful. Thanks for taking the time to look and improve the settings.
-
press left alt + d + s, then mouse actions and change the right click menu back to standard menu.
-
Save as compton.conf and put it under your ~/.config folder shadow = true; no-dnd-shadow = false; no-dock-shadow = true; clear-shadow = true; shadow-radius = 3; shadow-offset-x = -3; shadow-offset-y = -3; shadow-opacity = 0.7; shadow-red = 0.066667; shadow-green = 0.070588; shadow-blue = 0.086275; shadow-exclude = [ "! name~=''", "class_g = 'Cairo-clock'", "class_g = 'Conky'", "class_g ?= 'Notify-osd'", "class_g = 'Conky'", "class_g = 'Kupfer'", "class_g = 'Synapse'", "class_g ?= 'Cairo-dock'", "class_g...
-
KDE - Installation failed at 92%
-
oops apologies for that, i 'll make a check in future for that! /boot is the default now since kmpcore changes. It is essentially the same thing now!
-
/boot is the default now since kmpcore changes. It is essentially the same thing now!
-
KDE - No networks during install
-
you need to perform these steps first as outlined on the Arch Main Page! pacman -Rdd libdmx libxxf86dga libxxf86misc && pacman -Syu
-
salientos-plasma 20.02 problems
-
Two options really, either left alt + d + s, mouse option and change the right click menu back to standard menu. Or, long left click on the desktop and the widget will appear at teh top of the screen, there you can change desktop wallpapers.
-
That image show that the libc++ is being recompiled and is performing unit tests. There must have been an update for it.
-
This sounds like a corrupt ISO download. Could you please re-download and try again?
-
Have you performed this step from the terminal? pacman -Rdd libdmx libxxf86dga libxxf86misc && pacman -Syu explained here: https://www.archlinux.org/news/xorg-cleanup-requires-manual-intervention/ Then after that, still in terminal issue the following: sudo reflect pacupd pacupg After this your system should update correctly. The next build won't have this issue which arose after the current build.
-
Before doing anything else, you'll need to perform this step from the terminal: pacman -Rdd libdmx libxxf86dga libxxf86misc && pacman -Syu explained here: https://www.archlinux.org/news/xorg-cleanup-requires-manual-intervention/ Then after that, still in terminal issue the following: sudo reflect pacupd pacupg After this your system should update correctly. The next build won't have this issue which arose after the current build.
-
Before doing anything else, you'll need to perform this step from the terminal: pacman -Rdd libdmx libxxf86dga libxxf86misc && pacman -Syu explained here: https://www.archlinux.org/news/xorg-cleanup-requires-manual-intervention/ Then after that, still in terminalk issue the following: sudo reflect pacupd pacupg After this your system should update correctly. The next build won't have this issue which arose after the current build.
-
Sometimes Calamares cannot erase partitions correctly depending on the previous partition structure, If this happens (it is a known issue), use GParted instead and then run the installer again and choose keep in the options rather than erase.
-
Sometimes Calamares cannot erase partitions correctly depending on the previous partition structure, If this happens (it is a known issue), use GParted instead.
-
You need to perform these steps first: https://www.archlinux.org/news/xorg-cleanup-requires-manual-intervention/ pacman -Rdd libdmx libxxf86dga libxxf86misc && pacman -Syu That will resolve xorgproto issue.
-
Does the installer let you continue or does it stop you from installing? The message is concerning available RAM or Storage. I'll have to look into this on the next build and adjust those settings. Thank for letting me know.
-
This is an interesting situation. When you installed the nvidia drivers did you install just nvidia or the nvidia-390 drivers as i think your 660 works only with those? However, your 1070 should be fine with the newer nvidia drivers. In your BIOS do have have integrated graphics turned OFF? If you choose the first option at the USB Boot screen (ie no drivers) does it boot then? Question: did you use the included script to update the driver database and install the nvidia drivers as shown: Perform...
-
Try changing the system font and log off and back in again.
-
Try again without DD mode. Or use another tool like Etcher.
-
Package conflikt checking endless loop
-
Oh! Well if you use the commands I show above the system will update. It is possible to pamac to install packages after you have updated the mirror lists. So if you go back to previous post and follow those instructions you should find pamac working fine after a reboot.
-
Once you are logged in to the system you can use the network manager applet to disable wireless altogether. I do this as I am also on a wired connection.
-
Which package(s) are conflicting? Although you 'can' you pamac to update it is normally better to use the terminal commands I provide to do that. In sequence after a fresh install i recommend doing the following in terminal: To update to the fastest mirrors sudo reflect or sudo reflectuk (if you are in the UK) To update mirror list pacupd To perform update/upgrades pacupg This way you can see if there are any conflicts arising or if any manual intervetion is required (which there is BTW for this:...
-
It's a bit of a puzzle then since Cairo Dock shares NO dependencies with XFCE directly. I'm not sure what you mean by Option 11 of XFCE, please elaborate? If you look under the Graphics menu you will notice applications there that are creative in nature. Both Steam and Lutris are installed out of the box. Sign in to either and install your games. I don't see the issue here. I can only offer advice where Salient is concerned. If you are trying a multi-boot scenario then I would suggest thoroughly...
-
Then i would recommend reinstalling. Whatever you have done has had a major negative impact on the installation and without knowing 'exactly' the steps that were taken to put Salient into the state it is in now would prove very difficult. If you have a seperate HOME partition you can keep that partition from within Calamares.
-
Did you resolve your issue?
-
As long as you can boot into the system (ctrl+alt+f2) you can issue the following to reinstall xfce. From your terminal/console: pacman -S xfce4 That should reinstall the base xfce system for you. I'm assuming you haven't touched anything else and that the removal of Cairo Dock is the responsible party here, although it doens't depend on xfce so having that removed is very strange.
-
Those appear to optional dependencies, not implicit ones. Easy to resolve though: pacman -S cdrdao cdrtools dvd+rw-tools That should be enough looking at the Arch Wiki. if not reference this to see the dependencies: https://www.archlinux.org/packages/extra/x86_64/k3b/
-
Salient did used to auto size partitions but after feedback from the community I decided to remove that element from Calamares since everyone has different use case requirements and forcing a partition scheme probably isn't the best way. It is now down to the end user to decide which partition layout they would prefer. If you are going to install more than one OS on the drive then be mindful of which OS you would like to have priority over the others in terms of boot. It's easy to remedy with Salient...
-
By default, if you are setting up an EFI partition, Calamares will create a 300Mb boot partition. It may be better for you to create these partitions first with Gparted before installing. Your disk will have to have the GPT partition structure for this to work correctly. I use three partitons, 300Mb EFI /boot, 200Gb /root and the rest is left for /home. I do this first in Gparted and then in Calamares I use the 'Keep' option so that Calamares does not re-format the partitions.
-
Hi Paul, Sorry to hear of the troubles Windows gave you. I have heard many horror stories of what Windows is able to do after / during a large update. I sympathise but, am not suprised anymore to be honest :) Now, concerning updates, whilst it is true that at certain times an update can potentially cause breakages, these days it is quite rare. Since Salient only uses a few hand-curated foreign packages built from github (technically speaking, considered AUR), personally I have not had any issues...
-
Go to Settings, Power Manager, System and ensure the System Sleep Mode is set to Suspend, then move the slider all the way to the left so the text underneath says 'never'. Then go to the Display tab and move both sliders all the way to the left so for each again, the text says 'never'. Finally go to the Security tab and Set Automatically lock the session to never. Also make sure Lock the screen when system is going to sleep is unchecked. Now go to Settings, Screensaver and toggle enable screensaver...
-
Hi, first of all, thank you for your kind words. Secondly, is your system using Optimus?
-
Would you please try removing /home/youruser/.config/xfce4/xfconf/xfce-perchannel-xml/displays.xml and reboot?
-
This is something that has happended before which ironically was the result of a corrupt iso download. Would you please try re-downloading the iso and verify the md5 sum and try again?
-
Both nvidia and non-nvidia versions of salient os won't successfully boot from USB media on my Dell Inspiron 15 7577 Gaming laptop
1 >