LinuxMCE Forums

General => Users => Topic started by: l3mce on March 14, 2012, 03:12:19 pm

Title: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: l3mce on March 14, 2012, 03:12:19 pm
At long last, as a side effect of dealing with the dvd snapshot maker, I picked up where I left off trying to get better video card support. I believe the next build should have video detection kicked wide open.

I need people to test Intel, ATI, and VIA MDs. I am trying not to be overly optimistic... but I am out of equipment to test on... and everything works (newest versions of nVidia hardware notwithstanding). However the new nVidia chipset interoperability is right around the corner. I have the source code, I just need to compile our own versions of the nVidia 295.20 drivers and nvidia-settings specific to that driver, and get it all happy in the DB. I have already written the detection scheme. On the newest nVidia chipsets there is a new VDPAU revision (rev D) which reports greatly improved h264 support, so I am looking forward to that.

LMCE should work on just about anything now. Just apt-get update, apt-get upgrade, and you will have to then run /usr/pluto/bin/Diskless_CreateTBZ.sh (again if run before, so that the new code is used for them).

Then pull out your abandoned cards/MD projects, and just plug them in. Set your laptops to network boot... MDs are all slim clients... your host OS will not be affected.

So, come on folks. Make me a liar.
Please report any failures along with output of lspci -v | grep "VGA"
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: Marie.O on March 14, 2012, 04:42:45 pm
A note: The built producing the new debs is currently under way. Please wait a bit. As soon as you see a version with 25659 at the end, you know you've got the right stuff. Also, we will have a 1004 snapshot iso with those changes. A big thanks to l3mce!
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: Techstyle on March 14, 2012, 04:44:38 pm
Any particular UI that people should use?
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: l3mce on March 14, 2012, 05:31:39 pm
As good as you can get.

Intel is producing great results. I mean if you are running a late 90s dell optiplex, I wouldn't shoot for compositing... however if you have a G45 or similar, UI2 with alpha is working. Honestly I have said optiplex running UI2 (no alpha) brilliantly right now. Couple of laptops have run with alpha... and frankly... the performance has been better than my non-VDPAU nVidia stuff.

ATI is anybodies guess. I don't have any HW that uses the fglrx drivers, and you are not likely to get alpha with radeon. U2.1 works great on my radeon hw.

Laughably my pico-itx VIA runs well enough on UI2.1. Mythtv takes a few seconds to buffer up, but it runs, which is funny to me. Performance would probably be up to par if I could get the s3d driver to fire, but as it was problematic on my VIAs, I set it to openchrome.

Along with the fglrx, these are the additional drivers being correctly detected and applied:
radeon: xserver-xorg-video-radeon
radeonhd: xserver-xorg-video-radeonhd
intel: xserver-xorg-video-intel
i128: xserver-xorg-video-i128
i740: xserver-xorg-video-i740
openchrome: xserver-xorg-video-openchrome
savage: xserver-xorg-video-savage
via: xserver-xorg-video-s3
virge: xserver-xorg-video-s3virge

I somehow let go of the detection that unlocks the Intel vaapi on the G45, i3, i5, i7 cores in this build. Will replace for next build. In the meantime if you have any of those, when you get to avwizard, apt-get install libva-driver-i965 and reboot.

*Oh... and I am quite sure I broke vesa... so... best to wait until after build, and new pluto-boot-scripts is generated after that.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: bongowongo on March 14, 2012, 07:02:52 pm
As good as you can get.

Intel is producing great results. I mean if you are running a late 90s dell optiplex, I wouldn't shoot for compositing... however if you have a G45 or similar, UI2 with alpha is working. Honestly I have said optiplex running UI2 (no alpha) brilliantly right now. Couple of laptops have run with alpha... and frankly... the performance has been better than my non-VDPAU nVidia stuff.

ATI is anybodies guess. I don't have any HW that uses the fglrx drivers, and you are not likely to get alpha with radeon. U2.1 works great on my radeon hw.

Laughably my pico-itx VIA runs well enough on UI2.1. Mythtv takes a few seconds to buffer up, but it runs, which is funny to me. Performance would probably be up to par if I could get the s3d driver to fire, but as it was problematic on my VIAs, I set it to openchrome.

Along with the fglrx, these are the additional drivers being correctly detected and applied:
radeon: xserver-xorg-video-radeon
radeonhd: xserver-xorg-video-radeonhd
intel: xserver-xorg-video-intel
i128: xserver-xorg-video-i128
i740: xserver-xorg-video-i740
openchrome: xserver-xorg-video-openchrome
savage: xserver-xorg-video-savage
via: xserver-xorg-video-s3
virge: xserver-xorg-video-s3virge

I somehow let go of the detection that unlocks the Intel vaapi on the G45, i3, i5, i7 cores in this build. Will replace for next build. In the meantime if you have any of those, when you get to avwizard, apt-get install libva-driver-i965 and reboot.

Thank you L3mce, I have been waiting for this for so long, but this 2 weeks I cannot do anything. My boss expects me to work for my money. Weird! But my bongo is itching like always.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: JaseP on March 16, 2012, 10:28:54 pm
I'll test this tonight on my Intel core machine... I was getting an error at the avwizard with a fresh install using the script over the last several days.

Sorry for the OT request, but any chance on getting the ability to define partitions on the 1004 Install ISO, or is that right out???

I like my primary and /home partitons separate and got some junk on there I'd like to keep (that is; no reformatting of my /home partition).
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: JaseP on March 17, 2012, 01:14:48 am
OK simply downloading the libva driver is a no go... I've re-run the script and will see if that does the trick,... But I doubt it...

FYI my lspci output is as follows:
Code: [Select]
00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 02)

... Yep,... Just like I figured avwizard fails with "failed to setup X" message in ASCII...

It's broke...
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: l3mce on March 17, 2012, 01:34:24 am
I should have updated this as the build has not happened yet. Things have been very busy on the builder side, so I have been fine tuning and doing spot tests on very new hardware.

I will post again when it is ready to go. I was a bit anxious, so I just submitted the code and started the thread. I was a bit premature in the announcement. I think I will have to fine tune some things on the ATI side as well... but thank you for testing, and please try again when I repost.

Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: JaseP on March 17, 2012, 01:50:36 am
So it's not my particular chipset?!?! Thanks for responding so quickly and working on it... I'm anxious to get everything working for the first time...

I'm just DYING to duplicate my Z-wave stuff on to my second (LinuxMCE controlled) Aeon Z-wave stick.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: l3mce on March 18, 2012, 04:35:01 pm
Bring it.

Ok... to reiterate a couple of things.

In 1004 ONLY (for now), on the core:
Code: [Select]
sudo apt-get update
sudo apt-get upgrade
To pass this new code on to media directors you will need to rerun:
Code: [Select]
sudo /usr/pluto/bin/Diskless_CreateTBZ.shMedia Directors will NOT get the new detection scheme unless you do.

In web admin, remove any failed attempts at creating these md's before by clicking Media Directors on left, and choosing "Delete" to the right of the moon number.

Then... just plug it in and push da button.
(http://us.cdn4.123rf.com/168nwm/naumoid/naumoid0809/naumoid080900017/3522154-glowing-power-button-on-black-background.jpg)

I will tell you that this will NOT work on Sandy Bridge/HD3000. Just too new for 1004.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: l3mce on March 18, 2012, 05:02:19 pm
JaseP:

Quote
OK simply downloading the libva driver is a no go...
Please do not download any drivers on your own to try and fix it if it doesn't go.

There is a known bug in Intel driver for your specific chipset.
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/539533
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/578460

However, we build our xorg a little different, and with the updates to the driver on their side it may just light up, so give it a go as I have done it. If you still get a failed to setup x, I will give you some specific stuff to do to get it going, however I am not sure how WELL I can get it to perform once we change it.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: JaseP on March 19, 2012, 08:35:15 am
Here's the thing,... This is the Core machine, not just a media director... The chipset & install was working before (as of like 2 weeks ago, with a clean install)... I was getting decent performance out of it with UI2 with Alpha blending. The chip set works after the LinuxMCE avwizard fails and I manually login to my user account and do s startx. In fact I am typing this on that machine right now from inside KDE, running with full (KDE) compositing. So the Intel driver works fine... There are not limitations in it that would be of concern to LinuxMCE (3D gaming,... maybe). And to my knowledge that bug you mentioned, is over a year old and has been patched...

I DID the apt-get update/upgrade/rebuild all media directors thing. I do not have access to the web admin, as LinuxMCE does not come up (and I have no idea what the URL is for the web admin utility, or if it's even up & working at this point). So,... If you specific instructions that I can follow to get LinuxMCE to detect the chip set, I'd be appreciative.

PS: I found the thread about accessing the web admin portal,... So getting access to that's no problem.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: l3mce on March 19, 2012, 10:09:14 am
Look... I am really trying to be nice here. You do not make it easy.

I don't care what you did before. I don't care how you think things should work.

1. The limitation would be compositing, which is of concern to LinuxMCE using alpha blending. Do not explain to me what is important.
2. I know the driver can be made to work. The problem is setting up an xorg that the driver can take advantage of WITHOUT having to do anything manually.
3. Those bugs are open, as in not closed, as in not fixed. There is about a 50/50 chance the driver will "just work" on a given setup.
4. The build happened TODAY, so what you did previously matters f*** all because the code was not available to make it work.
5. The idea, is that nobody has to do anything special to make these things work. I don't want to give hacks. I am doing all of this to make it work for everyone... so, until you do what I tell you to, I am not going to place a hack here, because then people just patch their systems rather than helping me make things work for everyone.

Lastly, if you never plan on attaching any media directors to your core, you can skip the Diskless_SetupTBZ.sh. I will update the instructions to reflect this.


So... just follow the instructions, or drop out of my threads.
kthxbi
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: JaseP on March 19, 2012, 02:46:01 pm
I'm not trying to be difficult,... I'm just trying to point out that it was working before but didn't later...

Question:

You say the limitation would be compositing,... But the Intel driver supports compositing,... Compiz, Native compositing in KDE, XFCE, LXDE, etc (and it seemed to be working before in LinuxMCE). What is LinuxMCE doing differently that you say compositing won't work in LinuxMCE???

Again, I'm not trying to be a P.I.TA., I really just want to know. I've configured X-server configs for a decade, so I could actually be a little help here... I've got motivation to help make this work, as 2/3rds of my finished network will be running on similar Intel grafics chipsets. And I solved graphics issues surrounding various Intel chipsets before. I've got old Xorg.config files that work laying around.

P.S. I'll give the new build a spin tonight and post the results.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: l3mce on March 19, 2012, 03:43:59 pm
I'm not trying to be difficult,... I'm just trying to point out that it was working before but didn't later...

Question:

You say the limitation would be compositing,... But the Intel driver supports compositing,... Compiz, Native compositing in KDE, XFCE, LXDE, etc (and it seemed to be working before in LinuxMCE). What is LinuxMCE doing differently that you say compositing won't work in LinuxMCE???

Again, I'm not trying to be a P.I.TA., I really just want to know. I've configured X-server configs for a decade, so I could actually be a little help here... I've got motivation to help make this work, as 2/3rds of my finished network will be running on similar Intel grafics chipsets. And I solved graphics issues surrounding various Intel chipsets before. I've got old Xorg.config files that work laying around.

P.S. I'll give the new build a spin tonight and post the results.


The reason it was working before, and then didn't, is because I broke it trying to get to this point where it will work again, hopefully better than ever.

I was replying to your statement that it shouldn't matter to lmce. I did not say that compositing WOULDN'T work, I only meant to say that compositing does matter to the system. All that has changed on that front is detection and adding the newer libva-driver-i965. If you had compositing going, that is not an issue unless you added it yourself, which disrupts my ability to determine if our side is doing it right... which is the only reason I asked you not add any drivers on your side.

Our xorg.conf generation is complicated and the pieces each happen in several different places before coming together. I have nothing to indicate that it will NOT work for you, so as of yet I do not know that any help is needed. I try not to make changes to the process for a single chipset because it makes it more likely to break everything around it, and typically migrating to new distro's, the change becomes irrelevant except to cause problems. However if it is not particularly invasive, I am willing to generate specific modlines based on oddball cases.



Thus far, out of 8 Intel machines that never gotten to AVWizard before, all but the hd3000 have... and it is just too spanking new for Lucid, requiring natty backports and too much work in general to deal with.


I am sorry if I am curt with you. It seems like I try being nice to you, and you come back nasty at me. You begin posting in the thread, not reading where posde said:
A note: The built producing the new debs is currently under way. Please wait a bit. As soon as you see a version with 25659 at the end, you know you've got the right stuff. Also, we will have a 1004 snapshot iso with those changes. A big thanks to l3mce!

and then say

OK simply downloading the libva driver is a no go... I've re-run the script and will see if that does the trick,... But I doubt it...


... Yep,... Just like I figured avwizard fails with "failed to setup X" message in ASCII...

It's broke...

I have hundreds of hours in this. Your attitude is pessimistic and rude. Still I am polite. Then you come back, after not following directions, telling me it isn't going to work, not understanding that the new code has not been available until I posted saying it was ready (as I said I would do). I don't want to be unpleasant to you. It isn't constructive in any way. I don't want people kissing my ass either... but if we could find a happy medium between asshole and thankful, it would be much better for everyone.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: JaseP on March 19, 2012, 05:58:06 pm
I hadn't intentionally started mucking around and installing fresh to be a pest,... I had broken the MythTV portion of my install too badly (my channels configuration never worked right,... apparently a hardware and vendor issue, nothing to do with LinuxMCE,... it never worked right). So, I installed fresh, figuring it was faster than trying to track down and fix what I'd broken.

I hadn't read any of the threads before I tried my reinstall. I had reconfigured my network to (hopefully, If I got it right) be more compatible with LinuxMCE's expected topography. I hadn't read the entire thread (I got ADHD, I'm impatient like that), before trying the fix. So I missed the part about holding off. In short, leaped before I looked My fault.

I am not trying to be rude or obnoxious,... just short and concise. When I say something is "broken," I mean "it is not working." I absolutely do not mean, " You're a &+$*&+$+)>#, you busted my stuff." Sorry if comes off that way. The pessimistic post was not aimed at you or your work, but rather that I didn't believe the problem was related to the libva stuff. Not the best choice of wording on my part. I realize that if you were stressed, tired and overworked, you may have easily interpreted things the wrong way.

By the way,... to give you info on what worked and what didn't,... All I did after a fresh install was to add the libva stuff, update, upgrade, and rebuilt MDs... I had not changed anything from stock (for further clarification, I did it several times, the last time, not even adding the Medibuntu stuff that I had previously, and had worked, before). It was Kubuntu install, run an update, install LinuxMCE... Please note that compositing (and UI2 with Alpha blending) worked under the install I had screwed up before. So whatever detection or setup routines that were working before, absolutely worked.

I do not have anything newer than a couple of years old (that will be running LinuxMCE, anyway). So, all the chipsets are part of the GMA 945 series or successors. I have no HD3000s. So no worries there. I will note that even on identical chipsets, that the differences between hardware installs (bus configuration, etc.) from one OEM to another can make a huge difference in performance and capabilities. But that's a hardware problem, not a software problem. I already expect that.

I don't blame you for counting out a chipset with substandard Linux support. I'm the (unfortunate) owner of a MID with the Intel/PowerVR Poulsbo GMA 500 chipset. If it weren't for the fact that I otherwise love the little machine for it's specs and form factor, I'd have returned it as soon as I bought it. Getting all of it's hardware working is one of those eternal projects. And don't worry,... I'll never ask for GMA 500 support...

Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: l3mce on March 19, 2012, 08:24:19 pm
Then we're friends, and I owe you a beer for being hyper-senstitive and taking out my aggravation on you.

Have you done an update/upgrade yet today?

If not, please do, skip the Diskless_Create and when upgrade completes:
Code: [Select]
sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.bu; reboot
On boot it should automatically detect that your xorg is missing, run through its detection/install routine, generate a fresh xorg.conf.pluto.avwizard file and dump you into AVWizard, which will generate the final xorg.conf file.

You should not need to do ANYTHING. Please post success or failure... and thank you for testing.


*ps I write commands out, not because I presume any level of understanding on the user end, but because it makes it easier and my intent is made clear.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: JaseP on March 19, 2012, 08:46:43 pm
No beer necessary ... I just have to make a mental note to myself about working on my communication skills.

Haven't had the oppty to do update/upgrade,... at work now, no remote access to the machine (and I like it that way, keeps me from getting even more distracted). I'll do tonight and post a report. In the unlikely event it fails to recreate the org.conf, what reports logs should I look for or run & post???

Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: l3mce on March 19, 2012, 09:27:24 pm
It is a universal installer. It is pretty much gonna be a go or no go. AVWizard_Run.(date.timestamp).log might be helpful.... might be almost empty.

I wouldn't say the UNLIKELY event that it fails either... like I said... about a 50/50 shot on that one... but I am hopeful.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: JaseP on March 20, 2012, 12:50:56 am
Well,... Then God smiles on me 'cause the video worked!!!

But the audio didn't... But I don't think anything you changed affected that. Something was probably muted by KDE. I've seen this before, where KDE mutes key sound channels. That may be something to take note of for the DVD installer (i.e.: unmute all sound channels). ... I have this love/hate relationship with KDE. Sometimes I Love to Hate 'em, sometimes I Hate to Love 'em. I'm in conflict as to which I am feeling about them now.

I think I'll just do a reinstall.  I'd like the chance to eliminate some of the failed user accounts I created, and consolidate that data from the effective ones. ...

Thanks, l3mce,... Good Work ... !!!
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: l3mce on March 20, 2012, 01:04:05 am
Well that is good news... but I don't expect a reinstall will fix that...

try this instead
Code: [Select]
amixdigital=$(amixer | grep Simple | cut -d' ' -f4,5,6 | sort | uniq) ;  for output in $amixdigital; do amixer sset $output unmute; amixer sset output 80%; done 2>/dev/null
It will unmute everything that is mutable and raise all volumes to 80% that have volumes.

Unless of course you mean you have no sound DEVICE. If aplay -l has nothing avail... you will want to look at alsa.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: JaseP on March 20, 2012, 01:22:40 am
Thanks for that but the ADHD kicked in and I already started... I wanted to remove the "ghost" accounts peppering  the /home partition,... and that's more easily done in a pristine environment ... A quick reinstall,  purging useless accounts, and reinstalling LinuxMCE, will make me feel the install is more virg... pristine.  Standby,... and thanks (again?!?) for the sound channel command.

By the way would you like system specs on my core for reference??? If so, please specify the files you'd like to see copies of...

I'm planing on a leisurely reinstall,  while watching Top Gear on BBC America,... with a wine spritzer in hand,... "No worries"  (the phrase, a tip o' the hat to the Aussies in the crowd,... y'all know you watch Top Gear with all the enthusiasm of a Brit).

Peace.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: PaulH on March 20, 2012, 02:13:09 am
I was watching this thread with interest since I too went through what JaseP went through well, minus the advanced stuff.
Last night I reinstalled LMCE10.04 in my server and went to bed after initiating Diskless_Create.
Tonight, after work I fired up one of my MDs and worked beatifully. Thank You L3MCE for fixing and Thank You too JaseP for raising the question.
PaulH
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: l3mce on March 20, 2012, 02:28:20 am
What I would like is very simple... and this goes for all, if you would.
If it is a "regular computer", tell me what it is. If it is not, tell me what the motherboard is and graphics (onboard or added). Give me the lspci -v | grep "VGA", tell me what it is connected to and what connection it is using... and what resolution and UI you have had success or failure with. For example...

Compaq C500 (laptop)
Onboard video
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)
720p - Internal Display
UI2 no alpha
works swimmingly

Acer Aspire L5100 (nettop)
Onboard video
Flags: bus master, VGA palette snoop, 66MHz, medium devsel, latency 64
01:05.0 VGA compatible controller: ATI Technologies Inc RS690 [Radeon X1200 Series] (prog-if 00 [VGA controller])
1080p DVI - 24in lcd monitor
UI2 no alpha
no tearing, sluggish with screen saver activated

VIA Jetway J7F2WE1G2ES-LF (micro-itx)
Onboard video
01:00.0 VGA compatible controller: VIA Technologies, Inc. CN700/P4M800 Pro/P4M800 CE/VN800 [S3 UniChrome Pro] (rev 01)
1024x748 VGA - serial 3M MicroTouch 19 LCD
UI2 no alpha is sluggish, oddly Screensaver is not as bad for it as ATI. I use UI1 anyway as is touchscreen.

Dell OptiPlex 740 DCCY
Onboard video
00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)
1024x768 VGA - 19" LCD
UI2 no alpha
Flawless



We know nVidia work well. No need for them in this thread. Thanks again.

*** I might point out a few side effects I have worked out and written into the code as well.


I have to finish the DVD before I can give access to these things.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: JaseP on March 20, 2012, 02:25:02 pm
Sorry in advance for the following "book" ... And thanks, l3mce for your hard work,...

I fell asleep last night doing the reinstall, so never finished (been fighting off a cold,... that's my excuse). Might get the opportunity to finish tonight, ... Might, to re-emphasize. I keep my /home partitions intact (no reformatting that partition), and want to clean up the junk on the core's /home,... it's looking like a flea marketeer's back room on that partition.

I'll try to compile my list of machines over the next couple of days. I haven't set up any of the MDs yet... I had taken them off of net boot a while back. The only machine I have worries about is an ASUS eeePC Box 202, from a video playback perspective, but I understand that others have made that model work.

Currently, only the core is being worked on. I have 3 MDs (the ASUS being one), as well. The other two are Dell Studio Hybrids (nice machines, too bad they were discontinued, very stylish small footprint machines, and dual core too). Two more MDs are being ordered, but they won't be pressed into immediate service (I'll be using them for RHCSA/RHCE lab machines, then afterwards as MDs when I pass my certs). They'll be quad core Intels on small footprint motherboards with nVidia video cards on riser expansions.

All my Monitors are LCD TVs (all Sanyo, a good compromise between features, picture and price). One of the TVs (plus another, currently unused) has no VGA input, HDMI only, so it can be a nice testbed for mode line settings (nasty overscan on that machine), and testing the overscan settings in the avwizard. I'll be getting two new Sanyo 26-32"  TVs as monitors for the new MDs (maybe some switching around of what MDs are in what rooms, no sense in giving the kids the quad cores). Why all Sanyo?!?! To make future IR setup easier, by sticking with one brand (I have a bunch of those keychain sized universal remotes, and staying with one brand is great for keeping them strategically hidden throughout the house).

The rest of the system includes a MCV Vera (as external network and z-wave master controller), 2 HDhomeruns, an
Obi110 ATA for VOIP/POTS bridging, and maybe a SP3201 ATA that'd otherwise be gathering dust (the Obi110 and the Linksys/Sipura were developed by the same folks, so I'm hoping to follow the Wiki on the Sipura to get both working).

So you can see it's an ambitious system setup,... In all, about $6k to $7k of stuff, including TVs,... All I need is a a couple of more Z-wave units for a basement room we're building, another security cam or two, ... and maybe an R2 unit to fix it all   ;) . So, it'll be a great testbed for anything you want to throw at it, and I'll be happy to help out there. I've seen a few really cool ideas thrown out by folks on the forums.

Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: l3mce on March 20, 2012, 03:12:21 pm
TY for the update, and your future updates.

You might give the DVD snapshot a try when it is finished. This one should be close to working, and will give you the ability to do a "side by side" install. It is much faster than the current install process as well. Most of the system is pre-installed on the dvd. The new one (with all the detection stuff) is on its way (the previous one that works does not have new detection, the current several ones have detection but do not install). So you could just isolate that home folder on its own partition, and the dvd will make a new partition for you. Just a thought.
http://linuxmce.iptp.org/snapshots/

Again... when it is available (in 5 hrs or so) it will be completely untested... and desktop is purposefully broken. I will tell you how to undo it if you want it back.

As a side note. I can make your GMA 500 work. It requires its own version of X though, so that probably means screwing with pluto depends... so it goes in the "one day" pile. It will run with compositing.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: JaseP on March 21, 2012, 07:01:37 pm
Thanks,

No need to kill yourself on the GMA 500. You'll end up wanting to beat your head against a brick wall with that chipset. You can't get full function out of it with an Xorg newer than the one from Ubuntu 9.10 (vers. 1.7, I think). That means rebuilding everything that links to the Xorg. I'm going the other way with it and rebuilding the kernel in 9.10 to support the other devices the gadget has (equally problematic, and I suspect the devices were specifically chosen to thwart porting Linux to the thing). My main use for that machine will be as a car computer (it has mounting brackets and everything).

I intend to finish my LMCE install tonight. I got as far as reinstalling Kubuntu and cleaning some junk on it up. The LMCE 10.04 install will follow tonight.

I might try the side by side install with the DVD later, maybe this weekend. You say it has no KDE desktop available, I might want to put it back. I'm very comfortable with a command line interface, but I prefer the graphical tools anyway. I'll ask you about it when I try the DVD install. I'd have to adjust partitions, though. My core currently has 3, the main, home and a small swap. I'd need a fourth for a whole new OS. The gParted stand alone distro allows for easy shrinking and growing of partitions, and the app can do it as well.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: l3mce on March 22, 2012, 04:51:46 am
The GMA 500 has already been done on 1004... that is why I know it requires its own version of X.

The newer DVDs should have desktop back. Testing is needed on the DVDs before they are ready for prime time.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: JaseP on March 22, 2012, 02:17:01 pm


OK,... Install went relatively smooth. I didn't turn on all my stuff yet, or set up my TV cards, etc. But basic functions are working. The chipset is a GMA series (probably 3100 series). UI2 with Alpha blending working fine. Sound works.

So, ... nice work l3mce!

I noticed that the room setup sometimes has a hickup and pops you back out to the beginning of the sequence (I then fast forward back to room setup). This happens most often when renaming rooms. It seems to be something being detected that knocks you out that way. Not a show stopper, but it might scare a newbie a little. I assume it is possible to fix room names in the Web Admin utility. It might be something that is system dependent,  and may not happen on all different types of hardware.

Question: Is it possible to add the Intel microcode deb packages if you detect an Intel chipset at start-up? The Intel microcode stuff adds small tweaks to the Intel firmware that Intel has come up with since releasing the chipset. So it helps stability, etc. I've never noticed dramatic improvement with it, but have noticed small improvements (i.e.: recovering from suspends and hybernation less quirky, that sort of thing).

2nd Question: Does the multimedia scanning check hidden directories (those with a "." in front), and if so, is there a way to toggle that to off? I'd like to be able to remove from the system's "sight" duplicate media files that may exist on more than one hard drive.

PS: If you really want to mess with the GMA 500, by all means go to it. But I honestly cannot commit to testing it, as the particulars of my device (a Viliv S5) are such that I am better off locking the machine down with a tweaked and reworked version of Ubuntu 9.10, rather than testing anything else. The machine has problematic other peripherals as well, such as it's wireless chipset, touch screen controller, and GPS chipsets that make 9.10 the best convergence point. Older versions break some hardware, newer versions break other hardware (the Marvel SD8686 wireless chipset being particularly troublesome there). There are quite a few inexpensive Chinese import x86 tablets that use the GMA 500, though. They would make excellent orbiters. The GMA500 has good performance for a mobile chipset, when you can get it working 100%. So, working on it may actually prove beneficial, and open up LinuxMCE enthusiasts to some inexpensive,  yet powerful tablet/Orbiter devices.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: Marie.O on March 22, 2012, 09:19:21 pm
The 2nd question would have been better of in a new thread, but I think a search for folder lock on the wiki might be helpful.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: JaseP on March 22, 2012, 10:12:01 pm
That answers it then, thanks.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: phenigma on March 23, 2012, 09:14:59 pm
  • Video Cards are completely plug n play now. If you swap cards, it will know. So if you upgrade your onboard nvidia 8200 for instance to a GT260, it will know, purge the old driver and install the appropriate one for you.

Hmm, this is causing me problems with a net install on 1004.  The AVWizard pops up after each and every reboot.  I complete it successfully and orbiter loads, etc, etc... on reboot the AVWizard returns every time.  This may be fixed by issues you mentioned earlier and the newer 20120321 build, I'll check it tonight.

With an unknown video card the AVWizard was NOT creating an xorg.conf which was causing X to crash.

I have a patch, that I will submit tonight, that adds virtualbox video driver detection to your re-worded scripts so X (avwizard, orbiter, etc) will load in virtualbox.

