After more testing, it appears that there is still a problem with the Intel e1000e driver and some – but not all – supported NICs.. I have several ex-HP systems that have Intel NICs, and some have more than one. The HP Z820 has two (different models..): $ lspci |grep Eth 00:19.0 Ethernet controller: Intel Corporation 82579LM … Continue reading →
After updating my main HP Z820 system to Kernel 5.4, I found that the previous Intel e1000e Ethernet problem I had encountered on my test system with Kernel 5.4-rc6 seemed to have reappeared. (see http://rglinuxtech.com/?p=2632 ). But – this time, two of my systems with e1000e drivers were OK, but the third – the HP Z820 – … Continue reading →
Testing Fedora 31 – which is still work-in-progress, of course.. Tried to use # rpmbuild –rebuild to create a missing RPM from a F30 source RPM, and found the following error: ………….. Illegal char ‘)’ (0x29) in: Obsoletes:………. I found a reference to this error in the buglist, but it had been flagged as ‘rawhide’, and closed, … Continue reading →
Solved: After more investigation, reinstalling the Xorg driver fixed the problem.. # dnf reinstall xorg-x11-server-Xorg After successfully patching the NVIDIA 410.73 driver (see previous article), I encountered another problem at runtime, after # startx : ………………………………. [ 145.489] (II) Initializing extension GLX [ 145.489] (II) AIGLX: Screen 0 is not DRI2 capable [ 145.489] (EE) AIGLX: reverting … Continue reading →
I just encountered a problem installing the latest NVIDIA driver 410.73 on my ‘Main’ system, having successfully tested it on my ‘Test’ system: …………………… MODPOST 4 modules WARNING: “nv_pmops_suspend” [/home/rgadsdon/kernel/NVIDIA-Linux-x86_64-410.73/kernel/nvidia.ko] undefined! WARNING: “nv_pmops_resume” [/home/rgadsdon/kernel/NVIDIA-Linux-x86_64-410.73/kernel/nvidia.ko] undefined! WARNING: “nv_pmops_thaw” [/home/rgadsdon/kernel/NVIDIA-Linux-x86_64-410.73/kernel/nvidia.ko] undefined! WARNING: “nv_pmops_poweroff” [/home/rgadsdon/kernel/NVIDIA-Linux-x86_64-410.73/kernel/nvidia.ko] undefined! WARNING: “nv_pmops_restore” [/home/rgadsdon/kernel/NVIDIA-Linux-x86_64-410.73/kernel/nvidia.ko] undefined! WARNING: “nv_pmops_freeze” [/home/rgadsdon/kernel/NVIDIA-Linux-x86_64-410.73/kernel/nvidia.ko] undefined! ………………….. It appears that NVIDIA now … Continue reading →
When doing a # dnf system-upgrade reboot on an ARM64 system you may encounter a stream of GPG errors, followed by reboot, without upgrade. To fix this, simply import the F28 GPG key in advance, as done for Rawhide: # rpm –import /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-28-primary After this, the system-upgrade should proceed correctly.. Robert Gadsdon. July 6, 2018 … Continue reading →
VMware 14.1.2 worked OK with Kernel 4.17, on my Fedora 28 test system, but after updating to 4.18-rc1 the following occurred: Modules (vmmon/vmnet) compiled OK, but – after further testing – appeared to have a runtime problem.. I applied the vmmon patches from Michal Kubeček, at https://github.com/mkubecek/vmware-host-modules/commit/3f2a6c720f68 and this also compiled cleanly. When I ran # vmware-modconfig … Continue reading →
Just updated the Itanium2 system (RX2600/ZX9000 hybrid) to kernel 4.15-rc1, but encountered a problem with the NFSv4 code. Recent changes have exposed problems with ‘older’ compilers, and the system currently has GCC 4.3 (on Fedora 9/IA64): ………………….. CALL scripts/checksyscalls.sh <stdin>:1185:2: warning: #warning syscall perf_event_open not implemented <stdin>:1239:2: warning: #warning syscall seccomp not implemented <stdin>:1317:2: warning: #warning syscall … Continue reading →
After upgrading four Fedora systems (x86_64) from release 26 to 27, using # dnf system-upgrade download –refresh –releasever=27 –allowerasing –nogpgcheck –best -y, two of these worked OK, but two failed – with a sudden reboot, back to F26 – and no (apparent) error displayed, after # dnf system-upgrade reboot had rebooted the system, and the upgrade process … Continue reading →
I had been getting a warning on boot with recent kernels on my Intel Atom-based UP system, and found a workaround.. The error flagged is – apparently – harmless, and is due to systemd not being able to recognise some mmc disk partitions at that stage of the boot process.. …… [ 5.124250] systemd-gpt-auto-generator[416]: Failed to dissect: … Continue reading →