Hi,I install Centos 6.3 in to G7 server . I config the console port .That is ttyS0 .I add below file /etc/init/serial-ttyS0.conf with below content .
I know this is a rookie question, but I have never set up serial console redirection.I have always used KVM's, instead.I have an older HP DL140 G3, in which HP likes to charg... [by siterack_net]
I'm debugging a kernel module under VirtualBox with a guest and host OS as Ubuntu 10.10. I'm using the virtualbox serial port but I'm maxing out at the baudrate 115200. My grub config looks like this...
console=ttyS0,115200
Is there a way for me to change that setting in the guest OS so that the virtual serial port works at a faster baudrate? I've tried to use setserial.
Is it possible to create a console using the SPI device (/dev/spidev0.0) in a similar way that you would create a serial console, or if not is this possible ??
I'm working on embedded ARM platform, Slackware.
I've installed Fedora 11 on top of Windows 7, and at startup, when I select Windows 7 to boot to, I get a message saying:
Code:
NTLDR is missing
Press Ctrl+Alt+Del to Restart
Currently, I have my boot layout setup so that when my computer starts I go into grub. The content of my /boot/grub/menu.lst file looks like this:
I am trying to write a sed expression to detect lines similer to this:
s0:12345:respawn:/sbin/agetty -8 -s 115200 ttyS0 linux
and replace the "ttys0" with "something_else"
I do not want to detect commented out lines (beginning with #)
I can replace the whole line, but how to I just replace the substring, leaving the rest of the line intact ?
I got the grub loader to work finally. The problem is it does not always display at initial boot or a restart. I have seen the selection menu but it doesn't always appear. I have it set to point to windows so that my wife can hit enter when she gets a blank screen. Below is the contents of my /etc/grub.conf file:
#boot=/dev/sda
default=1
timeout=60
I just upgraded a F9 to F11 using the network install. After the successful install message, I rebooted to find the boot stuck on a grub prompt. After determining that somehow grub had not been installed properly, I used the rescue mode to re-install grub. When I then rebooted, I saw a blank (black) screen during the rhgb sequence, with just the multicolor progress bar moving from left to right.