On Sun, 22 Jun 2003, Alex Scarbro wrote:
using hyperterm), however,
^^^^^^^^^
nope. Don't use hyperterm, it's useless. You've got to use minicom on linux or youu will find that you are dropping huge amounts of output.
ron
This is my setup using kermit. I prefer kermit over minicom. I have yet to be able to get linuxbios booting (due to mtd issues), however, here's my setup that works with the normal kernel boot. You might need to augment the speed to 9600 or 19200 instead of 115200.
/etc/lilo.conf contains: append="console=ttyS1,115200"
~/.kermrc set modem type none set line /dev/ttyS1 set speed 115200 set flow rts/cts set carrier-watch off
You also need to set the speed of the com port via setserial before starting minicom or kermit.
ie:
# setserial /dev/ttyS1 baud_base 115200
On Mon, 2003-06-23 at 00:16, Alex Scarbro wrote:
On Sun, 22 Jun 2003 19:22:11 -0600 (MDT), ron minnich wrote:
On Sun, 22 Jun 2003, Alex Scarbro wrote:
using hyperterm), however,
^^^^^^^^^
nope. Don't use hyperterm, it's useless. You've got to use minicom on linux or youu will find that you are dropping huge amounts of output.
ron
Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
hi there,
Cheers for the reply. I'll get minicom setup. It was late at night that i finally got the K7sem booting, and hyperterm was the only terminal on hand. BTW, do you use any handshaking on the terminal (ie hardware/software/none)?
Thanks again
--
Alex Scarbro, linuxbios@techfreakz.net on 23/06/2003
_______________________________________________ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
On Mon, 23 Jun 2003, Alex Scarbro wrote:
Cheers for the reply. I'll get minicom setup. It was late at night that i finally got the K7sem booting, and hyperterm was the only terminal on hand. BTW, do you use any handshaking on the terminal (ie hardware/software/none)?
I usually turn all handshaking off.
ron
OK, I am now seeing these K7SEM lockups I think from more than one person, happening in that 'set UC on the fixed MTRRs' step.
Is there any chance that recent changes to improve boot time have caused trouble in the K7-based boards?
ron
On Sun, Jun 22, 2003 at 07:22:45PM -0600, ron minnich wrote:
OK, I am now seeing these K7SEM lockups I think from more than one person, happening in that 'set UC on the fixed MTRRs' step.
I've seen this symptom on EPIA when the RAM is not correctly initialized. I thought that until MTRR is set to UnCacheable, linuxbios_c runs on cache, not RAM.
Is there any chance that recent changes to improve boot time have caused trouble in the K7-based boards?
At least my modification to enable cache on 0xF0000-0xFFFFF area is not in CVS.
-- Takeshi
On Mon, 23 Jun 2003, SONE Takeshi wrote:
At least my modification to enable cache on 0xF0000-0xFFFFF area is not in CVS.
I still owe you that patch.
I'll commit it, I guess, but this will have to be the last one.
Let's try to all make sure it works ...
ron
On Tue, 24 Jun 2003, Alex Scarbro wrote:
rock n roll n compile, that will contribute/help in getting the K7SEM up and running in light of the recent changes to LInuxBIOS. Also, can i access an earlier version of the linuxbios CVS tree that might be more fruitfull?
Please see Andrew's small hack from yesterday and try it. It is a *very* short-term solution and we need a real answer, but it should help you.
ron