Firmware 1.1.2 doesn't work?

I've updated my iphone to 1.1.2 today...
but when I restarted it...It showed that I needed activation..
and Itunes said that activation was unavailable now...
Damt... I will go to NYC tommorow...and I need...A CELLPHONE!

The activation service was apparently down for a short period. It s now up and running (according to other posts). Firmware 1.1.2 works fine for me.

Similar Messages

MBP will not access n on TC Dual Band. Firmware 7.4.1 doesn't work either.

So maybe I'm missing something.
I have the Time Capsule dual band. Brand new. An Apple Care replacement of my original Time Capsule (non dual band). 1 TB versions.
Replaced because I can't access the 5ghz band from my MacBook Pro.
MacBook Pro 15"
Model Identifier: MacBookPro2,2
Processor Name: Intel Core 2 Duo
Processor Speed: 2.16 GHz
Wireless Card Type: AirPort Extreme (0x168C, 0x87)
Wireless Card Locale: USA
Wireless Card Firmware Version: 1.4.8.3
Current Wireless Network: xxxx
Wireless Channel: 11
I currently have the TC set with Radio Mode 802.11a/n-802.11g only. My MBP will only join the g side. I know this because holding down the Option key and looking at the Airport Menu icon shows I'm on channel 11 at Transmit Rate of 54.
In Airport Utility under Airport/Wireless/Wireless Options I have also allow the 5ghz network name to be shown.
I my Airport Menu if I select this 5ghz network I'm asked for the password. I type in the password and get connection timed out. All the time.
Now the interesting part:
The TC has firmware 7.4. If I upgrade it to 7.4.1 my computer will not even see the Time Capsule at all. I have to do a hard restart of the TC and immediately downgrade the Firmware back to 7.4.
Interesting part number two is:
I have an original Airport Extreme. The first release of the n Airport. If I try and use this unit at 5ghz also, my MBP will get the same Connection Timeout. But the MBP will work on n band at 2.4ghz. BThis running firmware 7.3.6 ( I think that is it). IF I upgrade this unit to 7.4.1? Again I will not even be able to see the Airport on my MBP. Again I have to down grade the unit to 7.3.6 after a hard restart.
So for me the 7.4.1 update is not workable. And Apple replaced my original TC twice with the same results. I returned them and they sent me the newest TC. And as stated above, the same results.
So 7.4.1 doesn't work at all for me.
5ghz n band doesn't work for me.
Any ideas? I'm assuming my Airport Card in the MBP is defective at this stage. It can't access 5ghz, And working on sending out the computer for check up to Apple. Or a Genius Bar visit.
Anyone else having n access on their computers? And the 7.4.1 Firmware?

Update to my post above- this is SO weird
If I manually select channel 40 on the 5ghz band, I can access 5ghz. I do not get the Connection Timeout. I on it right now.
Before I manually selected channel 40 the TC was in channel 149.
Does this mean anything? Now I'm not sure if the Airport Card in my MBP is defective or not.

Bose Sounddock remote doesn't work with 6th Gen 160GB iPod Classic

I have recently purchased a Bose Portable Sounddock and whilst my iPod Classic (160GB 6th Gen) will work in the docking station, the only buttons on the remote that work are the volume buttons - everything else has to be done on the device. It does charge when in the docking station as well. I have an iPhone 4 that works perfectly a Nano that works perfectly but the Classic won't. I have spoken to Bose who tell me that there should be no issues with my Classic. I have reset it to factory settings and it hasn't helped. I have tried another Sounddock in a local shop and it has the same issues.
Can anyone suggest a way to fix this? Any help appreciated.

Assuming that the Bose Soundock, is brand new and not refurbished or pre-owned
My Suggestions
Check that the remote batteries are good.
Hard Reset the iPod, (press menu and select buton for about 10 secs or till the Apple logo comes ON)
Restore the iPod (this is to fix any corrupted firmware)
If the above doesn't work, bring the iPod to the Bose store and try it on their Soundock (bring your remote and test)

Internal camera doesn't work after Firmware Update

Hi everybody,
I had some troubles after updating the Firmware to version 1.1 on my MacBook (the black model). Since the update my camera (the one mounted on top of the screen) doesn't work any longer (it keeps capturing a plain green picture) and the led near the camera is always lighted. Is there anyone who had the same problem? Any idea to solve it?
thanks
MacBook Mac OS X (10.4.8)

Hi,
problem solved restarting with OptAlt+PR

Airport doesn't work after firmware update

Hi.
I was using my home wireless network when the Software Update suggested a firmware update to my Airport. I did it, but since then it doesn't work any more. I mean, the Mac can't find it and it keep flashing the yellow light.
Have this happened to anyone else?
Thanks.
Best regards,
T

Try shutting down the DSL modem and your AirPort base station. Leave them S/D for about 5 minutes, then start the DSL modem, allow it to complete its test cycle, then start the AirPort base station.
Repair Permissions - /Applications/Utilities/Disk Utility.app. Start Disk Utility, select your HD and click on Repair Permissions. When finished, quit Disk Utility and then restart your computer.
Go to System Preferences/Network/AirPort
- click on the 'Network Name:' roll-button, select 'Join Other Network...', enter 'Network Name and select the security type you are using, and finally, enter your Password and click 'Join'.
- click on 'Advanced', TCP/IP and confirm that 'Configure IPv4:' is set to 'Using DHCP', click 'OK'.
- click the 'Apply' button and exit System Preferences.
If the above does not work then a factory reset of your AEB might be in order. The setup manuals for all AEBs are here: http://support.apple.com/manuals/#airport

HP Laserjet m1214nfh MFP Doesn't work after firmware updating

Hello
HP Laserjet m1214nfh MFP (USB Connetcion).
I downloaded the latest firmware (ver: 20130211 4 Mars 2013) and updated it.Now it doesn't work and on its LCD it prompts "Initializing" and after some seconds LCD turns off and again prompts "Initializing".
Please guide me.
thank you

Hi,
Please try plugging the printer to a direct power source without any power hub or surge protector usage and check if that may help.
If the same persists please contact HP support by following Technical support after you buy for your region below:
http://www8.hp.com/us/en/contact-hp/ww-contact-us.html
Shlomi
Say thanks by clicking the Kudos thumb up in the post.
If my post resolve your problem please mark it as an Accepted Solution

