You are not logged in.
Pages: 1
Hey,
since recently, without changing anything (did no package updates etc. before it occurred), 2 problems started to happen to my system.
1. When booting and the console comes up with all the lines and the last line "Reached Target Graphical Interface" appears, my system hangs for over a minute before it gets black and the login manager appears. Also somewhere after 40 seconds the blinking cursor freezes.
2. Every time I boot up and log into my xfce system, I have no sound at first. What I do so far and which works is, to plug out the HDMI cable to my receiver and plug it back in. After doing so the monitor turns black for 1ms and back on and then I have sound (it turns black because I mirror the output of my TV and PC so that I have sound from the speakers, which are connected to my receiver).
And this is the current situation. BEFORE that, whenever I logged in, the sound was not flawless and "stuttered" (like no sound, sound, no sound, sound) and then at some point completely turned off until I plugged the cable out and back in again. This phenomenon now also happens, when I am already logged in and for example turn off the receiver and turn it back on. Again, this is solved when I plug out and back in again. I doubt that the cable is damaged because it's rather new (from December) and after plugging it back in it works flawlessly.
Last edited by someguy (2017-03-19 12:29:11)
Offline
You seem to have two, completely separate and independent issues. In the future, I would put them each in there own thread, AFTER having researched both problems thoroughly. Do not make extra topics at this time though, as that would now be cross posting.
First, it is always a good idea to update your system completely before posting. If *after* updating you still have regressions, that's its own issue which can be troubleshooted. Now, for your kernel, can we have some journal outputs and logs? Remember to use code tags! Reboot, and the post back the following:
journalctl -b -p3
dmesg | tail -n10
cat .local/share/xorg/Xorg.0.logPlease consider using a pastebin service for these. I recommend sprunge.us as a command line pastebin.\
For your HDMI, what sound server (Pulse, ALSA, OSS) are you using? Have you made any configuration changes? Are you doing anything with xrandr for the multiple displays? If you leave the cable plugged in, and then reboot, do you have any/the same problems? We'll need quite a bit of diagnostic information be continuing. ![]()
I am diagnosed with bipolar disorder. As it turns out, what I thought was my greatest weakness is now my greatest strength.
Everyday, I make a conscious choice to overcome my challenges and my problems. It's not easy, but its better than the alternative...
Offline
Thanks for helping ![]()
Issue #1:
I know what you mean. I posted these two issues because they appeared at, as far as I can tell, the same time so I thought MAYBE they are related, so sorry if it does not look like that.
And I updated my system afterwards, I just wanted to point out that these issues appeared not after an update but just like that.
journalctl -b -p3: http://sprunge.us/fhZC
dmesg | tail -n10: http://sprunge.us/VeeQ
cat .local/share/xorg/Xorg.0.log: http://sprunge.us/LbDg
Issue #2:
During the initial install of arch I installed the alsa-utils and didn't fiddle around really except I disabled AC3/DTS in the output device configuration in the PulseAudio mixer. And I listen to some stuff via headphones instead of the speakers but that's about it. Haven't done anything with xrandr. And yes, the cable is always plugged in so the problem then still persists.
Last edited by someguy (2017-03-19 15:52:15)
Offline
You seem to have a lot of issues. Why is gnome-shell dumping the core? Why can't you start X?? <- If these are actual problems, you'll need a new thread for those. To the issues at hand here which are HDMI and possibly kernel, your dmesg output gives us a clue:
[ 89.387870] snd_hda_codec_hdmi hdaudioC2D0: HDMI: invalid ELD data byte 49I'm going google that error (recommend you do the same) and see if we can at least solve one of potentially four separate issues. ![]()
EDIT: What is the output of lspci -k? You may also want to try running grep -C1 HDMI to look for more HDMI errors in dmesg.
EDIT 2: For the long boot times as per the title, run systemd-analyze blame and it will tell you whats hogging your boot process. See the wiki for more information on that one. ![]()
Last edited by JohnBobSmith (2017-03-19 17:50:45)
I am diagnosed with bipolar disorder. As it turns out, what I thought was my greatest weakness is now my greatest strength.
Everyday, I make a conscious choice to overcome my challenges and my problems. It's not easy, but its better than the alternative...
Offline
Yes I'm afraid so but like you said, these other things won't fit in here and don't have priority (I think, haha).
lspci -k: http://sprunge.us/fNDC
And filtering via dmesg | grep -C1 HDMI results in http://sprunge.us/SjLi
It seems that the top process are
50.176s user@1000.service
8.095s dhcpcd@enp0s25.service
221ms systemd-hostnamed.serviceSo I'll look into the top one, whatever it is or rather why it takes so long ![]()
Last edited by someguy (2017-03-19 18:08:26)
Offline
Pages: 1