Net-auto-wireless isn't really doing anything

I've got netcfg installed and I'm trying to use it for my wifi configuration on my laptop which has an ath9k wireless chip.
I've got my profiles (WPA personal) setup just fine, when I do netcfg my.profile.name it brings it up and it works. However if my wireless drops for whatever reason, or I come to work, I always have to manually do "netcfg profile".
In my rc.conf I have nothing in INTERFACES (only have wlan0 on this machine), I have WIRELESS_INTERFACE defined as wlan0, I have two profiles in NETWORKS, and I have "syslog-ng hal net-auto-wireless netfs crond" in my DAEMONS list.
Can anyone see anything that I'm doing wrong? How does net-auto-wireless actually work?

Okay I can't get it to automatically connect neither to wired no wireless network.
ifplugd at least is trying to connect to networks, I can see in /var/log/everything that but wpa_actiond simply sits there silently and does nothing.
When run manually, either via rc.d/net-auto-wireless or directly, it connects to a wireless access point immediately. No problem here.
So, basically I had gone through the following scenario today. Went to work office, plugged in ethernet cable, ifplugd tried to connect to any of the networks specified in the profiles but failed to for whatever reason. No meaningful explanation. All it said was this:
Jan 27 09:44:57 localhost ifplugd(eth0)[27597]: ifplugd 0.28 initializing.
Jan 27 09:44:57 localhost ifplugd(eth0)[27597]: Using interface eth0/00:13:77:49:00:BE with driver <8139too> (version: 0.9.28)
Jan 27 09:44:57 localhost ifplugd(eth0)[27597]: Using detection mode: SIOCETHTOOL
Jan 27 09:44:57 localhost ifplugd(eth0)[27597]: Initialization complete, link beat detected.
Jan 27 09:44:57 localhost ifplugd(eth0)[27597]: Executing '/etc/ifplugd/netcfg.action eth0 up'.
Jan 27 09:44:57 localhost ifplugd(eth0)[27597]: client: up
Jan 27 09:44:57 localhost ifplugd(eth0)[27597]: client: loadin ho-eth
Jan 27 09:45:09 localhost ifplugd(eth0)[27597]: client: :: ho-eth up [BUSY] > DHCP IP lease attempt failed.
Jan 27 09:45:09 localhost ifplugd(eth0)[27597]: client: [FAIL]
Jan 27 09:45:09 localhost ifplugd(eth0)[27597]: client: loadin pdp-wifi
Jan 27 09:45:09 localhost ifplugd(eth0)[27597]: client: loadin st-mt
Jan 27 09:45:09 localhost ifplugd(eth0)[27597]: client: loadin home-wifi
Jan 27 09:45:09 localhost ifplugd(eth0)[27597]: client: loadin sc-eth
Jan 27 09:45:09 localhost ifplugd(eth0)[27597]: client: loadin st-eth
Jan 27 09:45:09 localhost ifplugd(eth0)[27597]: client: loadin st-wifi
Jan 27 09:45:09 localhost ifplugd(eth0)[27597]: client: loadin uncle-wifi
Jan 27 09:45:09 localhost ifplugd(eth0)[27597]: Program execution failed, return value is 1.
Jan 27 09:47:39 localhost ifplugd(eth0)[27597]: Executing '/etc/ifplugd/netcfg.action eth0 down'.
Jan 27 09:47:39 localhost ifplugd(eth0)[27597]: Program execution failed, return value is 1.
Jan 27 09:47:39 localhost ifplugd(eth0)[27597]: Exiting.
So, I had to do netcfg -u $PROFILE to set up network connection manually. Then I went back home, where I use wireless ap to connect to the home LAN, I saw ifplugd detect that ethernet had been down so it properly unconfigured eth0, again /var/log/everything clearly stated that
Jan 27 14:03:00 localhost ifplugd(eth0)[28240]: Link beat lost.
Jan 27 14:03:11 localhost ifplugd(eth0)[28240]: Executing '/etc/ifplugd/netcfg.action eth0 down'.
Jan 27 14:03:11 localhost ifplugd(eth0)[28240]: Program execution failed, return value is 1.
but nothing was happening for wireless interface at all. This was registered in the log when I got bored with netcfg/wpa_actiond not doing my job for me so I ran /etc/rc.d/net-auto-wireless restart which configured wireless network connection:
Jan 27 14:12:59 localhost wpa_actiond[4401]: Starting wpa_actiond session for interface 'wlan0'
Jan 27 14:13:00 localhost wpa_actiond[4401]: Interface 'wlan0' connected to network '$ESSID'
I think my configuration is correct but well I could've missed something of course. So, to save us time:
- all profiles are in /etc/network.d/. one of these looks like this:
% cat /etc/network.d/home-wifi
CONNECTION='wireless'
DESCRIPTION='A simple WPA encrypted wireless connection using a static IP'
INTERFACE='wlan0'
SECURITY='wpa'
ESSID='$ESSID'
KEY='$KEY'
IP='static'
IPCFG=('addr add dev wlan0 $CIDR/IP brd +' 'route add default via $IP')
DNS=('$IP')
POST_UP="sh /home/$USER/scripts/netcfg-home-post"
- /etc/rc.conf:
# net-auto-wireless support
WIRELESS_INTERFACE="wlan0"
WIRED_INTERFACE="eth0"
DAEMONS=(... !network @net-profiles net-auto-wireless net-auto-wired ...)
no ROUTES, no INTERFACES. Clean and neat. No syntax errors.
Software installed:
ifplugd 0.28-7
wpa_actiond 1.1-1
netcfg 2.5.4-1
So far the problem is that ifplugd can't connect to a wired network, but at least it attempts to, while wpa_actiond does nothing at all.
I really want my laptop to do this automatically. It's like... you know... 2011 already! Computers must do this stuff xD

Similar Messages

Wpa_actiond & net-auto-wireless config ?

Hi,
as documentation of roaming network configuration is rather sparse I'm looking for an advice here.
How can I set to use my roaming networks info stored in /etc/wpa_supplicant/wpa_supplicant.conf ? WPA_CONF option from /etc/network.d/interfaces/wlan0 is ignroed and wpa_supplicant is started with an empty configuration. In other words where does net-auto-wireless look for a configuration ?
My wireless card Broadcom BCM4313 requires to be unblocked with rfkill on two devices (phy0 and wireless). May it be done with just netcfg options as RFKILL and RFKILL_NAME is probably parsed only once ? With PRE_UP and POST_DOWN actions ?
Thanks.
David

Touching wpa supplicant configuration isn't needed. You just need to set profiles for all networks you want to connect to in /etc/conf.d/netcfg/ (check examples file in that dir). Then you specify wireless interface in /etc/conf.d/netcfg.
Do not set AUTO_PROFILES var if you want all of the profiles to be probed. And that should do it.
I don't think you need to use PRE and POST vars because net-auto should take care of rfkill automaticaly if it's configured in /etc/network.d/interfaces/wlan0 (I believe you have already done that).

Net-auto-wireless priorities?

Hey there,
I've got an annoying problem with netcfg/net-auto-wireless and hope you can help me out.
Basically, I have a wireless network at home, but there is also the university network. I use a wireless-wpa config for my home network and wireless-wpa-configsection for the university network (since it needs fancy stuff like certificates and such ).
The problem is that net-auto-wireless seems to favor the university network, although the signal strength is much stronger for my home network. I do not know why this happens - maybe wireless-wpa-configsection entries have a higher priority than wireless-wpa? I would really appreciate it however if anyone could tell me how to get net-auto-wireless to use my home network first when it is available, and only use the university network when the home network isn't there. Any way to do this?
Cheers,
Natanji

Hey there,
I've got an annoying problem with netcfg/net-auto-wireless and hope you can help me out.
Basically, I have a wireless network at home, but there is also the university network. I use a wireless-wpa config for my home network and wireless-wpa-configsection for the university network (since it needs fancy stuff like certificates and such ).
The problem is that net-auto-wireless seems to favor the university network, although the signal strength is much stronger for my home network. I do not know why this happens - maybe wireless-wpa-configsection entries have a higher priority than wireless-wpa? I would really appreciate it however if anyone could tell me how to get net-auto-wireless to use my home network first when it is available, and only use the university network when the home network isn't there. Any way to do this?
Cheers,
Natanji

Net-auto-wireless roaming with suspend

I didn't really know how to name this thread, but I think the gist of it is up there.
I bring my laptop to school and back every day, and use different wireless networks in each place.
I use net-auto-wireless (n-a-w) to connect on boot, but after suspending, and resuming in the new location I have to manually restart the daemon to get a connection back. I'm not sure if n-a-w is supposed to handle this use case, or if there is a better way to handle it.
Any tips?

Those of you have net-auto-wireless, please stop saying "me too" and provide relevant logs from wpa_* stuff. When you suspend, wpa_supplicant deauthenticates -- what is the reaction of wpa_actiond? For example:
dhcpcd[852]: wlan0: removing interface
wpa_actiond[674]: Interface 'wlan0' disconnected from network 'lsusecure'
After you wakeup the machine in a different location, is there a profile corresponding to your previous network in /run/network/profiles/?
@tomk:
I used net-profiles until very recently (when switched to net-auto-wireless) and suspend worked out of the box... you should probably investigate your problem further.
Also, putting a script into /etc/pm/sleep.d which stops net-auto-wireless will cure the suspend problem...

Netcfg net-auto-wireless

I am having a problem with netcfg's net-auto-wireless daemon. I am starting the daemon from my daemons array in /etc/rc.conf when I boot. However, some of my wireless network configs in /etc/network.d are symlinks to files on a encrypted drive which is only mounted after I login. So at the time net-auto-wireless is started those symlinks are not valid.
I expected that net-auto-wireless would automatically "recover" after login and connect to a wireless network using the now valid symlinked configs, but this is not the case. net-auto-wireless will not connect at sit there doing nothing.
Is there a way to make net-auto-wireless connect to a wireless without having to restart the daemon?
Thanks,
Daniel
Last edited by daba (2012-07-15 16:48:01)

If you bring up the netcfg connection manually/in a login script after that mount, maybe the daemon resumes watching by itself.

Netcfg: net-auto-wireless missing

Maybe I just don't know the actual reason, but can someone tell me why netcfg installs net-auto-wired into /usr/bin but not net-auto-wireless? To get it to work I've been having to copy it into /usr/bin. Is there something else I should be doing?

http://mailman.archlinux.org/pipermail/ … 15241.html
Last edited by skottish (2011-08-28 19:39:24)

It is plugged in, why isn't it doing anything?

i just reset my ipod and the screen has the plug in to wall icon on it, so i did but it doesn't go away what do i do? it has been plugged into the wall for 2 whole days and nothing has changed. i know that it recognizes that is it plugged into the wall but now what?

Welcome to Apple Discussions!
Have you tried resetting your iPod?
Reset your iPod
Does your iPod charge when you connect it to your
computer's USB port?
Can your iPod restore through the iPod Updater if you
try to?
Restoring your iPod
If your iPod just isn't charging (even after the
reset), then is this Apple article helpful?
iPod won't charge correctly
I hope this info helps!
-Kylene
I have a similar problem, except after I reset my iPod (when it is connected to the Wall adapter) it charges. But when i go to connect my iPod to my computer, it doesnt charge, and again i have to reset my iPod again so the computer recognizes it. This is quite annoying. is there anyway I can avoid this? I was able to charge my iPod without a hassle a couple of weeks ago, but now when i got a wall adapter this probelem is a recurrent.

Comp isnt really doing anything

i had a memory stick problem, just got the pc working 2 days ago, with 1 256mb stick, the other wont work, yesterday i started it up, but it wont do anything,i hear strange beeps, and a strange click, the second led is green and that reffers to a memory problem, what can i do now? i cant enter the bios, the monitor wont even start up.
memory stick change wont help
please help me
my specs
amd 1ghz
msi k7t 6330 bios ver 3
geforce 2 pro
512mb ram (both 133 but wont work)

is that board with jumper for 100/133 try forcing 100

Netcfg v2.5.2 - note: change in auto wireless config

This release brings a completely new auto wireless/wired configuration. The old net-auto is deprecated and no longer included. There are also some very minor configuration changes that may affect a few people.
Move to new auto-wireless/wired
The new automatic connection has proper roaming support and will prove more reliable than the old setup - particularly with more complicated wireless configurations. To migrate to the new automatic wireless setup:
1. pacman -S core/wpa_actiond
2. Set WIRELESS_INTERFACE="" to your wireless interface in /etc/rc.conf.
For example WIRELESS_INTERFACE="wlan0"
3. Add net-auto-wireless to your DAEMONS=() array.
Note: wpa-config profiles do not work with this, convert them to wpa-configsection profiles. An example is included in
/etc/network.d/examples/
The new auto-wired uses similar configuration - follow the above instructions except use the net-auto-wired daemon, and WIRED_INTERFACE configuration option.
New features:
- net-auto-wireless/wpa_actiond - Real wireless roaming/auto connection. Based on same principle as autowifi. Requires optional dependency: wpa_actiond
- net-auto-wired - automatic ethernet configuration. Requires optional dependency: ifplugd
- Interface configurations - set options for all profiles using an interface
- Output hooks
- Internal cleanup & improvement
Internal changes:
- Uses wpa_supplicant for all wireless configuration by default, including wep/none security. This adds improves support for most and should improve reliability.
- Uses iproute by default for all static configuration. net_tools which contains ifconfig is effectively obsolete and hasnt seen a release for over 8 years. The 'ethernet-iproute' and 'ethernet' connection types have been merged together to simply 'ethernet'. All options are still supported and existing configurations will continue to work for both types. A symlink has been made to ensure that profiles using 'ethernet-iproute' will continue to function.
Changes in configuration syntax
- net-auto and AUTO_NETWORKS is now deprecated in favour of net-auto-wireless/net-auto-wired.
- wireless: If you were previously specifying the wpa_supplicant driver in WPA_OPTS, you now need to specify it in WPA_DRIVER.
- wireless: iwconfig based configuration for wep/none can be used by changing to wep-old or none-old. This should not be necessary and is left in place only for the possibility of very old drivers that do not
support wpa_supplicant.
- ethernet-iproute: As 'ethernet' is now iproute based, those using 'ethernet-iproute' can revert the name. There is a symlink in place, so existing configurations of either name will continue to function
regardless.
- wireless-dbus: Unsupported. The wpa_supplicant dbus interface isn't particularly well documented and it doesn't fit well into the netcfg codebase. There is a symlink in place so that configurations using wireless-dbus will continue to function using the 'wireless' connection scripts.
Download:
netcfg 2.5.2 is in [core].
Source: ftp://ftp.archlinux.org/other/netcfg/ne … 5.2.tar.gz
PKGBUILD: In subversion
Documentation:
http://wiki.archlinux.org/index.php/Network_Profiles
Contributors:
I had a few big contributors to this release:
Jim Pryor: Many internal changes and improvements
Thomas Bächler: wpa_actiond based auto roaming/connection
Thanks guys!
Future Plans:
* Complete non-Arch support
* Redo rfkill using the 'rfkill' tool in the repos
* Fix bugs
Bugs:
On the bug tracker as always.
Last edited by iphitus (2010-02-18 11:22:41)

