SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Another thing I have noticed is that I have to manually rename vmlinuz to vmlinuz.old before compiling otherwise vmlinuz is just overwritten with new kernel. But I'm still getting FATAL FAILED TO LOAD MODULE xxx errors so blah
I did exactely what DaOne wrote in his lil' tut.
Everything went well until i tried to boot from the new (2.6.2) kernel.
The graphical console is working, the system seems to starts normal but I get a kernel panic.
Code:
VFS: Cannot open root device "001" or unknown-block(0,1)
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on unknown-block(0,1)
/dev/hda2 could be /dev/hdc8 or something
type: df
to see the partitions.
DaOne,
hello! from a fresh installed slackware 9.1, I followed every step in your tut.
copied .config from /usr/src/linux-2.4.22 to /usr/src/linux <-- symlink of /usr/src/linux-2.6.2
im using nvidia riva tnt2 and downloaded nVidia 2.6 ready drivers from: http://www.sh.nu/download/nvidia/
but i get a blank screen after i reboot.
i also followed on of the posts here that i should set y option to
CONFIG_VGA_CONSOLE=y
CONFIG_MDA_CONSOLE=m
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=m
CONFIG_PCI_CONSOLE=y
CONFIG_FONTS=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
etc.......
but i still get a blank screen.
is there something im missing???
is it the 2.6.2 version of the kernel or is the nVidia driver?
bashrc2
Thanks, but it still doesn't work. It's the same game, just the code is no longer 001, it's 801 now.
Does it matter where in lilo.conf i add the line?
I was just compiling the 2.6.2 kernel tonite and had the same problem. It came down to having to add support for my Promise IDE controller. (It seems I keep "discovering" this.)
Double-check the ATA device section to see if yours is listed.
hmmm ... but, if I imported my old .config the driver should be in there, shouldn't it?
edit:
I just recompiled the kernel, rebooted and get a bank screen -_-
BIIIG THANKS to the one who mentioned to make a linux.safe and add this to lilo!!!
Heh, I'm pretty confused now, I compiled FOR SURE the ATI Radeon drivers.
With the first messed up version of the 2.6.2 kernel i got a kernel panic but the graphic console worked. Do I need to add the 'Frambuffer Console support' ?
I just want my box to run properly *sob*
regards
cf
second edit:
recompiled kernel again, got the console to work, now the kernel panic: VFS shows up again
But I found out in menuconfig there is no driver that does support my raid (it was supported in 2.4.22, just had to choose adaptec.s during installation)
Did I forget something important? As I mentioned before, still a noob ...
Last edited by [c0ld~fusi0n]; 02-06-2004 at 09:51 AM.
Originally posted by [c0ld~fusi0n]
recompiled kernel again, got the console to work, now the kernel panic: VFS shows up again
But I found out in menuconfig there is no driver that does support my raid (it was supported in 2.4.22, just had to choose adaptec.s during installation)
Did I forget something important? As I mentioned before, still a noob ...
Aha! I think you're almost there. adaptec.s tells me I had you look in the wrong section. Instead of ATA, check out Device Drivers/SCSI Device Support/SCSI Low-level drivers.
There are several adaptec cards in there. Just add yours and you should be golden.
Originally posted by major.tom Aha! I think you're almost there. adaptec.s tells me I had you look in the wrong section. Instead of ATA, check out Device Drivers/SCSI Device Support/SCSI Low-level drivers.
There are several adaptec cards in there. Just add yours and you should be golden.
Garry
I did that, but in there, my card (Adaptec SCSI RAID 2100S) is not listed (at least my search wasn't succesful). But during the installation my card was recognized and it worked great (well, let's it just worked, didn't really test if it works great).
And considering what i see flying by during the bootup there is something with the word adaptec in it.
I really hope someone can help me with this issue.
Originally posted by [c0ld~fusi0n]
I did that, but in there, my card (Adaptec SCSI RAID 2100S) is not listed (at least my search wasn't succesful). But during the installation my card was recognized and it worked great (well, let's it just worked, didn't really test if it works great).
And considering what i see flying by during the bootup there is something with the word adaptec in it.
I really hope someone can help me with this issue.
regards
cf
It's *possible* (but I'm guessing unlikely) that your card isn't supported yet. There is a generic (I think) Adaptec RAID (AACRAID). Did you try compiling/booting with that? I'm pretty sure, too, that the hd controller cannot be built as a module -- it has to be in the kernel.
Reading the text files referred to in the comments for each driver might help. Or googling. Personally, I haven't experienced this problem, but I don't have the same card.
If you want to see the boot messages, use 'dmesg' and pipe the output to a file or less/more/most.
Originally posted by major.tom It's *possible* (but I'm guessing unlikely) that your card isn't supported yet. There is a generic (I think) Adaptec RAID (AACRAID). Did you try compiling/booting with that? I'm pretty sure, too, that the hd controller cannot be built as a module -- it has to be in the kernel.
Reading the text files referred to in the comments for each driver might help. Or googling. Personally, I haven't experienced this problem, but I don't have the same card.
If you want to see the boot messages, use 'dmesg' and pipe the output to a file or less/more/most.
dmesg | most
Cheers!
Garry
Thanks. Tried it but it still didn't work I still get the same bloody error message. BTW, the AAC RAID driver is experimental. The point that's confusing me is that my card worked (and still works) under 2.4.22. This makes no sense to me, the new kernel should have MORE support, not less. And my SCSI card isn't very new either.... Maybe there is a possibility to carry the module respectively the driver over from my old kernel? (Without any extreme complex procedures, I'm still new to the linux system.)
I cannot get the ati drivers working in 2.6.2 either. I have no problem getting to a console on boot, but when I type startx, all I get is a blank screen. I followed the same procedure I used to get them working on 2.4.21, but it does not work in 2.6.2.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.