 |
|
| KM-266 Pro queries |
|
|
By convict - Posted on January 17, 2003 - 00:19:49 (#5411)
Current version when comment was posted: 2002-05-27 |
|
|
anyone out there know if the KM266-pro with intergrated Via prosavage8 supports Open GL 1.2? If so does anyone know where to get that driver. Grrrr, Computers!!!
|
|
| not working on savage/mx :-\ |
|
|
By zulaica - Posted on November 8, 2002 - 19:58:24 (#4063)
Current version when comment was posted: 2002-05-27 |
|
|
i've tried installing on my toshiba tecra 8100. no dice. i have to run fail-safe video. :-/
multi-booting xp pro, lycoris d/lx (linux), and beos pro 5.0.3. using grub as boot manager.
any help would be GREATLY appreciated. thanks!
|
|
| Great thing! |
|
|
By ade - Posted on June 6, 2002 - 14:03:48 (#1710)
Current version when comment was posted: 2002-05-27 |
|
|
I finally found out that after updating the BIOS of the Savage4 Card the DSL DialUP works. Thats a great thing.
|
|
| Resolution problems |
|
|
By Eugenia - Posted on May 30, 2002 - 12:19:20 (#1625)
Current version when comment was posted: 2002-05-27 |
|
|
Hmmmmmm.... I have a suspicion as to why some of us can't go passed some resoulutions (make sure you cold boot before you join the club btw).
My suspicion is because all the newer Savage cards are incorporated into the VIA chipsets, they are not sold as individual AGP cards. Therefore, they are using the SHARED memory model. For example, my BIOS gives to the Savage card 16 MB off my main memory. However, the BeOS driver of BeSavage+ does not ask the motherboard BIOS to find out how much memory there is available for the card, because this driver was written for the "real" cards of S3 Savage, not for the integrated VIA chipset ones. Therefore, BeOS automatically reserves only 1 MB of VRAM for the graphics card, which is the minimum default. Therefore we can't go passed certain resolutions and color depths. The highest I could go is 1152x864 at 16bit color at 85 Hz.
The 810/815 driver for BeOS also had the same problem. By default, BeOS would only allocate 1 MB of VRAM for the Intel 81x graphics card. However, later, Be added a configuration file for the driver, where you could edit it and allocate more memory.
To do the same on the BeSavage+ driver, you need to modify the driver... :(
|
|
| SavagePRO+ DDR here! |
|
|
By Eugenia - Posted on May 28, 2002 - 16:36:34 (#1600)
Current version when comment was posted: 2002-05-27 |
|
|
I feel so lucky because just today this driver was released with the DDR version of the SavagePRO+ support, and today was also the day that I installed BeOS on my AthlonXP. :)
However, I can't get the driver to work above 1152x864 at 16bit at 85 Hz. When I switched to anything on 1280x1024 or above, the monitor goes out of range. This is obviously a bug in the driver (my Linux partition on the same machine can do higher resolutions). Please have a look at it.
And yes, I have cold-booted in the meantime. Same problem. Can't get passed the 1152 resolution.
|
|
| hmm |
|
|
By Jess - Posted on May 28, 2002 - 16:36:06 (#1599)
Current version when comment was posted: 2002-05-27 |
|
|
I wonder if the black boot screen is caused by the same thing with the S3 trio64 driver. I have tried it with a few systems & allways got da black screen. Sadly the Bios option you found to fix the prob is not in any of the systems Bios... whoas me! heh Wonder if there is another option that may produce the same results but I have tried almost all shadowing & mem caching options to no avail...
|
|
| Solution for black screen at startup |
|
|
By Yoghourt - Posted on May 28, 2002 - 16:18:06 (#1598)
Current version when comment was posted: 2002-05-27 |
|
|
I had the 'black screen at startup' problem with A7Pro and 3D Blaster Savage 4.
Go to BIOS, chip configuration, and disable Byte Merge (if someone can tell me what it is intended to...)
Now the driver works fine.
|
|
| Driver is not Work with Kt133a . |
|
|
By centu - Posted on May 2, 2002 - 11:38:27 (#1262)
Current version when comment was posted: 2002-03-07 |
|
|
MB Canyon 7Tabas (KT133a) , Duron1000 (Morgan) , Innovission Savage4 Pr(?) RevB. 32M , AGP4X , irq 12 - free , soundblaster live! 5.1 , 256m sdram PC133 ; on start color is present , mouse-hand & Tracker & Desckbar are vievless , sistem - loose ...
|
|
| Does not work with DialUp |
|
|
By ade - Posted on April 12, 2002 - 19:43:01 (#922)
Current version when comment was posted: 2002-03-07 |
|
|
When using savage driver, i cannot use DSL-Dialup
Its very very bad, because I cannot work(code) with BeOS(all Versions) and surf if i need to.
|
|
| Work with BeOS5 but not with Dano |
|
|
By rayman - Posted on March 12, 2002 - 06:51:43 (#596)
Current version when comment was posted: 2002-03-07 |
|
|
On a same portable computer, this driver work fine with BeOS 5, but
with Dano, I have one blue screen and the boot stop here.
|
|
| Re: can't change settings |
|
|
By Takayuki - Posted on March 12, 2002 - 03:47:12 (#592)
Current version when comment was posted: 2002-03-07 |
|
|
Try cold-booting. As ProSavage chipsets adopt Unified Memory Architecture, your video memory may be limited to 640x480x8 when booting BeOS from Win98.
|
|
| can't change settings |
|
|
By asr@iprimus.com.au - Posted on March 12, 2002 - 00:29:33 (#591)
Current version when comment was posted: 2002-03-07 |
|
|
I have installed the driver and it works partially.
I am using PE and booting from Win98. Colour works, but resolution is only 640X480. I can't change colour depth, resolution or refresh rate. All settings other than 640x480, 8bit and 60Hz are greyed out.
Any suggestions?
|
|
| similar problem |
|
|
By kaito - Posted on March 11, 2002 - 21:06:33 (#589)
Current version when comment was posted: 2002-03-07 |
|
|
There was hanging up problem by booting from win98 with my savage3d/mv. Fortunately a cold booting could solve it. Thanks for the driver!
|
|
| I spoke too soon |
|
|
By Big Al - Posted on March 11, 2002 - 08:44:03 (#584)
Current version when comment was posted: 2002-03-07 |
|
|
Wow - now the driver works! It might be because I reset from Win2k into BeOS and not from a cold-boot. As long as it works I'm happy! Thanks!
|
|
| Somehow DSL doesn't work anymore |
|
|
By ade - Posted on March 8, 2002 - 05:56:44 (#560)
Current version when comment was posted: 2002-03-07 |
|
|
On DANO, connection to DSL does not work if the driver is active, but when I enable VESA (safe mode) DSL works.
Curious
Can somebody fix that?
|
|
| From the publisher... |
|
|
By Takayuki - Posted on March 8, 2002 - 04:07:17 (#559)
Current version when comment was posted: 2002-03-07 |
|
|
Sorry for the inconvenience.
I'm afraid I have no idea about the driver's detail because all I did is to add some product IDs for the driver to accept more chipsets. I tried to contact the original author to merge the patch, but his account is no longer available. So I decided to publish it by myself.
I am running the driver on KL133 (Asus A7VL-VM) with R5 and Dano flawlessly. I have also heard it worked on KN133 and PL133.
|
|
| BeSavage+ Driver does not work |
|
|
By munde - Posted on March 7, 2002 - 12:12:12 (#545)
Current version when comment was posted: 2002-03-07 |
|
|
The BeSavage+ Driver does not work at all on a GigaByte GA 6BXD SMP system with a Savage4. Even the original Erdi Chen driver is causing occasional hangs. From my point of view this is caused by the implementation of the core Interrupt Routine. (shrug).
|
|
| The driver doesn't work on Shuttle Spacewalker FV24 Mainboard |
|
|
By David RENE - Posted on March 7, 2002 - 10:45:21 (#544)
Current version when comment was posted: 2002-03-07 |
|
|
On the Shuttle Spacewalker FV24 Mainboard, there is the same problem as Big AL motherboard.
|
|
| Still doesn't work on the Epox KL-133M motherboard... |
|
|
By Big Al - Posted on March 7, 2002 - 07:15:48 (#543)
Current version when comment was posted: 2002-03-07 |
|
|
I was hoping this would work on my KL-133M motherboard - the previous version wouldn't. This version at least looks like it's pulling up the driver but the system just locks before loading the desktop.
Anyone have any luck with the built-in Savage 4 chipset on the Epox KL-133M motherboard?
|
|
|
|
|
