Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • redox redox
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 231
    • Issues 231
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 14
    • Merge requests 14
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • redox-os
  • redoxredox
  • Issues
  • #994
Closed
Open
Created Jul 13, 2017 by Jeremy Soller@jackpot51Owner

grub4dos & isolinux compatibility?

Created by: leeoniya

hi,

i decided to try booting redox_0.3.0.iso from my multi-boot drive. the typical bootable iso entry in menu.lst looks like this: https://gist.github.com/poppen/3161814

title redox_0.3.0.iso
find --set-root /img/redox_0.3.0.iso
map /img/redox_0.3.0.iso (0xff) || map --mem /img/redox_0.3.0.iso (0xff)
map --hook
chainloader (0xff)

redox appears to fail image decompression with "Not enough memory to decompress image". this grab is from QEMU, but i get the same result on my Lenovo T440s.

redox-grub4dos-qemu

thanks!

Assignee
Assign to
Time tracking