FAQ/Obsolete - Revision history

Uwe: Move -fno-stack-protector stuff here.

2010-09-26T18:05:34Z

Move -fno-stack-protector stuff here.

Uwe: Moved here from Section overlaps.

2010-09-26T14:29:36Z

Moved here from Section overlaps.

Uwe at 22:56, 4 March 2007

2007-03-04T22:56:22Z

Uwe: Move sis630 item.

2007-03-04T22:50:34Z

Move sis630 item.

Uwe: Move testbios FAQ.

2007-03-04T22:44:04Z

Move testbios FAQ.

Show changes

Uwe: Move obsolete FAQ items to FAQ/Obsolete. Leave them there, because maybe someone still finds the information useful.

2007-03-04T22:38:59Z

Move obsolete FAQ items to FAQ/Obsolete. Leave them there, because maybe someone still finds the information useful.

New page

== Probably Obsolete FAQ Items ==

=== How do I burn a DoC? ===

A DoC (Disk on Chip) is a storage device aiming at serving as both boot-ROM and background storage (CF disk) to save circuit board space and pin-count, e.g. in a digital camera.

Currently, only the DoC Millennium is supported. See the documentation.

=== How do I put a filesystem on DoC? ===

OK, here is a little HOWTO on how to set up MTD with a file system.

This is a m810lmr, booting out of DoC. I am going to reserve the first 2M for kernel. So the layout will be the first 2M for linuxbios and kernel, and 6M for a file system. Kernel is 2.4.17, with linux-2.4.17-sis.patch from linuxbios source tree, and config-2.4.17-sis from the linuxbios source tree. Mainboard is the pcchips m810lmr.

So I:
modprobe doc2001
modprobe docprobe
dmesg

which shows:

DiskOnChip Millennium found at address 0xFFFC8000
Flash chip found: Manufacturer ID: 98, Chip ID: E6 (Toshiba TC58V64AFT/DC)
1 flash chips found. Total DiskOnChip size: 8 MiB
mtd: Giving out device 0 to DiskOnChip Millennium
Ignoring DiskOnChip Millennium at 0xFFFCA000 - already configured
Ignoring DiskOnChip Millennium at 0xFFFCC000 - already configured
Ignoring DiskOnChip Millennium at 0xFFFCE000 - already configured
Ignoring DiskOnChip Millennium at 0xFFFD0000 - already configured
Ignoring DiskOnChip Millennium at 0xFFFD2000 - already configured
Ignoring DiskOnChip Millennium at 0xFFFD4000 - already configured
Ignoring DiskOnChip Millennium at 0xFFFD6000 - already configured
(etc..)
Now I need MTD utilities.
So I:
cvs -d :pserver:anoncvs@cvs.infradead.org:/home/cvs login
CVS password:

(password is anoncvs)
Then:
cvs -d :pserver:anoncvs@cvs.infradead.org:/home/cvs co mtd

Forget the drivers and such, you don't need them. What you need is the tools.
cd mtd/tools
make

Go ahead and copy the executables somewhere handy, you'll need them.

Now we need to make the last 6M into a "disk". We need to format it. The tool is nftl_format, so:

[root@carly util]# ./nftl_format
$Id: nftl_format.c,v 1.17 2001/08/29 14:28:48 dwmw2 Exp $
Usage: ./nftl_format [ []]
[root@carly util]# expr 2048 \* 1024
2097152
[root@carly util]# expr 6 \* 1024 \* 1024
6291456
[root@carly util]# ./nftl_format /dev/mtd0 2097152 6291456
$Id: nftl_format.c,v 1.17 2001/08/29 14:28:48 dwmw2 Exp $
Phase 1. Checking and erasing Erase Zones from 0x00200000 to 0x00800000
Phase 2.a Writing NFTL Media Header and Bad Unit Table
Phase 2.b Writing Spare NFTL Media Header and Spare Bad Unit Table
Phase 3. Writing Unit Control Information to each Erase Unit

we now have a formatted disk in there. We can now partition it.

[root@carly util]# modprobe nftl

dmesg shows LOTS of errors, since this was never partitioned ...

Also, if you don't have /dev/nftla,

[root@carly util]# mknod /dev/nftla b 93 0

Don't use the script just yet, it makes /dev/nftla as b 93 16, which is the wrong unit #.

now fdisk /dev/nftla

[root@carly util]# fdisk /dev/nftlA
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-1, default 1):
Using default value 1
Command (m for help): p
Disk /dev/nftlA: 1 heads, 12224 sectors, 1 cylinders
Units = cylinders of 12224 * 512 bytes
Device Boot Start End Blocks Id System
/dev/nftlA1 1 1 6111+ 83 Linux
Partition 1 has different physical/logical endings:
phys=(768, 0, 0) logical=(0, 0, 12224)
Partition 1 does not end on cylinder boundary:
phys=(768, 0, 0) should be (768, 0, 12224)
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
WARNING: If you have created or modified any DOS 6.x partitions, please see the fdisk manual page for additional information.
Syncing disks.
[root@carly util]# mknod /dev/nftlA1 b 93 1
[root@carly util]# mke2fs /dev/nftlA1
mke2fs 1.23, 15-Aug-2001 for EXT2 FS 0.5b, 95/08/09
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
1528 inodes, 6111 blocks
305 blocks (4.99%) reserved for the super user
First data block=1
1 block group
8192 blocks per group, 8192 fragments per group
1528 inodes per group
Writing inode tables: done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 37 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override.

[root@carly util]# mount /dev/nftlA1 /mnt
[root@carly util]# cd /mnt
[root@carly mnt]# df .
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/nftlA1 5915 13 5597 1% /mnt
[root@carly mnt]#

and so you now have an ext2 file system on the DoC.

(Above is from [[User:Rminnich|Ron Minnich]])

← Older revision		Revision as of 18:05, 26 September 2010
Line 1:		Line 1:
	This is a collections of old (and maybe obsolete by now) FAQ items. We still keep them, as they might still be useful for some people.		This is a collections of old (and maybe obsolete by now) FAQ items. We still keep them, as they might still be useful for some people.
		+
		+	=== How do I fix __stack_chk_fail errors? ===
		+
		+	If compilation fails with errors like
		+
		+	vtxprintf.c:(.text+0x4eb2): undefined reference to `__stack_chk_fail'
		+
		+	you will need to disable the stack protector that is now enabled by default in the version of GCC shipped with some distros (e.g. Ubuntu).
		+
		+	This should not be necessary anymore for coreboot v4 and payloads (such as [[FILO]]) as our Makefiles already handle this. Should you still encounter such an error message, please report a bug on the [[Mailinglist\|mailing list]]. Basically you can fix this error by adding the '''-fno-stack-protector''' compiler option.

	=== How do I fix the "section overlaps" error in v2? ===		=== How do I fix the "section overlaps" error in v2? ===

← Older revision		Revision as of 14:29, 26 September 2010
Line 1:		Line 1:
	This is a collections of old (and maybe obsolete by now) FAQ items. We still keep them, as they might still be useful for some people.		This is a collections of old (and maybe obsolete by now) FAQ items. We still keep them, as they might still be useful for some people.
		+
		+	=== How do I fix the "section overlaps" error in v2? ===
		+
		+	'''The problem:'''
		+
		+	Section overlaps happen when a part of the v2 image has become too big. Usually, the error message looks like the example shown below:
		+
		+	/usr/bin/ld: section .id [<font style="color: #0000ff">00000000ffffef64</font> -> 00000000ffffef7f] overlaps section .rom [00000000ffff5d33 -> <font style="color: #00ff00">00000000fffff0cf</font>]
		+	/usr/bin/ld: coreboot: section .id lma 0xffffef64 overlaps previous sections
		+
		+	'''The fix, #1:'''
		+
		+	To understand the fix, you have to know that .rom sections have a start address you can set indirectly by setting ROM_IMAGE_SIZE. Since the overlap happens at the end of section .rom, you want to move the start of section .rom to a lower address, preferably only so much that the image fits exactly.
		+
		+	Take the address of the <font style="color: #00ff00">end of section .rom</font> and subtract the address of the <font style="color: #0000ff">beginning of section .id</font>, round it up a bit and increase ROM_IMAGE_SIZE by that amount. That should fix the problem in almost every case.
		+
		+	'''The fix, #2:'''
		+
		+	In case you want to take a different angle, calculate the size of section .rom and set ROM_IMAGE_SIZE to that size. This should work as well. Thanks to Harald Gutmann for that pointer.

	=== How do I set up testbios? ===		=== How do I set up testbios? ===

← Older revision		Revision as of 22:56, 4 March 2007
Line 1:		Line 1:
−	~~== Probably Obsolete~~ FAQ ~~Items ==~~	+	This is a collections of old (and maybe obsolete by now) FAQ items. We still keep them, as they might still be useful for some people.

	=== How do I set up testbios? ===		=== How do I set up testbios? ===

← Older revision		Revision as of 22:50, 4 March 2007
Line 349:		Line 349:

	(Above is from [[User:Rminnich\|Ron Minnich]])		(Above is from [[User:Rminnich\|Ron Minnich]])
		+
		+	=== How do I turn off embedded sis630 devices? ===
		+
		+	From aip@cwlinux.com Mon Mar 25 08:54:07 2002
		+	Date: Mon, 25 Mar 2002 22:07:54 +0800
		+	From: Andrew Ip
		+	To: Kei Furuuchi
		+	Cc: linuxbios@lanl.gov
		+	Subject: Re: How to turn off unused pci device.
		+	Hi,
		+	> I have pcchips m758lmr which has audio chip besides sis630.
		+	> those functions in sis630 are not used in the motherboard.
		+	> But, the functions keep coming up. How do I turn off those?
		+	The following is from Nikolai Valdych previous message. Hope this help.
		+	-Andrew
		+	--
		+	Andrew Ip
		+	Email: aip@cwlinux.com
		+	Actualy, it was pretty simple 0x7c00 - All devices enabled, You play with first 4 bits only. Cos there are 4 devices, so you have any combination of 4 bits.
		+	Set bit to 1 to turn off the device, bit 0 to enable it.
		+	This is the device list:
		+	Multimedia Audio controler
		+	Modem controler
		+	Ethernet sis930 controler
		+	USB controler.
		+	For example, to turn off Ethernet + USB it would be:
		+	0x7c0c -> 1100 in binary (first 4 bits)
		+	To turn off Multimedia audio :
		+	0x7c01 -> 0001
		+	in binary and so on... maybe there are more detail, but this is enogh for me, Ollie, again thanks!
		+	nikolai
		+	p.s. though my modem is not yet working..... damn driver......