| Summary: | Out of box bitbake for genericx86 and genericx86_64 FAILS on Toshiba-intel but works on Dell machines | ||
|---|---|---|---|
| Product: | [Runtime] General Runtime | Reporter: | BobDog555 <rr.mausa> |
| Component: | General Runtime | Assignee: | Darren Hart <dvhart> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | Undecided | CC: | rr.mausa, sgw |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | x86 | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
Hi Could you please provide some more details, it seems that an invalid argument is being passed, can you provide a complete kernel boot command from what ever bootload you are using. (In reply to comment #1) > Hi Could you please provide some more details, it seems that an invalid > argument is being passed, can you provide a complete kernel boot command > from what ever bootload you are using. Hi! Thanks for the help! I used whatever default kernel boot command that yocto with that recipe (core-image-full-cmdline) put into the ISO image. I'm a newbie at this so you will have to tell me how to dig the kernel boot command out, or I could put the iso image on a shared drive somewhere that you could look, presumably seeing the problem more quickly than I could. But I'll do as you instruct. We have to fix it. Thanks again..... If it's the exact same image, it's possible your Toshiba firmware doesn't like the format of the ISO image. The README.hardware describes various method for creating boot media. PC BIOS firmware can be *very* picky here and can complain about the size of the file, the exact position of the file in the filesystem/disk, etc. There is *a lot* of variation in boot support. 1) Does this Toshiba machine successfully boot ISO images from common Linux distributions, which ones, which versions. 2) Does this exact boot media work in other systems? 3. Are you required to use an ISO image? Are you using it on an optical disk? 4) Check your boot arguments in the Toshiba firmware, there may be some settings to try. If you don't have to use ISO, I suggest you try the .hddimg, and failing that, see the README.hardware (in the poky repo) for information on creating a zip-format boot disk, which some PC BIOS firmware are happier with. 2/23/14 UPDATE : Build/Run on Toshiba Tecra laptops needs special BIOS setting.
Yocto's building of a working environment using the recipe :
bitbake core-image-full-cmdline
with local.conf set to genericx86_64 will now boot successfully on our Toshiba Tecra 7xx machines.
The Toshiba first must have its BIOS System Settings BOOT value set to enable UEFI (not CSM). We also have Secure Boot set to DISABLED.
The Yocto build process produces an image labeled "core-image-full-cmdline-<etc>.hddimg" among others such as an ISO file.
Putting the hddimg image onto a USB thumb drive:
1) You should first unmount the volume on the USB /dev/sdb1 (or whatever your device configuration names the USB boot thumb drive you've inserted & mounted).
2) Then using the linux command:
sudo dd if=core-image-full-cmdline<etc>.hddimg of=/dev/sdb
will create a bootable USB stick.
SIDE NOTE: the created image seems to boot on our Dell Latitude machines without setting the boot option to enable UEFI: "traditional boot" seems to work OK on those. Hmmm.
.
Looks like we should probably add something to the README.hardware that suggests if you run into a general problem like the below that BIOS setting be checked and to enable the UEFI setting if it exists. |
bitbake core-image-full-cmdline to genericx86[or x86_64] creates an ISO which is burned to CD. This CD boots on a Dell laptop (Intel board) but fails on a Toshiba Tecra laptop (also an Intel board) with these messages: Loading /vmlinuz ... ok Loading /initrd ... ok /booting kernel failed: invalid argument ...and these messages continue to loop forever on the Toshiba. Perfect boot, login root, etc on my Dell, but the Toshiba is what we mostly use around here, so I need an idea for a fix.