Restart failed - no longer able to boot

I plugged a USB external DVD (as my B&W has only a CD-Rom) in order to install OS X. I was able to get to the OS X Welcome page, wher it ask to RESTART. As the RESTART did not work, I went to the startup disk select, saw the DVD with OS X, selected it, then clicked on RESTART from the Welcome screen of OS X.
Now, surprise : all I get is a dolder with a question mark (?) blinking. The Support online here says to go back and select another startup disk, which *of course* I cannot do!
I disconnected the DVD, retried many times, there is nothing to do.
Any insight or trick so I can restart this machine ?
Thanks,

Check firmware (see link later in post)
This may sound like an involved solution but the USB ports come online too late in the boot sequence to use as boot device.
Instead, consider replacing CD drive with a new DVD burner. You can pick up a DVD+-RW for about $40-80 at any computer store. Or open the USB burner case you have and remove the drive.
Open your B&W (power down of course)
For a temporary work around, notice that there are 2 ATA cables on the motherboard. Unplug the chain to the optical/ZIP carrier. Plug any ATA 33/66/100 cable into the system board and your DVD drive. Make sure your optical drive is set to master (check jumper settings). There are several unused power connectors in a Yikes case, use any one.
Restart with your CURRENT OS. Check system profiler to verify drive. (Burning may not be supported fix that later by visiting http://patchburn.de and get Patchburn. It installs profiles for ANY burner not Apple OE.)
Now insert your install DVD, hit restart (don't change start up disk) and hold down "C". If your B&W doesn't boot to 10.4 DVD you can release the "C" and it will boot to original drive. If is doesn't boot to 10.4 check firmware updates
http://docs.info.apple.com/article.html?artnum=86117
And seriously consider installing that cheap DVD drive in your B&W. The Yikes case is really easy to upgrade. And if you are brave you can turn that G3/400 (100 FSB) into a G3/472 (105 FSB)
G4/533 Dual   Mac OS X (10.3.9)  

Similar Messages

  • No longer able to boot into OSX

    My Mac Mini will only boot to Windows XP (I realise this situation is not without some degree of irony).
    Bootcamp has been installed for several months and I have had no problems booting between OSX and XP. I have not booted into XP recently only OSX and there have been no problems.
    Today I booted up from a shutdown and found that my Mac Mini booted into XP. I wasn't too worried so went into the Boot Camp control panel and selected "Restart in OSX". As Windows was shutting down, I noticed that it was installing several updates. My Mac Mini proceeded to boot back into XP and continued to install the remaining components of whatever updates it had previously been installing.
    So I repeated the Boot Camp control panel drill several times...each time, despite selecting to restart in OSX, it would restart in XP.
    I then tried holding down the Option key and was duly presented with the two partitions - "Hard Drive" or "Windows"...I selected Hard Drive (i.e. OSX)...and the system booted into Windows! Repeated this exercise but this time trying the second partition (i.e. Windows)...and the system booted into Windows (as you would expect).
    I have not done anything to the partitions/hard drive in recent months...the only thing I can think of is that I may have installed some Mac OSX updates earlier today...
    Any assistance to help me boot back into OSX would be appreciated (I realise my worst case scenario is a reinstall).
    Thanks
    Darren

    Thanks Stefan.
    I followed your instructions which did detect some errors in both the disk and permissins which I have repaired. I then reran the verify to check that there were no more errors. Following that I selected the Mac OSX startup volume and initiated a restart...it still boots into Windows!
    Understanding how to use the repair features of the OSX DVD was useful but unfortunately I am still looking for a solution.
    As a last effort, I tried rebooting while holding down the 'X' key...this did produce an onscreen log for a split second...from what I can make out in the short time it is onscreen...it appears to be trying to load the mac kernel and there is an error message saying "Read file failed: status"
    Any further ideas would be appreciated.
    Thanks
    Darren

  • No longer able to boot - failure with /boot

    I recently, due to a hard drive change, rebuilt my desktop.  Every now and again, since then, it hasn't booted.  I just logged into root and rebooted; figuring I'd sort it out at some point.
    Only, now it won't boot at all.  When I go through journalctl -xb I get the following errors (the ellipsis, in case it isn't clear, indicate an number of lines with no error in between the error messages):
    Job dev-sda2.device/start timed out.
    Timed out waiting for device dev-sda2.device.
    Dependency failed for /boot.
    Dependency failed for Local File Systems.
    Triggering OnFailure= dependencies of local-fs.target.
    Dependency failed for File System Check on /dev/sda2
    and also, much later in the logs:
    Failed at step EXEC spawning /bin/plymouth: No such file or directory
    My initial assumption would have been that the relevant drive is failing, but I only recently ran a check on the drives (a few days ago and since the rebuild) and all was fine and dandy - but I had already been seeing these errors on a periodic basis.  Only now, as I said, they happen at every boot and I never get as far as login.
    Thanks in advance for any help.

    I ran the extended smartmontools test on the disk today and it returned with no errors.  However, the error log for the disk did contain the following:
    Complete error log:
    SMART Error Log Version: 1
    Warning: ATA error count 21 inconsistent with error log pointer 5
    ATA Error Count: 21 (device log contains only the most recent five errors)
    CR = Command Register [HEX]
    FR = Features Register [HEX]
    SC = Sector Count Register [HEX]
    SN = Sector Number Register [HEX]
    CL = Cylinder Low Register [HEX]
    CH = Cylinder High Register [HEX]
    DH = Device/Head Register [HEX]
    DC = Device Command Register [HEX]
    ER = Error register [HEX]
    ST = Status register [HEX]
    Powered_Up_Time is measured from power on, and printed as
    DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
    SS=sec, and sss=millisec. It "wraps" after 49.710 days.
    Error 21 occurred at disk power-on lifetime: 10341 hours (430 days + 21 hours)
    When the command that caused the error occurred, the device was in an unknown state.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    c8 00 08 00 00 00 e0 08 01:12:12.224 READ DMA
    27 00 00 00 00 00 e0 08 01:12:12.224 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
    ec 00 00 00 00 00 a0 0a 01:12:12.224 IDENTIFY DEVICE
    ef 03 45 00 00 00 a0 0a 01:12:12.224 SET FEATURES [Set transfer mode]
    27 00 00 00 00 00 e0 08 01:12:12.224 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
    Error 20 occurred at disk power-on lifetime: 10341 hours (430 days + 21 hours)
    When the command that caused the error occurred, the device was in an unknown state.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    c8 00 08 00 00 00 e0 08 01:11:26.048 READ DMA
    27 00 00 00 00 00 e0 08 01:11:26.048 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
    ec 00 00 00 00 00 a0 0a 01:11:26.048 IDENTIFY DEVICE
    ef 03 46 00 00 00 a0 0a 01:11:26.048 SET FEATURES [Set transfer mode]
    27 00 00 00 00 00 e0 08 01:11:26.048 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
    Error 19 occurred at disk power-on lifetime: 10341 hours (430 days + 21 hours)
    When the command that caused the error occurred, the device was in an unknown state.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    c8 00 08 00 00 00 e0 08 01:10:16.816 READ DMA
    27 00 00 00 00 00 e0 08 01:08:51.584 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
    ec 00 00 00 00 00 a0 0a 01:08:51.584 IDENTIFY DEVICE
    ef 03 46 00 00 00 a0 0a 01:08:51.584 SET FEATURES [Set transfer mode]
    27 00 00 00 00 00 e0 08 01:08:51.568 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
    Error 18 occurred at disk power-on lifetime: 10340 hours (430 days + 20 hours)
    When the command that caused the error occurred, the device was in an unknown state.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    25 00 01 00 00 00 e0 08 00:04:28.384 READ DMA EXT
    c6 00 10 00 00 00 e0 08 00:04:28.384 SET MULTIPLE MODE
    91 00 3f 00 00 00 a0 08 00:04:28.384 INITIALIZE DEVICE PARAMETERS [OBS-6]
    10 00 00 00 00 00 a0 08 00:04:28.352 RECALIBRATE [OBS-4]
    25 00 01 00 00 00 e0 04 00:04:28.352 READ DMA EXT
    Error 17 occurred at disk power-on lifetime: 10340 hours (430 days + 20 hours)
    When the command that caused the error occurred, the device was in an unknown state.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    25 00 01 00 00 00 e0 08 00:04:28.288 READ DMA EXT
    c6 00 10 00 00 00 e0 08 00:04:28.288 SET MULTIPLE MODE
    91 00 3f 00 00 00 a0 08 00:04:28.288 INITIALIZE DEVICE PARAMETERS [OBS-6]
    10 00 00 00 00 00 a0 08 00:04:28.272 RECALIBRATE [OBS-4]
    25 00 01 00 00 00 e0 04 00:04:28.272 READ DMA EXT
    Does this mean my disk is dying?  That would be very annoying after just rebuilding from another failed disk!

  • [Solved] No longer able to boot Kernel

    Haven't been able to post this since I've been without internet for a time. Since the update requiring manual intervention on /etc/mtab (20th Dec, in the news feed) I have been unable to boot the kernel. Exact output is due to come (will have to try and boot it again then copy it down to get it) but the gist of it is that it can't find the modules, and so is not able to mount any partitions, dropping to an emergency shell.
    I've tried using a livecd to access it, and can mount the partitions, but proc will not mount once chrooted into the environment, and without it mkinitcpio seems unable to detect any filesystems.
    I suspect it's time for a reinstall because of this, but hope there's a fix that will save me the time and hassle of doing so.
    Last edited by Gremnon (2012-01-14 21:31:10)

    You have to mount /dev and /proc before chrooting. https://wiki.archlinux.org/index.php/Re … e_you_boot
    Other topics about the mismatch between the version of the kernel and the modules seem to be cropping up recently on the forum. Perhaps you will find some answers to your problem in them.
    Last edited by lucke (2012-01-14 20:37:43)

  • MSI K7N2 No longer able to boot up (Thinking PSU problem)

    I have a computer that was a hand-me-down from my husband that he originally built 12 years ago.  Recently I've been having trouble turning on the computer.  I will hit the power button, hear the fans running, but nothing else will power on.  There are no hard-drive beeps, the keyboard and screen won't respond.  The mouse lights up, but is useless.
    Before yesterday I could hit the restart button, or use the power button to turn it back off and back on to get the computer to boot up.  I would have to do this up to 8 times before it would catch, but eventually it would turn on.  Yesterday the computer was on when it reverted to just the fans running and nothing else.  I tried restarting it multiple times, but it never booted.  I opened it up, cleaned the mountain of dust, checked all the connections and tried again.  After many restart attempts with no response aside from running fans I figured it was time to ask for help.
    I think it is a power supply issue
    Enlight Corporation HPC-340-101
    +5V - 30A
    +12V - 15A
    +3.3V - 28A
    340W
    The power supply has never been replaced so it is 12 years old.
    I have been considering building a new computer and was looking at this power supply:
    Antec High Current Gamer Series HCG-750 750W ATX12V v2.3 / EPS12V v2.91 SLI Certified CrossFire Certified 80 PLUS BRONZE Certified Active PFC
    Would this fry my old motherboard?  My husband said that was possible, so I'm hesitant to try.
    Please let me know if I've done something wrong, or not provided enough information.  I will keep my computer opened up until I hear from someone so I can answer any questions if need be.  I've put my other computer specs in my signature.  Let's see if they actually post 

    So I tried my Mother-In-Law's PSU since my husband is over-protective of his computer.  No luck.  I took out the graphics card and it was pure luck that my husband remembered one of his siblings left an old computer in the spare room.  It had an old GeForce FX 5200 128Mb, so I salvaged it and it worked!  My computer booted up on the first try!  I had to switch back to my PSU as my Mother-In-Law is still using hers, but it still started up perfectly!  I am so excited!  Of course this means I don't have a valid reason to push for my new computer, and I probably can't play the Sims 3 anymore, but I still have a working computer
    Thank you guys so much!

  • My new WD hard drive is no longer able to boot. How do I fix this?

    I got a WD10EALX Cabiar Blue drive last week and copied my existing internal drive that had Tiger OSX on it. It booted fine until I copied an iphoto library from a friend's Mac and now this disk won't boot. I get the circle with the slash through it and the folder with the question mark on it. I ran it through disk utility and it was verified with no problems. What should I do from here?
    Western Digital Caviar Blue 1 TB,7200 RPM (WD10EALX) Hard Drive

    Well, assuming you mean you repaired permissions in Disk Utility, and that you ONLY copied some data/media files, and didn't go beyond 85% full, I'd say go back to square one on this experiment.
    A better approach is to leave or have an "OS only" boot drive, with apps of course, and keep data and media files on another disk drive - the beauty of having four internal hard drives.
    By the sounds of it you are using an external drive too. That alone can sometimes be a problem.
    As for "verify with Disk Utility" back in Tiger, I give it iffy grade and marks. Repair AND use Disk Warrior.

  • Not able to boot OES admin server

    Hi,
    I am not able to boot the admin server after running the install-ales-schema.bat. It gives Arme not Ready Exception.
    <Apr 24, 2010 9:03:12 PM CDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: Weblogic.security.SecurityInitializationException: User admin is not permitted to boot the server; The server policy may have changed i
    n such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions. weblogic.security.SecurityInitializationException: User admin is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.do
    BootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:991)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.in
    itialize(CommonSecurityServiceManagerDelegateImpl.java:1029)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:854)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    Truncated. see log file for complete stacktrace
    >
    Edited by: user12057577 on Apr 24, 2010 3:17 AM

    Hi,
    Can you mention the steps you used before running the ales_install script? Which WLS version are you using for Admin Server? Is it CP3 or CP4 patched?

  • I installed the new version of iTunes today. It's 12.1.1. After completing the installation, including restarting my computer, I was no longer able to use Windows Internet Explorer. Has anybody else experienced this? If so, how did you fix Explorer?

    I installed the new version of iTunes today. It's 12.1.1. After completing the installation, including restarting my computer, I was no longer able to use Windows Internet Explorer. Has anybody else experienced this? If so, how did you fix Explorer? I was using Explorer 11 and Windows 7, installed on an HP Pavilion g series

    Never heard of that being caused by installing iTunes. Try asking on a Windows forum. This isn't a problem with iTunes or any other Apple product. If you believe it is, uninstall iTunes. If the problem persists, you'll have to seek advice on a Windows forum or contact Microsoft for support.

  • Two Macbook pros circa 2009 in our temporary household in Turkey suddenly failed to boot and got stuck on the grey screen. They were able to boot at the Apple store, but not when we brought them back to our apartment. Could this be a coincidence?   A

    Two Macbook pros circa 2009 in our temporary household in Turkey suddenly failed to boot and got stuck on the grey screen. They were able to boot at the Apple store, but not when we brought them back to our apartment. Could this be a coincidence?   A

    THank you Ogelthorpe. When my wife's computer I went on line to the site that you sent and tried everything But nothing worked. When my son came to visit and his MacBook Pro did exactly the same thing we became suspicious - too much of a coincidence. We took both computers somewhere else, out of our apartment, and they both booted. We ran disk utility on both, but the report in both cases was that there are no issues with the hard drive.  Back in our apartment neither will boot up. My MacBook Pro is a later model with a solid state drive and it seems to work fine here.. I tried an external drive and it works fine. We think that this has something to do with some kind of magnetic interference in our apartment to which the 2009  drives are susceptible.  It is indeed a mystery!
    alf

  • My apple tv, all of a sudden, is no longer able to connect to my computer.  I have restarted EVERYTHING, multiple times, still not working.

    My apple tv, all of a sudden, is no longer able to connect to my computer.  I have restarted EVERYTHING, multiple times, still not working.

    Welcome to the Apple Community.
    Check your store location is set correctly, if this doesn't help, try restarting the Apple TV by removing ALL the cables for a 30 seconds.

  • All of a sudden, I am no longer able to send e-mails (tho I still receive them). the error message says "outgoing server failed" Any ideas?

    All of a sudden, I am no longer able to send e-mails (tho I still receive them). the error message says "outgoing server failed" Any ideas?

    Try:
    - Reset the iOS device. Nothing will be lost       
    Reset iOS device: Hold down the On/Off button and the Home button at the same time for at
    least ten seconds, until the Apple logo appears.
    - Can you send email from that account on another device?
    - You can try deleing the account from the iPod and reentering the settings.

  • CCC or Disk Utility to clone a Mac HD of one new iMac to another, over ThunderBolt, we are getting I/O errors. Even though the clone fails, the destination  system does boot and log in, however, the logins take a very very very long time.

    When using CCC (Carbon Cophy Cloner) or Disk Utility to clone a Mac HD of one new iMac to another, over ThunderBolt, we are getting I/O errors. Even though the clone fails, the destination  system does boot and log in, however, the logins take a very very very long time.
    Thoughts.
    Edit: Already ran Disk Utility. Also reinstalled a fresh OS on top of the cloned OS and it seemed to remedy the problem. Then, cloned to next machine in the row of the lab. Same problem.

    OK, by that I assume that you used Disk Utility to repair the subject disk and it reported "The volume (name) appears to be OK" in green.
    Also verify you followed the instructions here: http://help.bombich.com/kb/usage-scenarios/i-want-to-clone-my-entire-hard-drive- to-a-new-hard-drive-or-a-new-machine
    If so, the Thunderbolt connection begins to look suspicious.
    Reinstalling OS X subsequent to the "clone" operation may be an acceptable workaround but you should not have had the I/O errors you describe, nor should the login times (subsequent to the initial login, that is) be unacceptably long. It calls into question the integrity of all the information that was transferrred.
    I'll try to attract the attention of a CCC expert who will likely provide more competent assistance. You can also try the Bombich support site: http://help.bombich.com

  • I guess I didn't explaine that I have a healthy operating Windows 8 Boot camp partition on my hard drive. When I upgraded to Mavericks I am no long able to access the bootcamp partition from the disk icon in system preferences; the Windows 8 works fine.

    On both Mini Mac and iMac 27" I am no longer able to utalize the Startup Disk icon in System Preferences; the Windows 8 on Bootcamp partition works fine if I close the Mavericks OX and select the Windows partition at bootup from the hard drive. My question is why don't the icon in System Prederences work anymore since I upgraded to Mavericks. Also, Users & Groups, Printers & Scanners icons no longer work either.

    On both Mini Mac and iMac 27" I am no longer able to utalize the Startup Disk icon in System Preferences; the Windows 8 on Bootcamp partition works fine if I close the Mavericks OX and select the Windows partition at bootup from the hard drive. My question is why don't the icon in System Prederences work anymore since I upgraded to Mavericks. Also, Users & Groups, Printers & Scanners icons no longer work either.

  • Help!  I recently upgraded to OS 10.9.4 from 10.6.8, and now when I want to send an email to a group in my contacts I am no longer able to select the group as a whole.  I have to select each address individually.  This can't be right.

    Help!  I recently upgraded to OS 10.9.4 from 10.6.8, and now when I want to send an email to a group in my contacts I am no longer able to select the group as a whole.  I have to select each address individually.  This can't be right.  With 10.6.8 I used to be able to double click on the name of the group and they would all be selected.  I've also noticed that my address book is now called "contacts."  Thanks in advance for your help.

    Try these in order testing your system after each to see if it's back to normal:
    1. a. Resetting your Mac's PRAM and NVRAM
        b. Intel-based Macs: Resetting the System Management Controller (SMC)
    2. Restart the computer in Safe Mode, then restart again, normally. If this doesn't help, then:
         Boot to the Recovery HD: Restart the computer and after the chime press and hold down the
         COMMAND and R keys until the Utilities menu screen appears. Alternatively, restart the
         computer and after the chime press and hold down the OPTION key until the boot manager
         screen appears. Select the Recovery HD and click on the downward pointing arrow button.
    3. Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the Utilities menu. Repair the Hard Drive and Permissions as follows.
    When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu. Select Restart from the Apple menu.
         Reinstall the 10.9.4 update: OS X Mavericks 10.9.4 Update (Combo).
    4. Reinstall Lion/Mountain Lion, Mavericks: Reboot from the Recovery HD. Select Reinstall Lion/Mountain Lion, Mavericks from the Utilities menu, and click on the Continue button.
    Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.
         Reinstall the 10.9.4 update: OS X Mavericks 10.9.4 Update (Combo).

  • After updating to 10.7.3 I am no longer able to connect to the internet.

    Updated to 10.7.3 this morning on my Macbook Air (Oct. 2010 model). After restarting, I am no longer able to connect to the internet. I can connect to the router, and pull a valid IP address (sometimes - other times I get an automatic private IP), but I am unable to get to any websites, check email, etc. I am able to ping websites AND visit websites using their IP addresses, but not using their DNS names.
    I called Applecare this morning, and the tech walked me through some troubleshooting steps, including:
    Rebooting into Repair partition to check connectivity there (same issues, no change)
    Deleting and recreating various config files (Networkinterfaces.plist, preferences.plist and com.apple.airport.preferences.plist) (no change)
    I've also tried reinstalling the update (both delta and combo), repairing disk permissions and rebooting into safe mode, nether of which has solved the issue.
    Also on the network are (Mini, not updated to 10.7.3), a PC, my iPhone and an Apple TV, all of which aren't experiencing any issues. Any ideas?
    Thanks.

    Here is something to try.  Boot into the Recovery HD by holding
    down Command+R when booting.  Select the get help online option.
    It initially opens Safari with a local web page, but you can use
    the bookmarks on the bookmark bar or even enter a website.
    Many extensions may not be available but it could tell you if
    it is your Lion install that is a problem or perhaps a hardware
    problem. 
    If you can browse around in this mode, then it could eliminate
    any possible hardware issues.  If you still have problems, then
    the issue could possibly be hardware/driver related.
    Give it a shot and see what happens.

Maybe you are looking for