|
|||||
|
So, you find in your kernel logs or elsewhere some error message something like: bnx2: Can’t load firmware file “bnx2/bnx2-mips-09-6.2.1b.fw” That indicates there is a binary blob (or whatever firmware) missing that is needed for that device. The fix is to load up the Gentoo packaged firmware files. Most are in (surprise, surprise 😉 ) . . . → Read More: Gentoo-isms #2 – Can’t load firmware file Many many years ago, in the days before the (Intel) Atom and the (AMD) Geode, and when ARM SoCs were too niche to be known of, that left a few obscure manufacturers producing low (electrical) power x86-compatible systems for, err, low power use… Our group was kindly donated a (VIA) EPIA “C3” mini-ITX motherboard and . . . → Read More: Gentoo: Frightening or Fantastic? How To Fix a “gcc profile is invalid” Scenario: (all as the “root” user, or via “sudo”) You run an update with “emerge” and all goes well. Then for good housekeeping, you run a “depclean”. And then you find that nothing will compile! Typical errors are such as any/all of: configure: error: C compiler cannot . . . → Read More: Gentoo-isms #1 – gcc profile fix Not sure if this is a real bug or just an unexpected feature… For Gentoo at least, the easiest way to boot onto a multi-device btrfs root is to use the “dracut” utility to create an initramfs to do the “btrfs device scan” to find all the disks to get your btrfs raid/jbod up and . . . → Read More: Gentoo Dracut btrfs Quirk Comments and links for upgrading udev on Gentoo to beware of for the newly introduced scheme for naming network interfaces are given in this comment. That follows on from the talk given for a slightly unexpectedly messy udev update! Hope of help… Martin |
|||||
|
Copyright © 2024 Nottingham Linux Users Group - All Rights Reserved Powered by WordPress & Atahualpa |
|||||
Recent Comments