I continued to have difficulty connecting to my default wireless network, but I eventually figured out why. I seem to recall netcfg used to not care if a POSTUP command failed. I read somewhere that now it does.
So once I got that taken care of, I experimented with net-auto-wireless. It fails for me with no error message.
Being a bit of a tinkerer, I looked into the net-auto-wireless script. I found this line...
/usr/bin/netcfg-wpa_actiond "${WIRELESS_INTERFACE}" >/dev/null
...Removed the >/dev/null, and ran it again.
$ sudo /etc/rc.d/net-auto-wireless start
:: Starting netcfg auto-wireless mode for interface wlan0 [BUSY]
eth-xover
eth-hc
wifi-home
wifi-rounds
wifi-rollingst
wifi-kevin
eth-dhcp
Line 12: WPA-PSK accepted for key management, but no PSK configured.
Line 12: failed to parse network block.
Line 22: WPA-PSK accepted for key management, but no PSK configured.
Line 22: failed to parse network block.
Failed to read or parse configuration '/tmp/wpa.wlan0/wpa.conf'.
[FAIL]
...And now that I think about it, I bet it's because I didn't set security="none" in the open network profiles.
...Yep, that was it.
Last edited by aaaantoine (2010-02-21 01:03:02)

[Solved] net-auto-wired and ifplugd failing to work

Having installed Arch successfully on one machine I then move to another, so I've just got a fresh install with nothing else.
Using netcfg and ifplugd to manage network interfaces (trying to, did same process and it worked okay on other computer), however systemctl status of net-wired-auto gives:
net-auto-wired.service - Provides automatic netcfg wired connection
Loaded: loaded (/usr/lib/systemd/system/net-auto-wired.service; enabled)
Active: active (running) since Wed 2013-03-13 14:00:22 GMT; 12min ago
Main PID: 259 (ifplugd)
CGroup: name=systemd:/system/net-auto-wired.service
└─259 /usr/bin/ifplugd -i enp7s0 -r /etc/ifplugd/netcfg.action -fIns
Mar 13 14:00:22 alexpc systemd[1]: Started Provides automatic netcfg wired connection.
Mar 13 14:00:22 alexpc ifplugd[259]: ifplugd 0.28 initializing.
Mar 13 14:00:22 alexpc ifplugd[259]: Using interface enp7s0/8C:89:A5:37:9F:51 with driver <r8169> (version: 2...-NAPI)
Mar 13 14:00:22 alexpc ifplugd[259]: Using detection mode: SIOCETHTOOL
Mar 13 14:00:22 alexpc ifplugd[259]: Initialization complete, link beat not detected.
Mar 13 14:00:25 alexpc ifplugd[259]: Link beat detected.
Mar 13 14:00:26 alexpc ifplugd[259]: Executing '/etc/ifplugd/netcfg.action enp7s0 up'.
Mar 13 14:00:26 alexpc ifplugd[259]: client: up
Mar 13 14:00:26 alexpc ifplugd[259]: Program execution failed, return value is 1.
I've checked many times and interface is enp7s0 (only one anyway and no wireless)
Running
dhcpcd enp7s0
does work fine and connects me to the network. Also realtek driver (r8269) is being loaded (obv given I can connect to network)
Contents of /etc/conf.d/netcfg
# Enable these netcfg profiles at boot time.
# - prefix an entry with a '@' to background its startup
# - set to 'last' to restore the profiles running at the last shutdown
# - set to 'menu' to present a menu (requires the dialog package)
# Network profiles are found in /etc/network.d
NETWORKS=(last)
# Specify the name of your wired interface for net-auto-wired
WIRED_INTERFACE="enp7s0"
# Specify the name of your wireless interface for net-auto-wireless
WIRELESS_INTERFACE="wlan0"
# Array of profiles that may be started by net-auto-wireless.
# When not specified, all wireless profiles are considered.
#AUTO_PROFILES=("profile1" "profile2")
I can use dhcpcd service and it works fine - but it would be nice to use ifplugd/netcfg.
Not really sure what else to try...
Thanks.
Last edited by alexjj (2013-03-15 12:15:46)

