Dbus Daemon crashes during boot with ldap-client activ

Hello,
I just configured my ldap-client using this howto http://wiki.archlinux.org/index.php/HOW … entication. But when I restart the System, the dbus daemon hangs. It must have something to di with the /etc/nsswitch.conf. Wenn I change the settings to use ldap, I can't login anymore. As sone as I switch back to the old nsswitch.conf everything ist working. Can someone tell me how to get the ldap-client working together with dbus?
EDIT
I just looked in the logfile /var/log/daemon.log on the arch client. I found this:
Jun 6 11:21:07 stkaw kdm_greet[5967]: nss_ldap: reconnecting to LDAP server (sleeping 4 seconds)...
I looked in /var/log/messages of the ldap server:
Jun 6 11:21:07 fs1 slapd[6415]: conn=637 fd=34 ACCEPT from IP=192.168.123.3:58965 (IP=0.0.0.0:389)
Jun 6 11:21:07 fs1 slapd[6415]: conn=637 fd=34 closed
So the client seams to find the Server.
Last edited by stka (2007-06-06 09:28:56)

I found out what it is, but I don't understand it. The server is configured to use tls. All other clients use the clientoption "ssl start_tls" in /etc/nss_ldap.conf. On the new archlinux the ldapclient woun't work with tls. As sone as I deactrivate this option the client established the connection.:/

Similar Messages

2 month old iMac, crashes during boot

Yesterday I received an automatic software update. Today it crashes during boot up. This is what I see:
panic (cpu 0 caller 0x003AA827) Unable to find driver for this platform: "ACPI"
Debugger called: <panic> .... then it spits out a bunch of hex codes...
Darwin Kernel 8.9.1
Sigh...

The two hardware issues that come to mind are loose or unseated ram module(s) and resetting the SMC. There have been quite a few folks reporting an issue with a unseated ram module that reinstalling fixed.
http://docs.info.apple.com/article.html?artnum=303084
http://docs.info.apple.com/article.html?artnum=303446
There is a long list of issues related to firmware and software!
17" iMac Intel Core Duo 1.5GB Ram Mac OS X (10.4.9) Maxtor 300GB FireWire Creative Inspire 2.1 2G Nano

Crash during sleep with kernel messages

Two days in row now my Macbook Pro Retina crashed during my (long) commute in the car from work to home. It was put to sleep at about 17:10 and I opened it at around 19:30 and noticed immediately that I had crashed when seeing the initial login screen.
Checking the console logs I could see it woke up at around 18:20 and after several messages involving wifi and Calendar it starts outputting a massive amount (500) of kernel messages like the one's below. Does anyone have any idea what this could? Is this a hardware issue?
31/03/14 18:19:09,000 kernel[0]: [0x4402e1000, 0xf0b000]
31/03/14 18:19:09,000 kernel[0]: [0x714ad39000, 0xe5a000]
31/03/14 18:19:09,000 kernel[0]: [0x28fe22000, 0xe19000]
31/03/14 18:19:09,000 kernel[0]: [0x70b3409000, 0xdf6000]
31/03/14 18:19:09,000 kernel[0]: [0x70b8bc8000, 0xdec000]
31/03/14 18:19:09,000 kernel[0]: [0x712e3c7000, 0xd7f000]
31/03/14 18:19:09,000 kernel[0]: [0x73b0087000, 0xd63000]
After 500 suchs messages it finally ends with a reboot:
31/03/14 18:19:09,000 kernel[0]: [0x70d5aeb000, 0x2000]
31/03/14 18:19:09,000 kernel[0]: [0x70d5af7000, 0x1000]
31/03/14 18:19:09,000 kernel[0]: [0x70d5afd000, 0x1000]
31/03/14 18:19:09,000 kernel[0]: *** kernel exceeded 500 log message per second limit - remaining messages this second discarded ***
31/03/14 19:49:35,000 bootlog[0]: BOOT_TIME 1396288175 0
Before the long list of kernel messages I have the following logs, not sure if they can be of any help.
31/03/14 18:18:47,470 Calendar[338]: [com.apple.calendar.ui.log] [An error exists on principal: [Week Numbers]]
31/03/14 18:18:48,000 kernel[0]: IOPPF: Sent cpu-plimit-notification last value 27 (rounded time weighted average 27)
31/03/14 18:18:49,000 kernel[0]: IOPPF: Sent gpu-external-plimit-notification last value 0 (rounded time weighted average 10)
31/03/14 18:18:49,000 kernel[0]: IOPPF: Sent gpu-internal-plimit-notification last value 0 (rounded time weighted average 10)
31/03/14 18:18:50,077 mDNSResponder[55]: mDNSPlatformSourceAddrForDest: connect 213.211.144.65 failed errno 51 (Network is unreachable)
31/03/14 18:18:50,077 mDNSResponder[55]: mDNSPlatformSourceAddrForDest: connect 91.181.111.6 failed errno 51 (Network is unreachable)
31/03/14 18:19:00,957 AddressBookSourceSync[5096]: -[ABAddressBook save] failed. (<ABAddressBook: 0x7f871af06810>)
31/03/14 18:19:06,000 kernel[0]: AirPort_Brcm43xx::powerChange: System Sleep
31/03/14 18:19:08,000 kernel[0]: hibernate image path: /var/vm/sleepimage
31/03/14 18:19:08,000 kernel[0]: efi pagecount 63
31/03/14 18:19:08,000 kernel[0]: hibernate_page_list_setall(preflight 1) start 0xffffff82956fe000, 0xffffff8295a0b000
31/03/14 18:19:09,000 kernel[0]: hibernate_page_list_setall time: 324 ms
31/03/14 18:19:09,000 kernel[0]: pages 4098247, wire 1604474, act 508977, inact 56297, cleaned 0 spec 5, zf 423336, throt 0, compr 1106576, xpmapped 114574
31/03/14 18:19:09,000 kernel[0]: could discard act 1592 inact 200200 purgeable 193637 spec 3153 cleaned 0
31/03/14 18:19:09,000 kernel[0]: hibernate_page_list_setall preflight pageCount 1604474 est comp 56 setfile 3910287324 min 1073741824
31/03/14 18:19:09,000 kernel[0]: AppleThunderboltNHI::prePCIWake - power up complete - took 0 us
31/03/14 18:19:09,000 kernel[0]: AppleThunderboltHAL::earlyWake - complete - took 0 milliseconds
31/03/14 18:19:09,000 kernel[0]: Thunderbolt Self-Reset Count = 0xedefbe00
31/03/14 18:19:09,000 kernel[0]: IOThunderboltSwitch<0xffffff804fa74c00>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 0
31/03/14 18:19:09,000 kernel[0]: VNOP_ALLOCATE(0) 2836545536
31/03/14 18:19:09,000 kernel[0]: [0x4402e1000, 0xf0b000]
31/03/14 18:19:09,000 kernel[0]: [0x714ad39000, 0xe5a000]

