Hang when boot to install iso

[neptalactone]

I tried booting the iso that i downloaded from the release page, when the grub menu show up and i pick one, it cause my laptop to hang and make my laptop fans spin faster.

I burn the iso to bootable usb with dd from another distro and i download the amd64 iso of march 2021 snapshot

Here's the screen shot from which it hang

When I try on qemu/kvm, it boot up:

[neptalactone]

It hangs on my computer (barebones) for a bit too but later on boots fine

But the fan spins faster is my main concern, is it normal behavior?

Edit: i already wait around 1 hour and i still hang on grub menu

[neptalactone]

hmm, what about your firmware?

How i check that? I pick the firmware choice on grub but it still hang. As for my laptop specs, it is Acer Nitro 5 with specs:

CPU: AMD Ryzen 5 3550H
iGPU: AMD Radeon Vega 8 Mobile
dGPU: AMD Radeon RX 550X
SSD M.2 NVMe 500 GB
Wireless Qualcomm Atheros (ath10k)
Wired Realtek

[ergpopler]

to see if it is a firmware issue, try booting into a wholly free distro, such as the ones approved by the GNU project (Parabola GNU/Linux-libre, for instance).

If you are able to boot into that, then it is likely not a non-free firmware issue.

Have you tried with both UEFI and Legacy?
|____ If not, try both.

[neptalactone]

to see if it is a firmware issue, try booting into a wholly free distro, such as the ones approved by the GNU project (Parabola GNU/Linux-libre, for instance).

If you are able to boot into that, then it is likely not a non-free firmware issue.

Have you tried with both UEFI and Legacy?
|____ If not, try both.

It is arch-based distro right? i can boot up to arch, i have both fedora and arch on my laptop since i use btrfs to shared both OS on a single partition. Nevertheless, I'll try it when i get home.

My Laptop only support UEFI boot. i didn't find in BIOS setting to boot into legacy

[neptalactone]

It's not based on arch, read the site...

чт, 8 апр. 2021 г., 09:38 Abdul Subayu @.***>:

to see if it is a firmware issue, try booting into a wholly free distro,
such as the ones approved by the GNU project
https://www.gnu.org/distros/free-distros.html (Parabola GNU/Linux-libre
https://www.parabola.nu/, for instance).

If you are able to boot into that, then it is likely not a non-free
firmware issue.

Have you tried with both UEFI and Legacy?
|____ If not, try both.

It is arch-based distro right? i can boot up to arch, i have both fedora
and arch on my laptop since i use btrfs to shared both OS on a single
partition. Nevertheless, I'll try it when i get home.

My Laptop only support UEFI boot. i didn't find in BIOS setting to boot
into legacy

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#246 (comment),
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALI22ENRV4JFEDVJDZ4EEPLTHVFQDANCNFSM42PCSJMQ
.

[neptalactone]

to see if it is a firmware issue, try booting into a wholly free distro, such as the ones approved by the GNU project (Parabola GNU/Linux-libre, for instance).

If you are able to boot into that, then it is likely not a non-free firmware issue.

Have you tried with both UEFI and Legacy?
|____ If not, try both.

Him it's me again. I already try to boot the parabola iso on my laptop. And it's boot up fine. I confused why ataraxia won't boot on my laptop

[ghost]

Not sure what's wrong here. Seems odd it would hang there. Maybe ur installation media got corruped somehow?

[ghost]

Try using balenaetcher and let it verify. If that doesn't work still, try using the previous snapshot.

[neptalactone]

Not sure what's wrong here. Seems odd it would hang there. Maybe ur installation media got corruped somehow?

This could be possible, but i already tried to download the same image 3 times and burn it to usb, it was still the same.

[neptalactone]

Try using balenaetcher and let it verify. If that doesn't work still, try using the previous snapshot.

I even use rufus and balenaetcher aside with dd. I'll try with the previous snapshot to see if it'll work

[ghost]

Try using balenaetcher and let it verify. If that doesn't work still, try using the previous snapshot.

I even use rufus and balenaetcher aside with dd. I'll try with the previous snapshot to see if it'll work

Be sure to let us know if that works. The latest snapshot is just an updated version of the last snapshot for the most part as far as I know. If you have luck, be sure to let us know!

[neptalactone]

Hi. It's me again, I already tried the february snapshot iso and the result is just the same as before. I already tried with rufus, balenaetcher, and dd to make the bootable. But none seems to boot up and alway hang in the aftermath of grub menu.

[neptalactone]

Hi it's me again to update my situation. I tried the November snapshot and I'm able to boot! I try it 3 times with balena, rufus, and dd. Only balenaetcher that didn't show the bootable in bios.

One thing also that i noticed, when i burn the november snapshot iso with rufus, i get this option

which i didn't get with both february and march snapshot

I tried both options and i still able to boot

[neptalactone]

Also i want to give update that i tried to redownload the march snapshot today, and give it another try. I try burn it with rufus iso mode (both GPT and MBR), i only greeted by grub shell. Then i try to burn it with both rufus dd mode and dd, i got the grub menu.

When i burn with rufus dd mode in MBR, in grub menu selection, i tried to edit the boot option, i edit the initrd entry to get on similar position with the vmlinuz img entry then boot up. It hang a bit then it will reboot by itself. I tried the firmware grub menu, edit it the same and made 2 entry of initrd to seperate the seiba.zst and the firmware.zst on different line, it will hang a bit then it will show this kernel panic.

When i tried with balena and dd, this didn't happen and it will only hang after the grub menu

[neptalactone]

Well if you removed "seiba.zst" then basically the os won't load because
it's very small version of ataraxia

ср, 14 апр. 2021 г., 08:51 Abdul Subayu @.***>:

Also i want to give update that i tried to redownload the march snapshot
today, and give it another try. I try burn it with rufus iso mode (both GPT
and MBR), i only greeted by grub shell. Then i try to burn it with both
rufus dd mode and dd, i got the grub menu.

When i burn with rufus dd mode in MBR, in grub menu selection, i tried to
edit the boot option, i edit the initrd entry to get on similar position
with the vmlinuz img entry then boot up. It hang a bit then it will reboot
by itself. I tried the firmware grub menu, edit it the same and made 2
entry of initrd to seperate the seiba.zst and the firmware.zst on different
line, it will hang a bit then it will show this kernel panic.
[image: IMG_20210414_123432.jpg]
https://user-images.githubusercontent.com/34985816/114660719-fb43be80-9d1f-11eb-86ec-db1dfe0de352.jpg

When i tried with balena and dd, this didn't happen and it will only hang
after the grub menu

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#246 (comment),
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALI22EJ7I5DLZXT6WXX5FL3TIUUN5ANCNFSM42PCSJMQ
.

I didn't remove it, i just separate the seiba.zst and firmware.zst to different line. From this

linux /seiba.img
initrd. /seiba.zst /seiba/firmware.zst

To this

linux. /seiba.img
initrd. /seiba.zst
initrd. /seiba/firmware.zst

And by i mean that change the initrd entry to similar position with the .img is like this

Default:
linux. /seiba.img
initrd. (6 space) /seiba.zst

To this:
linux. /seiba.img
initrd. (4 space)/seiba.zst

[neptalactone]

grub does not work that way... ср, 14 апр. 2021 г., 09:05 Abdul Subayu @.>:
…
Well if you removed "seiba.zst" then basically the os won't load because it's very small version of ataraxia ср, 14 апр. 2021 г., 08:51 Abdul Subayu @.>: Also i want to give update that i tried to redownload the march snapshot today, and give it another try. I try burn it with rufus iso mode (both GPT and MBR), i only greeted by grub shell. Then i try to burn it with both rufus dd mode and dd, i got the grub menu. When i burn with rufus dd mode in MBR, in grub menu selection, i tried to edit the boot option, i edit the initrd entry to get on similar position with the vmlinuz img entry then boot up. It hang a bit then it will reboot by itself. I tried the firmware grub menu, edit it the same and made 2 entry of initrd to seperate the seiba.zst and the firmware.zst on different line, it will hang a bit then it will show this kernel panic. [image: IMG_20210414_123432.jpg] https://user-images.githubusercontent.com/34985816/114660719-fb43be80-9d1f-11eb-86ec-db1dfe0de352.jpg When i tried with balena and dd, this didn't happen and it will only hang after the grub menu — You are receiving this because you commented. Reply to this email directly, view it on GitHub #246 (comment) <#246 (comment)> , or unsubscribe https://github.com/notifications/unsubscribe-auth/ALI22EJ7I5DLZXT6WXX5FL3TIUUN5ANCNFSM42PCSJMQ . I didn't remove it, i just separate the seiba.zst and firmware.zst to different line. From this linux /seiba.img initrd. /seiba.zst /seiba/firmware.zst To this linux. /seiba.img initrd. /seiba.zst initrd. /seiba/firmware.zst And by i mean that change the initrd entry to similar position with the .img is like this Default: linux. /seiba.img initrd. /seiba.zst To this: linux. /seiba.img initrd. /seiba.zst — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#246 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALI22EPT4HYV3IJP4XDLHVTTIUWCHANCNFSM42PCSJMQ .

Yeah sorry, i just try if it will do something :(

[neptalactone]

I think I'll try ataraxia another go in the future then. Thank you for all the respond. Sorry if i'm such a bother guys

[ghost]

Don't worry neptalactone! You're just learning like all of us! Thank you for trying it out!

[ghost]

WIll try in a few, since i got this same laptop.

[ghost]

I think I'll try ataraxia another go in the future then. Thank you for all the respond. Sorry if i'm such a bother guys

Try using this to bootstrap Ataraxia and follow the install guide past the network part: https://www.system-rescue.org/Download/

[ghost]

@neptalactone try to boot from recent (28 march) iso and add "noacpi" in cmdline

Get's stuck at here:

[neptalactone]

@neptalactone try new iso

Whoa i just realized this issue has been reopen. Thanks for all the hardwork! I'll try it this weekend. I've been busy with work lately. Once again. Thank you very much

[ghost]

@neptalactone try new iso

Whoa i just realized this issue has been reopen. Thanks for all the hardwork! I'll try it this weekend. I've been busy with work lately. Once again. Thank you very much

Does new ISO work?

[neptalactone]

@neptalactone try new iso

Whoa i just realized this issue has been reopen. Thanks for all the hardwork! I'll try it this weekend. I've been busy with work lately. Once again. Thank you very much

Does new ISO work?

Sorry i forgot to reply. Yes it is working now. Great! Thanks very much. Is there no grub template? My laptop kinda weird, everytime i try to make efi stub entry with efibootmgr, when i restart, the entry just gone. But i still manage to boot using refind

[ghost]

@neptalactone try new iso

Whoa i just realized this issue has been reopen. Thanks for all the hardwork! I'll try it this weekend. I've been busy with work lately. Once again. Thank you very much

Does new ISO work?

Sorry i forgot to reply. Yes it is working now. Great! Thanks very much. Is there no grub template? My laptop kinda weird, everytime i try to make efi stub entry with efibootmgr, when i restart, the entry just gone. But i still manage to boot using refind

I actually seem to have the same laptop, and had the same thing happen. I hope to actually port refind to Ataraxia Linux in the future. I'd stick to using refind for Ataraxia with ur config. Just make sure you created a "refind_linux.conf" with all of the stuff u want! And Grub is only on ISOS. Closing.