Page 1 of 10 123 ... LastLast
Results 1 to 10 of 99

Thread: Got Knoppix 5.0.1 successfully booting from USB key

  1. #1
    Member registered user
    Join Date
    Mar 2006
    Posts
    50

    Got Knoppix 5.0.1 successfully booting from USB key

    Knoppix 5.0.1 boots rather nicely from a USB key. It's getting easier to get it working, as the USB bugs from the previous versions have been fixed.

    I have a 1GB USB key, so using the Knoppix CD was the best fit (the DVD is much too large).

    Here's a rather long thread I started a while ago, about getting an older version of Knoppix up and running: http://www.knoppix.net/forum/viewtopic.php?t=23558

    I've simplified that somewhat. Here's a mini-guide:

    * Boot Knoppix 5.0.1 from CD and make sure it works.

    Put in your USB key as soon as possible, when you see the title screen of Knoppix, so that it is sure to be found by Knoppix autodetection.

    Do not use the "toram" cheatcode when booting Knoppix. The RAM copy of the CD omits the /boot directory, but we require this directory, so we can't use the RAM copy.

    * Once Knoppix is up and running, open a root shell (from the penguin icon). Now, we need to find the drive letter of your USB key. It will be something like /dev/sda, /dev/sdb, /dev/sdc, and so on. Be very careful and make absolutely sure you have the drive letter correct, because you will be erasing the USB key, and you don't want to erase your hard drive by mistake!

    Commands to try:

    Code:
    dmesg | grep -i scsi
    Code:
    cat /proc/partitions
    Look at the sizes of the various drives you see here. Find your USB key, and do not get it confused with your hard drive! For the rest of this example, I'm going to be using /dev/sdz, a fictional drive letter that nobody has, just to prevent bad mistakes from typing in commands blindly.

    * Erase the entire USB key.

    Code:
    dd if=/dev/zero of=/dev/sdz
    Did you use the right drive letter? Did you? If not, you'll be crying, right about now....

    This command will take a while to finish. By writing to every block on the USB key, we are also testing it for bad blocks.

    You should get the "no space left on device" error message when it finishes erasing and reaches the end of the drive. Any other error messages might mean bad blocks: if you notice any, your key might be worn out and you'll need to buy another one (cheap keys are notorious for wearing out very quickly).

    * Make a quick patch to the mkdiskimage script.

    We need it to write partition type 0C (FAT32 LBA). Unfortunately, "out of the box" it only writes partition type 0B (FAT32 CHS). We want to make sure Windows always uses LBA and not CHS, for increased reliability, just in case we ever use the USB key with Windows. So, an easy one-line change.

    Use your favorite editor and edit /usr/bin/mkdiskimage.

    Code:
    vi /usr/bin/mkdiskimage
    Go to line 237.

    Change 0x0b to 0x0c then save the file and exit.

    * Run mkdiskimage, to automatically partition and format your USB key.

    Code:
    mkdiskimage -F -4 /dev/sdz 0 64 32
    This lays down a new MBR and partition table on the drive, and partitions and formats the entire drive as one big FAT32 LBA partition. I prefer FAT32 because it is a more efficient use of space than FAT16, and have noticed no difference in the ability of various systems to boot FAT32 as opposed to FAT16.

    The mkdiskimage script is USB-ZIP compliant, which may help it boot on more systems than USB-HDD. It's nice that Knoppix now includes this script by default. Here's the webpage for mkdiskimage: http://syslinux.zytor.com/usbkey.php

    KDE may throw a stupid popup window in your face, once it recognizes your new partition. If this happens, close the window.

    * Run the SYSLINUX installer on your new partition.

    Code:
    syslinux -s /dev/sdz4
    This installs the SYSLINUX bootloader onto the newly-created partition, and includes a special file, ldlinux.sys. The -s option is for safety and additional compatibility. Notice the partition is the fourth partition on the drive, not the first. This is for USB-ZIP compliance.

    * Mount your new partition.

    Code:
    mount /media/sdz4
    Knoppix should have autodetected the new partition and set up a fstab entry for it. The /media/sdz4 directory should now correspond to the /dev/sdz4 partition.

    Code:
    cd /media/sdz4
    ls
    You should notice one, and only one, file in this directory now: ldlinux.sys

    If you don't see this, then something probably went wrong earlier. Go back and try again before continuing.

    * Copy the contents of the Knoppix CD's boot directory, onto your USB key.

    You should already be in the /media/sdz4 directory, from the cd command above.

    Code:
    cp -av /cdrom/boot/isolinux/* .
    mv isolinux.cfg syslinux.cfg
    rm -f isolinux.bin
    Don't forget the dot on the end. It tells the cp command to copy everything into your current directory, which is what we want. Notice that there is a space between the asterisk and the dot!

    Ignore any errors about "failed to preserve ownership". This is normal, because we're using the FAT filesystem, which does not support file ownership. This is not a problem for us.

    What we're doing here is copying the Knoppix CD's /boot directory first. This increases reliability, by getting it as close to the beginning of the drive as possible. This should help on systems with buggy CHS handling of USB keys, which may become an issue as new USB keys get larger.

    We are renaming Knoppix's isolinux.cfg file to syslinux.cfg, and then removing the unnecessary isolinux.bin file. ISOLINUX (used to boot the CD) and SYSLINUX (what we just installed to your USB key) are really two different variations of the same bootloader program. They accept the same config file format, so we don't need to change anything at all, just rename.

    BTW, since ISOLINUX has isolinux.bin as its main program file, can you guess what is the equivalent file for SYSLINUX? If you guessed ldlinux.sys, the file you saw earlier, good job!

    * Finish copying the rest of the Knoppix CD.

    Again, you should still be in the /media/sdz4 directory. Again, don't forget the dot on the end of this command.

    Code:
    cp -av /cdrom/* .
    rm -rf ./boot
    This should take a while. We are filling up the USB key with the contents of the Knoppix CD.

    We already copied Knoppix's /boot directory earlier, in the previous step. We don't need two copies of it just wasting space, so we remove the extra copy.

    * You are now ready to boot!

    Cleanly unmount the USB key.

    Code:
    sync
    cd /
    umount /media/sdz4
    Shut down Knoppix, and remove the CD when it tells you to.

    * Reset your computer and fiddle with the BIOS until it sees the USB key.

    After unmounting above, the USB key can be removed. Some BIOS's require a removal and re-insertion before they will recognize it.

    Other things to try, if you're having trouble getting the BIOS to see your USB key and let you boot from it:

    Try a different USB port. Some BIOS's only search a few ports, not all of them.

    Hit a special key to bring up a boot menu. Some BIOS's can only boot from USB when manually selected.

    Go into your BIOS's setup menu, and walk through the boot settings. Look under all menus, especially "hard drives" and "removable devices" and other things like that. Some BIOS's will not search for newly attached devices until you manually go through the menus again.

    Turn your computer completely off and on again. Some BIOS's require you to physically turn the computer off and on again, before they will see newly attached drives.

    If all else fails, try a different PC. It's still fairly rare these days to find a computer that has a good ability to boot from USB devices, and it's not something that motherboard makers advertise, so it takes a bit of luck to find a computer that can do this.

    * Boot into Knoppix from your USB key.

    If it works, that's great. Notice how much faster it is. There's zero seek time on a USB key, so even though it isn't very fast, it feels a lot faster than the CD! Programs are surprisingly quick to load.

    Find the drive letter for your USB key again. It should not change, but it might have.

    * Make a persistent home directory, if you want.

    Knoppix assumes that the "CD-ROM" that it booted from is impossible to write to, but we have a USB key now, not a CD-ROM. So, we must fool Knoppix into letting you write to it.

    Code:
    mount -o remount,rw /cdrom
    mount --bind /cdrom /media/sdz4
    Now, we can run the Knoppix persistent home utility.

    (It's under the penguin menu, Configure, Create Persistent.)

    Choose your drive from the menu that appears, and follow the instructions.

    The program should complete without errors. If the program suddenly disappears midway through, check the kernel logs with "dmesg" again. If you see pagefuls of SCSI errors and such, beware, you might have a worn-out USB key!

    * Modify the Knoppix boot menu.

    This is an optional step, for customization. We want Knoppix to autofind the persistent home directory, and fix a few other things.

    You might have to repeat the above mounting steps, as the Knoppix persistent tool might randomly unmount the directory sometimes.

    Code:
    vi /media/sdz4/syslinux.cfg
    On line 3, the default timeout is 300. Lower this, to around 50 or so (5 seconds, since this counter is in tenths of seconds).

    It's nice to have it boot faster, without waiting for you to hit Enter, so you can put in the USB key and walk away, coming back in a few minutes to a fully booted system.

    On line 2, add a few more options to the end of the line.

    noswap noeject noprompt dma home=scan

    Here's a little explanation of what each option does.
    noswap = Security fix: assuming you're going to be using the USB key on a bunch of different computers you don't own, you don't want to be swapping your memory onto their hard drives.
    noeject = You can't physically eject a USB key.
    noprompt = Gets rid of the "remove CD and close drive door" prompt when shutting down, as this prompt is rather misleading when it's really a USB key instead.
    dma = Gets you a significant speed increase when dealing with many IDE drives, a good thing to have.
    home=scan = This will cause Knoppix to pick up your persistent home directory automatically the next time you boot up, asking you for the password as needed. You will get an extra menu during bootup, asking you if you want to mount your home directory or not.

    Save the file and quit the editor.

    Now, you should be all set. Reboot again, to make sure it all works.

    Enjoy your Knoppix-on-a-keychain!

    Josh

  2. #2
    Administrator Site Admin-
    Join Date
    Apr 2003
    Location
    USA
    Posts
    5,441

    Re: Got Knoppix 5.0.1 successfully booting from USB key

    What a great write-up. I hope that you will consider putting a copy in the wiki where it will be easy for people to find.

    Quote Originally Posted by Krellan2
    ...The mkdiskimage script is USB-ZIP compliant, which may help it boot on more systems than USB-HDD. ...
    I'm particularly interested in this. My HP notebook has an option in the BIOS to boot from USB, but I have not yet managed to get it to boot a usb flash drive. My latest attempts were with the configuration that DSL writes to flash. Everything looked good, but it just would not boot (nor would it boot on an IBM laptop that I had a chance to try it on). I'm wondering if this is the issue. Can you explain how we can determine if a flash drive has been configured USB-ZIP or USB-HDD? Are there any trade-off we should know about? Unfortunatey, at this time my largest flash drive is 512 meg, too small for Knoppix. I would gladly buy a larger one if I thought that my notebook would boot it, but my bad experiences so far have discouraged me from buying a larger flash device; I have no use for more flash devices other that putting together a bootable Linux on flash (doesn't even have to be Knoppix, DSL or Puppy would be fine if I could get them to boot.) Can you suggest any test I can do with a smaller flash device (64, 256 or 512 meg) to confirm that my notebook will indeed boot a flash device?

  3. #3
    Member registered user
    Join Date
    Mar 2006
    Posts
    50

    Re: Got Knoppix 5.0.1 successfully booting from USB key

    Quote Originally Posted by Harry Kuhman
    What a great write-up. I hope that you will consider putting a copy in the wiki where it will be easy for people to find.
    Thanks. I am working on debugging one problem on a certain machine, but after that, I'll attempt making a wiki page.

    I'm particularly interested in this. My HP notebook has an option in the BIOS to boot from USB, but I have not yet managed to get it to boot a usb flash drive. My latest attempts were with the configuration that DSL writes to flash. Everything looked good, but it just would not boot (nor would it boot on an IBM laptop that I had a chance to try it on). I'm wondering if this is the issue. Can you explain how we can determine if a flash drive has been configured USB-ZIP or USB-HDD? Are there any trade-off we should know about?
    USB-ZIP and USB-HDD are both attempts to solve a problem: the BIOS expects all "disk" devices to have a traditional cylinder/head/sector count (CHS), but USB key s don't have this. Like most modern drives, they're just a total count of sectors (LBA). There's no need for the old cylinder/head/sector nonsense, but try telling that to the blunderheads who seem to be programming most BIOS's these days!

    USB-ZIP attempts to simulate the layout of a ZIP drive: 64 heads, 32 sectors, and a variable number of cylinders depending on the size of the drive. In addition, ZIP drives use partition four (for whatever demented reason Iomega chose in the past). USB-ZIP was basically a hack to let a BIOS that was capable of booting from a ZIP drive, boot also from a USB key, with minimal reprogramming effort. Such is the state of the BIOS industry these days, I'm sad to say.

    USB-HDD simply relaxes these restrictions. USB-HDD is supported by fewer BIOS's than USB-ZIP, however, so it's a tradeoff for compatibility. USB-ZIP will let your key boot up in more computers, so for now, it's the one to use.

    You can change between USB-ZIP and USB-HDD by rewriting your partition table on the disk, and then reformatting.

    Unfortunatey, at this time my largest flash drive is 512 meg, too small for Knoppix. I would gladly buy a larger one if I thought that my notebook would boot it, but my bad experiences so far have discouraged me from buying a larger flash device; I have no use for more flash devices other that putting together a bootable Linux on flash (doesn't even have to be Knoppix, DSL or Puppy would be fine if I could get them to boot.) Can you suggest any test I can do with a smaller flash device (64, 256 or 512 meg) to confirm that my notebook will indeed boot a flash device?
    I'm not sure. The main reason I bought a 1GB USB key was to put a complete bootable "CD" on it

    Maybe you can try it with a remastered Knoppix that cuts down on the optional software (such as DSL). I haven't tried this myself.

  4. #4
    Administrator Site Admin-
    Join Date
    Apr 2003
    Location
    USA
    Posts
    5,441

    Re: Got Knoppix 5.0.1 successfully booting from USB key

    Quote Originally Posted by Krellan2
    ....You can change between USB-ZIP and USB-HDD by rewriting your partition table on the disk, and then reformatting.

    ....Maybe you can try it with a remastered Knoppix that cuts down on the optional software (such as DSL). I haven't tried this myself.
    Most of what you wrote should be able to be cut and pasted into a wiki article pretty cleanly although code blocks and the like will take different formatting. But in the end it will be an easy thing for people to find; old forum posts tend to sink in the listings and are seldom see if they are not on the first page.

    Thanks for the additional information. Let me ask my question a different way though. What in the partition table is it that flags USB-ZIP or USB-HDD? Lets assume I can byte edit the table, what bits or bytes am I looking for to tell me which I have?

    DSL was one of the smaller bootable systems that didn't work for me (along with a few others, but the others were more convoluted to make and I could have done something wrong). Could I just hex edit the partition table to change from USB-HDD to USB-ZIP, or are the actual partitions different as well?

    Give me low lever details, I can take it.

  5. #5
    Member registered user
    Join Date
    Mar 2006
    Posts
    50

    Re: Got Knoppix 5.0.1 successfully booting from USB key

    Quote Originally Posted by Harry Kuhman
    Thanks for the additional information. Let me ask my question a different way though. What in the partition table is it that flags USB-ZIP or USB-HDD? Lets assume I can byte edit the table, what bits or bytes am I looking for to tell me which I have?

    DSL was one of the smaller bootable systems that didn't work for me (along with a few others, but the others were more convoluted to make and I could have done something wrong). Could I just hex edit the partition table to change from USB-HDD to USB-ZIP, or are the actual partitions different as well?

    Give me low lever details, I can take it.
    In the partition table, it's the CHS information. Ending CHS must be a size of */64/32. This is the biggie, as it seems the BIOS gets its CHS sizing information from what's read from the partition table! Starting CHS should probably be the standard 0/1/1, with starting LBA to match. Ending LBA should be truncated to match the ending CHS, so unfortunately, you end up losing a few KB from your USB key. But, it's worth it, if doing so lets it boot!

    Your data partition must also be partition 4, and marked active. I haven't found a difference in filesystem type, as the BIOS should only care about this silly CHS information, and leave filesystems up to the OS.

    Here's my partition table, as seen by "fdisk":

    Code:
    Disk /dev/sda: 64 heads, 32 sectors, 977 cylinders
    
    Nr AF  Hd Sec  Cyl  Hd Sec  Cyl     Start      Size ID
     1 00   0   0    0   0   0    0          0          0 00
     2 00   0   0    0   0   0    0          0          0 00
     3 00   0   0    0   0   0    0          0          0 00
     4 80   1   1    0  63  32  976         32    2000864 0c
    The hex dump (notice partitions 1, 2, 3 are all blank):

    Code:
    00000130  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
    *
    000001e0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 80 01
    000001f0  01 00 0c 3f e0 d0 20 00  00 00 e0 87 1e 00 55 aa
    Notice I lose a little capacity from what my key really can hold:

    Code:
    SCSI device sda: 2001888 512-byte hdwr sectors (1025 MB)
    Good luck! There's lots more to read online if you Google: "USB-ZIP" "USB-HDD"
    (do not forget the quotation marks)

    Josh

  6. #6
    Administrator Site Admin-
    Join Date
    Apr 2003
    Location
    USA
    Posts
    5,441
    Thanks.
    ---
    Verifying of md5 checksum and burning a CD at slow speed are important.

  7. #7
    Junior Member
    Join Date
    Sep 2006
    Posts
    1

    Parted USB Disk

    Great info. And here's to not paying attention (me that is).
    After redoing the whole setup several times, using syslinux but also trying grub, i just couldn't get the damn thing to boot.
    My desktop has extensive BIOS so tried everything under the sky but to no avail....
    Then, when dinner was on the table i left the machine to try and boot from the flash for the umpth time, it booted up hdd ubuntu, intead of knoppix dvd, and to my surprise i got 2 (TWO) usb-drive icons on my ubuntu (6.06) desktop.....that didn't show in knoppix...!!??

    Opening both showed the "secret" (RTFM?) of the USB Disk Pro: I has a floppy-sized primary partition which holds a password/encryption tool to secure the second partition. Auto-format the key when 3 wrong pwds are given etc. That's why it never booted.
    On XP it mounts as floppy and Removable, but i never noticed the floppy......

    Time to sort out how to repartition the whole flash key.....later more on this.
    Right now ubuntu mounts them as sda4 (after using mkdiskimage) 1027MB, and sdb 1MB

    Edit: Think i'm screwed with this one. It appears to have firmware installed. The tool on the flash key: UDPV264.exe, i found a newer version, wich has an extra option of resizing the secure area, but trying to use that it stated Firmware not supporting option. How to get this mother to work.....to start i looks to behave as a usb-hub, ie 2 separate devices, sda and sdb.....

    Sep 8 22:25:10 Acer kernel: usb 1-1: new full speed USB device using uhci_hcd and address 3
    Sep 8 22:25:10 Acer kernel: usb 1-1: configuration #1 chosen from 1 choice
    Sep 8 22:25:10 Acer kernel: scsi1 : SCSI emulation for USB Mass Storage devices
    Sep 8 22:25:15 Acer kernel: Vendor: Model: USB DISK Pro Rev: PMAP
    Sep 8 22:25:15 Acer kernel: Type: Direct-Access ANSI SCSI revision: 00
    Sep 8 22:25:16 Acer kernel: SCSI device sda: 2006016 512-byte hdwr sectors (1027 MB)
    Sep 8 22:25:16 Acer kernel: sda: Write Protect is off
    Sep 8 22:25:16 Acer kernel: sda: assuming drive cache: write through
    Sep 8 22:25:16 Acer kernel: SCSI device sda: 2006016 512-byte hdwr sectors (1027 MB)
    Sep 8 22:25:16 Acer kernel: sda: Write Protect is off
    Sep 8 22:25:16 Acer kernel: sda: assuming drive cache: write through
    Sep 8 22:25:16 Acer kernel: sda: sda4
    Sep 8 22:25:16 Acer kernel: sd 1:0:0:0: Attached scsi removable disk sda
    Sep 8 22:25:16 Acer kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0
    Sep 8 22:25:16 Acer kernel: Vendor: Model: USB DISK Pro Rev: PMAP
    Sep 8 22:25:16 Acer kernel: Type: Direct-Access ANSI SCSI revision: 00
    Sep 8 22:25:16 Acer kernel: SCSI device sdb: 2880 512-byte hdwr sectors (1 MB)
    Sep 8 22:25:16 Acer kernel: sdb: Write Protect is off
    Sep 8 22:25:16 Acer kernel: sdb: assuming drive cache: write through
    Sep 8 22:25:16 Acer kernel: SCSI device sdb: 2880 512-byte hdwr sectors (1 MB)
    Sep 8 22:25:16 Acer kernel: sdb: Write Protect is off
    Sep 8 22:25:16 Acer kernel: sdb: assuming drive cache: write through
    Sep 8 22:25:16 Acer kernel: sdb: unknown partition table
    Sep 8 22:25:16 Acer kernel: sd 1:0:0:1: Attached scsi removable disk sdb
    Sep 8 22:25:16 Acer kernel: sd 1:0:0:1: Attached scsi generic sg1 type 0

  8. #8
    Senior Member registered user
    Join Date
    Sep 2006
    Posts
    802
    I have followed the advice completely, but my new ASUS A3Hf was not able to boot from the 1GB Corsair USB stick. I can, however, boot with a 512MB Corsair wirh DSL 3.0.1 installed, so there may be something with some BIOS'es not working well with the larger sticks.

    BUT, I'm writing this running that USB install. How could I boot it? By using GRUB already installed on the hard disk, just added an entry in /boot/grub/menu.lst for booting from the USB. Have to fix some parameters, though, because Knoppix came up completely German

    So, the method clearly works well for transferring Knoppix to a USB, but we may still not be able to boot from it. A way out of this may be to install GRUB on a CD, with different options for booting different devices. Then we only need to use the CD for starting up. I think that method may be worthwhile to explore, because USB booting really seems to be an unpredictable mess right now.

  9. #9
    Member registered user
    Join Date
    Mar 2006
    Posts
    50

    Re: Parted USB Disk

    Quote Originally Posted by /-/oek
    Time to sort out how to repartition the whole flash key.....later more on this.
    Right now ubuntu mounts them as sda4 (after using mkdiskimage) 1027MB, and sdb 1MB
    I thought you could get away with just blowing it all away by writing zeroes to the entire drive with "dd", but since it shows up as two devices, probably not. It's not a standard USB key: it's something else that is "smarter", unfortunately.

    Edit: Think i'm screwed with this one. It appears to have firmware installed. The tool on the flash key: UDPV264.exe, i found a newer version, wich has an extra option of resizing the secure area, but trying to use that it stated Firmware not supporting option. How to get this mother to work.....to start i looks to behave as a usb-hub, ie 2 separate devices, sda and sdb.....
    If you can get the firmware tool running, maybe you can get rid of the "secure area" entirely. Then, if it just shows up as a single device, you can erase that and just use it as a single drive.

  10. #10
    Member registered user
    Join Date
    Mar 2006
    Posts
    50
    Quote Originally Posted by Capricorny
    I have followed the advice completely, but my new ASUS A3Hf was not able to boot from the 1GB Corsair USB stick. I can, however, boot with a 512MB Corsair wirh DSL 3.0.1 installed, so there may be something with some BIOS'es not working well with the larger sticks.
    That's the same reason I bought a 1GB drive for $58, when 2GB drives were just $80, not all that much more.

    I don't trust the BIOS to boot pretty much anything right these days, and going over 1GB would break the USB-ZIP standard, as it would then go over 1024 "cylinders". So, I'm sticking with my 1GB drive.

    BUT, I'm writing this running that USB install. How could I boot it? By using GRUB already installed on the hard disk, just added an entry in /boot/grub/menu.lst for booting from the USB. Have to fix some parameters, though, because Knoppix came up completely German
    That's clever, but kind of defeats my purpose of wanting Knoppix bootable on a USB key: to be able to take it to all different computers everywhere, and have something that I can still boot from, no matter what's on the hard disk.

    I think that method may be worthwhile to explore, because USB booting really seems to be an unpredictable mess right now.
    That's putting it mildly. I'm amazed at the sheer incompetence of BIOS programmers these days. I really wish the BIOS would be split up into two parts: the motherboard-specific stuff that the motherboard maker puts in (the BSP), and then, a generic part that does all the menus, booting, etc. that people could reprogram and fix bugs on.

