Take a look at the sgfxi scripts I mentioned earlier in thread. They've worked flawlessly for me. Everything I needed was downloaded and installed in one shot. After installation, future driver updates are handled by a single command.

have the driver catalyst 15.9 installed on the machine .. Boinc does not recognize it .. talk about frustrating :(

---

have the driver catalyst 15.9 installed on the machine .. Boinc does not recognize it .. talk about frustrating :(

You'll need a new BOINC version with newer AMD recognition code. I've not too long ago sent in code with a lot of new AMD GPUs being recognized, so either you can build a new BOINC from code using branch 7.6, or look for new versions for your distro from people who build new versions (PPAs, package maintainers).

It'll have to be a version after 7.6.12

---

Thanks Fawkesguy and Ageless

As I continue to work my way thru this issue ...

---

Thanks Fawkesguy and Ageless

As I continue to work my way thru this issue ...

With my AMD cards I've always been able to fix that issue by placing a link to the opencl file in usr/lib. I've already posted this a couple of times but can't find it, so, here it is again.
If you don't have GKSU and Nautilus installed, install them;
sudo apt-get install gksu
sudo apt-get install nautilus

In the terminal run gksu nautilus, that will open a file browser as root.
Look in /usr/lib and see if you have a file named libOpenCL.so. You probably don't or it is named libOpenCL.so.1. Go to usr/lib/fglrx and make a link to libOpenCL.so.1, then move the link to usr/lib. Once the link is in usr/lib rename the link libOpenCL.so. If that doesn't work, make another link and name that one libOpenCL.so.1. With those links in usr/lib it should work.

Just another lie from M$. They said that Win10 Insider installations will contnue to work after Win10 release.
Today my Win10x64 Insider installation refused to boot with message about winloader.exe being expired...

One more obvious reason to trust M$ and believe Win10 will not be blocked at Windows with annual fee release...

Had you updated to the release build v10.0.1024 or were you still on something older? Prerelease versions have always expired & the dates are normally posted. Here are some of the dates for several of the Windows 10 builds:
http://microsoft-news.com/microsoft-details-expiration-dates-for-windows-10-technical-preview/

I tried update before booting into Vista. Then, booting today back I got that message. Cause it appears immediately after Win10 boot selection no way to update it into anything anymore.

You could try setting the clock back to October 1st. Perhaps that would let it boot. Then you could updates the date & do an update maybe.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Just another lie from M$. They said that Win10 Insider installations will contnue to work after Win10 release.
Today my Win10x64 Insider installation refused to boot with message about winloader.exe being expired...

One more obvious reason to trust M$ and believe Win10 will not be blocked at Windows with annual fee release...

Had you updated to the release build v10.0.1024 or were you still on something older? Prerelease versions have always expired & the dates are normally posted. Here are some of the dates for several of the Windows 10 builds:
http://microsoft-news.com/microsoft-details-expiration-dates-for-windows-10-technical-preview/

I tried update before booting into Vista. Then, booting today back I got that message. Cause it appears immediately after Win10 boot selection no way to update it into anything anymore.

You could try setting the clock back to October 1st. Perhaps that would let it boot. Then you could updates the date & do an update maybe.

In other words cheat the liar :)
Well, I made DVD with latest Insider build yesterday - will try if direct recommended way of booting from such media will help...

Oh.... now it's another message. It says that "device is not connected". Win10 was on SDD and there were no issues with it prior launching fresh Win10 DVD boot....

EDIT: Power cycle and old message about expiration of winload returned. One another boot and Win10 "Repairing disk errors"... What it did with SDD on prev launch that errors appeared?...

EDIT2: great... SDD disappeared again after "repairing" Win10 DVD boot. Another power cycle and booting directly to Vista. It sees SSD as 2 partitions 118.8 RAW and 450MB "EISA configuration".
Before fiddling with Win10 it was single NTFS partition.

So, Windows 10 completely erased partition (and I really hope if it did not damage SDD on hardware level :/)

So, net loss so far: ~2 rarely accessed games, BOINC x64 data folder (can't find it on other partitions so probably it was there and lost) and Win10 x64 installation itself. Well, "definitely nothing to worry about M$ ways".

R-Studio accesses SDD OK, maybe it could salvage something...

(thanks god I didn't trust SDD stability enough to put anything vital there)

R-studio salvaged almost all (if not all) files from erased by Win10 partition.
So, SDD device works OK by its own. The more weird Win10 DVD's behavior then. Why it deleted partition?... It seems smth happened after Win10 DVD boot. Cause power reset (just soft reset was not enough) was needed to restore SDD detection on POST .
After creation 64GB partition on that SDD and copying all files back I will try to repeat Win10 installation (now w/o repair option)...

Any one else tried any Win10 edition with OCZ Vertex4 SDD ?

All this ended with fresh install of Win10x64 Pro Insider Preview build 10565.
Had to reinstall BOINC and other apps.

Good side - embedded AMD driver works OK so far with HD6950.
On prev Win10 installation this card experienced driver restarts even on non-VLAR MB7 tasks. 43% done and no driver restarts or big lags so far.

Driver: 15.200.1055.0
As reported by OpenCL:

Driver version: 1800.8 (VM)
Version: OpenCL 1.2 AMD-APP (1800.8)

Will do some formal benchmarking later.

The news you knew was coming, on the down-play:
Microsoft doesn't see Windows 10's mandatory data collection as a privacy risk.

In the run-up to the launch of Windows 10 earlier this year, users noticed that Microsoft's operating system would be collecting more data on them by default than it had in the past, including information about their location and what they're typing, and sending it off to Microsoft.

Understandably, some folks were concerned about the privacy implications of such a move, especially given disclosures around government surveillance, and the fact that Microsoft previously hadn't built this kind of data collection into its operating system. Those concerns weren't helped by Microsoft, which was slow to clarify exactly what it takes from users and how to disable much of that collection. It's possible for users to opt out of things like the contact and calendar tracking through Microsoft that Cortana uses to provide its personal assistant services, but people who use Windows 10's express settings will toggle them on immediately.

Windows 10 also currently requires that all users hand over some information about how their devices are being used -- what Microsoft calls basic telemetry. That information relates to things like when and how Windows 10 crashes, and Microsoft Corporate Vice President Joe Belfiore said in an interview that the company needs that information to improve the experience of using its operating system. "And in the case of knowing that our system that we've created is crashing, or is having serious performance problems, we view that as so helpful to the ecosystem, and so not an issue of personal privacy, that today, we collect that data so that we make that experience better for everyone," he said.

In Belfiore's view, Microsoft's current setup properly addresses users' privacy concerns, since it lets them opt out of the collection of personal information. For those tracking features that users can't opt out of, he said the company doesn't consider them to be a privacy issue.
"And in the cases where we've not provided options, we feel that those things have to do with the health of the system, and are not personal information or are not related to privacy," he said.

Belfiore emphasized that Microsoft is still working on Windows 10 and adapting its policies to meet users' needs. The company has already begun back-tracking on its hardline stance toward telemetry data when it comes to enterprise users.
Windows and Devices Group head Terry Myerson said in a recent blog post that the company will allow Windows 10 Enterprise users to disable all data collection including telemetry data, though the company doesn't recommend users take that route.

"We're going to continue to listen to what the broad public says about these decisions, and ultimately our goal is to balance the right thing happening for the most people -- really, for everyone -- with complexity that comes with putting in a whole lot of control," Belfiore said.
He won't be around for a while to oversee that. Belfiore announced this week that he's taking a year-long sabbatical from the company (which he has worked at for more than 25 years), and spending more time with his family. In his absence, other members of his leadership team will work closely with Myerson.

---

And SETI data crunching perspective of new Win10 build in comparison with older Vista one:

GPU HD6950, CPU Intel Quad Core2, fully loaded.

Vista x86, OpenCL driver 1348.5

WU : Clean_01LC.wu
AP7_win_x86_SSE2_OpenCL_ATI_r2742.exe :
Elapsed 20.077 secs
CPU 2.434 secs

WU : Clean_20LC.wu
AP7_win_x86_SSE2_OpenCL_ATI_r2742.exe :
Elapsed 298.865 secs
CPU 25.163 secs

WU : short_ap_21oc08ab_B2_P0_00081_20081130_08605_v5.wu
AP7_win_x86_SSE2_OpenCL_ATI_r2742.exe :
Elapsed 22.604 secs
CPU 6.006 secs

WU : sigind_v5.wu
AP7_win_x86_SSE2_OpenCL_ATI_r2742.exe :
Elapsed 40.513 secs
CPU 6.817 secs

WU : single_pulses.wu
AP7_win_x86_SSE2_OpenCL_ATI_r2742.exe :
Elapsed 22.308 secs
CPU 7.628 secs

Windows 10 x64 Pro build 10564, default video driver (OpenCL driver 1800.7):

WU : Clean_01LC.wu
AP7_win_x86_SSE2_OpenCL_ATI_r2742.exe :
Elapsed 22.736 secs
CPU 3.000 secs

WU : Clean_20LC.wu
AP7_win_x86_SSE2_OpenCL_ATI_r2742.exe :
Elapsed 357.639 secs
CPU 39.578 secs

WU : short_ap_21oc08ab_B2_P0_00081_20081130_08605_v5.wu
AP7_win_x86_SSE2_OpenCL_ATI_r2742.exe :
Elapsed 24.914 secs
CPU 7.484 secs

WU : sigind_v5.wu
AP7_win_x86_SSE2_OpenCL_ATI_r2742.exe :
Elapsed 45.766 secs
CPU 9.328 secs

WU : single_pulses.wu
AP7_win_x86_SSE2_OpenCL_ATI_r2742.exe :
Elapsed 25.491 secs
CPU 8.813 secs

Hm... I would say it crunching slower, GPU-wide.

And same for MB:

Vista x86:
WU : PG0009_v7.wu
MB7_win_x86_SSE2_OpenCL_ATi_HD5_r2929.exe :
Elapsed 132.148 secs
CPU 30.607 secs

WU : PG0395_v7.wu
MB7_win_x86_SSE2_OpenCL_ATi_HD5_r2929.exe :
Elapsed 74.677 secs
CPU 26.629 secs

WU : PG0444_v7.wu
MB7_win_x86_SSE2_OpenCL_ATi_HD5_r2929.exe :
Elapsed 71.308 secs
CPU 27.035 secs

WU : PG1327_v7.wu
MB7_win_x86_SSE2_OpenCL_ATi_HD5_r2929.exe :
Elapsed 84.599 secs
CPU 20.577 secs

Windows 10 x64:
WU : PG0009_v7.wu
MB7_win_x86_SSE2_OpenCL_ATi_HD5_r2929.exe :
Elapsed 132.969 secs
CPU 34.078 secs

WU : PG0395_v7.wu
MB7_win_x86_SSE2_OpenCL_ATi_HD5_r2929.exe :
Elapsed 75.868 secs
CPU 38.922 secs

WU : PG0444_v7.wu
MB7_win_x86_SSE2_OpenCL_ATi_HD5_r2929.exe :
Elapsed 72.832 secs
CPU 38.563 secs

WU : PG1327_v7.wu
MB7_win_x86_SSE2_OpenCL_ATi_HD5_r2929.exe :
Elapsed 83.678 secs
CPU 36.125 secs

VLAR crashed with default settings and loaded CPU under Win10 and passed OK under Vista... And other tasks not faster.

Maybe best tuned configs for both OSes could give smth different but this test shows typical config average user will get after BOINC installation. Default stock installation doesn't reserve CPU cores or tunes app params. For such pure default Win10 slower for my hardware :/

Thanks Fawkesguy and Ageless

As I continue to work my way thru this issue ...

With my AMD cards I've always been able to fix that issue by placing a link to the opencl file in usr/lib. I've already posted this a couple of times but can't find it, so, here it is again.
If you don't have GKSU and Nautilus installed, install them;
sudo apt-get install gksu
sudo apt-get install nautilus

In the terminal run gksu nautilus, that will open a file browser as root.
Look in /usr/lib and see if you have a file named libOpenCL.so. You probably don't or it is named libOpenCL.so.1. Go to usr/lib/fglrx and make a link to libOpenCL.so.1, then move the link to usr/lib. Once the link is in usr/lib rename the link libOpenCL.so. If that doesn't work, make another link and name that one libOpenCL.so.1. With those links in usr/lib it should work.

TBar
Thank you for info .. followed your suggestion but still no usable GPU found .. which proprietary driver are you using?

---

Thanks Fawkesguy and Ageless

As I continue to work my way thru this issue ...

With my AMD cards I've always been able to fix that issue by placing a link to the opencl file in usr/lib. I've already posted this a couple of times but can't find it, so, here it is again.
If you don't have GKSU and Nautilus installed, install them;
sudo apt-get install gksu
sudo apt-get install nautilus

In the terminal run gksu nautilus, that will open a file browser as root.
Look in /usr/lib and see if you have a file named libOpenCL.so. You probably don't or it is named libOpenCL.so.1. Go to usr/lib/fglrx and make a link to libOpenCL.so.1, then move the link to usr/lib. Once the link is in usr/lib rename the link libOpenCL.so. If that doesn't work, make another link and name that one libOpenCL.so.1. With those links in usr/lib it should work.

TBar
Thank you for info .. followed your suggestion but still no usable GPU found .. which proprietary driver are you using?

I'm still using Cat 14.6 beta on both my AMD machines, I haven't found anything better and my re-released Cayman is picky. It is still in the repository for Ubuntu 14.10 even though the notes say it's only good up to kernel 3.13. It might work with your kernel 3.16 or it might not. If you install your system using the Ubuntu 14.04.1 image it will use kernel 3.13, that's what I do. Then the Updates take it to 14.04.3 but it's still using the 3.13 kernel. I just made a fresh install a couple days ago on a new SSD and Cat 14.6 installed and worked without any problems, No links needed. It appears you can Still get it from AMD;
http://support.amd.com/en-us/kb-articles/Pages/Latest-LINUX-Beta-Driver.aspx

Here is the list you need to install first, install them in the order as per the log file to resolve package-dependency issues.
Package dh-modaliases is missing from the system. Install it using the command apt-get install dh-modaliases.
Package execstack is missing from the system. Install it using the command apt-get install execstack.
Package dpkg-dev is missing from the system. Install it using the command apt-get install dpkg-dev.
Package debhelper is missing from the system. Install it using the command apt-get install debhelper.
Package dkms is missing from the system. Install it using the command apt-get install dkms.
Package lib32gcc1 is missing from the system. Install it using the command apt-get install lib32gcc1.
I keep the log file handy to use on new installs...

All right, I am beat. Random locks with no lost work. I have disabled all power saving features; Blue Tooth never off, Screen Saver off, Monitor never off, WIFI never off....all of it. My PC doesn't stop unless I shut it down, or so the settings would indicate... It just locks up. Unfortunately I'm am never near it when it happens. I have the latest drivers and updates for Windoze 10 and AMD (including BETA drivers), all of them.

Any suggestions?

---

All right, I am beat. Random locks with no lost work. I have disabled all power saving features; Blue Tooth never off, Screen Saver off, Monitor never off, WIFI never off....all of it. My PC doesn't stop unless I shut it down, or so the settings would indicate... It just locks up. Unfortunately I'm am never near it when it happens. I have the latest drivers and updates for Windoze 10 and AMD (including BETA drivers), all of them.

Any suggestions?

That is why I never will have a new OS until it is a year old.

---

All right, I am beat. Random locks with no lost work. I have disabled all power saving features; Blue Tooth never off, Screen Saver off, Monitor never off, WIFI never off....all of it. My PC doesn't stop unless I shut it down, or so the settings would indicate... It just locks up. Unfortunately I'm am never near it when it happens. I have the latest drivers and updates for Windoze 10 and AMD (including BETA drivers), all of them.

Any suggestions?

That is why I never will have a new OS until it is a year old.

Man! No kidding. Skipped ME, 2000 and Vista. I miss XP. Maybe I should have stayed with Windoze 7, I don't know... Hell, even Windoze 8 seemed tame....

---

Along with Jord, I'm keeping Windows 7 for the forseeable future. My wife's proprietary work programs aren't compatible w/ 10 so her machine is staying on 7 as well.

---

New blog post about how updating to Windows 10 is going to become easier:

Our aspiration is for customers to choose Windows, and to love Windows. Our early data shows customers from France to Brazil to China to the US strongly preferring Windows 10 over Windows 8.1 or Windows 7. Through the usage of these first adopters of Windows 10, and great work by the Windows ecosystem of developers, application compatibility and kinks have been worked out of Windows 10. We’ve learned so much, and we’d like to share how we’re implementing some of our learnings which make it easier for consumers to upgrade to Windows 10.

-- We understand you care deeply about what happens with your device. This is why – regardless of your upgrade path – you can choose to upgrade or decline the offer.

That being said, we would encourage everyone to upgrade because Windows 10 is the best Windows ever – familiar, safer, faster, and full of innovations. After any upgrade, you can easily go back to your prior version of Windows within 31 days if you choose. We do this by keeping a full copy of your previous operating system on your device – including apps and settings – for the first 31 days following your upgrade. At any time during the first 31 days, you can go to “Settings->Update and Security->Recovery and Uninstall Windows 10” to return to your prior version of Windows.

-- You can specify that you no longer want to receive notifications of the Windows 10 upgrade through the Windows 7 or Windows 8.1 settings pages.

-- Our original approach for the Windows 10 roll out included a two-step process: First, reserve, then later, we notify you to start the upgrade process. While over 110 million devices have successfully upgraded to Windows 10, the two-step process is no longer relevant now that we are beyond the preorder phase and Windows 10 is immediately available.

-- We will soon be publishing Windows 10 as an “Optional Update” in Windows Update for all Windows 7 and Windows 8.1 customers.

Early next year, we expect to be re-categorizing Windows 10 as a “Recommended Update”. Depending upon your Windows Update settings, this may cause the upgrade process to automatically initiate on your device.

---

Not included in the preview quote above (but in the article that was linked), is a mention of being able to turn automatic updates off if you're on a metered connection.

What MS still doesn't seem to acknowledge is that hard-wired connections can also be metered. They seem to only allow wireless connections to be labeled as 'metered.' I'm recalling people in Australia and New Zealand that have satellite connections and ended up with $500 over-usage fees because of the 3-8gb worth of downloads for win10's "automatic download in the background whether you asked for it or not" tactic.

Those people have a satellite connection and then plug it into a normal home wifi router, but probably plug their main computer in with a cable to that router. For some reason, windows won't let you call a wired connection 'metered.'

Or like people such as myself who are unfortunately stuck with Comcast's data cap (even though it is 300gb/mo, but still) have a metered connection effectively, but Windows provides no way for us to say that it is metered and therefore do not have an unlimited corporate OC-3 connection at my disposal.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)