Opened 15 years ago

Closed 6 years ago

#5877 closed enhancement (not reproducible)

the VIA P4M800 PRO/S3 UniChrome Pro is not supported anymore?

Reported by: khallebal Owned by: rudolfc
Priority: normal Milestone: Unscheduled
Component: Drivers/Graphics/VIA Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: x86

Description (last modified by axeld)

this graphics card was supported in the first alpha release but it's not anymore, now i'm using the rev:36447 and i was surprised to see that it's using the vesa driver, although this card was well supported?

Attachments (1)

syslog (70.4 KB ) - added by khallebal 15 years ago.

Download all attachments as: .zip

Change History (22)

by khallebal, 15 years ago

Attachment: syslog added

in reply to:  description comment:1 by khallebal, 15 years ago

Replying to khallebal:

this graphics card was supported in the first alpha release but it's not anymore, now i'm using the rev:36447 and i was surprised to see that it's using the vesa driver,although this card was well supported?

is this ticket has been fixed or it hasn't been seen yet?i'm not pushing or anything,but it's been here for 3 days now and it hasn't been assigned to anyone. strange that my pc now uses the vesa accelerator, no 2d acceleration at all and is a bit dark.

comment:2 by mmadia, 15 years ago

Owner: changed from nobody to gerald.zajac
Status: newassigned

taking a best guess & re-assigning to Gerald.

comment:3 by gerald.zajac, 15 years ago

This is not an s3 video chip; it is a Via chip. On line 14 of the syslog, the OEM string identifies it as a "VIA P4M800 PRO" which should be supported by the VIA driver which was written by Rudolf Cornelissen; thus, this bug should be assigned to Rudolf instead of Gerald Zajac.

comment:4 by anevilyak, 15 years ago

Owner: changed from gerald.zajac to rudolfc

Noted, thanks.

comment:5 by axeld, 15 years ago

Component: Drivers/Graphics/S3Drivers/Graphics/VIA
Description: modified (diff)

But that also means that this chipset was never supported; IOW this renders the ticket invalid, as there is no regression.

in reply to:  3 comment:6 by khallebal, 15 years ago

Replying to gerald.zajac:

This is not an s3 video chip; it is a Via chip. On line 14 of the syslog, the OEM string identifies it as a "VIA P4M800 PRO" which should be supported by the VIA driver which was written by Rudolf Cornelissen; thus, this bug should be assigned to Rudolf instead of Gerald Zajac.

if you look further in the syslog lines 311 up to 313 you'll see that it's reported as a s3 unichrom pro,that was reported also by the sreen preflet on the R1A1.(BTW s3 is owned by via since a couple of years now)that it explaines maybe the confusion about why it is reported differently in the line 14 of the syslog.

comment:7 by idefix, 15 years ago

The VIA driver does have an entry for this card, only it is commented out. The entry was added in changeset:23754.

in reply to:  7 comment:8 by khallebal, 15 years ago

Replying to idefix:

The VIA driver does have an entry for this card, only it is commented out. The entry was added in changeset:23754.

any idea why it's been commented out?it was working quiet stable! and are we gonna see it again in the next releases?

comment:9 by idefix, 15 years ago

As you can see, changeset:23754 is two years old and thus pre-dates Alpha 1. So your card shouldn't have worked with that release either.

What you can try though, is to uncomment that line, build the driver and test if it works with your card.

comment:10 by stippi, 15 years ago

Looking closely at hrev23754, I see the commented line was *added*, not commented out.

comment:11 by stippi, 15 years ago

No other changes to that file since that revision, BTW. (svn log)

in reply to:  10 comment:12 by idefix, 15 years ago

Replying to stippi:

Looking closely at hrev23754, I see the commented line was *added*, not commented out.

That's what I tried to say in comment:7, but I probably could have worded that better...

comment:13 by bonefish, 15 years ago

Owner: changed from rudolfc to axeld

Though small there's a certain chance that Axel still knows, why he added the line like that. :-)

comment:14 by axeld, 15 years ago

Milestone: R1/alpha2Unscheduled
Type: bugenhancement

That's an easy one for my eidetic brain: I have a system with that chipset, and had a look if it could easily be made to work. Which was not the case, which I left it commented out. Oh, and it was rainy that day ;-)

comment:15 by rudolfc, 14 years ago

Actually, I did write the VIA driver in Haiku svn. I think I never finished it for acceleration though.

I had a VIA Nimble V5 from Yellowtab for building and testing the driver. This had a CLE66 chipset (unichrome) which worked OK with the driver. In the beginning I added recognition for K8M800 Unichrome Pro and P4M800 Pro (VT3344) because I thought they would work the same as far as my driver was concerned.

Since I got some negative reports from users I disabled the P4M800 support, and I doublt the K8M800 support is OK. I never got my hands on these respective chipsets so I could not correct the problems.

In the end I stopped development and some time later Axel and I started mailing about the Nimble. I then donated this Nimble to Axel, so he has indeed some hardware ;-)

Bye!

Rudolf.

comment:16 by modeenf, 12 years ago

Summary: the s3 unichrom pro is not supported anymore?the VIA P4M800 PRO/S3 UniChrome Pro is not supported anymore?

comment:17 by khallebal, 9 years ago

I think Rudolf fixed this ticket? and i don't this HW anymore, so if it is fixed, please close.

comment:18 by rudolfc, 9 years ago

Owner: changed from axeld to rudolfc

I'll have a look for the status.. Thanks!

comment:19 by cocobean, 6 years ago

hrev52014 reviewed. Can close this ticket per reporter request (ticket and card are now 8+ years old).

comment:20 by rudolfc, 6 years ago

The card is a vendor 1106: VIA Technologies, Inc. device 3344: CN700/P4M800 Pro/P4M800 CE/VN800 [S3 UniChrome Pro]

This ID $3344 is not in the driver, so the card is currently not supported. Since I _did_ add explicit, and tested OK, K8M800 support, one could add the ID as a new test to see if this card behaves this time (previously it did not, just like K8M800).

K8M800 was added because I stumbled upon this card by chance.

If noone can actually test P4M800 The ID should best not be added.

Closing ticket. Please reopen if someone has acces to this card and runs Haiku on it..

Rudolf.

comment:21 by rudolfc, 6 years ago

Resolution: not reproducible
Status: assignedclosed

Not testable anymore.

Note: See TracTickets for help on using tickets.