Re: [Fedora-xen] problem creating my 1st VM
by Guillaume
> It has been a while since I have used a paravirtualized vm, so my responses
> will be vague, but perhaps helpful.
> Regarding your original install, both previous responses made good points.
> However, I thought some additional explanation might be helpful:
> a)
> -The kernel line you put in your config makes your vm boot that kernel (the
> one on your local disk), so you are already using a xen kernel to boot that
> vm.
Is there a problem by using the kernel use to boot up the system (Dom0) ?
If I understand, you mean that I have to use a kernel dedicated to
boot all DomU ! Why, is there some limitation by using this kernel
(Dom0) for running VM ?
> -There are ready made xen compatible installs of OSes on disk images
> available for download at various places, you should be able to find
> instructions on how to get thee images into your vm's virtual drive as well.
Ok, but I want first, understand how Xen works, and then, i'll get
theses files. I prefer to learn by getting rid of theses problem
before, its a godd formation i think. And i tought too, it's more
quick to use ready-to-use Xen images files.
Thanks for your time :)
16 years, 6 months
no fuse with xen?
by Nico Sabbi
Hi,
there's no fuse module in kernel-xen. Is it intentional
because fuse can't work with it?
Thanks,
Nico
16 years, 6 months
xm mem-set
by unixfoo
My domU's memory usage is around 512 MB , but it is alloted with 4GB of memory. When i try to xm mem-set and reduce memory on a domU, the memory doesnt decrease to the value specified ( even though the domU is idle and memory is not used up at all )
here is my xen version ..
[root@unixfoo ~]# xm info
host : unixfoo
release : 2.6.18-xen
version : #1 SMP Thu Mar 22 14:12:23 PDT 2007
machine : i686
nr_cpus : 1
nr_nodes : 1
sockets_per_node : 1
cores_per_socket : 1
threads_per_core : 1
cpu_mhz : 2394
hw_caps : bfebfbff:00000000:00000000:00000080:00004400
total_memory : 503
free_memory : 53
xen_major : 3
xen_minor : 0
xen_extra : -unstable
xen_caps : xen-3.0-x86_32p
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xf5800000
xen_changeset : unavailable
cc_compiler : gcc version 3.4.6 20060404 (Red Hat 3.4.6-3.1)
cc_compile_by : root
cc_compile_domain : localhost
cc_compile_date : Thu Mar 22 14:12:26 PDT 2007
xend_config_format : 3
[root@unixfoo0~]#
any pointers?
un1xf00
http://unixfoo.blogspot.com
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
16 years, 6 months
Reinstall host, guest management
by Augusto Castelan Carlson
Hi!
I have a server with two guests (all Fedora 7). Each one has its own partition.
host: /dev/hda1
guest1: /dev/hda2
guest2: /dev/hda3
Suppose that my host fail and I need to reinstall it. After
reinstalling, how can I have access to my 2 guests using tools such as
virt-manager/virsh/xm? or make them run as the were before the host
failed.
When I installed both guests, no configuration file was created in /etc/xen
Thanks in advance.
Regards,
--
Augusto Castelan Carlson
16 years, 6 months
Re: Rootkit
by Jordi Prats
About this discussion, chkrootkit are for live systems, isn't it?
There's any tool to do rootkit analysis on a "dead" system?
I'm thinking of check for rootkits on snapshots of the file system of a
virtual machine to determine if the running virtual machine is compromised.
Thanks,
Jordi
bob.smith(a)kolumbus.fi wrote:
> Dave Burns <tburns(a)hawaii.edu> kirjoitti:
>> > >> While reading this thread it occurred to me that if disk drives
>> had a
>> > >> read-only switch, then systems would be uncrackable.
>>
>> Well, that would go a long way to make intrusion more difficult, but
>> not impossible. Intruder just mounts something on top of your read
>> only partition that looks a lot like your partition but with a few
>> well chosen modifications. He then has to hide evidence of his trick,
>> which would not be easy (at least for me!), but that's not to say it
>> could not be done. In fact I have heard of a very similar approach
>> being used (sort of the opposite - an innocuous partition mounted over
>> a partition full of rootkit stuff to keep it hidden), though
>> apparently the intruder had not perfected it yet, since the admin
>> eventually figured out what was going on.
>>
>> > There are special filesystems ("unionfs" ?)
>> > that redirect writes to a read-only file to a copy of the file in a
>> > writable partition (I think).
>>
>> Yeah, but wouldn't that defeat the idea? Are you making it read only
>> so that you know for sure it is good and can use it with confidence or
>> so that you can easily recover your original files after getting
>> (expletive deleted)? This "read-only" partition approach is only worth
>> the trouble if it actually takes some capability away from the
>> intruder. If the filesystem is read/write but your "originals" are
>> read only, that only bothers the intruder if he actually wants to
>> erase them. What does he want to erase? Log files, which do not belong
>> on a read only filesystem in any case.
>>
>> You could use it for monitoring - if it was easy to do a check whether
>> ps and lsof and other critical executables were actually on the
>> read-only part of disk or had been modified. The utility that does the
>> check had better be on the read only partition, but what do you use to
>> check it? If you're totally hacked you can't be sure that the
>> utilities that you execute are actually coming from that disk. You
>> might be logged in to an emulator! Might as well use tripwire or aide
>> and not bother with the read-onlyness.
>>
>> This has got me thinking.
>> Dave
>>
>> --
>> fedora-list mailing list
>> fedora-list(a)redhat.com
>> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>>
>
> Hi, I am glad you are discussing this, because there are issues to
> ponder.
> About hacking and cracking. A while back I had this idea, well a few
> years back, but it was put aside because a university professor
> disregarded it as useless. and maybe it is.
> The idea was to create sort of(in some way) "encrypted and protected"
> executables. This to be able to verify that an executable is what it
> is(located on machine X, and compiled on machine x). Further, the
> executable would be made so that it could not run on a system on which
> it was not allowed to run. That was the basis of the idea. Purely
> theoretical. How this could be achieved in reality is beyond my
> current knowledgebase, but I am sure that someone else with more
> knowledge in encryption and protection than me, could maybe analyse
> this further.
> (Sure, most machines are loaded with translators and script
> interpreters like perl, and PHP and many others, which allows for
> making quite much damage through scripting. )
>
> Still, it could be something to think about.
> best r
> Bobo
>
>
>
>
--
......................................................................
__
/ / Jordi Prats
C E / S / C A Dept. de Sistemes
/_/ Centre de Supercomputació de Catalunya
Gran Capità, 2-4 (Edifici Nexus) · 08034 Barcelona
T. 93 205 6464 · F. 93 205 6979 · jprats(a)cesca.es
......................................................................
16 years, 6 months
Re: Fedora-xen Digest, Vol 23, Issue 15
by Fierbaugh, Stephen
unsubscribe
fedora-xen-request(a)redhat.com wrote:
> Send Fedora-xen mailing list submissions to
> fedora-xen(a)redhat.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://www.redhat.com/mailman/listinfo/fedora-xen
> or, via email, send a message with subject or body 'help' to
> fedora-xen-request(a)redhat.com
>
> You can reach the person managing the list at
> fedora-xen-owner(a)redhat.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Fedora-xen digest..."
>
>
> Today's Topics:
>
> 1. RE: 64-Bit RAM Detection >4GB? (Dustin Henning)
> 2. RE: 64-Bit RAM Detection >4GB? (Dustin Henning)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 19 Oct 2007 13:29:38 -0400
> From: "Dustin Henning" <Dustin.Henning(a)prd-inc.com>
> Subject: RE: [Fedora-xen] 64-Bit RAM Detection >4GB?
> To: <fedora-xen(a)redhat.com>
> Message-ID: <008301c81275$a02df860$e089e920$@Henning(a)prd-inc.com>
> Content-Type: text/plain; charset="utf-8"
>
>
>> -----Original Message-----
>> From: fedora-xen-bounces(a)redhat.com [mailto:fedora-xen-bounces@redhat.com] On Behalf Of Dale Bewley
>> Sent: Friday, October 19, 2007 11:46
>> To: fedora-xen
>> Subject: Re: [Fedora-xen] 64-Bit RAM Detection >4GB?
>>
>> I have 4 procs with 16G RAM and no mem paramters in grub at all, and it looks like this:
>>
>> Linux h 2.6.20-2931.fc7xen #1 SMP Mon Aug 13 10:11:56 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
>>
>> # grep 'model name' /proc/cpuinfo
>> model name : AMD Opteron(tm) Processor 852
>> model name : AMD Opteron(tm) Processor 852
>> model name : AMD Opteron(tm) Processor 852
>> model name : AMD Opteron(tm) Processor 852
>>
>> # grep Total /proc/meminfo
>> MemTotal: 13335552 kB
>> SwapTotal: 5261240 kB
>> VmallocTotal: 34359738367 kB
>>
>> # xm info |grep total
>> total_memory : 16319
>>
>> I have 3 domU's running with each allocated 1G, so 16-3=13 which I suppose explains the MemTotal line above from the perspective of dom0.
>>
>>
>> On an identical server running RHEL with no xen and I see something a bit different:
>>
>> Red Hat Enterprise Linux AS release 4 (Nahant Update 5)
>> Linux z 2.6.9-55.0.2.ELsmp #1 SMP Tue Jun 12 17:58:20 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
>>
>> # grep Total /proc/meminfo
>> MemTotal: 16359284 kB
>> HighTotal: 0 kB
>> LowTotal: 16359284 kB
>> SwapTotal: 5261240 kB
>> VmallocTotal: 536870911 kB
>> HugePages_Total: 0
>>
>> Not sure if that was helpful.
>> --
>> Dale Bewley - Unix Administrator - Shields Library - UC Davis
>> GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3
>>
>
> Dale,
> That could be very helpful, or it might just get someone to blame Intel. Either way, thanks, now I at least know that it should work and I can try to determine why it isn't. As for the MemTotal, you are correct on why it is 13 instead of 16. However, if you shut down one of those domU's, the memory wouldn't necessarily be automatically re-assigned to dom0, and /proc/meminfo is based on what is assigned to dom0. I think "xm info" would be the correct way to see the detected memory in the system once domU's are created or if dom0 isn't assigned all memory. There may be other ways. Thanks,
> Dustin
>
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 19 Oct 2007 13:34:34 -0400
> From: "Dustin Henning" <Dustin.Henning(a)prd-inc.com>
> Subject: RE: [Fedora-xen] 64-Bit RAM Detection >4GB?
> To: <fedora-xen(a)redhat.com>
> Message-ID: <008401c81276$509879f0$f1c96dd0$@Henning(a)prd-inc.com>
> Content-Type: text/plain; charset="utf-8"
>
>
>> -----Original Message-----
>> From: fedora-xen-bounces(a)redhat.com [mailto:fedora-xen-bounces@redhat.com] On Behalf Of Dale Bewley
>> Sent: Friday, October 19, 2007 11:46
>> To: fedora-xen
>> Subject: Re: [Fedora-xen] 64-Bit RAM Detection >4GB?
>>
>> I have 4 procs with 16G RAM and no mem paramters in grub at all, and it looks like this:
>>
>> Linux h 2.6.20-2931.fc7xen #1 SMP Mon Aug 13 10:11:56 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
>>
>> # grep 'model name' /proc/cpuinfo
>> model name : AMD Opteron(tm) Processor 852
>> model name : AMD Opteron(tm) Processor 852
>> model name : AMD Opteron(tm) Processor 852
>> model name : AMD Opteron(tm) Processor 852
>>
>> # grep Total /proc/meminfo
>> MemTotal: 13335552 kB
>> SwapTotal: 5261240 kB
>> VmallocTotal: 34359738367 kB
>>
>> # xm info |grep total
>> total_memory : 16319
>>
>> I have 3 domU's running with each allocated 1G, so 16-3=13 which I suppose explains the MemTotal line above from the perspective of dom0.
>>
>>
>> On an identical server running RHEL with no xen and I see something a bit different:
>>
>> Red Hat Enterprise Linux AS release 4 (Nahant Update 5)
>> Linux z 2.6.9-55.0.2.ELsmp #1 SMP Tue Jun 12 17:58:20 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
>>
>> # grep Total /proc/meminfo
>> MemTotal: 16359284 kB
>> HighTotal: 0 kB
>> LowTotal: 16359284 kB
>> SwapTotal: 5261240 kB
>> VmallocTotal: 536870911 kB
>> HugePages_Total: 0
>>
>> Not sure if that was helpful.
>> --
>> Dale Bewley - Unix Administrator - Shields Library - UC Davis
>> GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3
>>
>
> Dale,
> Could you tell me if you passed any arguments to the installer during your initial install? Also, can you show me the appropriate portion of your grub.conf? I would like to see if maybe it is different than mine even though they are both pre-packaged installs. I had a machine with 2.6.20-2931.fc7xen, so I copied that to the machine in question, and it also only shows 3.1GiB for me. I compared the config files for that kernel and the one I was using, and they are identical (minus version and date comment lines), so that was as I expected, but it makes it less likely that my problem is a version problem and more likely that something else is haywire. Thanks,
> Dustin
>
>
>
>
>
> ------------------------------
>
> --
> Fedora-xen mailing list
> Fedora-xen(a)redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen
>
>
> End of Fedora-xen Digest, Vol 23, Issue 15
> ******************************************
>
--
Sincerely Yours,
Stephen P. Fierbaugh <stephen(a)fierbaugh.org>
Pioneer Bible Translators <stephen.fierbaugh(a)pbti.org>
Pronounced: "Fire" as in hot, "Bah" as in humbug!
Jesus wept. John 11:35 NIV
16 years, 6 months
FC6 live migrate weirdness
by Pim van Riezen
Hello,
When trying a live migrate, I get the following error:
[2007-10-19 15:33:05 xend 4839] DEBUG (XendCheckpoint:83) [xc_save]: /
usr/lib64/xen/bin/xc_save 22 45 0 0 1
[2007-10-19 15:33:05 xend 4839] INFO (XendCheckpoint:239) Couldn't
enable shadow mode: 12
[2007-10-19 15:33:05 xend 4839] INFO (XendCheckpoint:239) Save exit rc=1
[2007-10-19 15:33:05 xend 4839] ERROR (XendCheckpoint:106) Save
failed on domain vps023 (45).
Traceback (most recent call last):
File "/usr/lib64/python2.4/site-packages/xen/xend/
XendCheckpoint.py", line 100, in save
forkHelper(cmd, fd, saveInputHandler, False)
File "/usr/lib64/python2.4/site-packages/xen/xend/
XendCheckpoint.py", line 227, in forkHelper
raise XendError("%s failed" % string.join(cmd))
XendError: /usr/lib64/xen/bin/xc_save 22 45 0 0 1 failed
[root@yankee ~]# free
total used free shared buffers
cached
Mem: 6286336 1267508 5018828 0 310712
202928
-/+ buffers/cache: 753868 5532468
Swap: 8385920 220 8385700
[root@yankee ~]# uname -a
Linux yankee.xl-is.net 2.6.20-1.2962.fc6xen #1 SMP Tue Jun 19
19:10:51 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
Seems I have plenty of RAM left. What's the deal?
Cheers,
Pi
16 years, 6 months
can't setup virt-install
by 植松健
I installed xen domainU using by virt-install command and kickstart.
The option of virt-install is following.
virt-install -p --ram=256 --name="host1"
--file="/var/lib/xen/images/host1" --file-size=5 --nographics
--location=http://192.168.1.10/fedora/ --extra-args="console=xvc0
ip=192.168.1.100 netmask=255.255.255.0 gateway=192.168.1.1
dns=192.168.1.10 ks=http://192.168.1.10/fedora/ks.cfg "
but error occured while installing domainU.
Messages is as following.
| Exception Occurred
| Traceback (most recent call first):
| File "/usr/lib/anaconda/text.py", line 510, in run
| if anaconda.isKickstart and not anaconda.id.instClass.ksdata.interactive:
| File "/usr/bin/anaconda", line 955, in
| <module>
| anaconda.intf.run(anaconda)
| AttributeError: DefaultInstall instance
| has no attribute 'ksdata'
If I don't use kickstart file , setup completed.
I think that it is no problem in kickstart file(ks.cfg).
If you have any infomation about this case, let me know detail.
ks.cfg
# Kickstart file automatically generated by anaconda.
install
url --url http://192.168.1.10/fedora/
lang ja_JP.UTF-8
network --device eth0 --bootproto static --ip 192.168.1.100 --netmask
255.255.255.0 --gateway 192.168.1.1 --nameserver 192.168.1.10
--hostname host1.e-uematsu.net
rootpw --iscrypted $1$o69YV.yo$rMQTUwIz1CH6HZXlfkQ8Y0
firewall --enabled --port=22:tcp
authconfig --enableshadow --enablemd5
selinux --enforcing
timezone Asia/Tokyo
bootloader --location=mbr --driveorder=xvda --append="console=xvc0"
# The following is the partition information you requested
# Note that any partitions you deleted are not expressed
# here so unless you clear all partitions first, this is
# not guaranteed to work
clearpart --linux --drives=xvda
part /boot --fstype ext3 --size=100 --ondisk=xvda
part pv.2 --size=0 --grow --ondisk=xvda
volgroup VolGroup00 --pesize=32768 pv.2
logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00
--size=272 --grow --maxsize=544
logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=1024 --grow
%packages
@admin-tools
@editors
@japanese-support
@text-internet
@core
@base
@hardware-support
pax
---
Takeshi Uematsu.
16 years, 6 months
domU fail to start with error Error: Device 0 (vif) could not be connected. /etc/xen/scripts/vif-route
by Asrai khn
We have recently upgraded our dom0 to fedora 7 and it was working fine from
last couple of days, today on of domU crashed and when i tries to start it
fails at error ...
xm create -c /etc/xen/vm3.cfg
Error: Device 0 (vif) could not be connected. /etc/xen/scripts/vif-route
failed
in end i have rebooted the host (dom0) and all vms started fine. We never
got this sort of problem at FC6.
Any help in this regards will be highly appreciated.
Askar.
16 years, 6 months
Follow up to "No agpgart? What?"
by Rick Stevens
Rich Jones offered to post this for me (because I sent it to him
directly by accident). However, I'll post it myself.
On Tue, 2007-10-16 at 16:21 +0100, Richard W.M. Jones wrote:
> Rick Stevens wrote:
> > Hi, gang. I'm trying to get an F7-based Xen dom0 running on my
laptop
> > (so I can run the "Dark Lord's" Vista as a domU). The laptop is an
> > HP dv6000 with an Intel Duo Core proc and has the Intel graphics
> > chipset.
> >
> > It all works well under F7, but the xen kernel doesn't create the
> > agpgart devices as witnessed by the Xorg.0.log:
> >
> > (EE) GARTInit: Unable to open /dev/agpgart (No such file or
directory)
> > (WW) intel(0): /dev/agpgart is either not available, or no memory is
> > available
> > for allocation. Using pre-allocated memory only.
> >
> > and hence, I can't use X (which makes Xen fairly useless to me).
This
> > is a fully updated F7. Relevant modules:
>
> So X doesn't start? Can you post the full Xorg logfile please.
Attached below, and I apologize for the length of the post, gang!
-------------------------- CUT HERE ------------------------------
X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Fedora Core 7 Red Hat, Inc.
Current Operating System: Linux golem3.ssssc.com 2.6.20-2936.fc7xen #1
SMP Fri Sep 21 11:56:20 EDT 2007 x86_64
Build Date: 11 June 2007
Build ID: xorg-x11-server 1.3.0.0-9.fc7
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Oct 10 16:15:45 2007
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Videocard0"
(WW) No monitor specified for screen "Screen0".
Using a default monitor configuration.
(**) |-->Input Device "Keyboard0"
(**) |-->Input Device "Synaptics"
(II) No default mouse found, adding one
(**) |-->Input Device "<default pointer>"
(WW) No FontPath specified. Using compiled-in default.
(==) FontPath set to:
unix/:7100,
built-ins
(==) RgbPath set to "/usr/share/X11/rgb"
(==) ModulePath set to "/usr/lib64/xorg/modules"
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or
directory)
(II) No APM support in BIOS or kernel
(II) Loader magic: 0x7be760
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.3
X.Org Video Driver: 1.2
X.Org XInput driver : 0.7
X.Org Server Extension : 0.3
X.Org Font Renderer : 0.5
(II) Loader running on linux
(II) LoadModule: "pcidata"
(II) Loading /usr/lib64/xorg/modules//libpcidata.so
(II) Module pcidata: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.2
(++) using VT number 7
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 8086,2a00 card 103c,30cc rev 0c class 06,00,00
hdr 00
(II) PCI: 00:02:0: chip 8086,2a02 card 103c,30cc rev 0c class 03,00,00
hdr 80
(II) PCI: 00:02:1: chip 8086,2a03 card 103c,30cc rev 0c class 03,80,00
hdr 80
(II) PCI: 00:1a:0: chip 8086,2834 card 103c,30cc rev 03 class 0c,03,00
hdr 80
(II) PCI: 00:1a:1: chip 8086,2835 card 103c,30cc rev 03 class 0c,03,00
hdr 00
(II) PCI: 00:1a:7: chip 8086,283a card 103c,30cc rev 03 class 0c,03,20
hdr 00
(II) PCI: 00:1b:0: chip 8086,284b card 103c,30cc rev 03 class 04,03,00
hdr 00
(II) PCI: 00:1c:0: chip 8086,283f card 0000,0000 rev 03 class 06,04,00
hdr 81
(II) PCI: 00:1c:1: chip 8086,2841 card 0000,0000 rev 03 class 06,04,00
hdr 81
(II) PCI: 00:1c:5: chip 8086,2849 card 0000,0000 rev 03 class 06,04,00
hdr 81
(II) PCI: 00:1d:0: chip 8086,2830 card 103c,30cc rev 03 class 0c,03,00
hdr 80
(II) PCI: 00:1d:1: chip 8086,2831 card 103c,30cc rev 03 class 0c,03,00
hdr 00
(II) PCI: 00:1d:2: chip 8086,2832 card 103c,30cc rev 03 class 0c,03,00
hdr 00
(II) PCI: 00:1d:7: chip 8086,2836 card 103c,30cc rev 03 class 0c,03,20
hdr 00
(II) PCI: 00:1e:0: chip 8086,2448 card 0000,0000 rev f3 class 06,04,01
hdr 01
(II) PCI: 00:1f:0: chip 8086,2815 card 103c,30cc rev 03 class 06,01,00
hdr 80
(II) PCI: 00:1f:1: chip 8086,2850 card 103c,30cc rev 03 class 01,01,8a
hdr 00
(II) PCI: 00:1f:2: chip 8086,2829 card 103c,30cc rev 03 class 01,06,01
hdr 00
(II) PCI: 00:1f:3: chip 8086,283e card 103c,30cc rev 03 class 0c,05,00
hdr 00
(II) PCI: 02:00:0: chip 8086,4229 card 8086,1100 rev 61 class 02,80,00
hdr 00
(II) PCI: 06:00:0: chip 10ec,8136 card 103c,30cc rev 01 class 02,00,00
hdr 00
(II) PCI: 07:09:0: chip 1180,0832 card 103c,30cc rev 05 class 0c,00,10
hdr 80
(II) PCI: 07:09:1: chip 1180,0822 card 103c,30cc rev 22 class 08,05,00
hdr 80
(II) PCI: 07:09:2: chip 1180,0843 card 103c,30cc rev 12 class 08,80,00
hdr 80
(II) PCI: 07:09:3: chip 1180,0592 card 103c,30cc rev 12 class 08,80,00
hdr 80
(II) PCI: 07:09:4: chip 1180,0852 card 103c,30cc rev 12 class 08,80,00
hdr 80
(II) PCI: End of PCI scan
(II) Intel Bridge workaround enabled
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (0,0,7), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 0 I/O range:
[0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) Bus 0 non-prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x100000000) MX[B]
(II) Bus 0 prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x100000000) MX[B]
(II) PCI-to-PCI bridge:
(II) Bus 2: bridge is at (0:28:0), (0,2,3), BCTRL: 0x0004 (VGA_EN is
cleared)
(II) Bus 2 non-prefetchable memory range:
[0] -1 0 0xf8200000 - 0xf82fffff (0x100000) MX[B]
(II) PCI-to-PCI bridge:
(II) Bus 4: bridge is at (0:28:1), (0,4,5), BCTRL: 0x0004 (VGA_EN is
cleared)
(II) Bus 4 I/O range:
[0] -1 0 0x00002000 - 0x000020ff (0x100) IX[B]
[1] -1 0 0x00002400 - 0x000024ff (0x100) IX[B]
[2] -1 0 0x00002800 - 0x000028ff (0x100) IX[B]
[3] -1 0 0x00002c00 - 0x00002cff (0x100) IX[B]
(II) Bus 4 non-prefetchable memory range:
[0] -1 0 0xf4000000 - 0xf7ffffff (0x4000000) MX[B]
(II) Bus 4 prefetchable memory range:
[0] -1 0 0xf0000000 - 0xf3ffffff (0x4000000) MX[B]
(II) PCI-to-PCI bridge:
(II) Bus 6: bridge is at (0:28:5), (0,6,6), BCTRL: 0x0004 (VGA_EN is
cleared)
(II) Bus 6 I/O range:
[0] -1 0 0x00003000 - 0x000030ff (0x100) IX[B]
[1] -1 0 0x00003400 - 0x000034ff (0x100) IX[B]
[2] -1 0 0x00003800 - 0x000038ff (0x100) IX[B]
[3] -1 0 0x00003c00 - 0x00003cff (0x100) IX[B]
(II) Bus 6 non-prefetchable memory range:
[0] -1 0 0xf8300000 - 0xf83fffff (0x100000) MX[B]
(II) Bus 6 prefetchable memory range:
[0] -1 0 0x88000000 - 0x880fffff (0x100000) MX[B]
(II) Subtractive PCI-to-PCI bridge:
(II) Bus 7: bridge is at (0:30:0), (0,7,7), BCTRL: 0x0004 (VGA_EN is
cleared)
(II) Bus 7 non-prefetchable memory range:
[0] -1 0 0xf8400000 - 0xf84fffff (0x100000) MX[B]
(II) PCI-to-ISA bridge:
(II) Bus -1: bridge is at (0:31:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is
set)
(--) PCI:*(0:2:0) Intel Corporation Mobile Integrated Graphics
Controller rev 12, Mem @ 0xf8000000/20, 0xd0000000/28, I/O @ 0x1800/3
(--) PCI: (0:2:1) Intel Corporation Mobile Integrated Graphics
Controller rev 12, Mem @ 0xf8100000/20
(II) Addressable bus resource ranges are
[0] -1 0 0x00000000 - 0xffffffff (0x100000000) MX[B]
[1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) OS-reported resource ranges:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
(II) Active PCI resource ranges:
[0] -1 0 0xf8401400 - 0xf84014ff (0x100) MX[B]
[1] -1 0 0xf8401000 - 0xf84010ff (0x100) MX[B]
[2] -1 0 0xf8400c00 - 0xf8400cff (0x100) MX[B]
[3] -1 0 0xf8400800 - 0xf84008ff (0x100) MX[B]
[4] -1 0 0xf8400000 - 0xf84007ff (0x800) MX[B]
[5] -1 0 0xf8300000 - 0xf8300fff (0x1000) MX[B]
[6] -1 0 0xf8200000 - 0xf8201fff (0x2000) MX[B]
[7] -1 0 0x88100000 - 0x881000ff (0x100) MX[B]
[8] -1 0 0xf8704000 - 0xf87047ff (0x800) MX[B]
[9] -1 0 0xf8704c00 - 0xf8704fff (0x400) MX[B]
[10] -1 0 0xf8700000 - 0xf8703fff (0x4000) MX[B]
[11] -1 0 0xf8704800 - 0xf8704bff (0x400) MX[B]
[12] -1 0 0xf8100000 - 0xf81fffff (0x100000) MX[B](B)
[13] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B)
[14] -1 0 0xf8000000 - 0xf80fffff (0x100000) MX[B](B)
[15] -1 0 0x00003000 - 0x000030ff (0x100) IX[B]
[16] -1 0 0x00001c20 - 0x00001c3f (0x20) IX[B]
[17] -1 0 0x000018e0 - 0x000018ff (0x20) IX[B]
[18] -1 0 0x000018d0 - 0x000018d3 (0x4) IX[B]
[19] -1 0 0x000018d8 - 0x000018df (0x8) IX[B]
[20] -1 0 0x000018d4 - 0x000018d7 (0x4) IX[B]
[21] -1 0 0x00001c00 - 0x00001c07 (0x8) IX[B]
[22] -1 0 0x00001810 - 0x0000181f (0x10) IX[B]
[23] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B]
[24] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B]
[25] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B]
[26] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B]
[27] -1 0 0x000018a0 - 0x000018bf (0x20) IX[B]
[28] -1 0 0x00001880 - 0x0000189f (0x20) IX[B]
[29] -1 0 0x00001860 - 0x0000187f (0x20) IX[B]
[30] -1 0 0x00001840 - 0x0000185f (0x20) IX[B]
[31] -1 0 0x00001820 - 0x0000183f (0x20) IX[B]
[32] -1 0 0x00001800 - 0x00001807 (0x8) IX[B](B)
(II) Active PCI resource ranges after removing overlaps:
[0] -1 0 0xf8401400 - 0xf84014ff (0x100) MX[B]
[1] -1 0 0xf8401000 - 0xf84010ff (0x100) MX[B]
[2] -1 0 0xf8400c00 - 0xf8400cff (0x100) MX[B]
[3] -1 0 0xf8400800 - 0xf84008ff (0x100) MX[B]
[4] -1 0 0xf8400000 - 0xf84007ff (0x800) MX[B]
[5] -1 0 0xf8300000 - 0xf8300fff (0x1000) MX[B]
[6] -1 0 0xf8200000 - 0xf8201fff (0x2000) MX[B]
[7] -1 0 0x88100000 - 0x881000ff (0x100) MX[B]
[8] -1 0 0xf8704000 - 0xf87047ff (0x800) MX[B]
[9] -1 0 0xf8704c00 - 0xf8704fff (0x400) MX[B]
[10] -1 0 0xf8700000 - 0xf8703fff (0x4000) MX[B]
[11] -1 0 0xf8704800 - 0xf8704bff (0x400) MX[B]
[12] -1 0 0xf8100000 - 0xf81fffff (0x100000) MX[B](B)
[13] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B)
[14] -1 0 0xf8000000 - 0xf80fffff (0x100000) MX[B](B)
[15] -1 0 0x00003000 - 0x000030ff (0x100) IX[B]
[16] -1 0 0x00001c20 - 0x00001c3f (0x20) IX[B]
[17] -1 0 0x000018e0 - 0x000018ff (0x20) IX[B]
[18] -1 0 0x000018d0 - 0x000018d3 (0x4) IX[B]
[19] -1 0 0x000018d8 - 0x000018df (0x8) IX[B]
[20] -1 0 0x000018d4 - 0x000018d7 (0x4) IX[B]
[21] -1 0 0x00001c00 - 0x00001c07 (0x8) IX[B]
[22] -1 0 0x00001810 - 0x0000181f (0x10) IX[B]
[23] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B]
[24] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B]
[25] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B]
[26] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B]
[27] -1 0 0x000018a0 - 0x000018bf (0x20) IX[B]
[28] -1 0 0x00001880 - 0x0000189f (0x20) IX[B]
[29] -1 0 0x00001860 - 0x0000187f (0x20) IX[B]
[30] -1 0 0x00001840 - 0x0000185f (0x20) IX[B]
[31] -1 0 0x00001820 - 0x0000183f (0x20) IX[B]
[32] -1 0 0x00001800 - 0x00001807 (0x8) IX[B](B)
(II) OS-reported resource ranges after removing overlaps with PCI:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
(II) All system resource ranges:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xf8401400 - 0xf84014ff (0x100) MX[B]
[5] -1 0 0xf8401000 - 0xf84010ff (0x100) MX[B]
[6] -1 0 0xf8400c00 - 0xf8400cff (0x100) MX[B]
[7] -1 0 0xf8400800 - 0xf84008ff (0x100) MX[B]
[8] -1 0 0xf8400000 - 0xf84007ff (0x800) MX[B]
[9] -1 0 0xf8300000 - 0xf8300fff (0x1000) MX[B]
[10] -1 0 0xf8200000 - 0xf8201fff (0x2000) MX[B]
[11] -1 0 0x88100000 - 0x881000ff (0x100) MX[B]
[12] -1 0 0xf8704000 - 0xf87047ff (0x800) MX[B]
[13] -1 0 0xf8704c00 - 0xf8704fff (0x400) MX[B]
[14] -1 0 0xf8700000 - 0xf8703fff (0x4000) MX[B]
[15] -1 0 0xf8704800 - 0xf8704bff (0x400) MX[B]
[16] -1 0 0xf8100000 - 0xf81fffff (0x100000) MX[B](B)
[17] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B)
[18] -1 0 0xf8000000 - 0xf80fffff (0x100000) MX[B](B)
[19] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[20] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[21] -1 0 0x00003000 - 0x000030ff (0x100) IX[B]
[22] -1 0 0x00001c20 - 0x00001c3f (0x20) IX[B]
[23] -1 0 0x000018e0 - 0x000018ff (0x20) IX[B]
[24] -1 0 0x000018d0 - 0x000018d3 (0x4) IX[B]
[25] -1 0 0x000018d8 - 0x000018df (0x8) IX[B]
[26] -1 0 0x000018d4 - 0x000018d7 (0x4) IX[B]
[27] -1 0 0x00001c00 - 0x00001c07 (0x8) IX[B]
[28] -1 0 0x00001810 - 0x0000181f (0x10) IX[B]
[29] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B]
[30] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B]
[31] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B]
[32] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B]
[33] -1 0 0x000018a0 - 0x000018bf (0x20) IX[B]
[34] -1 0 0x00001880 - 0x0000189f (0x20) IX[B]
[35] -1 0 0x00001860 - 0x0000187f (0x20) IX[B]
[36] -1 0 0x00001840 - 0x0000185f (0x20) IX[B]
[37] -1 0 0x00001820 - 0x0000183f (0x20) IX[B]
[38] -1 0 0x00001800 - 0x00001807 (0x8) IX[B](B)
(II) LoadModule: "vnc"
(II) Loading /usr/lib64/xorg/modules/extensions//libvnc.so
(II) Module vnc: vendor="RealVNC Ltd"
compiled for 4.3.99.902, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension VNC
(II) LoadModule: "intel"
(II) Loading /usr/lib64/xorg/modules/drivers//intel_drv.so
(II) Module intel: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 2.0.0
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 1.2
(II) LoadModule: "kbd"
(II) Loading /usr/lib64/xorg/modules/input//kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.1.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.6
(II) LoadModule: "synaptics"
(II) Loading /usr/lib64/xorg/modules/input//synaptics_drv.so
(II) Module synaptics: vendor="X.Org Foundation"
compiled for 4.3.99.902, module version = 1.0.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.6
(II) LoadModule: "mouse"
(II) Loading /usr/lib64/xorg/modules/input//mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.1.1
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.6
(II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G,
E7221 (i915), 915GM, 945G, 945GM, 945GME, 965G, 965G, 965Q,
946GZ,
965GM, 965GME/GLE, G33, Q35, Q33
(II) Primary Device is: PCI 00:02:0
(--) Assigning device section with no busID to primary device
(WW) intel: No matching Device section for instance (BusID PCI:0:2:1)
found
(--) Chipset 965GM found
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xf8401400 - 0xf84014ff (0x100) MX[B]
[5] -1 0 0xf8401000 - 0xf84010ff (0x100) MX[B]
[6] -1 0 0xf8400c00 - 0xf8400cff (0x100) MX[B]
[7] -1 0 0xf8400800 - 0xf84008ff (0x100) MX[B]
[8] -1 0 0xf8400000 - 0xf84007ff (0x800) MX[B]
[9] -1 0 0xf8300000 - 0xf8300fff (0x1000) MX[B]
[10] -1 0 0xf8200000 - 0xf8201fff (0x2000) MX[B]
[11] -1 0 0x88100000 - 0x881000ff (0x100) MX[B]
[12] -1 0 0xf8704000 - 0xf87047ff (0x800) MX[B]
[13] -1 0 0xf8704c00 - 0xf8704fff (0x400) MX[B]
[14] -1 0 0xf8700000 - 0xf8703fff (0x4000) MX[B]
[15] -1 0 0xf8704800 - 0xf8704bff (0x400) MX[B]
[16] -1 0 0xf8100000 - 0xf81fffff (0x100000) MX[B](B)
[17] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B)
[18] -1 0 0xf8000000 - 0xf80fffff (0x100000) MX[B](B)
[19] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[20] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[21] -1 0 0x00003000 - 0x000030ff (0x100) IX[B]
[22] -1 0 0x00001c20 - 0x00001c3f (0x20) IX[B]
[23] -1 0 0x000018e0 - 0x000018ff (0x20) IX[B]
[24] -1 0 0x000018d0 - 0x000018d3 (0x4) IX[B]
[25] -1 0 0x000018d8 - 0x000018df (0x8) IX[B]
[26] -1 0 0x000018d4 - 0x000018d7 (0x4) IX[B]
[27] -1 0 0x00001c00 - 0x00001c07 (0x8) IX[B]
[28] -1 0 0x00001810 - 0x0000181f (0x10) IX[B]
[29] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B]
[30] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B]
[31] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B]
[32] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B]
[33] -1 0 0x000018a0 - 0x000018bf (0x20) IX[B]
[34] -1 0 0x00001880 - 0x0000189f (0x20) IX[B]
[35] -1 0 0x00001860 - 0x0000187f (0x20) IX[B]
[36] -1 0 0x00001840 - 0x0000185f (0x20) IX[B]
[37] -1 0 0x00001820 - 0x0000183f (0x20) IX[B]
[38] -1 0 0x00001800 - 0x00001807 (0x8) IX[B](B)
(II) resource ranges after probing:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xf8401400 - 0xf84014ff (0x100) MX[B]
[5] -1 0 0xf8401000 - 0xf84010ff (0x100) MX[B]
[6] -1 0 0xf8400c00 - 0xf8400cff (0x100) MX[B]
[7] -1 0 0xf8400800 - 0xf84008ff (0x100) MX[B]
[8] -1 0 0xf8400000 - 0xf84007ff (0x800) MX[B]
[9] -1 0 0xf8300000 - 0xf8300fff (0x1000) MX[B]
[10] -1 0 0xf8200000 - 0xf8201fff (0x2000) MX[B]
[11] -1 0 0x88100000 - 0x881000ff (0x100) MX[B]
[12] -1 0 0xf8704000 - 0xf87047ff (0x800) MX[B]
[13] -1 0 0xf8704c00 - 0xf8704fff (0x400) MX[B]
[14] -1 0 0xf8700000 - 0xf8703fff (0x4000) MX[B]
[15] -1 0 0xf8704800 - 0xf8704bff (0x400) MX[B]
[16] -1 0 0xf8100000 - 0xf81fffff (0x100000) MX[B](B)
[17] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B)
[18] -1 0 0xf8000000 - 0xf80fffff (0x100000) MX[B](B)
[19] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B]
[20] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B]
[21] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B]
[22] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[23] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[24] -1 0 0x00003000 - 0x000030ff (0x100) IX[B]
[25] -1 0 0x00001c20 - 0x00001c3f (0x20) IX[B]
[26] -1 0 0x000018e0 - 0x000018ff (0x20) IX[B]
[27] -1 0 0x000018d0 - 0x000018d3 (0x4) IX[B]
[28] -1 0 0x000018d8 - 0x000018df (0x8) IX[B]
[29] -1 0 0x000018d4 - 0x000018d7 (0x4) IX[B]
[30] -1 0 0x00001c00 - 0x00001c07 (0x8) IX[B]
[31] -1 0 0x00001810 - 0x0000181f (0x10) IX[B]
[32] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B]
[33] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B]
[34] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B]
[35] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B]
[36] -1 0 0x000018a0 - 0x000018bf (0x20) IX[B]
[37] -1 0 0x00001880 - 0x0000189f (0x20) IX[B]
[38] -1 0 0x00001860 - 0x0000187f (0x20) IX[B]
[39] -1 0 0x00001840 - 0x0000185f (0x20) IX[B]
[40] -1 0 0x00001820 - 0x0000183f (0x20) IX[B]
[41] -1 0 0x00001800 - 0x00001807 (0x8) IX[B](B)
[42] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B]
[43] 0 0 0x000003c0 - 0x000003df (0x20) IS[B]
(II) Setting vga for screen 0.
(II) Enabling PCI device
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Loading /usr/lib64/xorg/modules//libint10.so
(II) Module int10: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.2
(II) Loading sub module "vbe"
(II) LoadModule: "vbe"
(II) Loading /usr/lib64/xorg/modules//libvbe.so
(II) Module vbe: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.1.0
ABI class: X.Org Video Driver, version 1.2
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/lib64/xorg/modules//libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 0.1.0
ABI class: X.Org Video Driver, version 1.2
(**) intel(0): Depth 24, (--) framebuffer bpp 32
(==) intel(0): RGB weight 888
(==) intel(0): Default visual is TrueColor
(II) intel(0): Integrated Graphics Chipset: Intel(R) 965GM
(--) intel(0): Chipset: "965GM"
(--) intel(0): Linear framebuffer at 0xD0000000
(--) intel(0): IO registers at addr 0xF8000000
(II) intel(0): 2 display pipes available.
(==) intel(0): Using XAA for acceleration
(--) intel(0): Will try to allocate texture pool for old Mesa 3D driver.
(II) intel(0): Will try to reserve 32768 kiB of AGP aperture space
for the DRM memory manager.
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"(II) Module already built-in
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"(II) Module already built-in
(II) intel(0): Output VGA has no monitor section
(II) intel(0): I2C bus "CRTDDC_A" initialized.
(II) intel(0): Output LVDS has no monitor section
(II) intel(0): I2C bus "LVDSDDC_C" initialized.
(II) intel(0): I2C device "LVDSDDC_C:ddc2" registered at address 0xA0.
(II) intel(0): I2C device "LVDSDDC_C:ddc2" removed.
(II) intel(0): EDID for output LVDS
(II) intel(0): Manufacturer: SEC Model: 3345 Serial#: 0
(II) intel(0): Year: 2004 Week: 0
(II) intel(0): EDID Version: 1.3
(II) intel(0): Digital Display Input
(II) intel(0): Max H-Image Size [cm]: horiz.: 33 vert.: 21
(II) intel(0): Gamma: 2.20
(II) intel(0): No DPMS capabilities specified; RGB/Color Display
(II) intel(0): First detailed timing is preferred mode
(II) intel(0): redX: 0.580 redY: 0.340 greenX: 0.310 greenY: 0.550
(II) intel(0): blueX: 0.155 blueY: 0.155 whiteX: 0.313 whiteY: 0.329
(II) intel(0): Manufacturer's mask: 0
(II) intel(0): Supported additional Video Mode:
(II) intel(0): clock: 68.9 MHz Image Size: 331 x 207 mm
(II) intel(0): h_active: 1280 h_sync: 1296 h_sync_end 1344 h_blank_end
1408 h_border: 0
(II) intel(0): v_active: 800 v_sync: 801 v_sync_end 804 v_blanking:
816 v_border: 0
(II) intel(0): SAMSUNG
(II) intel(0): LTN154X3-L01
(II) intel(0): EDID (in hex):
(II) intel(0): 00ffffffffffff004ca3453300000000
(II) intel(0): 000e0103802115780a87f594574f8c27
(II) intel(0): 27505400000001010101010101010101
(II) intel(0): 010101010101ee1a0080502010301030
(II) intel(0): 13004bcf100000190000000f00000000
(II) intel(0): 00000000002387026401000000fe0053
(II) intel(0): 414d53554e470a2020202020000000fe
(II) intel(0): 004c544e31353458332d4c30310a0068
(II) intel(0): EDID vendor "SEC", prod id 13125
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Reloading /usr/lib64/xorg/modules//libint10.so
(II) intel(0): initializing int10
(WW) intel(0): Bad V_BIOS checksum
(II) intel(0): Primary V_BIOS segment is: 0xc000
(II) intel(0): VESA BIOS detected
(II) intel(0): VESA VBE Version 3.0
(II) intel(0): VESA VBE Total Mem: 7616 kB
(II) intel(0): VESA VBE OEM: Intel(r)Crestline Graphics Chip Accelerated
VGA BIOS
(II) intel(0): VESA VBE OEM Software Rev: 1.0
(II) intel(0): VESA VBE OEM Vendor: Intel Corporation
(II) intel(0): VESA VBE OEM Product: Intel(r)Crestline Graphics
Controller
(II) intel(0): VESA VBE OEM Product Rev: Hardware Version 0.0
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOB" initialized.
(II) intel(0): I2C device "SDVOCTRL_E for SDVOB:SDVO Controller B"
registered at address 0x70.
(II) intel(0): No SDVO device found on SDVOB
(II) intel(0): I2C device "SDVOCTRL_E for SDVOB:SDVO Controller B"
removed.
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOB" removed.
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOC" initialized.
(II) intel(0): I2C device "SDVOCTRL_E for SDVOC:SDVO Controller C"
registered at address 0x72.
(II) intel(0): No SDVO device found on SDVOC
(II) intel(0): I2C device "SDVOCTRL_E for SDVOC:SDVO Controller C"
removed.
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOC" removed.
(II) intel(0): Output TV has no monitor section
(II) intel(0): Output VGA disconnected
(II) intel(0): EDID for output VGA
(II) intel(0): Output LVDS connected
(II) intel(0): I2C device "LVDSDDC_C:ddc2" registered at address 0xA0.
(II) intel(0): I2C device "LVDSDDC_C:ddc2" removed.
(II) intel(0): EDID for output LVDS
(II) intel(0): Manufacturer: SEC Model: 3345 Serial#: 0
(II) intel(0): Year: 2004 Week: 0
(II) intel(0): EDID Version: 1.3
(II) intel(0): Digital Display Input
(II) intel(0): Max H-Image Size [cm]: horiz.: 33 vert.: 21
(II) intel(0): Gamma: 2.20
(II) intel(0): No DPMS capabilities specified; RGB/Color Display
(II) intel(0): First detailed timing is preferred mode
(II) intel(0): redX: 0.580 redY: 0.340 greenX: 0.310 greenY: 0.550
(II) intel(0): blueX: 0.155 blueY: 0.155 whiteX: 0.313 whiteY: 0.329
(II) intel(0): Manufacturer's mask: 0
(II) intel(0): Supported additional Video Mode:
(II) intel(0): clock: 68.9 MHz Image Size: 331 x 207 mm
(II) intel(0): h_active: 1280 h_sync: 1296 h_sync_end 1344 h_blank_end
1408 h_border: 0
(II) intel(0): v_active: 800 v_sync: 801 v_sync_end 804 v_blanking:
816 v_border: 0
(II) intel(0): SAMSUNG
(II) intel(0): LTN154X3-L01
(II) intel(0): EDID (in hex):
(II) intel(0): 00ffffffffffff004ca3453300000000
(II) intel(0): 000e0103802115780a87f594574f8c27
(II) intel(0): 27505400000001010101010101010101
(II) intel(0): 010101010101ee1a0080502010301030
(II) intel(0): 13004bcf100000190000000f00000000
(II) intel(0): 00000000002387026401000000fe0053
(II) intel(0): 414d53554e470a2020202020000000fe
(II) intel(0): 004c544e31353458332d4c30310a0068
(II) intel(0): EDID vendor "SEC", prod id 13125
(II) intel(0): Not using default mode "640x350" (vrefresh out of range)
(II) intel(0): Not using default mode "640x400" (vrefresh out of range)
(II) intel(0): Not using default mode "720x400" (vrefresh out of range)
(II) intel(0): Not using default mode "640x480" (vrefresh out of range)
(II) intel(0): Not using default mode "640x480" (vrefresh out of range)
(II) intel(0): Not using default mode "640x480" (vrefresh out of range)
(II) intel(0): Not using default mode "800x600" (vrefresh out of range)
(II) intel(0): Not using default mode "800x600" (vrefresh out of range)
(II) intel(0): Not using default mode "800x600" (vrefresh out of range)
(II) intel(0): Not using default mode "800x600" (vrefresh out of range)
(II) intel(0): Not using default mode "1024x768" (vrefresh out of range)
(II) intel(0): Not using default mode "1024x768" (vrefresh out of range)
(II) intel(0): Not using default mode "1024x768" (vrefresh out of range)
(II) intel(0): Not using default mode "1152x864" (vrefresh out of range)
(II) intel(0): Not using default mode "1280x960" (hsync out of range)
(II) intel(0): Not using default mode "1280x960" (vrefresh out of range)
(II) intel(0): Not using default mode "1280x1024" (hsync out of range)
(II) intel(0): Not using default mode "1280x1024" (vrefresh out of
range)
(II) intel(0): Not using default mode "1280x1024" (vrefresh out of
range)
(II) intel(0): Not using default mode "1600x1200" (hsync out of range)
(II) intel(0): Not using default mode "1600x1200" (vrefresh out of
range)
(II) intel(0): Not using default mode "1600x1200" (vrefresh out of
range)
(II) intel(0): Not using default mode "1600x1200" (vrefresh out of
range)
(II) intel(0): Not using default mode "1600x1200" (vrefresh out of
range)
(II) intel(0): Not using default mode "1792x1344" (hsync out of range)
(II) intel(0): Not using default mode "1792x1344" (vrefresh out of
range)
(II) intel(0): Not using default mode "1856x1392" (hsync out of range)
(II) intel(0): Not using default mode "1856x1392" (vrefresh out of
range)
(II) intel(0): Not using default mode "1920x1440" (hsync out of range)
(II) intel(0): Not using default mode "1920x1440" (vrefresh out of
range)
(II) intel(0): Not using default mode "832x624" (vrefresh out of range)
(II) intel(0): Not using default mode "1152x768" (vrefresh out of range)
(II) intel(0): Not using default mode "1152x864" (exceeds panel
dimensions)
(II) intel(0): Not using default mode "1152x864" (vrefresh out of range)
(II) intel(0): Not using default mode "1152x864" (vrefresh out of range)
(II) intel(0): Not using default mode "1152x864" (vrefresh out of range)
(II) intel(0): Not using default mode "1152x864" (vrefresh out of range)
(II) intel(0): Not using default mode "1152x864" (vrefresh out of range)
(II) intel(0): Not using default mode "1280x720" (vrefresh out of range)
(II) intel(0): Not using default mode "1280x720" (vrefresh out of range)
(II) intel(0): Not using default mode "1280x720" (vrefresh out of range)
(II) intel(0): Not using default mode "1280x800" (vrefresh out of range)
(II) intel(0): Not using default mode "1280x800" (vrefresh out of range)
(II) intel(0): Not using default mode "1280x800" (vrefresh out of range)
(II) intel(0): Not using default mode "1280x768" (vrefresh out of range)
(II) intel(0): Not using default mode "1280x768" (vrefresh out of range)
(II) intel(0): Not using default mode "1280x768" (vrefresh out of range)
(II) intel(0): Not using default mode "1360x768" (exceeds panel
dimensions)
(II) intel(0): Not using default mode "1360x768" (exceeds panel
dimensions)
(II) intel(0): Not using default mode "1400x1050" (hsync out of range)
(II) intel(0): Not using default mode "1400x1050" (vrefresh out of
range)
(II) intel(0): Not using default mode "1400x1050" (vrefresh out of
range)
(II) intel(0): Not using default mode "1400x1050" (vrefresh out of
range)
(II) intel(0): Not using default mode "1400x1050" (vrefresh out of
range)
(II) intel(0): Not using default mode "1400x1050" (vrefresh out of
range)
(II) intel(0): Not using default mode "1440x900" (hsync out of range)
(II) intel(0): Not using default mode "1600x1024" (hsync out of range)
(II) intel(0): Not using default mode "1680x1050" (hsync out of range)
(II) intel(0): Not using default mode "1680x1050" (hsync out of range)
(II) intel(0): Not using default mode "1680x1050" (vrefresh out of
range)
(II) intel(0): Not using default mode "1680x1050" (vrefresh out of
range)
(II) intel(0): Not using default mode "1680x1050" (vrefresh out of
range)
(II) intel(0): Not using default mode "1920x1080" (hsync out of range)
(II) intel(0): Not using default mode "1920x1080" (hsync out of range)
(II) intel(0): Not using default mode "1920x1080" (vrefresh out of
range)
(II) intel(0): Not using default mode "1920x1080" (vrefresh out of
range)
(II) intel(0): Not using default mode "1920x1080" (vrefresh out of
range)
(II) intel(0): Not using default mode "1920x1200" (hsync out of range)
(II) intel(0): Not using default mode "1920x1200" (hsync out of range)
(II) intel(0): Not using default mode "1920x1200" (vrefresh out of
range)
(II) intel(0): Not using default mode "1920x1200" (vrefresh out of
range)
(II) intel(0): Not using default mode "1920x1200" (vrefresh out of
range)
(II) intel(0): Not using default mode "1920x1200" (vrefresh out of
range)
(II) intel(0): Not using default mode "1920x1440" (vrefresh out of
range)
(II) intel(0): Not using default mode "2048x1536" (hsync out of range)
(II) intel(0): Not using default mode "2048x1536" (vrefresh out of
range)
(II) intel(0): Not using default mode "2048x1536" (vrefresh out of
range)
(II) intel(0): Not using default mode "2560x1600" (hsync out of range)
(II) intel(0): Printing probed modes for output LVDS
(II) intel(0): Modeline "1280x800"x60.0 68.94 1280 1296 1344 1408
800 801 804 816 -hsync -vsync (49.0 kHz)
(II) intel(0): Modeline "1280x800"x60.0 83.46 1280 1344 1480 1680
800 801 804 828 -hsync +vsync (49.7 kHz)
(II) intel(0): Modeline "1280x768"x60.0 80.14 1280 1344 1480 1680
768 769 772 795 -hsync +vsync (47.7 kHz)
(II) intel(0): Modeline "1280x720"x60.0 74.48 1280 1336 1472 1664
720 721 724 746 -hsync +vsync (44.8 kHz)
(II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344
768 771 777 806 -hsync -vsync (48.4 kHz)
(II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600
601 605 628 +hsync +vsync (37.9 kHz)
(II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490
492 525 -hsync -vsync (31.5 kHz)
(II) intel(0): Output TV disconnected
(II) intel(0): EDID for output TV
(II) intel(0): Output VGA disconnected
(II) intel(0): Output LVDS connected
(II) intel(0): Output TV disconnected
(II) intel(0): Output LVDS using initial mode 1280x800
(II) intel(0): Monitoring connected displays enabled
(II) intel(0): detected 512 kB GTT.
(II) intel(0): detected 7676 kB stolen memory.
(==) intel(0): video overlay key set to 0x101fe
(==) intel(0): Will not try to enable page flipping
(==) intel(0): Triple buffering disabled
(==) intel(0): Using gamma correction (1.0, 1.0, 1.0)
(==) intel(0): DPI set to (75, 75)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib64/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.3
(II) Loading sub module "xaa"
(II) LoadModule: "xaa"
(II) Loading /usr/lib64/xorg/modules//libxaa.so
(II) Module xaa: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.2.0
ABI class: X.Org Video Driver, version 1.2
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"(II) Module already built-in
(II) intel(0): Comparing regs from server start up to After PreInit
(==) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] 0 0 0xd0000000 - 0xdfffffff (0x10000000) MS[B]
[1] 0 0 0xf8000000 - 0xf80fffff (0x100000) MS[B]
[2] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[3] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[4] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[5] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[6] -1 0 0xf8401400 - 0xf84014ff (0x100) MX[B]
[7] -1 0 0xf8401000 - 0xf84010ff (0x100) MX[B]
[8] -1 0 0xf8400c00 - 0xf8400cff (0x100) MX[B]
[9] -1 0 0xf8400800 - 0xf84008ff (0x100) MX[B]
[10] -1 0 0xf8400000 - 0xf84007ff (0x800) MX[B]
[11] -1 0 0xf8300000 - 0xf8300fff (0x1000) MX[B]
[12] -1 0 0xf8200000 - 0xf8201fff (0x2000) MX[B]
[13] -1 0 0x88100000 - 0x881000ff (0x100) MX[B]
[14] -1 0 0xf8704000 - 0xf87047ff (0x800) MX[B]
[15] -1 0 0xf8704c00 - 0xf8704fff (0x400) MX[B]
[16] -1 0 0xf8700000 - 0xf8703fff (0x4000) MX[B]
[17] -1 0 0xf8704800 - 0xf8704bff (0x400) MX[B]
[18] -1 0 0xf8100000 - 0xf81fffff (0x100000) MX[B](B)
[19] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B)
[20] -1 0 0xf8000000 - 0xf80fffff (0x100000) MX[B](B)
[21] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B](OprD)
[22] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprD)
[23] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprD)
[24] 0 0 0x00001800 - 0x00001807 (0x8) IS[B]
[25] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[26] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[27] -1 0 0x00003000 - 0x000030ff (0x100) IX[B]
[28] -1 0 0x00001c20 - 0x00001c3f (0x20) IX[B]
[29] -1 0 0x000018e0 - 0x000018ff (0x20) IX[B]
[30] -1 0 0x000018d0 - 0x000018d3 (0x4) IX[B]
[31] -1 0 0x000018d8 - 0x000018df (0x8) IX[B]
[32] -1 0 0x000018d4 - 0x000018d7 (0x4) IX[B]
[33] -1 0 0x00001c00 - 0x00001c07 (0x8) IX[B]
[34] -1 0 0x00001810 - 0x0000181f (0x10) IX[B]
[35] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B]
[36] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B]
[37] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B]
[38] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B]
[39] -1 0 0x000018a0 - 0x000018bf (0x20) IX[B]
[40] -1 0 0x00001880 - 0x0000189f (0x20) IX[B]
[41] -1 0 0x00001860 - 0x0000187f (0x20) IX[B]
[42] -1 0 0x00001840 - 0x0000185f (0x20) IX[B]
[43] -1 0 0x00001820 - 0x0000183f (0x20) IX[B]
[44] -1 0 0x00001800 - 0x00001807 (0x8) IX[B](B)
[45] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU)
[46] 0 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU)
(EE) GARTInit: Unable to open /dev/agpgart (No such file or directory)
(WW) intel(0): /dev/agpgart is either not available, or no memory is
available
for allocation. Using pre-allocated memory only.
(==) intel(0): VideoRam: 7676 KB
(EE) intel(0): [dri] I830CheckDRIAvailable failed: glx not loaded
(II) intel(0): Allocating 255 scanlines for pixmap cache
(EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too
low?
(EE) intel(0): Couldn't allocate video memory
Fatal server error:
AddScreen/ScreenInit failed for driver 0
-------------------------- CUT HERE ------------------------------
----------------------------------------------------------------------
- Rick Stevens, Principal Engineer rstevens(a)internap.com -
- CDN Systems, Internap, Inc. http://www.internap.com -
- -
- Which is worse: ignorance or apathy? I don't know. Who cares? -
----------------------------------------------------------------------
16 years, 6 months
