search for: iobase

...;Am79C973"/> <Adapter slot="7" enabled="false" MACAddress="080027C22A98" cable="true" speed="0" type="Am79C973"/> </Network> <UART> <Port slot="0" enabled="false" IOBase="0x3f8" IRQ="4" hostMode="Disconnected"/> <Port slot="1" enabled="false" IOBase="0x3f8" IRQ="4" hostMode="Disconnected"/> </UART> <LPT> <Port slot="0" enable...

...kernel-xen-nongpl-2.6.13-15 > > xen-3.0_6715-2 > > > > System startup with xen kernel fails on detecting the boot > > device, which is attached to the qla2300 fibre channel host > > bus adapter. > > > > qla2300 0000:05:01.0: Found an ISP2312, irq 185, iobase > > 0xf8812000 qla2300 0000:05:01.0: Configuring PCI space... > > qla2300 0000:05:01.0: Configure NVRAM parameters... > > qla2300 0000:05:01.0: Verifying loaded RISC code... > > qla2300 0000:05:01.0: Waiting for LIP to complete... > > > > Until here it''...

...kernel-xen-nongpl-2.6.13-15 > > xen-3.0_6715-2 > > > > System startup with xen kernel fails on detecting the boot > > device, which is attached to the qla2300 fibre channel host > > bus adapter. > > > > qla2300 0000:05:01.0: Found an ISP2312, irq 185, iobase > > 0xf8812000 qla2300 0000:05:01.0: Configuring PCI space... > > qla2300 0000:05:01.0: Configure NVRAM parameters... > > qla2300 0000:05:01.0: Verifying loaded RISC code... > > qla2300 0000:05:01.0: Waiting for LIP to complete... > > > > Until here it''...

...rrectly on boot. So i cannot see other partitions than sda. --------------------------------------------------------------------------------- QLogic Fibre Channel HBA Driver ACPI: PCI Interrupt 0000:04:02.0[A] -> GSI 24 (level, low) -> IRQ 185 qla2300 0000:04:02.0: Found an ISP2312, irq 185, iobase 0xf8840000 scsi3 : qla2xxx qla2300 0000:04:02.0: Configuring PCI space... qla2300 0000:04:02.0: Configure NVRAM parameters... qla2300 0000:04:02.0: Verifying loaded RISC code... qla2300 0000:04:02.0: Waiting for LIP to complete... qla2300 0000:04:02.0: LIP reset occured (f7f7). qla2300 0000:04:02.0...

...ing over a serial port. To print to I/O port 0x402 (the default used by SeaBIOS and OVMF), add "-DDEBUG_IO_PORT=0x402 -DCORE_DEBUG=1" to the build CFLAGS. To enable a debug console in QEMU that listens to I/O port 0x402 and prints to stdio, add "-debugcon stdio -global isa-debugcon.iobase=0x402" to the QEMU command line. Jonathan Boeing (1): dprintf: add debug console support com32/include/dprintf.h | 2 +- com32/lib/dprintf.c | 4 ++-- com32/lib/vdprintf.c | 21 ++++++++++++++++++++- core/lwip/src/netif/undiif.c | 2 +- mk/devel.mk...

...fairly impressive. They even have a boot diskette available to support those old BIOS that won't boot CDs, as this unit was. So, thanks Bryan. I'm trying to configure a backup unit on an old Aptiva DX2/66. Have 1 ISA Etherjet. Need a couple more ISA NICS that are configurable for IRQ/IOBASE. Anyone that wants to put two old good ISA NICS into a home where they will be cared for and appreciated, send me an email with details, if config diskette available (even if off the net), price, etc. I'll pay shipping too. Remove the underscores in the following address. w_ild-_bi_ll...

...> To print to I/O port 0x402 (the default used by SeaBIOS and OVMF), > add "-DDEBUG_IO_PORT=0x402 -DCORE_DEBUG=1" to the build CFLAGS. > > To enable a debug console in QEMU that listens to I/O port 0x402 and prints to > stdio, add "-debugcon stdio -global isa-debugcon.iobase=0x402" to the QEMU > command line. When enabled, what will the effect on real hardware without the diagnostic hardware ? When enabled, what will the effect on real hardware ? What (real) diagnostic hardware is adviced? Oops, I should have start with: Thank you for providing these de...

...This is on an HP DL320 G4 with a Pentium D 930 processor. I tried unloading and reloading the qla2xxx module, but rmmod reported it in use, however it did not seem to be used by any other module. dmesg output below: QLogic Fibre Channel HBA Driver qla2xxx 0000:06:01.0: Found an ISP2312, irq 16, iobase 0xffffc2000001e000 qla2xxx 0000:06:01.0: Configuring PCI space... qla2xxx 0000:06:01.0: Configure NVRAM parameters... ----------- [cut here ] --------- [please bite here ] --------- Kernel BUG at arch/x86_64/mm/fault-xen.c:292 invalid opcode: 0000 [1] SMP CPU 1 Modules linked in: qla2xxx libata fir...

...f you don't want balloon enabled you have to explicitly give model=none > + if guestcaps.gcaps_isa_pvpanic then > + push_back devices ( > + e "panic" ["model", "isa"] [ > + e "address" ["type", "isa"; "iobase", "0x505"] [] > + ] > + ); > + > (* Standard devices added to every guest. *) > append devices [ > e "input" ["type", "tablet"; "bus", "usb"] []; Regards, Daniel -- |: http://berrange.com -o...

...entium D 930 processor. I tried unloading > and reloading the qla2xxx module, but rmmod reported it in use, however it > did not seem to be used by any other module. > > dmesg output below: > > QLogic Fibre Channel HBA Driver > qla2xxx 0000:06:01.0: Found an ISP2312, irq 16, iobase 0xffffc2000001e000 > qla2xxx 0000:06:01.0: Configuring PCI space... > qla2xxx 0000:06:01.0: Configure NVRAM parameters... > ----------- [cut here ] --------- [please bite here ] --------- > Kernel BUG at arch/x86_64/mm/fault-xen.c:292 > invalid opcode: 0000 [1] SMP > CPU 1 > Mo...

...ing - it talks to a database and some other processes, i.e. I''d really like to avoid having the userspace driver in dom0. Is that somehow possible? I only know about dedicating whole PCI devices to domains but how about giving them serial ports? Is that possible? Given that I know the IRQ/iobase, have kernel with drivers in domU, etc... Thanks! Giovanni _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Adam Jackson (2): Remove mibstore.h Adapt Block/WakeupHandler signature for ABI 23 Egbert Eich (1): init: Initialize VGA IOBase before using it Jeremy White (1): Include xf86Modes.h to use functions from hw/xfree86/modes/xf86Modes.c. Matt Turner (1): xf86-video-nv 2.1.21 Matthieu Herrb (1): Fix shadow framebuffer implementation. git tag: xf86-video-nv-2.1.21 https://xorg.freedesktop.org/archive/indivi...

...en + push_back devices (e "memballoon" ["model", "virtio"] []); + if guestcaps.gcaps_isa_pvpanic then + push_back devices ( + e "panic" ["model", "isa"] [ + e "address" ["type", "isa"; "iobase", "0x505"] [] + ] + ); + (* Standard devices added to every guest. *) append devices [ e "input" ["type", "tablet"; "bus", "usb"] []; -- 2.12.0

...gt; of RAM available -- like most other BIOSes out there already > > do - it would be extremely helpful to aid troubleshooting. > > SeaBIOS boots too fast for anything useful to be seen on the screen. > That said, one can add "-chardev stdio,id=seabios -device > isa-debugcon,iobase=0x402,chardev=seabios" to the qemu command line > to > see the SeaBIOS debugging output. That output has the memory info > and much more. I guess that's then something to propose for libvirt as RFE as an extra argument for <bios useserial='yes' /> we could introduc...

...10DC100 GMCH + 82801AA ICH). The docs say that there is support for UDMA66, but FreeBSD reports that the drive is being set to UDMA33. I booted in verbose mode, and here are the relevant parts from dmesg. atapci0: <Intel ICH ATA66 controller> port 0xffa0-0xffaf at device 31.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xffa0 ata0: mask=03 ostat0=50 ostat2=50 ata0-master: ATAPI 00 00 ata0-slave: ATAPI 14 eb ata0: mask=03 stat0=50 stat1=10 ata0-master: ATA 01 a5 ata0: devices=09 ata0: at 0x1f0 irq 14 on atapci0 ... ad0: success setting UDMA2 on Intel chip Creating DISK ad0 ar: Free...

...2 (the default used by SeaBIOS and OVMF), > > add "-DDEBUG_IO_PORT=0x402 -DCORE_DEBUG=1" to the build CFLAGS. > > > > To enable a debug console in QEMU that listens to I/O port 0x402 > > and prints to stdio, add "-debugcon stdio -global > > isa-debugcon.iobase=0x402" to the QEMU command line. > > > When enabled, what will the effect on real hardware without the > diagnostic hardware ? > > When enabled, what will the effect on real hardware ? > > What (real) diagnostic hardware is adviced? > This doesn't support r...

...rident model 8500 VGA-compatible display device> (vendor=0x1023, dev=0x8 500) at 0.0 irq 11 isab0: <PCI to ISA bridge (vendor=1106 device=8231)> at device 17.0 on pci0 isa0: <ISA bus> on isab0 atapci0: <VIA 8231 ATA100 controller> port 0xd000-0xd00f at device 17.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xd000 ata0: mask=03 ostat0=50 ostat2=00 ata0-master: ATAPI 00 00 ata0-slave: ATAPI 00 00 ata0: mask=03 stat0=50 stat1=00 ata0-master: ATA 01 a5 ata0: devices=01 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xd008 ata1: mask=03 ostat0=5...

...driver version 1.32 mISDN: DSS1 Rev. 1.47 mISDN Capi 2.0 driver file version 1.21 mISDN: HFC-multi driver Rev. 1.68 HFC-multi: card manufacturer: 'Cologne Chip AG' card name: 'HFC-2S Beronet Card' clock: double PCI: enabling device 0000:00:05.0 (0000 -> 0003) HFC-2S#1: defined at IOBASE 0x1000 IRQ 28 HZ 100 leds-type 3 HFC_multi: resetting HFC with chip ID=0xc revision=1 hfcpci_probe: DIPs(0x9f) jumpers(0x1) HFC_manager: channel 2 (0..31) data c30d0000 prim f1681 arg 00000000 HFC_manager: MGR_REGLAYER HFC_manager: channel 2 (0..31) data c30d0000 prim f1482 arg 00000000 HFC_manag...

...is: 0xc000 (II) S3VIRGE(0): VESA BIOS detected (II) S3VIRGE(0): VESA VBE Version 1.2 (II) S3VIRGE(0): VESA VBE Total Mem: 2048 kB (II) S3VIRGE(0): VESA VBE OEM: S3 Incorporated. 86C375/86C385 (--) S3VIRGE(0): Chipset: "virge dx" (==) S3VIRGE(0): XVideo supported. (II) S3VIRGE(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000 (II) S3VIRGE(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000 (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Loading /usr/lib/xorg/modules/libddc.so (II) Module ddc: vendor="X.Org Fou...

I just noticed the 4.9-20030914-PRERELEASE and made a set of installation boot floppies from it to see which of the devices in my new PC the PRERELEASE would support. It wedged hard during the boot autoconfiguration monologue, just after typing these lines on the console: atapci0: <Intel ICH5 ATA100 controller> port 0xf000-0xf00f,0-0x3,0-0x7,0-0x3,0-0x7 irq 0 at device 31.1 on pci0 ata0: