Page 1 of 2 12 LastLast
Results 1 to 10 of 15

Thread: Boot Problem

  1. #1
    Join Date
    Apr 2009
    Location
    UK
    Beans
    109

    Boot Problem

    Since reporting all OK in this thread http://ubuntuforums.org/showthread.p...5#post12348975, I have a booting issue.

    When I try to boot normally, the process hangs at the line:
    35.189139 wlan0: no IP6 routers present.
    I then have to power off to try again.

    If I select Recovery Mode, followed by "resume normal reboot" all boots OK.

    When I try to do a "restart" I just get a blank screen with none of the foregoing.


    Other texts when the boot process hangs:

    22.392410 ath9k wlan0 disabling HT as WMM Q05 isn't supported by the AP, and similar for VHT

    wlan0 associates OK with the AP

    wlan0 link becomes ready

    no IP6 routers present

    When I look into sudo less /var/log/dmesg.0, I get (amongst other things I don't understand):
    ADDRSONF (NETDEV_UP) wlan0: link is not ready.
    Last edited by lisati; November 14th, 2012 at 04:37 AM. Reason: fix link

  2. #2
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    26,047
    Distro
    Ubuntu Development Release

    Re: Boot Problem

    What do you see here?
    sudo gedit /etc/network/interfaces
    If there is anything more than this, remove it.
    Code:
    auto lo
    iface lo inet loopback
    Proofread, save and close gedit.
    When I look into sudo less /var/log/dmesg.0, I get (amongst other things I don't understand):
    Can you please capture 15 lines or so for posting here?

    Reboot and see if your change helped.
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, B.Sc., M.Sc., M.A., Ph.D., Sc.D.

  3. #3
    Join Date
    Apr 2009
    Location
    UK
    Beans
    109

    Re: Boot Problem

    sudo gedit /etc/network/interfaces just shows:

    auto lo
    iface lo inet loopback

    From: sudo less /var/log/dmesg.0

    13.083546] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 13.083552] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 17.959901] lp: driver loaded but no devices found
    [ 30.798095] Adding 4085756k swap on /dev/sda5. Priority:-1 extents:1 across:4085756k
    [ 30.858883] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
    [ 30.910432] init: failsafe main process (1182) killed by TERM signal
    [ 31.057755] init: udev-fallback-graphics main process (1194) terminated with status 1
    [ 31.072011] init: friendly-recovery post-stop process (874) terminated with status 1
    [ 31.103000] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    [ 31.103003] Bluetooth: BNEP filters: protocol multicast
    [ 31.118547] ppdev: user-space parallel port driver
    [ 31.219363] Bluetooth: RFCOMM TTY layer initialized
    [ 31.219367] Bluetooth: RFCOMM socket layer initialized
    [ 31.219369] Bluetooth: RFCOMM ver 1.11
    [ 31.570951] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 31.574015] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 31.713145] r8169 0000:03:00.0: eth0: link down
    [ 31.713292] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 31.713577] ADDRCONF(NETDEV_UP): eth0: link is not ready
    (END)

    I also disabled IP6 tables in Firefox, but it made no difference.

  4. #4
    Join Date
    Apr 2009
    Location
    UK
    Beans
    109

    Re: Boot Problem

    From sudo less /var/log/dmesg

    9.660860] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 9.660867] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 14.592774] lp: driver loaded but no devices found
    [ 27.448381] Adding 4085756k swap on /dev/sda5. Priority:-1 extents:1 across:4085756k
    [ 27.557417] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
    [ 27.634250] init: failsafe main process (1174) killed by TERM signal
    [ 27.812372] init: udev-fallback-graphics main process (1186) terminated with status 1
    [ 27.825998] init: friendly-recovery post-stop process (865) terminated with status 1
    [ 27.863791] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    [ 27.863793] Bluetooth: BNEP filters: protocol multicast
    [ 27.917550] ppdev: user-space parallel port driver
    [ 28.017388] Bluetooth: RFCOMM TTY layer initialized
    [ 28.017393] Bluetooth: RFCOMM socket layer initialized
    [ 28.017394] Bluetooth: RFCOMM ver 1.11
    [ 28.458342] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 28.461322] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 28.593937] r8169 0000:03:00.0: eth0: link down
    [ 28.594083] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 28.594357] ADDRCONF(NETDEV_UP): eth0: link is not ready

  5. #5
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    26,047
    Distro
    Ubuntu Development Release

    Re: Boot Problem

    What extra settings have you placed in Network Manager. Ideally, with the exception of IPv6 and infrastructure, none are nneeded.
    When I try to boot normally, the process hangs at the line:
    35.189139 wlan0: no IP6 routers present.
    I then have to power off to try again.

    If I select Recovery Mode, followed by "resume normal reboot" all boots OK.
    If you just wait, does it boot? When it does, do you have an active network connection?
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, B.Sc., M.Sc., M.A., Ph.D., Sc.D.

  6. #6
    Join Date
    Apr 2009
    Location
    UK
    Beans
    109

    Re: Boot Problem

    No "extra" settings in Network Manager.

    Waiting, it just doesn't do anything - blank screen.
    It only boots after I've powered off and restarted, choosing Recovery Mode, and then "resume normal reboot", and when it does, I'm connected OK.

    EDIT: I've also renabled IP6 in FF
    Last edited by norm.h; November 12th, 2012 at 11:46 PM.

  7. #7
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    26,047
    Distro
    Ubuntu Development Release

    Re: Boot Problem

    Please reboot and let it fail. Power down and boot up from Rescue Mode. Then run:
    Code:
    sudo cat /vat/log/dmesg.0 > norm.txt
    sudo cat /var/log/dmesg >> norm.txt
    zip norm.zip norm.txt
    Find the file norm.zip in your user directory and attach it to your reply using the paperclip tool at the top of the reply box.
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, B.Sc., M.Sc., M.A., Ph.D., Sc.D.

  8. #8
    Join Date
    Apr 2009
    Location
    UK
    Beans
    109

    Re: Boot Problem

    I hope I've done this right.

    This morning I connected the laptop via ethernet cable to see if it worked, to eliminate the possibility of it being a wifi issue, but everything happened as I described yesterday.
    I have logged my actions and will send them if you think it helpful.

    BTW - typo in your first command - should be var not vat. This had me confused for a while
    Attached Files Attached Files

  9. #9
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    26,047
    Distro
    Ubuntu Development Release

    Re: Boot Problem

    I see a lot of these:
    [ 1.409256] ACPI Error: Field [CMDX] at 224 exceeds Buffer [SCBF] size 168 (bits) (20110623/dsopcode-236)
    [ 1.409350] ACPI Error: Method parse/execution failed [\GTFB] (Node f30408a0), AE_AML_BUFFER_LIMIT (20110623/psparse-536)
    [ 1.409490] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node f30409f0), AE_AML_BUFFER_LIMIT (20110623/psparse-536)
    You might Google the error and see if you can see a cause. You might also look in the computer's BIOS to be sure there are no funny ACPI settings. In many cases, resetting the BIOS to DEFAULT, often F9, cures a lot of ills.

    I also see:
    [ 0.523814] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12)
    [ 0.524054] ACPI: PCI Interrupt Link [LNKB] (IRQs *3 4 5 6 7 10 12)
    [ 0.524273] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 *4 5 6 7 10 12)
    [ 0.524492] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *10 12)
    [ 0.524708] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 12) *0, disabled.
    [ 0.524971] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 12) *0, disabled.
    [ 0.525237] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 *5 6 7 10 12)
    [ 0.525455] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 *10 12)
    I don't know why some IRQs would be disabled. Again, in the BIOS, if there is an IRQ selection page, I'd recommend 'Auto Select.' Please see attached. Although this is an ABIT BIOS page, many are quite similar.

    I see nothing in either dmesg that is an error with wireless. The last messages before you apparently froze look...well, normal.

    I suggest you address the issues above and then give us an update.
    Attached Images Attached Images
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, B.Sc., M.Sc., M.A., Ph.D., Sc.D.

  10. #10
    Join Date
    Apr 2009
    Location
    UK
    Beans
    109

    Re: Boot Problem

    As you suggested, I googled the errors, but it's all way above my head.

    I looked in the BIOS and there's no way to look at IRQs nor ACPI settings.

    I reset (F9) and all that did was disabled something called PXE boot, and hasn't made any difference.

Page 1 of 2 12 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
  •