Login screen blacked out

Hi Guys

the weirdest thing has just happened, I logged out of my desktop but instead of going to the login screen I just got a black screen, I hit ctrl alt del it rebooted into the grub bootloader I can select Peppermint 4, the Peppermint logo shows up then just a black screen with a fixed cursor at the top left of the screen.

Any help would be much appreciated

Many thanks

Graeme

Can you type in that screen (does it accept keyboard input)?

Also are you able to get to a console with Ctrl+Alt+F1 ?

Boot to a LiveCD/LiveUSB and post the output from:

sudo fdisk -l

Have you just got any updates ?

Can you type in that screen (does it accept keyboard input)?

It accepts no keyboard input

Have you just got any updates ?

Yes but I didn’t check to see what they were I just updated as I usually do


graeme@Linux3:~$ sudo fdisk -l
[sudo] password for graeme:

Disk /dev/sda: 40.0 GB, 40020664320 bytes




/dev/sdb2       366327806   703281151   168476673    5  Extended
/dev/sdb5       366327808   699105279   166388736   83  Linux
/dev/sdb6       699107328   703281151     2086912   82  Linux swap / Solaris
graeme@Linux3:~$
255 heads, 63 sectors/track, 4865 cylinders, total 78165360 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00039639

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048    73988095    36993024   83  Linux
/dev/sda2        73990142    78163967     2086913    5  Extended
/dev/sda5        73990144    78163967     2086912   82  Linux swap / Solaris

Disk /dev/sdb: 360.1 GB, 360080695296 bytes
255 heads, 63 sectors/track, 43777 cylinders, total 703282608 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
graeme@Linux3:~$
Disk identifier: 0x00000001

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *        2048   366326759   183162356    7  HPFS/NTFS/exFAT

Are the keyboard lights flashing ?

Try booting to a liveCD/LiveUSB and running:

sudo fsck -f /dev/sda5

then rebooting to the hard drive.

if that doesn’t work, boot back to the Live session and try to navigate onto your hard drives /var/log/atp/history.log … that should give us a clue what updates were applied.

You may want to try removing “quiet splash” from the kernel boot line and see if you get any clues where the boot is stalling.

I take it, it no longer gets as far as the login screen ?

Are the keyboard lights flashing ?

Can’t answer that at the moment I’m at work but I’ll post back with that as soon as i can

Try booting to a liveCD/LiveUSB and running: Code: [Select] sudo fsck -f /dev/sda5

I have another OS on the same PC but on a different drive, can i use that instead of a live disc ?

I take it, it no longer gets as far as the login screen ?

Yes I get to the point where i should get the login screen

When I boot I get the grub screen I can select the OS then I get the Peppermint logo with the 5 red lights, then i get a list of errors mounting cifs drives ( but that’s normal) the next stage should be the login screen but it just goes black with a fixed cursor at the top left corner and it accepts no keyboard input, the only way out is to switch off at the PC.

Hmm … I didn’t notice the weird way the partition information is being listed above … so IGNORE the fsck command from my last posting

I have another OS on the same PC but on a different drive, can i use that instead of a live disc ?

It propbaly wouldn’t be a good idea, you cannot run fsck on a mounted partition, and I’m not sure which is the Peppermint partition

sda1
or
sdb5

So it’s probably safer to boot to a LiveCD/LiveUSB and run fsck on both of those partitions.

Do you know which is the Peppermint one ?

Do you know which is the Peppermint one ?

I’d be guessing if i said i knew for certain but I think it’s sdb1

Peppermint is installed alongside Windows 7 on the 360gb drive, the other Linux OS (Bodhi) is installed on a separate 40gb drive on it’s own

I take it the 360GB drive is set as the first boot device ?

Yes it looks like it’s /dev/sdb5

But unless you’re 100% sure, it’s still safer to run it from a booted LiveUSB, as that won’t mount anything (as long as you do nothing to mount anything).

So boot a LiveCD/LiveUSB and run:

sudo fsck -f /dev/sdb5

then

sudo fsck /dev/sda1

then reboot and try Peppermint.

I’ll post back that information as soon as I can but it looks like I’m gonna have to work a bit later tonight (the joys of self employment)

but in the meantime if you remember there was some confusion regarding my system and in particular grub so it may be helpfull for you to refer back to this thread

