During boot up there is a flashing planet earth symbol

During boot up there is a flashing planet earth symbol and then after a minute or two I get the screen to enter my password. What is causing that and how do I correct the issue? Thank you for your help.

That means it's looking for a Network Disk to connect to. Shut down or restart and hold down the Option key when you hear the chime. This will bring you to a screen showing the available startup volumes. Select the one you usually boot from and continue; it's probably just called Macintosh HD, unless you renamed it. After you finish booting, go into Sys Prefs>Startup Disk and make sure the usual boot volume is selected there.

Similar Messages

My computer keyboard has a bad "M" key so I cannot login into my computer from boot is there a way to bypass the login to reset my macbook pro

my computer keyboard has a bad "M" key so I cannot login into my computer from boot is there a way to bypass the login to reset my macbook pro

Late reply, but if anyone is experiencing the same problem, I've found a solution. For whatever reason, some macbooks don't recognize usb flash drives during the boot-up phase, even though the usb ports themselves are powered (I tested this with a multimeter). The solution then, was to use an external USB hard drive that has its own power supply to install Snow Leopard. I don't know why, but it's the only way I got my macbook (Macbook 2,1/A1181) to recognize the install drive. Every was smooth sailing from there!

T400s Linux/Windows dual boot with Linux from Esata Flash Drive

This project is about a dual boot Windows/Linux system without using the normal dual boot changes in the bootloader of the windows hard drive. When I started this I found bits and pieces of information on the web but no complete description so I wrote this post.
I have done a dual boot system on my previous Thinkpad where I had partitioned the hard drive between Linux and windows. For this project I wanted to leave the windows hard drive absolutely intact and unaltered, and boot Linux from a flash drive in the esata port on the back of the T400s. Obviously this uses the F12 boot list function key to boot from the flash. The advantage of this is that Windows is totally unaltered and when I need Linux, I plug in the esata flash drive, hit F12 during the boot cycle and select booting from the esata flash drive. The reason for Esata rather than USB is simply speed. I have a nice fast Linux installation.
I used the OCZ esata flash drive but suspect any of the alternatives will work. It did not need the accessory usb cable because the Thinkpad powered the esata flash directly.
To boot from the esata drive I had to make the following changes in the bios
    I left the esata flash plugged in as I went into the bios
    Bios>config>Serial ATA and changed the Sata controller mode option to compatibility
    Restart and back into the Bios
    Bios>startup>boot - in my case the esata flash drive showed up as ATA HDD2 and was excluded from the boot order so I had to un-exclude it and move it to the point in the boot order that I wanted.
Next I downloaded a linux installation iso and put it on a CD - in my case opensuse. Then booted from the CD
From now on this instructions are specific to opensuse and yast but can be generalized to whatever Linux is being used.
In my case yast came up with a good set of suggestions for automatically partitioning the flash drive but then crashed during the partitioning itself. So I rebooted and specified the partitions manually.
    A fat32 partition left as a partition which both windows and Linux could see (in my case about 20% of the drive) (/dev/sdb1)
    An extended partition with the remainder of the drive (/dev/sdb2) which contains the following logical partitions
    A linux Swap partition of 2GB (/dev/sdb5)
    A linux /home partition –the remainder of the drive (/dev/sdb6)
    A linux /root partition of 8GB (/dev/sdb7)
Yast automatically suggested mount points of C,D,E for the windows partitions. Unfortunately because of the way the Thinkpad hard drive was laid out Yast had C assigned the ThinkPad Service partition and D assigned to the SW_Preload (or main windows partition). However there was an edit function that allows for the reversal of those mount points so that the windows C drive is mounted in Linux as Windows/C thereby avoiding confusion. I had already backed up and removed the Thinkpad factory install data so I did not have to deal with that. Yast suggested Windows/E for the mount point of the FAT32 partition on the flash drive, which I accepted.
The yast install configurator made all this manual selection easy, and after the manual configuration the partitioning worked perfectly.
Next step was Linux user configuration which went fine
Next was booting.
In the section management tab
    delete the windows 1 and 2 options (since we are not dual booting directly)