Hello Cuypers,
It sounds like your computer is getting a Kernel Panic. I recommend the information in the following article, and the troubleshooting steps toward the bottom of it named:
OS X: When your computer spontaneously restarts or displays "Your computer restarted because of a problem."
http://support.apple.com/kb/TS4636
Preventing unexpected restarts
In most cases, kernel panics are not caused by an issue with the Mac itself. They are usually caused by software that was installed, or a problem with connected hardware.
To help avoid kernel panics, install all available software updates until Software Update reports, "Your software is up to date." OS X updates help your Mac handle the kinds of issues that can cause kernel panics, such as malformed network packets, or third party software issues. For most kernel panics, updating your software is all you have to do.
Thank you for using Apple Support Communities.
Regards,
Sterling

My iMac crashed during rester with a kernel panic. What is wrong with it?

Hi. My iMac purchaced last month crashed during restart and it issued me with a Kernel panic report. Is there something wrong with the machine?
The report reads as follow:
Interval Since Last Panic Report: 72215 sec
Panics Since Last Report:          1
Anonymous UUID:                    EE4EEBBB-4B06-DAC0-4F2C-6656F553115A
Sun Oct 6 18:37:36 2013
panic(cpu 1 caller 0xffffff8023ab8945): Kernel trap at 0x0000000000000000, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0x0000000000000000, CR3: 0x0000000039491031, CR4: 0x00000000001606e0
RAX: 0xffffff80395c4000, RBX: 0x0000000000000000, RCX: 0x0000000000000000, RDX: 0xffffff803872ec00
RSP: 0xffffff8116893a98, RBP: 0xffffff8116893ad0, RSI: 0xffffff80f6ca7b44, RDI: 0xffffff80395af800
R8: 0x0000000000000000, R9: 0xffffff8116893304, R10: 0xffffffffffffffff, R11: 0x00000000ffffffff
R12: 0xffffff8038328000, R13: 0x0000000000000000, R14: 0x0000000000000001, R15: 0xffffff8039598400
RFL: 0x0000000000010286, RIP: 0x0000000000000000, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x0000000000000000, Error code: 0x0000000000000010, Fault CPU: 0x1
Backtrace (CPU 1), Frame : Return Address
0xffffff8116893730 : 0xffffff8023a1d636
0xffffff81168937a0 : 0xffffff8023ab8945
0xffffff8116893970 : 0xffffff8023acebfd
0xffffff8116893990 : 0x0
0xffffff8116893ad0 : 0xffffff7fa51a46f1
0xffffff8116893b00 : 0xffffff7fa51802b3
0xffffff8116893b30 : 0xffffff7fa416b380
0xffffff8116893b70 : 0xffffff7fa416d75b
0xffffff8116893b90 : 0xffffff7fa4172b73
0xffffff8116893bc0 : 0xffffff8023e70b13
0xffffff8116893c20 : 0xffffff8023e6e74f
0xffffff8116893d70 : 0xffffff8023a98c21
0xffffff8116893e80 : 0xffffff8023a20b4d
0xffffff8116893eb0 : 0xffffff8023a10448
0xffffff8116893f00 : 0xffffff8023a1961b
0xffffff8116893f70 : 0xffffff8023aa6546
0xffffff8116893fb0 : 0xffffff8023acf473
      Kernel Extensions in backtrace:
         com.apple.iokit.IOGraphicsFamily(2.3.7)[9928306E-3508-3DBC-80A4-D8F1D87650D7]@0 xffffff7fa415f000->0xffffff7fa4196fff
            dependency: com.apple.iokit.IOPCIFamily(2.8)[2FAEA49C-EA4C-39C6-9203-FC022277A43C]@0xffffff 7fa411c000
         com.apple.GeForce(8.1.6)[0E3D8776-A5B7-3D82-9BFD-9188170B358D]@0xffffff7fa517c0 00->0xffffff7fa5249fff
            dependency: com.apple.NVDAResman(8.1.6)[EA4F9902-5AAE-3F1D-A846-3796221C8C91]@0xffffff7fa41 b6000
            dependency: com.apple.iokit.IONDRVSupport(2.3.7)[F16E015E-1ABE-3C40-AC71-BC54F4BE442E]@0xff ffff7fa41a2000
            dependency: com.apple.iokit.IOPCIFamily(2.8)[2FAEA49C-EA4C-39C6-9203-FC022277A43C]@0xffffff 7fa411c000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[9928306E-3508-3DBC-80A4-D8F1D87650D7]@0 xffffff7fa415f000
