After successfully updating and re-configuring the Odroid C2 to use Fedora uefi/grub2 to boot, I decided to try to do the same to the even-older Hikey SOC. This already booted using fastboot with an older version of grub, with manual configuration, but I wanted to use the standard (Fedora) boot process. I had read that there was … 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 →
When the Odroid C2 was first released way back in 2016, I spent ages trying to get it to function correctly with a mainstream kernel, and tested innumerable development versions of U-Boot, including functionality that was working OK at that time, but that – for some reason – then failed to be included in the ‘mainstream’ U-Boot.. … Continue reading →
Tested the newly released Kernel 5.3-rc1 (brief details here: http://lkml.iu.edu/hypermail/linux/kernel/1907.2/04769.html ) The latest NVIDIA (430.34) compiles and runs OK, and (patched) VMware 15.1.0 vmnet compiles OK, but vmmon fails: ……… CC [M] /tmp/modconfig-Kk5UU0/vmmon-only/common/cpuid.o /tmp/modconfig-Kk5UU0/vmmon-only/linux/hostif.c: In function ‘HostIF_SetFastClockRate’: /tmp/modconfig-Kk5UU0/vmmon-only/linux/hostif.c:3406:10: error: too many arguments to function ‘force_sig’ 3406 | force_sig(SIGKILL, linuxState.fastClockThread); | ^~~~~~~~~ In file included from ./include/linux/taskstats_kern.h:12, from … Continue reading →
I had previously set up several dual-boot Fedora Linux/Win7 systems, but now had the challenge of doing the same for MacOS as well.. This is absolutely not the place for any discussion on the ramifications of the ‘Hackintosh’ movement, but it will suffice to use that terrible phrase ‘Google is your friend..’.. The Clover/MacOS instance was on … Continue reading →
After some serious problems on my test system with plasma-workspace 5.15.x and nouveau (to be described in a separate article..) I had to contemplate moving back to the proprietary nvidia driver, but found – of course – that older cards were not supported by the ‘latest’ drivers. I did find that at least one of the older … Continue reading →
NVIDIA have released driver 418.56, and details are here: https://devtalk.nvidia.com/default/topic/1048767/announcements-and-news/-linux-solaris-and-freebsd-driver-418-56-long-lived-branch-release-/ This version has almost the same problems with Kernel 5.1-rc1 as 418.43, but the fix mentioned in the previous article still applies, after the fixes for ‘list_is_first‘ in ~/kernel/common/inc/nv-list-helpers.h and ~/kernel/nvidia-uvm/uvm8_range_tree.c have been removed, as these are no longer required, and would now cause the compile to … Continue reading →
I have done some more investigation into the NVIDIA compile failures with Kernel 5.1-rc1, and now have a – rather inelegant – solution. I found clues to some of the errors in a post relating to nouveau: https://lkml.org/lkml/2019/2/20/50 and the rest were due to content removed from /include/drm/drm_crtc_helper.h in Kernel 5.1-rc1: https://elixir.bootlin.com/linux/v5.1-rc1/source/include/drm/drm_crtc_helper.h compared to: https://elixir.bootlin.com/linux/v5.0.3/source/include/drm/drm_crtc_helper.h. I also … Continue reading →
Setting up an old HP8000 desktop small-form-factor system as a crash-and-burn test system, with dual-boot Fedora 29 and Windows 7, on separate drives. First slight gotcha with the Fedora install: The installation utility shows the two disks, the first of which has Windows 7 (sda) and the second – additional – was for the Fedora Linux install … Continue reading →
I created a combo runtime patch for NVIDIA 410.73 on Kernel 4.20-rc1, by combining the changes identified in my previous article ( see http://rglinuxtech.com/?p=2426 ) with the pm patch (see http://rglinuxtech.com/?p=2421 ). The result ran – eventually – after blanking/refreshing the display, with garbage characters at top/bottom, so all was obviously not OK.. ……………………… [ 121.826292] [drm] … Continue reading →