WGT634U Tips & Tricks: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
m (WTF634U Tips & Tricks moved to WGT634U Tips & Tricks) |
(No difference)
|
Revision as of 00:35, 23 March 2006
New Kernel Howto
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:
$ cd linux-2.6.16
$ patch -p1 < /path/to/001-bcm947xx.patch
$ patch -p1 < /path/to/002-flash-map.patch
$ patch -p1 < /path/to/003-bcm4710_cache_fixes.patch
$ patch -p1 < /path/to/004-b44_bcm47xx_support.patch - You may use the .config file (it's in
/proc/config.gz
) from the old kernel, but there are some tweaks to do:- Machine selection -> System type: Support for BCM947xx based boards
- Device drivers -> Network device support: [*] Ethernet (10 or 100Mbit), [*] EISA, VLB, PCI and on board controller -> <*> Broadcom 4400 ethernet support (EXPERIMENTAL)
- (Do not check Device drivers -> Input device support -> Hardware I/O ports -> < > Serial I/O support)
- Device drivers -> Character devices -> Serial drivers -> <*> 8250/16550 and compatible serial support, [*] Console on 8250/16550 and compatible serial port
- Attention: Kernel hacking -> Default kernel command string, the 2.6.12-rc3 needed
console=ttyS1,115200
while the 2.6.16 needsconsole=ttyS0,115200
for the serial console. Also:/etc/inittab
should be changed to give a shell ontts/0
.
- 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
/dev
directory on your root file system. Simply use tar to pack up a copy of your old/dev
and untar it in your root. Note: your root will most likely be readonly, but the logger wants to create its/dev/log
socket on startup. Thus you should create a symlink that links/dev/log
to/tmp/log
(for example).