Date: Wed, 03 May 2000 22:30:47 +0800 From: Trent Nelson <tpnelson@echidna.stu.cowan.edu.au> To: questions@FreeBSD.org Subject: PnP devices being claimed by "unknown" driver. Message-ID: <39103817.3A7045A1@student.cowan.edu.au>
next in thread | raw e-mail | index | archive | help
Following up a previous post that went unanswered, is there any way to suppress the verbosity of the PnP device probing and subsequent claiming that results in this at boot time: unknown0: <PNP0c01> at iomem 0-0x9fbff,0x9fc00-0x9ffff,0xe0000-0xfffff,0x3fe0000-0x3ff7fff,0x3ff8000-0x3ffffff,0xfec00000-0xfec00fff,0xfee00000-0xfee00fff,0xfff80000-0xffffffff on isa0 unknown1: <PNP0c01> at iomem 0x100000-0x3fdffff on isa0 unknown: <PNP0000> can't assign resources unknown2: <PNP0200> at port 0-0xf,0x80-0x90,0x94-0x9f,0xc0-0xde drq 4 on isa0 unknown3: <PNP0100> at port 0x40-0x43 irq 0 on isa0 unknown4: <PNP0b00> at port 0x70-0x71 irq 8 on isa0 unknown: <PNP0303> can't assign resources unknown5: <PNP0800> at port 0x61 on isa0 unknown6: <PNP0c04> at port 0xf0-0xff irq 13 on isa0 unknown7: <PNP0c02> at port 0x4d0-0x4d1,0xcf8-0xcff,0x10-0x1f,0x22-0x3f,0x50-0x52,0x72-0x77,0x91-0x93,0xa2-0xbe,0x400-0x43f,0x440-0x44f on isa0 unknown8: <PNP0c02> at port 0x290-0x297,0x370-0x371 on isa0 unknown: <PNP0501> can't assign resources unknown9: <PNP0c02> on isa0 unknown: <PNP0400> can't assign resources unknown: <PNP0700> can't assign resources unknown: <PNP0f13> can't assign resources unknown10: <PNP0a03> on isa0 I was originally under the impression that something was broken - given that some of the I/O addresses reflect things like the Timer and DMA registers. Searching the archives, I found Peter Wemm stating: "..things will pretty much work as before, except you'll see unknown pnp devices being claimed by the "unknown" driver. You will need to remove "controller pnp0" from your config file if you have it. The latest config(8) has been fixed to warn about all unknown devices/controllers/etc. It's not a fatal error though and a kernel with the line will build and work just the same." From this I'm guessing nothing's actually broken (everything in the system works fine) - but surely there must be a simple way to get rid of such verbosity? Secondly, atomic.c won't compile (due to atomic.h) with g/cc unless an optimisation flag supplied. I noticed this when I tried compiling my kernel with COPTS=-pipe only (ie; no -O). Thirdly, what actually has to be done to remove the "WARNING: run /dev/MAKEDEV before 2000-06-01 to get rid of block devices" message? I've run sh MAKEDEV [all] numerous times - as well as making individual device nodes - to no avail; the message keeps coming up. Thanks for your time. Regards, Trent. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39103817.3A7045A1>