{"id":794,"date":"2013-09-06T15:57:03","date_gmt":"2013-09-06T14:57:03","guid":{"rendered":"http:\/\/www.nico-maas.de\/wordpress\/?p=794"},"modified":"2013-09-02T15:57:14","modified_gmt":"2013-09-02T14:57:14","slug":"ubuntu-12-04-eee-pc-1015-pn-with-ubuntu-12-04-lts","status":"publish","type":"post","link":"https:\/\/www.nico-maas.de\/?p=794","title":{"rendered":"[Ubuntu 12.04] EEE PC 1015 PN with Ubuntu 12.04 LTS"},"content":{"rendered":"

I could not help myself but felt the need to have at least one real \"Dual Boot\" system (not VMWare Stuff) - so I setup my Asus EEE PC 1015 PN with the Ubuntu 12.04 LTS according to mtrons excellent Tutorial (\u00a0https:\/\/sites.google.com\/site\/mtrons\/howtos\/eeepc-1015pn<\/a>\u00a0) which worked out right out of the box.<\/p>\n

But - as I haid some trouble with the old Broadcom Wifi\/BT Card in Windows 7, I went for an Intel 6250 AGN\/WiMax Card. I do not use WiMax and would love an BT option - but the price point of that card on ebay finally got me to press the \"Buy now\" button. I thought \"Well, it is an Intel Card - that should work quite well and stop throwing me out of the University Wifi with no chance but doing an hard reboot of the Laptop to solve the problem\" - yeah - it really did. BUT - somehow, after some time and updates to the Ubuntu System, I lost connectivity: Network Manager was nagging for the password all the time - without a reason. Finally I found the solution on this website:\u00a0http:\/\/askubuntu.com\/questions\/104651\/how-do-i-get-wireless-working-on-an-asus-notebook-u56e<\/a>\u00a0- with some changes.<\/p>\n

From Kernel > 3.1 on, the wifi driver is not called iwlagn but iwlwifi, so your changes would go in that way:<\/p>\n

sudo \/etc\/modprobe.d\/iwl.conf<\/p>\n

and add these options to the file. First does deactivate the not existing BT Module on the card, second does disable N networks, which could avoid other problems:<\/p>\n

options iwlagn bt_coex_active=0
\noptions iwlagn 11n_disable=1<\/p>\n

Reboot and you are done<\/p>\n

 <\/p>\n

Another problem was the Optimus system: The Dual GPU Option of the system, packing an Intel GMA as well as an Nvidia ION Graphics on the board, with the choice of changing between both on the fly. That *did* work according to mtrons guide, BUT after an kernel upgrade - the acpi_call module did not work anymore - and with that the optimus tool. Help to that problem could be found here:\u00a0http:\/\/hybrid-graphics-linux.tuxfamily.org\/index.php?title=Acpi_call<\/a>\u00a0with the following changes:<\/p>\n

cd \/usr\/src\/acpi_call-1.1.1\/
\n# got an newer version of acpi_call
\nsudo dkms add -m acpi_call -v 1.1.1
\n# did throw an error as the module already existed
\nsudo dkms build -m acpi_call -v 1.1.1
\n# rebuild the module
\nsudo dkms install -m acpi_call -v 1.1.1
\n# reinstalled it to the kernel
\nsudo modprobe acpi_call
\n# reload module
\nmodinfo acpi_call
\n# show some infos<\/p>\n

And thats it!<\/p>\n

I am quite happy with the performance of Ubuntu on the system and I will keep it a while. I also tried the latest Debian, but was not that satisfied with it :\/! So long!<\/p>\n