Re: How does it do it.
From: Nico Kadel-Garcia (nkadel_at_comcast.net)
Date: 01/30/05
- Next message: Michael Heiming: "Re: How does it do it."
- Previous message: ed doyle: "How does it do it."
- In reply to: ed doyle: "How does it do it."
- Next in thread: Michael Heiming: "Re: How does it do it."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 30 Jan 2005 11:21:26 -0500
"ed doyle" <doyleed@gmail.com> wrote in message
news:Gx7Ld.2633$S3.1971@newsread2.news.atl.earthlink.net...
> Many months ago, I downloaded the install CD's for RedHat 9.0 and
> isntalled it on my then Windows 95 only computer. Everything went fine.
> Somehow it figured out everything it needed to know about my cd drive, dvd
> drive, hard drives, audio, and everything worked perfectly.
>
> While Redhat update worked, I did all the updates and they always worked.
>
> Now I have tried to build the kernel 2.6.10. I had no .config file to
> start with as I had only done the RH install and updates, never built the
> RH 2.4 kernel from sources.
>
> I have by trial and error gotten a .config file that builds a kernel that
> boots, albeit with several errors or warnings related to iptables,
> mousedev, keyboarddev, fsdev, and a missing multimedia keyboard. Never
> the less, this kernel boots all the way to a log on screen, and once I log
> on - many things work - my usb keyboard, usb mouse, networking, audio all
> work.
Don't put a 2.6 kernel on RedHat 9 by building it yourself. Arjanv at RedHat
did a nice job of building up RPM dependencies for it, but really, start
with the RPM's from Fedora because those will list all the dependencies of
other packages like modutils.
At this point, if you can get into it, you should probably do a forklift
upgrade to Fedora Core 3, or use an RPM installation to revert to a 2.4
published RedHat 9 kernel.
> I can mount CD's but I can not write to them.
>
> What I don't understand is how was the original RH 9 install CD able to
> interrogate my hardware and come up with a build of a 2.4 kernel where
> everything worked and there were no errors, and yet when I attempt to
> build a 2.6 kernel by hand, there seems to be so many things that I have
> no clue as to what to read or how to analyze what is causing the error.
You need to read the 2.6 kernel documentation. There have been big changes
in related packages, and compatibility changes with compilers, that you
should avoid trying to wade through by hand if possible.
> If we take one problem at a time, supose we pick not being able to write
> to a CDRW. I can read the same CDRW. I can't even do cdrecord -scanbus.
> I get errors about /dev/pg? not found or something like that.
For example: the older cdrecord software relied on the use of an "ide-scsi"
module to provide SCSI like access to IDE devices like CD drives, which is
being deprecated in the 2.6 kernel.
> My 2.4 kernel still workes perfectly, and I am only interested in trouble
> shooting the 2.6 kernel for the learning experience, but I am afraid I am
> not sure even where to start. Any advice or comments are certainly
> welcome (including switch to windows, although I won't follow that advice
> because I am stubborn).
Start from the RPM's to get the dependencies right. You've basically shoved
a truck engine on top of a speedboat: you can make it work, but it'll be
better if you actually put the 2.6 kernel on an OS more recent rhan RedHat
9, one built to use it.
- Next message: Michael Heiming: "Re: How does it do it."
- Previous message: ed doyle: "How does it do it."
- In reply to: ed doyle: "How does it do it."
- Next in thread: Michael Heiming: "Re: How does it do it."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
