From: Benjamin Henne <metalhen@metalhen.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: gaim problems in 2.6.0
Date: Sun, 04 Jan 2004 20:55:01 +0100 [thread overview]
Message-ID: <3FF86F95.6040304@metalhen.de> (raw)
In-Reply-To: <20040104172535.GA322@elf.ucw.cz>
Pavel Machek wrote:
> Hi!
>
> I'm having bad problems with gaim... When I run gaim, my machine tends
> to freeze hard (no blinking leds). I'm running vesafb -> that should
> rule out X problems. Machine is rather strange pre-production athlon64
> noteook, but I'm running 32-bit (on 32-bit kernel), and I can run gaim
> under 2.4.X kernel.
>
> [Ugh, I was running with kgdb, but I recall same problem before, too.]
>
> Does anyone have similar problem?
> Pavel
It's not a so similiar problem or is it.
I also have problems with gnome and freezing when using 2.6.0.
With my old 2.4.20 kernel all is ok. My problems starts with 2.6.0
installation, which I needed for some hardware support. The new kernel
works well in console. Have no errors in `dmesg`, not even in syslog.
If I setup a nework device and then also define a default route to my
gateway gnome seems to freeze with it's first network access.
If I start net and then gnome, gnome needs to start over 20-30minutes
and still did not come up totally. If I setup network in a xterm in
gnome then gnome freezes after a short while, e.g. when starting mozilla.
It is no hard freeze, it looks like gnome is running on a 1 Mhz PC or as
if it has time lack of several minutes.
But it's only in grapical gnome. In a console I can surf with lynx.
First I thougth it could be a gnome problem, but problems only come when
booting with 2.6.0
Benjamin
next prev parent reply other threads:[~2004-01-04 19:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-04 17:25 gaim problems in 2.6.0 Pavel Machek
2004-01-04 17:48 ` Justin Pryzby
2004-01-04 18:37 ` Mike Fedyk
2004-01-04 18:44 ` Pavel Machek
2004-01-04 20:01 ` Dr. David Alan Gilbert
2004-01-04 18:51 ` Peter Zijlstra
2004-01-04 19:57 ` David Ford
2004-01-04 19:55 ` Benjamin Henne [this message]
2004-01-04 20:01 ` Pavel Machek
2004-01-07 10:38 ` Matthias Urlichs
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=3FF86F95.6040304@metalhen.de \
--to=metalhen@metalhen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox