[TriLUG] making modules
Ben Pitzer
uncleben at mindspring.com
Wed Dec 5 09:52:22 EST 2001
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Barry,
I understand. I suppose the first question is whether you overwrote your
previous kernel image in the /boot directory. If not, it's an easy matter
of correcting your LILO configuration and rebooting into that kernel.
Otherwise, you may need to break out the SuSE CD and try to reinstall the
original kernel RPM. Of course, since the RPM database will think that
the RPM is already install (and of course it is), you may need to force
it, but I'll make no recommendations there. I'm not RPM guru (I much
prefer Debian packages, myself), so you might want to ask some others here
about that.
Check /boot first, though, and see if you have multiple kernel images
there, and we can walk you through configuring /etc/lilo.conf if
necessary.
Regards,
Ben Pitzer
On Wed, 5 Dec 2001, Barry Ruvio wrote:
> Hi Ben,
> The thing is, that this was all working fine before I made my new kernel.
> All I want to do is to put it back the way it was. I can get the new sources
> for the newer kernels sometime later.
> Barry
> ----- Original Message -----
> From: "Ben Pitzer" <uncleben at mindspring.com>
> To: <trilug at trilug.org>
> Sent: Tuesday, December 04, 2001 9:17 AM
> Subject: Re: [TriLUG] making module
>
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Barry,
> >
> > Okay, you should be using at LEAST be running 2.2.18, I think, and you
> > could be running kernel 2.4 if you could get it onto your system. In any
> > case, not having Internet access on that machine is key. Somehow, you
> > need to get the SuSE kernel's sources on RPM update onto a disk and port
> > it over to the Linux side. Once the kernel stuff is there, then you can
> > go about compiling a new 2.4 or 2.2 kernel on your system.
> >
> > Incidentally, do you use a modem or a network card for your connectivity
> > device, and do you know what make/model that modem/card is? You need that
> > information to track down what modules you need to get that device
> > workable under your kernel.
> >
> > Good luck,
> > Ben Pitzer
> >
> >
> > On Tue, 4 Dec 2001, Barry Ruvio wrote:
> >
> > > Hi Ben,
> > > I'm using Suse 7.1 and I didn't realize that I'm using such an old
> kernel.
> > > At the moment, I can't print, use the internet and use the usb port so I
> am
> > > having to rely on Windows. If you could point out my error and what I
> can do
> > > to fix it I would be very happy.
> > > Thanks,
> > > Barry
> > > ----- Original Message -----
> > > From: "Ben Pitzer" <uncleben at mindspring.com>
> > > To: <trilug at trilug.org>
> > > Sent: Sunday, December 02, 2001 2:53 PM
> > > Subject: Re: [TriLUG] making module
> > >
> > >
> > > > -----BEGIN PGP SIGNED MESSAGE-----
> > > > Hash: SHA1
> > > >
> > > > Barry,
> > > >
> > > > First of all, what distro are you using, and why are you still using
> > > > kernel 2.0.x? You should probably be at least up to 2.2.x or even
> 2.4.x,
> > > > unless your current distro specifically cannot handle anything more
> modern
> > > > than 2.0.x.
> > > >
> > > > Regards,
> > > > Ben Pitzer
> > > >
> > > > On Sun, 2 Dec 2001, Barry Ruvio wrote:
> > > >
> > > > > I have made a new kernel in order to tryout some new features with
> video
> > > capture. The new kernel won't run correctly and neither will the old
> one.
> > > The old one is having problems with finding modules. After making the
> new
> > > kernel I ran make modules and make module_install. I now have two
> > > subdirectories in the modules directory. One is called 2.0.4 and the
> > > original one is called 2.0.4-GB. One of the modules that the kernel
> can't
> > > find is the pppd and so I can't use the dialup ppp connection on Linux.
> > > > > I tried doing a make mrproper to start over but this didn't help.
> Any
> > > suggestions would be appreciated.
> > > > > Barry Ruvio
> > > > >
> > > > -----BEGIN PGP SIGNATURE-----
> > > > Version: GnuPG v1.0.6 (GNU/Linux)
> > > > Comment: For info see http://www.gnupg.org
> > > >
> > > > iD8DBQE8CobULVEMrcXswYQRAllLAJwOkNL3Hvp0Vuz4LBUaw218gXtxngCfetJn
> > > > Z9jnhP4hsfCHfdM5XxLrIgQ=
> > > > =Xz0e
> > > > -----END PGP SIGNATURE-----
> > > >
> > > >
> > >
> > > _______________________________________________
> > > TriLUG mailing list
> > > http://www.trilug.org/mailman/listinfo/trilug
> > >
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.0.6 (GNU/Linux)
> > Comment: For info see http://www.gnupg.org
> >
> > iD8DBQE8DNsSLVEMrcXswYQRAvA/AJ9RUOrQzqu+UefNckM0BISvlv1jRQCfVkjC
> > bZiw+2J2GSf/xoholAIMUK0=
> > =vIQ3
> > -----END PGP SIGNATURE-----
> >
> >
>
> _______________________________________________
> TriLUG mailing list
> http://www.trilug.org/mailman/listinfo/trilug
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE8DjSpLVEMrcXswYQRAmNMAJ49Mep/KIur8G+ahO+hmDhHFFzedACdEnor
9EmJR86M3L+UNTh3ooZdJKA=
=IaNw
-----END PGP SIGNATURE-----
More information about the TriLUG
mailing list