unknown devices
Down near the botton I have some unknown pnp devices, is there any way to figure out what devices they are, they must be motherboard resources because all other devices seem to be accounted for. Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #5: Fri Jan 12 11:14:56 CST 2001 [EMAIL PROTECTED]:/usr/src/sys/compile/DWCJR Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 1102506314 Hz CPU: AMD Athlon(tm) Processor (1102.51-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x642 Stepping = 2 Features=0x183f9ff AMD Features=0xc044<,AMIE,DSP,3DNow!> real memory = 402587648 (393152K bytes) config> avail memory = 387854336 (378764K bytes) Preloaded elf kernel "kernel" at 0xc03b3000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc03b309c. Preloaded elf module "vesa.ko" at 0xc03b30ec. Preloaded elf module "if_xl.ko" at 0xc03b3188. Preloaded elf module "miibus.ko" at 0xc03b3228. Preloaded elf module "usb.ko" at 0xc03b32c8. Preloaded elf module "bktr.ko" at 0xc03b3364. Preloaded elf module "bktr_mem.ko" at 0xc03b3400. Preloaded elf module "random.ko" at 0xc03b34a0. Preloaded elf module "agp.ko" at 0xc03b3540. Preloaded elf module "snd_es137x.ko" at 0xc03b35dc. Preloaded elf module "snd_pcm.ko" at 0xc03b3680. bktr_mem: memory holder loaded Pentium Pro MTRR support enabled VESA: v3.0, 4096k memory, flags:0x1, mode table:0xc032a2e2 (122) VESA: NVidia ACPI debug layer 0x0 debug level 0x0 Using $PIR table, 8 entries at 0xc00f7960 acpi0: on motherboard acpi0: power button is handled as a fixed feature programming model. acpi_tz0: on acpi0 acpi_tz0: current temperature 52.0C acpi_button0: on acpi0 acpi_pcib0: on acpi0 pci0: on acpi_pcib0 agp0: mem 0xe000-0xefff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 7.4 (no driver attached) ahc0: port 0xd800-0xd8ff mem 0xd000-0xdfff irq 9 at device 12.0 on pci0 aic7880: Wide Channel A, SCSI Id=7, 16/255 SCBs bktr0: mem 0xdddfc000-0xdddfcfff irq 10 at device 13.0 on pci0 bktr0: Warning - card vendor 0x1002 (model 0x0001) unknown. bktr0: Detected a MSP3430G-A4 at 0x80 bktr0: Pinnacle/Miro TV, Temic NTSC tuner, msp3400c stereo. pci0: at 13.1 (no driver attached) pcm0: port 0xd400-0xd43f irq 11 at device 14.0 on pci0 xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xd000-0xd07f mem 0xdfffef80-0xdfffefff irq 5 at device 15.0 on pci0 xl0: Ethernet address: 00:50:04:b7:13:09 miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto acpi_button1: on acpi0 acpi_timer0: <24-bit timer at 3.579545MHz> on acpi0 npx0: on motherboard npx0: INT 16 interface atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 fd1: <1200-KB 5.25" drive> on fdc0 drive 1 pmtimer0 on isa0 ppc0: parallel port not found. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources ad0: 6149MB [13328/15/63] at ata0-master UDMA66 ad1: 2317MB [4708/16/63] at ata0-slave UDMA33 acd0: CDROM at ata1-master using PIO4 Waiting 5 seconds for SCSI devices to settle Mounting root from ufs:/dev/ad1s1a cd0 at ahc0 bus 0 target 3 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: cd present [1 x 2048 byte records] pcm0: hwptr went backwards 2208 -> 2016 --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Unknown Devices
Nick Hibma writes: > Yes, the driver is here and it seems to work according to Mike Meyer > (IIRC), he's fixed up a few other bits and pieces and I am ready to > commit it, but I haven't had time to test it yet. I've still got the problems I reported to the bsd-usb list, but I suspect those are specific to my modem, not umodem. I've been updating my development box to -current, along with creating space so I can install Win98 on a second disk to investigate this some more. Unfortunately, I probably won't be able to look into it for a couple of weeks, as Reality is about to make a serious intrustion. It's a lot better than what's in the tree now, and I'd certainly like to see it committed. Thanx,
Re: Unknown Devices
> : > usb tty and modems aren't supported, as far as I know. > : > : They're "nearly" there, AFAIR. I sent Nick some code a while back that > : addressed the last problem I understood he had. > > I'll have to ask him about it then. Picked it up, looked at it, got distracted by Reality and must have dropped it again. I wish Reality would just back off for a while... Yes, the driver is here and it seems to work according to Mike Meyer (IIRC), he's fixed up a few other bits and pieces and I am ready to commit it, but I haven't had time to test it yet. Nick -- [EMAIL PROTECTED] [EMAIL PROTECTED] USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Unknown Devices
In message <[EMAIL PROTECTED]> Mike Smith writes: : > In message <[EMAIL PROTECTED]> Mike Smith writes: : > : Watch out - some USB modems are also WinModems. : > : > usb tty and modems aren't supported, as far as I know. : : They're "nearly" there, AFAIR. I sent Nick some code a while back that : addressed the last problem I understood he had. I'll have to ask him about it then. : You pull them apart and look at the chipset inside. There are a number : of chipsets from eg. ST that take an isochronous audio stream. Yuck. Where's that air sickness bag... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Unknown Devices
> In message <[EMAIL PROTECTED]> Mike Smith writes: > : Watch out - some USB modems are also WinModems. > > usb tty and modems aren't supported, as far as I know. They're "nearly" there, AFAIR. I sent Nick some code a while back that addressed the last problem I understood he had. > How can you > tell the usb modems that are win modems? And can y ou get docs on > them? You pull them apart and look at the chipset inside. There are a number of chipsets from eg. ST that take an isochronous audio stream. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Unknown Devices
> : Watch out - some USB modems are also WinModems. Not WinModems as such (the USB link is too slow to feed the DSP, but they do have proprietary protocols). 3COM modems are safe though. They are class compliant. Nick > > usb tty and modems aren't supported, as far as I know. How can you > tell the usb modems that are win modems? And can y ou get docs on > them? > > Warner > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hardware" in the body of the message > -- [EMAIL PROTECTED] [EMAIL PROTECTED] USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Unknown Devices
In message <[EMAIL PROTECTED]> Mike Smith writes: : Watch out - some USB modems are also WinModems. usb tty and modems aren't supported, as far as I know. How can you tell the usb modems that are win modems? And can y ou get docs on them? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Unknown Devices
In message <[EMAIL PROTECTED]> Eaglez writes: : Well, i'm not sure about 5.0's new funky support (i : mean, if it supports the SB Live, who knows), but in : the past, PCI modems have never been supported, : because they all tend to be win modems (only MS : windows drivers available). I'd advise possibly an : external modem. (Hey, they're probably still cheaper : than USB modems, although i'd go with that if it IS : somehow cheaper.) PCI modems have been supported since just after 4.0 was released. They *MUST* be controller based. There are only two or three of these in the marketplace. > pci0: (vendor=0x11c1, dev=0x0441) at 0x11c1 is actiontec. 0x0441 is not the one known good device. 0x0480 is that one. 0x0441 is, I think, the winmodem version, which sadly we cannot support at this time. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Unknown Devices
On 05-Jun-00 John Hengstler wrote: > I don't know that what the actual modem is inside. The system is a Compaq > Presario 1200. I rather think that means Lucent windows only modem. It does in my 1690. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Unknown Devices
At 2 Jun 2000 21:09:16 GMT, John Hengstler <[EMAIL PROTECTED]> wrote: > pci0: (vendor=0x11c1, dev=0x0441) at 9.0 irq 9 http://www.yourvote.com/pci/pciread.asp?venid=0x11c1 says that chip is AT&T Microelectronics' WinModem. This is not yet supported by FreeBSD. -- Jun Kuriyama <[EMAIL PROTECTED]> // FreeBSD Project To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Unknown Devices
I don't know that what the actual modem is inside. The system is a Compaq Presario 1200. I am waiting for the compaq restore CD to reinstall the windows side to figure out what really on here. (Needs a compaq driver?) John - Original Message - From: "Mike Smith" <[EMAIL PROTECTED]> To: "Eaglez" <[EMAIL PROTECTED]> Cc: "John Hengstler" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Monday, June 05, 2000 8:23 AM Subject: Re: Unknown Devices > > Well, i'm not sure about 5.0's new funky support (i > > mean, if it supports the SB Live, who knows), but in > > the past, PCI modems have never been supported, > > because they all tend to be win modems (only MS > > windows drivers available). I'd advise possibly an > > external modem. (Hey, they're probably still cheaper > > than USB modems, although i'd go with that if it IS > > somehow cheaper.) > > Watch out - some USB modems are also WinModems. > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] > \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] > > > > > 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
Re: Unknown Devices
> Well, i'm not sure about 5.0's new funky support (i > mean, if it supports the SB Live, who knows), but in > the past, PCI modems have never been supported, > because they all tend to be win modems (only MS > windows drivers available). I'd advise possibly an > external modem. (Hey, they're probably still cheaper > than USB modems, although i'd go with that if it IS > somehow cheaper.) Watch out - some USB modems are also WinModems. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Unknown Devices
Well, i'm not sure about 5.0's new funky support (i mean, if it supports the SB Live, who knows), but in the past, PCI modems have never been supported, because they all tend to be win modems (only MS windows drivers available). I'd advise possibly an external modem. (Hey, they're probably still cheaper than USB modems, although i'd go with that if it IS somehow cheaper.) -Jesse --- John Hengstler <[EMAIL PROTECTED]> wrote: > Greetings, > > I just subscribed to -current list to get > suggestions on the following so if > I have missed comments on this already I am sorry > for the redundancy. > > I have just upgraded to 5.0-current in order to get > the driver for my ether > card, which has corrected that problem (xe device). > > But I still can't access my pci modem, because it is > listed as an unknown > device. There are many other unknown devices as > well. The following is > dmesg output: > > Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All > rights reserved. > FreeBSD 5.0-CURRENT #0: Thu Jun 1 22:20:39 PDT 2000 > [EMAIL PROTECTED]:/usr/src/sys/compile/ATBD > Timecounter "i8254" frequency 1193182 Hz > CPU: AMD-K6(tm) 3D processor (473.17-MHz 586-class > CPU) > Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 > > Features=0x8021bf > AMD Features=0x8800 > real memory = 29294592 (28608K bytes) > avail memory = 25411584 (24816K bytes) > Preloaded elf kernel "kernel" at 0xc033e000. > K6-family MTRR support enabled (2 registers) > md0: Malloc disk > npx0: on motherboard > npx0: INT 16 interface > apm0: on motherboard > apm: found APM BIOS v1.2, connected at v1.2 > pcib0: on motherboard > pci0: on pcib0 > pcib1: > at device 1.0 on pci0 > pci1: on pcib1 > pci1: device> at 0.0 irq 9 > isab0: at device 7.0 on > pci0 > isa0: on isab0 > atapci0: port > 0x1820-0x182f at device 7.1 on > pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > pci0: at 7.2 irq 11 > isab1: > at device 7.4 on pci0 > chip1: port > 0x1830-0x1833,0x1834-0x1837,0x1000-0x10ff irq 11 at > device 7.5 on pci0 > > ***built in card here ? also appeared in prior sys > releases *** > pci0: (vendor=0x11c1, dev=0x0441) at > 9.0 irq 9 > > pcic-pci0: at > device 10.0 on pci0 > pcic-pci0: TI12XX PCI Config Reg: [ring > enable][speaker enable][pwr > save][CSC serial isa irq] > fdc0: at port > 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > atkbdc0: at port > 0x60,0x64 on isa0 > atkbd0: irq 1 on atkbdc0 > psm0: irq 12 on atkbdc0 > psm0: model Generic PS/2 mouse, device ID 0 > vga0: at port 0x3c0-0x3df iomem > 0xa-0xb on isa0 > sc0: on isa0 > sc0: VGA <16 virtual consoles, flags=0x200> > pcic0: at port 0x3e0-0x3e1 on isa0 > pcic0: Polling mode > pccard0: on pcic0 > pccard1: on pcic0 > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > ppc0: This ppc chipset does not support the extended > I/O port range...no > problem > ppc0: at port 0x378-0x37b irq 7 on > isa0 > ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE > mode > ppi0: on ppbus0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > plip0: on ppbus0 > unknown0: at port > 0x80,0x62,0x66,0x72-0x75,0x92,0xa8-0xa9,0x38a-0x38b,0x8040-0x807f,0x9050-0x9 > 051 iomem 0xfffe-0x on isa0 > unknown1: at iomem > 0-0x9,0xec000-0xf,0x10-0x1bf on > isa0 > unknown2: at port > 0-0xf,0x81-0x8f,0xc0-0xdf drq 4 on isa0 > unknown: can't assign resources > unknown3: at port 0x40-0x43 irq 0 on isa0 > unknown4: at port 0x70-0x71 irq 8 on isa0 > unknown: can't assign resources > npxisa0: at port > 0xf0-0xff irq 13 on isa0 > unknown5: at port 0x61 on isa0 > unknown6: at port 0xcf8-0xcff on isa0 > unknown7: at port > 0x4d0-0x4d1,0x8000-0x803f,0x8080-0x808f on isa0 > unknown8: at port 0x3400-0x347f on isa0 > unknown9: at iomem 0xdc000-0xd on isa0 > unknown10: on isa0 > unknown: can't assign resources > unknown: can't assign resources > unknown: can't assign resources > unknown: can't assign resources > IP packet filtering initialized, divert disabled, > rule-based forwarding > enabled, default to deny, logging limited to 10 > packets/entry by default > ad0: 5729MB [12416/15/63] at > ata0-master using UDMA66 > acd0: CDROM at ata1-master > using UDMA33 > Mounting root from ufs:/dev/ad0s3a > pccard
Unknown Devices
Greetings, I just subscribed to -current list to get suggestions on the following so if I have missed comments on this already I am sorry for the redundancy. I have just upgraded to 5.0-current in order to get the driver for my ether card, which has corrected that problem (xe device). But I still can't access my pci modem, because it is listed as an unknown device. There are many other unknown devices as well. The following is dmesg output: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Thu Jun 1 22:20:39 PDT 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/ATBD Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (473.17-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x8800 real memory = 29294592 (28608K bytes) avail memory = 25411584 (24816K bytes) Preloaded elf kernel "kernel" at 0xc033e000. K6-family MTRR support enabled (2 registers) md0: Malloc disk npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 9 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1820-0x182f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 7.2 irq 11 isab1: at device 7.4 on pci0 chip1: port 0x1830-0x1833,0x1834-0x1837,0x1000-0x10ff irq 11 at device 7.5 on pci0 ***built in card here ? also appeared in prior sys releases *** pci0: (vendor=0x11c1, dev=0x0441) at 9.0 irq 9 pcic-pci0: at device 10.0 on pci0 pcic-pci0: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][CSC serial isa irq] fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> pcic0: at port 0x3e0-0x3e1 on isa0 pcic0: Polling mode pccard0: on pcic0 pccard1: on pcic0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A ppc0: This ppc chipset does not support the extended I/O port range...no problem ppc0: at port 0x378-0x37b irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 unknown0: at port 0x80,0x62,0x66,0x72-0x75,0x92,0xa8-0xa9,0x38a-0x38b,0x8040-0x807f,0x9050-0x9 051 iomem 0xfffe-0x on isa0 unknown1: at iomem 0-0x9,0xec000-0xf,0x10-0x1bf on isa0 unknown2: at port 0-0xf,0x81-0x8f,0xc0-0xdf drq 4 on isa0 unknown: can't assign resources unknown3: at port 0x40-0x43 irq 0 on isa0 unknown4: at port 0x70-0x71 irq 8 on isa0 unknown: can't assign resources npxisa0: at port 0xf0-0xff irq 13 on isa0 unknown5: at port 0x61 on isa0 unknown6: at port 0xcf8-0xcff on isa0 unknown7: at port 0x4d0-0x4d1,0x8000-0x803f,0x8080-0x808f on isa0 unknown8: at port 0x3400-0x347f on isa0 unknown9: at iomem 0xdc000-0xd on isa0 unknown10: on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources IP packet filtering initialized, divert disabled, rule-based forwarding enabled, default to deny, logging limited to 10 packets/entry by default ad0: 5729MB [12416/15/63] at ata0-master using UDMA66 acd0: CDROM at ata1-master using UDMA33 Mounting root from ufs:/dev/ad0s3a pccard: card inserted, slot 0 Everything else on the system works for now, except for the modem. This same results were in 4.0-release, and stable as well.. Any suggestions are appreciated. John Hengstler To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Unknown Devices in Dmesg
In message <[EMAIL PROTECTED]> "Thomas D. Dean" writes: : and have devices listed as 'unknown' in dmesg. Everything appears to : function OK. They are ok. : The serial ports, sio0 and sio1 appear both as sio and unknown. Yes. This is expected. The PnP BIOS code which should execute before all the other devices are probed actually executes after, so you get things like that. It is safe to ignore for now. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Unknown Devices in Dmesg
I cvsup'ed, make world, rebuild+install kernel, reboot, without problem. Good work. I upgraded from Apr 4 -current to May 28 -current and have devices listed as 'unknown' in dmesg. Everything appears to function OK. The serial ports, sio0 and sio1 appear both as sio and unknown. tomdean === dmesg Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #1: Sun May 28 11:07:09 PDT 2000 tomdean@celebris:/usr/src/sys/compile/CELEBRIS-SMP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P54C (109.34-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping = 5 Features=0x3bf real memory = 100663296 (98304K bytes) avail memory = 94887936 (92664K bytes) Programming 16 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee0 io0 (APIC): apic id: 2, version: 0x000f0011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc02f2000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02f209c. Intel Pentium detected, installing workaround for F00F bug npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 ncr0: port 0xec00-0xecff mem 0xfedfbf00-0xfedfbfff irq 11 at device 1.0 on pci0 isab0: at device 2.0 on pci0 isa0: on isab0 pci0: at 6.0 irq 9 de0: port 0xe880-0xe8ff mem 0xfedfbe80-0xfedfbeff irq 10 at device 8.0 on pci0 de0: DEC DE450-CA 21041 [10Mb/s] pass 1.1 de0: address 00:00:f8:02:76:db fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: This ppc chipset does not support the extended I/O port range...no problem ppc0: at port 0x378-0x37b irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Interrupt-driven port unknown0: at port 0x4d0-0x4d1,0xcf8,0xcfa on isa0 unknown1: at port 0x26,0x26e-0x26f on isa0 unknown2: at port 0x61 on isa0 unknown3: at iomem 0-0x9,0xe-0xf,0xfec0-0xfec3,0xfee0-0xfee3 on isa0 unknown: can't assign resources npxisa0: at port 0xf0-0xff irq 13 on isa0 unknown: can't assign resources unknown: <16550 compatible COM device> can't assign resources unknown: <16550 compatible COM device> can't assign resources unknown: can't assign resources unknown4: at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 unknown: can't assign resources unknown5: at port 0-0xf,0x81-0x8f,0xc0-0xdf drq 4 on isa0 unknown6: at port 0x20-0x21,0xa0-0xa1 irq 2 on isa0 unknown7: at port 0x40-0x43 irq 0 on isa0 unknown8: at port 0x70-0x71 irq 8 on isa0 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 Waiting 10 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! cd0 at ncr0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 4.237MB/s transfers (4.237MHz, offset 8) cd0: cd present [295811 x 2048 byte records] da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 8) da0: 1042MB (2134305 512 byte sectors: 255H 63S/T 132C) da2 at ncr0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da2: 1029MB (2109376 512 byte sectors: 255H 63S/T 131C) Mounting root from ufs:/dev/da1s1a da1 at ncr0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da1: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) de0: enabling BNC port To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