I think you may need to also put a config file into /etc/network.d/ - you can copy one of the sample files there and adapt it to your situation.
Also you have to set the correct interface in /etc/ifplugd/ifplugd.conf
You will also need:
systemctl start net-auto-wired
systemctl enable net-auto-wired
Hope this helps.
Last edited by mcloaked (2013-03-13 18:09:55)

My iPad 4 is stuck on the connect to iTunes screen. Have held the home button down while connecting the USB cable to the iPad and its not doing anything, not even showing up under my computer Please Help

IiPad is stuck in the iTunes connect screen. I have held the home button down while plugging the iPad in and still nothing. Hard reset isn't even doing anything. It's not even showing up under my computer. Please Help

Did you get a message that the iPad is disabled?
iOS: Device disabled after entering wrong passcode
http://support.apple.com/kb/ht1212
Using iPhone/iPad Recovery Mode
http://ipod.about.com/od/iphonetroubleshooting/a/Iphone-Recovery-Mode.htm
Saw this solution on another post about an iPad in a school enviroment. Might work on your iPad so you won't lose everything.
~~~~~~~~~~~~~
‘iPad is disabled’ fix without resetting using iTunes
Today I met my match with an iPad that had a passcode entered too many times, resulting in it displaying the message ‘iPad is disabled – Connect to iTunes’. This was a student iPad and since they use Notability for most of their work there was a chance that her files were not all backed up to the cloud. I really wanted to just re-activate the iPad instead of totally resetting it back to our default image.
I reached out to my PLN on Twitter and had some help from a few people through retweets and a couple of clarification tweets. I love that so many are willing to help out so quickly. Through this I also learned that I look like Lt. Riker from Star Trek (thanks @FillineMachine).
Through some trial and error (and a little sheer luck), I was able to reactivate the iPad without loosing any data. Note, this will only work on the computer it last synced with. Here’s how:
1. Configurator is useless in reactivating a locked iPad. You will only be able to completely reformat the iPad using Configurator. If that’s ok with you, go for it – otherwise don’t waste your time trying to figure it out.
2. Open iTunes with the iPad disconnected.
3. Connect the iPad to the computer and wait for it to show up in the devices section in iTunes.
4. Click on the iPad name when it appears and you will be given the option to restore a backup or setup as a new iPad (since it is locked).
5. Click ‘Setup as new iPad’ and then click restore.
6. The iPad will start backing up before it does the full restore and sync. CANCEL THE BACKUP IMMEDIATELY. You do this by clicking the small x in the status window in iTunes.
7. When the backup cancels, it immediately starts syncing – cancel this as well using the same small x in the iTunes status window.
8. The first stage in the restore process unlocks the iPad, you are basically just cancelling out the restore process as soon as it reactivates the iPad.
If done correctly, you will experience no data loss and the result will be a reactivated iPad. I have now tried this with about 5 iPads that were locked identically by students and each time it worked like a charm.
~~~~~~~~~~~~~
Try it and good luck. You have nothing more to lose if it doesn't work for you.
 Cheers, Tom

GTX 780 Ti - CUDA selected, but GPU isn't doing anything

