Systemrescuecd non pae12/4/2023 ![]() To complete this thread, here's the relevant output from Quick System Info: I've therefore decided to make MX my base distro, since what I've seen on their website is much in line with my own ideas and preferences. OTOH MX seems to have brought together a talented and competent team with a clear vision of what they're about, and perhaps even more importantly they seem to cooperate harmoniously and productively. getting a new distro going is a slow process, and they never quite seemed to know where they were headed. ![]() I've never liked SystemD and tried to support Devuan when they started, but. Perhaps the quickest, cleanest and best presented installation process I've followed. I'd be most grateful for any assistance in resolving this issue as I cannot use my new box until it's fixed. However, I've never used either and am unsure how to incorporate them during the installation process if this can solve the problem. ![]() It may be that the required upgrade is already in the queue, perhaps in "testing" or "unstable". The hardware lister (lshw) in SRCD reports the following:ī) Host Bridge: Atom Processor Z36xxx/Z37xxx Driver: iosf_mbi_pci. ArchBang Linux installs cleanly and runs fine.įrom this I conclude that the hardware is OK, but the Debian and PCLinuxOS hardware discovery utilities have not yet advanced to the hardware I am using. System Rescue CD 5.3.0 (Gentoo based) runs fine, as does the latest SRCD 7.0 (Arch based).Ĥ. PCLinuxOS live disk and install also hang at what appears to be the same point: hardware discovery.ģ. Both hang after reporting "Installed discover (amd64)".ġ. However, 10.1 failed to install, as does the latest 10.6. I've just purchased a second Qotom of the same model (Q190N). Two years ago I purchased a Qotom MiniPC and successfully installed Debian 8.2, subsequently upgraded to 10.1.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |