Configuring for Static IP Addressing

Products Support DragonBoard410c
#1

I’ve got my 410c up and running on the developer image running out of the SD card. I’m using a USB-to-Ethernet dongle and I have networking working. I’d like to configure it for static IP but when i try to edit the interfaces file in /etc/network and need to change the file permissions, I get an error:
root@linaro-developer:/etc/network# chmod 660 interfaces
chmod: changing permissions of ‘interfaces’: Read-only file system

Is this the right approach? Why can’t I change the permission write on this file?

Thanks.

#2

well, you can’t , exactly because of the error above. rootfs seems to be mounted read-only. so, the question is why is that… can you provide the entire boot log, ideally from UART console, otherwise the output of dmesg.

which SD Boot image are you using?

#3

The Debian Developer latest build.
I couldn’t upload it as a file due to the forum not allowing .log or .txt file uploads.

Should I just copy and paste my serial port output here?

#4

Maybe this is enough to give you a clue?
I noticed several errors and failures so I tried to copuy what I hope are teh relevenrt sections. Let me know if you want teh whole boot log pasted in here.
Thanks for your help!

[ 2.777154] ALSA device[ 2.785421] Freeing unused kernel memory: 1024K (ffff800000eb0000 - ffff800000fb0000)
Loading, please wait…
starting version 232
[ 3.042281] usb 1-1: new high-speed USB device number 2 using msm_hsusb_host
[ 3.191668] hub 1-1:1.0: USB hub found
[ 3.191820] hub 1-1:1.0: 3 ports detected
Begin: Loading essential drivers … done.
Begin: Running /scripts/init-premount … done.
Begin: Mounting root file system … Begin: Running /scripts/local-top … done.
Begin: Running /scripts/local-premount … done.
Begin: Will now check root file system … fsck from util-linux 2.29.2
fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/mmcblk1p9
fsck exited with status code 8
done.
Warning: File system check failed but did not detect errors
[ 3.482273] usb 1-1.2: new high-speed USB device number 3 using msm_hsusb_host
[ 3.595859] hub 1-1.2:1.0: USB hub found
[ 3.596073] hub 1-1.2:1.0: 4 ports detected
[ 3.886307] usb 1-1.2.1: new low-speed USB device number 4 using msm_hsusb_host
[ 4.029823] input: USB Keyboard as /devices/platform/soc/78d9000.ehci/usb1/1-1/1-1.2/1-1.2.1/1-1.2.1:1.0/0003:04D9:1702.0001/input/input2
[ 4.088037] hid-generic 0003:04D9:1702.0001: input: USB HID v1.10 Keyboard [ USB Keyboard] on usb-78d9000.ehci-1.2.1/input0
[ 4.108605] input: USB Keyboard as /devices/platform/soc/78d9000.ehci/usb1/1-1/1-1.2/1-1.2.1/1-1.2.1:1.1/0003:04D9:1702.0002/input/input3
[ 4.166865] hid-generic 0003:04D9:1702.0002: input: USB HID v1.10 Device [ USB Keyboard] on usb-78d9000.ehci-1.2.1/input1
[ 4.250393] usb 1-1.2.2: new low-speed USB device number 5 using msm_hsusb_host
[ 4.368166] input: Logitech Optical USB Mouse as /devices/platform/soc/78d9000.ehci/usb1/1-1/1-1.2/1-1.2.2/1-1.2.2:1.0/0003:046D:C016.0003/input/input4
[ 4.368741] hid-generic 0003:046D:C016.0003: input: USB HID v1.10 Mouse [Logitech Optical USB Mouse] on usb-78d9000.ehci-1.2.2/input0
[ 4.462287] usb 1-1.2.4: new high-speed USB device number 6 using msm_hsusb_host
[ 5.014871] asix 1-1.2.4:1.0 eth0: register ‘asix’ at usb-78d9000.ehci-1.2.4, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:4a:2c:66
[ 5.036222] asix 1-1.2.4:1.0 enx0050b64a2c66: renamed from eth0
[ 5.353324] coresight-replicator-qcom 824000.replicator: REPLICATOR 1.0 initialized
[ 5.358638] coresight-etm4x 85c000.etm: ETM 4.0 initialized
[ 5.362603] coresight-etm4x 85d000.etm: ETM 4.0 initialized
[ 5.368074] coresight-etm4x 85e000.etm: ETM 4.0 initialized
[ 5.372501] coresight-etm4x 85f000.etm: ETM 4.0 initialized
[ 8.325977] mmcblk1: error -84 transferring data, sector 1970208, nr 8, cmd response 0x900, card status 0xc00
[ 18.398281] mmc1: Timeout waiting for hardware interrupt.
[ 18.398327] sdhci: =========== REGISTER DUMP (mmc1)===========
[ 18.402676] sdhci: Sys addr: 0x00000008 | Version: 0x00002e02
[ 18.408403] sdhci: Blk size: 0x00007004 | Blk cnt: 0x00000000
[ 18.414217] sdhci: Argument: 0x00000000 | Trn mode: 0x00000013
[ 18.420034] sdhci: Present: 0x03f80206 | Host ctl: 0x0000001f
[ 18.425849] sdhci: Power: 0x00000001 | Blk gap: 0x00000000
[ 18.431666] sdhci: Wake-up: 0x00000000 | Clock: 0x00000007
[ 18.437481] sdhci: Timeout: 0x0000000a | Int stat: 0x00000000
[ 18.443297] sdhci: Int enab: 0x02ff900b | Sig enab: 0x02ff100b
[ 18.449112] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[ 18.454929] sdhci: Caps: 0x322dc8b2 | Caps_1: 0x00008007
[ 18.460744] sdhci: Cmd: 0x0000163a | Max curr: 0x00000000
[ 18.466559] sdhci: Host ctl2: 0x0000800b
[ 18.472377] sdhci: ADMA Err: 0x00000003 | ADMA Ptr: 0x00000000b8061218
[ 18.476455] sdhci: ===========================================
[ 18.585144] mmc1: Reset 0x1 never completed.
[ 18.585182] sdhci: =========== REGISTER DUMP (mmc1)===========
[ 18.588490] sdhci: Sys addr: 0x00000000 | Version: 0x00002e02
[ 18.594131] sdhci: Blk size: 0x00004000 | Blk cnt: 0x00000000
[ 18.599947] sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
[ 18.605763] sdhci: Present: 0x01f80000 | Host ctl: 0x00000000
[ 18.611578] sdhci: Power: 0x00000000 | Blk gap: 0x00000000
[ 18.617395] sdhci: Wake-up: 0x00000000 | Clock: 0x00000003
[ 18.623212] sdhci: Timeout: 0x00000000 | Int stat: 0x00000000
[ 18.629027] sdhci: Int enab: 0x00000000 | Sig enab: 0x00000000
[ 18.634843] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[ 18.640659] sdhci: Caps: 0x322dc8b2 | Caps_1: 0x00008007
[ 18.646475] sdhci: Cmd: 0x00000000 | Max curr: 0x00000000
[ 18.652289] sdhci: Host ctl2: 0x00000000
[ 18.658106] sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x0000000000000000
[ 18.662184] sdhci: ===========================================
[ 18.886296] mmcblk1: error -84 transferring data, sector 1970208, nr 8, cmd response 0x900, card status 0xc00
[ 28.894282] mmc1: Timeout waiting for hardware interrupt.
[ 28.894325] sdhci: =========== REGISTER DUMP (mmc1)===========
[ 28.898674] sdhci: Sys addr: 0x00000008 | Version: 0x00002e02
[ 28.904402] sdhci: Blk size: 0x00007004 | Blk cnt: 0x00000000
[ 28.910216] sdhci: Argument: 0x00000000 | Trn mode: 0x00000013
[ 28.916032] sdhci: Present: 0x03f80206 | Host ctl: 0x0000001f
[ 28.921849] sdhci: Power: 0x00000001 | Blk gap: 0x00000000
[ 28.927665] sdhci: Wake-up: 0x00000000 | Clock: 0x00000007
[ 28.933480] sdhci: Timeout: 0x0000000a | Int stat: 0x00000000
[ 28.939296] sdhci: Int enab: 0x02ff900b | Sig enab: 0x02ff100b
[ 28.945112] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[ 28.950929] sdhci: Caps: 0x322dc8b2 | Caps_1: 0x00008007
[ 28.956745] sdhci: Cmd: 0x0000163a | Max curr: 0x00000000
[ 28.962559] sdhci: Host ctl2: 0x0000800b
[ 28.968376] sdhci: ADMA Err: 0x00000003 | ADMA Ptr: 0x00000000b8061218
[ 28.972453] sdhci: ===========================================
[ 28.981028] blk_update_request: I/O error, dev mmcblk1, sector 1970208
[ 28.984686] Buffer I/O error on dev mmcblk1p9, logical block 196608, lost sync page write
[ 28.991214] JBD2: Error -5 detected when updating journal superblock for mmcblk1p9-8.
[ 28.999739] EXT4-fs warning (device mmcblk1p9): ext4_clear_journal_err:4670: Filesystem error recorded from previous mount: IO failure
[ 29.007261] EXT4-fs warning (device mmcblk1p9): ext4_clear_journal_err:4671: Marking fs in need of filesystem check.
[ 29.044181] mmcblk1: error -84 transferring data, sector 397344, nr 8, cmd response 0x900, card status 0xc00
[ 39.134282] mmc1: Timeout waiting for hardware interrupt.

#5

yeah… something is really going bad with this SD card. It could be this specific SD card, or the SD card type.

do you have a line like that in your bootlog:

[ 17.213647] mmc1: new ultra high speed SDR104 SDHC card at address 0007

just to see how the kernel detects the card? Do you know the model type (speed, bus, …)? Any chance you can try with a different card? Maybe a regluar SD Card (i mean non UHS)?

#6

It’s a Sandisk 16GB. Part # SDSDQAD-016. I tried in two boards with two of the same type SD card. Same result. I can’t look for that line right now but I’ll get back to you. I’ll order a different card and try that. Non UHS are harder to find but I located one.

Thanks.

#7

I too have had some difficulties with some Class 10 SDCards. I hadn’t gotten to the bottom of it, but here are a couple examples:

2150×700 381 KB

1658×576 353 KB

In both cases the card on the left works with no problems, and the card on the right doesn’t work. It is not all class U3 cards that fail, just some of them.

The 64GB on the right mounts and looks ok, but when I used gdisk to change the partition table the write fails. I wanted to make the entire card a single ext4 partition. I couldn’t get it partitioned even on a x86 system.

#8

Yes. Below I pasted some (hopefully) relevant lines just before and after it.

[ 2.006861] [drm] Driver supports precise vblank timestamp query.
[ 2.131113] mmc1: new ultra high speed SDR104 SDHC card at address aaaa
[ 2.131624] mmcblk1: mmc1:aaaa SL16G 14.8 GiB
[ 2.137388] mmcblk1: p1 p2 p3 p4 p5 p6 p7 p8 p9
[ 2.406868] remoteproc remoteproc0: Direct firmware load for mba.mbn failed with error -2
[ 2.406876] remoteproc remoteproc0: request_firmware failed: -2
[ 2.480269] Console: switching to colour frame buffer device 240x67

#9

I’m pleased to report that a SanDisk 16GB Mobile MicroSDHC Class 4 Flash Memory Card (Part# SDSDQM-016G-B35A) worked!

I tried three of the other cards in two 410c boards without luck.