Displaying 3 results from an estimated 3 matches for "tpm_atmel".
2016 Jul 21
3
Re: How to debug supermin5 issue?
...kernel/drivers/char/hw_random/amd-rng.ko:
kernel/drivers/char/hw_random/via-rng.ko:
kernel/drivers/char/hw_random/virtio-rng.ko: kernel/drivers/virtio/virtio_ring.ko kernel/drivers/virtio/virtio.ko
kernel/drivers/char/hw_random/tpm-rng.ko:
kernel/drivers/char/tpm/tpm_nsc.ko:
kernel/drivers/char/tpm/tpm_atmel.ko:
kernel/drivers/char/tpm/tpm_infineon.ko:
kernel/drivers/char/virtio_console.ko: kernel/drivers/virtio/virtio_ring.ko kernel/drivers/virtio/virtio.ko
...
which existed on the machine works fine.
It works fine now.
But why we make initrd only depends on modules.dep?
Regards,
- Chen
2016 Jul 21
0
Re: How to debug supermin5 issue?
...ndom/amd-rng.ko:
> kernel/drivers/char/hw_random/via-rng.ko:
> kernel/drivers/char/hw_random/virtio-rng.ko: kernel/drivers/virtio/virtio_ring.ko kernel/drivers/virtio/virtio.ko
> kernel/drivers/char/hw_random/tpm-rng.ko:
> kernel/drivers/char/tpm/tpm_nsc.ko:
> kernel/drivers/char/tpm/tpm_atmel.ko:
> kernel/drivers/char/tpm/tpm_infineon.ko:
> kernel/drivers/char/virtio_console.ko: kernel/drivers/virtio/virtio_ring.ko kernel/drivers/virtio/virtio.ko
> ...
>
> which existed on the machine works fine.
>
> It works fine now.
>
> But why we make initrd only depend...
2016 Jul 21
4
Re: How to debug supermin5 issue?
At 2016-07-21 18:43:04, "Richard W.M. Jones" <rjones@redhat.com> wrote:
>On Thu, Jul 21, 2016 at 06:36:20PM +0800, Chen Hanxiao wrote:
>> the virtio modules in kmods did existed in this machine.
>> with -v -v -v, I got:
>
>Can you attach or pastebin the complete output from this command on
>the failing machine please:
>
>supermin5 --build -f ext2 -v -v