ThinkPad USB 3.0 Dock - Firmware update doesn't work

Hello,
My company has bought over 200 ThinkPad USB 3.0 Docks to use with HP Folios to connect dual and single monitors. Some users have experience multiple issues with this product and I am trying to determine how to resolve these issues. I first want to update the firmware that is located here: http://support.lenovo.com/en_US/guides-and-manuals/detail.page?DocID=UM014961
ThinkPad USB 3.0 Dock - Firmware Update - Lenovo Docking FW Update Tool V1.0
I have the USB 3.0 dock connected to the 3.0 USB port on the Folio. The unit I am testing seems to be working fine as I have dual monitors up, external keyboard and mouse are working.
I ran the .exe, a command window comes up, and it attempted to look for the device. The text is as shown:
1. Initialzation<> Success
Start Search HUB
!!!No device found!
Press any key to continue . . .
This has been tried on several devices and it simply does not work. Does anybody have any suggestions? I have contacted support which was a complete waste of time because they have no idea what I am talking about.

I'm going to return my dock if possible. My main problem is that I cannot view Vmware virtual machine which is required for work. 2nd I can't view photos on my dual screens, it just hangs saying "Loading...", but I can view them on my W520 LCD Display. 3rd, I can't view a downloaded video, as in an .mp4. I disabled the hardware acceleration in Firefox, so I can see streaming video.
I have a Thinkpad W520 and an X1 Carbon and both exhibit the same problems with the dock.
I tried upgrading the DisplayLink Drivers to the 7.x version and that created a slew of problems. The Dock firmware driver link in the OP doesn't work either. As mentioned it couldn't find the device. Uninstalling the drivers and reinstalling the stock one cause lots of problems with my W520. The dock would try to connect but it kept connecting and disconnecting and the cycle would continue infinitly. It wasn't until I did a system restore that I could get it working again to where I can use the dock again.
I am extremely dissapointed with this dock.

I made a mistake of trying to put 5.0.1 beta 1 firmware on my ipod touch 3rd gen. Now the ipod doesn't work at all. Any suggestions?

I made a mistake of trying to put 5.0.1 beta 1 firmware on my ipod touch 3rd gen ( non-registered) unsuccessfully. Now the ipod doesn't work at all with any public firmware. Any suggestions?

You can try putting the iPod into Recovery Mode and restoring it:
http://support.apple.com/kb/ht1808
If that doesn't work, you'll need to take this up in the forums to which you have access as a member of Apple's iOS developer program.
Regards.

Z87-G45 firmware 1.8, MSI GTX 770 doesn't work

this is really :censored:ing me off
after flashing the new firmware with mflash (i selected bios firmware + ME) my GTX doesn't display on my monitor anymore. i tested with several other monitors and removed the card from the MOBO and it was able to display using the integrated graphics.
I set the bios to display with both the internal and external graphics to force the display so I can troubleshoot the issue. the MOBO sees the 770 in the hardware monitor but its not able to use it. everything is plugged into the card (2 8pin power slots) and it was working before the upgrade.
i reflashed several times and cleared the CMOS with no success and the OS is able to see the card in the device manager...
the card works fine on my other gigabyte MOBO.
everything was great until I flashed the new update

