You are not logged in. Please login or register.
We are very pleased and happy to announce the newest release of Hyperbola GNU/Linux-libre with v0.4.4.
See our official news for further details.
HyperForum → System → nvme disk instalation no works
Hi people, I have a question, someone install actual version of hyperbola on `nvme` disk type file system?
for example my partition is `/dev/nvme0n1p7` and not works
then, hyperbola linux-libre default config is enable, we have `nvme` module for kernel, then, too I ask to Lxo and he tell me -maybe grub don't have some configuration or some package is lack- someone have some idea of how repair? send photo of issue
There are several points within: First the question why you need a custom nvme-module? Is the nvme-disk installed very special? Then also the point: What kind of system is that? Do you use UEFI-boot with secure-boot as option? You should always have in mind the UEFI-rom may only support 64bit, your installation has to be that same also and you would need also efi-boot supported in your structure for partitioning.
oh nice, see next:
[root@zenbook /]# efibootmgr
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0001,0002,0000
Boot0000* Windows Boot Manager
Boot0001* GRUB
Boot0002* ubuntu
[root@zenbook /]# then my disk partition is some like:
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
nvme0n1 259:0 0 476,9G 0 disk
├─nvme0n1p1 259:1 0 260M 0 part /mnt/boot/efi
│ /boot/efi
├─nvme0n1p2 259:2 0 16M 0 part
├─nvme0n1p3 259:3 0 224G 0 part
├─nvme0n1p4 259:4 0 1,1G 0 part
├─nvme0n1p5 259:5 0 142,5G 0 part /
├─nvme0n1p6 259:6 0 200M 0 part
└─nvme0n1p7 259:7 0 107,9G 0 part /mnt^ then in /mnt my hyperbola, too grub is install on nvme0n1p7 ← then that is work with anothers O.S. installed on my laptop, some idea?
The point would be first to look which system was first there and installed the bootloader, so you would have to deal there. Afterwards more information is needed as stated before: UEFI only restricted towards 64bit? Overwritten UEFI and therefore the bootloader?
The point would be first to look which system was first there and installed the bootloader
Question, thar response your answer?
# tree
.
├── EFI
│ ├── BOOT
│ │ └── BOOTX64.EFI
│ ├── GRUB
│ │ └── grubx64.efi
│ ├── Microsoft
│ │ ├── Boot
│ │ │ ├── BCD
│ │ │ ├── BCD.LOG
│ │ │ ├── BCD.LOG1
│ │ │ ├── BCD.LOG2
│ │ │ ├── bg-BG
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ └── bootmgr.efi.mui
│ │ │ ├── bootmgfw.efi
│ │ │ ├── bootmgr.efi
│ │ │ ├── BOOTSTAT.DAT
│ │ │ ├── boot.stl
│ │ │ ├── cbmr_driver.efi
│ │ │ ├── CIPolicies
│ │ │ │ └── Active
│ │ │ │ ├── {5DAC656C-21AD-4A02-AB49-649917162E70}.cip
│ │ │ │ ├── {82443e1e-8a39-4b4a-96a8-f40ddc00b9f3}.cip
│ │ │ │ └── {CDD5CB55-DB68-4D71-AA38-3DF2B6473A52}.cip
│ │ │ ├── cs-CZ
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── da-DK
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── de-DE
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── el-GR
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── en-GB
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ └── bootmgr.efi.mui
│ │ │ ├── en-US
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── es-ES
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── es-MX
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ └── bootmgr.efi.mui
│ │ │ ├── et-EE
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ └── bootmgr.efi.mui
│ │ │ ├── fi-FI
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── Fonts
│ │ │ │ ├── chs_boot.ttf
│ │ │ │ ├── cht_boot.ttf
│ │ │ │ ├── jpn_boot.ttf
│ │ │ │ ├── kor_boot.ttf
│ │ │ │ ├── malgun_boot.ttf
│ │ │ │ ├── malgunn_boot.ttf
│ │ │ │ ├── meiryo_boot.ttf
│ │ │ │ ├── meiryon_boot.ttf
│ │ │ │ ├── msjh_boot.ttf
│ │ │ │ ├── msjhn_boot.ttf
│ │ │ │ ├── msyh_boot.ttf
│ │ │ │ ├── msyhn_boot.ttf
│ │ │ │ ├── segmono_boot.ttf
│ │ │ │ ├── segoen_slboot.ttf
│ │ │ │ ├── segoe_slboot.ttf
│ │ │ │ └── wgl4_boot.ttf
│ │ │ ├── fr-CA
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ └── bootmgr.efi.mui
│ │ │ ├── fr-FR
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── hr-HR
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ └── bootmgr.efi.mui
│ │ │ ├── hu-HU
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── it-IT
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── ja-JP
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── kd_02_10df.dll
│ │ │ ├── kd_02_10ec.dll
│ │ │ ├── kd_02_1137.dll
│ │ │ ├── kd_02_14e4.dll
│ │ │ ├── kd_02_15b3.dll
│ │ │ ├── kd_02_1969.dll
│ │ │ ├── kd_02_19a2.dll
│ │ │ ├── kd_02_1af4.dll
│ │ │ ├── kd_02_8086.dll
│ │ │ ├── kd_07_1415.dll
│ │ │ ├── kd_0C_8086.dll
│ │ │ ├── kdnet_uart16550.dll
│ │ │ ├── kdstub.dll
│ │ │ ├── ko-KR
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── lt-LT
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ └── bootmgr.efi.mui
│ │ │ ├── lv-LV
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ └── bootmgr.efi.mui
│ │ │ ├── memtest.efi
│ │ │ ├── nb-NO
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── nl-NL
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── pl-PL
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── pt-BR
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── pt-PT
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── qps-ploc
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── Resources
│ │ │ │ ├── bootres.dll
│ │ │ │ ├── en-US
│ │ │ │ │ └── bootres.dll.mui
│ │ │ │ ├── es-ES
│ │ │ │ │ └── bootres.dll.mui
│ │ │ │ ├── fr-FR
│ │ │ │ │ └── bootres.dll.mui
│ │ │ │ ├── pt-BR
│ │ │ │ │ └── bootres.dll.mui
│ │ │ │ ├── pt-PT
│ │ │ │ │ └── bootres.dll.mui
│ │ │ │ └── tr-TR
│ │ │ │ └── bootres.dll.mui
│ │ │ ├── ro-RO
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ └── bootmgr.efi.mui
│ │ │ ├── ru-RU
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── sk-SK
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ └── bootmgr.efi.mui
│ │ │ ├── sl-SI
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ └── bootmgr.efi.mui
│ │ │ ├── sr-Latn-RS
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ └── bootmgr.efi.mui
│ │ │ ├── sv-SE
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── tr-TR
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ ├── uk-UA
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ └── bootmgr.efi.mui
│ │ │ ├── winsipolicy.p7b
│ │ │ ├── zh-CN
│ │ │ │ ├── bootmgfw.efi.mui
│ │ │ │ ├── bootmgr.efi.mui
│ │ │ │ └── memtest.efi.mui
│ │ │ └── zh-TW
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ └── Recovery
│ │ ├── BCD
│ │ ├── BCD.LOG
│ │ ├── BCD.LOG1
│ │ └── BCD.LOG2
│ └── ubuntu
│ ├── BOOTX64.CSV
│ ├── grub.cfg
│ ├── grubx64.efi
│ ├── mmx64.efi
│ └── shimx64.efi
├── FSCK0000.REC
└── System Volume Information
54 directories, 155 filesSee you friends, I have send email to grub developers too:
Well, there are already some recommendations included like checking your fstab.
I wonder what using an nvme would be like on one of those nitropads that has 10th gen processors...
This I wonder, due to nitropads having intel me disabled at boot point with intel me network stack deactivated and coreboot variant heads bios on them.
Anywho, food for thought.
@saravia I wish you the best on figuring out what happened. Its possible microsoft got in the way. They do have a partnership with ubuntu, maybe that's why Hyperbola broke and Ubuntu didn't?
:s
The ASUS Zenbook is all but for sure not a good and libre-friendly computer. I have made myself enough experiences with older revisions to state: Installation of free and libre systems on those computers? Better try not. Yes, the UEFI-rom was able to work with legacy boot-mode and therefore enabling installation of a GNU/Linux-system but first this was about more than 9 years ago and second also other ways. And I want to underline again: UEFI is per default nothing bad or problem. It depends on the way it was done and which kind options included. And ASUS is surely not the user-friendly manufacturer delivering.
That said: It is for the moment not possible to support here until somebody has a comparable system and can provide more information or ideas.
The ASUS Zenbook is all but for sure not a good and libre-friendly computer. I have made myself enough experiences with older revisions to state: Installation of free and libre systems on those computers? Better try not. Yes, the UEFI-rom was able to work with legacy boot-mode and therefore enabling installation of a GNU/Linux-system but first this was about more than 9 years ago and second also other ways. And I want to underline again: UEFI is per default nothing bad or problem. It depends on the way it was done and which kind options included. And ASUS is surely not the user-friendly manufacturer delivering.
That said: It is for the moment not possible to support here until somebody has a comparable system and can provide more information or ideas.
If you can't put coreboot on it and neuter the intel me, then yeah.
But curious if you have seen, this... below:
https://en.wikipedia.org/wiki/Intel_Act … curity1-82
https://web.archive.org/web/20170828150 … el-me.html
https://thinkpenguin.com
https://configurelaptop.eu/
https://starlabs.systems/
https://system76.com/
Those 4 are the only ones I would even consider with the newer gens.
Oh I have seen many of them for sure. The problem is in the detail: Coreboot is fine, but Nvidia on the opposite side? Nope, not fine as you need again non-free blobs to run it. But let's stay on-topic. It is NOT only the hardware, it is the full blown part of the software. That's the issue!
Cool, I solve the problem, yeah!... I rename
/etc/fstabwith:
root=PARTUUID=b35cf2ee-077a-844a-b9872-7d622b45ee74 / ext4 rw,relatime 0 1too, for:
/etc/mkinitcpio.confI add to MODULES section:
MODULES="vfat ntfs ext4 vmd"then, run again:
grub-mkconfig -o /etc/grub/grub.cfg
mkinitcpio -p linux-libre-ltsHyperForum → System → nvme disk instalation no works
Powered by PunBB, supported by Informer Technologies, Inc.