In the boot loader installation tab
    uncheck boot from mbr ( this stops the install from installing Grub and dual boot on the windows c drive
    check boot from root partition (this installs grub and all associated files in the Linux root partition (/dev/sdb6)
I believe that the correct procedure at this point is to click Boot Loader installation details which will bring up the Grub device map. In the device map there will be a line for the fixed hard drive (aka the windows drive) and a line for the esata flash drive. When the installer started up these were in hard drive and esata drive order. However when we boot directly from the flash the esata drive will be grub drive hd0 and the fixed hard drive will be grub hd1. The device map order needs to be changed to reflect this ie the esata drive should be first not second.
I did not do this and ended up initially doing Grub command line editing to boot and later manually editing the grub files using information I had previously learned the hard way and through google.
At this point let the installer go ahead and install Linux. After doing this it should come back and tell you to reboot. Do not do it yet because we need to install the MBR into the flash drive.
I suspect that there is a way of doing this in Yast running from the Live CD but it was not obvious to me so I used the manual method that I have used before.
Open a root terminal
Mount /dev/sdb6 to /mnt/sdb6 (my linux root)
Touch /mnt/sdb6/boot/grub/flag
The purpose of this is when we go looking later at the grub command prompt we need an easy to find unique file
Start grub and do the following
#grub
            grub> find /boot/grub/flag
                (hd1,5)    -- the result of the find in my example
            grub> root (hd1,5)   -- using the result of the find in my example
            grub> setup (hd1)   -- install mbr -- my example parameters - if you get this wrong you will trash some other drive!!!
                  hopefully grub announces success
            grub> quit
Reboot and select the flash drive. In my case I still had the grub devicemap wrong and had to edit the grub commands during boot to tell grub how to find the correct partition and then edit them again after booting
Typical linux install issues that we all always seem to have and can be solved with a little (or a lot of) google research.
As I said at the beginning I now have an untouched windows installation and a nice fast Linux installation. I hope that this will be of some use to someone.

Hi chrissh
i tried this exact procedure... on the exact same notebook (T400s). However, as soon as I set the
   Bios>config>Serial ATA to "compatibility", I cannot use my default Windows installation! I immediately get the "blue screen of death".
I doubt I did anything differently since this is the first step of your procedure and my laptop is brand new!
any idea?

MacBook Air shuts down during boot

My Macbook Air (OS X Yosemite - Early 2014) automatically shuts down during boot, with the screen flashes during the loading bar at 40% and then shuts down. I've tried to reboot many times but it wouldn't get past the 40% on the loading bar.
I've also tried the following but none worked:
The Apple Hardware Test shows that "There may be an issue with a memory module." (PPM002, PPM003, PPM004) - though I've checked that the reference code and the definition doesn't match, as "There may be an issue with a memory module." should be PPM001, and PPM002-PPM015 should be "There may be an issue with the onboard memory.". I've sent this message to Apple and they'd only provided the option to visit their retail store.
Also, the Recovery Mode isn't much help either. As do not have a backup of my HD, I'm not able to restore from Time Machine Backup.
So, I've tried to reinstall OS X Yosemite, but it says "Unavailable to install OS X". A website online says that you can resolve this issue by correcting the date through terminal, but the basic menu bar won't appear, in which I'm not able to access Terminal during the Recovery Mode.
Therefore, I've also tried the Disk Utility, which it shows it can't be repaired, with the following messages: Invalid Node Structure (4, 57963), and 2 messages regarding the Invalid Extent Entry (4, 47013) and (4, 40808). The Single User Mode with the command fsck -fy yields the same message.
Is there any other options then to visit the Apple Retail Store?

Invalid node structure
I'm pretty sure you need more then Disk Utility to repair the drive.
http://www.alsoft.com/diskwarrior/index.html
Assuming you have Snow Leopard installed, you can try reinstalling the Mac OS but you'll have to do this from another Mac.
http://support.apple.com/kb/HT3910
"Important: For MacBook Air, a MacBook Air SuperDrive, or MacBook Air Software Reinstall Drive is required to complete this procedure."

Motorola Droid Razr M stops a red eye during boot

Was updating apps and the phone restarted on it's own. ever since it stops at red eye screen during boot. Tried factory reset - doesn't help - same behavior. I can get to the boot menu but none of the options offer anything useful. Verizon support guys - Any ideas?
based on other posts, it looks like I may need to try a reflash of the phone. Does Verizon support officially offer any suggestions for that process? is there a legit source for the flash roms? what utility is suggested we use for this? There is no 'official' Verizon store in or near my town.
-Trevor Jones

I regret to hear of the issues with your device! I understand the need of a reliable device and I want to make sure that yours works as it should. It seems like you completed your fair share of troubleshooting. I need additional information so that I can better assist. I will send you a private message so that I can assist!
LenaA_VZW
Follow us on Twitter @VZWSupport
If my response answered your question please click the "Correct Answer" button under my response. This ensures others can benefit from our conversation. Thanks in advance for your help with this!!

RV180 (wired only) problems with firmware 1.0.4.14, fails to boot correctly + LAN ports power off during boot (downgrading to 1.0.3.10 = fine again).

Hi All,
A few months ago when 1.0.4.14 was released I was quick to update to this version from 1.0.3.10 but very quickly ran into issues.
Bit of background info... I am not doing anything complex with this box, basic IP4 network over all LAN ports, no VLANs, firewall enabled and allowing 2 port access rules to a static IP address. Any static IPs are assigned manual at host level but all other devices receive DHCP IP addresses. I don’t host VPN on this RV180 but I do with another. Routing VPN has no issues. WAN is connected to another switch provided by my ISP who provides DHCP IP Address with their DNS etc. Only LAN ports 1 and 2 are connected, port 1 to my Wireless AP (AP mode passing all requests to the RV180, DHCP etc.), port 2 connects to a 8 port Smart Switch (but all 'Smart' features are currently not in use, so basic switching only). All other settings on the RV180 are on recommended defaults.
Everything is working fine on 1.0.3.10 but I have all kinds of issues after updating to 1.0.4.14. Here are the actions and experiences I had...
1) Backup my RV180 config to txt file.
2) Navigate to the firmware upgrade page and follow steps to complete the upgrade process from 1.0.3.10 to 1.0.4.14. *router does the normal process of upgrading*
3) RV180 reboots to complete but doesn’t come back up even after waiting 5-10 mins. LAN ports enable during boot up (link lights on) but after about 2mins turn off (no link lights). WAN light is on alongside the Power Light.
4) Power cycle even with rest... Same results.
5) Reset the RV180 to default settings. I can sometimes get the unit to boot up and the LAN remains active and powered up. The web UI is VERY slow compared with 1.0.3.10. Internet sometimes works and sometimes doesn't (I would expect it all work without issue on default settings).
6) I repeat this a few times, various resets, powered off waiting periods, etc. but I always have issues. I did manage to get some log file information and the Kernel appears in the Alert, Error and also the Warning logs (please see attached files).
7) I gave up at this point. No major issues like this reported on the internet from a few google searches etc. So I then reset to defaults (1.0.4.14), downgrade to 1.0.3.10 and finally reset to defaults again + restore backup config settings (with some manual changes).
The router has remained like this and seem to be working fine, but I would like any security improvements from 1.0.4.14 firmware on my device.
Anyone able to help, have the same issue or can advise me in any other ways?
I see 1.0.3.10 isn’t displayed as a firmware download on the standard support page for the RV180 now. Only 1.0.2.6 and 1.0.4.14. Do I need to downgrade again to 1.0.2.6 before upgrading to the latest version?
Regards,
~FAZ~

Hi,
I recently bought a RV180 router and immediately I encountered the same problem; practically I am not able to access the web GUI.
The PC is directly connected to the router, nothing else is connected; the TCP/IP configuration is as follows:
PC: 192.168.1.100
RV180: 192.168.1.1
GATEWAY: 192.168.1.1
SUBNET MASK: 255.255.255.0
Once the router is turned on, the power LED flashes fastly, the Ethernet LED is on but after few minutes it disappears and the PC detects a disconnection of the Ethernet cable.
The router is not pingable and, as I said, the web interface is not reachable.
I have tried to power cycle the router, to reset it (pressing the reset button for more than 3 second and for more than one minute), to access the rescue mode and download a new firmware through TFTP, but nothing worked.
Few times, after many boot and reset trials,I was able to access the web interface and in one of these occasions I updated the firmware to 1.0.4.14 but once the router is powered off the problem arises again at the next power on.
I have not tried yet to downgrade to an older firmware version.
Can you suggest any solution? thank you.

VIA Raid 0: Red screen of Death - fatal error during boot sequence

I have been using two Maxtor 120GB SATA drives in a RAID 0 array on my Athlon 64 MSI MB. I have occasionally had messages saying "Hard disk error. Can't find drive 0". I've assumed that this has been a driver issue because if I power down, wait a while I can reboot and continue without issue (other than chkdsk running during boot up). However after the last such error, when I next tried to reboot I got an error message as the RAID was initialising. The error message was in a red box on a black screen and stated that there was a fatal error and that the raid relationship and all HHD would be destroyed if I continued. Naturally I switched off at this point, but on rebooting got exactly the same message. Eventually, as I have backups, I continued past this point and sure enough the RAID had gone. So I rebuilt the raid array and everything seems to be OK.
However, I'd forgotten that my MSI DVD burner was incapacitated due to a failed firmware update so had temporaril;y replace it with a DVD rom drive to get access to my backups. BUT the drive won't read all my backup discs, in particular it won't read the Drive C backups .
Has anyone else had this RAID erro. Is it a driver error or is it a dsik failing (even though they were new at Christmas).
I am using a Superflower power supply which has 22A on the 12V rail
1GB PC3200 ram by A-Data (CAS 2.5)
Elderly HP 9100 CDRW
MSI DR-8 DVD RW
Ethernet card
Radeon 9600 128MB
AMD64 3000 processor
Freeflow

Raids do not really help benchmarks unless you considure hard drive benchmarks. Most games and benchmark proggies load everything they need prior to running. So unless you have a low memory condition that forces the game or benchmark to use the swap file the only place that you would typically see any gain in speed is during the loading of the game or benchmark. That is hard to quantify other than through experience.
Where a raid shines is in file tranfer situations. When you create and save large files such as movies, Reading or copying large files, defragging, or any other massive file effort. Overall the gains can be very small compaired to the rest of what you do with your system. However that is not to belittle what a Raid does. It does give a finer sheen to the overall computers operations and will make sluggish file transfers seem much more bearable overall.

Eth0 is being up and down for several time during boot

