Bug 2803

Summary: ctrl+alt+f1 = black screen
Product: Mageia Reporter: luca pedrielli <luca.pedrielli>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: Normal CC: dmorganec, mageia, mageia
Version: Cauldron   
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: systemd ? CVE:
Status comment:
Bug Depends on:    
Bug Blocks: 2120    

Description luca pedrielli 2011-09-21 20:01:44 CEST 
Description of problem:


i'm running mageia in virtualbox.

when i try to switch to a tty with ctrl+alt+F1/2/3.. the result is only a black screen.

but if i start mageia with linux-nofb i have my tty.

also if i start the sistem with init 3 mode and start dm with init 5 i have my ttys.
Comment 1 Manuel Hiebel 2011-09-21 20:22:06 CEST 
maybe it's related to plymouth/systemd.

On Mageia-dev@ ml:

http://www.mail-archive.com/mageia-dev@mageia.org/msg07959.html
Comment 2 luca pedrielli 2011-09-21 20:52:53 CEST 
Sorry, but i have no plymouth process.
Comment 3 luca pedrielli 2011-09-21 21:02:39 CEST 
..and i'm not using systemd.
Manuel Hiebel 2011-10-30 12:52:22 CET

Source RPM: (none) => iniscripts ?

Comment 4 Sander Lepik 2011-10-30 13:26:49 CET 
Where is your dm located? Under F7 or F8? When i had the same problem with plymouth my dm was under F8.

CC: (none) => sander.lepik

Comment 5 luca pedrielli 2011-10-30 17:39:11 CET 
now i'm using systemd
but there is no plymouth running
dm in F8
ctrl+alt+f1 still black screen.
Manuel Hiebel 2011-10-30 20:31:15 CET

Blocks: (none) => 2120
Source RPM: iniscripts ? => systemd ?

Comment 6 D Morgan 2011-10-30 20:41:07 CET 
if you do :

ps aux | grep plymouth  what do you obtain ?

CC: (none) => dmorganec

Comment 7 luca pedrielli 2011-10-30 20:50:27 CET 
ps aux | grep plymouth
user   10686  0.0  0.0   5796   796 pts/2    S+   20:47   0:00 grep --color plymouth

i have no plymouth process
Comment 8 Yann Ciret 2011-11-24 14:59:50 CET 
Hello,

I encounter this problem with old version of virtualbox, but not with the last one. Have you try to update to the last 4.1.6 ?

CC: (none) => mageia

Comment 9 luca pedrielli 2011-11-24 17:55:57 CET 
Yes, old virtualbox was the culprit!

Thanks.

Luca.
Comment 10 Yann Ciret 2011-11-24 17:59:52 CET 
Good, I close the bug then.

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME