Quoting Thomas Backlund <[EMAIL PROTECTED]>: > Viestiss� Keskiviikko 23. Hein�kuuta 2003 13:06, Svetoslav Slavtchev > kirjoitti: > > Quoting Thomas Backlund <[EMAIL PROTECTED]>: > > > Viestiss� Keskiviikko 23. Hein�kuuta 2003 11:56, Thomas Backlund > kirjoitti: > > [...] > > > > > > > I just checked my local cooker mirror... > > > The install images still uses the 13mdk kernel... > > > this is _BAD_ :-( > > > (for promise and aic79xx users...) > > > > also for some KT400 users :( > > my Epox 8k9a3+ lock ups really bad if the kernel > > doesn't have _really_ latest acpi or is an -ac one > > > > the last time i hardly managed to get to partitioning :( > > > > actually the 2.4.21-3mdk did hang too, but after some hours, > > any chanse to get acpi-200306xx or 200307xx in the kernel soon ? > > > > [...] > > Does it work with acpi=off ?
it works with "acpi=off pci=noacpi", but with -ac or the new acpi with older kernels/acpi that doesn't help :( i think that the problem exist partly because i can not disable ACPI in the BIOS( there is no such option ) turning ACPI off in the BIOS helped me to get running my previous KT333 + vt8235 Epox 8k5a3+ (hint hint - aren't they the only boards with 4 chanel ide on board) besides i'm seeng some very strange fs corruption (i think) but i couldn't find time to debug it. for example doing : "for i in 1 2 3; do rpmbuild --rebuild kernel-2.4.21.3mdk.....; done" would end on the 2nd or 3rd run with errors on decompressing linux-2.4.21.tar.bz2 or linux-2.4.21-q[n].tar.bz2 suggesting me to try to recover the brocken compressed file :( svetljo > (for me, I have to use acpi=off to get the network running > on my nforce2 board, wich means no fully working USB2...) > > Of course that's only a temporary solution, > and AFAIK Juan is well aware of the need of an updated acpi, > and alsa 0.95, and i2c/lm_sensors and ... > > And I think we well see them... and then some ... in the upcoming > kernels... > > Thomas > > --
