WGT634U Tips & Tricks - Revision history

Jeschke: /* New Kernel Howto */

2006-05-13T11:00:32Z

New Kernel Howto

← Older revision		Revision as of 11:00, 13 May 2006
Line 11:		Line 11:
	## '''Attention''': <tt>Kernel hacking</tt> -> <tt>Default kernel command string</tt>, the 2.6.12-rc3 needed <code>console=ttyS1,115200</code> while the 2.6.16 needs <code>console=ttyS0,115200</code> for the serial console. Also: <code>/etc/inittab</code> should be changed to give a shell on <code>tts/0</code>.		## '''Attention''': <tt>Kernel hacking</tt> -> <tt>Default kernel command string</tt>, the 2.6.12-rc3 needed <code>console=ttyS1,115200</code> while the 2.6.16 needs <code>console=ttyS0,115200</code> for the serial console. Also: <code>/etc/inittab</code> should be changed to give a shell on <code>tts/0</code>.
	# Big change: OpenWgt used devfs for its device file system which has been deprecated for some time and is completely removed by now. For the time being you'll need to set up a static <code>/dev</code> directory on your root file system. Simply use tar to pack up a copy of your old <code>/dev</code> and untar it in your root. Note: your root will most likely be readonly, but the logger wants to create its <code>/dev/log</code> socket on startup. Thus you should create a symlink that links <code>/dev/log</code> to <code>/tmp/log</code> (for example).		# Big change: OpenWgt used devfs for its device file system which has been deprecated for some time and is completely removed by now. For the time being you'll need to set up a static <code>/dev</code> directory on your root file system. Simply use tar to pack up a copy of your old <code>/dev</code> and untar it in your root. Note: your root will most likely be readonly, but the logger wants to create its <code>/dev/log</code> socket on startup. Thus you should create a symlink that links <code>/dev/log</code> to <code>/tmp/log</code> (for example).

			== Unionfs for linux-2.6.16 ==
			* UnionFS version 1.1.4 use a broken locking mechanism, so try a snapshot instead, e.g.:
			* Prepare build
			$ wget ftp://ftp.fsl.cs.sunysb.edu/pub/unionfs/snapshots/unionfs-20060503-0408.tar.gz
			$ tar xzf unionfs-20060503-0408.tar.gz
			$ cd unionfs-20060503-0408
			$ ./patch-kernel.sh ~/linux-2.6.16-with-unionfs/
			* Configure kernel
			$ cd ~/linux-2.6.16-with-unionfs/
			$ make menuconfig ARCH=mips (Select "File Systems" -> "Miscellaneous filesystems" -> "<M> Union fs support")
			$ # patch Makefile as described [[MathiasJeschke\|here]], if you don't want debugging stuff -> saves many (useless) code
			* Build kernel (and/or modules)
			$ cat build.sh
			#!/bin/sh

			CROSS_PATH=/home/mj/openwgt-dev/buildroot/build_mipsel/staging_dir/bin/

			make \
			CC=$CROSS_PATH/mipsel-linux-gcc \
			LD=$CROSS_PATH/mipsel-linux-ld \
			AR=$CROSS_PATH/mipsel-linux-ar \
			NM=$CROSS_PATH/mipsel-linux-nm \
			ARCH=mips $*
			$ sh build.sh modules
			$ ls -l fs/unionfs/unionfs.ko
			-rw-r--r-- 1 mj users 111415 2006-05-13 14:33 fs/unionfs/unionfs.ko

Henryk: /* New Kernel Howto */

2006-03-23T19:57:04Z

New Kernel Howto

← Older revision		Revision as of 19:57, 23 March 2006
Line 4:		Line 4:
	# Get the patches for bcm947xx support from OpenWrt's Kamikaze branch at https://dev.openwrt.org/browser/trunk/openwrt/target/linux/brcm-2.6/patches/		# Get the patches for bcm947xx support from OpenWrt's Kamikaze branch at https://dev.openwrt.org/browser/trunk/openwrt/target/linux/brcm-2.6/patches/
	# Apply the patches: <br /><code>$ cd linux-2.6.16<br />$ patch -p1 < <var>/path/to/</var>001-bcm947xx.patch<br />$ patch -p1 < <var>/path/to/</var>002-flash-map.patch<br />$ patch -p1 < <var>/path/to/</var>003-bcm4710_cache_fixes.patch<br />$ patch -p1 < <var>/path/to/</var>004-b44_bcm47xx_support.patch</code>		# Apply the patches: <br /><code>$ cd linux-2.6.16<br />$ patch -p1 < <var>/path/to/</var>001-bcm947xx.patch<br />$ patch -p1 < <var>/path/to/</var>002-flash-map.patch<br />$ patch -p1 < <var>/path/to/</var>003-bcm4710_cache_fixes.patch<br />$ patch -p1 < <var>/path/to/</var>004-b44_bcm47xx_support.patch</code>
	# You may use the .config file (it's in <code>/proc/config.gz</code>) ~~from the old kernel~~, but there are some tweaks to do:		# You may use the .config file from the old kernel (it's in <code>/proc/config.gz</code>), but there are some tweaks to do:
	## <tt>Machine selection</tt> -> <tt>System type: Support for BCM947xx based boards</tt>		## <tt>Machine selection</tt> -> <tt>System type: Support for BCM947xx based boards</tt>
	## <tt>Device drivers</tt> -> <tt>Network device support</tt>: <tt>[] Ethernet (10 or 100Mbit)</tt>, <tt>[] EISA, VLB, PCI and on board controller</tt> -> <tt><*> Broadcom 4400 ethernet support (EXPERIMENTAL)</tt>		## <tt>Device drivers</tt> -> <tt>Network device support</tt>: <tt>[] Ethernet (10 or 100Mbit)</tt>, <tt>[] EISA, VLB, PCI and on board controller</tt> -> <tt><*> Broadcom 4400 ethernet support (EXPERIMENTAL)</tt>
	## (Do ''not'' ~~check~~ <tt>Device drivers</tt> -> <tt>Input device support</tt> -> <tt>Hardware I/O ports</tt> -> <tt>~~< >~~ Serial I/O support</tt>)		## (Do ''not'' enable <tt>Device drivers</tt> -> <tt>Input device support</tt> -> <tt>Hardware I/O ports</tt> -> <tt>Serial I/O support</tt> -> <tt>i8042 PC Keyboard controller</tt>, the kernel would hang while probing for a keyboard controller.)
	## <tt>Device drivers</tt> -> <tt>Character devices</tt> -> <tt>Serial drivers</tt> -> <tt><> 8250/16550 and compatible serial support</tt>, <tt>[] Console on 8250/16550 and compatible serial port</tt>		## <tt>Device drivers</tt> -> <tt>Character devices</tt> -> <tt>Serial drivers</tt> -> <tt><> 8250/16550 and compatible serial support</tt>, <tt>[] Console on 8250/16550 and compatible serial port</tt>
	## '''Attention''': <tt>Kernel hacking</tt> -> <tt>Default kernel command string</tt>, the 2.6.12-rc3 needed <code>console=ttyS1,115200</code> while the 2.6.16 needs <code>console=ttyS0,115200</code> for the serial console. Also: <code>/etc/inittab</code> should be changed to give a shell on <code>tts/0</code>.		## '''Attention''': <tt>Kernel hacking</tt> -> <tt>Default kernel command string</tt>, the 2.6.12-rc3 needed <code>console=ttyS1,115200</code> while the 2.6.16 needs <code>console=ttyS0,115200</code> for the serial console. Also: <code>/etc/inittab</code> should be changed to give a shell on <code>tts/0</code>.

Henryk: WTF634U Tips & Tricks moved to WGT634U Tips & Tricks

2006-03-23T00:35:22Z

WTF634U Tips & Tricks moved to WGT634U Tips & Tricks

← Older revision	Revision as of 00:35, 23 March 2006
(No difference)

Henryk at 00:34, 23 March 2006

2006-03-23T00:34:04Z

New page

= New Kernel Howto =
[http://openwgt.informatik.hu-berlin.de/ OpenWgt] offers the choice of a 2.6.12-rc3 for the linux 2.6 series. This kernel comes from the Tuxap project and is slightly outdated by now. Here's how to get a more recent kernel up and running:
# Get a new kernel (I'll go with 2.6.16) from kernel.org (I used linux-mips.org, but kernel.org should be fine) and unpack it.
# Get the patches for bcm947xx support from OpenWrt's Kamikaze branch at https://dev.openwrt.org/browser/trunk/openwrt/target/linux/brcm-2.6/patches/
# Apply the patches: <code>$ cd linux-2.6.16 $ patch -p1 < <var>/path/to/</var>001-bcm947xx.patch $ patch -p1 < <var>/path/to/</var>002-flash-map.patch $ patch -p1 < <var>/path/to/</var>003-bcm4710_cache_fixes.patch $ patch -p1 < <var>/path/to/</var>004-b44_bcm47xx_support.patch</code>
# You may use the .config file (it's in <code>/proc/config.gz</code>) from the old kernel, but there are some tweaks to do:
## <tt>Machine selection</tt> -> <tt>System type: Support for BCM947xx based boards</tt>
## <tt>Device drivers</tt> -> <tt>Network device support</tt>: <tt>[*] Ethernet (10 or 100Mbit)</tt>, <tt>[*] EISA, VLB, PCI and on board controller</tt> -> <tt><*> Broadcom 4400 ethernet support (EXPERIMENTAL)</tt>
## (Do ''not'' check <tt>Device drivers</tt> -> <tt>Input device support</tt> -> <tt>Hardware I/O ports</tt> -> <tt>< > Serial I/O support</tt>)
## <tt>Device drivers</tt> -> <tt>Character devices</tt> -> <tt>Serial drivers</tt> -> <tt><*> 8250/16550 and compatible serial support</tt>, <tt>[*] Console on 8250/16550 and compatible serial port</tt>
## '''Attention''': <tt>Kernel hacking</tt> -> <tt>Default kernel command string</tt>, the 2.6.12-rc3 needed <code>console=ttyS1,115200</code> while the 2.6.16 needs <code>console=ttyS0,115200</code> for the serial console. Also: <code>/etc/inittab</code> should be changed to give a shell on <code>tts/0</code>.
# Big change: OpenWgt used devfs for its device file system which has been deprecated for some time and is completely removed by now. For the time being you'll need to set up a static <code>/dev</code> directory on your root file system. Simply use tar to pack up a copy of your old <code>/dev</code> and untar it in your root. Note: your root will most likely be readonly, but the logger wants to create its <code>/dev/log</code> socket on startup. Thus you should create a symlink that links <code>/dev/log</code> to <code>/tmp/log</code> (for example).