I know there's a bunch of posts on the 780 Ti, but I've been researching for days and I'm getting nowhere.
Disclaimer: First let me just quickly say this. I know it's not officially supported and I understand why, so please don't mention that. I'm a long time PC enthusiast and builder and I've worked in technical IT positions for 15 years. I understand liability implications of testing hardware and officially supporting something, and also the implications of using unsupported configurations (like PP maybe randomly crashing, etc). Now, with that said:
The Issue: In PP CC 2014, CUDA is available and it is selected. In fact I never had to select it. It has always been automatically selected when creating new projects. However, my cards aren't doing anything. They're idle 100% of the time.
I've read posts from users and from Adobe stating that unsupported CUDA capable cards will still work as long as the user accepts a message stating that the card isn't supported. However, I don't ever recall getting a message saying anything about my cards being unsupported. I only know about said message because it's been mentioned by Adobe and other users. I'll admit that I may have, in fact, been prompted and clicked accept, or continue, or whatever, but I'm pretty sure I would remember that. I also wouldn't have been surprised to see the 780 Ti missing from the supported cards list, which I only went looking for after learning that it wasn't using my cards.
I've messed with PP settings, NVIDIA settings, uninstalled/reinstalled drivers, older drivers, beta drivers, uninstall/reinstall PP CC 2014. I read something about deleting the CUDA file so I tried that but I think that's not supposed to be necessary anymore(?)... I'm losing my mind here.
1. I've read that exporting media "only uses the CPU and not the GPU" and I've also read "CUDA GPU acceleration will significantly reduce export times". What's the official answer on this?
2. During sped up playback and reverse playback (normal playback is fine), the CPU is pegged and the GPUs are idle. Shouldn't at least this use the GPUs?
3. I've read that not all effects will or can use CUDA. For example when applying the warp stabilizer to clips, the CPU is pegged and the GPUs are idle. Does that not use CUDA? That seems like a pretty common effect that should be able to use GPUs.
I would really appreciate an official answer as to whether the 780 Ti will work or not - completely ignoring whether it's officially supported. If the answer is "yes, it will (should) work, but something is wrong with your particular setup/configuration" I'm ok with that, but I'm hoping there's a suggestion I haven't found yet, that might help get my cards working.
Thank you very much for any input you can provide.

See the thing is, I've already read that post a dozen times. It seems to be
the de facto response to all these "CUDA isn't working" questions, haha. I
know what CUDA is and how it works. My issue with that page is that it's
four years old, and the only two updates aren't dated and they're vague.
The CUDA capable effects list on that page is just outdated. I've also gone
down several rabbit holes of links starting on that page, which end on
broken links or non-CUDA-related content.
With all that said, that page does specifically mention cropping, scaling,
and exporting as GPU accelerated. In my example, I'm using the warp
stabilizer set to smooth motion - position, scale, rotation, and I'm not
using any crazy export settings, just defaults with 2-pass selected instead
of 1-pass for example.

I updated to ios 5.1, after updating, now my screen is stuck with the apple logo and status bar and isn't doing anything....HELP

I updated to ios 5.1, after updating, now my screen is stuck with the apple logo and status bar and isn't doing anything....HELP

The typical fix if the progress bar totally freezes - meaning no movement at all for more than 20 minutes - and iTunes will no recognize the device - is to try to put the iPad into recovery mode. That is explained here.
iPad: Unable to update or restore
However, don't jump the gun. Keep an eye on the progress bar and if it is moving at all - even very slowly - let it go for a while. I'm updating my iPod touch first and the progress bar is moving but very slowly.

I recently bought the iPad 2 and never really did anything with the cloud on my iPhone 4s and was wondering if I can sync the apps and music on my phone to the iPad wirelessly ?

I recently bought the iPad 2 and never really did anything with the cloud on my iPhone 4s and was wondering if I can sync the apps and music on my phone to the iPad wirelessly ?

Metldr wrote:
I recently bought the iPad 2 and never really did anything with the cloud on my iPhone 4s and was wondering if I can sync the apps and music on my phone to the iPad wirelessly ?
Yes, but that has nothing to do with the cloud.
It is simply wifi syncing between your computer and iPad over your local wifi network

Screen is white and isn't doing anything

My computer froze so did a force shut down. The computer turned back on but the screen is just staying white and isn't doing anything. It has been doing this for over an hour now. I tried turning it off again and it won't even turn off!!! PLEASE HELP I have a ton of homework to get done!

Which os version are you using?

Net-auto-wireless isn't really doing anything

Similar Messages

Maybe you are looking for