Displaying 9 results from an estimated 9 matches for "d4000000".
Did you mean:
4000000
2011 Mar 18
1
Incorrect Video Card Recognization
...le controller: nVidia Corporation Device 0e23 (rev a1) (prog-if 00 [VGA controller])
Subsystem: eVga.com. Corp. Device 1366
Flags: bus master, fast devsel, latency 0, IRQ 18
Memory at fc000000 (32-bit, non-prefetchable) [size=32M]
Memory at d8000000 (64-bit, prefetchable) [size=128M]
Memory at d4000000 (64-bit, prefetchable) [size=64M]
I/O ports at ec00 [size=128]
[virtual] Expansion ROM at fe980000 [disabled] [size=512K]
Capabilities: [60] Power Management version 3
Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [78] Express Endpoint, MSI 00
Capabilities: [b4] Ven...
2002 Mar 09
1
Problem with smbfs on 2.4.18 kernel
...: System RAM
000a0000-000bffff : Video RAM area
000c0000-000c7fff : Video ROM
000c8000-000c97ff : Extension ROM
000f0000-000fffff : System ROM
00100000-1fffffff : System RAM
00100000-001d4763 : Kernel code
001d4764-002041c3 : Kernel data
d0000000-d3ffffff : S3 Inc. 86c764/765 [Trio32/64/64V+]
d4000000-d5ffffff : Intel Corp. 440BX/ZX - 82443BX/ZX Host bridge
d7000000-d70000ff : Realtek Semiconductor Co., Ltd. RTL-8139
d7000000-d70000ff : 8139too
ffff0000-ffffffff : reserved
linux:~ # lspci -vvv
00:00.0 Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge
(rev 03)
Control...
2012 Aug 15
5
[Bug 53535] New: G84M [Quadro NVS 140M] X crash after waking up from suspend: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT)
https://bugs.freedesktop.org/show_bug.cgi?id=53535
Bug #: 53535
Summary: G84M [Quadro NVS 140M] X crash after waking up from
suspend: Process /usr/bin/Xorg was killed by signal 6
(SIGABRT)
Classification: Unclassified
Product: xorg
Version: unspecified
Platform: x86-64 (AMD64)
OS/Version:
2011 Feb 22
6
how to optimize CentOS XEN dom0?
Hi,
I have a problematic CentOS XEN server and hope someone could point me
in the right direction to optimize it a bit.
The server runs on a Core2Quad 9300, with 8GB RAM (max motherboard can
take, 1U chassis) on an Intel motherboard with a 1TB SATA HDD.
dom0 is set to 512MB limit with a few small XEM VM''s running:
root@zaxen01:[~]$ xm list
Name ID
2009 Jun 02
3
how to debug random server reboots
...:30:22 usaxen02 kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9
global_irq 9 high level)
Jun 2 17:30:22 usaxen02 kernel: Setting APIC routing to xen
Jun 2 17:30:22 usaxen02 kernel: Using ACPI (MADT) for SMP
configuration information
Jun 2 17:30:22 usaxen02 kernel: Allocating PCI resources starting at
d4000000 (gap: d0000000:2ff00000)
--
Kind Regards
Rudi Ahlers
CEO, SoftDux Hosting
Web: http://www.SoftDux.com
Office: 087 805 9573
Cell: 082 554 7532
2017 Nov 01
2
Centos and xen network bridge issue
...U:1500 Metric:1
RX packets:1132794 errors:0 dropped:0 overruns:0 frame:0
TX packets:1000019 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:146054455 (139.2 MiB) TX bytes:188561087 (179.8 MiB)
Interrupt:27 Memory:d4000000-d4012800
guestname Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:4155 errors:0 dropped:0 overruns:0 frame:0
TX packets:100856 errors:0 dropped:0...
2007 Apr 18
1
[Bridge] recent crashes? Linux kernel 2.6.18-1.2239.fc5 (Linux Fedora Core 5)
At the risk of angering the crash Gods, my sustem has NOT crashed again
since I downgraded the kernel from 2.6.18-1.2239.fc5 to 2.6.18-1.2200.fc5.
Given that newfound stability, and my lack of time, I'm going to put on
hold any further diagnostics, until the next kernel revision is released.
I have submitted a report at bugzilla.redhat.com (bug 218128). (Ah, nuts;
accidentally created a
2011 Feb 22
6
how to optimize CentOS XEN dom0?
Hi,
I have a problematic CentOS XEN server and hope someone could point me
in the right direction to optimize it a bit.
The server runs on a Core2Quad 9300, with 8GB RAM (max motherboard can
take, 1U chassis) on an Intel motherboard with a 1TB SATA HDD.
dom0 is set to 512MB limit with a few small XEM VM's running:
root at zaxen01:[~]$ xm list
Name ID
2011 Jan 09
11
(no subject)
OK, so after several weeks of trying to get various versions of Xen running of various distributions, I''m starting to wonder if I''ve got a hardware compatibility problem and as the system never really boots with the Xen kernel I''ve got no log files to tell me where the problem is. I was wondering if there''s a way to compile from source with debug turned on,