Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 24 Jan 2003 15:22:50 +1100 (EST)
From:      Bruce Evans <bde@zeta.org.au>
To:        Walter Jontofsohn <wjontofs@berkom.de>
Cc:        freebsd-hardware@freebsd.org
Subject:   Re: can't boot/install freebsd from cdrom/floppy - serverworks g
Message-ID:  <20030124150506.P4290-100000@gamplex.bde.org>
In-Reply-To: <200301231758.02390.wjontofs@berkom.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 23 Jan 2003, Walter Jontofsohn wrote:

> > On Mon, 13 Jan 2003, John Baldwin wrote:
> > > On 13-Jan-2003 Walter wrote:
> > > > i've problems installing freebsd on System with ServerWorks GC SL
> > > > -Chipset, Pentium 4, LSI Logic MPT (53c1030) SCSI-Controller
> > > >
> > > > Booting with floppy kern.flp from 4.7-release, not even the bootstrap
> > > > loader works, then i tried from 5.0rc3 - i got
> > > >
> > > > fatal trap 10: trace trap while in vm86 mode
> > > > instruction pointer=0xf000:0xf842
> > > > stack pointer  = 0x0:0xff8
> > > > frame pointer  = 0x0:0x0
> > > > code segment   = base 0x0, linit 0x0, type 0x0
> > > >                        = DPL 0, pres 0, def32 0, gran 0
> > > > processor eflags = interupt enabled, vm86 IOPL = 0
> > > > current process        = 0 ()
> > > > trap number   = 10
> > > > panic: trace trap
> > > > Uptime: 1s
> > > >
> > > > I thought probably  a hardware failure,
> > > >  but i tried to install Linux Redhat 8.0, without problems ?!
> > > >
> > > > Any hints ?
> >
> > Try setting hw.hasbrokenint12 in the loader.
>
> this means 'set hw.hasbrokenint12' ? if yes, the  result is unfortunately the
> same as above, if no, how should i do this ?

Er, set it to 1?  I'm not sure what the loader does for null set commands
since I don't use it myself, but I guess it would set the variable to "" if
anything.  The kernel would then misparse "" as the number 0 (boolean false),
so thenull set command would have no effect except possubly to turn off any
previous setting.

> Further down you write, that the loader doesen't get the correct memsize, is

This doesn't seem to be in the quoted mail and I don't remember saying it in
this thread.

> it possible/useful to hand over the memory size (or is this for vm86
> special?)

One possible fix is doing it all in the loader.  I prefer to do it only in
the kernel, since vm86 calls need to work for other reasons.

Bruce


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030124150506.P4290-100000>