This is a part of the message I received. I don't know what is wrong.
Can any of you let me know what was wrong, or at least how to find out what was wrong?

(I showed here part of my output of dmesg)

Freeing unused kernel memory: 392k freed
intel_rng: FWH not detected
kobject_add failed for uhci_hcd with -EEXIST, don't try to register things with the same name in the same directory.
[<c03e86f7>] kobject_shadow_add+0x117/0x1a0
[<c013fba4>] mod_sysfs_setup+0x24/0xb0
[<c0141458>] sys_init_module+0x1648/0x1940
[<c0102ae8>] syscall_call+0x7/0xb
[<c0710000>] __mutex_lock_slowpath+0x40/0x90
=======================
iTCO_vendor_support: vendor-support=0
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.01 (21-Jan-2007)
iTCO_wdt: Found a ICH6-M TCO device (Version=2, TCOBASE=0x1060)
iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
kobject_add failed for uhci_hcd with -EEXIST, don't try to register things with the same name in the same directory.
[<c03e86f7>] kobject_shadow_add+0x117/0x1a0
[<c013fba4>] mod_sysfs_setup+0x24/0xb0
[<c0141458>] sys_init_module+0x1648/0x1940
[<c0102ae8>] syscall_call+0x7/0xb
[<c0710000>] __mutex_lock_slowpath+0x40/0x90
=======================
kobject_add failed for uhci_hcd with -EEXIST, don't try to register things with the same name in the same directory.
[<c03e86f7>] kobject_shadow_add+0x117/0x1a0
[<c013fba4>] mod_sysfs_setup+0x24/0xb0
[<c0141458>] sys_init_module+0x1648/0x1940
[<c0102ae8>] syscall_call+0x7/0xb
[<c0710000>] __mutex_lock_slowpath+0x40/0x90
=======================
kobject_add failed for uhci_hcd with -EEXIST, don't try to register things with the same name in the same directory.
[<c03e86f7>] kobject_shadow_add+0x117/0x1a0
[<c013fba4>] mod_sysfs_setup+0x24/0xb0
[<c0141458>] sys_init_module+0x1648/0x1940
[<c0102ae8>] syscall_call+0x7/0xb
[<c0710000>] __mutex_lock_slowpath+0x40/0x90
=======================
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
kobject_add failed for ehci_hcd with -EEXIST, don't try to register things with the same name in the same directory.
[<c03e86f7>] kobject_shadow_add+0x117/0x1a0
[<c013fba4>] mod_sysfs_setup+0x24/0xb0
[<c0141458>] sys_init_module+0x1648/0x1940
[<c0102ae8>] syscall_call+0x7/0xb
=======================
i2c_core: exports duplicate symbol i2c_smbus_write_i2c_block_data (owned by kernel)
ACPI: PCI Interrupt 0000:00:1f.3[B] -> GSI 19 (level, low) -> IRQ 22
ACPI: PCI Interrupt 0000:00:1e.2[A] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:00:1e.2 to 64
Linux agpgart interface v0.102 (c) Dave Jones

Trainee

I got the same "error", but I think it is a module that don't match or something, but the system seems to be ok, don't?

Only for your happiness, you are not the only one with this issue!

I hope to resolve this soon, or at least find out the problem..

Bye.

Janux

Thank you. It is good to know. The system seems to get going find. It just that I was curious and want to find out more about the system.

Have a look at Changes_and_Hints.txt:

"As stated earlier, it is recommended that you use one of the generic kernels
rather than the huge kernels; the huge kernel is primarily intended as
an "installer" and "emergency" kernel in case you forget to make an initrd.
However, if you do use one of the huge kernels, you will likely encounter
errors like this:
kobject_add failed for uhci_hcd with -EEXIST, don't try to register
These occur because the respective drivers are compiled statically into the
huge kernels but udev tries to load them anyway. These errors should be safe
to ignore, but if you really don't want them to appear, you can blacklist the
modules that try to load in /etc/modprobe.d/blacklist. However, make sure you
remove them from the blacklist if you ever decide to use the (recommended)
generic kernels." "

So if you install generic kernel instead of huge, the error should be gone.

Thank you.

Yes, there is a reason that the Release Notes and other documentation are placed on the cd images... :-)