Page 1 of 10 123 ... LastLast

Similar Threads

  1. Successfully installed Oracle 10g on Knoppix 3.4
    By rahulreddy in forum Tips and Tricks
    Replies: 6
    Last Post: 07-06-2006, 07:37 PM
  2. Successfully remastered 3.9 with rebuilt kernel and unionfs
    By Pallbearer in forum Customising & Remastering
    Replies: 1
    Last Post: 08-06-2005, 04:53 PM
  3. knoppix successfully detects eth0 and eth1 and ra0 appears
    By paradigm_shift in forum Networking
    Replies: 0
    Last Post: 07-15-2005, 05:41 AM
  4. Howto successfully "mkbootfloppy" with kernel 2.6
    By larrycow in forum Customising & Remastering
    Replies: 1
    Last Post: 11-16-2004, 05:52 PM
  5. Successfully boots from hard-drive... BUT...
    By Ewen in forum General Support
    Replies: 1
    Last Post: 05-03-2003, 07:49 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Supermicro 4U 36 Bay Storage Server 2.4Ghz 8-C 128GB 1x1280W Rails TrueNAS ZFS picture

Supermicro 4U 36 Bay Storage Server 2.4Ghz 8-C 128GB 1x1280W Rails TrueNAS ZFS

$721.06



