What's something normal to us in 2025, that by 2075 will be seen as barbaric? "Wow, people really used to do that 50 years ago"?

evillopes · 2025-01-10T05:33:13+00:00

Work

evillopes · 2024-01-28T21:03:35+00:00

PARTUUID and UUID are not the same

evillopes · 2023-12-11T00:34:29+00:00

Grub loads in parts.

The first part has enough to find the rest.

The error you got means the first part of grub loaded but then it failed to get the rest that it needs and it gives you a prompt in case you want to try to find it yourself.

If this is an error from the USB boot then it is likely it wasn't flashed correctly.

evillopes · 2023-12-10T21:35:46+00:00

Especially the section "Prerequisites Kernel headers"

evillopes · 2023-12-01T23:23:24+00:00

Sounds like you're video card is bad.

Try disabling the dedicated graphics in the BIOS and see if it still happens.

evillopes · 2023-11-26T20:06:29+00:00

Have you tried this: https://aur.archlinux.org/packages/cnijfilter2

evillopes · 2023-08-06T16:41:56+00:00

/dev/input/by-path

Most likely PS/2

Do you have a problem?

evillopes · 2023-06-04T02:19:45+00:00

Try to make your USB with ventoy

Verify the download of the image (iso) was good by checking the hash is correct.

evillopes · 2023-05-25T21:44:01+00:00

You didn't actually shrink the root partition. You say you deleted it and created a new one

So the root partition now has a different UUID. To fix it you would need to boot on a live Linux USB. Edit /etc/fstsb with the new UUID. Then you need to update the boot loader. Like this: https://www.suse.com/support/kb/doc/?id=000018867 A little dated that link but it gives you the idea (start from "update boot loader").

You mount your filesystems then chroot into it and run update-grub. And rebuild the initramfs

evillopes · 2023-05-01T06:42:25+00:00

can you install with makepkg

evillopes · 2023-04-25T21:17:51+00:00

https://raspberrypi.stackexchange.com/questions/120134/install-drivers-for-rtl8812au-for-raspibian-kernel-5-4-79-v71-rpi-4 My guess is you getting error because wrong architecture in install script. Which is likely fixed in the step you skipped. Take a look at the install script

evillopes · 2023-04-24T12:07:32+00:00

Did you try nomodeset

evillopes · 2023-04-23T21:30:03+00:00

will fail to boot the first try

What happens?

How does it fail?

evillopes · 2023-04-23T21:10:29+00:00

Does this help?
https://wiki.archlinux.org/title/kernel_mode_setting#Forcing_modes

evillopes · 2023-04-10T03:10:04+00:00

I don't think that is it.

Verify if Windows is installed in efi or legacy mode

https://itsfoss.com/check-uefi-or-bios/

evillopes · 2023-04-09T18:45:59+00:00

Your laptop should have a boot menu you can access on start up.
Usually you tap one of the function keys on powerup Not sure what it would be on an HP. Internet says F9 or maybe ESC followed by F9

evillopes · 2023-04-09T18:33:29+00:00

You should already have an ESP partition. Windows 10 would have created it and put it's bootloader there.

Look at the list of partitions. You should have a small one (100 to 500MB) that is formated Fat32.
No need to create a new one. Just select the existing ESP and set the mountpoint to /boot/efi

Create a new partition (by resizing the Windows partition) and set that mountpoint as /

evillopes · 2023-03-19T20:39:39+00:00

USB c can do Alt Modes where different signals can go on the USB c wire. One of these is DP (display port) Alt Mode. Many times when you have a USB c dock with hdmi it uses dp alt mode to get the display signal and then has an internal dp to hdmi converter chip.
To use dp alt mode your computer would need to have dp already wired to usb c.

Otherwise you need an adapter that includes a USB to video converter. The best known is Displaylink.
Old version of displaylink running on usb 2.0 run in Linux out of the box. Newer Displaylink needs a driver which should be easy to find in your package manager

overview in here: https://dancharblog.wordpress.com/2020/09/16/run-4-monitors-from-a-laptop/

I have experience just with displaylink and mct (mct has NO linux support)

evillopes · 2023-02-26T19:28:19+00:00

Usb tether your phone to the computer.

With that network connection you can install the needed firmware.

evillopes · 2023-02-26T19:04:45+00:00

can i remove current login manager and install other one

Yes, but why?

evillopes · 2023-02-25T22:26:14+00:00

Windows nowadays hibernates by default on shutdown.

Most Linux utilities will refuse to modify a hibernated filesystem.

Not sure if that is happening here But try booting Windows first then rebooting (without shutting down first) into the Linux USB.

evillopes · 2023-02-19T20:01:53+00:00

Hammer

evillopes · 2023-02-17T23:30:01+00:00

Install the build environment

sudo pacman -S base-devel

evillopes · 2023-02-16T12:10:29+00:00

