Can't boot my Alienware M18 #689
-
Short story, my laptop exploded and I had to get a new one. My Alienware M18 R2 is not booting ZBM, the screen just doesn't change and then nothing happens. What can I do now to troubleshoot this issue? |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 5 replies
-
Sorry If there's still typos all over the place, I'm not use to this keyboard yet. |
Beta Was this translation helpful? Give feedback.
-
The release images use the old gummiboot EFI stub, which is known to have problems with some hardware. I suggest you:
|
Beta Was this translation helpful? Give feedback.
-
I would rather not mess with rEFInd or systemd (I don't use either and they're big complex systems, especially systemd) Could you build me an image with kernel 6.11? I tried building,
Thanks |
Beta Was this translation helpful? Give feedback.
-
Actually why are there 6 different build scripts? there's image-build, build-init, zbm-builder, generate-zbm, and it's not explained anywhere how they differ. |
Beta Was this translation helpful? Give feedback.
-
Well, but i need to run the releng first, because I can’t find any arguments for setting kernel versions in the main builder.
What’s a convenience wrapper?
How do I pass the build image to generate zbm?
Sent from [Proton Mail](https://proton.me/mail/home) for iOS
…On Tue, Oct 29, 2024 at 00:45, Andrew J. Hesford ***@***.***(mailto:On Tue, Oct 29, 2024 at 00:45, Andrew J. Hesford <<a href=)> wrote:
There aren't six different build scripts.
- You should generally stay ouf of releng/docker. The image-build.sh is a buildah script to prepare a container image, and build-init.sh is the container entrypoint.
- generate-zbm is the utility that actually prepares a ZFSBootMenu image. You use this to build a custom image on the host.
- zbm-builder.sh is a convenience wrapper for invoking the build container, which internally runs generate-zbm in a controlled environment.
—
Reply to this email directly, [view it on GitHub](#689 (reply in thread)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ABNCTC6WSDXDVAWS2K4FOXLZ5ZZ4BAVCNFSM6AAAAABQXSAVGSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMBXG44TOMA).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
You almost certainly do not need a newer kernel version in ZFSBootMenu. If you run mkdir -p zbm-builds
/path/to/zbm-builder.sh -i ghcr.io/zbm-dev/zbm-builder:development -b zbm-builds you should find new default images in |
Beta Was this translation helpful? Give feedback.
-
That’s it! That worked with the newer 6.6 series.
Do you know how to generate locally without relying on the docker hub image?
I would like to do that, if you know how to do it?
Thanks a million!
Sent from [Proton Mail](https://proton.me/mail/home) for iOS
…On Tue, Oct 29, 2024 at 01:14, Andrew J. Hesford ***@***.***(mailto:On Tue, Oct 29, 2024 at 01:14, Andrew J. Hesford <<a href=)> wrote:
You almost certainly do not need a newer kernel version in ZFSBootMenu. If you run
mkdir -p zbm-builds
/path/to/zbm-builder.sh -i ghcr.io/zbm-dev/zbm-builder:development -b zbm-builds
you should find new default images in zbm-builds/build. The EFI executable in that directory will have been built with the newer systemd-boot stub.
—
Reply to this email directly, [view it on GitHub](#689 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ABNCTC2N3ZHN4MCAR4DWMVDZ5Z5KHAVCNFSM6AAAAABQXSAVGSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMBXHAZDKNQ).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
You almost certainly do not need a newer kernel version in ZFSBootMenu. If you run
you should find new default images in
zbm-builds/build
. The EFI executable in that directory will have been built with the newersystemd-boot
stub.