If anyone knows how the official images are compiled please let me know.
On Tue, Apr 7, 2020 at 5:23 PM Sreyan Chakravarty <sreyan32@xxxxxxxxx> wrote:
I am unable to boot the custom ISO I have created.I have just created a Custom ISO from the Fedora Live ISO using the following command:genisoimage -U -r -v -T -J -joliet-long -V "Fedora-WS-Live-31-1-9" -volset "Fedora-WS-Live-31-1-9" -A "CDLABEL=Fedora-WS-Live-31-1-9" -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -eltorito-alt-boot -e images/efiboot.img -no-emul-boot -o ../Fedora_Custom.iso .But I can't for the life of me figure out why I can't get the Live ISO to boot. Its stuck at the bootmenu.This is the directory structure for my custom ISO:[sreyan@localhost Fedora_ISO]$ tree .
.
├── anaconda-ks.cfg
├── EFI
│ └── BOOT
│ ├── BOOT.conf
│ ├── BOOTIA32.EFI
│ ├── BOOTX64.EFI
│ ├── fonts
│ │ └── unicode.pf2
│ ├── grub.cfg
│ ├── grubia32.efi
│ ├── grubx64.efi
│ ├── mmia32.efi
│ └── mmx64.efi
├── images
│ ├── efiboot.img
│ ├── macboot.img
│ └── pxeboot
│ ├── initrd.img
│ └── vmlinuz
├── isolinux
│ ├── boot.cat
│ ├── boot.msg
│ ├── grub.conf
│ ├── initrd.img
│ ├── isolinux.bin
│ ├── isolinux.cfg
│ ├── ldlinux.c32
│ ├── libcom32.c32
│ ├── libutil.c32
│ ├── memtest
│ ├── splash.png
│ ├── vesamenu.c32
│ └── vmlinuz
└── LiveOS
└── squashfs.img
7 directories, 28 filesAnd this is for the original:[sreyan@localhost Fedora-WS-Live-31-1-9]$ tree .--
.
├── EFI
│ └── BOOT
│ ├── BOOT.conf
│ ├── BOOTIA32.EFI
│ ├── BOOTX64.EFI
│ ├── fonts
│ │ └── unicode.pf2
│ ├── grub.cfg
│ ├── grubia32.efi
│ ├── grubx64.efi
│ ├── mmia32.efi
│ └── mmx64.efi
├── images
│ ├── efiboot.img
│ ├── macboot.img
│ └── pxeboot
│ ├── initrd.img
│ └── vmlinuz
├── isolinux
│ ├── boot.cat
│ ├── boot.msg
│ ├── grub.conf
│ ├── initrd.img
│ ├── isolinux.bin
│ ├── isolinux.cfg
│ ├── ldlinux.c32
│ ├── libcom32.c32
│ ├── libutil.c32
│ ├── memtest
│ ├── splash.png
│ ├── vesamenu.c32
│ └── vmlinuz
└── LiveOS
└── squashfs.img
7 directories, 27 filesAs you can see there is no difference except for the Kickstart file which I am not even using in isolinux.cfgThis is the output of isolinux.cfg:default vesamenu.c32
timeout 600
display boot.msg
# Clear the screen when exiting the menu, instead of leaving the menu displayed.
# For vesamenu, this means the graphical background is still displayed without
# the menu itself for as long as the screen remains in graphics mode.
menu clear
menu background splash.png
menu title Fedora-Workstation-Live 31
menu vshift 8
menu rows 18
menu margin 8
#menu hidden
menu helpmsgrow 15
menu tabmsgrow 13
# Border Area
menu color border * #00000000 #00000000 none
# Selected item
menu color sel 0 #ffffffff #00000000 none
# Title bar
menu color title 0 #ff7ba3d0 #00000000 none
# Press [Tab] message
menu color tabmsg 0 #ff3a6496 #00000000 none
# Unselected menu item
menu color unsel 0 #84b8ffff #00000000 none
# Selected hotkey
menu color hotsel 0 #84b8ffff #00000000 none
# Unselected hotkey
menu color hotkey 0 #ffffffff #00000000 none
# Help text
menu color help 0 #ffffffff #00000000 none
# A scrollbar of some type? Not sure.
menu color scrollbar 0 #ffffffff #ff355594 none
# Timeout msg
menu color timeout 0 #ffffffff #00000000 none
menu color timeout_msg 0 #ffffffff #00000000 none
# Command prompt text
menu color cmdmark 0 #84b8ffff #00000000 none
menu color cmdline 0 #ffffffff #00000000 none
# Do not display the actual menu unless the user presses a key. All that is displayed is a timeout message.
menu tabmsg Press Tab for full configuration options on menu items.
menu separator # insert an empty line
menu separator # insert an empty line
label linux
menu label ^Start Fedora-Workstation-Live 31
kernel vmlinuz
append initrd=initrd.img root=live:CDLABEL=Fedora-WS-Live-31-1-9 rd.live.image quiet
label check
menu label Test this ^media & start Fedora-Workstation-Live 31
menu default
kernel vmlinuz
append initrd=initrd.img root=live:CDLABEL=Fedora-WS-Live-31-1-9 rd.live.image rd.live.check quiet
menu separator # insert an empty line
# utilities submenu
menu begin ^Troubleshooting
menu title Troubleshooting
label vesa
menu indent count 5
menu label Start Fedora-Workstation-Live 31 in ^basic graphics mode
text help
Try this option out if you're having trouble starting
Fedora-Workstation-Live 31.
endtext
kernel vmlinuz
append initrd=initrd.img root=live:CDLABEL=Fedora-WS-Live-31-1-9 rd.live.image nomodeset quiet
label memtest
menu label Run a ^memory test
text help
If your system is having issues, a problem with your
system's memory may be the cause. Use this utility to
see if the memory is working correctly.
endtext
kernel memtest
menu separator # insert an empty line
label local
menu label Boot from ^local drive
localboot 0xffff
menu separator # insert an empty line
menu separator # insert an empty line
label returntomain
menu label Return to ^main menu
menu exit
menu endThis is the same as the original ISO, there is no difference.If there is no difference why am I unable to boot into Fedora.These are the command line params from isolinux in both mine and original ISO.Original: https://imgur.com/a/6sfmiJrFor me I am unable to progress any further than the boot screen.Where am I going wrong ?Regards,Sreyan Chakravarty
Regards,
Sreyan Chakravarty
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
