Activity for New1997
-
New1997 posted a comment on discussion Advanced Topics
Thank you for the info, will do, 😁😁😁
-
haha, lol, that was funny 🤣🤣🤣🤣. That's not what I meant, I was meaning to ask if there are people to help you or other people who experience the same problem on other distro or if someone mentioned it on the chat of Peppermeint OS, or that you spent all this time reproducing the error and tried to figured it out on your own. By the way you answer, I'd say that you spend a lot of time to figure it out and there was little to no help from others. It was because you said that "the fix has been in for...
-
Oh!!! where did you get the info? I didn't know, I'd love to have that too, thank you very much!!! I did see your answer in superuser, thank you very much
-
When choose the option encrypt disk and after the installation process and reboot. Before entering to grub I was asked to input the disk key, then grub initialized, and after that I got kick to busybox reason : the GRUB config was to look for /dev/mapper/luks-UUID, when manually decrypt using cryptsetup /dev/sda1 UUID the decrypted system was /dev/mapper/UUID solution : use live usb to boot into it, decrypt the partition, mount in mnt and modify both in /mnt/etc/default/grub and /mnt/boot/grub/grub.cfg...
-
When choose the option encrypt disk and after the installation process and reboot. Before entering to grub I was asked to input the disk key, then grub initialized, and after that I got kick to busybox reason : the GRUB config was to look for /dev/mapper/luks-UUID, when manually decrypt using cryptsetup /dev/sda1 UUID the decrypted system was /dev/mapper/UUID solution : use live usb to boot into it, decrypt the partition, mount in mnt and modify both in /mnt/etc/default/grub and /mnt/boot/grub/grub.cfg...
-
@cavy Good news, I actually found the solution, full detail in https://superuser.com/questions/1714597/peppermint-os-boot-failure-because-of-disk-encryption/1716808#1716808 so you can reproduce the error and follow the solution steps. The problem is indeed within "luks-" prefix, but not in the way I originally thought and I'll give summary here: First of all, everything is configured "correctly" but somehow the /etc/crypttab is not working and did not decrypt the partitions, upon removing all "luks-"...
-
Nope, what I said is wrong, lol. I misunderstood the text, I just reread, in LUKS1 the volume key can be found by user space, so having a key file doesn't change a thing, where LUKS2 the volume key is offloaded to the kernel keyring, so having a key file is less secure (and the first time I read it I thought that it can pass the password to the kernel, but upon rereading again, it seems to not be the case)
-
nice!!! 👍👍👍, BTW I might have found a solution on my side too regarding getting kicked to busybox (initramfs), I'll be tweaking a bit and if it works, I'll post the solution to super user stack exchange as an answer to myself, so those with the same problem can refer to it. If I understand it correctly it only present on LUKS1 and not LUKS2. So in the future, this solution might not be necessary at all. Thank you for your hard work and dedication and your time that you invested in this matter
-
nice!!! 👍👍👍, BTW I might have found a solution on my side too regarding getting kicked to busybox (initramfs), i'll be tweaking a bit and if it works, i'll post the solution to super user stack exchange as an answer to myself, so those with the same problem can refer to it. If I understand it correctly it only present on luks V1 and not V2. So in the futur, this solution might not be necessary at all. Thank you for your hard work and dedication and your time that you invested in this matter
-
thank you so much for your response, I'll be waiting patiently for all the new features, including 32 bit version, and to see the new ICE (I totally get what you mean, browsers these days are too resource hungry, not to mention all the website that are bloated with cookies and tracking and so on) so yay for browser agnostic future.
-
thank you for your reply, I'll try my best to see what I can do at my end (either informing them about the issue or trying to see how I can solve the problem) thank you for your time
-
OK, But my concern is, can you include the warning on your installation process to warn any future installer? and what about "luks-" that precede the UUID which make the mounting process go haywire, which I need to modify grubs and /etc/fstab to solve the problem? I do understand calamares and ubiquity is what is out of your power or are you trying to tell me that the "luks-" naming before UUID is part of ubiquity and that is where I should address my concerns? (and that means it is them who should...
-
I can see it now, thx, the current version is 11 right? (just to be sure)
-
Thanks for your reply, so essentially bad documentation and being lead to this, I presume? May I ask that you include some warning to the installer to prevent further case (maybe I got too hasty and did not read it, if that is the case, I apologize, otherwise, might appreciate the heads up). also aside from getting kick into busybox, can you do something about "luks-" before the UUID (In GRUBS when booting and in fstab when mounting, for those who want to encrypt \ or more, just in every case even...
-
(For those who like full version) $ inxi -Fxz System: Kernel: 5.10.0-13-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: Xfce 4.16.0 Distro: Debian GNU/Linux 11 (bullseye) Machine: Type: Laptop System: Hewlett-Packard product: Presario V3000 (RY213PA#AKL) v: F.39 serial: <filter> Mobo: Wistron model: 30B2 v: 61.65 serial: <filter> BIOS: Hewlett-Packard v: F.39 date: 08/27/2007 Battery: ID-1: BAT0 charge: 5.6 Wh condition: 5.6/47.5 Wh (12%) model: Hewlett-Packard Primary status: Full CPU: Info:...
-
$ neofetch _,met$$$$$gg. ,g$$$$$$$$$$$$$$$P. --------------- ,g$$P" """Y$$.". OS: Debian GNU/Linux 11 (bullseye) x86_64 ,$$P' `$$$. Host: Presario V3000 (RY213PA#AKL) F.39 ',$$P ,ggs. `$$b: Kernel: 5.10.0-13-amd64 `d$$' ,$P"' . $$$ Uptime: 6 hours, 24 mins $$P d$' , $$P Packages: 1704 (dpkg) $$: $$. - ,d$$' Shell: bash 5.1.4 $$; Y$b._ _,d$P' Resolution: 1280x800, 1280x720 Y$$. `.`"Y$$$$P"' DE: Xfce 4.16 `$$b "-.__ WM: Xfwm4 `Y$$ WM Theme: Default `Y$$. Theme: Peppermint-10-Red-Dark [GTK2/3] `$$b....
-
I just think carefully and trying to search as much as possible, but hen this occur to me : the reason that I got kicked into busybox might be because that the password from grub loader did not get passed down while booting, so ok, but what about the fact that I need to get dirty and use a live boot usb to edit the grub configuration file to remove the "luks-" before each UUID out in order for it to work, can you guys at the very least see to this "minor" configuration issue? because that would be...
-
I didn't choose, the installer encrypt every partition, when choosing which partition to install Peppermint, I choose the entire disk and left to auto, and then check the encryption button, the rest was done by the installer, even the swap partition got encrypted
-
I didn't choose, the installer encrypt every partition, when choosing which partition to install Peppermint, I choose the entire disk and left to auto, and then check the encryption button, the rest was done by the install, even the swap partition got encrypted
-
the link to the announcement failed to load the timeline that you wanted to show me so I can't read the announcement but only the recent post, and I don't understand want do you want me to see in the documentation. As for graphic requirement, I am a bit ignorant on this part, so why do we need this much, even when we are using on a machine that we do not intend to play game or editing high resolution video? (as for software that maybe true, they are too power hungry and we must promote the lightweight...
-
When choose the option encrypt disk and after the installation process and reboot. Before entering to grub I was asked to input the disk key, then grub initialized, and after that I got kick to busybox reason : the GRUB config was to look for /dev/mapper/luks-UUID, when manually decrypt using cryptsetup /dev/sda1 UUID the decrypted system was /dev/mapper/UUID solution : use live usb to boot into it, decrypt the partition, mount in mnt and modify both in /mnt/etc/default/grub and /mnt/boot/grub/grub.cfg...
-
Why the newer Peppermint OS has dropped it's development for 32 bit processor? This wasn't really mention anywhere (if mentioned it was too well hidden for me who only look at the installation page). And also, since I just check the OS (downloaded and installed) a few days ago I don't know what version it currently is the downloaded files just said PeppermintOS-amd64, so version 11 I assume ? also the browser compatible with ICE are too resource hungry (I have only test firefox-esr but I bet chromium...
1