[SOLVED] Boot loop after upgrade

Hi all,
When i try to boot arch, even in fallback mode, boot fail and go in loop.
loop happen just after the display of nvidia logo, then it try to do something (not showed in screen), it fail, and the nvidia logo is showen again.
I can't access to GDM, i can't turn off computer (have to remove battery from my laptop), i can't access to terminal/console/virtual console.
Last things i've made:
- full update system (pacman -Syu)
- changed /etc/environment adding this line (i was trying to solve tearing problem):
CLUTTER_PAINT=disable-clipped-redraws:disable-culling
CLUTTER_VBLANK=True
nothing seem to work
i've already removed the 2 added lines from another linux distro i've on the same computer, so i don't think /etc/environment is a problem here
don't know what to do and how to solve...
any hints?
thanks
Nico
Last edited by tracuboTL (2012-02-07 14:43:30)

I have exactly the same problem,
Did a full update with pacman.
I haven't updated with yaourt, because I had some problems and rebooted, but now I cannot access the terminal.
If I switch to tty1, I constantly switch back. Ctrl+Alt+Backspace is not enabled and I'm not sure it would work.
I've tried to only boot to runlevel 3, but gdm is in the daemons or I did something wrong because I boot into X again.
Anyone have an idea how to solve this?
Thanks
EDIT: solved it for me
Step 1: on boot let GRUB only boot to init 1
Step 2: change config files so not to start X
Step 3: reboot so you have networking support
Step 4: search in aur if you have a your own cairo package (pacman -Qm)
Step 5: rebuilt that cairo package
Step 6: start X
* step 2 and 3 are maybe not needed if you know how to get networking in init 1. Re;ember to undo the changes in Step 2 so X starts at boot again.
Last edited by tmske (2012-02-06 18:15:15)

