And another addition: When I press CTRL-S in an ssh session, it locks the ssh-terminal, I can unlock it by pressing CTRL-Q - that's the normal behaviour I'm used to. But on the console, this doesn't work... MARK > BTW, the same thing happens when I press CTRL-S. > The machine locks up completely. I opened a remote session > via ssh before pressing CTRL-S. The session does not respond > any more and gets disconnected after a while. > > MARK > > > > > > > Hi, > > > > I have a brand new Core3 system installed on an old Compaq > > Proliant 1815R - I used to have a RedHat system (don't > > remember the version, but it was before 8) on there that I > > wiped and replaced with the Core 3. I had to specify some > > parameters like "ide=nodma nousb nofirewire apm=off > > pcmcia=off" to get the thing to run without problems. > > > > I used a 2-port KVM to switch between that machine and my > > Windows box; the kind that switches when you press > > Scroll-Lock twice. That worked fine with the redhat system, > > but now on Core3, the box freezes on me when I press > > "Scroll-Lock". I first thought it was a problem with the KVM, > > but it still happens even when I plug the keyboard (PS/2 > > btw.) in directly. > > > > The machine is running as a server in text-only mode, without X. > > > > Since it worked fine under Redhat I expect that there is some > > switch/configuration that should fix this problem? > >
