1bfa0a5cdSXianjun Jiao# Known issue 2bfa0a5cdSXianjun Jiao 3d971c386SJiao Xianjun- [Network issue in quick start](#Network-issue-in-quick-start) 4d2ed8f98SJiao Xianjun- [EXT4 fs error rootfs issue](#EXT4-fs-error-rootfs-issue) 5d971c386SJiao Xianjun- [antsdr e200 UART console](#antsdr-e200-UART-console) 6a17e30c7SXianjun Jiao- [Client can not get IP](#Client-can-not-get-IP) 7*a4916c07SJiao Xianjun- [No space left on device](#No-space-left-on-device) 8bfa0a5cdSXianjun Jiao 9d971c386SJiao Xianjun## Network issue in quick star 10bfa0a5cdSXianjun Jiao 11bfa0a5cdSXianjun Jiao- OS: Ubuntu 22 LTS 12bfa0a5cdSXianjun Jiao- image: [openwifi img](https://drive.google.com/file/d/1fb8eJGJAntOciCiGFVLfQs7m7ucRtSWD/view?usp=share_link) 13bfa0a5cdSXianjun Jiao 147ac12f7cSJiao XianjunIf can't ssh to the board via Ethernet for the 1st time, you might need to delete /etc/network/interfaces.new on SD card (on your computer). 157ac12f7cSJiao Xianjun 1642e8e675SJiao XianjunIf still can't ssh the board via Ethernet, you should use UART console (/dev/ttyUSBx, /dev/ttyCH341USBx, etc.) to monitor what happened during booting. 17d971c386SJiao Xianjun 18d2ed8f98SJiao Xianjun## EXT4 fs error rootfs issue 19d2ed8f98SJiao Xianjun 20d2ed8f98SJiao XianjunSometimes, the 1st booting after flashing SD card might encounter "EXT4-fs error (device mmcblk0p2): ..." error on neptunesdr, changing SD card flashing tool might solve this issue. Some tool candidates: 21d2ed8f98SJiao Xianjun- gnome-disks 22d2ed8f98SJiao Xianjun- Startup Disk Creator 23d2ed8f98SJiao Xianjun- win32diskimager 24d2ed8f98SJiao Xianjun 25d971c386SJiao Xianjun## antsdr e200 UART console 26bfa0a5cdSXianjun Jiao 27dcda3265SJiao XianjunIf can't see the UART console in Linux (/dev/ttyUSB0 or /dev/ttyCH341USB0), according to https://github.com/juliagoda/CH341SER, you might need to do `sudo apt remove brltty` 28a17e30c7SXianjun Jiao 29a17e30c7SXianjun Jiao## Client can not get IP 30a17e30c7SXianjun Jiao 31a17e30c7SXianjun JiaoIf the client can not get IP from the openwifi AP, just re-run "service isc-dhcp-server restart" on board and do re-connect from the client. 32*a4916c07SJiao Xianjun 33*a4916c07SJiao Xianjun## No space left on device 34*a4916c07SJiao XianjunIt might be due to too many dmesg/log/journal, disk becomes full. 35*a4916c07SJiao Xianjun``` 36*a4916c07SJiao Xianjunsystemd-journald[5694]: Failed to open system journal: No space left on device 37*a4916c07SJiao Xianjun``` 38*a4916c07SJiao XianjunYou can try following operations. 39*a4916c07SJiao Xianjun``` 40*a4916c07SJiao Xianjunsystemd-tmpfiles --clean 41*a4916c07SJiao Xianjunsudo systemd-tmpfiles --remove 42*a4916c07SJiao Xianjunrm /var/log/* -rf 43*a4916c07SJiao Xianjunapt --autoremove purge rsyslog 44*a4916c07SJiao Xianjun``` 45*a4916c07SJiao XianjunAdd followings into `/etc/systemd/journald.conf` 46*a4916c07SJiao Xianjun``` 47*a4916c07SJiao XianjunSystemMaxUse=64M 48*a4916c07SJiao XianjunStorage=volatile 49*a4916c07SJiao XianjunRuntimeMaxUse=64M 50*a4916c07SJiao XianjunForwardToConsole=no 51*a4916c07SJiao XianjunForwardToWall=no 52*a4916c07SJiao Xianjun``` 53