IT Systemelektroniker & Master of Science, IT Security, Networks, Embedded Systems, Docker Campus Ambassador and Raspberry Pi Geek
If you killed your trusty grub (i.e. by new Install of Windows 8.. :/) you can repair it quite easily:
- Boot with an Ubuntu 12.04 Live CD
- CTRL + ALT + T
sudo add-apt-repository ppa:yannubuntu/boot-repair
sudo apt-get update
sudo apt-get install -y boot-repair && boot-repair
And click on the repair button! Done!
Very funny coincidence: Exactly one year after my devastating test of Windows 8 on the EEE PC 1015PN ( here) I tried Windows 8 again - 8.1 to be frankly.
After booting from the DVD, I entered my Key and choose to keep my data and such - an Upgrade Installation. Sadly, installer told me that I needed to choose that after booting into Windows 7 and starting the installation process there. Well, I did. But I only could choose to keep my data - not my programs(!). Sad, but - well. So - if you want to install and keep your stuff: Try to install Windows 8 first and then upgrade to Windows 8.1! I made an backup (just in any case - last time showed me the importance again...) and started with the installation. I took quite a while, but in the end it succeded. This time (and maybe because I changed my Wifi/Bluetooth Card from Azure for an Intel ABGN/WiMax Card?!) - I got none problems with Wifi. Working excellent from the first moment on.
I even got Optimus working by following my own tutorial here, by using the mentioned Versions.
Concerning other drivers and tools: I installed successfully the Optimus Tool, Capshook Driver - all by using the Windows 7 Compability Mode. ( I needed to use that as well on the Optimus Driver installation!)
Regarding - especially - the AHCI Drivers (Hotkey Service) and the SuperHybridEngine Tool - well: First of them gives REAL problems. It won't work and always remind to install an working AHCI Driver. Luckily, some guys found out an way to change that: Just install these tools from an newer ASUS EEE PC - the Asus 1225B. And that does work! Link: Source, Drivers - Good thing: Without the blocking AHCI Drivers Optimus does work correctly. But fixing ACPI is not enough. You need to setup the right Touchpad Driver!
About the Touchpad? Well - you need another Hack for Windows 8: Go with these. I chose the Elantech Touchpad driver Version v.10.6.6.0.
What I really changed? Well I did some normal stuff like disabeling the User Rights Control Thingy - as well as I changed the Resolution of the Display with this little hack. That got the Metro Apps working and my display from 1024x600 to 1152x864. Ok, it is not very crispy - but really gives more usability. ( Just watch for the "Display1_DownScalingSupported" setting in the registry and enable it )
To get back your classic Start Menu Button - use: http://www.classicshell.net/
Ok, that was a lot of stuff and I am curious to see how Windows 8.1 will perform in "real life". Well, I am off to installing some more tools and such.
An freshly installed Ubuntu got the root Account set to the best and most secure state ever: DISABLED!
But if you use ready-made Appliances and such, most of these Ubuntu Appliances come with an enabled Root Account. How to disable this account? Easy:
sudo usermod -p '!' root
Source: http://serverfault.com/questions/178080/how-do-i-disable-root-login-in-ubuntu
[2013-11-02 08:26:51 - SearchViewDemo] Dx
trouble writing output: already prepared
[2013-11-02 08:26:51 - Dex Loader] Unable to execute dex: java.nio.BufferOverflowException. Check the Eclipse log for stack trace.
[2013-11-02 08:26:51 - SearchViewDemo] Conversion to Dalvik format failed: Unable to execute dex: java.nio.BufferOverflowException. Check the Eclipse log for stack trace.
Well that happend to me as I tried to build my latest project.
Solution was quite simple but... strange.
Just remove all newer Android SDK build-tools (i.e. 19) until the Version 18.1.1 with the Android SDK Manager.
Restart Eclipse. And it will work.
If not, try to add the Support Libraries (Right click on your Android Project in Eclipse, choose Android Tools, Add Support Library)
Issue and solutions found here: https://code.google.com/p/android/issues/detail?id=61710
THIS POST IS OUTDATED! A NEW IMAGE HAS BEEN POSTED! PLEASE USE THE SEARCH FUNCTION TO FIND THE LATEST VERSION!
As I found out that the old tutorials weren't helpful and either the OpenWRT Trunk OR the Raspberry Pi Kernel broke the build process (you can still build it successfully, but you won't be able to use the RPi after boot!) - I sat down and found an new way. This time I don't let the kernel build by the OpenWRT enviroment, but insert an healthy and prebuilt one by the RPi Team ;)!
You can just download and use the (7zip-ed) image here: rpi_openwrt.7z [ 6.1 MB ]
There are several changes to the normal version:
- opkg list does contain the current stable package list for the OpenWRT RPi port of the latest stable release and will work out of the box (opkg update, opkg install..) Most packages like apache should work out of the box - but kernel moduls could/will probably fail. I won't build an package mirror and won't build packages because of limitied time. Sorry!
- Other than the normal behavior, the RPi does use DHCP to get its IP Adress. To connect for the first time, use nmap to find your RPi in your network. (Then connect via telnet, set an password with passwd and you're good to use SSH finally!)
- The main partition size has been changed from 48 MB to 64 MB - giving you additional space
All the best,
Nico
Recently I got an error on trying to upgrade my Android SDK, claming that I would not be able to access an URL. I was looking around the Internet and got the information that I should first upgrade the Eclipse Plugin. OK!
Upgrading AVT:
1. In Eclipse go to Help
2. Install New Software ---> Add
3. inside Add Repository write the Name: ADT and Location: https://dl-ssl.google.com/android/eclipse/
4. after loading you should get Developer Tools and NDK Plugins
5. check both if you want to use the Native Developer Kit (NDK) in the future or check Developer Tool only
6. click Next
7. Finish and Restart Eclipse
Ok, that got my Plugin to the latest version. But I still could not upgrade to the latest SDK. And thats when I found out that you need to start the SDK Manager as Administrator (right click, run as Administator) - and voilá: Upgrade successfully.
Source: http://stackoverflow.com/questions/4771895/android-sdk-manager-not-installing-components