Won't boot anymore after nvidia-xconfig

Hey Guys,
Got a problem with my Arch Linux here, hope you can help.
Today I tried to install the official Nvidia Driver and BumbleBee following along the great Wiki on this topic.
Everything worked just fine and I also could run optirun gfxgear or somemthing like this.
I wanted to switch to the Nvidia Settings in the settings menu and it told me to configure my xconfig and restart x so I typed nvidia-xconfig in the terminal and it gave me an success output.
I restarted my system and now it hangs on the graphical thing I think. It won't boot anymore.
Hope you can help me out.
Thanks alot
Edit: My Nvidia Card is a Nvidia GT 740M if this matters
Last edited by Whitz (2015-02-09 11:02:41)

No, I have a laptop with 2 graphic cards an intel hd4000 and a nvidia gt 740m.
I ran the Arch Linux installation well until I tried to get the nvidia gt working with bumblebee.
I followed the wiki of the bumblebee topic and it worked well. I wanted to switch into the nvidia settings and it told me my x isnt configured properly and I should type nvidia-xconfig and restart X.
After the restart it won't boot to the graphical interface anymore.
Hope this cleared up the things
Also I dont get any errors but it just wont load..
Last edited by Whitz (2015-02-09 12:08:49)

Similar Messages

Btrfs: System won't boot anymore after unclean shutdown

Hi,
I have a problem with my ArchLinux (kernel 3.19.2-1-ARCH).
I have my root partition as BTRFS and no /boot partition.
After an unclean shutdown the system won't boot anymore.
GRUB loads the kernel and the kernel starts but it hangs saying: Mounted /dev/sda3 on real root.
Then, I have to start a Live CD and do:
btrfsck /dev/sda3
After that the system boots correctly.
I've tried adding fsck to the HOOKS in the mkinitcpio.conf file and in fact it tries to fsck the filesystem (but with BTRFS, fsck.btrfs doesn't work...)
What can I do?
Thanks

I'm also having this problem. I tried booting up the netinstall image to debug it, but I can't mount my btrfs volume from there either: mount just hangs. After a while, the kernel goes:
[...] INFO: task mount:612 blocked for more than 120 seconds.
[...] Not tainted 3.19.2-1-ARCH #1
[...] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[...] INFO: task btrfs-transacti:636 blocked for more than 120 seconds.
[...] Not tainted 3.19.2-1-ARCH #1
[...] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
From this post I guessed that I might just need to wait so that I could defrag the volume once it was mounted, but it's been hanging for over 15min now (the message above continues to come up periodically).
Like the OP in the thread I linked to above, my btrfs volume is inside an LVM volume (which is on dm-crypt). Don't know whether that's relevant.
Output of btrfs-check:
Checking filesystem on /dev/pixie/btrfs
UUID: e04cc661-e31a-4dbf-870d-664bc913e34a
found 76855677062 bytes used err is 1
total csum bytes: 72928436
total tree bytes: 2092515328
total fs tree bytes: 1888452608
total extent tree bytes: 104644608
btree space waste bytes: 357251032
file data blocks allocated: 181197139968
referenced 109440282624
btrfs-progs v3.19
dmesg output:
[ 36.824998] Btrfs loaded
[ 36.826713] BTRFS: device fsid e04cc661-e31a-4dbf-870d-664bc913e34a devid 1 transid 98618 /dev/dm-3
[ 46.219014] BTRFS info (device dm-3): disk space caching is enabled
[ 46.259830] BTRFS: detected SSD devices, enabling SSD mode
[ 240.333313] INFO: task mount:539 blocked for more than 120 seconds.
[ 240.335542] Not tainted 3.19.2-1-ARCH #1
[ 240.337795] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 240.340263] mount D ffff8800cf2837f8 0 539 453 0x00000000
[ 240.340277] ffff8800cf2837f8 ffff8800cf2331b0 0000000000013f00 ffff8800cf283fd8
[ 240.340286] 0000000000013f00 ffffffff81818540 ffff8800cf2331b0 ffff8802094f67a8
[ 240.340291] 0000000000000004 ffff8800cf283758 ffffffffa0a2fc91 ffff8802094f67a8
[ 240.340298] Call Trace:
[ 240.340335] [<ffffffffa0a2fc91>] ? set_extent_buffer_dirty+0x71/0xc0 [btrfs]
[ 240.340357] [<ffffffffa0a05796>] ? btrfs_buffer_uptodate+0x56/0x80 [btrfs]
[ 240.340366] [<ffffffff8155e999>] schedule+0x29/0x70
[ 240.340389] [<ffffffffa0a47745>] btrfs_tree_lock+0x65/0x200 [btrfs]
[ 240.340396] [<ffffffff810b4380>] ? wait_woken+0x90/0x90
[ 240.340410] [<ffffffffa09e5cd9>] btrfs_search_slot+0x799/0xaa0 [btrfs]
[ 240.340425] [<ffffffffa09e79f5>] btrfs_insert_empty_items+0x75/0xd0 [btrfs]
[ 240.340446] [<ffffffffa0a47a37>] btrfs_insert_orphan_item+0x67/0xa0 [btrfs]
[ 240.340465] [<ffffffffa0a4a12e>] insert_orphan_item+0x5e/0x90 [btrfs]
[ 240.340482] [<ffffffffa0a4c531>] replay_one_buffer+0x361/0x380 [btrfs]
[ 240.340504] [<ffffffffa0a2f244>] ? alloc_extent_buffer+0x34/0x370 [btrfs]
[ 240.340523] [<ffffffffa0a488f3>] walk_down_log_tree+0x1d3/0x410 [btrfs]
[ 240.340540] [<ffffffffa0a48bfb>] walk_log_tree+0xcb/0x1d0 [btrfs]
[ 240.340558] [<ffffffffa0a507f7>] btrfs_recover_log_trees+0x1e7/0x490 [btrfs]
[ 240.340575] [<ffffffffa0a4c1d0>] ? replay_one_dir_item+0xf0/0xf0 [btrfs]
[ 240.340596] [<ffffffffa0a08b3e>] open_ctree+0x17ae/0x2030 [btrfs]
[ 240.340609] [<ffffffffa09dd633>] btrfs_mount+0x843/0x920 [btrfs]
[ 240.340618] [<ffffffff8117b7aa>] ? pcpu_alloc+0x35a/0x680
[ 240.340628] [<ffffffff811d5d68>] mount_fs+0x38/0x1c0
[ 240.340634] [<ffffffff8117bb05>] ? __alloc_percpu+0x15/0x20
[ 240.340641] [<ffffffff811f116b>] vfs_kern_mount+0x6b/0x120
[ 240.340647] [<ffffffff811f4184>] do_mount+0x224/0xb40
[ 240.340653] [<ffffffff811f4dae>] SyS_mount+0x7e/0xe0
[ 240.340661] [<ffffffff81562809>] system_call_fastpath+0x12/0x17
[ 240.340671] INFO: task btrfs-transacti:561 blocked for more than 120 seconds.
[ 240.342927] Not tainted 3.19.2-1-ARCH #1
[ 240.345175] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 240.348473] btrfs-transacti D ffff88020b88bd98 0 561 2 0x00000000
[ 240.348483] ffff88020b88bd98 ffff880211edc590 0000000000013f00 ffff88020b88bfd8
[ 240.348491] 0000000000013f00 ffff8802162289f0 ffff880211edc590 ffff8802094a70c8
[ 240.348496] ffff8802094d8000 ffff880200000000 ffff8802094d8000 ffff880200000033
[ 240.348501] Call Trace:
[ 240.348511] [<ffffffff811b5d1a>] ? kmem_cache_alloc+0x16a/0x180
[ 240.348525] [<ffffffffa09e07ca>] ? btrfs_free_path+0x2a/0x40 [btrfs]
[ 240.348543] [<ffffffffa0a64213>] ? __btrfs_run_delayed_items+0xf3/0x1d0 [btrfs]
[ 240.348550] [<ffffffff8155e999>] schedule+0x29/0x70
[ 240.348568] [<ffffffffa0a0b555>] btrfs_commit_transaction+0x2a5/0xbe0 [btrfs]
[ 240.348573] [<ffffffff810b4380>] ? wait_woken+0x90/0x90
[ 240.348590] [<ffffffffa0a06fc5>] transaction_kthread+0x1d5/0x240 [btrfs]
[ 240.348605] [<ffffffffa0a06df0>] ? btrfs_cleanup_transaction+0x5a0/0x5a0 [btrfs]
[ 240.348611] [<ffffffff81091748>] kthread+0xd8/0xf0
[ 240.348617] [<ffffffff81091670>] ? kthread_create_on_node+0x1c0/0x1c0
[ 240.348624] [<ffffffff81562758>] ret_from_fork+0x58/0x90
[ 240.348629] [<ffffffff81091670>] ? kthread_create_on_node+0x1c0/0x1c0
Last edited by ouroboros8 (2015-04-02 12:37:25)

IMac won't boot anymore after power cut

Thanks to the great storms in New Jersey, my iMac does not boot anymore after a power cut. Does not get past the apple logo screen with the spinning wheel and keeps rebooting every 2 minutes.
I was able to mount the HD via Firewire on a host machine and the disk seemed fine.
I booted from the Install disk and ran Disk Utility - seemed fine though I could not verify the disk permissions ?
One other thing - I seemed to remember the white light (front bottom right) was blinking before during start-up. Now it goes and stays black after couple of seconds.
Help please,
Philippe

HI Phillipe and Welcome to Apple Discussions...
If you haven't done so, try running the Apple Hardware Test.
http://support.apple.com/kb/HT1509
I doubt repairing disk permissions can't help this problem. It sounds like a hardware issue.
*"I booted from the Install disk and ran Disk Utility - seemed fine though I could not verify the disk permissions ?"*
When you ran Disk Utility via Firewire, did you actually Verify the hard disk for errors?
Carolyn

My MBP won't boot anymore after "repair disk" and "repair disk permission"

My 2011 MBP 15 with Lion stopped working after I attempted to use Disk Utility to "repair disk" and "repair disk permission".
It was having weird issues before I attempted the repairs, it was freezing every few seconds no matter what I am doing, the whole thing would freeze with only the mouse movable. then after a few seconds it goes back to normal again. This happened after I downloaded and installed some updates from Apple. I don't know if the updates would cause this or it's something else.
In Disk Utility, "Repair Disk Permission" took 5 hours. While "Repair Disk" resulted in "Disk utility can't repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed up files".
Now when it boots, there's a loading bar under the Apple logo, it loads half way and shuts down itself.
I can still get into CMD+R Utilities though.
Any idea how I can extract the data out of the disk? I'm going to format and do a clean install.

mike2016 wrote:
This happened after I downloaded and installed some updates from Apple. I don't know if the updates would cause this or it's something else. Now when it boots, there's a loading bar under the Apple logo, it loads half way and shuts down itself.
A stopped loading bar is indicative of a failed firmware install that didn't complete, it's trying to install and is failing.
Do a PRAM reset
https://support.apple.com/kb/HT1379
Reboot into Safe Mode, (shift key down) then reboot normally and see if that fixes the issue.
https://support.apple.com/kb/TS2570
You may have to try to reinstall your firmware manually, you'll need another disk burning Mac
Find your exact firmware(s) here (or on Apple Downloads page)
https://support.apple.com/kb/HT1237
Apply instructions here
https://support.apple.com/kb/HT2213
Lastly it could be your boot drive is failing or something wrong happened with the update and accounting for all the to the other issues.
A OS X "overwrite" may solve the issue, may not.
See 10.5, 106. 10.7 OS X "overwrite" here
https://discussions.apple.com/message/16276201#16276201

