Found this post via a google search when I found that my GA-EP45-UD3P did the same thing when I tried using dmidecode. Turns out that it's a GB problem which has been addresses in the most recent BIOS (FFb - 2010/10/06). Download it here if you're still experiencing problems: http://www.gigabyte.us/products/product-page.aspx?pid=3137&dl=1#bios --- dmidecode not working? March 11, 2010 07:08AM Let me start by saying this may or may not be a Fedora issue. I recently purchased two Gigabyte GA-EP45-UD3P motherboards and am running F12 on them. The marketing for these boards say they support SMBIOS 2.4 and DMI, yet dmidecode says: [root@phoenix ~]# dmidecode # dmidecode 2.10 # No SMBIOS nor DMI entry point found, sorry. What could be wrong? I've never seen a system that fails on this command before, and now I have two of them? They also have a problem with the on-board LAN and probably Firewire. Neither onboard NIC is working, the first shows a MAC of ff:ff:ff:ff:ff:ff. The other looks ok, but fails to work. Disabling the on-board NICs and using an off-board, PCI NIC works. The Firewire controller (granted I don't really use it), also identifies itself oddly: firewire_ohci 0000:06:07.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23 firewire_ohci: Added fw-ohci device 0000:06:07.0, OHCI version 1.10 firewire_core: created device fw0: GUID 0000000000000000, S400 I suspect these are all related. Possibly a bad BIOS although both systems are fully updated in that respect. Anyone else have a similar issue? -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
