You are not logged in.
Hi there,
I've been a happy arch user for about 6 months now! However I'm now having a problem where my machine can't seem to run xorg without crashing horribly with no errors!
I think it's not a graphics card driver problem because I switched from radeon to catalyst and the same thing happens.
Here's some config files and command outputs from _before_ I run startx:
Xorg.conf:
https://gist.github.com/5f694287f744fc295a78
lspci:
https://gist.github.com/3d4e844d1709cd131fb9
dmesg | grep fglrx:
https://gist.github.com/05255baef2b771bb1415
/var/log/Xorg.o.log is empty after a reboot once I've attempted to startx and it's failed.
After speaking to someone on IRC, I was advised to attempt to read the xorg by SSH'ing into my machine while running startx. Unfortunately tail -f returns nothing. I can see from running top, however, that xorg runs at 100% CPU.
Any advice on how I can fix this would be really appreciated!
Last edited by s0l1dsnak3123 (2012-12-06 17:53:35)
Offline
try removing xorg.conf
Offline
Hey there,
Since posting this I've removed both the open source "radeon" and the proprietary "fglrx" drivers, and I've managed to get xorg to start with VESA.
However, after re-installing the "radeon" driver, I can't seem to get Xorg to start with it.
Edit: a bit more info - after some wrangling I'm now at the point where I have managed to get radeon to run within xorg, but when I run startx I get:
(II) [KMS] drm report modesetting ism't supported.This error happens when I have nomodeset in my kernel params and when I don't.
Full Xorg.0.log:
https://gist.github.com/726fb8bc6e6810b13442
Last edited by s0l1dsnak3123 (2012-12-06 21:35:05)
Offline
[ 831.264] (==) Using config file: "/etc/X11/xorg.conf"
[ 831.280] (==) Using config directory: "/etc/X11/xorg.conf.d"Looks like you're still using an xorg.conf file, and chances are the problem is in that file.
As pajaro suggested , rename or remove xorg.conf , and run startx WITHOUT any xorg.conf file .
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
Hey, thanks for the response.
I was actually using a minimal xorg.conf to force the radeon driver to run. When I remove it, it drops down to VESA.
Here's the xorg.0.conf after running startx and dropping down to VESA https://gist.github.com/44203c39ecde439da96a
Edit: And if I uninstall VESA and run startx I get this: https://gist.github.com/14c770b242bedd0f83c8
Last edited by s0l1dsnak3123 (2012-12-07 13:05:35)
Offline
thanks, now atleast we're sure the problem is not due to xorg.conf .
It's possible that you didn't make the switch from catalyst to radeon correctly.
run
$ lsmod |grep radeon.
the output should look like similar to this :
$ lsmod |grep radeon
radeon 859719 2
i2c_algo_bit 5392 1 radeon
drm_kms_helper 32878 1 radeon
ttm 64385 1 radeon
drm 218903 4 ttm,drm_kms_helper,radeon
i2c_core 20708 5 drm,drm_kms_helper,i2c_algo_bit,radeon,i2c_nforce2If the radeon or drm_kms_helper modules are absent, try running modprobe radeon manually (as root) and then test startx again.
If that solves the problem check the archlinux ati wiki page , kernel mode setting and verify early or late start are configured correctly.
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
Hey there, thanks for such a quick reply!
Yes, lsmod doesn't show the radeon driver, however when I modprobe it, I'm met with this: https://gist.github.com/c63e596eba8f8274554d
Last edited by s0l1dsnak3123 (2012-12-07 13:21:17)
Offline
atleast x now sees the kernel module, as it loads the ati module .
What is the output of dmesg | tail after manually modprobing the radeon kernel message ?
Also check if you have vga= on your kernel line, that can have the same effect as nomodeset wrt disabling KMS.
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
It doesn't show any errors! I'm not using vga= on my kernel line. I made doubly sure I wasn't using nomodeset as well:
https://gist.github.com/7601333dafcd7c8ad09d
Offline
Any ideas? I'm very stuck!
Offline
ok, use the instructions on the wiki for KMS early start , then reboot .
if startx doesn't behave then, we'll probably need the entire kernel.log .
(hope you're still using syslog-ng ).
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
Yep, I get a black screen on boot unless I add nomodeset to the kernel line in grub.
I've not got syslog-ng installed, will need to set it up before I can give you the kernel.log!
Offline
Ok, so while the sceen is black, the system also freezes before it gets to the point where it connects to the internet, so I can't debug the machine over SSH. However after rebooting again with nomodeset and looking at kernel.log, I see messages about fglrx (!) even though I uninstalled it: https://gist.github.com/be0dc9b3aa7f369b4457
Offline
yep, that logs celarly shows fglrx kernel module is still loaded.
check the folder /etc/modules-load.d/ , maybe there's something left over there that loads fglrx automatically .
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
There was nothing in that directory, but I found some fglrx.ko files in /lib/modules and I deleted them. Kernel.log no longer mentions fglrx, but even now I still get a black screen. However I did find where the fglrx.ko was coming from - I had another package called catalyst-dkms installed (I only found it because I removed dkms and it depended on it) - I thought I'd removed all catalyst stuff (I used the list on the wiki to remove everything), but apparently I'd missed that one.
I then tried removing radeon from mkinitcpio.conf and running modprobe drm; modprobe radeon from the terminal, but I end up in VESA mode again. I still can't get to the prompt without nomodeset or radeon.modeset=0!
Last edited by s0l1dsnak3123 (2012-12-09 17:57:41)
Offline
I then tried removing radeon from mkinitcpio.conf and running modprobe drm; modprobe radeon from the terminal, but I end up in VESA mode again. I still can't get to the prompt without nomodeset or radeon.modeset=0!
Well, if you boot with nomodeset or radeon.modeset=0 , that effectively disables KMS entirely, and thus X can't use the radeon driver and falls back to other options like vesa.
for clarity : if you boot without nomodeset or radeon.modeset=0 on the kernel line, you don't get a console login ?
If that's the case, then the problem is in the early boot that happens BEFORE the login is shown.
remove the nomodeset options from the kernel line, and add systemd.unit=multi-user.target
(last is to make sure the graphical target is NOT started).
Then boot and watch the messages from systemd boot carefully for errors.
Last edited by Lone_Wolf (2012-12-10 12:38:32)
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
Hey,
I actually start my graphical target by myself with startx after logging into a TTY - I checked to see if there was anything in systemd named "graphical" but couldn't find anything. I've enabled multi-user target. /etc/systemd looks like this: https://gist.github.com/0860b077c6f58df8697f It doesn't make a difference though, I still get a black screen, and no visible errors coming from systemd's boot message (I don't have quiet enabled).
To be clear, the black screen happens prematurely - I never even see the TTY prompt to login and run startx with - it seems to happen halfway through the bootup process.
Last edited by s0l1dsnak3123 (2012-12-10 12:53:52)
Offline
that makes very clear the problem is on a low level, close to the hardware.
boot without nomodeset options, do nothing for 10 minutes (sometimes parts of the boot need a long time before sending a fail message).
then reboot with nomodeset , and post the everything.log for the boot without nomodeset.
We'll have to go through that log with a fine comb.
Note : i'm not well versed in systemd journalctl yet, if someone knows how to get systemd to display detailed boot info that's ofcourse also usable.
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
So I left my machine in that state a longer than anticipated, but I'm pretty sure there is nothing in the logs because syslog isn't being initialised early enough in the boot?
Here's the everything.log anyway! https://raw.github.com/gist/cee508ea822 … ything.log
Offline
there are entries in the log where you booted without nomodeset , so there is info .
Ypur system appears to be a laptop with an intel core i5 processor and an amd videocard .
best post the output of lspci so we can find out more detaisl about the harware, like whether there's also intel graphics present.
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
My machine is a 27" iMac (hence why it looks like a laptop). Here's lspci: https://gist.github.com/555c9e7e6fec8e8ad25e
Offline
So only 1 videocard present,
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Blackcomb [Radeon HD 6900M series]At this point i get the feeling the system is NOT crashing/hanging when you start with KMS, but sends the video signals to the wrong output.
with KMS disabled the right output is chosen, but then xorg won't work with the radeon driver.
I think the iMac has a built-in screen ?
best run xrandr to see how many and which screen outputs are seen by xorg.
If there are external video outputs you could try connecting a screen to those to see if that does show output when booting with KMS.
If my feeling is confirmed, we'll have to think of a way to figure out the cause.
Could be there are still leftovers from fglrx, but could also be a problem between kernel/KMS and the iMac hardware.
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
Sounds like a plan! I'm not going to be home until Friday, but I'll check it out on friday night and let you know if that fixes it ![]()
Offline
Sorry for the late response - I did some more digging around, eventually tried running an OSX boot CD and the same thing happened, making me think it's a hardware fault. It's going back to the Apple store to get fixed, then probably sold and I'll just build a new machine instead ![]()
Thanks for all the help!
JH
Offline
I found this thread while trying to solve a similar problem getting Ubuntu 12.04 to work on a MacMini 5,1 (Mid 2011) system.
Adding "nomodeset" (or equivalent) is necessary to avoid the use of KMS, which is only a problem for boot. I believe you can unload and then load the radeon module after boot and give it "modeset=1" to turn it on again. I'm not sure if that would work or not (probably wouldn't). More importantly, I don't think it matters. Here's more info on that: http://www.x.org/wiki/radeonBuildHowTo# … KMS_issues
Anyway, I found this documentation helpful: https://help.ubuntu.com/community/UEFIB … ding_Linux
If it is correct, then you may need to use the "dd" commands mentioned to create BIOS image files. As the document mentions, this may be necessary for X drivers that are coded to read the BIOS for system information. Since a Mac doesn't have a BIOS, you need to a create a fake one and tell GRUB to load it at boot time ("loadbios" directive in the GRUB config). Hopefully, that gets radeon (or vesa) to stop complaining about it and move on to actually starting up X.
Last edited by LinuxLuser (2013-05-21 18:41:53)
Offline