![]() Sigh! That second person promissed “it will be activated by Friday night”, that was last Wednesday, … Of course nothing was unlocked by Friday, nor Saturday, or Sunday, … not even this morning, … but now it is! So I had to dictate (wait what, should they not have that in their system to start with?) IMEI to a call center agent, and they pass it along to their Apple contact department, … And after the promised “unlocked in a week” had passed, nothing was unlocked and I called again: to find out that T-Mobile had not even passed it to Apple, yet. Unfortunately the IMEI exchange from the exclusive phone resellers to Apple is a little lazy, works by exchanging spreadsheets or even good old facsimile transmissions and does not appear to be directly database record exchange oriented. ![]() It only took 2 years for the contract to expire and endless calls to T-Mobile Germany. Update: Turned out every new version of udev started to use another just new Linux system-call - as T2 uses dietlibc for the initramfs early-userspace we had to add support for a dozen new system-calls to dietlibc, just to update udev, again, sigh! Rm -f etc/udev/rules.d/lesĪnd some very unnecessary down-time later an the system was back online running on the new server blade.Īnd this is even the second time this year the persistent naming got in my way - guess I’ll remove this persistent name gibberish from the default build. Remote management kept black, and scheduling a reboot into the maintenance PXE & NFS recovery system revealed udev used it’s default persistent name glue to rename the new boards’s NIC with (obviously) different MAC from eth0 to eth1. ![]() But you probably already guessed so from the headline, … udev was again in between us and the network packet flow :-(! In the past we usually had no problem with this, even tested it to be prepared for such disaster. Would the remote machine come back to remote managed life, or would it not? The box was flunky and we eventually decided to exchange the hardware to cure sporadic reboots (may have been a faulty cooling fan, …). Wasting my time during emergency maintenance at a remote datacenter server. Update 3: wow, just wow, less than an inch thick Compulab PC3, with AMD Fusion Embedded G series APU It looks like the VIA dual-core Nano X2 will again arrive late to the party, and the more performant Bobcat will not leave much niche for VIA to play (abysmal open source 3D drivers will do it’s rest).Ĭheers from my side -to booth of them- putting some real pressure on Intel, and I am desperately looking forward to sub 10W, slim & light AMD ultra portables:Īnd who knows, maybe we will eventually see AMD’s latest, greatest shipping in one or the other Apple, too … However, enough performance for a snappy web browser and video playback is certainly welcome as are more than 1024×600 pixel real estate to view more than a Twitter tweet as well as to drive more than an aging VGA link on your favorite desktop to do real work. One certainly does not need exorbitant number crunching performance while on-the-go. The new AMD C-50 and E-350 set off to finally end the performance stagnation that is the Intel Atom. ![]() Finally, with the CES 2011 AMD finally set free the new Fusion APUs built from the power-efficient Bobcat micro architecture.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |