Bug#396469: Installation report: failed install on Toshiba Satellite
The machine is hard hung, so I'm not in a debug shell and I can't page up to see what came before the segment fault. Unfortunately, I can't see what was loading before the fault: the very top of the screen is filled up with the register dump and whatnot.
I don't know how to figure out what was running when the seg fault occurred. I don't have a working shell so I can't read any log files, nor can I cat /proc/modules
or ls /dev.
From my Googling it seems like people were trying workarounds that involved directing Linux to boot off of different hard drive controllers (
e.g. changing some path in a configuration file from .../hda1 to .../hda2). I'm not sure exactly how to go about this.
I don't know exactly what disk controller hardware this machine has. However, before I blew away the Windows install I wrote down everything that the Windows device manager told me. I had the following node in the device manager tree:
IDE ATA/ATAPI Controller:
*-----ATA PCI IDE Bus Master
*-----Primary IDE (IRQ 14, I/O 01F0-01F7, 03F6)
*-----Secondary IDE (IRQ 15, I/O 0170-0177, 376)
Thanks for your help. I know a lot about computers, but I know very little about Linux system administration, so I don't know where to begin debugging this.
On 10/31/06, Frans Pop <elendil@planet.nl> wrote:
On Tuesday 31 October 2006 23:23, Bill McNeill wrote:
> Machine: Toshiba Satellite
> Processor: Intel Celeron 2.80 GHz
Strange, I have a quite similar machine which I reinstalled very recently
and which works perfectly (Toshiba Satellite A40, Mobile Pentium 4,
2.8
GHz).
> Comments/Problems:
> I did an install from CD taking all the defaults. When rebooting I get
> a Segmentation Fault followed by the error message
You don't say what causes the segfault. We'll need all the information
that you can see on the screen when it fails to help find the cause.
Can you still scroll upwards after the segfault (using shift-PgUp)? If so,
the lines immediately before the segfault (at least 5 or so) and the
lines of the segfault itself would be interesting to see.
> <6> Journalled Block device driver loaded
> pivot_root: No such file or directory
> /sbin/init: 432: cannot open dev/console: No such file
> Kernel panic: Attempted to kill init!
In general these messages mean that the initrd fails to load the drivers
needed to access the hard disk, OR, if there are multiple disk
controllers in the system, that device names are assigned differently
during the boot than during the installation.
Are you dropped into a debug shell when the failure occurs? If you are,
check if the modules needed are loaded (cat /proc/modules), check if any
disk devices are listed in /dev/.
Cheers,
FJP
--
Bill McNeill
http://staff.washington.edu/billmcn/index.shtml
Reply to: