红联Linux门户
Linux帮助

I8042.c: No controller found

发布时间:2009-08-05 19:03:48来源:红联作者:qinzan2009
I8042.c: No controller found
是什么原因造成的?!!!
文章评论

共有 14 条评论

  1. qinzan2009 于 2009-08-10 19:19:44发表:

    好象还没有回答我的问题哟?!

  2. 文义德 于 2009-08-06 21:02:29发表:

    原来如此

  3. 微宝贝 于 2009-08-06 20:24:23发表:

    [zhh@localhost /]$ sudo more /boot/grub/menu.lst
    [sudo] password for zhh:
    # grub.conf generated by anaconda
    #
    # Note that you do not have to rerun grub after making changes to this file
    # NOTICE: You have a /boot partition. This means that
    # all kernel and initrd paths are relative to /boot/, eg.
    # root (hd0,8)
    # kernel /vmlinuz-version ro root=/dev/sda10
    # initrd /initrd-version.img
    #boot=/dev/sda
    default=0
    timeout=5
    splashimage=(hd0,8)/grub/splash.xpm.gz
    #hiddenmenu
    title Fedora (2.6.29.5-191.fc11.x86_64)
    root (hd0,8)
    kernel /vmlinuz-2.6.29.5-191.fc11.x86_64 ro root=UUID=e2e0a848-b259-47ea
    -bfd9-ffaa1a8d9fff quiet
    initrd /initrd-2.6.29.5-191.fc11.x86_64.img
    title Fedora (2.6.29.4-167.fc11.x86_64)
    root (hd0,8)
    kernel /vmlinuz-2.6.29.4-167.fc11.x86_64 ro root=UUID=e2e0a848-b259-47ea
    -bfd9-ffaa1a8d9fff quiet
    initrd /initrd-2.6.29.4-167.fc11.x86_64.img
    title windows
    rootnoverify (hd0,0)
    chainloader +1
    [zhh@localhost /]$ ls /vm*
    ls: 无法访问 /vm*: 没有那个文件或目录
    [zhh@localhost /]$ ls /vm
    ls: 无法访问 /vm: 没有那个文件或目录
    [zhh@localhost /]$ ls /
    bin dev home lib64 media opt root selinux sys usr
    boot etc lib lost+found mnt proc sbin srv tmp var
    [zhh@localhost /]$ ls -al /
    总计 110
    drwxr-xr-x. 23 root root 4096 08-06 20:19 .
    drwxr-xr-x. 23 root root 4096 08-06 20:19 ..
    -rw-r--r--. 1 root root 0 08-06 20:19 .autofsck
    drwxr-xr-x. 2 root root 4096 07-10 20:28 bin
    drwxr-xr-x. 5 root root 1024 06-26 14:08 boot
    drwx------. 3 root root 4096 06-20 20:09 .dbus
    drwxr-xr-x. 17 root root 4040 08-06 20:19 dev
    drwxr-xr-x. 120 root root 12288 08-06 20:19 etc
    drwxr-xr-x. 4 root root 4096 06-21 19:17 home
    drwxr-xr-x. 11 root root 4096 06-20 21:38 lib
    drwxr-xr-x. 8 root root 12288 07-10 20:28 lib64
    drwx------. 2 root root 16384 06-20 19:40 lost+found
    drwxr-xr-x. 2 root root 4096 07-21 20:12 media
    drwxr-xr-x. 5 root root 4096 07-13 18:50 mnt
    drwxr-xr-x. 2 root root 4096 03-04 21:13 opt
    dr-xr-xr-x. 141 root root 0 2009-08-07 proc
    drwxr-x---. 23 root root 4096 07-12 19:53 root
    drwxr-xr-x. 2 root root 12288 07-10 20:29 sbin
    drwxr-xr-x. 7 root root 0 2009-08-07 selinux
    drwxr-xr-x. 2 root root 4096 03-04 21:13 srv
    drwxr-xr-x. 12 root root 0 2009-08-07 sys
    drwxrwxrwt. 30 root root 4096 08-06 20:19 tmp
    drwxr-xr-x. 14 root root 4096 06-20 19:48 usr
    drwxr-xr-x. 21 root root 4096 06-20 20:07 var

  4. 微宝贝 于 2009-08-06 20:24:12发表:

    [zhh@localhost /]$ sudo more /boot/grub/menu.lst
    [sudo] password for zhh:
    # grub.conf generated by anaconda
    #
    # Note that you do not have to rerun grub after making changes to this file
    # NOTICE: You have a /boot partition. This means that
    # all kernel and initrd paths are relative to /boot/, eg.
    # root (hd0,8)
    # kernel /vmlinuz-version ro root=/dev/sda10
    # initrd /initrd-version.img
    #boot=/dev/sda
    default=0
    timeout=5
    splashimage=(hd0,8)/grub/splash.xpm.gz
    #hiddenmenu
    title Fedora (2.6.29.5-191.fc11.x86_64)
    root (hd0,8)
    kernel /vmlinuz-2.6.29.5-191.fc11.x86_64 ro root=UUID=e2e0a848-b259-47ea
    -bfd9-ffaa1a8d9fff quiet
    initrd /initrd-2.6.29.5-191.fc11.x86_64.img
    title Fedora (2.6.29.4-167.fc11.x86_64)
    root (hd0,8)
    kernel /vmlinuz-2.6.29.4-167.fc11.x86_64 ro root=UUID=e2e0a848-b259-47ea
    -bfd9-ffaa1a8d9fff quiet
    initrd /initrd-2.6.29.4-167.fc11.x86_64.img
    title windows
    rootnoverify (hd0,0)
    chainloader +1
    [zhh@localhost /]$ ls /vm*
    ls: 无法访问 /vm*: 没有那个文件或目录
    [zhh@localhost /]$ ls /vm
    ls: 无法访问 /vm: 没有那个文件或目录
    [zhh@localhost /]$ ls /
    bin dev home lib64 media opt root selinux sys usr
    boot etc lib lost+found mnt proc sbin srv tmp var
    [zhh@localhost /]$ ls -al /
    总计 110
    drwxr-xr-x. 23 root root 4096 08-06 20:19 .
    drwxr-xr-x. 23 root root 4096 08-06 20:19 ..
    -rw-r--r--. 1 root root 0 08-06 20:19 .autofsck
    drwxr-xr-x. 2 root root 4096 07-10 20:28 bin
    drwxr-xr-x. 5 root root 1024 06-26 14:08 boot
    drwx------. 3 root root 4096 06-20 20:09 .dbus
    drwxr-xr-x. 17 root root 4040 08-06 20:19 dev
    drwxr-xr-x. 120 root root 12288 08-06 20:19 etc
    drwxr-xr-x. 4 root root 4096 06-21 19:17 home
    drwxr-xr-x. 11 root root 4096 06-20 21:38 lib
    drwxr-xr-x. 8 root root 12288 07-10 20:28 lib64
    drwx------. 2 root root 16384 06-20 19:40 lost+found
    drwxr-xr-x. 2 root root 4096 07-21 20:12 media
    drwxr-xr-x. 5 root root 4096 07-13 18:50 mnt
    drwxr-xr-x. 2 root root 4096 03-04 21:13 opt
    dr-xr-xr-x. 141 root root 0 2009-08-07 proc
    drwxr-x---. 23 root root 4096 07-12 19:53 root
    drwxr-xr-x. 2 root root 12288 07-10 20:29 sbin
    drwxr-xr-x. 7 root root 0 2009-08-07 selinux
    drwxr-xr-x. 2 root root 4096 03-04 21:13 srv
    drwxr-xr-x. 12 root root 0 2009-08-07 sys
    drwxrwxrwt. 30 root root 4096 08-06 20:19 tmp
    drwxr-xr-x. 14 root root 4096 06-20 19:48 usr
    drwxr-xr-x. 21 root root 4096 06-20 20:07 var

  5. 微宝贝 于 2009-08-06 20:17:13发表:

    其实内核基本都是在/boot,但是要是/boot是独立分区时会怎样呢?反正我一直是/boot独立。所以我观察的我的电脑启动时也参数也是以/ker.***为开始的。关键是/boot独立时,启动时候先执行root (hd0,x)所以/boot分区就是/了

  6. qinzan2009 于 2009-08-06 19:37:08发表:

    期待更多高人,指点迷津

  7. Lincoln_zeng 于 2009-08-06 16:52:35发表:

    我也想知道

  8. 文义德 于 2009-08-06 15:16:02发表:

    我倒想请教一下,rhel5的内核启动文件是在/下的?
    很多的 linux都是在/boot/下的

  9. qinzan2009 于 2009-08-06 11:49:56发表:

    引用:
    是RHEL5 ... 楼主这台是服务器吧,是不是没接键盘和鼠标? 如果是那很正常啊,系统检测说没有发现此类设备/控制器,不影响使用(远程控制即可,想本地用那就接上键鼠呗)
    hantu 发表于 2009-8-6 00:33
    是的,RHEL5.3 服务器的...它没有PS/2接口,但我的USB键盘鼠标一直接在机台上啊,,,而且安装过程都一直在用```各位大哥, 有什么办法解决吗?!谢谢

  10. hantu 于 2009-08-06 00:33:38发表:

    是RHEL5 ... 楼主这台是服务器吧,是不是没接键盘和鼠标? 如果是那很正常啊,系统检测说没有发现此类设备/控制器,不影响使用(远程控制即可,想本地用那就接上键鼠呗)

  11. wangyu 于 2009-08-05 22:44:50发表:

    引用:
    图中是启动系统还是安装系统?是centos5吧?
    感觉有点怪怪的,内核文件不是在/boot里的
    是在/里的?还是我孤陋寡闻?
    文义德 发表于 2009-8-5 20:40

    如果是内核文件找不到,可以修改menu.lst

  12. 文义德 于 2009-08-05 20:40:36发表:

    图中是启动系统还是安装系统?是centos5吧?
    感觉有点怪怪的,内核文件不是在/boot里的
    是在/里的?还是我孤陋寡闻?

  13. me26659408 于 2009-08-05 20:10:14发表:

    不知道哦。。。
    google下

  14. wangyu 于 2009-08-05 19:57:26发表:

    呵,没遇到过,你应该用百度搜下