KDM hangs on normal boot

[re-entity]

Hi All,
I have recently upgraded my computer, new motherboard, cpu, ram, graphics card. I had to reconfigure X using vesa drivers to get the desktop working and then load GForce 8800 drivers.

Since doing this, KDM will hang on a regular boot. I now boot in recovery mode and then I can enter "kdm" and everything is fine after that, including Compiz.

How can I do a regular boot right into KDM?

[toad]

Re: KDM hangs on normal boot

Hi,

where exactly does it hang? What is different to the normal booting experience? I think dibl has had GForce 8800 probs and solved them, so I'd search for that (or wait).

[re-entity]

Re: KDM hangs on normal boot

It's hard to say where it hangs exactly. The loading bar appears and maybe 3% loads then it stalls and soon changes to a black screen with a single white underbar character.

Apparently you can turn off that graphical loading bar. How do I do that so I can be more accurate about when it hangs?

[toad]

Re: KDM hangs on normal boot

You simply enter grub by pressing escape when it offers you to do so and then edit (I am sorry, cannot remember) the grub kernel line. I think it is as easy as selecting the kernel you want to boot (which should be the default anyway), then press "e" for edit and now delete the words "quiet" and "splash".

BTW, this only works one time. Next boot will be back to normal. For a permanent change you have to edit /boot/grub/menu.lst

[dibl]

Re: KDM hangs on normal boot

Sounds like the 8800 is hanging on the splash.

Have you tried a "vga=791" option on your kernel boot line in /boot/grub/menu..lst?

The other question is, did you use nvidia-xconfig to write a new xorg.conf file? The applicable command is

sudo nvidia-xconfig --add-argb-glx-visuals --compoosite

HTH

[re-entity]

Re: KDM hangs on normal boot

I don't know what adding vga=791 does but I don't think that is going to help now.

I did turn off quiet and splash and I discovered the following...

Normal boot is trying to resume an image which it can't find.

No resume image...
resume: libgcrypt version: 1.2.4
resume: Could not stat the resume device file /dev/sda5

I currently have 4 hard drives in my system. After the rebuild they aren't in the same order that they were before. Now sdb5 is an NTFS storage drive and sdc5 has my swap file on it. sdc1 is my Kubuntu installation. No other drives have partitions labeled sd_5.

How do I stop it looking for the image?

[toad]

Re: KDM hangs on normal boot

Well, no wonder that the bootloader gets confused if it points to a place which does not exist anymore

This is normally Qqmike's domain but try this first:

1. enter grub again
2. press "c" to get to the command line
3. type

find /boot/grub/stage1

You should get some output akin to (hd0,0)
4. type

root (hd0,0)

Naturally you should take the output from stage 3 above.
5. type the word "kernel" followed by a tab, then "/boot/vm" and now do a couple of tabs - you should see a list of available kernels. Select your standard kernel (tab is once again most useful!)
6. now you have selected the kernel do the same to the initrd, i.e. type the word "initrd" followed by a tab and then again "/boot/ini" and tab your way to the correct initrd
7. type "boot" and press enter.

You have now found your correct kernel and initrd in the new setup. You may encounter a slight problem during boot where you have to press CTRL+D. This is no big problem and we'll come to it later.

Report back if it works (and if it doesn't )

[re-entity]

Re: KDM hangs on normal boot

Ok, I tried that. It didn't work. I got the following output...

Check root = bootarg cat /proc/cmdline or missing modules, devices: cat /proc/modules ls /dev
ALERT! does not exist. Dropping to a shell!

BusyBox v1.1.3 (Debian 1:1.1.3-5Ubuntu7) Built-in shell (ash)

[toad]

Re: KDM hangs on normal boot

Cheers, but something went wrong here. Your output doesn't look like grub at all (having said that I don't recognise it...). Qqmike

[dibl]

Re: KDM hangs on normal boot

I currently have 4 hard drives in my system. After the rebuild they aren't in the same order that they were before.

This is the problem. Originally, you could boot into a CLI terminal -- if you still can do that, run the following, and post the outputs, and maybe we can put Humpty Dumpty back together:

sudo fdisk -lu

blkid

cat /etc/fstab

[re-entity]

Re: KDM hangs on normal boot

Sorry Toad, I should be more clear. I followed your steps in grub and proceeded to boot. The code I posted above is where the boot failed...Right, no longer grub!

