Can't boot, no post P45 Neo3-FR with DA HD4870 Sonic Dual

Hi all,
I'm new here and new user of MSI mobo.
Please help....why P45 Neo3-FR with Digital Alliance HD4870 Sonic Dual won't boot and no post everytime I start it?
It works fine when I changed the HD4870 with Ati X1050.
Below is the spec installed:
MSI P45 Neo3-FR
Intel C2D E6550
Transcend 667 2 x 1GB
Digital Alliance HD4870 Sonic Dual
Caviar SATA 80GB
BenQ DW1800
Viewsonic LCD '17
Corsair TX650W
Keyboard + Mouse Logitech
WinXP SP3
Thanks in advance... 

Try reseating the graphic card. And did you try uninstalling the previous drivers for the X1050 and install the lastest driver for the 4870? If i;m not wrong this card comes with a smart switch, did u mingle with it?

Similar Messages

  • Can't boot WinXPpro on K8N Neo3 gold

    Setting up new mobo and cpu, keeping all old peripheral hardware, including hard drive with XP Pro.
    Old board was ASUS A7S333 with SIS745 chipset, new board is K8N Neo3 gold (MS-7135 ATX) with nVIDIA nForce4-4X chipset and AMD K8 cpu.  The hard drive is a Maxtor DiamondMax Plus8 40Gb with two partitions, one an old WinME and the other is WinXP pro.
    The system posts, default selects the WinXP, and tries to boot the os but fails with a stop code of 7B "Inaccessible boot device".  The drive itself is fine, ran chkdsk diagnostics, even connected it as secondary drive on third machine and it comes up ok.
    Reading other forum topics it appears that the change of chipsets from old mobo to new requires a driver change for the IDE controller.  One forum topic "Can't boot Win2K SP4 on K8N Neo2" indicates that the Recovery console helped to fix the problem by reverting back to a plain vanilla version of a Microsoft driver but there were no explicit instructions on how to do this.  I can get the Recovery console up from my XP installation CD but its not obvious what to do from there.
    It took me a long time to get the WinXP system configured, patched, tweaked, apps installed, patched.....  so I'd hate to start all over.
    Anybody know how to pull this off?
    thx
    hoser

    Quote from: hoser77 on 12-June-05, 08:20:32
    how do I remove all system drivers beforehand?
    Hi there,
    You can do this removal in the old system where it used to work and in safe mode.
    Be well....

  • My mac Pro can't boot OS X, if it connected  with iPod video

    Hi All~ I have received the new Mac Pro, but I don't know why..... if
    my iPod video(60G) had connected with USB ports of Mac Pro, then I can't
    boot my OS system.... that seems the Mac Pro can't reach my hard
    disk, because the apple log doesn't appear (nothing on the screen)
    and everything is blocked, however when I put out the iPod, the Mac
    would go into the system smoothly, I don't know why. there is no
    problem with my powerbook or iMac G4 as the same situation to boot
    the OS system. Is a new rule to start the system with Intel CPU?
    Can anyone tell me what happen with my Mac Pro, does it have something wrong? Thanx
    Reeeeegards,

    Hi everybody!
    I´ve a similar problem. However, in my case it´s not when I boot Mac OS X but when I boot into bootcamp with Windows XP. It takes a loooooooong time for the Mac to start the booting when my 80gig ipod is connected to the USB-port . Maybe you also have just to wait longer?
    If I disconnect the ipod during this waiting period from the USB-port, the Mac starts booting immediatelly! Fortunatelly I´ve no problem when directly booting into Mac OS X.
    Direct connection or connection via self-powered USB-hub, disk-mode or no disk-mode, ipod formated in Mac or Windows format, I tried everything, but it all made no difference. Any advice to solve the problem would be very wellcome.
    By the way, I´ve another ipod connected via firewire, this is not causing any boot-trouble.

  • Need a new mac pro! Can I boot MacPro 6,1 (mid 2012) with an internal HD with OS 10.6 (Snow Leo)?

    5 hours after reading here: (so much information that says "yes" "maybe" "no".....)
    I want and have to change my actual MacPro (late 2007) to a newer one, because without my business is over.
    The newest one (end 2013) is not possible, because my other hardware is too old for that one.
    (still need Firewire and Rosetta)
    So I decided to buy an older "classicle" MacPro to put my 3 or 4 pieces of 2TB HDD in...
    ...... But I still need Rosetta, -> OS 10.6
    My question is:
    Can I boot a mac 6,1 (mid 2012) with a Harddisk with 10.6, I take out of my old machine?
    yes? anything to be aware or to update? (answeres here say mostly yes, sometimes, never ...)
    For sure I am interested in the latest model..... but will it work?
    If not:  I will buy a mac 5,1 (mid 2010).
    Anything to be aware or to update, if I pull in my HD with 10.6 out of the old model from late 2007?
    I don't want to downgrade to SL !!!!!!!
    I just want the Possibility to boot internal from the original OS on the first drive and from 10.6 on a second drive !!)
    (This good old Power Machines (all in one) will be jewels next year.....)  ;-)

    Mac Pro
    Date introduced
    Original Mac OS X included
    (see Tips 1 and 3)
    Later Mac OS X included
    (see Tip 1)
    Mac OS X Build(s)
    (see Tip 2)
    Mac Pro (Mid 2012)
    Jun 2012
    10.7.3
    10.8, 10.8.3
    11D2001, 12A269, 12D78
    Mac Pro (Mid 2010)
    Aug 2010
    10.6.4
    10.7, 10.7.2, 10.7.3
    10F2521, 10F2554, 11A511a, 11C74, 11D2001
    Mac Pro with Mac OS X Server (Mid 2010)
    Aug 2010
    10.6.4
    10.7, 10.7.2, 10.7.3 (Server)
    10F2522, 11A511a, 11C74, 11D2001 (Server)
    Mac Pro (Early 2009)
    Mar 2009
    10.5.6
    10.6
    9G3553, 10A432
    Mac Pro (Early 2008)
    Jan 2008
    10.5.1
    10.5.2, 10.5.4
    9B2117, 9C2031, 9E25
    Mac Pro
    Aug 2006
    10.4.7
    10.4.8, 10.4.9, 10.4.10, 10.5
    8K1079, 8N1430, 8N1250, 8K1124, 8P4037, 8R3032, 8R3041, 9A581, 9A3129
    -- from:
    Mac OS X versions (builds) for computers
    For example the Mac Pro 2010 CAN run 10.6.4 or later BUT--
    --- the last "Full Retail" 10.6 DVD conatins 10.6.3, which will not boot. You need a different Mac of just the right age to Install on, [starting from a Full Retail DVD, not a DVD from a different model] update to 10.6.8, then swap the drive over.
    The assertion has been made that the 2012 model (which runs 5,1 firmware) is indistinguishable from the 2010 model (which runs 5,1 firmware) as far as Hardware and therefore as far as what Mac OS X it can run. EveryMac.com agrees that this model will run 10.6.4.

  • Can I boot from an internal hard drive with a different verison of OSX?

    My wife had a MBP5,5 running a version of OSX earlier than Mavericks (came with snow leopard, believed we upgraded to Lion or Mountain Lion at some point but can't recall right now, for the life of me) and my daughter spilled a drink on it the other day ending its run.  As a result, I bought a used MBP MD101LL/A with Mavericks installed and planned on just swapping its hard drive with hers (which I know survived the spill...I've been able to access it via a tethered enclosure since) and choosing her old drive as the startup volume on boot.  All went according to plan, but the boot gets no further than the Apple logo.  Any suggestions?  Because I was swapping out the hard drive, I didn't take the drive that was in the new MBP when I bought it but I'm sure I can get it if need be.  Same applies to the installation discs.  I have the 10.6 installation DVD and tried to boot from it and get to Disk Utility to no avail.  Any information/guidance would be greatly appreciated.

    If your New to You Used Mac is froom mid 2012 and originally came with Lion installed on it you will need to Reinstall that version using the Online Internet Recovery system and then at first boot of the new install use the Setup Assistant system to copy over all the data from your wifes old hard drive.
    To access the Online system at startup hold down the Command + Option/alt + r keys and keep them held down until you see a globe on the screen. From the resulting screen that cames up, Mac OS X Utilities, select Disk Utility and then the top most entry for the hard drive, left hand panel, drive model number and size, and then the Partition tab. Repartition the drive as One Partition, You Must do that to get ride of the Mavericks Recovery HD partition which is hidden. Name the partition Macintosh HD with a format of Mac OS Extended (Journaled).
    Once that is done exit disk utility and select Reinstall Mac OS X.

  • How can I boot images on external hard drives with an older OS

    Hi,
    I recently bought a new MacBook Pro Retina (running OS 10.9.2 Mavericks), because I had to give back my „old“ one (bought in February 2013, running OS 10.8 Mountain Lion), which was only a loan from University.
    So here comes my problem: I used Carbon Copy Cloner to create bootable images of my old MacBook on two independent hard drives. I tested these images and they both booted perfectly well on the old MacBook. As it turns out, I cannot boot from these images on my new MacBook Pro, I just get a crossed grey circle (both images work perfectly well when I boot from my internal hard drive and I just use them as external drive, by the way). Is it really correct, that it is not possible to boot a system with an older OS as the OS of the MacBook? Why? I really would like to have the option of booting these images, since I have some applications installed I might want to use from time to time in the future (and I don’t want to migrate all applications to my new MacBook, but prefer a clean install). As I understand, it would be necessary to update the images to Mavericks. But how do I do this when I have no computer which is able to boot them?
    I still have a very old MacBook from 2007 running OS X 10.5 (Leopard) and I also tried booting the images with this computer - didn’t work either. Would it help to update this to Snow Leopard? What OS would I need to boot my Mountain Lion images?
    Any help on this is highly appreciated!
    Thanks!

    Hi!
    Thanks for your prompt response. The reason I don't want to migrate all apps is that I had installed a lot of scientific applications on the Mt-Lion MacBook that I will definitely not use in the future, some that I might use only very rarely, and I can migrate only the complete applications folder (and I have only a 256 GB hard drive). Of course I could deinstall the unused apps manually after the migration, but I am not 100% sure, if this procedure completely removes all the stuff from the libraries and preferences, etc. Moreover I also started playing with some time ago with server applications like apache server etc. and since I am a complete newbie in this field, I have to admit, I really don't know how to uninstall these things properly. So I figured a clean install for the new MacBook would be the best. Well, maybe I will migrate everything and remove the unnecessary stuff afterwards manually. I am just a bit disappointed, because I didn't anticipate these problems with the images...
    Just one further question: Is it correct, that if I find a way to update my images from Mt-Lion to Mavericks (if that is possible at all?), this would make them bootable again?
    Thanks!

  • Can I boot to an external hard drive with Windows OS installed on it to play games?

    Hello,
    I am getting a Mac in the near future for work, and was wondering if it was possible to take my current PC's hard drive and connect it to the Mac with the high speed thunderbolt cable, then book to the external hard drive to play games in windows. In my research I have not seen much about this. I understand that BootCamp works, and am willing to do this, but with the new Macbook Pros that were released, there is very little storage space for two partitions.
    Any help would be great,
    Also, I know that the performance would not be stunning, but my performance is already lacking because I only have AMD integrated graphics on my machine.
    Thanks

    A virtual machine is a software system such as VMware Fusion or Parallels which provides a software environment within which a different operating system, such as Windows can run. The files which make up the virtual machine itself (e.g., where Windows and any Windows based software, such as Microsoft Office, reside) can be located on an internal or an external drive. Only the virtualizing program itself needs to be on the boot drive. The connection between an external drive on which the virtual machine files reside will be faster than the external drive itself if the connection is USB 3.0 or Thunderbolt because the speed of an external HD will be the limiting factor. If the external is an SSD, the connection used might make a difference. But a virtual machine will still be slower than a physical machine (i.e., computer) because  hardware is faster than the software emulation of it whether the hardware is Windows in BootCamp or a real PC, as BobTheFisherman says.
    If you mean the new Retina MacBook Pro (Late 2013), the internal storage isn't a hard drive, it's an SSD on a PCIe bus. OWC, among other vendors, may one day develop an upgrade method as they have for the SSD's in earlier rMBP's but for now, what you order is what you get.

  • [SOLVED] Can't boot from LUKS - No key available with this passphrase

    The problem
    Latest kbd package responsible for your keyboard layout may break some LUKS installs depending on the password used, as there are some keymaps which are broken, resulting in the user not being able to enter the password correctly.
    Relevant bug report: https://bugs.archlinux.org/task/36689
    The fix
    Find an old live image with the old kbd package (I had success with 2012.11.01)
    Boot the image
    Change to your preferred keymap using
    loadkeys
    Open your encrypted device with
    cryptsetup luksOpen /path/to/device devicename
    Mount the device and any other relevant mount points (such as /boot) and perform a chroot with
    arch-chroot
    Revert the kbd package. The latest working version is 1.15.5-4. If you didn't clean your cache, you should have a working version under
    /var/cache/pacman/pkg
    If not, either try finding the package manually, or build it using ABS.
    Once the package is installed, confirm the keymap works by running loadkeys again and entering any keys that may have been problematic.
    While still under chroot, rebuild the initramfs with
    mkinitcpio -p linux
    If this goes without any problems, you should be able to reboot to a working system.
    Ever since I updated my system about a week ago, I cannot boot it anymore.
    The root filesystem encrypted and since the update, I can't unlock it on boot anymore. Typing in my passphrase, I get the error No key available with this passphrase.
    One thing that comes to mind is that the passphrase contains non-standard characters (Š for example), and I'm not sure if that's what might be causing problems?
    Any ideas or tips on how can I debug this?
    Another thing I've noticed is that if I drop into a recovery shell, the special characters on my keyboard aren't properly mapped. Š will print out C and it's hexdump seems invalid.
    Edit:
    Just noticed this thread: https://bbs.archlinux.org/viewtopic.php?id=148562
    Will try to unlock it from a live distro. It doesn't seem to want to unlock with Arch live as the keymap seems wrong there as well.
    Last edited by Mr. Pjer (2013-09-07 00:19:27)

    Here's the list. The update was done on 31/8.
    [2013-08-31 18:14] [PACMAN] Running 'pacman -Syu'
    [2013-08-31 18:14] [PACMAN] synchronizing package lists
    [2013-08-31 18:14] [PACMAN] starting full system upgrade
    [2013-08-31 18:34] [PACMAN] removed python2-distribute (0.6.45-1)
    [2013-08-31 18:34] [PACMAN] removed python-distribute (0.6.45-1)
    [2013-08-31 18:34] [ALPM-SCRIPTLET] ==> Appending keys from archlinux.gpg...
    [2013-08-31 18:34] [ALPM-SCRIPTLET] gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
    [2013-08-31 18:34] [ALPM-SCRIPTLET] gpg: depth: 0 valid: 1 signed: 5 trust: 0-, 0q, 0n, 0m, 0f, 1u
    [2013-08-31 18:34] [ALPM-SCRIPTLET] gpg: depth: 1 valid: 5 signed: 65 trust: 0-, 0q, 0n, 5m, 0f, 0u
    [2013-08-31 18:34] [ALPM-SCRIPTLET] gpg: depth: 2 valid: 65 signed: 3 trust: 65-, 0q, 0n, 0m, 0f, 0u
    [2013-08-31 18:34] [ALPM-SCRIPTLET] gpg: next trustdb check due at 2014-01-22
    [2013-08-31 18:34] [ALPM-SCRIPTLET] ==> Locally signing trusted keys in keyring...
    [2013-08-31 18:34] [ALPM-SCRIPTLET] -> Locally signing key 0E8B644079F599DFC1DDC3973348882F6AC6A4C2...
    [2013-08-31 18:34] [ALPM-SCRIPTLET] -> Locally signing key 684148BB25B49E986A4944C55184252D824B18E8...
    [2013-08-31 18:34] [ALPM-SCRIPTLET] -> Locally signing key 44D4A033AC140143927397D47EFD567D4C7EA887...
    [2013-08-31 18:34] [ALPM-SCRIPTLET] -> Locally signing key 27FFC4769E19F096D41D9265A04F9397CDFD6BB0...
    [2013-08-31 18:34] [ALPM-SCRIPTLET] -> Locally signing key AB19265E5D7D20687D303246BA1DFB64FFF979E7...
    [2013-08-31 18:34] [ALPM-SCRIPTLET] ==> Importing owner trust values...
    [2013-08-31 18:34] [ALPM-SCRIPTLET] ==> Disabling revoked keys in keyring...
    [2013-08-31 18:34] [ALPM-SCRIPTLET] -> Disabling key BC1FBE4D2826A0B51E47ED62E2539214C6C11350...
    [2013-08-31 18:34] [ALPM-SCRIPTLET] ==> Updating trust database...
    [2013-08-31 18:34] [ALPM-SCRIPTLET] gpg: next trustdb check due at 2014-01-22
    [2013-08-31 18:34] [PACMAN] upgraded archlinux-keyring (20130525-2 -> 20130818-1)
    [2013-08-31 18:34] [ALPM-SCRIPTLET]
    [2013-08-31 18:34] [ALPM-SCRIPTLET] NOTE for argyllcms:
    [2013-08-31 18:34] [ALPM-SCRIPTLET] ----
    [2013-08-31 18:34] [ALPM-SCRIPTLET] ==> The documentaion is only available as html!
    [2013-08-31 18:34] [ALPM-SCRIPTLET] ==> You will find it in /usr/share/argyllcms/doc
    [2013-08-31 18:34] [ALPM-SCRIPTLET] ==> Color charts located in /usr/share/argyllcms/ref
    [2013-08-31 18:34] [ALPM-SCRIPTLET] ==> Since release 1.5.0 ColorHug support is enabled by default. The environment variable "ENABLE_COLORHUG" is not longer needed!
    [2013-08-31 18:34] [ALPM-SCRIPTLET] ==> Please add your argyllcms user to plugdev group! <==
    [2013-08-31 18:34] [PACMAN] upgraded argyllcms (1.5.1-2 -> 1.6.0-1)
    [2013-08-31 18:34] [PACMAN] upgraded linux-api-headers (3.8.4-1 -> 3.10.6-1)
    [2013-08-31 18:34] [ALPM-SCRIPTLET] Generating locales...
    [2013-08-31 18:34] [ALPM-SCRIPTLET] en_US.UTF-8... done
    [2013-08-31 18:34] [ALPM-SCRIPTLET] hr_HR.UTF-8... done
    [2013-08-31 18:34] [ALPM-SCRIPTLET] Generation complete.
    [2013-08-31 18:34] [PACMAN] upgraded glibc (2.17-6 -> 2.18-3)
    [2013-08-31 18:34] [PACMAN] upgraded bash (4.2.045-4 -> 4.2.045-5)
    [2013-08-31 18:34] [PACMAN] upgraded binutils (2.23.2-2 -> 2.23.2-3)
    [2013-08-31 18:34] [PACMAN] upgraded boost-libs (1.54.0-2 -> 1.54.0-3)
    [2013-08-31 18:34] [PACMAN] upgraded ca-certificates-java (20121112+nmu2-2 -> 20130815-1)
    [2013-08-31 18:34] [PACMAN] upgraded glib2 (2.36.3-3 -> 2.36.4-1)
    [2013-08-31 18:34] [PACMAN] upgraded wayland (1.2.0-1 -> 1.2.1-1)
    [2013-08-31 18:34] [PACMAN] upgraded gcc-libs (4.8.1-2 -> 4.8.1-3)
    [2013-08-31 18:34] [PACMAN] installed elfutils (0.155-1)
    [2013-08-31 18:34] [PACMAN] installed llvm-libs (3.3-1)
    [2013-08-31 18:34] [PACMAN] upgraded mesa (9.1.6-1 -> 9.2.0-1)
    [2013-08-31 18:34] [PACMAN] upgraded mesa-libgl (9.1.6-1 -> 9.2.0-1)
    [2013-08-31 18:34] [PACMAN] upgraded cairo (1.12.14-4 -> 1.12.16-1)
    [2013-08-31 18:34] [PACMAN] upgraded ttf-dejavu (2.33-4 -> 2.34-1)
    [2013-08-31 18:34] [PACMAN] upgraded chromium (28.0.1500.95-1 -> 29.0.1547.62-1)
    [2013-08-31 18:34] [PACMAN] upgraded curl (7.31.0-1 -> 7.32.0-1)
    [2013-08-31 18:34] [PACMAN] upgraded libarchive (3.1.2-1 -> 3.1.2-2)
    [2013-08-31 18:34] [PACMAN] upgraded cmake (2.8.11.2-1 -> 2.8.11.2-2)
    [2013-08-31 18:34] [PACMAN] upgraded cpupower (3.10-1 -> 3.10-2)
    [2013-08-31 18:34] [PACMAN] upgraded device-mapper (2.02.98-4 -> 2.02.100-1)
    [2013-08-31 18:34] [PACMAN] upgraded cryptsetup (1.6.1-2 -> 1.6.2-1)
    [2013-08-31 18:34] [PACMAN] upgraded poppler (0.24.0-1 -> 0.24.1-1)
    [2013-08-31 18:34] [PACMAN] upgraded cups-filters (1.0.35-4 -> 1.0.37-1)
    [2013-08-31 18:34] [PACMAN] installed python2-setuptools (1.0-1)
    [2013-08-31 18:34] [PACMAN] upgraded deluge (1.3.6-1 -> 1.3.6-3)
    [2013-08-31 18:34] [PACMAN] upgraded dhcpcd (6.0.4-1 -> 6.0.5-1)
    [2013-08-31 18:34] [PACMAN] upgraded python2-numpy (1.7.1-1 -> 1.7.1-2)
    [2013-08-31 18:34] [PACMAN] upgraded dispcalgui (1.2.7.0-1 -> 1.2.7.0-2)
    [2013-08-31 18:34] [PACMAN] upgraded ffmpeg (1:2.0-2 -> 1:2.0.1-1)
    [2013-08-31 18:34] [PACMAN] upgraded gtk3 (3.8.2-1 -> 3.8.4-1)
    [2013-08-31 18:34] [PACMAN] upgraded file-roller (3.8.3-1 -> 3.8.4-1)
    [2013-08-31 18:34] [PACMAN] upgraded gcc (4.8.1-2 -> 4.8.1-3)
    [2013-08-31 18:34] [PACMAN] upgraded gettext (0.18.3-1 -> 0.18.3.1-1)
    [2013-08-31 18:34] [PACMAN] upgraded libtiff (4.0.3-2 -> 4.0.3-3)
    [2013-08-31 18:34] [PACMAN] upgraded ghostscript (9.07-2 -> 9.09-1)
    [2013-08-31 18:34] [PACMAN] upgraded librsvg (2.37.0-2 -> 1:2.37.0-1)
    [2013-08-31 18:34] [PACMAN] upgraded libmng (1.0.10-4 -> 2.0.2-2)
    [2013-08-31 18:34] [PACMAN] upgraded gimp (2.8.6-1 -> 2.8.6-2)
    [2013-08-31 18:34] [PACMAN] upgraded perl (5.18.0-1 -> 5.18.1-1)
    [2013-08-31 18:34] [PACMAN] upgraded perl-error (0.17020-1 -> 0.17021-1)
    [2013-08-31 18:34] [PACMAN] upgraded git (1.8.3.4-1 -> 1.8.4-1)
    [2013-08-31 18:34] [PACMAN] upgraded glew (1.10.0-1 -> 1.10.0-2)
    [2013-08-31 18:34] [PACMAN] upgraded glfw (3.0.1-2 -> 3.0.2-1)
    [2013-08-31 18:34] [PACMAN] upgraded glm (0.9.4.4-1 -> 0.9.4.5-1)
    [2013-08-31 18:34] [PACMAN] upgraded gnupg (2.0.20-2 -> 2.0.21-1)
    [2013-08-31 18:34] [PACMAN] upgraded gpgme (1.4.2-2 -> 1.4.3-1)
    [2013-08-31 18:35] [PACMAN] upgraded grails (2.2.3-1 -> 2.2.4-1)
    [2013-08-31 18:35] [PACMAN] upgraded groff (1.22.2-3 -> 1.22.2-5)
    [2013-08-31 18:35] [PACMAN] upgraded gstreamer (1.0.9-1 -> 1.0.10-1)
    [2013-08-31 18:35] [PACMAN] upgraded gst-plugins-base-libs (1.0.9-1 -> 1.0.10-1)
    [2013-08-31 18:35] [PACMAN] upgraded imagemagick (6.8.6.4-1 -> 6.8.6.9-1)
    [2013-08-31 18:35] [PACMAN] upgraded intel-dri (9.1.6-1 -> 9.2.0-1)
    [2013-08-31 18:35] [PACMAN] upgraded iputils (20121221-2 -> 20121221-3)
    [2013-08-31 18:35] [PACMAN] upgraded isl (0.12-1 -> 0.12.1-1)
    [2013-08-31 18:35] [PACMAN] upgraded kbd (1.15.5-4 -> 2.0.0-1)
    [2013-08-31 18:35] [PACMAN] upgraded kdelibs (4.10.5-2 -> 4.11.0-1)
    [2013-08-31 18:35] [PACMAN] upgraded kmod (14-1 -> 15-1)
    [2013-08-31 18:35] [PACMAN] upgraded lib32-glibc (2.17-5 -> 2.18-3)
    [2013-08-31 18:35] [PACMAN] upgraded lib32-gcc-libs (4.8.1-2 -> 4.8.1-3)
    [2013-08-31 18:35] [PACMAN] upgraded libbsd (0.5.2-2 -> 0.6.0-1)
    [2013-08-31 18:35] [PACMAN] upgraded libfm (1.1.1-1 -> 1.1.2-1)
    [2013-08-31 18:35] [PACMAN] upgraded libgdiplus (2.10.9-1 -> 2.10.9-2)
    [2013-08-31 18:35] [PACMAN] upgraded libreoffice-en-GB (4.0.4-1 -> 4.0.5-1)
    [2013-08-31 18:35] [PACMAN] upgraded libreoffice-common (4.0.4-2 -> 4.0.5-1)
    [2013-08-31 18:35] [PACMAN] upgraded libreoffice-base (4.0.4-2 -> 4.0.5-1)
    [2013-08-31 18:35] [PACMAN] upgraded libreoffice-calc (4.0.4-2 -> 4.0.5-1)
    [2013-08-31 18:35] [PACMAN] upgraded libreoffice-draw (4.0.4-2 -> 4.0.5-1)
    [2013-08-31 18:35] [PACMAN] upgraded libreoffice-gnome (4.0.4-2 -> 4.0.5-1)
    [2013-08-31 18:35] [PACMAN] upgraded libreoffice-impress (4.0.4-2 -> 4.0.5-1)
    [2013-08-31 18:35] [PACMAN] upgraded libreoffice-kde4 (4.0.4-2 -> 4.0.5-1)
    [2013-08-31 18:35] [PACMAN] upgraded libreoffice-math (4.0.4-2 -> 4.0.5-1)
    [2013-08-31 18:35] [PACMAN] upgraded libreoffice-postgresql-connector (4.0.4-2 -> 4.0.5-1)
    [2013-08-31 18:35] [PACMAN] upgraded libreoffice-sdk (4.0.4-2 -> 4.0.5-1)
    [2013-08-31 18:35] [PACMAN] upgraded libreoffice-sdk-doc (4.0.4-2 -> 4.0.5-1)
    [2013-08-31 18:35] [PACMAN] upgraded libwpd (0.9.6-1 -> 0.9.9-1)
    [2013-08-31 18:35] [PACMAN] upgraded libreoffice-writer (4.0.4-2 -> 4.0.5-1)
    [2013-08-31 18:35] [PACMAN] upgraded libsamplerate (0.1.8-1 -> 0.1.8-2)
    [2013-08-31 18:35] [PACMAN] upgraded libwbclient (4.0.8-1 -> 4.0.9-1)
    [2013-08-31 18:35] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
    [2013-08-31 18:35] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
    [2013-08-31 18:35] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
    [2013-08-31 18:35] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
    [2013-08-31 18:35] [ALPM-SCRIPTLET] ==> Starting build: 3.10.10-1-ARCH
    [2013-08-31 18:35] [ALPM-SCRIPTLET] -> Running build hook: [base]
    [2013-08-31 18:35] [ALPM-SCRIPTLET] -> Running build hook: [udev]
    [2013-08-31 18:35] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
    [2013-08-31 18:35] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
    [2013-08-31 18:35] [ALPM-SCRIPTLET] -> Running build hook: [block]
    [2013-08-31 18:35] [ALPM-SCRIPTLET] -> Running build hook: [keymap]
    [2013-08-31 18:35] [ALPM-SCRIPTLET] -> Running build hook: [encrypt]
    [2013-08-31 18:35] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
    [2013-08-31 18:35] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
    [2013-08-31 18:35] [ALPM-SCRIPTLET] ==> Generating module dependencies
    [2013-08-31 18:35] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
    [2013-08-31 18:35] [ALPM-SCRIPTLET] ==> Image generation successful
    [2013-08-31 18:35] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
    [2013-08-31 18:35] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
    [2013-08-31 18:35] [ALPM-SCRIPTLET] ==> Starting build: 3.10.10-1-ARCH
    [2013-08-31 18:35] [ALPM-SCRIPTLET] -> Running build hook: [base]
    [2013-08-31 18:35] [ALPM-SCRIPTLET] -> Running build hook: [udev]
    [2013-08-31 18:35] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
    [2013-08-31 18:35] [ALPM-SCRIPTLET] -> Running build hook: [block]
    [2013-08-31 18:35] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
    [2013-08-31 18:35] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: bfa
    [2013-08-31 18:35] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
    [2013-08-31 18:35] [ALPM-SCRIPTLET] -> Running build hook: [keymap]
    [2013-08-31 18:35] [ALPM-SCRIPTLET] -> Running build hook: [encrypt]
    [2013-08-31 18:35] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
    [2013-08-31 18:35] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
    [2013-08-31 18:35] [ALPM-SCRIPTLET] ==> Generating module dependencies
    [2013-08-31 18:35] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
    [2013-08-31 18:35] [ALPM-SCRIPTLET] ==> Image generation successful
    [2013-08-31 18:35] [PACMAN] upgraded linux (3.10.5-1 -> 3.10.10-1)
    [2013-08-31 18:35] [PACMAN] upgraded linux-headers (3.10.5-1 -> 3.10.10-1)
    [2013-08-31 18:35] [PACMAN] upgraded logrotate (3.8.5-1 -> 3.8.6-1)
    [2013-08-31 18:35] [ALPM] warning: /etc/lvm/lvm.conf installed as /etc/lvm/lvm.conf.pacnew
    [2013-08-31 18:35] [PACMAN] upgraded lvm2 (2.02.98-4 -> 2.02.100-1)
    [2013-08-31 18:35] [PACMAN] upgraded maven (3.0.5-1 -> 3.1.0-1)
    [2013-08-31 18:35] [PACMAN] upgraded net-snmp (5.7.2-7 -> 5.7.2-8)
    [2013-08-31 18:36] [PACMAN] upgraded nodejs (0.10.15-1 -> 0.10.17-1)
    [2013-08-31 18:36] [PACMAN] upgraded obex-data-server (0.4.6-7 -> 0.4.6-8)
    [2013-08-31 18:36] [PACMAN] upgraded openresolv (3.5.5-1 -> 3.5.6-1)
    [2013-08-31 18:36] [ALPM] warning: /etc/pacman.d/mirrorlist installed as /etc/pacman.d/mirrorlist.pacnew
    [2013-08-31 18:36] [PACMAN] upgraded pacman-mirrorlist (20130626-1 -> 20130830-1)
    [2013-08-31 18:36] [PACMAN] upgraded pcmanfm (1.1.1-1 -> 1.1.2-1)
    [2013-08-31 18:36] [ALPM] warning: /etc/php/php.ini installed as /etc/php/php.ini.pacnew
    [2013-08-31 18:36] [PACMAN] upgraded php (5.4.17-1 -> 5.5.3-1)
    [2013-08-31 18:36] [PACMAN] upgraded php-pear (5.4.17-1 -> 5.5.3-1)
    [2013-08-31 18:36] [PACMAN] upgraded poppler-glib (0.24.0-1 -> 0.24.1-1)
    [2013-08-31 18:36] [PACMAN] installed python-setuptools (1.0-1)
    [2013-08-31 18:36] [PACMAN] upgraded python-pip (1.4-1 -> 1.4.1-2)
    [2013-08-31 18:36] [PACMAN] upgraded python2-markupsafe (0.18-1 -> 0.18-2)
    [2013-08-31 18:36] [PACMAN] upgraded python2-mako (0.8.1-1 -> 0.8.1-2)
    [2013-08-31 18:36] [PACMAN] upgraded python2-pip (1.4-1 -> 1.4.1-2)
    [2013-08-31 18:36] [PACMAN] upgraded python2-zope-interface (4.0.5-1 -> 4.0.5-2)
    [2013-08-31 18:36] [PACMAN] upgraded sqlite (3.7.17-1 -> 3.8.0.1-1)
    [2013-08-31 18:36] [PACMAN] upgraded qt4 (4.8.5-1 -> 4.8.5-2)
    [2013-08-31 18:36] [PACMAN] upgraded redshift (1.7-6 -> 1.7-7)
    [2013-08-31 18:36] [PACMAN] upgraded reiserfsprogs (3.6.23-1 -> 3.6.24-1)
    [2013-08-31 18:36] [PACMAN] upgraded run-parts (4.3.4-1 -> 4.4-1)
    [2013-08-31 18:36] [PACMAN] upgraded smbclient (4.0.8-1 -> 4.0.9-1)
    [2013-08-31 18:36] [PACMAN] upgraded samba (4.0.8-1 -> 4.0.9-1)
    [2013-08-31 18:36] [PACMAN] upgraded serf (1.2.1-1 -> 1.3.0-1)
    [2013-08-31 18:36] [PACMAN] upgraded smartmontools (6.1-3 -> 6.2-1)
    [2013-08-31 18:36] [PACMAN] upgraded subversion (1.8.1-1 -> 1.8.1-2)
    [2013-08-31 18:36] [PACMAN] upgraded vim-runtime (7.3.1287-1 -> 7.4.0-2)
    [2013-08-31 18:36] [PACMAN] upgraded vim (7.3.1287-1 -> 7.4.0-2)
    [2013-08-31 18:36] [PACMAN] upgraded wicd (1.7.2.4-7 -> 1.7.2.4-9)
    [2013-08-31 18:36] [PACMAN] upgraded wicd-gtk (1.7.2.4-7 -> 1.7.2.4-9)
    [2013-08-31 18:36] [ALPM-SCRIPTLET] >>> This driver now uses SNA as the default acceleration method. You can
    [2013-08-31 18:36] [ALPM-SCRIPTLET] still fall back to UXA if you run into trouble. To do so, save a file
    [2013-08-31 18:36] [ALPM-SCRIPTLET] with the following content as /etc/X11/xorg.conf.d/20-intel.conf :
    [2013-08-31 18:36] [ALPM-SCRIPTLET] Section "Device"
    [2013-08-31 18:36] [ALPM-SCRIPTLET] Identifier "Intel Graphics"
    [2013-08-31 18:36] [ALPM-SCRIPTLET] Driver "intel"
    [2013-08-31 18:36] [ALPM-SCRIPTLET] Option "AccelMethod" "uxa"
    [2013-08-31 18:36] [ALPM-SCRIPTLET] EndSection
    [2013-08-31 18:36] [PACMAN] upgraded xf86-video-intel (2.21.14-1 -> 2.21.15-1)
    [2013-08-31 18:36] [PACMAN] upgraded xorg-xset (1.2.2-2 -> 1.2.3-1)
    I've just tried rebuilding the initramfs. It goes through without errors, but still won't accept my password on boot.

  • Can't boot OS after installation on TS200 with ServeRAID card

    Hi,
    I have a Lenovo TS200 which I am having problems with.  It is fitted with a ServeRAID card and a single 2TB HD (configured as JBOD and set bootable).
    After having installed Windows Server 2008 (which installs fine) it won't boot.  Basically it seems that the boot device can't be
    found (so Windows doesn't even get to load).  Also I've had the same issue with WHS v2 so it's not specific to the OS.
    BTW, during the installation of the OS I needed to add the drivers (via USB) for the ServeRAID card.
    When I look in the BIOS boot settings I can see a new device that seems to have been automatically added by the installation
    process.  I have tried all of the sensible boot options in the BIOS.
    Another thing I have noticed is that during the continual boot cycle/loop I'm NOT seeing the Network Card or ServeRAID BIOS as I normally do as follows (as an example):
    Initializing Intel(R) Boot Agent GE v1.3.27
    PXE 2.1 Build 086 (WfM 2.0)
    Initializing Intel(R) Boot Agent GE v1.3.27
    PXE 2.1 Build 086 (WfM 2.0)
    LSI MegaRAID SAS-MFI BIOS
    Version 4.14.00 (Build Jan 29, 2010)
    Copyright(c) 2010 LSI Corporation
    HA -0 (Bus 26 Dev 0) ServeRAID M1015 SAS/SATA Controller
    0 JBOD(s) found on the host adapter
    0 JBOD(s) handled by BIOS
    0 Virtual Drive(s) found on the host adapter
    0 Virtual Drive(s) handled by BIOS
    Press <Ctrl><H> for WebBIOS or press <Ctrl><Y> for Preeboot CLI
    I have tried setting the BIOS back to defaults but that's not helped.
    Any thoughts appreciated.
    Cheers Ian

    Which RAID card do you have, and what's your HDD model/type?
    And of course assuming uEFI and firmwares have been updated to the latest?

  • Can't boot to 10.4 install disc with Powerbook G4 15" (alu hi-res)

    I had the four disc cd version of tiger for my older G3 imac with a slot loading cd-rom drive. I've recently replaced the hard disc in the imac and need to reinstall tiger on it, but it seems the cd-rom drive's given up the ghost. It won't read any discs anymore. So I thought instead I'd start it up in target disc mode and use my powerbook to install tiger to it. However I've run into another problem.
    Target disc mode works and everything but the powerbook is having trouble with the boot disc. I thought I'd be able to run the installer off the disc but it asks for the computer to be restarted, so I figured I'd do that and presumably target disc mode would still work. However upon restarting the powerbook and letting tiger load, it gets as far as the apple logo with the spinning loading icon, then after a few minutes of loading the screen goes blue, then it just gets stuck.
    The disc drive eventually spins down and nothing happens. I have to force the computer to shut down. I've tried zapping the PRAM but that didn't work. Any ideas what's wrong? I have leopard 10.5 on the powerbook as my default OS, which works fine. The 10.4 disc is also apparently clean as a whistle, no visible scratches. I used disc utility to scan the disc when I was booted into 10.5 and it shows the disc as apparently being ok.

    With the retail installer, it should work. Here's some links that may help.
    Installing OS X 10.4 'Tiger' on DVD-Challenged Macs Using FireWire Target Disk Mode @ http://lowendmac.com/misc/06/0710.html
    Installing Tiger Without a DVD Drive
    http://www.oreillynet.com/mac/blog/2005/05/thecats_mustachesinstalling.html
    How To: Installing Tiger Using FireWire Target Disk Mode
    http://www.applelinks.com/index.php/more/osx_odyssey_752_how_to_installing_tiger_using_firewire_target_diskmode/
     Cheers, Tom

  • P45 Neo3-FR memory problem / questions

    Hello all
    My old motherboard just died on me so yesterday I upgraded to a P45 Neo3-FR with an Intel E8500.  Problem is that I can't get it to boot up with my old memory (4 x 1Gb modules as below).  Most of the time the PC doesn't do anything, no screen, no post, but occasionally some weird characters at the top of the screen.  I have put in some old DDR2 RAM and the system starts up OK.  I bought this board as the MSI spec page says it supports 1066 memory.
    Questions,
    1) Is there any chance of getting this memory working in the board?
    2) If so, how?
    3) If not, what should I replace it with?
    4) Do I need to touch the 2 jumpers to change the FSB.  I left them on default and everything "seems" to be working OK but I guess I should be setting them to 333 for my CPU?
    5) I have installed 2 system fans on the MB connectors.  The fans are spinning but the speeds are not being reported in the BIOS.  Any ideas?
    6) Is there a comprehensive setup guide for this board anywhere on this forum?  There was an excellent one for my old MSI board and I'm not finding the manual to be much help to be honest.
    Thanks very much (in advance) for any help with all this.
    P.S.  I don-t know what BIOS version the board came with.  I will check it when I get home.
    Intel E8500
    P45 Neo3-FR (PCB 1.0)
    4Gb Corsair TWIN2X2048-8500C5DF
    ASUS 8800GTX
    Zalman 460W PSU

    Quote
    I bought this board as the MSI spec page says it supports 1066 memory.
    Note that is says "1066* (OC)" on the product page.  The Intel P45 Chipset does not natively support DDR2-1066 memory modules.
    This is the datasheet for your Corsair Memory modules:
    http://www.corsair.com/_datasheets/TWIN2X2048-8500C5DF.pdf
    As you can see, these modules are essentially DDR2-800 modules and that DDR2-1066 @2.1-2.2V is an overclocking rating that requires non-standard voltage settings.  Those OC Settings are pre-programmed into the SPD Chips of your memory modules via an EPP-Profile which is essentially an overclocking profile which is for NVIDIA Chipset boards, not for Intel Chipset boards.  Even if the BIOS is able to notice the DDR2-1066 EPP profile and decides to AUTO-memory frequency to 1066 MHz, it is not able to raise the memory voltage accordingly (it can't, because as I said, EPP Profile Information and settings parameters are for NVIDIA Chipset.)
    Do you see now, why your system won't boot?
    Try this:
    - try one of the factory overclocked Corsair stick alone
    If that works, lower memory frequency to DDR2-800 in BIOS and check again, if the system will boot with four sticks (you may have to raise memory voltage slightly.
    If that fails, put in one of your DDR2-800 sticks, then set FSB/DRAM Ratio to 1:1, save an exit and then try again with your factory overclocked modules.

  • Can't Boot From Install Disc 1 ?

    Holding down "C" at Start Up isn't working.
    Most of the time I can't get Preferences > Start-Up to even "see" my Disc 1.
    When I can get it to show up in Start-Up, and Select it, and Lock it ... it Still Won't Start Up from the Install Disc 1 ... and in fact usually ejects the disc.
    Sometimes when I re-push in the disc, I get the message that a Blank Disc has been detected, "what do you want to do with it."
    But, it shows up in Disc Utility, and when I run Verify Disc, it all looks good?!
    The Disc has Mac OS version 10.4.8 on it. I'm running 10.5.7. I'm all up to date with my software.
    Yesterday I ran the latest version of Disc Warrior. When I run TechTools 4.0 it seems to get stuck running Files. When I run Repair Permissions from Disc Utilities, it shows a fairly massive amount of issues. Running it over and over again doesn't seem to make any difference.
    I WANT to run my Install Disc so I can run Repair Disc from Disc Utility ... because I'm having a number of issues ... and I seem to get the spinning rainbow a lot.
    SUGGESTIONS ?! ... thanks ...

    Disk Utility that can repair a 10.5.7 permissions is only found on the Leopard installer disc. Tiger can't repair Leopard when it comes to permissions, and may also have difficulty with the directory.
    Secondly, if your MacBook Pro was purchased after October 26, 2007, it can't boot from any Tiger disc.
    If your MacBook Pro was purchased prior, you can use the disk, but you'll want to follow these directions for hardware diagnostics:
    http://docs.info.apple.com/article.html?artnum=303081
    Only if your MacBook Pro has Tiger installed, should you use Tiger for the directory or permissions*:
    http://www.macmaps.com/directoryfaq.html
    Macs can only boot from the operating system that shipped with them, and newer retail operating systems. This means:
    1. pre-October 1st, 2007 MacBook Pros can boot off:
    - - the discs that shipped with them
    - - retail 10.5 discs which look like * that do not say Upgrade, DropIn, or OEM.
    2. October 1st through October 25, 2007 can do #1, and also use Upgrade and DropIn discs. Those disks were offered as a limited time mail order Up to date program, some were dropped in the box that came with them.
    3. October 26th through November 14, 2007 can boot off the discs that came with them, and retail 10.5.1, 10.5.4, and 10.5.6 discs that do not say Upgrade, DropIn, or OEM, and have a label like the image above.
    4. November 15, 2007 through June 29, 2008 can boot off the discs that came with them, and the retail 10.5.4, and 10.5.6 discs that do not say Upgrade, DropIn, or OEM, and have a label like the image above.
    5. June 30, 2008 through December 14, 2008 can boot off the discs that came with them, and the retail 10.5.6 discs that do not say Upgrade, DropIn, or OEM, and have a label like the image above.
    6. December 15, 2008 and later MacBook Pros can only boot off the discs that came with them.
    Presumably when Snow Leopard comes out in September, all of the above will be able to use Snow Leopard because of the specs on http://www.apple.com/macosx/specs.html
    - * Links to my pages may give me compensation.
    Message was edited by: a brody

  • Can not boot off of installation disk - MBP 10.6

    I am trying to wipe and reinstall the OS in my 2010 MBP 15. I have tried everything - and it will not boot off of the disk. It sees the disk and starts to boot - but it gets stuck at the gray screen with the darker gray Apple logo. I tried it with the original disks that came with the MBP (has OS 10.5.7). And, I tried it with the store-bought Snow Leopard disks (when 10.6 first came out). 
    Here is a partial list of what I've tried:
    Held down the C key to boot directly off of the disk - stuck at gray screen
    Held down the Option key and then selected the disk - stuck at gray screen
    I thought maybe it was the optical drive. So, I put a DVD movie in there - and it played just fine.
    Reset the PRAM
    Cloned the hard drive to an external HD. Booted from the cloned HD using a firewire. Then, used Disk Utility to Erase the internal HD. Then, restarted with nothing on the internal HD. Still wouldn't boot from the disk
    Reset the SMC
    Checked hard drive with Disk Warrior - and it found that the HD was fine. Ran SMART - and it also tested just fine
    I've tried all I can think of to just get the MBP

    If you can't boot from a valid installation disc with no peripherals connected, then you have a hardware problem. Take the unit in for service.

  • Can't boot from cd or dvd

    i have a imac with isight 20 inch, when startup i get a grey screen with a folder that blinks with a question mark and the two faces symbol, when i leave it like this for a minut, fan starts blowing at full speed.
    i run leopard with all the updates untill januari 7 2009
    I have a iomega timemachine disk from this imac
    i can not boot from a cd that came with this imac neither from the leopard dvd
    how can i find out what is wrong? why can i not boot from cd (all threads i read say you should do this but it just won't go) i noticed my dvd drive often rejected cd's lately but after several trys i would eventually....
    can i boot from a timemachine set up hdd from this broken imac to find out what hardware failed ?

    If your hard drive fails, Time Machine cannot boot your computer. A bootable clone, which is an exact copy of your system and its contents, can be used to boot your machine, or, if you install a new drive, to reverse clone (or make the new drive exactly like to old one).
    Time Machine can restore your system to the state it was in on any given day, but you must have a working hard drive with the OS installed on it. I use both TM and a clone that I automatically make with SuperDuper!, so that if I want to restore a file, I can use TM, if I want to exactly duplicate my HDD, I use my SD! clone and am up and running with an exact copy of my machine before the hard drive died.
    You will be able to restore from TM once you have initialized the new drive and put an OS on it.

  • Can't boot from an upgraded drive

    Hi, I upgraded a 12" PowerBook G4 to a 160GB HD. The machine was running 10.4.11 on its original 60GB drive.
    The new drive formatted correctly (extended), and I clean installed OS 10.4 without a hitch. But on reboot, after the apple logo, I ended up with a solid blue screen. Tried an update to 10.4.11, and got the same result. I zapped the PRAM and still can't boot -- though now I start up with vertical pinstripes behind the apple logo, then a black screen.
    I've checked the new drive thoroughly with Disk Utility and Tech Tool, and no problems there. SMART status fine, same power requirements, etc. Boot ROM version is 4.9 0f0, which should support a 160 GB drive, if I'm not mistaken, but can't find any info on the Support site as to what the correct Boot ROM version should be to run with 10.4.11.
    I can boot fine from the original drive via a firewire enclosure, so no hardware problems with the G4.
    Any ideas? Thanks!

    Okay, I don't know what happened, but it seems to be fixed now.
    I migrated the old system files over from the original drive (hadn't wanted to, as I assumed a clean install would simplify things). After doing that, I got a kernel panic screen at startup, which after a blank screen, seemed like progress.
    Then I zapped PRAM and reset the PMU again, and voila. Everything is fine. If anyone has any clue what could've been better about a crufty old System folder than a fresh clean install of the same version of the OS, I'd love to know.

Maybe you are looking for