On Fri, Sep 01, 2000 at 03:33:34PM -0700, Matthew Jacob wrote:
>
>
>
> > mcclock isn't at 112 on the alpha.
>
> Oops (*blush*).. these are decimal...
Maybe a stupid question, but why are these values reported in decimal in the
first place?
> > > > Maybe. It's also not clear to me whether &m
Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, John Baldwin writes:
> >Poul-Henning Kamp wrote:
> >>
> >> If I boot this machine on a -current kernel, it doesn't find the
> >> fxp#'s at all:
> >
> >Do you have Peter's latest commits to pci/pci.c pci/pcisupport.c and
> >i386/isa/pcibus
In message <[EMAIL PROTECTED]>, John Baldwin writes:
>Poul-Henning Kamp wrote:
>>
>> If I boot this machine on a -current kernel, it doesn't find the
>> fxp#'s at all:
>
>Do you have Peter's latest commits to pci/pci.c pci/pcisupport.c and
>i386/isa/pcibus.c? Without that, mulitple PCI busses is
> > Maybe. It's also not clear to me whether &my& current breakage is PCI related
> > or device.hints related (it appears that the read of my /boot/devices.hints
> > file gets things garbled):
>
> If you want a working vidconsole on the alpha, compile your hints statically
> into the kernel. :)
Matthew Jacob wrote:
>
> Maybe. It's also not clear to me whether &my& current breakage is PCI related
> or device.hints related (it appears that the read of my /boot/devices.hints
> file gets things garbled):
If you want a working vidconsole on the alpha, compile your hints statically
into the
Poul-Henning Kamp wrote:
>
> If I boot this machine on a -current kernel, it doesn't find the
> fxp#'s at all:
Do you have Peter's latest commits to pci/pci.c pci/pcisupport.c and
i386/isa/pcibus.c? Without that, mulitple PCI busses is b0rked on i386.
--
John Baldwin <[EMAIL PROTECTED]> -- h
> mcclock isn't at 112 on the alpha.
Oops (*blush*).. these are decimal...
>
> > >
> > > Maybe. It's also not clear to me whether &my& current breakage is PCI related
> > > or device.hints related (it appears that the read of my /boot/devices.hints
> > > file gets things garbled):
> >
> >
mcclock isn't at 112 on the alpha.
> >
> > Maybe. It's also not clear to me whether &my& current breakage is PCI related
> > or device.hints related (it appears that the read of my /boot/devices.hints
> > file gets things garbled):
>
> What makes you say that? This all looks fine to me. (The
>
> Maybe. It's also not clear to me whether &my& current breakage is PCI related
> or device.hints related (it appears that the read of my /boot/devices.hints
> file gets things garbled):
What makes you say that? This all looks fine to me. (The hang is not so
good though...)
> Hit [Enter] t
Maybe. It's also not clear to me whether &my& current breakage is PCI related
or device.hints related (it appears that the read of my /boot/devices.hints
file gets things garbled):
Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [kernel]...
Entering k
If I boot this machine on a -current kernel, it doesn't find the
fxp#'s at all:
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD CC28 #0: Mon Aug 28 16:30:18 GMT 2000
[EMAIL PROTECTE
11 matches
Mail list logo