Re: [XFree86] XFree86 freezes in minutes (was:Trident Blade, no screens)
Thanks. I think this is really a bit of a conundrum -- on my RH7.x system, Trident is mentioned in the XFree86 config file, and SiS is not. And on my RH9 system, running on the very same hardware, SiS is mentioned, and Trident is not. Both configurations seem to cause X to come up on the PCI video card. I haven't tried to max out the resolution on either RH7 or RH9, but both seem to support 1400x1050. I suspect this is impossible, and I must be failing to observe something. The crashing is the symptom I care more about, of course, and I will take your advice about the SiS drivers. But in the future, I will avoid like the plague motherboards with onboard video. Thanks again. -jmc David Dawes writes: On Fri, Nov 14, 2003 at 04:30:54AM -0800, John Chandler wrote: [...] Does anyone have an opinion as to whether the freezing I'm seeing is an XFree86 issue or something else? Does RH9 do this a lot? I'd consider hardware deficiencies, but when I boot my old RH 7.x on the exact same hardware (except different HD), it stays up for days, vs. minutes w/RH9 and the new XFree86. Adjusting the resolution to pathetically low doesn't fix it. Feel free to recommend that I have someone cut the traces to the onboard video, replace my motherboard, install SUSE, etc. I presume XFree86 is *the* X server at this point, but I'm even open to changing that if you think it would be an option -- I am stuck at RedHat 7.something until I get past this. Thanks, and I realize nobody's getting paid for the advice given here. All I can suggest is that you try the latest sis driver. Thomas has a very comprehensive web site for his driver http://www.winischhofer.net/linuxsisvga.shtml. You can download driver updates from there too. I don't have any sis hardware and I'm not familiar with the driver myself, so there isn't much more I can add. David -- David Dawes developer/release engineer The XFree86 Project www.XFree86.org/~dawes ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] XFree86 freezes in minutes (was:Trident Blade, no screens)
Oh. OK, well, maybe I will understand this stuff at some point and it will seem less like Vulcan magic. Nah, prob'ly not. :-/ Thanks again. -jmc David Dawes writes: On Sun, Nov 16, 2003 at 07:01:39PM -0800, John Chandler wrote: Thanks. I think this is really a bit of a conundrum -- on my RH7.x system, Trident is mentioned in the XFree86 config file, and Actually, for the old 3.3.x based config file you posted, there was nothing Trident specific other than strings that have no affect on which driver actually gets used. I don't think there's really any mystery there. David -- David Dawes developer/release engineer The XFree86 Project www.XFree86.org/~dawes ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] XFree86 freezes in minutes (was:Trident Blade, no screens)
I notice a deafening silence on this topic all of a sudden. Have I offended my hosts or become tiresome? Please accept my apologies. Does anyone have an opinion as to whether the freezing I'm seeing is an XFree86 issue or something else? Does RH9 do this a lot? I'd consider hardware deficiencies, but when I boot my old RH 7.x on the exact same hardware (except different HD), it stays up for days, vs. minutes w/RH9 and the new XFree86. Adjusting the resolution to pathetically low doesn't fix it. Feel free to recommend that I have someone cut the traces to the onboard video, replace my motherboard, install SUSE, etc. I presume XFree86 is *the* X server at this point, but I'm even open to changing that if you think it would be an option -- I am stuck at RedHat 7.something until I get past this. Thanks, and I realize nobody's getting paid for the advice given here. -jmc | Thomas Winischhofer writes: | John Chandler wrote: | (--) PCI:*(0:8:0) Silicon Integrated Systems [SiS] SiS300/305 PCI/AGP VGA Display Adapter rev 144, Mem @ 0xd000/27, 0xe000/17, I/O @ 0xdc00/7 | (--) PCI: (1:0:0) Trident Microsystems CyberBlade/i1 rev 106, Mem @ 0xdd80/23, 0xde00/17, 0xdd00/23 | | [...] |The monitor is not connected to the on-board video card, it is | | This is slightly OT: Is the SiS 300/305 really on-board? If so, what MB | is this? | | Is there any way to tell, other than just remembering or checking the | docs, in which case I'm hosed? | | BTW, it does appear that the add-on card is the SiS. That is, when I | reinstalled RedHat and told it I had an SiS, X did come up. It came | up in patheticaly low resolution and the system froze after about five | minutes, but it did come up. Any clue what the issue would be here? The resolution problem is fixable using a Gnome utility. But the machine still abruptly freezes after a short while -- five to ten minutes. Once it was when emacs had just come up, once it was when another app had painted the blank rectangle of a drop-down menu but had not filled in any of the menu panes. And it's utter lockup -- caps lock key doesn't make the LED come on. Any clue why I'd be seeing this, and more to the point, what I can do to fix it? Get a horse? I guess I'll try lowering the resolution and see if that changes anything. But my current desktop is 1400x1050 with the same card, and I'm sure I'm not setting the resolution on the new system any higher than that. -jmc ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Trident Blade, no screens
Thomas Winischhofer writes: John Chandler wrote: (--) PCI:*(0:8:0) Silicon Integrated Systems [SiS] SiS300/305 PCI/AGP VGA Display Adapter rev 144, Mem @ 0xd000/27, 0xe000/17, I/O @ 0xdc00/7 (--) PCI: (1:0:0) Trident Microsystems CyberBlade/i1 rev 106, Mem @ 0xdd80/23, 0xde00/17, 0xdd00/23 [...] The monitor is not connected to the on-board video card, it is This is slightly OT: Is the SiS 300/305 really on-board? If so, what MB is this? Is there any way to tell, other than just remembering or checking the docs, in which case I'm hosed? BTW, it does appear that the add-on card is the SiS. That is, when I reinstalled RedHat and told it I had an SiS, X did come up. It came up in patheticaly low resolution and the system froze after about five minutes, but it did come up. Any clue what the issue would be here? Someone mentioned that a log from my working, RH7.? installation would be helpful. Any idea where it lives? It doesn't seem to be in /var/log. I am becoming truly astounded at how difficult this is. I thank you for your help, though. -jmc ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Update re: [XFree86] Trident Blade, no screens
From: John Chandler [EMAIL PROTECTED] Subject: Re: [XFree86] Trident Blade, no screens | Thomas Winischhofer writes: | John Chandler wrote: | (--) PCI:*(0:8:0) Silicon Integrated Systems [SiS] SiS300/305 PCI/AGP VGA Display Adapter rev 144, Mem @ 0xd000/27, 0xe000/17, I/O @ 0xdc00/7 | (--) PCI: (1:0:0) Trident Microsystems CyberBlade/i1 rev 106, Mem @ 0xdd80/23, 0xde00/17, 0xdd00/23 | | [...] |The monitor is not connected to the on-board video card, it is | | This is slightly OT: Is the SiS 300/305 really on-board? If so, what MB | is this? | | Is there any way to tell, other than just remembering or checking the | docs, in which case I'm hosed? | | BTW, it does appear that the add-on card is the SiS. That is, when I | reinstalled RedHat and told it I had an SiS, X did come up. It came | up in patheticaly low resolution and the system froze after about five | minutes, but it did come up. Any clue what the issue would be here? The resolution problem is fixable using a Gnome utility. But the machine still abruptly freezes after a short while -- five to ten minutes. Once it was when emacs had just come up, once it was when another app had painted the blank rectangle of a drop-down menu but had not filled in any of the menu panes. And it's utter lockup -- caps lock key doesn't make the LED come on. Any clue why I'd be seeing this, and more to the point, what I can do to fix it? Get a horse? I guess I'll try lowering the resolution and see if that changes anything. But my current desktop is 1400x1050 with the same card, and I'm sure I'm not setting the resolution on the new system any higher than that. -jmc ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Trident Blade, no screens
Thank you very much for your response. What you suggest had an effect, but not an entirely good one... David Dawes writes: On Tue, Nov 11, 2003 at 01:27:54PM -0800, John Chandler wrote: When I my newly-installed RedHat system launches, X fails with this message: [...] (II) Primary Device is: PCI 00:08:0 (WW) TRIDENT: No matching Device section for instance (BusID PCI:1:0:0) found (EE) No devices detected. Fatal server error: no screens found (--) PCI:*(0:8:0) Silicon Integrated Systems [SiS] SiS300/305 PCI/AGP VGA Display Adapter rev 144, Mem @ 0xd000/27, 0xe000/17, I/O @ 0xdc00/7 (--) PCI: (1:0:0) Trident Microsystems CyberBlade/i1 rev 106, Mem @ 0xdd80/23, 0xde00/17, 0xdd00/23 The easiest way to deal with this would be to make the AGP video card the primary video card from your BIOS configuration (assuming that it has such an option). That way you'll be using the same card with XFree86 that you're booting on. The XFree86 server is showing the primary video (the one you're bootting up with) to currently be the on-board SiS video. Where do you have your monitor connected? The monitor is not connected to the on-board video card, it is connected to the one that is mounted in a PCI slot. The on-board video has a very small amount of RAM and would only support Fisher-Price resolutions. Apparently the only thing I can do in the BIOS is specify which of the two to initialize first, I can't make the on-board one disappear entirely. One might argue that there are good reasons for that... If you want XFree86 to run on the Trident card without making it the primary you'll need to edit your XF86Config file to tell the trident driver which device it should be driving. You can do that by adding the following line to the relevant Device section of your XF86Config file: Busid 1:0:0 I tried this, and when I restarted the server from the command line, the screen went dark and never came back. I was able to do a ctrl-alt-f1 to get back to screen one where I was then able to do a ctr-c and abort the server. I thought the trouble might be that I hadn't rebooted, so I tried that. This time, the screen went dark and stayed dark. Any clue what I ought to do at this point? (I guess I first have to look up how to boot RedHat 9 without starting X...) A second alternative is that you really want to be using the built-in SiS video. I wish I had a decent on-board video interface. [We should make busid optional in cases like this where there is only one card the driver could possibly be wanting to use.] I understand that it's not reasonable to expect you to comment on someone else's product, but maybe you have some idea why the X server used by the RH graphical install sequence seemed to choose the right card? I mean what could account for the different behavior -- it can't be that RH uses someone else's X server for installs, can it? -jmc ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Trident Blade, no screens
David Dawes writes: On Wed, Nov 12, 2003 at 01:01:13AM -0800, John Chandler wrote: Thank you very much for your response. What you suggest had an effect, but not an entirely good one... David Dawes writes: On Tue, Nov 11, 2003 at 01:27:54PM -0800, John Chandler wrote: When I my newly-installed RedHat system launches, X fails with this message: [...] (II) Primary Device is: PCI 00:08:0 (WW) TRIDENT: No matching Device section for instance (BusID PCI:1:0:0) found (EE) No devices detected. Fatal server error: no screens found (--) PCI:*(0:8:0) Silicon Integrated Systems [SiS] SiS300/305 PCI/AGP VGA Display Adapter rev 144, Mem @ 0xd000/27, 0xe000/17, I/O @ 0xdc00/7 (--) PCI: (1:0:0) Trident Microsystems CyberBlade/i1 rev 106, Mem @ 0xdd80/23, 0xde00/17, 0xdd00/23 [...] If you want XFree86 to run on the Trident card without making it the primary you'll need to edit your XF86Config file to tell the trident driver which device it should be driving. You can do that by adding the following line to the relevant Device section of your XF86Config file: Busid 1:0:0 I tried this, and when I restarted the server from the command line, the screen went dark and never came back. I was able to do a ctrl-alt-f1 to get back to screen one where I was then able to do a ctr-c and abort the server. I thought the trouble might be that I hadn't rebooted, so I tried that. This time, the screen went dark and stayed dark. Any clue what I ought to do at this point? (I guess I first have to look up how to boot RedHat 9 without starting X...) A second alternative is that you really want to be using the built-in SiS video. I wish I had a decent on-board video interface. Based on what you've said, maybe it's the Trident that is on-board and the SiS is the external card? If that's the case, you need to modify your XF86Config to use the sis driver instead of the trident driver (and remove the 'busid' line you just added). [...] I don't have much info about the other driver. And of course, I've lost the docs for the add-on card, too. I'd look at the mfr's web site, but there's not much writing on the card, so I don't know *what* mfr. (It's amazing how worthless a card can become without docs.) What I do have is the XF86Config file that works with this add-on card. I attach it below, and perhaps it reveals something. I note that in the Graphics device sections, the VideoRam lines are commented out (I don't know why, and don't remember doing it), but it is my vague recollection that the on-board interface had 1/4 MB and the add-on had 32MB. Again, I greatly appreciate the presence of experts in this field. Thank you. -jmc # File generated by XConfigurator. # ** # Refer to the XF86Config(4/5) man page for details about the format of # this file. # ** # ** # Files section. This allows default font and rgb paths to be set # ** Section Files # The location of the RGB database. Note, this is the name of the # file minus the extension (like .txt or .db). There is normally # no need to change the default. RgbPath /usr/X11R6/lib/X11/rgb # Multiple FontPath entries are allowed (they are concatenated together) # By default, Red Hat 6.0 and later now use a font server independent of # the X server to render fonts. FontPath unix/:7100 EndSection # ** # Server flags section. # ** Section ServerFlags # Uncomment this to cause a core dump at the spot where a signal is # received. This may leave the console in an unusable state, but may # provide a better stack trace in the core dump to aid in debugging #NoTrapSignals # Uncomment this to disable the CrtlAltBS server abort sequence # This allows clients to receive this key event. #DontZap # Uncomment this to disable the CrtlAltKP_+/KP_- mode switching # sequences. This allows clients to receive these key events. #DontZoom EndSection # ** # Input devices # ** # ** # Keyboard section # ** Section Keyboard ProtocolStandard # when using XQUEUE, comment
Re: [XFree86] Trident Blade, no screens
Thomas Winischhofer writes: John Chandler wrote: (--) PCI:*(0:8:0) Silicon Integrated Systems [SiS] SiS300/305 PCI/AGP VGA Display Adapter rev 144, Mem @ 0xd000/27, 0xe000/17, I/O @ 0xdc00/7 (--) PCI: (1:0:0) Trident Microsystems CyberBlade/i1 rev 106, Mem @ 0xdd80/23, 0xde00/17, 0xdd00/23 [...] The monitor is not connected to the on-board video card, it is This is slightly OT: Is the SiS 300/305 really on-board? If so, what MB is this? Other than reading the mfr's name off the card (which I've tried but I can't find anything helpful printed there), or just managing to remember what I was doing 18 months ago, how do I tell? The info above came from software probes, and it appears that one line describes an SiS AGP interface. It is also intuitively appealing to think of the integrated peripherals as having PCI id's starting with 0 rather than 1, but I don't know if that really means anything. My recollection is that the on-board interface had 1/4 MB, which is why I replaced it. Is the amount of RAM specified by one of those numbers? That might be a clue. -jmc ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Supported video card
Since I've been having some problems getting XFree86 to come up properly, I've been wondering if I shouldn't just get a new video card to eliminate the uncertainty of what card to specify in the config file. Two questions: 1. If I say, Chaintech nVidia GeForce MX400 64MB AGP, does anyone break out in hives? Is there a list of video cards that are either very well supported or have been problematic in practice? (erm, Three Questions!) 2. There used to be a configurator program that allowed me to pick video cards, monitors, etc. from lists, but this seems to have been left in the dustbin of CVS. Currently, I am aware of two ways to configure XFree86: A. run XFree86 --reconfigure and hope it does the right thing (which in my case it doesn't), or B. edit the config file by hand, making sure to spell everything right. Is that it, or is there a utility that replaces the old configurator and allows that kind of constrained choice? -jmc ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Supported video card
Thomas Winischhofer writes: John Chandler wrote: Since I've been having some problems getting XFree86 to come up properly, I've been wondering if I shouldn't just get a new video card to eliminate the uncertainty of what card to specify in the config file. Two questions: 1. If I say, Chaintech nVidia GeForce MX400 64MB AGP, does anyone break out in hives? Is there a list of video cards that are either very well supported or have been problematic in practice? (erm, Three Questions!) Can't answer that one, but make sure your mother board has a AGP connector before buying an AGP card. Maybe the reason for buying the PCI version of the SiS card had to do what that? After further investigation, it seems you have either a VIA GA-6VMM or GA-7VMM. These have NO AGP slot. Thomas Thank you. I'm now 10x closer to being an expert than I was yesterday. Which says more about yesterday than today. Thanks. -jmc ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Trident Blade, no screens
David Dawes writes: On Wed, Nov 12, 2003 at 08:04:16AM -0800, John Chandler wrote: David Dawes writes: On Wed, Nov 12, 2003 at 01:01:13AM -0800, John Chandler wrote: Thank you very much for your response. What you suggest had an effect, but not an entirely good one... David Dawes writes: On Tue, Nov 11, 2003 at 01:27:54PM -0800, John Chandler wrote: When I my newly-installed RedHat system launches, X fails with this message: [...] (II) Primary Device is: PCI 00:08:0 (WW) TRIDENT: No matching Device section for instance (BusID PCI:1:0:0) found (EE) No devices detected. Fatal server error: no screens found (--) PCI:*(0:8:0) Silicon Integrated Systems [SiS] SiS300/305 PCI/AGP VGA Display Adapter rev 144, Mem @ 0xd000/27, 0xe000/17, I/O @ 0xdc00/7 (--) PCI: (1:0:0) Trident Microsystems CyberBlade/i1 rev 106, Mem @ 0xdd80/23, 0xde00/17, 0xdd00/23 [...] Well, the primary card is the one that you get the BIOS boot messages on, and which Linux boots on. Since your monitor is plugged into the add-in PCI card, it's almost certain that it is the SiS card. So that's the driver you need to be using. The VideoRam lines usually should be commented out, so don't worry about that. I'm not up on which SiS cards are supported by the 4.3 sis driver, but since Thomas is following this thread, I'm sure he can help with that. Have you tried modifying your XFree86 4.x config to use the sis driver instead of the trident driver? Do I have to do anything besides change Trident to SiS? E.g., do I need to specify a Busid? Thanks, and I'm sorry I'm so ignorant. -jmc ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Trident Blade anomaly on Redhat 9 (shrike)
XFree86 -- This could fundamentally be a Red Hat issue, but maybe I can recover with a word of advice from you. I have a video card I got over a year ago and for which I've lost the docs. When installing RedHat 9, it is probed as a Trident Blade, and the graphical install works fine. When I boot the installed system, X fails to come up. The message has something to do with no screens found. I would email you the entire file, but I don't currently have my email config set up on the new system. If necessary, I'll sneakernet it, but I'm wondering if this is a strange problem or one that you've seen a million times. RedHat may even have fixed it -- this is a relatively old version of RedHat 9 -- the CD's were burned circa May 2003. But if possible I don't want to burn a new set (the PITA factor). If you can't help me, or need more info in order to do so, please tell me. Thanks. -jmc ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Trident Blade, no screens
When I my newly-installed RedHat system launches, X fails with this message: [...] (II) Primary Device is: PCI 00:08:0 (WW) TRIDENT: No matching Device section for instance (BusID PCI:1:0:0) found (EE) No devices detected. Fatal server error: no screens found In the exact same box, booting from a different disk with an earlier version of XFree86 (# XFree86 4.0 configuration generated by Xconfigurator) allows X to come up just fine. Also, the graphic install worked fine. I attach the log and the config. Also, some of the config from the installation that works properly. I know it's a lot of lines, but I'm hoping someone understands what to look for and can ignore the other 90%. Thanks. -jmc XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2) Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] Build Date: 27 February 2003 Build Host: porky.devel.redhat.com Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.4.20-8 ([EMAIL PROTECTED]) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Thu Mar 13 17:54:28 EST 2003 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/XFree86.0.log, Time: Tue Nov 11 11:05:56 2003 (==) Using config file: /etc/X11/XF86Config (==) ServerLayout Default Layout (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Videocard0 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc105 (**) XKB: model: pc105 (**) Option XkbLayout us (**) XKB: layout: us (==) Keyboard: CustomKeycode disabled (**) |--Input Device DevInputMice (**) FontPath set to unix/:7100 (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (--) using VT number 7 (II) Open APM successful (II) Module ABI versions: XFree86 ANSI C Emulation: 0.2 XFree86 Video Driver: 0.6 XFree86 XInput driver : 0.4 XFree86 Server Extension : 0.2 XFree86 Font Renderer : 0.4 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x8060, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1106,0601 card , rev 05 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1106,8601 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:07:0: chip 1106,0686 card 1106, rev 40 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 1106,0571 card , rev 06 class 01,01,8a hdr 00 (II) PCI: 00:07:2: chip 1106,3038 card 0925,1234 rev 1a class 0c,03,00 hdr 00 (II) PCI: 00:07:3: chip 1106,3038 card 0925,1234 rev 1a class 0c,03,00 hdr 00 (II) PCI: 00:07:4: chip 1106,3057 card , rev 40 class 00,80,00 hdr 00 (II) PCI: 00:07:5: chip 1106,3058 card 1106,4511 rev 50 class 04,01,00 hdr 00 (II) PCI: 00:08:0: chip 1039,0300 card 1039,0300 rev 90 class 03,00,00 hdr 00 (II) PCI: 00:09:0: chip 9004,8178 card , rev 00 class 01,00,00 hdr 00 (II) PCI: 00:0e:0: chip 10ec,8139 card 10ec,8139 rev 10 class 02,00,00 hdr 00 (II) PCI: 01:00:0: chip 1023,8500 card 1023,8500 rev 6a class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x0004 (VGA_EN is cleared) (II) Bus 1 non-prefetchable memory range: [0] -1 0 0xdc00 - 0xdeff (0x300) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:7:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (--) PCI: (0:7:4) VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] rev 64 (--) PCI:*(0:8:0) Silicon Integrated Systems [SiS] SiS300/305 PCI/AGP VGA Display Adapter rev 144, Mem @ 0xd000/27, 0xe000/17, I/O @
