Hey Orbmiser. Guess what was my first thought when I read your report. Waiting for pulse? Of course. What soundcard are you using? Built-in or external?
BTW, realtime with pulse? That's not a very good thing.
UP 2014.10.15
Re: UP 2014.10.15
This likely means that your installation is broken. -Mr Pixbuf.
Re: UP 2014.10.15
Orbmiser
share the output of
share the output of
Code: Select all
systemctl --state=failedbliss of ignorance
Re: UP 2014.10.15
Updating the rest of my VMs turned into a disaster because of this.
I've gone back to kernel 3.14 (good thing I still had a local mirror of the security repo).
Now to try to get the VMs back to a useable state (one is borked beyond repair)...
Reminder for the next update pack testing session: test updating VMs after the host has been updated.
I've gone back to kernel 3.14 (good thing I still had a local mirror of the security repo).
Now to try to get the VMs back to a useable state (one is borked beyond repair)...
Reminder for the next update pack testing session: test updating VMs after the host has been updated.
Frank
SolydX EE 64 - tracking Debian Testing
SolydX EE 64 - tracking Debian Testing
Re: UP 2014.10.15
zerozero wrote:Orbmiser
share the output ofCode: Select all
systemctl --state=failed
Code: Select all
orbmiser@winterfell ~ $ systemctl --state=failed
UNIT LOAD ACTIVE SUB DESCRIPTION
rc-local.service loaded failed failed /etc/rc.local Compatibility
rtkit-daemon.service loaded failed failed RealtimeKit Scheduling Policy Service
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
2 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.Code: Select all
orbmiser@winterfell ~ $ systemctl list-unit-files
UNIT FILE STATE
proc-sys-fs-binfmt_misc.automount static
dev-hugepages.mount static
dev-mqueue.mount static
proc-sys-fs-binfmt_misc.mount static
run-lock.mount static
run-user.mount static
sys-fs-fuse-connections.mount static
sys-kernel-config.mount static
sys-kernel-debug.mount static
tmp.mount disabled
systemd-ask-password-console.path static
systemd-ask-password-plymouth.path static
systemd-ask-password-wall.path static
session-1.scope static
acpid.service disabled
alsa-restore.service static
alsa-state.service static
alsa-store.service static
alsa-utils.service masked
anacron.service enabled
atd.service enabled
autovt@.service disabled
avahi-daemon.service enabled
binfmt-support.service enabled
bluetooth.service enabled
bootlogd.service masked
bootlogs.service masked
bootmisc.service masked
checkfs.service masked
checkroot-bootclean.service masked
checkroot.service masked
configure-printer@.service static
console-getty.service disabled
console-kit-daemon.service disabled
console-kit-log-system-restart.service static
console-kit-log-system-start.service static
console-kit-log-system-stop.service static
console-shell.service disabled
cron.service enabled
cryptdisks-early.service masked
cryptdisks.service masked
dbus-org.bluez.service enabled
dbus-org.freedesktop.Avahi.service enabled
dbus-org.freedesktop.hostname1.service static
dbus-org.freedesktop.locale1.service static
dbus-org.freedesktop.login1.service static
dbus-org.freedesktop.machine1.service static
dbus-org.freedesktop.ModemManager1.service enabled
dbus-org.freedesktop.NetworkManager.service enabled
dbus-org.freedesktop.nm-dispatcher.service enabled
dbus-org.freedesktop.timedate1.service static
dbus.service static
debian-fixup.service static
debug-shell.service disabled
display-manager.service enabled
dns-clean.service enabled
emergency.service static
fancontrol.service enabled
fuse.service masked
geoclue.service static
getty@.service enabled
gpsd.service static
gpsdctl@.service static
halt-local.service static
halt.service masked
hostname.service masked
hwclock.service masked
hwclockfirst.service masked
ifup@.service static
initrd-cleanup.service static
initrd-parse-etc.service static
initrd-switch-root.service static
initrd-udevadm-cleanup-db.service static
killprocs.service masked
kmod-static-nodes.service static
kmod.service static
lightdm.service enabled
lm-sensors.service enabled
ModemManager.service enabled
module-init-tools.service static
motd.service masked
mountall-bootclean.service masked
mountall.service masked
mountdevsubfs.service masked
mountkernfs.service masked
mountnfs-bootclean.service masked
mountnfs.service masked
network-manager.service disabled
NetworkManager-dispatcher.service enabled
NetworkManager-wait-online.service disabled
NetworkManager.service enabled
openvpn@.service disabled
packagekit-offline-update.service disabled
packagekit.service static
plymouth-halt.service static
plymouth-kexec.service static
plymouth-log.service enabled
plymouth-poweroff.service static
plymouth-quit-wait.service static
plymouth-quit.service enabled
plymouth-read-write.service enabled
plymouth-reboot.service static
plymouth-start.service static
plymouth-switch-root.service static
plymouth.service enabled
polkitd.service static
pppd-dns.service enabled
procps.service static
quotaon.service static
rc-local.service static
rc.local.service static
reboot.service masked
rescue.service static
rmnologin.service masked
rsync.service disabled
rsyslog.service enabled
rtkit-daemon.service disabled
sendsigs.service masked
serial-getty@.service disabled
single.service masked
stop-bootlogd-single.service masked
stop-bootlogd.service masked
sudo.service disabled
syslog.service enabled
systemd-ask-password-console.service static
systemd-ask-password-plymouth.service static
systemd-ask-password-wall.service static
systemd-backlight@.service static
systemd-binfmt.service static
systemd-fsck-root.service static
systemd-fsck@.service static
systemd-halt.service static
systemd-hibernate.service static
systemd-hostnamed.service static
systemd-hybrid-sleep.service static
systemd-initctl.service static
systemd-journal-flush.service static
systemd-journald.service static
systemd-kexec.service static
systemd-localed.service static
systemd-logind.service static
systemd-machined.service static
systemd-modules-load.service static
systemd-nspawn@.service disabled
systemd-poweroff.service static
systemd-quotacheck.service static
systemd-random-seed.service static
systemd-readahead-collect.service disabled
systemd-readahead-done.service static
systemd-readahead-drop.service disabled
systemd-readahead-replay.service disabled
systemd-reboot.service static
systemd-remount-fs.service static
systemd-shutdownd.service static
systemd-suspend.service static
systemd-sysctl.service static
systemd-timedated.service static
systemd-tmpfiles-clean.service static
systemd-tmpfiles-setup-dev.service static
systemd-tmpfiles-setup.service static
systemd-udev-settle.service static
systemd-udev-trigger.service static
systemd-udevd.service static
systemd-update-utmp-runlevel.service static
systemd-update-utmp.service static
systemd-user-sessions.service static
udev-finish.service static
udev.service static
udisks.service static
udisks2.service static
umountfs.service masked
umountnfs.service masked
umountroot.service masked
unattended-upgrades.service enabled
upower.service disabled
urandom.service static
usb_modeswitch@.service static
usbmuxd.service static
user@.service static
wpa_supplicant.service disabled
x11-common.service masked
-.slice static
machine.slice static
system.slice static
user.slice static
acpid.socket enabled
avahi-daemon.socket enabled
dbus.socket static
gpsd.socket enabled
syslog.socket static
systemd-initctl.socket static
systemd-journald.socket static
systemd-shutdownd.socket static
systemd-udevd-control.socket static
systemd-udevd-kernel.socket static
basic.target static
bluetooth.target static
cryptsetup-pre.target static
cryptsetup.target static
ctrl-alt-del.target disabled
default.target static
emergency.target static
final.target static
getty.target static
graphical.target static
halt.target disabled
hibernate.target static
hybrid-sleep.target static
initrd-fs.target static
initrd-root-fs.target static
initrd-switch-root.target static
initrd.target static
kexec.target disabled
local-fs-pre.target static
local-fs.target static
mail-transport-agent.target static
multi-user.target static
network-online.target static
network.target static
nss-lookup.target static
nss-user-lookup.target static
paths.target static
poweroff.target disabled
printer.target static
reboot.target disabled
remote-fs-pre.target static
remote-fs.target enabled
rescue.target disabled
rpcbind.target static
runlevel0.target disabled
runlevel1.target disabled
runlevel2.target static
runlevel3.target static
runlevel4.target static
runlevel5.target static
runlevel6.target disabled
shutdown.target static
sigpwr.target static
sleep.target static
slices.target static
smartcard.target static
sockets.target static
sound.target static
suspend.target static
swap.target static
sysinit.target static
syslog.target static
system-update.target static
time-sync.target static
timers.target static
umount.target static
x-display-manager.target static
systemd-readahead-done.timer static
systemd-tmpfiles-clean.timer static Portfolio
http://500px.com/Orbmiser
Flickr
http://www.flickr.com/photos/orb9220/
SolydK - Kernel 3.16-2-amd64 - KDE 4.14.1 Update Pack: 2014.10.15
http://500px.com/Orbmiser
Flickr
http://www.flickr.com/photos/orb9220/
SolydK - Kernel 3.16-2-amd64 - KDE 4.14.1 Update Pack: 2014.10.15
Re: UP 2014.10.15
ok, now
the output should give (in the last line, probably) the process number, like this
it might give us some hints about what is wrong.
again with my example
Code: Select all
systemctl status rtkit-daemon.serviceat this point tryzerozero@home ~ $ systemctl status fancontrol.service
● fancontrol.service - fan speed regulator
Loaded: loaded (/lib/systemd/system/fancontrol.service; enabled)
Active: failed (Result: exit-code) since Wed 2014-10-15 15:22:15 BST; 1 day 2h ago
Docs: man:fancontrol(8)
man:pwmconfig(8)
Process: 1027 ExecStartPre=/usr/sbin/fancontrol --check (code=exited, status=1/FAILURE)
zerozero@home ~ $
Code: Select all
sudo journalctl -b _PID=<NUMBER>again with my example
Code: Select all
zerozero@home ~ $ sudo journalctl -b _PID=1027
[sudo] password for zerozero:
-- Logs begin at Wed 2014-10-15 15:21:56 BST, end at Thu 2014-10-16 18:10:41 BST. --
Oct 15 15:22:15 home fancontrol[1027]: Loading configuration from /etc/fancontrol ...
Oct 15 15:22:15 home fancontrol[1027]: Some mandatory settings missing, please check your config file!bliss of ignorance
Re: UP 2014.10.15
I've also had problems with rtkit, had this in the logs:
systemd[...]: Failed at step NAMESPACE spawning /usr/lib/rtkit/rtkit-daemon: Operation not permitted
Some googling led me to this: https://bugs.debian.org/cgi-bin/bugrepo ... bug=754076
After upgrading to UP 2014.10.15, /tmp is a link to /var/tmp and that causes some problems.
EDIT 3: Explained by zerozero here: http://forums.solydxk.nl/viewtopic.php? ... =60#p45961
I deleted the link an recreated /tmp as a directory, after reboot rtkit started without issues.
It solved some strange hangs/timeouts too, on a freshly booted machine it took15 seconds after clicking Kickoff until it popped up.
systemd[...]: Failed at step NAMESPACE spawning /usr/lib/rtkit/rtkit-daemon: Operation not permitted
Some googling led me to this: https://bugs.debian.org/cgi-bin/bugrepo ... bug=754076
After upgrading to UP 2014.10.15, /tmp is a link to /var/tmp and that causes some problems.
EDIT 3: Explained by zerozero here: http://forums.solydxk.nl/viewtopic.php? ... =60#p45961
I deleted the link an recreated /tmp as a directory, after reboot rtkit started without issues.
It solved some strange hangs/timeouts too, on a freshly booted machine it took15 seconds after clicking Kickoff until it popped up.
Re: UP 2014.10.15
1. are the sources.list correct and the UP was installed without errors?zerozero wrote:we need to check a couple things:abqnm wrote:This UP has fixed some things, while it has broken some things terribly. First, now I can use the current kernel for the first time since 3.11-2. Every kernel since would cause my display not to wake back up after closing the lid. The 3.16-2 is the first kernel since that allows my display to wake when I close the lid. So that is a plus.
SolydK 32-Bit
Now to what is broken.
First, I have the display brightness bar permanently displayed on my screen at 100%, regardless of what brightness setting I am using. It also does not change when I change the brightness. I am using the Intel 2:2.21.15-2+b2 graphics driver. Update: As I was typing the rest of this, about 8 minutes after boot, the brightness slider went away. I will come edit this post with details after I submit it and reboot because I don't want to lose all this in case it is gone for good or is just temporary.
Second, I tried to take a screenshot of this, and noticed that the PrintScreen key does not launch the screenshot tool.
Third, If I launch any key combo using the Super (Windows) Key, the system becomes completely unresponsive, requiring me to hold the power button to power down.
Here is my hardware info for reference:Any help would be appreciated.Code: Select all
H/W path Device Class Description ==================================================== system XPS M1330 /0 bus 0N6705 /0/0 memory 64KiB BIOS /0/400 processor Core 2 Duo /0/400/700 memory 32KiB L1 cache /0/400/701 memory 2MiB L2 cache /0/400/0.1 processor Logical CPU /0/400/0.2 processor Logical CPU /0/1000 memory 3GiB System Memory /0/1000/0 memory 1GiB DIMM DDR Synchronous 667 MHz (1.5 ns) /0/1000/1 memory 2GiB DIMM DDR Synchronous 667 MHz (1.5 ns) /0/100 bridge Mobile PM965/GM965/GL960 Memory Controller Hub /0/100/2 display Mobile GM965/GL960 Integrated Graphics Controller (primary) /0/100/2.1 display Mobile GM965/GL960 Integrated Graphics Controller (secondary) /0/100/1a bus 82801H (ICH8 Family) USB UHCI Controller #4 /0/100/1a/1 usb1 bus UHCI Host Controller /0/100/1a.1 bus 82801H (ICH8 Family) USB UHCI Controller #5 /0/100/1a.1/1 usb2 bus UHCI Host Controller /0/100/1a.7 bus 82801H (ICH8 Family) USB2 EHCI Controller #2 /0/100/1a.7/1 usb6 bus EHCI Host Controller /0/100/1b multimedia 82801H (ICH8 Family) HD Audio Controller /0/100/1c bridge 82801H (ICH8 Family) PCI Express Port 1 /0/100/1c.1 bridge 82801H (ICH8 Family) PCI Express Port 2 /0/100/1c.1/0 wlan0 network AR928X Wireless Network Adapter (PCI-Express) /0/100/1c.3 bridge 82801H (ICH8 Family) PCI Express Port 4 /0/100/1c.5 bridge 82801H (ICH8 Family) PCI Express Port 6 /0/100/1c.5/0 eth1 network NetLink BCM5906M Fast Ethernet PCI Express /0/100/1d bus 82801H (ICH8 Family) USB UHCI Controller #1 /0/100/1d/1 usb3 bus UHCI Host Controller /0/100/1d.1 bus 82801H (ICH8 Family) USB UHCI Controller #2 /0/100/1d.1/1 usb4 bus UHCI Host Controller /0/100/1d.2 bus 82801H (ICH8 Family) USB UHCI Controller #3 /0/100/1d.2/1 usb5 bus UHCI Host Controller /0/100/1d.2/1/1 generic Biometric Coprocessor /0/100/1d.7 bus 82801H (ICH8 Family) USB2 EHCI Controller #1 /0/100/1d.7/1 usb7 bus EHCI Host Controller /0/100/1d.7/1/6 multimedia Laptop Integrated Webcam /0/100/1e bridge 82801 Mobile PCI Bridge /0/100/1e/1 bus R5C832 IEEE 1394 Controller /0/100/1e/1.1 generic R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter /0/100/1e/1.2 generic R5C592 Memory Stick Bus Host Adapter /0/100/1e/1.3 generic xD-Picture Card Controller /0/100/1f bridge 82801HM (ICH8M) LPC Interface Controller /0/100/1f.1 storage 82801HM/HEM (ICH8M/ICH8M-E) IDE Controller /0/100/1f.2 storage 82801HM/HEM (ICH8M/ICH8M-E) SATA Controller [IDE mode] /0/100/1f.3 bus 82801H (ICH8 Family) SMBus Controller /0/1 scsi0 storage /0/1/0.0.0 /dev/cdrom disk DVD+-RW UJ-857G /0/2 scsi2 storage /0/2/0.0.0 /dev/sda disk 250GB WDC WD2500BEKT-0 /0/2/0.0.0/1 /dev/sda1 volume 100MiB Windows NTFS volume /0/2/0.0.0/2 /dev/sda2 volume 51GiB Windows NTFS volume /0/2/0.0.0/3 /dev/sda3 volume 54GiB Extended partition /0/2/0.0.0/3/5 /dev/sda5 volume 14GiB Linux filesystem partition /0/2/0.0.0/3/6 /dev/sda6 volume 37GiB Linux filesystem partition /0/2/0.0.0/3/7 /dev/sda7 volume 2988MiB Linux swap / Solaris partition /0/2/0.0.0/4 /dev/sda4 volume 125GiB EXT3 volume /1 power DELL 15
Edit: As mentioned in my update earlier, about 8 minutes after boot, the brightness bar went away. When that happened, everything else worked normally. I rebooted the system, and the brightness bar is back, and the odd behavior with it--no screenshots, Super key locks up the system, etc. I'm sure I can wait it out and it will go to normal again, but I shouldn't have to wait 8 minutes after boot to use the system. So, if anyone has any thoughts as to what could be causing this, I'm all ears. I can post any details you need.
Edit 2: I have noticed that immediately after the Brightness bar goes away and normal behavior resumes, my touchpad driver loads into the system tray, so it would indicate that it is hanging somewhere in the startup process for whatever immediately precedes the touchpad loading.
Any ideas? It is really frustrating having to wait ten minutes before my system is usable after boot, and walking on eggshells in those first ten minutes, because if I touch the wrong key or right click the wrong place I have to hard reset the system and start again. It isn't kernel related as I can boot into the older kernels and it still happens. I don't know what to do here, but something in this UP has caused this fragile extended boot behavior. Once the screen brightness bar goes away, the system becomes perfectly stable. I can't see anything unusual happening in dmesg around the time it suddenly starts to work either. I don't know what else to look for. I would appreciate some guidance. The UP completed with no errors of any kind (or if it did, it didn't display them in the console long enough to read them). I really don't want to have to wipe my production system just to solve this problem. Thanks.
share the output of
Code: Select all
inxi -r; apt update && apt dist-upgrade
Repos: Active apt sources in file: /etc/apt/sources.list
deb http://packages.solydxk.com/production/ solydxk main upstream import kdenext community
deb http://debian.solydxk.com/production/ testing main contrib non-free
deb http://debian.solydxk.com/production/multimedia/ testing main non-free
deb http://debian.solydxk.com/security/ testing/updates main contrib non-free
deb http://community.solydxk.com/production/ solydxk main
deb http://ftp.us.debian.org/debian/ wheezy contrib
deb http://download.opensuse.org/repositories/home:/DarkPlayer:/Pipelight/Debian_7.0/ ./
Active apt sources in file: /etc/apt/sources.list.d/google-chrome-unstable.list
deb http://dl.google.com/linux/chrome/deb/ stable main
Active apt sources in file: /etc/apt/sources.list.d/google-chrome.list
deb http://dl.google.com/linux/chrome/deb/ stable main
Active apt sources in file: /etc/apt/sources.list.d/google-earth.list
deb http://dl.google.com/linux/earth/deb/ stable main
Active apt sources in file: /etc/apt/sources.list.d/google-talkplugin.list
deb http://dl.google.com/linux/talkplugin/deb/ stable main
[sudo] password for brandon:
Ign http://dl.google.com stable InRelease
Hit http://packages.solydxk.com solydxk InRelease
Ign http://ftp.us.debian.org wheezy InRelease
Ign http://dl.google.com stable InRelease
Hit http://debian.solydxk.com testing InRelease
Hit http://debian.solydxk.com testing InRelease
Hit http://community.solydxk.com solydxk InRelease
Hit http://debian.solydxk.com testing/updates InRelease
Hit http://ftp.us.debian.org wheezy Release.gpg
Ign http://download.opensuse.org ./ InRelease
Ign http://dl.google.com stable InRelease
Hit http://ftp.us.debian.org wheezy Release
Hit http://packages.solydxk.com solydxk/kdenext i386 Packages
Hit http://packages.solydxk.com solydxk/main i386 Packages
Hit http://packages.solydxk.com solydxk/upstream i386 Packages
Hit http://packages.solydxk.com solydxk/import i386 Packages
Hit http://download.opensuse.org ./ Release.gpg
Hit http://ftp.us.debian.org wheezy/contrib i386 Packages
Hit http://dl.google.com stable Release.gpg
Hit http://community.solydxk.com solydxk/main i386 Packages
Hit http://dl.google.com stable Release.gpg
Hit http://download.opensuse.org ./ Release
Hit http://dl.google.com stable Release.gpg
Hit http://dl.google.com stable Release
Ign http://ftp.us.debian.org wheezy/contrib Translation-en
Ign http://community.solydxk.com solydxk/main Translation-en_US
Ign http://community.solydxk.com solydxk/main Translation-en
Hit http://dl.google.com stable Release
Hit http://dl.google.com stable Release
Get:1 http://dl.google.com stable/main i386 Packages [1,214 B]
Hit http://debian.solydxk.com testing/updates/contrib i386 Packages
Hit http://debian.solydxk.com testing/updates/non-free i386 Packages
Get:2 http://dl.google.com stable/main i386 Packages [464 B]
Hit http://debian.solydxk.com testing/main i386 Packages
Hit http://download.opensuse.org ./ Packages
Hit http://debian.solydxk.com testing/contrib i386 Packages
Hit http://debian.solydxk.com testing/non-free i386 Packages
Hit http://debian.solydxk.com testing/main i386 Packages
Hit http://debian.solydxk.com testing/non-free i386 Packages
Hit http://debian.solydxk.com testing/updates/main i386 Packages
Get:3 http://dl.google.com stable/main i386 Packages [710 B]
Ign http://download.opensuse.org ./ Translation-en_US
Ign http://download.opensuse.org ./ Translation-en
Ign http://debian.solydxk.com testing/contrib Translation-en_US
Ign http://debian.solydxk.com testing/contrib Translation-en
Ign http://debian.solydxk.com testing/main Translation-en_US
Ign http://debian.solydxk.com testing/main Translation-en
Ign http://debian.solydxk.com testing/non-free Translation-en_US
Ign http://debian.solydxk.com testing/non-free Translation-en
Ign http://debian.solydxk.com testing/main Translation-en_US
Ign http://debian.solydxk.com testing/main Translation-en
Ign http://debian.solydxk.com testing/non-free Translation-en_US
Ign http://debian.solydxk.com testing/non-free Translation-en
Ign http://debian.solydxk.com testing/updates/contrib Translation-en_US
Ign http://debian.solydxk.com testing/updates/contrib Translation-en
Ign http://debian.solydxk.com testing/updates/main Translation-en_US
Ign http://debian.solydxk.com testing/updates/main Translation-en
Ign http://debian.solydxk.com testing/updates/non-free Translation-en_US
Ign http://debian.solydxk.com testing/updates/non-free Translation-en
Ign http://dl.google.com stable/main Translation-en_US
Ign http://dl.google.com stable/main Translation-en
Ign http://dl.google.com stable/main Translation-en_US
Ign http://dl.google.com stable/main Translation-en
Ign http://dl.google.com stable/main Translation-en_US
Ign http://dl.google.com stable/main Translation-en
Fetched 2,388 B in 4s (499 B/s)
W: Failed to fetch http://packages.solydxk.com/production/dists/solydxk/InRelease Unable to find expected entry 'community/binary-i386/Packages' in Release file (Wrong sources.list entry or malformed file)
E: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
W: Duplicate sources.list entry http://dl.google.com/linux/chrome/deb/ stable/main i386 Packages (/var/lib/apt/lists/dl.google.com_linux_chrome_deb_dists_stable_main_binary-i386_Packages)
W: You may want to run apt-get update to correct these problems2. it doesn't hurt have a look at the general system information, so please can you also provide the output of
Code: Select all
inxi -Fzx
System: Host: lodys Kernel: 3.16-2-686-pae i686 (32 bit gcc: 4.8.3) Desktop: KDE 4.14.1 (Qt 4.8.6)
Distro: SolydXK 1 testing
Machine: System: Dell product: XPS M1330
Mobo: Dell model: 0N6705 Bios: Dell v: A15 date: 12/26/2008
CPU: Dual core Intel Core2 Duo T6400 (-MCP-) cache: 2048 KB
flags: (lm nx pae sse sse2 sse3 sse4_1 ssse3) bmips: 7979
Clock Speeds: 1: 2000 MHz 2: 2000 MHz
Graphics: Card: Intel Mobile GM965/GL960 Integrated Graphics Controller (primary) bus-ID: 00:02.0
Display Server: X.Org 1.16.1 drivers: intel (unloaded: fbdev,vesa) Resolution: 1280x800@60.00hz
GLX Renderer: Mesa DRI Intel 965GM x86/MMX/SSE2 GLX Version: 2.1 Mesa 10.2.6 Direct Rendering: Yes
Audio: Card Intel 82801H (ICH8 Family) HD Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0
Sound: Advanced Linux Sound Architecture v: k3.16-2-686-pae
Network: Card-1: Qualcomm Atheros AR928X Wireless Network Adapter (PCI-Express) driver: ath9k bus-ID: 0c:00.0
IF: wlan0 state: down mac: <filter>
Card-2: Broadcom NetLink BCM5906M Fast Ethernet PCI Express driver: tg3 v: 3.137 bus-ID: 09:00.0
IF: eth1 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives: HDD Total Size: 250.1GB (35.1% used) ID-1: /dev/sda model: WDC_WD2500BEKT size: 250.1GB temp: 38C
Partition: ID-1: / size: 15G used: 11G (81%) fs: ext4 dev: /dev/sda5
ID-2: /home size: 37G used: 20G (56%) fs: ext4 dev: /dev/sda6
ID-3: swap-1 size: 3.13GB used: 0.07GB (2%) fs: swap dev: /dev/sda7
Sensors: System Temperatures: cpu: 55.5C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 192 Uptime: 19:03 Memory: 1148.5/3030.1MB Init: systemd runlevel: 5 Gcc sys: 4.9.1
Client: Shell (bash 4.3.251) inxi: 2.1.28 the buggy behaviour persists if you reset them to defaults?
I do not believe I have modified anything related to power settings. Anything in particular I should check? This just began after this UP. All previous UPs have installed without issue, though as I mentioned, I had to stay on the 3.11-2 kernel because all of the newer kernels up until this UP's kernel would cause my screen not to wake when I reopened the lid of my laptop.
4. post the output of
Code: Select all
sudo journalctl -b | grep err
Oct 15 16:22:10 lodys kernel: ACPI: IRQ0 used by override.
Oct 15 16:22:10 lodys kernel: ACPI: IRQ2 used by override.
Oct 15 16:22:10 lodys kernel: ACPI: IRQ9 used by override.
Oct 15 16:22:10 lodys kernel: ACPI: Using IOAPIC for interrupt routing
Oct 15 16:22:10 lodys kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 9 10 *11)
Oct 15 16:22:10 lodys kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 5 7) *10
Oct 15 16:22:10 lodys kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 9 10 11) *4
Oct 15 16:22:10 lodys kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs *5 7 9 10 11)
Oct 15 16:22:10 lodys kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
Oct 15 16:22:10 lodys kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
Oct 15 16:22:10 lodys kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 *7 9 10 11 12 14 15)
Oct 15 16:22:10 lodys kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
Oct 15 16:22:10 lodys kernel: sdhci: Copyright(c) Pierre Ossman
Oct 15 16:22:12 lodys kernel: EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro
Oct 15 16:22:14 lodys kernel: i801_smbus 0000:00:1f.3: SMBus using PCI Interrupt
Oct 15 16:22:17 lodys kernel: EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: errors=remount-ro
Oct 15 16:22:17 lodys kernel: EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: errors=remount-ro
Oct 15 16:22:19 lodys systemd[1]: Starting Deferred execution scheduler...
Oct 15 16:22:19 lodys systemd[1]: Started Deferred execution scheduler.
Oct 15 16:34:38 lodys kernel: perf interrupt took too long (2502 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
Oct 15 16:43:09 lodys org.gtk.Private.UDisks2VolumeMonitor[2122]: index_parse.c:191: indx_parse(): error opening /media/Media/BDMV/index.bdmv
Oct 15 16:43:09 lodys org.gtk.Private.UDisks2VolumeMonitor[2122]: index_parse.c:191: indx_parse(): error opening /media/Media/BDMV/BACKUP/index.bdmv
Oct 15 17:06:41 lodys kernel: perf interrupt took too long (5006 > 5000), lowering kernel.perf_event_max_sample_rate to 25000
Oct 15 19:14:12 lodys kernel: Workqueue: kacpi_notify acpi_os_execute_deferred
Oct 15 19:14:12 lodys kernel: [<c12baeed>] ? acpi_os_execute_deferred+0x11/0x1b
Oct 16 03:00:46 lodys NetworkManager[1603]: <info> (eth1): link disconnected (deferring action for 4 seconds)
Code: Select all
sudo systemctl status upower
upower.service - Daemon for power management
Loaded: loaded (/lib/systemd/system/upower.service; disabled)
Active: active (running) since Wed 2014-10-15 16:22:44 MDT; 19h ago
Docs: man:upowerd(8)
Main PID: 2178 (upowerd)
CGroup: /system.slice/upower.service
└─2178 /usr/lib/upower/upowerd
Oct 15 16:22:44 lodys systemd[1]: Started Daemon for power management.
Re: UP 2014.10.15
I hade some other issues as well, not sure if they are related to UP 2014.10.15: my (only) network card was named eth1. Checked a machine that hadn't been upgraded to UP 2014.10.15 and it too had eth1.
Turns out eth0 in /etc/udev/rules.d/70-persistent-net.rules is configured to be an Intel e1000 card:
# PCI device 0x8086:0x100e (e1000)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:27:52:fe:13", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
The same NIC is in the config on all my machines so it has to be from the installation media.
Worked around it by removing the Intel e1000 lines and changed the config for my real NIC from eth1 to eth0 in the same file.
Also had to remove eth0 completely from /etc/network/interfaces, Network Manager didn't manage it otherwise.
Turns out eth0 in /etc/udev/rules.d/70-persistent-net.rules is configured to be an Intel e1000 card:
# PCI device 0x8086:0x100e (e1000)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:27:52:fe:13", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
The same NIC is in the config on all my machines so it has to be from the installation media.
Worked around it by removing the Intel e1000 lines and changed the config for my real NIC from eth1 to eth0 in the same file.
Also had to remove eth0 completely from /etc/network/interfaces, Network Manager didn't manage it otherwise.
-
Gonzalo_VC
- Posts: 321
- Joined: 07 May 2013 13:25
- Location: SouthAmerica
Re: UP 2014.10.15
I boldly upgrade my main PC at work, saw some disturbing messages, but everything was fine, in the end.
Looks like something the team warned about:
Looks like something the team warned about:
Code: Select all
(gtk-update-icon-cache-3.0:3761): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': Arquivo ou diretório não encontrado
This likely means that your installation is broken.
Try running the command
gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
to make things work again for the time being.
Processing triggers for shared-mime-info (1.3-1) ...
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'
Unknown media type in type 'uri/mms'
Unknown media type in type 'uri/mmst'
Unknown media type in type 'uri/mmsu'
Unknown media type in type 'uri/pnm'
Unknown media type in type 'uri/rtspt'
Unknown media type in type 'uri/rtspu'
Don't be a pirate, nor a slave. Use GNU/Linux!
GNU/Linux user 451206
SolydXK, GALPon MiniNo, PCLinuxOS, Xubuntu
Re: UP 2014.10.15
Thanks, but that was the first thing that I tried. I actually have not been able to run any kernel newer than 3.11-2 because of graphics card issues, so for the last 3 UPs I have always booted with the older kernel. Whenever I would close the lid of my laptop, the screen would not wake back up on any newer kernel version. The 3.16 kernel that came with this UP actually solved that problem, but something else with the UP seems to be causing the issues I am having, as booting with the 3.11-2 kernel results in the same behavior--screen brightness bar stays on screen at 100% for 8-10 minutes, screenshot doesn't work, and using the super key will completely freeze the system. If I wait until that bar goes away in 8-10 minutes, my mouse driver loads in the system tray and then the system is completely stable. Zerozero posted some more detailed requests for info, so maybe he will be able to help me through it. Thanks though!Schoelje wrote:@abqnm
It sounds like a kernel issue.
I googled for "Mobile GM965/GL960 Integrated Graphics Controller" and found these to be interesting:
https://bugs.freedesktop.org/show_bug.cgi?id=75723
workaround:
https://bugs.kde.org/show_bug.cgi?id=332784#c3
Some people booted the old kernel to get it all working again.
Re: UP 2014.10.15
Pretty sure that happens in every UP and is nothing to worry about.Gonzalo_VC wrote:I boldly upgrade my main PC at work, saw some disturbing messages, but everything was fine, in the end.
Looks like something the team warned about:
Code: Select all
(gtk-update-icon-cache-3.0:3761): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': Arquivo ou diretório não encontrado This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. Processing triggers for shared-mime-info (1.3-1) ... Unknown media type in type 'all/all' Unknown media type in type 'all/allfiles' Unknown media type in type 'uri/mms' Unknown media type in type 'uri/mmst' Unknown media type in type 'uri/mmsu' Unknown media type in type 'uri/pnm' Unknown media type in type 'uri/rtspt' Unknown media type in type 'uri/rtspu'
Re: UP 2014.10.15
Some more poettering effect. A collateral effect this time, but again pulse lagging systems for some cause or another. AFAIK; rtkit-daemon is only needed by pulseaudio.dali wrote:I've also had problems with rtkit, had this in the logs:
systemd[...]: Failed at step NAMESPACE spawning /usr/lib/rtkit/rtkit-daemon: Operation not permitted
Some googling led me to this: https://bugs.debian.org/cgi-bin/bugrepo ... bug=754076
After upgrading to UP 2014.10.15, /tmp is a link to /var/tmp and that causes some problems.
I deleted the link an recreated /tmp as a directory, after reboot rtkit started without issues.
It solved some strange hangs/timeouts too, on a freshly booted machine it took15 seconds after clicking Kickoff until it popped up.
This likely means that your installation is broken. -Mr Pixbuf.
-
Gonzalo_VC
- Posts: 321
- Joined: 07 May 2013 13:25
- Location: SouthAmerica
Re: UP 2014.10.15
Yea. It's OK, here.abqnm wrote: Pretty sure that happens in every UP and is nothing to worry about.
Thanks.
By the way, is this not yet the synchronization between the old Home and Business Eds. into the new "Regular" one, right? Since the repos are changed but there are a lot of "testing", there. So we have to expect more changes.
Godspeed SolydXK!
Don't be a pirate, nor a slave. Use GNU/Linux!
GNU/Linux user 451206
SolydXK, GALPon MiniNo, PCLinuxOS, Xubuntu
Re: UP 2014.10.15
Yep, sound wasn't working either until I fixed the rtkit problem.Snap wrote: Some more poettering effect. A collateral effect this time, but again pulse lagging systems for some cause or another. AFAIK; rtkit-daemon is only needed by pulseaudio.
-
TeaSwigger
- Posts: 57
- Joined: 27 Feb 2013 14:07
Re: UP 2014.10.15
output:zerozero wrote:could you post the output ofTeaSwigger wrote:Unfortunately the update did not succeed here (fortunately there's 2 OS on this PC). It said something like "dpkg: error processing package gpsd (--configure)" and neither sudo apt-get -f install nor sudo dpkg --configure -a will get her past it. What now?so we can see exactly what went wrong.Code: Select all
cat /var/log/apt/term.log | grep gpsd
Code: Select all
Preparing to unpack .../archives/gpsd_3.11-1_amd64.deb ...
Unpacking gpsd (3.11-1) over (3.10+dev3~d6b65b48-1) ...
Setting up gpsd (3.11-1) ...
Creating/updating gpsd user account...
A dependency job for gpsd.service failed. See 'journalctl -xn' for details.
invoke-rc.d: initscript gpsd, action "start" failed.
dpkg: error processing package gpsd (--configure):
gpsd
So I tried to purge gpsd as zerozero suggests; this did succeed, but trying updatemanager again results in a repeat of the above none the less. So we seem to be stuck at:
Code: Select all
Setting up gpsd (3.11-1) ...
Creating/updating gpsd user account...
A dependency job for gpsd.service failed. See 'journalctl -xn' for details.
invoke-rc.d: initscript gpsd, action "start" failed.
dpkg: error processing package gpsd (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
gpsd
E: Sub-process /usr/bin/dpkg returned an error code (1)"You can't get to wonderful without passing through alright" -Bill Withers
SolydK 64-bit - AMD Quad Core - 4GB RAM - accursed NVIDIA GeForce 5800 graphics - lovely ASUS Xonar Essence ST sound
SolydK 64-bit - AMD Quad Core - 4GB RAM - accursed NVIDIA GeForce 5800 graphics - lovely ASUS Xonar Essence ST sound
Re: UP 2014.10.15
zerozero wrote:ok, nowthe output should give (in the last line, probably) the process number, like thisCode: Select all
systemctl status rtkit-daemon.serviceat this point tryzerozero@home ~ $ systemctl status fancontrol.service
● fancontrol.service - fan speed regulator
Loaded: loaded (/lib/systemd/system/fancontrol.service; enabled)
Active: failed (Result: exit-code) since Wed 2014-10-15 15:22:15 BST; 1 day 2h ago
Docs: man:fancontrol(8)
man:pwmconfig(8)
Process: 1027 ExecStartPre=/usr/sbin/fancontrol --check (code=exited, status=1/FAILURE)
zerozero@home ~ $it might give us some hints about what is wrong.Code: Select all
sudo journalctl -b _PID=<NUMBER>
again with my exampleCode: Select all
zerozero@home ~ $ sudo journalctl -b _PID=1027 [sudo] password for zerozero: -- Logs begin at Wed 2014-10-15 15:21:56 BST, end at Thu 2014-10-16 18:10:41 BST. -- Oct 15 15:22:15 home fancontrol[1027]: Loading configuration from /etc/fancontrol ... Oct 15 15:22:15 home fancontrol[1027]: Some mandatory settings missing, please check your config file!
Code: Select all
orbmiser@winterfell ~ $ systemctl status rtkit-daemon.service
rtkit-daemon.service - RealtimeKit Scheduling Policy Service
Loaded: loaded (/lib/systemd/system/rtkit-daemon.service; disabled)
Active: failed (Result: exit-code) since Thu 2014-10-16 11:45:45 PDT; 14min ago
Process: 1679 ExecStart=/usr/lib/rtkit/rtkit-daemon (code=exited, status=226/NAMESPACE)
Main PID: 1679 (code=exited, status=226/NAMESPACE)
CGroup: /system.slice/rtkit-daemon.serviceCode: Select all
orbmiser@winterfell ~ $ sudo journalctl -b _PID=1679
-- Logs begin at Thu 2014-10-16 11:23:07 PDT, end at Thu 2014-10-16 11:57:43 PDT. --
Oct 16 11:45:45 winterfell systemd[1679]: Failed at step NAMESPACE spawning /usr/lib/rtkit/rtkit-daemon: Operation not
lines 1-2/2 (END)But don't have SSD just plain old Sata & a IDE hardrives.Maybe something mentioned by by dali
I've also had problems with rtkit, had this in the logs:
systemd[...]: Failed at step NAMESPACE spawning /usr/lib/rtkit/rtkit-daemon: Operation not permitted
Some googling led me to this: https://bugs.debian.org/cgi-bin/bugrepo ... bug=754076
After upgrading to UP 2014.10.15, /tmp is a link to /var/tmp and that causes some problems.
.
Portfolio
http://500px.com/Orbmiser
Flickr
http://www.flickr.com/photos/orb9220/
SolydK - Kernel 3.16-2-amd64 - KDE 4.14.1 Update Pack: 2014.10.15
http://500px.com/Orbmiser
Flickr
http://www.flickr.com/photos/orb9220/
SolydK - Kernel 3.16-2-amd64 - KDE 4.14.1 Update Pack: 2014.10.15
Re: UP 2014.10.15
this is the key of these problems (not only yours but also Orb's)dali wrote:
EDIT: I'm probably responsible for linking /tmp to /var/tmp, I've upgraded two other machines without this issue. The only machine with this problem has an SSD and I usually redirect /tmp to tmpfs in fstab to spare the SSD from unnecessary wear, but I was probably lazy and just linked it to /var/tmp ... and forgot about it ...
that symlink was removed with the July UP [the discussion starts here http://forums.solydxk.nl/viewtopic.php? ... tmp#p39002 if you are interested]
and all the isos published after that have that symlink removed.
Orb
what is the output of
Code: Select all
ls -lA /varbliss of ignorance
Re: UP 2014.10.15
That sure looks like the same problem that I had. It isn't necessarily related to SSD:s.Orbmiser wrote:Code: Select all
orbmiser@winterfell ~ $ sudo journalctl -b _PID=1679 -- Logs begin at Thu 2014-10-16 11:23:07 PDT, end at Thu 2014-10-16 11:57:43 PDT. -- Oct 16 11:45:45 winterfell systemd[1679]: Failed at step NAMESPACE spawning /usr/lib/rtkit/rtkit-daemon: Operation not lines 1-2/2 (END)But don't have SSD just plain old Sata & a IDE hardrives.Maybe something mentioned by by dali
I've also had problems with rtkit, had this in the logs:
systemd[...]: Failed at step NAMESPACE spawning /usr/lib/rtkit/rtkit-daemon: Operation not permitted
Some googling led me to this: https://bugs.debian.org/cgi-bin/bugrepo ... bug=754076
After upgrading to UP 2014.10.15, /tmp is a link to /var/tmp and that causes some problems.
Check if /tmp is a link, run this:
Code: Select all
file /tmp
Code: Select all
sudo rm /tmp
sudo mkdir /tmp
Re: UP 2014.10.15
Ah, that explains it. I've found the symlink on two of my three machines, the one without was probably installed using a later ISO.zerozero wrote: this is the key of these problems (not only yours but also Orb's)
that symlink was removed with the July UP [the discussion starts here http://forums.solydxk.nl/viewtopic.php? ... tmp#p39002 if you are interested]
and all the isos published after that have that symlink removed.
-
freecicero
- Posts: 41
- Joined: 29 Jun 2014 19:23
Re: UP 2014.10.15
Perhaps this was never a good idea in the first place, but in my Solydx installation I had installed Dolphin to use for file work. All seemed to work and co-exist fine.
This update on most (but not all) of my machines has resulted in all the kde programs being removed. One or two machines seem to be still ok, but on most the update deleted the kde programs.
I am not sure how to go about dealing with this. Going to synaptic and marking dolphin and hoping it will load all base items that are needed results in a "broken package" message that will not let me proceed.
apt install dolphin gives me a list of unmet dependencies which I suppose I could go through and install til it lets me install dolphin.
Am I really messing up Solydx by installing Dolphin? I don't mind the disk space loss for things I don't need - I just don't want to mess up the system.
If I try to proceed, what is the best way to get dolphin installed for use on a XFCE desktop without making KDE the desktop?
thanks!
This update on most (but not all) of my machines has resulted in all the kde programs being removed. One or two machines seem to be still ok, but on most the update deleted the kde programs.
I am not sure how to go about dealing with this. Going to synaptic and marking dolphin and hoping it will load all base items that are needed results in a "broken package" message that will not let me proceed.
apt install dolphin gives me a list of unmet dependencies which I suppose I could go through and install til it lets me install dolphin.
Am I really messing up Solydx by installing Dolphin? I don't mind the disk space loss for things I don't need - I just don't want to mess up the system.
If I try to proceed, what is the best way to get dolphin installed for use on a XFCE desktop without making KDE the desktop?
thanks!
Who is online
Users browsing this forum: Bing [Bot] and 1 guest
