Re: Boot problem

[christos%astron.com@localhost (Christos Zoulas)]

In article <201102092300.48654.cendres%videotron.ca@localhost>,
Robert Connolly  <cendres%videotron.ca@localhost> wrote:
>On Wednesday 09 February 2011 19:24:39 Christos Zoulas wrote:
>> In article <201102090146.56846.cendres%videotron.ca@localhost>,
>> 
>> Robert Connolly  <cendres%videotron.ca@localhost> wrote:
>> >On Tuesday 08 February 2011 21:06:35 Christos Zoulas wrote:
>> >> In article <201102081735.40589.cendres%videotron.ca@localhost>,
>> >> 
>> >> Robert Connolly  <cendres%videotron.ca@localhost> wrote:
>> >> >On Tuesday 08 February 2011 03:36:31 Ajay Rahar wrote:
>> >> >> pckbc1 refers to pc keyboard controller. I think there is some
>> >> >> problem in keyboard detection.
>> >> >
>> >> >With acpi disabled, there is no "pckbc1", it's "pckbc0".
>> >> >
>> >> >ACPI disabled:
>> >> >pckbc0 at isa0 port 0x60-0x64
>> >> >pckbd0 at pckbc0 (kbd slot)
>> >> >pckbc0: using irq 1 for kbd slot
>> >> >wskbd0 at pckbd0: console keyboard, using wsdisplay0
>> >> >pms0 at pckbc0 (aux slot)
>> >> >pms0: Synaptics touchpad version 6.3
>> >> >pms0: Palm detect, Multi-finger
>> >> >
>> >> >So, with ACPI enabled, maybe the touchpad is being detected as a second
>> >> >keyboard?
>> >> 
>> >> disable pckbd* and pms*
>> >> 
>> >> christos
>> >
>> >Then the boot stops on viaide1.
>> 
>> Ouch. disable viaide1?
>> 
>> christos
>
>After disabling viaide, the boot hung on pciide. After disabling pciide. the 
>boot hung on wd. After disabling wd, the boot hung on ieee1394if. After 
>disabling ieee1294if, the boot hung on atabus. The kernel would not link 
>without atabus because a dozen other modules depend on it.

So it is back to the initial theory that somehow acpi messes up interrupts?
Why do you need ACPI?

christos