Monitor Signal Drops During XP Boot

Hello All!
This is my first post on this forum, so please forgive me if I make any mistakes. I have recently bought a MSI Motherboard, and all was well until I turned my pc on without the monitor plugged in - now, the monitor signal drops during the boot up (at the xp screen when the bar is moving across the screen).
My system setup is this
Athlon xp 2000+
MSI K7n2G Board
Using the on-board graphics
256mb DDR Kingston RAM 27000 (fully compatible with the board)
120 GB Western Digital hard disk
Liteon cd writer 52x 24x 52x
Pioneer 106 DVD writer
I believe I am running BIOS 3.5
I tried booting up in safe mode and that boots up fine. I did a system restore to the day before I accidentally turned the machine on without the monitor plugged in, and that didn’t make any difference.
I am clueless as to why this doesn’t work, and am hoping someone here could tell me how to solve this problem.
Many thanks for any advice, and thanks for reading,
Regards,
Rupz112

I have come across a similar problem before. The problem was that the monitor couldnt support the default resolution of windows XP so I went in safe mode and lowered the resolution and the problem was solved.

Similar Messages

Aspire One D255 monitor shuts off during boot

Every time I boot, immediately after the kernel lauches init, my screen powers off. About 15 seconds later, it comes back on.
The delay before coming back on seems to be independent of the init process. If I speed init up, by the time it comes back on it's waiting at the login prompt. If I slow it down, it comes back on while init is still running.
I tried adding an echo -e -n '\033[13]' to my init scripts in an effort to unblank the display, but it doesn't help.
This happens both booting of the install image and after installation. It makes it extremely hard to figure out what's going on during startup.
Has anyone seen this before?

I have a similar issue with my aspire one, but the display is not turning off, it is actually the backlight turning off during boot. I use fbsplash with a dark theme but a bright progress bar. During boot, it appears as if the screen has turned off, but looking closely, I can still see the progress bar.
I have tried several different methods of keeping the backlight on to no avail.
Personally I am thinking it is monitor signal detection during a monitor mode reset during boot, ie from console resolution switching to KMS resolution. Most monitors lose signal detection when changing mode (in my experience). Some display a "No Signal" message of some sort, some briefly turn off until signal is detected again, and in the Aspire One case, the backlight turns off. Put it down to monitor manufacturers built in power saving "features".
Tha same thing happens when I boot windows.
Of course, if anyone does come up with a solution, I am eagerly listening!
Cheers.

Late 2012 mac mini display signal drops while booting and monitor goes to sleep

I have a new Late 2012 Mac Mini. I have had it for a week, what just started happening is that during restart, the video signal drops and my monitor goes to sleep. I then have to toggle through the input options on the monitor and the video signal is detected again and the monitor wakes up.
Here is what I see - If i shut down and then power back up, I get the grey screen, then the apple logo, then the little status circle spins for a few cycles then stops and then the screen goes black and the monitor says signal lost and then 5 seconds later goes to sleep.
It is possible it is my monitor but, I haven't had any issues with it and i only drops the signal like that during a reboot.

Welcome to the family. Search this forum for the main thread for this problem titled: "mac mini 2012 video blinking out".

LG 34um95 Ultrawide Monitor Not Waking During Boot on 2013 MP

I have a new LG 34um95 ultra-wide monitor that is Mac Pro comparable and has thunderbolt ports. When try to boot on my 2013 Mac Pro using bootcamp and switch between OSX and Windows 8, the monitor is black (both HDMI and on thunderbolt) as if the monitor is not recognized. If I hook up a DVI to MiniDV port to an old school monitor I get a display on that just fine. Anytime I load OSX, the LG monitor is black until the login page - I cannot see the white screen with the apple logo ever except for the old DVI monitor.
I also get random flashes and stutters on the picture of the LG monitor?
I don't know if it's the monitor or the Mac Pro? Already called apple care and they told me to reset the VRam. That did nothing.
Any Help?

Hi,
I have the same issue with this monitor using Thunderbolt on my Late 2013 6-core Mac Pro with D500 GPUs. I get no image displayed until I get past my FileVault login and it takes me to the desktop. I have to enter my password blind as nothing is displayed at all during the boot. This also prevents me from choosing boot drives, or allowing other users to unlock the FileVault. The issue also occurs during a safe boot, and booting into recovery mode. My Mac Pro is running Yosemite, however it hasn't fixed the issue. I have tried a PRAM and SMC reset, however it hasn't changed the issue over Thunderbolt.
I have contacted LG (which is of no use as their support is really terrible), and Apple who actually sent my issue to engineering. However, engineering was only able to assist me with getting the HDMI working again. To get HDMI working, they had me do a PRAM reset with it plugged in using HDMI. They were unable to get the Thunderbolt working though, as the monitor is not officially supported.
I have been unable to find anyway to make the Thunderbolt work correctly on this monitor. This is very disappointing as this monitor is advertised by LG as being supported by the new Mac Pro.

Keynote video signal drops out

Keynote 4 video signal drops out during presentations where we are switching between two different Apple Computers (one G4 and one Intel). Both machines had previous versions of Keynote on them and over a period of time never had a signal drop out condition. Sounds like new version problem.
Any input appreciated.

I have two laptops each with their video out adapter connected and then cabled to a switch box where the big monitors project the signal of the laptop that the swtich box is set to. Like channel selection. Previous versions of Keynote were never a problem and I mean never. The signal came right through but now with Keynote 4 the signal drops out even tho the laptop is still active and apparently sending a signal through its video out connection. I have to hit escape and get out of keynote and then go back to PLAY for keynote to once again send that signal.

I have recently upgraded to Mavericks and I am being subjected to additional password requests and the monitor take store ever to boot up. Approximately 5 mins which is way in excess of previous operating system.

I have recently upgraded to Mavericks and I am being subjected to additional password requests and the monitor take store ever to boot up. Approximately 5 mins which is way in excess of previous operating system.

You may need to rebuild permissions on your user account. To do this,boot to your Recovery partition (holding down the Command and R keys while booting) and open Terminal from the Utilities menu. In Terminal, type: ‘resetpassword’ (without the ’s), hit return, and select the admin user. You are not going to reset your password. Click on the icon for your Macs hard drive at the top. From the drop down below it select the user account which is having issues. At the bottom of the window, you'll see an area labeled Restore Home Directory Permissions and ACLs. Click the reset button there. The process takes a few minutes. When complete, restart.
Repair User Permissions
Startup Issues - Resolve
Startup Issues - Resolve (2)

Airplay video signal drops

We have 7 Apple TV's throughout our company and all of them exhibit the same behaviour, on many different laptops.
All laptops are running minimum of OS 10.9.2.
We have a Cisco Clean Air WiFi network with excellent signal coverage in all areas surrounding each of the AirPlay devices.
Here's exactly what happens:
User will enter conference room with Apple TV connected to an LED Flat Panel TV. Power it up, then select the appropriate Airplay device from their Airplay menu and begin streaming mirroring their desktop to the television set. Within 2 minutes, the signal drops, forcing the user to re-select the airplay device once again. Usually it will drop again within 2 minutes.
If the user reboots the Apple TV, the issue will go away for the rest of the session. Perhaps something about the Apple TV's keeping a sustained connection to our WiFi network.
We've been working with Cisco to pour over our WiFi network but they cannot find anything from the WiFi gear that is contributing to the signal loss.
Anyone have any ideas here? I'd like to try an Apple TV alternative to see if a different device would have the same issue but the options seem extremely limited.
Thank you.

I have two laptops each with their video out adapter connected and then cabled to a switch box where the big monitors project the signal of the laptop that the swtich box is set to. Like channel selection. Previous versions of Keynote were never a problem and I mean never. The signal came right through but now with Keynote 4 the signal drops out even tho the laptop is still active and apparently sending a signal through its video out connection. I have to hit escape and get out of keynote and then go back to PLAY for keynote to once again send that signal.

Help! Frames Dropped During Live Capture

I am trying to switch over to Adobe Premiere from Final Cut Pro, but am having a serious problem with frames being dropped during capture. When I do have frames dropped, it doesn't even save the video that it was capturing. All that I get is a corrupt file that won't open.
I'm using a Mac Pro with 3.0Ghz Dual Core Xeon Processor, 9GB 667MHz RAM, and a BlackMagic Decklink SDI card, and am trying to capture 720p 59.94fps video over SDI. I am capturing to an interal 1TB 7200RPM dedicated scratch disk that is not used for ANTYHING but live capture. The OS is 10.6.8.
I only have 3 capture options in Premiere using the Blackmagic card: 8-bit, 10-bit or DVCHDPRO. I want to use 8-bit, because DVCHDPRO is 960x720 instead of 1280x720. But, I have tried DVCHDPRO and it did not work either. I can successfully capture video for 5-10 minutes, but then I always get the Warning that frames were dropped and Premiere fails to save the video properly so that it can be opened.
I have used BlackMagic's speed test app and determined that my internal hard drive's data rate is plenty sufficient for both 8-bit and DVCHDPRO.
Final Cut Pro 6 has always captured perfectly fine using this exact setup. It even gives me a lot more capture options for the BlackMagic card - I'm not sure why I'm limited to only those 3 capture settings in Premiere.
I would really appreciate some help to point me in the right direction to get this resolve. Thanks!

Randal,
It might be a bit tough on a fast computer, especially if the BIOS are not set to show POST at boot-up, a common setting nowadays. As Steve says, the exact key will differ by your BIOS brand.
You may not actually see the particular logo screen, that Steve is talking about. I'd do a cold-boot and immediately tap the ESC key. If this does not get you into your BIOS Setup, then repeat, but tap the F1 key. When I say "immediately," I mean immediately upon hitting the Power On button.
With older computers, you had about 5 sec. to get into Setup, but not anymore. On my laptop, I still have trouble hitting the F8 key fast enough to boot Windows into Safe Mode. I miss it, more than I get it. Could also be that I've been away from gaming for too many decades, and my gunfighter reflexes ain't what they used to be, but I'll just blame it on faster computers. I have the same problem with trying to flush my Preferences in Adobe programs, gotta' hit the Shift-Ctrl-Alt key at precisely the right time. [Exact key combo does differ with some Adobe programs]
Also, if you can give us the name of your BIOS, say "Award," we might be able to give the exact key to hit for Setup. If you have the MoBo manual, it will be in there, plus the correct key. You still have to be quick, however.
Good luck,
Hunt

Mac Pro won't send monitor signal

Was checking my email and a Word doc, when I got the grey screen of death... that one that comes down like a windowshade and tell you to re-start.
When I restarted, get no monitor signal out of either DVI. I think it's booting up, but my Cinema Display is totally black, with LED flashing 3 short flashes. I also tried hooking it up to an older Studio Display... still a dark screen.
I was able to use another Mac to look at my HD in targeted disk mode... it seemed OK.
Re-set PRAM and SMC, but no luck.
Any quick fixes I'm missing here... or is my graphics card shot?

Does it do the same thing if you try to boot from the system installation disk? If so, then you probably have a hardware problem. What you experienced was a kernel panic, and those are more likely to be caused by a logic board or CPU problem rather than a display adapter failure, though there's no way for me to be sure what component might have failed. If it won't work from the system installer disk either, then you'll have to get the system in for servicing, most likely. You can try reseating the RAM and display card and see if that makes any difference.
Good luck.

IPhone 6 freezing after WiFi signal drops

Anyone else having recurring OS freezing and hanging problems after a sudden WiFi signal drop?
The phone seems fine on WiFi for a period of time, sometime hours, sometimes days but then all of a sudden the signal strength drops to one and everything goes crazy. Trying to turnoff WiFi from the control center doesn't have any effect (it looks like it's off but the wifi indicator remains on). If I try an go into the settings app, it comes up as a blank white page and hangs. Sometimes I can go back to the home screen, sometimes not but the phone will freeze up solid or eventually reboot. If it reboots or I do a hard reset the wifi switch is grayed out and can not be enabled.
If I perform another hard reset the wifi switch will sometimes be accessible again but the phone seem unstable. It will reboot randomly or simply freeze up. The last time it froze on the apple boot screen and I had to put the phone into recovery mode to restore it.
I have iOS 8.1.1 installed and have done a dozen hard resets and restored as a new phone from iTunes twice in the past week. It's driving me nuts because the phone just seems unstable.

