Jump to content

Ikrk

Members
  • Posts

    4
  • Joined

  • Last visited

  1. For my purposes worked this workaround: 1) in file linux-headers-3.4.112-sun8i/fs/Kconfig comment out lines #107: source "fs/fatfs/Kconfig" and #287: source "fs/fs_compat.kconfig" 2) in file linux-headers-3.4.112-sun8i/fs/Makefile comment out lines #76: obj-$(CONFIG_FATFS_FS) += fatfs/ 3) in linux-headers-3.4.112-sun8i folder execute make scripts
  2. Hi pschasch, as mentioned before, I have Orange Pi One with 3.4.110-sun8i kernel and I compiled directly on the device. I did not try to crosscompile. Regards
  3. Resolved! I took this modified driver: https://github.com/shaun2029/rt5572sta(Btw, thank you so much shaun2029!) Then you have to in ./include/os/rt_linux.h change the datatypes "kuid_t" to "uid_t" and "kgid_t" to "gid_t" (this is possibly valid only for kernels >= 3.4.0) And then in driver's root just: make -j4 ARCH=arm make install modprobe rt5572sta Best regards
  4. Hi all, I have this configuration: uname -a Linux orangepione 3.4.110-sun8i #18 SMP PREEMPT Tue Mar 8 20:03:32 CET 2016 armv7l GNU/Linux and also Ralink RT5572 and I can confirm, that driver DPO_RT5572_LinuxSTA_2.6.1.3_20121022 does not work for me either... So I have tried to backport the rt2800usb drivers as pschasch proposed and I could get the same result: modinfo ./rt2800usb.ko | grep "version\|5572" version: backported from Linux (v3.12.8-0-g97f15f1) using backports v3.12.8-1-0-geb41fad version: 2.3.0 srcversion: D0035750636933A8C0E52C5 alias: usb:v148Fp5572d*dc*dsc*dp*ic*isc*ip* vermagic: 3.4.110 SMP preempt mod_unload modversions ARMv7 p2v8 Unfortunately, the module cannot be loaded and dmesg sais: rt2800usb: disagrees about version of symbol rt2800_config_erp rt2800usb: Unknown symbol rt2800_config_erp (err -22) and many other symbols... After a research, I have read, that this can happen when the module is compiled againt another Kernel version or when the configuration differs. I have used the linux-headers-3.4.110-sun8i that came within the image and executed make scripts before compiling backports. My understanding of backports was, that it should take the .config file from /usr/src/linux-headers-... and do the configuration automatically... Do you have any idea, where could be the problem? Thank you very much for any help! Regards.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines