Display doesn't work after sleeping.

I have a trouble, after I put my notebook in sleep mode, it doesn't wake up, but the leds are working. I have to shut it down manually from the button, that is not so good.

Hi @m1do ,
Thank you for visiting the HP Support Forums and Welcome. I have looked into your issue about your HP Pavilion 15-n057sr Notebook PC and issues with the sleep mode. Here is a link that goes through some troubleshooting steps to resolve the sleep issues.
Here is a link to the HP Support Assistant. Just download and run the application and it will help with the software and drivers on your system making sure your system is up to date, as this could cause this same issue.
Please let me know how this goes.
Thanks.
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom to say “Thanks” for helping!

Similar Messages

IMac - Display doesn´t work after restart

My iMac 21 Display doesn´t work after restart. If I turn it off and 1 hour later I want use it again the iMac shows the white screen with the mac logo and then the display goes off. I connected an external display to check if the iMac was ON and with the external display I can login and do everything but the iMac Display doesn´t work .
If I turn it off and wait 3 or 4 hours and then turn it back on the display works OK.
This is very strange behavior I have spent hours and hours trying to fine the solution or a similar issue but nothing so I am looking help here at apple.com
BTW When I bougth the iMac 21 there were some spots over the display so the display was replaced by the provider. The warranty has expired by now.

To tell you the truth, I don't know if they have to repalce the LCD panel or what they do for a bad backlight. In this reality of block or assembly replacement it probably involves repalcing the panel and not the backlight component. Don't know what it would cost. You'd have to ask that of a service center.

M3800 Developer Edition: wifi doesn't work after sleep

I have an M3800 Developer Edition (2015 model). Ubuntu is factory-installed 14.04, with hardware enablement stack installed. Recently (past 1-2 weeks) wifi doesn't work after sleep (lid closed or open doesn't matter), and only rebooting gets in back. Tried rmmod and modprobe with no success. Has anyone else seen this, and/or are you aware of any open bug(s) for this?
Relevant ouput:
lsmod when problem exists:
iwlmvm                217725 0
mac80211              652718 1 iwlmvm
iwlwifi               179412 1 iwlmvm
cfg80211              494362 3 iwlwifi,mac80211,iwlmvm
rfkill list when problem exists:
1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
3: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no
rmmod the above, then modprobe iwlwifi. Does not fix problem, only rebooting does:
May 4 08:23:14 jonathan-m3800 kernel: [69089.189614] cfg80211: Calling CRDA to update world regulatory domain
May 4 08:23:14 jonathan-m3800 kernel: [69089.192181] cfg80211: World regulatory domain updated:
May 4 08:23:14 jonathan-m3800 kernel: [69089.192184] cfg80211: DFS Master region: unset
May 4 08:23:14 jonathan-m3800 kernel: [69089.192185] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
May 4 08:23:14 jonathan-m3800 kernel: [69089.192187] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
May 4 08:23:14 jonathan-m3800 kernel: [69089.192188] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
May 4 08:23:14 jonathan-m3800 kernel: [69089.192189] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm), (N/A)
May 4 08:23:14 jonathan-m3800 kernel: [69089.192190] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
May 4 08:23:14 jonathan-m3800 kernel: [69089.192191] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
May 4 08:23:14 jonathan-m3800 kernel: [69089.204141] Intel(R) Wireless WiFi driver for Linux, in-tree:
May 4 08:23:14 jonathan-m3800 kernel: [69089.204143] Copyright(c) 2003- 2014 Intel Corporation
May 4 08:23:14 jonathan-m3800 kernel: [69089.204414] iwlwifi 0000:06:00.0: irq 48 for MSI/MSI-X
May 4 08:23:14 jonathan-m3800 kernel: [69089.204904] iwlwifi 0000:06:00.0: loaded firmware version 25.228.9.0 op_mode iwlmvm
May 4 08:23:14 jonathan-m3800 kernel: [69089.207709] iwlwifi 0000:06:00.0: Detected Intel(R) Dual Band Wireless AC 7260, REV=0x144
May 4 08:23:14 jonathan-m3800 kernel: [69089.207790] iwlwifi 0000:06:00.0: L1 Enabled - LTR Enabled
May 4 08:23:14 jonathan-m3800 kernel: [69089.208150] iwlwifi 0000:06:00.0: L1 Enabled - LTR Enabled
May 4 08:23:14 jonathan-m3800 kernel: [69089.392408] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
May 4 08:23:14 jonathan-m3800 NetworkManager[901]:    SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:1c.2/0000:06:00.0/net/wlan0, iface: wlan0)
May 4 08:23:14 jonathan-m3800 NetworkManager[901]:    SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:1c.2/0000:06:00.0/net/wlan0, iface: wlan0): no ifupdown configuration found.
May 4 08:23:14 jonathan-m3800 NetworkManager[901]: <info> (wlan0): using nl80211 for WiFi device control
May 4 08:23:14 jonathan-m3800 NetworkManager[901]: <info> (wlan0): driver supports Access Point (AP) mode
May 4 08:23:14 jonathan-m3800 NetworkManager[901]: <info> (wlan0): new 802.11 WiFi device (driver: 'iwlwifi' ifindex: 4)
May 4 08:23:14 jonathan-m3800 NetworkManager[901]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/2
May 4 08:23:14 jonathan-m3800 NetworkManager[901]: <info> rfkill5: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.2/0000:06:00.0/ieee80211/phy0/rfkill5) (driver iwlwifi)
May 4 08:23:16 jonathan-m3800 ModemManager[852]: <warn> Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:1c.2/0000:06:00.0': not supported by any plugin
lspci:
06:00.0 Network controller: Intel Corporation Wireless 7260 (rev 6b)
After reboot:
lsmod |grep -i iwl:
iwlmvm                217725 0
mac80211              652718 1 iwlmvm
iwlwifi               179412 1 iwlmvm
cfg80211              494362 3 iwlwifi,mac80211,iwlmvm
rfkill list after reboot:
0: nfc0: NFC
        Soft blocked: no
        Hard blocked: no
