Ok, problem solved...
Thanx for your notes, it helped a lot.
For thse who may wonder, I simply changed 2 parameters :
hw.pci.enable_io_modes
Enable PCI resources which are left off by some BIOSes or
are not enabled correctly by the device driver. Tunable
value set to ON (1) by default, but this may cause problems
with some peripherals.
hw.pci_allow_unsupported_io_range
Allow the PCI bridge to pass through an unsupported memory
range assigned by the BIOS. Tunable value set to OFF (0)
by default.
can't say exactly which one prevented me from crash (surely 1st one but
didn't tried any further). Dunno if it would be possible to prevent such
things to happen by simply test it, I guess testing it will crash the whole
system too.
Thanx all btw, I learn, I learn :o)
----- Original Message -----
From: "Steve Kargl" <[EMAIL PROTECTED]>
To: "Coercitas Temet'Nosce" <[EMAIL PROTECTED]>
Cc: "Francis Barnhart" <[EMAIL PROTECTED]>; "Kevin Oberman"
<[EMAIL PROTECTED]>; "Nate Lawson" <[EMAIL PROTECTED]>; "FreeBSD current users"
<[EMAIL PROTECTED]>
Sent: Tuesday, January 14, 2003 9:55 PM
Subject: Re: Problem with RC3
> On Tue, Jan 14, 2003 at 09:52:10PM +0100, Coercitas Temet'Nosce wrote:
> >
> > Thanx all for your messages, I think I start to figure how it is
handled.
> > Problem still exists, system still hangs at "agp0: <Ali Generic host to
PCI
> > bridge> mem 0xf0000000-0xf3ffffff at device 0.0 on pci0" but I think it
is
> > in this way I may find a solution. Is there by chance anyway to see what
> > will be load or not simply hitting SPACEBAR at prompt ? I didn't find
any
> > place where it is discussed nor a way to see the "set" variables that
will
> > be used to boot.
> >
>
> lsdev and lsmod show the devices that can be loaded and
> the deviced currently loaded, respectively.
>
> --
> Steve
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
