PowerBook G4 12" 1.33ghz hangs on boot after installing Leopard

I have a Powerbook G4 40gig HD; 512 RAM, 1.33 processor which has a spinning icon on boot under an Apple symbol. I left the computer to work on booting for an hour. Yes, the clock spun for an hour. To solve the problem, I just installed Leopard; and then when it persisted, I reset PRAM, and Power Manager, and then tried to use the recent posting information from Apple on modifying the system. Last step was to boot from the the Leopard installer in and cannot get it to obey to command to boot from CD.
grrrr.
No firewire cable availabe to put in target disk mode.
Any ideas on what is wrong?

I've seen reports that if the internal clock battery has failed, you can get into a totally bricked state like this during an install as apparently some critical step depends upon that battery working.
Have you found yourself having to reset the clock manually upon power up prior to your attempt to install Leopard?
If that's what's going on, you'll need to get Apple service to replace the battery, then you should be able to start over on the Leopard install by booting directly from the Leopard DVD.

Similar Messages

  • After installing Leopard, my G4 will no longer boot in OS 9.22. (Classic still works, but I need it to boot in OS 9.)  Any clues about what the Leopard installer might have done to my machine that rendered OS 9 boot unusable? What can I do to fix it?

    After installing Leopard, my G4 will no longer boot in OS 9.22.
    (Classic still works, but I need it to boot in OS 9.)
    Any clues about what the Leopard installer might have done to my machine that rendered OS 9 boot unusable? (And what can I do to fix it?)
    Details:
    G4 Gigabit Ethernet
    Boot ROM version: 4.2.8fl
    Accelerator card added: 1.6 MHz
    1.5 Gig Ram
    I have erased the partition that had Leopard installed on it.
    I zapped the pram.
    In Open Firmware, I "reset-nvram", and then "reset-all"
    I tried to reinstall G4 FW Update 4.2.8, but that must be done when booted from OS 9, and of course, that's the problem: it won't boot into 9.
    I tried restarting from 9.2.1 DVD.
    I tried restarting from an external firewire drive containing OS 9.2.2.
    I tried moving a fresh OS 9.2.2 system folder into an empty partition on an internal hard drive. (Partition was created WITH OS 9 drivers installed.)
    All attempts to boot into OS 9 give me the same results - grey screen - no spinning beach ball, no icons or logos - just a blank grey screen.
    This machine still works fine in OS 10.3 and 10.4, and it worked fine for many years booting into OS 9, until I installed Leopard, and I haven't been able to boot into OS 9 since then, although I have done considerable research online and tried many things.
    I have since learned that this machine does not support Leopard - 10.5. Fine, but how did it break 9.2.2?
    Any help greatly appreciated.

    Thanks for checking in, BDAQua.
    Problem solved.
    In the docs that came with my Powerlogix accelerator card, I found this sentence buried:
    "If you reset the PRAM, the NVRAM code for OS9 compatibility is cleared, so you will have to boot from the Firmawre Update CD and perform this process again in order to boot in OS9."
    The "process" it's referring to is the process of setting up the NVRAM for booting into OS9 from the CD.
    Fortunately, I was able to find the disk, and it worked as expected. I can now, once again boot into OS9.
    Conclusion: My (unadvised) attempt to load Leopard on this old machine apparently reset the PRAM on the accelerator card and cleared the NVRAM code for OS9 boot. Although I did attempt to reset the NVRAM via Open Firmware, it did not reset it on the accelerator card.
    So, thank you BDAQua, for your "Ah yes" . . . that's all I needed to steer me in the right direction.
    Gratefully,
    tupester

  • Windows 8.1 Pro not booting after install of Hyper V - ASUS z87 + intel 4670K

    Hi,
    I am running windows 8.1 pro on a intel 4670K 4th Gen Haswell CPU and ASUS z87 plus motherboard. 16gb of kingston hyperx ddr1600 memory.
    I have enabled virtualisation technology in the bios.  CPU has SLAT.... or Extended Page Table, as intel likes to refer to it.
    When I install HyperV platform and management tools the computer configures and reboots
    AFter reboot it brings up the blue window image and spinning circle of dots for a while then reboots. It does the same thing again and then reboots and goings into repair mode and asks me to do a system restore. It then restores to before they HyperV install.
    I've tried turning off xHCI mode (i.e USB 3.0) in the bios as this seemed to be a known issue with some gigabyte boards. This did not rectify the issue
    Updated to latest asus mainboard bios 1405.  Same issue still occurs upon install of hyper V.
    Automatic repair does not work and I have to restore from system restore point.
    I performed a clean boot after installing the feature and it still couldnt boot to windows.. it just sits at windows logo and then restarts a few times and then launches the startup repair. Once the startup repair begins, the only way I can get into windows
    is restoring to a system restore point from before the hyperv feature install.
    Please see the following logs which may have further information:
    CBS Log 
    https://skydrive.live.com/redir?resid=1F523A0B8734322C!685&authkey=!AGMjUfosLFpzYNI
    Setuperr
    https://skydrive.live.com/redir?resid=1F523A0B8734322C!682&authkey=!AKS8Jb1S6W2IAH8
    Windows update
    https://skydrive.live.com/redir?resid=1F523A0B8734322C!683&authkey=!AJdWKuKj4negBoQ
    Windowsupdate(1)
    https://skydrive.live.com/redir?resid=1F523A0B8734322C!684&authkey=!APplVjuLpNZW_AY
    I logged a job with asus support and their response was:
    "Clear CMOS and ensure virtualisation technology is turned on in BIOS. If it still doesn't work, seek assistance from Microsoft"
    Previously asked this question but took a while to get back to update with the logs and it was listed as Answered.
    This issue is still existing and I'd appreciating any assistance. 
    Simon

    Hi Simon,
    Thank you for uploading the Log files.
    According to the log files, no actuate clue can be found. 
    So, I suggest you upload the dump file so that we can help you analyze them.
    Automatic Memory Dump Settings on Windows 8:
    http://www.thewindowsclub.com/automatic-memory-dump-settings-windows-8
    It also applies to windows 8.1.
    Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
    Note: I highly recommend you use SkyDrive to upload collected files and to post screen shots/pictures. Although you might not be used to it, SkyDrive features a lot of free advanced functionality around file storage capacity, sharing,
    privacy, and collaboration:
    http://skydrive.com
    Regards,
    Kelvin hsu
    TechNet Community Support

  • Will not start even in safe boot after installing latest camera update

    MacBook Pro will not start even in safe boot after installing latest camera update.
    I started my machine and did a software update. Only the camera update needed. So installed and when required I pressed restart. It restarted and did install. Then restarted again. I expected to get to the login screen and it turned itself off. Tried three more times. Each time shutting off. I unplugged everything, and pressed start waiting for log in window. No it shutdown before the log in window. I then tried safe mode and that did not work either on three more occasions.

    I have managed to resolve some issues. I can now restart the machine via a CD boot. If I do cmd C into something like tech tool pro, then restart from that disks menu it restarts every time.
    If I try a safe start it shuts down. If I try a normal start it shuts down. I have managed to repair permissions and that cleared up some start up permissions but with no improvement to the boot problem. The only way to load is via the cmd-C boot option. Any other ideas?

  • Macbook pro won't boot after installing update 10.9.3

    macbook pro won't boot after installing update 10.9.3

    Please read this whole message before doing anything.
    This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
    The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
    Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode.
    Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Ask for further instructions.
    Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
    The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    Test while in safe mode. Same problem?
    After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

  • PowerBook G4 will not shut down after installing Leopard

    Hi - has anyone found shut down problems (or restart for that matter) after installing Leopard. I've got 30Gb of hard drive free on a Powerbook G4 (3 years old).

    No I don't.
    Looking around for answers to this one it seems it is a fairly common problem with new Leopard users. One solution (apparently from Apple) was to delete the cache folders in both the user's home folder and in the top-level system folder. I have tried that but no luck yet.

  • Very slow boot after installing 10.10.3

    insanely slow boot after installing 10.10.3, it takes 10times longer compare to 10.10.2, using MBA 2014

    Open System Preferences, select Startup Disk, and make sure your internal drive is selected as the startup disk. Then click restart!
    This worked for me, personally with the same issue.
    Good luck!

  • Hang on boot after upgrade to kernel 2.6.31 [SOLVED]

    hey all,
    My system hangs after installing 2.6.31.  the message is this:
    pci 0000:00:00.0: BAR 3: address space collision on of device [0xe0000000-0xffffffff]
    i tried 2.6.30, but compiz was too slow, so i went back to 2.6.29.  dmesg:
    Linux version 2.6.29-ARCH (root@T-POWA-LX) (gcc version 4.4.0 (GCC) ) #1 SMP PREEMPT Wed May 20 07:06:02 UTC 2009
    KERNEL supported cpus:
    Intel GenuineIntel
    AMD AuthenticAMD
    NSC Geode by NSC
    Cyrix CyrixInstead
    Centaur CentaurHauls
    Transmeta GenuineTMx86
    Transmeta TransmetaCPU
    UMC UMC UMC UMC
    BIOS-provided physical RAM map:
    BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
    BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)
    BIOS-e820: 00000000000e6000 - 0000000000100000 (reserved)
    BIOS-e820: 0000000000100000 - 00000000cfda0000 (usable)
    BIOS-e820: 00000000cfda0000 - 00000000cfdae000 (ACPI data)
    BIOS-e820: 00000000cfdae000 - 00000000cfdf0000 (ACPI NVS)
    BIOS-e820: 00000000cfdf0000 - 00000000cff00000 (reserved)
    BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved)
    BIOS-e820: 0000000100000000 - 0000000130000000 (usable)
    DMI present.
    AMI BIOS detected: BIOS may corrupt low RAM, working around it.
    last_pfn = 0xcfda0 max_arch_pfn = 0x100000
    x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    Scanning 0 areas for low memory corruption
    modified physical RAM map:
    modified: 0000000000000000 - 0000000000010000 (reserved)
    modified: 0000000000010000 - 000000000009f000 (usable)
    modified: 000000000009f000 - 00000000000a0000 (reserved)
    modified: 00000000000e6000 - 0000000000100000 (reserved)
    modified: 0000000000100000 - 00000000cfda0000 (usable)
    modified: 00000000cfda0000 - 00000000cfdae000 (ACPI data)
    modified: 00000000cfdae000 - 00000000cfdf0000 (ACPI NVS)
    modified: 00000000cfdf0000 - 00000000cff00000 (reserved)
    modified: 00000000fff00000 - 0000000100000000 (reserved)
    modified: 0000000100000000 - 0000000130000000 (usable)
    kernel direct mapping tables up to 377fe000 @ 10000-15000
    RAMDISK: 7fbab000 - 7ffef415
    Allocated new RAMDISK: 005a6000 - 009ea415
    Move RAMDISK from 000000007fbab000 - 000000007ffef414 to 005a6000 - 009ea414
    ACPI: RSDP 000F9410, 0014 (r0 ACPIAM)
    ACPI: RSDT CFDA0000, 003C (r1 7577MS A7577100 20090427 MSFT 97)
    ACPI: FACP CFDA0200, 0084 (r1 7577MS A7577100 20090427 MSFT 97)
    ACPI Warning (tbfadt-0596): Optional field Pm2ControlBlock has zero address or length: 0000000000000000/1 [20081204]
    FADT: X_PM1a_EVT_BLK.bit_width (16) does not match PM1_EVT_LEN (4)
    ACPI: DSDT CFDA0440, A216 (r1 A7577 A7577100 100 INTL 20051117)
    ACPI: FACS CFDAE000, 0040
    ACPI: APIC CFDA0390, 006C (r1 7577MS A7577100 20090427 MSFT 97)
    ACPI: MCFG CFDA0400, 003C (r1 7577MS OEMMCFG 20090427 MSFT 97)
    ACPI: OEMB CFDAE040, 0072 (r1 7577MS A7577100 20090427 MSFT 97)
    ACPI: HPET CFDAA660, 0038 (r1 7577MS OEMHPET 20090427 MSFT 97)
    ACPI: SSDT CFDAA6A0, 088C (r1 A M I POWERNOW 1 AMD 1)
    ACPI: Local APIC address 0xfee00000
    2437MB HIGHMEM available.
    887MB LOWMEM available.
    mapped low ram: 0 - 377fe000
    low ram: 00000000 - 377fe000
    bootmap 00011000 - 00017f00
    (9 early reservations) ==> bootmem [0000000000 - 00377fe000]
    #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
    #1 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000]
    #2 [0000006000 - 0000007000] TRAMPOLINE ==> [0000006000 - 0000007000]
    #3 [0000100000 - 00005a2604] TEXT DATA BSS ==> [0000100000 - 00005a2604]
    #4 [00005a3000 - 00005a6000] INIT_PG_TABLE ==> [00005a3000 - 00005a6000]
    #5 [000009f000 - 0000100000] BIOS reserved ==> [000009f000 - 0000100000]
    #6 [0000010000 - 0000011000] PGTABLE ==> [0000010000 - 0000011000]
    #7 [00005a6000 - 00009ea415] NEW RAMDISK ==> [00005a6000 - 00009ea415]
    #8 [0000011000 - 0000018000] BOOTMAP ==> [0000011000 - 0000018000]
    found SMP MP-table at [c00ff780] 000ff780
    Zone PFN ranges:
    DMA 0x00000010 -> 0x00001000
    Normal 0x00001000 -> 0x000377fe
    HighMem 0x000377fe -> 0x000cfda0
    Movable zone start PFN for each node
    early_node_map[2] active PFN ranges
    0: 0x00000010 -> 0x0000009f
    0: 0x00000100 -> 0x000cfda0
    On node 0 totalpages: 851247
    free_area_init_node: node 0, pgdat c0430600, node_mem_map c1000200
    DMA zone: 32 pages used for memmap
    DMA zone: 0 pages reserved
    DMA zone: 3951 pages, LIFO batch:0
    Normal zone: 1744 pages used for memmap
    Normal zone: 221486 pages, LIFO batch:31
    HighMem zone: 4876 pages used for memmap
    HighMem zone: 619158 pages, LIFO batch:31
    ACPI: PM-Timer IO Port: 0x808
    ACPI: Local APIC address 0xfee00000
    ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
    ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
    ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
    ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
    ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
    IOAPIC[0]: apic_id 4, version 33, address 0xfec00000, GSI 0-23
    ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
    ACPI: IRQ0 used by override.
    ACPI: IRQ2 used by override.
    ACPI: IRQ9 used by override.
    Enabling APIC mode: Flat. Using 1 I/O APICs
    Using ACPI (MADT) for SMP configuration information
    ACPI: HPET id: 0x8300 base: 0xfed00000
    SMP: Allowing 4 CPUs, 0 hotplug CPUs
    nr_irqs_gsi: 24
    PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
    PM: Registered nosave memory: 00000000000a0000 - 00000000000e6000
    PM: Registered nosave memory: 00000000000e6000 - 0000000000100000
    Allocating PCI resources starting at d0000000 (gap: cff00000:30000000)
    NR_CPUS:16 nr_cpumask_bits:16 nr_cpu_ids:4 nr_node_ids:1
    PERCPU: Allocating 36864 bytes of per cpu data
    Built 1 zonelists in Zone order, mobility grouping on. Total pages: 844595
    Kernel command line: root=/dev/disk/by-uuid/deebdc30-3ac7-4de2-81d2-eb4d199468b9 ro quiet vga=792 splash
    Enabling fast FPU save and restore... done.
    Enabling unmasked SIMD FPU exception support... done.
    Initializing CPU#0
    PID hash table entries: 4096 (order: 12, 16384 bytes)
    Fast TSC calibration using PIT
    Detected 3214.713 MHz processor.
    Console: colour dummy device 80x25
    console [tty0] enabled
    Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
    Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
    Memory: 3367428k/3405440k available (2363k kernel code, 36780k reserved, 1059k data, 340k init, 2496136k highmem)
    virtual kernel memory layout:
    fixmap : 0xffee8000 - 0xfffff000 (1116 kB)
    pkmap : 0xff800000 - 0xffc00000 (4096 kB)
    vmalloc : 0xf7ffe000 - 0xff7fe000 ( 120 MB)
    lowmem : 0xc0000000 - 0xf77fe000 ( 887 MB)
    .init : 0xc045d000 - 0xc04b2000 ( 340 kB)
    .data : 0xc034ec74 - 0xc0457a88 (1059 kB)
    .text : 0xc0100000 - 0xc034ec74 (2363 kB)
    Checking if this processor honours the WP bit even in supervisor mode...Ok.
    SLUB: Genslabs=12, HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
    hpet clockevent registered
    HPET: 4 timers in total, 1 timers will be used for per-cpu timer
    Calibrating delay loop (skipped), value calculated using timer frequency.. 6431.31 BogoMIPS (lpj=10715710)
    Security Framework initialized
    Mount-cache hash table entries: 512
    CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
    CPU: L2 Cache: 512K (64 bytes/line)
    CPU: Physical Processor ID: 0
    CPU: Processor Core ID: 0
    Intel machine check architecture supported.
    Intel machine check reporting enabled on CPU#0.
    using C1E aware idle routine
    Checking 'hlt' instruction... OK.
    ACPI: Core revision 20081204
    ACPI: Checking initramfs for custom DSDT
    ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    CPU0: AMD Phenom(tm) II X4 955 Processor stepping 02
    Booting processor 1 APIC 0x1 ip 0x6000
    Initializing CPU#1
    Calibrating delay using timer specific routine.. 6431.80 BogoMIPS (lpj=10714888)
    CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
    CPU: L2 Cache: 512K (64 bytes/line)
    CPU: Physical Processor ID: 0
    CPU: Processor Core ID: 1
    Intel machine check architecture supported.
    Intel machine check reporting enabled on CPU#1.
    x86 PAT enabled: cpu 1, old 0x7040600070406, new 0x7010600070106
    CPU1: AMD Phenom(tm) II X4 955 Processor stepping 02
    checking TSC synchronization [CPU#0 -> CPU#1]: passed.
    System has AMD C1E enabled
    Switch to broadcast mode on CPU1
    Booting processor 2 APIC 0x2 ip 0x6000
    Initializing CPU#2
    Calibrating delay using timer specific routine.. 6431.79 BogoMIPS (lpj=10714876)
    CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
    CPU: L2 Cache: 512K (64 bytes/line)
    CPU: Physical Processor ID: 0
    CPU: Processor Core ID: 2
    Intel machine check architecture supported.
    Intel machine check reporting enabled on CPU#2.
    x86 PAT enabled: cpu 2, old 0x7040600070406, new 0x7010600070106
    CPU2: AMD Phenom(tm) II X4 955 Processor stepping 02
    checking TSC synchronization [CPU#0 -> CPU#2]: passed.
    Switch to broadcast mode on CPU2
    Booting processor 3 APIC 0x3 ip 0x6000
    Initializing CPU#3
    Calibrating delay using timer specific routine.. 6431.80 BogoMIPS (lpj=10714888)
    CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
    CPU: L2 Cache: 512K (64 bytes/line)
    CPU: Physical Processor ID: 0
    CPU: Processor Core ID: 3
    Intel machine check architecture supported.
    Intel machine check reporting enabled on CPU#3.
    x86 PAT enabled: cpu 3, old 0x7040600070406, new 0x7010600070106
    CPU3: AMD Phenom(tm) II X4 955 Processor stepping 02
    checking TSC synchronization [CPU#0 -> CPU#3]: passed.
    Brought up 4 CPUs
    Total of 4 processors activated (25726.72 BogoMIPS).
    Switch to broadcast mode on CPU3
    Switch to broadcast mode on CPU0
    net_namespace: 1016 bytes
    Booting paravirtualized kernel on bare hardware
    NET: Registered protocol family 16
    ACPI: bus type pci registered
    PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
    PCI: Not using MMCONFIG.
    PCI: PCI BIOS revision 3.00 entry at 0xf0031, last bus=6
    PCI: Using configuration type 1 for base access
    PCI: Using configuration type 1 for extended access
    bio: create slab <bio-0> at 0
    ACPI: EC: Look up EC in DSDT
    ACPI: Interpreter enabled
    ACPI: (supports S0 S1 S3 S4 S5)
    ACPI: Using IOAPIC for interrupt routing
    PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
    PCI: MCFG area at e0000000 reserved in ACPI motherboard resources
    PCI: Using MMCONFIG for extended config space
    ACPI: No dock devices found.
    ACPI: PCI Root Bridge [PCI0] (0000:00)
    pci 0000:00:00.0: reg 1c 64bit mmio: [0xe0000000-0xffffffff]
    pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
    pci 0000:00:02.0: PME# disabled
    pci 0000:00:05.0: PME# supported from D0 D3hot D3cold
    pci 0000:00:05.0: PME# disabled
    pci 0000:00:06.0: PME# supported from D0 D3hot D3cold
    pci 0000:00:06.0: PME# disabled
    pci 0000:00:07.0: PME# supported from D0 D3hot D3cold
    pci 0000:00:07.0: PME# disabled
    pci 0000:00:09.0: PME# supported from D0 D3hot D3cold
    pci 0000:00:09.0: PME# disabled
    pci 0000:00:11.0: reg 10 io port: [0x8000-0x8007]
    pci 0000:00:11.0: reg 14 io port: [0x7000-0x7003]
    pci 0000:00:11.0: reg 18 io port: [0x6000-0x6007]
    pci 0000:00:11.0: reg 1c io port: [0x5000-0x5003]
    pci 0000:00:11.0: reg 20 io port: [0x3000-0x300f]
    pci 0000:00:11.0: reg 24 32bit mmio: [0xf9fffc00-0xf9ffffff]
    pci 0000:00:11.0: set SATA to AHCI mode
    pci 0000:00:12.0: reg 10 32bit mmio: [0xf9ffe000-0xf9ffefff]
    pci 0000:00:12.1: reg 10 32bit mmio: [0xf9ffd000-0xf9ffdfff]
    pci 0000:00:12.2: reg 10 32bit mmio: [0xf9fff800-0xf9fff8ff]
    pci 0000:00:12.2: supports D1 D2
    pci 0000:00:12.2: PME# supported from D0 D1 D2 D3hot
    pci 0000:00:12.2: PME# disabled
    pci 0000:00:13.0: reg 10 32bit mmio: [0xf9ffc000-0xf9ffcfff]
    pci 0000:00:13.1: reg 10 32bit mmio: [0xf9ffb000-0xf9ffbfff]
    pci 0000:00:13.2: reg 10 32bit mmio: [0xf9fff400-0xf9fff4ff]
    pci 0000:00:13.2: supports D1 D2
    pci 0000:00:13.2: PME# supported from D0 D1 D2 D3hot
    pci 0000:00:13.2: PME# disabled
    pci 0000:00:14.1: reg 10 io port: [0x00-0x07]
    pci 0000:00:14.1: reg 14 io port: [0x00-0x03]
    pci 0000:00:14.1: reg 18 io port: [0x00-0x07]
    pci 0000:00:14.1: reg 1c io port: [0x00-0x03]
    pci 0000:00:14.1: reg 20 io port: [0xff00-0xff0f]
    pci 0000:00:14.2: reg 10 64bit mmio: [0xf9ff4000-0xf9ff7fff]
    pci 0000:00:14.2: PME# supported from D0 D3hot D3cold
    pci 0000:00:14.2: PME# disabled
    pci 0000:00:14.5: reg 10 32bit mmio: [0xf9ffa000-0xf9ffafff]
    pci 0000:01:00.0: reg 10 32bit mmio: [0xfd000000-0xfdffffff]
    pci 0000:01:00.0: reg 14 64bit mmio: [0xd0000000-0xdfffffff]
    pci 0000:01:00.0: reg 1c 64bit mmio: [0xfa000000-0xfbffffff]
    pci 0000:01:00.0: reg 24 io port: [0x9800-0x987f]
    pci 0000:01:00.0: reg 30 32bit mmio: [0xfe7e0000-0xfe7fffff]
    pci 0000:00:02.0: bridge io port: [0x9000-0x9fff]
    pci 0000:00:02.0: bridge 32bit mmio: [0xfa000000-0xfe7fffff]
    pci 0000:00:02.0: bridge 64bit mmio pref: [0xd0000000-0xdfffffff]
    pci 0000:02:00.0: reg 10 io port: [0xa800-0xa8ff]
    pci 0000:02:00.0: reg 18 64bit mmio: [0xf8eff000-0xf8efffff]
    pci 0000:02:00.0: reg 20 64bit mmio: [0xf8ef8000-0xf8efbfff]
    pci 0000:02:00.0: reg 30 32bit mmio: [0xfe8e0000-0xfe8fffff]
    pci 0000:02:00.0: supports D1 D2
    pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    pci 0000:02:00.0: PME# disabled
    pci 0000:00:05.0: bridge io port: [0xa000-0xafff]
    pci 0000:00:05.0: bridge 32bit mmio: [0xfe800000-0xfe8fffff]
    pci 0000:00:05.0: bridge 64bit mmio pref: [0xf8e00000-0xf8efffff]
    pci 0000:03:00.0: reg 10 io port: [0xb800-0xb8ff]
    pci 0000:03:00.0: reg 18 64bit mmio: [0xf8fff000-0xf8ffffff]
    pci 0000:03:00.0: reg 20 64bit mmio: [0xf8ff8000-0xf8ffbfff]
    pci 0000:03:00.0: reg 30 32bit mmio: [0xfe9e0000-0xfe9fffff]
    pci 0000:03:00.0: supports D1 D2
    pci 0000:03:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    pci 0000:03:00.0: PME# disabled
    pci 0000:00:06.0: bridge io port: [0xb000-0xbfff]
    pci 0000:00:06.0: bridge 32bit mmio: [0xfe900000-0xfe9fffff]
    pci 0000:00:06.0: bridge 64bit mmio pref: [0xf8f00000-0xf8ffffff]
    pci 0000:04:00.0: reg 10 64bit mmio: [0xfeaff800-0xfeafffff]
    pci 0000:04:00.0: reg 18 io port: [0xc800-0xc8ff]
    pci 0000:04:00.0: supports D2
    pci 0000:04:00.0: PME# supported from D2 D3hot D3cold
    pci 0000:04:00.0: PME# disabled
    pci 0000:00:07.0: bridge io port: [0xc000-0xcfff]
    pci 0000:00:07.0: bridge 32bit mmio: [0xfea00000-0xfeafffff]
    pci 0000:05:00.0: reg 24 32bit mmio: [0xfebfe000-0xfebfffff]
    pci 0000:05:00.0: PME# supported from D3hot
    pci 0000:05:00.0: PME# disabled
    pci 0000:05:00.1: reg 10 io port: [0xe800-0xe807]
    pci 0000:05:00.1: reg 14 io port: [0xe400-0xe403]
    pci 0000:05:00.1: reg 18 io port: [0xe000-0xe007]
    pci 0000:05:00.1: reg 1c io port: [0xd800-0xd803]
    pci 0000:05:00.1: reg 20 io port: [0xd400-0xd40f]
    pci 0000:00:09.0: bridge io port: [0xd000-0xefff]
    pci 0000:00:09.0: bridge 32bit mmio: [0xfeb00000-0xfebfffff]
    pci 0000:00:14.4: transparent bridge
    pci_bus 0000:00: on NUMA node 0
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCE2._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCE5._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCE6._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCE7._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCE9._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0PC._PRT]
    ACPI: PCI Interrupt Link [LNKA] (IRQs 4 7 10 *11 12 14 15)
    ACPI: PCI Interrupt Link [LNKB] (IRQs 4 7 10 *11 12 14 15)
    ACPI: PCI Interrupt Link [LNKC] (IRQs 4 7 *10 11 12 14 15)
    ACPI: PCI Interrupt Link [LNKD] (IRQs 4 *7 10 11 12 14 15)
    ACPI: PCI Interrupt Link [LNKE] (IRQs 4 7 10 11 12 14 15) *0, disabled.
    ACPI: PCI Interrupt Link [LNKF] (IRQs 4 7 10 11 12 14 15) *0, disabled.
    ACPI: PCI Interrupt Link [LNKG] (IRQs *10 11 12 14 15)
    ACPI: PCI Interrupt Link [LNKH] (IRQs 4 7 10 11 12 14 15) *0, disabled.
    ACPI Warning (tbutils-0242): Incorrect checksum in table [OEMB] - 47, should be 46 [20081204]
    PCI: Using ACPI for IRQ routing
    pci 0000:00:00.0: BAR 3: can't allocate resource
    NetLabel: Initializing
    NetLabel: domain hash size = 128
    NetLabel: protocols = UNLABELED CIPSOv4
    NetLabel: unlabeled traffic allowed by default
    hpet: hpet2 irq 24 for MSI
    pnp: PnP ACPI init
    ACPI: bus type pnp registered
    pnp 00:0d: mem resource (0x0-0x9ffff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling
    pnp 00:0d: mem resource (0xc0000-0xcffff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling
    pnp 00:0d: mem resource (0xe0000-0xfffff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling
    pnp 00:0d: mem resource (0x100000-0xcfefffff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling
    pnp: PnP ACPI: found 14 devices
    ACPI: ACPI bus type pnp unregistered
    system 00:09: iomem range 0xfec00000-0xfec00fff has been reserved
    system 00:09: iomem range 0xfee00000-0xfee00fff has been reserved
    system 00:0a: ioport range 0x4d0-0x4d1 has been reserved
    system 00:0a: ioport range 0x40b-0x40b has been reserved
    system 00:0a: ioport range 0x4d6-0x4d6 has been reserved
    system 00:0a: ioport range 0xc00-0xc01 has been reserved
    system 00:0a: ioport range 0xc14-0xc14 has been reserved
    system 00:0a: ioport range 0xc50-0xc51 has been reserved
    system 00:0a: ioport range 0xc52-0xc52 has been reserved
    system 00:0a: ioport range 0xc6c-0xc6c has been reserved
    system 00:0a: ioport range 0xc6f-0xc6f has been reserved
    system 00:0a: ioport range 0xcd0-0xcd1 has been reserved
    system 00:0a: ioport range 0xcd2-0xcd3 has been reserved
    system 00:0a: ioport range 0xcd4-0xcd5 has been reserved
    system 00:0a: ioport range 0xcd6-0xcd7 has been reserved
    system 00:0a: ioport range 0xcd8-0xcdf has been reserved
    system 00:0a: ioport range 0x800-0x89f has been reserved
    system 00:0a: ioport range 0xb00-0xb0f has been reserved
    system 00:0a: ioport range 0xb20-0xb3f has been reserved
    system 00:0a: ioport range 0x900-0x90f has been reserved
    system 00:0a: ioport range 0x910-0x91f has been reserved
    system 00:0a: ioport range 0xfe00-0xfefe has been reserved
    system 00:0a: iomem range 0xffb80000-0xffbfffff has been reserved
    system 00:0a: iomem range 0xfec10000-0xfec1001f has been reserved
    system 00:0b: ioport range 0x600-0x6df has been reserved
    system 00:0b: ioport range 0x6e0-0x6ef has been reserved
    system 00:0c: iomem range 0xe0000000-0xefffffff has been reserved
    system 00:0d: iomem range 0xfec00000-0xffffffff could not be reserved
    Switched to high resolution mode on CPU 3
    Switched to high resolution mode on CPU 1
    Switched to high resolution mode on CPU 2
    Switched to high resolution mode on CPU 0
    pci 0000:00:02.0: PCI bridge, secondary bus 0000:01
    pci 0000:00:02.0: IO window: 0x9000-0x9fff
    pci 0000:00:02.0: MEM window: 0xfa000000-0xfe7fffff
    pci 0000:00:02.0: PREFETCH window: 0x000000d0000000-0x000000dfffffff
    pci 0000:00:05.0: PCI bridge, secondary bus 0000:02
    pci 0000:00:05.0: IO window: 0xa000-0xafff
    pci 0000:00:05.0: MEM window: 0xfe800000-0xfe8fffff
    pci 0000:00:05.0: PREFETCH window: 0x000000f8e00000-0x000000f8efffff
    pci 0000:00:06.0: PCI bridge, secondary bus 0000:03
    pci 0000:00:06.0: IO window: 0xb000-0xbfff
    pci 0000:00:06.0: MEM window: 0xfe900000-0xfe9fffff
    pci 0000:00:06.0: PREFETCH window: 0x000000f8f00000-0x000000f8ffffff
    pci 0000:00:07.0: PCI bridge, secondary bus 0000:04
    pci 0000:00:07.0: IO window: 0xc000-0xcfff
    pci 0000:00:07.0: MEM window: 0xfea00000-0xfeafffff
    pci 0000:00:07.0: PREFETCH window: disabled
    pci 0000:00:09.0: PCI bridge, secondary bus 0000:05
    pci 0000:00:09.0: IO window: 0xd000-0xefff
    pci 0000:00:09.0: MEM window: 0xfeb00000-0xfebfffff
    pci 0000:00:09.0: PREFETCH window: disabled
    pci 0000:00:14.4: PCI bridge, secondary bus 0000:06
    pci 0000:00:14.4: IO window: disabled
    pci 0000:00:14.4: MEM window: disabled
    pci 0000:00:14.4: PREFETCH window: disabled
    pci 0000:00:02.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
    pci 0000:00:02.0: setting latency timer to 64
    pci 0000:00:05.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    pci 0000:00:05.0: setting latency timer to 64
    pci 0000:00:06.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
    pci 0000:00:06.0: setting latency timer to 64
    pci 0000:00:07.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
    pci 0000:00:07.0: setting latency timer to 64
    pci 0000:00:09.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    pci 0000:00:09.0: setting latency timer to 64
    pci_bus 0000:00: resource 0 io: [0x00-0xffff]
    pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffff]
    pci_bus 0000:01: resource 0 io: [0x9000-0x9fff]
    pci_bus 0000:01: resource 1 mem: [0xfa000000-0xfe7fffff]
    pci_bus 0000:01: resource 2 mem: [0xd0000000-0xdfffffff]
    pci_bus 0000:01: resource 3 mem: [0x0-0x0]
    pci_bus 0000:02: resource 0 io: [0xa000-0xafff]
    pci_bus 0000:02: resource 1 mem: [0xfe800000-0xfe8fffff]
    pci_bus 0000:02: resource 2 mem: [0xf8e00000-0xf8efffff]
    pci_bus 0000:02: resource 3 mem: [0x0-0x0]
    pci_bus 0000:03: resource 0 io: [0xb000-0xbfff]
    pci_bus 0000:03: resource 1 mem: [0xfe900000-0xfe9fffff]
    pci_bus 0000:03: resource 2 mem: [0xf8f00000-0xf8ffffff]
    pci_bus 0000:03: resource 3 mem: [0x0-0x0]
    pci_bus 0000:04: resource 0 io: [0xc000-0xcfff]
    pci_bus 0000:04: resource 1 mem: [0xfea00000-0xfeafffff]
    pci_bus 0000:04: resource 2 mem: [0x0-0x0]
    pci_bus 0000:04: resource 3 mem: [0x0-0x0]
    pci_bus 0000:05: resource 0 io: [0xd000-0xefff]
    pci_bus 0000:05: resource 1 mem: [0xfeb00000-0xfebfffff]
    pci_bus 0000:05: resource 2 mem: [0x0-0x0]
    pci_bus 0000:05: resource 3 mem: [0x0-0x0]
    pci_bus 0000:06: resource 0 mem: [0x0-0x0]
    pci_bus 0000:06: resource 1 mem: [0x0-0x0]
    pci_bus 0000:06: resource 2 mem: [0x0-0x0]
    pci_bus 0000:06: resource 3 io: [0x00-0xffff]
    pci_bus 0000:06: resource 4 mem: [0x000000-0xffffffff]
    NET: Registered protocol family 2
    IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
    TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
    TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
    TCP: Hash tables configured (established 131072 bind 65536)
    TCP reno registered
    NET: Registered protocol family 1
    Unpacking initramfs... done
    Freeing initrd memory: 4369k freed
    apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
    apm: disabled - APM is not SMP safe.
    Scanning for low memory corruption every 60 seconds
    audit: initializing netlink socket (disabled)
    type=2000 audit(1252627399.657:1): initialized
    highmem bounce pool size: 64 pages
    VFS: Disk quotas dquot_6.5.2
    Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    msgmni has been set to 1711
    alg: No test for stdrng (krng)
    Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
    io scheduler noop registered
    io scheduler anticipatory registered
    io scheduler deadline registered
    io scheduler cfq registered (default)
    pci 0000:01:00.0: Boot video device
    pcieport-driver 0000:00:02.0: setting latency timer to 64
    pcieport-driver 0000:00:02.0: irq 25 for MSI/MSI-X
    pcieport-driver 0000:00:05.0: setting latency timer to 64
    pcieport-driver 0000:00:05.0: irq 26 for MSI/MSI-X
    pcieport-driver 0000:00:06.0: setting latency timer to 64
    pcieport-driver 0000:00:06.0: irq 27 for MSI/MSI-X
    pcieport-driver 0000:00:07.0: setting latency timer to 64
    pcieport-driver 0000:00:07.0: irq 28 for MSI/MSI-X
    pcieport-driver 0000:00:09.0: setting latency timer to 64
    pcieport-driver 0000:00:09.0: irq 29 for MSI/MSI-X
    vesafb: framebuffer at 0xfb000000, mapped to 0xf8080000, using 6144k, total 14336k
    vesafb: mode is 1024x768x32, linelength=4096, pages=1
    vesafb: protected mode interface info at c000:b2e0
    vesafb: pmi: set display start = c00cb343, set palette = c00cb39e
    vesafb: pmi: ports = 3b4 3b5 3ba 3c0 3c1 3c4 3c5 3c6 3c7 3c8 3c9 3cc 3ce 3cf 3d0 3d1 3d2 3d3 3d4 3d5 3da
    vesafb: scrolling: redraw
    vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
    Console: switching to colour frame buffer device 128x48
    fb0: VESA VGA frame buffer device
    isapnp: Scanning for PnP cards...
    isapnp: No Plug & Play device found
    Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    00:07: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    input: Macintosh mouse button emulation as /devices/virtual/input/input0
    PNP: PS/2 Controller [PNP0303:PSKE,PNP0f03:PSMS] at 0x60,0x64 irq 1,12
    serio: i8042 KBD port at 0x60,0x64 irq 1
    serio: i8042 AUX port at 0x60,0x64 irq 12
    mice: PS/2 mouse device common for all mice
    cpuidle: using governor ladder
    cpuidle: using governor menu
    TCP cubic registered
    NET: Registered protocol family 17
    Using IPI No-Shortcut mode
    registered taskstats version 1
    Freeing unused kernel memory: 340k freed
    SCSI subsystem initialized
    libata version 3.00 loaded.
    pata_acpi 0000:00:14.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    pata_acpi 0000:00:14.1: setting latency timer to 64
    pata_acpi 0000:05:00.1: enabling device (0000 -> 0001)
    pata_acpi 0000:05:00.1: PCI INT B -> GSI 18 (level, low) -> IRQ 18
    pata_acpi 0000:05:00.1: setting latency timer to 64
    pata_acpi 0000:05:00.1: PCI INT B disabled
    ahci 0000:00:11.0: version 3.0
    ahci 0000:00:11.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
    ahci 0000:00:11.0: irq 30 for MSI/MSI-X
    ahci 0000:00:11.0: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode
    ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp pio slum part
    scsi0 : ahci
    scsi1 : ahci
    scsi2 : ahci
    scsi3 : ahci
    ata1: SATA max UDMA/133 abar m1024@0xf9fffc00 port 0xf9fffd00 irq 30
    ata2: SATA max UDMA/133 abar m1024@0xf9fffc00 port 0xf9fffd80 irq 30
    ata3: SATA max UDMA/133 abar m1024@0xf9fffc00 port 0xf9fffe00 irq 30
    ata4: SATA max UDMA/133 abar m1024@0xf9fffc00 port 0xf9fffe80 irq 30
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    pata_jmicron 0000:05:00.1: PCI INT B -> GSI 18 (level, low) -> IRQ 18
    pata_jmicron 0000:05:00.1: setting latency timer to 64
    scsi4 : pata_jmicron
    scsi5 : pata_jmicron
    ata5: PATA max UDMA/100 cmd 0xe800 ctl 0xe400 bmdma 0xd400 irq 18
    ata6: PATA max UDMA/100 cmd 0xe000 ctl 0xd800 bmdma 0xd408 irq 18
    ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
    ata1: SATA link down (SStatus 0 SControl 300)
    ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    ata2.00: ATAPI: TSSTcorp CD-RW/DVD-ROM TS-H493A, D200, max UDMA/33, ATAPI AN
    ata2.00: configured for UDMA/33
    scsi 1:0:0:0: CD-ROM TSSTcorp CDRWDVD TS-H493A D200 PQ: 0 ANSI: 5
    ata3: SATA link down (SStatus 0 SControl 300)
    ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    ata4.00: ATA-7: ST3500630AS, 3.AAK, max UDMA/133
    ata4.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
    ata4.00: configured for UDMA/133
    scsi 3:0:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5
    ahci 0000:05:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    scsi6 : pata_atiixp
    scsi7 : pata_atiixp
    ata7: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xff00 irq 14
    ata8: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xff08 irq 15
    ahci 0000:05:00.0: AHCI 0001.0000 32 slots 2 ports 3 Gbps 0x3 impl SATA mode
    ahci 0000:05:00.0: flags: 64bit ncq pm led clo pmp pio slum part
    ahci 0000:05:00.0: setting latency timer to 64
    scsi8 : ahci
    scsi9 : ahci
    ata9: SATA max UDMA/133 abar m8192@0xfebfe000 port 0xfebfe100 irq 17
    ata10: SATA max UDMA/133 abar m8192@0xfebfe000 port 0xfebfe180 irq 17
    ata9: SATA link down (SStatus 0 SControl 300)
    ata8.01: ATA-7: ST3500630AS, 3.AAK, max UDMA/133
    ata8.01: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
    ata8.01: configured for UDMA/100
    scsi 7:0:1:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5
    ehci_hcd 0000:00:12.2: PCI INT B -> GSI 17 (level, low) -> IRQ 17
    ehci_hcd 0000:00:12.2: EHCI Host Controller
    ehci_hcd 0000:00:12.2: new USB bus registered, assigned bus number 1
    ehci_hcd 0000:00:12.2: debug port 1
    ehci_hcd 0000:00:12.2: irq 17, io mem 0xf9fff800
    ehci_hcd 0000:00:12.2: USB 2.0 started, EHCI 1.00
    usb usb1: configuration #1 chosen from 1 choice
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 6 ports detected
    ohci_hcd 0000:00:12.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    ohci_hcd 0000:00:12.0: OHCI Host Controller
    ohci_hcd 0000:00:12.0: new USB bus registered, assigned bus number 2
    ohci_hcd 0000:00:12.0: irq 16, io mem 0xf9ffe000
    Driver 'sd' needs updating - please use bus_type methods
    sd 3:0:0:0: [sda] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
    sd 3:0:0:0: [sda] Write Protect is off
    sd 3:0:0:0: [sda] Mode Sense: 00 3a 00 00
    sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    sd 3:0:0:0: [sda] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
    sd 3:0:0:0: [sda] Write Protect is off
    sd 3:0:0:0: [sda] Mode Sense: 00 3a 00 00
    sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    sda: sda1 sda2 sda3
    sd 3:0:0:0: [sda] Attached SCSI disk
    sd 7:0:1:0: [sdb] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
    sd 7:0:1:0: [sdb] Write Protect is off
    sd 7:0:1:0: [sdb] Mode Sense: 00 3a 00 00
    sd 7:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    sd 7:0:1:0: [sdb] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
    sd 7:0:1:0: [sdb] Write Protect is off
    sd 7:0:1:0: [sdb] Mode Sense: 00 3a 00 00
    sd 7:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    sdb: sdb1
    sd 7:0:1:0: [sdb] Attached SCSI disk
    usb usb2: configuration #1 chosen from 1 choice
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 3 ports detected
    ehci_hcd 0000:00:13.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
    ehci_hcd 0000:00:13.2: EHCI Host Controller
    ehci_hcd 0000:00:13.2: new USB bus registered, assigned bus number 3
    ehci_hcd 0000:00:13.2: debug port 1
    ehci_hcd 0000:00:13.2: irq 19, io mem 0xf9fff400
    ehci_hcd 0000:00:13.2: USB 2.0 started, EHCI 1.00
    usb usb3: configuration #1 chosen from 1 choice
    hub 3-0:1.0: USB hub found
    hub 3-0:1.0: 6 ports detected
    ohci_hcd 0000:00:12.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    ohci_hcd 0000:00:12.1: OHCI Host Controller
    ohci_hcd 0000:00:12.1: new USB bus registered, assigned bus number 4
    ohci_hcd 0000:00:12.1: irq 16, io mem 0xf9ffd000
    usb usb4: configuration #1 chosen from 1 choice
    hub 4-0:1.0: USB hub found
    hub 4-0:1.0: 3 ports detected
    ohci_hcd 0000:00:13.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
    ohci_hcd 0000:00:13.0: OHCI Host Controller
    ohci_hcd 0000:00:13.0: new USB bus registered, assigned bus number 5
    ohci_hcd 0000:00:13.0: irq 18, io mem 0xf9ffc000
    usb usb5: configuration #1 chosen from 1 choice
    hub 5-0:1.0: USB hub found
    hub 5-0:1.0: 3 ports detected
    ohci_hcd 0000:00:13.1: PCI INT A -> GSI 18 (level, low) -> IRQ 18
    ohci_hcd 0000:00:13.1: OHCI Host Controller
    ohci_hcd 0000:00:13.1: new USB bus registered, assigned bus number 6
    ohci_hcd 0000:00:13.1: irq 18, io mem 0xf9ffb000
    ata10: SATA link down (SStatus 0 SControl 300)
    usb usb6: configuration #1 chosen from 1 choice
    hub 6-0:1.0: USB hub found
    hub 6-0:1.0: 3 ports detected
    ohci_hcd 0000:00:14.5: PCI INT C -> GSI 18 (level, low) -> IRQ 18
    ohci_hcd 0000:00:14.5: OHCI Host Controller
    ohci_hcd 0000:00:14.5: new USB bus registered, assigned bus number 7
    ohci_hcd 0000:00:14.5: irq 18, io mem 0xf9ffa000
    usb usb7: configuration #1 chosen from 1 choice
    hub 7-0:1.0: USB hub found
    hub 7-0:1.0: 2 ports detected
    Driver 'sr' needs updating - please use bus_type methods
    sr0: scsi3-mmc drive: 8x/48x writer cd/rw xa/form2 cdda tray
    Uniform CD-ROM driver Revision: 3.20
    sr 1:0:0:0: Attached scsi CD-ROM sr0
    usb 3-2: new high speed USB device using ehci_hcd and address 3
    usb 3-2: configuration #1 chosen from 1 choice
    hub 3-2:1.0: USB hub found
    hub 3-2:1.0: 4 ports detected
    usb 5-1: new low speed USB device using ohci_hcd and address 2
    usb 5-1: configuration #1 chosen from 1 choice
    usbcore: registered new interface driver hiddev
    input: Microsoft Microsoft 3-Button Mouse with IntelliEye(TM) as /devices/pci0000:00/0000:00:13.0/usb5/5-1/5-1:1.0/input/input1
    generic-usb 0003:045E:0040.0001: input,hidraw0: USB HID v1.10 Mouse [Microsoft Microsoft 3-Button Mouse with IntelliEye(TM)] on usb-0000:00:13.0-1/input0
    usbcore: registered new interface driver usbhid
    usbhid: v2.6:USB HID core driver
    usb 3-2.4: new high speed USB device using ehci_hcd and address 4
    usb 3-2.4: configuration #1 chosen from 1 choice
    hub 3-2.4:1.0: USB hub found
    hub 3-2.4:1.0: 4 ports detected
    usb 3-2.4.1: new low speed USB device using ehci_hcd and address 5
    usb 3-2.4.1: configuration #1 chosen from 1 choice
    input: Microsoft Comfort Curve Keyboard 2000 as /devices/pci0000:00/0000:00:13.2/usb3/3-2/3-2.4/3-2.4.1/3-2.4.1:1.0/input/input2
    generic-usb 0003:045E:00DD.0002: input,hidraw1: USB HID v1.11 Keyboard [Microsoft Comfort Curve Keyboard 2000] on usb-0000:00:13.2-2.4.1/input0
    input: Microsoft Comfort Curve Keyboard 2000 as /devices/pci0000:00/0000:00:13.2/usb3/3-2/3-2.4/3-2.4.1/3-2.4.1:1.1/input/input3
    generic-usb 0003:045E:00DD.0003: input,hidraw2: USB HID v1.11 Device [Microsoft Comfort Curve Keyboard 2000] on usb-0000:00:13.2-2.4.1/input1
    SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
    SGI XFS Quota Management subsystem
    XFS mounting filesystem sda3
    Ending clean XFS mount for filesystem: sda3
    rtc_cmos 00:04: RTC can wake from S4
    rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0
    rtc0: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
    udev: starting version 146
    r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
    r8169 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    r8169 0000:02:00.0: setting latency timer to 64
    r8169 0000:02:00.0: irq 31 for MSI/MSI-X
    eth0: RTL8168d/8111d at 0xf888c000, 00:24:21:b7:ca:4d, XID 281000c0 IRQ 31
    r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
    r8169 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
    r8169 0000:03:00.0: setting latency timer to 64
    r8169 0000:03:00.0: irq 32 for MSI/MSI-X
    eth1: RTL8168d/8111d at 0xf8696000, 00:24:21:b7:ca:4c, XID 281000c0 IRQ 32
    HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    hda_codec: Unknown model for ALC883, trying auto-probe from BIOS...
    usbcore: registered new interface driver snd-usb-audio
    input: Power Button (FF) as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
    ACPI: Power Button (FF) [PWRF]
    input: Power Button (CM) as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input5
    ACPI: Power Button (CM) [PWRB]
    processor ACPI_CPU:00: registered as cooling_device0
    ACPI: Processor [P001] (supports 8 throttling states)
    processor ACPI_CPU:01: registered as cooling_device1
    processor ACPI_CPU:02: registered as cooling_device2
    processor ACPI_CPU:03: registered as cooling_device3
    sr 1:0:0:0: Attached scsi generic sg0 type 5
    sd 3:0:0:0: Attached scsi generic sg1 type 0
    sd 7:0:1:0: Attached scsi generic sg2 type 0
    Linux agpgart interface v0.103
    ohci1394 0000:04:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
    ohci1394 0000:04:00.0: setting latency timer to 64
    ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[19] MMIO=[feaff800-feafffff] Max Packet=[2048] IR/IT contexts=[4/8]
    input: PC Speaker as /devices/platform/pcspkr/input/input6
    ACPI: I/O resource piix4_smbus [0xb00-0xb07] conflicts with ACPI region SOR1 [0xb00-0xb0f]
    ACPI: Device needs an ACPI driver
    piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xb00, revision 0
    nvidia: module license 'NVIDIA' taints kernel.
    ACPI: WMI: Mapper loaded
    nvidia 0000:01:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
    nvidia 0000:01:00.0: setting latency timer to 64
    NVRM: loading NVIDIA UNIX x86 Kernel Module 180.44 Mon Mar 23 14:59:10 PST 2009
    ieee1394: Host added: ID:BUS[0-00:1023] GUID[0010dc0001947652]
    Adding 996020k swap on /dev/sda2. Priority:-1 extents:1 across:996020k
    r8169: eth0: link up
    r8169: eth0: link up
    NET: Registered protocol family 10
    lo: Disabled Privacy Extensions
    nvclock:4989 freeing invalid memtype fd000000-fd010000
    nvclock:4989 freeing invalid memtype fd010000-fd030000
    nvclock:4989 freeing invalid memtype fd010000-fd030000
    IRQ 18/nvidia: IRQF_DISABLED is not guaranteed on shared IRQs
    eth0: no IPv6 routers present
    ideas?
    Last edited by pnatural (2009-09-17 19:59:58)

    pnatural wrote:
    hi,
    I was able to install 2.6.31 by setting the motherboards E-SATA/RAID mode to "ACPI" instead of "PCI".  I first tried to disable the motherboard raid completely, but the system would not boot at all that way; setting the mode to "ACPI" did the trick.
    I would say thanks, but I did all the work!  But thanks to the Arch folks for a great distribution.
    Hi,I got the follow message,much same with you,could you tell me how to deal?thx.
    Nov  3 23:00:06 ArchLinux kernel: pci 0000:00:14.2: BAR 0: address space collision on of device [0xd4408000-0xd440bfff]

  • 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)

  • [Solved] UEFI. System hangs on boot after successfully activating swap

    Alright.
    Unnecessary Background:
    I've been using Arch for years. I just bought a stupidly good computer with a bunch of specs that I don't think are relevant, except for the fact that I am using an X99-pro. It has RAID support, but I am not using that currently. I bought all the parts and finished constructing it this morning (I live in Japan, so that was a while ago). Normally, I have no problems with installation; however, I wanted to do this one UEFI mode. After booting into the live disk, I checked to make sure everything was working as it should. Arch recognized my graphics card, most of my ram (one of the cards is a bit finicky for some reason), my SSD and HDD, along with the built-in WiFi (although it is an annoying broadcom one, so I need to install the driver separately later). Now, there are plenty of sources of error in here:
    Problem:
    I got through the arch installation and tried gummiboot. It would hang every time after successfully activating swap. I tried grub, too, but had the same problem. Because gummiboot is much less cumbersome, I switched back to that. Interestingly, systemd will sometimes recognize my drive twice before activating swap, and if I edit my fstab to ignore the swap completely, it hangs on the next step with is mounting the boot partition. I would like to point out that because I am not able to successfully boot my system, I cannot provide the exact messages for you guys, which may pose a problem.
    Solutions I have tried:
    1. Chrooting / mkinitcpio -p linux
    2. modifying fstab / removing swap from it completely
    3. fresh re-install
    Sources of error:
    1. Construction. Everything seems appropriate on the live usb, but maybe there is a problem in which ports I used for the SSD and HDD
    2. UEFI. It could be that UEFI just doesn't like mounting multiple things and freezes up when put on the spot.
    3. Legacy. It could be that this is not a problem with UEFI or my construction, but something I missed in the installation.
    Additional info:
    Partitioning scheme:
    sda1: ~500MiB boot / EFI partition
    sda2: ~4G swap
    sda3: ~110G /
    sdb:   ~2T, untouched (for storage later)
    I apologize for any typos and hope it was readable. I am super exhausted and going to take a nap. I'll check back in on this in the morning.
    Last edited by Leios (2015-02-08 00:16:27)

    Please post the output of:
    # gdisk -l /dev/sda
    lsblk -f
    And the contents of your gummiboot loader.conf and arch.conf (or whatever you've called it).
    Post the output of the commands after you have mounted all your partitions and (arch-)chroot'd into your system.
    You can use wgetpaste to post the outputs, as described by @ewaller here:
    https://bbs.archlinux.org/viewtopic.php … 8#p1500528
    Alternatively, pipe the command output to a text file and export it (using a live distribution or a USB stick).
    You should remove swap from your fstab -- systemd mounts it automatically anyway.

  • 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?

  • Hangs on boot after lion upgrade

    I've upgraded to Lion and since upgrading my macbook pro hangs when booting about 4 out of 10  times.  I get to the desktop and then get a never-ending spinning color wheel.
    2.8 Gb core 2 duo
    8 GB ram
    Summer 2009 model

    When you boot in single user or safe mode, all third party software is prevented from started. So it is possbile one of your third party party applications that are starting at boot is not compatable with the new RAM. I would try turning it all off and then test them all each in turn.
    Allan

  • Windows NT does not boot after installing NI-CAN 1.6.0 or security update

    We are running Windows NT 4.0 SP 6 english with MS IE 5.5.
    On one machine we had NI-CAN 1.6.0 installed. After installing the security update from Microsoft over the web the machine did not boot.
    On another machine the security update was installed. After installing NI-CAN 1.6.0 the machine booted but hangs during logon. On this machine we installed Windows NT, MS IE 5.5 the security update and NI-CAN from new and the effect was the same.
    Does anyone else have similar experience with this problem?
    Machines with Windows 2000 and XP work well with NI-CAN 1.6.0.
    Waldemar
    Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
    Don't forget to give Kudos to good answers and/or questions

    Hi,
    I haven't found any known issues. I going to try it out here. What's the security update you're installing?. I noticed there's a bunch of them in the Microsoft web site.
    What CAN hardware do you have (PCI, PCMCIA, etc)?.
    Let me know this details and I'll try to reproduce the problem.
    DiegoF.
    National Instruments.

  • Won't boot after installing new video card

    Hello, I have a H8-1284 desktop computer, and a few days ago the video card went. So i bought a Geforce GTX 650 video card, and after installing the card and starting the comp, it just hangs at the HP logo splash screen. So I put an older geforce 8800, and it boots no problem. When I try the new Geforce GTX 650 card, same thing, just hangs at splash screen.  I checked the bios and there doent seem to be anything there that wouild help. My power supply is 460 w, and the new card only needs 400 w, any and all help will be greatly appreciated
    This question was solved.
    View Solution.

    Hi,
    Most PCI-E 3.0 cards are backwards compatible with PCI-E 2.0 slots.  However, in order to get PCI-E version 3 you need to be using an Ivy Bridge processor.  Review these specifications for a typical NVIDIA GTX 650.
    HP DV9700, t9300, Nvidia 8600, 4GB, Crucial C300 128GB SSD
    HP Photosmart Premium C309G, HP Photosmart 6520
    HP Touchpad, HP Chromebook 11
    Custom i7-4770k,Z-87, 8GB, Vertex 3 SSD, Samsung EVO SSD, Corsair HX650,GTX 760
    Custom i7-4790k,Z-97, 16GB, Vertex 3 SSD, Plextor M.2 SSD, Samsung EVO SSD, Corsair HX650, GTX 660TI
    Windows 7/8 UEFI/Legacy mode, MBR/GPT

  • Windows 8.1 Pro will not boot after installing iTunes 11.1.5.5

    It's a little hard for me to accept that this is true, but the symptoms seem to be pointing the direction of the title of this thread.  I have an all-in-one touch-screen Gateway computer that came with windows 7 (yeah, a win7 machine that came with touch, yeesh) and I put windows 8.1 pro 64-bit on it with a clean install (actually windows 8 was the clean install and then I did the free microsoft store upgrade to 8.1).  It has 4GB of RAM and has a Pentium Dual Core cpu @ 2.2 Ghz.  It was running fine with the previous version of iTunes, but as soon as I updated to iTunes 11.1.5.5 (and there may have been other apple things that updated too (ie quicktime of course), the computer prompted me for a reboot and froze during the reboot process (before it even shut down).  Then it had trouble booting into windows.  I ran startup repair to no avail and decided to do a sytem restore.  My most recent restore point was from a few weeks back, before iTunes was even installed at all on the machine.  I went back to that point and the machine worked fine again.  Then I installed iTunes 11.1.5.5 and the same exact problem occurred - it froze while shutting down after the iTunes install and then would not boot into windows 8.  I did another system restore and have not put iTunes back on.  The system is working fine.  I'm going to try to find out if there's a way to download older versions of iTunes, so that I can install it, but the bigger issue here is: Is this a legitimate bug/incompatibility with some hardware or software or driver that I have on this computer?  I run a computer support business so I know my way around but I don't have time to troubleshoot this from scratch.  Anyone else seeing this?  Apple employees...a little help here?  Any input?

    let it sit for about 30 min and still got nothing
    I then did a "hard shutdown(just pressed power button till it turned off the computer)"
    That may not have been long enough.  But a "hard shutdown" would definitely have been construed as a problem due to the update.
    Asus apparently is a known problem case...
    http://blogs.msdn.com/b/usbcoreblog/archive/2013/10/19/help-after-installing-windows-8-1-the-superspeed-ports-of-my-asus-system-don-t-work.aspx
    Link courtesy Darrell Gorter [MSFT] found here
    "Windows 8 Keyboard and mouse not working"
    http://social.technet.microsoft.com/Forums/en-US/w8itprohardware/thread/06e9b341-0619-4085-acbf-e2f0133ca428?outputAs=rss
    (RSS given to avoid overhead of opening long thread for IE users)
    Note that there may be useful tips for you in both of those threads' comments.
    Robert Aldwinckle

Maybe you are looking for

  • Samba configuration on solarisintel 8

    hai i heve downloaded and installed samba server on my intel solaris 8 .. can any one help me to configure the server so that i can login from a widows desktop. help.. appriciated. konkani

  • New Itunes 11.1.12

    Not used to forums so please be patient with me. Ever since new itunes installed all of my songs are duplicated. Old itunes gave an option to cleanup duplicates. I can't find any such thing here without going and manually doing all 110 songs I have.

  • Leica Dlux 4 question

    I understand that Aperture does not yet support the Leica Dlux 4 Raw files. If I shoot the raw/jpeg combo with the dlux4, will Aperture import the jpegs? Then I would re-load the raw files when Aperture updates with the raw conversion.

  • I can't see some of my photos. iPhoto says "The Operation couldn't be completed. (OSStatus error -54.)

    when I click on some photos i saw this sign. This happen after one Time Machine backup (I think) and I couldn't solve it. I've tried  to rebuild library and thumbnail and it didn't work. and this too. What should I do?

  • Skype for Android sent messages have wrong time an...

    I have a problem with Skype on my Huawei phone. When I send a message, it seems Skype thinks it was sent in the past, because I see it for a couple seconds and then BOOM it's way back mixed in with my past messages. It basically disappears and I have