Ok, here is the deal... inspiron 9300, Slackware 11.0, Intel 2200 ProWireless. Kernel-2.6.18. My kernel worked great, no complaints whatsoever with my wireless, and everything. Then I was planning to configure my firewall, but i was told that my kernel didnt have support for ipchains. So I went into the kernel config and enabled Network Packet Filtering, because I searched google, and that is what i was told to enable. So I did that, recompiled (make, make install, run lilo). O then restarted, and it started up fine. But since my wireless needs thier own set of drivers/modules, every time I reconfigure my kernel, I need to reinstall those drivers/modules. So I reinstalled, and got to enabling the modules, and I got a kernel panic. I thought that was wierd, but I will restart to maybe fix the problem. I got the same kernel panic. So I saved my old kernel config (2.4.33) So I ran that, got the same kernel error. So I stuck my slackware install disk in to do a boot with the bare.i kernel. Got the SAME kernel panic. I have PHLAK to boot with. I can access my linux partition. I reconfigured the kernel without the option i enabled, but to no avail. I am pretty certain that my error is caused when i am starting up and it tries to start the wireless. My question is how to disable the startup script for my wireless? And why I cant start ANY kernel that I try? I will post the full kernel panic output soon. Leme know of your ideas. Thanks
DragonM15

Alrighty, since I cant exactly simply copy/paste my kernel panic, and i REALLY dont want to write all of this down, here you go:
http://i141.photobucket.com/albums/r...s/100_0281.jpg

Any Ideas?

It looks like the problem is from io_apic. Just recompile the kernel without it, and maybe everything will work fine

I would suggest that you do the following (assuming you are doing kernels from source):

• cd /usr/src/linux
• make a backup copy of .config ... you should keep a copy of every one you've used.
• mv .config foobar
• make distclean
• mv foobar .config
• make
• mount /boot (if necessary)
• make install

You want to make absolutely sure that everything associated with your kernel .. modules and all .. has been successfully compiled; particularly all of the modules! Everything in /lib/modules/kernelversion/kernel should be brand-spanking new when you are finished.

You could be shooting in the dark for a very long time trying to guess-fix this thing. Incompatibility between a module and the resident kernel is an excellent prospect.

I hope that you have been keeping backup copies of all of your .configs, because if you did, a simple diff will tell you exactly what different options were selected between "the one that worked" and "the one that doesn't."

Yeah, but my problem is yes, that i cant boot my slackware, but i cant even boot my old 2.4.33 kernel nemore either... it just makes 3 beeps, and literally shows giberish... as in those funky chars with smiley faces and such But neways, if I boot into PHLAK (live linux distro for those of you who dont know) and I mount my slack drive, and go in and recompile my kernel, will that work, or is there some specail step you have to make, because lets say i want to put my kernel modules in my slackwars /usr/modules/, but in PHLAK since it is the running OS, the folder name would be /mnt/hda4/usr/modules/ Do you understand what I am asking? And yes, I always keep backups of my kernels, assuming i am going to a newer version... if i just change one thing, i dont, because it is ONLY 1 thing But I know the 1 thing i changed... neways, get back to me on that one, and lemme know. Thanks,
DragonM15

Ok, here is what I did.... I booted up my live linux distro, recompiled my 2.4 kernel config, and since by default, the making of the modules goes to /lib/modules/etc... I had to copy those to /mnt/hda4/lib/modules/etc.... and it worked.... so now I have my 2.4 running again, but if I do the same thing to my 2.6 kernel, replacing the old .config with my backup that WORKED earlier... I am back to unable to mount root device..... check out this error..... i have NEVER gotten so many errors before it gave that one...
http://i59.photobucket.com/albums/g2...5/100_0296.jpg I have gotten this error before... the way i resolved it was to place my 2.4 config file in the 2.6 folder, and run make.... it worked last time.... but this time for some reason it gives me the same error shown in the above image... ideas? Thanks

Oh, and one more quick question... my hard drive is a Hitachi 80GB... I did some looking up, and from what I gather my Hard Drive is a Parallel-ATA drive.... so in my kernel config, would I need to enable the parallel port option? Just a thought... I was thikning parallel port as in printer port... but let me know your thoughts.. thanks

I also noticed here: http://rtr.ca/dell_i9300/ That in order to use that hard drive, that person needed to use ata_piix but i have that enabled in all my kernel configs that i have tried.... just to throw that out the window...

Ok, here is the solution for those who need a fix.... Kernel 2.4 recognizes your hard drive as /dev/hda.... whereas Kernel 2.6 recognizes your hard drive as /dev/sda...
This to do to fix this problem:
1. Compile your kernel with your filesystem included (ext3, reiserfs, etc...)
2. Compile your kernel with your hardware included (in my case I needed ata_pIIx, SCSI_ATA, and QLA5XXX)
3. Modify your /etc/lilo.conf to have the root partitions as /dev/sda#
4. If you have a windows partition leave it as hda
5. Modify /etc/fstab and change all hda's to sda's