-
#1
Здравствуйте. Не получается соединиться с CM2MT2 ver.2.28
Получаю ошибку Fail to init protocol!
Mode : FLASH
1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
2. Insert USB cable in phone
Waiting for device connection …
PTFN : MediaTek PreLoader USB VCOM_V1632 (Android) (COM6)
MODE : PRELOADER PORT
PORT : 6
Waiting BOOT ack …
PRELOADER : ACK confirmed!
BROM : Init BROM
Error : Fail to init protocol!
>>> Remove battery, cable. Check cable/connection/driver! Check SW hint! Repeat operation!
Reconnect Power/Cable!
если выбираю в настройках BROM, то телефон не видится вообще.
Зажимал во всех вариантах боковые кнопки при подключении кабеля. Не помогло. Менял драйвера.Не помогло. Что еще можно предпринять?
-
#2
А
купить чтобы получить доступ к скрытому контенту.
пробовал ? < ссылка
-
#3
Здравствуйте. Не получается соединиться с CM2MT2 ver.2.28
Получаю ошибку Fail to init protocol!Mode : FLASH
1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
2. Insert USB cable in phone
Waiting for device connection …PTFN : MediaTek PreLoader USB VCOM_V1632 (Android) (COM6)
MODE : PRELOADER PORT
PORT : 6
Waiting BOOT ack …
PRELOADER : ACK confirmed!
BROM : Init BROMError : Fail to init protocol!
>>> Remove battery, cable. Check cable/connection/driver! Check SW hint! Repeat operation!Reconnect Power/Cable!
если выбираю в настройках BROM, то телефон не видится вообще.
Зажимал во всех вариантах боковые кнопки при подключении кабеля. Не помогло. Менял драйвера.Не помогло. Что еще можно предпринять?
Подключать только через тест пойнт
-
#4
Спасибо за подсказку, все получилось.К сожалению, справился флештул, а не инфинити.
 03-16-2019, 06:42 |
#1 (permalink) |
|
ali-f16 Freak Poster
Join Date: Oct 2012 Location: IRAN.IR —-عل
Posts: 262 Thanks Meter: 110 |
Error : Fail to init protocol! Card found : 73FD734E , v0137 Load IDBase v123080 Ok! Operation : Identify [ v2.05 ]
1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
PTFN : MediaTek PreLoader USB VCOM Port (COM3)
Error : Fail to init protocol! Reconnect Power/Cable! Operation : Identify [ v2.05 ]
1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
PTFN : MediaTek PreLoader USB VCOM Port (COM3)
BROM : 0x00002001 : DA SEND ERROR!
Error : Fail to init protocol! Reconnect Power/Cable! Operation : Identify [ v2.05 ]
1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
PTFN : MediaTek PreLoader USB VCOM Port (COM3)
BROM : 0x00002001 : DA SEND ERROR!
Error : Fail to init protocol! Reconnect Power/Cable! Operation : Identify [ v2.05 ]
1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
PTFN : MediaTek PreLoader USB VCOM Port (COM3)
BROM : 0x00002001 : DA SEND ERROR!
Error : Fail to init protocol! Reconnect Power/Cable! Operation : Identify [ v2.05 ]
1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
PTFN : MediaTek PreLoader USB VCOM Port (COM3)
BROM : 0x00002001 : DA SEND ERROR!
Error : Fail to init protocol! Reconnect Power/Cable! |
|
|
 |
| 03-16-2019, 06:55 |
#2 (permalink) |
|
ali-f16 Freak Poster
Join Date: Oct 2012 Location: IRAN.IR —-عل
Posts: 262 Thanks Meter: 110 |
Curent Platform: MT6580 |
|
|
|
| 03-16-2019, 09:51 |
#3 (permalink) |
|
princesaddam No Life Poster
Join Date: Apr 2009 Location: Inside Infinity
Posts: 1,677 Sonork: using fb Thanks Meter: 721 |
Quote:
Originally Posted by ali-f16 Card found : 73FD734E , v0137 Load IDBase v123080 Ok! Operation : Identify [ v2.05 ]
1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
PTFN : MediaTek PreLoader USB VCOM Port (COM3)
Error : Fail to init protocol! Reconnect Power/Cable! Operation : Identify [ v2.05 ]
1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
PTFN : MediaTek PreLoader USB VCOM Port (COM3)
BROM : 0x00002001 : DA SEND ERROR!
Error : Fail to init protocol! Reconnect Power/Cable! Operation : Identify [ v2.05 ]
1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
PTFN : MediaTek PreLoader USB VCOM Port (COM3)
BROM : 0x00002001 : DA SEND ERROR!
Error : Fail to init protocol! Reconnect Power/Cable! Operation : Identify [ v2.05 ]
1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
PTFN : MediaTek PreLoader USB VCOM Port (COM3)
BROM : 0x00002001 : DA SEND ERROR!
Error : Fail to init protocol! Reconnect Power/Cable! Operation : Identify [ v2.05 ]
1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
PTFN : MediaTek PreLoader USB VCOM Port (COM3)
BROM : 0x00002001 : DA SEND ERROR!
Error : Fail to init protocol! Reconnect Power/Cable! Hello, |
|
|
|
|
The Following User Says Thank You to princesaddam For This Useful Post: |
| 03-16-2019, 18:35 |
#4 (permalink) |
|
ali-f16 Freak Poster
Join Date: Oct 2012 Location: IRAN.IR —-عل
Posts: 262 Thanks Meter: 110 |
Card found : 73FD734E , v0137 Load IDBase v123080 Ok!
Update configuration … Operation : Identify [ v2.05 ]
1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
PTFN : MediaTek PreLoader USB VCOM (Android) (COM3)
Error : Fail to init protocol! Reconnect Power/Cable! Operation : Identify [ v2.05 ]
1. Make sure device is powered off. Power off, if need. Wait 20 seconds after |
|
|
|
| 03-16-2019, 19:45 |
#5 (permalink) |
|
imranidrisi Freak Poster
Join Date: Dec 2010
Posts: 160 Thanks Meter: 88 |
Quote:
Originally Posted by ali-f16 Card found : 73FD734E , v0137 Load IDBase v123080 Ok!
Update configuration … Operation : Identify [ v2.05 ]
1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
PTFN : MediaTek PreLoader USB VCOM (Android) (COM3)
Error : Fail to init protocol! Reconnect Power/Cable! Operation : Identify [ v2.05 ]
1. Make sure device is powered off. Power off, if need. Wait 20 seconds after dear sir read your sw log carefully connect handset in boot rom mode (press both volume keys) then insert usb cable |
|
|
|
|
The Following User Says Thank You to imranidrisi For This Useful Post: |
| 03-16-2019, 22:13 |
#6 (permalink) |
|
nessyb No Life Poster
Join Date: Jan 2013 Location: zimbabwe south africa
Posts: 1,441 Sonork: 100.1681933 Thanks Meter: 707 |
Quote:
Originally Posted by ali-f16 Curent Platform: MT6580 its useless to compare boot info from different modes posted logs are meta while you try working in flash mode in cm2 |
|
|
|
|
The Following User Says Thank You to nessyb For This Useful Post: |
| 03-19-2019, 07:08 |
#7 (permalink) |
|
ali-f16 Freak Poster
Join Date: Oct 2012 Location: IRAN.IR —-عل
Posts: 262 Thanks Meter: 110 |
Operation : Identify [ v2.05 ]
1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
PTFN : MediaTek PreLoader USB VCOM (Android) (COM3)
BROM : 0x00000002 : DA SEND ERROR!
Error : Fail to init protocol! Reconnect Power/Cable! |
|
|
|
| 03-25-2019, 09:02 |
#8 (permalink) |
|
ali-f16 Freak Poster
Join Date: Oct 2012 Location: IRAN.IR —-عل
Posts: 262 Thanks Meter: 110 |
Operation : Format FileSystem [ v1.58 ]
1. Power Off Phone , Remove battery , Insert back
Wait for phone…
[DA_ERROR] : SECURITYBOOT_BOOT_NOT_ACCEPTED
Operation Failed |
|
|
|
| 03-25-2019, 13:37 |
#9 (permalink) |
|
ali-f16 Freak Poster
Join Date: Oct 2012 Location: IRAN.IR —-عل
Posts: 262 Thanks Meter: 110 |
ooooooooooooooooooookkkkkkkkkkkkkkkkkkkkkkk Thanks Operation : Check / Read Info [ v1.58 ]
1. Power Off Phone , Remove battery , Insert back
Wait for phone… [AP] : Initial info read Ok!
Brand : SMART
SECURITY :
Done! |
|
|
|
| 02-26-2020, 00:31 |
#10 (permalink) |
|
Auwal4720 Junior Member Join Date: Feb 2018
Posts: 10 Thanks Meter: 0 |
My cm2mt2 is show me error-fail-init-protocol when I opened pls sir |
|
|
|
| 02-26-2020, 09:20 |
#11 (permalink) |
|
PASSIONATE_BOYS No Life Poster
Join Date: Jul 2007 Location: Infinity-Box Support-
Posts: 9,307 Sonork: 100.1611509 Thanks Meter: 7,352 |
Quote:
Originally Posted by Auwal4720 My cm2mt2 is show me error-fail-init-protocol when I opened pls sir Hello,
Br. |
|
|
|
| 03-01-2020, 14:04 |
#12 (permalink) |
|
nadar Crazy Poster
Join Date: Mar 2014
Posts: 58 Sonork: nawaz Thanks Meter: 4 |
qmobile lt950 Infinity-Box [ Chinese Miracle ] MediaTek Service Module [ MTK ] v2.08 Load IDBase v124106 Ok! Operation : Identify [ v2.08 ]
1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
PTFN : MediaTek PreLoader USB VCOM (Android) (COM8)
BROM : 0x00007024 : DA SEND ERROR!
Error : Fail to init protocol! Reconnect Power/Cable! Operation : Identify [ v2.08 ]
1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
PTFN : MediaTek USB Port (COM5)
DA : BOOT 2ND DA FAILED!
Error : Fail to init protocol! Reconnect Power/Cable! Operation : Identify [ v2.08 ]
1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
PTFN : MediaTek USB Port (COM5)
DA : BOOT 2ND DA FAILED!
Error : Fail to init protocol! Reconnect Power/Cable! Operation : Identify [ v2.08 ]
1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
PTFN : MediaTek PreLoader USB VCOM (Android) (COM8)
BROM : 0x00007024 : DA SEND ERROR!
Error : Fail to init protocol! Reconnect Power/Cable! Operation : Identify [ v2.08 ]
1. Make sure device is powered off. Power off, if need. Wait 20 seconds after
PTFN : MediaTek PreLoader USB VCOM (Android) (COM8)
BROM : 0x00007024 : DA SEND ERROR!
Error : Fail to init protocol! Reconnect Power/Cable! |
|
|
|
| 03-08-2020, 15:59 |
#13 (permalink) |
|
Auwal4720 Junior Member Join Date: Feb 2018
Posts: 10 Thanks Meter: 0 |
Please I need yr help consigning my cm2mt2 is not WK |
|
|
|
| 07-24-2020, 12:31 |
#14 (permalink) |
|
bijoychowdry No Life Poster
Join Date: Jul 2013 Location: gsm forum
Posts: 558 Sonork: 119.30.39.25 Thanks Meter: 75 |
nokia 5.1
PTFN : MediaTek USB Port (COM23) DA : POWER_SOURCE set FAILED! 0xC0010002
Error : Fail to init protocol! Reconnect Power/Cable! |
|
|
|
| 09-01-2020, 12:30 |
#15 (permalink) |
|
rajamtkmaster Freak Poster
Join Date: Sep 2016 Location: Rawalpindi
Posts: 302 Sonork: 100.1582347 Thanks Meter: 85 |
Hi sir,
Card found : 0906506F , v0122 Operation : Identify [ v1.20 ]
1. Make sure device is powered off. Power off, if need. Wait 10 seconds after
PTFN : Nokia USB Serial Port (COM13)
Error : Fail to init protocol! Reconnect Power/Cable! Operation : Identify [ v1.20 ]
1. Make sure device is powered off. Power off, if need. Wait 10 seconds after
PTFN : Nokia USB Serial Port (COM13)
Error : Fail to init protocol! Reconnect Power/Cable! Operation : Identify [ v1.20 ]
1. Make sure device is powered off. Power off, if need. Wait 10 seconds after
Device not found ! Reconnect Power/Cable! Operation : Identify [ v1.20 ]
1. Make sure device is powered off. Power off, if need. Wait 10 seconds after
Device not found ! Reconnect Power/Cable! Operation : Identify [ v1.20 ]
1. Make sure device is powered off. Power off, if need. Wait 10 seconds after
PTFN : Nokia USB Serial Port (COM13)
Error : Fail to init protocol! Reconnect Power/Cable! Operation : Identify [ v1.20 ]
1. Make sure device is powered off. Power off, if need. Wait 10 seconds after
PTFN : Nokia USB Serial Port (COM13)
Error : Fail to init protocol! Reconnect Power/Cable! Operation : Identify [ v1.20 ]
1. Make sure device is powered off. Power off, if need. Wait 10 seconds after
PTFN : Nokia USB Serial Port (COM13)
Error : Fail to init protocol! Reconnect Power/Cable! Operation : Identify [ v1.20 ]
1. Make sure device is powered off. Power off, if need. Wait 10 seconds after
PTFN : Nokia USB Serial Port (COM13)
Error : Fail to init protocol! Reconnect Power/Cable!
Thanks |
|
|
|
|
The Following User Says Thank You to rajamtkmaster For This Useful Post: |
Просмотр полной версии : Xiaomi 2016101 Redmi Note 4x нормально не коннектица с QLM
Доброе время суток!
Тел с блокировкой аккаунта, проц Snapdragon 625
Подскажите плиз как подцепить тел к QLM 1.16, после замыкания ТП переходит в emergency care, прога его видит, но пишет
Operation : Reset Settings [ v1.16 ]
1. Power Off Phone , Remove battery , Insert back
2. PRESS and HOLD BOTH VOLUME KEYS!
3. Insert USB cable. In some cases require use EDL cable or TP to force EDL mode!
Wait for phone…
Device Found!
Initialize …
ERROR : Fail to init protocol!
HINT : Check cable, connection and drivers!
Reconnect Power/Cable!
Если порубать дрова и поставить Qualcomm HS-USB Qdloader 9008, то не видит совсем…
Что за трабла?
p.s. BST его не видит не в каком из режимов кроме фастбут
mobilrepair
07.02.2018, 00:54
а на какой системе ?
выбрать дрова nokia care дык драйвера из папки QLM, файл EmergencyDownloadDriver , определяется как Care Suite Emergency Connectivity!? Пару дней назад был Nokia 5, все виделось…
а на какой системе ?
W7 64
Сорри, сори, разобрался, я не правильно работал с ТП, надо нажать коннект в проге, замкнуть ТП и вставить кабель…
BST его прекрасно видит просто нужно в фастбуте его просканировать зажать тп и кликнуть ребут edl.
дык драйвера из папки QLM, файл EmergencyDownloadDriver , определяется как Care Suite Emergency Connectivity!? Пару дней назад был Nokia 5, все виделось…
W7 64
Сорри, сори, разобрался, я не правильно работал с ТП, надо нажать коннект в проге, замкнуть ТП и вставить кабель…
Принудительнео установи и будет счастье, где стоят Qualcomm HS-USB Qdloader 9008 драйвера, он автоматом не станет.
BST его прекрасно видит просто нужно в фастбуте его просканировать зажать тп и кликнуть ребут edl.
Спасибо! След. раз надо будет проверить (уже лень открывать крышку)…
Принудительнео установи и будет счастье, где стоят Qualcomm HS-USB Qdloader 9008 драйвера, он автоматом не станет.
У меня ставятся автоматом…
-
#1
comio c1 imei not rebuiled sussecs show errorr PTFN : Micromax A110 PreLoader USB VCOM Port (COM84)
MODE : BOOTROM
PORT : 84
Waiting BOOT ack …
BROM : Skip ACK verify
BROM : Init BROM
BROM init passed!
CHIP : MT6735 , SBID : 0x8A00 , HWVR : 0xCA00 , SWVR : 0x0000
TYPE : LEGACY MTK
BROM : SecLevel : 0x00000001
BROM : SecMode : SBC
BROM : BOOTROM
MODE : 0_base : BASE_v1712 | Manual : Enabled
Fail to disable Dog!
AGENT : Look for suitable BootChain in DA …
AGENT : Comio DA C1 By GD_Mekail92.bin
AGENT : Found MT6735
AGENT : MTK_DOWNLOAD_AGENT
BROM : Sending 1st DA …
BROM : DA sent
BROM :Transfer control to DA …
DA : AGENT started!
NAND : DEVICE NOT FOUND
eMMC : OK
eMMC : 4501004446343033320138715B3CCF31
DAInf: 4 : 2 : 155
DA : EXT_RAM NOT initialized!
eMMC : OK
eMMC : 44000145333034467138013231CF3C5B
NAND : DEVICE NOT FOUND
NAND : 000000000000000000000000
EMI : DEV : INFINITY
EMI : SRC : INFINITY-BOX_INTERNAL_EMIDB_v0
DA : EMI : Failed to get EMI info from selected source!
DA : Failed to configure DA!
Error : Fail to init protocol!
Remove battery, cable. Check cable/connection/driver! Check SW hint! Repeat operation!
Reconnect Power/Cable!
-
#3
I try attche da but not succes
-
#4
I try attche da but not succes
Use Da + preloader
or else simply follw the thread vit out cm2
Sent from my Redmi Note 5 using Tapatalk
-
#5
use da + preloader
or else simply follw the thread vit out cm2
sent from my redmi note 5 using tapatalk
bro. I try mt2 but not selcet preloader
-
#6
use da + preloader
or else simply follw the thread vit out cm2
sent from my redmi note 5 using tapatalk
bro. I try mt2 but not selcet preloader
PTFN : PreLoader USB VCOM Port (COM85)
MODE : PRELOADER PORT
PORT : 85
Waiting BOOT ack …
PRELOADER : ACK confirm FAIL!
BROM : Init BROM
BROM init passed!
CHIP : MT6735 , SBID : 0x8A00 , HWVR : 0xCA00 , SWVR : 0x0000
TYPE : LEGACY MTK
BROM : SecLevel : 0x00000001
BROM : SecMode : SBC
BROM : PRELOADER PORT
MODE : 0_base : BASE_v1712 | Manual : Enabled
AGENT : Look for suitable BootChain in DA …
AGENT : MTK_AllInOne_DA.bin
AGENT : Found MT6735
AGENT : MTK_DOWNLOAD_AGENT
BROM : Sending 1st DA …
BROM : DA sent
BROM : JUMP TO DA FAILED!
Error : Fail to init protocol!
Remove battery, cable. Check cable/connection/driver! Check SW hint! Repeat operation!
Reconnect Power/Cable!
The reason I’ve done this is because partition names are not consistent between devices, in fact they’re totally arbitrary even when using different PIT files on the same device. There’s really nothing stopping ROM developers (or Samsung) from creating new PIT files and naming partitions however they please.
This might be a bit long-winded, but I’ll try explain why this is a problem…
Heimdall needs to know partition names in order to determine which files should be flashed to which partition on the device. In fact Heimdall actually needs uses the partition IDs. But the partition ID can be grabbed by looking up a partition name in a PIT file. The partition ID is what is sent to the phone when flashing.
When I first started developing Heimdall it only supported one device, the GT-I9000. As such I hard-coded the partition names to match arguments. Here’s the official mapping as supported by Heimdall 1.4 RC1:
argumentPartitionNamesMap["pit"].push_back("PIT");
argumentPartitionNamesMap["factoryfs"].push_back("FACTORYFS");
argumentPartitionNamesMap["cache"].push_back("CACHE");
argumentPartitionNamesMap["dbdata"].push_back("DBDATAFS");
argumentPartitionNamesMap["primary-boot"].push_back("IBL+PBL");
argumentPartitionNamesMap["primary-boot"].push_back("BOOT");
argumentPartitionNamesMap["secondary-boot"].push_back("SBL");
argumentPartitionNamesMap["secondary-boot"].push_back("SBL1");
argumentPartitionNamesMap["secondary-boot-backup"].push_back("SBL2");
argumentPartitionNamesMap["param"].push_back("PARAM");
argumentPartitionNamesMap["kernel"].push_back("KERNEL");
argumentPartitionNamesMap["recovery"].push_back("RECOVERY");
argumentPartitionNamesMap["efs"].push_back("EFS");
argumentPartitionNamesMap["modem"].push_back("MODEM");
argumentPartitionNamesMap["radio"].push_back("RADIO");
argumentPartitionNamesMap["normal-boot"].push_back("NORMALBOOT");
argumentPartitionNamesMap["system"].push_back("SYSTEM");
argumentPartitionNamesMap["user-data"].push_back("USERDATA");
argumentPartitionNamesMap["fota"].push_back("FOTA");
argumentPartitionNamesMap["hidden"].push_back("HIDDEN");
argumentPartitionNamesMap["movinand"].push_back("MOVINAND");
argumentPartitionNamesMap["data"].push_back("DATAFS");
argumentPartitionNamesMap["ums"].push_back("UMS.EN");
argumentPartitionNamesMap["emmc"].push_back("GANG");
As you can see that list is already a bit ridiculous, and some parameters like —primary-boot can correspond with multiple partition names eg. «IBL+PBL» or «BOOT».
Potentially I could keep updating this list every time someone encounters a new partition name. But between the time someone encounters the new partition and the time it takes me to update Heimdall, users would be stuck, and totally unable to flash.
However, I already solved this problem with the introduction of partition ID based flashing (in Heimdall 1.3?) through numbered arguments. This allows Heimdall to flash partitions that aren’t in the list of known hard-coded partition names (shown above). Theoretically this allows Heimdall to flash any device that uses PIT files.
This is actually how the Heimdall Firmware Package format works, through use of partition IDs. Although I’m considering migrating it to use partition names instead.
The new partition name arguments are just an extension of this system, instead of using the partition ID, you specify the exact partition name and Heimdall looks it up in the PIT file for you.
In fact as of v1.3, Heimdall Frontend was already using partition names. If you load up your devices PIT file in Heimdall Frontend you see the complete list of partitions on the device using their actual partition names (much like print pit).
Basically what I’m saying is that the —kernel, —secondary-boot etc. way of flashing has reached its limits and is no longer useful. This is particularly true when you look at the Qualcomm phones in US. Unfortunately they don’t match the —primary-boot, —secondary-boot model at all. If I recall correctly, there are 6 different files that are required to perform roughly the same task as just boot.bin and Sbl.bin on Exynos devices. They also have two different modem partitions one called MODEM, and one called MDM. Rather than trying to define and maintain separate arguments for all these different partitions its much easier just to allow users to flash using partition names directly.
HOWEVER, I am considering adding the following command:
heimdall autoflash [--pit <filename>] --files <filename[, filename, ...]>
For example, your flash would have looked like:
heimdall autoflash --files system.img cache.img modem.bin boot.img bootloader.bin hidden.img recovery.img
What autoflash would do, is what I just did for you manually. Which is map filenames to particular partitions.
However, this autoflash method would give up one of the most significant advantages of Heimdall, which is that you can name your files however you please. For autoflash to work, you’d have to name your files precisely how they appear in the PIT file, but this is how Odin works anyway so it’s not too big of an issue. The other downside is of course that autoflash would be limited to flashing partitions that actually have a filename. If you look at the output of your print-pit command you’ll see some partitions don’t have filenames. Odin is not capable of flashing these partitions, but Heimdall is.
No protocol specified — Unable to init server: Could not connect: Connection refused
Let us see how to fix this No protocol specified error on fedora 29 and open virt-manager successfully in this page,
[username@localhost ~]$ sudo -i [root@localhost ~]# virt-manager
virt-manager is not opened and got below errors in console,
[root@localhost ~]# No protocol specified Unable to init server: Could not connect: Connection refused No protocol specified Unable to init server: Could not connect: Connection refused No protocol specified Unable to init server: Could not connect: Connection refused (virt-manager:2994): Gtk-WARNING **: 14:11:33.277: cannot open display: :0 ^C
Please try xhost commnd,
[root@localhost ~]# xhost +local: No protocol specified xhost: unable to open display ':0'
Not worked as root user,
[root@localhost ~]# exit logout
Exit root user mode and tried in normal loggedin user
[username@localhost ~]$ xhost +local: non-network local connections being added to access control list
Now try to open virt-manager,
[username@localhost ~]$ virt-manager
Now virt-manager is opened but not connected to create instance. so trying with sudo acces
[username@localhost ~]$ sudo virt-manager
Now opened virt-manager in connected mode and could able to create instances.
« Previous
Next »
- Печать
Страницы: [1] Вниз
Тема: Novatel mc551 и kubuntu 12.04.5/14.04.1 (Прочитано 979 раз)
0 Пользователей и 1 Гость просматривают эту тему.
Spidey
Намаялся я с этим модемом… в Kubuntu чистой на стандартном ядре 3.2.0.67 все замечательно запускается, определяется, интернет идет, а вот на 14.04.1 соединение моментально обрывается…. перепробовал кучу вариантов с этого форума и никаких результатов 
Пользователь решил продолжить мысль 22 Ноября 2014, 19:23:23:
Дополню вопрос….
Интернет Intertelecom, в 12.04 была архитектура х86. а 14.04 х64, может в этом быть подвох?
« Последнее редактирование: 22 Ноября 2014, 19:23:23 от Spidey »
chemtech
Spidey
Bus 003 Device 005: ID 1410:b001 Novatel Wireless Ovation MC551так же было и в 12.04, но работало 
upd. Обновил ядро до 3.17.3, все равно не пашет
Так же пробовал добавлять айди модема в 40-usb_modeswitch но не помогло 
« Последнее редактирование: 22 Ноября 2014, 19:43:12 от Spidey »
chemtech
Spidey,
Покажите
cat /var/log/syslog | egrep -i "(error|fail|warning)"
Spidey
chemtech
Spidey,
Возможно регрессия.
Хотите зарегистрировать ошибку?
Spidey
В смысле зарегистрировать???
Кстати, ранее на 14.04 через wvdial удавалось запустить, но я никак не могу найти настройки с какими это у меня получалось…
chemtech
Spidey
Эх, не особо люблю иностранные сайты… а что даст регистрация регрессии?
chemtech
Spidey,
Показать ошибку разработчикам. Может советы дадут какие-либо
Spidey
Плюнул на все, решил перейти на Elementary OS Luna, там у меня все работает, да и в отличии от KDE шустрее, ибо DE проще
Пользователь решил продолжить мысль 23 Ноября 2014, 16:37:27:
Прям беда какая-то 
в 12.04 звук не заводится 
« Последнее редактирование: 23 Ноября 2014, 16:37:27 от Spidey »
Spidey
Решение проблемы пришло неожиданно от LMDE Mate — модем завелся сразу и без каких-либо танцев с бубном!
- Печать
Страницы: [1] Вверх