My wicd doesn't connect to eth0 on the first attempt after boot up. It is configured to eth0 always have a higher priority to connect.
My dmesg shows that eth0 being up and down for several time during boot. I have e1000e in my MODULES list.
Here is my 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=""
TIMEZONE="Asia/Hong_Kong"
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.
MOD_AUTOLOAD="yes"
MODULES=(acpi-cpufreq fuse tp_smapi vboxdrv e1000e)
# 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="antony-tp"
# 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=
# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="yes"
# 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 !dhcpcd rpcbind acpid @wicd nfs-common netfs @crond cups @laptop-mode @alsa @sensors ntpd @slim bluetooth)
Here is a segment of my dmesg
[ 2.759302] e1000e: Intel(R) PRO/1000 Network Driver - 1.5.1-k
[ 2.759304] e1000e: Copyright(c) 1999 - 2011 Intel Corporation.
[ 2.759338] e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[ 2.759348] e1000e 0000:00:19.0: setting latency timer to 64
[ 2.759467] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
[ 2.766107] tpm_tis 00:0a: 1.2 TPM (device-id 0x0, rev-id 78)
[ 2.766808] ACPI: AC Adapter [AC] (on-line)
[ 2.776492] wmi: Mapper loaded
[ 2.777212] mei: module is from the staging directory, the quality is unknown, you have been warned.
[ 2.777781] thermal LNXTHERM:00: registered as thermal_zone0
[ 2.777783] ACPI: Thermal Zone [THM0] (66 C)
[ 2.778291] iTCO_vendor_support: vendor-support=0
[ 2.780137] ACPI: Battery Slot [BAT0] (battery present)
[ 2.780958] input: PC Speaker as /devices/platform/pcspkr/input/input4
[ 2.781462] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07
[ 2.781547] iTCO_wdt: Found a Cougar Point TCO device (Version=2, TCOBASE=0x0460)
[ 2.781919] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[ 2.783139] cfg80211: Calling CRDA to update world regulatory domain
[ 2.789182] [drm] Initialized drm 1.1.0 20060810
[ 2.789538] hub 4-1:1.0: USB hub found
[ 2.789616] hub 4-1:1.0: 8 ports detected
[ 2.792925] Non-volatile memory driver v1.3
[ 2.795877] thinkpad_acpi: ThinkPad ACPI Extras v0.24
[ 2.795879] thinkpad_acpi: http://ibm-acpi.sf.net/
[ 2.795881] thinkpad_acpi: ThinkPad BIOS 8DET54WW (1.24 ), EC unknown
[ 2.795882] thinkpad_acpi: Lenovo ThinkPad X220, model 4290NL5
[ 2.797236] thinkpad_acpi: detected a 8-level brightness capable ThinkPad
[ 2.797352] thinkpad_acpi: radio switch found; radios are enabled
[ 2.797466] thinkpad_acpi: possible tablet mode switch found; ThinkPad in laptop mode
[ 2.799752] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked
[ 2.800067] Registered led device: tpacpi::thinklight
[ 2.800091] Registered led device: tpacpi::power
[ 2.800106] Registered led device: tpacpi::standby
[ 2.800120] Registered led device: tpacpi::thinkvantage
[ 2.800192] thinkpad_acpi: Standard ACPI backlight interface available, not loading native one
[ 2.800254] thinkpad_acpi: Console audio control enabled, mode: monitor (read only)
[ 2.801077] input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input5
[ 2.801162] sdhci: Secure Digital Host Controller Interface driver
[ 2.801164] sdhci: Copyright(c) Pierre Ossman
[ 2.801707] Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
[ 2.801709] Copyright(c) 2003-2011 Intel Corporation
[ 2.801744] iwlwifi 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 2.801753] iwlwifi 0000:03:00.0: setting latency timer to 64
[ 2.801789] iwlwifi 0000:03:00.0: pci_resource_len = 0x00002000
[ 2.801791] iwlwifi 0000:03:00.0: pci_resource_base = ffffc90005abc000
[ 2.801793] iwlwifi 0000:03:00.0: HW Revision ID = 0x34
[ 2.801877] iwlwifi 0000:03:00.0: irq 49 for MSI/MSI-X
[ 2.801913] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Advanced-N 6205 AGN, REV=0xB0
[ 2.801962] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
[ 2.802045] sdhci-pci 0000:0d:00.0: SDHCI controller found [1180:e822] (rev 7)
[ 2.802067] sdhci-pci 0000:0d:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 2.802107] sdhci-pci 0000:0d:00.0: setting latency timer to 64
[ 2.802118] _regulator_get: 0000:0d:00.0 supply vmmc not found, using dummy regulator
[ 2.802188] Registered led device: mmc0::
[ 2.803329] mmc0: SDHCI controller on PCI [0000:0d:00.0] using DMA
[ 2.815226] iwlwifi 0000:03:00.0: device EEPROM VER=0x715, CALIB=0x6
[ 2.815229] iwlwifi 0000:03:00.0: Device SKU: 0X1f0
[ 2.815231] iwlwifi 0000:03:00.0: Valid Tx ant: 0X3, Valid Rx ant: 0X3
[ 2.815247] iwlwifi 0000:03:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
[ 2.845674] iwlwifi 0000:03:00.0: loaded firmware version 17.168.5.3 build 42301
[ 2.845820] Registered led device: phy0-led
[ 2.850630] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
[ 2.862431] usb 1-1.2: new low-speed USB device number 3 using ehci_hcd
[ 2.943648] e1000e 0000:00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) f0:de:f1:92:77:26
[ 2.943651] e1000e 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
[ 2.943712] e1000e 0000:00:19.0: eth0: MAC: 10, PHY: 11, PBA No: 1000FF-0FF
[ 2.943734] mei 0000:00:16.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 2.943739] mei 0000:00:16.0: setting latency timer to 64
[ 2.943817] mei 0000:00:16.0: irq 50 for MSI/MSI-X
[ 2.944502] agpgart-intel 0000:00:00.0: Intel Sandybridge Chipset
[ 2.945021] agpgart-intel 0000:00:00.0: detected gtt size: 2097152K total, 262144K mappable
[ 2.946341] watchdog: INTCAMT: cannot register miscdev on minor=130 (err=-16).
[ 2.946452] watchdog: error registering /dev/watchdog (err=-16).
[ 2.946523] mei: unable to register watchdog device.
[ 2.946598] agpgart-intel 0000:00:00.0: detected 65536K stolen memory
[ 2.946692] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xe0000000
[ 2.946734] i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[ 2.948359] snd_hda_intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[ 2.948422] snd_hda_intel 0000:00:1b.0: irq 51 for MSI/MSI-X
[ 2.948444] snd_hda_intel 0000:00:1b.0: setting latency timer to 64
[ 3.022245] usb 1-1.3: new full-speed USB device number 4 using ehci_hcd
[ 3.172080] usb 1-1.4: new full-speed USB device number 5 using ehci_hcd
[ 3.274597] Bluetooth: Core ver 2.16
[ 3.274611] NET: Registered protocol family 31
[ 3.274612] Bluetooth: HCI device and connection manager initialized
[ 3.274614] Bluetooth: HCI socket layer initialized
[ 3.274614] Bluetooth: L2CAP socket layer initialized
[ 3.274618] Bluetooth: SCO socket layer initialized
[ 3.275535] Bluetooth: Generic Bluetooth USB driver ver 0.6
[ 3.276006] usbcore: registered new interface driver btusb
[ 3.338454] usb 1-1.6: new high-speed USB device number 6 using ehci_hcd
[ 3.444567] Linux media interface: v0.10
[ 3.447387] Linux video capture interface: v2.00
[ 3.448573] input: Logitech Trackball as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input6
[ 3.448671] generic-usb 0003:046D:C404.0001: input,hidraw0: USB HID v1.10 Mouse [Logitech Trackball] on usb-0000:00:1a.0-1.2/input0
[ 3.448690] usbcore: registered new interface driver usbhid
[ 3.448691] usbhid: USB HID core driver
[ 3.449136] uvcvideo: Found UVC 1.00 device Integrated Camera (04f2:b217)
[ 3.450945] input: Integrated Camera as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/input/input7
[ 3.450987] usbcore: registered new interface driver uvcvideo
[ 3.450988] USB Video Class driver (1.1.1)
[ 3.484049] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input8
[ 3.491137] HDMI status: Codec=3 Pin=5 Presence_Detect=0 ELD_Valid=0
[ 3.491298] HDMI status: Codec=3 Pin=6 Presence_Detect=0 ELD_Valid=0
[ 3.491486] HDMI status: Codec=3 Pin=7 Presence_Detect=0 ELD_Valid=0
[ 3.491637] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
[ 3.491709] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
[ 3.491765] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
[ 3.492050] i915 0000:00:02.0: power state changed by ACPI to D0
[ 3.492053] i915 0000:00:02.0: power state changed by ACPI to D0
[ 3.492059] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 3.492062] i915 0000:00:02.0: setting latency timer to 64
[ 3.538056] mtrr: no more MTRRs available
[ 3.538058] [drm] MTRR allocation failed. Graphics performance may suffer.
[ 3.538266] i915 0000:00:02.0: irq 52 for MSI/MSI-X
[ 3.538270] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[ 3.538271] [drm] Driver supports precise vblank timestamp query.
[ 3.538292] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[ 3.664501] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.0, id: 0x1e2b1, caps: 0xd001a3/0x940300/0x120c00
[ 3.664518] psmouse serio1: synaptics: serio: Synaptics pass-through port at isa0060/serio1/input0
[ 3.716317] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input12
[ 4.407165] fbcon: inteldrmfb (fb0) is primary device
[ 4.575259] Console: switching to colour frame buffer device 170x48
[ 4.577042] fb0: inteldrmfb frame buffer device
[ 4.577043] drm: registered panic notifier
[ 4.607860] acpi device:01: registered as cooling_device4
[ 4.607985] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input13
[ 4.608039] ACPI: Video Device [VID] (multi-head: yes rom: no post: no)
[ 4.608122] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[ 4.757243] EXT4-fs (sda3): re-mounted. Opts: discard
[ 4.765917] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: discard
[ 4.776777] Adding 262140k swap on /dev/sda2. Priority:-1 extents:1 across:262140k SS
[ 5.099467] NET: Registered protocol family 10
[ 6.048650] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 6.098038] Bluetooth: RFCOMM TTY layer initialized
[ 6.098055] Bluetooth: RFCOMM socket layer initialized
[ 6.098057] Bluetooth: RFCOMM ver 1.11
[ 6.278766] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
[ 6.278893] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
[ 6.568639] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
[ 6.568775] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
[ 6.684082] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 7.176563] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
[ 7.226662] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
[ 7.227110] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 10.229345] IBM TrackPoint firmware: 0x0e, buttons: 3/3
[ 10.490618] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio2/input/input14
[ 10.817814] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[ 10.819315] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 11.186166] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
[ 11.186292] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
[ 11.313367] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 11.665342] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
[ 11.717591] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
[ 11.718042] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 11.964795] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
[ 12.017213] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
[ 12.017720] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 13.811264] EXT4-fs (sda3): re-mounted. Opts: discard,commit=0
[ 13.826031] EXT4-fs (sda4): re-mounted. Opts: discard,commit=0
[ 15.178905] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[ 15.180472] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 25.663056] eth0: no IPv6 routers present
Any hint for tracing the root of this problem? Thank you very much!

