On Wed, 6 Aug 2003 02:16:21 -0700, Paul Dickson wrote:
> But all is not perfect. I'll attach the problems I had as replies (so
> each has it's own message thread).
I built 2.6.0-test2 for my Dell Inspiron 7000 notebook (PII, 300Mhz) with
a RH9 distribution. I build the kernel on another system (1.33GHz) using
ssh.
I was missing some device support, so did a "make menuconfig". The
configuration options were shown, I selected "Sound -->" and pressed
enter. The terminal went back to text mode and then hung. Gnome-terminal
started consuming all unused CPU cycles.
I could recover the process by closing the tab or resetting the terminal,
but this would only fix the problem for the moment. Frequently, it
wouldn't even finish redisplaying the screen before it locked again.
This would happen running "make menuconfig" locally or via ssh on another
system.
This is likely caused by some difference in the tty code in 2.6.0-test2.
The problem does not occur under 2.4.20-18.9. If 2.6.0-test2 is correct,
then I might need an updated version of gnome-terminal suitable for 2.6.0.
-Paul
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Aug 07 2003 - 22:00:32 EST