wasnt working like it was supposed to. My wireless chip is rtl8188su, and it was supposed to work out of the box. Well, switching back to regular Rasbian, it does, so something in beeryboot breaks the wireless driver. llionevans wrote: Just wondering if it was possible to change the default OS once one had booted up. See page 5 That's great, sorry for the repost. I did search first but didn't come across that. Ok so I'm kind of new - you say that by doing this I'd have to do memsplit changing manually. What does this mean? What steps would I have to take, or is it something that's not going to affect the average user? llionevans wrote: Ok so I'm kind of new - you say that by doing this I'd have to do memsplit changing manually. What does this mean? What steps would I have to take, or is it something that's not going to affect the average user? It only affects you if you plan to boot an operating system that requires that extra memory is allocated to the GPU. That is the case with media center stuff like OpenELEC. If you only plan to use your Pi as headless server, it doesn't affect you. The one that is currently in use will be missing from the "ls *.elf" output. First you must rename it back to its original name. E.g. if 192 is currently in use, do "sudo mv /boot/start.elf /boot/arm192_start.elf" Now rename the one