/usr/share/bibledit-gtk/site/gtk/installation/technicalities/asus-eeepc-emulated-under-vmware.html is in bibledit-gtk-data 4.6-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<link href="../../../bibledit.css" rel="stylesheet" type="text/css" /><!--
Copyright (©) 2003-2011 Teus Benschop and Contributors to the Wiki.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3
or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
Texts. A copy of the license is included in the section entitled "GNU
Free Documentation License" in the file FDL.
-->
<title></title>
</head>
<body>
<div id="menu">
<ul>
<li>
<a href="../../../home.html">1 Bibledit</a>
</li>
<li>
<a href="../technicalities.html">Technicalities</a>
</li>
<li style="list-style: none; display: inline">
<hr />
</li>
<li>Asus EeePC emulated under VMWare
</li>
<li>
<a href="configure-source.html">Configure source</a>
</li>
<li>
<a href="create-binary-package-for-asus-eee-pc.html">Create binary package for Asus Eee PC</a>
</li>
<li>
<a href="install-fedora-packages.html">Install Fedora Packages</a>
</li>
<li>
<a href="compile-from-source.html">Install bibledit from source</a>
</li>
<li>
<a href="install-opensuse-packages.html">Install openSUSE packages</a>
</li>
<li>
<a href="install-optional-components.html">Install optional components</a>
</li>
<li>
<a href="macintosh.html">Macintosh</a>
</li>
<li>
<a href="run-bibledit.html">Run Bibledit</a>
</li>
</ul>
</div>
<div id="content">
<h1>
Asus EeePC emulated under VMWare
</h1>
<p>
This describes how the Eee PC software was made to run within VMWare on Linux.
</p>
<p>
</p>
<p>
The restore DVD that came with the PC is needed as the starting point. If you have lost your restore DVD, it has been seen in the bittorrent as EEEPC.iso.
</p>
<p>
</p>
<p>
Further a working VMWare installation is needed. The description below was made using VMWare Server 1.05 running on Debian 4.0. Also qemu and parted should be installed in Debian. Some of the instructions given below should be run as the root user. If an error occurs on executing some of these instructions, try them again as the root user.
</p>
<p>
</p>
<p>
Open a terminal, create a new directory, and cd into it. In this example directory ~/eee-pc was chosen.
</p>
<p>
</p>
<p>
Copy the image tarball from the restore DVD (P701L.gz) into the ~/eee-pc directory.
</p>
<p>
If the restore DVD is inserted into the drive, then the file P701L.gz should show up and it can be copied from there.
</p>
<p>
Else if using an iso file, you can mount that iso file in Linux with "mount -o loop /path/to/file.iso /path/to/mount/point".
</p>
<p>
</p>
<p>
Unzip the P701L.gz image.
</p>
<p>
joe@debian:~/eee-pc$ gunzip P701L.gz
</p>
<p>
</p>
<p>
Create a new disk image file called eeepc.img.
</p>
<p>
joe@debian:~/eee-pc$ qemu-img create eeepc.img 4001M
</p>
<p>
</p>
<p>
Copy the P701L image into the new image.
</p>
<p>
joe@debian:~/eee-pc$ dd if=P701L of=eeepc.img bs=512 conv=nocreat,notrunc
</p>
<p>
After this the file P701L is no longer needed.
</p>
<p>
</p>
<p>
Look up the first unused loop device.
</p>
<p>
joe@debian:~/eee-pc$ losetup -f
</p>
<p>
/dev/loop0
</p>
<p>
In this example the first unused loop device was /dev/loop0. Use this in the next steps.
</p>
<p>
</p>
<p>
Get the image as a device.
</p>
<p>
joe@debian:~/eee-pc$ losetup /dev/loop0 eeepc.img
</p>
<p>
Verify that this was succesful.
</p>
<p>
joe@debian:~/eee-pc$ echo $?
</p>
<p>
0
</p>
<p>
The above command verifies it and it should return 0.
</p>
<p>
</p>
<p>
Partition the second drive on the image.
</p>
<p>
joe@debian:~/eee-pc$ fdisk -C 486 /dev/loop0
</p>
<p>
</p>
<p>
Create the partition. The text below shows what is on the screen, and what the user types. To summarize the below steps, the user has to type: n, p, 2, <Enter>, 484, w.
</p>
<p>
Command (m for help): n
</p>
<p>
Command action
</p>
<p>
e extended
</p>
<p>
p primary partition (1-4)
</p>
<p>
p
</p>
<p>
Partition number (1-4): 2
</p>
<p>
First cylinder (301-510, default 301): <Enter>
</p>
<p>
Using default value 301
</p>
<p>
Last cylinder or +size or +sizeM or +sizeK (301-510, default 510): 484
</p>
<p>
Command (m for help): w
</p>
<p>
The partition table has been altered!
</p>
<p>
Calling ioctl() to re-read partition table.
</p>
<p>
WARNING: Re-reading the partition table failed with error 22: Invalid argument.
</p>
<p>
The kernel still uses the old table.
</p>
<p>
The new table will be used at the next reboot.
</p>
<p>
Syncing disks.
</p>
<p>
joe@debian:~/eee-pc$
</p>
<p>
</p>
<p>
Format the second partition.
</p>
<p>
joe@debian:~/eee-pc$ parted /dev/loop0
</p>
<p>
GNU Parted 1.7.1
</p>
<p>
Using /dev/loop0
</p>
<p>
Welcome to GNU Parted! Type 'help' to view a list of commands.
</p>
<p>
(parted) mkfs
</p>
<p>
Partition number? 2
</p>
<p>
File system? [ext2]? <Enter>
</p>
<p>
Error: Error informing the kernel about modifications to partition /dev/loop0p1
</p>
<p>
-- Invalid argument. This means Linux won't know about any changes you made to
</p>
<p>
/dev/loop0p1 until you reboot -- so you shouldn't mount it or use it in any way
</p>
<p>
before rebooting.
</p>
<p>
Ignore/Cancel? Ignore
</p>
<p>
Error: Error informing the kernel about modifications to partition /dev/loop0p2
</p>
<p>
-- Invalid argument. This means Linux won't know about any changes you made to
</p>
<p>
/dev/loop0p2 until you reboot -- so you shouldn't mount it or use it in any way
</p>
<p>
before rebooting.
</p>
<p>
Ignore/Cancel? Ignore
</p>
<p>
(parted) quit
</p>
<p>
Information: Don't forget to update /etc/fstab, if necessary.
</p>
<p>
joe@debian:~/eee-pc$
</p>
<p>
</p>
<p>
Remove the loop device:
</p>
<p>
joe@debian:~/eee-pc$ losetup -d /dev/loop0
</p>
<p>
</p>
<p>
Create a mount point for the loopback:
</p>
<p>
joe@debian:~/eee-pc$ mkdir loop
</p>
<p>
</p>
<p>
Mount the first partition:
</p>
<p>
joe@debian:~/eee-pc$ mount -o loop,offset=32256 eeepc.img loop
</p>
<p>
</p>
<p>
Fix the the xorg.conf file:
</p>
<p>
joe@debian:~/eee-pc$ gedit loop/etc/X11/xorg.conf
</p>
<p>
Change "intel" to "vesa" and screen resolutions to 800x600.
</p>
<p>
To make it easier, the whole file is available, see <a href="http://bibledit.pbworks.com/f/xorg.conf" rel="nofollow">xorg.conf</a>
</p>
<p>
</p>
<p>
Download the networking kernel module for VMWare, see <a href="http://bibledit.pbworks.com/f/pcnet32.ko" rel="nofollow">pcnet32.ko</a>. Save it to the eee-pc directory.
</p>
<p>
</p>
<p>
Install the kernel module in the image:
</p>
<p>
joe@debian:~/eee-pc$ cp pcnet32.ko loop/lib/modules/2.6.21.4-eeepc/kernel/drivers/net
</p>
<p>
Let the kernel module start on boot:
</p>
<p>
joe@debian:~/eee-pc$ gedit loop/etc/modules
</p>
<p>
Add the following line to the end of the list of modules:
</p>
<p>
pcnet32
</p>
<p>
Save the file.
</p>
<p>
</p>
<p>
Umount the loopback file system:
</p>
<p>
joe@debian:~/eee-pc$ umount loop
</p>
<p>
</p>
<p>
Remove the mount point for the loopback:
</p>
<p>
</p>
<p>
joe@debian:~/eee-pc$ rmdir loop
</p>
<p>
</p>
<p>
Use the qemu-img function from Qemu to convert the image into a vmdk file fit for VMWare.
</p>
<p>
joe@debian:~/eee-pc$ qemu-img convert eeepc.img -O vmdk eeepc.vmdk
</p>
<p>
</p>
<p>
The image eeepc.vmdk is now ready to be used in VMWare Server. Create a new directory, for example ~/vmware/eeepc, and move the file eeepc.vmdk, created above, into it, and also the VMWare configuration file, available as <a href="http://bibledit.pbworks.com/f/eee-pc.vmx" rel="nofollow"><img border="0" src="http://bibledit.pbworks.com/ficons/type_none.jpg" /></a> <a href="http://bibledit.pbworks.com/f/eee-pc.vmx" rel="nofollow">eee-pc.vmx</a>. Then start VMWare Server, and open the eee-pc.vmx virtual machine. Start the virtual machine, and then you'll see the Asus EeePC software running, if all is well.
</p>
<p>
</p>
<p>
Once the image runs, the networking module needs to be activated. This needs to be done only once.
</p>
<p>
Within the Asus EEE PC software, running in VMWare, open a terminal ty pressing Ctrl-Alt-t
</p>
<p>
/home/user>
</p>
<p>
Become root:
</p>
<p>
/home/user> sudo su -l
</p>
<p>
eeepc-joe:/root> cd /
</p>
<p>
eeepc-joe:/> depmod -a -v 2.6.21.4-eeepc
</p>
<p>
eeepc-joe:/> modprobe pcnet32
</p>
<p>
eeepc-joe:/> exit
</p>
<p>
/home/user> exit
</p>
<p>
In het Network tab of the EEE PC, there is a Network icon. Clicking that icon opens the Network Connections. It shows Local Area Connection 1. Click Propeties, and then the Hardware tab. Select the Advanced Micro Devices entry, and click the OK button. Then click the Connection button, and select the Connect option. The network will now connect. If all is well, then the network will start automatically next time.
</p>
<p>
</p>
<p>
</p>
<p>
It has been noticed that if you don't shutdown nicely you sometimes have to clear all files from /tmp in the image for X to start, as an old lock file sits in there.
</p>
<p>
It has been noticed that directory /var/log in the image has to be cleared out from time to time.
</p>
<p>
</p>
<p>
The informatioin above was assembled with the help of trial and error and various sources on the internet:
</p>
<p>
<a href="http://forum.eeeuser.com/viewtopic.php?id=3394" rel="nofollow">http://forum.eeeuser.com/viewtopic.php?id=3394</a>
</p>
<p>
<a href="http://www.blogeee.net/forum/viewtopic.php?f=2&t=200" rel="nofollow">http://www.blogeee.net/forum/viewtopic.php?f=2&t=200</a>
</p>
<p>
</p>
</div>
</body>
</html>
|