bad motherboard detection with Hardy 2.6.24-15 & 16

[dino99]

My hardware is: mobo= Asus P5wdh, video= Asus En8500gt

I have some bugs when booting:
- need to add irqpoll but after a very long time, a busybox appear showing a problem about ata detection (need to boot in recovery mode)
- some warnings about acpi-cpufreq and irq (try pci=routeirq but nothing better for booting)

After this difficult boot, i look what sysinfo (0.7) identify:
-don't recognise xorg version (unknown 30 march 2008)
- hardware subsystem: Asustek P5WDG2 WS professional motherboard instead of the good one: P5WDH (which is not the same !!!)
- ide interface: unknown device 2601 ( intel 82801 gb/gr ich7r lpc interface bridge rev 01 )
- isa bridge: unknown device 8179 (intel 82801 gb/gr/gh sata ide controller)

In var/log/debug: - kernel acpi: irq0/2/9 used by override
               /kernel.log: acpi: lapic (acpi_id[0x03] lapic_id[0x82] disabled
                                  acpi: lapic (acpi_id[0x04] lapic_id[0x83] disabled
                                  acpi: looking for DSDT in initramfs... error, file /DSDT.aml not found
                                  acpi warning (tbutils-0217): incorrect checksum in table [oemb] - BC, should be B3 [20070126]
                                  EDD information not available
                                 acpi exception (processor_core-0816):AE_NOT_FOUND processor device not present [20070126]
                                  ata4.00: 640 sectors (nb: due to bad mobo detection, that ide don't exist (probably is a chipset Jmicron or Silicon)
                                  driver 'sd' needs updating - please use bus_type methods
                                  lp: driver loaded but no devices found
                                  coretemp: using undocumented features, absolute temperature might be wrong

****** dmidecode is giving the real motherboard model ********

[dino99 (9d9)]

some news about that virtual device ata4 found after googling

this mobo p5wdh have module 975x (ich7r);
there are 3 sata avaliable: sata1, sata3, sata4 to plug hardware.
Sata2 is hired for raid with Sil4723 chipset: this one is identified as ata4 when i'm booting.

So, we need to find a way to blacklist this Sil4723 chipset as an ata device.

[tj (htejun)]

dino99, can you please cc yourself in the following kernel bz and test the patch posted there?

  http://bugzilla.kernel.org/show_bug.cgi?id=10466

Thanks.

[dino99 (9d9)]

thanks, but how do i can apply this ? please tell me how.

[Leann Ogasawara (leannogasawara)]

Hi dino99,

Care to test the latest Alpha for the upcoming Intrepid Ibex 8.10. It contains the patch from the upstream bug report that tj reference. For more information regarding the latest Alpha for Intrepid, refer to http://www.ubuntu.com/testing. Please let us know your results. If the issue still exists, per the kernel team's bug policy, can you please attach the following information. Please be sure to attach each file as a separate attachment.

* cat /proc/version_signature > version.log
* dmesg > dmesg.log

For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help and feedback.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.