public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Shillinglaw <linuxtech@knology.net>
To: mikpe@csd.uu.se
Cc: linux-kernel@vger.kernel.org
Subject: Re: Still more Redhat Module Troubles
Date: 25 May 2003 00:29:26 -0400	[thread overview]
Message-ID: <1053836965.2912.5.camel@Aragorn> (raw)
In-Reply-To: <200305241014.h4OAE8s0011456@harpo.it.uu.se>

Thanks again,

My only real problem now seems to be that while X loads like it's
supposed to, my mouse ( generic ps/2 wheel mouse ) doesn't move once X
has started.

Only other problems were a message about keybdev being not found which I
understand is normal, and a usb-ohci not found error which hopefully I
found the missing config setting for.

If I can just figure out why the mouse doesn't work, I'll be running on
2.5.69

Thanks again
On Sat, 2003-05-24 at 06:14, mikpe@csd.uu.se wrote:
> On 24 May 2003 00:02:30 -0400, John Shillinglaw wrote:
> >Anyway I get not found messages when redhat modprobes char-major-10-1,
> >eth1, etc. when it boots up. This seems to be related to aliases since
> >eth1 is aliased to sis900 and char-major-10-1 to psaux. All help greatly
> >appreciated... exact details and .config file below:
> ...
> >I also tried to run the generate modprobe.conf script with no changes to
> >the behavior.
> 
> Did you install the generated modprobe.conf in /etc? If not, do so.
> 
> rc.sysinit has a known problem that causes it to disable module
> autoloading in 2.5 kernels. Fixed by the patch below.
> 
> mkinitrd generally doesn't work with 2.5 modules, or once the new
> module-init-tools have been installed. I don't know how to fix
> that; maybe an LKML archive search will find something.
> 
> --- /etc/rc.d/rc.sysinit~	2003-02-24 22:54:17.000000000 +0100
> +++ /etc/rc.d/rc.sysinit	2003-05-01 17:07:09.000000000 +0200
> @@ -357,7 +357,7 @@
>      IN_INITLOG=
>  fi
>  
> -if ! LC_ALL=C grep -iq nomodules /proc/cmdline 2>/dev/null && [ -f /proc/ksyms ]; then
> +if ! LC_ALL=C grep -iq nomodules /proc/cmdline 2>/dev/null && [ -f /proc/modules ]; then
>      USEMODULES=y
>  fi
>  
> 


  reply	other threads:[~2003-05-25  4:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-24 10:14 Still more Redhat Module Troubles mikpe
2003-05-25  4:29 ` John Shillinglaw [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-24  2:45 HD DMA disabled in 2.4.21-rc2, works fine in 2.4.20 Lars
2003-05-24  4:02 ` Still more Redhat Module Troubles John Shillinglaw

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=1053836965.2912.5.camel@Aragorn \
    --to=linuxtech@knology.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    /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