Hi ...
If you have moved the Safari application from the Applications folder, move it back.
As far as the cache goes, there's a work around for that when you can't empty the Safari cache from the menu bar.
Go to ~/Library/Caches/com.aple.Safari.Cache.db. Move the Cache.db file to the Trash.
Try Safari.
Mac OS X (10.7.2) < from your profile
If that is corrrect, you need to update your system software. Click your Apple menu icon top left in your screen. From the drop down menu click Software
Update ...
~ (Tilde) character represents the Home folder.
For Lion v10.7x: To find the Home folder in OS X Lion, open the Finder, hold the Option key, and choose Go > Library

Read-Only Problem during Boot

Hi,
I tried to update my system today, like every week, with the standard command pacman -Syu. After installing all updates, my window manager (gnome3) crashed and i tried to restart my System. After the grub window appeared and I choosed my kernel the normal startup commands are shown until the Arch prompt appeared. The one where Arch Linux tried to start all relevant processes. After that there are only mistakes. All startup processes are busy or failing. The only message i get is, that the filesystem, i think thats the root partition (ext4), is read-only or another error: some files for startup cannot be created because they already exist.
Getting to console is also impossible, because the system tries to start virtualbox additions, with an funny message, that it is busy and tries it again in 5 min (infinity loop). But shidt happens. I have read in another post that I can try another Linux System, mount my root partition and do an
fsck /dev/sda3 -p or -f
. But it says that all is clean (sda3 is root and sda1 is /boot). The filesystem is ext4, so i tried also fsck.ext4, but it also say all is clean.
After another boot i stoped at the position, where the fist error occur.
Mounting Local Filesystems
/etc/rc.sysinit: line 285: /etc/mtab: Read-only file System
next one:
Activating Swap
/bin/rm: cannot remove '/etc/localtime': Read-only file system
removing leftover Files
/usr/bin/find: cannot delete 'var/run/cups.pid': Read-only file system
After that message there are also al lot of analog errors.
I have no other idea than an dirty filesystem. Is there another possibility to rescue my system without an fresh install. Im sorry but i cannot log any messages at that state of boot. So it is not easy to get better informations about special error codes.
I have forget to give you some informations about my stats:
- actual stable arch kernel 2.6.38
- gnome 3
- thinkpad t400
Last edited by Psikon (2011-05-13 20:18:12)

With udev 168-1 I obtain this message during boot:
:: checking filesystems
fsck.ext4: no such file or directory while trying to open /dev/sda6 (my root device)
Possibly non-existent device?
***************** FILESYSTEM CHECK FAILED ****************
* Please repair manually and reboot. Note that the root *
* file system is currently mounted read-only. To remount *
* it read-write type: mount -n -o remount,rw / *
* When you exit the maintenance shell the system will *
* reboot automatically. *
but fsck run manually says it's all clean.
I have to remount rw / partition and manually mount all the other partition, then I can switch to runlevel 3.
With udev 167-2 (and prior) I can boot without any problems.
I'm not sure it's a problem from udev, but downgrading it works for me.

Q10 won't boot! only red light flashing.

my phone suddenly wont respond when i was trying to open a bbm, so, i restarted the handheld. however, it wont turn on anymore. try to put off the batt, and put it back again, still won't to boot. it only does flashing the red light. i've tried to reload the software through bb link, and it has done nothing. anyone exprience the same trouble as mine? please..help me. thank you

Hey panda1111,
Welcome to the BlackBerry Support Community Forums.
Thanks for the question.
Follow the steps below to try and bring the BlackBerry Z10 back to life:
Ensure that BlackBerry Link is installed on the PC or Mac OS
Ensure the computer has an internet connection.
Launch the BlackBerry Link Software.
Note: A backup of the BlackBerry device should be tried before a reload.
Turn off the BlackBerry device. Make sure there are no flashing LEDs and that the LCD is not still being lit by the backlight. If there are any flashing LEDs, hold the power button for 15 seconds until the LEDs stop.
Connect the BlackBerry device to the computer.
When prompted with Cannot communicate with device, click Restore and then click yes allow the update to be downloaded and installed on the BlackBerry device.
If the restore button is not seen press the vertical dots in the lower right corner of BlackBerry Link and select disconnected device. Highlight the disconnected device you are working with and attempt steps 4 to 6 again.
If the issue still persists, then I suggest contacting your network service provider for repair options.
Let me know if you have any more questions.
Cheers.
VIA | ViciousFerret
http://supportforums.blackberry.com/t5/BlackBerry-Z10/BB-Z10-Died/m-p/2230087#M10125
Please thank those who help you by clicking the button.
If your issue has been solved, please resolve it by marking "Accept as Solution"

Suddenly "Fatal error during GPU init" during boot - radeon

Hi,
after a rather abrupt shutdown my system doesn't boot correctly anymore.
I have an Asus laptop with an ATI radeon HD 2400 (so the sticker on the laptop says - I'm not really a hardware guy)
Before:
While booting, the kernel/console output had bigger, somewhat non-high-resolution letters. Halfway in, the letters changed into a smaller, higher-defined font which was more "beautiful".
Sorry, I don't know what mechanism that is, so I had to describe it that way.
After:
This doesn't happen anymore. Rather, I get this message during boot (this is a copy out of /var/log/errors.log):
Jun 21 17:59:55 localhost kernel: [ 4.081919] radeon 0000:01:00.0: Fatal error during GPU init
Jun 21 17:59:55 localhost kernel: [ 4.082998] radeon 0000:01:00.0: no bo for sa manager
Jun 21 17:59:55 localhost kernel: [ 4.083059] [TTM] Trying to take down uninitialized memory manager type 1
I already tried the following:
- reinstall xorg and xf86-video-ati
- sections "Enable KMS" and "Troubleshoot KMS" from that wiki entry:
https://wiki.archlinux.org/index.php/ATI
- scream and slightly hit the side of the laptop
Nothing worked. Could anyone tell me where to continue searching? I'd hate to reinstall a 1-week old system.
Thanks in advance,
Alex

If you remove the ati drivers, the mesa-drivers are used I think.
Since the open source drivers don't work, you should try the closed source drivers (ATI Catalyst) from the AUR. Installing this is a bit of a hassle. The catalyst driver does not support Xorg 1.12, so you have to add a repository for Xorg1.11 and downgrade (see the wiki page). Then, you should install either catalyst-utils and catalyst-hook from AUR (as described in the wiki) or catalyst-total (which combines both and is also mentioned in the wiki).
See the Catalyst Wiki for all information.
Catalyst Utils in AUR
Catalyst Hook
Catalyst Total
edit: I just read the wiki. It seems like there is an easier way to install things now: https://wiki.archlinux.org/index.php/AT … repository
Last edited by Terminator (2012-06-25 23:32:39)

[SOLVED] How to get NetworkManager start on background during boot?

NetworkManager has always taken relatively long time to start during boot, presumably waiting for wlan to connect.
$ systemd-analyze blame
7.682s NetworkManager.service
Previously I was able to get it to start on background by removing /etc/systemd/system/multi-user.target.wants/NetworkManager.service
This prevented multi-user.target from waiting for NM to start and it would continue to connect on background while my boot finishes.
However, after upgrade to networkmanager-0.9.10.0-2 that doesn't seem work any more.
If I remove the .service file from multi-user.target.wants/, NetworkManager doesn't start during boot at all.
enabling NetworkManager.service creates these symlinks:
# systemctl enable NetworkManager
Created symlink from /etc/systemd/system/dbus-org.freedesktop.NetworkManager.service to /usr/lib/systemd/system/NetworkManager.service.
Created symlink from /etc/systemd/system/multi-user.target.wants/NetworkManager.service to /usr/lib/systemd/system/NetworkManager.service.
Created symlink from /etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service to /usr/lib/systemd/system/NetworkManager-dispatcher.service.
looks like enabling any other basic systemd unit links the .service file to multi-user.target.wants/ as well..
How can I enable NetworkManager.service during boot without multi-user.target.wants/, and get it to start on background again?
any ideas appreciated :)
Last edited by ooo (2014-08-03 12:13:28)

Okay, looks like this can be resolved by simply changing the NetworkManager.service type from dbus to forking.
$ systemd-analyze blame
173ms NetworkManager.service
Here's the modified service file if anyone's interested:
place it in /etc/systemd/system/NetworkManager.service
[Unit]
Description=Network Manager
Wants=network.target
Before=network.target
[Service]
Type=forking
PIDFile=/var/run/NetworkManager.pid
BusName=org.freedesktop.NetworkManager
ExecStart=/usr/bin/NetworkManager --pid-file=/var/run/NetworkManager.pid
# NM doesn't want systemd to kill its children for it
KillMode=process
[Install]
WantedBy=multi-user.target
Alias=dbus-org.freedesktop.NetworkManager.service
Also=NetworkManager-dispatcher.service
You need to disable NetworkManager.service before creating the file and enable it after so that systemd links the file from /etc/systemd instead of /usr/lib/systemd,
there may be simpler way but I can't be bothered to go through systemd manuals any more.
Note that this will probably break any systemd .service that actually requires network, although that was the case with my previous workaround as well.
I won't guarantee this will work for you and won't set your machine on fire. If you have issues, simply remove the file and re-enable to go back to default

Cisco Aironet 1262N stuck during boot process

I am banging my head against the wall trying to figure out why my AIR-AP1262N-A-K9 will not boot all the way. It will get all the way to initiating the interfaces and stop. I can never get to controlling the cli. This is my first time with a cisco ap but from everything that I read it seamed very easy.
This unit from what I understand will work all on its own with no controller. Hence it is called a "standalone" model. Yet it seems to be looking for something to finish during the boot. Below is the out put during boot. The last line is where it stops.
If anyone can help me I would greatly appreciate it.
r WRDTR,CLKTR: 0x8200083f 0x40000000
r RQDC ,RFDC : 0x80000033 0x00000212
using eeprom values
WRDTR,CLKTR: 0x8200083f 0x40000000
RQDC ,RFDC : 0x80000033 0x00000212
using MCNG ddr static values from serial eeprom
ddr init done
IOS Bootloader - Starting system.
FLASH CHIP: Numonyx P33
Checking for Over Erased blocks
Xmodem file system is available.
DDR values used from system serial eeprom.
WRDTR,CLKTR: 0x8200083f, 0x40000000
RQDC, RFDC : 0x80000033, 0x00000212
PCIE0: link is up.
PCIE0: VC0 is active
PCIE1: link is up.
PCIE1: VC0 is active
64bit PCIE devices
PCIEx: initialization done
flashfs[0]: 147 files, 7 directories
flashfs[0]: 0 orphaned files, 0 orphaned directories
flashfs[0]: Total bytes: 31739904
flashfs[0]: Bytes used: 6435328
flashfs[0]: Bytes available: 25304576
flashfs[0]: flashfs fsck took 9 seconds.
Reading cookie from system serial eeprom...Done
Base Ethernet MAC address: 7c:ad:74:93:36:ba
Waiting for PHY auto negotiation to complete... TIMEOUT !
Ethernet link is down.
Error: RGMII speed
The system has encountered an error initializing
the Ethernet port.
The system is ignoring the error and continuing to boot.
If you abort the system boot process, the following
commands will re-initialize Ethernet, TFTP, and finish
loading the operating system software:
    ether_init
    tftp_init
    boot
button pressed for 22 seconds
process_config_recovery: set IP address and config to default 10.0.0.1
process_config_recovery: image recovery
ap:
r WRDTR,CLKTR: 0x8200083f 0x40000000
r RQDC ,RFDC : 0x80000033 0x00000212
using eeprom values
WRDTR,CLKTR: 0x8200083f 0x40000000
RQDC ,RFDC : 0x80000033 0x00000212
using MCNG ddr static values from serial eeprom
ddr init done
Running Normal Memtest...
Passed.
IOS Bootloader - Starting system.
FLASH CHIP: Numonyx P33
Checking for Over Erased blocks
Xmodem file system is available.
DDR values used from system serial eeprom.
WRDTR,CLKTR: 0x8200083f, 0x40000000
RQDC, RFDC : 0x80000033, 0x00000212
PCIE0: link is up.
PCIE0: VC0 is active
PCIE1: link is up.
PCIE1: VC0 is active
64bit PCIE devices
PCIEx: initialization done
flashfs[0]: 147 files, 7 directories
flashfs[0]: 0 orphaned files, 0 orphaned directories
flashfs[0]: Total bytes: 31739904
flashfs[0]: Bytes used: 6435328
flashfs[0]: Bytes available: 25304576
flashfs[0]: flashfs fsck took 9 seconds.
Reading cookie from system serial eeprom...Done
Base Ethernet MAC address: 7c:ad:74:93:36:ba
Waiting for PHY auto negotiation to complete... TIMEOUT !
Ethernet link is down.
Error: RGMII speed
The system has encountered an error initializing
the Ethernet port.
The system is ignoring the error and continuing to boot.
If you abort the system boot process, the following
commands will re-initialize Ethernet, TFTP, and finish
loading the operating system software:
    ether_init
    tftp_init
    boot
Loading "flash:/ap3g1-k9w7-mx.124-25d.JA1/ap3g1-k9w7-mx.124-25d.JA1"...#########
File "flash:/ap3g1-k9w7-mx.124-25d.JA1/ap3g1-k9w7-mx.124-25d.JA1" uncompressed a
nd installed, entry point: 0x4000
executing...
enet halted
              Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
           cisco Systems, Inc.
           170 West Tasman Drive
           San Jose, California 95134-1706
Cisco IOS Software, C1260 Software (AP3G1-K9W7-M), Version 12.4(25d)JA1, RELEASE
SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2011 by Cisco Systems, Inc.
Compiled Thu 11-Aug-11 02:07 by prod_rel_team
Proceeding with system init
Proceeding to unmask interrupts
Initializing flashfs...
FLASH CHIP: Numonyx P33
Checking for Over Erased blocks
flashfs[1]: 147 files, 7 directories
flashfs[1]: 0 orphaned files, 0 orphaned directories
flashfs[1]: Total bytes: 31481856
flashfs[1]: Bytes used: 6435328
flashfs[1]: Bytes available: 25046528
flashfs[1]: flashfs fsck took 7 seconds.
flashfs[1]: Initialization complete.
flashfs[2]: 0 files, 1 directories
flashfs[2]: 0 orphaned files, 0 orphaned directories
flashfs[2]: Total bytes: 11999232
flashfs[2]: Bytes used: 1024
flashfs[2]: Bytes available: 11998208
flashfs[2]: flashfs fsck took 1 seconds.
flashfs[2]: Initialization complete....done Initializing flashfs.
Radio0 present 8364B 8000 B8020000 0 B8030000 10
Radio1 present 8364B 8000 B0020000 0 B0030000 C
Waiting for PHY auto negotiation to complete... TIMEOUT !
Ethernet link is down.
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
[email protected].
cisco AIR-AP1262N-A-K9     (PowerPC460exr) processor (revision B0) with 81910K/4
9152K bytes of memory.
Processor board ID FTX1716E2DN
PowerPC460exr CPU at 666Mhz, revision number 0x18A8
Last reset from power-on
1 Gigabit Ethernet interface
2 802.11 Radio(s)
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: 7C:AD:74:93:36:BA
Part Number                          : 73-12175-06
PCA Assembly Number                  : 800-32268-06
PCA Revision Number                  : B0
PCB Serial Number                    : FOC17106662
Top Assembly Part Number             : 800-33866-02
Top Assembly Serial Number           : FTX1716E2DN
Top Revision Number                  : A0
Product/Model Number                 : AIR-AP1262N-A-K9
Press RETURN to get started!
*Mar 1 00:00:09.481: %SOAP_FIPS-2-SELF_TEST_IOS_SUCCESS: IOS crypto FIPS self t
est passed
*Mar 1 00:00:09.490: *** CRASH_LOG = YES
*Mar 1 00:00:09.490: 64bit PCIE devices
*Mar 1 00:00:09.789: soap_extern_intr_dispatch: no handler for UIC2 intrno 12 l
evel 4
*Mar 1 00:00:10.088: soap_extern_intr_dispatch: no handler for UIC2 intrno 12 l
evel 4
*Mar 1 00:00:12.966: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self
test passed on interface Dot11Radio 0
*Mar 1 00:00:15.649: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self
test passed on interface Dot11Radio 1Base Ethernet MAC address: 7C:AD:74:93:36:
BA
*Mar 1 00:00:56.377: %LINK-3-UPDOWN: Interface GigabitEthernet0, changed state
to up
to up
ernet0, changed state to down
*Mar 1 00:11:00.003: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to a
dministratively down
*Mar 1 00:11:00.003: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to a
dministratively down
*Mar 1 00:11:00.003: %CDP_PD-4-POWER_OK: Full power - AC_ADAPTOR inline power s
ource
*Mar 1 00:11:00.012: %SYS-5-RESTART: System restarted --
Cisco IOS Software, C1260 Software (AP3G1-K9W7-M), Version 12.4(25d)JA1, RELEASE
SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2011 by Cisco Systems, Inc.
Compiled Thu 11-Aug-11 02:07 by prod_rel_team
*Mar 1 00:11:00.012: %SNMP-5-COLDSTART: SNMP agent on host ap is undergoing a c
old start
*Mar 1 00:11:00.994: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, chan
ged state to up
*Mar 1 00:11:01.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio
1, changed state to down
*Mar 1 00:11:01.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio
0, changed state to down
*Mar 1 00:11:11.956: %LINK-3-UPDOWN: Interface BVI1, changed state to down
*Mar 1 00:11:12.957: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, chan
ged state to down

what are your console settings set for?
you need to be 9600/none/8/1 and flow controll set to off to be able to interact with the CLI
HTH,
Steve
Please remember to rate useful posts, and mark questions as answered

[solved]How to unlock LUKS using keyfile on usbdrive during boot?

