Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
"top" shows excessive use in ARCH by Xorg and home-name, with additional programs such as browser or libreoffice putting usage over 100 steadily, sometimes freezing the computer. Also a lot of fan and heating.
"top" in Debian WHEEZY, which is also on the same computer, shows usage to be normal, yet WHEEZY is also almost as slow (one minute to bring up iceweasel browser, for example, in which I am writing this slowly).
This slowing began about the time messages showed up in ARCH at first boot. They are not in journalctl so I can only write them from memory:
Code:
[*****](1 of 4) a start job is running for *******(the wired interface)
[*****](2 of 4) a start job is running for wlp16s0
[*****](3 of 4) a start job is running for *******
[*****](4 of 4) a start job is running for *******
The *****'s on the left are flashing red. The ones on the right are notations that I can't remember.
These messages revolve in sequence for a bit, then stop and booting carries on. Can they be a clue to the over usage?
The above is on an hpcompaq6910p. That is regarded as an old machine so I post here because someone may recognize it as a hardware problem.
Last edited by hilltownboy; 08-18-2015 at 11:24 AM.
This indicates that systemd is trying to start a service, but in the end the service fails. This definitely should show up in the journal, however. For a start it would be good to know which services exactly are failing and what you get from
The four messages that recycle do not show on journalctl. I have examined all 1000+ lines.
Of the two devices that I can identify, here are the references that do show:
Code:
Aug 20 11:19:44 arch systemd[1]: sys-subsystem-net-devices-enp0s25.device: Job sys-subsystem-net-devices-enp0s25.device/start timed out.
Aug 20 11:19:44 arch systemd[1]: Timed out waiting for device sys-subsystem-net-devices-enp0s25.device.
Aug 20 11:19:46 arch systemd[1]: Dependency failed for dhcpcd on enp0s25.
Aug 20 11:19:48 arch systemd[1]: dhcpcd@enp0s25.service: Job dhcpcd@enp0s25.service/start failed with result 'dependency'.
Aug 20 11:19:48 arch systemd[1]: sys-subsystem-net-devices-enp0s25.device: Job sys-subsystem-net-devices-enp0s25.device/start failed with result 'timeout'.
Aug 20 11:20:03 arch kernel: e1000e 0000:00:19.0 enp0s25: renamed from eth0
The above is not surprising inasmuch as the wired service cable was not plugged in
Code:
Aug 20 11:19:40 arch systemd[1]: sys-subsystem-net-devices-wlp16s0.device: Job sys-subsystem-net-devices-wlp16s0.device/start timed out.
Aug 20 11:19:40 arch systemd[1]: Timed out waiting for device sys-subsystem-net-devices-wlp16s0.device.
Aug 20 11:19:44 arch systemd[1]: netctl-auto@wlp16s0.service: Job netctl-auto@wlp16s0.service/start failed with result 'dependency'.
Aug 20 11:19:44 arch systemd[1]: sys-subsystem-net-devices-wlp16s0.device: Job sys-subsystem-net-devices-wlp16s0.device/start failed with result 'timeout'.
Aug 20 11:21:02 arch kernel: iwl4965 0000:10:00.0 wlp16s0: renamed from wlan0
* enp0s25.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
* wlp16s0.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
Also maybe of interest:
Code:
* netctl-auto@wlp16s0.service - Automatic wireless network connection using netctl profiles
Loaded: loaded (/usr/lib/systemd/system/netctl-auto@.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2015-08-20 12:04:45 EDT; 1h 53min ago
Docs: man:netctl.special(7)
Process: 271 ExecStart=/usr/bin/netctl-auto start %I (code=exited, status=0/SUCCESS)
CGroup: /system.slice/system-netctl\x2dauto.slice/netctl-auto@wlp16s0.service
`-309 wpa_supplicant -q -B -P /run/wpa_supplicant_wlp16s0.pid -i wlp16s0 -D nl80211,wext -c/run/network/wpa_supplicant_wlp16s0.conf -W
Aug 20 12:04:42 arch systemd[1]: Starting Automatic wireless network connection using netctl profiles...
Aug 20 12:04:44 arch netctl-auto[271]: Included profile 'WIRELESS'
Aug 20 12:04:45 arch systemd[1]: Started Automatic wireless network connection using netctl profiles.
Aug 20 12:04:45 arch wpa_actiond[317]: Starting wpa_actiond session for interface 'wlp16s0'
Accordig to the specs that machine has GMA X3100 for video. TobiSGD may be able to offer some input on the likely performance of that chip - I had very bad experiences with an earlier GMA.
It may explain poor performance even under Wheezy. As for the swap issue, check that UUID in /etc/fstab. To check if it's really an issue, just comment it out for a while. Also check it isn't specified as a resume target on the boot-loader options.
If you can install inxi, post the output of the following
Sorry for this horrible code presentation. Had to get it off PCLinux because inxi is unavailable in WHEEZY and I can't install it in ARCH which is so slow that the wifi connection times out.
Accordig to the specs that machine has GMA X3100 for video. TobiSGD may be able to offer some input on the likely performance of that chip[/code]
The GMA X3100 luckily is not some relabeled PowerVR chip, but a true Intel design. Performance for normal desktop usage should be fine, though this chip is not suited for gaming or serious 3D work.
Yeah, that's pretty ugly - I forgot I have inxi aliased to get rid of the colour highlighting. "inxi -v 4 -c 0" should look better for posting.
So, that actually has an AMD chip using the radeon open source driver - 2-D video performance should be ok. And that Intel iwl4965 should be fine for wifi. Try this on the Arch (and Debian) system so we can compare what drivers you are using
00:19.0 Ethernet controller [0200]: Intel Corporation 82566MM Gigabit Network Connection [8086:1049] (rev 03)
Subsystem: Hewlett-Packard Company Compaq 6910p [103c:30c1]
Kernel driver in use: e1000e
00:1a.0 USB controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 [8086:2834] (rev 03)
--
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI M64-S [Mobility Radeon X2300] [1002:7188]
Subsystem: Hewlett-Packard Company 6910p [103c:30c1]
Kernel driver in use: radeon
02:06.0 CardBus bridge [0607]: Ricoh Co Ltd RL5c476 II [1180:0476] (rev b9)
--
10:00.0 Network controller [0280]: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection [8086:4229] (rev 61)
Subsystem: Intel Corporation Device [8086:1000]
Kernel driver in use: iwl4965
Most everything seems to work but unbelievably slow: 20 minutes to load browser, log in to linuxquestions and find thread; 8 seconds to load a terminal.
Last edited by hilltownboy; 08-22-2015 at 09:10 AM.
Gentlemen, I have to apologize for dragging you through this whole exercise. I just acquired a new power adapter and now the computer is up to speed. So the trouble was mechanical.
Many thanks for your help, from which I learned a lot.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.