Re: Asus EEE PC 900 SD and WiFi

[frendcarlo]

Hi John,

Did you try other builds of tabletsx86.org? ---> carlo

On Wednesday, November 14, 2012 4:26:44 PM UTC+1, John Stottlemire wrote:

Does anyone know a work around to get 4.0RC2 Wi-Fi working? (with the exception of replacing the wi-fi hardware since that is impossible on the 900 SD).  Wi-Fi works fine on 3.2RC2 but with the lack of Google Play is worthless to me.

Thanks in advance to those who contribute on topic :-)

-john

[John Stottlemire]

I tried the builds at tabletsx86.org.  I have yet to get any of those builds to successfully  boot.  Each time, after detecting the location of Android, it sits on a black screen until I reboot.

-john

[frendcarlo]

Hi John,

What build is working in 4.0RC2 that WIFI doesn't work?  Maybe there I can help you but you have to tell me what build is loading successfully.  Also, in the 3.2RC2, you mentioned that WIFI works, if you can run the command lspci -k > /sdcard/data/devices.txt in the console mode and send devices.txt file here? maybe I can help you. Do you create your own build? --> carlo

[John Stottlemire]

First, I do not create my own build.

The build I can load which Wi-Fi does not work is the build available today at www.android-x86.org/download 

I am not sure how to get to get to the console mode in 3.2RC2 (I am not a Android or Linux guru, sorry).

If it matters, the wi-fi card in my 900SD is a Realtek RTL8187SE

-john

[frendcarlo]

Hi John,

Perhaps I can help you with the RTL8187SE wifi but it would be faster if you can tell me which specific build that loads without wifi so that we can start with that build.  With regards to the console mode, just press ALT-F1, to go back, ALT-F7 ... --> carlo

[John Stottlemire]

Thank you Carlo,

The first build that loads is http://android-x86.googlecode.com/files/android-x86-4.0-RC2-eeepc.iso  Link to file.  If there is something more specific you need, please let me know.

-john

[Andrew Trimble]

Good afternoon John,

I spent 2 minutes researching your problem, and discovered that you are running on an Intel graphics chipset. If memory serves me, the Intel onboard video drivers have a tendency to use LVDS as it's output, so we need to turn that output off.

Next time you load up one of the "Black Screen" editions of android, try appending the following to the GRUB boot line: video="LVDS-1:d"

This is done on the selection screen just before it starts "Detecting Android-x86"

This will disable the LVDS portion and (hopefully) pipe the video through to your screen.

Seems to be a common problem with at least some onboard Intel graphics.

Hope this helps get ya going!

[frendcarlo]

Hi John, I have an existing build which I upload in this link. You can try that build and wish you good luck and more fun. -> Carlo

[John Stottlemire]

Thank you Carlo.  Sorry it has taken me so long to respond.  This version (even with the suggested video="LVDS-1:d") sits on a black screen until I reboot the machine shortly after the "Detecting Android-x86" screen.

-john

[John Stottlemire]

Thank you for the suggestion Andrew but this work around did not work for me. (and I tried both video=LVDS-1:d and video="LVDS-1:d")

[frendcarlo]

Hi John,

I make another build for you, this time it is a fresh build without any changes except adding a wifi with your requirements.  here is the link http://www.4shared.com/file/8vBIRl4n/pc-x86.html . good luck~ carlo

[John Stottlemire]

Thank you Carlo.  This new build acts the same as the last.  After detecting Android it sits on a black screen until I reboot.

I verified the last bootable version of Android and the file name is android-x86-4.0-RC1-eeepc.iso size 181 MB

Thank you again.

-john

[frendcarlo]

Hi John,

I don't think I can get the source for the RC1 as what I have now is the latest RC2.  You can try to the asus_laptop version and add video=LVDS-1:d in the parameters before you boot, (during the grub menu, press tab upon selected Run android without installing) and see if that helps.  If that works, I can make another build for you with the wifi on that target. ~ carlo

[John Stottlemire]

asus_laptop RC2 reboots after detecting Android.  Guess I'm outta luck here.  Thanks for all your help Carlo.

[John Stottlemire]

I have been able to load android-x86-4.0-RC2-eeepc.iso with the VIDEO=LVDS-1:d command line parameter however it fails on the "Turning WiFi on.." screen.

[gerhard smith]

If you can install the working version (without WiFi) to hard disk, testing can be a lot easier - make sure you install with /system  as writable when asked. If you already multi-boot windows/linux DONT install grub - you have to edit the grub.cfg afterwards.
then:
If frendcarlo can post the driver somewhere, you can copy it to the /system folder down in "/system/........./kernel/drivers/net/wireless" or you can make your own directory "/system/mytestdriver" and copy the driver there.
then you should be able to "modprobe -d<directory> rtl8187se.ko" and try your wifi.
If it works you can add the modprobe to /system/etc/init.sh (at the bottom) or build a new iso image including the driver.

