mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: j4K3xBl4sT3r <jakexblaster@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel config problem between 2.4.x to 2.6.x!
Date: Mon, 13 Mar 2006 08:42:06 -0300	[thread overview]
Message-ID: <436c596f0603130342u4d38445bt5e9f129349cda0c8@mail.gmail.com> (raw)
In-Reply-To: <200603130708.13685.nick@linicks.net>

On 3/12/06, Nick Warne <nick@linicks.net> wrote:
> On 12/03/06, j4K3xBl4sT3r <jakexblaster@gmail.com> wrote:
> > I tried also installing the lastest Slackware (10.2, comes with 2.4.x
> > kernel) distro, got it working very well, until installed the Kernel
> > 2.6.x.
> >
> > The problem is:
> >
> > 1. On the slack system, when I install the 2.6.x, everything on the
> > system starts crashing, the Xorg doesnt starts anymore, the network
> > doesnt works anymore (DSL by PPPoE), and also the sound.
>
> Well, I don't know what is going on your end, but I use base Slack 10,
> and when I installed I was on 2.4.x.
>
> Then I upgraded to 2.6.x but used the .config supplied by Pat to build
> a base kernel, which all worked.  Then I modified from there.
>
> The only issue I had (later in 2.6.x development) was udev needed
> upgrading (search lkml for that thread).
>
> Nick
>

I've tried on the last 2 hrs like you, copying the .config from the
2.4.x kernel (slack 10.2) to the newest stable 2.6.15.4. The situation
now was:

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've tryed to do the same on the last 10 mins, but the
compilation of the kernel took too long, around 50 min (I did a small
kernel just with IDE and got on 5min, and a smart kernel for my system
took 15~ mins).

On the LFS system, I still cant compile net-tools, gpm. =/

@Chris, I couldn't get the dmesg, cuz I put fire on my HDC1 first =P
and lsmod doesnt matter to much since most hardware I compile as
built-in, so it doesn't show. But I did a TarGz of this distro hehe,
so I'll try it again and show up to you here.

j4k3.

  parent reply	other threads:[~2006-03-13 11:42 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 [this message]
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
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=436c596f0603130342u4d38445bt5e9f129349cda0c8@mail.gmail.com \
    --to=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®