mPCIE to SATA adapter nefunguje

Omnia hardware [CZ] Omnia HW problémy [CZ]
1

Zdravim,
v Omnii mi nefunguje ani jeden z dvoch mPCIE to SATA adapterov, konkretne mam doma tieto 2:
https://www.ebay.com/itm/282020924668
https://www.ebay.com/itm/Mini-PCIe-PCI-Express-to-2-Ports-SATA-3-0-III-6Gb-s-Expansion-Card-Single-Chip/282120525477
pricom ten prvy som nasiel odporucany niekde na nete (uz neviem kde) a ten druhy je udajne presne ten isty co bol aj sucastou perku. Oba skratka po zasunuti do slotu niesu detekovane a logicky, omnia ani nevidi disky do nich pripojene.

Turris - lspci
Turris - lspci933×410 12.8 KB
Turris - zaznam jadra
Turris - zaznam jadra955×953 72.6 KB

Slot ako taky asi funguje, ked do neho prehodim totiz wifi kartu, tak tu najde (aj ked aj tu stoji za zmienku ze obcas nie a router musim rebootnut, no to spravilo aj na jeho povodnej pozicii). Naopak, oba adaptery nenajde ani v slote kde je povodne wifi modul. Ci su adaptery ako take funkcne otestovat neviem, ale predpokladam ze by to bolo privela “stastia” ak by boli oba chybne.

Mate niekto napady co s tym? Prip. nieje tu niekto z Bratislavy (idealne Petrzalka), kto by bol ochotny v nejakom mPCIE vyskusat ci tie adaptery funguju? Prip. vie mi niekto odporucit link na URCITE fungujuce adaptery?

Vopred dakujem

2

Mea culpa, mea culpa, mea maxima culpa.

3

Tyto řadiče nebudou fungovat ve slotu u procesoru. Podporovány jsou jen v prostředním a “LTE” slotu (standartně neosazený slot, u kraje desky jež má podporu pro LTE modemy).

4

Dakujem za rychle odpovede:
MiKe - hladal :wink: To co si linkol je problem ohladom SSD disku, ja mam len adapter. Ako nizsie Jan.Horacek pise, ten adapter praveze bude fungovat LEN v LTE a strednom slote (kde som ich samozrejme skusal). Neboj sa, niesom ten typ co si nevie zakladne info vygooglit (aj ked samozrejme, mohlo mi nieco ujst, kedze toto forum je dokopy v 3 jazykoch :slight_smile: ), prave naopak, aj to youtube video ohladom skladania NASboxu som si pozrel cele od zaciatku do konca, ci nerobim nieco blbo… kazdopadne, dik za tip, to prelepenie pinu 43 skusit mozem, to je najmenej…

Jan.Horacek - ano, presne v tom neosadenom (LTE) a strednom som ich oba skusal.

5

Zde jsme se bavili o 4 portove karte. Kdyz jsem kartu zakoupil, tak jsem ji rovnou zkousel a dle navodu jsem ji videl ve vypisu z “lspci”.
Nicmene jeste jsem nemel cas predelat napajeni a box pro disky atd :slight_smile: Vse jim mam nakreslene, ale jde to pomalu …
Kdyz to zkousim ted, tak jiz kartu ve vypisu nevidim… Od te doby doslo ke spouste updatu a take jsem od te doby presel na btrfs. Zatim jsem nezjistoval, kde je problem, ale zacina me to trapit…

6

@ ondrejo - ved toto… ja mam silne podozrenie na SW problem (aj ked som to dal sem do HW problemov, kedze to je symptom), nakolko v minulosti to este nikto nereportoval, tj. to evidentne fungovalo (oi. asi niesom prvy co chce funkcionalitu NASu pouzit), slot je funkncny (hovorim, wifi v nom facha) a ze by som mal doma zrovna 2 vadne kusy adapterov sa mi zda malo pravdepodobne… a na tu kabelaz som sa tiez odhodlaval dlho, kym som nezistil, ze elektro, kde predavaju vsetko potrebne (GM, tusim funguje aj v CR) mam pod oknami :slight_smile:

Prosimta, ak sa do toho nahodou pustis a na nieco prides, das mi vediet, ja som co sa linuxu tyka len snazivy zaciatocnik, nemam ani tucha ako sa pustit do nejakej diagnostiky

7

Jelikoz se zde bavime o problemech, tak dodam, ze mam Turris 1.0! Samozrejme downgrade lze udelat i na Omnii, ale povazuji za dulezite to zduraznit, protoze tema je ve vlakne pro Omnie!

Takze je to software :frowning: Bohuzel, nedokazi rici, ktery balicek je to presne, ale predpokladam, ze kmod-ata-ahci.
Poporade.

Provedl jsem downgrade u balicku kmod-ata-ahci.
Tento balicek jsem zvolil, protoze zde by mely byt ovladace k sata. Alespon jsem to nekde cetl, nemam overeno.
Downgrade jsem provedl na verzi Turrisu 3.8.1. (Dle datumu nakupu controlleru jsem zkusil odhadnout verzi, kde jsem to zkousel a controller byl funkcni.) Balicek se konkretne nachazi v packages/base ve verzi 4.4.87.
Downgrade jsem provedl podle navodu v dokumentaci.
Soubor archive.lua:

Repository(‘turris-archive’, ‘Index of /archive/turris/3.8.1/packages/’, {
subdirs = {‘base’, ‘turrispackages’, ‘lucics’, ‘packages’, ‘routing’, ‘management’, ‘telephony’, ‘print
ing’},
priority = 40,
ocsp = false,
pubkey = “file:///etc/updater/keys/release.pub”
})

A do souboru user.lua jsem pridal nasledujici:

Install(“kmod-ata-ahci”, {repository = {‘turris-archive’}})

Po spusteni prikazu

updater.sh

se system “aktualizoval”, ale balicku, kde probehl downgrade bylo diky zavislostem o mnoho vice…

Update notifications

• Installed version 4.4.87-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kernel
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-nf-ipt
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-nf-conntrack
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-nf-nat
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-nf-nathelper
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-nls-base
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-usb-core
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-usb-uhci
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-usb3
• Installed version 4.4.87+2017-01-31-2-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-cfg80211
• Installed version 4.4.87+2017-01-31-2-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-mac80211
• Installed version 4.4.87+2017-01-31-2-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-ath
• Installed version 4.4.87+2017-01-31-2-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-ath10k
• Installed version 4.4.87+2017-01-31-2-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-ath9k-common
• Installed version 4.4.87+2017-01-31-2-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-ath9k
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-mmc
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-sdhci
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-mmc-fsl-p2020
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-input-core
• Installed version 4.4.87-3-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-button-hotplug
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-i2c-core
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-hwmon-core
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-hwmon-lm90
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-leds-gpio
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-input-gpio-keys
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-ipt-core
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-ipt-nat
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-ipt-conntrack
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-llc
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-stp
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-bridge
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-ebtables
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-lib-crc-ccitt
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-slhc
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-ppp
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-pppox
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-pppoe
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-nf-conntrack6
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-nf-ipt6
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-ip6tables
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-ipt-conntrack-extra
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-ipt-ipopt
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-ifb
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-sched-core
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-sched
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-nfnetlink
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-nf-conntrack-netlink
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-tun
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-atm
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-pppoa
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-crypto-pcompress
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-crypto-hash
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-crypto-null
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-crypto-aead
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-crypto-manager
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-crypto-ecb
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-crypto-sha1
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-mppe
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-iptunnel
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-gre
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-iptunnel6
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-ip6-tunnel
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-iptunnel4
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-sit
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-lib-textsearch
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-nf-nathelper-extra
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-mii
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-usb-net
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-usb-net-cdc-ether
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-usb-net-rndis
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-usb-wdm
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-usb-net-qmi-wwan
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-usb-serial
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-usb-serial-wwan
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-usb-serial-option
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-scsi-core
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-ata-core
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-ata-ahci
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-fs-fscache
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-dnsresolver
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-crypto-fcrypt
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-crypto-pcbc
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-rxrpc
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-fs-afs
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-fs-autofs4
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-lib-xor
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-lib-raid6
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-lib-zlib
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-lib-lzo
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-crypto-crc32c
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-lib-crc32c
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-fs-btrfs
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-crypto-sha256
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-crypto-des
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-crypto-md4
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-crypto-md5
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-crypto-hmac
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-fs-cifs
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-fs-configfs
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-fs-cramfs
• Installed version 4.4.87+git-20151121-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-fs-exfat
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-fs-exportfs
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-lib-crc16
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-fs-ext4
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-fs-f2fs
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-fs-hfs
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-nls-utf8
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-fs-hfsplus
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-fs-isofs
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-fs-jfs
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-fs-minix
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-fs-vfat
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-fs-msdos
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-fs-nfs-common
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-fs-nfs
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-lib-oid-registry
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-fs-nfs-common-v4
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-fs-nfsd
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-fs-ntfs
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-lib-crc-itu-t
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-fs-udf
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-fs-xfs
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-nls-cp1250
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-nls-cp1251
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-nls-cp437
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-nls-cp775
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-nls-cp850
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-nls-cp852
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-nls-cp862
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-nls-cp864
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-nls-cp866
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-nls-cp932
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-nls-iso8859-1
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-nls-iso8859-13
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-nls-iso8859-15
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-nls-iso8859-2
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-nls-iso8859-6
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-nls-iso8859-8
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-nls-koi8r
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-md-mod
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-md-linear
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-md-multipath
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-md-raid0
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-md-raid1
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-md-raid10
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-md-raid456
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-usb-storage
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-usb-storage-extras
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-usb2-fsl
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-usb2
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-fs-reiserfs
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-dm
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-fuse
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-sound-core
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-crypto-authenc
• Installed version 4.4.87+1.8-mpc85xx-2 of package kmod-cryptodev
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-crypto-user
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-crypto-cbc
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-crypto-wq
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-crypto-rng
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-crypto-iv
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-crypto-seqiv
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-crypto-ctr
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-crypto-gf128
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-crypto-xts
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-crypto-cmac
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-crypto-sha512
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-crypto-ccm
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-crypto-deflate
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-nfnetlink-log
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-ipt-nflog
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-nfnetlink-nfacct
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-ipt-ipset
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-nf-nat6
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-ipt-nat6
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-ipt-tproxy
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-veth
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-usb-printer
• Installed version 4.4.87+2-1-d74822050ae7ec4a1e49c6af6d672787-2 of package kmod-spi-dev

Nyni po spusteni prikazu lspci vidim controller

0000:00:00.0 PCI bridge: Freescale Semiconductor Inc P2020E (rev 21)
0001:02:00.0 PCI bridge: Freescale Semiconductor Inc P2020E (rev 21)
0001:03:00.0 Network controller: Qualcomm Atheros AR93xx Wireless Network Adapter (rev 01)
0002:04:00.0 PCI bridge: Freescale Semiconductor Inc P2020E (rev 21)
0002:05:00.0 SATA controller: Marvell Technology Group Ltd. Device 9215 (rev 11)

Zkusim opet prejit na aktualni verzi a uvidime, zda controller zmizi :frowning:

8

Tak jsem zmaten…

Update zpet na aktualni verzi. kmod-ata-ahci je ted ve verzi 4.4.110 (tato verze byla i pred downgrade)

Nicmene ve vypisu lspci controller “zustal”:

0000:00:00.0 PCI bridge: Freescale Semiconductor Inc P2020E (rev 21)
0001:02:00.0 PCI bridge: Freescale Semiconductor Inc P2020E (rev 21)
0001:03:00.0 Network controller: Qualcomm Atheros AR93xx Wireless Network Adapter (rev 01)
0002:04:00.0 PCI bridge: Freescale Semiconductor Inc P2020E (rev 21)
0002:05:00.0 SATA controller: Marvell Technology Group Ltd. Device 9215 (rev 11)

Jsem si jist, ze pred downgrade nebyl.
Samozrejme z toho mam radost, ale jsme zpet na zacatku, protoze netusim co “vypadek” zpusobilo.

Vypada to, jako by postupny updrage zpusobil vypadek, zatimco downgrade a zpet “narazovy” upgrade pomohl. Nevim jak si to overit.
Downgrade i upgrade vyzadovali reboot a reboot probehl i pred par dny (17.01.2018), takze v tom, ze bych dlouho nedelal reboot Turrisu problem nebude.

Jeste pridam seznam balicku, kdere probehly pri upgrade na aktualni verzi, kdyby nekdo chtel hledat rozdily:

• Installed version 4.4.110-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kernel
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-nf-ipt
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-nf-conntrack
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-nf-nat
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-nf-nathelper
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-nls-base
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-usb-core
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-usb-uhci
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-usb3
• Installed version 4.4.110+2017-01-31-4-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-cfg80211
• Installed version 4.4.110+2017-01-31-4-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-mac80211
• Installed version 4.4.110+2017-01-31-4-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-ath
• Installed version 4.4.110+2017-01-31-4-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-ath10k
• Installed version 4.4.110+2017-01-31-4-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-ath9k-common
• Installed version 4.4.110+2017-01-31-4-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-ath9k
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-mmc
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-sdhci
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-mmc-fsl-p2020
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-input-core
• Installed version 4.4.110-3-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-button-hotplug
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-i2c-core
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-hwmon-core
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-hwmon-lm90
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-leds-gpio
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-input-gpio-keys
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-ipt-core
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-ipt-nat
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-ipt-conntrack
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-llc
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-stp
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-bridge
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-ebtables
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-lib-crc-ccitt
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-slhc
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-ppp
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-pppox
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-pppoe
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-nf-conntrack6
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-nf-ipt6
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-ip6tables
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-ipt-conntrack-extra
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-ipt-ipopt
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-ifb
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-sched-core
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-sched
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-nfnetlink
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-nf-conntrack-netlink
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-tun
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-atm
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-pppoa
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-crypto-pcompress
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-crypto-hash
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-crypto-null
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-crypto-aead
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-crypto-manager
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-crypto-ecb
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-crypto-sha1
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-mppe
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-iptunnel
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-gre
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-iptunnel6
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-ip6-tunnel
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-iptunnel4
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-sit
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-lib-textsearch
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-nf-nathelper-extra
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-mii
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-usb-net
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-usb-net-cdc-ether
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-usb-net-rndis
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-usb-wdm
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-usb-net-qmi-wwan
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-usb-serial
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-usb-serial-wwan
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-usb-serial-option
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-scsi-core
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-ata-core
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-ata-ahci
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-fs-fscache
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-dnsresolver
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-crypto-fcrypt
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-crypto-pcbc
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-rxrpc
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-fs-afs
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-fs-autofs4
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-lib-xor
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-lib-raid6
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-lib-zlib
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-lib-lzo
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-crypto-crc32c
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-lib-crc32c
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-fs-btrfs
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-crypto-sha256
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-crypto-des
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-crypto-md4
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-crypto-md5
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-crypto-hmac
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-fs-cifs
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-fs-configfs
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-fs-cramfs
• Installed version 4.4.110+git-20151121-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-fs-exfat
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-fs-exportfs
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-lib-crc16
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-fs-ext4
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-fs-f2fs
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-fs-hfs
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-nls-utf8
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-fs-hfsplus
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-fs-isofs
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-fs-jfs
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-fs-minix
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-fs-vfat
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-fs-msdos
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-fs-nfs-common
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-fs-nfs
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-lib-oid-registry
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-fs-nfs-common-v4
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-fs-nfsd
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-fs-ntfs
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-lib-crc-itu-t
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-fs-udf
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-fs-xfs
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-nls-cp1250
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-nls-cp1251
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-nls-cp437
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-nls-cp775
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-nls-cp850
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-nls-cp852
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-nls-cp862
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-nls-cp864
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-nls-cp866
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-nls-cp932
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-nls-iso8859-1
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-nls-iso8859-13
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-nls-iso8859-15
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-nls-iso8859-2
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-nls-iso8859-6
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-nls-iso8859-8
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-nls-koi8r
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-md-mod
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-md-linear
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-md-multipath
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-md-raid0
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-md-raid1
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-md-raid10
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-md-raid456
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-usb-storage
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-usb-storage-extras
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-usb2-fsl
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-usb2
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-fs-reiserfs
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-dm
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-fuse
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-sound-core
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-crypto-authenc
• Installed version 4.4.110+1.8-mpc85xx-2 of package kmod-cryptodev
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-crypto-user
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-crypto-cbc
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-crypto-wq
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-crypto-rng
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-crypto-iv
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-crypto-seqiv
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-crypto-ctr
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-crypto-gf128
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-crypto-xts
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-crypto-cmac
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-crypto-sha512
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-crypto-ccm
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-crypto-deflate
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-nfnetlink-log
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-ipt-nflog
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-nfnetlink-nfacct
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-ipt-ipset
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-nf-nat6
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-ipt-nat6
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-ipt-tproxy
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-veth
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-usb-printer
• Installed version 4.4.110+0-1-56ef06674a2579d8488bcbf4fe98e926-0 of package kmod-spi-dev

9

hmm, tak som spravil to iste, bohuzial vysledok sa nedostavil :frowning: jedine co som teda spravil inak, ze som v tej archivnej url pouzil “omnia” namiesto “turris” (s turris mi to nic nerobilo a potom co som si precital tvoj disclaimer som pochopil ze mam asi inu verziu). Kazdopadne, potom uz downgrade a aj nasledny upgrade prebehol, no nic… a tiez som restartoval, este som vyskusal aj vymenit tie adaptery medzi sebou ked to bolo downgradnute, nepomohlo… uaaaaa a to bol moj hlavny dovod kupy tohto routra (nenadavam, len som frustrovany…)

10

Také bych se přidal do tohoto vlákna. Mám Turris 1.0 a získal jsem vyřazený 1U switch CISCO (doma mám pod stropem malý rack). Plánuji použít zdroj a case z toho CISCa a nacpat do něj Turris 1.0 + miniPCIe SATA + miniPCIe USB 3.0 a jako WiFi adaptér použít USB 3.0 WiFi AC.

https://www.aliexpress.com/item/Wireless-Adapter-Detachable-Wifi-Receiver-EDUP-1900Mbps-USB3-0-Dual-Band-5-8Ghz-2-4GHz-External/32826938822.html?spm=a2g0s.9042311.0.0.aRla9V

https://www.aliexpress.com/item/2-Ports-Mini-PCI-E-PCI-Express-to-SATA-3-0-Converter-Hard-Drive-Extension-Card/32839056287.html?spm=a2g0s.9042311.0.0.aRla9V

https://www.aliexpress.com/item/XT-XINTE-MINI-PCI-E-to-USB3-0-Adapter-Card-MINI-PCIE-to19-pin-USB-3/32831005411.html?spm=a2g0s.9042311.0.0.aRla9V

Očekávám, že celá akce na něčem určitě ztroskotá, nicméně pokusit se musím. Externí WiFi jsem volil ze dvou důvodů. Potřebuji 2.4G i 5G WiFi a to mi dnes zabírá oba sloty miniPCIe. A za druhé, vše je nyní zavřeno v RACKu a ten stíní celkem slušně. Buďto tedy budu reportovat zde nebo založím nové vlákno. Nyní čekám na Aliexpress.

11

@Petki Asi blba otazka, ale radeji se zeptam.
A mel jsi kartu(y) ve spravnem portu? V tomto vlaknu vyse psali, ze ne vsechny miniPCIE zvladaji controller.

12

blba :slight_smile: Ako som vyssie pisal, skusal som to v tom LTE slote (uplne vlavo, ktory je v zaklade neosadeny), ako aj tom strednom kde je 5GHz wifi, neslo ani v jednom…

13

Skúsim ešte jeden pokus :slight_smile: tu spomínajú podobný modul a vyzerá že im funguje lebo riešia iné veci (napájanie) takže by sa dal brať ako funkčný aj keď vyzerá dosť podobne ako tie čo máš ty -
PCI SATA controller - HDDs won't spin

14

hej, ved ja som tie svoje tiez kupil na zaklade info ze v Turrise urcite funguju… btw, mne sa naopak disky krasne tocia, len keby ich Turris detekoval… inak, ako najvhodnejsie riesenie sa mi stale javi tvoja pomoc (ak budes ochotny) :slight_smile: -> by sme sa niekde stretli, ja by som ti dal oba adaptery a ty by si u seba vyskusal ci ti ich Turris detekuje (len supnut do slotu, zapnut, command “lspci” a info ci ho je vidno alebo nie…).

15

Asi jsem to nemel delat. Ted jsem provedl jeden reboot. Nic jsem neinstaloval a nic jsem neodinstaloval. Nemenil jsem nic ani po HW strance (odpojeni ci pripojeni USB zarizeni atd…) a hle:

0000:00:00.0 PCI bridge: Freescale Semiconductor Inc P2020E (rev 21)
0001:02:00.0 PCI bridge: Freescale Semiconductor Inc P2020E (rev 21)
0001:03:00.0 Network controller: Qualcomm Atheros AR93xx Wireless Network Adapter (rev 01)
0002:04:00.0 PCI bridge: Freescale Semiconductor Inc P2020E (rev 21)

Tak co ted? Mam zkusit znovu downgrade, zda to pomuze?
Poradi nekdo z Turris tymu?

UPDATE: Verze 4.4.87 opet vratila controller do hry. Vse jsem povysil zpet na aktualni verzi 4.4.110 a controller je videt. Zkusil jsem nekolikero restartu a controller stale je. Ozvu se, jakmile opet zmizi, ci zjistim nejake nove informace.

16

Dnes probehl upgrade Turrisu na 3.9.4, kde je kmod-ata-ahci ve verzi 4.4.113.
Jeste nez jsem provedl reboot (ale uz po oznameni, ze probehl update, ktery reboot vyzaduje) jsem zkusil lspci a vyzledek byl pozitivni (verze 4.4.110):

0000:00:00.0 PCI bridge: Freescale Semiconductor Inc P2020E (rev 21)
0001:02:00.0 PCI bridge: Freescale Semiconductor Inc P2020E (rev 21)
0001:03:00.0 Network controller: Qualcomm Atheros AR93xx Wireless Network Adapter (rev 01)
0002:04:00.0 PCI bridge: Freescale Semiconductor Inc P2020E (rev 21)
0002:05:00.0 SATA controller: Marvell Technology Group Ltd. Device 9215 (rev 11)

Ted po reboot jsem tedy na verzi 4.4.113 a vysledek negativni:

0000:00:00.0 PCI bridge: Freescale Semiconductor Inc P2020E (rev 21)
0001:02:00.0 PCI bridge: Freescale Semiconductor Inc P2020E (rev 21)
0001:03:00.0 Network controller: Qualcomm Atheros AR93xx Wireless Network Adapter (rev 01)
0002:04:00.0 PCI bridge: Freescale Semiconductor Inc P2020E (rev 21)

UPDATE:
Downgrade z 4.4.113 na 4.4.87. Vysledek negativni. Nekolikrat reboot.Vysledek negativni
Upgrade zpet z 4.4.87 na 4.4.113. Vysledek negativni.
Budu zkouset a ozvu se, pokud na neco prijdu.

UPDATE:
Zkousel jsem udelat downgrade Turris na 3.9.3 a po rebootu provest downgrade kmod-ata-ahci na verzi, kdy se controller rozchodil, ale tentokrat negativni vysledek. Zkusil jsem pote postupny ugrade a to napred Turris a pote teprve balicek na nejnovejsi verzi a take negativni vysledek. Jsem na konci mych znalosti.

1 Like
17

Zdravim.
Upgradol som svoj modul na vyssiu verziu a povodny mam doma nevyuzity. Modul je urcite funkcny. Ak mas zaujem mozem ti ho poslat postou v bublinkovej obalke a ho otestujes u seba.

18

Zdravim.
Upgradol som svoj modul na vyssiu verziu. Modul/Turris sa vsak spraval nevyspytatelne-raz bol modul detegovany, raz nebol, inokedy fungoval kym som nezacal pripajat disky a pod. Zaroven som mal v turrise pripojeny usb 3.0 kluc v prednom usb 3.0 porte a podivne hlasky s btrfs v logoch. Vobec neviem aky to moze mat suvis, ale po vypojeni usb kluca z usb portu prestali hlasky v logoch a modul bol nasledne po kazdom reboote, upgrade korektne detegovany. Problem som riesil pri verzii 3.9.1, teraz aktualne 3.9.3 a vsetko zatial funguje.

19

@ondrejo - len FYI, MiKe teda vyskusal moje adaptery, u neho funguju… a pisal som aj na tech support, nech sa na to pozru… kazdopadne, si na tom predsalen o kusok lepsie ako ja - tebe sa ten adapter aspon vtedy raz po downgrade ukazal, u mna 0 bodov

@fidko2000 - dik moc, ked pride, dam vediet co a ako…

20

@Petki: zkoušel jsi modul s nějakým USB zařízením či bez?
@MiKe: když jsou zkoušel moduly od @Petki, měl jsi zapojené nějaké USB zařízení?

Já jsem momentálně na Turris 1.0 (v 3.9.5) převedeném na btrfs a mám připojený externí USB disk, kde mi běží LXC kontejnery. Jeden je s PiHole a jeden s připraveným Nextcloudem, až se mi podaří dokončit case pro Turris, disky a napájení. Vše mám již v 3D a pár dílů i připravených. Jen to potřebuji nastříkat a smontovat :slight_smile:

Je možné, že připojený USB disk způsobuje problémy pro kartu, zkusít vypnout kontejnery a napíši výsledek, zda se karta objeví.

EDIT: Tak odpojení USB nepomáhá. Controler není vidět ani po několika rebootech a dokonce ani po opětovném připojení USB disku… Budu doufat, že nějaký následující release pomůže. Jde o to, že pokud má problém pouze malá hrstka uživatelů, tak se s tím ani nic dělat nebude…