AndLinux: Difference between revisions

From miki
Jump to navigation Jump to search
Line 16: Line 16:
* TAP Interfaces - Reference [http://www.andlinux.org/forum/viewtopic.php?t=260], [http://www.andlinux.org/forum/viewtopic.php?t=72].
* TAP Interfaces - Reference [http://www.andlinux.org/forum/viewtopic.php?t=260], [http://www.andlinux.org/forum/viewtopic.php?t=72].
* Message '''Network cable unplugged''' for TAP interface even when AndLinux started.
* Message '''Network cable unplugged''' for TAP interface even when AndLinux started.
:* Open your settings file <tt>settings.txt</tt>, and check the configuration line for the ''tuntap'' interface
** Go to ''Network Connections'' window. Check that the connection for device named ''TAP-Win32 Adapter V8 (coLinux)'' is called '''TAP-Colinux'''. If not (for instance it is called '''Local Area Connection''' or '''Local Area Connection 2'''), then rename it!
<div style="padding-left:4em;">
** Other solution (not tried) from [http://docs.blackfin.uclinux.org/doku.php?id=colinux:network]:
eth1=tuntap,"TAP-Colinux",00:11:22:33:44:55
***'''Control-Panel''' &rarr; '''Network Connections''' &rarr; '''right click''' on the TAP-Win32 connection &rarr; '''Properties''' &rarr; '''Configure''' &rarr; '''Advanced''' &rarr; '''Media Status''' = Always connected.
</div>
:* Go to ''Network Connections'' window. Check that the connection for device named ''TAP-Win32 Adapter V8 (coLinux)'' is indeed called '''TAP-Colinux''', as specified above. If not (for instance it is called '''Local Area Connection''' or '''Local Area Connection 2'''), then rename it!
:* Another solution (not tried) from [http://docs.blackfin.uclinux.org/doku.php?id=colinux:network]:
:**'''Control-Panel''' &rarr; '''Network Connections''' &rarr; '''right click''' on the TAP-Win32 connection &rarr; '''Properties''' &rarr; '''Configure''' &rarr; '''Advanced''' &rarr; '''Media Status''' = Always connected.

Revision as of 11:22, 5 October 2009

Troubleshooting

Startup delays

  • Interaction with Anti-Virus software - AV software may interact with the startup of AndLinux, typically by maintaining a lock on the 4GB disk image file base.drv while it is scanned.
    • Solution: To prevent this, one can exclude the andlinux directory from the AV on-access scanner. In McAfee, this is done by opening the VirusScan consoledouble-ckick On-Access Scanner → then select All Processes → open the pane Detection and click the button Exclusions... → click Add... to add a new exclusion → Browse to AndLinux directory and select Also exclude subfolders.
  • Stalling when mounting / - You experience a huge delay during the startup process, and when launching the FLTK console, you observe that andlinux is stalling on the message below.
ReiserFS: cobd0: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on cobd0
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Modules already installed.
Closing /
kjournald starting.  Commit interval 5 seconds
  • Solution: The fix proposed in this post is to actually change the extension of the disk image file from .drv to something like .drive (ie. change ./Drives/base.drv to ./Drives/base.drive and ./Drives/swap.drv to ./Drives/swap.drive) and adapt the configuration files ./settings.txt accordingly.

Network issues

  • TAP Interfaces - Reference [1], [2].
  • Message Network cable unplugged for TAP interface even when AndLinux started.
  • Open your settings file settings.txt, and check the configuration line for the tuntap interface
eth1=tuntap,"TAP-Colinux",00:11:22:33:44:55
  • Go to Network Connections window. Check that the connection for device named TAP-Win32 Adapter V8 (coLinux) is indeed called TAP-Colinux, as specified above. If not (for instance it is called Local Area Connection or Local Area Connection 2), then rename it!
  • Another solution (not tried) from [3]:
    • Control-PanelNetwork Connectionsright click on the TAP-Win32 connection → PropertiesConfigureAdvancedMedia Status = Always connected.