Comment 18 for bug 82921

Since Kyle mentionned the problem might be related to kernel modules, here is the difference between the lsmod on an installed system and the lsmod on a system after booting from the installation media:

3c3
< af_packet 23816 2
---
> af_packet 23816 6
7c7
< ata_piix 16132 3
---
> ata_piix 16132 1
26c26
< ext3 133128 2
---
> ext3 133128 0
30c30,31
< freq_table 5792 3 acpi_cpufreq,cpufreq_ondemand,cpufreq_stats
---
> freq_table 5792 3 acpi_cpufreq,cpufreq_stats,cpufreq_ondemand
> fuse 46612 1
38,39c39,41
< ipv6 261920 12
< ipw3945 118688 0
---
> ipv6 261920 10
> ipw3945 118688 1
> isofs 36284 1
44c46,47
< libata 117912 2 ata_generic,ata_piix
---
> libata 117912 2 ata_piix,ata_generic
> loop 17800 2
48a52
> nls_cp437 6784 1
61c65
< scsi_mod 142348 4 sg,sd_mod,sr_mod,libata
---
> scsi_mod 142348 4 sg,sr_mod,sd_mod,libata
63c67
< sd_mod 22272 4
---
> sd_mod 22272 0
84c88,89
< sr_mod 17060 0
---
> squashfs 46340 1
> sr_mod 17060 1
91a97
> unionfs 74148 1