I am attempting to boot inquisitor from a headless server. The only access that I have is through a serial console. I have successfully created a bootable USB using the instructions here: http://track.inquisitor.ru/issues/show/35 , but I cannot get GRUB to load over the serial connection. I see a syslinux header and then, the system becomes unresponsive. I have tried modifying the menu.lst file by appending serial to the options. This did not work. Then, I un-squashed the filesystem and changed inittab to force connections back to serial. Neither one has been successful. Help!
My menu.lst file looks like this: serial --unit=0 --speed=9600 --word=8 --parity=no --stop=1 terminal --timeout=15 serial console default 0 timeout 30 title Inquisitor 3.1beta LiveCD amd64 kernel /live/vmlinuz-2.6.26-2-amd64 boot=live noautologin nolocales hostname=inq union=aufs console=tty0 console=ttyS0,9600n8 initrd /live/initrd.img-2.6.26-2-amd64 title Inquisitor 3.1beta LiveCD amd64 (fail-safe mode) kernel /live/vmlinuz-2.6.26-2-amd64 boot=live noautologin nolocales hostname=inq union=aufs noapic noapm nodma nomce nolapic nosmp vga=normal console=tty0 console=ttyS0,9600n8 initrd /live/initrd.img-2.6.26-2-amd64 title Other: root title Memtest86+ kernel /live/memtest Also, my inittab in the squashfs looks like this: # /etc/inittab: init(8) configuration. # $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $ # The default runlevel. id:2:initdefault: # Boot-time system configuration/initialization script. # This is run first except when booting in emergency (-b) mode. si::sysinit:/etc/init.d/rcS # What to do in single-user mode. ~~:S:wait:/sbin/sulogin # /etc/init.d executes the S and K scripts upon change # of runlevel. # # Runlevel 0 is halt. # Runlevel 1 is single-user. # Runlevels 2-5 are multi-user. # Runlevel 6 is reboot. l0:0:wait:/etc/init.d/rc 0 l1:1:wait:/etc/init.d/rc 1 l2:2:wait:/etc/init.d/rc 2 l3:3:wait:/etc/init.d/rc 3 l4:4:wait:/etc/init.d/rc 4 l5:5:wait:/etc/init.d/rc 5 l6:6:wait:/etc/init.d/rc 6 # Normally not reached, but fallthrough in case of emergency. z6:6:respawn:/sbin/sulogin # What to do when CTRL-ALT-DEL is pressed. ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now # Action on special keypress (ALT-UpArrow). #kb::kbrequest:/bin/echo "Keyboard Request--edit /etc/inittab to let this work." # What to do when the power fails/returns. pf::powerwait:/etc/init.d/powerfail start pn::powerfailnow:/etc/init.d/powerfail now po::powerokwait:/etc/init.d/powerfail stop # /sbin/getty invocations for the runlevels. # # The "id" field MUST be the same as the last # characters of the device (after "tty"). # # Format: # <id>:<runlevels>:<action>:<process> # # Note that on most Debian systems tty7 is used by the X Window System, # so if you want to add more getty's go ahead but skip tty7 if you run X. # 2:23:respawn:/sbin/getty 38400 tty2 3:23:respawn:/sbin/getty 38400 tty3 4:23:respawn:/sbin/getty 38400 tty4 5:23:respawn:/sbin/getty 38400 tty5 6:23:respawn:/sbin/getty 38400 tty6 # Example how to put a getty on a serial line (for a terminal) # T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100 T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100 # Example how to put a getty on a modem line. # #T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3 inq:2345:respawn:/usr/bin/inq-live-wrapper |
Free forum by Nabble | Edit this page |