J.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: JaseP on March 23, 2012, 09:58:09 pm
phenigma,

Have you tested virtualbox against the new installer DVD??? What's your experience with running inside of virtualbox??? Positive? Negative? OK, but with issues?

Have you tried KVM at all.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: phenigma on March 24, 2012, 12:35:08 am
phenigma,

Have you tested virtualbox against the new installer DVD??? What's your experience with running inside of virtualbox??? Positive? Negative? OK, but with issues?

Have you tried KVM at all.

Please do not take this the wrong way JaseP, I mean no disrespect, but I do not intend to hijack this thread for a discussion of these topics.  In short: No, varied, depends, sometimes, definitely.  You should search the forum, there have been numerous discussions of running lmce under virtual box and there is more knowledge there than I have about the topic.  Wiki probably has topics too.  I'd be happy to respond to a PM or discuss this in a new topic.

To be on topic: I find lmce works best on virtualbox with the vboxvideo driver enabled rather than the default vesa driver.

J.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: ardirtbiker on March 24, 2012, 02:33:21 am
I recently ran an update on my core/hybrid.. its got an onboard ati rage xl card that usually uses the mach64 kernel module... however the new installer detects the board and is trying to install the fglrx module.. it crashes.. I cant even figure out how to get it to get past this so that it finishes booting to the UI1.

Ive tried disabling my onboard video and install a PCI nVidia card... but it seems to be having issues getting it working as well

The nvidia card info is

03:00.0 VGA compatible controller [0300]: nVidia Corporation G98 [GeForce 8400 GS] [10de:06e4] (rev a1)
        Subsystem: eVga.com. Corp. Device [3842:b724]
        Flags: bus master, fast devsel, latency 0, IRQ 26
        Memory at f3000000 (32-bit, non-prefetchable) [size=16M]
        Memory at d0000000 (64-bit, prefetchable) [size=256M]
        Memory at f4000000 (64-bit, non-prefetchable) [size=32M]
        I/O ports at ac00 [size=128]
        [virtual] Expansion ROM at f67e0000 [disabled] [size=128K]
        Capabilities: [60] Power Management version 3
        Capabilities: [68] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
        Capabilities: [78] Express Endpoint, MSI 00
        Kernel driver in use: nvidia
        Kernel modules: nvidia-glx-260, nvidiafb, nouveau

I'd have to shut it down and re-enable the Rage XL card to get that info.

Dennis
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: l3mce on March 24, 2012, 06:56:49 am
phenigma... that should absolutely not be occurring anymore.

Please give me a pastebin of /usr/pluto/bin/Utils.sh and /etc/init.d/0start_avwizard

Very sorry for the trouble. Will fix immediately if you are indeed at the newest versions.



Dennis: I have never heard of that driver. I will put in a fix. Thanks for giving it a go.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: huh on March 24, 2012, 07:09:30 am
Dell Latitude C400, ui2 with alpha is a little laggy, so went to ui2 w/o alpha...  about 1/2" of what should have been the far right of the display was displaced on the left hand side.  Will run through AVWizard again later..  output of 'lspci -v | grep "VGA"'

00:02.0 VGA compatible controller: Intel Corporation 82830 CGC [Chipset Graphics Controller] (rev 04)
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: bongowongo on March 24, 2012, 09:12:45 am
phenigma,

Have you tested virtualbox against the new installer DVD??? What's your experience with running inside of virtualbox??? Positive? Negative? OK, but with issues?

Have you tried KVM at all.


JaseP all the snapshots that work with VirtualBox are listed here.
http://wiki.linuxmce.org/index.php/Snapshot_overview
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: dextaslab on March 24, 2012, 02:11:54 pm
Hmm, this is causing me problems with a net install on 1004.  The AVWizard pops up after each and every reboot.  I complete it successfully and orbiter loads, etc, etc... on reboot the AVWizard returns every time.  This may be fixed by issues you mentioned earlier and the newer 20120321 build, I'll check it tonight.

Same here, I have run apt-get upgrade on the MD and the Core is already updated, I have attached the Utils.sh and 0start_avwizard as text files.

Chipset is:  VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)
It detects it correctly as an intel driver in xorg.conf

Cheers
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: ardirtbiker on March 24, 2012, 02:55:44 pm
Here is the lspci -nnv output for the ATI Rage XL card:

03:06.0 VGA compatible controller [0300]: ATI Technologies Inc Rage XL [1002:4752] (rev 27)
        Subsystem: ATI Technologies Inc Device [1002:8008]
        Flags: bus master, stepping, medium devsel, latency 64, IRQ 11
        Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
        I/O ports at b000 [size=256]
        Memory at feaff000 (32-bit, non-prefetchable) [size=4K]
        Expansion ROM at feac0000 [disabled] [size=128K]
        Capabilities: [5c] Power Management version 2
        Kernel modules: atyfb

Xorg document dated Feb 2012:  http://www.x.org/releases/X11R7.5/doc/ati.html (http://www.x.org/releases/X11R7.5/doc/ati.html)

According to the document there is an 'ati' driver for use with this chipset.  

the xserver-xorg-video-ati package IS already installed.   There is a driver named ati_drv.so AND a driver named mach64_drv.so in /usr/lib/xorg/modules/drivers


With Driver  "ati"   set in xorg.conf  running startx brings up the kde desktop.   here is output of Xorg.0.log:
Code: [Select]

X.Org X Server 1.7.6
Release Date: 2010-03-17
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-29-server i686 Ubuntu
Current Operating System: Linux dcerouter 2.6.32-40-generic-pae #87-Ubuntu SMP Mon Mar 5 21:44:34 UTC 2012 i686
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-40-generic-pae root=UUID=a698baa3-0241-4042-96f8-d186b58407b2 ro quiet
Build Date: 25 February 2012  06:59:39AM
xorg-server 2:1.7.6-2ubuntu7.11 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.21.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
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: Sat Mar 24 09:02:20 2012
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using config directory: "/usr/lib/X11/xorg.conf.d"
(==) ServerLayout "X.org Configured"
(**) |-->Screen "Screen0" (0)
(**) |   |-->Monitor "Monitor0"
(**) |   |-->Device "Card0"
(**) |-->Input Device "Mouse0"
(**) |-->Input Device "Keyboard0"
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
Entry deleted from font path.
(**) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,
built-ins,
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,
built-ins
(**) ModulePath set to "/usr/lib/xorg/modules"
(WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
(WW) Disabling Mouse0
(WW) Disabling Keyboard0
(II) Loader magic: 0x81f0e80
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 6.0
X.Org XInput driver : 7.0
X.Org Server Extension : 2.0
(--) using VT number 1

(--) PCI: (0:1:3:0) 14f1:8800:0070:6906 Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder rev 5, Mem @ 0xf0000000/16777216
(--) PCI: (0:2:3:0) 14f1:8800:7063:5500 Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder rev 5, Mem @ 0xf8000000/16777216
(--) PCI:*(0:3:6:0) 1002:4752:1002:8008 ATI Technologies Inc Rage XL rev 39, Mem @ 0xfd000000/16777216, 0xfeaff000/4096, I/O @ 0x0000b000/256, BIOS @ 0x????????/131072
(II) Open ACPI successful (/var/run/acpid.socket)
(II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
(II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
(II) "glx" will be loaded. This was enabled by default and also specified in the config file.
(II) "record" will be loaded. This was enabled by default and also specified in the config file.
(II) "dri" will be loaded. This was enabled by default and also specified in the config file.
(II) "dri2" will be loaded. This was enabled by default and also specified in the config file.
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions/librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 1.7.6, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension RECORD
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions/libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 1.7.6, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions/libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.7.6, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.7.6, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.7.6, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dri2"
(II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
compiled for 1.7.6, module version = 1.1.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "ati"
(II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
(II) Module ati: vendor="X.Org Foundation"
compiled for 1.7.6, module version = 6.13.1
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 6.0
(II) LoadModule: "mach64"
(II) Loading /usr/lib/xorg/modules/drivers/mach64_drv.so
(II) Module mach64: vendor="X.Org Foundation"
compiled for 1.7.2, module version = 6.8.2
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 6.0
(II) MACH64: Driver for ATI Mach64 chipsets
(II) Primary Device is: PCI 03@00:06:0
(==) MACH64(0): Depth 24, (--) framebuffer bpp 32
(==) MACH64(0): Using XAA acceleration architecture
(II) MACH64: Mach64 in slot 3:6:0 detected.
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Loading /usr/lib/xorg/modules/libint10.so
(II) Module int10: vendor="X.Org Foundation"
compiled for 1.7.6, module version = 1.0.0
ABI class: X.Org Video Driver, version 6.0
(II) MACH64(0): Primary V_BIOS segment is: 0xc000
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(II) Loading sub module "vbe"
(II) LoadModule: "vbe"
(II) Loading /usr/lib/xorg/modules/libvbe.so
(II) Module vbe: vendor="X.Org Foundation"
compiled for 1.7.6, module version = 1.1.0
ABI class: X.Org Video Driver, version 6.0
(II) MACH64(0): VESA BIOS detected
(II) MACH64(0): VESA VBE Version 2.0
(II) MACH64(0): VESA VBE Total Mem: 8128 kB
(II) MACH64(0): VESA VBE OEM: ATI MACH64
(II) MACH64(0): VESA VBE OEM Software Rev: 1.0
(II) MACH64(0): VESA VBE OEM Vendor: ATI Technologies Inc.
(II) MACH64(0): VESA VBE OEM Product: MACH64GM
(II) MACH64(0): VESA VBE OEM Product Rev: 01.00
(II) MACH64(0): VESA VBE DDC supported
(II) MACH64(0): VESA VBE DDC Level 2
(II) MACH64(0): VESA VBE DDC transfer in appr. 2 sec.
(II) MACH64(0): VESA VBE DDC read successfully
(II) MACH64(0): Manufacturer: SAM  Model: 191  Serial#: 1112092983
(II) MACH64(0): Year: 2005  Week: 11
(II) MACH64(0): EDID Version: 1.3
(II) MACH64(0): Analog Display Input,  Input Voltage Level: 0.700/0.300 V
(II) MACH64(0): Sync:  Separate  Composite  SyncOnGreen
(II) MACH64(0): Max Image Size [cm]: horiz.: 34  vert.: 27
(II) MACH64(0): Gamma: 2.20
(II) MACH64(0): DPMS capabilities: Off; RGB/Color Display
(II) MACH64(0): First detailed timing is preferred mode
(II) MACH64(0): redX: 0.650 redY: 0.330   greenX: 0.330 greenY: 0.600
(II) MACH64(0): blueX: 0.150 blueY: 0.080   whiteX: 0.313 whiteY: 0.329
(II) MACH64(0): Supported established timings:
(II) MACH64(0): 720x400@70Hz
(II) MACH64(0): 640x480@60Hz
(II) MACH64(0): 640x480@67Hz
(II) MACH64(0): 640x480@72Hz
(II) MACH64(0): 640x480@75Hz
(II) MACH64(0): 800x600@56Hz
(II) MACH64(0): 800x600@60Hz
(II) MACH64(0): 800x600@72Hz
(II) MACH64(0): 800x600@75Hz
(II) MACH64(0): 832x624@75Hz
(II) MACH64(0): 1024x768@60Hz
(II) MACH64(0): 1024x768@70Hz
(II) MACH64(0): 1024x768@75Hz
(II) MACH64(0): 1280x1024@75Hz
(II) MACH64(0): 1152x864@75Hz
(II) MACH64(0): Manufacturer's mask: 0
(II) MACH64(0): Supported standard timings:
(II) MACH64(0): #0: hsize: 1280  vsize 1024  refresh: 60  vid: 32897
(II) MACH64(0): #1: hsize: 1280  vsize 960  refresh: 60  vid: 16513
(II) MACH64(0): #2: hsize: 1152  vsize 864  refresh: 75  vid: 20337
(II) MACH64(0): Supported detailed timing:
(II) MACH64(0): clock: 108.0 MHz   Image Size:  338 x 270 mm
(II) MACH64(0): h_active: 1280  h_sync: 1328  h_sync_end 1440 h_blank_end 1688 h_border: 0
(II) MACH64(0): v_active: 1024  v_sync: 1025  v_sync_end 1028 v_blanking: 1066 v_border: 0
(II) MACH64(0): Ranges: V min: 56 V max: 75 Hz, H min: 30 H max: 81 kHz, PixClock max 140 MHz
(II) MACH64(0): Monitor name: SyncMaster
(II) MACH64(0): Serial No: HCJY329690
(II) MACH64(0): EDID (in hex):
(II) MACH64(0): 00ffffffffffff004c2d910137314942
(II) MACH64(0): 0b0f01030e221b782aaaa5a654549926
(II) MACH64(0): 145054bfef8081808140714f01010101
(II) MACH64(0): 010101010101302a009851002a403070
(II) MACH64(0): 1300520e1100001e000000fd00384b1e
(II) MACH64(0): 510e000a202020202020000000fc0053
(II) MACH64(0): 796e634d61737465720a2020000000ff
(II) MACH64(0): 0048434a593332393639300a20200076
(II) MACH64(0): EDID vendor "SAM", prod id 401
(II) MACH64(0): Using hsync ranges from config file
(II) MACH64(0): Using vrefresh ranges from config file
(II) MACH64(0): Printing DDC gathered Modelines:
(II) MACH64(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
(II) MACH64(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz)
(II) MACH64(0): Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz)
(II) MACH64(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz)
(II) MACH64(0): Modeline "640x480"x0.0   31.50  640 664 704 832  480 489 492 520 -hsync -vsync (37.9 kHz)
(II) MACH64(0): Modeline "640x480"x0.0   30.24  640 704 768 864  480 483 486 525 -hsync -vsync (35.0 kHz)
(II) MACH64(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz)
(II) MACH64(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz)
(II) MACH64(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
(II) MACH64(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz)
(II) MACH64(0): Modeline "1024x768"x0.0   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz)
(II) MACH64(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz)
(II) MACH64(0): Modeline "832x624"x0.0   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync (49.7 kHz)
(II) MACH64(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz)
(II) MACH64(0): Modeline "800x600"x0.0   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz)
(II) MACH64(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz)
(II) MACH64(0): Modeline "1280x960"x0.0  108.00  1280 1376 1488 1800  960 961 964 1000 +hsync +vsync (60.0 kHz)
(II) MACH64(0): BIOS Data:  BIOSSize=0x8000, ROMTable=0x0114.
(II) MACH64(0): BIOS Data:  ClockTable=0x097C, FrequencyTable=0x0000.
(II) MACH64(0): BIOS Data:  LCDTable=0x0000.
(II) MACH64(0): BIOS Data:  VideoTable=0x0000, HardwareTable=0x015E.
(II) MACH64(0): BIOS Data:  I2CType=0x0F, Tuner=0x00, Decoder=0x00, Audio=0x0F.
(--) MACH64(0): ATI 3D Rage XL or XC graphics controller detected.
(--) MACH64(0): Chip type 4752 "GR", version 7, foundry TSMC, class 0, revision 0x00.
(--) MACH64(0): PCI bus interface detected;  block I/O base is 0xB000.
(--) MACH64(0): ATI Mach64 adapter detected.
(!!) MACH64(0): For information on using the multimedia capabilities
of this adapter, please see http://gatos.sf.net.
(--) MACH64(0): Internal RAMDAC (subtype 1) detected.
(==) MACH64(0): RGB weight 888
(==) MACH64(0): Default visual is TrueColor
(==) MACH64(0): Using gamma correction (1.0, 1.0, 1.0)
(II) MACH64(0): Using Mach64 accelerator CRTC.
(II) MACH64(0): Storing hardware cursor image at 0xFD7FFC00.
(II) MACH64(0): Using 8 MB linear aperture at 0xFD000000.
(!!) MACH64(0): Virtual resolutions will be limited to 8191 kB
 due to linear aperture size and/or placement of hardware cursor image area.
(II) MACH64(0): Using Block 0 MMIO aperture at 0xFEAFF400.
(II) MACH64(0): Using Block 1 MMIO aperture at 0xFEAFF000.
(II) MACH64(0): MMIO write caching enabled.
(--) MACH64(0): 8192 kB of SGRAM (2:1) 32-bit detected (using 8191 kB).
(WW) MACH64(0): Cannot shadow an accelerated frame buffer.
(II) MACH64(0): Engine XCLK 62.353 MHz;  Refresh rate code 1.
(--) MACH64(0): Internal programmable clock generator detected.
(--) MACH64(0): Reference clock 157.5/11 (14.318) MHz.
(II) MACH64(0): Monitor0: Using hsync range of 30.00-81.00 kHz
(II) MACH64(0): Monitor0: Using vrefresh range of 56.00-75.00 Hz
(II) MACH64(0): Monitor0: Using maximum pixel clock of 140.00 MHz
(II) MACH64(0): Estimated virtual size for aspect ratio 1.2593 is 1280x1024
(II) MACH64(0): Maximum clock: 124.00 MHz
(II) MACH64(0): Not using default mode "640x350" (vrefresh out of range)
(II) MACH64(0): Not using default mode "320x175" (vrefresh out of range)
(II) MACH64(0): Not using default mode "640x400" (vrefresh out of range)
(II) MACH64(0): Not using default mode "320x200" (vrefresh out of range)
(II) MACH64(0): Not using default mode "720x400" (vrefresh out of range)
(II) MACH64(0): Not using default mode "360x200" (vrefresh out of range)
(II) MACH64(0): Not using default mode "640x480" (vrefresh out of range)
(II) MACH64(0): Not using default mode "320x240" (vrefresh out of range)
(II) MACH64(0): Not using default mode "800x600" (vrefresh out of range)
(II) MACH64(0): Not using default mode "400x300" (vrefresh out of range)
(II) MACH64(0): Not using default mode "1024x768" (vrefresh out of range)
(II) MACH64(0): Not using default mode "512x384" (vrefresh out of range)
(II) MACH64(0): Not using default mode "1024x768" (vrefresh out of range)
(II) MACH64(0): Not using default mode "512x384" (vrefresh out of range)
(II) MACH64(0): Not using default mode "1280x960" (bad mode clock/interlace/doublescan)
(II) MACH64(0): Not using default mode "640x480" (hsync out of range)
(II) MACH64(0): Not using default mode "1280x1024" (bad mode clock/interlace/doublescan)
(II) MACH64(0): Not using default mode "1280x1024" (bad mode clock/interlace/doublescan)
(II) MACH64(0): Not using default mode "640x512" (hsync out of range)
(II) MACH64(0): Not using default mode "1600x1200" (width too large for virtual size)
(II) MACH64(0): Not using default mode "1600x1200" (width too large for virtual size)
(II) MACH64(0): Not using default mode "1600x1200" (width too large for virtual size)
(II) MACH64(0): Not using default mode "800x600" (hsync out of range)
(II) MACH64(0): Not using default mode "1600x1200" (width too large for virtual size)
(II) MACH64(0): Not using default mode "800x600" (hsync out of range)
(II) MACH64(0): Not using default mode "1600x1200" (width too large for virtual size)
(II) MACH64(0): Not using default mode "800x600" (hsync out of range)
(II) MACH64(0): Not using default mode "1792x1344" (insufficient memory for mode)
(II) MACH64(0): Not using default mode "896x672" (hsync out of range)
(II) MACH64(0): Not using default mode "1792x1344" (insufficient memory for mode)
(II) MACH64(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan)
(II) MACH64(0): Not using default mode "1856x1392" (insufficient memory for mode)
(II) MACH64(0): Not using default mode "928x696" (hsync out of range)
(II) MACH64(0): Not using default mode "1856x1392" (insufficient memory for mode)
(II) MACH64(0): Not using default mode "928x696" (bad mode clock/interlace/doublescan)
(II) MACH64(0): Not using default mode "1920x1440" (insufficient memory for mode)
(II) MACH64(0): Not using default mode "960x720" (hsync out of range)
(II) MACH64(0): Not using default mode "1920x1440" (insufficient memory for mode)
(II) MACH64(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan)
(II) MACH64(0): Not using default mode "1152x864" (vrefresh out of range)
(II) MACH64(0): Not using default mode "576x432" (vrefresh out of range)
(II) MACH64(0): Not using default mode "1152x864" (vrefresh out of range)
(II) MACH64(0): Not using default mode "576x432" (vrefresh out of range)
(II) MACH64(0): Not using default mode "1152x864" (bad mode clock/interlace/doublescan)
(II) MACH64(0): Not using default mode "576x432" (hsync out of range)
(II) MACH64(0): Not using default mode "1360x768" (width too large for virtual size)
(II) MACH64(0): Not using default mode "1360x768" (width too large for virtual size)
(II) MACH64(0): Not using default mode "1400x1050" (width too large for virtual size)
(II) MACH64(0): Not using default mode "1400x1050" (width too large for virtual size)
(II) MACH64(0): Not using default mode "1400x1050" (width too large for virtual size)
(II) MACH64(0): Not using default mode "1400x1050" (width too large for virtual size)
(II) MACH64(0): Not using default mode "700x525" (hsync out of range)
(II) MACH64(0): Not using default mode "1440x900" (width too large for virtual size)
(II) MACH64(0): Not using default mode "1600x1024" (width too large for virtual size)
(II) MACH64(0): Not using default mode "1680x1050" (width too large for virtual size)
(II) MACH64(0): Not using default mode "1680x1050" (width too large for virtual size)
(II) MACH64(0): Not using default mode "1680x1050" (width too large for virtual size)
(II) MACH64(0): Not using default mode "1680x1050" (width too large for virtual size)
(II) MACH64(0): Not using default mode "840x525" (hsync out of range)
(II) MACH64(0): Not using default mode "1680x1050" (width too large for virtual size)
(II) MACH64(0): Not using default mode "840x525" (hsync out of range)
(II) MACH64(0): Not using default mode "1920x1080" (width too large for virtual size)
(II) MACH64(0): Not using default mode "1920x1200" (insufficient memory for mode)
(II) MACH64(0): Not using default mode "1920x1440" (insufficient memory for mode)
(II) MACH64(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan)
(II) MACH64(0): Not using default mode "2048x1536" (insufficient memory for mode)
(II) MACH64(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(II) MACH64(0): Not using default mode "2048x1536" (insufficient memory for mode)
(II) MACH64(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(II) MACH64(0): Not using default mode "2048x1536" (insufficient memory for mode)
(II) MACH64(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(II) MACH64(0): Not using driver mode "1280x1024" (bad mode clock/interlace/doublescan)
(--) MACH64(0): Virtual size is 1280x1024 (pitch 1280)
(**) MACH64(0): *Driver mode "1280x1024": 108.0 MHz, 64.0 kHz, 60.0 Hz
(II) MACH64(0): Modeline "1280x1024"x60.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
(**) MACH64(0): *Default mode "1280x1024": 108.0 MHz, 64.0 kHz, 60.0 Hz
(II) MACH64(0): Modeline "1280x1024"x60.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
(**) MACH64(0): *Driver mode "1280x960": 108.0 MHz, 60.0 kHz, 60.0 Hz
(II) MACH64(0): Modeline "1280x960"x60.0  108.00  1280 1376 1488 1800  960 961 964 1000 +hsync +vsync (60.0 kHz)
(**) MACH64(0): *Default mode "1280x960": 108.0 MHz, 60.0 kHz, 60.0 Hz
(II) MACH64(0): Modeline "1280x960"x60.0  108.00  1280 1376 1488 1800  960 961 964 1000 +hsync +vsync (60.0 kHz)
(**) MACH64(0): *Driver mode "1152x864": 108.0 MHz, 67.5 kHz, 75.0 Hz
(II) MACH64(0): Modeline "1152x864"x75.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz)
(**) MACH64(0): *Default mode "1152x864": 108.0 MHz, 67.5 kHz, 75.0 Hz
(II) MACH64(0): Modeline "1152x864"x75.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz)
(**) MACH64(0): *Default mode "1152x864": 105.0 MHz, 67.6 kHz, 75.0 Hz
(II) MACH64(0): Modeline "1152x864"x75.0  104.99  1152 1224 1352 1552  864 865 868 902 -hsync +vsync (67.6 kHz)
(**) MACH64(0): *Default mode "1152x864": 96.8 MHz, 63.0 kHz, 70.0 Hz
(II) MACH64(0): Modeline "1152x864"x70.0   96.77  1152 1224 1344 1536  864 865 868 900 -hsync +vsync (63.0 kHz)
(**) MACH64(0): *Default mode "1152x864": 81.6 MHz, 53.7 kHz, 60.0 Hz
(II) MACH64(0): Modeline "1152x864"x60.0   81.62  1152 1216 1336 1520  864 865 868 895 -hsync +vsync (53.7 kHz)
(**) MACH64(0): *Driver mode "1024x768": 78.8 MHz, 60.0 kHz, 75.0 Hz
(II) MACH64(0): Modeline "1024x768"x75.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz)
(**) MACH64(0): *Driver mode "1024x768": 75.0 MHz, 56.5 kHz, 70.1 Hz
(II) MACH64(0): Modeline "1024x768"x70.1   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz)
(**) MACH64(0): *Driver mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz
(II) MACH64(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz)
(**) MACH64(0): *Default mode "1024x768": 78.8 MHz, 60.0 kHz, 75.0 Hz
(II) MACH64(0): Modeline "1024x768"x75.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz)
(**) MACH64(0): *Default mode "1024x768": 75.0 MHz, 56.5 kHz, 70.1 Hz
(II) MACH64(0): Modeline "1024x768"x70.1   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz)
(**) MACH64(0): *Default mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz
(II) MACH64(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz)
(**) MACH64(0): *Driver mode "832x624": 57.3 MHz, 49.7 kHz, 74.6 Hz
(II) MACH64(0): Modeline "832x624"x74.6   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync (49.7 kHz)
(**) MACH64(0): *Default mode "832x624": 57.3 MHz, 49.7 kHz, 74.6 Hz
(II) MACH64(0): Modeline "832x624"x74.6   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync (49.7 kHz)
(**) MACH64(0): *Driver mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz
(II) MACH64(0): Modeline "800x600"x75.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz)
(**) MACH64(0): *Driver mode "800x600": 50.0 MHz, 48.1 kHz, 72.2 Hz
(II) MACH64(0): Modeline "800x600"x72.2   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz)
(**) MACH64(0): *Driver mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz
(II) MACH64(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz)
(**) MACH64(0): *Driver mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz
(II) MACH64(0): Modeline "800x600"x56.2   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz)
(**) MACH64(0): *Default mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz
(II) MACH64(0): Modeline "800x600"x75.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz)
(**) MACH64(0): *Default mode "800x600": 50.0 MHz, 48.1 kHz, 72.2 Hz
(II) MACH64(0): Modeline "800x600"x72.2   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz)
(**) MACH64(0): *Default mode "800x600": 87.8 MHz, 81.2 kHz, 65.0 Hz (D)
(II) MACH64(0): Modeline "800x600"x65.0   87.75  800 832 928 1080  600 600 602 625 doublescan +hsync +vsync (81.2 kHz)
(**) MACH64(0): *Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz
(II) MACH64(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz)
(**) MACH64(0): *Default mode "800x600": 81.0 MHz, 75.0 kHz, 60.0 Hz (D)
(II) MACH64(0): Modeline "800x600"x60.0   81.00  800 832 928 1080  600 600 602 625 doublescan +hsync +vsync (75.0 kHz)
(**) MACH64(0): *Default mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz
(II) MACH64(0): Modeline "800x600"x56.2   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz)
(**) MACH64(0): *Default mode "840x525": 87.0 MHz, 76.6 kHz, 69.9 Hz (D)
(II) MACH64(0): Modeline "840x525"x69.9   87.00  840 900 988 1136  525 526 529 548 doublescan -hsync +vsync (76.6 kHz)
(**) MACH64(0): *Default mode "840x525": 73.1 MHz, 65.3 kHz, 60.0 Hz (D)
(II) MACH64(0): Modeline "840x525"x60.0   73.12  840 892 980 1120  525 526 529 544 doublescan -hsync +vsync (65.3 kHz)
(**) MACH64(0): *Default mode "700x525": 77.9 MHz, 81.5 kHz, 74.8 Hz (D)
(II) MACH64(0): Modeline "700x525"x74.8   77.90  700 732 892 956  525 526 532 545 doublescan +hsync +vsync (81.5 kHz)
(**) MACH64(0): *Default mode "700x525": 72.5 MHz, 76.5 kHz, 70.1 Hz (D)
(II) MACH64(0): Modeline "700x525"x70.1   72.53  700 748 824 948  525 525 527 546 doublescan -hsync +vsync (76.5 kHz)
(**) MACH64(0): *Default mode "700x525": 61.0 MHz, 64.9 kHz, 60.0 Hz (D)
(II) MACH64(0): Modeline "700x525"x60.0   61.00  700 744 820 940  525 526 532 541 doublescan +hsync +vsync (64.9 kHz)
(**) MACH64(0): *Default mode "640x512": 67.5 MHz, 80.0 kHz, 75.0 Hz (D)
(II) MACH64(0): Modeline "640x512"x75.0   67.50  640 648 720 844  512 512 514 533 doublescan +hsync +vsync (80.0 kHz)
(**) MACH64(0): *Default mode "640x512": 54.0 MHz, 64.0 kHz, 60.0 Hz (D)
(II) MACH64(0): Modeline "640x512"x60.0   54.00  640 664 720 844  512 512 514 533 doublescan +hsync +vsync (64.0 kHz)
(**) MACH64(0): *Default mode "720x450": 53.2 MHz, 55.9 kHz, 59.9 Hz (D)
(II) MACH64(0): Modeline "720x450"x59.9   53.25  720 760 836 952  450 451 454 467 doublescan -hsync +vsync (55.9 kHz)
(**) MACH64(0): *Driver mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz
(II) MACH64(0): Modeline "640x480"x75.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz)
(**) MACH64(0): *Driver mode "640x480": 31.5 MHz, 37.9 kHz, 72.8 Hz
(II) MACH64(0): Modeline "640x480"x72.8   31.50  640 664 704 832  480 489 492 520 -hsync -vsync (37.9 kHz)
(**) MACH64(0): *Driver mode "640x480": 30.2 MHz, 35.0 kHz, 66.7 Hz
(II) MACH64(0): Modeline "640x480"x66.7   30.24  640 704 768 864  480 483 486 525 -hsync -vsync (35.0 kHz)
(**) MACH64(0): *Driver mode "640x480": 25.2 MHz, 31.5 kHz, 59.9 Hz
(II) MACH64(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz)
(**) MACH64(0): *Default mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz
(II) MACH64(0): Modeline "640x480"x75.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz)
(**) MACH64(0): *Default mode "640x480": 31.5 MHz, 37.9 kHz, 72.8 Hz
(II) MACH64(0): Modeline "640x480"x72.8   31.50  640 664 704 832  480 489 492 520 -hsync -vsync (37.9 kHz)
(**) MACH64(0): *Default mode "640x480": 54.0 MHz, 60.0 kHz, 60.0 Hz (D)
(II) MACH64(0): Modeline "640x480"x60.0   54.00  640 688 744 900  480 480 482 500 doublescan +hsync +vsync (60.0 kHz)
(**) MACH64(0): *Default mode "640x480": 25.2 MHz, 31.5 kHz, 59.9 Hz
(II) MACH64(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz)
(**) MACH64(0): *Driver mode "720x400": 28.3 MHz, 31.5 kHz, 70.1 Hz
(II) MACH64(0): Modeline "720x400"x70.1   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz)
(**) MACH64(0): *Default mode "680x384": 36.0 MHz, 47.4 kHz, 60.0 Hz (D)
(II) MACH64(0): Modeline "680x384"x60.0   36.00  680 704 720 760  384 385 390 395 doublescan +hsync -vsync (47.4 kHz)
(**) MACH64(0): *Default mode "680x384": 42.4 MHz, 47.7 kHz, 59.8 Hz (D)
(II) MACH64(0): Modeline "680x384"x59.8   42.38  680 716 784 888  384 385 390 399 doublescan -hsync +vsync (47.7 kHz)
(**) MACH64(0): *Default mode "576x432": 54.0 MHz, 67.5 kHz, 75.0 Hz (D)
(II) MACH64(0): Modeline "576x432"x75.0   54.00  576 608 672 800  432 432 434 450 doublescan +hsync +vsync (67.5 kHz)
(**) MACH64(0): *Default mode "576x432": 52.5 MHz, 67.6 kHz, 75.0 Hz (D)
(II) MACH64(0): Modeline "576x432"x75.0   52.49  576 612 676 776  432 432 434 451 doublescan -hsync +vsync (67.6 kHz)
(**) MACH64(0): *Default mode "576x432": 48.4 MHz, 63.0 kHz, 70.0 Hz (D)
(II) MACH64(0): Modeline "576x432"x70.0   48.38  576 612 672 768  432 432 434 450 doublescan -hsync +vsync (63.0 kHz)
(**) MACH64(0): *Default mode "576x432": 40.8 MHz, 53.7 kHz, 60.1 Hz (D)
(II) MACH64(0): Modeline "576x432"x60.1   40.81  576 608 668 760  432 432 434 447 doublescan -hsync +vsync (53.7 kHz)
(**) MACH64(0): *Default mode "512x384": 39.4 MHz, 60.0 kHz, 75.0 Hz (D)
(II) MACH64(0): Modeline "512x384"x75.0   39.38  512 520 568 656  384 384 386 400 doublescan +hsync +vsync (60.0 kHz)
(**) MACH64(0): *Default mode "512x384": 37.5 MHz, 56.5 kHz, 70.1 Hz (D)
(II) MACH64(0): Modeline "512x384"x70.1   37.50  512 524 592 664  384 385 388 403 doublescan -hsync -vsync (56.5 kHz)
(**) MACH64(0): *Default mode "512x384": 32.5 MHz, 48.4 kHz, 60.0 Hz (D)
(II) MACH64(0): Modeline "512x384"x60.0   32.50  512 524 592 672  384 385 388 403 doublescan -hsync -vsync (48.4 kHz)
(**) MACH64(0): *Default mode "416x312": 28.6 MHz, 49.7 kHz, 74.7 Hz (D)
(II) MACH64(0): Modeline "416x312"x74.7   28.64  416 432 464 576  312 312 314 333 doublescan -hsync -vsync (49.7 kHz)
(**) MACH64(0): *Default mode "400x300": 24.8 MHz, 46.9 kHz, 75.1 Hz (D)
(II) MACH64(0): Modeline "400x300"x75.1   24.75  400 408 448 528  300 300 302 312 doublescan +hsync +vsync (46.9 kHz)
(**) MACH64(0): *Default mode "400x300": 25.0 MHz, 48.1 kHz, 72.2 Hz (D)
(II) MACH64(0): Modeline "400x300"x72.2   25.00  400 428 488 520  300 318 321 333 doublescan +hsync +vsync (48.1 kHz)
(**) MACH64(0): *Default mode "400x300": 20.0 MHz, 37.9 kHz, 60.3 Hz (D)
(II) MACH64(0): Modeline "400x300"x60.3   20.00  400 420 484 528  300 300 302 314 doublescan +hsync +vsync (37.9 kHz)
(**) MACH64(0): *Default mode "400x300": 18.0 MHz, 35.2 kHz, 56.3 Hz (D)
(II) MACH64(0): Modeline "400x300"x56.3   18.00  400 412 448 512  300 300 301 312 doublescan +hsync +vsync (35.2 kHz)
(**) MACH64(0): *Default mode "320x240": 15.8 MHz, 37.5 kHz, 75.0 Hz (D)
(II) MACH64(0): Modeline "320x240"x75.0   15.75  320 328 360 420  240 240 242 250 doublescan -hsync -vsync (37.5 kHz)
(**) MACH64(0): *Default mode "320x240": 15.8 MHz, 37.9 kHz, 72.8 Hz (D)
(II) MACH64(0): Modeline "320x240"x72.8   15.75  320 332 352 416  240 244 246 260 doublescan -hsync -vsync (37.9 kHz)
(**) MACH64(0): *Default mode "320x240": 12.6 MHz, 31.5 kHz, 60.1 Hz (D)
(II) MACH64(0): Modeline "320x240"x60.1   12.59  320 328 376 400  240 245 246 262 doublescan -hsync -vsync (31.5 kHz)
(**) MACH64(0): Display dimensions: (340, 270) mm
(**) MACH64(0): DPI set to (95, 96)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules/libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.7.6, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(II) Loading sub module "xaa"
(II) LoadModule: "xaa"
(II) Loading /usr/lib/xorg/modules/libxaa.so
(II) Module xaa: vendor="X.Org Foundation"
compiled for 1.7.6, module version = 1.2.1
ABI class: X.Org Video Driver, version 6.0
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"
(II) Module "i2c" already built-in
(II) MACH64(0): I2C bus "Mach64" initialized.
(--) Depth 24 pixmap format is 32 bpp
(WW) MACH64(0): DRI static buffer allocation failed -- need at least 12800 kB video memory
(II) MACH64(0): Largest offscreen areas (with overlaps):
(II) MACH64(0): 1280 x 614 rectangle at 0,1024
(II) MACH64(0): 256 x 615 rectangle at 0,1024
(II) MACH64(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
8x8 mono pattern filled rectangles
Indirect CPU to Screen color expansion
Solid Lines
Setting up tile and stipple cache:
20 128x128 slots
5 256x256 slots
(==) MACH64(0): Backing store disabled
(==) MACH64(0): Silken mouse enabled
(**) MACH64(0): DPMS enabled
(II) MACH64(0): Direct rendering disabled
(==) RandR enabled
(II) Initializing built-in extension Generic Event Extension
(II) Initializing built-in extension SHAPE
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension BIG-REQUESTS
(II) Initializing built-in extension SYNC
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-MISC
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) AIGLX: Screen 0 is not DRI2 capable
(II) AIGLX: Screen 0 is not DRI capable
(II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so
(II) GLX: Initialized DRISWRAST GL provider for screen 0
(II) XKB: reuse xkmfile /var/lib/xkb/server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm
(II) config/udev: Adding input device Power Button (/dev/input/event1)
(**) Power Button: Applying InputClass "evdev keyboard catchall"
(II) LoadModule: "evdev"
(II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
compiled for 1.7.6, module version = 2.3.2
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 7.0
(**) Power Button: always reports core events
(**) Power Button: Device: "/dev/input/event1"
(II) Power Button: Found keys
(II) Power Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "pc105"
(**) Option "xkb_layout" "us"
(**) Option "xkb_variant" "basic"
(II) XKB: reuse xkmfile /var/lib/xkb/server-FA909DFBFFB6007765A9F4B3490F5D40DB9AB26E.xkm
(II) config/udev: Adding input device Power Button (/dev/input/event0)
(**) Power Button: Applying InputClass "evdev keyboard catchall"
(**) Power Button: always reports core events
(**) Power Button: Device: "/dev/input/event0"
(II) Power Button: Found keys
(II) Power Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "pc105"
(**) Option "xkb_layout" "us"
(**) Option "xkb_variant" "basic"
(II) config/udev: Adding input device HID 0461:4d09 (/dev/input/event4)
(**) HID 0461:4d09: Applying InputClass "evdev pointer catchall"
(**) HID 0461:4d09: always reports core events
(**) HID 0461:4d09: Device: "/dev/input/event4"
(II) HID 0461:4d09: Found 9 mouse buttons
(II) HID 0461:4d09: Found scroll wheel(s)
(II) HID 0461:4d09: Found relative axes
(II) HID 0461:4d09: Found x and y relative axes
(II) HID 0461:4d09: Configuring as mouse
(**) HID 0461:4d09: YAxisMapping: buttons 4 and 5
(**) HID 0461:4d09: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "HID 0461:4d09" (type: MOUSE)
(II) HID 0461:4d09: initialized for relative axes.
(II) config/udev: Adding input device HID 0461:4d09 (/dev/input/mouse1)
(II) No input driver/identifier specified (ignoring)
(II) config/udev: Adding input device cx88 IR (pcHDTV HD5500 HDTV) (/dev/input/event5)
(**) cx88 IR (pcHDTV HD5500 HDTV): Applying InputClass "evdev keyboard catchall"
(**) cx88 IR (pcHDTV HD5500 HDTV): always reports core events
(**) cx88 IR (pcHDTV HD5500 HDTV): Device: "/dev/input/event5"
(II) cx88 IR (pcHDTV HD5500 HDTV): Found keys
(II) cx88 IR (pcHDTV HD5500 HDTV): Configuring as keyboard
(II) XINPUT: Adding extended input device "cx88 IR (pcHDTV HD5500 HDTV)" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "pc105"
(**) Option "xkb_layout" "us"
(**) Option "xkb_variant" "basic"
(II) config/udev: Adding input device cx88 IR (Hauppauge WinTV-HVR400 (/dev/input/event6)
(**) cx88 IR (Hauppauge WinTV-HVR400: Applying InputClass "evdev keyboard catchall"
(**) cx88 IR (Hauppauge WinTV-HVR400: always reports core events
(**) cx88 IR (Hauppauge WinTV-HVR400: Device: "/dev/input/event6"
(II) cx88 IR (Hauppauge WinTV-HVR400: Found keys
(II) cx88 IR (Hauppauge WinTV-HVR400: Configuring as keyboard
(II) XINPUT: Adding extended input device "cx88 IR (Hauppauge WinTV-HVR400" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "pc105"
(**) Option "xkb_layout" "us"
(**) Option "xkb_variant" "basic"
(II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event3)
(**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
(**) AT Translated Set 2 keyboard: always reports core events
(**) AT Translated Set 2 keyboard: Device: "/dev/input/event3"
(II) AT Translated Set 2 keyboard: Found keys
(II) AT Translated Set 2 keyboard: Configuring as keyboard
(II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "pc105"
(**) Option "xkb_layout" "us"
(**) Option "xkb_variant" "basic"
(II) config/udev: Adding input device Macintosh mouse button emulation (/dev/input/event2)
(**) Macintosh mouse button emulation: Applying InputClass "evdev pointer catchall"
(**) Macintosh mouse button emulation: always reports core events
(**) Macintosh mouse button emulation: Device: "/dev/input/event2"
(II) Macintosh mouse button emulation: Found 3 mouse buttons
(II) Macintosh mouse button emulation: Found relative axes
(II) Macintosh mouse button emulation: Found x and y relative axes
(II) Macintosh mouse button emulation: Configuring as mouse
(**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
(**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Macintosh mouse button emulation" (type: MOUSE)
(II) Macintosh mouse button emulation: initialized for relative axes.
(II) config/udev: Adding input device Macintosh mouse button emulation (/dev/input/mouse0)
(II) No input driver/identifier specified (ignoring)

How can I disable the 'chipset detection' during bootup and get avwizard to successfully run (or bypass avwizard)?

Dennis

Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: phenigma on March 24, 2012, 06:39:16 pm
phenigma... that should absolutely not be occurring anymore.

My bad, adding the virtualbox driver I missed the test for detected driver equaling current driver which prevented the AVWizard override from being set.  I've caught it now.  Everything is working great!  I spent last night updating my 1004 builder to current svn and I'll submit the code addition I'm using to detect the virtualbox video driver.

J.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: JaseP on March 25, 2012, 08:47:26 pm
By the way,...

Video interface is working in the core:

Del Inspiron 530
4GB RAM, 320GB HD, Intel GMA3100 series graphics (G33/G31 chipset)
UI2 + Alpha
Complete LSPCI output:
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: l3mce on March 26, 2012, 05:34:56 am
For those of you caught in the vesa loop... update pluto-boot-scripts. That will likely fix you. Sorry for the confusion... I hadn't uploaded a fix I had on my local system.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: ardirtbiker on March 28, 2012, 01:22:25 am
okay..  I was adding additional items to the video detection section of Utils.sh (added new item for ATI driver 'ati' and 'mach64')   on bootup, the system identifies my display as requiring the 'ati' driver (identified in yellow text)... but continues to flicker... unable to launch AVWizard.. non-stop I might add



If i put a valid xorg.conf file in /etc/X11 on bootup there is the yellow text stating the 'ati' driver IS installed... but still cannot either run AVWizard or the orbiter... however I may sometimes get a 'cannot configure X' screen (or something along those lines).


For now, I have to kill all the AVWizard and X -config programs and then launch startx to get into myth setup (my dvb cards are in my core)

Any suggestions on how to get my orbiter working again or get the AVWizard to launch correctly?

Dennis
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: l3mce on March 28, 2012, 05:27:40 pm
ardirtbiker: There is also a radeon r128 driver out there. I am currently looking at how xserver-xorg-video-ati figures out and applies radeon/r128/mach64 driver based on the pci info. I should have a solution soon.

*Please try this Utils.sh
Code: [Select]
#!/bin/bash

if [[ -n "$HEADER_Utils" ]]; then
    return 0
fi
HEADER_Utils=included

. /usr/pluto/bin/SQL_Ops.sh
. /usr/pluto/bin/Config_Ops.sh

DEVICETEMPLATE_OnScreen_Orbiter=62
DEVICEDATA_Use_OpenGL_effects=172
DEVICEDATA_Use_alpha_blended_UI=169
DEVICEDATA_PK_UI=104

function AddBookmark {
    return 0
    Url="$1"
    Name="$2"

    [[ ! -f /home/public/bookmarks.html ]] || return 0

    # Generate an id for this bookmark
    ID=$(echo "$Url" | sha1sum)
    ID='rdf:#$'${ID:0:6}

    # Generate the bookmark entry
    Bookmark='   <DT><A HREF="'$Url'" ADD_DATE="1126869382" LAST_MODIFIED="1126869442" ID="'$ID'">'$Name'</A>'
    Bookmark=$(echo $Bookmark | sed 's/"/\\\"/g')

    for BookmarksFile in /home/public/bookmarks.html /home/user_*/bookmarks.html ;do
        # See if the bookmark is already there
        if grep -q "ID=\"$ID\"" $BookmarksFile ;then
            continue
        fi

        # Add the bookmark string to the file
        awk '
            BEGIN { HR=0 }
            HR==0 && /<HR>/ {print "'"$Bookmark"'"; HR=1}
            {print}
        ' $BookmarksFile > $BookmarksFile.$$
        mv $BookmarksFile.$$ $BookmarksFile
    done

}

function DelBookmark {
    return 0
    Url="$1"
    Name="$2"

    [[ ! -f /home/public/bookmarks.html ]] || return 0

    # Generate an id for this bookmark
    ID=$(echo "$Url" | sha1sum)
    ID='rdf:#$'${ID:0:6}
   
    for BookmarksFile in /home/public/bookmarks.html /home/user_*/bookmarks.html ;do
        grep -v "ID=\"$ID\"" $BookmarksFile >> $BookmarksFile.$$
        mv $BookmarksFile.$$ $BookmarksFile
    done
}

TranslateSerialPort()
{
    local SearchFor="$1"
    local PCI USB

    SerialPort=
    if [[ "$SearchFor" == pci* ]]; then
        if [[ -d /sys/class/tty ]]; then
            pushd /sys/class/tty &>/dev/null
            for dev in ttyUSB*/device ttyACM*/device; do
                id=$(readlink -f "$dev" | sed -r 's,^.*(pci.*)/usb[0-9]*/[0-9./-]*/[0-9]*-([0-9.]*):[0-9.]*(/ttyUSB[0-9]*)?$,\1+\2,g')
                if [[ "$id" == "$SearchFor" ]]; then
                    SerialPort="/dev/$(dirname "$dev")"
                    break;
                fi
            done
            popd &>/dev/null
        fi
    else
        SerialPort="$SearchFor"
    fi

    builtin echo "$SerialPort"
}

TranslateSoundCard()
{
    local SoundCard="$1" AlsaCard=
    local PCI USB
    local Cards Card Dev

    if [[ -d /sys/class/sound && "$SoundCard" == pci* ]]; then
        if [[ "$SoundCard" == *+* ]]; then
            PCI="${SoundCard%+*}"
            USB="${SoundCard#*+}"
        else
            PCI="${SoundCard}"
            USB=
        fi
        pushd /sys/class/sound &>/dev/null
        Cards=$(find -name 'controlC*')
        for Card in $Cards; do
            Card="${Card#./}"
            Dev=$(readlink "$Card/device"|cut -f3 -d/)
            if [[ -n "$USB" ]]; then
                if [[ "$Dev" == *"$PCI"*usb*"$USB:"* ]]; then
                    AlsaCard="${Card#controlC}"
                    break
                fi
            else
                if [[ "$PCI" == *"$Dev" ]]; then
                    AlsaCard="${Card#controlC}"
                    break
                fi
            fi
        done
        popd &>/dev/null
    fi

    builtin echo "$AlsaCard"
}

UseAlternativeLibs()
{
    export LD_LIBRARY_PATH=/opt/libsdl/lib:/opt/libxine/lib:/opt/libsdl1.2-1.2.7+1.2.8cvs20041007/lib:/opt/linphone-1.3.5/lib
}

function ListTemplates_Category {
    local FK_DeviceCategory_Parent="$1"
    local PK_DeviceTemplate_List=""
    local PK_DeviceCategory=""
    local PK_DeviceTemplate=""

    R=$(RunSQL "SELECT PK_DeviceCategory FROM DeviceCategory WHERE FK_DeviceCategory_Parent = $FK_DeviceCategory_Parent")
    for PK_DeviceCategory in $R ;do
        PK_DeviceTemplate_List="$PK_DeviceTemplate_List $(ListTemplates_Category "$PK_DeviceCategory")"
    done

    R=$(RunSQL "SELECT PK_DeviceTemplate FROM DeviceTemplate WHERE FK_DeviceCategory=$FK_DeviceCategory_Parent")
    for PK_DeviceTemplate in $R ;do
        PK_DeviceTemplate_List="$PK_DeviceTemplate_List $PK_DeviceTemplate"
    done

    echo $PK_DeviceTemplate_List
}


FindDevice_Template()
{
    local PK_Device_Parent="${1//\'}" FK_DeviceTemplate="${2//\'}" NoRecursion="$3" IncludeParent="$4" All="$5"
    local Limit Found=0

    if [[ -z "$PK_Device_Parent" || -z "$FK_DeviceTemplate" ]]; then
        echo ""
        return 1
    fi

    if [[ -z "$All" ]]; then
        Limit="LIMIT 1"
    fi

    local i R Q
    if [[ "$PK_Device_Parent" == 0 ]]; then
        Q="
            SELECT PK_Device
            FROM Device
            WHERE FK_Device_ControlledVia IS NULL AND FK_DeviceTemplate IN ($FK_DeviceTemplate)
            $Limit
        "
    elif [[ -z "$IncludeParent" ]]; then
        Q="
            SELECT PK_Device
            FROM Device
            WHERE FK_Device_ControlledVia='$PK_Device_Parent' AND FK_DeviceTemplate IN ($FK_DeviceTemplate)
            $Limit
        "
    else
        Q="
            SELECT PK_Device
            FROM Device
            WHERE (FK_Device_ControlledVia='$PK_Device_Parent' OR PK_Device='$PK_Device_Parent') AND FK_DeviceTemplate IN ($FK_DeviceTemplate))
            $Limit
        "
    fi
    R="$(RunSQL "$Q")"

    if [[ -n "$R" ]]; then
        echo "$R"
    fi

    if [[ ( -z "$R" || -n "$All" ) && -z "$NoRecursion" ]]; then
        Q="SELECT PK_Device FROM Device WHERE FK_Device_ControlledVia='$PK_Device_Parent'"
        R="$(RunSQL "$Q")"
        for i in $R; do
            if FindDevice_Template "$i" "$FK_DeviceTemplate" "" "" "$All"; then
                if [[ -z "$All" ]]; then
                    return 0
                else
                    Found=1
                fi
            fi
        done
    else
        return 1
    fi

    [[ "$Found" -eq 1 ]]
    return $?
}

FindDevice_Category()
{
    local PK_Device_Parent="${1//\'}" FK_DeviceCategory="${2//\'}" NoRecursion="$3" IncludeParent="$4" All="$5"
    local Limit Found=0

    if [[ -z "$PK_Device_Parent" || -z "$FK_DeviceCategory" ]]; then
        echo ""
        return 1
    fi

    if [[ -z "$All" ]]; then
        Limit="LIMIT 1"
    fi

    local i R Q
    if [[ "$PK_Device_Parent" == 0 ]]; then
        Q="
            SELECT PK_Device
            FROM Device
            JOIN DeviceTemplate ON FK_DeviceTemplate=PK_DeviceTemplate
            WHERE FK_Device_ControlledVia IS NULL AND FK_DeviceCategory IN ($FK_DeviceCategory)
            $Limit
        "
    elif [[ -z "$IncludeParent" ]]; then
        Q="
            SELECT PK_Device
            FROM Device
            JOIN DeviceTemplate ON FK_DeviceTemplate=PK_DeviceTemplate
            WHERE FK_Device_ControlledVia='$PK_Device_Parent' AND FK_DeviceCategory IN ($FK_DeviceCategory)
            $Limit
        "
    else
        Q="
            SELECT PK_Device
            FROM Device
            JOIN DeviceTemplate ON FK_DeviceTemplate=PK_DeviceTemplate
            WHERE (FK_Device_ControlledVia='$PK_Device_Parent' OR PK_Device='$PK_Device_Parent') AND FK_DeviceCategory IN ($FK_DeviceCategory)
            $Limit
        "
    fi
    R="$(RunSQL "$Q")"

    if [[ -n "$R" ]]; then
        echo "$R"
    fi

    if [[ ( -z "$R" || -n "$All" ) && -z "$NoRecursion" ]]; then
        Q="SELECT PK_Device FROM Device WHERE FK_Device_ControlledVia='$PK_Device_Parent'"
        R="$(RunSQL "$Q")"
        for i in $R; do
            if FindDevice_Category "$i" "$FK_DeviceCategory" "" "" "$All"; then
                if [[ -z "$All" ]]; then
                    return 0
                else
                    Found=1
                fi
            fi
        done
    else
        return 1
    fi

    [[ "$Found" -eq 1 ]]
    return $?
}

# Get the device number for the parent of the given device
# Returns: number or empty string
GetDeviceParent()
{
    local PK_Device="$1"
    Q="
        SELECT FK_Device_ControlledVia
        FROM Device
        WHERE PK_Device='$PK_Device'
    "
    local R=$(RunSQL "$Q")
   
    if [[ "$R" == NULL ]]; then
        R=""
    fi
    echo "$R"
}

# Delete a device and make its children top level
# Does exactly the same thing as CMD_Delete_Device in General_Info_Plugin
DeleteDevice()
{
    local PK_Device="$1"
    local Q R

    # Delete embedded devices
    Q="SELECT PK_Device FROM Device where FK_Device_RouteTo=$PK_Device"
    R=$(RunSQL "$Q")
    for Device in $R; do
        DeleteDevice "$Device"
    done

    local -a Queries
    Queries=(
        "UPDATE Device SET FK_Device_ControlledVia=NULL WHERE FK_Device_ControlledVia=$PK_Device"
        "DELETE FROM Device WHERE PK_Device=$PK_Device"
        "DELETE FROM CommandGroup_Command WHERE FK_Device=$PK_Device"
        "DELETE FROM Device_Command WHERE FK_Device=$PK_Device"
        "DELETE FROM Device_CommandGroup WHERE FK_Device=$PK_Device"
        "DELETE FROM Device_DeviceData WHERE FK_Device=$PK_Device"
        "DELETE FROM Device_DeviceGroup WHERE FK_Device=$PK_Device"
        "DELETE FROM Device_Device_Related WHERE FK_Device=$PK_Device OR FK_Device_Related=$PK_Device"
        "DELETE FROM Device_EntertainArea WHERE FK_Device=$PK_Device"
        "DELETE FROM Device_HouseMode WHERE FK_Device=$PK_Device"
        "DELETE FROM Device_Orbiter WHERE FK_Device=$PK_Device"
        "DELETE FROM Device_StartupScript WHERE FK_Device=$PK_Device"
        "DELETE FROM Device_Users WHERE FK_Device=$PK_Device"
        "DELETE FROM Package_Device WHERE FK_Device=$PK_Device"
        "DELETE FROM PaidLicense WHERE FK_Device=$PK_Device"
        "DELETE FROM Device_Device_Pipe WHERE FK_Device_From=$PK_Device OR FK_Device_To=$PK_Device"
        "DELETE FROM PaidLicense WHERE FK_Device=$PK_Device"
    )

    for Q in "${Queries[@]}"; do
        RunSQL "$Q"
    done
}

XineConfSet()
{
    local Setting="$1"
    local Value="$2"
    local XineConf="${3:-/etc/pluto/xine.conf}"
   
    [[ -z "$Setting" || -z "$Value" ]] && return 1
   
    if grep -qF "$Setting" "$XineConf"; then
        sed -i "s/^.*$Setting:.*$/$Setting:$Value/" "$XineConf"
    else
        echo "$Setting:$Value" >>"$XineConf"
    fi
}

DeviceIsDisabled()
{
    local PK_Device="$1"
    local R Q

    [[ -z "$PK_Device" ]] && return 1

    Q="SELECT COUNT(*) FROM Device WHERE PK_Device='$PK_Device' AND Disabled=0"
    R=$(RunSQL "$Q")

    if [[ -n "$R" && "$R" -eq 0 ]]; then
        return 0 # Device is disabled or does not exist at all
    else
        return 1 # Device exists and is enabled
    fi
}

FindInArray()
{
    local Value="$1" Array i
    shift
    Array=("$@")
   
    for ((i = 0; i < ${#Array[*]}; i++)); do
        if [[ "${Array[$i]}" == "$Value" ]]; then
            echo "$i"
            return 0
        fi
    done
    return 1
}

FindInArray_Prefix()
{
    local Value="$1" Array i
    shift
    Array=("$@")

    for ((i = 0; i < ${#Array[*]}; i++)); do
        if [[ "${Array[$i]}" == "$Value"* ]]; then
            echo "$i"
            return 0
        fi
    done
    return 1
}

# Verify that the given string is a valid IPv4
ValidIP()
{
    local IP="$1"

    local IPn="[0-9]{1,3}"
    local IPpattern="^($IPn)\\.($IPn)\\.($IPn)\\.($IPn)$"
    local i Number

    # Bash 3.1 requires $IPpattern to be quoted, otherwise it gives a syntax error
    # Bash 3.2 requires $IPpattern to be unquoted, otherwise it fails to match the pattern
    # Ubuntu has Bash 3.2
    if [[ ! "$IP" =~ $IPpattern ]]; then
        return 1
    fi

    for ((i = 1; i <= 4; i++)); do
        Number="${BASH_REMATCH[$i]}"
        if ((Number < 0 || Number > 255)); then
            return 1
        fi
    done

    return 0
}

# Colors and bolds messages
# '\E begin escape sequence
# [XX; is the text color
# XXm' is the background color
# \033 is the an escape
# [1m bold     [0m unbold
# "" around text   '' around color
# COLOR         FOREGROUND      BACKGROUND
# black         30              40
# red           31              41
# green         32              42
# yellow        33              43
# blue          34              44
# magenta       35              45
# cyan          36              46
# white         37              47

StatusMessage () {
    echo -e '\E[33;40m'"\033[1m  $* \033[0m"
}
ErrorMessage () {
    echo -e '\E[33;41m'"\033[1m  $* \033[0m"
}
NotifyMessage () {
    echo -e '\E[32;40m'"\033[1m  $* \033[0m"
}

confirmRoot () {
    testroot="`whoami`"
    if [ "$testroot" != "root" ]; then
        ErrorMessage "Need to be root to run. Exiting"
        exit 1
    fi
}

StartService() {
ServiceDescription="$1"
ServiceCmd="$2"
ServiceBkg="$3"
    if [[ -x $(echo $ServiceCmd | cut -d ' ' -f1) ]] ;then
        if [ -x /bin/plymouth ]; then
            /bin/plymouth update --status="$ServiceDescription ... "
        fi
        echo -n "$ServiceDescription ... "
            if [[ "$ServiceBkg" == "&" ]] ;then
                $ServiceCmd 1>/dev/null 2>/dev/null &
            else
                $ServiceCmd 1>/dev/null 2>/dev/null
            fi
            err=$?
            if [[ "$err" == "0" ]] ;then
                echo "ok"
            else
                echo "fail"
            fi
    fi
        return $err
}

GetVideoDriver () {
        vga_pci=$(lspci -v | grep -i 'VGA')
        prop_driver="vesa"
        chip_man=$(echo "$vga_pci" | grep -Eo '(ATI|VIA|nVidia|Intel)')
        case $chip_man in
                nVidia)
            if ping -c 1 google.com; then
                prop_driver="nvidia" 
            else
                prop_driver="nouveau"
            fi ;;

                ATI)
                        prop_driver="fglrx"
                        if echo $vga_pci | grep -Ei '(r5|r6|r7)'; then
                                prop_driver="radeonhd"; fi
                        if echo "$vga_pci" | grep -E '((9|X|ES)(1|2?)([0-9])(5|0)0|Xpress)'; then
                                prop_driver="radeon"; fi
                        if echo $vga_pci | grep -i "Rage" | grep "128"; then
                                prop_driver="r128"; fi
                        if echo $vga_pci | grep -i "Rage"; then
                                prop_driver="mach64"; fi ;;

                Intel)
                        prop_driver="intel"
                        if echo $vga_pci | grep "i740"; then
                                prop_driver="i740"; fi
                        if echo $vga_pci | grep "i128"; then
                                prop_driver="i128"; fi ;;

                VIA)
                        prop_driver="openchrome" ;
                        if echo $vga_pci | grep -i "Savage"; then
                                prop_driver="savage"; fi
#                       if echo $vga_pci | grep -i "s3"; then
#                               prop_driver="via"; fi
                        if echo $vga_pci | grep -i "virge"; then
                                prop_driver="virge"; fi ;;
        *)
            prop_driver="vesa"
        esac

}

InstallVideoDriver () {
    GetVideoDriver
    case "$prop_driver" in
            nvidia)
            if ! PackageIsInstalled nvidia-glx && ! PackageIsInstalled nvidia-glx-new && ! PackageIsInstalled nvidia-glx-71 && ! PackageIsInstalled nvidia-glx-96 && ! PackageIsInstalled nvidia-glx-173 && ! PackageIsInstalled nvidia-glx-180 && ! PackageIsInstalled nvidia-glx-190 && ! PackageIsInstalled nvidia-glx-195 && ! PackageIsInstalled nvidia-glx-260 && ! PackageIsInstalled nvidia-glx-185 && ! PackageIsInstalled nvidia-current && ping -c 1 google.com; then
                apt-get -yf install pluto-nvidia-video-drivers
                VerifyExitCode "Install Pluto nVidia Driver"
                nv_pid=$(pidof nvidia-install.sh)
                    if [[ -n $nv_pid ]] ; then
                        StatusMessage "Installing nVidia driver this may take a few minutes"
                        installCorrectNvidiaDriver
                    else StartService "Installing nVidia driver this may take a few minutes" ". /usr/pluto/bin/nvidia-install.sh"
                        installCorrectNvidiaDriver
                    fi
            else
                apt-get -yf install xserver-xorg-video-nouveau
                VerifyExitCode "Install nouveau Driver"
                prop_driver="nouveau"
            fi ;;
        radeon)
            if ! PackageIsInstalled xserver-xorg-video-radeon; then
                apt-get -yf install xserver-xorg-video-radeon
                VerifyExitCode "Install radeon Driver"
            fi ;;
        mach64)
            if ! PackageIsInstalled xserver-xorg-video-mach64; then
                apt-get -yf install xserver-xorg-video-mach64
                VerifyExitCode "Install mach64 Driver"
            fi ;;
        r128)
            if ! PackageIsInstalled xserver-xorg-video-mach64; then
                apt-get -yf install xserver-xorg-video-r128
                VerifyExitCode "Install r128 Driver"
            fi ;;
        fglrx)
            if ! PackageIsInstalled fglrx && ping -c 1 google.com; then
                apt-get -yf install fglrx
                VerifyExitCode "Install fglrx Driver"
            else
                apt-get -yf install xserver-xorg-video-radeon
                VerifyExitCode "Install radeon Driver"
                prop_driver="radeon"
            fi ;;
        radeonhd)
            if ! PackageIsInstalled xserver-xorg-video-radeonhd; then
                apt-get -yf install xserver-xorg-video-radeonhd
                VerifyExitCode "Install radeonhd Driver"
            fi ;;
        intel)
            if ! PackageIsInstalled xserver-xorg-video-intel; then
                apt-get -yf install xserver-xorg-video-intel
                VerifyExitCode "Install Intel Driver"
            fi ;;
        i128)
            if ! PackageIsInstalled xserver-xorg-video-i128; then
                apt-get -yf install xserver-xorg-video-i128
                VerifyExitCode "Install i128 Driver"
            fi ;;
        i740)
            if ! PackageIsInstalled xserver-xorg-video-i740; then
                apt-get -yf install xserver-xorg-video-i740
                VerifyExitCode "Install i740 Driver"
            fi ;;
        openchrome)
            if ! PackageIsInstalled xserver-xorg-video-openchrome; then
                apt-get -yf install xserver-xorg-video-openchrome
                VerifyExitCode "Install opencrhome Driver"
            fi ;;
        savage)
            if ! PackageIsInstalled xserver-xorg-video-savage && ping -c 1 google.com; then
                apt-get -yf install xserver-xorg-video-savage
                VerifyExitCode "Install VIA Savage Driver"
            else prop_driver="openchrome"
            fi ;;
        via)
            if ! PackageIsInstalled xserver-xorg-video-s3; then
                apt-get -yf install xserver-xorg-video-s3
                VerifyExitCode "Install VIA S3 Driver"
            fi ;;
        virge)
            if ! PackageIsInstalled xserver-xorg-video-s3virge && ping -c 1 google.com; then
                apt-get -yf install xserver-xorg-video-s3virge
                VerifyExitCode "Install VIA S3 Virge Driver"
            else prop_driver="openchrome"
            fi ;;
                esac
    if [[ "$chip_man" == "Intel" ]] && ping -c 1 google.com; then
        if ! PackageIsInstalled "libva-driver-i965" && ping -c 1 google.com; then
            apt-get -yf install libva-driver-i965
            VerifyExitCode "Install Intel Graphics Accelerator"
        fi
    fi
VideoDriver="$prop_driver"
}

CheckVideoDriver () {
    GetVideoDriver
    if [[ -f /etc/X11/xorg.conf ]]; then
        # TODO figure out a better way to isolate the video driver in the xorg.conf list of "Driver" options
            cur_driver=$(grep "Driver" /etc/X11/xorg.conf | grep -Eo '(nvidia|radeon|radeonhd|fglrx|savage|openchrome|via|virge|intel|i740|i128|vesa)')
                card_detail=$(lspci | grep 'VGA' | cut -d':' -f3)
        # Check to see that the appropriate driver is installed by type
                if [[ "$prop_driver" != "$cur_driver" ]]; then
            driver_match="no"
        else
            driver_match="yes"
        fi
        # If current driver is nvidia, check that it is the correct one
        if [[ "$driver_match" == "yes" ]] && [[ "$cur_driver" == "nvidia" ]]; then
            StartService "Checking nVidia driver" ". /usr/pluto/bin/nvidia-install.sh"
            current_nvidia=$(getInstalledNvidiaDriver)
            preferred_nvidia=$(getPreferredNvidiaDriver)
            if [[ "$current_nvidia" != "$preferred_nvidia" ]]; then
                driver_match="no"
            fi
        fi
        # remove fglrx or nVidia drivers if they are installed, but do not match current requirements
                if [[ "$driver_match" == "no" ]]; then
                        ErrorMessage "Video chipset change detected !!!"
            if [[ "$cur_driver" == "fglrx" ]]; then
                echo ""
                echo ""
                echo ""
                ErrorMessage "Purging fglrx driver due to multiple conflicts"
                apt-get -y remove --purge xorg-driver-fglrx fglrx* --force-yes
                apt-get -y install --reinstall libgl1-mesa-glx libgl1-mesa-dri fglrx-modaliases --force-yes
                dpkg-reconfigure xserver-xorg
                apt-get -y install --reinstall xserver-xorg-core --force-yes
                rm /etc/X11/xorg.conf
                reboot
                exit 0
            elif [[ $cur_driver == "nvidia" ]]; then
                StatusMessage "Removing old nVidia driver"
                apt-get -yf remove $current_driver --force-yes
            fi
            # If there is an xorg, but the driver does not match best selection, install driver and run AVWizard
                        StatusMessage "Installing video driver '$prop_driver' for $card_detail"
            InstallVideoDriver
                        ConfSet "AVWizardOverride" "1"
                else
            StatusMessage "Correct driver '$prop_driver' already loaded"
                fi
        else
        # If there is no xorg.conf, install driver and run AVWizard
        StatusMessage "Installing video driver '$prop_driver' for $card_detail"
        InstallVideoDriver
        ConfSet "AVWizardOverride" "1"
        fi
}

