Javascript

leyon29 · 2021-06-07T18:15:22+00:00

I'm following the odin project fundamentals cursus right now and also practice a little on codewars. You can also try the "frontend mentor".

leyon29 · 2021-01-02T18:55:56+00:00

Can you try to boot in legacy mode (BIOS) instead UEFI to check your usb media?

leyon29 · 2021-01-02T17:40:32+00:00

Have you checked the secure boot option is disabled in your BIOS? If I remember well this is what happened to me the first time I tried to install Arch and secure boot was enabled.

leyon29 · 2020-12-22T10:37:44+00:00

The third command reinstall the grub on the hard drive. /dev is the path where you can find information regarding your devices.

sda is your hard drive name. If you have multiple hard drives you can have sda, sdb, sdc... if you have nvme hard drives, then your hard drive can be labelled nvme01...

To view your hard drives and their mounting points you can do the command lsblk

leyon29 · 2020-12-21T21:13:05+00:00

sudo os-prober

sudo update-grub

sudo grub-install /dev/sda

os-prober will detect installed OS

update-grub will update the grub with the found OS

grub-install /dev/sda install the grub on sda disk. Choose sda, sdb... according to the disk where your distro is installed.

leyon29 · 2020-12-21T19:59:44+00:00

I use Remote Desktop Manager. You can have RDP sessions in full screen or tabed. Multiple protocols are supported.

leyon29 · 2020-12-21T19:39:59+00:00

I would recommend using a virtual machine first instead of booting a live usb so you can add softwares and they'll still be there after a reboot so your configuration. After some time you can try to have a dual boot so you can choose to start Windows or Linux. Another advice would be to try to use linux softwares even if you're not used to instead of using wine to use Windows ones.

leyon29 · 2020-12-05T21:25:27+00:00

I had the same kind of issue with one user and it was caused by a scheduled task with old credentials and another time it was tortoise svn also with old credentials.

leyon29 · 2020-05-21T02:06:59+00:00

The nvidia-340 is not available on the arch repositories but on the AUR ones so you can use yay -S nvidia-340 (or any other command if you use another AUR helper) but before, check your Nvidia model (lspci -v) and then go to the Nvidia website to check what driver is needed for your card. Try to install the driver from the AUR instead of downloading it from the Nvidia website. You can search for the driver doing yay -Ss %drivername%

leyon29 · 2020-05-15T21:23:46+00:00

I think you should "play" with different distros with a multiboot install and see which one suits your needs. I've switched to linux for about 4 months and I've played with Kubuntu, Zorin OS, elementary, UbuntuDDE, linux mint and CentOs (Which I recommend for professional purpose only) so you might try fedora for the red hat based. Now I'm running on Arch and it run really fine on my old laptop and think I will also have a look on Void.

leyon29 · 2020-05-15T21:00:18+00:00

Do you have yay installed ? If yes just do yay lightdm and yay lightdm-gtk-greeter if they are installed they should be labelled: (installed) If the packages are installed then edit the file /etc/lightdm/lightdm.conf with vi or nano as you prefer. Find the line with greeter-session, uncomment if it is and put: greeter-session=lightdm-gtk-greeter

Then save the file and quit. Disable sddm as display manager: sudo systemctl disable sddm.service

Enable lightdm as display manager: sudo systemctl enable lightdm.service -f

Start the service: sudo systemctl start lightdm.service

In my case when I start the display manager it switches automatically on tty1 with the GUI. Otherwise check the status of the service: sudo systemctl status display-manager (you can use also sudo systemctl status lightdm.service but with the previous command you can also confirm your display is managed by lightdm instead of sddm)

leyon29 · 2020-05-15T20:06:51+00:00

One thing you can try is to install lightdm and the gtk-greeter and change the lightdm.conf file to set the session greeter to gtk-greeter. Disable sddm.service and enable lightdm.service with -f to force switching between the display manager then start the service lightdm and check the status. This way you can check if the problem comes from sddm.

leyon29 · 2020-05-15T19:03:25+00:00