I have reset the modem everytime this happened. That is why I believe this could be a software problem between iOS 8 or iPhone 6 wifi and the band in which the airport express communicates.
Today I have disabled the airport express and began using the wifi from the HUB of my internet provider. So far no drops on wifi signal no freezing, no crashing. Connectivity seems much faster and clean now. Lets hope it keeps this way.

Airport Signal Dropping

When I boot up I have full strength, then when I go to a web page the page loads and then the signal will drop. I reset airport and get full strength. I go to another page and the signal drops again and I reset and get full strength. I do this several times and the signal finally stays at full strength.
Is changing channels something that might fix this?
Thanks

You should probably check out the other threads here on wireless performance issues with the Macbook. This has been a big problem for many people.

[solved] Large number of services enabled during first boot

I just set up Arch Linux on a VM and was surprised to see a large number of services enabled in systemd during the first boot, including ftpd! I have set up several Arch Linux installations before, and have never encountered this before.
To be sure, I installed a second time. While still booted in the install ISO, I checked and verified that only a few services were enabled. After the first boot into the system, sure enough, a large number of services were enabled.
Any ideas as to what might be causing this?
Edit #1: found the following in journalctl. It looks like a bunch of packages are missing systemd preset files, and services that are missing preset files are enabled by default.
Edit #2: filed a bug report: https://bugs.archlinux.org/task/41711
Edit #3: until this is fixed, a workaround is to get systemd-214-2 from ARM and downgrade to that before your first boot into the new installation. After you've booted, you should be able to upgrade back to the current systemd and have everything work out.
Edit #4: Fixed in systemd-216-3. If you installed and rebooted prior to 216-3 hitting [core], see here for a proper fix.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about iptables.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-root-fs.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable systemd-networkd-wait-online.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about busnames.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-remount-fs.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kpropd.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about nscd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-setup-dev.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-done.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rsyncd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rlogin.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udev-trigger.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sys-kernel-config.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable systemd-journal-gatewayd.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about gpm.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about paths.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-remote.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about system-update.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-wall.path, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about quotaon.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-setup.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about final.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-initctl.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about talk.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-modules-load.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udevd-kernel.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about proc-sys-fs-binfmt_misc.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about nss-lookup.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about local-fs.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-switch-root.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dev-mqueue.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kpropd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-parse-etc.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-reboot.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about updatedb.timer, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.resolve1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kadmind.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-update-utmp.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about ftpd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kdc.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journald.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about graphical.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sshd.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-sysusers.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sys-kernel-debug.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-vconsole-setup.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about ldconfig.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable console-shell.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-console.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about machine.slice, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-flush.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rescue.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.timedate1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about proc-sys-fs-binfmt_misc.automount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-firstboot.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-catalog-update.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sockets.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-hybrid-sleep.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-initctl.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about cryptsetup-pre.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-resolved.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-hibernate.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-wall.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-logind.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sys-fs-fuse-connections.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-update-done.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about emergency.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about slices.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about iptables.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about logrotate.timer, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-quotacheck.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about tmp.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dm-event.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-done.timer.
Aug 27 02:53:41 host systemd[1]: Preset file says disable console-getty.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-localed.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about printer.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-clean.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journald.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-shutdownd.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about uuidd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.locale1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rsh.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-timesyncd.service.
Aug 27 02:53:41 host systemd[1]: Preset file says disable kexec.target.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-collect.service.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-drop.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about suspend.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about mkinitcpio-generate-shutdown-ramfs.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable [email protected].
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-update-utmp-runlevel.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about cryptsetup.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-fs.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about smartcard.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dbus.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-console.path, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-random-seed.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about uuidd.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about basic.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about remote-fs-pre.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dhcpcd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about logrotate.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sshdgenkeys.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-fsck-root.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about fstrim.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-suspend.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about swap.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.login1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-replay.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journald-dev-log.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about timers.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable rescue.target.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about user.slice, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-sysctl.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about fstrim.timer, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sysinit.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about hybrid-sleep.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dev-hugepages.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udev-hwdb-update.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-upload.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-shutdownd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about emergency.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-user-sessions.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sound.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable poweroff.target.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dbus.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable systemd-journal-gatewayd.socket.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about talk.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable remote-fs.target.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about shadow.timer, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about system.slice, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about bluetooth.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable syslog.socket.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about getty.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-kexec.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable halt.target.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about -.slice, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about network-online.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sleep.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dm-event.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-clean.timer, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about kmod-static-nodes.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about multi-user.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.machine1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about hibernate.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-networkd.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about nss-user-lookup.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-halt.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about umount.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about network.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-timedated.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udevd-control.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about ip6tables.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sshd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about time-sync.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about updatedb.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sigpwr.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-poweroff.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-udevadm-cleanup-db.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rpcbind.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about shadow.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about network-pre.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-switch-root.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable debug-shell.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-hostnamed.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about telnet.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable reboot.target.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.hostname1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rsyncd.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-machined.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about local-fs-pre.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-remote.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udev-settle.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-binfmt.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udevd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about shutdown.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-cleanup.service, enabling.
Aug 27 02:53:41 host systemd[1]: Populated /etc with preset unit settings.
Things enabled before first boot (based on contents of /etc/system/systemd/*.wants):
getty.target.wants:
* [email protected]
multi-user.target.wants:
* [email protected]
* iptables.service
* remote-fs.target
* sshd.service
sysinit.target.wants:
(none)
Stuff additionally enabled and started during first boot (also based on /etc/system/systemd/*.wants):
default.target.wants:
* systemd-readahead-collect.service
* systemd-readahead-replay.service
multi-user.target.wants:
* dhcpcd.service * krb5-kpropd.service
* fstrim.service * nscd.service
* ftpd.service * rsyncd.service
* gpm.service * systemd-journal-upload.service
* ip6tables.service * systemd-networkd.service
* krb5-kadmind.service * systemd-resolved.service
* krb5-kdc.service
sockets.target.wants:
* krb5-kpropd.socket * systemd-journal-remote.socket
* rlogin.socket * talk.socket
* rsh.socket * telnet.socket
* rsyncd.socket * uuidd.socket
* sshd.socket
sysinit.target.wants:
* dm-event.service
* systemd-timesyncd.service
system-update.target.wants:
* systemd-readahead-drop.service
Explicitly installed packages:
dhcpcd iputils procps-ng systemd-sysvcompat
diffutils linux-grsec psmisc tar
dnsutils logrotate reflector vim-systemd
file mlocate rsync wget
gradm mtr s-nail which
grub openssh screen whois
inetutils pacman
Last edited by tazmanian (2014-09-10 23:11:42)

+1.
Here is the ports these services are listening:
$ ss -tpl
State Recv-Q Send-Q Local Address:Port Peer Address:Port
LISTEN 0 128 *:llmnr *:*
LISTEN 0 128 *:ssh *:*
LISTEN 0 128 :::llmnr :::*
LISTEN 0 128 :::19532 :::*
LISTEN 0 128 :::tell :::*
LISTEN 0 128 :::ssh :::*
LISTEN 0 128 :::telnet :::*
LISTEN 0 128 :::login :::*
LISTEN 0 128 :::shell :::*
LISTEN 0 128 :::rsync :::*
LISTEN 0 128 :::git :::*

Signals drop on iPhone 5s iOS 8.1 both wifi and network

I am having the following problems since i updated to iOS 8.1 on my iPhone 5s 16GB model A1533 :
1- My network signals drop to 3 dots and sometimes to 2 and stay there.
2- Sometimes my wifi disconnects itself on my iphone for almost 4 or 5 seconds
3- My battery is draining faster that ever. I turned off the use of fingerprint and found it useful but still my iphone consumes a lot of battery. I get my battery percentage dropped to 80% from 100% in just 20minutes of whatsapp usage. My fone's vibration is never on. Location services all off except find my iphone. Background app refresh also off. I tried everything. Erase all settings, hard reset etc. NO USE
4- Playing games is really difficult. Battery drains very fast.
I did not have these problems on 7.1.2. Need help
Regards,
Ahmad

I understand that but I hope that people from Apple will be referring to the support groups and may actually think about that last paragraph.

Why does my signal drop every time I try to use an application.

I've got a UFO style 802.11g, which I unfortunately kept up to date with the updates.
For well over a year now I've had my gear set up like this, airport in the den, my wife's older Imac in the den with it, the printer in the den as well and my Imac across the house. Now, everything in the den connects like cake. Always up, always a great signal.
My Imac across the house has always had it's ups and downs, we've got a stone fireplace and out kitchen in between. Basically, it's 3 rooms away. A whole bunch of walls and corners for the signal to bounce off of. So, I know, not an ideal set up. But it's worked ok for a good long time.
So, a few months ago I performed the recommended update. It said that it would increase connection quality. So I thought, hey, this might help me out! At first glance my connection seemed great! I never lost a bar, not while I was looking anyway. Then I started noticing that occasionally I switch a webpage or some such and it would tell me that I wasn't connected to the internet. What? I look up and I've got all the bars, so I try again and get through... then I notice the bars just flat out go dead. Now I can't connect again. Odd.
Ok, so I start paying attention and it just drops out at random... now, the signal used to fluctuate up and down fairly regularly before the update. I'd researched the problem and found out all the things that can interrupt my signal, and basically I've got em all in between my Airport and my Imac. I could live with that, because it would slow down, but it stayed connected for the most part. This was something new.
Ok, back to the problem at hand. Now I see the signal is either all bars or none. No 2 bars, no 3 bars. Here or gone. And while I'm paying attention, I notice that practically every time I click on something, from my mail app to a preview image the signal drops to nothing. Seemed a coincidence at first, but know I'm certain that it isn't.
So, random complete signal loss and complete signal loss when I use and app. Really not pleased.
Ok, so I figured maybe there's a fix on the way, but I've heard nothing of it. I installed the most recent update, absolutely no effect. Oh, and this one too was supposed to provide better connectivity. Where? I'm not seeing it! Everything in the den works just as well as it ever has. That's one of the things I've loved about Mac for more than 10 years. Easy to use and reliable. But this, this is just a big old pain.
I've tried to extend the network unsuccessfully with the Express. I've got another option to try with that, so my fingers are crossed. But I just don't get why my network is now worse than when I set it up when the only change that's been made have been the updates that I installed at Apple's insistence that my signal would actually be better.
Sorry for being so long winded, and for anyone who made it this far... is there anything that I can do? I really do prefer to have my office in the room that it's in, but it doesn't help me at all when I have to move my Imac to use it online.

This may sound stupid, but I'm gonna throw it out there anyway. Is it possible, that if I have enough junk on my desktop it might disrupt the signal? It seems odd, but it kind of looks like my signal is strong and relatively steady now that I've cleaned my desktop. I do tend to get very cluttered. I use a lot of reference images and save text clippings to use later... it just piles up very quickly.
So, I wonder if all that extra effort my system has to do keeping up with the junk might have something to do with the drop outs?

Why does my signal drops and takes a long time to search and connect when I turn on or off my cellular data? And normal text messages are not getting delivered properly. It shows sent but later it will show try again, Is it just me?

I do not know what the problem is, but after the latest update it is really hard to send text messages. It is taking alot of time to send the messages, it is not the problem with the carrier because sending text messages with the same number in the same area is really easy on my normal nokia 1100. Please suggest me what I should check. Second problem I am facing is the carrier signal drops to nothing when I turn on the cellular data. It has to then search for the network and connect again the same happens when I turn the data off again. Please tell a solution. I do not think it is the problem with the hardware because the phone is hardly 2weeks old and everything was working properly with ios 6. It initaly had problem with the battery on updating to ios7 but that was rectified with the new update but again these are the new issues am facing.

This may sound stupid, but I'm gonna throw it out there anyway. Is it possible, that if I have enough junk on my desktop it might disrupt the signal? It seems odd, but it kind of looks like my signal is strong and relatively steady now that I've cleaned my desktop. I do tend to get very cluttered. I use a lot of reference images and save text clippings to use later... it just piles up very quickly.
So, I wonder if all that extra effort my system has to do keeping up with the junk might have something to do with the drop outs?

Monitor Signal Drops During XP Boot

Similar Messages

Maybe you are looking for