You are not logged in.
Hello
I have just done a pacman -Syu : my system now won't boot into X. It's clearly trying to ---- the monitor looks as though it is trying to find the correct "mode" ie the screen is a patchwork of lines of colours. Normally I log in via gdm.
My video card is an Intel.
I can't access a tty!
Any ideas?
PS I have a sort of square "shadow" mouse on screen.
Last edited by esteeven (2011-04-11 16:35:44)
Offline
My hardware has not failed. I have booted using a live Ubuntu CD without issues.
Last edited by esteeven (2011-04-11 16:44:51)
Offline
What does Xorg.0.log tell you?
Offline
What does Xorg.0.log tell you?
I can't get to it. The system is inaccessible (to me!) I tried editing /etc/rc.conf to remove gdm via Ubuntu but the boot effect was the same. I may boot using Ubuntu again and remove my xorg.conf to see what that does. Not sure what else to try.
Offline
Well. That didn't help. Same issue.
Offline
Why don't you use your ubuntu Live CD to get access to Xorg.0.log?
Offline
Why don't you use your ubuntu Live CD to get access to Xorg.0.log?
Fair point but if the same error occurs with no X ie gdm isn't in my daemons array, isn't the issue somewhere else? Problem is, I don't know where
Offline
Boot into a console and look through pacman's log to see what packages were upgraded - that will at least give you a starting point for correctly diagnosing your issue...
You could then try selectively downgrading any of the obvious ones.
Offline
You could then try selectively downgrading any of the obvious ones.
Good idea but how can I do that if I can't actually log in to my Arch install?
Offline
Did you try a ctrl-alt-F1 to get to a tty and login from there?
Offline
Switch your run level:
Offline
Hmmmm! Appending 1 in grub to boot in to run level 1 still gives the same error.
Offline
You have hit a DRM bug most likely and downgrading the kernel should fix it. For the record, you can access your Arch installation from Ubuntu by doing "chroot /mount/point/of/arch"
Offline
Okay. I will try to chroot to my Arch install and then downgrade my kernel (or whatever was upgraded at my last pacman -Syu) Could I achieve a rescue by waiting and then doing pacman -Syu from the chrooted environment in a few days?
Offline
Oh I almost forgot: you can probably boot into your Arch install (but X may not work) with i915.modeset=0 on the kernel line.
And it's possible that an upgrade will fix it, but if I were you I'd downgrade to get a usable system and then report the bug (to the kernel).
Offline
nope. this left me with the same issue.
Offline
I am all for downgrading the kernel but I am one of those idiot new Arch users that did pacman -Scc (because I could?) and don't have a local package to install. I tried to install the lts kernel from my chrooted environment but this failed.
Offline
Check the wiki
Offline
I am reading the wiki but there is something I don't understand. "pacman -S kernel-lts" should install the LTS kernel. I was unable to do this from the chrooted environment - something to do with /dev/null and permissions. Will I not hit the same issue if I find an earlier kernel on an out of sync mirror. How do I get past this?
Offline
Try it with arch linux cd instead od ubuntu liveCD.
Offline
You'll want to mount the special file systems before you chroot. See https://wiki.archlinux.org/index.php/Chroot
Offline
Try it with arch linux cd instead od ubuntu liveCD.
Is that with a normal arch install cd or some live cd?
Offline
The Arch Linux installation discs *are* live CDs.
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
The Arch Linux installation discs *are* live CDs.
I have just found that out.
"pacman -S kernel26-lts" sorted the issue. Clearly, kernel 2.6.38 was causing the problem. I'll stick with LTS for now -- unless someone tells me why this is a bad idea. Otherwise, I'll hunt down 2.6.37
Thanks for all of your help.
Offline
There's something to diagnosing your problem and not being able to solve it, and resorting to a workaround. But you didn't even diagnose your problem. People told you repeatedly to check your logs. Please do that. If you want to run Arch, you need to be able to fix your problems - or learn how to do it.
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline