Re: no console with radeon + kernel mode setting?
Giacomo Mulas <[email protected]>
| Newsgroups | gmane.linux.debian.ports.amd64 |
|---|---|
| Message-ID | <alpine.DEB.2.02.1111301027340.29204@capitanata.oa-cagliari.inaf.it> |
On Tue, 29 Nov 2011, victor curtis wrote: > If you can get to the command prompt login, use startx to activate the > x-server, that should automatically start gnome as well. if startx doesn't > activate gnome, > > startx gnome-session should do it. > > If you don't have an attachment to the graphical login screen, go to main > menue/system/administration/services and disable the GDM (if you can even > find that in gnome3) that should solve the problem, and enable login as > root. Hi Victor, thanks for your answer, but unfortunately it does not help much. I probably did not explain my problem properly, or you misunderstood. I have no problem logging into gnome (or any other X session) through the graphical login manager, be it gdm, kdm, xdm... X works all right. My problem is that the text console disappears very early in the boot sequence, namely as soon as the [drm] console messages say that kernel mode setting is being enabled, when using the free radeon driver (autodetected and loaded as a kernel module). When that happens, the screen goes blank, and stays blank until the boot sequence reaches the graphical login manager, and fires up X. Then the screen goes through a brief flashing of bright, random colours slowly fading one into another (nice to watch, I admit), afterwards X starts fine, as does the login manager and anything I want to run on X. But if I try to use the text console (e.g. using ctrl-alt-f1) nothing is displayed. I can even login into the text console (blindly) and blindly run commands, which do work, but no console display. This is not nice, since the console is my last line of defense for cases in which some update goes wrong and I have to fix things (not so frequent, but hey, I'm running sid, sometimes it happens, it's called "unstable" for some reason...). Moreover, since the console goes blank so early in the boot sequence, I cannot even boot in single user mode: it ends up with a blank console, and unless I can run all commands I need blindly, it's obviously useless. Hoping I made the problem clearer: any suggestions? Bye Giacomo -- _________________________________________________________________ Giacomo Mulas <[email protected]> _________________________________________________________________ OSSERVATORIO ASTRONOMICO DI CAGLIARI Str. 54, Loc. Poggio dei Pini * 09012 Capoterra (CA) Tel. (OAC): +39 070 71180 248 Fax : +39 070 71180 222 Tel. (UNICA): +39 070 675 4916 _________________________________________________________________ "When the storms are raging around you, stay right where you are" (Freddy Mercury) _________________________________________________________________ -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.