08-12-2002
There could be two possibilities that causing this problem for you. First, Either the memory timing is not properly set for your device,
or the transmission channel you download your kernel is not clean. Second, corrupted zImage file. This means that while the decompressor was running, it came across bad data which didn't look like a valid gzip file. Possibilities are: bad media where the zImage is stored (eg, flash, ram, etc). Have you checked your Motherboard compatibility status for linux. Best if you could post your dmesg output if you able to get in the System after Linux boots.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hey guys, need some help. Running AIX Version 5.2 and one of our cron jobs is writing errors to a log file. Any ideas on the following error message.
Error: Internal system error: Unable to initialize standard output file
I'm guessing more info might be needed, so let me know.
Thanks (2 Replies)
Discussion started by: firkus
2 Replies
2. UNIX for Advanced & Expert Users
Trying to answer a question about whether tar table-of-contents is a good tool for verifying tape data. (1 Reply)
Discussion started by: tjlst15
1 Replies
3. Solaris
I am getting this error when trying to unzip a file.gz . Anyone know how to resolve this ? (3 Replies)
Discussion started by: jxh461
3 Replies
4. Programming
Hi,
We have packet of size 144 bytes and wants to genrate & check CRC . Can u give the CRC code ? (3 Replies)
Discussion started by: namrata5
3 Replies
5. Programming
hello,
I have implemented a 32bit crc generation algorithm. Now at the receiver side i need to check the crc for that....i need to add the message in the packet and the crc and divide it with the key common at both side and the remainder should be zero.
now how to add crc which is hexadecimal... (4 Replies)
Discussion started by: madfox
4 Replies
6. AIX
--------------------------------------------------------------------------------
Hello, help me please.
I am trying to create a mksysb bakup using nim. I am geting this error, how to correct it ? :
Command : failed stdout: yes stderr: no... (9 Replies)
Discussion started by: astjen
9 Replies
7. Solaris
Hi, I was working on the M3000 and I did a init 0, powered off the system during the weekend. When I tried to poweron today, the XSCF linux boot image keeps on rebooting and does not go to the login for XSCF access. The "Check" LED is on amber. Tried diagnosing but cant get the system up. Any help... (1 Reply)
Discussion started by: incredible
1 Replies
8. Programming
Good Evening,
I started working on the 17x17 4-colouring challenge, and I ran into a bit of an I/O snag.
It was an enormous headache to detect the differences in very similar 289-char strings.
Eventually, it made more sense to associate a CRC-Digest with each colouring.
After learning... (0 Replies)
Discussion started by: HeavyJ
0 Replies
9. UNIX for Dummies Questions & Answers
im kinda new to shell scripting so i need some help
i try to run this script and get the error code
> 5 ")syntax error: operand expected (error token is "
the code for the script is
#!/bin/sh
#
# script to see if the given value is correct
#
# Define errors
ER_AF=86 # Var is... (4 Replies)
Discussion started by: metal005
4 Replies
10. Shell Programming and Scripting
unzip -v gives CRC info of each file in a zip(in my case .EAR) file.
# unzip -v my-application.ear
Archive: my-application.ear
Length Method Size Cmpr Date Time CRC-32 Name
-------- ------ ------- ---- ---------- ----- -------- ----
197981 Defl:N 183708 7%... (1 Reply)
Discussion started by: kchinnam
1 Replies
LEARN ABOUT SUNOS
mkfs.minix
MKFS.MINIX(8) System Administration MKFS.MINIX(8)
NAME
mkfs.minix - make a Minix filesystem
SYNOPSIS
mkfs.minix [options] device [size-in-blocks]
DESCRIPTION
mkfs.minix creates a Linux MINIX filesystem on a device (usually a disk partition).
The device is usually of the following form:
/dev/hda[1-8] (IDE disk 1)
/dev/hdb[1-8] (IDE disk 2)
/dev/sda[1-8] (SCSI disk 1)
/dev/sdb[1-8] (SCSI disk 2)
The device may be a block device or a image file of one, but this is not enforced. Expect not much fun on a character device :-).
The size-in-blocks parameter is the desired size of the file system, in blocks. It is present only for backwards compatibility. If omit-
ted the size will be determined automatically. Only block counts strictly greater than 10 and strictly less than 65536 are allowed.
OPTIONS
-c, --check
Check the device for bad blocks before creating the filesystem. If any are found, the count is printed.
-n, --namelength length
Specify the maximum length of filenames. Currently, the only allowable values are 14 and 30 for file system versions 1 and 2. Ver-
sion 3 allows only value 60. The default is 30.
-i, --inodes number
Specify the number of inodes for the filesystem.
-l, --badblocks filename
Read the list of bad blocks from filename. The file has one bad-block number per line. The count of bad blocks read is printed.
-1 Make a Minix version 1 filesystem. This is the default.
-2, -v Make a Minix version 2 filesystem.
-3 Make a Minix version 3 filesystem.
-V, --version
Display version information and exit. The long option cannot be combined with other options.
-h, --help
Display help text and exit.
EXIT CODES
The exit code returned by mkfs.minix is one of the following:
0 No errors
8 Operational error
16 Usage or syntax error
SEE ALSO
fsck(8), mkfs(8), reboot(8)
AVAILABILITY
The mkfs.minix command is part of the util-linux package and is available from https://www.kernel.org/pub/linux/utils/util-linux/.
util-linux June 2015 MKFS.MINIX(8)