You are not logged in.
- Topics: Active | Unanswered
#1676 Installation » [Solved] update-initramfs problem » 2019-05-23 21:26:59
- Altoid
- Replies: 2
Hello:
For reasons long to explain, I had to transplant the HDD with a working Devuan installaiton in my 1000HE to another (presumably identical) 1000HE.
It had the original BIOS from purchase date which for some reason, had no AHCI option, so my Devuan installation would fail to boot as it was loading the AHCI modules.
So I updated the new 1000HE's BIOS to the same version but it seems that there's some difference in the hardware as this new BIOS does not have an AHCI option either.
It's exactly the same BIOS file that my original 1000HE has so it is probably a difference in the hardware.
But I'll only know for sure once I can boot it. =-/
So, as I did once with the original 1000HE, I booted a netinstall DVD, entered 'rescue mode', opened a shell in the installation's root directory and made the necessary changes in /etc/initramfs-tools/modules and /etc/initramfs-tools/initramfs.conf.
See https://dev1galaxy.org/viewtopic.php?pid=15995#p15995
Once done, I ran update-initramfs -u.
It should have ended there but no ...
Instead I get this:
# update-initramfs -u
ls: cannot access '/var/lib/initramfs-tools': no such file or directory
update-initramfs: /boot/initrd.img-4.9.0-9-686-pae has been altered.
update-initramfs: Cannot update. Override with -t option.I've tried -u -t and -t -k all -c to no avail as all give errors.
Any one can point to a solution to this?
Thanks in advance.
A.
#1677 Re: Hardware & System Configuration » dmesg WARNING: CPU and WARN_ON(!connector->state->crtc) messages » 2019-05-19 17:13:05
Hello:
... still a bug if no .dev package is installed.
... no logical path for this info to be generated ...
... rate the issue very serious indeed.
But the maintainers have to think so too ... =-D
... worth putting in a bug report for this, even after 2 years ...
Done.
... clearly isn't completely rooted out ...
I have not seen any indication of its being assigned.
... provide as much relevant info to the circumstances ...
Yes ...
kern.log snippet, lshw, lspci, lsusb, lsmod and kernel-image information.
Being a bug with a number, I sent mail to the <bug_number>@bugs.debian.org address.
Hope it is enough and that I've done it properly.
Thanks for your input.
A.
#1678 Re: Hardware & System Configuration » dmesg WARNING: CPU and WARN_ON(!connector->state->crtc) messages » 2019-05-19 15:24:03
Hello:
... related to building the kernel module for the i915 GPU driver
... it's a trace ...
... shouldn't really be there.
OK.
So it's just debugging information for the developer/maintainer?
... have any related .dev package installed ...
Related, none that I can see.
groucho@devuan:~$ dpkg -l | grep -i i9xx
ii xserver-xorg-video-intel 2:2.99.917+git20161206-1 i386 X.Org X server -- Intel i8xx, i9xx display driver
groucho@devuan:~$ I've also had a thorough look in synaptic installed and no, none.
... may have 'escaped' from there.
Report it as a bug to whomever is/are the dev's for the Intel i915 ...
Would it still be a bug without there being an installed -dev package?
EDIT:
A search on the web for the last part of the initial string ie:
c:414 intel_fb_initial_config+0x3fc/0x5f0 [i915]... got me this from 20 Feb 2017:
https://lists.debian.org/debian-kernel/ … 00265.html
Package: src:linux
Version: 4.9.6-3
Severity: importantThe DRM driver for i915 hardware oopses in a systematic way during bootup on this Dell D430 using kernel 4.9 from testing/frozen.
Booting with kernel 3.16 from stable/updates doesn't produce these symptoms.
-- Package-specific info:
** Version:
Linux version 4.9.0-1-686-pae (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170124 (Debian 6.3.0-5) ) #1 SMP Debian 4.9.6-3 (2017-01-28)
Should I file something more?
It's been more than two years and it's still there.
Severity: important?
Thank you for your input.
A.
#1679 Hardware & System Configuration » dmesg WARNING: CPU and WARN_ON(!connector->state->crtc) messages » 2019-05-19 02:57:41
- Altoid
- Replies: 5
Hello:
Never ending surprises ...
Came across this new set of entries in my dmsg log.
It's new, had not seen it when I had just installed ASCII in my 1000HE.
The [ cut here ] sort of tells me it is something abnormal and meant to be sent somewhere.
[ 9.424614] ------------[ cut here ]------------
[ 9.424781] WARNING: CPU: 0 PID: 6 at /build/linux-6uB1fl/linux-4.9.168/drivers/gpu/drm/i915/intel_fbdev.c:414 intel_fb_initial_config+0x3fc/0x5f0 [i915]
[ 9.424821] WARN_ON(!connector->state->crtc)
[ 9.424831] Modules linked in:
[ 9.424850] i915 crc_ccitt coretemp rfkill psmouse pcspkr uhci_hcd ehci_pci ata_generic drm_kms_helper ehci_hcd snd_hda_codec_realtek snd_hda_codec_generic lpc_ich mfd_core atl1e ata_piix sg drm rng_core wmi usbcore snd_hda_intel usb_common battery i2c_algo_bit snd_hda_codec shpchp snd_hda_core video button ac snd_hwdep snd_pcm snd_timer snd soundcore acpi_cpufreq ext4 crc16 jbd2 crc32c_generic fscrypto ecb xts lrw gf128mul ablk_helper cryptd aes_i586 mbcache sd_mod ahci libahci libata evdev serio_raw scsi_mod thermal
[ 9.425099] CPU: 0 PID: 6 Comm: kworker/u4:0 Not tainted 4.9.0-9-686-pae #1 Debian 4.9.168-1+deb9u2
[ 9.425131] Hardware name: ASUSTeK Computer INC. 1000HE/1000HE, BIOS 1104 10/14/2009
[ 9.425170] Workqueue: events_unbound async_run_entry_fn
[ 9.425193] f5d19d40 c42ff602 f5d19d54 00000000 c406a30a f9029dc6 f5d19d74 00000006
[ 9.425240] f901d370 0000019e f8fcbf0c 0000019e 00000009 f8fcbf0c 00000001 f5e5f800
[ 9.425285] 00000000 f5d19d60 c406a376 00000009 00000000 f5d19d54 f9029dc6 f5d19d74
[ 9.425331] Call Trace:
[ 9.425359] [<c42ff602>] ? dump_stack+0x55/0x73
[ 9.425384] [<c406a30a>] ? __warn+0xea/0x110
[ 9.425531] [<f8fcbf0c>] ? intel_fb_initial_config+0x3fc/0x5f0 [i915]
[ 9.425671] [<f8fcbf0c>] ? intel_fb_initial_config+0x3fc/0x5f0 [i915]
[ 9.425697] [<c406a376>] ? warn_slowpath_fmt+0x46/0x60
[ 9.425835] [<f8fcbf0c>] ? intel_fb_initial_config+0x3fc/0x5f0 [i915]
[ 9.425869] [<c41c5dbf>] ? __kmalloc+0xef/0x500
[ 9.425987] [<f8fcbb10>] ? intelfb_create+0x4d0/0x4d0 [i915]
[ 9.426012] [<f8951946>] ? drm_setup_crtcs+0x1a6/0x950 [drm_kms_helper]
[ 9.426032] [<c40936f5>] ? try_to_wake_up+0x45/0x370
[ 9.426049] [<c4093a6e>] ? wake_up_q+0x2e/0x60
[ 9.426071] [<f89523e1>] ? drm_fb_helper_initial_config+0xc1/0x410 [drm_kms_helper]
[ 9.426098] [<c40a7420>] ? pick_next_task_fair+0x490/0x520
[ 9.426202] [<f8fcc6e0>] ? intel_fbdev_fini+0xd0/0xd0 [i915]
[ 9.426307] [<f8fcc6f6>] ? intel_fbdev_initial_config+0x16/0x30 [i915]
[ 9.426325] [<c408b20a>] ? async_run_entry_fn+0x3a/0x180
[ 9.426342] [<c4092900>] ? deactivate_task+0x20/0xf0
[ 9.426360] [<c45bd6f8>] ? __schedule+0x268/0x770
[ 9.426377] [<c4082df6>] ? process_one_work+0x146/0x390
[ 9.426395] [<c4083079>] ? worker_thread+0x39/0x480
[ 9.426411] [<c4088397>] ? kthread+0xb7/0xd0
[ 9.426427] [<c4083040>] ? process_one_work+0x390/0x390
[ 9.426444] [<c40882e0>] ? kthread_park+0x50/0x50
[ 9.426461] [<c45c1f67>] ? ret_from_fork+0x1b/0x3c
[ 9.426478] ---[ end trace 280b97008804440b ]---
[ 9.430341] fbcon: inteldrmfb (fb0) is primary device
[ 9.431973] ------------[ cut here ]------------
[ 9.431994] WARNING: CPU: 1 PID: 6 at /build/linux-6uB1fl/linux-4.9.168/drivers/gpu/drm/drm_atomic_helper.c:783 drm_atomic_helper_update_legacy_modeset_state+0x22a/0x260 [drm_kms_helper]
[ 9.432106] Modules linked in: i915 crc_ccitt coretemp rfkill psmouse pcspkr uhci_hcd ehci_pci ata_generic drm_kms_helper ehci_hcd snd_hda_codec_realtek snd_hda_codec_generic lpc_ich mfd_core atl1e ata_piix sg drm rng_core wmi usbcore snd_hda_intel usb_common battery i2c_algo_bit snd_hda_codec shpchp snd_hda_core video button ac snd_hwdep snd_pcm snd_timer snd soundcore acpi_cpufreq ext4 crc16 jbd2 crc32c_generic fscrypto ecb xts lrw gf128mul ablk_helper cryptd aes_i586 mbcache sd_mod ahci libahci libata evdev serio_raw scsi_mod thermal
[ 9.432114] CPU: 1 PID: 6 Comm: kworker/u4:0 Tainted: G W 4.9.0-9-686-pae #1 Debian 4.9.168-1+deb9u2
[ 9.432116] Hardware name: ASUSTeK Computer INC. 1000HE/1000HE, BIOS 1104 10/14/2009
[ 9.432125] Workqueue: events_unbound async_run_entry_fn
[ 9.432135] f5d19b00 c42ff602 00000000 00000000 c406a30a c46bb29c 00000001 00000006
[ 9.432143] f8954bb0 0000030f f894ac3a 0000030f 00000009 f894ac3a f5e5f800 00000000
[ 9.432150] f5689800 f5d19b14 c406a41a 00000009 00000000 00000000 f5d19b3c f894ac3a
[ 9.432152] Call Trace:
[ 9.432161] [<c42ff602>] ? dump_stack+0x55/0x73
[ 9.432167] [<c406a30a>] ? __warn+0xea/0x110
[ 9.432179] [<f894ac3a>] ? drm_atomic_helper_update_legacy_modeset_state+0x22a/0x260 [drm_kms_helper]
[ 9.432189] [<f894ac3a>] ? drm_atomic_helper_update_legacy_modeset_state+0x22a/0x260 [drm_kms_helper]
[ 9.432194] [<c406a41a>] ? warn_slowpath_null+0x2a/0x30
[ 9.432204] [<f894ac3a>] ? drm_atomic_helper_update_legacy_modeset_state+0x22a/0x260 [drm_kms_helper]
[ 9.432305] [<f8fae7b5>] ? intel_pre_plane_update+0x55/0x140 [i915]
[ 9.432398] [<f8faf6f4>] ? intel_atomic_commit_tail+0x9a4/0xf60 [i915]
[ 9.432490] [<f8fb751c>] ? intel_prepare_plane_fb+0xdc/0x2a0 [i915]
[ 9.432501] [<f894b45c>] ? drm_atomic_helper_swap_state+0x1cc/0x2d0 [drm_kms_helper]
[ 9.432593] [<f8faffe5>] ? intel_atomic_commit+0x335/0x4c0 [i915]
[ 9.432614] [<f88223a4>] ? drm_atomic_check_only+0x324/0x6a0 [drm]
[ 9.432633] [<f8821dd1>] ? drm_atomic_set_crtc_for_connector+0xb1/0x100 [drm]
[ 9.432725] [<f8fafcb0>] ? intel_atomic_commit_tail+0xf60/0xf60 [i915]
[ 9.432744] [<f882276e>] ? drm_atomic_commit+0x4e/0x60 [drm]
[ 9.432755] [<f8950753>] ? restore_fbdev_mode+0x153/0x2a0 [drm_kms_helper]
[ 9.432774] [<f8821504>] ? drm_modeset_lock_all_ctx+0xa4/0xb0 [drm]
[ 9.432784] [<f8952267>] ? drm_fb_helper_restore_fbdev_mode_unlocked+0x27/0x70 [drm_kms_helper]
[ 9.432793] [<f89522dd>] ? drm_fb_helper_set_par+0x2d/0x70 [drm_kms_helper]
[ 9.432884] [<f8fcb5e5>] ? intel_fbdev_set_par+0x15/0x70 [i915]
[ 9.432891] [<c4378730>] ? fbcon_init+0x540/0x590
[ 9.432897] [<c4400240>] ? visual_init+0xc0/0x120
[ 9.432901] [<c4401369>] ? do_bind_con_driver+0x179/0x370
[ 9.432906] [<c4401863>] ? do_take_over_console+0x123/0x1a0
[ 9.432911] [<c4378af0>] ? set_con2fb_map+0x370/0x370
[ 9.432916] [<c43746df>] ? do_fbcon_takeover+0x5f/0xc0
[ 9.432921] [<c4089851>] ? notifier_call_chain+0x51/0x70
[ 9.432926] [<c4089b79>] ? __blocking_notifier_call_chain+0x39/0x60
[ 9.432931] [<c4089bbf>] ? blocking_notifier_call_chain+0x1f/0x30
[ 9.432935] [<c43802c6>] ? register_framebuffer+0x1f6/0x340
[ 9.432947] [<f8952594>] ? drm_fb_helper_initial_config+0x274/0x410 [drm_kms_helper]
[ 9.433039] [<f8fcc6e0>] ? intel_fbdev_fini+0xd0/0xd0 [i915]
[ 9.433130] [<f8fcc6f6>] ? intel_fbdev_initial_config+0x16/0x30 [i915]
[ 9.433135] [<c408b20a>] ? async_run_entry_fn+0x3a/0x180
[ 9.433139] [<c4092900>] ? deactivate_task+0x20/0xf0
[ 9.433145] [<c45bd6f8>] ? __schedule+0x268/0x770
[ 9.433150] [<c4082df6>] ? process_one_work+0x146/0x390
[ 9.433155] [<c4083079>] ? worker_thread+0x39/0x480
[ 9.433159] [<c4088397>] ? kthread+0xb7/0xd0
[ 9.433164] [<c4083040>] ? process_one_work+0x390/0x390
[ 9.433168] [<c40882e0>] ? kthread_park+0x50/0x50
[ 9.433173] [<c45c1f67>] ? ret_from_fork+0x1b/0x3c
[ 9.433177] ---[ end trace 280b97008804440c ]---I've never seen this in four+ years of Linux distributions.
Can anyone shed a light on this and it's cause?
Thanks in advance.
A.
#1680 Re: Installation » eeepc-acpi-scripts in ASCII » 2019-05-18 16:52:35
Hello:
... upgrade to unstable/ceres ...
... some sort of apt repository pinning magic.
No, I've tried too much magic recently.
It's a backport or I won't try. =- ^
... try at installing from upstream source first maybe?
Thanks, I'll have a look at that.
The reason for Devuan repositories having packages for jessie eeepc-acpi-scripts-1.1.12 and ceres eeepc-acpi-scripts-1.1.13 but not for ASCII is probably because there's no package in the Debian repository for stretch either:
https://packages.debian.org/search?keyw … pi-scripts
Package eeepc-acpi-scripts
jessie (oldstable) (utils): Scripts to support suspend and hotkeys on the Asus Eee PC laptop
1.1.12: all
sid (unstable) (utils): Scripts to support suspend and hotkeys on the Asus Eee PC laptop
1.1.13: all
Maybe it is something that's happened somewhere in ASCII (and obviously affects how the package works) that was not in jessie and won't be in ceres?
Thanks for your input.
A.
#1681 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.
#1682 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.
#1683 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.
#1684 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.
#1685 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.
#1686 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.
#1687 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.
#1688 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.
#1689 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.
#1690 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.
#1691 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.
#1692 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.
#1693 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.
#1694 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.
#1695 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.
#1696 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.
#1697 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.
#1698 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.
#1699 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.
#1700 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.
Board footer