BSD process name corresponding to current thread: WindowServer
Mac OS version:
12F45
Kernel version:
Darwin Kernel Version 12.5.0: Sun Sep 29 13:33:47 PDT 2013; root:xnu-2050.48.12~1/RELEASE_X86_64
Kernel UUID: EA38B02E-2B88-309F-BA68-1DE29F605DD8
Kernel slide:     0x0000000023800000
Kernel text base: 0xffffff8023a00000
System model name: iMac13,2 (Mac-FC02E91DDD3FA6A4)
System uptime in nanoseconds: 19597183232
last loaded kext at 18740272837: com.apple.driver.AppleBluetoothMultitouch          75.19 (addr 0xffffff7fa5d42000, size 77824)
loaded kexts:
com.apple.driver.AppleBluetoothMultitouch          75.19
com.apple.iokit.IOBluetoothSerialManager          4.1.7f2
com.apple.driver.AppleHWSensor          1.9.5d0
com.apple.filesystems.autofs          3.0
com.apple.driver.AudioAUUC          1.60
com.apple.driver.X86PlatformShim          1.0.0
com.apple.driver.ApplePlatformEnabler          2.0.7d2
com.apple.driver.AGPM          100.13.12
com.apple.driver.AppleMikeyHIDDriver          124
com.apple.driver.AppleHDAHardwareConfigDriver          2.4.7fc4
com.apple.driver.AppleHDA          2.4.7fc4
com.apple.driver.AppleUpstreamUserClient          3.5.12
com.apple.iokit.IOBluetoothUSBDFU          4.1.7f2
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport          4.1.7f4
com.apple.GeForce          8.1.6
com.apple.driver.AppleMuxControl          3.4.5
com.apple.driver.AppleBacklight          170.3.5
com.apple.driver.AppleMCCSControl          1.1.11
com.apple.driver.AppleMikeyDriver          2.4.7fc4
com.apple.driver.AppleIntelHD4000Graphics          8.1.6
com.apple.driver.AppleSMCLMU          2.0.3d0
com.apple.driver.ACPI_SMC_PlatformPlugin          1.0.0
com.apple.iokit.IOUserEthernet          1.0.0d1
com.apple.Dont_Steal_Mac_OS_X          7.0.0
com.apple.driver.ApplePolicyControl          3.4.5
com.apple.driver.AppleLPC          1.6.3
com.apple.driver.AppleSMBusPCI          1.0.11d1
com.apple.driver.AppleIntelFramebufferCapri          8.1.6
com.apple.nvidia.NVDAStartup          8.1.6
com.apple.iokit.SCSITaskUserClient          3.5.6
com.apple.driver.AppleUSBODD          3.3.1
com.apple.driver.AppleFileSystemDriver          3.0.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
com.apple.BootCache          34
com.apple.driver.XsanFilter          404
com.apple.iokit.IOAHCIBlockStorage          2.3.5
com.apple.driver.AppleUSBHub          635.4.0
com.apple.driver.AppleSDXC          1.4.3
com.apple.iokit.AppleBCM5701Ethernet          3.6.2b4
com.apple.driver.AppleAHCIPort          2.6.6
com.apple.driver.AirPort.Brcm4331          615.20.17
com.apple.driver.AppleUSBEHCI          621.4.6
com.apple.driver.AppleUSBXHCI          635.4.0
com.apple.driver.AppleACPIButtons          1.8
com.apple.driver.AppleRTC          1.5
com.apple.driver.AppleHPET          1.8
com.apple.driver.AppleSMBIOS          1.9
com.apple.driver.AppleACPIEC          1.8
com.apple.driver.AppleAPIC          1.7
com.apple.driver.AppleIntelCPUPowerManagementClient          214.0.0
com.apple.nke.applicationfirewall          4.0.39
com.apple.security.quarantine          2.1
com.apple.driver.AppleIntelCPUPowerManagement          214.0.0
com.apple.driver.IOBluetoothHIDDriver          4.1.7f2
com.apple.driver.AppleMultitouchDriver          237.4
com.apple.iokit.IOSerialFamily          10.0.6
com.apple.kext.triggers          1.0
com.apple.driver.DspFuncLib          2.4.7fc4
com.apple.iokit.IOAudioFamily          1.9.2fc7
com.apple.kext.OSvKernDSPLib          1.12
com.apple.iokit.IOBluetoothHostControllerUSBTransport          4.1.7f2
com.apple.driver.AppleBacklightExpert          1.0.4
com.apple.nvidia.gk100hal          8.1.6
com.apple.NVDAResman          8.1.6
com.apple.iokit.IOAcceleratorFamily          74.15
com.apple.driver.AppleSMBusController          1.0.11d1
com.apple.driver.AppleThunderboltEDMSink          1.2.0
com.apple.driver.IOPlatformPluginLegacy          1.0.0
com.apple.driver.X86PlatformPlugin          1.0.0
com.apple.iokit.IOSurface          86.0.4
com.apple.iokit.IOBluetoothFamily          4.1.7f2
com.apple.driver.AppleSMC          3.1.5d4
com.apple.driver.AppleGraphicsControl          3.4.5
com.apple.iokit.IONDRVSupport          2.3.7
com.apple.driver.IOPlatformPluginFamily          5.4.1d13
com.apple.driver.AppleHDAController          2.4.7fc4
com.apple.iokit.IOHDAFamily          2.4.7fc4
com.apple.iokit.IOGraphicsFamily          2.3.7
com.apple.iokit.IOSCSIBlockCommandsDevice          3.5.6
com.apple.iokit.IOSCSIMultimediaCommandsDevice          3.5.6
com.apple.iokit.IOBDStorageFamily          1.7
com.apple.iokit.IODVDStorageFamily          1.7.1
com.apple.iokit.IOCDStorageFamily          1.7.1
com.apple.iokit.IOUSBMassStorageClass          3.5.2
com.apple.iokit.IOSCSIArchitectureModelFamily          3.5.6
com.apple.iokit.IOUSBHIDDriver          623.4.0
com.apple.driver.AppleThunderboltDPOutAdapter          2.5.0
com.apple.driver.AppleThunderboltDPInAdapter          2.5.0
com.apple.driver.AppleThunderboltDPAdapterFamily          2.5.0
com.apple.driver.AppleThunderboltPCIDownAdapter          1.3.2
com.apple.driver.AppleUSBMergeNub          621.4.6
com.apple.driver.AppleUSBComposite          621.4.0
com.apple.driver.AppleThunderboltNHI          1.9.2
com.apple.iokit.IOThunderboltFamily          2.7.7
com.apple.iokit.IOUSBUserClient          630.4.4
com.apple.iokit.IOEthernetAVBController          1.0.2b1
com.apple.iokit.IOAHCIFamily          2.5.1
com.apple.iokit.IO80211Family          530.5
com.apple.iokit.IONetworkingFamily          3.0
com.apple.iokit.IOUSBFamily          635.4.0
com.apple.driver.AppleEFINVRAM          2.0
com.apple.driver.AppleEFIRuntime          2.0
com.apple.iokit.IOHIDFamily          1.8.1
com.apple.iokit.IOSMBusFamily          1.1
com.apple.security.sandbox          220.3
com.apple.kext.AppleMatch          1.0.0d1
com.apple.security.TMSafetyNet          7
com.apple.driver.DiskImages          345
com.apple.iokit.IOStorageFamily          1.8
com.apple.driver.AppleKeyStore          28.21
com.apple.driver.AppleACPIPlatform          1.8
com.apple.iokit.IOPCIFamily          2.8
com.apple.iokit.IOACPIFamily          1.4
com.apple.kec.corecrypto          1.0
Model: iMac13,2, BootROM IM131.010A.B04, 4 processors, Intel Core i5, 2.9 GHz, 8 GB, SMC 2.11f14
Graphics: NVIDIA GeForce GTX 660M, NVIDIA GeForce GTX 660M, PCIe, 512 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333531533643465238432D50422020
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333531533643465238432D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xF4), Broadcom BCM43xx 1.0 (5.106.98.100.17)
Bluetooth: Version 4.1.7f2 12718, 3 service, 21 devices, 3 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: APPLE HDD ST1000DM003, 1 TB
USB Device: hub_device, 0x8087 (Intel Corporation), 0x0024, 0x1a100000 / 2
USB Device: hub_device, 0x058f (Alcor Micro, Corp.), 0x6254, 0x1a120000 / 4
USB Device: hub_device, 0x058f (Alcor Micro, Corp.), 0x6254, 0x1a124000 / 6
USB Device: Ext HDD 1021, 0x1058 (Western Digital Technologies, Inc.), 0x1021, 0x1a124100 / 7
USB Device: PTK-640, 0x056a (WACOM Co., Ltd.), 0x00b9, 0x1a123000 / 5
USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8511, 0x1a110000 / 3
USB Device: hub_device, 0x8087 (Intel Corporation), 0x0024, 0x1d100000 / 2
USB Device: MacBook Air SuperDrive, apple_vendor_id, 0x1500, 0x1d130000 / 5
USB Device: hub_device, 0x0424 (SMSC), 0x2412, 0x1d180000 / 3
USB Device: BRCM20702 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x1d181000 / 4
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x828b, 0x1d181300 / 7

