Page 1 of 3 123 LastLast
Results 1 to 10 of 27

Thread: ubuntu no longer starts, can't diagnose error

  1. #1
    Join Date
    Apr 2008
    Beans
    10

    ubuntu no longer starts, can't diagnose error

    My ubuntu (kubuntu, actually), 9.10 karmic, no longer starts. All I did was a regular daily upgrade and now it's broken. X begins to start, then I get a series of strange windows that appear fuzzy on my screen, so I can't read them. I'm runnig ubuntu from a disc, now. The following is from the old machine's disc:

    Code:
    ubuntu@ubuntu:/media/ubuntu$ cd var/log/
    
    ubuntu@ubuntu:/media/ubuntu/var/log$ cat dmesg |tail
    [   28.487076] type=1505 audit(1259800302.224:17): operation="profile_replace" pid=1146 name=/usr/bin/evince-previewer
    [   28.495597] type=1505 audit(1259800302.234:18): operation="profile_replace" pid=1146 name=/usr/bin/evince-thumbnailer
    [   28.506829] type=1505 audit(1259800302.244:19): operation="profile_replace" pid=1148 name=/usr/lib/cups/backend/cups-pdf
    [   28.507855] type=1505 audit(1259800302.244:20): operation="profile_replace" pid=1148 name=/usr/sbin/cupsd
    [   28.522113] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [   28.554764] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [   28.618289] type=1505 audit(1259800302.354:21): operation="profile_replace" pid=1149 name=/usr/sbin/mysqld
    [   28.620978] type=1505 audit(1259800302.364:22): operation="profile_replace" pid=1155 name=/usr/sbin/mysqld-akonadi
    [   28.940720] cfg80211: Found new beacon on frequency: 2472 MHz (Ch 13) on phy0
    [   28.948396] cfg80211: Found new beacon on frequency: 2467 MHz (Ch 12) on phy0
    
    ubuntu@ubuntu:/media/ubuntu/var/log$ cat syslog |tail
    Dec  3 00:31:47 Dual-Core udev-configure-printer: parent devpath is /devices/pci0000:00/0000:00:1d.7/usb1/1-4
    Dec  3 00:31:47 Dual-Core udev-configure-printer: Device vendor/product is 05AC:1209
    Dec  3 00:31:47 Dual-Core udev-configure-printer: invalid or missing IEEE 1284 Device ID
    Dec  3 00:31:47 Dual-Core bluetoothd[1820]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory
    Dec  3 00:31:47 Dual-Core bluetoothd[1820]: probe failed with driver input-headset for device /org/bluez/1803/hci0/dev_00_1F_00_22_A8_22
    Dec  3 00:31:47 Dual-Core bluetoothd[1820]: Adapter /org/bluez/1803/hci0 has been enabled
    Dec  3 00:31:48 Dual-Core pulseaudio[2195]: core-util.c: Home directory /etc/timidity not ours.
    Dec  3 00:31:48 Dual-Core pulseaudio[2195]: lock-autospawn.c: Cannot access autospawn lock.
    Dec  3 00:31:48 Dual-Core pulseaudio[2195]: main.c: Failed to acquire autospawn lock
    Dec  3 00:31:51 Dual-Core kernel: Kernel logging (proc) stopped.
    
    ubuntu@ubuntu:/media/ubuntu/var/log$ cat Xorg.0.log
    _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
    _XSERVTransMakeAllCOTSServerListeners: server already running
    
    Fatal server error:
    Cannot establish any listening sockets - Make sure an X server isn't already running
    
    Please consult the The X.Org Foundation support 
    	 at http://wiki.x.org
     for help. 
    Please also check the log file at "/var/log/Xorg.0.log" for additional information.
    
    (WW) xf86CloseConsole: KDSETMODE failed: Bad file descriptor
    (WW) xf86CloseConsole: VT_GETMODE failed: Bad file descriptor
    (WW) xf86OpenConsole: VT_GETSTATE failed: Bad file descriptor
     ddxSigGiveUp: Closing log
    ubuntu@ubuntu:/media/ubuntu/var/log$
    It looks like X is to blame, but why? And how can I fix it?

  2. #2
    Join Date
    Aug 2009
    Beans
    38

    Re: ubuntu no longer starts, can't diagnose error

    Mine was working fine till I did the update also and now it won't start and the screen just goes black.

  3. #3
    Join Date
    Apr 2008
    Beans
    10

    Re: ubuntu no longer starts, can't diagnose error

    That's another thing: the screen buffer goes black on all terminals. It's not even possible to use ctr-alt-F1, etc. Text appears for an instant and then it's all black.

  4. #4
    Join Date
    Aug 2005
    Location
    India
    Beans
    419

    Re: ubuntu no longer starts, can't diagnose error

    I'm having the same problem. If I remember correctly, there was some update that replaced/upgraded the "upstart" package. Maybe this is the cause.

    Also, I cannot press 'e' or 'c' in Grub to edit any options. "Recovery mode" also has the same problem (which is extremely retarded, IMO).

    Any help/solution/workaround would be appreciated.

  5. #5
    Join Date
    Dec 2009
    Location
    Edinburgh, Scotland
    Beans
    11
    Distro
    Kubuntu 9.10 Karmic Koala

    Re: ubuntu no longer starts, can't diagnose error

    Same here. This is really dumb. I can read the message if I choose to boot a 2.6.28-16 kernel buts its all mushed up with 2.16.31-14 / 2.6.31-15. The message is basically trying to tell me that Ubuntu is running in low graphics mode. Under the 2.6.28-16 kernel I can get to a console and manually startx at which point it appears everything but my synaptics touchpad works (external mouse works).

    Now I know what the menu is saying I can navigate it under 2.6.31-15 but I don't get a console just blank screens.

    My hardware is okay as I can boot from a Ubuntu CD and everything works.

  6. #6
    Join Date
    Apr 2008
    Beans
    10

    Re: ubuntu no longer starts, can't diagnose error

    I figured out that my problem was that X starts twice, the second time being the "good" one. Frantically typing ctrl-alt-backspace again and again got me to boot normally. But this is obviously a workaround, not a solution.

  7. #7
    Join Date
    Dec 2009
    Location
    Edinburgh, Scotland
    Beans
    11
    Distro
    Kubuntu 9.10 Karmic Koala

    Re: ubuntu no longer starts, can't diagnose error

    Okay sorted my problem. I had been trying to install alternative input methods for Chinese/Japanese seems I broke HAL. I eventually noticed the line "config/hal: couldn't initialise context: unknown error (null)" in /var/log/Xorg.failsafe.log. So in my case apt-get reinstalling hal fixed my system.

    I think there is still an underlying problem with "upstart" and 2.6.31 kernels.

    No expert but the following also from /var/log/Xorg.failsafe.log might be relevant:

    (WW) VESA(0): Unable to estimate virtual size
    (WW) VESA(0): No valid modes left. Trying less strict filter...
    (WW) VESA(0): Unable to estimate virtual size
    (WW) VESA(0): No valid modes left. Trying aggressive sync range...
    (WW) VESA(0): Unable to estimate virtual size

    System is a DELL laptop XPS M1210

  8. #8
    Join Date
    Dec 2009
    Location
    Edinburgh, Scotland
    Beans
    11
    Distro
    Kubuntu 9.10 Karmic Koala

    Re: ubuntu no longer starts, can't diagnose error

    In case you want to comment on it I've filed a bug report on "upstart" and 2.6.31 kernels.

    https://bugs.launchpad.net/ubuntu/+s...rt/+bug/492270

  9. #9
    Join Date
    Mar 2007
    Location
    Toronto, ON
    Beans
    72
    Distro
    The Feisty Fawn Testing

    Re: ubuntu no longer starts, can't diagnose error

    same problem here guys, exactly the same "low graphics mode" thingy/ The whole bootup is completely random - I cannot see the console text, it all mushed up. Are we sure this is not an NVIDIA driver problem? I remember updating the driver not too long ago.

    I have one more aspect that might be relevant for diagnosis.
    When I boot, the Kubuntu loading bar appears. When the bar reaches about 50% the screen disappears and I get a blinking cursor at the top of the screen. After a few minutes, sometimes, something happens and the cursor rapidly moves to the bottom of the screen, and then the OS starts normally

    it seems to me this is a serious problem. I hope this will be dealt soon because the system is essentially not functional anymore.

    My system is a dell latitude d830 with ubuntu64 on kde dualbooting windows 7 ultimate

  10. #10
    Join Date
    Oct 2009
    Beans
    4

    Re: ubuntu no longer starts, can't diagnose error

    Looks like I have the same problem - my sysem is almost unusable after update.
    After showing splash screen the screen goes blank with a blinking cursor in top-left corner.
    Pressing Alt-Fx does not change anything - sometimes there are only some white dots on the screen.
    It is not nvidia related - I have Intel card.
    After adding removing splash and adding i915.modeset=0 on boot a popup with "Failed to load i810 module" message or similar appears and I can login in text mode. Then I can issue startx and wow - GNOME starts normally.

Page 1 of 3 123 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •