Re: i386 boot failure

2003-01-17 Thread Mark Murray
 I've recently been trying to bring a system of mine (4.7-R) up-to-date
 with -CURRENT by following the dotted lines in UPDATING;  basically,
 everything up through 'make installkernel' and the 'make install' from
 /usr/src/sys/boot has gone fine;  I reboot into loader(8) and 'boot -s',
 but literally just after printing its I just loaded acpi.ko message the
 system just hangs at a twiddle-prompt, forever stilled.  Well, not quite:
 the keyboard lights blink once and the hard drives click, but no further
 response.  This isn't an ACPI problem;  I've unset acpi_load, and the only
 difference is that the system spins for half a second longer before dying.
 loader claims to have preloaded the (new) kernel already.

[ snip ]

 # Pseudo devices - the number indicates how many units to allocate.device
 random  # Entropy device

This looks funny. What happens if you load the random device?

M
--
Mark Murray
iumop ap!sdn w,I idlaH

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: i386 boot failure

2003-01-17 Thread John McCall
On Fri, 17 Jan 2003, Mark Murray wrote:
  I've recently been trying to bring a system of mine (4.7-R) up-to-date
  with -CURRENT by following the dotted lines in UPDATING;  basically,
  everything up through 'make installkernel' and the 'make install' from
  /usr/src/sys/boot has gone fine;  I reboot into loader(8) and 'boot -s',
  but literally just after printing its I just loaded acpi.ko message the
  system just hangs at a twiddle-prompt, forever stilled.  Well, not quite:
  the keyboard lights blink once and the hard drives click, but no further
  response.  This isn't an ACPI problem;  I've unset acpi_load, and the only
  difference is that the system spins for half a second longer before dying.
  loader claims to have preloaded the (new) kernel already.

 [ snip ]

  # Pseudo devices - the number indicates how many units to allocate.device  
 random  # Entropy device

 This looks funny. What happens if you load the random device?

Ack, sorry.  That's a snipping artifact;  the actual conf file has these
as two separate lines, and random.ko is in fact present in /boot/kernel/.

John.
-- 
évana roì, séana coì, reìja venacoì u vëja haman.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message