Arch Live CD x64 hanging during boot at "triggering uevents"

Hello!
I recently was recommended Arch by a friend, and after I followed the 'Newbies Guide' and burning a live CD to install Arch with, it appears to hang during Live CD boot at "installing uevents."
I am trying to install Arch as a dual boot on a late 2008 MacBook Pro which is currently running x64 Windows 7. I have plenty of HD space (100gb free and 100gb unallocated to install Arch onto).
Here is a picture:
http://i.imgur.com/Y8P41nf.jpg
I get the same error weather I try to install x64 or i686 (I think that's what it's called). Is there any reason for this?
Thank you!
-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code --
(Sorry, missed that. My bad!)
Last edited by RalphORama (2013-09-07 03:09:13)

frank604 wrote:
You can try nomodeset.  Seems to be a failure in loading a driver for your hardware. To read more on similar issues, there's a few posts with more info and suggestions by googling it. 
Google result: http://lmgtfy.com/?q=halt+at+triggering+uevent
Results:
https://bbs.archlinux.org/viewtopic.php?id=151259
https://bbs.archlinux.org/viewtopic.php?id=140426
Thanks! I tried googling it myself but got mostly answers that didn't work. I'll try this!

Similar Messages

  • Ultra 5 Hangs During Boot

    My Ultra 5 hangs during boot at the following point....
    setting default ipv4 interface......
    I have tried resetting my router, unplugging the network cable, and nothing seems to work.
    John

    jmorrissey3, is this a system that just suddenly stopped working, or is this a "new" system (it's not like Ultra 5s are really new) that you're trying to bring up?
    If this is a new system for you to tinker with, you should just go ahead and reinstall the operating system. This will blow everything away, of course, but it's good experience if you've never done it before and it will guarantee that the system is clean.
    If the data on there must be retained, you can boot from CD-ROM, mount the / partition, and look at some of the configuration files to try to isolate the problem. I would agree that it either is set up for DHCP and there is no DHCP server or there is an invalid NFS mount that is trying to take place.

  • K8N Neo 2 Platinum -- Hanging during boot --RESOLVED--

    Heres the problem...
    My system will hang during boot at anytime, from bios initalization to full windows boot (No BSOD ever and where the pc hangs in the boot proccess is totally random). And the only way to get past the hang is do a soft reset. I have to restart my system up to 3 times before I get a good boot, but once the pc is up and running, it stay running till I shut it down. (no hangs)
    Now if I shut it down after the system has been running for a while, the pc will restart normally without any hangs. The hangs only occur after the pc has been down for a time.
    I have reseated all the connectors, the memory (even tried different slots), add-in cards, cpu.
    I have a clean install of Windows XP Pro (hard drives have been repartitioned and reformatted as NTFS)
    All fans are spinning up fine, all temps are within norm, power supply voltages are within norm.
    No phsysical signs of bad caps on the system board.
    I ran ran Memtest86 for 18 hours striaght with no errors.
    Ran CPU stress test with no problems.
    No IRQ,DMA,etc conflicts found.
    Windows records no errors during a freeze and I have checked for unwanted services/proccess as well.
    I have tried min install to no avail.
    Bois is retaining its settings (so bios battery is good)
    I do not over clock anything. Bios is set to discover all important setting automaticly. (Bios setting are the same now as they were 6 months ago)
    I am down to a possible cold solder joint on the system board?
    This problem started to occur about a month ago.
    If someone has seen this exact problem and has a resolution, well I would appreciate it if you passed along your knowladge 
    I am down to my last option of RMAing my system board. No. I have not replaced any components due to the fact I don't have extras lieing around nor can I spend the money just to troubleshoot :(
    Specs..
    Athlon 64 3500+
    2 gig (pqi TURBO 1GB 184-Pin DDR SDRAM DDR 400 (PC 3200) Unbuffered System Memory Model PQI3200-1024SB)  Ran in Dual config
    Geforce 6800  (BFG 6800 GT oc)
    Creative X-Fi XtremeMusic
    Antec NeoPower 480
    2 WD 36gig SATA Raptors in raid 0 (system partition)
    2 WD 120gig IDE  in raid 0 (data partition)
    Windows XP Pro
    all drivers and bios are manufacture ref and up-to-date.
    Ok I won't go into all the details of why I missed this but it turns out the northbridge heatsink fan had stopped spinning and thus the hangs during boot due to overheating (hhmmm, when I step back and look at this the symptoms point right to overheating).
    This also expains why after several attempts at booting up, once the pc was up it would run like a champ. The chip would of course overheat and cause random freezes. Now due to the placement of the chip and the design of the heatsink once there was enough airflow over the heatsink the chip would remain cool enough to prevent further freezing of the system.
    What helped to facilitate this is that I have a ducted fan system installed in the bottom of my case which directs a substantal amount of fresh air to the pci slots, the chip set and the AGI slot as well.
    So what have we learned class?
    1. check the obvious
    2. do a complete physical inspection of your system
    3. KISS  -- keep it simple stupid

    Is this your ram:
    Quote
    Part Number: PQI3200-1024SB
    Quality Control: Comprehensively and rigorously tested
    Package: 1024MB single pack
    Organization: 128M x 64-bit
    CAS Latency: 3-4-4-8
    Test Voltage: 2.6 V
    PCB Board: 8 Layers PCB
    Heat Spreader: Mirrored Black Copper
    Speed: DDR 400 MHz (PC3200)
    Type: 184-pin DDR SDRAM
    Error Checking: Non-ECC
    Registered/Unbuffered: Unbuffered
    Warranty: Lifetime
    This is a quote from MSI web site:
    Quote
    Main Memory
      • Supports dual channel DDR 266/333/400, using four 184-pin DDR DIMMs.
    • Supports the memory size up to 4GB 
    • Supports 2.5v DDR SDRAM DIMM 
    Due to the High Performance Memory design, motherboards or system configurations may or may not operate smoothly at the JEDEC (Joint Electron Device Engineering Council) standard settings (BIOS Default on the motherboard) such as DDR voltage, memory speeds and memory timing. Please confirm and adjust your memory setting in the BIOS accordingly for better system stability.
    Example: Kingston HyperX DDR500 PC4000 operates at 2.65V, 3-4-4-8, CL=3.
    For more information about specification of high performance memory modules, please check with your Memory Manufactures for more details.
    Manually adjust your ram voltage to 2.65 volts and then manually adjust your ram timings to 3-4-4-8-2T.
    If that does not work then do as Richard suggested and strip down to a bar-bone system, this is CPU+fan, 1 stick of ram (try other stick and different slots as one may be bad), graphic card and PS-2 keyboard, if it boots fine without any problems then add one device at a time until you find the problem.
    Post back results as there are more things one can try but lets start with the simple stuff and work up.

  • P205-s6237 Hangs during boot to recovery after replace HDD

    I replaced a bad HDD and the machine hangs during boot to the recovery disk. it gets past the inspecting screen and then hangs when the VISTA dots appear. the dots continue to scroll left to right but nothing ever happens. Any ideads on getting it past this point?

    I replaced a bad HDD and the machine hangs during boot to the recovery disk. it gets past the inspecting screen and then hangs when the VISTA dots appear. the dots continue to scroll left to right but nothing ever happens. Any ideads on getting it past this point?

  • Hangs during boot after upgrading to Kernel 2.6.39

    I have just installed Arch on a new computer. It works fine until I upgrade to Kernel 2.6.39. After that it hangs on boot.
    The end of /var/log/everything.log is posted below.
    Jul 26 23:52:06 localhost kernel: [ 6.036766] [drm] nouveau 0000:04:00.0: Parsing VBIOS init table at offset 0x85F3
    Jul 26 23:52:06 localhost kernel: [ 6.129046] adt7475 1-002e: ADT7473 device, revision 1
    Jul 26 23:52:06 localhost kernel: [ 6.138997] [drm] nouveau 0000:04:00.0: Detected monitoring device: adt7473
    Jul 26 23:52:06 localhost kernel: [ 6.139000] [drm] nouveau 0000:04:00.0: 1 available performance level(s)
    Jul 26 23:52:06 localhost kernel: [ 6.139002] [drm] nouveau 0000:04:00.0: 0: memory 405MHz core 270MHz shader 540MHz
    Jul 26 23:52:06 localhost kernel: [ 6.139233] [TTM] Zone kernel: Available graphics memory: 12371030 kiB.
    Jul 26 23:52:06 localhost kernel: [ 6.139236] [TTM] Zone dma32: Available graphics memory: 2097152 kiB.
    Jul 26 23:52:06 localhost kernel: [ 6.139238] [TTM] Initializing pool allocator.
    Jul 26 23:52:06 localhost kernel: [ 6.139252] [drm] nouveau 0000:04:00.0: Detected 5376MiB VRAM
    Jul 26 23:52:06 localhost kernel: [ 6.139260] mtrr: type mismatch for d0000000,8000000 old: write-back new: write-combining
    Jul 26 23:52:06 localhost kernel: [ 6.150626] [drm] nouveau 0000:04:00.0: 512 MiB GART (aperture)
    Jul 26 23:52:06 localhost kernel: [ 6.152371] [drm] nouveau 0000:04:00.0: failed to load fuc409d
    Jul 26 23:52:06 localhost kernel: [ 6.176193] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
    Jul 26 23:52:06 localhost kernel: [ 6.176195] [drm] No driver support for vblank timestamp query.
    Jul 26 23:52:06 localhost kernel: [ 6.228800] No connectors reported connected with modes
    Jul 26 23:52:06 localhost kernel: [ 6.228802] [drm] Cannot find any crtc or sizes - going 1024x768
    Jul 26 23:52:06 localhost kernel: [ 6.231002] [drm] nouveau 0000:04:00.0: allocated 1024x768 fb: 0x8020000, bo ffff880608d97800
    Jul 26 23:52:06 localhost kernel: [ 6.233786] Console: switching to colour frame buffer device 128x48
    Jul 26 23:52:06 localhost kernel: [ 6.235094] fb0: nouveaufb frame buffer device
    Jul 26 23:52:06 localhost kernel: [ 6.235094] drm: registered panic notifier
    Jul 26 23:52:06 localhost kernel: [ 6.235098] [drm] Initialized nouveau 0.0.16 20090420 for 0000:04:00.0 on minor 0
    Jul 26 23:52:06 localhost kernel: [ 6.255449] HDA Intel 0000:04:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
    Jul 26 23:52:06 localhost kernel: [ 6.255451] hda_intel: Disable MSI for Nvidia chipset
    Jul 26 23:52:06 localhost kernel: [ 6.255599] HDA Intel 0000:04:00.1: setting latency timer to 64
    Jul 26 23:52:06 localhost kernel: [ 7.663482] EXT4-fs (sda3): re-mounted. Opts: (null)
    Jul 26 23:52:06 localhost kernel: [ 7.807508] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
    Jul 26 23:52:06 localhost kernel: [ 7.851401] Adding 265068k swap on /dev/sda2. Priority:-1 extents:1 across:265068k
    Jul 26 23:52:06 localhost kernel: [ 8.569682] r8169 0000:08:00.0: eth0: link down
    Jul 26 23:52:06 localhost kernel: [ 8.569687] r8169 0000:08:00.0: eth0: link down
    Jul 26 23:52:06 localhost dhcpcd[747]: eth0: waiting for carrier
    Jul 26 23:52:08 localhost dhcpcd[747]: eth0: carrier acquired
    Jul 26 23:52:08 localhost kernel: [ 10.301736] r8169 0000:08:00.0: eth0: link up
    Jul 26 23:52:08 localhost dhcpcd[747]: eth0: broadcasting for a lease
    Jul 26 23:52:12 localhost dhcpcd[747]: eth0: offered 131.181.53.42 from 131.181.127.32
    Jul 26 23:52:13 localhost dhcpcd[747]: eth0: acknowledged 131.181.53.42 from 131.181.59.48
    Jul 26 23:52:13 localhost dhcpcd[747]: eth0: checking for 131.181.53.42
    Jul 26 23:52:18 localhost dhcpcd[747]: eth0: leased 131.181.53.42 for 43200 seconds
    Jul 26 23:52:18 localhost dhcpcd[747]: forked to background, child pid 774
    Jul 26 23:52:18 localhost crond[823]: /usr/sbin/crond 4.5 dillon's cron daemon, started with loglevel info
    Jul 26 23:53:01 localhost crond[823]: FILE /etc/cron.d/prune-cronstamps USER root PID 835 job prune-cronstamps
    Jul 26 23:53:01 localhost crond[823]: FILE /var/spool/cron/root USER root PID 836 job sys-hourly
    Jul 26 23:53:01 localhost crond[823]: FILE /var/spool/cron/root USER root PID 837 job sys-daily
    Jul 26 23:53:01 localhost crond[823]: FILE /var/spool/cron/root USER root PID 838 job sys-weekly
    Any help fixing this would be greatly appreciated.

    I have been trying to isolate the problem a little further. I re-installed (with just the base and sudo) and after upgrading pacman rebooted and it worked without fail. Then I installed libusb and libusb-compat which where required when I tried to upgrade just the kernel using
    pacman -S kernel26
    which initially failed because of the missing dependencies libusb and libusb-compat. I then re-booted and that worked without a problem.
    I then upgraded to Kernel 2.6.39 using the above command and then it hung on rebooting. I saved the logs at each stage.
    The additional logs in errors.log in the reboot that failed are as follows.
    ul 26 16:28:39 O313 kernel: [ 5.120698] [drm] nouveau 0000:04:00.0: Pointer to BIT loadval table invalid
    Jul 26 16:28:39 O313 kernel: [ 5.360508] [drm] nouveau 0000:04:00.0: failed to load fuc409d
    Jul 26 16:28:39 O313 kernel: [ 5.808016] sd 20:0:0:0: [sdb] Assuming drive cache: write through
    Jul 26 16:28:39 O313 kernel: [ 5.809960] sd 20:0:0:0: [sdb] Assuming drive cache: write through
    Jul 26 16:28:39 O313 kernel: [ 5.812116] sd 20:0:0:0: [sdb] Assuming drive cache: write through
    Jul 26 16:28:35 O313 udevd[369]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'
    The end of kernel.log is as follows:
    Sat Jul 9 14:57:41 CEST 2011
    Jul 26 16:28:39 O313 kernel: [ 0.000000] Command line: root=/dev/disk/by-uuid/e4733c60-3e54-4001-a83e-415b690dfcb0 ro
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-provided physical RAM map:
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 0000000000100000 - 00000000cfed0000 (usable)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000cfed0000 - 00000000cfed1000 (ACPI NVS)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000cfed1000 - 00000000cfee0000 (ACPI data)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000cfee0000 - 00000000cff00000 (reserved)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 0000000100000000 - 0000000630000000 (usable)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] NX (Execute Disable) protection: active
    Jul 26 16:28:39 O313 kernel: [ 0.000000] DMI 2.4 present.
    Jul 26 16:28:39 O313 kernel: [ 0.000000] DMI: Gigabyte Technology Co., Ltd. X58A-UD5/X58A-UD5, BIOS FD 02/01/2011
    Jul 26 16:28:39 O313 kernel: [ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] No AGP bridge found
    Jul 26 16:28:39 O313 kernel: [ 0.000000] last_pfn = 0x630000 max_arch_pfn = 0x400000000
    And this is the end of daemon.log
    Jul 26 16:27:49 O313 init: Switching to runlevel: 6
    Jul 26 16:27:50 O313 dhcpcd: received SIGTERM, stopping
    Jul 26 16:27:50 O313 dhcpcd: eth0: removing interface
    Jul 26 16:28:39 O313 2.352592] udevd[87]: starting version 171
    Jul 26 16:28:39 O313 4.531007] udevd[370]: starting version 171
    Jul 26 16:28:39 O313 dhcpcd: version 5.2.2 starting
    Jul 26 16:28:39 O313 dhcpcd: eth0: waiting for carrier
    Jul 26 16:28:35 O313 udevd[369]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'
    Jul 26 16:28:39 O313 init: Entering runlevel: 3
    Please let me know if any further information would be useful in tracking down this problem. Also ignore any timings in my initial post they were incorrect.
    Last edited by TheStatsMan (2011-07-26 07:40:48)

  • How can I get the arch logo in console/terminal during boot?

    Hello
    I just installed arch as my first linux, and I would like to get the arch logo in the top left corner during boot, like on the following screenshot:
    http://i4.photobucket.com/albums/y132/s … h_boot.png
    uname  -a:
    Linux 3.6.6.1-ARCH #1
    syslinux bootloader
    How can I do that?
    Thanks a lot and greetings

    I'm not sure what's the situation now, but you may not get the logo - neither the penguin nor Arch logo:
    * https://bbs.archlinux.org/viewtopic.php?id=120516
    * https://bbs.archlinux.org/viewtopic.php?id=122778
    * https://bbs.archlinux.org/viewtopic.php?id=124730

  • Multiple cPCI Graphics cards - System Hangs during Boot

    We have 2 Kontron dual output CP332 cPCI graphics cards to install into a NI PXI rack in order to give us 4 graphics outputs.
    When one card is installed it acts as the Primary graphics card and it is required to disable to NI on-board graphics card in order for this to boot and function correctley.
    If a 2nd Kontron CP322 card is added the system will hang during WinXP boot, as it switches from VGA to SVGA mode.
    Disabling the 2nd card via device manager allows the system to boot.
    Re-enabling the 2nd card once booted, then configuring with the ATI driver application allows the 4 graphics output to work as expected.
    If the system is re-powered it will once again hang during WinXp booting.
    Is there anything that can be configured on the NI Embedded PC (BIOS) to prevent this ?
    Is there anything in windows that can be set to prevent this ?
    Can we control the windows device manager from labview in order to enable/disable the 2nd card after power-on and before shutdown.
    many thanks

    Hi Scott,
    I have some more information for you regarding your issue. We have tested the Kontron CP332 with the PXI-8196.
    However when we tested the setup, we had 3 monitors working, the on-board graphics and the dual output from the card.
    Until we get the on-board graphics working with a single CP332 I don't think we will get bot CP332's working.
    So these are the steps to get on-board graphics working with a single Kontron card the steps come from talking to our PXI Product Support Engineer:
    "The first thing you need to make sure is that you are using the
    driver for Windows XP, and not the one for Windows 2000. Here's a link
    to the driver download page:
    http://us.kontron.com/index.php?searchword=cp+332&id=363
    Notice that the first two driver downloads look just the same, but if
    you hover over them and look at the url, you'll notice that the first
    one is for Windows 2000 (w2k), and the second one is for Windows XP
    (wxp). So, just make sure you are using the second one. The PSE did
    mention that she was initially using the Win 2k driver, and was having
    some issues with it hanging and all. Here's the information she sent me
    about how she was able to get things working:
    "Here is the info. My controller has BIOS version 1.3 but have him try this first before updating the BIOS.
    The Kontron Board is the CP 332. I was able to get all three monitors working with the PXI-8196.
    Configuration steps:
    1) Insert both the controller and the kontron board in the chassis.
    Note: When the computer is starting it will give you the Windows boot
    up screen on the DVI 1 on the Kontron board and then give you the login
    screen on the monitor connected to the 8196 so make sure you still have
    a monitor connected to the controller.
    2) Cancel the NI installation wizard if it comes up.
    3)
    Unzip the drivers and run the setup.exe file. Make sure you install
    both the ATI display driver and the ATI Control Panel. (Check the zip
    name to make sure you have the xp version of the driver)
    4) After
    restart go to the Display Properties and under the Settings tab you
    should have monitors 1 and 2 on Mobility Radeon 9000 (Kontron CP-332)."
    If you don't have BIOS version 1.20 or higher, please upgrade to BIOS version 1.30, if you need to upgrade the BIOS please make sure you fully understand the readme file. Then follow the steps above to enable triple output on the graphics cards.
    When you have this working please try adding the second Kontron card.
    Regards
    JamesC
    NIUK and Ireland

  • Mac Mini keeps hanging during boot

    My ~3 year old Mac Mini keeps freezing during booting with the error message "You need to restart your computer. Hold down the Power button...". This happens every time. Booting in safe mode works.
    This happened with Mac OS X Tiger but keeps happening even after I have completely reformatted that hard disk and reinstalled Leopard from scratch. There are no external devices connected to the computer besides the monitor and a bluetooth mouse and keyboard.
    After reading some discussion forums I have already tried starting into Open Bootware and running "reset-nvram" and "reset-all" but to no avail.

    Welcome to Apple Discussions!
    What you are suffering is a Kernel Panic, and given you have reformatted your drive and reinstalled MacOS, it would tend to suggest the issue is hardware related - most common culprit being RAM.
    http://docs.info.apple.com/article.html?artnum=106227 explains what kernel panics are, and http://www.thexlab.com/faqs/kernelpanics.html and http://www.index-site.com/kernelpanic.html may give some assistance in working through the problem to determine the cause.
    The one good thing is that your system appears sufficiently stable to allow you to boot to the Leopard installer and complete a full install. This makes it less likely there is a fundamental issue with the most expensive component of the system, the logic board.

  • OSX hangs during boot or install

    Hello all,
    I'm writing this because I'm not really sure where else to post this at to get an indepth answer. Currently I have a dual G4 450mhz AGP PowerMac that I bought used. When I purchased it, it had 768mb of ram and the only thing it didn't have was a working hard drive. After putting in a new hard drive the system worked great when i intially installed OS9 and later OSX for fun.
    However I had to remove the 768mb of RAM because a client PC needed it and that took priority over my dual G4 at the time. Just the other week I purchased 2 x 256mb of RAM from Omni Technologies (omnitechnologies.biz) which guarantees working ram for specified Apple systems.
    Upon receiving that ram and installing it, I powered on the G4 only to find it would "hang" when booting OSX (10.3.9). The symptoms are as follows: When powering on I hear the normal chime and the white screen with gray apple logo appears. Seconds later the spinning progress indicator shows up spinning in circles as OSX is booting. However after about 5 minutes with no DVD/hdd activitity, the system then hangs. The gray apple logo changes to a gray 'prohibited' logo. It's the logo of the circle with the slash through it. Like the kind you see over no-smoking signs.
    I figured the hard drive was messed up and I decided to reinstall OSX cleanly. However when I booted from the CD by pressing 'c', the EXACT SAME symptoms above happened. It was at this point I started getting really worried. So I decided to remove the hard drive temporarily and boot from the CD just to make sure it really was booting from the CD. Unfortunately the exact same symptoms happened.
    Out of desperation to make sure that my hardware was OK, I decided to install OS 9.2.1 which installed and WORKED perfectly. I also installed UbuntuPPC and Slackintosh versions of linux which also installed and worked perfectly.
    The issue appears to reside with OSX. I've borrowed friends cd's of 10.2-10.3 and all of them will NOT install. They start to boot from the CD, but never even make it to the first window.
    Help!!
    Brad

    Actually trying one stick in each individual slot was one of the first things I did. Unfortunately that did not provide a resolution for me.
    Thanks for the links regarding the broken folder/prohibitory sign. I read those and they made mention of resetting the nvram and pram. I just did that a bit earlier today but logging into the open firmware by pressing Option-Command-F-O and typing: reset-nvram; set-defaults; reset-all.
    Upon the reboot and after I plugged the hdd with OSX on it back into the system, the resolution was a bit off as I figured. But this time there was no progress indicator. Instead only the gray apple logo showed and there was no response from the hdd or cdrom drive.
    I also noticed that the USB mouses red light went out within the first 45 seconds of booting. I swapped out keyboards and mice and the new ones did the same thing as well. I also tested the memory in an imac I have and OSX that is installed ont heimac works gerat with that stick of memory. I'm leaning towards the fact that the memory I have is fine, being that it was ordered from a company that specifically guaranteed it to work on macs of all kinds.
    Any other thoughts or ideas?

  • Replace the arch logo in the framebuffer during boot?

    since the tango version of the arch logo http://www.archlinux.org/media/logo.png is also used on the homepage and since it looks better than the currently used (IMHO ), i would like to know how people would think about replacing the current icon during bootup: http://www.archlinux.org/logos/archlinux_logo_aqua.png with the tango version?
    i think it would look better.

    onearm wrote:
    scottlc wrote:The beyond kernel package has fbspash support for those who want a graphical boot.
    Yeah, I know and it's what I'm using right now 
    What I meant was why not using fbsplash/gensplash/splashy with a arch-based theme (from 800x600 till 1900x1200 or similar resolution to satisfy everybody needs) by default? Why only a little logo when you can have better resolution and a nicer without-X look?
    Obviously with the beyond and/or the vanilla kernel.
    Not everyone wants a graphical bootup. And some cards don't support framebuffer and throw error messages. My card did this until kernel 2.6.18.

  • Plymouth causes tty1 to tty6 to hang during boot

    Hello,
    During the boot process of my Arch installation the screen is halted at terminal login and password, where I previously had configured Arch to automatically start X. Now, I've also noticed that tty2 to tty6 are not available in the beginning and then every 10 seconds one extra comes available. The cause, has something to do with Plymouth.
    I installed Plymmouth, but failed to get it running. Then I inunstalled, removed the hooks from /etc/
    mkinitcpio.conf. Also rebuilt initrd image, but somehow Plymouth still tries to start. I've added a bootlog in which the problem is very clearly reported (from line 163 or so). (I'm not sure how to post, so I just post the link to pastebin)
    How can I solve this problem?
    http://pastebin.com/FR6AW7Ak
    Last edited by Archer22 (2014-09-23 07:52:57)

    jasonwryan wrote:
    Please read the Etiquette entry on how to post (https://wiki.archlinux.org/index.php/Fo … ow_to_Post): note the one topic per thread to make things manageable.
    Are you sure that you removed plymouth from your initrd?
    Not a Sysadmin issue, moving to NC...
    I edited my post. Yes I think removed Plymouth from initrd through the following command:
    # mkinitcpio -p linux
    Is there anyway I can check? Also, I was thinking maybe the fallback image is used, where plymouth is still configured to start?

  • [SOLVED (mysteriously)] Arch on USB not recognized during boot

    Hi there,
    I hope, someone can help me with my problem, I have been searching and trying different things for quite some time now, without success.
    I treated myself a new Notebook, Acer Aspire S7 and wanted to run Arch on it. However I am new to Linux and want to try it out on an USB-Stick, to keep the factory install of Win8 intact. (Also, this notebook does not have such a great HDD capacity) Additionally I want to have full disk encryption.
    So I followed the Beginner's Guide with modifications described here and here
    When it came to install the bootloader I chose Grub for EFI.
    I then removed the USB-Stick with the live-Arch, which I used for installation and rebooted and it worked!
    However: As soon as I completely shut down and boot again, the USB-Stick with my installation is no longer recognized. If i boot the live-Arch again, reinstall Grub and then reboot, it again works.
    Here is something, I found strange. This is the output of efibootmgr:
    BootCurrent: 0000
    Timeout: 0 seconds
    BootOrder: 2001,0003,0002,2002,2003
    Boot0000* USB HDD: KingstonDataTraveler 2.0
    Boot0001* Intel HDD0
    Boot0002* Windows Boot Manager
    Boot0003* arch_grub
    Boot2001* EFI USB Device
    Boot2002* EFI DVD/CDROM
    Boot2003* EFI Network
    BootCurrent is 0000, but that number does not appear in the Boot-Order list. Could that be something?
    Well, I hope someone has an idea. I will happily share any information about my setup with you, just ask.
    Thanks,
    Max
    Last edited by MaxT (2014-04-07 08:35:20)

    Sorry for digging that threat up again. I just wanted to share with you the solution to the problem I was having. Perhaps it will save someone else some frustration.
    The Acer Aspire S7 has a dongle that goes in the display port and provides an ethernet and an VGA port. It was that dongle that prevented the USB stick with the Arch installation from being recognized. Done attached -> USB stick was ignored, dongle detached -> it worked.
    I have no idea, why that is the case, but maybe this info is helpful for someone.
    Cheers,
    Max

  • V570 hangs during boot up - message "please wait"

    I just got a new V570 Lenovo IdeaPad laptop on Sunday. It was working fine until Monday. I tried to start it up and it paused at the Please Wait screen. I didn't know what to do so I held the power button until it shut down. I then left it for a bit and it started up fine. Now, this has happened again and I am guessing it is not good. How can I fix it?
    Solved!
    Go to Solution.

    UPDATE - OFFICIAL LENOVO SOLUTION
    Please follow the link above to the Lenovo support site - this tip covers a software hang condition / please wait message caused by an interaction with the fingerprint reader and veriface software which may develop under certain conditions on V470/V570 and B470/B570 systems.
    who knows - you may have fixed it (DMB stack in CMOS).  edit: removed suggestion about safe start since it didn't work..
    The removing the battery and the power cord is similar to what we had to do with desktop mobos - unplug it , wait 10 seconds, press power-on a few times to bleed the power off the PSU, and then plug it in and start up - it takes power off the BIOS and causes it to re-create the DMB stack the next time you boot.  DMB = info about each device .
    I also advise you to get current with MS updates (not necessarily all the optional ones!).
    IdeaPad V570-1066A9U, Built 5-22-2011, BIOS 44CN36WW(2011-08-04)
    Win7 Pro x64 clean install. Sammy 840 Pro 128GB SSD. Fast! Used nice hardware manual to re-grease CPU and remove tiny bit of lint.

  • T61 sometimes hangs during boot

    Sometimes when booting my T61  it hangs about 4 sec into it after displaying one icon in the system tray.  After that the only activity is the hard drive indicator blicking about once every 5 seconds.  When I manually turn off the computer then reboot sometimes it repeats this and sometimes not.  Sometimes it takes 3 or 4 manual reboots before it starts booting normally again.  The last time it started right after I removed the AC power and went on battery then rebooted but the problem has occurred regardless of power source.

    speedkreature, welcome to the forum,
    what you have experienced is definitely not normal, I'd go as far as saying weird.
    Does the same happen running without the battery? Has your RAM also been swapped out? If you are running with two sticks of RAM, does the same happen running with one, (swapping sticks and slots etc.)?
    All that would then remain would be to remove the WLAN and BT cards.
    Andy  ______________________________________
    Please remember to come back and mark the post that you feel solved your question as the solution, it earns the member + points
    Did you find a post helpfull? You can thank the member by clicking on the star to the left awarding them Kudos Please add your type, model number and OS to your signature, it helps to help you. Forum Search Option T430 2347-G7U W8 x64, Yoga 10 HD+, Tablet 1838-2BG, T61p 6460-67G W7 x64, T43p 2668-G2G XP, T23 2647-9LG XP, plus a few more. FYI Unsolicited Personal Messages will be ignored.
      Deutsche Community     Comunidad en Español    English Community Русскоязычное Сообщество
    PepperonI blog 

  • 2007 MacBook Pro Snow Leopard hangs during boot up

    All I get is the grey screen and the little circle with the rotating fan blades.  Then they stop spinning and it just hangs.
    I cannot boot up.   Is this a bad hard drive?
    Are there other keys I could hit to make something work?
    Thanks for looking at this last cry for help before I take it in.

    Try booting in Safe Mode by holding the Shift key down on startup until you see the grey Apple backdrop with the spinning cogwheel and progress bar. You can let go of the Shift key when the progress bar appears. Booting in Safe Mode takes a long time, so be patient. Log in to your account, and reboot normally when you have reached a fully functional Desktop.

Maybe you are looking for