Server Administration
 
Forums: » Register « |  User CP |  Games |  Calendar |  Members |  FAQs |  Sitemap |  Support | 
User Name:
Password:
Remember me
Go Back   Codewalkers ForumsOther TechnologiesServer Administration

Reply
Add This Thread To:
  Del.icio.us   Digg   Google   Spurl   Blink   Furl   Simpy   Y! MyWeb 
Thread Tools Search this Thread Rate Thread Display Modes
 
Unread Codewalkers Forums Sponsor:
AT&T devCentral & BlackBerry(r) Webcast Series: BlackBerry and GPS -Build Location Awareness into your BlackBerry Applications, July 10th-1:00PM EST. Register Today!
  #1  
Old December 29th, 2003, 04:35 PM
tkarkkainen's Avatar
tkarkkainen tkarkkainen is offline
Moderator
Click here for more information
 
Join Date: Apr 2007
Location: Finland
Posts: 2,320 tkarkkainen User rank is Lance Corporal (50 - 100 Reputation Level)tkarkkainen User rank is Lance Corporal (50 - 100 Reputation Level)tkarkkainen User rank is Lance Corporal (50 - 100 Reputation Level)  Folding Points: 10700 Folding Title: Novice Folder
Time spent in forums: 6 Days 8 h 46 m 44 sec
Reputation Power: 4
Kernel problems

I have Debian on my computer. It's currently running rather ancient kernel, version 2.2.20. I wanted a newer one so that it would recognize my USB mouse, I could use my sound card and put the nVidia video driver so I could play Enemy Territory from Linux.

I used apt-get to install the kernel 2.4.18-686 (the newest available through apt-get.) Then I created a grub boot diskette. Grub refuses to find my HD which contains the linux root partition /dev/hdd5.

Then I thought I'd create a syslinux diskette and put the new kernel on the boot disk and boot that way. Well, it found the kernel, but after loading the kernel it saind Kernel panic: no root partition found. The new kernel couldn't find my hard disk at /dev/hdd!!!

The older kernel is able to find it. Any suggestions? I've already tried to change the HD to /dev/hdb but it didn't work. Even Windows couldn't find it anymore.

Reply With Quote
  #2  
Old December 31st, 2003, 03:14 AM
bluephoenix's Avatar
bluephoenix bluephoenix is offline
Levelheaded Curmudgeon
Codewalkers Novice (500 - 999 posts)
 
Join Date: Apr 2007
Location: Syracuse, NY
Posts: 507 bluephoenix User rank is Just a Lowly Private (1 - 20 Reputation Level) 
Time spent in forums: 7 h 13 m 2 sec
Reputation Power: 2
Send a message via AIM to bluephoenix
RE: Kernel problems

Have you considered compiling the kernel from source?

I did this recently on my Mandrake laptop so I could use some power management features. I was able to download the distribution specific kernel source... I learned that distributions tend to heavily patch their kernels and I'm not experienced enough to get a "clean kernel" compile working yet.

The kernel configuration file for you current kernel is probably in /boot/config (remember to back the file up, just in case). When you do "make xconfig" you'll be able to load a previous configuration file... load /boot/config and change only what's necessary for you USB support. Sometimes you'll change a few things and it wont work, and you won't really know what specifically it was that broke everything.

There are plenty of kernel compile tutorials avaialable on the internet. But my 2-cents is just to try and find a distribution specific source and make small changes to the config at a time.

Best of luck.

Reply With Quote
  #3  
Old December 31st, 2003, 03:51 PM
tkarkkainen's Avatar
tkarkkainen tkarkkainen is offline
Moderator
Click here for more information
 
Join Date: Apr 2007
Location: Finland
Posts: 2,320 tkarkkainen User rank is Lance Corporal (50 - 100 Reputation Level)tkarkkainen User rank is Lance Corporal (50 - 100 Reputation Level)tkarkkainen User rank is Lance Corporal (50 - 100 Reputation Level)  Folding Points: 10700 Folding Title: Novice Folder
Time spent in forums: 6 Days 8 h 46 m 44 sec
Reputation Power: 4
RE: Kernel problems

Thank you Timothy. Yes, I have considered compiling the kernel from source, but because I am a Linux newbie, I don't have the courage yet. First I'd like to see if there are other options. I wrote up the exact error messages.

VFS: Cannot open root device "hdd5" or 16:45
Kernel panic: VFS: unable to mount root fs on 16:45

This is a bit confusing message.On the first line it says 'or' and on the second line it says 'on'. What does 16:45 mean? It is not the time coz the the clock didn't say 16:45 that time.

Reply With Quote
  #4  
Old January 3rd, 2004, 06:03 AM
bluephoenix's Avatar
bluephoenix bluephoenix is offline
Levelheaded Curmudgeon
Codewalkers Novice (500 - 999 posts)
 
Join Date: Apr 2007
Location: Syracuse, NY
Posts: 507 bluephoenix User rank is Just a Lowly Private (1 - 20 Reputation Level) 
Time spent in forums: 7 h 13 m 2 sec
Reputation Power: 2
Send a message via AIM to bluephoenix
RE: RE: Kernel problems

From your second post I gather your problem isn't with the kernel, but it rather finding the disk partition to mount the root file system.

I believe hdd5 and 16:45 are the same, you know it as hdd5 and the kernel knows it as 16:45. Think of it as "Cannot opn root device on hdd5 or 16:45" is like saying, "Hey, what's the way to New York City, or NYC?"

I don't have much experience with GRUB my server boot using GRUB but my laptop (which is where I spend most of my time) uses LILO. Hopefully this'll be a learning experience for me as well!

What does your grub.conf say? It's usually in /boot/grub/grub.conf, but if not then perhaps check /boot/grub/menu.lst.

The following is mine:

timeout 10
color black/cyan yellow/cyan
i18n (hd0,0)/boot/grub/messages
keytable (hd0,0)/boot/us.klt
altconfigfile (hd0,0)/boot/grub/menu.once
default 0

title linux
kernel (hd0,0)/boot/vmlinuz root=/dev/hda1 devfs=mount hdc=ide-scsi
initrd (hd0,0)/boot/initrd.img

title failsafe
kernel (hd0,0)/boot/vmlinuz root=/dev/hda1 devfs=nomount hdc=ide-scsi failsafe
initrd (hd0,0)/boot/initrd.img

title floppy
root (fd0)
chainloader +1

What we're looking for specifically is how the entry appears for your older (functional) kernel. In this case, for me it is:

title linux
kernel (hd0,0)/boot/vmlinuz root=/dev/hda1 devfs=mount hdc=ide-scsi
initrd (hd0,0)/boot/initrd.img

That should at least get us pointed in the right direction.

-Tim

Reply With Quote
Reply

Viewing: Codewalkers ForumsOther TechnologiesServer Administration > Kernel problems


Thread Tools  Search this Thread 
Search this Thread:

Advanced Search
Display Modes  Rate This Thread 
Rate This Thread:


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
View Your Warnings | New Posts | Latest News | Latest Threads | Shoutbox
Forum Jump


Forums: » Register « |  User CP |  Games |  Calendar |  Members |  FAQs |  Sitemap |  Support | 
  
 





© 2003-2008 by Developer Shed. All rights reserved. DS Cluster 4 hosted by Hostway