ReloadDevicesOnThisMachine()
{
    for Dev in $(cat /usr/pluto/locks/pluto_spawned_local_devices.txt); do
        /usr/pluto/bin/MessageSend "$DCERouter" 0 "$Dev" 7 1 163 "Utils.sh ReloadDevicesOnThisMachine"
    done
}

OpenGLeffects()
{
    local Q

    Q="
        SELECT IK_DeviceData
        FROM Device
        LEFT JOIN Device AS Parent ON Parent.PK_Device=Device.FK_Device_ControlledVia
        JOIN Device_DeviceData ON Device.PK_Device=FK_Device
        WHERE
            Device.FK_DeviceTemplate='$DEVICETEMPLATE_OnScreen_Orbiter'
            AND (
                Device.FK_Device_ControlledVia='$PK_Device'
                OR Parent.FK_Device_ControlledVia='$PK_Device'
            )
        AND FK_DeviceData='$DEVICEDATA_Use_OpenGL_effects'
    "
    RunSQL "$Q"
}

AlphaBlendingEnabled()
{
    local Q

    Q="
        SELECT IK_DeviceData
        FROM Device
        LEFT JOIN Device AS Parent ON Parent.PK_Device=Device.FK_Device_ControlledVia
        JOIN Device_DeviceData ON Device.PK_Device=FK_Device
        WHERE
            Device.FK_DeviceTemplate='$DEVICETEMPLATE_OnScreen_Orbiter'
            AND (
                Device.FK_Device_ControlledVia='$PK_Device'
                OR Parent.FK_Device_ControlledVia='$PK_Device'
            )
        AND FK_DeviceData='$DEVICEDATA_Use_alpha_blended_UI'
    "
    RunSQL "$Q"
}

