I'd just INstall the Binary Kernel... It works well..

Post #79,526

2/5/03 1:14:37 PM

I am currently running the Testing Kernel on a both Debian Boxen I have so far... 2.4.20-5

Recognizes dam near everything *I* need... (I have a camera it pukes on... way OFF brand, if bought in Taiwan, it'd have been a Cheap import knock-off of the ones THEY make as knock-offs...)

Get a working system first *THEN* screw it up... It seems to be always easier to get a Known Good a t one time system back from the dead that way... Same Idea in RedHat and Mandrake etc...

[link|mailto:curley95@attbi.com|greg] - Grand-Master Artist in IT

[link|http://www.iwethey.org/ed_curry/|REMEMBER ED CURRY!] [link|http://pascal.rockford.com:8888/SSK@kQMsmc74S0Tw3KHQiRQmDem0gAIPAgM/edcurry/1//|ED'S GHOST SPEAKS!]

[link|http://www.eweek.com/article2/0,3959,857673,00.asp|Writing on wall, Microsoft to develop apps for Linux by 2004]

Heimatland Geheime Staatspolizei reminds:
These [link|http://www.whitehouse.gov/pcipb/cyberstrategy-draft.html|Civilian General Orders], please memorize them.
"Questions" will be asked at safety checkpoints.

Post #79,535

by inthane-chan

2/5/03 1:34:15 PM

Just tried that.

Puked on me pretty bad (kernel panic), and so I manually hacked it back to the old kernel. I'd dump the spew here if I knew where it threw boot spew - couldn't find anything looking like it after I jumped back to 2.2.20. I may try again...

"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd all be running around in darkened rooms, munching magic pills and listening to repetitive electronic music." -- Kristian Wilson, Nintendo, Inc, 1989

Post #79,539

by folkert

2/5/03 1:44:20 PM

Okay... I *GUESS*...

I am just shicked at how hard it is to get the 2.4 kernel to workey...

Of course we both know, you have less "experience" than I... but that shouldn't preclude you from running the Kernel...

OK, just for Grins and Giggle as We are experiencing ALOT of issues here...

Why not try a re-install using bf24, select testing... and if you can, don't select Frame Buffer... UNLESS you have to... DRM might be better...

And this is still the first time I have suggested an R&R...

[link|mailto:curley95@attbi.com|greg] - Grand-Master Artist in IT

[link|http://www.iwethey.org/ed_curry/|REMEMBER ED CURRY!] [link|http://pascal.rockford.com:8888/SSK@kQMsmc74S0Tw3KHQiRQmDem0gAIPAgM/edcurry/1//|ED'S GHOST SPEAKS!]

[link|http://www.eweek.com/article2/0,3959,857673,00.asp|Writing on wall, Microsoft to develop apps for Linux by 2004]

Post #79,661

by lordbeatnik

2/5/03 7:01:30 PM

Re: Just tried that.

Configuring the debian kernels for the first time is a PITA. You may need to configure /etc/mkinitrd/modules. And then you need to recreate the initrd.

First off, lets configure /etc/mkinitrd/modules. It needs to list all the modules for accessing your root filesystem. So, you'll need to load modules for your filesystem and some for your hard disk.

For example, my one box with ext3 and a scsi disk has:

jbd
ext3
scsi_mod
sd_mod
sym53c8xx

For ext3 and and an ide disk, you should need:

jbd
ext3
ide-mod
ide-disk

Then, you need to rerun mkinitrd. run "mkinitrd -o INITRD_FILE_NAME /lib/modules/KERNEL_VERSION". e.g. For my 2.4.20-k6 kernel, I run "mkinitrd -o /boot/initrd.img-2.4.20-k6 /lib/modules/2.4.20-k6"

Last of all, when you set up grub or lilo, make sure you have the kernel parameter root=ROOT_DEV set. If you don't set it's root dev, it'll try and use /dev/ram0 as root IIRC.

Wasn't that fun?

David "LordBeatnik"

Post #79,766

by pwhysall

2/6/03 2:34:40 AM

Boot Spew

/var/log/messages
/var/log/dmesg

Welcome to IWETHEY!