Jump to content

Search the Community

Showing results for tags 'clearfogpro'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Upcoming Hardware (WIP)
    • News
    • Odroid M1
    • ROCK 5B
  • Maintained Hardware
    • Board does not start
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Unmaintained (CSC/EOL/TVB) / Other
    • TV boxes
    • Off-topic
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP/Jabber


Skype


Github


Discord


Location


Interests

Found 1 result

  1. Hello to you! I was using Arch Linux ARM on my Clearfog Pro for years. Then things got bad. I think it's a bad combination to have a distro with the most up-to-date software while developers are rapidly abandoning and not testing 32-bit Linux software. First wget became incompatible with gnutls and then programs in coreutils that use utmp started malfunctioning. The last straw was the system became unbootable, issuing a message about ext4 "ext4fs_devread read outside partition 18446744073709551440". I switched to Armbian but now I'm at a loss as to how to configure DSA on the Clearfog Pro. I installed the mv88e6xxx but the LAN ports on the DSA switch did not come to life. sudo modprobe mv88e6xxx Module Size Used by +mv88e6xxx 139264 0 +dsa_core 61440 1 mv88e6xxx +hsr 28672 1 dsa_core +bridge 163840 2 mv88e6xxx,dsa_core +stp 16384 1 bridge +llc 16384 2 bridge,stp rfkill 20480 1 lz4hc 16384 0 lz4 16384 0 $ networkctl -a WARNING: systemd-networkd is not running, output will be incomplete. IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback n/a unmanaged 2 eth0 ether n/a unmanaged 3 eth1 ether n/a unmanaged 4 eth2 ether n/a unmanaged 4 links listed. $ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1024 link/ether 02:b3:7f:ac:38:c4 brd ff:ff:ff:ff:ff:ff inet 192.168.1.100/24 brd 192.168.1.255 scope global dynamic noprefixroute eth0 valid_lft 39361sec preferred_lft 39361sec inet6 fdee:207b:f0ce::6ba/128 scope global dynamic noprefixroute valid_lft 39363sec preferred_lft 39363sec inet6 fdee:207b:f0ce:0:7b29:63c:40fc:4405/64 scope global noprefixroute valid_lft forever preferred_lft forever inet6 fe80::e1d8:2674:2151:93fc/64 scope link noprefixroute valid_lft forever preferred_lft forever 3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1024 link/ether 00:50:43:84:25:2f brd ff:ff:ff:ff:ff:ff 4: eth2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1024 link/ether 00:50:43:0d:19:18 brd ff:ff:ff:ff:ff:ff Back when it was working on Arch Linux ARM I would see this $ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 4e:ea:ed:f3:18:fb brd ff:ff:ff:ff:ff:ff inet 192.168.0.8/24 brd 192.168.0.255 scope global br0 valid_lft forever preferred_lft forever inet6 2601:14a:600:6420:4cea:edff:fef3:18fb/64 scope global dynamic mngtmpaddr noprefixroute valid_lft 3069586540sec preferred_lft 3069586540sec inet6 fe80::4cea:edff:fef3:18fb/64 scope link valid_lft forever preferred_lft forever 3: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 532 link/ether 00:50:43:00:05:01 brd ff:ff:ff:ff:ff:ff 4: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 532 link/ether 00:50:43:00:00:01 brd ff:ff:ff:ff:ff:ff inet6 fe80::250:43ff:fe00:1/64 scope link valid_lft forever preferred_lft forever 5: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 532 link/ether 00:50:43:05:00:00 brd ff:ff:ff:ff:ff:ff 6: lan5@eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:50:43:00:00:01 brd ff:ff:ff:ff:ff:ff 7: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:c0:ca:95:8b:89 brd ff:ff:ff:ff:ff:ff 8: lan4@eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:50:43:00:00:01 brd ff:ff:ff:ff:ff:ff 9: lan3@eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:50:43:00:00:01 brd ff:ff:ff:ff:ff:ff 10: lan2@eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:50:43:00:00:01 brd ff:ff:ff:ff:ff:ff 11: lan1@eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UP group default qlen 1000 link/ether 00:50:43:00:00:01 brd ff:ff:ff:ff:ff:ff 12: lan6@eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:50:43:00:00:01 brd ff:ff:ff:ff:ff:ff Does anyone know what I should do to bring up the DSA? Best Regards, KES
×
×
  • Create New...