| Jeff Abrahamson on 29 Jul 2005 01:28:49 -0000 |
|
On Wed, Jul 27, 2005 at 10:12:17PM -0700, Carlos Konstanski wrote:
> [92 lines, 549 words, 3556 characters] Top characters: erntosia
>
> I dealt with this kind of thing before once, where we got 5 new
> boxes that were not our usual build. We had to use "nolapic" in the
> kernel boot arguments. These were single-processor machines. I
> forget which CPU and motherboard they were, but I think the boards
> were Asus.
>
> With "nolapic" specified, these machines have been reliable, one
> even running as a qa server for a huge tomcat app.
Just to make sure I understand, this means booting where I type "Linux
nolapic" at the boot prompt and if it all works I add a line to
/etc/lilo.conf so that it looks like this:
image=/vmlinuz
label=Linux
read-only
# restricted
# alias=1
initrd=/initrd.img
append = "nolapic"
--
Jeff
Jeff Abrahamson <http://www.purple.com/jeff/> +1 215/837-2287
GPG fingerprint: 1A1A BA95 D082 A558 A276 63C6 16BF 8C4C 0D1D AE4B
Attachment:
signature.asc ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|