Quote from: flobelix on 22-July-14, 00:14:37
If driver uninstall/reinstall suggested does not work reflash the bios.
>>Use the MSI HQ Forum USB flasher<<
A.) Download the attached archive (180.rar) and place it on your desktop. Do not decompress.
B.) Download and install the Forum flash tool.
C.) Insert your FAT32 formatted usb stick.
D.) Make sure that all win 8 options are disabled. (Fast Boot etc) Also make sure the legacy USB is enabled.
E.) Start the forum flash tool and select option 1. Then point the tool at the compressed archive we downloaded earlier. Then to your USB Flash Drive.
F.) Boot to the USB
G.) Now follow the directions and let the tool flash
H.) After flashing reinstall ME drivers in Windows: http://download.msi.com/dvr_exe/intel_me90_mb.zip
If still no help Try the attached vbios (3D0).
Decompress the provided .rar archive with Winrar: http://www.rarlab.com/download.htm
Then flash the included file with Nvflash for dos: http://www.guru3d.com/files_details/nvflash_download.html
To do so rename the included file to .rom and create a dos bootstick (https://forum-en.msi.com/index.php?topic=165175.0)
Put nvflash and the vbios file on it and boot from the stick. Then type nvflash -4 -5 -6 gop.rom (if renamed vbios that way) and hit enter. Confirm the questions and let the tool flash.
Driver install/update = FAILED... drivers was uninstalled and freshly installed... no change
BIO flash = FAILED... still no change
vbios flash = FAILED... no luck
played around with the bios settings and i managed to get...... something
i'm starting to guess that its the card...

[SOLVED]Xorg 1.8 doesn't work

Hello, I've just upgraded to linux-firmware and the newest X.org, which doesn't work.
Xorg.0.log tells me:
[ 934.318]
X.Org X Server 1.8.1
Release Date: 2010-05-11
[ 934.322] X Protocol Version 11, Revision 0
[ 934.323] Build Operating System: Linux 2.6.33-ARCH x86_64
[ 934.325] Current Operating System: Linux staerseus 2.6.34-ARCH #1 SMP PREEMPT Sat Jun 19 00:07:49 CEST 2010 x86_64
[ 934.326] Kernel command line: root=/dev/disk/by-uuid/727c4683-ee4c-4b32-8a59-370264cb7d9f ro i915.modeset=1 init=/sbin/bootchartd
[ 934.327] Build Date: 26 May 2010 07:50:07PM
[ 934.329]
[ 934.330] Current version of pixman: 0.18.2
[ 934.331] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 934.334] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 934.338] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jun 21 10:15:38 2010
[ 934.340] (==) Using config file: "/etc/X11/xorg.conf"
[ 934.341] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 934.343] (==) No Layout section. Using the first Screen section.
[ 934.343] (==) No screen section available. Using defaults.
[ 934.343] (**) |-->Screen "Default Screen Section" (0)
[ 934.343] (**) | |-->Monitor "<default monitor>"
[ 934.343] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 934.343] (==) Automatically adding devices
[ 934.343] (==) Automatically enabling devices
[ 934.343] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 934.343] Entry deleted from font path.
[ 934.343] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 934.343] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 934.343] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 934.343] (II) Loader magic: 0x7ce880
[ 934.343] (II) Module ABI versions:
[ 934.343] X.Org ANSI C Emulation: 0.4
[ 934.343] X.Org Video Driver: 7.0
[ 934.343] X.Org XInput driver : 9.0
[ 934.343] X.Org Server Extension : 3.0
[ 934.352] (--) PCI:*(0:0:2:0) 8086:2a42:1734:113f Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller rev 7, Mem @ 0xf2400000/4194304, 0xd0000000/268435456, I/O @ 0x00001800/8
[ 934.352] (--) PCI: (0:0:2:1) 8086:2a43:1734:113f Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller rev 7, Mem @ 0xf2100000/1048576
[ 934.352] (II) Open ACPI successful (/var/run/acpid.socket)
[ 934.352] (II) LoadModule: "extmod"
[ 934.352] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 934.352] (II) Module extmod: vendor="X.Org Foundation"
[ 934.352] compiled for 1.8.1, module version = 1.0.0
[ 934.352] Module class: X.Org Server Extension
[ 934.352] ABI class: X.Org Server Extension, version 3.0
[ 934.352] (II) Loading extension MIT-SCREEN-SAVER
[ 934.352] (II) Loading extension XFree86-VidModeExtension
[ 934.352] (II) Loading extension XFree86-DGA
[ 934.352] (II) Loading extension DPMS
[ 934.352] (II) Loading extension XVideo
[ 934.352] (II) Loading extension XVideo-MotionCompensation
[ 934.352] (II) Loading extension X-Resource
[ 934.352] (II) LoadModule: "dbe"
[ 934.352] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 934.352] (II) Module dbe: vendor="X.Org Foundation"
[ 934.353] compiled for 1.8.1, module version = 1.0.0
[ 934.353] Module class: X.Org Server Extension
[ 934.353] ABI class: X.Org Server Extension, version 3.0
[ 934.353] (II) Loading extension DOUBLE-BUFFER
[ 934.353] (II) LoadModule: "glx"
[ 934.353] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 934.353] (II) Module glx: vendor="X.Org Foundation"
[ 934.353] compiled for 1.8.1, module version = 1.0.0
[ 934.353] ABI class: X.Org Server Extension, version 3.0
[ 934.353] (==) AIGLX enabled
[ 934.353] (II) Loading extension GLX
[ 934.353] (II) LoadModule: "record"
[ 934.353] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 934.353] (II) Module record: vendor="X.Org Foundation"
[ 934.353] compiled for 1.8.1, module version = 1.13.0
[ 934.353] Module class: X.Org Server Extension
[ 934.353] ABI class: X.Org Server Extension, version 3.0
[ 934.353] (II) Loading extension RECORD
[ 934.353] (II) LoadModule: "dri"
[ 934.353] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 934.353] (II) Module dri: vendor="X.Org Foundation"
[ 934.353] compiled for 1.8.1, module version = 1.0.0
[ 934.353] ABI class: X.Org Server Extension, version 3.0
[ 934.353] (II) Loading extension XFree86-DRI
[ 934.354] (II) LoadModule: "dri2"
[ 934.354] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 934.354] (II) Module dri2: vendor="X.Org Foundation"
[ 934.354] compiled for 1.8.1, module version = 1.2.0
[ 934.354] ABI class: X.Org Server Extension, version 3.0
[ 934.354] (II) Loading extension DRI2
[ 934.354] (==) Matched intel as autoconfigured driver 0
[ 934.354] (==) Matched vesa as autoconfigured driver 1
[ 934.354] (==) Matched fbdev as autoconfigured driver 2
[ 934.354] (==) Assigned the driver to the xf86ConfigLayout
[ 934.354] (II) LoadModule: "intel"
[ 934.354] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 934.354] (II) Module intel: vendor="X.Org Foundation"
[ 934.354] compiled for 1.7.6, module version = 2.11.0
[ 934.354] Module class: X.Org Video Driver
[ 934.354] ABI class: X.Org Video Driver, version 6.0
[ 934.354] (EE) module ABI major version (6) doesn't match the server's version (7)
[ 934.356] (II) UnloadModule: "intel"
[ 934.356] (II) Unloading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 934.356] (EE) Failed to load module "intel" (module requirement mismatch, 0)
[ 934.357] (II) LoadModule: "vesa"
[ 934.357] (WW) Warning, couldn't open module vesa
[ 934.357] (II) UnloadModule: "vesa"
[ 934.357] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 934.359] (II) LoadModule: "fbdev"
[ 934.359] (WW) Warning, couldn't open module fbdev
[ 934.359] (II) UnloadModule: "fbdev"
[ 934.359] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 934.360] (EE) No drivers available.
[ 934.362]
Fatal server error:
[ 934.364] no screens found
[ 934.365]
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 934.370] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 934.372]
What does the problem with modules mean? Archlinux was warning me, that "in future releases /etc/modprobe.d/framebuffer_blacklist.conf.save will be ignored, but it is the same file as /etc/modprobe.d/framebuffer_blacklist.conf.
I don't understand, why it cannot find any screens (I use a laptop screen)
I tried to start with and without xorg.conf, which is:
Section "Device"
Identifier "Intel X4500MHD"
Driver "intel"
VendorName "Intel Corporation"
BoardName "Mobile 4 Series Chipset Integrated Graphics Controller"
BusID "PCI:0:2:0"
Option "DRI" "true"
Option "AccelMethod" "uxa"
Option "MigrationHeuristic" "greedy"
EndSection
The graphic driver I use is xf86-video-intel-newest from archstuff, but it is the same version as xf86-video-intel.
I am not sure if I provided all needed info, but I hope so. Thank you for your help.SOLVED
Last edited by Staerseus (2010-06-21 09:18:03)

Use the arch version. It is actually built against the xorg version that you are using... here is the relevant section of your log:
[ 934.354] (EE) module ABI major version (6) doesn't match the server's version (7)

[SOLVED] network randomly doesn't work after reboot (e100)

Hi
Lately I have some weird issues with network. I shutdown computer during night, so basicly I reboot it at least once per day and every now and then without any pattern network doesn't work at all and so far only solution I have found is to reboot (again).
Before anything else I'm sure it's not hardware problem, since other OS on same computer don't have any issues, neither is router since other devices in network from laptops to mobile phones work flawless.
Relevant info and what I have found so far (not everything is copy/pasted so there may be some typos):
$less rc.conf (network part)
eth1="eth1 192.168.1.242 netmask 255.255.255.0 broadcast 192.168.1.255
INTERFACES=(eth1)
gateway="default gw 192.168.1.1"
ROUTES=(gateway)
$ifconfig
eth1 Link encap:Ethernet HWaddr 00:D0:B7:5A:7A:A9
inet addr:192.168.1.242 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:380 errors:0 dropped:0 overruns:0 frame:0
TX packets:380 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:36154 (35.3 Kb) TX bytes:36154 (35.3 Kb)
$route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth1
$ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data
From 192.168.1.242 icmp_seq=2 Destination Host Unreachable
So basicly network is dead, can't even ping router, cable connection is detected tho (lights are on). I have tried to restart newtork with /etc/rc.d/network stop/start, nothing. Only clue is dmesg.
$dmesg
Linux version 2.6.30-ARCH (root@T-POWA-LX) (gcc version 4.4.1 (GCC) ) #1 SMP PREEMPT Fri Jul 31 07:30:28 CEST 2009
e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
e100 0000:03:07.0: PCI INT A -> Link[APC2] -> GSI 17 (level, low) -> IRQ 17
e100 0000:03:07.0: PME# disabled
e100: eth1: e100_probe: addr 0xfdfff000, irq 17, MAC addr 00:d0:b7:5a:7a:a9
e100 0000:03:07.0: firmware: requesting e100/d101m_ucode.bin
ADDRCONF(NETDEV_UP): eth1: link is not ready
modrope -r e100 and then reloading it doesn't help either, but reboot does (once I had to reboot twice tho).
Anyone with more clue and ideas then me, it's getting really annoying, it also kill whole KDE plasma-desktop for couple of minutes before plasmoids find out network is really down and I'm not really fan of morning "gamble". I can't pinpoint some hard date/update when this started to happening because like I said it's random but last couple of months should be quite accurate. Thanks in advance.
EDIT: dmesg when network works:
tilen@pikmin ~]$ dmesg | grep e100
pci 0000:03:07.0: Firmware left e100 interrupts enabled; disabling
e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
e100 0000:03:07.0: PCI INT A -> Link[APC2] -> GSI 17 (level, low) -> IRQ 17
e100 0000:03:07.0: PME# disabled
e100: eth0: e100_probe: addr 0xfdfff000, irq 17, MAC addr 00:d0:b7:5a:7a:a9
Last edited by NoOrdinary (2009-09-05 09:47:20)

I don't have anything special set at router but I doubt rc.conf play any role. I will try to set it up with dhcp (but I think I have tried that already) if there is any change.
This morning I had to reboot twice, so new kernel didn't help. Fowler, what network card are you using, also e100 (well or some intel)? I dunno, should this be handed to the kernel team? If it will piss me enough one morning I'll just go and buy a new network card, just wanna be sure that will really solve the problem.
UPDATE: OK, this is just silly. I remebered I have acctualy onboard LAN so I edited rc.conf and dived into the dust under my desk to move cable and there I found out it was acctual onboard in use all the time Now this dosen't make much sense to me anymore, when I can't get net up all the stuff in dmesg is e100 related. Anyway, I connected network to e100 and rebooted, suprise, same story. Dmesg reported again link was not ready. I edited rc.conf to
INTERFACES=(eth0 !eth1)
in case this has anything to do with proper timing at assigning whatever needs to be assigned to network cards at boot so I'm sure just 1 card with all info provided get's kicked in at boot. First reboot after that works, it dosen't prove anything yet but at leat it's some kind of progress in recognising proper cause.
UPDATE 2: Nah, still happens. Googling for "no link during initialization" show a lot of familiar problems, almost all on nforce motherboards and mine is nforce too. I just don't get it why this mess seperate PCI network card. In any case it's extremely annoying.
Last edited by NoOrdinary (2009-09-02 11:46:27)

Skydrive built in app wont let me update it and it doesn't work

A day after the name change became official my built in skydrive app stopped working. Every time I click on the app it loads the clouds then goes to a message "This location can't be found, please try again later", then it flat crashes and I
am back at the start screen. What the hell people, why? Also, why the hell can't I uninstall it then just re-install it? What on earth possessed you into believing that this app HAS TO BE BUILT IN, for god's sake Microsoft the damn thing is broken now and
the only possible way I can think of to fix it would be to refresh the OS which I don't want to do because then I have to sit around and let it update all over again plus I would have to re-install my programs as well. I hope you not only fire the engineer
who thought this was a good idea but I also hope you castrate him. This was truly a sad, unnecessary, stupid act to do. All you idiots had to do was make this no different from office 365 and I would have uninstalled it, re-installed it and probably saved
us all the trouble. Also, it hasn't stopped me from using onedrive but the entire point of your built in app has become pointless, it doesn't work because of your name change for some reason and now I can't fix it without sacrificing a whole damn day to get
back to where I am at. Would it be too much for you to make this onedrive app removable in your next firmware update? As of now, I have removed your office 365 because that was a pointless thing to have when I already have office 2007 but now I am stuck with
this broken skydrive app that I can't fix, update, or remove without sacrificing my time. It is not easy re-installing a program like bluebeam revu you know and as of yesterday my photos app has now become just like the skydrive app, it doesn't work, my pictures
are all there but the app itself keeps crashing. Seriously man, let us remove your trashy apps and let me re-install it already

Hi,
"A day after the name change became official my built in skydrive app stopped working"
Did you point that SkyDrive changed to OneDrive?
Did you move your OneDrive to another location or change its name?
Please login OneDrive with web-based to check if you could access it successfully.
Please refer to the following article to try the troubleshooter and check the service status:
SkyDrive: FAQ
http://windows.microsoft.com/en-in/windows-8/skydrive-app-faq
Karen Hu
TechNet Community Support

Wired connection doesn't work if cable is not plugged in at boot time

Hey all,
I started using arch a few days ago and I simply love it, but I have a problem. The wired connection doesn't work if the cable is not plugged in at boot time, or if it was plugged in at boot time, then plugged out and in again. Switching it off and on again via the gui has the same effect. I am using NetworkManager with dhcpcd, NetworkManager is started via systemd, dhcpcd is not, I let NetworkManager do that. When I started investigating this problem there were some remnants of netctl, but now NetworkManager is the only networking-related service started at boot time. When the cable is plugged back in, NM-applet shows that it's connected, and an IP address is assigned, but the connection doesn't work.
Here's some information regarding the system:
It's a lenovo G50-70 laptop, it uses the r8169 driver for ethernet. (I dualboot it with windows 8.1, but arch is default and all this stuff happens also if i only use arch)
The router is a Linksys EA2700/N600
journalctl -u NetworkManager
aug 26 19:14:33 arch_daboka NetworkManager[527]: <info> NetworkManager (version 0.9.10.1) is starting...
aug 26 19:14:33 arch_daboka NetworkManager[527]: <info> Read config: /etc/NetworkManager/NetworkManager.conf
aug 26 19:14:33 arch_daboka NetworkManager[527]: <info> WEXT support is enabled
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> Loaded plugin keyfile: (c) 2007 - 2013 Red Hat, Inc. To report bugs please use the NetworkMan
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> new connection /etc/NetworkManager/system-connections/Bokros
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> new connection /etc/NetworkManager/system-connections/1. vezetékes kapcsolat
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> new connection /etc/NetworkManager/system-connections/UPC1838142
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> monitoring kernel firmware directory '/usr/lib/firmware'.
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.3/0000:02:00.0/iee
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1f.0/PNP0C09:00/VPC20
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> WiFi hardware radio set enabled
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> WWAN hardware radio set enabled
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-wifi.so
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-wwan.so
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-adsl.so
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-bluetooth.so
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> WiFi enabled by radio killswitch; enabled by state file
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> WWAN enabled by radio killswitch; enabled by state file
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> WiMAX enabled by radio killswitch; enabled by state file
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Networking is enabled by state file
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (lo): link connected
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (lo): carrier is ON
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (lo): new Generic device (driver: 'unknown' ifindex: 1)
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (lo): exported as /org/freedesktop/NetworkManager/Devices/0
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): carrier is OFF
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): new Ethernet device (driver: 'r8169' ifindex: 2)
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): exported as /org/freedesktop/NetworkManager/Devices/1
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
aug 26 19:14:36 arch_daboka systemd[1]: Started Network Manager.
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): preparing device
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): using nl80211 for WiFi device control
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): driver supports Access Point (AP) mode
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): new 802.11 WiFi device (driver: 'ath9k' ifindex: 3)
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): exported as /org/freedesktop/NetworkManager/Devices/2
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): preparing device
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> use BlueZ version 5
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> wpa_supplicant started
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0) supports 4 scan SSIDs
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: starting -> ready
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: ready -> disconnected
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0) supports 4 scan SSIDs
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: disconnected -> inactive
aug 26 19:14:42 arch_daboka NetworkManager[527]: <info> startup complete
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Auto-activating connection 'Bokros'.
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) starting connection 'Bokros'
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) scheduled...
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) started...
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTING
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) scheduled...
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) complete.
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) starting...
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: prepare -> config (reason 'none') [40 50 0]
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0/wireless): connection 'Bokros' has security, and secrets exist. No new sec
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: added 'ssid' value 'Bokros'
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: added 'scan_ssid' value '1'
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: added 'psk' value '<omitted>'
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) complete.
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: set interface ap_scan to 1
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: inactive -> authenticating
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: authenticating -> associated
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: associated -> 4-way handshake
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: 4-way handshake -> completed
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireles
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 3 of 5 (IP Configure Start) scheduled.
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 3 of 5 (IP Configure Start) started...
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: config -> ip-config (reason 'none') [50 70 0]
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> dhcpcd started with pid 3599
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 3 of 5 (IP Configure Start) complete.
aug 26 19:15:01 arch_daboka dhcpcd[3599]: version 6.4.3 starting
aug 26 19:15:01 arch_daboka NetworkManager[527]: dhcpcd[3599]: version 6.4.3 starting
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> (wlp2s0): DHCPv4 state changed nbi -> preinit
aug 26 19:15:01 arch_daboka dhcpcd[3599]: DUID 00:01:00:01:1b:7c:0d:d6:28:d2:44:7f:89:66
aug 26 19:15:01 arch_daboka dhcpcd[3599]: wlp2s0: IAID 65:59:c9:b5
aug 26 19:15:01 arch_daboka NetworkManager[527]: dhcpcd[3599]: DUID 00:01:00:01:1b:7c:0d:d6:28:d2:44:7f:89:66
aug 26 19:15:01 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: IAID 65:59:c9:b5
aug 26 19:15:01 arch_daboka dhcpcd[3599]: wlp2s0: soliciting an IPv6 router
aug 26 19:15:01 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: soliciting an IPv6 router
aug 26 19:15:02 arch_daboka dhcpcd[3599]: wlp2s0: rebinding lease of 192.168.1.137
aug 26 19:15:02 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: rebinding lease of 192.168.1.137
aug 26 19:15:07 arch_daboka dhcpcd[3599]: wlp2s0: leased 192.168.1.137 for 86400 seconds
aug 26 19:15:07 arch_daboka dhcpcd[3599]: wlp2s0: adding route to 192.168.1.0/24
aug 26 19:15:07 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: leased 192.168.1.137 for 86400 seconds
aug 26 19:15:07 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: adding route to 192.168.1.0/24
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> (wlp2s0): DHCPv4 state changed preinit -> reboot
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> address 192.168.1.137
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> plen 24 (255.255.255.0)
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> gateway 192.168.1.1
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> server identifier 192.168.1.1
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> lease time 86400
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> hostname 'arch_daboka'
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> nameserver '192.168.1.1'
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> domain name 'chello.hu'
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 5 of 5 (IPv4 Commit) started...
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 5 of 5 (IPv4 Commit) complete.
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_LOCAL
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_GLOBAL
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Policy set 'Bokros' (wlp2s0) as default for IPv4 routing and DNS.
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Writing DNS information to /usr/bin/resolvconf
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) successful, device activated.
aug 26 19:15:14 arch_daboka dhcpcd[3599]: wlp2s0: no IPv6 Routers available
aug 26 19:15:14 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: no IPv6 Routers available
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): link connected
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 4
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Auto-activating connection '1. vezetékes kapcsolat'.
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) starting connection '1. vezetékes kapcsolat'
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 1 of 5 (Device Prepare) scheduled...
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 1 of 5 (Device Prepare) started...
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 2 of 5 (Device Configure) scheduled...
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 1 of 5 (Device Prepare) complete.
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 2 of 5 (Device Configure) starting...
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: prepare -> config (reason 'none') [40 50 0]
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 2 of 5 (Device Configure) successful.
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 3 of 5 (IP Configure Start) scheduled.
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 2 of 5 (Device Configure) complete.
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 3 of 5 (IP Configure Start) started...
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: config -> ip-config (reason 'none') [50 70 0]
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> dhcpcd started with pid 4322
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 3 of 5 (IP Configure Start) complete.
aug 26 19:15:34 arch_daboka dhcpcd[4322]: version 6.4.3 starting
aug 26 19:15:34 arch_daboka dhcpcd[4322]: DUID 00:01:00:01:1b:7c:0d:d6:28:d2:44:7f:89:66
aug 26 19:15:34 arch_daboka dhcpcd[4322]: enp1s0: IAID 44:7f:89:66
aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: version 6.4.3 starting
aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: DUID 00:01:00:01:1b:7c:0d:d6:28:d2:44:7f:89:66
aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: IAID 44:7f:89:66
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): DHCPv4 state changed nbi -> preinit
aug 26 19:15:34 arch_daboka dhcpcd[4322]: enp1s0: soliciting an IPv6 router
aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: soliciting an IPv6 router
aug 26 19:15:34 arch_daboka dhcpcd[4322]: enp1s0: rebinding lease of 192.168.1.138
aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: rebinding lease of 192.168.1.138
aug 26 19:15:39 arch_daboka dhcpcd[4322]: enp1s0: leased 192.168.1.138 for 86400 seconds
aug 26 19:15:39 arch_daboka dhcpcd[4322]: enp1s0: adding route to 192.168.1.0/24
aug 26 19:15:39 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: leased 192.168.1.138 for 86400 seconds
aug 26 19:15:39 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: adding route to 192.168.1.0/24
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): DHCPv4 state changed preinit -> reboot
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> address 192.168.1.138
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> plen 24 (255.255.255.0)
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> gateway 192.168.1.1
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> server identifier 192.168.1.1
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> lease time 86400
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> hostname 'arch_daboka'
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> nameserver '192.168.1.1'
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> domain name 'chello.hu'
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 5 of 5 (IPv4 Commit) started...
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 5 of 5 (IPv4 Commit) complete.
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_LOCAL
aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_GLOBAL
aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> Policy set '1. vezetékes kapcsolat' (enp1s0) as default for IPv4 routing and DNS.
aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> Writing DNS information to /usr/bin/resolvconf
aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) successful, device activated.
aug 26 19:15:47 arch_daboka dhcpcd[4322]: enp1s0: no IPv6 Routers available
aug 26 19:15:47 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: no IPv6 Routers available
ping -c 10 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=4.38 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=2.79 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=4.89 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=5.30 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1.59 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=1.61 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=4.37 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=2.40 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=6.47 ms
--- 192.168.1.1 ping statistics ---
10 packets transmitted, 9 received, 10% packet loss, time 9014ms
rtt min/avg/max/mdev = 1.599/3.759/6.471/1.627 ms
ping -c 100 8.8.8.8 - it's not completely disconnected, but it's always 8 packets at once that are received
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=20 ttl=46 time=41.7 ms
64 bytes from 8.8.8.8: icmp_seq=21 ttl=46 time=40.0 ms
64 bytes from 8.8.8.8: icmp_seq=22 ttl=46 time=38.8 ms
64 bytes from 8.8.8.8: icmp_seq=23 ttl=46 time=39.3 ms
64 bytes from 8.8.8.8: icmp_seq=24 ttl=46 time=41.8 ms
64 bytes from 8.8.8.8: icmp_seq=25 ttl=46 time=38.4 ms
64 bytes from 8.8.8.8: icmp_seq=26 ttl=46 time=38.4 ms
64 bytes from 8.8.8.8: icmp_seq=27 ttl=46 time=38.0 ms
64 bytes from 8.8.8.8: icmp_seq=56 ttl=46 time=43.4 ms
64 bytes from 8.8.8.8: icmp_seq=57 ttl=46 time=49.8 ms
64 bytes from 8.8.8.8: icmp_seq=58 ttl=46 time=40.2 ms
64 bytes from 8.8.8.8: icmp_seq=59 ttl=46 time=44.3 ms
64 bytes from 8.8.8.8: icmp_seq=60 ttl=46 time=38.5 ms
64 bytes from 8.8.8.8: icmp_seq=61 ttl=46 time=43.4 ms
64 bytes from 8.8.8.8: icmp_seq=62 ttl=46 time=39.2 ms
64 bytes from 8.8.8.8: icmp_seq=63 ttl=46 time=40.5 ms
64 bytes from 8.8.8.8: icmp_seq=92 ttl=46 time=38.3 ms
64 bytes from 8.8.8.8: icmp_seq=93 ttl=46 time=43.7 ms
64 bytes from 8.8.8.8: icmp_seq=94 ttl=46 time=42.3 ms
64 bytes from 8.8.8.8: icmp_seq=95 ttl=46 time=46.6 ms
64 bytes from 8.8.8.8: icmp_seq=96 ttl=46 time=44.9 ms
64 bytes from 8.8.8.8: icmp_seq=97 ttl=46 time=42.9 ms
64 bytes from 8.8.8.8: icmp_seq=98 ttl=46 time=41.7 ms
64 bytes from 8.8.8.8: icmp_seq=99 ttl=46 time=37.8 ms
--- 8.8.8.8 ping statistics ---
100 packets transmitted, 24 received, 76% packet loss, time 99062ms
rtt min/avg/max/mdev = 37.886/41.455/49.829/3.000 ms
cat /etc/dhcpcd.conf - I tried clientid instead of duid and disabling IPv6, but neither of those helped.
# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.
# Inform the DHCP server of our hostname for DDNS.
hostname
# Use the hardware address of the interface for the Client ID.
#clientid
# or
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
duid
# Persist interface configuration when dhcpcd exits.
persistent
# Rapid commit support.
# Safe to enable by default because it requires the equivalent option set
# on the server to actually work.
option rapid_commit
# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Most distributions have NTP support.
option ntp_servers
# Respect the network MTU.
# Some interface drivers reset when changing the MTU so disabled by default.
#option interface_mtu
# A ServerID is required by RFC2131.
require dhcp_server_identifier
# Generate Stable Private IPv6 Addresses instead of hardware based ones
slaac private
# A hook script is provided to lookup the hostname if not set by the DHCP
# server, but it should not be run by default.
nohook lookup-hostname
#noipv4ll
#Disable IPv6
#noipv6rs
#noipv6
cat /etc/NetworkManager/NetworkManager.conf
[main]
plugins=keyfile
dhcp=dhcpcd
## Set static hostname
#[keyfile]
#hostname=foobar
## HTTP-based connectivity check
#[connectivity]
#uri=http://nmcheck.gnome.org/check_network_status.txt
I couldn't find anything else to append, but if there are other log or conf files or anything else, which would help solving the problem, I should put here, please tell me.

Try to use dhclient perhaps? Might I also suggest letting systemd deal with the dhcp issue and not NM. That may seem incongruous but it is possible NM is mis-handling the dhcp hand-off to the network card. I'm no guru but I got thinking about this when I saw this in your output:
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_LOCAL
It is very possible that I'm mis-interpreting this information so please take it with a boulder of salt.

[SOLVED]Custom DSDT not loading - OEM battery doesn't work - Sony Vaio

EDITING ORIGINAL POST TO POST SOLUTION so I don't do a massive bump
Installed windows and ran the BIOS flasher that came with the battery. Didn't work until I changed a line in the plaintext configuration file (config.ini or something) it comes with. Changed "Capacity: 20" to "Capacity: -10". This changed the battery charge requirement from 20% to negative ten percent (any negative number will do), allowing the program to run and flash the BIOS. Didn't realize I could do that, but it fixed the problem 100%.
#### BEGIN ORIGINAL POST: ################################
Hey guys,
I'm a bit of a linux noob, but I've spent many hours this week trying to fix this issue on my own and have learned a lot about making custom kernels, hardware stuff, ACPI, and ABS. However, nothing I've done has worked and I've hit a wall. For reference, I'm on a Sony Vaio VGN-FZ4000 with linux-3.0 base kernel, gnome3/gdm. The battery is made in china and doesn't list a manufacturer, just model number BPS8, 52000mAh.
[Backstory]
So I recently got an OEM battery to replace the broken original, which hasn't worked since before I installed arch (though it worked with an Arch install I did a couple years ago). When I first plugged it in, the gnome battery symbol popped up listing the battery at 0% with an exclamation icon. I unplugged from AC power and the laptop still ran, but the battery monitor just said it was at 0% and 'Estimating' remaining time. I figured this was a glitch with gnome or just because it was this battery's first cycle so I let it run down until it hard-crashed. Then I plugged back into AC and tried to turn on the computer, but it wouldn't do anything until I removed the battery.
Looking into the problem I discovered this was due to the ACPI firmware table DSDT being compiled for Windows, which has, shall we say, fewer restrictions on sanity than the Intel ASL compiler used for UNIX systems. Sure enough I extracted /sys/firmware/acpi/tables/DSDT to find that its section about the battery contained the entry 'Zero' for Battery Technology, which translates to "non-rechargeable", rather than 'One', which makes it chargeable. acpitool confirmed this; my system thought the battery was non-rechargeable and was constantly discharging it. Needless to say I've only been putting it in temporarily to test solutions since.
[/backstory]
[tl;dr] DSDT firmware contains malformed battery description, now I can't get my system to run with a custom DSDT. [/tl;dr]
Attempted solutions:
[1]
Extract, modify, recompile DSDT and include it with the kernel compilation .config options
CONIFG_ACPI_CUSTOM_DSDT=y
CONFIG_ACPI_CUSTOM_DSDT_FILE="/usr/src/custom_dsdt.hex
CONIFG_STANDALONE=n
as suggested here, a page linked to by the arch wiki page on DSDT.
I followed the instructions but no matter what this has generated errors during the kernel compilation, sometimes due to every line containing unexpected \231 (or other numbers) characters, sometimes finding some error in the DSDT file and then claiming that the driver it was compiling (ol.c somewhere in the drivers/acpi section I believe) had references to undefined functions all over the place. I CANNOT compile with a custom DSDT specified.
[2]
Place recompiled DSDT in /lib/initcpio/custom.dsdt and add 'dsdt' to the HOOKS in mkinitcpio (and rebuild the initramfs-linux-*.img, of course). Another version of this included recompiling the kernel with CONFIG_STANDALONE disabled.
In neither of these situations has the running DSDT ever been anything but the BIOS-supplied one and not once has the battery shown any different behavior.
acpitool and $ cat /proc/acpi/battery/BAT0/info have consistently claimed the information specified in the BIOS-supplied DSDT; the battery is non-rechargeable and is discharging at an unknown rate. Sometimes acpi will even report that the battery has zero capacity.
The arch wiki does say mkinitcpio doesn't support the dsdt hook as of 2.6.30, but [1] didn't work either and mkinitcpio -H dsdt still told me to try this so I did.
[3]
The final solution I have tried has been to do [2] but to recompile the kernel with the legacy support for battery and ac adapter stuff disabled. I tried this because it was suggested in the kernel.log;
Sep 13 11:51:03 localhost kernel: [ 11.740059] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Sep 13 11:51:03 localhost kernel: [ 11.753434] ACPI: AC Adapter [ADP1] (on-line)
The corresponding line now reads
ACPI: AC Adapter [ADP1] (on-line)
(The same goes for the battery BAT0)
but all this does is remove the battery/ and adp1/ folders from /proc/acpi/ and break acpitool functionality. The log still doesn't mention the dsdt hook, either.
[4]
The old way to do this was to use the acpi-dsdt-initrd-patch-* patch, but that hasn't been updated for modern kernels, presumably because of the new "functionality" from mkiniticpio. The current kernel .config doesn't include any options for ACPI initrd/initramfs support or reading a DSDT from initramfs, which is the functionality provided by this patch.
This covers all the methods I've been able to find on the internet and I'm at a loss for what to do. Am I doing something wrong in [1]? Under what conditions will the compiler fail/succeed with a CONFIG_ACPI_CUSTOM_DSDT_FILE?
When I recompile I fix the 'Zero' definition and a couple compiler errors and warnings. The errors come from section length definitions, which read as 0x00000000 rather than the appropriate max-min value so I fix those, and the warnings come from _T_* methods belonging to the compiler, so I refactor the code to remove the initial underscores. The last warning comes from an isolated And statement that's within brackets (compiler complains it doesn't do anything), but if I remove that the compiler fails hard.
Thanks to anyone who's read this far. Please let me know if you have any ideas how to get my system to use a customized DSDT.
Last edited by paraffin (2011-09-29 23:20:30)

Thanks for the offer, Radioactive man However, I'm actually compiling a customized kernel with the linux-ck and -sony patches, so your packages won't help. (The custom kernel works fine and I've tested this battery behavior on the the regular, -ck, and -sony kernels as well)
Anyway, so I tried another compile with
CONFIG_PREVENT_FIRMWARE_BUILD=n in addition to the options listed in [1] and that time it compiled.
Unfortunately it still didn't load the DSDT!
I did catch a quick little error message that turned up in kernel.log though;
/var/log/kernel.log:Sep 15 11:50:24 localhost kernel: [ 0.925780] acerhdf: unknown (unsupported) BIOS version Sony Corporation/VGN-FZ4000E/R2110J7, please report, aborting!
acerhdf is a fan controller module for the Aspire One, and perhaps I left that in the kernel config and it's preventing the custom DSDT from loading, even though the acerhdf module never gets loaded itself, nor is it in my rc.conf or anything else... If that was the cause of all this, I'm gonna be angry...
Anyway, this message does not appear with my latest kernel build because I took off the custom DSDT option, hoping to be able to use ACPI_CUSTOM_METHOD=y, which supposedly allows one to inject a custom AML method into a debug fs. It wouldn't have worked anyway, as it doesn't let you modify Device sections, but even with a dummy method insertion it didn't give my root modification privileges as it was supposed to...
Will try recompiling AGAIN with this CONFIG_ACERHDF=n (it's simply 'not set' in my current .config), while also enabling the custom kernel etc. If this doesn't work I have no idea what I'll do.
Anyway, thanks for your help and time:

DHCP & self-assigned IP problem-Airport doesn't work

I'm not really a technical type, but I'm pretty quick to pick things up and several weeks of trying to deal with this issue has made me pretty knowledgeable about things related to it specifically.
Background:
I have a month-old Macbook Pro that runs Snow Leopard and is up to date on all its software stuff. On our home network we have another pretty new Macbook Pro running 10.5.9 and a fairly old Macbook also running 10.5.9.
We have a Linksys WRT54G wireless router. Our network uses a 40-bit Hex WEP password.
Problem(s):
When I try to connect to our wireless network, Network preferences tells me that it cannot connect because of a self-assigned IP address. Sure enough, the IP address DHCP comes up with is of the 64.XX.XX.XX variety. Google's revealed that this is a common problem for all recent versions of OSX, back to at least Tiger.
The "subnet mask" it comes up with is 255.255.0.0, which is different from the settings on our other (working) computers, which is 255.255.255.0. I'm not sure what this means, or whether it's significant. Renewing the DHCP lease either comes up with the same 64.XX.XX.XX type or, sometimes, it comes up with no IP settings at all. The most frustrating thing about this is that if I chose "DHCP with manual address" and type in any in our set that I've confirmed isn't in use and hit "apply", as soon as I go back to the panel it has reverted to the 64.XX.XX.XX type.
I've also tried manually entering the router/subnet mask/IP data, as well as the DNS numbers, and that leads to the Network Settings connectivity dot thing being green, but the internet still doesn't work. In those cases, diagnostics claims that everything is fine up to and including the ISP, but that it's unable to connect to the server and internet.
Of note: some people with a similar problem have talked about networks with this problem working intermittently, but mine seems to be consistently broken.
Initially I was able to avoid fixing the problem by using our neighbors' unsecured wireless network, which is sort of awful, I know, but at least it kept me from having to deal with this for a while. Today it started to do the same thing to that network. Both networks continue to work on our Macbook and other Macbook Pro, which is why I don't think that it's a router problem.
I've been able to connect to our other computers through computer-to-computer networks—going through our main shared network (and thus the wireless router) doesn't seem to work—which I think shows that the Airport card/hardware itself is intact (?). I did try connecting to the internet through the "internet sharing" option on our Macbook, but that had the exact same problems.
Another thing that may or may not be relevant, but is equally infuriating:
I've also noticed that my Macbook Pro has more trouble staying connected to a network than our Macbook—even when it was working, it disconnected/timed out extremely often, which is something our Macbook never does, even from the same location. When I try to connect to a network it spends a very long time displaying the "searching for network" animation in the menu bar icon, sometimes after the Network Preferences pane believes that it's connected, and sometimes even after I hit the button to turn Airport off. It's also started refusing to connect to any networks at all, on occasion, which is especially evident in the process of the diagnostics box thingy, because there it actually tells me it's unable to connect rather than just playing the searching animation for ages.
Here are some other things that I've tried:
setting up a new 'location'
restarting the computer
deleting the airport preferences file
restarting in safe mode
restarting open firmware
confirming that the firewall allows all incoming thingies
resetting the router
making sure the keychain password allows all applications to access it
connecting to the internet through a computer-to-computer network from another machine
Because the situation has deteriorated over time, I'd also like to know whether people think that it's two problems (the type of router then later the airport hardware(?)/software(?) itself, perhaps) or just one. Since I've tried basically everything besides switching out our router, I'm kind of inclined to blame it on that, especially because one of the more plausible explanations for this problem that I've heard is a time-out error due to Airport expecting a faster response than it's able to get from older routers; however, the fact that other networks haven't been working means that it's not likely to be just the router. If it's just one problem, which is the simpler explanation, then I guess there's something properly wrong with my computer's software, in which case I guess I'll take it to the Apple Store. :/
I'm in love with my computer otherwise, and I'll admit that I spent a good twenty minutes sobbing out of frustration over this. Any help would be immensely appreciated.

HI and Welcome to Apple Discussions...
Try Changing the Airport Channel
Open AirPort Utility, located in the Utilities folder in the Applications folder on a computer using Mac OS X.
Select the device you’re setting up, and then click Manual Setup. Enter the base station password if necessary
Click AirPort in the toolbar, and then click Wireless.
Choose a new channel from the Channel pop-up menu.
Carolyn

Firmware 1.1.2 doesn't work?

Similar Messages

Maybe you are looking for