Jump to content

Clover Theme Manager


blackosx
 Share

589 posts in this topic

Recommended Posts

Strange for it to just stop there without the /tmp/CloverThemeManager directory as the app binary creates /tmp/CloverThemeManager on launch before the bash script is started.

 
Are you using the latest version of CloverThemeManager?
Are there any errors in system.log?
Link to comment
Share on other sites

Well done updating your theme on the repo chris1111.

 

For ref:

I notice you are following the steps in the add_theme.html file, which is great.

When you get to step 6 - Commit your change, you don't have to enter the command exactly as I have shown and you can always change the message to describe the commit.

 

For example. Rather than

git commit -m "Adding my new theme."

You could use something like this (from your last commit)

git commit -m "Updating the screenshot"

:)

  • Like 1
Link to comment
Share on other sites

Well done updating your theme on the repo chris1111.

 

For ref:

I notice you are following the steps in the add_theme.html file, which is great.

When you get to step 6 - Commit your change, you don't have to enter the command exactly as I have shown and you can always change the message to describe the commit.

 

For example. Rather than

git commit -m "Adding my new theme."

You could use something like this (from your last commit)

git commit -m "Updating the screenshot"

:)

Ok perfect; thank you blackosx  :)

Link to comment
Share on other sites

  • 3 months later...

updateID 15 pushed.

 
- Fix two incorrect calls to the wrong git binary. 
- Change detection of default gateway dependent on use of either discoveryd or mDNSResponder.
- Improve feedback on first page when loading the app.
 
Previous versions should present update.
But otherwise I've attached latest build to first post.
 
Note: If re-loading the app, after updating from inside the app, you see the ‘Symbolic Link’ status as red then please quit the app and re-load it.
  • Like 1
Link to comment
Share on other sites

updateID 16 pushed.

 
- Click theme bands rather than image thumbnail to reveal large theme screenshot.
- Fix bug where uninstalling a theme with an update still showed the update available.
- Double check temp directory is removed at close of app.
 
Previous versions should present update.
But otherwise I've attached latest build to first post.
 
Note: If re-loading the app, after updating from inside the app, you see the ‘Symbolic Link’ status as red then please quit the app and re-load it (should be fixed now and not happen for future updates).

 

  • Like 1
Link to comment
Share on other sites

Any help with this?

 

"The remote Clover Theme repository is not responding. This app cannot continue. Exiting."

The problem with sf.net site. Please wait, they say.

  • Like 1
Link to comment
Share on other sites

Hi,

I recently purchased a LG 34UM95-P 21:9 display wit a resolution of 3440x1440 and I'm currently using the 'mac' theme but it looks distorted (stretched and cut off at the bottom) with this display.

Does anyone know which theme I should use with this display to get correct aspect ratio?

Is there a 21:9 theme available or is someone willing to create one?

 

Changing GUI resolution to 3400x1440 in clover didn't change anything unfortunately :(

Hope to post this in the right section, if not please point me in the right direction – I couldn't find anything regarding this.

 

Thanks in advance!

Link to comment
Share on other sites

Wow.. That's a beast of a monitor :)

If the video resolution can be correctly set then I believe Clover would properly draw a theme to fit.

Are you booting legacy or UEFI? if using UEFI are you using CsmVideoDxe-64.efi in /EFI/CLOVER/drivers64UEFI on the ESP?

Maybe check Clover's bootlog to see what it says about detected video modes.

Also, when in Clover's GUI you can press up/down arrows on the keyboard to switch different video resolutions.

Link to comment
Share on other sites

Wow.. That's a beast of a monitor :)

If the video resolution can be correctly set then I believe Clover would properly draw a theme to fit.

Are you booting legacy or UEFI? if using UEFI are you using CsmVideoDxe-64.efi in /EFI/CLOVER/drivers64UEFI on the ESP?

Maybe check Clover's bootlog to see what it says about detected video modes.

Also, when in Clover's GUI you can press up/down arrows on the keyboard to switch different video resolutions.

CsmVideoDxe-64.efi in /EFI/CLOVER/drivers64UEFI gave me no input upon boot (after clover menu) so I had to connect my ssd with my macbook pro and remove it.

arrow up/down doesn't do anything unfortunately..

how to access bootlog?

any other solutions?

Link to comment
Share on other sites

hmmm.. Do you have PatchVBios=yes in your config.plist ?

 
This goes in the graphics section
    <key>Graphics</key>
    <dict>
        <key>PatchVBios</key>
        <string>Yes</string>
    </dict>
 
Clover bootlog will be in ioreg. The simplest way to read it is by using the bdmesg tool which normally gets installed to /usr/local/bin by a bootloader installer. Typing bdmesg in Terminal will be enough to print the bootlog if you have it installed. Otherwise for simplicity, just run Darwindumper's Firmware (Boot) Log dump with does the same thing.
 
Here's what I see here with UEFI boot using CsmVideoDxe
0:137  0:005  LoadDrivers() start
0:178  0:016  Loading CsmVideoDxe-64.efi  status=Success
0:232  0:010  Video driver loaded: disconnect Success
0:320  0:012  VideoBiosPatchNativeFromEdid:
0:325  0:005   Bios: ATI, MasterDataTables: 0xCA948, std_vesa: 0xCA98C, ati_mode_table: 0xCA990, mode_table_size: 0x1F8 BT_ATI_2
0:363  0:037   VideoBiosPatchInit(LegacyRegion = Success) = Success
0:379  0:015   VideoBiosUnlock:  unlocked
0:393  0:014   Patching: BT_ATI_2
0:405  0:011   Parse Edid: descriptor block 0 is timing descriptor (h_active: 1920, v_active: 1080, h_sync_offset: 88, h_sync_width: 44, h_blanking: 280, v_blanking: 45, pixel_clock: 14850, v_sync_offset: 4, v_sync_width: 5)
0:426  0:021   mode 0 (320x200) patched to 1920x1080
0:431  0:005   VideoBiosLock: Success
0:459  0:027  CsmVideoDriverBindingStart
0:464  0:005  mixed support=40010
0:469  0:005  Controller is [030000]
0:474  0:005  Check for VBE
0:510  0:035   found Detail Timing 1920x1080
0:517  0:007    0 1920x1080 attr=BB - ok, edid+, working, highest, pref=0
0:555  0:037    1 1152x864 attr=BB - ok, edid+, working
0:578  0:023    2 1280x960 attr=BB - ok, edid+, working
0:601  0:022    3 640x480 attr=BB - ok, edid+, 640x480, working
0:628  0:027    4 800x600 attr=BB - ok, edid+, 800x600, working
0:656  0:027    5 1024x768 attr=BB - ok, edid+, 1024x768, working
0:684  0:027    6 1280x1024 attr=BB - ok, edid+, working
0:708  0:023    7 1400x1050 attr=BB - ok, edid-
0:728  0:020  CsmVideo: New mode: 0 1920x1080 - set
0:847  0:118   - SetMode pref 0 (0) = Success
0:854  0:007  CsmVideoCheckForVbe - Success
0:861  0:006  CsmVideoDriverBindingStart end Success
0:866  0:005  CsmVideo: New mode: 4 800x600 - blocking that switch
0:876  0:010  CsmVideo: New mode: 1 1152x864 - blocking that switch
0:886  0:010  CsmVideoDriverBindingStart
0:907  0:005  CsmVideoDriverBindingStart end Unsupported
0:986  0:079  LoadDrivers() end
1:075  0:082  SetScreenResolution: 1920x1080 - already set
1:087  0:011  Console modes reported: 3, available modes:
1:092  0:005    Mode 1: 80x25 (current mode)
1:097  0:005    Mode 2: 80x50
1:102  0:005    Mode 3: 100x31
1:107  0:005  SetScreenResolution: 1920x1080 - already set
 
And with Legacy boot:
0:804  0:010  Video bios patch requested or CustomEDID - forcing video reconnect
0:815  0:011  2 drivers needs connecting ...
0:818  0:002  PlatformDriverOverrideProtocol->GetDriver overriden
0:821  0:002  Video driver loaded: disconnect Success
0:884  0:062  VideoBiosPatchNativeFromEdid:
0:886  0:002   Bios: ATI, MasterDataTables: 0xCA948, std_vesa: 0xCA98C, ati_mode_table: 0xCA990, mode_table_size: 0x1F8 BT_ATI_2
0:903  0:017   VideoBiosPatchInit(LegacyRegion = Not Found, LegacyRegion2 = Success) = Success
0:936  0:032   VideoBiosUnlock:  unlocked
0:948  0:012   Patching: BT_ATI_2
0:953  0:004   Parse Edid: descriptor block 0 is timing descriptor (h_active: 1920, v_active: 1080, h_sync_offset: 88, h_sync_width: 44, h_blanking: 280, v_blanking: 45, pixel_clock: 14850, v_sync_offset: 4, v_sync_width: 5)
0:968  0:015   mode 0 (320x200) patched to 1920x1080
0:973  0:005   VideoBiosLock: Success
0:997  0:023  BiosVideoDriverBindingStart!
1:006  0:009  BiosVideoCheckForVbe
1:008  0:002  EdidOverride not found
1:040  0:031   Edid1+
1:048  0:008   found Detail Timing 1920x1080
1:079  0:031   Edid0+
1:092  0:012   found Detail Timing 1920x1080
1:100  0:008  ... already present
1:106  0:005     0 1920x1080 attr=BB - ok, edid+, working, highest, pref=0
1:159  0:053     1 1152x864 attr=BB - ok, edid+, working
1:180  0:020     2 1280x960 attr=BB - ok, edid+, working
1:215  0:035     3 640x480 attr=BB - ok, edid+, 640x480, working
1:242  0:027     4 800x600 attr=BB - ok, edid+, 800x600, working
1:291  0:049     5 1024x768 attr=BB - ok, edid+, 1024x768, working
1:312  0:020     6 1280x1024 attr=BB - ok, edid+, working
1:332  0:019     7 1400x1050 attr=BB - ok, edid-
1:350  0:017  BV new mode: 0 1920x1080
1:471  0:121   SetMode pref 0 (0) = Success
1:583  0:111  LoadDrivers() end
1:587  0:004  SetScreenResolution: 1920x1080 - already set
1:593  0:005  Console modes reported: 4, available modes:
1:595  0:002    Mode 1: 80x25
1:598  0:002    Mode 2: 80x50
1:601  0:002    Mode 3: 100x31
1:603  0:002    Mode 4: 240x56 (current mode)
1:606  0:002  SetScreenResolution: 1920x1080 - already set

 

Link to comment
Share on other sites

That's strange. Although I set 1920x1080 in clover configurator (and 3440x1440 before that) this resolution apparently isn't recognized. Because of the 'mac' theme perhaps?

Do I need a fullHD theme? Can't be because it worked fine before with my Eizo at 1920x1200

PatchVBios isn't activated. Should I do that?

Here's the log uefi without CsmVideoDxe

 

btw, forget my signature - it's from 2007. using gtx 670 now which works oob.

0:116  0:000  LoadDrivers() start
0:118  0:002  Loading FSInject-64.efi  status=Success
0:120  0:001  Loading OsxAptioFix2Drv-64.efi  status=Success
0:121  0:001  Loading OsxFatBinaryDrv-64.efi  status=Success
0:122  0:000  Loading HFSPlus.efi  status=Success
0:124  0:002   - driver needs connecting
0:124  0:000  1 drivers needs connecting ...
0:124  0:000  PlatformDriverOverrideProtocol->GetDriver overriden
0:124  0:000  HFS+ driver loaded 
0:124  0:000  Searching for invalid DiskIo BY_DRIVER connects: not found, all ok
0:227  0:102  LoadDrivers() end
0:227  0:000  Dump SMC keys from NVRAM:
0:231  0:004  SetScreenResolution: 1920x1080 - not found!
0:231  0:000  SetMaxResolution: found best mode 1: 1024x768
0:231  0:000   - already set
0:231  0:000  Console modes reported: 3, available modes:
0:231  0:000    Mode 1: 80x25 (current mode)
0:231  0:000    Mode 2: 128x40
0:231  0:000    Mode 3: 100x31
0:231  0:000  SetScreenResolution: 1024x768 - already set
Link to comment
Share on other sites

Don't worry about any particular theme for now.

Add the PatchVBios entry in config.plist and may as well add 3440x1440 in there too.

Then try.

 

EDIT:

I'm thinking you will want to try these settings in the config.plist

    <key>Graphics</key>
    <dict>
        <key>Inject</key>
        <dict>
            <key>NVidia</key>
            <true/>
        </dict>
        <key>PatchVBios</key>
        <true/>
    </dict>
    <key>GUI</key>
    <dict>
        <key>ScreenResolution</key>
        <string>3440x1440</string>
    </dict>
  • Like 1
Link to comment
Share on other sites

And doesn't show for example

0:804  0:010  Video bios patch requested or CustomEDID - forcing video reconnect[\code]You should see that.

Are you sure your configure.plist is correct?

 

EDIT:

Argh... Stupid forum software and iPhone...!!

Link to comment
Share on other sites

Same thing, no input when injecting nvidia.

when injecting patchvbios and setting res to 3440x1440 there'S no effect

I am sorry but Clover can't set the resolution for Nvidia cards.

Possible resolutions for Nvidia are

static TABLE_0 nvda_res[RESOLUTIONS_NUMBER] = {
  {1280,  720},
  {1280,  800},
  {1360,  768},
  {1400, 1050},
  {1440,  900},
  {1600,  900},
  {1600, 1200},
  {1680, 1050},
  {1920, 1080},
  {1920, 1200},
  {2048, 1536}
};

That's all, sorry.

Link to comment
Share on other sites

 Share

×
×
  • Create New...