All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@gentoo.org>
To: Matthew Harrell  <mharrell-dated-1053999362.22891b@bittwiddlers.com>
Cc: Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Strange terminal problem with 2.5.6[8-9]
Date: 22 May 2003 07:31:59 +0200	[thread overview]
Message-ID: <1053581519.6507.22.camel@workshop.saharact.lan> (raw)
In-Reply-To: <20030522013601.GA1327@bittwiddlers.com>

On Thu, 2003-05-22 at 03:36, Matthew Harrell wrote:
> : 
> : The last working kernel I had under my X windows system was 2.5.67-bk7.  After
> : that point every 2.5.6[8-9] and bk patch has had one major problem on my
> : laptop - when I bring up a gnome-terminal or xterm the console prompt never
> : shows up.  The terminals just hang with a blinking cursor but I never get
> : a prompt.  If I reboot with the same setup into my 2.5.67 or any previous
> : kernel then everything works fine.
> : 
> : This is a Debian Sid system running gnome2.  Any ideas?
> : 
> 
> This problem still exists with all current bk patches for 2.5.69.  I'm not
> even sure where to look for the problem.  Since nobody else has reported a 
> problem I'm going to boot back to an older, working kernel and assume the 
> problem as something to do with the configuration I'm using (attached below).
> If anyone has any ideas just let me know and I'll give them a try

2.5.68 and later have depreciated devpts support in devfs.  Thus
you have to enable:

 CONFIG_DEVPTS_FS=y

and mount it during boot.  Easy way is just to add to fstab:

------------------
none	/dev/pts	devpts	defaults	0 0
------------------


Regards,

-- 
Martin Schlemmer



  reply	other threads:[~2003-05-22  5:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-11  0:44 Strange terminal problem with 2.5.6[8-9] Matthew Harrell
2003-05-22  1:36 ` Matthew Harrell
2003-05-22  5:31   ` Martin Schlemmer [this message]
2003-05-22 12:17     ` Matthew Harrell
2003-05-22 18:38       ` Nuno Silva

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1053581519.6507.22.camel@workshop.saharact.lan \
    --to=azarah@gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mharrell-dated-1053999362.22891b@bittwiddlers.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.