On 5/5/06, Paul Armor <parmor@xxxxxxxxxxxxxxxxxxxx> wrote:
Hi,
I don't know which combo of this is correct, but I had kickstarting
viewable over a serial port that redirected over an IPMI/BMC. I don't
know if everything I do is correct or necessary, but it works ;-)
I found somewhere references to do the following:
Put this in the first line of the anaconda bootloader config -
serial 1,19200n8 0xab3
In the kernel options, pass something like -
console=ttyS1,19200n8r
Such that, our default.blah file looks like:
serial 1,19200n8 0xab3
default linux
label linux
kernel vmlinuz.FC4x86_64
append ksdevice=eth0 console=tty0 console=ttyS1,19200n8r \
load_ramdisk=1 initrd= initrd.FC4x86_64-sata.img ramdisk_size=16384 network \
ks=nfs:192.168.0.11:/export1/FC4install/install-server/ks-slave_FC4x86_64.cfg
The appended "r" forces hardware flow control? This was about 1.5 months
ago, so I'm already groggy on details, but this is how we were able to
work around the flow control problems.
Hope that helps!
Cheers and Happy Friday!
Paul
On Fri, 5 May 2006, Josh Martinek wrote:
> On my terminal client I tried VT100, I tried ANSI, VT*, VT100, VT101, etc.,
> and none of them corrected the problem. I also tried passing utf8 to the
> kernel in my isolinux.cfg file, but that didn't work either, like this:
>
> kernel vmlinuz
> append ks=cdrom:/ks.cfg initrd=initrd.img console=ttyS0,38400 utf8
>
> I also set these variables in my kickstrart ks.cfg file:
>
> lang en_US.UTF-8
> langsupport --default en_US.UTF-8 en_US.UTF-8
>
> That didn't help either. I think it's a problem with how anaconda is setting
> up the terminal.
>
> josh
>
>
> On 5/5/06, Oden, James < James.Oden@xxxxxxxxxxx> wrote:
>>
>> Looks like your terminal server needs to be set to a better term type
>> (vt* I think works fine...james
>>
>