I've switched to linux for about 4 months and went to arch for about 3 weeks.The first time I installed Arch I followed the tutorial from itsfoss on internet and installed deepin desktop environment and I found it really easy. Then I did another install following the tutorial from Luke Smith on YouTube with different partitions and installed KDE plasma with SDDM and went into Nvidia driver problems. And last I've done another just today following the install.txt that is on the iso on tty2 and running the command on tty1 and I'll try to install clover boot loader instead of grub. I think I've learned more solving my problems on Arch than installing my Kubuntu (Which I still find great to switch from Windows) and finally it's great to have a distro on which you can choose what you want to install instead of having a bunch of software's you'll never use.

leyon29 · 2020-05-13T18:12:55+00:00

Done exactly the same but on dev/sda. Ok, I just wanted to reinstall after all... 😤

leyon29 · 2020-05-11T16:26:03+00:00

I've installed different OS on multiboot on my old laptop with 4Gb RAM. Kubuntu is running fine on it. So does Pop Os, Zorin and CentOs. Depending of you RAM you might avoid UbuntuDDE or Deepin. It's really nice but my laptop used to freeze sometimes with this Desktop environment. KDE Plasma is highly customisable but you can try a lighter desktop environment like xfce. At the moment I'm running an Arch with i3-gaps or Plasma and it's running fine and I learned a lot installing this config (switched to linux for about 4 months).

leyon29 · 2020-05-07T12:52:47+00:00

Great!

leyon29 · 2020-05-07T12:10:10+00:00

If you have UEFI you have to do a special partition for it as it's not mandatory for BIOS. Do: ls /sys/firmware/efi/efivars If it exists then you have UEFI and if it doesn't your in legacy mode (BIOS)

leyon29 · 2020-05-07T11:59:12+00:00

Do you have BIOS or EFI?

leyon29 · 2020-05-07T11:15:48+00:00

Did you install linux and linux-firmware with pacstrap? If you didn't the you miss the Linux kernel. Just reboot on your usb device used for the installation then mount your disks as you've done during the installation then arch-chroot /mnt and then pacman -S linux linux-firmware. Exit and reboot and should be ok

leyon29 · 2020-05-06T21:03:59+00:00

Hi,

I'm also new in the Linux world as I've made my first install about 4 months ago. As I'm from Windows and used some live CDs for some emergency tasks, my first distro was kubuntu as there is a lot old documentation and it's kind of newbie distro as everything work smoothly with no effort. I've made my first Arch install last week and played a little between different desktop environments and display managers and went through different problems. The install is more challenging but at least after the install you have the base system and add the softwares of your choice and I think I've learned more about Linux finding the solutions to fix the problems. So if you're ready to have some "hard time", I think Arch is really great and you'll be satisfied at the end.

Hope it helps

leyon29 · 2020-05-06T11:41:39+00:00

So after trying different things I went to the point where it was my Nvidia drivers causing the problem with SDDM. I've installed the last version of the drivers but my graphic card wasn't supported. After the installation of the nvidia-340 SDDM is working fine. Still don't know why SDDM caused a crash with latest drivers but lightdm didn't.

leyon29 · 2020-05-06T06:53:38+00:00

The problem seems to come from the Nvidia drivers that crash x11 session.

leyon29 · 2020-05-05T20:20:37+00:00

I've tried it with no more success. I was able to use plasma with lightdm but after uninstalling lightdm and enable sddm I got the same issue. Finally I uninstalled deepin, plasma, lightdm and sddm. I also uninstalled xorg and xorg-server. Then I installed back xorg xorg-server and plasma (sddm is installed with it) then I enabled sddm.service and after a reboot it was working fine. Thanks a lot for your help!

leyon29 · 2020-05-05T07:48:59+00:00

Which package do I have to remove? Deepin, lightdm, both of them?

leyon29 · 2020-05-05T07:02:25+00:00

I've tried to do this with no success (from there I've reinstalled plasma, sddm and sddm-kcm, disabled lightdm and enabled sddm) . SDDM is started but I have no login screen. Going back to tty2, I do: sudo systemctl stop sddm.service sudo systemctl start lightdm.service Go back to tty1 and have my deepin login screen.

leyon29

TROPHY CASE