- 博客介绍
易也博客是一个“合众博客”站点,所谓合众,是经过管理员批准的一众技术爱好者,在这个站点上用各自的账号发表博客。合众博客有别于传统的博客,一个人管理和统御站点的所有事务和内容——它的问题是,很少有人有这样旺盛的精力,把博客站点推向兴盛。
张佩是这个站点的首要管理员,所有新帐号都由他批准和建立。现在我们有四位作者,希望有越来越多的朋友参与。请主动找我。
在这个站点上发表文章,我们只有一个要求:技术干货!
- 作者们
- 张佩,1982年生人,工作以来,纯码农;技术不坏,文章称佳;历职NEC、Dextrys、AMD、Intel,现在Alibaba。
兴趣领域:熟悉内核、虚拟化、AI和IoT技术;对技术培训方向兴趣盎然。
欢迎网友来小站访问,也希望、喜欢和网友互动。你们可以给我留言,也可以给我发送邮件:zhang.xiaopei在outlook.com (’在’=’@’)
2. 罗冰,喜欢侦探小说、历史小说、漫画、足球….爱好太多,博而不精。误入编程领域,十数年未有明显建树,仍不改初衷,纯粹喜欢。现居南京,做嵌入式无线通讯相关产品。
个人简历:LinkedIn
十多年编程经历,前5年主要开发语言是x86汇编和C,开发各类OptionRom。后5年涉及一些驱动开发和App以及UEFI编程,从此更多的精力用在了团队和公司管理上。然不忘初心,仍不停于在各技术领域钻研,其乐无穷。
近一年开始,对物联网相关产业以及AI极有兴趣,立志并着手进行中。
有缘相识佩兄,邀我在此开博。诠才末学,不值方家一笑。希望和技术同好多多交流:luobing4365@163.com
21,851 total views, 3 views today
感谢张生对无数网友的奉献,工具相当好用,并且还是无私的奉献,谢谢你
张老师的帮助使我受益匪浅,多谢了
比某水大一年,呵呵!也很喜欢WINDOWS和VC编程,不过比较喜欢玩各种有趣的东西,所以很多并不专精 ^-^
水水颇有趣
博客极新颖
初看如乱码
细读乃文言
:)
谢谢,你上班好早啊=A=,难道也是属于爱早班类型^^?
感谢您为很多驱动开发者做出的贡献,向您学习!
CY001的板子为啥不卖了呢?
谢谢问起。板子没货了,打板对我而言是个负担。下半年起,很多人通过各种途径问CY001的情况,所以已决定再打一次板,再生产50片。12月下旬应可以看到。
谢谢,能开个预订么,我怕抢不到,^.^。能请教一下虚拟USB设备是如何实现的么?
Action requires knegwedlo, and now I can act!
一不小心发现了这个宝库,里面好多宝贝,怎么办,搬走了,别哭哈
无法完成签名,提示的是
XXX.inf is failed to be signed, refer to log file.
不过我也没有找到这个log文件在哪,大侠帮助一下小弟我否?
>>> [Device Install (DiInstallDevice) – ROOT\UNKNOWN000]
>>> Section start 2016/09/22 21:46:49.273
cmd: “C:\Windows\system32\mmc.exe” /s C:\Windows\system32\devmgmt.msc
dvi: {Plug and Play Service: Device Install for ROOT\UNKNOWN000}
ump: Creating Install Process: DrvInst.exe 21:46:49.278
! ndv: Installing NULL driver!
dvi: Set selected driver complete.
dvi: {DIF_ALLOW_INSTALL} 21:46:49.322
dvi: No class installer for ‘未知驱动程序软件程序包’
dvi: No CoInstallers found
dvi: Default installer: Enter 21:46:49.333
dvi: Default installer: Exit
dvi: {DIF_ALLOW_INSTALL – exit(0xe000020e)} 21:46:49.337
dvi: {DIF_INSTALLDEVICE} 21:46:49.339
dvi: No class installer for ‘未知驱动程序软件程序包’
dvi: Default installer: Enter 21:46:49.350
! dvi: Installing NULL driver!
! dvi: A NULL driver installation is not allowed for this type of device!
!!! dvi: Cleaning up failed installation (e0000219)
!!! dvi: Default installer: failed!
!!! dvi: Error 0xe0000219: The installation failed because a function driver was not specified for this device instance.
dvi: {DIF_INSTALLDEVICE – exit(0xe0000219)} 21:46:49.366
ump: Server install process exited with code 0xe0000219 21:46:49.377
ump: {Plug and Play Service: Device Install exit(e0000219)}
<<< Section end 2016/09/22 21:46:49.381
<<< [Exit status: FAILURE(0xe0000219)]
我是驱动初学者能不能帮我看看这是什么问题
这是因为找不到合适的驱动包。你的设备ID是ROOT\UNKNOWN000(奇怪),然后系统尝试寻找能应用的驱动时失败。
Probably caused by : ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!5801A4BE820000 )
Followup: MachineOwner
———
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffe1809a005f70, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffe1809a005ec8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
Debugging Details:
——————
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn’t have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing “.symopt- 100”. Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
请问张老师这个问题怎么解决,我没法往下继续了,怎么提示symbols是错误的呢
另外已将dmp文件上传,如有时间帮忙分析下吧,多谢了http://pan.baidu.com/s/1nvRPb3z
张老师 ,易听声卡您记得吗?现在厂商倒闭,可是声卡驱动要通过联网到服务器获取ID才能使用,我该怎么办呢?
经历,还是精力呢?
精力吧^^
你好 想问一下编译 edk2我遇到个问题 该怎么解决呢~网上实在找不到资料了~
build.py…
c:\users\12\uefiworkspace\edk2-libc\AppPkg\AppPkg.dsc(…): error 4000: Instance of library class [RegisterFilterLib] is not found
in [c:\users\12\uefiworkspace\edk2\MdePkg\Library\BaseLib\BaseLib.inf] [IA32]
consumed by module [c:\users\12\uefiworkspace\edk2-libc\AppPkg\Applications\Hello\Hello.inf]
看起来是编译环境没有搭建好,其他UEFI APP能编译通过吗?
您那边有解决不?我也遇到了这个问题。并且编译其他uefi模块都正常,不知是哪个配置文件还是环境配置的有问题?