|
Home > Archive > alt.os.linux > July 2002 > Booting New Kernel Problem (First Timer)
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Booting New Kernel Problem (First Timer)
|
|
| Lifeless Bodoh 2002-07-21, 8:25 pm |
| Hi,
I desperately need a lot of help for this one.
Distribution: Redhat 6.2
Laptop: Toshiba 2520 CDT
New Kernel: 2.4.9-13 (previously, it was 2.2.14)
When I boot up my new kernel, I got some very strange errors:
I have no idea on what are "SeekComplete Errors" and "BadCRC"
....
==
/* Repetition of 4 times for this error */
hda: dma_initr: status=0x51 { DriverReady SeekComplete Errors }
hda: dma_initr: eror=0x84 { DriverStatusErro BadCRC }
ide0: unexpected interrupt, status =0x80, count=1
ide0: reset: success
INIT: version 2.78 booting
/* Welcome message ... until file system check */
Check root filesystem
/dev/hda2 is mounted. e2fsck: Cannot continue, aborting.
[failed]
*** An error occured during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
Give root password for maintenance
(or type Control-D for normal setup):
==
Seeing that /dev/hda2 (where I install my Linux) is mounted,
I umounted it and run e2fsck on it. But the annoying thing as
mentioned in the error message is once I leave this shell,
the system will get rebooted. And this becomes an infinite loop
to me!
Arrgghhhh (after waiting for 4 hours of compiling and got this
instead, so please bear with my whinings for a while ...)
Thanks.
| |
| Richard James 2002-07-22, 6:25 am |
| wb wrote:
> These errors indicate that your disk is failing .
> Does it happen with the stardard kernel ?
>
> You may have hardware problems .
Or that the driver the kernel is using to talk to the harddisks is not the
right one or flakey.
Ricahrd 
--
I lost my train of thought, I think it's in a tunnel.
| |
|
| True - That is why I asked if the old (default) kernel
was booting.
//
"Richard James" <thisemailwontwork@all.will.it> wrote in message
news:n5rgha.fal.ln@server.techdrive.foo...
> wb wrote:
>
> > These errors indicate that your disk is failing .
> > Does it happen with the stardard kernel ?
> >
> > You may have hardware problems .
>
> Or that the driver the kernel is using to talk to the harddisks is not the
> right one or flakey.
>
> Ricahrd
>
> --
> I lost my train of thought, I think it's in a tunnel.
| |
| Lifeless Bodoh 2002-07-22, 8:25 am |
|
wb <b24warbaby@yahoo.com> wrote in message
news:xwR_8.4$A06.213090@news.cpqcorp.net...
> These errors indicate that your disk is failing .
> Does it happen with the stardard kernel ?
Hi, I've solved this partially already.
I've accidentally included "initrd= ...." in my lilo.conf (which
means scsi). So what I did was to remove that line and
recompile lilo. After I rebooted and went into my new
kernel, I still got "Seek Complete Errors".
By the way, I'm using a laptop and I still haven't fixed my
pc card yet (which is in another thread named pcmcia) ...
I have tested my new kernel by typing "uname -a" and it
gives me my new kernel version, 2.4.9-13 (previously,
2.2-14). So I have upgraded my kernel-pcmcia to 3.1.24-2
now.
I'm still in the middle of compiling my kernel at this time in
writing... Hopefully nothing goes wrong ...
Thanks for all the replies.
Cheers,
mingshun
| |
| Lifeless Bodoh 2002-07-22, 12:25 pm |
| Hi,
I've recompiled my kernel again after upgrading my pcmcia.
But the bootup gives me a lot of error messages that run
before my eye catches them. It is something like:
PCMIA: PCI: No IRQ unknown for pin ...
I then login as root in my newly installed kernel and read
the /var/log/messages. Here's the snippet:
==
pcmcia: Starting PCMCIA services:
pcmcia: modules
pcmcia: cardmgr
rc: Starting pcmcia: succeeded
cardmgr [618]: starting, version is 3.1.22
cardmgr [618]: watching 2 sockets
cardmgr [618]: initializing socket 0
cardmgr [618]: socket 0: Xircom CBEM56G-100 CardBus ...
cardmgr [618]: executing: 'modprobe cb_enabler'
cardmgr [618]: executing: 'modprobe xircom_cb'
cardmgr [618]: executing: 'modprobe serial_cb'
/* lpd start, not relevant */
cardmgr [618]: + modprobe: Can't locate module serial_cb
cardmgr [618]: modprobe exited with status 255
cardmgr [618]: module /lib/modules/2.4.9-13custom/pcmcia/serial_cb not
available
/* Hmmm ... so should 'make menuconfig' and and find this serial_cb
again??? */
cardmgr [618]: executing: './network start xircom_cb'
cardmgr [618]: executing: './serial start xircom_cb'
/* 3 irrelevant statements in between */
/etc/hotplug/pci.agent: ... no drivers for PCI slot
/etc/hotplug/net.agent: register event not handled
/* loading system font */
cardmgr [618]: + ./MAKEDEV: don't know how to make device "xircom_cb"
==
It takes me no less than 3 hours to compile my kernel because
my laptop is slow.  I have just compiled twice before posting
here. This really drains off my energy ... Hence I think I really
need help from people who have much more experience than me.
Thanks.
| |
| ns@NOSPAM.com 2002-07-23, 2:25 am |
| Try fsck /dev/hda2
when you finish, type reboot
In comp.os.linux.misc Lifeless Bodoh <lukmengs@comp.nus.edu.sg> wrote:
> Hi,
> I desperately need a lot of help for this one.
> Distribution: Redhat 6.2
> Laptop: Toshiba 2520 CDT
> New Kernel: 2.4.9-13 (previously, it was 2.2.14)
> When I boot up my new kernel, I got some very strange errors:
> I have no idea on what are "SeekComplete Errors" and "BadCRC"
> ...
> ==
> /* Repetition of 4 times for this error */
> hda: dma_initr: status=0x51 { DriverReady SeekComplete Errors }
> hda: dma_initr: eror=0x84 { DriverStatusErro BadCRC }
> ide0: unexpected interrupt, status =0x80, count=1
> ide0: reset: success
> INIT: version 2.78 booting
> /* Welcome message ... until file system check */
> Check root filesystem
> /dev/hda2 is mounted. e2fsck: Cannot continue, aborting.
> [failed]
> *** An error occured during the file system check.
> *** Dropping you to a shell; the system will reboot
> *** when you leave the shell.
> Give root password for maintenance
> (or type Control-D for normal setup):
> ==
> Seeing that /dev/hda2 (where I install my Linux) is mounted,
> I umounted it and run e2fsck on it. But the annoying thing as
> mentioned in the error message is once I leave this shell,
> the system will get rebooted. And this becomes an infinite loop
> to me!
> Arrgghhhh (after waiting for 4 hours of compiling and got this
> instead, so please bear with my whinings for a while ...)
> Thanks.
| |
| Nucleon 2002-07-24, 11:25 am |
| On Sun, 21 Jul 2002 15:51:35 -0500, Lifeless Bodoh wrote:
> Hi,
>
> I desperately need a lot of help for this one.
>
> Distribution: Redhat 6.2
> Laptop: Toshiba 2520 CDT
> New Kernel: 2.4.9-13 (previously, it was 2.2.14)
>
> When I boot up my new kernel, I got some very strange errors: I have no
> idea on what are "SeekComplete Errors" and "BadCRC" ...
>
> ==
> /* Repetition of 4 times for this error */ hda: dma_initr: status=0x51 {
> DriverReady SeekComplete Errors } hda: dma_initr: eror=0x84 {
> DriverStatusErro BadCRC }
Sounds like something may be wrong with your drive.
> ide0: unexpected interrupt, status =0x80, count=1 ide0: reset: success
> INIT: version 2.78 booting
>
> /* Welcome message ... until file system check */ Check root filesystem
> /dev/hda2 is mounted. e2fsck: Cannot continue, aborting.
>
> [failed]
make sure the kernel is mounting / read-only, if necessary, at the LILO
prompt, type <what you normally type> root=ro
IIRC
> *** An error occured during the file system check. *** Dropping you to a
> shell; the system will reboot *** when you leave the shell. Give root
> password for maintenance
> (or type Control-D for normal setup): ==
>
> Seeing that /dev/hda2 (where I install my Linux) is mounted, I umounted
> it and run e2fsck on it. But the annoying thing as mentioned in the
do you mean is /dev/hda2 mounted on root, and you mean you remounted it
read-only? If not, /etc/fstab would be helpful to see.
> error message is once I leave this shell, the system will get rebooted.
> And this becomes an infinite loop to me!
Try typing telinit 3 for text logins, telinit 5 for graphical logins.
> Arrgghhhh (after waiting for 4 hours of compiling and got this instead,
> so please bear with my whinings for a while ...)
>
> Thanks.
--
Nucleon
I created the universe, give *me* the gift certificate!
-- Lisa Simpson, Treehouse of Horror VII (4F02)
| |
| Lifeless Bodoh 2002-07-26, 5:25 am |
|
wb <b24warbaby@yahoo.com> wrote in message
news:aQS_8.11$m46.287781@news.cpqcorp.net...
> True - That is why I asked if the old (default) kernel
> was booting.
The old kernel is okay.
Thanks to those who have answered this.
But now, my network card doesn't work. Refer to
the "Need help in irq/io values for Xircom" post for
details. Would try to look into the menuconfig again
after solving this netword card problem.
|
|
|
|
|