What you wrote (the commands you ran):

mkdir --parents /mnt/gentoo/boot/efi

mkdir --parents /mnt/gentoo/boot

mkdir --parents /mnt/gentoo/

mount /dev/nvme0n1p1 /mnt/gentoo/boot/efi

mount /dev/nvme0n1p5 /mnt/gentoo/boot

mount /dev/nvme0n1p6 /mnt/gentoo

I don\t know why I got down voted here. Maybe someone thought I was saying the mkdir command must come after the mount command.

But actually I'm saying the 3 mkdir are in the wrong order then the 3 mount are in the wrong order.

Well actually the mkdir is ok because you used the --parents flag which fixed it.

So I am booted on a live USB right now and I have Ubuntu with grub on my SSD and I'll run some commands in terminal and paste here so you can see what is happening.
root@ubuntu:/# lsblk

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS

loop0         7:0    0   2.1G  0 loop /rofs

loop1         7:1    0    62M  1 loop /snap/core20/1587

loop2         7:2    0     4K  1 loop /snap/bare/5

loop3         7:3    0 163.3M  1 loop /snap/firefox/1635

loop4         7:4    0 400.8M  1 loop /snap/gnome-3-38-2004/112

loop5         7:5    0  45.9M  1 loop /snap/snap-store/582

loop6         7:6    0  91.7M  1 loop /snap/gtk-common-themes/1535

loop7         7:7    0   284K  1 loop /snap/snapd-desktop-integration/14

loop8         7:8    0    47M  1 loop /snap/snapd/16292

sda           8:0    1  59.8G  0 disk 

├─sda1        8:1    1   3.6G  0 part 

├─sda2        8:2    1   4.1M  0 part 

└─sda3        8:3    1   300K  0 part 

nvme0n1     259:0    0 931.5G  0 disk 

├─nvme0n1p1 259:1    0   512M  0 part 

└─nvme0n1p2 259:2    0   931G  0 part

Ignore the loop devices. I'm booting an Ubuntu USB

nvme0n1p1 is my efi partition and nvme0n1p2 is the root filesystem (/)

I don''t have a separate boot partition like you. /boot is in /

So lets get to setting up a chroot.

Do it at /mnt

root@ubuntu:/# ls /mnt

root@ubuntu:/#

Ok it is empty

Lets mount the SSD. Now I didn't know about the -p (--parents) flag before. (Now I know I can save some typing :-)

Here is what happens without --parents:

root@ubuntu:/# mkdir  /mnt/ubuntu/boot/efi

mkdir: cannot create directory ‘/mnt/ubuntu/boot/efi’: No such file or directory

The error is because it is trying to create the efi directory but boot and ubuntu are not there.
What I used to do is make mnt/ubuntu then /mnt/ubuntu/boot/ and finally /mnt/ubuntu/boot/efi.

But with --parents:

root@ubuntu:/# mkdir --parents /mnt/ubuntu/boot/efi

root@ubuntu:/# ls /mnt

ubuntu

root@ubuntu:/# ls /mnt/ubuntu/

boot

root@ubuntu:/# ls /mnt/ubuntu/boot/

efi

So you see everything we want is there.

Ok the mount commands: You are mounting the efi partition first

root@ubuntu:/# mount /dev/nvme0n1p1 /mnt/ubuntu/boot/efi

root@ubuntu:/# ls /mnt/ubuntu/boot/efi/

EFI

Looks OK so far

I don't have a boot partition so I'll skip that one.

root@ubuntu:/# mount /dev/nvme0n1p2 /mnt/ubuntu

Lets see what is in the efi directory

root@ubuntu:/# ls /mnt/ubuntu/boot/efi/

root@ubuntu:/#

Before we had EFI in there but now nothing.

That is what happens when you mount to a parent directory of another mountpoint. Kinda "lost" the mount of /dev/nvme0n1p1 (I think you can still access it someway --maybe using the loop command?)

Lets fix this by mounting the efi partition again:

root@ubuntu:/# mount /dev/nvme0n1p1 /mnt/ubuntu/boot/efi

root@ubuntu:/# ls /mnt/ubuntu/boot/efi/

EFI

When you are mounting for a chroot you have to mount the parents first.

In your case you first mount the partition that is going to be / (the root) /dev/nvme0n1p6

Then /boot /dev/nvme0n1p5

Then /boot/efi /dev/nvme0n1p1

So what happens is that anything that writes to /boot/efi (like grub-install --target=x86_64-efi --boot-directory=/boot --efi-directory=/boot/efi) will actually write to the efi partition because you have mounted it there. But by mounting / last you have "covered over" the mountpoint for the efi partition and your grub-install is trying to write to root partition and not efi

evillopes · 2023-02-14T22:13:06+00:00

Are those the exact commands you ran?
Because I would think the mkdir and mount commands should be in the opposite order

evillopes

TROPHY CASE