version 6000 unsupported must be 7100 or later что делать

# Kernel Issues

Issues surrounding from initial booting the macOS installer to right before the install GUI pops up.

# Stuck on [EB|#LOG:EXITBS:START]

This section will be split into 3 parts, so pay close attention:

# Booter Issues

The main culprits to watch for in the Booter section are:

DevirtualiseMmio

SetupVirtualMap

EnableWriteUnprotector

Regarding MATs support, firmwares built against EDK 2018 will support this and many OEMs have even added support all the way back to Skylake laptops. Issue is it’s not always obvious if an OEM has updated the firmware, you can check the OpenCore logs whether yours supports it(See here how to get a log):

# Kernel Patch Issues

This section will be split between Intel and AMD users:

# AMD Users

# Intel Users

# Legacy Intel users

For macOS Big Sur, many firmwares have issues determining the CPU core count and thus will kernel panic too early for screen printing. Via serial, you can see the following panic:

However on certain machines like the HP Compaq DC 7900, the firmware will still panic so we need to force a CPU core count value. Only use the below patch if AvoidRuntimeDefrag didn’t work:

Legacy CPU Core patch

To do this, Add the following patch(replacing the 04 from B8 04 00 00 00 C3 with the amount of CPU threads your hardware supports):

# UEFI Issues

# Stuck on EndRandomSeed

