[bb] NFS環境を作りたいがうまくいかない

うまくいかんシリーズです。
前回から続けている、BeagleBoardをNFSブートさせたいというお話。
bootargsがよくないのでうまくいっていないのかと思ったが、ログを見るとUSB-LANを認識し終わっていないときにやろうとしているのか？という気がした。

Linux version 2.6.32 (xxxx@xxxx) (gcc version 4.4.3 (GCC) ) #14 Mon Oct 10 21:13:36 JST 2011 CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c53c7f CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache Machine: OMAP3 Beagle Board Memory policy: ECC disabled, Data cache writeback OMAP3430/3530 ES3.1 (l2cache iva sgx neon isp 720m ) SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000 Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 25146 Kernel command line: mem=99M console=ttyS2,115200n8 noinitrd ip=192.168.0.22::255.255.255.0::eth0 rw root=/dev/nfs nfsroot=192.168.0.2:/home/xxx/Qt/nfs,nolock,rsize=1024,wsize=1024 mpurate=600 omapfb.rotate=1 omapfb.vrfb=y vram=10M omapfb.vram=0:10M omapdss.def_disp=dvi omapfb.mode=dvi:720x480MR-16@60 Booting kernel: `0:10M' invalid for parameter `omapfb.vram' PID hash table entries: 512 (order: -1, 2048 bytes) Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 99MB = 99MB total Memory: 94904KB available (4312K code, 811K data, 168K init, 0K highmem) Hierarchical RCU implementation. NR_IRQS:402 Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz Reprogramming SDRC clock to 332000000 Hz GPMC revision 5.0 IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupts Total of 96 interrupts on 1 active controller OMAP GPIO hardware version 2.5 OMAP clockevent source: GPTIMER12 at 32768 Hz Console: colour dummy device 80x30 Calibrating delay loop... 516.77 BogoMIPS (lpj=2019328) Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok regulator: core version 0.5 NET: Registered protocol family 16 Found NAND on CS0 Registering NAND on CS0 Unable to get DVI reset GPIO Target VDD1 OPP = 5, VDD2 OPP = 3 OMAP DMA hardware revision 4.0 bio: create slab <bio-0> at 0 SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz twl4030: PIH (irq 7) chaining IRQs 368..375 twl4030: power (irq 373) chaining IRQs 376..383 twl4030: gpio (irq 368) chaining IRQs 384..401 regulator: VUSB1V5: 1500 mV normal standby regulator: VUSB1V8: 1800 mV normal standby regulator: VUSB3V1: 3100 mV normal standby twl4030_usb twl4030_usb: Initialized TWL4030 USB module regulator: VMMC1: 1850 <--> 3150 mV normal standby regulator: VDAC: 1800 mV normal standby regulator: VPLL2: 1800 mV normal standby regulator: VSIM: 1800 <--> 3000 mV normal standby regulator: VAUX3: 1800 mV normal standby regulator: VAUX4: 1800 mV normal standby i2c_omap i2c_omap.2: bus 2 rev3.12 at 100 kHz i2c_omap i2c_omap.3: bus 3 rev3.12 at 100 kHz Switching to clocksource 32k_counter musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0 musb_hdrc: USB OTG mode controller at fa0ab000 using DMA, IRQ 92 NET: Registered protocol family 2 IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 4096 (order: 3, 32768 bytes) TCP bind hash table entries: 4096 (order: 2, 16384 bytes) TCP: Hash tables configured (established 4096 bind 4096) TCP reno registered UDP hash table entries: 256 (order: 0, 4096 bytes) UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) NET: Registered protocol family 1 RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. NetWinder Floating Point Emulator V0.97 (double precision) ashmem: initialized VFS: Disk quotas dquot_6.5.2 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) msgmni has been set to 185 alg: No test for stdrng (krng) io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654 serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654 serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654 console [ttyS2] enabled brd: module loaded loop: module loaded pegasus: v0.6.14 (2006/09/27), Pegasus/Pegasus II USB Ethernet driver usbcore: registered new interface driver pegasus ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver ehci-omap ehci-omap.0: OMAP-EHCI Host Controller ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1 ehci-omap ehci-omap.0: irq 77, io mem 0x48064800 ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00 hub 1-0:1.0: USB hub found hub 1-0:1.0: 3 ports detected Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. usbcore: registered new interface driver usbserial usbserial: USB Serial Driver core USB Serial support registered for cp210x usbcore: registered new interface driver cp210x cp210x: v0.09:Silicon Labs CP210x RS232 serial adaptor driver USB Serial support registered for FTDI USB Serial Device usbcore: registered new interface driver ftdi_sio ftdi_sio: v1.5.0:USB FTDI Serial Converters Driver USB Serial support registered for pl2303 usbcore: registered new interface driver pl2303 pl2303: Prolific PL2303 USB to serial adaptor driver android init android_probe pdata: c048f2dc android_bind android_usb gadget: android_usb ready musb_hdrc musb_hdrc: MUSB HDRC host driver musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 2 hub 2-0:1.0: USB hub found hub 2-0:1.0: 1 port detected f_adb init android_register_function adb adb_bind_config f_mass_storage init android_register_function usb_mass_storage f_accessory init android_register_function accessory mice: PS/2 mouse device common for all mice input: gpio-keys as /devices/platform/gpio-keys/input/input0 using rtc device, twl_rtc, for alarms twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0 twl_rtc twl_rtc: Power up reset detected. twl_rtc twl_rtc: Enabling TWL-RTC. i2c /dev entries driver Linux video capture interface: v2.00 sn9c102: V4L2 driver for SN9C1xx PC Camera Controllers v1:1.47pre49 usbcore: registered new interface driver sn9c102 usbcore: registered new interface driver uvcvideo USB Video Class driver (v0.1.0) mmci-omap-hs mmci-omap-hs.1: err -16 configuring card detect usbcore: registered new interface driver usbhid usbhid: USB HID core driver logger: created 64K log 'log_main' logger: created 256K log 'log_events' logger: created 64K log 'log_radio' logger: created 64K log 'log_system' usb 1-2: new high speed USB device using ehci-omap and address 2 Advanced Linux Sound Architecture Driver Version 1.0.21. No device for DAI omap-mcbsp-dai-0 No device for DAI omap-mcbsp-dai-1 No device for DAI omap-mcbsp-dai-2 No device for DAI omap-mcbsp-dai-3 No device for DAI omap-mcbsp-dai-4 OMAP3 Beagle SoC init asoc: twl4030 <-> omap-mcbsp-dai-0 mapping ok ALSA device list:   #0: omap3beagle (twl4030) TCP cubic registered NET: Registered protocol family 17 NET: Registered protocol family 15 Power Management for TI OMAP3. Switched to new clocking rate (Crystal/Core/MPU): 26.0/332/600 MHz IVA2 clocking rate: 430 MHz SmartReflex driver initialized VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1 regulator_init_complete: incomplete constraints, leaving VAUX3 on regulator_init_complete: incomplete constraints, leaving VDVI on regulator_init_complete: incomplete constraints, leaving VDAC on twl_rtc twl_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800) hub 1-2:1.0: USB hub found hub 1-2:1.0: 4 ports detected usb 1-2.2: new full speed USB device using ehci-omap and address 3 mmc0: new high speed SD card at address b368 mmcblk0: mmc0:b368 SDC   1.85 GiB mmcblk0: p1 pegasus 1-2.2:1.0: setup Pegasus II specific registers IP-Config: No network devices available. pegasus 1-2.2:1.0: eth0, MELCO/BUFFALO LUA2-TX, 00:40:26:c0:bf:af Looking up port of RPC 100003/2 on 192.168.0.2

pegasusというのは、うちで使っているUSB-LANの「LUA2-TX」だ。
昔、実家でADSLを引けそうだったので買ったけど、距離が遠すぎて回線につなげられず、放置されていたのだ。
赤文字にしたところが、ちょうどデバイス認識の前後に挟まっているのか、NFSを使いたいからデバイスを認識し始めたのか知らないが、いずれにせよ間に合っていないように見える。

nfsとは関係ないが、bootargsに関するエラーも気になる。

Booting kernel: `0:10M' invalid for parameter `omapfb.vram'

Documentation/arm/OMAP/DSSには、こう書いてある。

omapfb.vram=<fbnum>:<size>[@<physaddr>][,...]

fb0に対してやってるんだけどなあ。
まあ、後で調べよう。