On Tue, 26 Apr 2005 09:03:02, Christoph Hellwig wrote: > On Tue, Apr 26, 2005 at 12:10:31AM +0200, Frederik Schueler wrote: > > Hello, > > > > I have a dpt_i2o card myself wich I had to remove from my workstation > > when I moved to amd64, I know your problem pretty well. Thus I am > > interested in this patch, I tried to contact adaptec back then but > > got no response. Where did you get that patch from? Was it already > > proposed for inclusion in the official 2.6 tree? > > Not sure where this thread started, but please always use the > i2o_block/i2o_scsi drivers and not dpt_i2o for 2.6.x.
There is no support for the i2o block driver in the debian installer. The debian-supplied kernels don't even have the i2o modules enabled. There _is_ support for the dpt_i2o driver in the installer, on both 2.4 and 2.6 kernels. It just didn't work on 2.6 in 64 bit mode. > If you see > problems with that driver please report it to the very active upstream > maintainer. There are problems with the i2o block driver in 64 bits mode, it doesn't work if you have 4GB of RAM. I reported this to the maintainer a week ago, on LKML. I did get an initial reponse from the i2o maintainer Markus Lidel right away, and Alan Cox, after which we figured out that the driver was not DMA 32/64 bit clean. But there hasn't been a followup on that yet. A workaround is booting with mem=3840m, by the way. That makes it work. I did make a driver floppy for the dpt_i2o.ko module to use in the installation process - which works just fine, _except_ that after you reboot, the newly installed kernel doesn't have that module, so that it's impossible to mount the root filesystem :( So again, with the current debian-installer, dpt_i2o needs to be in the debian-provided kernels. As things stand now, using dpt_i2o will get us a working dpt driver in sarge, while moving to i2o_block is an etch project I guess. Frederik- I'll send you the driver I got from Adaptec later today. Mike.
