Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • U utility
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure 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

Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.

  • firmware
  • utility
  • Issues
  • #11
Closed
Open
Issue created Aug 21, 2023 by rugk me@rugk

Shows no output at all on Fedora (CoreOS/rpm-ostree systems)?

I wanted to run this on Fedora CoreOS, which is an rpm-ostree based system, i.e. based on system images and .deb/.rpm packages are only layered at the top if needed.

STR

What I did was running it I was following your guide here: https://puri.sm/projects/coreboot/ (same instructions as in your Readme IIRC) with some modifications as wget was not layered, so I needed to use curl etc.

What happens

When I run the script on my system it just creates an empty file check_dependencies.txt in the current directory. That is it – there is no output at all, not even an error.

I looked into it and even layered dmidecode for that and it did not help, there was still zero output.

What should happen

IMHO it should at least show an error, and if it is generic enough as "Unfortunately, this system is not supported. Please try from another system.". Or, better, with some more detailed error of what is missing.

Full support would of course be better, but that is already tracked in #5 (closed) and likely way harder than at least some good error messages/UX.

Possible problem

I assume it is stuck somewhere here: https://source.puri.sm/firmware/utility/-/blob/master/coreboot_util.sh#L1383

Or maybe here as it can detect dnf likely – so confusingly there is some dnf support, but may fail to further proceed.

But I am not sure at all.

System

fedora:fedora/x86_64/coreos/stable (index: 0)
                  Version: 38.20230722.3.0 (2023-08-07T18:56:37Z)

More details:

  • https://coreos.github.io/rpm-ostree/
  • source: https://github.com/coreos/rpm-ostree
Edited Aug 21, 2023 by rugk me
Assignee
Assign to
Time tracking