From: Chris Largret <largret@gmail.com>
To: j4K3xBl4sT3r <jakexblaster@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel config problem between 2.4.x to 2.6.x!
Date: Mon, 13 Mar 2006 16:52:52 -0800 [thread overview]
Message-ID: <1142297572.7090.4.camel@shogun.daga.dyndns.org> (raw)
In-Reply-To: <436c596f0603130342u4d38445bt5e9f129349cda0c8@mail.gmail.com>
On Mon, 2006-03-13 at 08:42 -0300, j4K3xBl4sT3r wrote:
> 1. before, the mouse worked fine. now, it doesnt works
> 2. before, the sound worked. and now, still working, just with ALSA,
> no OSS support (tested with mpg321 and ogg123 on bash terminal)
> 3. strangely, the X worked fine after the kernel update, is DRM and
> AGPGART needed by Xorg?
> 4. before, the PPPoE connected within the 2 first "." (seconds?). Now,
> doesnt work, I always get TIMEOUT from PPPoE.
> 5. the PNPDUMP returns a empty file on the isapnptools (from the
> compilation, this is the only file that gets fully compiled)
>
> This situation happened on the Slackware 10.2, assuming a Kernel
> Update.
I'm running Slackware 10.2 on my server with the 2.6 kernel. Did you
remember to chmod +x /etc/rc.d/rc.udev? It is either an issue with /dev
or an issue with the drivers not being initialized correctly.
--
Chris Largret <http://daga.dyndns.org>
next prev parent reply other threads:[~2006-03-14 0:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-12 18:15 j4K3xBl4sT3r
2006-03-12 20:43 ` Chris Largret
[not found] ` <7c3341450603121247n7afe018m@mail.gmail.com>
[not found] ` <436c596f0603121632qe3151k793fd3ccd9a0eacb@mail.gmail.com>
[not found] ` <200603130708.13685.nick@linicks.net>
2006-03-13 11:42 ` j4K3xBl4sT3r
2006-03-13 18:06 ` Lee Revell
2006-03-16 11:25 ` Pavel Machek
2006-03-16 19:06 ` Lee Revell
2006-03-15 23:13 ` Pavel Machek
2006-03-16 20:49 ` Lee Revell
2006-03-14 0:52 ` Chris Largret [this message]
2006-03-14 1:31 ` j4K3xBl4sT3r
2006-03-14 1:37 ` Lee Revell
2006-03-14 20:50 ` marcos cunha
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=1142297572.7090.4.camel@shogun.daga.dyndns.org \
--to=largret@gmail.com \
--cc=jakexblaster@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®