e1000e-dkms-debian
QEMU
e1000e-dkms-debian | QEMU | |
---|---|---|
3 | 190 | |
68 | 9,313 | |
- | 1.3% | |
0.0 | 10.0 | |
almost 2 years ago | 1 day ago | |
C | C | |
GNU General Public License v3.0 only | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
e1000e-dkms-debian
-
PXE provisioning issues with new hardware that requires specific drivers!
Hello, Our hardware vendor stopped selling the previous models of our standard desktops and laptops and possess sent the newest models in our latest purchase. Unfortunately, when installing Ubuntu on these machines the NICs are not recognized by the OS and need manual intervention to be updated, which I was able to get going by downloading the appropriate e1000e driver onto a USB and installing from that. Our standard workflow was provisioning the system with Foreman, and configuring it with ansible after the OS was installed. The manual steps now required between these steps have caused delays in setting up new equipment. Getting this hardware to allow PXE in the first place was a pain, I had to take the initrd.gz that foreman provides for the PXE environment, unpack it and replace the e1000e network driver with the very latest one to even allow the PXE process to start. But because the archive foreman uses for Ubuntu is the standard Canonical hosted Ubuntu archive, the OS is again missing that version of the driver and it needs to get updated again. Does anyone have recommendations on how to get around this? * I tried using HWE but it seems to not include this very latest version of e1000e so had no luck there * Could this process be included in the preseed file/provisioning template to handle the driver? * Our foreman install has Katello, but I have been having a hell of a time getting deb repos hosted. Even if that gets set up properly, it seems pretty hacky again to insert a kernel with the correct driver version. (GPG issues? idk) * Foreman/Katello docs are lackluster and havent seen anything related to this kind of problem * FYI the desktop is a Dell Precision Tower 3650 and installing Ubuntu 18.04 I was hired as a Junior Sys Admin 2 years and now find myself as the sole IT in the company, this has been driving me nuts as my previous provisioning workflow was pretty solid but dont have anyone internal to turn to for advice. Would really appreciate any thoughts or ideas you all have or any resources you know of I can look into. Thanks! EDIT: Thanks for the replies everyone, I ended up getting this resolved by using DKMS. https://github.com/koljah-de/e1000e-dkms-debian was a good starting point, I built a deb from that and placed it on my tftp server. Then in Foreman's finish template I included the following lines: tftp -m binary tftp.example.com -c get e1000e-dkms.deb dpkg -i e1000e-dkms.deb That worked for me, after the installation process the NIC was usable. Plus this has the added benefit of not needing to tweak the drivers after upgrading the kernel at a later date.
-
7-zip 22.00 – APFS, Posix TAR, high precision timestamps
Intel out-of-tree NIC drivers too; https://sourceforge.net/projects/e1000/ - But there are not many!
-
Intel NIC drivers confusion
[1] qemu/hw/net/e1000.c [2] Devices supported by Linux's e1000 [3] e1000 from Intel
QEMU
-
QEMU Version 9.0.0 Released
My most-wanted QEMU feature: https://github.com/qemu/qemu/commit/a2260983c6553
Using `gic-version=3` on macOS you can now use more than 8 cores on ARM chips.
-
Autoconf makes me think we stopped evolving too soon
A better solution is just to write a plain ass shell script that tests if various C snippets compile.
https://github.com/oilshell/oil/blob/master/configure
https://github.com/oilshell/oil/blob/master/build/detect-pwe...
Not an unholy mix of m4, shell, and C, all in the same file.
---
These are the same style as a the configure scripts that Fabrice Bellard wrote for tcc and QEMU.
They are plain ass shell scripts, because he actually understands the code he writes.
https://github.com/qemu/qemu/blob/master/configure
https://github.com/TinyCC/tinycc/blob/mob/configure
OCaml’s configure script is also “normal”.
You don’t have to copy and paste thousands of lines of GNU stuff that you don’t understand.
(copy of lobste.rs comment)
-
WASM Instructions
Related:
A fast Pascal (Delphi) WebAssembly interpreter:
https://github.com/marat1961/wasm
WASM-4:
https://github.com/aduros/wasm4
Curated list of awesome things regarding WebAssembly (wasm) ecosystem:
https://github.com/mbasso/awesome-wasm
Also, it would be nice if there was a WASM (soft) CPU for QEMU, which (if it existed!) would go here:
https://github.com/qemu/qemu/tree/master/target
-
Revng translates (i386, x86-64, MIPS, ARM, AArch64, s390x) binaries to LLVM IR
> architectural registers are always updated
In tiny code, the guest registers (global TCG variables) are stored in the host's registers until you either call an helper which can access the CPU state or you return (`git grep la_global_sync`). This is the reason why QEMU is not so terribly slow.
But after a check, this also happens when you access the guest memory address space! https://github.com/qemu/qemu/blob/master/include/tcg/tcg-opc... (TCG_OPF_SIDE_EFFECTS is what matters)
But still, in the end, it's the same problem. What QEMU does, can be done in LLVM too. You could probably be more efficient in LLVM by using the exception handling mechanism (invoke and friends) to only serialize back to memory when there's an actual exception, at the cost of higher register pressure. More or less what we do here: https://rev.ng/downloads/bar-2019-paper.pdf
-
State of x86-64 emulation of non-MacOS binaries
Um, in case you don't know, UTM (based on QEMU) is out for quite a while.
-
Multipass: Ubuntu Virtual Machines Made Easy
Some of these tools include Oracle VM VirtualBox (that I've used since before the acquisition of Sun Microsystems by Oracle), VMWare Workstation Player, and QEMU, but last year, I found out about Multipass.
-
Libsodium: A modern, portable, easy to use crypto library
For C/C++ projects that use meson as the build system, there is an excellent way to manage dependencies:
https://mesonbuild.com/Wrapdb-projects.html
https://mesonbuild.com/Wrap-dependency-system-manual.html
meson will download and build the libraries automatically and give you a variable which you pass as a regular dependency into the built target:
https://github.com/qemu/qemu/tree/005ad32358f12fe9313a4a0191...
https://github.com/harfbuzz/harfbuzz/tree/main/subprojects
https://github.com/harfbuzz/harfbuzz/blob/37457412b3212463c5...
Or, if you're using proper operating systems, they're managed by the usual package manager, just like everything else.
-
Top 6 Virtual Machine Software in 2023
For all the users of the Linux platform, QEMU is the VM that you should go for. This software comes without any price tag and works as an emulator of various machines with utmost ease and completion; the software uses dynamic translations to emulate hardware peripherals and enhances its overall performance. If you are using QEMU as a virtualizer, then it will function exactly like the host system (provided you have the right set of hardware).
- Show HN: I'm 17 and wrote this guide on how CPUs run programs
-
UTM for Developers
In this tutorial, we set up macOS and Windows virtual machines on UTM, a macOS application that provides a GUI wrapper for QEMU, a powerful open-source emulator and virtualizer. UTM allows you to easily manage and run virtual machines without memorizing complex commands. It also has special handling for macOS, making it simpler to install compared to other virtual machine software.
What are some alternatives?
ntfs3 - ntfs3 Linux kernel module by Paragon Software
UTM - Virtual machines for iOS and macOS
asus-fan - Kernel module to get/set (both) fan speed(s) on ASUS Zenbooks
TermuxArch - Experience the pleasure of the Linux command prompt in Android, Chromebook, Fire OS and Windows on smartphone, smartTV, tablet and wearable https://termuxarch.github.io/TermuxArch/
realtek-r8125-dkms - A DKMS package for easy use of Realtek r8125 driver, which supports 2.5 GbE.
Unicorn Engine - Unicorn CPU emulator framework (ARM, AArch64, M68K, Mips, Sparc, PowerPC, RiscV, S390x, TriCore, X86)
rapiddisk - An Advanced Linux RAM Drive and Caching kernel modules. Dynamically allocate RAM as block devices. Use them as stand alone drives or even map them as caching nodes to slower local disk drives. Access those volumes locally or export them across an NVMe Target network. Manage it all from a web API.
Vagrant - Vagrant is a tool for building and distributing development environments.
daemon - turns other processes into daemons
xemu - Original Xbox Emulator for Windows, macOS, and Linux (Active Development)
bcm5719-fw - BCM5719 firmware reimplementation
em-dosbox - An Emscripten port of DOSBox