Re: Installing amd64 on Adaptec 2015S (SmartRAID V) with dpt_i2o
Lennart Sorensen wrote: On Fri, Sep 02, 2005 at 11:56:54AM -0700, Neil Gunton wrote: Thanks Kevin, I had not seriously considered this option yet, in part because this is a tightly packed 1U case, with no space for an IDE drive inside. So I guess I could try an external USB drive enclosure - would that work? Is USB generally well supported for installing and booting up off of these days? No it isn't. It seems no one has even quite agreed what the boot protocol should be for usb drives, since there seems to be no standard for doing bios disk calls for usb drives. Actually, I think I may have a 2.5 external drive enclosure sitting around in one of my drawers, with a 20GB hard drive from my old laptop. If I remember correctly, it has two USB connectors, because it gets all its power from USB and so needs two ports. Should that work for installing? I doubt you would be able to boot from it after installing to it (if it even recognizes it as a disk in the installer). Len Sorensen Hi again, I'm sorry about not following up on this sooner, I have been out of action for the last few days due to a broken arm. I was returning from a mountain bike ride in the hills outside of Corvallis (Oregon) at dusk last Saturday when I went head first over the handlebars. Ironically I had gone for the ride to celebrate finally getting Debian amd64 to boot successfully by itself on the new server! Nothing much else computer-wise has happened since. I'll try (typing one handed here) to summarise how I finally got this working: To recap, with the 2015S, the Debian amd64 netinst CD currently fails to see any drives, but it does give the clue that the driver it wants is dpt_i2o. Apparently this driver is not enabled in Debian amd64 because it a) does not work under 64 bit and b) is apparently being deprecated by the community in favor of i2o_block. However i2o_block was not available in the netinst either. I found that CentOS 4.1 x86_64 does install out of the box - they have a good 64-bit version with more drivers and better ability to select modules manually at install time: http://www.centos.org/ It will say you have no disks at first, but it will give you the opportunity to select a driver, and i2o_block appears to make it work. Your drives will appear under /dev/i2o/hda rather than /dev/sda etc. For more info on i2o_block see: http://i2o.shadowconnect.com/ Two things struck me here: First, really I wanted to run Debian, not a RHE-based distro. Second, I really wanted to have real scsi disks rather than i2o block devices if I could. I had also heard an anecdotal story from someone that they got block transfer errors under load from i2o_block with the 2015S, so I wanted to use Adaptec's official driver if possible. I tried rolling a custom Debian kernel and netinst CD from CentOS, but after many tries I was unable to get this to boot. It always panicked at some point, so I gave up on that route. Apparently there is quite a lot more to rolling your own netinst cd than simply replacing the vmlinuz an initrd - on a side note, is anybody aware of a howto on making a custom netinst cd? Someone also suggested installing onto a temporary IDE disk and then rolling a custom kernel from there and copying the system over, but I found that even this didn't work since my network driver (tg3) didn't seem to be present in the 2.6.8 kernel. In the meantime, I had been in touch with Mark Salyzyn of Adaptec ([EMAIL PROTECTED]), who maintains the dpt_i2o driver. He sent me a version that he said should work under 64-bit. He said that the community appeared to be deprecating dpt_i2o in favor of i2o_block, if only because there were always questions about why we would have two different drivers for the same device. Nevertheless as outlined above I was interested in getting dpt_i2o working if I could. In a nutshell, Mark's 64-bit dpt_i2o *does* indeed work - I can forward his email with the dpt_i2o source tarball to anyone who wants it, though you are probably better off going directly to Mark for the latest update. As for why they don't simply put this up on their website, Mark said: As for making the driver 'more available' it is a victim of Technical Support policy. They don't like to put up untested products. However, they do have a private ftp used for customers to slip them such updated contents. I will (or should I perish, [EMAIL PROTECTED]) remain the best means of getting the latest driver, but I assure you that sooner or later you will see this, or a more advanced, version of the driver showing on the web site once someone does some testing. Anyway, step-by-step here's what got it all working for me (as far as I can remember): 1. Install CentOS onto one partition of your system, using i2o_block. I put it way up on /dev/i2o/hda10, the lower partitions being reserved for my future Debian installation. So the idea is that you partition the disks under the CentOS
Re: Installing amd64 on Adaptec 2015S (SmartRAID V) with dpt_i2o
On Fri, Sep 09, 2005 at 01:09:06PM -0700, Neil Gunton wrote: That should do it! Easy, eh? ;-) I tried to remember everything I did, but I may have missed something. Thanks again for all the help and tips from members of this list. I will try and include the patched dpt_i2o if I get around to rebuilding the kernel I use on my version of the install CD, although if it does see the disks as i2o block devices, then I guess it technically does work already even if not quite how you would like it. Good to see you got it working though. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing amd64 on Adaptec 2015S (SmartRAID V) with dpt_i2o
Lennart Sorensen wrote: On Thu, Sep 01, 2005 at 03:12:28PM -0700, Neil Gunton wrote: This is a stupid question, but I am trying to create a netinst bootable CD and I don't know how to do the El Torito thing with the boot image. Is there an easy way to generate the bootable iso from the official netinst CD I have, given that I have mirrored the files to my hard drive so I can replace the initrd and vmlinuz? You should tell it to use isolinux/isolinux.bin as the boot image, and use the no emulation option, and there is one other option about size I can't remember (I think it should be 4k but I can't remember for sure). Sorry to bug you, but any clues much appreciated... I've read lots about the boot.img requirement, but I have no idea where you're meant to get that from. I see there's a boot.cat on the CD already. Can we somehow extract the existing boot image and re-use that? mkisofs generates boot.cat for you. ie: mkisofs -o /tmp/sarge-amd64-2.6.12-netinst.iso -r -J -no-emul-boot -boot-load-size 4 -boot-info-table -b isolinux/isolinux.bin -c isolinux/boot.cat . The config in the isolinux dir points at the kernel files in install. Len Sorensen Thanks very much for the tips! I was in fact doing something similar to this all day yesterday, and I now have a handy little pile of CD coasters. I just can't get this thing to boot! I just tried it using your incantation and it doesn't make any difference. Here's what I am doing: I have an working version of CentOS 4.1 installed on the hard drive (actually 4 hard drives, RAID 10) and running ok using i2o_block. I downloaded 2.6.12.6 from kernel.org and built it, including the new 64-bit-capable dpt_i2o driver from Adaptec (it won't compile on 2.6.13). That works fine, and I can even boot into it off the hard drive from grub. All the important modules are compiled statically into the kernel. This includes all the ide, scsi, dpt_i2o, ext3 etc. But when I try this from my custom netinst cd, there is a kernel panic. To build the CD I am simply replacing the install/vmlinuz and install/initrd.gz with my own versions, and then creating the iso and burning the CD as outlined above. It does boot ok past the isolinux and into the kernel, and it does appear to recognize the RAID card. But then it gets the panic: ... Freeing unused kernel memory: 220k freed Red Hat nash version 4.2.1.3 starting Mounted /proc filesystem Mounting sysfs Creating /dev Starting udev Creating root device Mounting root filesystem mount: error 6 mounting ext3 mount: error 2 mounting none Switching to new root switchroot: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempted to kill init! What am I doing wrong here??? Is this something to do with the /devfs issue? But Len, you must be doing something different, because your ISO gets past this point with no problem. I get the feeling I am missing some crucial piece in the kernel and/or CD build process that makes it not see that it's booting from CD. Also, I'm a little confused as to why it's still saying Red Hat nash version 4.2.1.3 starting, because this should be a custom kernel, I downloaded it from kernel.org. Where does it get the Red Hat bit from? Is that a system thing that it includes automatically, or are my kernels just somehow getting all mixed up with the one already on the hard drive (which really is the CentOS kernel)... I am about out of ideas with this path, I'd love to be able to get a real Debian netinst CD working with dpt_i2o so that I can build a real Debian system from the ground up. Any clues much appreciated... Thanks again, -Neil -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing amd64 on Adaptec 2015S (SmartRAID V) with dpt_i2o
On Fri, Sep 02, 2005 at 10:06:02AM -0700, Neil Gunton wrote: Thanks very much for the tips! I was in fact doing something similar to this all day yesterday, and I now have a handy little pile of CD coasters. I just can't get this thing to boot! I just tried it using your incantation and it doesn't make any difference. Here's what I am doing: I have an working version of CentOS 4.1 installed on the hard drive (actually 4 hard drives, RAID 10) and running ok using i2o_block. I downloaded 2.6.12.6 from kernel.org and built it, including the new 64-bit-capable dpt_i2o driver from Adaptec (it won't compile on 2.6.13). That works fine, and I can even boot into it off the hard drive from grub. All the important modules are compiled statically into the kernel. This includes all the ide, scsi, dpt_i2o, ext3 etc. But when I try this from my custom netinst cd, there is a kernel panic. To build the CD I am simply replacing the install/vmlinuz and install/initrd.gz with my own versions, and then creating the iso and burning the CD as outlined above. It does boot ok past the isolinux and into the kernel, and it does appear to recognize the RAID card. But then it gets the panic: ... Freeing unused kernel memory: 220k freed Red Hat nash version 4.2.1.3 starting Mounted /proc filesystem Mounting sysfs Creating /dev Starting udev Creating root device Mounting root filesystem mount: error 6 mounting ext3 mount: error 2 mounting none Switching to new root switchroot: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempted to kill init! What am I doing wrong here??? Is this something to do with the /devfs issue? But Len, you must be doing something different, because your ISO gets past this point with no problem. I get the feeling I am missing some crucial piece in the kernel and/or CD build process that makes it not see that it's booting from CD. I use the kernel from linux-image-2.6.12-1-amd64-generic. That one has initrd and cramfs and such support and all the other options debian expects a kernel to have, and also what the debian installer expects. I suspect you don't have initrd or at least not cramfs initrd support and that makes the installer fail to load the initrd containing the installer. The initrd also has to be rebuilt for the kernel from the debian-installer package, and the udeb's rebuilt using another debian package. Also, I'm a little confused as to why it's still saying Red Hat nash version 4.2.1.3 starting, because this should be a custom kernel, I downloaded it from kernel.org. Where does it get the Red Hat bit from? Is that a system thing that it includes automatically, or are my kernels just somehow getting all mixed up with the one already on the hard drive (which really is the CentOS kernel)... I am about out of ideas with this path, I'd love to be able to get a real Debian netinst CD working with dpt_i2o so that I can build a real Debian system from the ground up. Well if you say the driver appears to work, I would be willing to try building an image with a _debian_ 2.6.12 kernel with that driver in it. Starting from kernel.org sources is way to much work. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing amd64 on Adaptec 2015S (SmartRAID V) with dpt_i2o
Lennart Sorensen wrote: I use the kernel from linux-image-2.6.12-1-amd64-generic. That one has initrd and cramfs and such support and all the other options debian expects a kernel to have, and also what the debian installer expects. I suspect you don't have initrd or at least not cramfs initrd support and I do build in initrd and cramfs, I have been through menuconfig a few times now and selected everything that looked remotely relevant. that makes the installer fail to load the initrd containing the installer. The initrd also has to be rebuilt for the kernel from the debian-installer package, and the udeb's rebuilt using another debian package. Sorry, but I don't really understand that last sentence, could you expand some more please? The initrd has to be rebuilt for the kernel from the debian-installer package. Surely if I built the kernel and did the mkinitrd using the modules from that then we should be ok? ... and the udeb's rebuilt using another Debian package - I don't understand this Well if you say the driver appears to work, I would be willing to try building an image with a _debian_ 2.6.12 kernel with that driver in it. Starting from kernel.org sources is way to much work. Ok, that would be nice! Although, I would like to be able to do this myself, so perhaps I will try to get the actual Debian kernel source and see if that has better luck. Let me know if you get a working iso... Thanks, /Neil -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing amd64 on Adaptec 2015S (SmartRAID V) with dpt_i2o
On Fri, Sep 02, 2005 at 10:48:54AM -0700, Neil Gunton wrote: I do build in initrd and cramfs, I have been through menuconfig a few times now and selected everything that looked remotely relevant. kernel sources from kernel.org do NOT support cramfs initrd's. Debian kernel sources has patches for that. I don't actually know if the installer uses ext2 or cramfs for the initrd. Sorry, but I don't really understand that last sentence, could you expand some more please? The initrd has to be rebuilt for the kernel from the debian-installer package. Surely if I built the kernel and did the mkinitrd using the modules from that then we should be ok? The installer has it's own initrd containing kernel modules and other things needed for the installer to load other files from the CD. The installer boots the kernel, loads an initrd and runs with that initrd as the root filesystem while the install is running. ... and the udeb's rebuilt using another Debian package - I don't understand this Making an install cd with a replacement kernel involves a lot more updates than just the vmlinuz file. Ok, that would be nice! Although, I would like to be able to do this myself, so perhaps I will try to get the actual Debian kernel source and see if that has better luck. Let me know if you get a working iso... Well you need to take an existing netinstall image, replace the kernel image file on the cd, replace the kernel udebs on the cd, replace the debian installer base package with one that looks for your new kernel name, and the packages files have to be rebuilt to match those new files. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing amd64 on Adaptec 2015S (SmartRAID V) with dpt_i2o
Lennart Sorensen wrote: kernel sources from kernel.org do NOT support cramfs initrd's. Debian kernel sources has patches for that. Ok... I was just going by the fact that the 2.6.12.6 from kernel.org did have cramfs under Miscellaneous filesystems, so I thought that would do it. If it needs to be patched then that's a whole other kettle of fish... Making an install cd with a replacement kernel involves a lot more updates than just the vmlinuz file. Well you need to take an existing netinstall image, replace the kernel image file on the cd, replace the kernel udebs on the cd, replace the debian installer base package with one that looks for your new kernel name, and the packages files have to be rebuilt to match those new files. Ah! Well, that would explain a lot. I guess I was probably very naiive thinking I could simply replace the initrd.gz and vmlinuz, because I thought those were the crucial elements needed to boot. Since this starts to look a lot more complex than I thought, I will probably try the debootstrap route instead, so I can skip the whole CD mess. Unless anyone has a step-by-step howto on how to roll your own netinst CD - especially when you do not have an already-working Debian system to use for getting packages, building etc. Thanks again for all your help, it's been most illuminating! Seems like every time I think I have linux down pat, then I try to do something on a new machine and have to spend a week just getting the hardware working... Linux, it's always good for your humility! /Neil -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing amd64 on Adaptec 2015S (SmartRAID V) with dpt_i2o
Neil Gunton wrote: Thanks again for all your help, it's been most illuminating! Seems like every time I think I have linux down pat, then I try to do something on a new machine and have to spend a week just getting the hardware working... Linux, it's always good for your humility! Neil, You've probably already thought of this, but after years of building installing Linux on unsupported disk controllers, I've given up on attempting to build custom driver or installer disks to support the new hardware. These days, as soon as I find out the controller is unsupported, I just pop on old, small IDE drive off the shelf into the system and install the OS on that. Then, of course, it's a simple matter of building a custom kernel, booting to single user mode, and copying the OS from the temporary IDE drive to the SCSI drive. One nice thing about Debian is that after the initial installation, you can easily upgrade to new versions without every going through a reinstallation. Last I looked, RedHat, Fedora, and SuSE require reinstallations to upgrade to new versions. Kevin -- Kevin Rosenberg [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing amd64 on Adaptec 2015S (SmartRAID V) with dpt_i2o
Kevin Rosenberg wrote: Neil Gunton wrote: Thanks again for all your help, it's been most illuminating! Seems like every time I think I have linux down pat, then I try to do something on a new machine and have to spend a week just getting the hardware working... Linux, it's always good for your humility! Neil, You've probably already thought of this, but after years of building installing Linux on unsupported disk controllers, I've given up on attempting to build custom driver or installer disks to support the new hardware. These days, as soon as I find out the controller is unsupported, I just pop on old, small IDE drive off the shelf into the system and install the OS on that. Then, of course, it's a simple matter of building a custom kernel, booting to single user mode, and copying the OS from the temporary IDE drive to the SCSI drive. One nice thing about Debian is that after the initial installation, you can easily upgrade to new versions without every going through a reinstallation. Last I looked, RedHat, Fedora, and SuSE require reinstallations to upgrade to new versions. Kevin Thanks Kevin, I had not seriously considered this option yet, in part because this is a tightly packed 1U case, with no space for an IDE drive inside. So I guess I could try an external USB drive enclosure - would that work? Is USB generally well supported for installing and booting up off of these days? Actually, I think I may have a 2.5 external drive enclosure sitting around in one of my drawers, with a 20GB hard drive from my old laptop. If I remember correctly, it has two USB connectors, because it gets all its power from USB and so needs two ports. Should that work for installing? Thanks again, -Neil -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing amd64 on Adaptec 2015S (SmartRAID V) with dpt_i2o
Neil Gunton wrote: Thanks Kevin, I had not seriously considered this option yet, in part because this is a tightly packed 1U case, with no space for an IDE drive inside. So I guess I could try an external USB drive enclosure - would that work? Is USB generally well supported for installing and booting up off of these days? I'm not certain that USB is supported for booting/installing. What I typically do for rackmounts, is not to bother mounting the temporary drive in the enclosure. With the case out of the cabinet, I rest the temporary IDE drive on top of the drive cage with the lid off of the case. Most of the time, I'm done with the installation and copying within an hour or two. You can also use this for cloning an installation. Install your desired base system on an IDE drive, then rest that drive on or inside the case of the new system. Boot off the IDE into single user mode then copy the system onto the mounted internal drives of the new system. Kevin Actually, I think I may have a 2.5 external drive enclosure sitting around in one of my drawers, with a 20GB hard drive from my old laptop. If I remember correctly, it has two USB connectors, because it gets all its power from USB and so needs two ports. Should that work for installing? Might work. Would depend the Debian installer would install upon a USB drive and if your BIOS could boot off of a USB drive. If either of those doesn't work, you can probably remove the IDE drive from the USB enclosure fairly quickly and connect it via IDE (serial or parallel, depending upon the drive) to your motherboard. -- Kevin Rosenberg [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing amd64 on Adaptec 2015S (SmartRAID V) with dpt_i2o
On Fri, Sep 02, 2005 at 11:56:54AM -0700, Neil Gunton wrote: Thanks Kevin, I had not seriously considered this option yet, in part because this is a tightly packed 1U case, with no space for an IDE drive inside. So I guess I could try an external USB drive enclosure - would that work? Is USB generally well supported for installing and booting up off of these days? No it isn't. It seems no one has even quite agreed what the boot protocol should be for usb drives, since there seems to be no standard for doing bios disk calls for usb drives. Actually, I think I may have a 2.5 external drive enclosure sitting around in one of my drawers, with a 20GB hard drive from my old laptop. If I remember correctly, it has two USB connectors, because it gets all its power from USB and so needs two ports. Should that work for installing? I doubt you would be able to boot from it after installing to it (if it even recognizes it as a disk in the installer). Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing amd64 on Adaptec 2015S (SmartRAID V) with dpt_i2o
On Wed, Aug 31, 2005 at 03:21:30PM -0700, Neil Gunton wrote: I just built a server which has dual Opteron 265, 4GB RAM, Adaptec 2015S zero-channel RAID controller and 4 x Ultra320 10k SCSI drives. I am having a problem installing Debian amd64, because of the 2015S card. This requires the dpt_i2o driver, which is not included by default in Debian amd64. Well last I looked (2.6.12 kernel), the dpt_i2o driver was listed explicitly as not 64bit compatible and couldn't be selected on any 64bit platform. An alternative would be the i2o_blocks module. I can install CentOS 4.1 x86_64 using i2o_blocks, but there does not seem to be any way to do this with Debian. I don't know what i2o_blocks is, but I did include the i2o drivers in my 2.6.12 based sarge amd64 netinst image. Feel free to try that one if you wish. I have i2o_block, i2o_config, i2o_core, i2o_proc and i2o_scsi included. May have to manually modprobe them from console 2, since I have no idea I the discover data knows to try those for your controller. http://www.tinyplanet.ca/~lsorense/amd64/ I managed to get hold of Mark Salyzyn at Adaptec, and he sent me source code for the dpt_i2o driver which he tells me should work in 64-bit mode. I could presumably build this into a custom kernel. But I don't know how to do this while installing Debian from scratch. That would be a problem yes. If I knew it would work, I would be willing to add the driver to my installer image's kernel. Could you send me the updated driver to have a look at? So, I see three possibilities, but I don't know how to do any of them: 1. MANUAL MODULE SELECTION: Specify the i2o_blocks module (if it's actually on the install CD) manually at install time with the Debian installer. I can't see any option for this. 2. DRIVER DISK: Compile the dpt_i2o source code and build a driver disk for Debian amd64 (if that's even possible - should I be able to install using 'linux dd' with this port?) 3. CUSTOM KERNEL: Build a custom kernel from CentOS 4.1 x86_64 (which I can install using i2o_blocks) and build in the dpt_i2o driver... but then, even if this works, how then to package up and use this kernel at install time for Debian? CentOS 4.1 does work, with i2o_blocks, but I would much rather be running Debian. Please help... Hope the above might give you a way to go. At least if i2o_blocks works. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing amd64 on Adaptec 2015S (SmartRAID V) with dpt_i2o
Lennart Sorensen wrote: On Wed, Aug 31, 2005 at 03:21:30PM -0700, Neil Gunton wrote: I just built a server which has dual Opteron 265, 4GB RAM, Adaptec 2015S zero-channel RAID controller and 4 x Ultra320 10k SCSI drives. I am having a problem installing Debian amd64, because of the 2015S card. This requires the dpt_i2o driver, which is not included by default in Debian amd64. Well last I looked (2.6.12 kernel), the dpt_i2o driver was listed explicitly as not 64bit compatible and couldn't be selected on any 64bit platform. I have replaced the dpt_i2o files with the new ones provided by Adaptec, but I cannot figure out how to enable the module for selection under x86_64. I tried adding a line to arch/x86_64/configs/defconfig, but this still doesn't make the module come up in the list when I do a 'make menuconfig'. Do you have any idea how to enable the module? Where is the kernel config being told specifically not to include this? I did a grep for DPT_I2O but I couldn't find anything else. I don't know what i2o_blocks is, but I did include the i2o drivers in my Sorry for the typo, I meant i2o_block 2.6.12 based sarge amd64 netinst image. Feel free to try that one if you wish. I have i2o_block, i2o_config, i2o_core, i2o_proc and i2o_scsi included. May have to manually modprobe them from console 2, since I have no idea I the discover data knows to try those for your controller. http://www.tinyplanet.ca/~lsorense/amd64/ I tried this, and it looked promising at first. I was able to modprobe i2o_block and then partition the hard drives, but it failed later when trying to install the kernel, with a message something like this: /usr/bin/mkinitrd: device /dev/i2o/hda/part3 is not a block device Failed to create initrd image In any case, I noticed that the installer was attempting to install linux-image-2.6.12-1-amd64-generic, which makes me nervous - surely this would not have the dpt_i2o driver, and so I would not be able to boot into the system after install? I had an idea to compile the kernel with dpt_i2o under CentOS, since that is working currently under x86_64 and i2o_block. If I was able to include the new dpt_i2o driver in this kernel, and then replaced the one on the stock Debian netinstall disk with the new one, should that work? Would it be able then to see the 2015S using the dpt_i2o module? But then, if the installer still wants to put in a stock kernel then that's no good. I suppose I could then boot into linux rescue and replace the stock kernel with the custom one off the install disk. Might that work? I managed to get hold of Mark Salyzyn at Adaptec, and he sent me source code for the dpt_i2o driver which he tells me should work in 64-bit mode. I could presumably build this into a custom kernel. But I don't know how to do this while installing Debian from scratch. That would be a problem yes. If I knew it would work, I would be willing to add the driver to my installer image's kernel. Could you send me the updated driver to have a look at? Yes, I will send this in a separate email. Thanks for your help! /Neil -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing amd64 on Adaptec 2015S (SmartRAID V) with dpt_i2o
Paul Brook wrote: CentOS 4.1 does work, with i2o_blocks, but I would much rather be running Debian. Please help... You could install debian from your CentOS installations using debootstrap. http://d-i.alioth.debian.org/manual/en.i386/apcs04.html Paul Thanks very much for the pointer. This looks promising, and I am trying it out along with some other avenues... I'll post again once I've worked out the easiest way to bootstrap this system. Thanks again, -Neil -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing amd64 on Adaptec 2015S (SmartRAID V) with dpt_i2o
Am Donnerstag 01 September 2005 20:22 schrieb Neil Gunton: Paul Brook wrote: CentOS 4.1 does work, with i2o_blocks, but I would much rather be running Debian. Please help... You could install debian from your CentOS installations using debootstrap. http://d-i.alioth.debian.org/manual/en.i386/apcs04.html Paul Thanks very much for the pointer. This looks promising, and I am trying it out along with some other avenues... I'll post again once I've worked out the easiest way to bootstrap this system. Thanks again, -Neil I have done this way. Works smooth. Only a bit strange in the /dev/i2o/* :-) Last time i called withe Adaptec they say my that they will not build the dt_i2o on 64 bit. For me the reason my Adaptec 3410 to remove of my maschine. Cu Ryen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing amd64 on Adaptec 2015S (SmartRAID V) with dpt_i2o
On Thu, Sep 01, 2005 at 11:15:54AM -0700, Neil Gunton wrote: I have replaced the dpt_i2o files with the new ones provided by Adaptec, but I cannot figure out how to enable the module for selection under x86_64. I tried adding a line to arch/x86_64/configs/defconfig, but this still doesn't make the module come up in the list when I do a 'make menuconfig'. Do you have any idea how to enable the module? Where is the kernel config being told specifically not to include this? I did a grep for DPT_I2O but I couldn't find anything else. There is a !64BIT somewhere in the DPT_I2O option section you would have to remove. Look for 'config SCSI_DPT_I2O' in drivers/scsi/Kconfig, and a few lines down it has: depends on !64BIT SCSI PCI change that to: depends on SCSI PCI I tried this, and it looked promising at first. I was able to modprobe i2o_block and then partition the hard drives, but it failed later when trying to install the kernel, with a message something like this: /usr/bin/mkinitrd: device /dev/i2o/hda/part3 is not a block device Failed to create initrd image In any case, I noticed that the installer was attempting to install linux-image-2.6.12-1-amd64-generic, which makes me nervous - surely this would not have the dpt_i2o driver, and so I would not be able to boot into the system after install? It does have i2o_block. If that can read the disk, it should work, if mkinitrd had a clue about i2o. Odd, how it says part3 is not a block device. What does 'ls -l /dev/i2o/hda/part3' say then? I had an idea to compile the kernel with dpt_i2o under CentOS, since that is working currently under x86_64 and i2o_block. If I was able to include the new dpt_i2o driver in this kernel, and then replaced the one on the stock Debian netinstall disk with the new one, should that work? Would it be able then to see the 2015S using the dpt_i2o module? But then, if the installer still wants to put in a stock kernel then that's no good. I suppose I could then boot into linux rescue and replace the stock kernel with the custom one off the install disk. Might that work? Yes, I will send this in a separate email. The PCI id from lspci and lspci -n would be nice too. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Installing amd64 on Adaptec 2015S (SmartRAID V) with dpt_i2o
Hi, I just built a server which has dual Opteron 265, 4GB RAM, Adaptec 2015S zero-channel RAID controller and 4 x Ultra320 10k SCSI drives. I am having a problem installing Debian amd64, because of the 2015S card. This requires the dpt_i2o driver, which is not included by default in Debian amd64. An alternative would be the i2o_blocks module. I can install CentOS 4.1 x86_64 using i2o_blocks, but there does not seem to be any way to do this with Debian. I managed to get hold of Mark Salyzyn at Adaptec, and he sent me source code for the dpt_i2o driver which he tells me should work in 64-bit mode. I could presumably build this into a custom kernel. But I don't know how to do this while installing Debian from scratch. So, I see three possibilities, but I don't know how to do any of them: 1. MANUAL MODULE SELECTION: Specify the i2o_blocks module (if it's actually on the install CD) manually at install time with the Debian installer. I can't see any option for this. 2. DRIVER DISK: Compile the dpt_i2o source code and build a driver disk for Debian amd64 (if that's even possible - should I be able to install using 'linux dd' with this port?) 3. CUSTOM KERNEL: Build a custom kernel from CentOS 4.1 x86_64 (which I can install using i2o_blocks) and build in the dpt_i2o driver... but then, even if this works, how then to package up and use this kernel at install time for Debian? CentOS 4.1 does work, with i2o_blocks, but I would much rather be running Debian. Please help... Thanks, -Neil -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing amd64 on Adaptec 2015S (SmartRAID V) with dpt_i2o
CentOS 4.1 does work, with i2o_blocks, but I would much rather be running Debian. Please help... You could install debian from your CentOS installations using debootstrap. http://d-i.alioth.debian.org/manual/en.i386/apcs04.html Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
