[S.u.S.E. Linux] HD/SCSI Problem Under SuSE 5.2 - Need Help
I need help so please excuse the verbose info. My system has the following hardware and problems: Linux only sytem. ASUS P55T2P4 Rev 3. w/Intel 200MMX & 128megs EDO 60ns AHA2940UW -> Seagate Barracuda 4.1gig SCSI2 (1st in 50pin chain) Here's the boot.msg info: --------------------------------------------------------------------------- 6>aic7xxx: in the Adaptec SCSI BIOS by hitting CTRL-A when prompted <6>aic7xxx: during machine bootup. <6>aic7xxx: Cables present (Int-50 YES, Int-68 NO, Ext-68 NO) <6>aic7xxx: Termination (Low ON, High ON) <6>(scsi0) <Adaptec AHA-294X Ultra SCSI host adapter> found at PCI 10/0 <6>(scsi0) Wide Channel, SCSI ID=7, 16/255 SCBs <6>(scsi0) BIOS enabled, IO Port 0xe000, IO Mem 0xe6000000, IRQ 10 <6>(scsi0) Resetting channel <6>(scsi0) Downloading sequencer code... 413 instructions downloaded <4>scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.0.7/3.2.2 <4> <Adaptec AHA-294X Ultra SCSI host adapter> <4>scsi : 1 host. <6>(scsi0:0:-1:-1) Scanning channel for devices. <6>(scsi0:0:0:0) Using narrow (8 bit) transfers. <6>(scsi0:0:0:0) Synchronous at 10.0MHz, offset 15. <4> Vendor: SEAGATE Model: ST15150N Rev: 0023 <4> Type: Direct-Access ANSI SCSI revision: 02 <4>Detected scsi disk sda at scsi0, channel 0, id 0, lun 0 <6>(scsi0:0:3:0) Using narrow (8 bit) transfers. <6>(scsi0:0:3:0) Synchronous at 10.0MHz, offset 15. <4> Vendor: PLEXTOR Model: CD-ROM PX-20TS Rev: 1.01 <4> Type: CD-ROM ANSI SCSI revision: 02 <4>Detected scsi CD-ROM sr0 at scsi0, channel 0, id 3, lun 0 <6>(scsi0:0:4:0) Refusing WIDE negotiation; using 8 bit transfers. <6>(scsi0:0:4:0) Synchronous at 5.0MHz, offset 15. <4> Vendor: SONY Model: CD-ROM CDU-76S Rev: 1.2d <4> Type: CD-ROM ANSI SCSI revision: 02 <4>Detected scsi CD-ROM sr1 at scsi0, channel 0, id 4, lun 0 <4>scsi : detected 2 SCSI cdroms 1 SCSI disk total. <4>SCSI device sda: hdwr sector= 512 bytes. Sectors= 8388315 [4095 MB] [4.1 GB] ---------------------------------------------------------------------------------- I am unable to boot the system all of a sudden and get kernel panics with *any* kernel when using lilo. Yet, with a freashly compiled monolithic kernel ( linux -> linux-2.0.33.SuSE), it boots fine. No disk errors on boot up. It is fresh install of 5.2. What's wrong that lilo and the same kernel as the one on the floppy won't boot off the hardrive ? Please help. -Dee -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
At 04:36 PM 98-05-26 -0800, Dee wrote:
I need help so please excuse the verbose info. My system has the following hardware and problems:
Linux only sytem. ASUS P55T2P4 Rev 3. w/Intel 200MMX & 128megs EDO 60ns AHA2940UW -> Seagate Barracuda 4.1gig SCSI2 (1st in 50pin chain)
I am unable to boot the system all of a sudden and get kernel panics with *any* kernel when using lilo. Yet, with a freashly compiled monolithic kernel ( linux -> linux-2.0.33.SuSE), it boots fine.
No disk errors on boot up. It is fresh install of 5.2. What's wrong that
... stuff deleted ... lilo
and the same kernel as the one on the floppy won't boot off the hardrive ?
Please help.
-Dee
I am not sure what it is you are trying to do. I guess you have reinstalled Lilo with image map for the new kernel since you can boot fine with it. I suggest that you choose the upgrade option in YaST to upgrade to 5.2. Unless you wish to do a fresh install of 5.2. In such case, you might want to try a new boot kernel for aic78xx. One of the SuSE engineers had posted a message that a new boot image with the latest aic78xx drivers is available on the SuSE ftp site. Perhaps that would help with a fresh 5.2 installation. Good luck. -- Arun Khan -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
W.D.McKinney wrote: ...
I am unable to boot the system all of a sudden and get kernel panics with *any* kernel when using lilo. Yet, with a freashly compiled monolithic kernel ( linux -> linux-2.0.33.SuSE), it boots fine.
No disk errors on boot up. It is fresh install of 5.2. What's wrong that lilo and the same kernel as the one on the floppy won't boot off the hardrive ? ...
I don't know for sure, but I think the floppy kernel runs the aic driver as a module. That works fine from floppy, since the floppy filesystem type is built as a kernel driver. The module driver can easily be loaded from the floppy and the whole thing works fine. If You put it onto Your harddisk, the module aic has to be loaded from the harddisk, but there's no driver present to do that. The recommended solution is to build a fresh kernel with the aic compiled into the kernel. If I'm wrong, please correct me. I'm searching for wisdom ;^) Regards, Matthias -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hello and thanks for helping....
Well let me re-iterate. I loaded up a fresh copy of 5.2 on the hardrive,
grabbed a copy of the latest kernel from ftp.suse.com and when I try to boot
off the hardrive I get this boot-up-message:
-------------------------------------------------------------
Calibrating delay loop.. ok - 398.95 BogoMIPS
Memory: 0k/0k Available (0k kernel code, 0k reserved, 0k data)
Kernel Panic; Failed to allocate buffer hash table
In swapper task - not syncing
------------------------------------------------------------
But booting the same kernel off a floppy....:
---------------------------------------------------------------
<4>Probing PCI hardware.
<4>Calibrating delay loop.. ok - 398.95 BogoMIPS
<4>Memory: 127784k/131072k available (768k kernel code, 384k reserved, 2136k data)
-----------------------------------------------------------------
And it boots fine with the floppy . Is this a lage hard disk error now ?
I have the same disk I had before and it worked fine in the past ?
Sure do appreciate the responses but still need help.
-Dee
Matthias Morche
W.D.McKinney wrote: ...
I am unable to boot the system all of a sudden and get kernel panics with *any* kernel when using lilo. Yet, with a freshly compiled monolithic kernel ( linux -> linux-2.0.33.SuSE), it boots fine.
No disk errors on boot up. It is fresh install of 5.2. What's wrong that lilo and the same kernel as the one on the floppy won't boot off the hardrive ? ...
I don't know for sure, but I think the floppy kernel runs the aic driver as a module. That works fine from floppy, since the floppy filesystem type is built as a kernel driver. The module driver can easily be loaded from the floppy and the whole thing works fine. If You put it onto Your harddisk, the module aic has to be loaded from the harddisk, but there's no driver present to do that. The recommended solution is to build a fresh kernel with the aic compiled into the kernel.
If I'm wrong, please correct me. I'm searching for wisdom ;^)
Regards, Matthias -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Well, check the obvious first. Boot off your floppy, run /sbin/lilo and try rebooting off the hard drive. Hope it's that simple. W.D.McKinney wrote:
Hello and thanks for helping.... Well let me re-iterate. I loaded up a fresh copy of 5.2 on the hardrive, grabbed a copy of the latest kernel from ftp.suse.com and when I try to boot off the hardrive I get this boot-up-message:
------------------------------------------------------------- Calibrating delay loop.. ok - 398.95 BogoMIPS Memory: 0k/0k Available (0k kernel code, 0k reserved, 0k data) Kernel Panic; Failed to allocate buffer hash table
In swapper task - not syncing ------------------------------------------------------------
But booting the same kernel off a floppy....:
--------------------------------------------------------------- <4>Probing PCI hardware. <4>Calibrating delay loop.. ok - 398.95 BogoMIPS <4>Memory: 127784k/131072k available (768k kernel code, 384k reserved, 2136k data) -----------------------------------------------------------------
And it boots fine with the floppy . Is this a lage hard disk error now ? I have the same disk I had before and it worked fine in the past ?
Sure do appreciate the responses but still need help. -Dee
Matthias Morche
wrote:
-- _____ .-'WWWWW'L. WindowMaker.... .'WWWWWWWWWWWW.__ /WWWWWWW| \W| The choice of ;WWWWWWWW| ;| a GNU generation. |WWWWWWWW| || ;WWW| ;| ===================================== \WW| /W| |Michael Lankton, satan@nfinity.com | __'W| .'WW| | University of Nebraska-Omaha CIST | |WWWWW-._____._WWWWW| ===================================== -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Michael Lankton
Well, check the obvious first. Boot off your floppy, run /sbin/lilo and try rebooting off the hard drive. Hope it's that simple.
W.D.McKinney wrote:
Hi Michael, Yes, I've tried running lilo and it shows linux* with no problems but the same error on booting of the hard-drive. Any other ideas ? Thanks -Dee -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Ok, /me crosses my fingers, one more obvious thing to check would be to fire up fdisk and make sure the / partition has the bootable toggle on (option "a" in linux fdisk, and I'm not sure if that would cause that behaviour, but check it anyway). If that isn't the problem let me get this straight, booting off the hard drive makes it past lilo into the boot process, where was it locking? W.D.McKinney wrote:
Hi Michael,
Yes, I've tried running lilo and it shows linux* with no problems but the same error on booting of the hard-drive. Any other ideas ?
Thanks
-Dee
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
-- _____ .-'WWWWW'L. WindowMaker.... .'WWWWWWWWWWWW.__ /WWWWWWW| \W| The choice of ;WWWWWWWW| ;| a GNU generation. |WWWWWWWW| || ;WWW| ;| ===================================== \WW| /W| |Michael Lankton, satan@nfinity.com | __'W| .'WW| | University of Nebraska-Omaha CIST | |WWWWW-._____._WWWWW| ===================================== -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
At 07:47 PM 98-05-27 +0200, Matthias wrote:
... stuff deleted ...
I don't know for sure, but I think the floppy kernel runs the aic driver as a module. That works fine from floppy, since the floppy filesystem type is built as a kernel driver. The module driver can easily be loaded from the floppy and the whole thing works fine. If You put it onto Your harddisk, the module aic has to be loaded from the harddisk, but there's no driver present to do that. The recommended solution is to build a fresh kernel with the aic compiled into the kernel.
If I'm wrong, please correct me. I'm searching for wisdom ;^)
Regards, Matthias
Matthias, Regarding loadable modules for SCSI, I have not experienced the problem with NCR/Symbios (NCR8xx chip set) SCSI cards. Although, in most cases I do compile a custom kernel with the NCR8xxx drivers non-modularized. -- Arun Khan -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Arun K. Khan wrote: ...
Matthias,
Regarding loadable modules for SCSI, I have not experienced the problem with NCR/Symbios (NCR8xx chip set) SCSI cards. Although, in most cases I do compile a custom kernel with the NCR8xxx drivers non-modularized. ...
Maybe the ncr driver is compiled into the kernel on the floppy. I'm not clever enough to imagine for what reason the aic is not :-) Matthias -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
participants (4)
-
arunkhan@xnet.com
-
deem@wdm.com
-
morche@sat1.de
-
satan@nfinity.com