[John Stottlemire]

Wow, thanks for the info Gerhard. Sounds easy enough.  I'm linux stupid, however, Hope google can tell me how to copy files or create directories. LOL.  

[gerhard smith]

Some easy guidance:
Under Windows or Linux:
1. Download the driver file
2. Copy it to a memory stick (USB drive).

Boot Android.
1. Start the terminal emulator from the apps screen.
2. enter "su" without the quotes to become super user.
3. enter "df" to see where the USB is mounted
4. enter "mkdir       /system/rtl8187driver"
5. enter "cp       <usb stick mount point>/<drivername>     /system/rtl8187driver" replacing <usb stick mount point> with the mount point from the "df" and <driver name> with the name of the driver.
6. enter "modprobe     -d       /system/rtl8187driver      <driver name>
Note that I left big spaces where spaces are important.
Try your Wifi.

[John Stottlemire]

Thank you very much.  Should I be impatient (and not want to wait for Carlo to post the driver) what exactly am I looking for on google?  Is it the Linux driver that is required?  

[gerhard smith]

You are looking for rtl8187se.ko (according toprevious posts, but it st be for the kernel used by Android (version) so I would try and get the one from frencarlo as it will be compiled with the correct interfaces.

[frendcarlo]

Hi John, attached to this are the drivers. good luck ~ Carlo

[gerhard smith]

I am not sure whether there is a difference between rtl8187 and rtl8187se, so in case here is a link to the rtl8187se driver
https://rapidshare.com/files/3724379381/r8187se.ko
This was taken from the generic_x86 build

Test to see if wifi works. If it doesnt:

open a terminal
su
dmesg | grep 8187 > /system/dmesgoutput

post the file /system/dmesgoutput here so we can have a look.
rm /system/dmesgoutput  afterwards to clean up

[John Stottlemire]

Thank you Carlo and Gerhard.

I have followed instructions to a T with one exception:

When using modprobe with the -d switch I was given the error "unknown option -- dBusyBox v1.19.4-cm9 bionic (2012-02-05 18:40 +0100) multi-call binary" so I executed the command without a switch.

after execution of "modprobe /system/rtl8187driver rtl8187" and then returning to WiFi settings I was unable to flip the WiFi "switch" from OFF to ON.  dmesgoutput follows:

<4>[    6.545665] r8187se: module is from the staging directory, the quality is unknown, you have been warned.

<6>[    6.554344] r8180: MAC controller is a RTL8187SE b/g

<0>[   72.650092] Modules linked in: bsd_comp ppp_deflate ppp_async pppoe pppox ppp_generic slhc option usb_wwan usbserial cdc_acm btusb rfcomm bnep bluetooth hid_multitouch uvcvideo videodev psmouse pcspkr atl1e r8187se(C-) eeprom_93cx6 i2c_i801 snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer snd snd_page_alloc i915 drm_kms_helper drm i2c_algo_bit eeepc_laptop sparse_keymap hwmon rfkill

<0>[   72.650285]  [<e05d9c24>] ? rtl8180_proc_remove_one+0x54/0x60 [r8187se]

<0>[   72.650302]  [<e05f66d8>] ? rtl8180_pci_remove+0x2b/0xe3 [r8187se]

<0>[   72.650389]  [<e05f679b>] ? rtl8180_pci_module_exit+0xb/0x32 [r8187se]

<0>[   72.650405]  [<e05f6790>] ? rtl8180_pci_remove+0xe3/0xe3 [r8187se]

<6>[  402.085508] usbcore: registered new interface driver rtl8187

after execution of "modprobe /system/rtl8187driver r8187se", then returning to WiFi settings and flipping the WiFi switch to the ON position, the screen went to "Turning WiFi on" and stayed there until I intervened.  dmesgoutput follows:

<4>[   12.445158] r8187se: module is from the staging directory, the quality is unknown, you have been warned.

<6>[   12.453786] r8180: MAC controller is a RTL8187SE b/g

<0>[   35.600118] Modules linked in: bsd_comp ppp_deflate ppp_async pppoe pppox ppp_generic slhc option usb_wwan usbserial cdc_acm btusb rfcomm bnep bluetooth hid_multitouch uvcvideo videodev psmouse pcspkr atl1e r8187se(C-) eeprom_93cx6 i2c_i801 snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer snd snd_page_alloc i915 drm_kms_helper drm i2c_algo_bit eeepc_laptop sparse_keymap hwmon rfkill

<0>[   35.600309]  [<e05d9c24>] ? rtl8180_proc_remove_one+0x54/0x60 [r8187se]

<0>[   35.600326]  [<e05f66d8>] ? rtl8180_pci_remove+0x2b/0xe3 [r8187se]

<0>[   35.600410]  [<e05f679b>] ? rtl8180_pci_module_exit+0xb/0x32 [r8187se]

<0>[   35.600425]  [<e05f6790>] ? rtl8180_pci_remove+0xe3/0xe3 [r8187se]

<4>[ 1176.678001] r8187se: module is from the staging directory, the quality is unknown, you have been warned.

<6>[ 1176.684957] r8180: MAC controller is a RTL8187SE b/g

<0>[ 1260.710117] Modules linked in: r8187se(C-) bsd_comp ppp_deflate ppp_async pppoe pppox ppp_generic slhc option usb_wwan usbserial cdc_acm btusb rfcomm bnep bluetooth hid_multitouch uvcvideo videodev psmouse pcspkr atl1e eeprom_93cx6 i2c_i801 snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer snd snd_page_alloc i915 drm_kms_helper drm i2c_algo_bit eeepc_laptop sparse_keymap hwmon rfkill [last unloaded: r8187se]

<0>[ 1260.710311]  [<e302fc24>] ? rtl8180_proc_remove_one+0x54/0x60 [r8187se]

<0>[ 1260.710326]  [<e304c6d8>] ? rtl8180_pci_remove+0x2b/0xe3 [r8187se]

<0>[ 1260.710403]  [<e304c79b>] ? rtl8180_pci_module_exit+0xb/0x32 [r8187se]

<0>[ 1260.710418]  [<e304c790>] ? rtl8180_pci_remove+0xe3/0xe3 [r8187se]

Again, thank you both very much for your assistance with this.

-john

[gerhard smith]

Sadly it looks like the driver is not working. I am unfortunately also a novice at this.
Next suggestion:

If you can sill boot rc3.2 from cd then do that and do
open termina;
su
find . -name "*818*" to try and find the driver on that version and see what it is called.
Also try the drivers that frendcarlo has posted; maybe they work - the process is the same.

Are you sure that your tablet/pc uses the rtl8187se chipset?

[John Stottlemire]

My last post included results from driver provided by Carlo (the first result) and after a clean install of the ISO the driver you provided (the second result).

The Windows XP driver is RTL8187SE downloaded from Asus website for the 900 SD and after installation of the XP driver XP is able to use the wireless network so I am assuming it is the RTL8187SE. I have not cracked open the case to confirm and although I am very adept at computers in general (just Linux stupid... I was sued by Coupons, Inc. afterall) I have no desire to open the case on the 900 SD.

[gerhard smith]

It looks like you might have to go down the ndis route where you can use your windows driver. I have not done this but there must be someone on this group that can help you with that.
I might also be missing something somewhere.

[gerhard smith]

I found bits and pieces of ndis in the source tree, but I have not checked whether they are included in any of the builds.
The main thing you are looking for is ndiswrapper (in the source tree it is driver_ndiswrapper)
If you google install ndis you will find indtructions on how to install it - it is actually quite simple.

[John Stottlemire]

This really is beyond my comfort level and I don't have the time required to do this on my own.  Hope someone else on the board can. I really would like to run 4.x Android on this Netbook.

[gerhard smith]

You can try the following:
1. boot the thinkpad.iso that has a working wifi
2. Open a terminal app
3. su
4. find . -name "*818*" or look in kernel/drivers/net/wireless
(4) should find any  files with 818 in the name and that should include the driver. The driver would typically be in kernel/drivers/net/wireless(I think - dont have tablet at hand).
5. copy it to your hard disk or a memory stick and then follow the earlier post to install and modprobe it.

[frendcarlo]

Hi John,

What I can suggest is to use the ubuntu live disk. You can download it and run the ubuntu live without installing.  Then in the upper right top button you can run the terminal prompt type the command lspci -k,  and lsusb, and dmesg | grep 818 and then copy and paste the output here.  This way, we can see what linux driver it uses.  ~ good luck Carlo

[gerhard smith]

What frendcarlo suggests is a very good idea. Also, if you download ubuntu 3.0(I think the current version is 3.2) live cd, then the driver on there can be copied off and used in android-x86 (drivers from later ubuntu might even work).
good luck.

[John Stottlemire]

Thank you both. I'll get on this as soon as the weekend is over. :-)

[Gerhard Smith]

you have to install to hard disk and select make system writable during the install.

On Monday, December 3, 2012 1:40:55 PM UTC, Carlo Molinari wrote:

i have te same problem (with an eeepc 900HD) and i tryed this guide but terminal emulator says "mkdir failed for /system/rt8187driver, read only file system"

what can i do? can i move manually the files with a file explorer?

thanks :)

[Carlo Molinari]

how could i put it in the iso? i setted system asread-write  but it doesn't work...

[Gerhard Smith]

It is not the iso that is the problem. You have to install to hard disk and while installing select writable system. Otherwise only the data directory is writable.

[Miguel Sousa]

Already tried to compile with module from linux kernel linux-3.0.55 - the result is the same.. 

[Carlo Molinari]

it doesn't ask me if i want to set system as writable... is there any way to put the driver into system before i install the iso?