http://linuxforums.org.uk/index.php?topic=10893.0

Many thanks

Graeme

Hi Mark

Ok I followed your last instructions but it made no difference other than I now have no fixed cursor at the top left of the screen. :frowning:

Graeme

Not sure if this is any help but I found this in /var/log

[+0.06s] DEBUG: Logging to /var/log/lightdm/lightdm.log [+0.06s] DEBUG: Starting Light Display Manager 1.6.0, UID=0 PID=1298 [+0.06s] DEBUG: Loaded configuration from /etc/lightdm/lightdm.conf [+0.06s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager [+0.07s] DEBUG: Registered seat module xlocal [+0.07s] DEBUG: Registered seat module xremote [+0.07s] DEBUG: Adding default seat [+0.07s] DEBUG: Starting seat [+0.07s] DEBUG: Starting new display for greeter [+0.07s] DEBUG: Starting local X display [+0.08s] DEBUG: X server :0 will replace Plymouth [+0.10s] DEBUG: Using VT 7 [+0.10s] DEBUG: Logging to /var/log/lightdm/x-0.log [+0.10s] DEBUG: Writing X server authority to /var/run/lightdm/root/:0 [+0.10s] DEBUG: Launching X Server [+0.10s] DEBUG: Launching process 1341: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch -background none [+0.10s] DEBUG: Waiting for ready signal from X server :0 [+0.10s] DEBUG: Acquired bus name org.freedesktop.DisplayManager [+0.11s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0 [+0.26s] DEBUG: Process 1341 terminated with signal 6 [+0.26s] DEBUG: X server stopped [+0.26s] DEBUG: Removing X server authority /var/run/lightdm/root/:0 [+0.26s] DEBUG: Releasing VT 7 [+0.26s] DEBUG: Stopping Plymouth, X server failed to start [+89.87s] DEBUG: Display server stopped [+89.87s] DEBUG: Stopping display [+89.87s] DEBUG: Stopping seat, failed to start a display [+89.87s] DEBUG: Stopping seat [+89.87s] DEBUG: Seat stopped [+89.87s] DEBUG: Required seat has stopped [+89.87s] DEBUG: Stopping display manager [+89.87s] DEBUG: Display manager stopped [+89.87s] DEBUG: Stopping daemon [+89.88s] DEBUG: Exiting with return value

that’s from the Peppermint partition ?

I’m gonna guess so, as I doubt if Bodhi uses LightDM.

that's from the Peppermint partition ?

Yes it’s from the Peppermint 4 partition

Hmm … looks like X is crashing

Which log was that from?

and can you access the (peppermint partition) /var/log/apt/history.log … scroll to the bottom, and post anything with yesterdays date.

sda1 = Bodhi

sdb1= Windows

sdb5= Peppermint

Start-Date: 2013-06-26 19:57:35 Commandline: aptdaemon role='role-commit-packages' sender=':1.58' Upgrade: python3-software-properties:i386 (0.92.17, 0.92.17.1), peppermint-system:i386 (4.0.4, 4.0.5), pm-utils:i386 (1.4.1-9git1, 1.4.1-9git1ubuntu0.1), software-properties-common:i386 (0.92.17, 0.92.17.1), software-properties-gtk:i386 (0.92.17, 0.92.17.1), yad:i386 (0.21.0-1~webupd8~raring, 0.22.0-1~webupd8~raring), firefox-locale-en:i386 (21.0+build2-0ubuntu0.13.04.2, 22.0+build2-0ubuntu0.13.04.1) End-Date: 2013-06-26 19:58:01

Start-Date: 2013-06-26 21:28:25
Commandline: /usr/sbin/synaptic
Install: mypaint-data:i386 (1.0.0-1, automatic), mypaint:i386 (1.0.0-1)
End-Date: 2013-06-26 21:28:35

That’s all I see for yesterdays date

Are you able to boot to Peppermint recovery mode and drop to a root prompt ?

Are you able to boot to Peppermint recovery mode and drop to a root prompt ?

I’ll try, what do you want me to do ?

First I want you to run:

lshw -C display

(im after which driver is being used)

can youu also pot any output from this:

ls -al /etc/X11/xorg.conf