dibl, I still have no problem booting to the desktop from the recovery mode. Here are the outputs:

sudo fdisk -lu

Disk /dev/sda: 20.4 GB, 20404101120 bytes
255 heads, 63 sectors/track, 2480 cylinders, total 39851760 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x0d5c0d5c

  Device Boot   Start     End   Blocks  Id System
/dev/sda1  *     63  39825134  19912536  7 HPFS/NTFS

Disk /dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders, total 312581808 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x40b540b4

  Device Boot   Start     End   Blocks  Id System
/dev/sdb1    78140160  312576704  117218272+  f W95 Ext'd (LBA)
/dev/sdb2  *    16128  78140159  39062016  7 HPFS/NTFS
/dev/sdb5    78140223  146030849  33945313+  7 HPFS/NTFS
/dev/sdb6    146030913  213921539  33945313+  7 HPFS/NTFS
/dev/sdb7    213921603  281812229  33945313+  7 HPFS/NTFS
/dev/sdb8    281812293  312576704  15382206  7 HPFS/NTFS

Partition table entries are not in disk order

Disk /dev/sdc: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders, total 312581808 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x08380838

  Device Boot   Start     End   Blocks  Id System
/dev/sdc1  *     63  303467849  151733893+ 83 Linux
/dev/sdc2    303467850  312576704   4554427+  5 Extended
/dev/sdc5    303467913  312576704   4554396  82 Linux swap / Solaris

Disk /dev/sdd: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders, total 312581808 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x26d126d0

  Device Boot   Start     End   Blocks  Id System
/dev/sdd1  *     63  312576704  156288321  7 HPFS/NTFS

blkid

/dev/sdb2: TYPE="ntfs" UUID="D8A88369A88344CA" LABEL="Storage"
/dev/sdb6: TYPE="ntfs" UUID="E82CB48E2CB458F0" LABEL="Projects"
/dev/sdb7: TYPE="ntfs" UUID="C414E09214E0892E" LABEL="Media"
/dev/sdb8: TYPE="ntfs" UUID="D45CAC045CABDF8A" LABEL="Programs"
/dev/sdb5: UUID="EEC888D1C888998B" LABEL="Documents" TYPE="ntfs"
/dev/sdc1: UUID="24cdf5ae-bfae-4257-926c-a8e2a1bc7679" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda1: UUID="EAE47852E47822CD" TYPE="ntfs"
/dev/sdd1: UUID="524CD63F4CD61D93" LABEL="Megaton" TYPE="ntfs"
/dev/sdc5: TYPE="swap" UUID="a25c3b30-7bcb-4b1b-b4a1-d5cf83c4f066"

cat /etc/fstab

# /etc/fstab: static file system information.
#
# <file system> <mount point>  <type> <options>    <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda1
UUID=24cdf5ae-bfae-4257-926c-a8e2a1bc7679 / ext3 nouser,defaults,errors=remount-ro,atime,auto,rw,dev,exec,suid 0 1
# /dev/sda5
UUID=a25c3b30-7bcb-4b1b-b4a1-d5cf83c4f066 none swap sw 0 0
/dev/hdc /media/cdrom0 udf,iso9660 user,atime,noauto,rw,dev,exec,suid 0 0
/dev/hdd /media/cdrom1 udf,iso9660 user,atime,noauto,rw,dev,exec,suid 0 0
/dev/sda6 /projects ntfs uid=1000,gid=1000,auto,ro,nouser 0 0
/dev/sda5 /documents ntfs uid=1000,gid=1000,auto,ro,nouser 0 0
/dev/sda6 /projects ntfs uid=1000,gid=1000,auto,ro,nouser 0 0
/dev/sda7 /multimedia ntfs uid=1000,gid=1001,auto,rw,nouser 0 0

//192.168.1.101/motherload /motherload cifs iocharset=utf8,file_mode=0775,dir_mode=0775,uid=0,gid=0,auto,rw,nouser,credentials=/etc/fstab_smb_credentials_1 0 0
/dev/sdc1 /megaton ntfs uid=1000,gid=1001,auto,rw,nouser 0 0

[dibl]

Re: KDM hangs on normal boot

OK, if you compare your /etc/fstab to the blkid and fdisk outputs, you will observe that there is some confusion regarding the drive designations. For the main filesystem, since you are mounting by UUID (good idea!), it is not a problem that the hard drive was previously identified as /dev/sda but is now /dev/sdc, as per blkid which reflects the "new reality" on your drive designations.

