FS#32030 - [systemd] Screen goes crazy

Attached to Project: Arch Linux
Opened by Linas (Linas) - Wednesday, 17 October 2012, 14:21 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 20 October 2012, 19:53 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Dave Reisner (falconindy)
Tom Gundersen (tomegun)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Installing systemd makes the screen unusable after the "Waiting for udev events" message. Looks like on enabling KMS it is set to an unsupported mode/resolution.
This happens for the console, *without* even running xserver. Not even the end of loading is viewable, which makes the system unusable (well, you can login from ssh...). It fails just with installing systemd package, ie. without adding init=/usr/lib/systemd/systemd

This not only happens with modern systemd 194-3 but also with older ones such as 189-4. Using libsystemd (188-2) and systemd-tools (188-2) work.
This task depends upon

Closed by  Dave Reisner (falconindy)
Saturday, 20 October 2012, 19:53 GMT
Reason for closing:  Deferred
Additional comments about closing:  Please reopen if you can reproduce on an up to date system.
Comment by Alexander F. Rødseth (xyproto) - Wednesday, 17 October 2012, 15:17 GMT
Thanks for reporting, but more information is needed to be able to figure out what the reason for this may be. Please see https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines.
Which graphics card do you have? Which kernel version? Is this on 32-bit or 64-bit? What are your boot options? Can this be reproduced by just installing systemd and then rebooting? What do you mean by crazy, does the screen go black?
Comment by Linas (Linas) - Wednesday, 17 October 2012, 17:15 GMT
The kernel command line is: root=xyz ro noapic radeon.no_wb=1 security=yama memmap=abcd
That's an ATI Radeon. There used to be some problems with KMS, which is why upstream asked to add radeon.no_wb (cf  FS#23422 )

It's basically an 64 bits Arch kernel (3.4.3-1) with pax patches. It's not state of the art but I got some conflicts with the /lib move so I didn't touch it or the kernel since. I need to fix that, eventually. This same kernel works fine with the earlier libsystemd.

Yes, just installing systemd (removes libsystemd and systemd-tools) and rebooting reproduces it. I then need to connect through ssh in order to downgrade to the earlier versions.

No, if the screen went black I would have said black :)
I am aware 'crazy' is not a good description but I don't know how to express it better. It's the kind of dizzy moving lines you could get if you configured a resolution out of the limits of the screen.
Comment by Dave Reisner (falconindy) - Wednesday, 17 October 2012, 17:23 GMT
There's little I'm willing to do if you can't upgrade to the latest versions and reproduce this with the newest ARCH kernel.
Comment by Linas (Linas) - Wednesday, 17 October 2012, 20:45 GMT
Will the newest ARCH kernel install and boot correctly if /lib is not a symlink to usr/lib? I'm in a little chicken-and-egg problem with /lib holding files of the existing kernel.
Comment by Dave Reisner (falconindy) - Wednesday, 17 October 2012, 20:54 GMT
You can assume that Arch userspace will not function correctly without /lib being a symlink. You've compounded your problems by avoiding this upgrade.
Comment by Alexander F. Rødseth (xyproto) - Thursday, 18 October 2012, 15:49 GMT
Does it work if you upgrade all packages to the latest versions?

Loading...