Author Topic: Unable to log in <SOLVED>  (Read 1489 times)

lwfitz

  • DEFCON 1
  • Posts: 1774
  • sudo rm -rf /
    • View Profile
Unable to log in <SOLVED>
« on: January 14, 2013, 07:34:01 PM »
Ok so I figured I would bring this issue here in case anyone else ends up having this same problem.

I did a clean install and for some reason I am unable to log in normally. I can drop to tty and log in through tty and with

Code: [Select]
sudo startx
I am able to start an xfce root session

or at lightdm enter my username as root and then log in with my root password but thats it.

If I hard restart I can sometimes then log in normally but that isnt guaranteed.

This has been an ongoing issue with another machine, both are AMD w/ ATI Raedeon HD cards.

lspci
Code: [Select]
luke@MSI-VSIDO:~$ lspci
00:00.0 Host bridge: Advanced Micro Devices [AMD] nee ATI RX780/RX790 Chipset Host Bridge
00:02.0 PCI bridge: Advanced Micro Devices [AMD] nee ATI RD790 PCI to PCI bridge (external gfx0 port A)
00:11.0 SATA controller: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode] (rev 40)
00:12.0 USB controller: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:12.2 USB controller: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:13.0 USB controller: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:13.2 USB controller: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:14.0 SMBus: Advanced Micro Devices [AMD] nee ATI SBx00 SMBus Controller (rev 42)
00:14.1 IDE interface: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 IDE Controller (rev 40)
00:14.2 Audio device: Advanced Micro Devices [AMD] nee ATI SBx00 Azalia (Intel HDA) (rev 40)
00:14.3 ISA bridge: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 LPC host controller (rev 40)
00:14.4 PCI bridge: Advanced Micro Devices [AMD] nee ATI SBx00 PCI to PCI Bridge (rev 40)
00:14.5 USB controller: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
00:15.0 PCI bridge: Advanced Micro Devices [AMD] nee ATI SB700/SB800/SB900 PCI to PCI bridge (PCIE port 0)
00:15.1 PCI bridge: Advanced Micro Devices [AMD] nee ATI SB700/SB800/SB900 PCI to PCI bridge (PCIE port 1)
00:16.0 USB controller: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:16.2 USB controller: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:18.0 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor HyperTransport Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor Link Control
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Juniper XT [AMD Radeon HD 6000 Series]
01:00.1 Audio device: Advanced Micro Devices [AMD] nee ATI Juniper HDMI Audio [Radeon HD 5700 Series]
02:07.0 Multimedia audio controller: C-Media Electronics Inc CMI8788 [Oxygen HD Audio]
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)

Anyone have any ideas?


UPDATE!!!!!

fstab wasnt using uuid's to assign drive paths so when I rebooted things got all messed up. By logging in as root I opened fstab with a terminal

Code: [Select]
geany /etc/fstab
and from another terminal I got my drive uuid's by running

Code: [Select]
blkid
which gave me this

Code: [Select]
luke@Asus-VSIDO:~$ sudo blkid
[sudo] password for luke:
/dev/sdf5: LABEL="External" UUID="530e27ef-3701-4eb0-8f5f-01102fd27eba" TYPE="ext4"
/dev/sde5: UUID="d556b421-6d67-45ae-8b3a-c360f09912ef" TYPE="ext4"
/dev/sda5: UUID="959eed61-477e-456c-aa3d-bf582957fb51" TYPE="ext4"
/dev/sdb1: LABEL="storage" UUID="0D78843743DFACE1" TYPE="ntfs"
/dev/sdd1: UUID="d5014b82-66e7-4dad-8787-e14aa1f79af2" TYPE="ext4"
/dev/sdd2: UUID="fd0b669f-cc60-4799-a342-a719249a8d57" TYPE="ext4"
/dev/sdd3: UUID="4d4296c2-0299-4d32-bc71-73bb4b7ea936" TYPE="swap"
/dev/sdc5: UUID="92981918-8ba7-47f8-8927-f8aca3e56ee9" TYPE="ext4"

I then edited fstab and removed the drive path and entered my drive uuid.

So mine went from this:

Code: [Select]
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>

proc /proc proc defaults 0 0
/dev/sde1 / ext4 relatime,errors=remount-ro 0 1
/dev/sdf5 /media/External ext4 defaults 0 0
/dev/sda5 /media/sda5 ext4 defaults 0 0
/dev/sdb5 /media/sdb5 ext4 defaults 0 0
/dev/sdc1 /media/storage  ntfs-3g defaults,locale=en_US.UTF-8 0 0
/dev/sdd5 /media/sdd5 ext4 defaults 0 0
/dev/sde2 /home ext4 relatime 0 0
/dev/sde3 none swap sw 0 0
/dev/cdrom /media/cdrom udf,iso9660 user,noauto,exec,utf8 0 0

To this

Code: [Select]
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>

proc /proc proc defaults 0 0
#Entry for /dev/sde1 :
UUID=d5014b82-66e7-4dad-8787-e14aa1f79af2 / ext4 relatime,errors=remount-ro 0 1
#Entry for /dev/sdf5 :
UUID=530e27ef-3701-4eb0-8f5f-01102fd27eba /media/External ext4 defaults 0 0
#Entry for /dev/sda5 :
UUID=959eed61-477e-456c-aa3d-bf582957fb51 /media/sda5 ext4 defaults 0 0
#Entry for /dev/sdb5 :
UUID=d556b421-6d67-45ae-8b3a-c360f09912ef /media/sdb5 ext4 defaults 0 0
#Entry for /dev/sdc1 :
UUID=0D78843743DFACE1 /media/storage ntfs-3g defaults,locale=en_US.UTF-8 0 0
#Entry for /dev/sdd5 :
UUID=92981918-8ba7-47f8-8927-f8aca3e56ee9 /media/sdd5 ext4 defaults 0 0
#Entry for /dev/sde2 :
UUID=fd0b669f-cc60-4799-a342-a719249a8d57 /home ext4 relatime 0 0
#Entry for /dev/sde3 :
UUID=4d4296c2-0299-4d32-bc71-73bb4b7ea936 none swap sw 0 0
/dev/cdrom /media/cdrom udf,iso9660 user,noauto,exec,utf8 0 0
Don't Be A Dick!

jedi

  • DEFCON 1
  • Posts: 1631
  • Not all those who wander are lost.
    • View Profile
    • NixNut.com
Re: Unable to log in <SOLVED>
« Reply #1 on: January 14, 2013, 10:10:51 PM »
Originally posted: Sat Dec 22, 2012 7:13 pm
Quote from: VastOne
Great to hear this Jed!  As stated in another post, I got pulled away by life also...

A couple of questions...

Did you see a login as soon as you booted to LiveCD or did it take you to OpenBox in an autologin?

Were there any issues like what lwfitz had not being able to login?

Is there anything you saw out of whack?

Did you 'use' the How To I wrote as a guide or was the install self explanatory?

How do you think a brand new user would do with this install?

Thanks!

Using the LiveCD (LiveUSB for me) it went right into OB with no login required.  I had none of lwfitz's issues.  My only "issue" is hardware related as you know, (the Optimus mess courtesy of nVidia).  I did read the HowTo quite thoroughly before I did my install.  I could have gotten through it however without reading the HowTo.  It was that self explanatory.

When I first started using Sid, I wasn't sure about it being for the new Linux user.  Your VSIDO distro has changed my mind completely in that regard.  Very simple install, accompanied by the fact that everything you need to be up, running, and productive right out of the box makes for a pretty sweet distro!  So, that being said, yes, I believe this could be very beneficial to any New User.  Brand new or otherwise!  With the addition of having smxi already installed and ready to use, it is basically perfection!

One other note, I have gone ahead and edited my grub.cfg manually.  I did this only to avoid the issue on reboot of having to edit the Grub2 menu.  After this edit (NEVER EDIT THE GRUB.CFG FILE MANUALLY!  :ugeek: ) it boots perfectly every time.  I know you submitted a bug report about this, and it is for me, a very minor issue.  I added the bit about never editing the grub.cfg for anyone tempted to do so.  If you do decide to edit grub.cfg (not to be confused with editing and then updating grub which is a completely DIFFERENT file than grub.cfg) please know that you can seriously break your system.  You have been warned!  My only reason for doing so was completely hardware related and in no way due to VSIDO.  I have a hybrid (read, ominous Optimus Intel/nvidia worthless video card in my laptop that this install was done on) graphics system that seriously confuses Linux.  Do a search for Linus Torvalds and the F word rant against nVidia.  You'll get a real chuckle!

If anyone were to install that has a similar hardware setup to mine, making a note of the edit to grub is the only way they'll successfully get it to boot.

Jed
Forum Netiquette

"No matter how smart you are you can never convince someone stupid that they are stupid."  Anonymous