H261-Z61 2U 24SFF AMD Server 8x EPYC 7551 256-Cores 256GB RAM 8x25G NIC 2x2200W picture

H261-Z61 2U 24SFF AMD Server 8x EPYC 7551 256-Cores 256GB RAM 8x25G NIC 2x2200W

$2512.18



CSE-118 Supermicro 1U 3x GPU Server  2.1Ghz 16-C 128GB CX353A 2x1600W PSU Rails picture

CSE-118 Supermicro 1U 3x GPU Server 2.1Ghz 16-C 128GB CX353A 2x1600W PSU Rails

$450.03



Dell PowerEdge R630 8SFF 2.6Ghz 20-Core 128GB Mem 4x1G RJ-45 NIC 2x750W PSU picture

Dell PowerEdge R630 8SFF 2.6Ghz 20-Core 128GB Mem 4x1G RJ-45 NIC 2x750W PSU

$399.04



Dell PowerEdge R720XD Xeon E5-2680 V2 2.8GHz 20 Cores 256GB RAM 12x4TB picture

Dell PowerEdge R720XD Xeon E5-2680 V2 2.8GHz 20 Cores 256GB RAM 12x4TB

$510.00



DELL PowerEdge R730 Server 2x E5-2690v3 2.6GHz =24 Cores 32GB H730 4xRJ45 picture

DELL PowerEdge R730 Server 2x E5-2690v3 2.6GHz =24 Cores 32GB H730 4xRJ45

$275.00



Dell PowerEdge R730XD 28 Core Server 2X Xeon E5-2680 V4 H730 128GB RAM No HDD picture

Dell PowerEdge R730XD 28 Core Server 2X Xeon E5-2680 V4 H730 128GB RAM No HDD

$389.99



SuperMicro Server 505-2 Intel Atom 2.4GHz 8GB RAM SYS-5018A-FTN4 1U Rackmount picture

SuperMicro Server 505-2 Intel Atom 2.4GHz 8GB RAM SYS-5018A-FTN4 1U Rackmount

$224.99



Dell PowerEdge R430 3.5 1U 2x E5-2690 v3 2.6ghz 24-Cores 256gb 4x Trays 2x 550w picture

Dell PowerEdge R430 3.5 1U 2x E5-2690 v3 2.6ghz 24-Cores 256gb 4x Trays 2x 550w

$289.99



HP Proliant DL360 Gen9 28 Core SFF Server 2X E5-2680 V4 16GB RAM P440ar No HDD picture

HP Proliant DL360 Gen9 28 Core SFF Server 2X E5-2680 V4 16GB RAM P440ar No HDD

$191.95