Hi all,
I would like some advise for booting encrypted partitions using kefiles on a flashdrive. I'm setting up a Intel Atom based homeserver, and and want my data to be encrypted in case the server gets stolen. To save some encryption overhead I prefer to leave root unencrypted and only encrypt /home, and if this works, later on /var, /tmp and swap as well. My plan is to have a keyfile on a flash thumbdrive, and only have the thumbdrive plugged in while booting.
I have read the dm-crypt wiki page, but it assumes an encrypted root, and this approach won't work in my situation, where only non-root mountpoints are encrypted. If i put 'ASK' in /etc/crypttab I get prompted for the passphrase and the LUKS container unlocks and mounts fine. I can also unlock the LUKS container manually using the keyfile that I created. However when I put the path to the keyfile in /etc/crypttab instead of 'ASK', and let the usbdrive automount using an udev rule the unlock at boot fails. It seems that my udev rule is only executed when I plug in a drive after booting, not when it is already plugged in during boot. How would I accomplish this? Mount it with fstab and automatically unmount it after booting, or some entirely different way?
my /etc/fstab:
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/sda1 / ext4 defaults 0 1
/dev/sda2 swap swap defaults 0 0
/dev/mapper/home /home ext4 defaults 0 1
/etc/crypttab:
home /dev/sda3 /media/usbhd-sdc1/keyfiles/arch_server_-_home.key
/etc/udev/rules.d/01.usbdrive_automount.rules (sdb is a second, currently unused harddisk):
KERNEL=="sd[b-z]", NAME:="%k", SYMLINK+="usbhd-%k", GROUP:="users", OPTIONS="last_rule"
ACTION=="add", KERNEL=="sd[c-z][0-9]", SYMLINK+="usbhd-%k", GROUP:="users", NAME:="%k"
ACTION=="add", KERNEL=="sd[c-z][0-9]", RUN+="/bin/mkdir -p /media/usbhd-%k"
ACTION=="add", KERNEL=="sd[c-z][0-9]", PROGRAM=="/sbin/blkid -t %N", RESULT=="vfat", RUN+="/bin/mount -t vfat -o rw,noauto,flush,dirsync,noexec,nodev,noatime,dmask=000,fmask=111 /dev/%k /media/usbhd-%k", OPTIONS="last_rule"
ACTION=="add", KERNEL=="sd[c-z][0-9]", RUN+="/bin/mount -t auto -o rw,noauto,async,dirsync,noexec,nodev,noatime /dev/%k /media/usbhd-%k", OPTIONS="last_rule"
ACTION=="remove", KERNEL=="sd[c-z][0-9]", RUN+="/bin/umount -l /media/usbhd-%k"
ACTION=="remove", KERNEL=="sd[c-z][0-9]", RUN+="/bin/rmdir /media/usbhd-%k", OPTIONS="last_rule"
<edit>
Okay I have found a solution. The trick was to make sure the usbstick gets mounted first, so the keyfile is available for the unlocking/mounting during boot. To do so I have added 'usb' to the hooks line in /etc/mkinitcpio.conf and recompiled the initramfs as described in the wiki link above.
Next I changed my /etc/udev/rules.d/01.usbdrive_automount.rules a little so that the mountpoint of the usbdrive stays after unplugging it:
KERNEL=="sd[b-z]", NAME:="%k", SYMLINK+="usbhd-%k", GROUP:="users", OPTIONS="last_rule"
ACTION=="add", KERNEL=="sd[c-z][0-9]", SYMLINK+="usbhd-%k", GROUP:="users", NAME:="%k"
ACTION=="add", KERNEL=="sd[c-z][0-9]", RUN+="/bin/mkdir -p /media/usbhd-%k"
ACTION=="add", KERNEL=="sd[c-z][0-9]", PROGRAM=="/sbin/blkid -t %N", RESULT=="vfat", RUN+="/bin/mount -t vfat -o rw,noauto,flush,dirsync,noexec,nodev,noatime,dmask=000,fmask=111 /dev/%k /media/usbhd-%k", OPTIONS="last_rule"
ACTION=="add", KERNEL=="sd[c-z][0-9]", RUN+="/bin/mount -t auto -o rw,noauto,async,dirsync,noexec,nodev,noatime /dev/%k /media/usbhd-%k", OPTIONS="last_rule"
ACTION=="remove", KERNEL=="sd[c-z][0-9]", RUN+="/bin/umount -l /media/usbhd-%k", OPTIONS="last_rule"
#ACTION=="remove", KERNEL=="sd[c-z][0-9]", RUN+="/bin/umount -l /media/usbhd-%k"
#ACTION=="remove", KERNEL=="sd[c-z][0-9]", RUN+="/bin/rmdir /media/usbhd-%k", OPTIONS="last_rule"
/etc/fstab:
The usbdrive is put above the encrypted partition to make it get mounted first:
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/sdc1 /media/usbhd-sdc1 ext2 defaults 0 0
/dev/sda1 / ext4 defaults 0 1
/dev/sda2 swap swap defaults 0 0
/dev/mapper/home /home ext4 defaults 0 1
/etc/crypttab:
home /dev/sda3 /media/usbhd-sdc1/keyfiles/arch_server_-_luks.key
So now I plug in the flashdrive, turn on the server, unplug the flashdrive and udev automatically unmounts the flashdrive while leaving the mountpoint /media/usbhd-sdc1 for the next boot.
</edit>
Last edited by rwd (2009-12-04 19:36:14)

graysky wrote:@ratcheer - You can try now if it's a major pain in the balls by enabling [testing] and using the updated linux package.
If you do enable testing make sure you aren't like myself: I'm not competent enough to enable testing..
Edit:
To elaborate a bit. If you enable testing and then just do a "pacman -Syu" then you are going to pull in all sorts of packages you may not want and it may be complicated to get rid of later. To avoid this I would enable testing, do this:
sudo pacman -Syy
sudo pacman -S testing/linux
So it would pull in the absolute minimum that I wanted from testing. Then I would disable the testing repository and pacman -Syy again. That would convert the new linux package and packages it requires to manual packages. E.g. they would be shown under "pacman -Qm"
Because once you start pulling packages in from testing it is almost a one-way street. As I instructed above, that is my gross understanding. I don't use testing at all, it is supposed to be used if you are actively testing Arch and providing feedback while doing so.
Last edited by headkase (2012-10-03 01:51:51)

How to diagnose NTP server problem during boot-up?

We're having a problem on our campus network where Macs aren't able to use the time.apple.com NTP server to correct the time during boot-up. Once the user logs in, open the Date & Time pref pane causes the time to be corrected.
I've noticed this problem for quite a while but it's really been just a minor inconvenience. Then some users started using Boot Camp and it became a bigger inconvenience because their Mac time is wrong by 4 hours when they return to OS X from Windows XP. It has now become something that we need to address because we have set up a lab with iMacs all configured with Boot Camp and set up to authenticate off of our Active Directory server, which requires that the time be correct on the iMacs when the user tries to log in.
We'd like to monitor the network traffic on Mac during boot-up to see if we can figure out why this is happening. My person theory is that something that the network admins have the network configured to do when it first sees a new computer is causing enough of a delay in the DHCP process that the Mac doesn't have a network connection when the NTP server call would normally be made. The college has a DSL line that is not part of our network and NTP server time correction works correctly on it.
We're looking for the best way to capture the activity on the Mac and the network traffic at boot-up. Here are the things that we're looking into.
1) Verbose mode - Interesting looking but it goes by pretty quickly and I don't have time to read all of that info. Is this recorded in a log automatically somewhere or is there a way to capture this info?
2) Single user mode - I haven't been able to determine whether the NTP server call should have occurred by the time I get a prompt in Single User Mode. If so, is there a command I could use here that would give me a dump of activity and network traffic up to this point?
3) I have Interarchy which will let me record network traffic but as far as I can tell there's isn't a way to use this feature during boot-up. Am I wrong about that?
4) Someone suggested using Ethereal which appears to require Fink when installed. I can't tell if this will work during boot for if it's an app that I can only run after logging in (like Interarchy). Does anyone know how this works?
Any suggestions would be welcomed.
-McD-

Turns out it was a network timing issue. The DHCP server wasn't providing the IP address quick enough (never figured out why, though).

During boot up there is a flashing planet earth symbol

Similar Messages

Maybe you are looking for