[fli4l] alix.2d3 installation problem

Alexander Dahl lespocky at web.de
Fr Apr 10 23:43:16 CEST 2020


Hello,

Bernard schrieb Freitag, 10. April 2020, 22:50 (CEST):
> Hi, Alexander
>
> Le 10/04/2020 à 19:14, Alexander Dahl a écrit :
>> Is you card listed with `lspci` or `lspci -k`?
>
> fli4l 3.10.19 # lspci
> -sh: lspci: not found
> fli4l 3.10.19 # lspci -k
> -sh: lspci: not found
>
> This command does not work! Why?

Did you activate it in opt tools with OPT_LSPCI='yes'?

>> Is the 'rt2800pci' kernel module loaded? Do you see it with `lsmod`?
>
> fli4l 3.10.19 # lsmod
> Module                  Size  Used by    Tainted: G
> lm90                   16432  0
> hwmon                  12564  1 lm90
> nf_nat_ftp             12336  0
> nf_conntrack_ftp       12336  2 nf_nat_ftp
> rt2800pci              12336  0
> rt2800mmio             13065  1 rt2800pci
> rt2800lib              62832  2 rt2800pci,rt2800mmio
> rt2x00pci              12437  1 rt2800pci
> rt2x00mmio             12496  2 rt2800pci,rt2800mmio
> rt2x00lib              32403  5 
> rt2800pci,rt2800mmio,rt2800lib,rt2x00pci,rt2x00mmio
> eeprom_93cx6           12447  1 rt2800pci
> crc_ccitt              12331  1 rt2800lib
> via_rhine              20528  0
> mii                    12568  1 via_rhine
> mac80211              203097  3 rt2800lib,rt2x00pci,rt2x00lib
> cfg80211              136515  2 rt2x00lib,mac80211
> rfkill                 12799  1 cfg80211
> ledtrig_timer          12336  0
> ledtrig_pattern        12336  0
> scx200_acb             12336  0
> i2c_core               17886  2 lm90,scx200_acb
> leds_alix              12336  0
> leds_gpio              12336  0
> led_class              12487  2 rt2x00lib,leds_gpio
> gpio_cs5535            12512  4
> cs5535_mfd             12336  0
> aes_i586               16566  0
> ecb                    12336  0
> cbc                    12336  0
> geode_aes              12336  0
> cryptodev              29405  0
> geode_rng              12336  0
> rng_core               12400  1 geode_rng
> nls_iso8859_1          12336  1
> ums_usbat              16432  0
> ums_sddr55             12336  0
> ums_sddr09             16432  0
> ums_realtek            12336  0
> ums_onetouch           12336  0
> ums_karma              12336  0
> ums_jumpshot           12336  0
> ums_isd200             12336  0
> ums_freecom            12336  0
> ums_datafab            12336  0
> ums_cypress            12336  0
> ums_alauda             16432  0
> usb_storage            38310 12 
> ums_usbat,ums_sddr55,ums_sddr09,ums_realtek,ums_onetouch,ums_karma,ums_jumpshot,ums_isd200,ums_freecom,ums_datafab,ums_cypress,ums_alauda
> ahci                   28755  0
> libahci                21176  1 ahci
> ata_piix               20528  0
> ata_generic            12336  0
> sr_mod                 16851  0
> cdrom                  25061  1 sr_mod
> sd_mod                 28720  2
> isofs                  33178  0
> ext4                  246386  0
> crc16                  12327  1 ext4
> mbcache                12701  1 ext4
> jbd2                   44914  1 ext4
> pata_amd               12336  1
> hid_generic            12336  0
> usbhid                 25061  0
> hid                    50317  2 hid_generic,usbhid
> ohci_pci               12336  0
> ehci_pci               12336  0
> uhci_hcd               20528  0
> ohci_hcd               20744  1 ohci_pci
> ehci_hcd               37093  1 ehci_pci
> xhci_hcd               78251  0
> usbcore               113967 20 
> ums_usbat,ums_sddr55,ums_sddr09,ums_realtek,ums_onetouch,ums_karma,ums_jumpshot,ums_isd200,ums_freecom,ums_datafab,ums_cypress,ums_alauda,usb_storage,usbhid,ohci_pci,ehci_pci,uhci_hcd,ohci_hcd,ehci_hcd,xhci_hcd
> usb_common             12408  1 usbcore
> libata                119854  5 ahci,libahci,ata_piix,ata_generic,pata_amd
> scsi_mod              104277  5 ums_cypress,usb_storage,sr_mod,sd_mod,libata

Looks good, including the mac80211 modules.

>> What does dmesg show, when you try to load that thing with modprobe or
>> insmod?
>
> fli4l 3.10.19 # modprobe
> fli4l 3.10.19 # insmod
> BusyBox v1.22.1 (fli4l) multi-call binary.

That's not how those work, but it doesn't matter, the module is loaded
already. Did you check if a wlan interface ist present, e.g. with `ip
addr show`?

> I think the rt2880 does not have in rt2800 driver
> view site:
> https://wiki.debian.org/rt2800pci
> view also:
> https://wireless.wiki.kernel.org/en/users/drivers/rt2880_inic

As I said, I looked in kernel code and at least in the help text it
says. lspci could be helpful, we could look for pci ids then.

Alex

-- 
***** http://blog.antiblau.de/ *****************************
GnuPG-FP: C28E E6B9 0263 95CF 8FAF  08FA 34AD CD00 7221 5CC6


Mehr Informationen über die Mailingliste Fli4L