xref: /openwifi/doc/known_issue/notter.md (revision 9d7c6e634f14808c446226d4d3d1c695fe201460)
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
8## Network issue in quick star
9
10- OS: Ubuntu 22 LTS
11- image: [openwifi img](https://drive.google.com/file/d/1fb8eJGJAntOciCiGFVLfQs7m7ucRtSWD/view?usp=share_link)
12
13If 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).
14
15If still can't ssh the board via Ethernet, you should use UART console (/dev/ttyUSBx, /dev/ttyCH341USBx, etc.) to monitor what happened during booting.
16
17## EXT4 fs error rootfs issue
18
19Sometimes, 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:
20- gnome-disks
21- Startup Disk Creator
22- win32diskimager
23
24## antsdr e200 UART console
25
26If 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`
27
28## Client can not get IP
29
30If 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.
31