How To: Fix “Unknown keyword in configuration file.” Ubuntu USB Boot

Attempting Boot From USB Device

SYSLINUX 3.63 Debian-2008-07-15 EBIOS Copyright (C) 1994-2008 H. Peter Anvin
Unknown keyword in configuration file.
boot:
_

After creating a USB bootable version of Ubuntu from the Startup Disk Creator (or usb-creator-gtk) and attempting to boot, I was greeted by the error above. It might look a bit scary but it’s really easy to fix, just plug the USB flash drive into a computer (windows or linux, mac too probably but I haven’t tried that.)

Solution 1:
  1. Open the the syslinux folder in the root of the flash drive.
  2. Inside is a file called syslinux.cfg you’ll want to edit that.
  3. Find the line “ui gfxboot bootlogo” and simply remove the “ui “.
  4. Save and try booting again.

Below is how my syslinux.cfg file looks after editing:

# D-I config version 2.0
include menu.cfg
default vesamenu.c32
prompt 0
timeout 50
gfxboot bootlogo


Solution 2

Alternatively it looks as though there is another way of fixing this issue if there is no “ui” in the file, this is to do as followed (as pointed out in the comments below):

  1. Type “help” and press enter
  2. Hit Enter again

This should boot correctly and shouldn’t need to be done every time.

Ubuntu Disconnecting from Wi-Fi and Failing to Reconnect.

I have an updated fix for this issue using a startup script to connect and a time scheduled script for checking the connection, rather than having one constantly running in the background, avalible here – http://alexsleat.co.uk/2011/01/09/a-more-elegant-solution-to-ubuntu-wi-fi-reconnecting-issue/

I’ve been having some trouble with my wifi on Ubuntu recently but I think it’s because I’m almost out of range of the access point. The problem is that once it disconnects it never seems to be able to reconnect unless wireless is disabled and re-enabled. No doubt there is another way of fixing this issue but it gives me a chance to write my first shell script.

In short the script disables network-manager (it was trying to do things auto which was screwing with things), sets up the connection and connects then checks for a string in the wireless card parameters which will only occur if it’s disconnected, if the string appears it’ll disable and re-enable the wireless device which seems to allow it to connect again. If it’s connected it’ll wait 3 minutes (180 seconds) before checking again where as if it does disconnect it’ll check again 30 seconds after it’s tired rebooting the device.

Here’s the script, be sure to try it if you’re having the same problem (you might need to change the wireless device ‘wlan1′ to yours) and comment if I’m doing something wrong or there’s another way around this, cheers.

#!/bin/bash

service network-manager stop

iwconfig wlan1 essid NETWORKNAME
iwconfig wlan1 key NETWORKKEY
ifconfig wlan1 up
dhclient3 wlan1

while true;
do

if (iwconfig wlan1) | grep -o "Access Point: Not-Associated"
then
	ifconfig wlan1 down
	echo "not connected, rebooting Wifi"
	ifconfig wlan1 up
	sleep 30
else
	echo "connected"
	sleep 180
fi

done

gedit – failed to load type module: menu_proxy_module_load | Ubuntu

(gedit:2205): Gtk-WARNING **: Failed to load type module: (null)

`menu_proxy_module_load’: gedit: undefined symbol: menu_proxy_module_load

Annoying error, seems to has no serious effect on it running but just nice to clean stuff up so just install ‘appmenu-gtk’.
sudo apt-get install appmenu-gtk