1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
2: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no

Wi-Fi still not reconnecting after sleep
http://forums.macrumors.com/showthread.php?t=1229591

Stand-by button on Cinema HD display doesn't work after Mountain Lion upgrade

Hi,
After I upgraded my Mac mini (spring '09) to Mountain Lion it appears that the buttons on the side of my Cinema HD display doesn't work. There is a setting in sys preferences that should put the Mac in stand-by when the power button is pressed. This doesn't work after I upgraded to OSX 10.8 Mountain Lion.
Does anyone have similar experience. Anyway to fix it?
Thanks,
Henrik

Have done some further investigating (to no avail). The TV is displaying in my system Info as follows:
Intel HD Graphics 3000:
Chipset Model: Intel HD Graphics 3000
Type: GPU
Bus: Built-In
VRAM (Total): 384 MB
Vendor: Intel (0x8086)
Device ID: 0x0116
Revision ID: 0x0009
Displays:
Color LCD:
Display Type: LCD
Resolution: 1440 x 900
Pixel Depth: 32-Bit Color (ARGB8888)
Main Display: Yes
Mirror: Off
Online: Yes
Built-In: Yes
Connection Type: DisplayPort
TOSHIBA-TV:
Resolution: 1920 x 1080 @ 60 Hz
Pixel Depth: 32-Bit Color (ARGB8888)
Mirror: Off
Online: Yes
Rotation: Supported
Television: Yes
But nothing on the screen.
Does anyone know if Apple have banned certain screens????

Wifi doesn't work after sleep

I'm having an issue where my wifi will stop working after sleep. This isn't the same problem where the network had to be manually reconnected--
The "radar" will be grayed out, and I can see the networks if I click on it, but I cannot reconnect, disable wifi (make the radar the pie shape). The only thing I can do is do a hard reset holding the power button until the computer shuts off.
In fact, if I select 'Apple -> Restart,' nothing happens. I have to hold the power button down.
Any thoughts?

Wi-Fi still not reconnecting after sleep
http://forums.macrumors.com/showthread.php?t=1229591

Help! 2010 imac 27" - Display doesn't work after long sleep

I just recently started having this problem. I've had this iMac since 2010 with zero issues, but it seems like ever since I downloaded Yosemite, the screen won't work after the computer has been sleeping for a while. I have to hold the power button and do a hard restart to get it to work again. If the computer has only been sleeping for a while, it wakes just fine. It's only after it's been sleeping all night and I go to use it agsin. I've checked power connections and all is good. Any ideas??

Hi Punisher8522,
Welcome to the Support Communities! The resource below offers some troubleshooting steps to try when your computer won't wake from sleep.
OS X: When your Mac doesn't sleep or wake - Apple Support
http://support.apple.com/en-us/TS5357
Your computer cannot wake from sleep
Make sure your computer isn't powered off by pressing the power key for one second.
If you're using an external display, make sure your display is not powered off or unplugged.
If you are using a Mac desktop:
Make sure the AC power cord is connected securely to the computer and outlet.
Make sure the AC power outlet it is connected to is working properly.
If your computer is plugged into a power strip, make sure the power strip is not turned off. Check to make sure other items connected to the power strip are receiving power.
Your computer is slow to wake from sleep
If you see a progress bar when you wake your computer from sleep, this is normal. The computer is waking from safe sleep.
OS X Recovery and sleep
The system software your computer uses when started from OS X Recovery allows display sleep. Your computer does not go to sleep on idle while started from Recovery unless you are using a Mac notebook that is not connected to AC power.
Additional troubleshooting
If the steps above do not resolve your sleep-related issue, try these additional recommendations.
Reset SMC
The System Management Controller (SMC) is involved in managing power on your computer. Reset the SMC on your Mac if you are having difficulty sleeping or waking your computer.
Reset NVRAM/PRAM
Nonvolatile RAM (NVRAM)/Parameter RAM (PRAM) stores some power-related settings.Try resetting NVRAM/PRAM if you are having difficulty sleeping or waking your computer.
Test with external devices disconnected
Some external devices can prevent your computer from sleeping. Try disconnecting items other than your Apple keyboard or mouse from the built-in USB, Thunderbolt and Firewire ports on your Mac. If this resolves the issue, try reconnecting your external devices one at a time until you find the device preventing sleep or wake. Check the documentation that came with the device, or contact the device manufacturer for more information.
Try Safe Mode
Check to see if the issue still occurs when the computer is started in Safe Mode. If this resolves the issue, it could be related to a third party software item such as:
a login item
a startup item
a third party kernel extension
Try another user account
Try creating another user account, or log in as guest. See if your computer sleeps and wakes properly from the additional user account. If it does, your issue may be related to one of the following:
a login item
an app open in the original user account
You can disable login items from the Accounts pane of System Preferences. Try opening only one app at a time in the original user account to determine which app is preventing sleep. If you isolate the issue to a particular app or login item, check its documentation, or contact the developer of that software for more information.
Last Modified: Sep 19, 2014
I hope this information helps ....
- Judy

Display doesn't work after latest security update

I have three Apple displays with my MacPro, and after installing the latest security update, one of them just stopped working.
The status light is still on, and my usb devices connected still function, but I have a black screen and nothing is recognized in the displays system preferences.
Anyone else experience this? Did my display just die?

Ut-oh!
FWIW:
My 7-year-old 22” Cinema Display, on a 10.4.11 machine, with nearly constant use, now becomes so dim during the screen saver mode that regardless of which saver I use, it becomes no longer visible.
As soon as the screen saver is activated, I have full brightness (though not as bright as when the display was new), then it gradually fades until the screen is all black.
Upon awaking, the screen is very dim, and then, over a 90 second period, it slowly returns to normal brightness.
1. The brightness control is set to max.
2. I have toggled the brightness control and changed screen savers, both to no avail.
3. Recalibrating the display did not work.
This seems to have occurred on the same day I installed the latest Apple Security Updater.
Very weird...

Bluetooth doesn't work after sleep mode wake up

Okay, so my computer goes to sleep while in Windows XP and I wake is up. I have my bluetooth mouse and keyboard hooked up to it and I try to wake them up. My mouse doesn't reconnect. I notice that my computer also says that it's not connected to my wireless network, but the my web browser and messenger still connect fine. I check my bluetooth preferences to find out that nothing is connected and when I try to reconnect it doesn't work. This never used to happen and it just recently started when I reinstalled windows this past week. The only way I could get the devices to reconnect was to reboot and even then when my computer goes back to sleep they still disconnect.
Anyone else have this problem... or better yet, an answer?

How did you actually solve your problem ?
I have this too on a macbook 2.4.
any help appreciated, this is very annoying.
I installed all latest updates to windows/bootcamp. Did not help.

Bluetooth keyboard and magic pad doesn't work after sleep

This only recently developed, once my 2013 iMac goes into sleep mode, when I tap the keyboard to wake it up to put in my security password, the bluetooth keyboard doesn't work. Also, the track pad shows no point, i.e. I have a sign in screen, but can't sign it.

Hi there,
I would recommend taking a look at the troubleshooting steps found in the article below.
Troubleshooting wireless mouse and keyboard issues
http://support.apple.com/kb/ts3048
-Griff W.

Display doesn't work after power outage

The electricity was knocked out in my neighborhood for a few hours and when it was finally restored I found that my display no longer works. It is getting no power at all. None of the lights on the front of the display are working--it's totally dead.
No settings or connections were changed during the time when there was no electricity. So it's obviously a result of the power outage, right? I had it plugged into a surge protector (which I thought was supposed to be a safeguard against exactly this type of occurence) so I'm wondering if that has somehow saved me--only there's some secret Mac trick that needs to be done to get my display back to life.
Can anyone please help me? This economy is strangling me to death--I simply cannot afford to buy a new display at this point.

I just realized that I never actually asked my question (duu-uuuh):
Can anyone tell me if there is a way to figure out (without having to spend any money) if my problem is only with the power supply or if the entire display is just garbage at this point?
Or perhaps someone has experienced this situation, was able to resolve it and knows what I should do to make my display functional again?

Kotoeri Caps Lock modifier doesn't work after sleep

I use Kotoeri Japanese input as my only input system, and under the Kotoeri preferences I have set Caps Lock key function to "When down input romaji". This allows me to keep the Caps Lock key down to type in English, and release it to type in Japanese. However, when I leave the Caps Lock on, close the lid of my MBP and re-open it, the input switches back to Japanese (but the Caps Lock light stays on). I have to double-toggle the Caps Lock to get back to romaji input. The problem also sometimes occurs if I just leave the machine to go to screensaver.
Is this a bug? If not, does anyone know how I can stop this behaviour?

Sounds like a bug, but if you know Japanese well you might also ask on the Japanese discussions:
https://discussionsjapan.apple.com/community/macos/mac_osx_v10.6_snowleopard

[Solved] Network doesn't work after hibernate?

Hello! This is my first legit Linux install so excuse me if I'm a bit slow. I installed Arch last night and everything went smoothly. However, after I tested out hibernate on my machine, the network doesn't seem to work. Just prior to the hibernate, I installed Pidgin and Skype but they worked alright, so I think that the hibernate caused a problem on eth0.
I have an Asus P8Z68-V Pro motherboard with an Intel 82579V Gigabit Ethernet Controller that's using the e1000e driver. Running "dmesg | grep e1000e" says that it is up.
I'm not entirely clear here, but from reading, I think that I have several ways of connecting to the network, including network, dhcpcd, networkmanager, and wicd. I am using wicd so I did the following (or at least I think I am only using wicd):
#rc.d stop network
#rc.d stop dhcpcd
#rc.d stop networkmanager
Similarly, I put a ! in front of network in rc.conf:
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
# startup and during the boot process. If set to 'no', the C locale is used.
# HARDWARECLOCK: set to "", "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# Note: Using "localtime" is discouraged, using "" makes hwclock fall back
# to the value in /var/lib/hwclock/adjfile
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# Note: if unset, the value in /etc/localtime is used unchanged
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.UTF-8"
DAEMON_LOCALE="no"
HARDWARECLOCK="UTC"
TIMEZONE="America/New_York"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
# Replace every !module by an entry as on the following line in a file in
# /etc/modprobe.d:
# blacklist module
# See "man modprobe.conf" for details.
MODULES=()
# Udev settle timeout (default to 30)
UDEV_TIMEOUT=30
# Scan for FakeRAID (dmraid) Volumes at startup
USEDMRAID="no"
# Scan for BTRFS volumes at startup
USEBTRFS="no"
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="Vicious"
# Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
# Wired network setup
# - interface: name of device (required)
# - address: IP address (leave blank for DHCP)
# - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
# - broadcast: broadcast address (ignored for DHCP) (optional)
# - gateway: default route (ignored for DHCP)
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# broadcast=192.168.0.255
# gateway=192.168.0.1
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=
interface=eth0
address=
netmask=
broadcast=
gateway=
# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"
# Enable these netcfg profiles at boot-up. These are useful if you happen to
# need more advanced network features than the simple network service
# supports, such as multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
# If something other takes care of your hardware clock (ntpd, dual-boot...)
# you should disable 'hwclock' here.
DAEMONS=(hwclock syslog-ng dbus !network netfs crond wicd)
Restarting eth0 through wicd-cli still did not work. I also tried resuscitating the network via instructions on the configure network page before trying to focus solely on wicd.
I found a few similar problems on the forums by searching "wicd hibernate" and tried several solutions but they did not work. Several problems seem to be that the network doesn't work after a suspend because I guess the stuff in RAM did not get saved? But people were able to restart the network by running "/usr/lib/wicd/autoconnect.py" and I wasn't able to get this to work. As a final effort, I added "resume" into mkinitcpio.conf and placed the machine into sleep again to see if it may magically reset something but of course this did not happen .
mkinitcpio.conf:
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES=""
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run first, so it may be used to
# override the actual binaries used in a given hook.
# (Existing files are NOT overwritten if already added)
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options
# like so:
# FILES="/etc/modprobe.d/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS="base udev autodetect pata scsi sata filesystems"
## This is identical to the above, except the old ide subsystem is
## used for IDE devices instead of the new pata subsystem.
# HOOKS="base udev autodetect ide scsi sata filesystems"
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS="base udev pata scsi sata usb filesystems"
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS="base udev pata mdadm encrypt filesystems"
## This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
HOOKS="base udev autodetect pata scsi sata resume filesystems usbinput"
# COMPRESSION
# Use this to compress the initramfs image. With kernels earlier than
# 2.6.30, only gzip is supported, which is also the default. Newer kernels
# support gzip, bzip2 and lzma. Kernels 2.6.38 and later support xz
# compression.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""
Not sure if my fstab.conf is useful but if this has something to do with settings getting "lost" in swap, here it is. Linux is on an SSD and HDD (sda and sdc) and Windows 7 is on a HDD (sdb).
fstab.conf:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /tmp tmpfs nodev,nosuid,noatime,size=2000M,mode=1777 0 0
/dev/sda1 / ext4 defaults,noatime,discard 0 1
/dev/sda2 /home ext4 defaults,noatime,discard 0 2
/dev/sdc1 /boot ext4 defaults 0 1
/dev/sdc2 /var ext4 defaults 0 0
/dev/sdc3 swap swap defaults 0 0
/dev/sdc4 /media/data ext4 defaults 0 0
shm /dev/shm tmpfs nodev,nosuid,size=10G 0 0
Is wicd causing these problems or did I configure something else improperly? Would appreciate any help to get eth0 up again!
Last edited by TheBigCow7 (2011-09-13 17:57:20)

Ok, I think I've made some progress! Hibernate definitely affects my network connection. Could this be a kernel 3.0 problem?
I noticed that ifconfig showed eth0 without an inet addr, just an inet6 addr for the longest time. e1000e seemed to be loading up ok. I'm not certain here, but I think that meant the dhcp settings didn't stick, or something along those lines.
Trying to use dhcpcd like the instructions here did not work. By some chance, one attempt did work and while it did, I downloaded and installed dhclient. After that one successful attempt, renewing the DHCP lease via dhcpcd did not work again.
Luckily though, I found that running "dhclient eth0" worked. My DHCP settings seemed to have somehow gotten messed up after my initial, problematic hibernate to the point where none would stick, even after a reboot. Manually typing in "dhclient eth0" would get eth0 working, so I decided to add it to the bottom of /etc/rc.local, like in the example on the networking page.
Now, eth0 works after a boot. However, after the daemons load up during the boot process, my computer takes a long time to get to the login prompt (this is relatively speaking, since I am on a SSD and the boot process used to be blazing fast before). I'm pretty sure it's because I added "dhclient eth0" to /etc/rc.local.
I should say that even with these changes, after a hibernate, my eth0 still does not work and if it weren't for the edit to /etc/rc.local, eth0's inet settings would still not stick after a reboot (that is to say, the hibernate does do something to my network settings).
Is this the correct/most efficient way to fix my DHCP problem? Can I fix my "eth0 after hibernate" issue? Also, can I make my DHCP settings boot up without changes to /etc/rc.local so that I can get a fast boot again (still not sure how it was able to work before without my edit)?

Mail server doesn't work after upgrading from SL to ML

My Mail server doesn't work after upgrading from SL to ML
Mail client connects with the Mail Server wich seems to run but then they can't receive any email...
the problem seems to be related with dovecot ... in my smtp log i get this:
relay=dovecot, delay=324, delays=324/0.02/0/0.01, dsn=4.3.0, status=deferred (temporary failure. Command output: pipe: fatal: pipe_command: execvp /usr/libexec/dovecot/deliver: Permission denied
I have to say that in the usr/libexec there wasn't the dovecot directory so I just tried to create one but with no luck
Any Ideas?
Cheers
Carlo
This is my postconf -n info:
server:Data admin$ postconf -n
biff = no
command_directory = /usr/sbin
config_directory = /Library/Server/Mail/Config/postfix
content_filter = smtp-amavis:[127.0.0.1]:10024
daemon_directory = /usr/libexec/postfix
data_directory = /Library/Server/Mail/Data/mta
debug_peer_level = 2
debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin xxgdb $daemon_directory/$process_name $process_id & sleep 5
dovecot_destination_recipient_limit = 1
enable_server_options = yes
header_checks = pcre:/etc/postfix/custom_header_checks
html_directory = /usr/share/doc/postfix/html
imap_submit_cred_file = /Library/Server/Mail/Config/postfix/submit.cred
inet_interfaces = all
inet_protocols = ipv4
mail_owner = _postfix
mailbox_size_limit = 0
mailbox_transport =
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
maps_rbl_domains =
message_size_limit = 20971520
mydestination = $myhostname, localhost.$mydomain, localhost
mydomain = moremoremore.it
mydomain_fallback = localhost
myhostname = server.moremoremore.it
mynetworks = 127.0.0.0/8,192.168.178.0/24
newaliases_path = /usr/bin/newaliases
queue_directory = /Library/Server/Mail/Data/spool
readme_directory = /usr/share/doc/postfix
recipient_delimiter = +
relayhost = mail.mclink.it
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = _postdrop
smtp_sasl_auth_enable = no
smtp_sasl_password_maps =
smtpd_client_restrictions = permit_mynetworks permit_sasl_authenticated reject_rbl_client zen.spamhaus.org permit
smtpd_enforce_tls = no
smtpd_helo_required = yes
smtpd_helo_restrictions = reject_invalid_helo_hostname reject_non_fqdn_helo_hostname
smtpd_pw_server_security_options = cram-md5,gssapi
smtpd_recipient_restrictions = permit_sasl_authenticated permit_mynetworks reject_unauth_destination check_policy_service unix:private/policy permit
smtpd_sasl_auth_enable = yes
smtpd_tls_CAfile = /etc/certificates/server.moremoremore.it.A358901573EE7B9B4D489725407934780D24D5 36.chain.pem
smtpd_tls_cert_file = /etc/certificates/server.moremoremore.it.A358901573EE7B9B4D489725407934780D24D5 36.cert.pem
smtpd_tls_exclude_ciphers = SSLv2, aNULL, ADH, eNULL
smtpd_tls_key_file = /etc/certificates/server.moremoremore.it.A358901573EE7B9B4D489725407934780D24D5 36.key.pem
smtpd_use_pw_server = yes
smtpd_use_tls = yes
tls_random_source = dev:/dev/urandom
unknown_local_recipient_reject_code = 550
virtual_alias_maps =
server:Data admin$

if this could help:
mail:setStateVersion = 1
mail:readWriteSettingsVersion = 1
mail:connectionCount = 11
mail:servicePortsRestrictionInfo = _empty_array
mail:protocolsArray:_array_index:0:status = "ON"
mail:protocolsArray:_array_index:0:kind = "INCOMING"
mail:protocolsArray:_array_index:0:protocol = "IMAP"
mail:protocolsArray:_array_index:0:state = "RUNNING"
mail:protocolsArray:_array_index:0:error = ""
mail:protocolsArray:_array_index:1:status = "ON"
mail:protocolsArray:_array_index:1:kind = "INCOMING"
mail:protocolsArray:_array_index:1:protocol = "POP3"
mail:protocolsArray:_array_index:1:state = "RUNNING"
mail:protocolsArray:_array_index:1:error = ""
mail:protocolsArray:_array_index:2:status = "ON"
mail:protocolsArray:_array_index:2:kind = "INCOMING"
mail:protocolsArray:_array_index:2:protocol = "SMTP"
mail:protocolsArray:_array_index:2:state = "RUNNING"
mail:protocolsArray:_array_index:2:error = ""
mail:protocolsArray:_array_index:3:status = "ON"
mail:protocolsArray:_array_index:3:kind = "OUTGOING"
mail:protocolsArray:_array_index:3:protocol = "SMTP"
mail:protocolsArray:_array_index:3:state = "RUNNING"
mail:protocolsArray:_array_index:3:error = ""
mail:protocolsArray:_array_index:4:status = "OFF"
mail:protocolsArray:_array_index:4:kind = "INCOMING"
mail:protocolsArray:_array_index:4:protocol = "Junk_mail_filter"
mail:protocolsArray:_array_index:4:state = "STOPPED"
mail:protocolsArray:_array_index:4:error = ""
mail:protocolsArray:_array_index:5:status = "OFF"
mail:protocolsArray:_array_index:5:kind = "INCOMING"
mail:protocolsArray:_array_index:5:protocol = "Virus_scanner"
mail:protocolsArray:_array_index:5:state = "STOPPED"
mail:protocolsArray:_array_index:5:error = ""
mail:startedTime = "2013-01-21 21:18:32 +0000"
mail:logPaths:IMAP Log = "/Library/Logs/Mail/mailaccess.log"
mail:logPaths:Server Log = "/Library/Logs/Mail/mailaccess.log"
mail:logPaths:POP Log = "/Library/Logs/Mail/mailaccess.log"
mail:logPaths:SMTP Log = "/var/log/mail.log"
mail:logPaths:Migration Log = "/Library/Logs/MailMigration.log"
mail:logPaths:Virus Log = "/Library/Logs/Mail/clamav.log"
mail:logPaths:Amavisd Log = "/Library/Logs/Mail/amavis.log"
mail:logPaths:Virus DB Log = "/Library/Logs/Mail/freshclam.log"
mail:imapStartedTime = "2013-01-21 21:18:34 +0000"
mail:servicePortsAreRestricted = "NO"
mail:state = "RUNNING"
mail:postfixStartedTime = "2013-01-21 21:18:32 +0000"

Voice command for Contacts doesn't work after a re...

Voice command for Contacts doesn't work after a reboot or a contacts restore.
Steps to reproduce:
1. Backup contacts. Open Files > Backup & Restore > Select Contact for Backup Contents and select Back up now.
2. Edit/save a contact, press and hold the call button, speak contacts name. The voice recognition works fine.
3. Restore contacts. Open Files > Backup & Restore > Select Contact for Backup Contents and select Restore.
4. Reboot phone when prompted.
5. Press and hold the call button, speak contacts name. The voice recognition does not work.
Work around:
Edit and save each contact.
Additional Information:
Social integration with contacts also does not work after a reboot. The facebook icon and "See what xxx is up to on Facebook" is not displayed. The same work around "Edit and save each contact" also applies. This occurs using the Nokia N8 and Nokia 808 Pureview.

Nancy2015 wrote:
I have my phone paired with my car, I can do everything except it does not recognize any of my contact names. If I try say a contact name, it says "not recognized" but if I say the contacts phone number, the name pops up onthe display in my car.
Has anyone had this issue, is there a setting I am missing in my phone?
Hello,
This is not necessarily and issue with the phone. It could also be an issue with the car`s bluetooth software that is only limited to some functions like reading your contacts list, last calls, missed calls, etc. which is most likely the basic 2.0 version.
The Z30 has the 4.0 version that has a lot more communication capability but if the car`s bluetooth its a lower version, then you will not be able to take full advantage of it unless you upgrade the bluetooth software in your car. Call your dealer and inquire about the bluetooth software upgrade in your car

Imessage doesn't work after the installation of the update 6.0

imessage doesn't work after the installation of the update 6.0

iMessage will not work until it's activated.
Switch iMessage OFF. Double tap Home button and delete Messages in multitask-bar.
Do a reset (Hold Sleep/Wake and Home buttons about 10 secs or more till Apple logo appears, ignore the Slide to Power Off that appears)
Note: You will not lose any data.
Switch iMessage back ON.

Display doesn't work after sleeping.

Similar Messages

Maybe you are looking for