uncleflo
Registered since September 28th, 2017
Has a total of 4246 bookmarks.
Showing top Tags within 4 bookmarks
howto information development guide reference administration design website software solution service product online business uk tool company linux code server system application web list video marine create data experience description tutorial explanation technology build blog article learn world project boat download windows security lookup free performance javascript technical network control beautiful support london tools course file research purchase library programming image youtube example php construction html opensource quality install community computer profile feature power browser music platform mobile user process work database share manage hardware professional buy industry internet dance advice installation developer 3d search access customer material camera travel test standard review documentation css money engineering develop webdesign engine device photography digital api speed source program management phone discussion question event client story simple water marketing yacht app content setup package fast idea interface account communication cheap compare script study market live easy google resource operation startup monitor training
Tag selected: scsi.
Looking up scsi tag. Showing 4 results. Clear
Device map - GNU GRUB Manual 2.00~rc1
Saved by uncleflo on August 31st, 2013.
If the device map file exists, the GRUB utilities (grub-probe, grub-setup, etc.) read it to map BIOS drives to OS devices. This file consists of lines like this: (device) file Device is a drive specified in the GRUB syntax (see Device syntax), and file is an OS file, which is normally a device file. Historically, the device map file was used because GRUB device names had to be used in the configuration file, and they were derived from BIOS drive numbers. The map between BIOS drives and OS devices cannot always be guessed correctly: for example, GRUB will get the order wrong if you exchange the boot sequence between IDE and SCSI in your BIOS.
device file manual grub map bios drive configuration boot os scsi guess administration linux
How do i know the BIOS number for my SCSI disks
Saved by uncleflo on August 30th, 2013.
The contribution from Marc Tanguy (mtanguy@ens.uvsq.fr), 2001-09-27. If you have an adaptec scsi card (2940u2, 29160, 39160), you simply use the 'diagnose' mode (using BIOS v3.10.0 recommended). It must be activated in the scsi card BIOS menu. If you don't own an adaptec card, you have to know what is the 'booting' disk (usually ID 0, but not necessary, it can be defined in the scsi card BIOS) where LILO is going to be found and start : this is the first disk so it has number 0x80. Then it's very simple, the BIOS follows the IDs.
configuration hardware system operating development administration os partition adaptec menu card boot id number disk scsi bios linux grub lilo
Result Linux patch/support for: RevoDrive3, RevoDrive3 X2, zDrive R4
Saved by uncleflo on January 26th, 2012.
After a friend bought a RevoDrive3 120GB without doing much research, I got annoyed that there wasn't any Linux support, so I looked at the Windows driver and wrote in some Linux support. Written & tested remotely on his machine, in 6 hours on a Saturday afternoon. It _should_ work for RevoDrive3, RevoDrive X2 as well as zDrive R4, as they all seem to use the same Marvell 88SE9485 part and Sandforce 2281 or 2582 together. My patch has been submitted to the linux-kernel, linux-scsi, linux-ide mailing lists for review and inclusion. http://www.spinics.net/lists/linux-scsi/msg54932.html Anybody that wants to use it, you need to apply the linked/attached patch on top of a kernel at least v3.1-rc1 or newer.
linux development patch bios support revodrive zdrive marvell sandforce kernel scsi ubuntu
[PATCH] mv_sas: OCZ RevoDrive3 & zDrive R4 support (Linux SCSI)
Saved by uncleflo on January 26th, 2012.
In the OCZ RevoDrive3/zDrive R4 series, the "OCZ SuperScale Storage Controller" with "Virtualized Controller Architecture 2.0" really seems to be a Marvell 88SE9485 part, with OCZ firmware/BIOS. Developed and tested on OCZ RevoDrive3 120GB [PCI 1b85:1021] Should work on: - OCZ RevoDrive3 (2x SandForce 2281) - OCZ RevoDrive3 X2 (4x SandForce 2281) - OCZ zDrive R4 CM84 (4x SandForce 2281) - OCZ zDrive R4 CM88 (8x SandForce 2281) - OCZ zDrive R4 RM84 (4x SandForce 2582) - OCZ zDrive R4 RM88 (8x SandForce 2582) All of this because a friend recently bought a OCZ RevoDrive3 and was bitten by the lack of Linux support.
linux compile support scsi revodrive zdrive ocz patch code development storage controller architecture marvell bios firmware
No further bookmarks found.