Hi, Linc Davis, can you tell me witch type of error that was? CPU error, GPU error, so on. Thanks.

Installer freezes during boot with ATI Radeon card

System: Toshiba Satellite A305-S6916
Video card: ATI Radeon Mobility HD 3650
Installer: 2010.05 amd64 netinstall
Problem: Installer freezes during boot at "setting console to utf-8 mode".
Solution: Add "radeon.modeset=0" to kernel command line.
Posting for the sake of anyone else who might be having this same problem.

Same here:
System: Dell Inspiron 1525
Video card: Intel GMA X3100
Installer: 2010.05 i686
Problem: screen turn black during system load.
Solution: Add "nomodeset" or "i915.modeset0" to kernel command line.

During boot up get message "Activating SWAP [FAILED]&qu

I've just re-compiled my kernel (mainly for the fun of it) and after a few false starts almost everything appears to be working as before. The one remaining oddity is that during boot up I get a FAIL message for "Activating SWAP". I would have thought this would be fairly fatal but in fact the rest of the boot up completes OK adn the PC appears to run fine. I had a look at 'dmesg' and the only reference to swap is
Adding 262576k swap on /dev/discs/disc0/part2. Priority:-1 extents:1
which I guess means some kind of swap does get created, but perhaps its not the right one? BTW, here's the /etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
none /proc proc defaults 0 0
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
tmpfs /tmp tmpfs defaults 0 0
sysfs /sys sysfs defaults 0 0
usbdevfs /proc/bus/usb usbdevfs defaults 0 0
/dev/cdroms/cdrom0 /mnt/cd iso9660 ro,user,noauto,unhide 0 0
/dev/cdroms/cdrom0 /mnt/dvd udf ro,user,noauto,unhide 0 0
/dev/floppy/0 /mnt/fl vfat user,noauto,unhide 0 0
/dev/discs/disc0/part3 / ext3 defaults 0 1
/dev/discs/disc0/part1 /boot ext2 defaults 0 1
/dev/discs/disc0/part2 swap swap defaults 0 0
/dev/discs/disc0/part3 / ext3 defaults 0 1
/dev/discs/disc0/part1 /boot ext2 defaults 0 1
/dev/discs/disc0/part2 swap swap defaults 0 0
Any ideas?