Similar Messages

  • 4404 WLC stuck in boot loop after upgrade

    In prepping for the upgrade to 4.1.185.0 I've got two controllers at different sites stuck in a boot loop after applying 4.0.219.0. Units will not even get to the <ESC> option menu.
    ANy ideas?

    Did you clear the configuration on the controller by using Option 5 in the boot menu? This will corrupt the boot image. You should not choose the clear config (option 5) from the boot menu on controllers running 3.2.78.0, 3.2.116.21, 3.2.150.6 or 3.2.150.10, 3.2.171.5 or 3.2.171.6, 4.0.155.5 or 4.0.179.8 and 4.0.179.11.

  • [Solved] Boot failure after upgrade to udev 0.84

    After upgrading my system it no longer boot properly.
    The kernel boots fine. Initrd executes and the normal init starts.
    First of is the start of udev. This starts and immediately complains that nss_ldap is unable to contact the ldap server. Not very strange when networking isn't started yet.
    After a little while and a few repetitions of the nss_ldap error message udev says its done.
    After this activating swap fails but mounting Root readonly succeds. After this init proceeds with "Checking file system". This fails miserably saying "no such file or directory /dev/sda3" which is the previously mounted root filesystem.
    It seems like udev gets busy when not able to connect to the ldap server and hence doesn't create the device nodes for my harddrive in time.
    Because the check of the filesystem fails i end up on a rescue prompt. And when logging in to that and check /dev the sda* nodes are there.
    Does anyone have a clue on how udev depends on nss_ldap? Any other thought on whats going on?

    Ok, after some investigation it turns out that it seems like udev starts a few /sbin/vol_id on the disks/partitions attached. These processes in turn triggered nss_ldap which couldnt connect to the remote ldap server due to network not being up.
    I have a less than beautiful solution to the problem. Altering nss_ldap to do soft binds instead of the default that is hard binding. When using hard bind and connect fails it uses an exponential backoff and tries again a little later. Changing to soft bind makes nss_ldap returning immediately when failing.
    To  change this edit  /etc/nss_ldap.conf and change the line saying something like
    #bind_policy hard
    to
    bind_policy soft
    This at least helped me getting a system that boots again.

  • Xperia Z1 stuck in boot loop after upgrade to lollipop!

    Hi,
    I tried to upgrade my Xperia Z1 to lollipop on my macbook - but it failed due to something about update server error. Now , the phone just tries to boot, shows the sony and xperia logo, backlight comes on - and then shuts down and cycles through this! I tried using EMMA and the phone is locked and says to go to sonymobile/update - but that says to use PCCOmpanion -  I have tried to use PCcompanion on a PC and folloed the instructions and it shows the start screen, select screen then just tells me to take the battery out and put the usb cable in again - obviously can't take the battery out - so i shutdown, put it in fastboot and it just does the same.
    HELP! Followed the upgrade procedure to the letter and now my phone looks like its bricked....hope sony will replace as it was their fault! Or can someone help me!?!?!?
    Solved!
    Go to Solution.

    You may need to perform a software repair using PC Companion.The process will erase all internal memory.You might need to charge your device for about 1-2 hours before so the device has at least 60% battery.
    Make sure the device is not connected to computer or laptop and turned off (sometimes you have to press power button and volume up until the device vibrates 3 times or on some devices you have to press the small button near the SIM tray or on the back of the device).
    Open PC companion->support zone->phone/tablet software update->repair my phone/tablet blue highlighted.Follow the steps given,do not connect your phone until prompted to press volume down while plugging USB cable. If PC companion does not start the repair process, you might need to run it in compatibility mode with Windows 7 (in some cases XP).
    All we have to decide is what to do with the time that is given to us - J.R.R. Tolkien

  • Z68a-gd65 boot loop after bios update using USB

    Hi there,
    My  z68a-gd65 (G3) went into a boot loop after I did a bios update from a USB key that I installed using the latest BIOS version on the MSI site 7681vP8.zip
    After the system restarted, it keeps booting up for 5 seconds and then shutting down, I removed all external devices and the Geforce GTX 550 Ti card and used the onboard card, but still no change...
    Is there a way to set the board to factory defaults again???
    Marcel

    Hi there,
    Maybe for others to solve the same problem, I found out what was the cause of this problem, I had a USB/Firewire card installed in the PC, after removing it the BIOS update could proceed from the USB stick as planned.
    After the update though, my USB/firewire card can still not be installed back into the slot, because doing so will make the boot loop appear again, very odd!
    Does anyone know why this new BIOS will not work with the card that has been inside my PC for 2 years???
    Marcel

  • My ipod is stuck in a boot loop after restoring

    My iPod touch 4g is in a boot loop after restoring
    It will boot up but 10 seconds later after the unlock screen it goes into the apple boot screen please help!!!

    Try:
    - iOS: Not responding or does not turn on
    - Also try DFU mode after try recovery mode
    How to put iPod touch / iPhone into DFU mode « Karthik's scribblings
    - If not successful and you can't fully turn the iOS device fully off, let the battery fully drain. After charging for an least an hour try the above again.
    - Try on another computer
    - If still not successful that usually indicates a hardware problem and an appointment at the Genius Bar of an Apple store is in order.
      Apple Retail Store - Genius Bar

  • Windows 10 Upgrade infinite boot loop after reset

    I did a Windows 10 upgrade on an old computer with these specs:-Windows 7 Pro- 64 bit-Dell Optiplex 755-4 GB RAM-Intel Core2 Duo processor Everything ran fine after the upgrade. However I wanted to do a clean install. So I did so and chose the option to not keep any files or programs. It went through the process and was stalled at 99% for some time. I let it run over night. I came back and looked at it about 16 hours later and the 99% was gone, but the "hourglass" was still going. I pressed Escape and then CTRL+ALT+Delete to try to get it to respond. Now it is stuck in an infinite boot loop. It will reboot and then after several minutes it brings up an error message of "Your PC ran into a problem and needs to restart...- Inaccessible boot device." Then it restarts and the loop starts over.I've tried booting into safe mode using F8, but...

    These days, there are many ways to combine electronics. Custom gaming PC? No problem. Raspberry Pi arcade? Easy. GoPro on the hood of your RC car? Awesome!I thought up this combo, a tiny portable computer with a huge screenhttp://www.newegg.com/Product/Product.aspx?Item=0FC-001H-00017&cm_re=pico_projector-_-0FC-001H-0...http://www.newegg.com/Product/Product.aspx?Item=N82E16883400001&cm_re=compute_stick-_-83-400-001...What are some of your cool tech combos?

  • SG300-28 switch in boot loop after firmware upgrade

    After performing a firmware upgrade on an SG300-20 switch from ver 1.1.0.73  to 1.2.5.70 the switch now boots up with the following error and resets:
    30-Aug-2011 10:47:33 %L1Mngr-F-PARAMTOOLONG: csco-sb parameter %s is too long.
    The attached file contains a full output of the console boot process.
    I have tried loading different versions from the console, but all produce the same error.
    Has any one any idea how to resolve this issue?
    Thanks
    Des

    Hello Tom, Thanks for your reply,
    I had done the process before with the 3 firmwares offered in the cisco website. I did it again, and i get a boot loop again, with following error:
    %L1Mngr-F-PARAMTOOLONG: csco-sb parameter serialNo is too long.
    Any ideas?
    Thank you,
    Nico
    Console
         Startup Menu
    [1]  Download Software
    [2]  Erase Flash File
    [3]  Password Recovery Procedure
    [4]  Set Terminal Baud-Rate
    [5]  Stack menu
    [6]  Back
    Enter your choice or press 'ESC' to exit:
    Downloading code using XMODEM.
    -- Download complete --
    Calculating file's checksum...OK
    Erasing FLASH ->>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Writing to flash 0x6aa500 records...
    Setting checksum: 0x350925f6 , Address: 0x0
    OK.
    Flash programming success.
    Perform WARM BOOT ...
    Boot1 Checksum Test...............................PASS
    Boot2 Checksum Test...............................PASS
    Flash Image Validation Test.......................PASS
    BOOT Software Version 1.0.0.4 Built  08-Apr-2010  16:37:57
    Networking device with Marvell ARM CPU core. 128 MByte SDRAM.
    I-Cache 16 KB. D-Cache 16 KB. L2 Cache 256 KB. Cache Enabled.
    MAC Address   :  58:35:d9:96:7f:5d.
    Autoboot in 2 seconds - press RETURN or Esc. to abort and enter prom.
    Preparing to decompress...
    100%
    Decompressing SW from image-1
    100%
    OK
    Running from RAM...
    Board ID is 22
    Device ID 0xdf5111ab
    *** Running  SW  Ver. 1.2.7.76  Date  19-Jul-2012  Time  17:54:43 ***
    HW version is V
    Base Mac address is: 58:35:d9:96:7f:5d
    Dram size is  : 128M bytes
    Dram first block size is  : 101376K bytes
    Dram first PTR is  : 0x1900000
    Dram second block size is  : 4096K bytes
    Dram second PTR is  : 0x7C00000
    Flash size is: 16M
    19-Jul-2012 17:54:46 %CDB-I-LOADCONFIG: Loading running configuration.
    19-Jul-2012 17:54:47 %CDB-I-LOADCONFIG: Loading startup configuration.
    Device configuration:
    Slot 1 - SF302-08MP
    Device 0: GT_98DX1005 (AlleyCat)
    -- Unit Standalone                --
    Tapi Version: v1.9.5
    Core Version: v1.9.5
    19-Jul-2012 17:55:02 %L1Mngr-F-PARAMTOOLONG: csco-sb parameter serialNo is too l
    ong.
    ***** FATAL ERROR *****
    Reporting Task: ROOT.
    Software Version: 1.2.7.76 (date  19-Jul-2012 time  17:54:43)
    ***** DEBUG *****
    DEBUG LOG IS EMPTY
    0x16a614
    0x167054
    0x6bdc18
    0x490518
    0x4959e4
    0x495bac
    0x815674
    0x816b10
    0x817e64
    0x1d51e8
    0x1cb010
    0x121d3c
    *****************  SYSTEM RESET  *****************

  • [SOLVED] Broken setup after upgrading to 2.6.29

    I am running a x86_64 system.
    I have been running kernel26-2.6.28.7-2 for a while now. Upgrade to kernel26-2.6.28.8-1 caused some problem for me so I installed the older version from /var/cache/pacman/pkg/. After upgrading day before yesterday to 2.6.29.1, I can boot and login to the system but pretty much nothing works. The obvious problem that I can find out is that everyting is trying to load modules from 2.6.28-ARCH. After logging in even 'uname -r' reports 2.6.28-ARCH. I do have the /lib/modules/2.6.29-ARCH folder with all the modules.
    Any help will be much appreciated. I can provide further information if required. Thank you.
    Last edited by partha (2009-04-20 03:13:17)

    I was able to solve it. The problem was I was using grub installed from Ubuntu. So, there was some problem loading the kernel. Installing grub from arch fixed it. Thanks.

  • [SOLVED] System freeze after upgrade linux-3.12.9-2 to linux-3.13.4-1

    After upgrading from kernel 3.12.9 to 3.13.4 (booth x86_64 architecture) i detected system freeze after round about 0.5s of the login screen about 80% of the time.
    So i first thought it coulbe be the the ati driver and uninstalled that via livecd/chroot.
    But the same thing happens in comand line only mode.
    Afterwards i setup at ssh server to get into the maschine if it is still running, but is was also not responding to that.
    Downgrading to 3.12.9 solved the issue. In journalctl i could not find any usefull information.
    Last edited by schlumpfimsumpf (2014-04-10 19:16:57)

    Me wrote:
    It is same for me. Wont boot, and crash before I can write mine pass to text screen. I use lts at now.
    H/W path Device Class Description
    ===============================================
    system GA-970A-UD3
    /0 bus GA-970A-UD3
    /0/0 memory 128KiB BIOS
    /0/4 processor Athlon
    /0/4/a memory 128KiB L1 cache
    /0/4/c memory 2MiB L3 cache
    /0/b memory 128KiB L1 cache
    /0/29 memory 8GiB System Memory
    /0/29/0 memory DIMM 1600 MHz (0,6 ns) [empty]
    /0/29/1 memory DIMM 1600 MHz (0,6 ns) [empty]
    /0/29/2 memory 4GiB DIMM 1600 MHz (0,6 ns)
    /0/29/3 memory 4GiB DIMM 1600 MHz (0,6 ns)
    /0/100 bridge RD890 PCI to PCI bridge (external gfx0 port B)
    /0/100/0.2 generic RD990 I/O Memory Management Unit (IOMMU)
    /0/100/2 bridge RD890 PCI to PCI bridge (PCI express gpp port B)
    /0/100/2/0 display GF106 [GeForce GTS 450]
    /0/100/2/0.1 multimedia GF106 High Definition Audio Controller
    /0/100/4 bridge RD890 PCI to PCI bridge (PCI express gpp port D)
    /0/100/4/0 bus EJ168 USB 3.0 Host Controller
    /0/100/4/0/0 usb3 bus xHCI Host Controller
    /0/100/4/0/0/2 storage ADATA USB Flash Drive
    /0/100/4/0/1 usb2 bus xHCI Host Controller
    /0/100/9 bridge RD890 PCI to PCI bridge (PCI express gpp port H)
    /0/100/9/0 eth0 network RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
    /0/100/a bridge RD890 PCI to PCI bridge (external gfx1 port A)
    /0/100/a/0 bus EJ168 USB 3.0 Host Controller
    /0/100/a/0/0 usb8 bus xHCI Host Controller
    /0/100/a/0/1 usb7 bus xHCI Host Controller
    /0/100/11 storage SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode]
    /0/100/12 bus SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
    /0/100/12/1 usb6 bus OHCI Host Controller
    /0/100/12/1/5 input M Dongle
    /0/100/12.2 bus SB7x0/SB8x0/SB9x0 USB EHCI Controller
    /0/100/12.2/1 usb1 bus EHCI Host Controller
    /0/100/13 bus SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
    /0/100/13/1 usb9 bus OHCI Host Controller
    /0/100/13/1/1 input USB Receiver
    /0/100/13.2 bus SB7x0/SB8x0/SB9x0 USB EHCI Controller
    /0/100/13.2/1 usb4 bus EHCI Host Controller
    /0/100/14 bus SBx00 SMBus Controller
    /0/100/14.2 multimedia SBx00 Azalia (Intel HDA)
    /0/100/14.3 bridge SB7x0/SB8x0/SB9x0 LPC host controller
    /0/100/14.4 bridge SBx00 PCI to PCI Bridge
    /0/100/14.4/7 multimedia SAA7134/SAA7135HL Video Broadcast Decoder
    /0/100/14.4/e bus VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller
    /0/100/14.5 bus SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
    /0/100/14.5/1 usb10 bus OHCI Host Controller
    /0/100/15 bridge SB700/SB800/SB900 PCI to PCI bridge (PCIE port 0)
    /0/100/16 bus SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
    /0/100/16/1 usb11 bus OHCI Host Controller
    /0/100/16/1/3 multimedia USB Web Camera
    /0/100/16/1/4 multimedia USB Sound Device
    /0/100/16.2 bus SB7x0/SB8x0/SB9x0 USB EHCI Controller
    /0/100/16.2/1 usb5 bus EHCI Host Controller
    /0/101 bridge Family 15h Processor Function 0
    /0/102 bridge Family 15h Processor Function 1
    /0/103 bridge Family 15h Processor Function 2
    /0/104 bridge Family 15h Processor Function 3
    /0/105 bridge Family 15h Processor Function 4
    /0/106 bridge Family 15h Processor Function 5
    /1 scsi6 storage
    Working again. I think problem was the partition was full.
    Last edited by gyurman (2014-04-13 07:51:22)

  • Problem: Mac won't boot up after upgrade to 10.5.4

    Upgraded MacBook Air (SSD model) to 10.5.4 last night. Got a couple of boots where MBA showed a grey panel in the centre of the screen (in 4 languages) saying that I needed to restart my computer. On the third try got the white Apple startup, then a plain light blue screen. I know from previous upgrades that can sit for a while, so I left it overnight. In the morning, still blue. Power off, power on, grey panel telling me to restart again. Seems to be in a cycle of twice with a grey box, then the blue screen. Any ideas?
    Everything is backed up, so if I get it sort-of working, I can restore to my last good 10.5.3 and take it from there.

    Hi,
    it happened to me too.
    I've G4 mini with 1Gb RAM: with 10.5.3 everything was working fine.
    Once upgraded to 10.5.4 and reboot, the Mac just won't start: blue screen with mouse cursor but nothing more.
    Additionally, the mac becomes extremely noisy as for some process taking out all the CPU.
    It's the second time I got a system failure after upgrading Leopard: this starts to be annoying.
    M.

  • [solved] dhcpcd problem after upgrading to 6.0.4/6.0.5

    I cant access any network after upgrading to 6.0.4 or 6.0.5.
    Im using the Linux-Kernel 3.10.3.
    Does anyone have the same problem?
    Downgrading to 5.6.8 solved this problem.
    Here is the output of dhcpcd and wpa_supplicant:
    dhcpcd[28734]: version 6.0.4 starting
    dhcpcd[28742]: wlan0: starting wpa_supplicant
    dhcpcd[28734]: eth0: waiting for carrier
    dhcpcd[28734]: wlan0: waiting for carrier
    dhcpcd[28734]: wlan0: carrier acquired
    dhcpcd[28734]: wlan0: soliciting an IPv6 router
    dhcpcd[28734]: wlan0: rebinding lease of 192.168.0.104
    dhcpcd[28734]: wlan0: soliciting a DHCP lease
    dhcpcd[28734]: wlan0: carrier lost
    dhcpcd[28734]: wlan0: carrier acquired
    dhcpcd[28734]: wlan0: soliciting an IPv6 router
    dhcpcd[28734]: wlan0: rebinding lease of 192.168.0.104
    dhcpcd[28734]: wlan0: leased 192.168.0.104 for 86400 seconds
    dhcpcd[28734]: wlan0: adding host route to 192.168.0.104 via 127.0.0.1
    dhcpcd[28734]: wlan0: adding route to 192.168.0.0/24
    dhcpcd[28734]: wlan0: adding default route via 192.168.0.1
    dhcpcd[28734]: forked to background, child pid 28849
    Successfully initialized wpa_supplicant
    wlan0: SME: Trying to authenticate with f8:df:a8:33:0e:7f (SSID='VHC' freq=2452 MHz)
    wlan0: Trying to associate with f8:df:a8:33:0e:7f (SSID='VHC' freq=2452 MHz)
    wlan0: Associated with f8:df:a8:33:0e:7f
    wlan0: WPA: Key negotiation completed with f8:df:a8:33:0e:7f [PTK=TKIP GTK=TKIP]
    wlan0: CTRL-EVENT-CONNECTED - Connection to f8:df:a8:33:0e:7f completed [id=2 id_str=]
    wlan0: CTRL-EVENT-DISCONNECTED bssid=f8:df:a8:33:0e:7f reason=3 locally_generated=1
    wlan0: SME: Trying to authenticate with f8:df:a8:33:0e:7f (SSID='VHC' freq=2452 MHz)
    wlan0: Trying to associate with f8:df:a8:33:0e:7f (SSID='VHC' freq=2452 MHz)
    wlan0: Associated with f8:df:a8:33:0e:7f
    wlan0: WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
    wlan0: WPA: Could not verify EAPOL-Key MIC - dropping packet
    wlan0: WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
    wlan0: WPA: Could not verify EAPOL-Key MIC - dropping packet
    wlan0: Authentication with f8:df:a8:33:0e:7f timed out.
    wlan0: CTRL-EVENT-DISCONNECTED bssid=f8:df:a8:33:0e:7f reason=3 locally_generated=1
    wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
    wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=2 ssid="VHC" auth_failures=1 duration=10
    wlan0: Failed to initiate AP scan
    wlan0: Failed to initiate AP scan
    wlan0: Failed to initiate AP scan
    wlan0: CTRL-EVENT-DISCONNECTED bssid=f8:df:a8:33:0e:7f reason=3 locally_generated=1
    wlan0: Failed to initiate AP scan
    wlan0: Failed to initiate AP scan
    wlan0: CTRL-EVENT-DISCONNECTED bssid=f8:df:a8:33:0e:7f reason=3 locally_generated=1
    wlan0: CTRL-EVENT-DISCONNECTED bssid=f8:df:a8:33:0e:7f reason=3 locally_generated=1
    wlan0: CTRL-EVENT-SSID-REENABLED id=2 ssid="VHC"
    wlan0: SME: Trying to authenticate with f8:df:a8:33:0e:7f (SSID='VHC' freq=2452 MHz)
    wlan0: Trying to associate with f8:df:a8:33:0e:7f (SSID='VHC' freq=2452 MHz)
    wlan0: Associated with f8:df:a8:33:0e:7f
    wlan0: WPA: Key negotiation completed with f8:df:a8:33:0e:7f [PTK=TKIP GTK=TKIP]
    wlan0: CTRL-EVENT-CONNECTED - Connection to f8:df:a8:33:0e:7f completed [id=2 id_str=]
    wlan0: CTRL-EVENT-DISCONNECTED bssid=f8:df:a8:33:0e:7f reason=3 locally_generated=1
    wlan0: SME: Trying to authenticate with f8:df:a8:33:0e:7f (SSID='VHC' freq=2452 MHz)
    wlan0: Trying to associate with f8:df:a8:33:0e:7f (SSID='VHC' freq=2452 MHz)
    wlan0: Associated with f8:df:a8:33:0e:7f
    wlan0: CTRL-EVENT-DISCONNECTED bssid=f8:df:a8:33:0e:7f reason=3 locally_generated=1
    wlan0: SME: Trying to authenticate with f8:df:a8:33:0e:7f (SSID='VHC' freq=2452 MHz)
    wlan0: Trying to associate with f8:df:a8:33:0e:7f (SSID='VHC' freq=2452 MHz)
    wlan0: Associated with f8:df:a8:33:0e:7f
    wlan0: CTRL-EVENT-DISCONNECTED bssid=f8:df:a8:33:0e:7f reason=3 locally_generated=1
    dbus: wpas_dbus_bss_signal_prop_changed: Unknown Property value 7
    Edit:
    I reported this.
    Last edited by rosenrot (2013-08-08 13:35:18)

    rosenrot wrote:I solved it with downgrading, I think its a Bug.
    1. Not exactly a solution, more like a temporary workaround.
    2. Please open a bug report, although dhcpcd 6.0.5-1 works fine for me.
    3. When pasting configs, code or command output, please use [ code ] tags https://bbs.archlinux.org/help.php#bbcode
    like this
    It makes the code more readable and - in case of longer listings - more convenient to scroll through.

  • Firefox boots slow after upgrading to v28

    After upgrading to v28, firefox boots in 8secs instead of 1sec, only when I "Use hardware acceleration when available".
    My graphics card is NVIDIA GeForce GTX 550 Ti, with 335.23 drivers installed.
    The problem occurs in soft and hard boot (even if i close firefox and re-execute it.)
    Is there something I could do?

    If hardware acceleration in Firefox isn't working properly then you will have to disable it and possibly check if there is an update for the graphics display driver.
    *https://support.mozilla.org/kb/upgrade-graphics-drivers-use-hardware-acceleration

  • DROID in boot loop after OTA update

    Just accepted the update today.  After phone updated and attempted to reboot...its in a continuous boot loop.  How can I stop it?

    Try taking the battery out.  If it still loops when you try to power it on, then the only other thing to try besides a factory reset is to take it to a verizon store and see if they can do anything.

  • KB300061 - Boot loop after isntalling

    We are in an enterprise running Win 7 x64 on all of our workstations. Our updates are managed by WSUS, and we have an auto approval setup to allow critical and security updates to be installed. This morning, several of our workstations requested a reboot
    to finish applying updates. Upon rebooting, many of them were stuck in a boot loop. Windows would attempt to load, it would then blue screen for a fraction of a second, then brought up the recovery menu. Here's what we've tried:
    - Startup repair
    - MBR repair
    - SFC /scannow
    - DISM (tried removing packages individually and rolling back)
    - System restore (no restore points) 
    - wusa to uninstall packages by KB (catastrophic failure) 
    - Safe mode doesn't boot
    None of what we knew to try worked. The one thing the computers stuck in the boot loop have in common is the model number. They are all HP Probooks, sharing the same model number. None of my other computers in the enterprise had trouble applying the updates.
    I'm conflicted. Any advice or help would be appreciated! 

    Hi,
    Please refer to my reply in another thread, follow the steps to troubleshoot your problem for test.
    https://social.technet.microsoft.com/Forums/windows/en-US/3d9d948e-eaf9-43e0-92e7-bebb96cb6180/stop-error-0x7b-after-windows-updates-101410152014?forum=w7itproappcompat#73e3402b-c420-48c6-b2e7-b4a6a5be327c
    Roger Lu
    TechNet Community Support

Maybe you are looking for