You are not logged in.
- Topics: Active | Unanswered
#1601 Installation » eeepc-acpi-scripts in ASCII » 2019-05-18 11:10:32
- Altoid
- Replies: 3
Hello:
I need to install the eeepc-acpi-scripts package in ASCII but it is not listed by apt:
groucho@devuan:~$ sudo apt-get install eeepc-acpi-scripts
[sudo] password for groucho:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package eeepc-acpi-scripts
groucho@devuan:~$ Notwithstanding, according to https://pkginfo.devuan.org/cgi-bin/d1pk … elease=any it is available for Devuan:
2 results for "eeepc-acpi-scripts" in any (in 19.878343ms)
[ceres] eeepc-acpi-scripts-1.1.13
[jessie] eeepc-acpi-scripts-1.1.12
What would be the correct way of installing this package?
Add one of these two repositories to sources.list?
If so, which would be the appropriate one?
Thanks in advance.
A.
#1602 Re: Desktop and Multimedia » (EE) in Xorg.0.log -> systemd-logind failure » 2019-05-17 12:17:04
Hello:
... features that you clearly do not understand.
Note taken, thanks. =-)
So, am I to understand that the --no-install-recommends flag means that all required dependencies will not necessarily be met when installing a package using it?
I was under the impression that --no-install-recommends did not affect dependencies but only the addiitonal functionality by recommended packages.
... then avoid metapackages.
OK.
I'll keep that in mind.
Thanks for your input.
A.
#1603 Re: Desktop and Multimedia » (EE) in Xorg.0.log -> systemd-logind failure » 2019-05-16 23:59:54
Hello:
See the section on "### Starting X from a console (TTY)"
https://files.devuan.org/devuan_ascii/Release_notes.txt
Thanks for the heads up.
I'll give it a read (again) tonight.
Best,
A.
#1604 Re: Desktop and Multimedia » (EE) in Xorg.0.log -> systemd-logind failure » 2019-05-16 23:58:38
Hello:
... plain startx command should start an xterm if there is no window manager ...
Eventually, after adding some xorg related packages, it started.
But with no keyboard or mouse.
So I gave up and installed Slim which was not the end of it as I also had to install packages that seemed to be missing.
I did that by comparing with the packages I have in my workstation which also runs ASCII.
... think xserver-xorg pulls in all the video, inputs ...
... installing xorg packages with flag --no-install-recommends that might be a hindrance.
So it seems, but not only xorg.
eg: --no-install-recommends in xfce4 will still force orage down your throat while at the same time other basic things do not work properly.
rant
When I uninstall a package (like I did with Slim to have everything go south on me), as a matter of procedure I always do apt-get update + apt-get check before doing apt-get purge + apt-get autoremove (if indicated) and then apt-get check again.
Taking these precautions are basic to me.
That said, I believe the system (apt) when apt-get check returns no errors.
The very same way I believe it when it says that the packages in the list that will be purged when I do apt-get autoremove are really no longer needed.
I also believe it will effectively install every needed dependency/package when I install any package with the --no-install-recommends flag and leave out the recommended and suggested packages I assume I can safely do without.
Why?
Because I expect that the $%&*@ meaning and difference between dependencies and recommends / suggested have been clearly defined wherever they have to be defined.
I expect that to be so because first, I trust the developers/packagers and second, I have no way to run some sort of sanity check to see if everything is OK.
I find it rather worrying that installing a package with the --no-install-recommends flag would end up being a problem.
/rant
The result of all this is that, despite my best efforts and the infinite patience of my fellow forum members (thanks to all), it has proven rather difficult to get a minimal ASCII installation into my 1000HE.
But I have it running quite well at the moment and thanks to installing Slim my boot time has been cut by at least 50%.
Though I really did expect it to be the other way around. =-D!
Best,
A.
#1605 Desktop and Multimedia » (EE) in Xorg.0.log -> systemd-logind failure » 2019-05-15 22:28:57
- Altoid
- Replies: 9
Hello:
I installed xorg (w/apt from the command line) but startx fails.
[ 110.795]
X.Org X Server 1.19.2
Release Date: 2017-03-02
[ 110.795] X Protocol Version 11, Revision 0
[ 110.796] Build Operating System: Linux 4.9.0-8-amd64 i686 Debian
[ 110.796] Current Operating System: Linux devuan 4.9.0-9-686-pae #1 SMP Debian 4.9.168-1+deb9u2 (2019-05-13) i686
[ 110.796] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-9-686-pae root=UUID=d7ba4ecc-07b2-47a8-9f73-93cd00864862 ro ipv6.disable=1 enable_mtrr_cleanup nmi_watchdog=0
[ 110.797] Build Date: 03 November 2018 03:08:43AM
[ 110.797] xorg-server 2:1.19.2-1+deb9u5 (https://www.debian.org/support)
[ 110.797] Current version of pixman: 0.34.0
--- snip ---
[ 110.949] (EE) systemd-logind: failed to get session: The name org.freedesktop.login1 was not provided by any .service files
--- snip ---
Permission denied
[ 111.953] (EE)
Fatal server error:
[ 111.953] (EE) AddScreen/ScreenInit failed for driver 0
[ 111.953] (EE)
[ 111.953] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 111.953] (EE) Please also check the log file at "/home/groucho/.local/share/xorg/Xorg.0.log" for additional information.
[ 111.953] (EE)
[ 111.983] (EE) Server terminated with error (1). Closing log file.I have not installed anything else yet as I want to go step by step to check if anything fails.
Next would be xfce with --no-install-recommends to keep it lean.
Does this happen because there is no manager or is something wrong?
Never done it like this before, shouldn't I get an x screen?
Thanks in advance.
A.
#1606 Re: Desktop and Multimedia » LXDE GDBus.Error woes » 2019-05-15 13:08:18
Hello:
I think input subsystem doesn't start properly. Check X.org logs: Xorg.0.log from /var/log or ~/.local/share/xorg
Yes, I've been looking into that.
The xserver relies on udev for the list of input devices and the log does not list keyboard or trackpad.
So that's a lead.
But there's something else, of a more serious nature, amiss here ...
To post here, I was wanting to put the output of Xorg.0.log (a txt file) on an SD card mounted by me as root in /media/SD and as root was denied access.
I was also denied chown. (!!!)
Something (what?) when/after I uninstalled slim knocked out some essentials. ie: udev whatevers and some permission configs.
We removed lxde from the desktop choices in the ascii installer isos because it wasn't quite right. You'll need to find the right combination of packages to get what you want.
I did not know that and went for it as it is what Knoppix chose in their rescue CDs.
They usually know what they are doing but then each CD is a custom compound of many sources, custom tailored and not really updateable.
ie: have to reinstall (if used 'on-disk') every time and have probably ironed out whatever ails lxde.
It's a dejavu feeling having to reinstall (years of suffering MS) to fix something but at this point I think it is the best thing to do.
It's all down to Linux experience and eventually I will know how to avoid this type of crap and if not, know enough to be able to fix it.
But now I'm reinstalling. =-/
Thanks to all for your input.
A.
#1607 Re: Desktop and Multimedia » LXDE GDBus.Error woes » 2019-05-14 23:17:07
Hello:
I'll try a couple of things and check back.
Famous last words ...
I reinstalled slim and the result was a totally unresponsive keyboard and trackpad.
So I purged slim and went for lxde, with the same result.
Then I purged both lxde and xserver, reinstalled xserver and ...
... got the same result ie: was a totally unresponsive keyboard and trackpad.
So now I've purged lxde and xserver, pondering my next step.
Theoretically speaking, what I now have is a base system with a few added things (like sudo, etc.)
Cheers,
A.
#1608 Re: Desktop and Multimedia » LXDE GDBus.Error woes » 2019-05-14 19:24:44
Hello:
Then run it.
My mistake, it seems it is running.
groucho@devuan:~$ pgrep -a polkit
1685 /usr/lib/policykit-1/polkitd --no-debug
1828 lxpolkit
groucho@devuan:~$ My earlier post suggests how.
This:
... install a graphical polkit authentication agent and (auto)start it.
If you mean slim, xdm and such, that's what I was not wanting to have, which is why I unisntalled lxdm.
Maybe that's where it went south?
So much for modularity ...
With respect to /.xsessionrc, it's not in /:
groucho@devuan:/$ locate xsessionrc
/etc/X11/Xsession.d/40x11-common_xsessionrc
groucho@devuan:/$ 40x11-common_xsessionrc relates to Xsession:
groucho@devuan:/$ cat /etc/X11/Xsession.d/40x11-common_xsessionrc
# This file is sourced by Xsession(5), not executed.
#Source user defined xsessionrc (locales and other environment variables)
if [ -r "$USERXSESSIONRC" ]; then
. "$USERXSESSIONRC"
fi
groucho@devuan:/$ Which in turn I can find elsewhere and gets complicated:
groucho@devuan:/$ locate Xsession
/etc/X11/Xsession
/etc/X11/Xsession.d
/etc/X11/Xsession.d/20vdpau-va-gl
/etc/X11/Xsession.d/20x11-common_process-args
/etc/X11/Xsession.d/30x11-common_xresources
/etc/X11/Xsession.d/35x11-common_xhost-local
/etc/X11/Xsession.d/40x11-common_xsessionrc
/etc/X11/Xsession.d/50x11-common_determine-startup
/etc/X11/Xsession.d/52gtk3-nooverlayscrollbar-nocsd
/etc/X11/Xsession.d/60xdg-user-dirs-update
/etc/X11/Xsession.d/75dbus_dbus-launch
/etc/X11/Xsession.d/90consolekit
/etc/X11/Xsession.d/90gpg-agent
/etc/X11/Xsession.d/90qt-a11y
/etc/X11/Xsession.d/90qt5-opengl
/etc/X11/Xsession.d/90x11-common_ssh-agent
/etc/X11/Xsession.d/95dbus_update-activation-env
/etc/X11/Xsession.d/99x11-common_start
/etc/X11/Xsession.options
/usr/share/man/man5/Xsession.5.gz
/usr/share/man/man5/Xsession.options.5.gz
groucho@devuan:/$ FWIW, my workstation which runs slim and XFCE4 has the same 40x11-common_xsessionrc and no /.xsessionrc.
If polkit and lxpolkit are running maybe it is some DBus issue?
I'll try a couple of things and check back.
Thanks a lot for your input.
A.
#1609 Re: Desktop and Multimedia » LXDE GDBus.Error woes » 2019-05-14 16:58:28
Hello:
The ? means that polkitd isn't attached to a terminal. ps aux gives more ...
OK, here's ps aux:
groucho@devuan:~$ ps aux | grep polkit
root 1709 0.3 0.3 37032 6428 ? Sl 13:49 0:00 /usr/lib/policykit-1/polkitd --no-debug
groucho 1852 0.2 0.8 45036 17144 tty1 Sl 13:50 0:00 lxpolkit
groucho 2052 0.0 0.0 4728 840 pts/0 S+ 13:51 0:00 grep polkit
groucho@devuan:~$ chris@rigel:~/bin$ ps aux | head -3 USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1 0.0 0.0 15812 1628 ? Ss 2018 2:25 init [2] root 2 0.0 0.0 0 0 ? S 2018 0:05 [kthreadd]The second command is just to show the column headings.
The first column shows polkit runs as root which is why you need ps ax to show it.
I see ...
(have to read up on this)
Thanks for your input.
A.
#1610 Re: Desktop and Multimedia » LXDE GDBus.Error woes » 2019-05-14 01:55:08
Hello:
ps ax | grep polkitto see if it's running.
Ahh ...
groucho@devuan:~$ ps ax | grep polkit
1677 ? Sl 0:00 /usr/lib/policykit-1/polkitd --no-debug
1820 tty1 Sl 0:00 lxpolkit
1961 pts/0 S+ 0:00 grep polkit
groucho@devuan:~$ It seems it's ?
I also had a look at /var/log/auth.log.
groucho@devuan:~$ cat /var/log/auth.log | grep -i failed
--- snip ...
May 13 17:02:40 devuan dbus[1518]: [system] Failed to activate service 'org.freedesktop.ConsoleKit': timed out
May 13 17:13:51 devuan polkitd(authority=local): Operator of unix-process:2448:231281 FAILED to authenticate to gain authorization for action com.ubuntu.pkexec.synaptic for unix-process:2448:231281 [/bin/sh /usr/bin/synaptic-pkexec] (owned by unix-user:groucho)
May 13 17:17:28 devuan polkitd(authority=local): Operator of unix-process:2524:253913 FAILED to authenticate to gain authorization for action com.ubuntu.pkexec.synaptic for unix-process:2524:253913 [/bin/sh /usr/bin/synaptic-pkexec] (owned by unix-user:groucho)
May 13 22:02:12 devuan dbus[1516]: [system] Failed to activate service 'org.freedesktop.ConsoleKit': timed out
May 13 22:48:28 devuan dbus[1513]: [system] Failed to activate service 'org.freedesktop.ConsoleKit': timed out
May 13 23:54:04 devuan dbus[1499]: [system] Failed to activate service 'org.freedesktop.ConsoleKit': timed outI saw this on this info as relevant (?) in bugs.debian and thought it may help if you had it:
Not that I have a clue ... =-/
groucho@devuan:~$ ls -al /usr/lib/dbus-1.0/dbus-daemon-launch-helper
-rwsr-xr-- 1 root messagebus 42892 Mar 16 03:22 /usr/lib/dbus-1.0/dbus-daemon-launch-helper
groucho@devuan:~$ groucho@devuan:~$ LANG=C apt-cache policy $(dpkg -S /usr/lib/dbus-1.0/dbus-daemon-launch-helper | cut -d":" -f1)
dbus:
Installed: 1.10.22-1+devuan2
Candidate: 1.10.22-1+devuan2
Version table:
*** 1.10.22-1+devuan2 500
500 http://deb.devuan.org/merged ascii/main i386 Packages
500 http://deb.devuan.org/merged ascii-updates/main i386 Packages
500 http://packages.devuan.org/devuan ascii/main i386 Packages
100 /var/lib/dpkg/status
groucho@devuan:~$ dbusThanks for your input.
A.
#1611 Re: Desktop and Multimedia » LXDE GDBus.Error woes » 2019-05-13 21:36:22
Hello:
... install a graphical polkit authentication agent ...
See the list of installed packages.
It is installed but not (?) running.
Thanks for your input.
A.
#1612 Re: Desktop and Multimedia » LXDE GDBus.Error woes » 2019-05-13 21:33:05
Hello:
It probably has to do with policykit backends.
A permissions things, to be sure.
...removed lxde from the desktop choices in the ascii installer isos because it wasn't quite right.
I see ...
... need to find the right combination of packages ...
OK.
...find out what's installed.
dpkg -l | egrep "consolekit|elogind|libpam|policykit|polkit"
Here it is ...
groucho@devuan:~$ dpkg -l | egrep "consolekit|elogind|libpam|policykit|polkit"
ii consolekit 0.4.6-6 i386 framework for defining and tracking users, sessions and seats
ii elogind 234.4-2 i386 user, seat and session management daemon
ii libelogind0:i386 234.4-2 i386 user, seat and session management library
ii libpam-cap:i386 1:2.25-1 i386 POSIX 1003.1e capabilities (PAM module)
ii libpam-elogind:i386 234.4-2 i386 elogind PAM module
ii libpam-gnome-keyring:i386 3.20.0-3 i386 PAM module to unlock the GNOME keyring upon login
ii libpam-modules:i386 1.1.8-3.6 i386 Pluggable Authentication Modules for PAM
ii libpam-modules-bin 1.1.8-3.6 i386 Pluggable Authentication Modules for PAM - helper binaries
ii libpam-runtime 1.1.8-3.6 all Runtime support for the PAM library
ii libpam0g:i386 1.1.8-3.6 i386 Pluggable Authentication Modules library
ii libpolkit-agent-1-0:i386 0.105-25+devuan0~bpo2+1 i386 PolicyKit Authentication Agent API
ii libpolkit-backend-1-0 0.105-25+devuan0~bpo2+1 all PolicyKit Authorization API
ii libpolkit-backend-consolekit-1-0:i386 0.105-25+devuan0~bpo2+1 i386 PolicyKit backend API
ii libpolkit-gobject-1-0 0.105-25+devuan0~bpo2+1 all PolicyKit Authorization API
ii libpolkit-gobject-consolekit-1-0:i386 0.105-25+devuan0~bpo2+1 i386 PolicyKit Authorization API
ii libpolkit-qt5-1-1:i386 0.112.0-5 i386 PolicyKit-qt5-1 library
ii lxpolkit 0.5.3-2 i386 LXDE PolicyKit authentication agent
ii lxqt-policykit 0.11.1-1 i386 LXQt authentication agent for PolicyKit
ii lxqt-policykit-l10n 0.11.2-1 all Language package for lxqt-policykit
ii policykit-1 0.105-25+devuan0~bpo2+1 i386 framework for managing administrative policies and privileges
ii policykit-1-gnome 0.105-6 i386 authentication agent for PolicyKit
groucho@devuan:~$ ... but none in the list seem to be running:
groucho@devuan:~$ ps x | grep "consolekit|elogind|libpam|policykit|polkit"
5050 pts/0 S+ 0:00 grep consolekit|elogind|libpam|policykit|polkit
groucho@devuan:~$ Thanks in advance,
A.
#1613 Desktop and Multimedia » LXDE GDBus.Error woes » 2019-05-13 19:20:32
- Altoid
- Replies: 16
Hello:
While testing light desktops for my 1000HE, I installed a minimal Devuan ASCII, then X11 and LXDE.
Uninstalled LXDM and start X as user after the login.
All installations made as root after login (without the desktop) have worked perfectly.
But I'm having a problem for which I have not been able to find a solution and am at my wits end.
1. Once the desktop is up (takes a good 30/40s) , there's a pop-up with a notice:
GDBus.Error:org.freedesktop.ConsoleKit.Manager.GeneralError: Unable to lookup session information for process '1824'
This only happens if from a cold start, after a reboot.
Logging out and then logging in again, from the desktop or the system will not have this behaviour. ie: desktop comes up quickly and no pop-up.
But if I reboot it is there again.
2.
I can only start synaptic via gksu in a terminal, if I try to do it from the menu, anything I try to click with the mouse or even ctrl+alt+del is unresponsive.
ie: synaptic-pkexec (.desktop file command) is not working.
Hard shutdown required.
3. Attempting to shutdown or reboot from the menu shows an error at the bottom of the window:
GDBus.Error:org.freedesktop.DBus.Error.Interactive authentication required.
Only logout is possible.
4. Maybe unrelated ...
Cannot get the new settings for the LXTerminal to stick.
Any ideas?
Thanks in advance.
A.
#1614 Re: Installation » [Solved ] Change from IDE to AHCI borks Devuan ASCII installation » 2019-05-11 02:25:53
Hello:
Sometimes the long way is the short way.
Quite so ...
Next time I'll do a more thorough search before posting. =^ |
The upside is that the solution (if needed by anyone else) now has a reference here at Dev1.
EDIT:
Because of what happened here https://dev1galaxy.org/viewtopic.php?pid=16075#p16075 I had to reinstall ASCII again.
What called my attention was that, with the SATA configuration in BIOS now set at AHCI (instead of IDE), the ASCII 2.0.0_i386_netinst.iso did not do what I expected it would.
ie:
Automatically detect AHCI in the BIOS (or ask/offer), setting the proper parameters by adding ahci and libahci to /etc/initramfs-tools/modules and writing list instead of most into /etc/initramfs-tools/initramfs.conf.
Granted, I was using expert install without being one, but is Is this by design?
Maybe this could be fixed by the option most including ahci and libahci?
AHCI is needed for SSDs and these days many notebooks come with one as standard issue.
Just an idea, don't know if there's something that prevents it.
When I was not able to boot into the new installation, I tried to make the necessary changes from within (opening a terminal in the root filesystem) but was ultimately stumped by not being able to do update-initramfs -u so I had to reinstall again.
Cheers,
A.
#1615 Re: Installation » [Solved ] Change from IDE to AHCI borks Devuan ASCII installation » 2019-05-11 00:48:21
Hello:
I guess I could reinstall ASCII and be done with it but I'd like to know if it is something (relatively) simple to fix so I can learn something new from this.
But it will not boot into recovery mode, just drops to a shell I've never used:
It was much easier than I would have thought.
Certainly easier to fix than the hassle I went throug to install the AHCI drivers in XP.
See:
https://askubuntu.com/questions/976071/ … de-to-ahci
This is what worked for me.
modify: /etc/initramfs-tools/modules
add the modules (each per new line):ahci libahci
modify then this file: /etc/initramfs-tools/initramfs.conf
and change < most > into < list>run: update-initramfs -u
Reboot to BIOS, switch to AHCI and boot Xubuntu.
Cheers,
A.
#1616 Installation » [Solved ] Change from IDE to AHCI borks Devuan ASCII installation » 2019-05-11 00:21:05
- Altoid
- Replies: 3
Hello:
Continuing with my Devuan ASCII Asus 1000HE installation.
One of the things that were not done a few years ago (7 or 8?) when I last updated the XP installation that (still) resides on the drive was to update the drivers for AHCI.
At the time XP was rolled out, AHCI was still under developement and drivers were rolled out by Intel a few years on but MS did not see it fit to include them in SP3.
I've done it now and the 1000HE seems to be a bit snappier in XP and was hoping that the same would happen with Devuan ASCII, but now it will not boot.
At a certain point at the start of the boot process, the screen reads:
Begin: Running /scripts/local-block ... doneThis for about 10/12 lines, then waits for the root file system and finally quits: Gave up waiting for the file system device.
Seems Devuan now cannot find the HDD.
Common problems:
- Boot args (cat /proc/cmdline
- Check rootdelay= (did the system wait long enough?)
- Missing modules (cat /proc/modules: ls/dev)
ALERT! UUID=[number] does not exist. Dropping to a shell!Not susrprising as the drive is now running in AHCI mode but back then, when Devuan was installed, the drive was running in IDE mode
I've moved the goal posts/unilaterally changed condiitons, so to speak.
My bets are on a missing AHCI module but I would not know where to start to fix that.
I guess I could reinstall ASCII and be done with it but I'd like to know if it is something (relatively) simple to fix so I can learn something new from this.
But it will not boot into recovery mode, just drops to a shell I've never used:
BusyBox v1.22.1 (Debian 1:1.22.0-19+b3) built-in shell (ash)
Enter 'help' for a list of built-in comands.
(initramfs) _ Thanks in advance.
A.
#1617 Re: Hardware & System Configuration » Asus 1000HE and similar - Newer drivers with older Intel chipsets » 2019-05-08 21:39:05
Hello:
Sorry, I should have said that.
No problem ...
Things I should have said but never did. 8^D!
In any case, it doesn't work.
Boot freezes at ~34.000s on, right after eth0 gets up.
And there it stays, waiting for crtl+alt+del.
Fortunately I've been brushing up on my command line and fixed it in a jiffy.
It seems that the newer drivers are not so backwards compatible with the older chipsets.
Thanks for your input.
A.
#1618 Re: Hardware & System Configuration » Asus 1000HE and similar - Newer drivers with older Intel chipsets » 2019-05-08 20:03:36
Hello:
The UXA acceleration method is ancient ...
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.
... have you tried Xorg's built-in modesetting DDX driver?
Actually, I had no idea about all this.
I came across this setting because of the issue I had with Pale Moon.
/etc/X11/xorg.conf.d/20-modesetting.conf:
Section "Device" Identifier "Device0" Driver "modesetting" EndSection
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.
#1619 Hardware & System Configuration » Asus 1000HE and similar - Newer drivers with older Intel chipsets » 2019-05-06 21:34:38
- Altoid
- Replies: 4
Hello:
I've successfully installed 32bit Devuan ASCII to run on my Asus 1000HE (Atom N280@166/2Gb RAM).
I then rid myself of Mozilla Firefox and installed Pale Mooon 28.5.0, I think it's probably a keeper.
Then, looking to solve an issue which I thought was related to Pale Mooon, I posted at the Pale Moon forum and was directed to a thread with this post:
https://forum.palemoon.org/viewtopic.ph … 41#p160541
The issue I was looking to solve turned out to be totally unrelated to Pale Moon and directly related to the Intel chipset in my 1000HE and the new drivers/kernels.
groucho@devuan:~$ inxi -G
Graphics: Card: Intel Mobile 945GSE Express Integrated Graphics Controller
Display Server: X.Org 1.19.2 driver: intel Resolution: 1024x600@60.00hz
GLX Renderer: Mesa DRI Intel 945GME x86/MMX/SSE2 GLX Version: 2.1 Mesa 13.0.6
groucho@devuan:~$ The fellow who posted the fix actually found it while looking for something else, unrelated to Pale Moon.
So when he came across the Pale Moon thread, decided to share it with the forum.
The references to the fix he found are these:
https://mxlinux.org/wiki/hardware/intel-video-driver
and
https://wiki.archlinux.org/index.php/In … SNA_issues
Apparently the default acceleration method, called sna, can cause issues when using older intel chipsets. An alternative is to use the older acceleration method, uxa.
To do this, I followed the instructions in the links I posted above:
Created a file (as root) called /etc/X11/xorg.conf.d/20-intel.conf with the following contents:
Section "Device"
Identifier "Device0"
Driver "intel"
Option "AccelMethod" "uxa"
EndSection
I followed the instructions to the letter and the supposed Pale Moon issue ceased to exist. =-)
I had also been having some pointer lag problems on the desktop, not as severe as the ones with Pale Moon (a nuisance nevertheless) which at first I adscribed to the unit's touchpad or the Bluetooth mouse but now I see that they were related to the Intel chipset/driver configuration.
I'm posting it all this here as a heads-up and a future reference to anyone wanting to revive their Asus EeePCs.
But the merit belongs 100% to the original poster at the Pale Moon forum.
Cheers,
A.
#1620 Re: Desktop and Multimedia » Mozilla Firefox unacceptable tactics - PLEASE ADVISE » 2019-05-06 00:49:13
Hello:
... using Pale Moon for years and love it.
... post here (in off topic I suppose). I usually visit this forum ...
Will do.
Thank you.
A.
#1621 Re: Desktop and Multimedia » Mozilla Firefox unacceptable tactics - PLEASE ADVISE » 2019-05-05 20:04:59
Hello:
Thanks a lot.
Installed Pale Moon and uBlock Origin + a No Coin file that works with it.
It all works, for the time being.
Big bonus is that the interface is not screwed up.
If this setup really works as I need, I am seriously thinking of not going back to Mozilla Firefox.
A.
#1622 Re: Installation » Devuan ASCII 32bit on Asus 1000HE issue » 2019-05-05 16:56:50
Hello:
That's interesting, you have two entries for the same device, no idea why
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
If legacy device (SB.ATKD - ASUS010) used by eeepc-laptop
is enabled, don't allow eeepc-wmi to load because:
- eeepc-laptop may be loaded, and can conflict with
eeepc-wmi (they both try to register eeepc::touchpad
led for example).
- the WMI interface is inteded to be used when the OS is
not detected as Win 7. And when this is the case, the
ASUS010 device is disabled.
Edit
Apparently the ASUS010 device is the EEEPC Hotkey set.
See
https://github.com/torvalds/linux/blob/ … c-laptop.c
#define EEEPC_LAPTOP_VERSION "0.1"
#define EEEPC_LAPTOP_NAME "Eee PC Hotkey Driver"
#define EEEPC_LAPTOP_FILE "eeepc"#define EEEPC_ACPI_CLASS "hotkey"
#define EEEPC_ACPI_DEVICE_NAME "Hotkey"
#define EEEPC_ACPI_HID "ASUS010"
/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.
"So I removed the 'use acpi_dev_found' patch from my kernel source, and without
this patch eeepc_wmi is loaded successfully, and all fn+ buttons working with
this netbook without acpi_os=Linux extra boot parameter"
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.
#1623 Desktop and Multimedia » Mozilla Firefox unacceptable tactics - PLEASE ADVISE » 2019-05-05 02:31:15
- Altoid
- Replies: 15
Hello:
I use Mozilla Firefox 55, an outdated version.
I do it for a very good reason.
Beside the newer interfaces being utter crap, the specific reason is that with this version I can still use three add-ons that I find very important to have while on-line.
1. No Coin
2. Privacy Badger
3. UBlock Origin
I have managed perfectly well up to now with no issues whatsoever but this afternoon I find that they have been disabled.
When I go to Tools > Add-ons I see that each of the extensions has a legend saying "... could not be verified for muse in Firefox and has been disabled."
Does anyone know what the holy fuck is going on here?
I do not allow automatic upgrades or addons from anyone unless specifically done by me.
So how has this happened?
And most important, how can this crap be overridden?
Thanks in advance.
A.
#1624 Re: Installation » Devuan ASCII 32bit on Asus 1000HE issue » 2019-05-05 01:34:34
Hello:
What does the plain lspci -knn report about your graphics card?
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:~$Oh, and leave that poor cat(1) alone:
grep -i _OS dsdt.dsl
There's more than one way to skin a cat. =-)
I still have to polish my command line.
Thanks for the tip.
Cheers,
A.
#1625 Re: Installation » Devuan ASCII 32bit on Asus 1000HE issue » 2019-05-04 20:01:47
Hello:
You could try clearing the string by using
acpi_osi=
This is what I get using acpi_osi= in the kernel line.
groucho@devuan:~$ sudo dmesg | grep eeepc
[ 6.284913] eeepc_laptop: Eee PC Hotkey Driver
[ 6.285177] eeepc_laptop: Hotkey init flags 0x41
[ 6.286378] eeepc_laptop: TYPE (2000000) not reported by BIOS, enabling anyway
[ 6.292166] eeepc_laptop: PANELPOWER (4000000) not reported by BIOS, enabling anyway
[ 6.292281] eeepc_laptop: Get control methods supported: 0x6101713
[ 6.293219] input: Asus EeePC extra buttons as /devices/platform/eeepc/input/input7
--- from here down were already there ---
[ 7.878347] eeepc_wmi: Found legacy ATKD device (ASUS010)
[ 7.884493] eeepc_wmi: WMI device present, but legacy ATKD device is also present and enabled
[ 7.890126] eeepc_wmi: You probably booted with acpi_osi="Linux" or acpi_osi="!Windows 2009"
[ 7.895852] eeepc_wmi: Can't load eeepc-wmi, use default acpi_osi (preferred) or eeepc-laptop
[ 7.901709] eeepc-wmi: probe of eeepc-wmi failed with error -16
[ 8.559056] eeepc_laptop: Unable to find port
groucho@devuan:~$ Just FYI, the options I got from disassembling dsdt.dat are these:
groucho@devuan:~/dsdt$ cat dsdt.dsl | grep -i _OS
If (CondRefOf (_OSI, Local1))
If (_OSI ("Windows 2000"))
If (_OSI ("Windows 2001"))
If (_OSI ("Windows 2001 SP1"))
If (_OSI ("Windows 2001 SP2"))
If (_OSI ("Windows 2001.1"))
If (_OSI ("Windows 2001.1 SP1"))
If (_OSI ("Windows 2006"))
ElseIf (MCTH (_OS, "Microsoft Windows NT"))
If (MCTH (_OS, "Microsoft WindowsME: Millennium Edition"))
If (MCTH (_OS, "Linux"))
If (CondRefOf (_OSI, Local0))
If (_OSI ("Windows 2001"))
If (_OSI ("Windows 2001 SP1"))
If (_OSI ("Windows 2001 SP2"))
If (_OSI ("Windows 2006"))
If (_OSI ("Windows 2009"))
If (_OSI ("Linux"))
ElseIf (MCTH (_OS, "Microsoft Windows"))
ElseIf (MCTH (_OS, "Microsoft WindowsME: Millennium Edition"))
ElseIf (MCTH (_OS, "Microsoft Windows NT"))
groucho@devuan:~/dsdt$ The kernel is evidently seeing something somewhere that is indicating acpi_osi="Linux" or acpi_osi="!Windows 2009".
That said, the default acpi_osi (preferred) or eeepc-laptop entires are not in the dsdt file.
I'll have to run some tests and see what happens.
Can you post
lspci -knn | grep -iA2 'vga\|3d\|display'
It returns nothing.
I seem to recall having seen something about ASUS010 somewhere once ...
I'll have a look and see what I can find.
Thanks for your input.
A.
Board footer