However, you have a series of NTFS formatted partitions on the drive presently seen as /dev/sdb, but you are attempting to mount them in /etc/fstab as /dev/sda, so you need to fix them in fstab. One of them (the one containing "projects") is duplicated in fstab, so you need to remove the redundant line. If you want other partitions mounted when you run Linux, such as /dev/sdd1 "megaton", you'll have to manually add a mount line in /etc/fstab.

So the recommendation is to use the fdisk and blkid outputs as "truth" and edit /etc/fstab to mount them accordingly. I personally use "mount by UUIDs" exclusively, since that helps avoid this exact problem.

Note that every time you add, delete, or reformat a partition, you will be doing this little "compare and contrast" exercise again. I usually just open /etc/fstab in Kate as Super User, then open the terminal and run blkid and copy and paste the UUID's into their correct mount lines in fstab. It can be complicated when you're running numerous drives and partitions:

# <file system> <mount point>  <type> <options>    <dump> <pass>
proc      /proc      proc  defaults    0    0
# /dev/sda1
UUID=4947d60b-b181-4a7d-9c22-f4782ed7cb0a /        xfs   noatime,nodiratime,logbufs=8    0    1
# /dev/sda2
UUID=6d870dce-d248-4ad8-b500-8c01e21d3ef9 /boot      ext3  defaults    0    2
# /dev/sda3
UUID=2d98b093-b312-4ef5-9dc8-bb8ff404277f /home      xfs   noatime,nodiratime,logbufs=8    0    2
# /dev/sda4
UUID=8bd15bd5-04df-437c-b5f8-25897e5ea7b0 /media/sda4   xfs   noatime,nodiratime,logbufs=8    0    2
# /dev/sdb2
UUID=a50bfecb-c48b-4f1e-bcf4-8597166eae6c /media/sdb2   reiserfs noatime,notail    0    2
# /dev/sdb3
UUID=003245d2-a1dc-4c1c-bc52-32601bc65e46 /media/sdb3   reiserfs noatime,notail    0    2
# /dev/sdb4
UUID=f98e6bb6-0ed4-45a8-b596-9ed76e2d2364 /media/sdb4   reiserfs noatime,notail    0    2
# /dev/sdc1
UUID=92c0453f-2a35-40d5-8013-b8870ed66127 /media/sdc1   xfs   noatime,nodiratime,logbufs=8    0    2
# /dev/sdc2
UUID=f4e36b39-af7d-475c-8990-b2093f558295 /media/sdc2   xfs   noatime,nodiratime,logbufs=8    0    2
# /dev/sdc3
UUID=eba33247-0dbb-482c-9351-81505a953864 /media/sdc3   xfs   noatime,nodiratime,logbufs=8    0    2
# /dev/sdd2
UUID=5df77414-98e4-4241-b696-00001ad57fc9 /media/sdd2   ext3  defaults    0    2
# /dev/sdd3
UUID=e11635ae-7dae-45fa-9372-bdc70ef9ec6b /media/sdd3   ext3  defaults    0    2
# /dev/sde1
UUID=e731c3cf-e2ff-4692-8353-ede2a3dcb85e /media/sde1   xfs   noatime,nodiratime,logbufs=8    0    2
# /dev/sdd1
UUID=f292aef5-76a6-4455-a4e0-b760e43126e5 none      swap  sw       0    0
/dev/scd0    /media/cdrom0  udf,iso9660 user,noauto,exec,utf8 0    0
/dev/fd0    /media/floppy0 auto  rw,user,noauto,exec,utf8 0    0

[re-entity]

Re: KDM hangs on normal boot

I've been using the GUI tool to mount drives and partitions. I guess that is where things have become messed up. Sometimes partitions were active, sometimes not. Somewhere along the way they have gotten all mixed up. So now, I have removed all mounts except the main partition and swap file.

Below, blkid is listing Storage and Megaton twice. How do I fix that? I should get that cleaned up before I add anything back to fstab, right?

sudo fdisk -lu

Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders, total 312581808 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x40b540b4

  Device Boot   Start     End   Blocks  Id System
