see: usb-stick documentation how to create "basic" usb stick ----------------- E-UAE - usb stick ----------------- There is two instructions to make uae usb-stick. First there is instructions to run uae on DirectFB and another is X11 version. I used X11 version because it makes possible to choose several screenmodes with picasso. ubuntu (karmic) - Both methods ------------------------------- Perform these steps in kvm/qemu or in stick * sudo aptitude install libsdl1.2debian-all - again I'm lazy and just select everything. * sudo aptitude install e-uae - now you should have e-uae properly installed ----------------------------- e-uae filepaths, configs etc. ----------------------------- At this point you can install e-uae configs and other files. Easiest way is first install everything to the desktop machine, then copy and modify directory structure to the home directory of your uae user on the usb-stick. Then just modify bootscript(s) use that structure. e-uae directory structure example --------------------------------- $HOME \ - euae \ - Workbech - Work - Games - Roms - Configs * Workbech, Work and Games are amiga partitions. * Roms contains used rom file(s) * Configs are for config file(s) ------------------------------------ DirectFB - e-uae and automatic login ------------------------------------ !! This didn't work very well with my minilaptop. Use X11 method instead!! Perform these steps in kvm/qemu or in stick With ubuntu (karmic) -------------------- * add your user video group (if not already) - sudo addgroup user video * add udev rule. To get access to the input devices. - /etc/udev/rules.d/99-input.rules " ACTION!="add|change", GOTO input_end KERNEL=="event*", GROUP="video" KERNEL=="mouse*", GROUP="video" KERNEL=="mice", GROUP="video" KERNEL=="js*", GROUP="video" LABEL="input_end" " * vesa/vga framebuffer - add to /etc/initramfs-tools/modules " fbcon vesafb vga16fb " - uncomment from /etc/modprobe.d/blacklist-framebuffer " vesafb vga16fb " To keep everything as small and simple as possible * use alsamixer to get sound * other framebuffer drivers - test those yourself vesa is fast enough for me * network drivers (at least with ubuntu) - add manually Make e-uae autostart with framebuffer ------------------------------------- This is not tasted, but should work * sudo aptitude install mingetty script (/home/username/start-uae.sh): " #!/bin/sh uae -f /path/to/your/uae/configs/some_nice_euae_config.euaerc " remember to make script executable "chmod u+x /home/username/start-uae.sh" * vi /etc/init/tty1.conf (ubuntu with upstart) - change "exec /sbin/getty -8 38400 tty1" to "exec /sbin/mingetty --autologin=username tty1" * if there is no upstart try /etc/inittab add to .bashrc: if [ -z $DISPLAY ] && [ $(tty) == /dev/tty1 ]; then while [ 1 == 1 ] do /home/username/start-uae-sh sleep 10 done fi " Stick should be ready to try. ...and it should autostart e-uae to the top of the framebuffer. See also -------- * http://sunbruce.spaces.live.com/blog/cns!5B0415F75B69AB09!958.entry * http://harrison3001.blogspot.com/2009/09/grub-2-graphical-boot-tips-to-set.html Problems -------- * It is hard to get proper framebuffer modes to work with some machines. * crt users might have to us some 60Hz mode. (makes you feel sick) ------------------------------- X11 - e-uae and automatic login ------------------------------- Perform these steps in kvm/qemu or in stick To keep roofs as small as possible only mandatory packages are installed. Jit enabled e-uae didn't work with kvm. So I had to do e-uae part with real machine with stick. You might need to make udevs rule thing from directfb part. Try first without it and tell. Install some packages --------------------- * sudo aptitude install xinit * sudo aptitude install xutils * optional: sudo aptitude install some_nice_windowmanager_for_linux_use Try startx command at this point with your e-uae user * make sure that your e-uae config have " ... gfx_linemode=double gfx_fullscreen_amiga=true gfx_fullscreen_picasso=true ... " .xsession --------- * add .xsession to your users home with line: "uae -f /path/to/your/uae/configs/some_nice_euae_config.euaerc" Try startx again and e-uae should start by default in fullscreen. autologin to X without gdm or kdm ---------------------------------- xdm does not support autologin at all. * apt-get install mingetty - you might need to add some repositories before this step + sudo nano /eyc/apt/ssources.list - you might need to update repositories before this step + sudo aptitude update * vi /etc/init/tty6.conf (ubuntu with upstart) - change "exec /sbin/getty -8 38400 tty6" to "exec /sbin/mingetty --autologin=your_username tty6" * if there is no upstart try /etc/inittab * vi /home/your_username/.bashrc - add to the end of the file " if [ -z $DISPLAY ] && [ $(tty) == /dev/tty6 ]; then while [ 1 == 1 ] do startx sleep 10 done fi " Stick should be ready to try. ...and it should autostart e-uae to the top of the X11. Problems -------- 1. e-uae fails to start (in fullscreen) When previously selected Workbech screenmode is not supported by computer X11 generates an error and uae exits. This only happens when computer you use last time have and you saved some weird screenmode. For example netbook/minilaptos has 1024x576 screenmode save that to the workbench and swich to desktop machine and kaboom desktop machine supports a lot of screenmodes but not 1024x576. Probably the best fix1: save wb screenmode as 640x480x32 it should work every pc. Then every time you boot/reset just go and select suitable screenmode. Do not save just use it. possible fix2: add second uae starter with window mode to .xsession. if first fullscreen uae fails to start windowed mode should work nicely example .xsession: " uae -f /path/to/your/uae/configs/some_nice_euae_config.euaerc uae -f /path/to/your/uae/configs/some_nice_euae_config_with_windowed_mode.euaerc " possible fix3: simple start some windowmanage and start uae in windowed mode and change screenmode. example .xsession: " uae -f /path/to/your/uae/configs/some_nice_euae_config.euaerc wmaker " wmaker is easy to use and quite lightweight windowmager. I use first method and as fallback xterm starts. It is a lot of easier to find out what is wrong than trying to disable autoboot etc.