issues after recent update to kernel 3.15.3-1-ARCH cannot start kde/X

chuckiv · 2014-07-04 07:11:04

did my typical pacman -Syu today and there was a kernel update and lots of xorg packages update
kernel 3.15.3-1-ARCH
now machine wont start
cntrl alt f1 got me to terminal i saw somewhere that quiet in kernel param could be an issue so i removed it from arch.conf and that got me farther in the boot process but hangs still
kdm.service is running
Xorg.0.log shows this
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
No devices detected
No screens found
all my google searches end up in nvidia threads
I am using generic intel drivers
Any ideas? When I was installing I remember making some customizations, like adding quiet to arch.conf, which i have now had to undo
I also recall adding some i915 stuff somewhere but I dont remember exactly. I'm so lost now

/etc/mkinitcpio.conf
has modules="i915"
hooks="base udev autodetect modconf block filesystems keyboard fsck"
also from intel page
/etc/modprobe.d/i915.conf
options i915 enable_rc6=7 enable_fbc=1 lvds_downclock=1
boot hangs on [OK] Reached target Graphical Interface
with blinking cursor, no prompt, must do ctrl alt f1 to get prompt
everything was working great until today's updates

efivar -l says command not found which i think is weird
startx says command not found as well
none of this was like this before update, i know i have X installed and startx should be a recognizable command

I do not have an xorg.conf
sudo find / -name xorg.conf
returns nothing

jasonwryan · 2014-07-04 07:14:50

This is your third shot at this: better make it count...

Chroot in and look through pacman's log, see what was updated. Then work out why you don't have startx any more.

chuckiv · 2014-07-04 07:24:00

iirc i think i used kdm.service to start kde and never installed xinit.

this was a method suggested by the installation guide i think bc systemd can do it instead of xinit

probably explains why i dont have a xorg.conf file and never did

but my system was working fine this way until xorg updates today, not sure how to even begin figuring out what the heck happened

well this is weird, a reboot gives a new error

Failed to start Verify integrity of password and group files

pacman.log shows that shadow was updated

im guessing the update cleared my saved password as I had my computer to auto-login

now what?

Last edited by chuckiv (2014-07-04 07:44:02)

Kartious · 2014-07-04 07:46:07

Did you end up doing what Polks asked you to do in the previous thread to do with downgrading packages? Usually breakage after upgrading normally makes me look into the the pacman logs and seeing what packages to downgrade. You may want to consider any config files that could of been replaced during the update process.

polks wrote:

You can edit your first post to update you know
Try commenting out xorg.conf completely, if it fails downgrade xorg* and xf86* and linux*

chuckiv · 2014-07-04 07:53:28

chuckiv wrote:

iirc i think i used kdm.service to start kde and never installed xinit.
this was a method suggested by the installation guide i think bc systemd can do it instead of xinit
probably explains why i dont have a xorg.conf file and never did

chuckiv wrote:

a reboot gives a new error
Failed to start Verify integrity of password and group files
pacman.log shows that shadow was updated
im guessing the update cleared my saved password as I had my computer to auto-login
now what?

sigh... yes.. please read post before trying to answer. I do not have an xorg.conf and I have checked my pacman log

thanks anyways though, I appreciate the attempt

is there a way to reset kdm to default so it doesnt try to auto-login with failed password and instead prompts me with the default login screen?

perhaps I should move to kde forum now?

well, it gets more confusing, another reboot and this time it doesnt complain about shadow. now I am super confused. I get different results on different boots and I'm not changing things....

edited kdmrc file changed autologin=true to false, problem persists

also, I cant downgrade bc I can't resolve hosts. I cant even ping google but wifi-menu tells me that I am connected. It says ping: unknown host www.google.com

I have never been in this situation before, I always talk about how stable Arch is.... this really sucks

cant install xorg-xinit to try to startx the old fashioned way. kdm.service is up and running with no errors for kdm but then reports

X server died during startup
X server for display :0 cannot be started, session disabled

downgrade says command not found and I have installed downgrade. efivar -l also says command not found. something very weird is going on

Last edited by chuckiv (2014-07-04 08:17:24)

chuckiv · 2014-07-04 08:31:23

yup it was the kernel I used gummiboot to load older one and all is well. I wonder why the new kernel completely messed up, still have no answers

berbae · 2014-07-04 09:18:52

chuckiv wrote:

well, it gets more confusing, another reboot and this time it doesnt complain about shadow

This is because the control is made once a day by the daily systemd shadow.timer.
I don't think you lost your passwords, if you have not merged blindly the /etc/shadow file with the .pacnew created by pacman (don't do that, if you have not done it).
There are other threads about the filesystem package upgrade to manage the .pacnew files of /etc/passwd, /etc/group and /etc/shadow.

edited kdmrc file changed autologin=true to false, problem persists

So the problem is not there.

I cant downgrade bc I can't resolve hosts

If you didn't clear the pacman cache, you still should have previous versions of your packages there.
Not the best way, but you can try to downgrade all the packages which were upgraded, to regain a quieter state of mind at the moment.

kdm.service is up and running with no errors for kdm but then reports
X server died during startup
X server for display :0 cannot be started, session disabled

I think the main problem is there, not kdm, but xorg server or intel graphical driver.
Post the /var/log/Xorg.0.log file.

Try to keep calm and look at one problem at a time; the shadow warning should not prevent you from logging in, if you didn't merge any packages with the .pacnew files; so you can concentrate on the other graphical problem first.
Also post the entire list of the upgraded packages.
Have courage to face what sometimes happens with bleeding edge Arch Linux...

Arch Linux

#1 2014-07-04 07:11:04

issues after recent update to kernel 3.15.3-1-ARCH cannot start kde/X

#2 2014-07-04 07:14:50

Re: issues after recent update to kernel 3.15.3-1-ARCH cannot start kde/X

#3 2014-07-04 07:24:00

Re: issues after recent update to kernel 3.15.3-1-ARCH cannot start kde/X

#4 2014-07-04 07:46:07

Re: issues after recent update to kernel 3.15.3-1-ARCH cannot start kde/X

#5 2014-07-04 07:53:28

Re: issues after recent update to kernel 3.15.3-1-ARCH cannot start kde/X

#6 2014-07-04 08:31:23

Re: issues after recent update to kernel 3.15.3-1-ARCH cannot start kde/X

#7 2014-07-04 09:18:52

Re: issues after recent update to kernel 3.15.3-1-ARCH cannot start kde/X

Board footer