Hello:

Yes, that's what (in a way) the post I referred to implies.
But the problem I (and others had) with Pale Moon had to do not with Pale Moon but with the (newer) default acceleration method setting ie: sna used on the older Intel chipsets, like the ones my Asus 1000HE has. Going back to uxa apparently solved the issue.

Actually, I had no idea about all this.
I came across this setting because of the issue I had with Pale Moon.

I guess I can try it and see what happens.

And what do I do with /etc/X11/xorg.conf.d/20-intel.conf?
I guess there cannot be two acceleration settings.
Or are they unrelated?

Thanks for your input.

A.

Hello:

Will do.
Thank you.

A.

Hello:

The display appears to be working fine, so that would be something to look at later on.
Maybe it has to do with the 1000HE's vga port?

In any case, the issue in this post was mainly related to eeepc_wmi.

I have searched the web and traced the problem to a bug in linux-source-4.9 kernel due to a regression apparently caused by this patch:

https://git.kernel.org/pub/scm/linux/ke … ?h=v4.9.51

It seems that it is the same as this, but [sort of] explained:

https://git.amelchem.com/amel/linux/com … 573777c6ac

Edit

Apparently the ASUS010 device is the EEEPC Hotkey set.

See

https://github.com/torvalds/linux/blob/ … c-laptop.c

/Edit

Here's the original bug report from 20170920:

https://bugs.debian.org/cgi-bin/bugrepo … bug=876303

Here's what apparently needs to be done, no idea though.

And this is the last post in the bug report darted 20180301:

https://bugs.debian.org/cgi-bin/bugrepo … =876303#28

I've written to the author of the last post and apparently the bug is still there.

I have to get some live 32bit distro with a 5.0 kernel to see if it has been fixed but I am not holding my breath.

Looks like a bug originated in what was probably (?) a hastily applied patch.
It would be nice if the same haste would be applied to rolling it back. No?

Any ideas welcome (blacklisting something, etc.).

Cheers,

A.

Hello:

Much more.
And about the other hardware too.
Here you go ...

groucho@devuan:~$ lspci -knn
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GSE Express Memory Controller Hub [8086:27ac] (rev 03)
	Subsystem: ASUSTeK Computer Inc. Mobile 945GSE Express Memory Controller Hub [1043:8340]

--->
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03)
	Subsystem: ASUSTeK Computer Inc. Mobile 945GSE Express Integrated Graphics Controller [1043:8340]
	Kernel driver in use: i915
	Kernel modules: i915
00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03)
	Subsystem: ASUSTeK Computer Inc. Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [1043:8340]
<---

00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High Definition Audio Controller [8086:27d8] (rev 02)
	Subsystem: ASUSTeK Computer Inc. NM10/ICH7 Family High Definition Audio Controller [1043:834a]
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 1 [8086:27d0] (rev 02)
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:1c.1 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 2 [8086:27d2] (rev 02)
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:1c.3 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 4 [8086:27d6] (rev 02)
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:1d.0 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 [8086:27c8] (rev 02)
	Subsystem: ASUSTeK Computer Inc. NM10/ICH7 Family USB UHCI Controller [1043:830f]
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci_hcd
00:1d.1 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 [8086:27c9] (rev 02)
	Subsystem: ASUSTeK Computer Inc. NM10/ICH7 Family USB UHCI Controller [1043:830f]
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci_hcd
00:1d.2 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 [8086:27ca] (rev 02)
	Subsystem: ASUSTeK Computer Inc. NM10/ICH7 Family USB UHCI Controller [1043:830f]
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci_hcd
00:1d.3 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 [8086:27cb] (rev 02)
	Subsystem: ASUSTeK Computer Inc. NM10/ICH7 Family USB UHCI Controller [1043:830f]
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci_hcd
00:1d.7 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller [8086:27cc] (rev 02)
	Subsystem: ASUSTeK Computer Inc. NM10/ICH7 Family USB2 EHCI Controller [1043:830f]
	Kernel driver in use: ehci-pci
	Kernel modules: ehci_pci
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev e2)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge [8086:27b9] (rev 02)
	Subsystem: ASUSTeK Computer Inc. 82801GBM (ICH7-M) LPC Interface Bridge [1043:830f]
	Kernel driver in use: lpc_ich
	Kernel modules: intel_rng, lpc_ich, leds_ss4200
00:1f.1 IDE interface [0101]: Intel Corporation 82801G (ICH7 Family) IDE Controller [8086:27df] (rev 02)
	Subsystem: ASUSTeK Computer Inc. 82801G (ICH7 Family) IDE Controller [1043:830f]
	Kernel driver in use: ata_piix
	Kernel modules: ata_piix, ata_generic
00:1f.2 IDE interface [0101]: Intel Corporation 82801GBM/GHM (ICH7-M Family) SATA Controller [IDE mode] [8086:27c4] (rev 02)
	Subsystem: ASUSTeK Computer Inc. 82801GBM/GHM (ICH7-M Family) SATA Controller [IDE mode] [1043:830f]
	Kernel driver in use: ata_piix
	Kernel modules: ata_piix, ata_generic
01:00.0 Network controller [0280]: Ralink corp. RT2790 Wireless 802.11n 1T/2R PCIe [1814:0781]
	Subsystem: AzureWave RT2790 Wireless 802.11n 1T/2R PCIe [1a3b:1059]
	Kernel driver in use: rt2800pci
	Kernel modules: rt2800pci
03:00.0 Ethernet controller [0200]: Qualcomm Atheros AR8121/AR8113/AR8114 Gigabit or Fast Ethernet [1969:1026] (rev b0)
	Subsystem: ASUSTeK Computer Inc. AR8121/AR8113/AR8114 Gigabit or Fast Ethernet [1043:8324]
	Kernel driver in use: ATL1E
	Kernel modules: atl1e
groucho@devuan:~$

There's more than one way to skin a cat. =-)
I still have to polish my command line.
Thanks for the tip.

Cheers,

A.

Hello:

We may be drifting off topic here ...

But jo make my position clear: I'm not nocking Linux or Devuan, quite the contrary.

It is just that (IMO) what XFCE does by forcing the installation of (unneeded) Orage and on top of that, making it impossible to uninstall without also uninstalling XFCE altogether is contrary to the basic philosophy behind Linux:

------------------- > Do one thing and do it well. 

There are other programs/maintainers that do this same sort of thing.
Must have all learnt how to do it at the Redmond Academy.  8-D!!!

Well ...
It's the same type of different opinion than generated the need for Devuan.
systemd is also a different opinion on how to do things and also contrary to the basic philosophy behind Linux. 

Just what I am doing: openbox and tint2 work quite well for the time being.

It is of the utmost importance, not only to both of us but for how Linux will continue to develop.

Thanks a lot for your input.

Best,

A.

Hello:

I managed to fix the problem but have no idea why it happened or how to avoid it happening.

To fix it, with the USB installation in place, I booted with a Devuan ASCII 2.0.0_i386_DVD-1 installer DVD, went to Rescue Mode and reinstalled GRUB to the USB stick (/dev/sdb).

And that was it.

The drive booted into GRUB and upon logging in I installed XFCE4 which, after a reboot, started without any issues (for the time being).

rant
It's a pity that installing a desktop drags so much stuff in with it ...
eg: I did not ask for an Orage Calendar or Orage Globaltime.
But there it is.

And uninstalling it also uninstalls XFCE4 (and only XFCE4).
Reminds me of some similar MS practises we have all suffered at some time or another ...
/rant

But the problem is fixed.

Thanks for your input.

A.

Hello:

It refused to do it.
ie: failed at that point in the installation.

Retried a number of times but the only way I was able to continue and write GRUB to the USB stick was to uncheck that.
But it will not boot.

I just get a  j (lowercase) followed by a blinking underscore.

ie:  j_ 

I'm having a very hard time with this installation, no idea what's going on.
The .iso file I downloaded checked out perfectly well and the installer verified the "CD-ROM" so that's not it.

This is what I have:

groucho@devuan:~$ sudo fdisk -l /dev/sdf
[sudo] password for groucho: 
Disk /dev/sdf: 7.2 GiB, 7757398016 bytes, 15151168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x000312cd

Device     Boot    Start      End Sectors  Size Id Type
/dev/sdf1  *        4096  9220095 9216000  4.4G 83 Linux
/dev/sdf2        9222142 15151103 5928962  2.8G  5 Extended
/dev/sdf5        9222144 12294143 3072000  1.5G 82 Linux swap / Solaris
/dev/sdf6       12296192 15151103 2854912  1.4G 83 Linux
groucho@devuan:~$ 

Any ideas?

Thanks in advance.

A.

Hello:

OK, one down.  =-)

I thought as much once I realised I could split / from the rest of the installation and boot my main rig from a SSD. 
Have not done it yet.

I really like Linux's ability to put things in their own place.
I recall that in another life/another OS, I put both the /swap and a /programs directory on separate partitions.
I did not trust the MS 'program files' arrangement.

Not to much use besides keeping things tidy as a lot of stuff still ended up in /program files.   
Eventually I put the swap file in the same partition as /programs as all that took a toll speedwise.

Of course, thanks for the heads up.

OK.

What worries me a bit is the actual process, eg:

1. boot Devuan ASCII (to ram?) from image dd'd to a USB stick.
2. install to the second partition (ext4) on HDD, where the first partition (NTFS) holds the XP installation.
3. make sure /, boot record and GRUB are installed to the SC Card in the slot.

Q1.: How do I make that last part of the process failsafe?

Q2.: Am I correct in assuming that installing ASCII in this manner will allow for updating?
It is something I have found booting from an *.iso with persistance will not and mess it all up.

Thanks for your input.

A.