>I suspect you were trying to go too far back in software history while >using current hardware/bios etc.
Well no; I've researched BIOS/UEFI. AFAIK 386, 486 is still valid/compatable. Only I can't run <floppy/dev/fd0 installed mulinux> on my laptops. My background is hardware, and programming a 8bit Uproc in hex. Was that in the 70s ? On Thu, Nov 19, 2020 at 10:51 AM <[email protected]> wrote: > On Mon, 16 Nov 2020, hebisch-at-math.uni.wroc.pl |pop-forum| wrote: > (snip) > > > > There is good chance that there is some configuration parameter to > > enable old behaviour (to run programs like Poplog). Simply, ATM > > we lack info. We do not know exact reason for fault. We do not > > know if this is general 5.8 thing or (more likely) Fedora thing. > > We do not know if this is really kernel change or say configuration > > change that is somewhat tied to the kernel (say buch of configuration > > changes with some dependent of kernel features). > > > > To put it differently, most guesses about software problems are > > wrong. Here there are several factors involved, so chance > > of resolving problem without digging deeper is virtually 0. > > A data point: > > In a virtual machine running Ubuntu 20.04.1 LTS, which comes with kernel > 5.4, Waldek's 64 bit system with the no-pie patch builds and both pop11 > and xved start up normally. > > When I upgrade the kernel to 5.8, build_pop0 immediately gives an error > <<<<<<< Access Violation: PC = 00000000007AB060, Addr = 00000000007AB060, > Code = 2 >>>>>>> > but carries on and produces a corepop. The corepop starts up with the > same error, repeated several times. It then works at least to the > extent of doing simple arithmetic, but trying to define and run a > factorial function gives the access violation. > > So the problem under kernel 5.8 is not exclusively a Fedora one. It is > at least a problem with something that Fedora and Ubuntu have in common. > Selinux is not installed in the virtual machine. > > Steve > > > >
