On Friday, February 26, 2016 11:08:37 PM Warner Losh wrote:
> On Fri, Feb 26, 2016 at 6:49 PM, Marcel Moolenaar wrote:
>
> Any reason not to add .disabled=1 to all the entries that are there,
> with the possible exception of uart.0? At least for i386 and amd64?
> Bonus points for writing code tha
ist to send
> to.
> >
> > On Intel Atom X5-Z8300 SoC (CherryTrail) the install memstick image
> (amd64)
> > halts during boot because of uart.1 settings in device hints.
>
> I have found that FreeBSD’s default device.hints file has fallen
> behind on reality and is indeed caus
f uart.1 settings in device hints.
I have found that FreeBSD’s default device.hints file has fallen
behind on reality and is indeed causing problems on more modern
H/W, like the H/W you mention.
>
> I'm sure it is there for a reason so what is the alternative actions? Is
> the solu
Yes. Doing that or removing it from device.hints and it will boot properly.
I haven't really dug any deeper as to why, yet.
On Fri, Feb 26, 2016 at 9:56 AM, Ian Lepore wrote:
> On Fri, 2016-02-26 at 09:48 -0600, Lundberg, Johannes wrote:
> > Hi
> >
> > Not sure if i
of uart.1 settings in device hints.
>
> I'm sure it is there for a reason so what is the alternative actions?
> Is
> the solution to get a bootable Atom SoC image to create yet another
> distribution or can the installer choose the proper device.hints
> dynamically during boot?
actions? Is
the solution to get a bootable Atom SoC image to create yet another
distribution or can the installer choose the proper device.hints
dynamically during boot?
Best regards
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
秘密保持について：この電子メールは、名宛人に送信したものであり、秘匿特権の対象となる情報を含んでいます。
もし、名宛人
; >> hw.machine_arch: amd64
> >> Radeon HD 6320
> >>
> >> This kernel was launched in FreeBSD 10 Beta 4 (build 10 PCBSD
> >> -Stable http://iso.cdn.pcbsd.org/10-STABLE/amd64/)
> >>
> >> Everything is working fine .
> >
D Graphics
> hw.ncpu: 2
> hw.machine_arch: amd64
> Radeon HD 6320
>
> This kernel was launched in FreeBSD 10 Beta 4 (build 10 PCBSD -Stable
> http://iso.cdn.pcbsd.org/10-STABLE/amd64/)
>
> Everything is working fine .
> I have one question : Is it possible to ins
Hello, Lev.
You wrote 10 августа 2013 г., 15:01:57:
LS> Hello, Current.
LS> I've make simple mistake (DOS-style EOL) in /boot/device.hints and
LS> /boot/loader.conf was skipped too with strange (device.hints-related)
LS> message:
LS> FreeBSD/x86 bootstrap loader, Revision
Hello, Current.
I've make simple mistake (DOS-style EOL) in /boot/device.hints and
/boot/loader.conf was skipped too with strange (device.hints-related)
message:
FreeBSD/x86 bootstrap loader, Revision 1.1
(r...@fbsd-c-64.vm.home.serebryakov.spb.ru, Sat Aug 10 14:02:41 MSK 2013)
Loading
for the irq etc. but no
> way to put something in polled mode or to find an info on it.
>
> It's a "lack" of device.hints(5) and some devices manual pages :)
If you set bit 5 of ppc(4) 'flags' lpt will do polling. But lptcontrol
won't change it anymore.
N
On Mon, Nov 25, 2002 at 10:32:46PM +1100, Bruce Evans wrote:
[...]
>
> "lptcontrol -i" and "lptcontrol -p" work for me under -current. They
> presumably work because the driver sets up the interrupt for every
> write(2) if interrupts are enabled. This used to cause panics because
> a thread was
On Mon, 25 Nov 2002, Marc Fonvieille wrote:
[polled mode for sio0 and ppc0]
> But what about ppc0 ? I have to remove the IRQ line as well?
> (sorry I can't test now)
I don't know exactly (I rarely use it).
> I also noted that lptcontrol(8) "does not" work under 4.X and 5.X.
> It seems that sin
On Mon, Nov 25, 2002 at 05:37:49PM +1100, Bruce Evans wrote:
> For sio, polled mode is configured by not creating an irq resource.
> Leave the irq out of the device line in the config file for RELENG_4,
> and don''t configure a hint for the irq in 5.x. This might not actually
> work since PNP or A
but no
> way to put something in polled mode or to find an info on it.
>
> It's a "lack" of device.hints(5) and some devices manual pages :)
For sio, polled mode is configured by not creating an irq resource.
Leave the irq out of the device line in the config file for RELENG
t's a "lack" of device.hints(5) and some devices manual pages :)
Marc
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Mon, Aug 26, 2002 at 11:18:36AM +1000, Bruce Evans wrote:
>
> It seems to be proper for disabling acpi itself (see dev/acpica/acpi.c)
> but not its loading. So to fully disable acpica, you have to do something
> like:
>
> hint.acpi.0.disable="I prefer not to use code that (mis)uses !gete
On Sun, 25 Aug 2002, David O'Brien wrote:
> On Sun, Aug 25, 2002 at 12:43:44PM -0400, Mike Barcroft wrote:
> > Craig Rodrigues <[EMAIL PROTECTED]> writes:
> > > device.hints.5:
> > > $FreeBSD: src/share/man/man5/device.hints.5,v 1.3 2002/08/09 06:07:3
> The following example disables the ACPI driver
>
>hint.acpi.0.disable="1"
My man page doest have this example (but is is some days older), but a
look to
Twoflower# grep "disable" /sys/i386/conf/GENERIC.hints
hint.apm.0.disabled="1"
hint.pcic.1.disabled="1"
hint.sio.2.disa
David O'Brien <[EMAIL PROTECTED]> writes:
> On Sun, Aug 25, 2002 at 12:43:44PM -0400, Mike Barcroft wrote:
> > Craig Rodrigues <[EMAIL PROTECTED]> writes:
> > > device.hints.5:
> > > $FreeBSD: src/share/man/man5/device.hints.5,v 1.3 2002/08/09 0
On Sun, Aug 25, 2002 at 12:54:01PM -0400, Craig Rodrigues wrote:
> On Sun, Aug 25, 2002 at 05:49:38PM +0200, Jan Stocker wrote:
> >
> > > The following example disables the ACPI driver
> > >hint.acpi.0.disable="1"
> >
> > My man page doest have this example (but is is some days
On Sun, Aug 25, 2002 at 12:43:44PM -0400, Mike Barcroft wrote:
> Craig Rodrigues <[EMAIL PROTECTED]> writes:
> > device.hints.5:
> > $FreeBSD: src/share/man/man5/device.hints.5,v 1.3 2002/08/09 06:07:33 obrien
>Exp $
> > I would like to subm
Craig Rodrigues <[EMAIL PROTECTED]> writes:
> device.hints.5:
> $FreeBSD: src/share/man/man5/device.hints.5,v 1.3 2002/08/09 06:07:33 obrien
>Exp $
>
>
> I would like to submit the following trivial patch:
>
>
> --- device.hints.5.orig Sun Aug 25 1
> Twoflower# grep "disable" /sys/i386/conf/GENERIC.hints
>
> hint.apm.0.disabled="1"
> hint.pcic.1.disabled="1"
> hint.sio.2.disabled="1"
> hint.sio.3.disabled="1"
>
> shows that the description is right and the e
Hi,
Running: 5.0-CURRENT-20020818-JPSNAP
I am reading the man page for device.hints, and I think I see an
inconsistency:
=
A device hint line looks like:
hint.driver.unit.keyword="value"
Is it possible to make devices enumerated by acpi to take notice of the
flags given to them in device.hints?
for example if I allow acpi then I get:
sio0 port 0x3f8-0x3ff irq 4 on acpi0
sio0: type 16550A, console
sio1 port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
despite the fact that I
Is it possible to make devices enumerated by acpi to take notice of the
flags given to them in device.hints?
for example if I allow acpi then I get:
sio0 port 0x3f8-0x3ff irq 4 on acpi0
sio0: type 16550A, console
sio1 port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
despite the fact that I
th recent "duplicate make_dev panics" commit.
> >
> > It looks like conflict with /boot/device.hints here.
> > If I remove this line
> > hint.sc.0.at="isa"
> > from device.hints, no fake second VGA appearse (the bug is gone), BUT...
> > I h
sing sc1 instead
> vga-: vga0 already exists, using vga1 instead
>
> vga-: line is especially dangerous since cause fake second VGA detection
> (as MDA) which cause panic with recent "duplicate make_dev panics" commit.
>
> It looks like conflict with /boot/device.hints here.
detection
(as MDA) which cause panic with recent "duplicate make_dev panics" commit.
It looks like conflict with /boot/device.hints here.
If I remove this line
hint.sc.0.at="isa"
from device.hints, no fake second VGA appearse (the bug is gone), BUT...
I have absolutely NO console o
I am writing a man page for the /boot/device.hints file.
My understanding is that /boot/device.hints is for
describing resources for devices, and /boot/loader.conf is for
loader variables and kernel tunable parameters.
(The loader.conf file, the loader variables, and the kernel
tunable
On Tue, Jul 24, 2001 at 12:51:39PM -0800, Beech Rintoul wrote:
> > I want to experiment with current. All went well on the build, but when I
> > try and install the kernel it stops telling me to install a "device.hints"
You should have also read UPDATING. Please start a
On Tuesday 24 July 2001 11:23 am, Beech Rintoul wrote:
> I want to experiment with current. All went well on the build, but when I
> try and install the kernel it stops telling me to install a "device.hints"
> file. What do I need to do? I tried re-compiling the kernel with
On Tue, Jul 24, 2001 at 11:23:16AM -0800, Beech Rintoul wrote:
> I want to experiment with current. All went well on the build, but when I try
> and install the kernel it stops telling me to install a "device.hints" file.
> What do I need to do? I tried re-compiling the kern
On Tue, Jul 24, 2001 at 11:23:16AM -0800, Beech Rintoul wrote:
> I want to experiment with current. All went well on the build, but when I try
> and install the kernel it stops telling me to install a "device.hints" file.
> What do I need to do? I tried re-compiling the kern
On Tue, 24 Jul 2001, Beech Rintoul wrote:
> I want to experiment with current. All went well on the build, but when I try
> and install the kernel it stops telling me to install a "device.hints" file.
> What do I need to do? I tried re-compiling the kernel with the "s
I want to experiment with current. All went well on the build, but when I try
and install the kernel it stops telling me to install a "device.hints" file.
What do I need to do? I tried re-compiling the kernel with the "static" line
uncomented, but same problem on i
Hello,
I have been playing with PnP and device hints. Using a device.hints
with hints for all the drivers, some " can't assing resources"
messages showed up at boot. Then I removed hints one by one, until
I ended up with these:
hint.fd.0.at="fdc0"
hint.fd.0.drive=&q
On Fri, 2001-02-02 at 11:35:21, Graham Wheeler wrote:
[cut]
> I don't see anything in the manpages or archives about this. Can someone
> please enlighten me as to what this file should be?
Try /usr/src/UPDATING
--
Karol Makowski
Market Internetowy Click And Buy sp z o.o.
http://www.buy.pl
GSM
Graham Wheeler wrote:
> When trying to compile the kernel, I get an error saying I should
> install a /boot/device.hints file first.
See the /usr/src/UPDATING file:
2825:
/boot/device.hints is now required for installkernel to
succeed. You should copy GENERIC.hints fo
/boot/device.hints file first.
I don't see anything in the manpages or archives about this. Can someone
please enlighten me as to what this file should be?
TIA
gram
--
Dr Graham WheelerE-mail: [EMAIL PROTECTED]
Director, Research and Development WWW:http://www.c
In message <[EMAIL PROTECTED]> "David O'Brien" writes:
: See /usr/src/UPDATING. If you don't find the answer there, update your
: 'UPDATING'.
Or update the UPDATING maintainer as to what updates to UPDATING are
needed for your to update.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
w
>
> > [root@calloc:/usr/src/sys/compile/CALLOC]# make install
> > You must activate /boot/device.hints in loader.conf.
> > *** Error code 1
> >
> > How do i activate it?
>
> See /usr/src/UPDATING. If you don't find the answer there, update your
>
On Wed, Aug 30, 2000 at 11:49:25AM +, Justin Ovens [[EMAIL PROTECTED]] wrote:
> I have a little Q: when i compile my kernel for 5.0-CURRENT
>
> [root@calloc:/usr/src/sys/compile/CALLOC]# make install
> You must activate /boot/device.hints in loader.conf.
> *** Error code
I have a little Q: when i compile my kernel for 5.0-CURRENT
[root@calloc:/usr/src/sys/compile/CALLOC]# make install
You must activate /boot/device.hints in loader.conf.
*** Error code 1
How do i activate it?
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Justin Ovens
45 matches
Mail list logo
