## Repair of the Antminer S9 control board

Antminer S9 does not display a kernel page and cannot access settings to change the pool details. updated firmware via Bitmain. The flash controller card with SD card and miner was started, but could not save any new pool settings. When the miner was restarted, it returned to the settings that were mined in Antpool if it previously had to contain slush pool details on which it was last mined for flashing. can someone please help me with this problem.

## Repair – is it possible / practical to set the light meter of the Gost scale on a Kiewer 4M so that it works with ASA values?

I have just received a Kiewer 4M (a Contax II or Contax III variant built in Ukraine, which was manufactured with repatriated devices from the Zeiss plant). This is the version with a light meter made of selenium (or silicon?) On the top of the camera directly under the accessory shoe. It is a "middle needle" type, in which the exposure on a dial is set around the rewind button with film speed scale in the old Soviet Gost system (the Gost value is 90% of ASA, so Gost 100 film would be ASA 90 ) You measure by turning the exposure control until the measuring needle is on the diamond marking. Then read the exposure (shutter and aperture values) from the scale and enter them into the lens and the shutter timer.

It's a relatively easy-to-use meter and more convenient than wearing a separate meter, although it's less useful indoors due to its limited sensitivity (a very common problem with selenium meters).

What interests me is whether it's fairly easy to set this meter to read 10% lower so that I can set the film speed of the linear ISO / ASA scale directly on the measurement scale.

Under / behind the meter is a tiny screw in a protective collar on the back of the top cover of the camera. Is this screw for adjusting the meter or the rangefinder? If the former, is a 10% change in reading practical to apply with this screw?

## How to repair rubber grips on Nikon cameras yourself?

I recommend the Loctite Plastics Bonding System for this kind of "rubbery" plastics. I haven't used it specifically for a Nikon grip, but it works very well in similar applications.

The problem with normal "5 min" epoxy and gorilla glue is that they are stiff and not flexible, so the glue cannot bond with rubber items. Gorilla Glue has the additional problem that it is suitable for porous surfaces, requires activation with water (not in plastics) and expands when cured, so it may not look original when using Gorilla Glue.

The special thing about this material is that it has something to offer. In applications where you need something that isn't stiff like regular epoxy, you should get the following:

http://www.loctiteproducts.com/p/sg_plstc/overview/Loctite-Plastics-Bonding-System.htm

## redhat – Repair the file system by editing the fstab file

Is it possible to run the xfs repair by editing the fstab file again?

``````/dev/mapper/vg-linux_root /                       xfs     defaults        0 0
UUID=7de1dc5c-b605-4a6f-bdf1-f1e869f6ffb9 /boot   xfs     defaults        0 0
/dev/mapper/vg-linux_var /var                     xfs     defaults        0 0
/dev/mapper/vg-linux_swap swap                    swap    defaults        0 0
``````

I'm not sure, but by replacing the last number from 0 to 1, is it correct?

## git – move Gitlab to a new IP address, lfs has stopped working. How do you repair?

We installed GitLab 11.2.1-ee on our local network
We use Git LFS in our projects
And all work fine before we change the Gitlab computer's IP address.
We changed the IP address of the Gitlab computer to 192.168.160.160 and LFS no longer works
Now it shows errors

``````Error downloading object: some/object/path: Smudge error: Error downloading some/object/path (HASH_OF_OBJECT): batch response: Post http://192.168.1.100/root/PROJECT.git/info/lfs/objects/batch: dial tcp 192.168.1.100:80: connect: network is unreachable
``````

We have changed the address from gitlab to customers in a new one.
We also changed external_url to gitlab.rb
Our git projects that do not use lfs work perfectly.
Only projects with LFS show this error

How can I fix it?

## Repair operator for evolutionary algorithm

I am working on a resource allocation problem using a SPEA 2 evolution algorithm. The problem concerns decision variables where each variable has a different domain, e.g. $$E_i le d_i$$ Where $$E_i$$ is the assignment to a user and $$d_i$$ is individual requirements. The problem involves a linear constraint, so $$sum (E_i) = total resource$$. The likelihood that possible offspring will arise after crossover and mutation operators is extremely low. For this purpose we need a repair operator. I need instructions for choosing suitable repair operators and how should I use it? I mean, we should fix all solutions or a certain percentage.

So far I have designed an operator who repairs the generated spring as follows:
1) Apply bound
2) Determine a constraint violation, i.e. H. A leftover resource or an overused resource
3) Find unmet demand $$d_i$$
4) Distribute the remaining resource proportionally to the user. So update them $$E_i$$

This operator creates a workable solution, but I'm not sure if my approach is appropriate and what percentage of the solution I need to fix.

## Windows Startup Repair: The Boot Manager could not find the OS Loader

File repair error code failed 0x57
Boot configuration data store repair failed with error code 0x490

The computer is in a non-bootable state, not even in security mode. I cloned the Windows installation onto a new hard drive, on which I ended up with a Linux installation on a partition. It won't boot. Tried fixboot fixmbr bcdboot, not working from these.

How can I fix this without reinstalling?

## Distributions – How can I correctly repair a site that was originally developed with Composer but was made available via FTP?

I have put together a site with the Drupal Varbase distribution. I installed with Composer, this is my first project with Composer. Now that I'm done with the development, I'm working on installing it on our production server. I created the database and filled it with the data from development, the code base via FTP in production on & # 39; public_html & # 39; uploaded and then tried to load the site. Then I got my first 500 server error:

``````(17-Mar-2020 22:15:07 UTC) PHP Warning:  require(/home/vuunifcm/public_html/../vendor/autoload.php): failed to open stream: No such file or directory in /home/vuunifcm/public_html/autoload.php on line 16
(17-Mar-2020 22:15:07 UTC) PHP Warning:  require(/home/vuunifcm/public_html/../vendor/autoload.php): failed to open stream: No such file or directory in /home/vuunifcm/public_html/autoload.php on line 16
(17-Mar-2020 22:15:07 UTC) PHP Fatal error:  require(): Failed opening required '/home/vuunifcm/public_html/../vendor/autoload.php' (include_path='.:/opt/cpanel/ea-php73/root/usr/share/pear') in /home/vuunifcm/public_html/autoload.php on line 16
``````

I am used to all the files that are required for a site that is contained in the site's root folder, which for me is usually "public_html". It appears that Composer is installed at a higher level and the error is somehow trying to reference components in higher directories where Composer would be located. I thought Composer was more of a utility and not part of the actual website, but now I know I'm wrong, so I uploaded the Composer files from the parent directory.

However, when I did the Varbase installation with Composer when I created the site on the dev server, the site was in a folder called & # 39; docroot & # 39; and not & # 39; public_html & # 39; filed. I thought I was going to refer to & # 39; docroot & # 39; search and see if changing these instances to & # 39; public_html & # 39; would help. I found it in the composer files. However, your change only resulted in:

``````(17-Mar-2020 23:09:56 UTC) PHP Warning:  include(/home/vuunifcm/vendor/composer/../../docroot/core/lib/Drupal/Core/DrupalKernel.php): failed to open stream: No such file or directory in /home/vuunifcm/vendor/composer/ClassLoader.php on line 444
(17-Mar-2020 23:09:56 UTC) PHP Warning:  include(/home/vuunifcm/vendor/composer/../../docroot/core/lib/Drupal/Core/DrupalKernel.php): failed to open stream: No such file or directory in /home/vuunifcm/vendor/composer/ClassLoader.php on line 444
(17-Mar-2020 23:09:56 UTC) PHP Warning:  include(): Failed opening '/home/vuunifcm/vendor/composer/../../docroot/core/lib/Drupal/Core/DrupalKernel.php' for inclusion (include_path='/home/vuunifcm/vendor/pear/archive_tar:/home/vuunifcm/vendor/pear/console_getopt:/home/vuunifcm/vendor/pear/pear-core-minimal/src:/home/vuunifcm/vendor/pear/pear_exception:.:/opt/cpanel/ea-php73/root/usr/share/pear') in /home/vuunifcm/vendor/composer/ClassLoader.php on line 444
(17-Mar-2020 23:09:56 UTC) PHP Fatal error:  Uncaught Error: Class 'DrupalCoreDrupalKernel' not found in /home/vuunifcm/public_html/index.php:16
Stack trace:
#0 {main}
thrown in /home/vuunifcm/public_html/index.php on line 16
``````

Could this be the cause of my problems or was my approach wrong? I have the feeling that I have gone in the completely wrong direction. Can this be fixed or do I have to start with a different approach? I know there may be a workaround, but I don't want to mess around with workarounds every time I need to update the site from here.

## Lens – aperture repair from Nikon 14-24 f / 2.8G

[![Hi there.
Somehow one of the nine blades in the aperture of my Nikon 14-24mm f / 2.8G has completely loosened and is turned sideways when I look through the lens. I do not want to pay money for the repair and I am technically quite competent. Before I really take the lens apart, I have questions. Does anyone know how difficult it is to repair? And can I repair this blade that came loose by itself or do I have to replace the entire orifice membrane assembly?
Thank you very much
Andrew] [1]] [1]

[1]: https://i.stack.imgur.com/a0m8Y.jpg