My issue is nearly identical to this question. I tried those solution and none worked. But I am using a different Android x86 image. I'm using the ICS (4.0-RC1) asus_laptop image. (I tried a different image previously and couldn't get it to install.)
I installed VirtualBox 4.1.12 on Kubuntu 12.04. I followed these steps and installed the android-x86-4.0-RC1-asus_laptop.iso image in my VM. It boots up and works correctly except for networking.
Alt-F1 netcfg shows no interfaces up except the lo (127.0.0.1). eth0, which should be available, is not shown. That prevents me from trying the solution here.
New references I'm checking out:
Android ICS x86 on VirtualBox with Internet Connection
http://groups.google.com/group/android-x86/browse_thread/thread/30fa23d81cddfab1/2e480f6b9cbf773d
How to setup network for Android Honeycomb in VirtualBox?
The following works very good for me
sudo vi /etc/init.sh
add 4 lines below to init.sh
netcfg eth0 dhcp
echo nameserver <ip> > /etc/resolv.conf
dnsmasq
setprop net.dns1 8.8.8.8
on virtualbox set the network interface to bridged (PCnet Fast III) and that's all.
Update: If Android x86 does not work well for you, you might want to look at AndroVM. I run it in VirtualBox and have had no hardware related issues.
Real Answer:
Somewhat of a follow-up answer since I can't add comments yet. I think getting this setup is highly dependent on your host hardware. I am not using hardware that perfectly fits any of the current ISOs. So I tested all of them with all Ethernet settings to see what would work.
On a Dell Latitude D820 here is what I got:
eeepc - Bridged Adapter with PCnet-PCI II
tegav2 - NAT adapter with PCnet-PCI III
amd_brazos - No CPU support
asus_laptop - No eth0 option for any Ethernet adapter setting
s104t - Would not boot
For the two ISOs that would work for me (eeepc and tegav2), I added the following two lines to /etc/init.sh (as per the other answer)
netcfg eth0 dhcp
setprop net.dns1 8.8.8.8
For me the solution of user1330614 worked very well.
Another nice writeup for the problem can be found here:
http://davematthew.blogspot.de/2012/04/android-x86-ics-on-virtualbox.html
try this one
VBoxManage modifyvm "Your Android VB name" --natpf1 adb,tcp,*,5555,*,5555
If you can't edit /etc/init.sh or /etc/init.androVM.sh and the error is the read-only file (despite being su) you can just write the following as superuser on the commandline:
setprop net.dns1 10.0.0.138
or any other IP, this is often the local router (capable of DNS). Check your network connection details for getting this IP.
The drawback is, that you have to do this every time, but it is not very time-consuming.
I had to enable WiFi in the Android settings and select the virtual network created by VirtualBox. In my case it was called "VirtWifi", which is a fake WiFi network using my computer network.
Some sources in the net says you should use the PCnet-Fast III either in bridged mode or NAT in your VBox Machine settings. Just give it a try.
This is a guide i found, but to be sincere, i am new to Android on VBox (and to Android at all) and i didn't test it myself.
Related
I'd like to know if it is possible to establish communication via a serial port in an Ubuntu for W10 terminal using the USB interface.
Concretely, I am using a Sparkfun edge board and in this tutorial, it is explained how to detect if the device is connected by checking /dev/tty*. However, it does not work in my testbed, nothing new appears in the directory.
Probably, it is related to using Ubuntu over Windows, but I'd like to be sure before moving to another system.
This is a bit old, but it should've worked then... New devices don't show up in the directory, they're already all there, so you need to know what COM port it's on, let's say it's on COM4, then your device will be /dev/ttyS4 in linux.
I've been using this for well over a year to upload files to my MCU boards kinda like what you want to do, and as long as the device shows up as a COM interface in Windows, and isn't in use, you should be able to connect it to it in WSL as /dev/ttyS[COM#].
Hope this helps, even if it's a bit delayed.
I have a Beaglebone Black(rev c),I am trying to connect it to Windows 8 laptop using putty. I am putting IP address as 192.168.7.2 and port as 22,but when I says open to it,putty window will pop-up and after sometime I will get fatal ERROR saying:
"Network connection time-out"
I am new to this, can someone tell me what am i missing?
Seems to indicate the an SSH server is not running on the BBB. Or possibly for some reason the BBB did not take 192.168.7.2 as an IP. Or perhaps you might need to wait a little bit longer for the SSH server to start up.
Short of this, there is not much to go on. One way to trouble shoot the issue would be to get a serial debug cable, connected and working to the BBB. Then you could dmesg | grep ssh or some such and hopefully get closer to what the actual problem is. Sorry if this is not enough for you to go by, but it is really hard to figure out what is going on without more information.
Other potential problems could be as simple as a USB cable that sometimes works or sometimes doesn't.
It may not be this but have you installed the drivers? See step 2 here: http://beagleboard.org/getting-started. If it's not that or you have already installed those then I am not sure sorry. Perhaps someone else has another suggestion.
Is the BeagleBone connected to your network with an Ethernet cable? It will only use 192.168.7.2 for the network-over-usb when there's only a USB cable connected - if you have Ethernet connected it will use DHCP to get an IP from your router, in which case you can check your router page to see what IP it got.
If you do just have USB connected then a driver issue is the most likely culprit, but you could try to ssh to the hostname beaglebone.local instead of the IP.
Is there a foolproof way to discover the MAC address of a device that is freshly plugged into an ethernet network in linux?
I'm looking specifically for something that works on the MAC address level. Assume everything at the ip address level is broken.
i.e. maybe ethernet chip drivers expose a list of the MAC's they've seen in /proc?
Taken from a similar question, this gets pretty close:
sudo tshark -i eth0 -e eth.src -Tfields
However, it doesn't de-duplicate lines, and it seems there are intermittent line number prefixes.
I have xmobar running in xmonad displaying network traffic summary via the dynnetwork monitor. It works fine with eth0 and wlan0, as wired and wireless network are identified on this machine, but the usb0 interface is not picked up when in use. bmon sees and reports traffic on usb0. Is there some way to have dynnetwork pick up usb0 traffic when it is in use or is it just not designed to do so?
Thanks to the author for identifying the problem. The usb0 interface was being raised after xmobar was run and the Net plugin only identifies active interfaces at initial runtime. By raising the usb0 interface before xmobar (or restarting xmabar after the interface is raised) it will be detected and reported normally. Hopefully a fix on the way.
This is my first post, so don't judge if I mess something up.
The problem is that I bought a new Desktop PC for my office (a Windows 8 machine with motherboard Z97-HD3 (has integrated Ethernet/LAN card)) and it worked OK for a few weeks, but now, the internet is gone.
When I boot up my PC I get "Network Identifying". After a minute or so, it says that it is connected, but when I open a browser it either says: "This webpage is not available" (more often) or "SSL certificate problem" (rarely). I've been chipping on this problem for a few days and the only steps that I've mustered up to take are these:
1. Is it the cable? Try the Ethernet/LAN cable on a different computer
Tried that. It works on my other laptop. So I conclude that the problem is with the new computer.
2. Is it a software problem or hardware?
2.1. Look at the back of the PC. The Ethernet card lights are on.
2.2. Try pinging localhost. Start > Open command prompt (cmd) > "ping 127.0.0.1". All 4 packages are sent and received with time 1ms
2.3. Maybe there is something wrong with Windows? Tried installing Ubuntu, but the internet doesn't connect as well
Anything else I could do? Or should I conclude that this is a hardware issue and return it to the shop?
First, make sure that you can ping your Gateway (gateways are computers/routers that are between two networks ). You can find out the IP of your gateway by running this in cmd:
ipconfig
There you will see your currently assigned(or static) ipaddress, the subnetwork, as well as the IP of your Gateway. Then try to ping your Gateway.
If you can then you know that all is good with cables and software and the problem is either configuration(you dont have gateway set) or the gateway can't make the connection outside of your local network.
if you can't ping your gateway, then you know something is wrong on your PC.