mirror of
https://github.com/open-sdr/openwifi.git
synced 2025-02-10 13:11:24 +00:00
31 lines
1.3 KiB
Markdown
31 lines
1.3 KiB
Markdown
# Known issue
|
|
|
|
- [Network issue in quick start](#Network-issue-in-quick-start)
|
|
- [EXT4 fs error rootfs issue](#EXT4-fs-error-rootfs-issue)
|
|
- [antsdr e200 UART console](#antsdr-e200-UART-console)
|
|
- [Client can not get IP](#Client-can-not-get-IP)
|
|
|
|
## Network issue in quick star
|
|
|
|
- OS: Ubuntu 22 LTS
|
|
- image: [openwifi img](https://drive.google.com/file/d/1fb8eJGJAntOciCiGFVLfQs7m7ucRtSWD/view?usp=share_link)
|
|
|
|
If 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).
|
|
|
|
If still can't ssh the board via Ethernet, you should use UART console (/dev/ttyUSBx, /dev/ttyCH341USBx, etc.) to monitor what happened during booting.
|
|
|
|
## EXT4 fs error rootfs issue
|
|
|
|
Sometimes, 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:
|
|
- gnome-disks
|
|
- Startup Disk Creator
|
|
- win32diskimager
|
|
|
|
## antsdr e200 UART console
|
|
|
|
If 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`
|
|
|
|
## Client can not get IP
|
|
|
|
If 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.
|