paranoos wrote:... you've got two entries in your fstab for your swap partition. the second one is failing.
yep, remove
/dev/discs/disc0/part3 / ext3 defaults 0 1
/dev/discs/disc0/part1 /boot ext2 defaults 0 1
/dev/discs/disc0/part2 swap swap defaults 0 0
I had this problem when i installed arch to, is it the installer that does it?

X58 Pro BIOS Crash during Boot

Hi All,
I have recently assembled a system with X58 Pro board and Core i7 920. It was working fine for 3 months except that it started having BIOS crashes since last night. The issue is that the mainbaord lights would be on without the POST screen and within few seconds the system resets automatically. The same procedure happens for about 4-6 cycles and on the 7th cycle i get a message on screen saying the previous overclocking has failed and the BIOS is reset to default settings. Post then the system boots up normal and works just fine. But once the system is shut down and when the system is switched on(cold boot) I get the same problem. I have also noticed that a month back the CPU clock had jumped from default 2.66 to 2.67 automatically without any overclocking and just couple of weeks after that the clock rose up to 2.87. It has remained like that until the BIOS crash issue. All these happened without any manual overclocking. I was wondering how can this happen automatically unless the clock speeds are adjusted manually. That was quiet strange though. Neways after this issue(BIOS Crash) popped up the clock speed is back to 2.67 than the default 2.66. Weird again. The BIOS version is the default one(V7.0) that was shipped with the mainboard. I tried to M-Flash the BIOS to V7.3(after reading couple of postings from the forum) but without success. The same problem still persists. I have done the following things after going through the forums regarding the issue.
1. Cleared CMOS using the clear CMOS button(With power chord unplugged)
2. Tried M-Flashing to V7.3 (Not sure whether the BIOS was updated during the process)
I kindly request all of you so provide some solutions so as to get my system back to normalcy. Your worthwhile suggestions would be really appreciated. The system config is mentioned below
Core i7 920 @ 2.66 GHz
MSI X 58 Pro - BIOS Version 7.0
Corsair 6 GB(3 x 2 Gigs) DDR3 @ 1066 MHz (installed on the black slots currently)
EVGA GeForce GTX 295 1.7 GB GDDR3
Tagan 1100 W PSU
2 x 1 TB Seagate Sata HDD @ 7200 RPM w 32 MB cache
Sony Optiarc DVD-RW Drive
Windows XP 64Bit SP2
Looking forward for some positive solutions

Hey NovJoe,
Thanks a lot for your reply. I have done as per your suggestion and the system works fine now. Pretty interesting though. During the individual RAM tests i did not face any BIOS crashes and i thought the MOBO DIMM SLOTS would be faulty. So i installed the second RAM strip on the second slot worked fine and finally the third one and works fine too. I am really wondering wht had happened in the first place. Was that due to any dirt or dust in the memory and DIMM contacts? Well neways i am kinda relieved now. But i wanna make sure that everything works fine. What types of tests do you suggest to make sure that the system is working almost fine??
Thanks a lots
Regards
Rahul

[SOLVED] alsa daemon error during init with Thinkpad X220

Hi,
I just updated my system (including a kernel update). After reboot, I found alsa daemon, which is used to restore previous volume level, failed to start. I tried to start that daemon manually after the boot process is completed, and that produced an error message
sudo rc.d start alsa
:: Restoring ALSA Levels [BUSY]
Found hardware: "HDA-Intel" "Intel CougarPoint HDMI" "HDA:14f1506e,17aa21da,00100000 HDA:80862805,80860101,00100000" "0x17aa" "0x21da"
Hardware is initialized using a generic method
[FAIL]
However, the volume level restored successfully. It seems that recent Intel plantform provides two soundcard, and that error only affected the secondary card, which has nothing to do about system volume level.
Anyway, I hate to have a ``[FAIL]'' During init process. Any suggesting to get rid of that problem? Thanks
System Info: (I use linux-ck as my kernel with modified config)
uname -a
Linux Thomas 3.2.1-2-ck #1 SMP PREEMPT Sun Jan 15 00:16:41 CST 2012 x86_64 Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz GenuineIntel GNU/Linux
lspci
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4)
00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b4)
00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b4)
00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b4)
00:1c.6 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 7 (rev b4)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation QM67 Express Chipset Family LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 04)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04)
03:00.0 Network controller: Intel Corporation Centrino Advanced-N + WiMAX 6250 (rev 5e)
0d:00.0 System peripheral: Ricoh Co Ltd Device e823 (rev 07)
0e:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04)
config.gz:
http://codepad.org/XtUSbtdw
(Edit typo)
Last edited by cap_sensitive (2012-01-17 06:12:01)

This morning, I performed a system update and I did not see any errors with alsa when I rebooted. Audio hardware is:
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05)
Have you tried manually restarting alsa after the system boots up to see if you get the same error? You can restart alsa with the following command:
sudo /etc/rc.d/alsa force-restart
Post your results. If the error occurs during the manual restart, it should also include some details about what caused the error

Windows blue screen of death crash during Boot Camp driver install

I have been trying to get Windows running under Boot Camp on my 2.66 GHz Alu iMac, but without success.
Boot Camp partitions the drive and Windows XP SP2 installs properly. I boot into Windows, and then insert my Leopard install DVD to install the Apple drivers.
The driver installation gets about halfway, then the machine crashes with a blue screen of death and restarts automatically. It puts me back in Windows, with no drivers installed.
I am installing the Boot Camp drivers from the Leopard retail DVD. This machine is missing the Leopard install/restore discs that came with it, and Apple want to charge £99 for a replacement set.
Is there any way I can get the Boot Camp drivers installed, or do I need to find a friend with the exact same machine and original system discs and use those?

Aloha Adam.
Don't know whether this is helpful, but below is a list of drivers that are installed (as of Aug 08).
Also, if you have not already, you may find FAQ helpful, as well, at URL: http://support.apple.com/kb/HT1656
Lastly, though they're a year old, the Update 2.1 is in .exe format, so if you can get it the .exe download package onto your installed Windows OS somehow (e.g., copied onto a CD, IF Windows can read it), you might stand a chance of alternate means of installing the drivers.
If this helps, please so indicate.
Thanks,
HJ
"Drivers, Macintosh features within Microsoft Windows, other
Which drivers are included on the Mac OS X 10.5 (Leopard) DVD?
The Mac OS X 10.5 (Leopard) DVD contains the following Macintosh drivers for Windows:
Apple Bluetooth
Apple Keyboard Support
Apple Remote Driver
Apple Trackpad
Atheros 802.11 Wireless
ATI Graphics
Boot Camp Control panel for Microsoft Windows
Boot Camp System Task Notification item (System Tray)
Broadcom Wireless
Intel Chipset Software
Intel Integrated Graphics
iSight Camera
Marvel Yukon Ethernet
nVidia Graphics
Realtek Audio
SigmaTel Audio
Startup Disk Control panel for Microsoft Windows"

Yosemite System Crashes on Boot with Dell U2713HM

Previously under Mavericks I had no issue with a Dell U2713HM monitor and my 'non-stock' NVidia card. (The reason I'm using the video card I am is because the stock ATI card (ATI Radeon HD 2600 XT) is known do fry itself which I discovered after replacing it with an identical card and having the 2nd one fry itself after a year. I did a lot of research and settle don the card I now have because others had reported success with it. It worked fine for nearly a year until updating to Yosemite.)
After upgrading to Yosemite my system went into an infinite reboot loop on startup. On a hunch, I swapped out my U2713HM for an old 17" monitor and was able to boot. I can't even have the U2713HM plugged in/turned off using the second port on the card without the system crashing. If I get the system booted using the 17", I can then plug in/turn on the U2713HM and set the resolution - at that point I can (sometimes) boot but it will then crash on shutdown triggering an automatic restart.
Is anyone having any success with a U2713HM, and especially with an NVidia card? The only option I haven't tried is a completely fresh, clean install. Once the system boots, I get the dialog that it was restarted because of an issue and can view part of the dump info that will be sent to Apple -> that clearly indicates the issue is with the kernel/NVidia driver somewhere.
System specs: Mac Pro (Early 2008) with an NVidia GeForce GTX 650 1024MB card installed running Yosemite (OS X 10.10)

My mac mini (late 2012, Yosemite installed) doesn't start with Dell U2713HM if the USB cable of the monitor is connected.
No problems if I connect the usb-cable after successful startup. Also the usb-hub of the Dell is working fine then.

[SOLVED] No polish characters during boot with DAEMON_LOCALE=YES

Hello, it didn't bother me much before cause I always had DAEMON_LOCALE=NO, but with recent upgrade new rc.conf was introduced with DAEMON_LOCALE set by default to YES. Now my messages are like this:
Checking Filesystems [BUSY] /dev/sda2: czysty, 183465/647168 plikÃ³w, 2083335/2588473 blokÃ³w
Questions are: is it supposed to be half message in english half in polish? and how to repair those missing characters? (loading console font is done after those messages)
BTW this is on virtualbox guest with all testing + kde-unstable repos enabled
Last edited by masteryod (2012-06-06 10:46:45)

DSpider wrote:
Whenever you edit the "/etc/mkinitcpio.conf" file (ie. add "consolefont" to the HOOKS line), don't forget to regenerate your initramfs image!
# mkinitcpio -p linux
Yes, I know and I do execute it every time I touch the "/etc/mkinitcpio.conf"
DSpider wrote:It still wasn't fixed? Then try adding keymap (which says there that it "Adds keymap and consolefonts from rc.conf."), and don't forget to regenerate your initramfs image!
I have tried that and still no luck:
1. Edit CONSOLE* settings in /etc/rc.conf
[root@dog etc]# grep ^CONSOLE rc.conf
CONSOLEFONT="lat2-16"
CONSOLEMAP="8859-2"
2. Add consolefont and keymap to HOOKS in /etc/mkinitcpio.conf
[root@dog etc]# grep ^HOOKS mkinitcpio.conf
HOOKS="base udev autodetect sata filesystems fsck consolefont keymap"
3. Run mkinitcpio
[root@dog etc]# mkinitcpio -p linux
==> Building image from preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.3.7-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [sata]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
-> Running build hook: [consolefont]
-> Running build hook: [keymap]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.3.7-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [sata]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
-> Running build hook: [consolefont]
-> Running build hook: [keymap]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful
I have dug the problem deeper and checked what is going on in the /etc/rc.* scripts. Everything seems to be in order, but the loading of consolefont/keymap on boot is not having any effect in my case:
1. System boots, then
2. Loging in as root
3. Typing in some Polish pangram as test: zażółć gęślą jaźń
4. Observing lack of Polish diacritics printed
5. Re-executing the rc.sysinit steps releated to consolefont/keymap settings:
# source /etc/rc.conf
# source /etc/rc.d/functions
# set_consolefont
:: Loading Console Font: lat2-16
6. Trying the Polish pangram test again.
7. Success, all Polish characters are rendered correctly.
Here is screenshot which presents the simple test explained above:
Now, this test suggests to me that the rc.sysinit procedure of configuring consolefont/keymap seems correct.
However, something seems to get messed during rc.sysinit, so the configuration is later overriden and doesn't persist afterwards.
Does anyone have an idea what may be wrong? Does it qualify to be reported as a bug?
Last edited by mloskot (2012-06-06 00:34:10)

Pciimaq.sys causes nt40 to crash during booting?

I'm trying to install a 1408 IMAQ card. Anyhow, the system running
NT40+SP6 does not manage to boot anymore. It allways presents me with a
blue-screen,
telling me that PCIIMAQ.SYS causes some kind of adress error.
What can I do to fix this?
Regards,
Thomas jennewein

Is the IMAQ board in the computer when this crash occurs? Do the crash occur if the boasrd is out of the computer. If you can boot without the board in, you probably have a bad board. If it still does not boot, can you boot in safe mode and uninstall the driver or it won't even let you select which mode to boot in?

Can not load modules during boot with kernel 2.6.31

Every time i install kernel 2.6.31 (ever since it got into core), after reboot i receive message
FATAL: module ... not found
with every module in my rc.conf, or sometimes with this message:
FATAL: could not load /lib/modules/2.6.30-ARCH/modules.dep no such file or directory
Before those errors the boot script complaisn about hardware clock (right after the Arch Linux line):
Could not access the hardware clock via any known method.
After that I can still start X but my keyboard and mouse are completely dead. The console works fine, i just can not load any module per hand, some daemon can not be started - obviously.
Latest kernel 2.6.30 works fine. Is this a problem of 2.6.31 ?

/lib/modules/2.6.30-ARCH/
That is very strange... it's not booting into .31
It's an install problem because that dir shouldn't be there after updating kernel26.
I know you said you installed from core, but was it a custom install? Did you change the PKGBUILD in anyway?
After installing .31, before rebooting do depmod 2.6.31-ARCH
Then do mkinitcpio -p kernel26
Post the output of the second one.
Last edited by gog (2009-10-26 00:32:06)

Crash during capture with Kona

I have an odd problem with video capture. During the capture, if I click onto another app or even just the Finder, Final Cut crashes. It actually looks perfectly fine: video continues to be displayed in the capture screen and disk activity continues. However, FCP doesn't come back to being the front application and I have to force quit it.
If I don't click on another app during capture, everthing is fine.
Yeah, yeah: if it hurts, don't do it, right? However, I don't think FCP should crash just because I've switched into another app (particularly when it's just the Finder & no other "real" app is running). I just added a Kona LHe card and I think this crash has started since then.
Details:
* Quad G5
* Kona LHe
* OS X 10.4.6
* FCP 5.1.1
* external SATA array
* latest Aja drivers
Has anyone else seen this?
Regards,
fh

