need help porting - BzImage too large
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 1.6k
- Forks
- 211
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 6
Description
I am trying to port heads to the Google kuldax chromebox. I'm using Mr.chromebox coreboot.config file as a template, but running to problems. I kept most original settings intact but changed the payload from EDK to Linux elf. However, I get the error when building coreboot:
E: Could not add [../kuldax/bzImage, 9071469 bytes (8858 KB)@0x0]; too big?
E: Failed to add '../kuldax/bzImage' into ROM image.
E: Failed while operating on 'COREBOOT' region!
E: The image will be left unmodified.
make[1]: *** [Makefile.mk:1211: kuldax/coreboot.pre] Error 1
I made a few changes to the coreboot.config file to take out unused drivers such as wifi, soundcard, etc to save some space but I keep getting the same error. Doesn't make a lot of sense because the BIOS chip is 32Mb so there should be plenty of extra space. I am certain the problem is with the coreboot.config file because when I swap it out with another coreboot.config from a different board but leave all other config files the same, it builds fine.
I am including the coreboot.config file I am using for your review.
[coreboot.config.txt](https://github.com/user-attachments/files/26798869/coreboot.config.txt)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the attached coreboot.config with the working board configuration, then inspect Makefile.mk:1211 and the kuldax/coreboot.pre build step. Check how ../kuldax/bzImage is placed in the COREBOOT region and which configuration settings determine that region's size. Done means the kuldax image builds successfully with the Linux bzImage included.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- build-system, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100