Results 1 - 10 of 352 m systems diskonchip 2000 free download - WinASO Registry Optimizer, registry errors, clean history record, and speed up the system. Results 1 - 10 of 352 . m systems diskonchip 2000 free download - WinASO Registry Optimizer. Using M- Systems Disk. On. Chip 2. 00. 0 TSOP as an additional storage drive in Linux. The following are the steps performed for this purpose. Step 1: Patch the Kernel. Download a fresh copy of Kernel 2. The kernel that is downloaded from the site does not have support for the M- Systems driver so we need to add this functionality. This is done by adding a patch to the kernel. The steps to conduct patching are as follows: Untar the kernel source file and the M- systems True. FFS Linux driver version 5. If the source code is in . Урок алгебры построен таким образом, что достаточно много времени отводится на повторение изученных ранее функций, графиков этих функций и их основных свойств. Это впоследствии. Мых систем не осталось без внимания и было. установкой в систему нужда If the source code is in . After using bunzip. Untar it using the commandtar - xvflinux- 2. Unarchiving the driver is done using the commandtar - xvzflinux_binary. This results in the creation of two directories: linux and linux_binary. The True. FFS Linux driver package contains three different folders: Documentation: this contains a PDF document describing the various functions of True. FFS. dformat_5_1_4_3. Disk. On. Chip (DOC) and to create low level partitions on the DOC. Now apply the patch to the kernel. We will use the linux- 2_4_7- patch file that is present in linux_binary. The following commands are used for this purpose: cd linux_binary. This will create a directory named doc in the linux/drivers/block directory. The patch created the doc directory, but did not copy the source files of the M- Systems driver, which are necessary in order to build the driver, into this directory. So execute the following command: cp linux_binary. Kernel version The patch will fail for kernels other than 2. The patch has been provided specifically for kernel 2. Before moving on to Step 2, do the following: Login as root. Make sure that gcc version is 2. Use gcc - -version to check this. If your gcc version is different compile gcc- 2. Refer to http: //xlife. Step 2: Compile the Kernel. Complete the following tasks for compiling the kernel: cd linuxmake menuconfig. Check for the following options: In the "Block devices menu", select: M- Systems driver as module i. M)Loopback device support as built- in i. RAM disk support as built- in i. Initial RAM disk (initrd) support as built . In the "Processor type and features menu", select "Disable Symmetric Multiprocessor Support". In the "filesystem menu", select: Ext. DOS FAT fs support as built- ina. MSDOS fs support as built- inb. VFAT (Windows- 9. File System Menu a,b,c options should be activated if you want to mount your MS Windows partition, else they can be left out. It is, however, generally recommended to use them. An excellent resource on kernel compilation is the Kernel Rebuild Guide. The configuration file, linux/. Loadable module support. CONFIG_MODULES=y. CONFIG_MODVERSIONS=y. Processor type and features. CONFIG_SMP is not set. Memory Technology Devices (MTD). CONFIG_MTD is not set. Block devices. # CONFIG_BLK_DEV_FD is not set. CONFIG_BLK_DEV_XD is not set. CONFIG_PARIDE is not set. CONFIG_BLK_CPQ_DA is not set. CONFIG_BLK_CPQ_CISS_DA is not set. CONFIG_BLK_DEV_DAC9. CONFIG_BLK_DEV_LOOP=y. CONFIG_BLK_DEV_NBD is not set. CONFIG_BLK_DEV_RAM=y. CONFIG_BLK_DEV_RAM_SIZE=4. CONFIG_BLK_DEV_INITRD=y. CONFIG_BLK_DEV_MSYS_DOC=m. CONFIG_QUOTA is not set. CONFIG_AUTOFS_FS is not set. CONFIG_AUTOFS4_FS is not set. CONFIG_EXT3_FS=y. CONFIG_FAT_FS=y. CONFIG_MSDOS_FS=y. CONFIG_UMSDOS_FS is not set. CONFIG_VFAT_FS=y. CONFIG_EFS_FS is not set. CONFIG_JFFS_FS is not set. CONFIG_JFFS2_FS is not set. CONFIG_CRAMFS is not set. CONFIG_RAMFS is not set. CONFIG_ISO9. 66. 0_FS=y. CONFIG_JOLIET is not set. CONFIG_HPFS_FS is not set. CONFIG_PROC_FS=y. CONFIG_DEVFS_FS is not set. CONFIG_DEVFS_MOUNT is not set. CONFIG_DEVFS_DEBUG is not set. CONFIG_DEVPTS_FS=y. CONFIG_QNX4. FS_FS is not set. CONFIG_QNX4. FS_RW is not set. CONFIG_ROMFS_FS is not set. CONFIG_EXT2_FS=y. Imagemake modulesmake modules_install. Copy the newly created bz. Image to the /bott directory and name it vmlinuz- 2. Image /boot/vmlinuz- 2. Check for lib/modules/2. This is the M- Systems driver that we need to access Disk. On. Chip. 4. 3. Step 3: Create Nodes. Now we will create block devices, which are required to access the DOC. These block devices will use the M- Systems driver that was built in Section 4. DOC. The script mknod_fl in linux_binary. We need to create the block devices with the major number of 6. For this purpose we will pass the argument 6. This will create the following devices in /dev/msys with major number 6. Step 4: Reboot with the new kernel. In order to have the Disk. On. Chip recognized by Linux OS, we need to insert the DOC driver module into the kernel. Since the currently running kernel doesn. M- Systems Driver, we need to boot into new kernel we just compiled in . For this purpose we need to add the following entries in the /boot/grub/menu. Debian GNU/Linux,Kernel 2. Where (hd. 0,7) is the partition holding the kernel image vmlinuz- 2. These partitions may vary from one system to another. Now reboot and choose the kernel 2. Step 2) in the grub menu to boot into the new kernel. Step 5: Insert M- Systems Driver/Module in the new Kernel. The M- Systems driver by default gets loaded with major number 1. Section 4. 3) have a major number 6. Therefore we need to insert this module with a major number 6. This can be done in either of two ways: While inserting the module using insmod also mention the major number for the module which needs to be assigned to it otherwise it will take the default major number of 1. Add the following line to /etc/modules. Then use modprobe doc to insert the modules. Check for the correct loading of the module using the lsmod command without options. Step 6: Create a filesystem on the Disk. On. Chip. Before we can start using Disk. On. Chip we need to create a filesystem on it. We will create an ext. This involves a hidden step of making partitions on the DOC using fdisk. The actual steps are as follows: fdisk /dev/msys/fla. This command will ask to create partitions. Create a primary partition number 1 with start cylinder as 1 and final cylinder as 1. Check the partition table, which should look like this. Device Boot Start End Blocks ID System. Linux. Make the filesystem on /dev/msys/fla. Where fla. 1 is the first primary partition on the DOC. We have created only one partition in order to avoid unnecessary complexity.)4. Step 7: Mount the newly created partition to start accessing DOCCreate a new mount point for the Disk. On. Chip in the /mnt directory: mkdir /mnt/doc. Mount the DOC partition on the newly created directory: mount - tauto/dev/msys/fla. You will now be able to read and write to the DOC as an additional storage drive. When you reboot your system, make the DOC available by inserting the driver into the kernel (see Section 4.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2016
Categories |