Activity for Silent Robot
-
Silent Robot modified a comment on ticket #10
Did you try nomodeset edd=off ???
-
Did you try nomodeset edd=off ???
-
Hi, if you go into ~/.config/xfce4/xfconf/ you should see a configuration file for displays, delete it and reboot. That should reset the display options.
-
You just download the archive from the website and extract it to its own folder, then double click the installer. Also you're attempting to use apt in an arch based system, where pacman is the package manager.
-
You just download the archive from the website and extract it to its own folder, then double click the installer.
-
https://www.blackmagicdesign.com/products/davinciresolve/ Fill out the short form and download the installer. If you have nvidia supported graphics then you need to install cuda first. pacman -S cuda Once both are installed. Reboot.
-
Uninstall dolphin-root first. From terminal: yay -Rs dolphin-root (it'll probably tell you that kde-servicemenus-rootactions needs go too, let it, you can add that back in afterwards). Once Dolphin is uninstalled from terminal: yay -Syu System should now update ok. Reboot after update/upgrade. Now you can add Dolphin back. yay -S dolphin-root yay -S kde-servicemenus-rootactions Reboot again. Should be good.
-
I am, there is a plasma testing build but, i am working on the next iteration very soon.
-
Ok try creating a new VM with at least 28GB HD. It could be running out of space.
-
Steam
-
That's good, i had a feeling it might have been a bad install since that is an unlikely sceanrio given you had net access.
-
What is your hardware please, WiFi / Ethernet controllers? You can get that from terminal: lspci
-
What is your hardware please, WiFi / Ethernet controllers?
-
After a little digging i found this: https://wiki.archlinux.org/index.php/NVIDIA/Tips_and_tricks#Enabling_SLI Which seems to be related. If you follow this guide you may find your solution, I cannot test this since I don't have an SLI configuration. So, what you can do is install as per our previous post but, after reboot, boot back in to the Live Media, which will give you access to your installed drive and you should be able to follow the steps required. Also, this could help, before trying the...
-
After a little digging i found this: https://wiki.archlinux.org/index.php/NVIDIA/Tips_and_tricks#Enabling_SLI Which seems to be related. If you follow this guide you may find your solution, I cannot test this since I don't have an SLI configuration. So, what you can do is install as per our previous post but, after reboot, boot back in to the Live Media, which will give you access to your installed drive and you should be able to follow the steps required.
-
If the non-nvidia version is installing for you, you can install the nvidia drivers manually from the terminal. Update your mirrors sudo reflect Update the mirrorlist sudo pacupd Update the system (answer yes when required to import the key) sudo pacupg Once that is done, reboot. Open System Settings and Session & Startup, in there you will see an entry for nvidia-start. This is a script in the ~/Scripts folder under your Home folder. Select that item and choose the Edit button and re-link it to...
-
If the non-nvidia version is installing for you, you can install the nvidia drivers manually from the terminal. Update your mirrors sudo reflect Update the mirrorlist sudo pacupd Update the system (answer yes when required to import the key) sudo pacupg Once that is done, reboot. Open System Settings and Session & Startup, in there you will see an entry for nvidia-start. This is a script in the ~/Scripts folder under your Home folder. Select that item and choose the Edit button and re-link it to...
-
If the non-nvidia version is installing for you, you can install the nvidia drivers manually from the terminal. Update your mirrors sudo reflect Update the mirrorlist sudo pacupd Update the system (answer yes when required to import the key) sudo pacupg Once that is done, reboot. Then, from terminal enter the following to install the nvidia drivers but, DON'T reboot yet! Open System Settings and Session & Startup, in there you will see an entry for nvidia-start. This is a script in the ~/Scripts...
-
If the non-nvidia version is installing for you, you can install the nvidia drivers manually from the terminal. Update your mirrors sudo reflect Update the mirrorlist sudo pacupd Update the system (answer yes when required to import the key) sudo pacupg Once that is done, reboot. Then, from terminal enter the following to install the nvidia drivers but, DON'T reboot yet! Open System Settings and Session & Startup, in there you will see an entry for nvidia-start. This is a script in the ~/Scripts...
-
Both ISOs are now updated and ready for download. I appologise that this is an issue for you but, i'm also curious to find why Salient is having issues with your particular hardware.
-
Thanks, i noticed that myself too. I've fixed this issue and will be refreshing both ISOs today
-
Thanks, i noticed that myself too. I think some regressions have crept in, i'm going to wait for the next Linux Kernel update and rebuild.
-
Is that where it always stops, starting the Samba Daemon?
-
These flags are set duriung the partition creation. Please ensure you are not setting them post install with the exception of the boot flag after install but still within the Live Media.
-
Yep, i've fixed this and will be refreshing the ISOs shortly.
-
You have to open gparted after the install when using the boot partition method and set the boot flag for a successful boot at the moment until the regression has been addressed by the Calamares team. That is, whilst still in the Live Media BEFORE rebooting.
-
You have to open gparted after the install when using the boot partition method and set the boot flag for a successful boot at the moment until the regression has been addressed by the Calamares team.
-
Ok, try formatting using gparted from the live media instead.
-
Ok that's progress. One thing though you don't need to update while in the live media, the installer will upgrade your target system during install. What error did you get when setting the boot flag? You shouldn't get any for that task...
-
I have a working prototype of openbox in the works.
-
I'm sorry i am not familiar with that application
-
Thank you :)
-
I've refreshed both ISOs today so you may want to try the new builds?
-
Take a look in /usr/share/lightdm-webkit/themes/sequoia/img/. Any modifications you'll have to do with elevated privileges. So, right click in that folder, open folder as root.
-
Could you try this version please? https://drive.google.com/open?id=1dWGeOyfMNYwA6gbpe-gDtBRQPifxW6QN
-
Possible but still strange as i have this installed on SSD no problems. I'm using also an 1080TI and for me if i get the blank screen after boot, i do ctrl+alt+f2 then ctrl+alt+f7 and it restores the screen for me. Well, i'm not going to stop supporting your issue until you have a successful working install :)
-
try typing startx at this prompt, what is the output?
-
Well, that is a successful boot, after this short period it should take you to desktop? It does take a few moments on very first boot after install.
-
Incidentally, since you're using an NVME device, do you have secure boot turned off in your BIOS? Also, are you booting in Legacy or UEFI mode? If UEFI you need to reformat your device with a GPT partition structure and set your boot partition as FAT32 (512mb), The root and home partitions can be as normal (ext4).
-
Hi, ok thanks. I take you're flashing the ISO from Windows since you mentioned rufus? Could you try re-flashing the ISO, this time using Etcher? Anyway, i'm rebuilding the ISO's after reviewing some of the configurations and making minor changes. I will upload the new ISO's within a day or so.
-
I'm looking into this issue and believe it is due to SLI configuration. Would you mind testing by removing one card temporarily and see if you get the same result? I understand if this is inconvenient but, i believe it will help eliminate running in SLI as the cause.
-
Ok, i'll need to look into this a bit further. For most other those key combinations return the desktop screen from blank but for you it is not. Are you running those cards in SLI?
-
So, let's be clear. You're doing CTRL+ALT+F2 waiting for the prompt then straight away doing CTRL+ALT+F7 ( or F1 ) ???
-
OK, so there is a display! This is a quick switch between those key combinations. So, you do CTRL+ALT+F2, wait for the login prompt and then CTRL+ALT+F7 (or F1 depening on settings) and the screen should come back. So you are switching between them. OK? However, there are several combinations here, F1 through F7. F7 is usually the default but can be F1 as well. This is a driver issue on certain cards. I have 1080TI and also get this sometimes. For me, CTRL+ALT+F2, then CTRL+ALT+F7 brings my screen...
-
OK, so there is a display! CTRL+ALT+F7 should normally bring the screen back. However, there are several combinations here, F1 through F7. F7 is usually the default but can be F1 as well. try CTRL+ALT+F2 then CTRL+ALT+F1 instead. This is a driver issue on certain cards. I have 1080TI and also get this sometimes. For me, CTRL+ALT+F2, then CTRL+ALT+F7 brings my screen back. Once we get the display back i can walk you through the startup script i included to get round this but, we need the screen back...
-
Ok, thanks. Try rebooting. At the black screen press CTRL+ALT+F2 wait a second for the login prompt, then CTRL+ALT+F7 does this bring the screen to life?
-
That's great thanks for reporting the issue. I will look into why it is not setting the boot flag by default.
-
Ok, try this. Use Gparted to partition and format your drive as follows: 1st partition: /boot 512mb ext4 (set boot flag - right click manage flags) 2nd partition: /root 50GB ext4 3rd partition: /home (rest of drive) ext4 4th partition (optional swap if you want. When you start Installer choose Manual option and for each partition use Keep instead of Format. That should work for you.
-
How are you partitioning your drives? Are you allowing Calamares to partition (and which option are you choosing), or are you partitioning your drive yourself with gparted or whatever tool you use first? Another thing you can check, before rebooting after install load up gparted and check that the boot flag has been set. If not you can set it then reboot.
-
How are you partitioning your drives? Are you allowing Calamares to partition (and which option are you choosing), or are you partitioning your drive yourselg with gparted or whatever tool you use first? Another thing you can check, before rebooting after install load up gparted and check that the boot flag has been set. If not you can set it then reboot.
-
Installer stuck at 80%
-
Calamares replace a partition (encrypted) not working.
-
sudo systemctl enable bluetooth.service and reboot. That should enable your bluetooth / wireless. also what is the output of: lspci -v and the output of (should be all on one line): hwinfo --netcard --wlan --bluetooth | grep -Ei "model\:|driver\:|status\:|cmd\:|file\:|detected\:" | grep -v "Config Status" Thanks
-
sudo systemctl enable bluetooth.service and reboot. That should enable your bluetooth / wireless. also what is the output of: lspci -v
-
Hi, what gfx adapter do you have? Did you install standard or nvidia version?
-
Hi, yes i am aware of this issue and will be updating the ISOs over the next day or so.
-
Hi, well Salient uses lightdm-webkit2-greeter with a theme called sequoia. There's only the possibility of changing the background image for yourself unless you get into the code itself for that theme. You also have the option of removing it and reverting back to lightdm-gtk-greeter if you prefer it.
-
Hi, yes i am aware of this issue which has now been fixed, i will be uploading new builds within the next day or so. Apologies for the inconvenience.
-
Hi there and thank you for your kind words and feedback / suggestions for your current setup. There are a number of solutions for switching between graphics hardwares and one in particular that looks interesting to me is: nvman. https://github.com/quebin31/nvman You may want to look into this particular solution. Concerning applications not starting, i personally have not experienced this and wonder if it is related to your hardware in this case? Although your suggestions / workarounds to seem plausable...
-
libinput is included in salient os, it should already be active?
-
I have considered other DE but, at this time budgie is not one of them right now. Maybe in the future though.
-
Salient OS, at this time is not really recommended for use with encrypted drives. Since its primary target audience is aimed squarley at creative / entertainment pursuits which normally don't have a requirement for encryption. This, in this context would be more of a hiderance. I can though recommend reading through the Arch Wiki documentation on this subject to ensure that your system is set up correctly and that any requred dependencies are met to enable this feature in your particular use case:...
-
Thanks for pointing this out, i will take a look and try to replicate
-
Very nice indeed :)
-
That is very kind of you to say so. I hope Salient provides you what you require.
-
Hi Mr Pops, Thank you, Woops, thank you for pointing that out i will ensure that is corrected in the next build release and thanks for taking the time to report that issue, much appreciated. Kind regards, Silent
-
Hi Paul, yes if you install xf86-video-vmware and open-vm-tools this should resolve the issue for you. Conversely, pressing CTRL+ALT+F2 then CTRL+ALT+F1 will sometimes get the desktop display to return (or whatever the vmware key combination equivalent is). Also if you had already saved an xorg.conf file, remove it and reboot.
-
Hi Paul, yes if you install xf86-video-vmware and open-vm-tools this should resolve the issue for you. Conversely, pressing CTRL+ALT+F2 then CTRL+ALT+F1 will sometimes get the desktop display to return (or whatever the vmware key combination equilelent is). Also if you had already saved an xorg.conf file, remove it and reboot.
-
Hi Paul, yes if you install xf86-video-vmware and open-vm-tools this should resolve the issue for you. Conversely, pressing CTRL+ALT+F2 then CTRL+ALT+F1 will sometimes get the desktop display to return (or whatever the vmware key combination equilelent is).
-
I need help ?
-
I would suggest downloading the standard version without nvidia drivers to test. If you can boot into the 'Live Media' you should be good.
-
Will not install
-
I am also right now building new refreshed ISOs due to some important driver updates. So there will be new files very soon.
-
Hi, ok, have you tried adding nomodeset at the boot prompt? At the grub screen press the TAB key and at the end of the text displayed, add a space then type nomodeset, press enter Or, you can try downloading the other ISO and boot from that. Only difference is you'd need to install the nvidia drivers manually as detailed in the readme once installed.
-
That's great, i'm very happy it is working for you now :)
-
Does running "rfkill unblock 0" or "rfkill unblock 1" as root make any difference to your wifi connectivity? Or you can try: modprobe iwl3945 then try connecting
-
What wi-fi module do you have Fishman, integrated, external?
-
There are new builds available now if you would like to try again.
-
If you are willing, there is a new build available now. I would be interested if you are still having the issues you described.
-
Hi there Keegan, Thank you, that's something for me to consider for sure. Calamares has been a little problemtic let's say but i think i'm learning to tame it now :) I'll have a think on your propsoal and get back to you in due course. Silent
-
Hey Eznix, I'm looking into reverting back to Calamares 3.2.3 as 3.2.4 appears to be producing this partitioning error. I'll test it out and come back to you ok? Logging in is too cumbersome with the current theme. You have to click on your user logo, which then selects your user, then click again to enable the password entry field. This is being changed for a different theme that does not exhibit this odd behaviour. Thanks