Matthew Dillon wrote:
Crashes as in seg faults in init?
Are you getting any console errors or warnings at all?
Crashes as in "rcorder segfaults". I had written it some mails earlier.
Here's the output I get:
start_init: trying /sbin/init
pid 4 (rcorder), uid 0: exited on signal 11
Segmentation fault
pid 5 (sysctl), uid 0: exited on signal 11
Segmentation fault
pid 6 (rcorder), uid 0: exited on signal 11
Segmentation fault
Sat Jun 2 23:52:08 CEST 2007
Jun 2 23:52:08 init: can't exec getty '/usr/libexec/getty' for port
/dev/ttyv0: No such file or directory
Jun 2 23:52:08 init: can't exec getty '/usr/libexec/getty' for port
/dev/ttyv1: No such file or directory
Jun 2 23:52:08 init: can't exec getty '/usr/libexec/getty' for port
/dev/ttyv2: No such file or directory
Jun 2 23:52:08 init: can't exec getty '/usr/libexec/getty' for port
/dev/ttyv3: No such file or directory
Jun 2 23:52:08 init: can't exec getty '/usr/libexec/getty' for port
/dev/ttyv4: No such file or directory
Jun 2 23:52:08 init: can't exec getty '/usr/libexec/getty' for port
/dev/ttyv5: No such file or directory
Jun 2 23:52:08 init: can't exec getty '/usr/libexec/getty' for port
/dev/ttyv6: No such file or directory
Jun 2 23:52:08 init: can't exec getty '/usr/libexec/getty' for port
/dev/ttyv7: No such file or directory
See if you can boot into single user mode and natacontrol ad0 to
PIO4 mode or something like that.
When I boot into single user mode, /bin/sh will segfault.
I'll burn a NATA LiveCD later and check out if I can access my hard disk
from it.
Sascha
--
http://yoyodyne.ath.cx