/dev/sda1    78140160  312576704  117218272+  f W95 Ext'd (LBA)
/dev/sda2  *    16128  78140159  39062016  7 HPFS/NTFS
/dev/sda5    78140223  146030849  33945313+  7 HPFS/NTFS
/dev/sda6    146030913  213921539  33945313+  7 HPFS/NTFS
/dev/sda7    213921603  281812229  33945313+  7 HPFS/NTFS
/dev/sda8    281812293  312576704  15382206  7 HPFS/NTFS

Partition table entries are not in disk order

Disk /dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders, total 312581808 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x08380838

  Device Boot   Start     End   Blocks  Id System
/dev/sdb1  *     63  303467849  151733893+ 83 Linux
/dev/sdb2    303467850  312576704   4554427+  5 Extended
/dev/sdb5    303467913  312576704   4554396  82 Linux swap / Solaris

Disk /dev/sdc: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders, total 312581808 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x26d126d0

  Device Boot   Start     End   Blocks  Id System
/dev/sdc1  *     63  312576704  156288321  7 HPFS/NTFS

Disk /dev/sdd: 20.4 GB, 20404101120 bytes
255 heads, 63 sectors/track, 2480 cylinders, total 39851760 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x0d5c0d5c

  Device Boot   Start     End   Blocks  Id System
/dev/sdd1  *     63  39825134  19912536  7 HPFS/NTFS

blkid

/dev/sda5: UUID="EEC888D1C888998B" LABEL="Documents" TYPE="ntfs"
/dev/sda2: TYPE="ntfs" UUID="D8A88369A88344CA" LABEL="Storage"
/dev/sda6: TYPE="ntfs" UUID="E82CB48E2CB458F0" LABEL="Projects"
/dev/sda7: TYPE="ntfs" UUID="C414E09214E0892E" LABEL="Media"
/dev/sda8: TYPE="ntfs" UUID="D45CAC045CABDF8A" LABEL="Programs"
/dev/sdb2: TYPE="ntfs" UUID="D8A88369A88344CA" LABEL="Storage"
/dev/sdb5: UUID="a25c3b30-7bcb-4b1b-b4a1-d5cf83c4f066" TYPE="swap"
/dev/sdc1: UUID="524CD63F4CD61D93" LABEL="Megaton" TYPE="ntfs"
/dev/sda1: UUID="EAE47852E47822CD" TYPE="ntfs"
/dev/sdd1: UUID="EAE47852E47822CD" LABEL="Megaton" TYPE="ntfs"
/dev/sdb1: UUID="24cdf5ae-bfae-4257-926c-a8e2a1bc7679" SEC_TYPE="ext2" TYPE="ext3"

cat /etc/fstab

# /etc/fstab: static file system information.
#
# <file system> <mount point>  <type> <options>    <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda1
UUID=24cdf5ae-bfae-4257-926c-a8e2a1bc7679 / ext3 nouser,defaults,errors=remount-ro,atime,auto,rw,dev,exec,suid 0 1
# /dev/sda5
UUID=a25c3b30-7bcb-4b1b-b4a1-d5cf83c4f066 none swap sw 0 0
/dev/hdc /media/cdrom0 udf,iso9660 user,atime,noauto,rw,dev,exec,suid 0 0
/dev/hdd /media/cdrom1 udf,iso9660 user,atime,noauto,rw,dev,exec,suid 0 0

[dibl]

Re: KDM hangs on normal boot

I think you have actually labeled two different drives "Megaton". :P

The reason I think so is (a) from fdisk I see:

  Device Boot   Start     End   Blocks  Id System
/dev/sdc1  *     63  312576704  156288321  7 HPFS/NTFS

Disk /dev/sdd: 20.4 GB, 20404101120 bytes
255 heads, 63 sectors/track, 2480 cylinders, total 39851760 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x0d5c0d5c

  Device Boot   Start     End   Blocks  Id System
/dev/sdd1  *     63  39825134  19912536  7 HPFS/NTFS

and (b) in blkid I see:

/dev/sdc1: UUID="524CD63F4CD61D93" LABEL="Megaton" TYPE="ntfs"
..
/dev/sdd1: UUID="EAE47852E47822CD" LABEL="Megaton" TYPE="ntfs"

The two UUIDs, combined with the /dev/sd# IDs, tell me there are two devices.

[re-entity]

Re: KDM hangs on normal boot

Doh, I think you are right. I did label two drive Megaton. Ok, what about Storage? sdb2 is the swap file, why would that be labeled storage?