I finally got around to calling AJA on this. They said it's to be expected. I should have realized but the problem is caused by the switching of control of the Kona card. There's a whole bunch of information about this in the Kona manual and it sounds insanely complicated, so now that I think about it, it's no surprise that switching during a capture might be bad.
AJA tech support (Rudi, I think) was, as always, fantastic. I love that company.
thanks,
fh

Ds 6.x with ldap client

Hi,
Im wondering, do we need a nfs server to be as automounter for home directory users?
I have reading 2 articles that im thinking easier for me to understand:
-http://www.datadisk.co.uk/html_docs/ldap/
-http://www.tech-recipes.com/rx/1828/solaris_10_directory_server_installation/
Anyway, just querying on how is the best steps to make sure when the users login, the automount will mount the user's home directory
& users can do their works through eg: JDS environment.
Im really no idea rite now.

There're 3 different steps here:
- First you need to decide how to access your home directories, via NAS,SAN, NFS and such likes. This has
nothing to do with DSEE, but it will help to you to know what to put in your automount tables.
- Then, you need to decide how and where your client systems/workstations will get the automount tables.
You can define them locally one each machine, or use NIS or LDAP. If you choose LDAP, then of course
DSEE 6 can help you. Basically, you'll have to set up DSEE to store such kind of datas, and then set up
your clients so that they get the automount tables via LDAP.
This is all very well documented in the Naming and Directory Services guide that you can use even if not
on Solaris: http://docs.sun.com/app/docs/doc/816-4556/preface-1?l=fr&q=naming+and+directory+services&a=view
- Finally, you'll have to setup your clients to use LDAP to get the automount tables. It requires configuring the
Name Service Switch layer and the way to do it depends on the client system(s). For Solaris, it's explained in the
document above but you can easily find docs for any kind of other systems.
Good Luck ..

Dbus Daemon crashes during boot with ldap-client activ

Similar Messages

Maybe you are looking for