Sol10 won't boot anymore after patching

Hi,
I tried patching (Recommended patches of 1/1/2008) an old Netra T1 running Sol10 while running in multi-user mode (yes, I'm that stupid). Unfortunately when I rebooted the server it won't come up again all I get is:
Netra T1 200 (UltraSPARC-IIe 500MHz), No Keyboard
OpenBoot 4.0, 512 MB memory installed, Serial #51796331.
Ethernet address 0:3:ba:16:59:6b, Host ID: 8316596b.
Executing last command: boot disk
Boot device: /pci@1f,0/pci@1/scsi@8/disk@0,0 File and args:
SunOS Release 5.10 Version Generic_127111-05 64-bit
Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
/kernel/fs/sparcv9/specfs: undefined symbol 'stralloctty'
WARNING: mod_load: cannot load module 'specfs'
(Can't load specfs) Program terminated
ok
Trying a 'boot disk -s' or 'boot disk -r' doesn't make any difference.
Unfortunately the server is located in another country so booting from cdrom is not an option. I only have serial and network access (limited by a firewall that I don't control so remote booting is not an option either).
Anybody any idea how I can boot my server?
Thanks in advance,
Nico

I think a call to Sun is in order... however I do have a long shot you could try (at your own risk or course :) )
I checked a Solaris 10 system and confirmed that stralloctty is used by specfs (sparcv9)
I then check the 32-bit version on specfs and it doesn't use stralloctty...
You could trying booting the server in 32-bit mode instead of 64-bit while this wont solve the problem is may let you boot so you can fix it....
"........To get the image to install switch the machine to 32bit mode (not supported for newer machines). To set the mode, halt the machine and at the ok prompt type setenv boot-file kernel/unix
To change the machine back to 64bit mode type the following at the ok prompt: setenv boot-file kernel/sparcv9/unix........"
NOTE: I have not ever tried this so I would test it on a machine you have locally first!!!
BTW: I don't think patching in multi user is stupid, I think if you do it (and I do) you need to quiesce the system and make sure you have a backout plan e.g. detached mirror.
I am guessing something went amiss in the patching and the kernel is stuffed i.e. half applied patch

Powermac G5 1.8Ghz June 2004 won't boot anymore

Hi all,
Past week i've bought a second hand PM G5. At first it seems to be all ok, but right now its not working anymore.
I've managed to install the OSX on the first evening i've had the PM G5. After installing evrything seemed to be fine. But after 30 minutes surfing on the internet, it froze. I had to give it an hard reset by holding down the power button.
After turning it of, it won't boot anymore. after a few times trying with 10 secconds between it, i unpluged the powercabel for 2 minutes. Wile turning it on after 2 minutes, it was booting , but it stopped booting after 1,5 minute and froze.. after hard resetting it, i've managed to boot it right. The OS seemed to be ok again, but after 5 till 10 minutes it froze again.
Right now it won't boot anymore... it starts (without the front light, this light only blinks fast once i turn it on, but after that no more. Sometimes it won''t even flash.
I've been buzzy replacing some components to get to know if it was a hardware fail. I've first replaced the PSU with two other PSU's from the PM G5, but won't do a thing.
The i've replaced the memory with 4 kind of difrent pairs, but won't do a thing either. At last i replaced the Logic Board, this won't even do a thing about it.
Of course i replaced the PRAM battery first, but also this won't help me.
I've tested it in AHT, but evrything was working well, according to AHT. I've managed to get the system log, but nothing scarry though here also, only some 122 errors some times. (download the system log here: http://www.mijnbestand.nl/Bestand-F4DDN66WLRCI.log )
I've reset al things possible like PRAM reset, PMU reset. Nothing seem to be working.
What can i do next to get this thing work?? I'm getting nut's here..
Please help..
Thanks a Lot
MArtijn Snoek

Hi martijnsnoek, and a warm welcome to the forums!
Can you count the beeps or flashes?
1 beep = no RAM installed
2 beeps = incompatible RAM types
3 beeps = no good banks
4 beeps = no good boot images in the boot ROM (and/or bad sys config block)
5 beeps = processor is not usable
In addition to the beeps, on some computers the power LED will flash a corresponding number of times plus one. The LED will repeat the sequence after approximately a 5-second pause. The tones are only played once.
Note: In this case, a flash is considered to be 1/4 second or 250 ms or greater in length.
http://support.apple.com/kb/HT1547
So, with the info you given, two things come to mind...
Bad solder joints around the RAM slots, try heating that area with a Hair Dryer for 3 to 5 minutes, then see if it starts.
If you can get it running, Get Temperature Monitor to see if it's heat related...
http://www.macupdate.com/info.php/id/12381/temperature-monitor
And/or iStat Pro...
http://www.islayer.com/apps/istatpro/
If you have any temps in the 70°C/160°F range, that's likely it.
BTW, have you blown the dust out of it since you got it?

Won't boot anymore but in safe mode

My laptop won't boot anymore. I get a gray screen with a prohibition sign. Here's what I found so far:
If I boot in the verbose mode it gets stuck on something like Looking for boot device.
I zapped the PRAM. Didn't help.
I can boot in safe mode.
I used Disk Utility to check the drive and permisions. Everything ok.
I can't boot from the original Snow Leopard DVD. I press C, the drive spins then stops.
I reinstalled Snow Leopard from the safe mode. Didn't help.
In safe mode Safari is crazy slow. Firefox runs full speed.
Any idea?

Reinstall OS X without erasing the drive
Do the following:
1. Repair the Hard Drive and Permissions
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. 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 installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
2. Reinstall Snow Leopard
If the drive is OK then quit DU and return to the installer. Proceed with reinstalling OS X. Note that the Snow Leopard installer will not erase your drive or disturb your files. After installing a fresh copy of OS X the installer will move your Home folder, third-party applications, support items, and network preferences into the newly installed system.
Download and install the Combo Updater for the version you prefer from support.apple.com/downloads/.
Unless you can boot from your installer DVD there's nothing you can do to reinstall OS X, so I'm not sure how you did reinstall as you said.
Booting From An OS X Installer Disc
1. Insert OS X Installer Disc into the optical drive.
2. Restart the computer.
3. Immediately after the chime press and hold down the "C" key.
4. Release the key when the spinning gear below the dark gray Apple logo appears.
5. Wait for installer to finish loading.

Re: Satellite C850 won't boot anymore - broken HDD

Hello Folks,
I bought a *Toshiba Satellite C850 - 1F2* with *+Windows 8+*.
After installing, upgrading to *+Windows 8.1+* and setting up everything, the whole machine worked pretty fine.
BUT since yesterday the laptop won't boot anymore!
When I turn it on, the HDD makes click and click and the system tries to boot from DVD, from USB, from HDD, from IPV4, from IPV6 and then it says, that there is no bootable device.
Unfortunately I wanted to make the +Windows 8 Restoration-/Rescue-DVDs+ this weekend!
Huh!!!
Well, I still have an *+original Windows-7-DVD and license+*, which would be good as well (I used it the last years).
*YET*, I cannot install *+Windows 7+*.
It says something like that, that +this system is not available for Secure Boot+.
I read about "Secure Boot".
So I pressed F2, turned the laptop on and could with this reach the BIOS.
It is a *+InsydeH20 Rev. 3.7+*.
*BUT*, when I go to "Boot Mode" I can only see, that this option is greyed and I cannot change from +UEFI Boot+ to +CSM Boot+.
Even the change of the HDD made no difference.
I put in my old HDD with Windows 7 installed (wich works in the other laptop), but the system won't boot, for it is +not suitable for Secure Boot+.
*So, WHAT NOW?*
I mean, it cannot really be the Toshiba politics, that you need to throw away your laptop, if the HDD breaks, can it?
For I didn't create the Rescue-DVD, I have just my Windows 7 DVD and another HDD with installed Windows 7.
Do I need to buy another Windows 8 licence and another HDD, to install Windows 8 (suitable for Secure Boot) again?
Would it even work like that?
Or is there any chance to upgrade the BIOS, for that I can then change from UEFI Boot to CSM Boot?
Or is there any other chance, to use my other HDD with Windows 7, or at least a new clean HDD, on wich I then can install my Windows 7 OS?
I hope, that someone can give me any good advice, what to do now ... without throwing the Toshiba laptop away ;)
Thanks in advance!

If the HDD died, in needs to be replaced.
If notebook is still covered by warranty, the HDD will be replaced free of charge. If warranty isnt valid, you will need to pay for the new HDD.
I think this understandable.
_Now some facts about the Recovery disk._
If you did not create a recovery disk in the past, you could order the recovery medium on this page: http://backupmedia.toshiba.eu/landing.aspx
The recovery disk would install the Toshiba image and would set the notebook back to the same state like at the first day of purchase.
_Regarding the Win 7 installation:_
Usually to install the non UEFI capable system, the secure boot needs to be disabled and boot mode needs to be set to CSM mode.
If this isnt possible you should update the BIOS but to do that you need an running Windows system (Win 8).

Mac mini won't boot anymore

My Mac mini won't boot anymore. It's been running fine for months.
It's running Leopard Server 10.5.2 Build 9C31
It starts to boot, I get the first spinning gear with the gray screen, then the blue desktop blinks, then a second spinning gear on a gray screen and it appears to hang (the gear stops spinning).
I booted off the install DVD, ran disk utility, repaired the HD, repaired the permissions: the behavior is the same.
Safe mode doesn't work (same hang as above).
Single user mode does work.
I can connect to it via Server Admin while it appears hung.
The last few lines of the system log are:
May 15 18:38:58 server emond[67]: SetUpLogs: uid = 0 gid = 0
May 15 18:38:58 server emond[67]: SetUpLogs: opening /Library/Logs/EventMonitor/EventMonitor.error.log
May 15 18:38:59 server kextd[23]: writing kernel link data to /var/run/mach.sym
May 15 18:39:09 server KernelEventAgent[59]: tid 00000000 received unknown event (12)
May 15 18:39:20 server kernel[0]: display: Not usable
May 15 18:39:20 server com.apple.KerberosAutoConfig[126]: Kerberos configuration is up to date
May 15 18:39:20 server com.apple.ATSServer[125]: FODBCheck: New annex file created
May 15 18:39:21 server ARDAgent [130]: ******ARDAgent Launched******
May 15 18:39:21 server com.apple.KerberosAutoConfig[132]: Kerberos configuration is up to date
May 15 18:39:22 server ARDAgent [130]: call logout from LoginLogoutProxyCallBackFunction
May 15 18:39:22 server com.apple.launchd[1] (com.apple.RemoteDesktop.agent): Throttling respawn: Will start in 9 seconds
May 15 18:39:24 server loginwindow[58]: Login Window Started Security Agent
May 15 18:39:29 server servermgrd[53]: servermgr_calendar: created default calendar virtual host
May 15 18:39:31 server ARDAgent [146]: ******ARDAgent Launched******
May 15 18:39:32 server ARDAgent [146]: ******ARDAgent Ready******
May 15 18:39:33 server mdworker[109]: (Error) SyncInfo: Boot-cache avoidance timed out!
May 15 18:39:54 server Python[47]: CGImageSourceCreateWithData data parameter is nil
May 15 18:39:54 server com.apple.wikid[47]: Thu May 15 18:39:54 server.jeff.carpenter.name Python[47] <Error>: CGImageSourceCreateWithData data parameter is nil\n
May 15 18:39:56 server kernel[0]: AppleYukon2 - bad packet received. length: 1440, packet status bits: MII error
May 15 18:39:56 server kernel[0]: AppleYukon2: 00000000,00000001 sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket tried N times
May 15 18:49:54 server kernel[0]: serialnumberd 194 FSWRITEDATA SBF /dev/dtracehelper 13 (seatbelt)
May 15 18:49:54 server kernel[0]: serialnumberd 194 FSREADDATA SBF /dev/autofs_nowait 13 (seatbelt)
May 15 18:49:54 server kernel[0]: serialnumberd 194 FSREADDATA SBF /usr/sbin 13 (seatbelt)
May 15 18:55:12 server kernel[0]: AppleYukon2 - bad packet received. length: 23, packet status bits: MII error
Any ideas?

Yes, it's been running Server since I purchased it.
I doubt the serial number is in use elsewhere: I purchased the 10-user version at a retail store in a sealed package and I've only installed it once.

My 2006 iMac running Snow Leopard won't boot even after erasing and re-installing Snow Leopard (via my MacBookPro), either from the HD or DVD drive. Can't get it to run Hardware Test. Disk Utility says disk OK - files are there. What can I do?

My 2006 iMac running Snow Leopard won't boot even after erasing and re-installing Snow Leopard. I erased and re-installed by putting the iMac in Target Disk mode and usin my MacBookPro as the host. But after numerous attempts I still can't get it to boot either from the HD or DVD drive. I just get the white screen after the wheel stops spinning. I can't get it to run Hardware Test - just get the white screen. If I use Disk Utility via my MBP it says the disk appears OK. All the Snow Leopad files appear to have been installed. What can I do?

Hi-NRG Bwoy wrote:
I erased and re-installed by putting the iMac in Target Disk mode and using my MacBookPro as the host.
Reet the SMC and the PRAM
 Cheat sheet to help diagnose and fix your Mac
Perhaps you installed the wrong version OS X onto the iMac, you can't use the disk from another Mac.
clean the disk.
If it's not working then use this method to create a bootable 10.6 USB from the iMac machine specific 10.6 disk or the 10.6.3 retail disk on your other Mac, use it to boot the iMac with.
http://www.maciverse.com/install-os-x-snow-leopard-from-usb-flash-drive.html
How to erase and install Snow Leopard 10.6

Macbook pro won't boot up after installing a Micro Trend security.

Macbook pro 13" unibody non-retina won't boot up after installing a Micro Trend security.
Please Help Thanks!

Boot to safe mode and uninstall Micro Trend from there.
http://esupport.trendmicro.co.jp/Pages/JP-2075680.aspx

Mac OSx won't boot up after update to 10.6.7?

Mac OSx won't boot up after update to 10.6.7?

Hi Mike
This is called a kernel panic, similar to s 'blue screen of death' on Windows. When you say you reinstalled 3 times, do you mean the OS or the Update?
When does this kernel panic appear? You may have a hardware issue if it's happening on boot.
Taylor

Satellite L40 18P won't boot anymore

Hello folks,
my Satellite L40 18P won't boot anymore. All I get is the Power LED to go green. The DVD ROM drive blinks and I can open and close it - but that's it. Nothing else happens.
Any idea in the forum what I can do to get the notebook boot again ? Or please ask questions for additional details.
many thanks, Johi 13

Hi,
wow, that was fast.
No, I can't see anything - the screen stays black. I do not hear the HDD start, neither do I hear the fan.
This behavior appeard for the first time yesterday evening.
Last activity was (if I remember correctly) closing the lid and sending the notebook to standby.
So far, I haven't tested it with an external monitor.
thanks, Johi13

SRW248G4P switch won't boot anymore

I have a Linksys Cisco Small Business switch model SRW248G4P which won't boot anymore. This is what I see with Putty when it boots (console interface):
Image Loader 1.0.1
Loading Diagnostic Image File : SRW224G4P_SRW248G4P_boot.bix
Diagnostic 1.0.1
in
The boot file seems to be the problem.
Does anyone have a solution for this problem? Some kind of hardware reset?
Kind regards
(I know it is not officially supported anymore, but I am still looking for some help)

Hi Aleksandra,
Thank you for your reply. By pressing Crtl+u rapidly while booting I managed to get in the download/xmodem menu.
Output:
Image Loader 1.0.1
File Name                         S/Up Type Size       Create Time
$logfile_1                          0    3         64 1193046:28:15
Factory_Default_Config.cfg          0    5        354 24:01:02
SRW224G4P_SRW248G4P_boot.bix        1    1    1377600 00:01:03
SRW224G4P_SRW248G4P_image.bix       1    2    3517532 00:03:42
certificate                         0    8      18040 24:00:55
startup-config                      1    5       5596 25:40:57
startup1.cfg                        0    5       5537 24:01:14
Free Space : 2097152
[X]modem Download [D]elete File [S]et Startup File
[Q]uit
Select>
Which image should I send to the switch?
The image provided by the official support page:
http://software.cisco.com/download/type.html?mdfid=282414078&flowid=3659
(version 1.0.2 or version 1.3.1)
Or the image referred to by vasukris (Moorthy) (above) (version 1.2.3 or version 1.2.2b)
Considering the advice of Tom Watts
( https://supportforums.cisco.com/discussion/11733231/srw248g4p-loader-binary-checksum-error-runtime-loading-fail-system-halt )
"1.2.2a is 1.0.6 boot code.
1.2.2b is 1.0.1 boot code.
1.2.3.0 is 1.0.2 boot code
It looks like you're using 1.0.1 boot code so the 1.2.2b firmware should be for you."
Thank you in advance!

Can't get into my DE anymore after nvidia/nouveau switch + other stuff

I made a mess of things, and I'd very much like to get my system back into a normal state. Here's a brief history of important events:
(1) About 2 weeks ago after a system update, I couldn't log into Gnome via GDM anymore (see topic). Thankfully I could still get into Gnome via 'startx', so I stuck with that for a while. Busy time, and no real fix was forthcoming.
(2) About 4 days ago after a system update, that didn't work anymore either. (Both monitors would just stay black, but with a thick white bar on the left side of the right monitor.)
(3) I switched from binary nvidia drivers to nouveau, in the hope that that would fix things. It did, sort of. I could use startx again, but my display would now freeze after a short time of use, with many nouveau related errors in dmesg. My bug report to freedesktop.org about this is most comprehensive.
I really need a functional PC right now. Short of an actual fix, I'd love to just roll back everything to the state it was a month ago or so. But no luck there either.
(4) I installed the nvidia drivers again, uninstalled the nouveau stuff, set my system to query the Arch Rollback Machine for a month ago, and did a `pacman -Syyuu --force`. GDM still doesn't work, nor does startx. Using startx, I get the following 'Xorg.0.log' (I remember getting the same errors during my earlier messing about):
[ 40.414]
X.Org X Server 1.17.1
Release Date: 2015-02-10
[ 40.414] X Protocol Version 11, Revision 0
[ 40.414] Build Operating System: Linux 3.18.6-1-ARCH x86_64
[ 40.414] Current Operating System: Linux mhelvens-pc 3.19.3-3-ARCH #1 SMP PREEMPT Wed Apr 8 14:10:00 CEST 2015 x86_64
[ 40.414] Kernel command line: initrd=\initramfs-linux.img rw root=/dev/disk/by-label/root resume=/dev/disk/by-label/swap usbhid.quirks=0x1B1C:0x1B13:0x20000000
[ 40.414] Build Date: 14 March 2015 06:45:50PM
[ 40.414]
[ 40.414] Current version of pixman: 0.32.6
[ 40.414] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 40.414] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 40.414] (==) Log file: "/var/log/Xorg.0.log", Time: Sat May 16 21:19:34 2015
[ 40.414] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 40.414] (==) No Layout section. Using the first Screen section.
[ 40.414] (==) No screen section available. Using defaults.
[ 40.414] (**) |-->Screen "Default Screen Section" (0)
[ 40.414] (**) | |-->Monitor "<default monitor>"
[ 40.414] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 40.414] (==) Automatically adding devices
[ 40.414] (==) Automatically enabling devices
[ 40.414] (==) Automatically adding GPU devices
[ 40.414] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 40.414] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 40.414] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 40.414] (II) Loader magic: 0x815d80
[ 40.414] (II) Module ABI versions:
[ 40.414] X.Org ANSI C Emulation: 0.4
[ 40.414] X.Org Video Driver: 19.0
[ 40.414] X.Org XInput driver : 21.0
[ 40.414] X.Org Server Extension : 9.0
[ 40.415] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c11
[ 40.415] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 40.416] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 8 paused 0
[ 40.416] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 40.416] (II) systemd-logind: got fd for /dev/dri/card1 226:1 fd 9 paused 0
[ 40.417] (--) PCI: (0:0:2:0) 8086:0412:1462:7930 rev 6, Mem @ 0xf7400000/4194304, 0xd0000000/268435456, I/O @ 0x0000f000/64
[ 40.417] (--) PCI:*(0:1:0:0) 10de:1184:1462:2990 rev 161, Mem @ 0xf6000000/16777216, 0xe0000000/134217728, 0xe8000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 40.417] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 40.417] (II) LoadModule: "glx"
[ 40.417] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 40.421] (II) Module glx: vendor="NVIDIA Corporation"
[ 40.422] compiled for 4.0.2, module version = 1.0.0
[ 40.422] Module class: X.Org Server Extension
[ 40.422] (II) NVIDIA GLX Module 346.59 Tue Mar 31 13:38:58 PDT 2015
[ 40.422] (II) Applying OutputClass "nvidia" to /dev/dri/card0
[ 40.422] loading driver: nvidia
[ 40.422] (==) Matched nvidia as autoconfigured driver 0
[ 40.422] (==) Matched nouveau as autoconfigured driver 1
[ 40.422] (==) Matched nv as autoconfigured driver 2
[ 40.422] (==) Matched intel as autoconfigured driver 3
[ 40.422] (==) Matched nouveau as autoconfigured driver 4
[ 40.422] (==) Matched nv as autoconfigured driver 5
[ 40.422] (==) Matched modesetting as autoconfigured driver 6
[ 40.422] (==) Matched fbdev as autoconfigured driver 7
[ 40.422] (==) Matched vesa as autoconfigured driver 8
[ 40.422] (==) Assigned the driver to the xf86ConfigLayout
[ 40.422] (II) LoadModule: "nvidia"
[ 40.422] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 40.422] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 40.422] compiled for 4.0.2, module version = 1.0.0
[ 40.422] Module class: X.Org Video Driver
[ 40.422] (II) LoadModule: "nouveau"
[ 40.422] (WW) Warning, couldn't open module nouveau
[ 40.422] (II) UnloadModule: "nouveau"
[ 40.422] (II) Unloading nouveau
[ 40.422] (EE) Failed to load module "nouveau" (module does not exist, 0)
[ 40.422] (II) LoadModule: "nv"
[ 40.422] (WW) Warning, couldn't open module nv
[ 40.422] (II) UnloadModule: "nv"
[ 40.422] (II) Unloading nv
[ 40.422] (EE) Failed to load module "nv" (module does not exist, 0)
[ 40.422] (II) LoadModule: "intel"
[ 40.422] (WW) Warning, couldn't open module intel
[ 40.422] (II) UnloadModule: "intel"
[ 40.422] (II) Unloading intel
[ 40.422] (EE) Failed to load module "intel" (module does not exist, 0)
[ 40.422] (II) LoadModule: "modesetting"
[ 40.422] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 40.422] (II) Module modesetting: vendor="X.Org Foundation"
[ 40.422] compiled for 1.17.1, module version = 1.17.1
[ 40.422] Module class: X.Org Video Driver
[ 40.422] ABI class: X.Org Video Driver, version 19.0
[ 40.422] (II) LoadModule: "fbdev"
[ 40.422] (WW) Warning, couldn't open module fbdev
[ 40.422] (II) UnloadModule: "fbdev"
[ 40.422] (II) Unloading fbdev
[ 40.422] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 40.422] (II) LoadModule: "vesa"
[ 40.422] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 40.422] (II) Module vesa: vendor="X.Org Foundation"
[ 40.422] compiled for 1.17.0, module version = 2.3.2
[ 40.422] Module class: X.Org Video Driver
[ 40.422] ABI class: X.Org Video Driver, version 19.0
[ 40.422] (II) NVIDIA dlloader X Driver 346.59 Tue Mar 31 13:17:41 PDT 2015
[ 40.422] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 40.422] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 40.422] (II) VESA: driver for VESA chipsets: vesa
[ 40.422] (++) using VT number 2
[ 40.422] (--) controlling tty is VT number 2, auto-enabling KeepTty
[ 40.422] (II) Loading sub module "fb"
[ 40.422] (II) LoadModule: "fb"
[ 40.423] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 40.423] (II) Module fb: vendor="X.Org Foundation"
[ 40.423] compiled for 1.17.1, module version = 1.0.0
[ 40.423] ABI class: X.Org ANSI C Emulation, version 0.4
[ 40.423] (II) Loading sub module "wfb"
[ 40.423] (II) LoadModule: "wfb"
[ 40.423] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 40.423] (II) Module wfb: vendor="X.Org Foundation"
[ 40.423] compiled for 1.17.1, module version = 1.0.0
[ 40.423] ABI class: X.Org ANSI C Emulation, version 0.4
[ 40.423] (II) Loading sub module "ramdac"
[ 40.423] (II) LoadModule: "ramdac"
[ 40.423] (II) Module "ramdac" already built-in
[ 40.423] (II) modeset(G0): using drv /dev/dri/card1
[ 40.423] (WW) Falling back to old probe method for modesetting
[ 40.423] (WW) Falling back to old probe method for vesa
[ 40.423] (II) NVIDIA(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 40.423] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 40.423] (==) NVIDIA(0): RGB weight 888
[ 40.423] (==) NVIDIA(0): Default visual is TrueColor
[ 40.423] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 40.423] (**) NVIDIA(0): Enabling 2D acceleration
[ 40.770] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20150116)
[ 40.771] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 770 (GK104) at PCI:1:0:0 (GPU-0)
[ 40.771] (--) NVIDIA(0): Memory: 2097152 kBytes
[ 40.771] (--) NVIDIA(0): VideoBIOS: 80.04.c3.00.00
[ 40.771] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 40.779] (--) NVIDIA(0): Valid display device(s) on GeForce GTX 770 at PCI:1:0:0
[ 40.779] (--) NVIDIA(0): CRT-0
[ 40.779] (--) NVIDIA(0): DELL U2713HM (DFP-0) (boot, connected)
[ 40.779] (--) NVIDIA(0): SHARP HDMI (DFP-1) (connected)
[ 40.779] (--) NVIDIA(0): DFP-2
[ 40.779] (--) NVIDIA(0): DELL U2713HM (DFP-3) (connected)
[ 40.779] (--) NVIDIA(0): DFP-4
[ 40.779] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
[ 40.779] (--) NVIDIA(0): DELL U2713HM (DFP-0): Internal TMDS
[ 40.779] (--) NVIDIA(GPU-0): DELL U2713HM (DFP-0): 330.0 MHz maximum pixel clock
[ 40.779] (--) NVIDIA(0): SHARP HDMI (DFP-1): Internal TMDS
[ 40.779] (--) NVIDIA(GPU-0): SHARP HDMI (DFP-1): 340.0 MHz maximum pixel clock
[ 40.779] (--) NVIDIA(0): DFP-2: Internal TMDS
[ 40.779] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[ 40.779] (--) NVIDIA(0): DELL U2713HM (DFP-3): Internal TMDS
[ 40.779] (--) NVIDIA(GPU-0): DELL U2713HM (DFP-3): 330.0 MHz maximum pixel clock
[ 40.779] (--) NVIDIA(0): DFP-4: Internal DisplayPort
[ 40.779] (--) NVIDIA(GPU-0): DFP-4: 960.0 MHz maximum pixel clock
[ 40.779] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 40.779] (**) NVIDIA(0): device DELL U2713HM (DFP-0) (Using EDID frequencies has
[ 40.779] (**) NVIDIA(0): been enabled on all display devices.)
[ 40.780] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 40.780] (**) NVIDIA(0): device SHARP HDMI (DFP-1) (Using EDID frequencies has been
[ 40.780] (**) NVIDIA(0): enabled on all display devices.)
[ 40.781] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 40.781] (**) NVIDIA(0): device DELL U2713HM (DFP-3) (Using EDID frequencies has
[ 40.781] (**) NVIDIA(0): been enabled on all display devices.)
[ 40.782] (==) NVIDIA(0):
[ 40.782] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 40.782] (==) NVIDIA(0): will be used as the requested mode.
[ 40.782] (==) NVIDIA(0):
[ 40.782] (II) NVIDIA(0): Validated MetaModes:
[ 40.782] (II) NVIDIA(0):
[ 40.782] (II) NVIDIA(0): "DFP-0:nvidia-auto-select,DFP-1:nvidia-auto-select,DFP-3:nvidia-auto-select"
[ 40.782] (II) NVIDIA(0): Virtual screen size determined to be 7040 x 1440
[ 40.816] (--) NVIDIA(0): DPI set to (108, 107); computed from "UseEdidDpi" X config
[ 40.816] (--) NVIDIA(0): option
[ 40.816] (==) modeset(G0): Depth 24, (==) framebuffer bpp 32
[ 40.816] (==) modeset(G0): RGB weight 888
[ 40.816] (==) modeset(G0): Default visual is TrueColor
[ 40.816] (II) Loading sub module "glamoregl"
[ 40.816] (II) LoadModule: "glamoregl"
[ 40.816] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[ 40.818] (II) Module glamoregl: vendor="X.Org Foundation"
[ 40.818] compiled for 1.17.1, module version = 1.0.0
[ 40.818] ABI class: X.Org ANSI C Emulation, version 0.4
[ 40.818] (II) glamor: OpenGL accelerated X.org driver based.
[ 40.830] (EE)
[ 40.830] (EE) Backtrace:
[ 40.830] (EE) 0: /usr/lib/xorg-server/Xorg (OsLookupColor+0x119) [0x5949c9]
[ 40.830] (EE) 1: /usr/lib/libc.so.6 (__restore_rt+0x0) [0x7f1989d2053f]
[ 40.830] (EE) 2: /usr/lib/libX11.so.6 (_XSend+0x2b) [0x7f197fa6301b]
[ 40.830] (EE) 3: /usr/lib/libX11.so.6 (_XFlush+0x15) [0x7f197fa634d5]
[ 40.830] (EE) 4: /usr/lib/libX11.so.6 (_XGetRequest+0x55) [0x7f197fa65fa5]
[ 40.830] (EE) 5: /usr/lib/libX11.so.6 (XQueryExtension+0x4d) [0x7f197fa5955d]
[ 40.830] (EE) 6: /usr/lib/libX11.so.6 (XInitExtension+0x32) [0x7f197fa4d352]
[ 40.831] (EE) 7: /usr/lib/libXext.so.6 (XextAddDisplay+0x4f) [0x7f197f81c38f]
[ 40.831] (EE) 8: /usr/lib/libnvidia-glsi.so.346.59 (_nv016glsi+0x5f467) [0x7f197fe254b7]
[ 40.831] (EE) 9: /usr/lib/libnvidia-glsi.so.346.59 (_nv016glsi+0x804) [0x7f197fd67bf4]
[ 40.831] (EE) unw_get_proc_name failed: no unwind info found [-10]
[ 40.831] (EE) 10: /usr/lib/libEGL.so.1 (?+0x804) [0x7f1980010ef4]
[ 40.831] (EE) unw_get_proc_name failed: no unwind info found [-10]
[ 40.831] (EE) 11: /usr/lib/libEGL.so.1 (?+0x804) [0x7f1980011924]
[ 40.831] (EE) 12: /usr/lib/libEGL.so.1 (NvEglRegClientApi+0x4f36) [0x7f198001e866]
[ 40.831] (EE) 13: /usr/lib/xorg/modules/libglamoregl.so (glamor_egl_init+0x99) [0x7f1982557539]
[ 40.831] (EE) 14: /usr/lib/xorg/modules/drivers/modesetting_drv.so (_init+0x29ce) [0x7f1982df6e9e]
[ 40.831] (EE) 15: /usr/lib/xorg-server/Xorg (InitOutput+0xbcc) [0x47b63c]
[ 40.831] (EE) 16: /usr/lib/xorg-server/Xorg (remove_fs_handlers+0x22a) [0x43c9da]
[ 40.831] (EE) 17: /usr/lib/libc.so.6 (__libc_start_main+0xf0) [0x7f1989d0d800]
[ 40.831] (EE) 18: /usr/lib/xorg-server/Xorg (_start+0x29) [0x427039]
[ 40.832] (EE) 19: ? (?+0x29) [0x29]
[ 40.832] (EE)
[ 40.832] (EE) Segmentation fault at address 0x0
[ 40.832] (EE)
Fatal server error:
[ 40.832] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 40.832] (EE)
[ 40.832] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 40.832] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 40.832] (EE)
[ 40.832] (EE) Server terminated with error (1). Closing log file.
A (virtual) beer to whomever can help me out of this jam!
Please let me know what additional info I should provide.

Malkymder wrote:
Glad to hear it is a step forward ...
can you try with another Display manager like lightdm see if that works ?
I might try that, though now that I finally have my PC back I have some other work that takes priority for a few days. :-)
Malkymder wrote:And yes xorg.conf should be replaced with /etc/xorg.conf.d/20-nvidia.conf instead
I'm using `nvidia-xconfig` to generate that file (I haven't had to tinker with it manually for years now).
The tool generates this 'deprecated' file. Should I just move its exact content to the new location?

Won't boot anymore after nvidia-xconfig

Similar Messages

Maybe you are looking for