GetDeviceData()
{
    local Q
    local Device="$1" DeviceData="$2"

    Q="
        SELECT IK_DeviceData
        FROM Device_DeviceData
        WHERE FK_Device='$Device' AND FK_DeviceData='$DeviceData'
    "
    Field 1 "$(RunSQL "$Q")"
}

SetDeviceData()
{
    local Q
    local Device="$1" DeviceData="$2" Value="$3"

    Q="
        UPDATE Device_DeviceData
        SET IK_DeviceData='$Value'
        WHERE FK_Device=$Device AND FK_DeviceData=$DeviceData
    "
    RunSQL "$Q"
}

UI_SetOptions()
{
    local OrbiterDev="$1"
    local OpenGLeffects="$2"
    local AlphaBlending="$3"
    local UI_Version="$4"

    # disable OpenGL effects
    Q="
        REPLACE INTO Device_DeviceData(FK_Device, FK_DeviceData, IK_DeviceData)
        VALUES('$OrbiterDev', '$DEVICEDATA_Use_OpenGL_effects', '$OpenGLeffects')
    "
    RunSQL "$Q"
    # disable alpha blending
    Q="
        REPLACE INTO Device_DeviceData(FK_Device, FK_DeviceData, IK_DeviceData)
        VALUES('$OrbiterDev', '$DEVICEDATA_Use_alpha_blended_UI', '$AlphaBlending')
    "
    RunSQL "$Q"
    # select UI
    Q="
        REPLACE INTO Device_DeviceData(FK_Device, FK_DeviceData, IK_DeviceData)
        VALUES('$OrbiterDev', '$DEVICEDATA_PK_UI', '$UI_Version')
    "
    RunSQL "$Q"
}

function GeneratePassword() {
    #TODO: Replace with this --->  </dev/urandom tr -dc A-Za-z0-9_ | head -c8
        local -a alpha1=(Q W E R T Y U I O P A S D F G H J K L Z X C V B N M)
        local -a alpha2=(q w e r t y u i o p a s d f g h j k l z x c v b n m)
        local -a alpha3=(1 2 3 4 5 6 7 8 9 0)

        local pass=""
        pass=$pass"${alpha1[$(($RANDOM%26))]}${alpha1[$(($RANDOM%26))]}${alpha1[$(($RANDOM%26))]}"
        pass=$pass"${alpha2[$(($RANDOM%26))]}${alpha2[$(($RANDOM%26))]}${alpha2[$(($RANDOM%26))]}"
        pass=$pass"${alpha3[$(($RANDOM%10))]}${alpha3[$(($RANDOM%10))]}"

        local fromwhere=$(( $RANDOM % 3 + 1 ))
        [[ $fromwhere == 1 ]] && pass=$pass"${alpha1[$(($RANDOM%26))]}"
        [[ $fromwhere == 2 ]] && pass=$pass"${alpha2[$(($RANDOM%26))]}"
        [[ $fromwhere == 3 ]] && pass=$pass"${alpha3[$(($RANDOM%10))]}"


        for i in `seq 1 100` ;do
                local split=$(( $RANDOM % ${#pass} + 1 ))
                pass1=${pass:$split}
                pass2=${pass:0:$split}
                pass="${pass1}${pass2}"
        done

        echo $pass
}

function GeneratePasswordOf6Digits()
{
    local pass
    for ((i = 0; i < 6; i++)); do
        pass="${pass}$((RANDOM % 10))"
    done
    echo "$pass"
}

Log()
{
    local File="$1"; shift
    local Msg="$*"

    echo "LOG: $Msg"
    echo "$Msg" >>"$File"
}


function BlacklistConfFiles()
{
    local file=$1

    if [[ -e /etc/confblacklist ]] ;then
        while read line; do
            if [[ "$line" == "$file" ]] ;then
                return 0
            fi
        done < /etc/confblacklist
    fi

    return 1               
}

function VDRInstalled() {
    # Return true if VDR is installed
    DEVICETEMPLATE_VDR_Plugin="1704"
    Q="SELECT PK_Device FROM Device Where FK_DeviceTemplate = $DEVICETEMPLATE_VDR_Plugin"
    VDRDevice=$(RunSQL "$Q")                                         
    if [ "$VDRDevice" == "" ] ; then                                 
        RETURNVALUE=1                                             
    else                                                             
        RETURNVALUE=0                                             
    fi                                                               
    return $RETURNVALUE
}
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: ardirtbiker on March 28, 2012, 06:23:25 pm
have grabbed your file... will test it on next reboot sometime later today.

Thanks

Dennis
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: m3freak on March 28, 2012, 07:41:51 pm
I want to help test.  I already have a working MD, plus one new MD waiting to be deployed (bedroom wiring not yet ready).

If I run Diskless_CreateTBZ.sh again, I have to delete the working MD in order to test it, correct?
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: ardirtbiker on March 28, 2012, 08:53:34 pm
actually.. if you rebuild the TBZ image, then for a fresh MD from that.. you can rebuild the image from the web admin page (media directors).  then on boot of the MD, it will re-build everything based on settings already in the database for that MD. (at least that is what I have observed)

Dennis
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: l3mce on March 28, 2012, 09:18:51 pm
I want to help test.  I already have a working MD, plus one new MD waiting to be deployed (bedroom wiring not yet ready).

If I run Diskless_CreateTBZ.sh again, I have to delete the working MD in order to test it, correct?

Well... you will have to update pluto-boot-scripts and pluto-avwizard, first of all. Then you can run Diskless_CreateTBZ.sh, You can do this simply by:
Code: [Select]
sudo apt-get update
sudo apt-get install pluto-avwizard pluto-boot-scripts
sudo /usr/pluto/bin/Diskless_CreateTBZ.sh

Your old MD is fine as it is. That data is already configured. It MAY take you through AVWizard the next time it reboots. Your new MD will use the new code. You are not likely to notice any difference really unless this MD is an ATI, Intel, or VIA video chipset. However should it break something that currently works, that is equally useful.

So please list what the hardware is, and how it reacts. Thanks.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: m3freak on March 29, 2012, 03:48:26 am
Well... you will have to update pluto-boot-scripts and pluto-avwizard, first of all.

Already ran an update a couple of days ago - I'm set.

Then you can run Diskless_CreateTBZ.sh

Did that earlier today.

Your old MD is fine as it is. That data is already configured. It MAY take you through AVWizard the next time it reboots.

Ok.

Your new MD will use the new code. You are not likely to notice any difference really unless this MD is an ATI, Intel, or VIA video chipset. However should it break something that currently works, that is equally useful.

So please list what the hardware is, and how it reacts. Thanks.

Understood - will do.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: ardirtbiker on March 29, 2012, 02:36:10 pm
l3mce,
grabbed your file and substituded it for existing Utils.sh    System detected and set up correct driver, however I had something else wrong as the avwizard failed to run even if forced.

I downloaded the lasted (recommended) dvd image and re-installed... then substituted your Utils.sh  ... AVWizard ran correctly (however it runs twice back-to-back for some reason), then the system finished installing.

Thanks

Dennis
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: l3mce on March 29, 2012, 05:25:29 pm
Yes... the back to back avwizard thing is driving me ape. I have got to figure out why that is happening. Thank you for testing.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: JaseP on March 29, 2012, 07:26:42 pm
Is this back to back thing the same thing as the setup wizard restarting while creating and renaming rooms???

I've noticed the setup does that. Annoying, but not a show stopper. It almost seems like processes are timing out, and kicking it back to the beginning.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: ardirtbiker on March 29, 2012, 07:38:36 pm
JaseP,
 No.. this is on bootup when the system has detected your video card and runs the AVWizard (video port/resolution/sound) before the setup wizard even runs (Sarah).

Dennis
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: m3freak on April 15, 2012, 06:24:44 pm
So please list what the hardware is, and how it reacts. Thanks.

I deleted my running MD - it was acting weird.   Plus, it gave me the opportunity to properly test the new video card detection.

My Jetway ran through the setup and although the video part worked (just as before), the HDMI audio wasn't setup correctly (just as before).  I'll have  to use my "hdmi how to" get the audio working for my particular MD.

My MD is off at the moment, so I can't give the lspci output right now.  I'll post again later today with the info you requested.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: l3mce on April 15, 2012, 08:16:16 pm
Hold off for a min.

I am changing a LOT of things.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: m3freak on April 15, 2012, 11:03:52 pm
Hold off for a min.

I am changing a LOT of things.

I already got the audio working manually.  But, I can delete the MD and go through the entire process again, no problem.  Just let me know when I can pull down updates on the core and restart the MD build.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: Armor Gnome on August 07, 2012, 09:07:18 am
Wanted to add a couple of working cards:

XFX GeForce 7600GT PCIe x16 (http://www.tomshardware.com/reviews/summer-2006-geforce-7-graphics-gear,1283-4.html)
Works with everything I have thrown at it UI2, alpha blending no problem
Works now in 8.10 and 10.04 out of the box.
256MB DDR3, SLI available if you're that brave
PCIe slot
Was extremely cheap 4 years ago so probably available as wholesale lots now...
Able to support twin x screens with small tweeks to xorg.conf.  Used as a media director in the living room or the bedroom.
  - Display is mirrored to both DVI outputs so one DVI out to bedroom 23" monitor, one DVI out to DVI-to-HDMI cable connected to 60" Sharp Plasma
  - Doing 1080p to both displays though the monitor DVI port is connected to DVI-to-VGA adapter to make it through my VGA KVM switch.


Nvidia GeForce 6600 AGP x8
1 VGA, 1 DVI (I think there was an S-video)
AGP slot, 256MB
Worked with Medium settings in 1004
Installed on loan from roommate to test a troublesome Media Director = Didn't get to play much
Failed to setup X on first MD boot.  I ssh'ed in and poked my nose around without altering anything.  Did a standard reboot and it booted back up to av wizard.
Large card for a MD and required a molex power connector.


Still to test
An older 128MB Radeon AGP
The always lovely Intel 82845G (onboard)
Homemade AGP riser for htpc cases or crazy case mods I like to mess with
USB video - I am getting one of these with hopes of adding new options for MDs, will stick it in a laptop if it fails horribly

Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: Armor Gnome on August 09, 2012, 02:42:00 pm
ATI Radeon 9200 SE (http://images.canadianlisted.com/nlarge/ati-radeon-9200se-128mb-ddr-8x-agp-tv-out_5115563.jpg)
128MB, AGP card, fanless model and fairly low profile
Working in 1004
First attempt (just to beat it up a little) 1080p with UI2 openGL alpha blending
Booted, Made it to onscreen orbiter with a little chop.  crashes when trying to open screens - though flicker images continue to move
ssh to force reboot to avwizard with
Quote
/usr/pluto/bin/RebootWithAVWizard.sh
Redid AV wizard with VGA 720 @ 60Htz - UI2 medium
working smoothly

Driver info - for L3mce if he wants it
Quote
lspci | grep VGA
# 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV280 [Radeon 9200 SE] (rev 01)
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: Armor Gnome on August 13, 2012, 05:33:04 am
Another successful card.  This was onboard equipment for a couple year old eMachine. 128MB dedicated video memory.

Quote
00:0d.0 VGA compatible controller: nVidia Corporation C61 [GeForce 6150SE nForce 430] (rev a2)

Running VGA 1920 X 1080 60Hz, UI2 (medium) with slight chop currently.  720 I am sure will produce much smoother operation and I will post results if I still have problems smoothing it out.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: l3mce on August 14, 2012, 01:50:19 am
I just wanted to thank you for your continued enthusiasm and reporting. It is very helpful for me.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: Armor Gnome on August 14, 2012, 02:21:57 am
No need at all to thank me, I am just a grateful user.  I have been using LMCE in some form or another for 3 years now and I enjoy doing my part to make it even better.  With enough effort I will eventually help write code but until that time I do what I know, which is piecing things together until they POST, then dumping the results on your lap.  :o

From the Forum Home Page:
Quote

89580 Posts in 12106 Topics by 18821 Members. Latest Member:

Imagine if 18,821 people gave hardware and setup feedback from their unique systems!  For me to find unsupported junk I would have to dig out a IIgs or C128 cassette drive.
Title: Re: VIDEO CARDS: ATI, Intel, VIA... whatever you got...
Post by: Armor Gnome on August 14, 2012, 06:39:21 am
Disappointing test tonight.  I had pretty high hopes for this card and wanted to test multiple output modes.  Supported yes but not good in any way.  I will keep it up for a few days and perhaps see if I can't adjust it and edit this post if I get better results.  Here you go L3mce:

nVidia GeForce 5200 AGP 128MB
VGA, DVI & S-Video outputs
Fanless, PCI powered, full PCI card height

lspci | grep VGA
Quote
01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200] (rev a1)

lspci -nnk | grep VGA -A2
Quote
01:00.0 VGA compatible controller [0300]: nVidia Corporation NV34 [GeForce FX 5200] [10de:0322] (rev a1)
        Kernel driver in use: nouveau
        Kernel modules: nvidiafb, nouveau

/etc/X11/xorg.conf (portion)
Quote
Section "Device"
       
Identifier   "Card0"
   Driver      "nouveau"
   VendorName   "Unknown Vendor Name"
   BoardName   "Unknown Board Name"
   Option      "LinearAlloc"      "16384"
   #BusID      "PCI:0:2:0"
#   Option      "NoDDC"            "true"
   Option "XvmcUsesTextures" "true"
   Option "renderAccel" "true"
   Option "NoDDCValue"
   Option "UseEDID" "true"
   Option "ExactModeTimingsDVI" "true"
   Option "NoLogo" "true"
   Option "NoBandWidthTest" "true"
   Option "ModeValidation" "NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes, NoEdidModes"
   Option "DynamicTwinView" "false"
   Option "UseEvents" "true"
   Option "AllowGLXWithComposite" "true"
   Option "AddARGBGLXVisuals" "true"
   Option      "ConnectedMonitor" "CRT"
EndSection

Section "Screen"
   Identifier   "Screen0"
   Device      "Card0"
   Monitor      "Monitor0"
   DefaultDepth   24
   SubSection "Display"
      Modes      "1280x720"
      Virtual      1280 720
   EndSubSection
   Option "XvmcUsesTextures" "true"
   Option "renderAccel" "true"
   Option "NoDDCValue"
   Option "UseEDID" "true"
   Option "ExactModeTimingsDVI" "true"
   Option "NoLogo" "true"
   Option "NoBandWidthTest" "true"
   Option "ModeValidation" "NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes, NoEdidModes"
   Option "DynamicTwinView" "false"
   Option "UseEvents" "true"
   Option "AllowGLXWithComposite" "true"
   Option "AddARGBGLXVisuals" "true"
   Option   "TVStandard"   "720p"
EndSection