Same issues above, see here for more details: Stuck on [EB|#LOG:EXITBS:START]

# Stuck after selecting macOS partition in OpenCore

Same issues above, see here for more details: Stuck on [EB|#LOG:EXITBS:START]

# Kernel Panic on Invalid frame pointer

Another issue may be that macOS is conflicting with the write protection from CR0 register, to resolve this we have 2 options:

Regarding MATs support, firmwares built against EDK 2018 will support this and many OEMs have even added support all the way back to Skylake laptops. Issue is it’s not always obvious if an OEM has updated the firmware, you can check the OpenCore logs whether yours supports it:

Note: 1 means it supports MATs, while 0 means it does not.

# Stuck on [EB|LD:OFS] Err(0xE) when booting preboot volume

This can happen when the preboot volume isn’t properly updated, to fix this you’ll need to boot into recovery and repair it:

Then finally reboot

This is due to missing outdated Apple Secure Boot manifests present on your preboot volume resulting is a failure to load if you have SecureBootModel set, reason for these files being missing is actually a bug in macOS.

To resolve this you can do one of the following:

To do this via terminal:

This is due to incorrect BIOS settings:

# Stuck on Buffer Too Small

# Stuck on Plist only kext has CFBundleExecutable key

Missing or incorrect Executable path in your config.plist, this should be resolved by re-running ProperTree’s snapshot tool(Cmd/Ctrl+R).

# Stuck on This version of Mac OS X is not supported: Reason Mac.

This error happens when SMBIOS is one no longer supported by that version of macOS, make sure values are set in PlatformInfo->Generic with Automatic enabled. For a full list of supported SMBIOS and their OSes, see here: Choosing the right SMBIOS

# Couldn’t allocate runtime area errors

Well this general area is where a lot of PCI devices are first setup and configured, and is where most booting issues will happen. Other names include:

The main places to check:

Missing EC patch:

IRQ conflict:

PCI allocation issue:

NVMe or SATA issue:

NVRAM Failing:

(opens new window) on how to stop NVRAM write, note that for install you do not need to run the script. Just setup the config.plist

RTC Missing:

Example of what a disabled RTC with no way to enable looks like(note that there is no value to re-enable it like STAS ):

# Stuck at ACPI table loading on B550

If you’re getting stuck at or near ACPI table loading with an AMD B550 or A520 motherboard, add the following SSDT:

# «Waiting for Root Device» or Prohibited Sign error

This is generally seen as a USB or SATA error, couple ways to fix:

# USB Issues

This assumes you’re only booting the installer USB and not macOS itself.

If you’re hitting the 15 port limit, you can temporarily get around this with XhciPortLimit but for long term use, we recommend making a USBmap

Another issue can be that certain firmware won’t pass USB ownership to macOS

Sometimes, if the USB is plugged into a 3.x port, plugging it into a 2.0 port can fix this error.

For AMD’s 15h and 16h CPUs, you may need to add the following:

If XLNCUSBFix still doesn’t work, then try the following:

X299 Users: Enable Above4G Decoding

Missing USB ports in ACPI:

# SATA Issues

On rare occasions(mainly laptops), the SATA controller isn’t officially supported by macOS. To resolve this, we’ll want to do a few things:

Note that you will only experience this issue after installing macOS onto the drive, booting the macOS installer will not error out due to SATA issues.

# Kernel panic with IOPCIFamily on X99

For those running the X99 platform from Intel, please go over the following:

# Stuck on or near IOConsoleUsers: gIOScreenLock. / gIOLockState (3.

This is right before the GPU is properly initialized, verify the following:

# Scrambled Screen on laptops

Enable CSM in your UEFI settings. This may appear as «Boot legacy ROMs» or other legacy setting.

# Black screen after IOConsoleUsers: gIOScreenLock. on Navi

For MSI Navi users, you’ll need to apply the patch mentioned here: Installer not working with 5700XT #901

Note: macOS 11, Big Sur no longer requires this patch for MSI Navi.

# Kernel Panic Cannot perform kext summary

Generally seen as an issue surrounding the prelinked kernel, specifically that macOS is having a hard time interpreting the ones we injected. Verify that:

Note: this error may also look very similar to Kernel Panic on Invalid frame pointer

# Kernel Panic AppleIntelMCEReporter

With macOS Catalina, dual socket support is broken, and a fun fact about AMD firmware is that some boards will actually report multiple socketed CPUs. To fix this, add AppleMCEReporterDisabler

# Kernel Panic AppleIntelCPUPowerManagement

# Kernel Panic AppleACPIPlatform in 10.13

On macOS 10.13, High Sierra the OS is much stricter with ACPI tables, specifically a bug with how headers were handled

# macOS frozen right before login

This is a common example of screwed up TSC, for most system add CpuTscSync

The most common way to see the TSC issue:

Case 1	Case 2

# Keyboard works but trackpad does not

Make sure that VoodooInput is listed before VoodooPS2 and VoodooI2C kexts in your config.plist.

# kextd stall[0]: AppleACPICPU

This is due to either a missing SMC emulator or broken one, make sure of the following:

# Kernel Panic on AppleIntelI210Ethernet

For those running Comet lake motherboards with the I225-V NIC, you may experience a kernel panic on boot due to the I210 kext. To resolve this, make sure you have the correct PciRoot for your Ethernet. This commonly being either:

For those who can to your PciRoot manually, you’ll want to install macOS fully and run the following with gfxutil

This should spit out something like this:

The ending PciRoot(0x0)/Pci(0x1F,0x6) is what you want to add in your config.plist with device-id of F2150000

# Kernel panic on «Wrong CD Clock Frequency» with Icelake laptop

# Kernel panic on «cckprng_int_gen»

This is likely to be 1 of 2 things:

For the latter, ensure you’re only using SSDT-CPUR with B550 and A520. Do not use on X570 or older hardware(ie. B450 or A320)

# Stuck at Forcing CS_RUNTIME for entitlement in Big Sur

This is actually the part at where macOS will seal the system volume, and where it may seem that macOS has gotten stuck. DO NOT RESTART thinking you’re stuck, this will take quite some time to complete.

# Stuck on ramrod (^^^^^^^^^^^^^)

If you get stuck around the ramrod section (specifically, it boots, hits this error, and reboots again back into this, causing a loop), this hints that your SMC emulator is broken. To fix this, you have 2 options:

(opens new window) (you can use the MinKernel / MaxKernel trick mentioned above to restrict FakeSMC to Big Sur and up

And when switching kexts, ensure you don’t have both FakeSMC and VirtualSMC enabled in your config.plist, as this will cause a conflict.

# Virtual Machine Issues

# Reboot on «AppleUSBHostPort::createDevice: failed to create device» on macOS 11.3+

Источник

Blender 2.78 can’t import any FBX exported from Cheetah v7

pegot

Active member

Blender 2.78 can’t import any FBX exported from Cheetah v7

I tried all options, from exporting as FBX 6.1.0 and FBX 7.5.0 (all both as binary and Ascii even though Blender only accepts binary).

For FBX 6.1.0 Blender error was:
Version 6100 unsupported, must be 7100 or later.

But when I did export as the later FBX 7.5.0 it said:
Unsupported FBX version (7500), binary format is incompatible!

The only way I was able to get an FBX from Cheetah into Blender 2.78a was to first convert it to FBX 2013 version using Autodesk’s free (but no longer maintained) FBX converter.

Is FBX 2013 a version between 6.1.0 and 7.50?

podperson

Well-known member

pegot

Active member

I was transferring a morph animation to Blender Shape Keys and Collada didn’t seem to work for that, though I had no trouble importing the model itself as dae.

Will need to double check on that agin though when I am in front of my computer. I might not have looked at the shape keys when I imported the Collada file.

After converting using the Autodesk app the FBX file came in with its Shape Key animations perfectly though.

Swizl

Well-known member

I was transferring a morph animation to Blender Shape Keys and Collada didn’t seem to work for that, though I had no trouble importing the model itself as dae.

Will need to double check on that agin though when I am in front of my computer. I might not have looked at the shape keys when I imported the Collada file.

After converting using the Autodesk app the FBX file came in with its Shape Key animations perfectly though.

pegot

Active member

I don’t think its Cheetah I think the issue is in fact Blender. When I was Googling the problem I found a bunch of posts with Blender users having an issue with FBX import.

What could be useful, though, is if Cheetah maybe afford additional FBX versions to export to since the Autodesk 2013 versions seem to work with Blender. But then I really don’t know ho much additional work that would be for Martin. Guess we could always just use the Autodesk converter. But at some point that may no longer work with newer OS versions.

Swizl

Well-known member

I don’t think its Cheetah I think the issue is in fact Blender. When I was Googling the problem I found a bunch of posts with Blender users having an issue with FBX import.

What could be useful, though, is if Cheetah maybe afford additional FBX versions to export to since the Autodesk 2013 versions seem to work with Blender. But then I really don’t know ho much additional work that would be for Martin. Guess we could always just use the Autodesk converter. But at some point that may no longer work with newer OS versions.

Ok, I’ve made some very simple cube animations in each app and try all three of them in the other. Blender FBX to MODO works. MODO to Blender works with some odd scaling of the camera etc. C3d to Blender acts like it’s importing right, but the cube and animation are nowhere to be seen. C3d to MODO flat out refused to open it at all.

Maybe my settings aren’t right either. Attaching the three files if anyone else wants to look.

edit:
I didn’t see this Blender error on importing the C3d FBX until after posting this. «Couldn’t open file «C3d FBX Test.fbx» (Unsupported FBX version (7500), binary format is incompatible!)

edit 2:
The other version of FBX gives this error in Blender. «ASCII FBX files are not supported C3d FBX Test v6.fbx»

Oops, I see you’ve already posted those errors! Maybe Martin can chime in?

Attachments

Martin

Moderator

Hi,
Cheetah3D 7 is using the latest FBX SDK 2017.1 which exports to the FBX 7.5.0 file format by default. The FBX 7.5.0 file format was introduced with the FBX SDK 2016 and is incompatible with all FBX SDKs older than 2016.

The problem with the new FBX 7.5.0 file format is that all integers are now saved in 64Bit and no longer in 32Bit. I’m actually not sure why Autodesk did this troublesome decision since 32Bit integers should be more than enough for todays needs. I also don’t think that they did the FBX file format a favor by completely breaking backward compatibility.

Unluckily the FBX SDK 2017 can’t generate 7.4.0 files anymore. But apps which haven’t updated to the FBX SDK 2016 should still be able to import FBX 6.1.0 files but I’m not sure how compatible the FBX 6.1.0 files generated by 2017.1 are.

The FBX SDK 2013 is quite outdated. It was already released in early 2012 and generates FBX 7.3.0 files. So maybe it’s a good time to update the importer in Blender.

While it is possible to bundle various older FBX SDKs it’s not really possible for me for two reasons.
1. The APIs of the FBX SDK changes regularly so I can’t use the same exporter code for all versions of the FBX SDK. I would have to maintain various versions of my exporter class. The work would linearly grow with every FBX SDK I support.
2. I would be forces to bundle various shared libraries of the FBX SDK. But it has a 30 MByte file size. Since Autodesk releases every year a FBX SDK the fie size of Cheetah3D would grow every year by 30 MByte.

Источник

Debian не апгрейдится: Kernel must be upgraded. Попытка обновить kernel приводит к этой же ошибке

При попытке апгрейда Debian со stretch на buster вышла ошибка:

Попытка вручную обновить kernel приводит к этой же ошибке. Версий меньше 4.19 apt search не предлагает. Команду ввожу следующую:

Что делать? Как обновить kernel?

Верни всё назад! ТЕБЕ обновление НЕНУЖНО! Не судьба.

ну, а glibc-то обновилась?

свежее ядро можно впихнуть лапками руками с помощью dpkg, но я бы всё-таки сначала забекапил данные и настройки – процентов 75 даю, что в процессе система придёт в негодность.

классная шутка, забористая: «и взлетит, и влетит … мало не покажется»

Виртуалочка на OpenVZ?

не хочешь и ладно: тебе больше надо

А если требуемые пакеты поставить и потом reconfigure на сам пакет с ядром? Тут же непонятно, в чем корень ошибки, когда все зависимости вытаскиваешь руками. Еще бы посоветовал работать через chroot

Ни на что новее Debian 9 Stretch / Devuan 2 ASCII на OpenVZ 6 надеяться не получится (если не считать Alpine), ядро «обновить» на OpenVZ всё равно не сможешь, это контейнер.

Спасибо за предложение. Но проще новый VPS купить с уже установленным Debian-ом нужной версии.

Но проще новый VPS купить с уже установленным Debian-ом нужной версии.

В данном случае, это даже не «проще», а так и нужно, потому что OpenVZ 6 – это проблема.

А теперь посмотри, сколько у тебя локальных пакетов : aptitude search

VDS (виртуалку) лучше возьми, там всякие долбаны уже не будут решать, какое ядро использовать, да и своп можно самому регулировать. Ну и по такому случаю я бы сразу двигал на мейнстрим: AWS, Azure, Яндекс на худой конец.

Никак, тогда. Там принцип работы такой, что ядро хостовой системы и у тебя на виртуалке.

Да, ладно. Если «для себя», то стоит начать с бесплатных Oracle виртуалок. Если не прокатит, то выбирать что-то поконкретнее под задачу/бюджет. Не спорю, AWS, Azure, DO, Vultr могут быть вот тут как раз в тему.

Источник

Ошибки при прошивки Samsung телефонов в ODIN

Ошибки при прошивки Samsung телефонов в ODIN. И так вы созрели до момента, что необходимо прошить свой Samsung. Скачали программу Odin, прочитали статью как прошить свой Android, нашли прошивку, но в момент ее установки все время выбивает ошибки? Как это все исправить и понять что происходит? Все ответы в данной статье!

Типичные ошибки при прошивки Samsung в ODIN

Ошибка подключения устройства

Вариант 1

Вариант 2

Решение:

Samsung «не виден» в Odin

В Odin не отображается ID и COM подключенного смартфона или планшета Samsung

Решение:

Процесс прошивки остановлен на процессе инициализации (проверка подключения)

Если при прошивке Samsung в программе ODIN появиться ошибка:

Вариант 1

Вариант 2

Решение: Необходимо подключить устройство в другой USB порт, либо попробовать прошить Samsung на другом компьютере.

Файл Прошивки битый: MD5 hash value is invalid

Если Odin не дает прошить Android и выдает подобную ошибку:

Это означает что, вы скачали битый файл (недокачанный) или файл не верно подписан.

Решение: Стоит убедиться действительно ли файл прошивки скачанный полностью, если нет, то перекачать. Если файл скачан полностью, удалить с файла расширение .md5

Ошибки при прошивке разделов system.img, boot.img, recovery.img, sboot.bin, cache.img и других разделов

и другие похожие варианты, но с разными разделами.

Может возникнуть из-за того, что вы пытаетесь прошить либо битый файл прошивки или от другого устройства Samsung ( у вас модель i9100, а прошиваете от i9300). Также это может быть следствие попытки понизить версию ОС Android.

Решение:

Ошибки связанные с повреждением разделов памяти Samsung

Вариант 1

Вариант 2

Вариант 3

Данные проблемы могут возникнуть в следствие повреждения разметки секторов внутренних разделов флеш-памяти устройства, попытки прошить чужой или модифицированный PIT файл, либо поврежден загрузчик

Решение:

Ошибки с отсутствием возможности доступа к записи разделов

Изменить несколько параметров в настройках:

1. Включить « Отладку по USB » и там в же настройках включить «Разблокировка OEM»;

2. Отключить «Удаленное управление» Samsung;

Samsung не запускается

Если у вас на экране похожее соображение, то это означает что предыдущая прошивка была прервана:

Решение:

Источник