Re: Adaptec 2010S i2o + x86_64 doesn't work
On Gwe, 2005-04-15 at 19:16, Arjan van de Ven wrote: > are you sure the HW isn't 31 bit by accident ? It is reported working with mem=3840 so its not 31bit, and I2O requires 32bit DMA, with option for 64bit. Alan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec 2010S i2o + x86_64 doesn't work
Hello, Arjan van de Ven wrote: On Fri, 2005-04-15 at 20:10 +0200, Markus Lidel wrote: Alan Cox wrote: On Gwe, 2005-04-15 at 17:15, Miquel van Smoorenburg wrote: However, I removed 2 GB from the box as Alan sugggested and now the box comes up just fine with a 64-bit 2.6.11.6 kernel! I've put the 4GB back, and booted with the kernel "mem=2048" command line option - that also works, the i2o_block driver sees the adaptec controller just fine. And I just booted it with "mem=3840M" and that works too. So the problem appears to be 4 GB memory in 64 bit mode, on this box. Or the driver is incorrectly handling 64/32bit DMA limit masks which would be my first guess here, and would explain why it works on AMD Athlon64 boxes. Hmmm, i only set DMA_32BIT_MASK and don't do anything special on 64-bit systems... Is there anything else to do for correct DMA mapping? are you sure the HW isn't 31 bit by accident ? I don't know :-( But if the controller could only handle 31-bit DMA, wouldn't the 32-bit kernel with 4 GB also have the same problems? Best regards, Markus Lidel -- Markus Lidel (Senior IT Consultant) Shadow Connect GmbH Carl-Reisch-Weg 12 D-86381 Krumbach Germany Phone: +49 82 82/99 51-0 Fax:+49 82 82/99 51-11 E-Mail: [EMAIL PROTECTED] URL:http://www.shadowconnect.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec 2010S i2o + x86_64 doesn't work
On Fri, 2005-04-15 at 20:10 +0200, Markus Lidel wrote: > Hello, > > Alan Cox wrote: > > On Gwe, 2005-04-15 at 17:15, Miquel van Smoorenburg wrote: > >>However, I removed 2 GB from the box as Alan sugggested and now the box > >>comes up just fine with a 64-bit 2.6.11.6 kernel! I've put the 4GB back, > >>and booted with the kernel "mem=2048" command line option - that also > >>works, the i2o_block driver sees the adaptec controller just fine. > >>And I just booted it with "mem=3840M" and that works too. > >>So the problem appears to be 4 GB memory in 64 bit mode, on this box. > > OK, i never tried it with 4 GB so it really could be a problem... > > > Or the driver is incorrectly handling 64/32bit DMA limit masks which > > would be my first guess here, and would explain why it works on AMD > > Athlon64 boxes. > > Hmmm, i only set DMA_32BIT_MASK and don't do anything special on 64-bit > systems... Is there anything else to do for correct DMA mapping? are you sure the HW isn't 31 bit by accident ? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec 2010S i2o + x86_64 doesn't work
Hello, Alan Cox wrote: On Gwe, 2005-04-15 at 17:15, Miquel van Smoorenburg wrote: However, I removed 2 GB from the box as Alan sugggested and now the box comes up just fine with a 64-bit 2.6.11.6 kernel! I've put the 4GB back, and booted with the kernel "mem=2048" command line option - that also works, the i2o_block driver sees the adaptec controller just fine. And I just booted it with "mem=3840M" and that works too. So the problem appears to be 4 GB memory in 64 bit mode, on this box. OK, i never tried it with 4 GB so it really could be a problem... Or the driver is incorrectly handling 64/32bit DMA limit masks which would be my first guess here, and would explain why it works on AMD Athlon64 boxes. Hmmm, i only set DMA_32BIT_MASK and don't do anything special on 64-bit systems... Is there anything else to do for correct DMA mapping? Best regards, Markus Lidel -- Markus Lidel (Senior IT Consultant) Shadow Connect GmbH Carl-Reisch-Weg 12 D-86381 Krumbach Germany Phone: +49 82 82/99 51-0 Fax:+49 82 82/99 51-11 E-Mail: [EMAIL PROTECTED] URL:http://www.shadowconnect.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec 2010S i2o + x86_64 doesn't work
On Gwe, 2005-04-15 at 17:15, Miquel van Smoorenburg wrote: > However, I removed 2 GB from the box as Alan sugggested and now the box > comes up just fine with a 64-bit 2.6.11.6 kernel! I've put the 4GB back, > and booted with the kernel "mem=2048" command line option - that also > works, the i2o_block driver sees the adaptec controller just fine. > > And I just booted it with "mem=3840M" and that works too. > > So the problem appears to be 4 GB memory in 64 bit mode, on this box. Or the driver is incorrectly handling 64/32bit DMA limit masks which would be my first guess here, and would explain why it works on AMD Athlon64 boxes. Alan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec 2010S i2o + x86_64 doesn't work
On Fri, 2005-04-15 at 15:52 +0100, Alan Cox wrote: > On Mer, 2005-04-13 at 17:03, Miquel van Smoorenburg wrote: > > I have a supermicro dual xeon em64t system, X6DH8-XG2 motherboard, > > 4 GB RAM, with an Adaptec zero raid 2010S i2o controller. In 32 > > bits mode it runs fine, both with the dpt_i2o driver and the > > generic i2o_block driver using kernel 2.6.11.6. > > Does it work if you drop the box to 2Gbytes ? I tried 2.6.9 with 4GB and it didn't make any difference. However, I removed 2 GB from the box as Alan sugggested and now the box comes up just fine with a 64-bit 2.6.11.6 kernel! I've put the 4GB back, and booted with the kernel "mem=2048" command line option - that also works, the i2o_block driver sees the adaptec controller just fine. And I just booted it with "mem=3840M" and that works too. So the problem appears to be 4 GB memory in 64 bit mode, on this box. Mike. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec 2010S i2o + x86_64 doesn't work
On Mer, 2005-04-13 at 17:03, Miquel van Smoorenburg wrote: > I have a supermicro dual xeon em64t system, X6DH8-XG2 motherboard, > 4 GB RAM, with an Adaptec zero raid 2010S i2o controller. In 32 > bits mode it runs fine, both with the dpt_i2o driver and the > generic i2o_block driver using kernel 2.6.11.6. Does it work if you drop the box to 2Gbytes ? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec 2010S i2o + x86_64 doesn't work
On Mer, 2005-04-13 at 17:03, Miquel van Smoorenburg wrote: I have a supermicro dual xeon em64t system, X6DH8-XG2 motherboard, 4 GB RAM, with an Adaptec zero raid 2010S i2o controller. In 32 bits mode it runs fine, both with the dpt_i2o driver and the generic i2o_block driver using kernel 2.6.11.6. Does it work if you drop the box to 2Gbytes ? - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec 2010S i2o + x86_64 doesn't work
On Fri, 2005-04-15 at 15:52 +0100, Alan Cox wrote: On Mer, 2005-04-13 at 17:03, Miquel van Smoorenburg wrote: I have a supermicro dual xeon em64t system, X6DH8-XG2 motherboard, 4 GB RAM, with an Adaptec zero raid 2010S i2o controller. In 32 bits mode it runs fine, both with the dpt_i2o driver and the generic i2o_block driver using kernel 2.6.11.6. Does it work if you drop the box to 2Gbytes ? I tried 2.6.9 with 4GB and it didn't make any difference. However, I removed 2 GB from the box as Alan sugggested and now the box comes up just fine with a 64-bit 2.6.11.6 kernel! I've put the 4GB back, and booted with the kernel mem=2048 command line option - that also works, the i2o_block driver sees the adaptec controller just fine. And I just booted it with mem=3840M and that works too. So the problem appears to be 4 GB memory in 64 bit mode, on this box. Mike. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec 2010S i2o + x86_64 doesn't work
On Gwe, 2005-04-15 at 17:15, Miquel van Smoorenburg wrote: However, I removed 2 GB from the box as Alan sugggested and now the box comes up just fine with a 64-bit 2.6.11.6 kernel! I've put the 4GB back, and booted with the kernel mem=2048 command line option - that also works, the i2o_block driver sees the adaptec controller just fine. And I just booted it with mem=3840M and that works too. So the problem appears to be 4 GB memory in 64 bit mode, on this box. Or the driver is incorrectly handling 64/32bit DMA limit masks which would be my first guess here, and would explain why it works on AMD Athlon64 boxes. Alan - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec 2010S i2o + x86_64 doesn't work
Hello, Alan Cox wrote: On Gwe, 2005-04-15 at 17:15, Miquel van Smoorenburg wrote: However, I removed 2 GB from the box as Alan sugggested and now the box comes up just fine with a 64-bit 2.6.11.6 kernel! I've put the 4GB back, and booted with the kernel mem=2048 command line option - that also works, the i2o_block driver sees the adaptec controller just fine. And I just booted it with mem=3840M and that works too. So the problem appears to be 4 GB memory in 64 bit mode, on this box. OK, i never tried it with 4 GB so it really could be a problem... Or the driver is incorrectly handling 64/32bit DMA limit masks which would be my first guess here, and would explain why it works on AMD Athlon64 boxes. Hmmm, i only set DMA_32BIT_MASK and don't do anything special on 64-bit systems... Is there anything else to do for correct DMA mapping? Best regards, Markus Lidel -- Markus Lidel (Senior IT Consultant) Shadow Connect GmbH Carl-Reisch-Weg 12 D-86381 Krumbach Germany Phone: +49 82 82/99 51-0 Fax:+49 82 82/99 51-11 E-Mail: [EMAIL PROTECTED] URL:http://www.shadowconnect.com - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec 2010S i2o + x86_64 doesn't work
On Fri, 2005-04-15 at 20:10 +0200, Markus Lidel wrote: Hello, Alan Cox wrote: On Gwe, 2005-04-15 at 17:15, Miquel van Smoorenburg wrote: However, I removed 2 GB from the box as Alan sugggested and now the box comes up just fine with a 64-bit 2.6.11.6 kernel! I've put the 4GB back, and booted with the kernel mem=2048 command line option - that also works, the i2o_block driver sees the adaptec controller just fine. And I just booted it with mem=3840M and that works too. So the problem appears to be 4 GB memory in 64 bit mode, on this box. OK, i never tried it with 4 GB so it really could be a problem... Or the driver is incorrectly handling 64/32bit DMA limit masks which would be my first guess here, and would explain why it works on AMD Athlon64 boxes. Hmmm, i only set DMA_32BIT_MASK and don't do anything special on 64-bit systems... Is there anything else to do for correct DMA mapping? are you sure the HW isn't 31 bit by accident ? - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec 2010S i2o + x86_64 doesn't work
Hello, Arjan van de Ven wrote: On Fri, 2005-04-15 at 20:10 +0200, Markus Lidel wrote: Alan Cox wrote: On Gwe, 2005-04-15 at 17:15, Miquel van Smoorenburg wrote: However, I removed 2 GB from the box as Alan sugggested and now the box comes up just fine with a 64-bit 2.6.11.6 kernel! I've put the 4GB back, and booted with the kernel mem=2048 command line option - that also works, the i2o_block driver sees the adaptec controller just fine. And I just booted it with mem=3840M and that works too. So the problem appears to be 4 GB memory in 64 bit mode, on this box. Or the driver is incorrectly handling 64/32bit DMA limit masks which would be my first guess here, and would explain why it works on AMD Athlon64 boxes. Hmmm, i only set DMA_32BIT_MASK and don't do anything special on 64-bit systems... Is there anything else to do for correct DMA mapping? are you sure the HW isn't 31 bit by accident ? I don't know :-( But if the controller could only handle 31-bit DMA, wouldn't the 32-bit kernel with 4 GB also have the same problems? Best regards, Markus Lidel -- Markus Lidel (Senior IT Consultant) Shadow Connect GmbH Carl-Reisch-Weg 12 D-86381 Krumbach Germany Phone: +49 82 82/99 51-0 Fax:+49 82 82/99 51-11 E-Mail: [EMAIL PROTECTED] URL:http://www.shadowconnect.com - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec 2010S i2o + x86_64 doesn't work
On Gwe, 2005-04-15 at 19:16, Arjan van de Ven wrote: are you sure the HW isn't 31 bit by accident ? It is reported working with mem=3840 so its not 31bit, and I2O requires 32bit DMA, with option for 64bit. Alan - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec 2010S i2o + x86_64 doesn't work
Hello, Miquel van Smoorenburg wrote: I have a supermicro dual xeon em64t system, X6DH8-XG2 motherboard, 4 GB RAM, with an Adaptec zero raid 2010S i2o controller. In 32 bits mode it runs fine, both with the dpt_i2o driver and the generic i2o_block driver using kernel 2.6.11.6. In 64 bits mode however the dpt_i2o driver isn't supported, so you have to use the generic i2o layer. But that doesn't work either - sometimes when booting the partition table is detected, sometimes it isn't. If it isn't, then fdisk /dev/i2o/hda works but shows an empty disk (while there definitely are partitions present) In both cases doing a dd if=/dev/i2o/hda of=/dev/null crashes the system. According to http://i2o.shadowconnect.com/ , it should work. I've upgraded the BIOS and firmware of the mobo and controller to the latest versions - doesn't help. Can someone suggest what to try next ? Could you try out the 2.6.9 kernel, because i know that this one is working? Also could you send me a complete output of dmesg? Thank you very much. Best regards, Markus Lidel -- Markus Lidel (Senior IT Consultant) Shadow Connect GmbH Carl-Reisch-Weg 12 D-86381 Krumbach Germany Phone: +49 82 82/99 51-0 Fax:+49 82 82/99 51-11 E-Mail: [EMAIL PROTECTED] URL:http://www.shadowconnect.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Adaptec 2010S i2o + x86_64 doesn't work
Hello, Miquel van Smoorenburg wrote: I have a supermicro dual xeon em64t system, X6DH8-XG2 motherboard, 4 GB RAM, with an Adaptec zero raid 2010S i2o controller. In 32 bits mode it runs fine, both with the dpt_i2o driver and the generic i2o_block driver using kernel 2.6.11.6. In 64 bits mode however the dpt_i2o driver isn't supported, so you have to use the generic i2o layer. But that doesn't work either - sometimes when booting the partition table is detected, sometimes it isn't. If it isn't, then fdisk /dev/i2o/hda works but shows an empty disk (while there definitely are partitions present) In both cases doing a dd if=/dev/i2o/hda of=/dev/null crashes the system. According to http://i2o.shadowconnect.com/ , it should work. I've upgraded the BIOS and firmware of the mobo and controller to the latest versions - doesn't help. Can someone suggest what to try next ? Could you try out the 2.6.9 kernel, because i know that this one is working? Also could you send me a complete output of dmesg? Thank you very much. Best regards, Markus Lidel -- Markus Lidel (Senior IT Consultant) Shadow Connect GmbH Carl-Reisch-Weg 12 D-86381 Krumbach Germany Phone: +49 82 82/99 51-0 Fax:+49 82 82/99 51-11 E-Mail: [EMAIL PROTECTED] URL:http://www.shadowconnect.com - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
