1# Known issue 2 3- [Network issue in quick start](#Network-issue-in-quick-start) 4- [EXT4 fs error rootfs issue](#EXT4-fs-error-rootfs-issue) 5- [antsdr e200 UART console](#antsdr-e200-UART-console) 6- [Client can not get IP](#Client-can-not-get-IP) 7- [No space left on device](#No-space-left-on-device) 8 9## Network issue in quick star 10 11- OS: Ubuntu 22 LTS 12- image: [openwifi img](https://drive.google.com/file/d/1fb8eJGJAntOciCiGFVLfQs7m7ucRtSWD/view?usp=share_link) 13 14If 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). 15 16If still can't ssh the board via Ethernet, you should use UART console (/dev/ttyUSBx, /dev/ttyCH341USBx, etc.) to monitor what happened during booting. 17 18## EXT4 fs error rootfs issue 19 20Sometimes, 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: 21- gnome-disks 22- Startup Disk Creator 23- win32diskimager 24 25## antsdr e200 UART console 26 27If 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` 28 29## Client can not get IP 30 31If 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 33## No space left on device 34It might be due to too many dmesg/log/journal, disk becomes full. 35``` 36systemd-journald[5694]: Failed to open system journal: No space left on device 37``` 38You can try following operations. 39``` 40systemd-tmpfiles --clean 41sudo systemd-tmpfiles --remove 42rm /var/log/* -rf 43apt --autoremove purge rsyslog 44``` 45Add followings into `/etc/systemd/journald.conf` 46``` 47SystemMaxUse=64M 48Storage=volatile 49RuntimeMaxUse=64M 50ForwardToConsole=no 51ForwardToWall=no 52``` 53