You are not logged in.
I am using the catalyst total 12.9-1 driver from AUR
I am not sure what caused this but I updated my system after a long time and the first couple reboots where fine.
The issue now is that when I try to reboot, X seems to close normaly and then my screen is stuck on the startup screen of archlinux (the one before we login that shows that everything is starting). The system does never shut down and I have to do it manually.
This behavior is also noticed when I try to switch to tty from my X session. Whenever I try it I am stuck on the same screen as described above. Now it seems that I can login to the tty and do stuff there but there is no display in my monitor of what I am doing, just the stupid start up screen. I am noticing some frames though that pop very fast indicating there is something below this "layer of graphics".
There is also another symptom. Normally when I boot arch the startup screen is on very low resolution and stays so until I start X. Since this issue appeared the start up screen is in the beggining at low resolution and after a certain point the resolution becomes perfect (1920x1200). Now this happens to me a lot when I do stuff with the catalyst driver and it usually indicates that something is going terribly wrong and thats why I am posting it as a symptom. My normal behavior is for the resolution to be low on the start up screen.
Since I don't know what else to give you guys to figure wth is going on, I'll just write what I did after I updated my system although I dont think they are of much help:
- I changed my gtk and openbox theme
- I tried to run World of Warcraft (game) with wine, failed miserably. After I did that I couldn't start any game (like HON) and I had to reboot. After that games where fine.
- I installed Xbmc (A media center for those who don't know) . Now XBMC was working fine at the beggining but after some point when I started it the loggo popped up and It stuck there for ages doing nothing. I couldn't close the window or kill the proccess. It just sat there.
Now my X is working fine, flash is working fine and I can play games. But still cant reboot (or shutdown ofc). I reinstalled the catalyst driver with no success. Any clues for my mess?
Thanks in advance
Edit: I am not using any login managers. I also have a dual screen setup.
Last edited by Crone (2012-10-18 16:55:19)
Offline
There is also another symptom. Normally when I boot arch the startup screen is on very low resolution and stays so until I start X. Since this issue appeared the start up screen is in the beggining at low resolution and after a certain point the resolution becomes perfect (1920x1200). Now this happens to me a lot when I do stuff with the catalyst driver and it usually indicates that something is going terribly wrong and thats why I am posting it as a symptom. My normal behavior is for the resolution to be low on the start up screen.
This suggests KMS might be started on your system, and catalyst doesn't support KMS at all.
A workaround to make sure KMS is disabled is to boot with nomodeset on the kernel line.
Please post your mkinitcpio.conf .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Hmm it looks intact. I remember editing this file at some point though. Here it is
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES=""
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run first, so it may be used to
# override the actual binaries used in a given hook.
# (Existing files are NOT overwritten if already added)
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options
# like so:
# FILES="/etc/modprobe.d/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
#
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS="base udev autodetect pata scsi sata filesystems"
#
## This is identical to the above, except the old ide subsystem is
## used for IDE devices instead of the new pata subsystem.
# HOOKS="base udev autodetect ide scsi sata filesystems"
#
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS="base udev pata scsi sata usb filesystems"
#
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS="base udev pata mdadm encrypt filesystems"
#
## This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
#
## NOTE: If you have /usr on a separate partition, you MUST include the
# fsck and shutdown hooks.
HOOKS="base udev autodetect pata scsi sata filesystems usbinput fsck fglrx"
# COMPRESSION
# Use this to compress the initramfs image. With kernels earlier than
# 2.6.30, only gzip is supported, which is also the default. Newer kernels
# support gzip, bzip2 and lzma. Kernels 2.6.38 and later support xz
# compression.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""Offline
## NOTE: If you have /usr on a separate partition, you MUST include the
# fsck and shutdown hooks.
Check if your /usr is on a separate partition, that change happened this year i think.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
I am pretty sure I have a /usr partition how do I verify it though?
fdisk -l doesn't help
Edit: Nvm it was df, I in fact do not have a user partition
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 24027628 8724616 14082476 39% /
dev 1990164 0 1990164 0% /dev
run 2026052 412 2025640 1% /run
/dev/sda6 24027628 8724616 14082476 39% /
shm 2026052 0 2026052 0% /dev/shm
tmpfs 2026052 12 2026040 1% /tmp
/dev/sda2 781249996 527166640 254083356 68% /mnt/windows
/dev/sda5 101086 20784 75083 22% /boot
/dev/sda7 9614116 5867724 3258020 65% /var
/dev/sda9 157633360 63730760 85895280 43% /homeLast edited by Crone (2012-10-18 13:42:17)
Offline
I apparently solved the issue by simply rebuilding initframs. I suspect wine did something bad with KMS settings but I'm not sure yet. Anyway marked as solved.
Reference for those with similar issue: https://wiki.archlinux.org/index.php/AT … ooting_KMS
Thanks a lot for the input
Last edited by Crone (2012-10-18 16:56:22)
Offline