tag:linuxfr.org,2005:/forums/linux-embarqueLinuxFr.org : le forum Linux.embarqué2024-03-03T22:54:18+01:00/favicon.pngtag:linuxfr.org,2005:Post/441322024-03-03T22:54:18+01:002024-03-03T22:54:18+01:00Buildroot Raspberry pi zero - Ethernet Gadget<p>Bonjour,<br>
j'aimerais pouvoir me connecter via l'USB à un Raspberry Pi Zero dont l'image est générée par buildroot.<br>
j'ai bien ajouté dtoverlay=dwc2 dans le config.txt, j'ai essayé eudev, j'ai fouillé dans la configuration du kernel et essayé différentes options, mais là je sèche.<br>
quelqu'un aurait-il quelques conseils, ou un lien vers un tutoriel ?<br>
Merci!</p>
<div><a href="https://linuxfr.org/forums/linux-embarque/posts/buildroot-raspberry-pi-zero-ethernet-gadget.epub">Télécharger ce contenu au format EPUB</a></div> <p>
<strong>Commentaires :</strong>
<a href="//linuxfr.org/nodes/135036/comments.atom">voir le flux Atom</a>
<a href="https://linuxfr.org/forums/linux-embarque/posts/buildroot-raspberry-pi-zero-ethernet-gadget#comments">ouvrir dans le navigateur</a>
</p>
max22https://linuxfr.org/nodes/135036/comments.atomtag:linuxfr.org,2005:Post/440522024-01-13T17:52:53+01:002024-01-13T17:52:53+01:00Problème pour charger le firmware Realtek rtw88<p>Bonjour,</p>
<p>Je n'arrive pas à charger correctement le firmware Realtek <strong>rtw88</strong> pour la <a href="https://www.friendlyelec.com/index.php?route=product/product&product_id=293">carte M.2 AzureWave RTL8822CE</a> sur mon <a href="https://wiki.friendlyelec.com/wiki/index.php/NanoPi_R5C#Hardware_Spec">Nanopi R5C</a>.</p>
<p>Voici la sortie de <code>lspci -k</code> :</p>
<blockquote>
<p>root@nanopi:~# lspci -k<br>
0000:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal Processor (rev 01)<br>
Kernel driver in use: pcieport<br>
0000:01:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822CE 802.11ac PCIe Wireless Network Adapter<br>
Subsystem: AzureWave RTL8822CE 802.11ac PCIe Wireless Network Adapter<br>
Kernel modules: rtw88_8822ce<br>
0001:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal Processor (rev 01)<br>
Kernel driver in use: pcieport<br>
0001:01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)<br>
Subsystem: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller<br>
Kernel driver in use: r8169<br>
Kernel modules: r8169, r8125<br>
0002:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal Processor (rev 01)<br>
Kernel driver in use: pcieport<br>
0002:01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)<br>
Subsystem: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller<br>
Kernel driver in use: r8169<br>
Kernel modules: r8169, r8125</p>
</blockquote>
<p>On voit que pour le bus PCI 0000:01:00.0, le module <strong>rtw88_88ce</strong> a bien été identifié, mais n'est pas utilisé (il manque la ligne "<em>Kernel driver in use</em>" comme les deux ports ethernet).</p>
<p>La sortie de <code>journalctl</code> donne :</p>
<blockquote>
<p>kernel: pcieport 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring<br>
kernel: pci 0000:01:00.0: [10ec:c822] type 00 class 0x028000<br>
kernel: pci 0000:01:00.0: reg 0x10: [io 0x1000-0x10ff]<br>
kernel: pci 0000:01:00.0: reg 0x18: [mem 0xf4300000-0xf430ffff 64bit]<br>
kernel: pci 0000:01:00.0: supports D1 D2<br>
kernel: pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot D3cold<br>
kernel: pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01<br>
kernel: pcieport 0000:00:00.0: BAR 14: assigned [mem 0xf4300000-0xf43fffff]<br>
kernel: pcieport 0000:00:00.0: BAR 13: assigned [io 0x1000-0x1fff]<br>
kernel: pci 0000:01:00.0: BAR 0: assigned [io 0x1000-0x10ff]<br>
kernel: rtw_8822ce 0000:01:00.0: enabling device (0000 -> 0003)<br>
kernel: rtw_8822ce 0000:01:00.0: firmware: direct-loading firmware rtw88/rtw8822c_wow_fw.bin<br>
kernel: rtw_8822ce 0000:01:00.0: WOW Firmware version 9.9.4, H2C version 15<br>
kernel: rtw_8822ce 0000:01:00.0: firmware: direct-loading firmware rtw88/rtw8822c_fw.bin<br>
kernel: rtw_8822ce 0000:01:00.0: Firmware version 9.9.15, H2C version 15<br>
kernel: rtw_8822ce 0000:01:00.0: error beacon valid<br>
kernel: rtw_8822ce 0000:01:00.0: failed to download rsvd page<br>
kernel: rtw_8822ce 0000:01:00.0: failed to download firmware<br>
kernel: rtw_8822ce 0000:01:00.0: failed to setup chip efuse info<br>
kernel: rtw_8822ce 0000:01:00.0: failed to setup chip information<br>
kernel: rtw_8822ce: probe of 0000:01:00.0 failed with error -16</p>
</blockquote>
<p>J’ai une erreur : « <strong>error beacon valid</strong> », mais impossible de trouver de l’information là dessus.</p>
<p>Pouvez-vous m'aider à comprendre pourquoi ce firmware ne se charge pas correctement ?</p>
<p>Je ne sais pas comment avoir plus d'informations lors de la génération des logs. Peut-être est-il possible d'avoir un mode "<strong>debug</strong>" ?</p>
<div><a href="https://linuxfr.org/forums/linux-embarque/posts/probleme-pour-charger-le-firmware-realtek-rtw88.epub">Télécharger ce contenu au format EPUB</a></div> <p>
<strong>Commentaires :</strong>
<a href="//linuxfr.org/nodes/134489/comments.atom">voir le flux Atom</a>
<a href="https://linuxfr.org/forums/linux-embarque/posts/probleme-pour-charger-le-firmware-realtek-rtw88#comments">ouvrir dans le navigateur</a>
</p>
libresurfhttps://linuxfr.org/nodes/134489/comments.atomtag:linuxfr.org,2005:Post/439662023-12-01T10:06:51+01:002023-12-01T10:06:51+01:00[Raspberry pi4] : OS debian pour raspberry et boot USB HDD<p>Bonjour,</p>
<p>J'ai testé hier le boot depuis HDD de 4To 3"5 avec l'OS ci-dessous.</p>
<p><a href="https://raspi.debian.net/tested/20231109_raspi_4_bookworm.img.xz">https://raspi.debian.net/tested/20231109_raspi_4_bookworm.img.xz</a></p>
<p>Le flash a été effectué avec cette cmd sinon même avec une µSD seul sur la rpi l'OS ne boot pas.</p>
<p>xzcat 20210408_raspi_3_bullseye.xz | sudo dd of=/dev/{YOUR_DEVICE} bs=64k oflag=dsync status=progress</p>
<p>Log lors du boot rpi 4 sur HDD 4To avec dans le bootloader BOOT_ORDER=0xf14</p>
<pre><code>[0.000000]
.......................
[7.000000] /dev/sda2 : Mounted filesystem with ordered data mode. Quota mode: non.
[7.000001] /dev/sda2 : Unmounted Filesystem
</code></pre>
<p>Le temps était environ à 7 ms dans le log de démarrage du rpi4.</p>
<p>A priori, on m'a dit que l'OS debian pour Rpi était fait pour booter sur µSD.</p>
<p><a href="https://raspi.debian.net/tested/20231109_raspi_4_bookworm.img.xz">https://raspi.debian.net/tested/20231109_raspi_4_bookworm.img.xz</a></p>
<p>Mais malgré tout, j'ai une rpi4 qui fonctionne avec cet OS mais je ne sais plus comment j'ai fait.</p>
<p>Il y a une méthode particulière pour boot cet OS depuis un HDD ?</p>
<p>Il y a t-il besoin de modifier le BOOT_ORDER aujourd'hui à "0xf14" ?</p>
<p><a href="https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#BOOT_ORDER">https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#BOOT_ORDER</a></p>
<p>0x4 USB-MSD -> celui-ci à l'air le plus approprié (USB Mass Storage Boot (Available on Raspberry Pi 2B v1.2, until 4B, …))</p>
<p>0x3 RPIBOOT -> ne sait pas exactement ce que c'est<br>
0x5 BCM-USB-MSD -> ne sait pas exactement ce que c'est</p>
<p>Autre lien : <a href="https://wiki.debian.org/RaspberryPi4">https://wiki.debian.org/RaspberryPi4</a></p>
<p>Si vous avez une idée, une expérience la dessus.</p>
<p>Merci pour vos retour.</p>
<div><a href="https://linuxfr.org/forums/linux-embarque/posts/raspberry-pi4-os-debian-pour-raspberry-et-boot-usb-hdd.epub">Télécharger ce contenu au format EPUB</a></div> <p>
<strong>Commentaires :</strong>
<a href="//linuxfr.org/nodes/134062/comments.atom">voir le flux Atom</a>
<a href="https://linuxfr.org/forums/linux-embarque/posts/raspberry-pi4-os-debian-pour-raspberry-et-boot-usb-hdd#comments">ouvrir dans le navigateur</a>
</p>
electro575https://linuxfr.org/nodes/134062/comments.atomtag:linuxfr.org,2005:Post/439572023-11-29T23:26:47+01:002023-11-29T23:26:47+01:00tel classique avec wifi+xmpp+sip?<p>bonjour</p>
<p>connaitriez vous un type d'appareil, à mi chemin entre le smartphone basique et le tel classique, qui permettrait de :<br>
-communiquer en 2/3/4G (sms, tel)<br>
-connexion wifi<br>
-communiquer via email, sip, xmpp (omemo/jingle)<br>
-disposerait d'un clavier physique/plastique<br>
-disposerait d'un tout petit écran, apparence "frigo", d'une batterie à recharger tous les trois mois</p>
<p>j'avais bien en vue la lignée des bberry q10, dont l'intégration android 4 (bberryOS10) permet conversations et linphone dans leurs anciennes versions, mais je ne parviens pas à en trouver un..</p>
<p>merci bcp!</p>
<div><a href="https://linuxfr.org/forums/linux-embarque/posts/tel-classique-avec-wifi-xmpp-sip.epub">Télécharger ce contenu au format EPUB</a></div> <p>
<strong>Commentaires :</strong>
<a href="//linuxfr.org/nodes/134037/comments.atom">voir le flux Atom</a>
<a href="https://linuxfr.org/forums/linux-embarque/posts/tel-classique-avec-wifi-xmpp-sip#comments">ouvrir dans le navigateur</a>
</p>
tkrhttps://linuxfr.org/nodes/134037/comments.atomtag:linuxfr.org,2005:Post/438792023-10-05T19:58:35+02:002023-10-05T19:58:35+02:00[QEMU] [MICRO:BIT] utiliser STDIO (ou autre) pour debugger l'UART<p>Bonjour.</p>
<p>Je suis en train de jouer avec l'uart de la Micro:bit. Cette carte est normalement censée être émulée par qemu, et l'UART est censée être implémentée.</p>
<p>Je cherche à faire en sorte de pouvoir envoyer des caractères depuis l'UART, et en recevoir. J'aimerais passer par la console, l'interface graphique QEMU, ou n'importe quel moyen.Cependant je n'ai pas l'impression de bien m'y prendre. (il me semble avoir réussi à le faire, mais c'est il y a longtemps et je ne sais plus comment je m'y suis pris)</p>
<p>J'exécute qemu à l'aide de cette commande :</p>
<p>qemu-system-arm -M microbit -device loader,file=./uart.hex -s -S </p>
<p>Ensuite j'exécute mon programme via GDB. Mon programme dans un premier temps est censé envoyer un caractère via l'UART (émission). Or je ne vois rien sur la console (je vais voir ce qui se passe sur la liaison serie dans l'interface graphique de qemu)</p>
<p>Du coup je me demande si c'est ma ligne de commande, mon programme ou l'émulation qemu qui ne fonctionne pas.</p>
<p>Pourriez-vous m'indiquer si vous constatez quelque chose d'anormal dans ma ligne de commande SVP ?</p>
<p>Ma version de qemu : QEMU emulator version 7.1.0</p>
<p>Merci d'avance.</p>
<div><a href="https://linuxfr.org/forums/linux-embarque/posts/qemu-micro-bit-utiliser-stdio-ou-autre-pour-debugger-l-uart.epub">Télécharger ce contenu au format EPUB</a></div> <p>
<strong>Commentaires :</strong>
<a href="//linuxfr.org/nodes/133547/comments.atom">voir le flux Atom</a>
<a href="https://linuxfr.org/forums/linux-embarque/posts/qemu-micro-bit-utiliser-stdio-ou-autre-pour-debugger-l-uart#comments">ouvrir dans le navigateur</a>
</p>
totof2000https://linuxfr.org/nodes/133547/comments.atomtag:linuxfr.org,2005:Post/438372023-09-14T14:34:31+02:002023-09-14T14:57:25+02:00v4l2rtspserver sur webcam arm - not a tty<p>Bonjour,</p>
<p>Je tente de recycler une webcam Netvue pour en faire un webcam IP standard.<br>
Elle vient par défaut avec son application pour le paramétrage et l'usage.<br>
Ce que je cherche à faire est publier le flux video sur le réseau local (rtsp ou via webpage).</p>
<p>Par defaut elle n'écoute que sur le port 5555 - protocole propriétaire je suppose.<br>
J'ai donc ouvert la webcam pour brancher sur le port série. Je passe tous les détails, mais au final:</p>
<ul>
<li>software Netvue desactivé</li>
<li>network up branche à mon wifi local</li>
<li>cross-compilation sur mon x86_64 de openssl + v4l2rtspserver (car il n'y a que 16mo d'espace disque sur la webcam)</li>
</ul>
<p>Sauf que quand je lance le v4l2rtspserver depuis la webcam:<br>
<code><br>
/media # ./v4l2rtspserver -vv /dev/video0 <br>
[NOTICE] v4l2rtspserver/main.cpp:269<br>
Version: 0.3.7-44-g0b4247c-dirty live555 version:2023.07.24<br>
[NOTICE] v4l2rtspserver/src/V4l2RTSPServer.cpp:37<br>
Create V4L2 Source.../dev/video0<br>
VIDIOC_REQBUFS: Not a tty<br>
[NOTICE] v4l2rtspserver/libv4l2cpp/src/V4l2MmapDevice.cpp:49<br>
Device /dev/video0<br>
VIDIOC_STREAMOFF: Not a tty<br>
VIDIOC_REQBUFS: Not a tty<br>
[NOTICE] v4l2rtspserver/libv4l2cpp/src/V4l2MmapDevice.cpp:141<br>
Device /dev/video0<br>
</code><br>
Informations additionnelles:</p>
<ul>
<li>Uname -a: Linux "nv-goke-ipc" 3.4.43-gk #267 PREEMPT Thu Apr 12 18:04:00 CST 2018 armv6l GNU/Linux</li>
<li>Chipset: GK7101/GK7102</li>
</ul>
<p>Le driver a aussi créé un /dev/gk_video - mais j'obtiens encore une erreur (bad file descriptor).</p>
<p>Je ne sais pas si ça vous parle… ou bien si une alternative légere à v4l2rtspserver existe pour broadcaster le flux video sur le réseau local.</p>
<p>Merci</p>
<div><a href="https://linuxfr.org/forums/linux-embarque/posts/v4l2rtspserver-sur-webcam-arm-not-a-tty.epub">Télécharger ce contenu au format EPUB</a></div> <p>
<strong>Commentaires :</strong>
<a href="//linuxfr.org/nodes/133294/comments.atom">voir le flux Atom</a>
<a href="https://linuxfr.org/forums/linux-embarque/posts/v4l2rtspserver-sur-webcam-arm-not-a-tty#comments">ouvrir dans le navigateur</a>
</p>
ctetruitehttps://linuxfr.org/nodes/133294/comments.atomtag:linuxfr.org,2005:Post/438332023-09-12T14:30:06+02:002023-09-12T14:31:24+02:00Mise en œuvre d'un lecteur de films 4K HDR<p>Bonjour à tous,</p>
<p>Je cherche une carte électronique pour regarder la TV en 4K UHD.</p>
<p>J'ai remarqué que la raspberry pi 4 supporte le 4K mais pas pour tous les standards.</p>
<p>Il me semble que leur CPU embarque le GPU de marque broadcom.</p>
<p>J'ai noté la rock64, après il y en a peut être d'autres mais j'aimerais savoir si vous vous êtes déjà penché la dessus.</p>
<p>Actuellement j'ai l'OS LibreElec pour regarder la TV et je pensais donc à leur liste de cartes.</p>
<p><a href="https://forum.libreelec.tv/board/23-community/">https://forum.libreelec.tv/board/23-community/</a></p>
<p>Merci pour vos retours.</p>
<p>Rock64<br>
4 x ARM Cortex A53 cores @ 1.5 GHz<br>
ARM Mali 450 MP2 GPU</p>
<p>Raspberry-pi<br>
BCM2711<br>
Quad-core Cortex-A72 (ARM v8) 64-bit SoC @ 1.5 GHz.</p>
<div><a href="https://linuxfr.org/forums/linux-embarque/posts/mise-en-oeuvre-d-un-lecteur-de-films-4k-hdr.epub">Télécharger ce contenu au format EPUB</a></div> <p>
<strong>Commentaires :</strong>
<a href="//linuxfr.org/nodes/133265/comments.atom">voir le flux Atom</a>
<a href="https://linuxfr.org/forums/linux-embarque/posts/mise-en-oeuvre-d-un-lecteur-de-films-4k-hdr#comments">ouvrir dans le navigateur</a>
</p>
electro575https://linuxfr.org/nodes/133265/comments.atomtag:linuxfr.org,2005:Post/437672023-08-01T11:43:28+02:002023-08-01T11:58:46+02:00vacances, raspi pico et neveu<p>Bonjour Nal [1],</p>
<p>j'ai récupéré un raspberry pico, et je me demande ce que je peux bien en faire. J'ai deux neveux qui aiment bien la programmation et je me demande si leur donner le pico est une bonne idée.</p>
<p>En gros, je pose la question: qu'est ce qu'on peut faire avec un pico d'amusant? Je suis même prêt à acheter un peu de matos au besoin (moteurs? autres?)<br>
Et côté soft? ça se passe comment?</p>
<p>Merci si vous avez des pistes pour bootstrap mon idée</p>
<p>[1] bon, techniquement c'est pas un journal c'est un forum</p>
<div><a href="https://linuxfr.org/forums/linux-embarque/posts/vacances-raspi-pico-et-neveu.epub">Télécharger ce contenu au format EPUB</a></div> <p>
<strong>Commentaires :</strong>
<a href="//linuxfr.org/nodes/132870/comments.atom">voir le flux Atom</a>
<a href="https://linuxfr.org/forums/linux-embarque/posts/vacances-raspi-pico-et-neveu#comments">ouvrir dans le navigateur</a>
</p>
octanehttps://linuxfr.org/nodes/132870/comments.atomtag:linuxfr.org,2005:Post/436732023-06-15T09:16:23+02:002023-06-15T09:16:23+02:00Créer udev rule pour périphérique USB avec plusieurs ports virtuels<p>Hello Linux community,</p>
<p>Dans le cadre de mon travail sous linux avec différents device USB, je me retrouve à écrire des udev rules afin d'éviter de vérifier le port USB du device à chaque pluggin et de l'ajuster dans le code. </p>
<p>Dans ce processus, un certain périphérique me pose problème car il a deux ports virtuels (config et data), et lorsque je fais mes rules standard, je ne crée qu'un port équivalent au port config, donc le port data est comme ignoré.</p>
<p>Quelqu'un a déjà testé des trucs la dessus ? Une aide peut être ?</p>
<p>Merci,<br>
Lilia</p>
<div><a href="https://linuxfr.org/forums/linux-embarque/posts/creer-udev-rule-pour-peripherique-usb-avec-plusieurs-ports-virtuels.epub">Télécharger ce contenu au format EPUB</a></div> <p>
<strong>Commentaires :</strong>
<a href="//linuxfr.org/nodes/131563/comments.atom">voir le flux Atom</a>
<a href="https://linuxfr.org/forums/linux-embarque/posts/creer-udev-rule-pour-peripherique-usb-avec-plusieurs-ports-virtuels#comments">ouvrir dans le navigateur</a>
</p>
lilipop2513https://linuxfr.org/nodes/131563/comments.atomtag:linuxfr.org,2005:Post/436592023-06-02T16:42:11+02:002023-06-02T16:42:11+02:00Sécuriser la SDCard d'un Raspberry PI4<p>Bonjour,</p>
<p>J'utilise plusieurs PI4 avec le système sur la SDCard sous forme d'un volume unique.</p>
<p>Mais je me pose une question sur la sécurisation de cette SDCard.<br>
Car je prends la SD, je la monte sur un Linux quelconque et je peux bricoler dedans.<br>
Niveau sécurité on a vu mieux.</p>
<p>Connaissez vous des solutions pour résoudre cette lacune ?</p>
<p>J'avoue que coté chiffrement et protection je suis néophyte alors je n'ai pas trop d'idée coté mise en œuvre d'une solution.</p>
<p>Chiffrer la SD me parait une piste mais comment faire en sorte que le contenu soit déchiffré automatiquement et sans que la clé soit sur la SD elle même ?</p>
<p>A vos avis :-)<br>
Merci.</p>
<div><a href="https://linuxfr.org/forums/linux-embarque/posts/securiser-la-sdcard-d-un-raspberry-pi4.epub">Télécharger ce contenu au format EPUB</a></div> <p>
<strong>Commentaires :</strong>
<a href="//linuxfr.org/nodes/131450/comments.atom">voir le flux Atom</a>
<a href="https://linuxfr.org/forums/linux-embarque/posts/securiser-la-sdcard-d-un-raspberry-pi4#comments">ouvrir dans le navigateur</a>
</p>
Philippe GRAILLEhttps://linuxfr.org/nodes/131450/comments.atomtag:linuxfr.org,2005:Post/436542023-05-30T21:30:04+02:002023-05-31T11:15:01+02:00[SMARTPHONES & OS] : Retours d'expériences<p>Bonsoir,</p>
<p>Voila maintenant un moment que j'essaie quelques OS de téléphone.</p>
<p>Dans l'ordre suivant :<br>
-android<br>
-sailfish<br>
-e os<br>
-mobian</p>
<p>Dans le souci de l'opensource et le libre, j'essaie de me tourner d'avantage vers des OS type Linux.</p>
<p>Mes applications principales en plus du classique GPS se tournent vers des clients XMPP/Matrix pour du chat ou de la video.</p>
<p>-<strong>SalfishOS</strong>, je l'ai testé avec un htc one m8 et c'était pas facile de porter le projet sur ce téléphone.<br>
L'écosystème applicatif n'étant pas aussi développé qu'android et le manque de temps pour continuer m'a fait arrêter.<br>
Et puis, il y a la partie UI propriétaire qui me plaisait pas beaucoup.</p>
<p>-Ensuite, j'ai vu le projet <strong>E OS (Murena)</strong> que j'ai testé, qui est un fork d'android avec un purge des lignes de code google (autant que faire ce peu).<br>
Je n'ai pas inspecté leur roadmap mais c'est honorable et peut être aussi un modèle économique.</p>
<p>Le fairephone est aussi interessant mais assez couteux également.</p>
<p>Cet OS fonctionne bien, avec quelques fonctionnalités intéressantes en plus.</p>
<p>-Puis, je me suis mis à l'OS <strong>Mobian</strong> pour être au plus proche de debian que j'utilise quotidiennement.<br>
J'ai acheté le pinephone. L'OS est développé par une communauté.<br>
Le plus gros problème c'est dès que tu utilises des applications un peu gourmandes, la batterie part assez vite !</p>
<p>Et d'après un internaute, les OS linux ne feront jamais assez bien en terme d'<strong>autonomie de la batterie</strong> qu'android à moins d'implémenter les fonctions suivante :<br>
-l'OS sauvegarde l'état de chaque application et peut la suspendre/fermer <br>
-sauvegarde en mémoire l'interface utilisateur et freeze les applications pour reprendre plus tard</p>
<p>Les OS linux comme ceux disponible sur le pinephone : Manjaro, Plasma Mobile (en), Ubuntu Touch, PostmarketOS, Sailfish OS, Mobian, GloDroid</p>
<p>On me dit que la <strong>majorité des personnes qui cherchent un autre OS</strong> se tournent vers postmarketOS et le smartphone onePlus6, je ne sais pas pourquoi exactement.</p>
<p>Que pensez-vous des projets d'OS sous linux et qu'utilisez-vous comme OS/smartphone ?</p>
<p>Avec Mobian et le pinephone, j'arrive à une journée maximum avec peu d'applications et une 4G/Wifi raisonnable. Le GPS est très long à accrocher une position (via plusieurs satellites).</p>
<p>Merci pour vos retours d'expériences.</p>
<p>Bonne journée.</p>
<div><a href="https://linuxfr.org/forums/linux-embarque/posts/smartphones-os-retours-d-experiences.epub">Télécharger ce contenu au format EPUB</a></div> <p>
<strong>Commentaires :</strong>
<a href="//linuxfr.org/nodes/131413/comments.atom">voir le flux Atom</a>
<a href="https://linuxfr.org/forums/linux-embarque/posts/smartphones-os-retours-d-experiences#comments">ouvrir dans le navigateur</a>
</p>
electro575https://linuxfr.org/nodes/131413/comments.atomtag:linuxfr.org,2005:Post/436352023-05-20T12:14:22+02:002023-05-20T12:14:22+02:00hostapd et les conf 5ghz et 6ghz<h2 class="sommaire">Sommaire</h2>
<ul class="toc">
<li><a href="#toc-hostapd--dd-wlan0conf">hostapd -dd wlan0.conf</a></li>
</ul>
<p>Hello.</p>
<p>J'essaie de mettre en place du wifi AP sur ma Mochabin.</p>
<p>J'ai essayé avec une carte wifi 5ghz, driver ath10k et ça fonctionne.</p>
<p>Par contre, j'ai une carte wifi Mediatek, driver mt7915e.</p>
<p>Quand je lance hostapd avec une conf en 2.4ghz, ça fonctionne.<br>
Mais quand je mets une conf 5ghz ( la meme que pour la carte sous le driver ath10k qui fonctionne) ou même 6ghz, il n'y a pas de retour en erreur, ca reste figé sur mgmt::deauth cb<br>
```</p>
<h2 id="toc-hostapd--dd-wlan0conf">hostapd -dd wlan0.conf</h2>
<p>random: Trying to read entropy from /dev/random<br>
Configuration file: wlan0.conf<br>
nl80211: TDLS supported<br>
nl80211: TDLS external setup<br>
nl80211: Supported cipher 00-0f-ac:1<br>
nl80211: Supported cipher 00-0f-ac:5<br>
nl80211: Supported cipher 00-0f-ac:2<br>
nl80211: Supported cipher 00-0f-ac:4<br>
nl80211: Supported cipher 00-0f-ac:10<br>
nl80211: Supported cipher 00-0f-ac:8<br>
nl80211: Supported cipher 00-0f-ac:9<br>
nl80211: Supported cipher 00-0f-ac:6<br>
nl80211: Supported cipher 00-0f-ac:13<br>
nl80211: Supported cipher 00-0f-ac:11<br>
nl80211: Supported cipher 00-0f-ac:12<br>
nl80211: Using driver-based off-channel TX<br>
nl80211: Driver-advertised extended capabilities (default) - hexdump(len=8): 00 00 40 00 00 00 00 40<br>
nl80211: Driver-advertised extended capabilities mask (default) - hexdump(len=8): 00 00 40 00 00 00 00 40<br>
nl80211: key_mgmt=0x1ff0f enc=0xfef auth=0x7 flags=0x4003d31db5bd8e0 rrm_flags=0x10 probe_resp_offloads=0x0 max_stations=0 max_remain_on_chan=5000 max_scan_ssids=4<br>
nl80211: interface wlan1 in phy phy1<br>
nl80211: Set mode ifindex 8 iftype 3 (AP)<br>
nl80211: Failed to set interface 8 to mode 3: -16 (Device or resource busy)<br>
nl80211: Try mode change after setting interface down<br>
nl80211: Set mode ifindex 8 iftype 3 (AP)<br>
nl80211: Mode change succeeded while interface is down<br>
nl80211: Setup AP(wlan1) - device_ap_sme=0 use_monitor=0<br>
nl80211: Subscribe to mgmt frames with AP handle 0xaaaafeb7c9a0<br>
nl80211: Register frame type=0xb0 (WLAN_FC_STYPE_AUTH) nl_handle=0xaaaafeb7c9a0 match= multicast=0<br>
nl80211: Register frame type=0x0 (WLAN_FC_STYPE_ASSOC_REQ) nl_handle=0xaaaafeb7c9a0 match= multicast=0<br>
nl80211: Register frame type=0x20 (WLAN_FC_STYPE_REASSOC_REQ) nl_handle=0xaaaafeb7c9a0 match= multicast=0<br>
nl80211: Register frame type=0xa0 (WLAN_FC_STYPE_DISASSOC) nl_handle=0xaaaafeb7c9a0 match= multicast=0<br>
nl80211: Register frame type=0xc0 (WLAN_FC_STYPE_DEAUTH) nl_handle=0xaaaafeb7c9a0 match= multicast=0<br>
nl80211: Register frame type=0x40 (WLAN_FC_STYPE_PROBE_REQ) nl_handle=0xaaaafeb7c9a0 match= multicast=0<br>
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xaaaafeb7c9a0 match=04 multicast=0<br>
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xaaaafeb7c9a0 match=0501 multicast=0<br>
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xaaaafeb7c9a0 match=0503 multicast=0<br>
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xaaaafeb7c9a0 match=0504 multicast=0<br>
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xaaaafeb7c9a0 match=06 multicast=0<br>
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xaaaafeb7c9a0 match=08 multicast=0<br>
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xaaaafeb7c9a0 match=09 multicast=0<br>
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xaaaafeb7c9a0 match=0a multicast=0<br>
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xaaaafeb7c9a0 match=11 multicast=0<br>
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xaaaafeb7c9a0 match=7f multicast=0<br>
rfkill: Cannot open RFKILL control device<br>
nl80211: RFKILL status not available<br>
nl80211: Add own interface ifindex 8 (ifidx_reason -1)<br>
nl80211: if_indices[16]: 8(-1)<br>
nl80211: Do not open EAPOL RX socket - using control port for RX<br>
phy: phy1<br>
BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)<br>
wlan1: interface state UNINITIALIZED->COUNTRY_UPDATE<br>
Previous country code FR, new country code FR<br>
nl80211: Regulatory information - country=FR (DFS-ETSI)<br>
nl80211: 2400-2483 @ 40 MHz 20 mBm<br>
nl80211: 5150-5250 @ 80 MHz 23 mBm (no outdoor)<br>
nl80211: 5250-5350 @ 80 MHz 20 mBm (no outdoor) (DFS)<br>
nl80211: 5470-5725 @ 160 MHz 26 mBm (DFS)<br>
nl80211: 5725-5875 @ 80 MHz 13 mBm<br>
nl80211: 5945-6425 @ 160 MHz 23 mBm (no outdoor)<br>
nl80211: 57000-71000 @ 2160 MHz 40 mBm<br>
nl80211: Mode IEEE 802.11a: 5180 5200 5220 5240 5260[RADAR] 5280[RADAR] 5300[RADAR] 5320[RADAR] 5500[RADAR] 5520[RADAR] 5540[RADAR] 5560[RADAR] 5580[RADAR] 5600[RADAR] 5620[RADAR] 5640[RADAR] 5660[RADAR] 5680[RADAR]<br>
nl80211: Mode IEEE 802.11a: 5955 5975 5995 6015 6035 6055 6075 6095 6115 6135 6155 6175 6195 6215 6235 6255 6275 6295 6315 6335 6355 6375 6395 6415 6435[DISABLED] 6455[DISABLED] 6475[DISABLED] 6495[DISABLED] 6515[DISABLED]<br>
Allowed channel: mode=2 chan=36 freq=5180 MHz max_tx_power=23 dBm<br>
Allowed channel: mode=2 chan=40 freq=5200 MHz max_tx_power=23 dBm<br>
Allowed channel: mode=2 chan=44 freq=5220 MHz max_tx_power=23 dBm<br>
Allowed channel: mode=2 chan=48 freq=5240 MHz max_tx_power=23 dBm<br>
Allowed channel: mode=2 chan=52 freq=5260 MHz max_tx_power=20 dBm (DFS state = usable)<br>
Allowed channel: mode=2 chan=56 freq=5280 MHz max_tx_power=20 dBm (DFS state = usable)<br>
Allowed channel: mode=2 chan=60 freq=5300 MHz max_tx_power=20 dBm (DFS state = usable)<br>
Allowed channel: mode=2 chan=64 freq=5320 MHz max_tx_power=20 dBm (DFS state = usable)<br>
Allowed channel: mode=2 chan=100 freq=5500 MHz max_tx_power=26 dBm (DFS state = usable)<br>
Allowed channel: mode=2 chan=104 freq=5520 MHz max_tx_power=26 dBm (DFS state = usable)<br>
Allowed channel: mode=2 chan=108 freq=5540 MHz max_tx_power=26 dBm (DFS state = usable)<br>
Allowed channel: mode=2 chan=112 freq=5560 MHz max_tx_power=26 dBm (DFS state = usable)<br>
Allowed channel: mode=2 chan=116 freq=5580 MHz max_tx_power=26 dBm (DFS state = usable)<br>
Allowed channel: mode=2 chan=120 freq=5600 MHz max_tx_power=26 dBm (DFS state = usable)<br>
Allowed channel: mode=2 chan=124 freq=5620 MHz max_tx_power=26 dBm (DFS state = usable)<br>
Allowed channel: mode=2 chan=128 freq=5640 MHz max_tx_power=26 dBm (DFS state = usable)<br>
Allowed channel: mode=2 chan=132 freq=5660 MHz max_tx_power=26 dBm (DFS state = usable)<br>
Allowed channel: mode=2 chan=136 freq=5680 MHz max_tx_power=26 dBm (DFS state = usable)<br>
Allowed channel: mode=2 chan=140 freq=5700 MHz max_tx_power=26 dBm (DFS state = usable)<br>
Allowed channel: mode=2 chan=144 freq=5720 MHz max_tx_power=0 dBm (DFS state = usable)<br>
Allowed channel: mode=2 chan=149 freq=5745 MHz max_tx_power=13 dBm<br>
Allowed channel: mode=2 chan=153 freq=5765 MHz max_tx_power=13 dBm<br>
Allowed channel: mode=2 chan=157 freq=5785 MHz max_tx_power=13 dBm<br>
Allowed channel: mode=2 chan=161 freq=5805 MHz max_tx_power=13 dBm<br>
Allowed channel: mode=2 chan=165 freq=5825 MHz max_tx_power=13 dBm<br>
Allowed channel: mode=2 chan=169 freq=5845 MHz max_tx_power=13 dBm<br>
Allowed channel: mode=2 chan=173 freq=5865 MHz max_tx_power=13 dBm<br>
Allowed channel: mode=2 chan=1 freq=5955 MHz max_tx_power=23 dBm<br>
Allowed channel: mode=2 chan=5 freq=5975 MHz max_tx_power=23 dBm<br>
Allowed channel: mode=2 chan=9 freq=5995 MHz max_tx_power=23 dBm<br>
Allowed channel: mode=2 chan=13 freq=6015 MHz max_tx_power=23 dBm<br>
Allowed channel: mode=2 chan=17 freq=6035 MHz max_tx_power=23 dBm<br>
Allowed channel: mode=2 chan=21 freq=6055 MHz max_tx_power=23 dBm<br>
Allowed channel: mode=2 chan=25 freq=6075 MHz max_tx_power=23 dBm<br>
Allowed channel: mode=2 chan=29 freq=6095 MHz max_tx_power=23 dBm<br>
Allowed channel: mode=2 chan=33 freq=6115 MHz max_tx_power=23 dBm<br>
Allowed channel: mode=2 chan=37 freq=6135 MHz max_tx_power=23 dBm<br>
Allowed channel: mode=2 chan=41 freq=6155 MHz max_tx_power=23 dBm<br>
Allowed channel: mode=2 chan=45 freq=6175 MHz max_tx_power=23 dBm<br>
Allowed channel: mode=2 chan=49 freq=6195 MHz max_tx_power=23 dBm<br>
Allowed channel: mode=2 chan=53 freq=6215 MHz max_tx_power=23 dBm<br>
Allowed channel: mode=2 chan=57 freq=6235 MHz max_tx_power=23 dBm<br>
Allowed channel: mode=2 chan=61 freq=6255 MHz max_tx_power=23 dBm<br>
Allowed channel: mode=2 chan=65 freq=6275 MHz max_tx_power=23 dBm<br>
Allowed channel: mode=2 chan=69 freq=6295 MHz max_tx_power=23 dBm<br>
Allowed channel: mode=2 chan=73 freq=6315 MHz max_tx_power=23 dBm<br>
Allowed channel: mode=2 chan=77 freq=6335 MHz max_tx_power=23 dBm<br>
Allowed channel: mode=2 chan=81 freq=6355 MHz max_tx_power=23 dBm<br>
Allowed channel: mode=2 chan=85 freq=6375 MHz max_tx_power=23 dBm<br>
Allowed channel: mode=2 chan=89 freq=6395 MHz max_tx_power=23 dBm<br>
Allowed channel: mode=2 chan=93 freq=6415 MHz max_tx_power=23 dBm<br>
hw vht capab: 0x339a59f6, conf vht capab: 0x0<br>
wlan1: interface state COUNTRY_UPDATE->HT_SCAN<br>
Scan for neighboring BSSes prior to enabling 40 MHz channel<br>
40 MHz affected channel range: [5190,5230] MHz<br>
wlan1: nl80211: scan request<br>
nl80211: Passive scan requested<br>
nl80211: Scan frequency 5200 MHz<br>
nl80211: Scan frequency 5220 MHz<br>
Scan requested (ret=0) - scan timeout 10 seconds<br>
Interface initialization will be completed in a callback<br>
ctrl_iface not configured!<br>
random: Got 20/20 bytes from /dev/random<br>
RTM_NEWLINK: ifi_index=8 ifname=wlan1 operstate=2 linkmode=0 ifi_family=0 ifi_flags=0x1002 ()<br>
nl80211: Ignore interface down event since interface wlan1 is up<br>
RTM_NEWLINK: ifi_index=8 ifname=wlan1 operstate=2 linkmode=0 ifi_family=0 ifi_flags=0x1003 ([UP])<br>
nl80211: Event message available<br>
nl80211: Drv Event 33 (NL80211_CMD_TRIGGER_SCAN) received for wlan1<br>
wlan1: nl80211: Scan trigger<br>
wlan1: Event SCAN_STARTED (47) received<br>
Unknown event 47<br>
RTM_NEWLINK: ifi_index=8 ifname=wlan1 wext ifi_family=0 ifi_flags=0x1003 ([UP])<br>
nl80211: Event message available<br>
nl80211: Drv Event 34 (NL80211_CMD_NEW_SCAN_RESULTS) received for wlan1<br>
wlan1: nl80211: New scan results available<br>
nl80211: Scan included frequencies: 5200 5220<br>
wlan1: Event SCAN_RESULTS (3) received<br>
nl80211: Received scan results (0 BSSes)<br>
HT40: control channel: 40 (5200 MHz), secondary channel: 44 (5220 MHz)<br>
HT40 channel pair (40, 44) not allowed<br>
Fallback to 20 MHz<br>
Completing interface initialization<br>
Mode: IEEE 802[ 211.650331] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready<br>
.11a Channel: 40 Frequency: 5200 MHz<br>
DFS 0 channels required radar detection<br>
nl80211: Set freq 5200 (ht_enabled=1, vht_enabled=1, he_enabled=0, bandwidth=20 MHz, cf1=5200 MHz, cf2=0 MHz)<br>
* freq=5200<br>
* he_enabled=0<br>
* vht_enabled=1<br>
* ht_enabled=1<br>
* bandwidth=20<br>
* channel_width=1<br>
* center_freq1=5200<br>
* center_freq2=0<br>
RATE[0] rate=60 flags=0x1<br>
RATE[1] rate=90 flags=0x0<br>
RATE[2] rate=120 flags=0x1<br>
RATE[3] rate=180 flags=0x0<br>
RATE[4] rate=240 flags=0x1<br>
RATE[5] rate=360 flags=0x0<br>
RATE[6] rate=480 flags=0x0<br>
RATE[7] rate=540 flags=0x0<br>
hostapd_setup_bss(hapd=0xaaaafeb7bae0 (wlan1), first=1)<br>
nl80211: flush -> DEL_STATION wlan1 (all)<br>
Using interface wlan1 with hwaddr 00:0a:52:08:32:49 and ssid "doudoo_diagbox"<br>
Deriving WPA PSK based on passphrase<br>
SSID - hexdump_ascii(len=14):<br>
64 6f 75 64 6f 6f 5f 64 69 61 67 62 6f 78 doudoo_diagbox<br>
PSK (ASCII passphrase) - hexdump_ascii(len=8): [REMOVED]<br>
PSK (from passphrase) - hexdump(len=32): [REMOVED]<br>
Get randomness: len=32 entropy=0<br>
GMK - hexdump(len=32): [REMOVED]<br>
Get randomness: len=32 entropy=0<br>
Key Counter - hexdump(len=32): [REMOVED]<br>
WPA: Delay group state machine start until Beacon frames have been configured<br>
nl80211: Set beacon (beacon_set=0)<br>
nl80211: Beacon head - hexdump(len=65): 80 00 00 00 ff ff ff ff ff ff 00 0a 52 08 32 49 00 0a 52 08 32 49 00 00 00 00 00 00 00 00 00 00 64 00 11 00 00 0e 64 6f 75 64 6f 6f 5f 64 69 61 67 62 6f 78 01 08 8c 12 98 24 b0 48 60 6c 03 01 28<br>
nl80211: Beacon tail - hexdump(len=161): 07 12 46 52 20 24 04 17 34 04 14 64 0b 1a 90 01 00 95 07 0d 3b 02 73 00 2d 1a 4e 08 17 ff ff 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 3d 16 28 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 7f 08 04 00 40 00 00 00 00 40 bf 0c 00 00 00 00 fa ff 00 00 fa ff 00 20 c0 05 00 00 00 fc ff c3 02 00 2e dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 dd 18 00 50 f2 02 01 01 01 00 03 a4 00 00 27 a4 00 00 42 43 5e 00 62 32 2f 00<br>
nl80211: ifindex=8<br>
nl80211: beacon_int=100<br>
nl80211: beacon_rate=0<br>
nl80211: rate_type=0<br>
nl80211: dtim_period=2<br>
nl80211: ssid=doudoo_diagbox<br>
* beacon_int=100<br>
* dtim_period=2<br>
nl80211: hidden SSID not in use<br>
nl80211: privacy=1<br>
nl80211: auth_algs=0x1<br>
nl80211: wpa_version=0x1<br>
nl80211: key_mgmt_suites=0x2<br>
nl80211: pairwise_ciphers=0x8<br>
nl80211: group_cipher=0x8<br>
nl80211: beacon_ies - hexdump(len=10): 7f 08 04 00 40 00 00 00 00 40<br>
nl80211: proberesp_ies - hexdump(len=10): 7f 08 04 00 40 00 00 00 00 40<br>
nl80211: assocresp_ies - hexdump(len=10): 7f 08 04 00 40 00 00 00 00 40<br>
nl80211: twt_responder=1<br>
nl80211: multicast to unicast disabled on interface wlan1<br>
wlan1: Deauthenticate all stations at BSS start<br>
nl80211: send_mlme - da=ff:ff:ff:ff:ff:ff noack=0 freq=0 no_cck=0 offchanok=0 wait_time=0 no_encrypt=0 fc=0xc0 (WLAN_FC_STYPE_DEAUTH) nlmode=3<br>
nl80211: send_mlme - Use bss->freq=5200<br>
nl80211: send_mlme -> send_frame_cmd<br>
nl80211: CMD_FRAME freq=5200 wait=0 no_cck=0 no_ack=0 offchanok=0<br>
CMD_FRAME - hexdump(len=26): c0 00 00 00 ff ff ff ff ff ff 00 0a 52 08 32 49 00 0a 52 08 32 49 00 00 02 00<br>
nl80211: Frame TX command accepted; cookie 0x3<br>
WPA: Start group state machine to set initial keys<br>
WPA: group state machine entering state GTK_INIT (VLAN-ID 0)<br>
Get randomness: len=32 entropy=0<br>
GTK - hexdump(len=32): [REMOVED]<br>
WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0)<br>
wpa_driver_nl80211_set_key: ifindex=8 (wlan1) alg=2 addr=0xaaaad86fe4bf key_idx=1 set_tx=1 seq_len=0 key_len=32 key_flag=0x1a<br>
nl80211: NEW_KEY<br>
nl80211: KEY_DATA - hexdump(len=32): [REMOVED]<br>
broadcast key<br>
nl80211: NL80211_CMD_SET_KEY - default key<br>
nl80211: Set wlan1 operstate 0->1 (UP)<br>
netlink: Operstate: ifindex=8 linkmode=-1 (no change), operstate=6 (IF_OPER_UP)<br>
nl80211: TX queue param set: queue=0 aifs=1 cw_min=3 cw_max=7 burst_time=15 --> res=0<br>
nl80211: TX queue param set: queue=1 aifs=1 cw_min=7 cw_max=15 burst_time=30 --> res=0<br>
nl80211: TX queue param set: queue=2 aifs=3 cw_min=15 cw_max=63 burst_time=0 --> res=0<br>
nl80211: TX queue param set: queue=3 aifs=7 cw_min=15 cw_max=1023 burst_time=0 --> res=0<br>
wlan1: interface state HT_SCAN->ENABLED<br>
wlan1: AP-ENABLED<br>
wlan1: Setup of interface done.<br>
RTM_NEWLINK: ifi_index=8 ifname=wlan1 operstate=6 linkmode=0 ifi_family=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])<br>
nl80211: Event message available<br>
nl80211: Drv Event 60 (NL80211_CMD_FRAME_TX_STATUS) received for wlan1<br>
nl80211: MLME event 60 (NL80211_CMD_FRAME_TX_STATUS) on wlan1(00:0a:52:08:32:49) A1=ff:ff:ff:ff:ff:ff A2=00:0a:52:08:32:49<br>
nl80211: MLME event frame - hexdump(len=26): c0 00 00 00 ff ff ff ff ff ff 00 0a 52 08 32 49 00 0a 52 08 32 49 00 00 02 00<br>
nl80211: Frame TX status event A1=ff:ff:ff:ff:ff:ff stype=12 cookie=0x3 ack=0<br>
wlan1: Event TX_STATUS (16) received<br>
mgmt::deauth cb</p>
<p>```Voici la conf de Hostapd : </p>
<pre><code># Interface wifi
interface=wlan1
# SSID et clef de securite
ssid=doudoo_diagbox
wpa_passphrase=12345678
# Mode :
hw_mode=a
# Canal
channel=40
# Wifi 4
ieee80211n=1
ht_capab=[HT40+][HT40-][SHORT-GI-40][MAX-AMSDU-7935]
# Wifi 5
ieee80211ac=1
vht_oper_chwidth=0
#vht_oper_centr_freq_seg0_idx=
#vht_capab=
# DFS
ieee80211h=1
ieee80211h=1
ieee80211d=1
country_code=FR
# Algo de secu
auth_algs=1
#wpa=2
wpa=1
wpa_key_mgmt=WPA-PSK
rsn_pairwise=CCMP
macaddr_acl=0
# Bridge Lan
#bridge=br-wifi
# QoS
wmm_enabled=1
wmm_ac_bk_cwmin=4
wmm_ac_bk_cwmax=10
wmm_ac_bk_aifs=7
wmm_ac_bk_txop_limit=0
wmm_ac_bk_acm=0
wmm_ac_be_aifs=3
wmm_ac_be_cwmin=4
wmm_ac_be_cwmax=10
wmm_ac_be_txop_limit=0
wmm_ac_be_acm=0
wmm_ac_vi_aifs=2
wmm_ac_vi_cwmin=3
wmm_ac_vi_cwmax=4
wmm_ac_vi_txop_limit=94
wmm_ac_vi_acm=0
wmm_ac_vo_aifs=2
wmm_ac_vo_cwmin=2
wmm_ac_vo_cwmax=3
wmm_ac_vo_txop_limit=47
wmm_ac_vo_acm=0
tx_queue_data3_aifs=7
tx_queue_data3_cwmin=15
tx_queue_data3_cwmax=1023
tx_queue_data3_burst=0
tx_queue_data2_aifs=3
tx_queue_data2_cwmin=15
tx_queue_data2_cwmax=63
tx_queue_data2_burst=0
tx_queue_data1_aifs=1
tx_queue_data1_cwmin=7
tx_queue_data1_cwmax=15
tx_queue_data1_burst=3.0
tx_queue_data0_aifs=1
tx_queue_data0_cwmin=3
tx_queue_data0_cwmax=7
tx_queue_data0_burst=1.5
# Logs
logger_syslog=0
logger_syslog_level=4
logger_stdout=-1
logger_stdout_level=0
</code></pre>
<p>Merci d'avance :)</p>
<div><a href="https://linuxfr.org/forums/linux-embarque/posts/hostapd-et-les-conf-5ghz-et-6ghz.epub">Télécharger ce contenu au format EPUB</a></div> <p>
<strong>Commentaires :</strong>
<a href="//linuxfr.org/nodes/131292/comments.atom">voir le flux Atom</a>
<a href="https://linuxfr.org/forums/linux-embarque/posts/hostapd-et-les-conf-5ghz-et-6ghz#comments">ouvrir dans le navigateur</a>
</p>
doudootianahttps://linuxfr.org/nodes/131292/comments.atomtag:linuxfr.org,2005:Post/436342023-05-20T08:35:53+02:002023-05-20T20:14:18+02:00commande ethtool<p>Hello :)</p>
<p>Je travaille sur une carte Mochabin de GlobalScale.<br>
Elle possède une cage sfp+ et une sfp.</p>
<p>Lorsque j'essaie de récupérer des infos via la commande ethtool -m, il manque des informations :</p>
<pre><code> # ethtool -m eth2
Identifier : 0x03 (SFP)
Extended identifier : 0x04 (GBIC/SFP defined by 2-wire interface ID)
Connector : 0x01 (SC)
Transceiver codes : 0x00 0x0a 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Transceiver type : SONET: SONET reach specifier bit 2
Transceiver type : SONET: OC-48, intermediate reach
Encoding : 0x03 (NRZ)
BR, Nominal : 2500MBd
Rate identifier : 0x0c (reserved or unknown)
Length (SMF,km) : 50km
Length (SMF) : 0m
Length (50um) : 0m
Length (62.5um) : 0m
Length (Copper) : 0m
Length (OM3) : 0m
Laser wavelength : 38275nm
Vendor name : Hisense
Vendor OUI : 00:1a:95
Vendor PN : LTE3678M-BH+
Vendor rev : 1.0
Option values : 0x00 0x1a
Option : RX_LOS implemented
Option : TX_FAULT implemented
Option : TX_DISABLE implemented
BR margin, max : 20%
BR margin, min : 20%
Vendor SN : HISCCN2102K780
Date code : 210108
# ethtool -m eth0
Identifier : 0x03 (SFP)
Extended identifier : 0x04 (GBIC/SFP defined by 2-wire interface ID)
Connector : 0x01 (SC)
Transceiver codes : 0x00 0x00 0x00 0x02 0x00 0x00 0x00 0x00 0x00
Transceiver type : Ethernet: 1000BASE-LX
Encoding : 0x03 (NRZ)
BR, Nominal : 1200MBd
Rate identifier : 0x00 (unspecified)
Length (SMF,km) : 20km
Length (SMF) : 20000m
Length (50um) : 0m
Length (62.5um) : 0m
Length (Copper) : 0m
Length (OM3) : 0m
Laser wavelength : 1310nm
Vendor name : FS
Vendor OUI : 00:00:00
Vendor PN : GSFP-ONU-SC
Vendor rev : 01
Option values : 0x00 0x1a
Option : RX_LOS implemented
Option : TX_FAULT implemented
Option : TX_DISABLE implemented
BR margin, max : 0%
BR margin, min : 0%
Vendor SN : SCOM210A1F5A
Date code : 211007
</code></pre>
<p>L'information que j'aimerais récupérer est le signal rx et tx du laser.<br>
J'ai essayé les modules sfp sur une autre carte et les infos voulues apparaissent.</p>
<p>Quelqu'un aurait une idée?<br>
Merci par avance ;)</p>
<div><a href="https://linuxfr.org/forums/linux-embarque/posts/commande-ethtool.epub">Télécharger ce contenu au format EPUB</a></div> <p>
<strong>Commentaires :</strong>
<a href="//linuxfr.org/nodes/131284/comments.atom">voir le flux Atom</a>
<a href="https://linuxfr.org/forums/linux-embarque/posts/commande-ethtool#comments">ouvrir dans le navigateur</a>
</p>
doudootianahttps://linuxfr.org/nodes/131284/comments.atomtag:linuxfr.org,2005:Post/436032023-05-02T20:31:02+02:002023-05-02T20:31:02+02:00 portails, controle d'entrée : reprendre l'indépendance sans fil? <p>bonjour</p>
<p>je ne sais pas du tout où mettre cela mais bon. (peut etre un journal?)<br>
depuis quelques années je vois "fleurir" un bon nombre d'interphones qui se greffent aux immeubles.<br>
tout va bien, jusqu'à la problématique : l'interface n'est plus l'interphone relais situé dans l'entrée de chaque logement, mais au niveau du téléphone portable de la personne.<br>
pour moi, ce phénomène qui s'impose (et qui va à contre courant, dans le "lard", d'un certain business à ""valeur"" ajoutée), apporte surtout deux magistraux inconvénients :<br>
1. la dépendance de structures tierces, externes :<br>
la compagnie qui s'occupe de faire le lien entre l'interphone par voie cellulaire, souvent visio pixellisée sur une vieille 3G, facturée à prix d'or au syndic<br>
2. la dépendance à un outil le plus volatile après les clés de voiture : le téléphone portable.<br>
Si celui ci est indisponible, on ne peut donc plus ouvrir chez soi. C'est comme le guichet en ligne pour les banques, au lieu du guichetier physique : cela délocalise l'investissement sur le résident au lieu de dédier un interphone au logement, surtout s'il est loué. Imaginez le bordel pour les colocs!</p>
<p>je m'interrogeais donc : ayant reçu plusieurs dizaines d'avis négatifs et très réservés sur cette nouvelle tendance d'interphones, est il possible pour un syndic, juridiquement, mais surtout sur le plan pratique, de remplacer ce genre de système par quelque chose de filaire ou de transmission radio avec simple bouton ou intercom à chaque logement?</p>
<p>est ce que certains ont tenté de retrouver une certaine indépendance par rapport à ces prestataires?<br>
j'ai l'impression que les fournisseurs de solutions de portail/controle d'entrée, en sont arrivés à l'idée de génie pour l'argent, de faire non pas une pose simple, mais pose+location à l'année (un peu comme les logiciels d'aujourd'hui)</p>
<p>qu'en pensez vous?<br>
possible de refaire un pas vers l'indépendance de prestataires pour ce genre de situation?</p>
<p>pour la petite histoire, juste après le covid, une connaissance m'a rapporté que son voisin s'était fait cambrioler, par une idée toute bete :<br>
les cambrioleurs, comprenant que les interphones sont reliés au tel, ont appelé un résident, qui a répliqué via son portable qu'il était en vacances à l'étranger. Evidemment, cela n'a pas découragé les cambrioleurs de le visiter.</p>
<p>en campagne, je vois beaucoup de portails qui s'ouvrent avec code, ou simple télécommande, et interphone/bouton dans l'entrée.. j'imagine qu'un tel système "démultiplié" pourrait revenir moins cher, et surtout indépendant des réseaux mobiles?</p>
<p>merci de vos impressions</p>
<div><a href="https://linuxfr.org/forums/linux-embarque/posts/portails-controle-d-entree-reprendre-l-independance-sans-fil.epub">Télécharger ce contenu au format EPUB</a></div> <p>
<strong>Commentaires :</strong>
<a href="//linuxfr.org/nodes/131110/comments.atom">voir le flux Atom</a>
<a href="https://linuxfr.org/forums/linux-embarque/posts/portails-controle-d-entree-reprendre-l-independance-sans-fil#comments">ouvrir dans le navigateur</a>
</p>
tkrhttps://linuxfr.org/nodes/131110/comments.atomtag:linuxfr.org,2005:Post/435872023-04-21T19:34:26+02:002023-04-21T19:34:26+02:00Port ethernet up mais aucun flux<h2 class="sommaire">Sommaire</h2>
<ul class="toc">
<li><a href="#toc-dmesg">dmesg</a></li>
</ul>
<p>Hello.</p>
<p>JE travaille sur une Clearfog base cn9130.<br>
Elle possède deux ports éthernet (eth1 et eth2) et un port sfp (eth0).</p>
<p>Les interfaces eth0 et eth1 fonctionnent.</p>
<p>Cependant pour eth2 :<br>
j'arrive à l'activer mais aucun flux ne passe (test ping etc…).</p>
<p>Pourtant je n'ai aucune erreur dans le dmesg <br>
```</p>
<h2 id="toc-dmesg">dmesg</h2>
<p>[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd083]<br>
[ 0.000000] Linux version 5.15.0 (root@workstation) (aarch64-linux-gnu-gcc (Linaro GCC 7.5-2019.12) 7.5.0, GNU ld (Linaro_Binutils-2019.12) 2.28.2.20170706) #1 SMP PREEMPT Fri Apr 21 19:02:50 CEST 2023<br>
[ 0.000000] Machine model: SolidRun CN9130 based SOM Clearfog Base<br>
[ 0.000000] earlycon: uart8250 at MMIO32 0x00000000f0512000 (options '')<br>
[ 0.000000] printk: bootconsole [uart8250] enabled<br>
[ 0.000000] efi: UEFI not found.<br>
[ 0.000000] NUMA: No NUMA configuration found<br>
[ 0.000000] NUMA: Faking a node at [mem 0x0000000000000000-0x000000013fffffff]<br>
[ 0.000000] NUMA: NODE_DATA [mem 0x13f7d5c00-0x13f7d7fff]<br>
[ 0.000000] Zone ranges:<br>
[ 0.000000] DMA [mem 0x0000000000000000-0x00000000ffffffff]<br>
[ 0.000000] DMA32 empty<br>
[ 0.000000] Normal [mem 0x0000000100000000-0x000000013fffffff]<br>
[ 0.000000] Movable zone start for each node<br>
[ 0.000000] Early memory node ranges<br>
[ 0.000000] node 0: [mem 0x0000000000000000-0x0000000003ffffff]<br>
[ 0.000000] node 0: [mem 0x0000000004000000-0x00000000041fffff]<br>
[ 0.000000] node 0: [mem 0x0000000004200000-0x00000000bfffffff]<br>
[ 0.000000] node 0: [mem 0x0000000100000000-0x000000013fffffff]<br>
[ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000013fffffff]<br>
[ 0.000000] cma: Reserved 32 MiB at 0x00000000be000000<br>
[ 0.000000] psci: probing for conduit method from DT.<br>
[ 0.000000] psci: PSCIv1.1 detected in firmware.<br>
[ 0.000000] psci: Using standard PSCI v0.2 function IDs<br>
[ 0.000000] psci: MIGRATE_INFO_TYPE not supported.<br>
[ 0.000000] psci: SMC Calling Convention v1.2<br>
[ 0.000000] percpu: Embedded 19 pages/cpu s40152 r8192 d29480 u77824<br>
[ 0.000000] pcpu-alloc: s40152 r8192 d29480 u77824 alloc=19*4096<br>
[ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3<br>
[ 0.000000] Detected PIPT I-cache on CPU0<br>
[ 0.000000] CPU features: detected: Spectre-v2<br>
[ 0.000000] CPU features: detected: Spectre-v3a<br>
[ 0.000000] CPU features: detected: ARM errata 1165522, 1319367, or 1530923<br>
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 1032192<br>
[ 0.000000] Policy zone: Normal<br>
[ 0.000000] Kernel command line: board=base console=ttyS0,115200n1 earlycon=uart8250,mmio32,0xf0512000 debug=7 initrd=0x9000000,550M<br>
[ 0.000000] Unknown command line parameters: board=base<br>
[ 0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes, linear)<br>
[ 0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)<br>
[ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off<br>
[ 0.000000] software IO TLB: mapped <a href="64MB">mem 0x00000000ba000000-0x00000000be000000</a><br>
[ 0.000000] Memory: 3427532K/4194304K available (12928K kernel code, 1282K rwdata, 4948K rodata, 2304K init, 444K bss, 734004K reserved, 32768K cma-reserved)<br>
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1<br>
[ 0.000000] rcu: Preemptible hierarchical RCU implementation.<br>
[ 0.000000] rcu: RCU event tracing is enabled.<br>
[ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4.<br>
[ 0.000000] Trampoline variant of Tasks RCU enabled.<br>
[ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.<br>
[ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4<br>
[ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0<br>
[ 0.000000] GIC: Adjusting CPU interface base to 0x00000000f022f000<br>
[ 0.000000] Root IRQ handler: gic_handle_irq<br>
[ 0.000000] GIC: Using split EOI/Deactivate mode<br>
[ 0.000000] GICv2m: DT overriding V2M MSI_TYPER (base:160, num:32)<br>
[ 0.000000] GICv2m: range[mem 0xf0280000-0xf0280fff], SPI[160:191]<br>
[ 0.000000] GICv2m: DT overriding V2M MSI_TYPER (base:192, num:32)<br>
[ 0.000000] GICv2m: range[mem 0xf0290000-0xf0290fff], SPI[192:223]<br>
[ 0.000000] GICv2m: DT overriding V2M MSI_TYPER (base:224, num:32)<br>
[ 0.000000] GICv2m: range[mem 0xf02a0000-0xf02a0fff], SPI[224:255]<br>
[ 0.000000] GICv2m: DT overriding V2M MSI_TYPER (base:256, num:32)<br>
[ 0.000000] GICv2m: range[mem 0xf02b0000-0xf02b0fff], SPI[256:287]<br>
[ 0.000000] random: get_random_bytes called from start_kernel+0x484/0x674 with crng_init=0<br>
[ 0.000000] arch_timer: cp15 timer(s) running at 25.00MHz (phys).<br>
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x5c40939b5, max_idle_ns: 440795202646 ns<br>
[ 0.000000] sched_clock: 56 bits at 25MHz, resolution 40ns, wraps every 4398046511100ns<br>
[ 0.008332] Console: colour dummy device 80x25<br>
[ 0.012873] Calibrating delay loop (skipped), value calculated using timer frequency.. 50.00 BogoMIPS (lpj=100000)<br>
[ 0.023416] pid_max: default: 32768 minimum: 301<br>
[ 0.028136] LSM: Security Framework initializing<br>
[ 0.032868] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)<br>
[ 0.040459] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)<br>
[ 0.049056] rcu: Hierarchical SRCU implementation.<br>
[ 0.054206] EFI services will not be available.<br>
[ 0.058873] smp: Bringing up secondary CPUs …<br>
[ 0.063863] Detected PIPT I-cache on CPU1<br>
[ 0.063898] CPU1: Booted secondary processor 0x0000000001 [0x410fd083]<br>
[ 0.064319] Detected PIPT I-cache on CPU2<br>
[ 0.064343] CPU2: Booted secondary processor 0x0000000100 [0x410fd083]<br>
[ 0.064773] Detected PIPT I-cache on CPU3<br>
[ 0.064791] CPU3: Booted secondary processor 0x0000000101 [0x410fd083]<br>
[ 0.064825] smp: Brought up 1 node, 4 CPUs<br>
[ 0.101099] SMP: Total of 4 processors activated.<br>
[ 0.105884] CPU features: detected: 32-bit EL0 Support<br>
[ 0.111136] CPU features: detected: 32-bit EL1 Support<br>
[ 0.116367] CPU features: detected: CRC32 instructions<br>
[ 0.128851] CPU: All CPU(s) started at EL2<br>
[ 0.133027] alternatives: patching kernel code<br>
[ 0.138450] devtmpfs: initialized<br>
[ 0.143487] KASLR disabled due to lack of seed<br>
[ 0.148073] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns<br>
[ 0.157957] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)<br>
[ 0.165269] pinctrl core: initialized pinctrl subsystem<br>
[ 0.170825] DMI not present or invalid.<br>
[ 0.174918] NET: Registered PF_NETLINK/PF_ROUTE protocol family<br>
[ 0.181542] DMA: preallocated 512 KiB GFP_KERNEL pool for atomic allocations<br>
[ 0.188860] DMA: preallocated 512 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations<br>
[ 0.196880] DMA: preallocated 512 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations<br>
[ 0.204961] audit: initializing netlink subsys (disabled)<br>
[ 0.210509] audit: type=2000 audit(0.152:1): state=initialized audit_enabled=0 res=1<br>
[ 0.210695] thermal_sys: Registered thermal governor 'step_wise'<br>
[ 0.218370] thermal_sys: Registered thermal governor 'power_allocator'<br>
[ 0.224762] cpuidle: using governor menu<br>
[ 0.235456] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.<br>
[ 0.242389] ASID allocator initialised with 65536 entries<br>
[ 0.248080] Serial: AMBA PL011 UART driver<br>
[ 0.260134] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages<br>
[ 0.266911] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages<br>
[ 0.273729] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages<br>
[ 0.280535] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages<br>
[ 0.287899] cryptd: max_cpu_qlen set to 1000<br>
[ 0.293155] ACPI: Interpreter disabled.<br>
[ 0.297555] ap0_sd_vccq: Bringing 3300000uV into 1800000-1800000uV<br>
[ 0.304035] iommu: Default domain type: Translated<br>
[ 0.308992] iommu: DMA domain TLB invalidation policy: strict mode<br>
[ 0.315437] vgaarb: loaded<br>
[ 0.318313] SCSI subsystem initialized<br>
[ 0.322162] libata version 3.00 loaded.<br>
[ 0.326094] usbcore: registered new interface driver usbfs<br>
[ 0.331672] usbcore: registered new interface driver hub<br>
[ 0.337148] usbcore: registered new device driver usb<br>
[ 0.342598] pps_core: LinuxPPS API ver. 1 registered<br>
[ 0.347657] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <a href="mailto:giometti@linux.it">giometti@linux.it</a><br>
[ 0.356978] PTP clock support registered<br>
[ 0.361043] EDAC MC: Ver: 3.0.0<br>
[ 0.364504] FPGA manager framework<br>
[ 0.368007] Advanced Linux Sound Architecture Driver Initialized.<br>
[ 0.374582] clocksource: Switched to clocksource arch_sys_counter<br>
[ 0.380815] VFS: Disk quotas dquot_6.6.0<br>
[ 0.384805] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)<br>
[ 0.391875] pnp: PnP ACPI: disabled<br>
[ 0.397861] NET: Registered PF_INET protocol family<br>
[ 0.402948] IP idents hash table entries: 65536 (order: 7, 524288 bytes, linear)<br>
[ 0.411347] tcp_listen_portaddr_hash hash table entries: 2048 (order: 3, 32768 bytes, linear)<br>
[ 0.420109] TCP established hash table entries: 32768 (order: 6, 262144 bytes, linear)<br>
[ 0.428277] TCP bind hash table entries: 32768 (order: 7, 524288 bytes, linear)<br>
[ 0.435925] TCP: Hash tables configured (established 32768 bind 32768)<br>
[ 0.442664] UDP hash table entries: 2048 (order: 4, 65536 bytes, linear)<br>
[ 0.449562] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes, linear)<br>
[ 0.456943] NET: Registered PF_UNIX/PF_LOCAL protocol family<br>
[ 0.462857] RPC: Registered named UNIX socket transport module.<br>
[ 0.468889] RPC: Registered udp transport module.<br>
[ 0.473684] RPC: Registered tcp transport module.<br>
[ 0.478461] RPC: Registered tcp NFSv4.1 backchannel transport module.<br>
[ 0.485000] PCI: CLS 0 bytes, default 64<br>
[ 0.489077] Unpacking initramfs…<br>
[ 0.498782] kvm [1]: IPA Size Limit: 44 bits<br>
[ 0.506604] kvm [1]: vgic interrupt IRQ9<br>
[ 0.510679] kvm [1]: Hyp mode initialized successfully<br>
[ 0.517547] Initialise system trusted keyrings<br>
[ 0.522194] workingset: timestamp_bits=42 max_order=20 bucket_order=0<br>
[ 0.531122] squashfs: version 4.0 (2009/01/31) Phillip Lougher<br>
[ 0.537340] NFS: Registering the id_resolver key type<br>
[ 0.542513] Key type id_resolver registered<br>
[ 0.546764] Key type id_legacy registered<br>
[ 0.550916] nfs4filelayout_init: NFSv4 File Layout Driver Registering…<br>
[ 0.557743] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering…<br>
[ 0.565364] 9p: Installing v9fs 9p2000 file system support<br>
[ 0.590602] Key type asymmetric registered<br>
[ 0.594777] Asymmetric key parser 'x509' registered<br>
[ 0.599766] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)<br>
[ 0.607322] io scheduler mq-deadline registered<br>
[ 0.611968] io scheduler kyber registered<br>
[ 0.617914] armada-ap806-pinctrl f06f4000.system-controller:pinctrl: registered pinctrl driver<br>
[ 0.627195] armada-cp110-pinctrl f2440000.system-controller:pinctrl: registered pinctrl driver<br>
[ 0.636886] EINJ: ACPI disabled.<br>
[ 0.641643] mv_xor_v2 f0400000.xor: Marvell Version 2 XOR driver<br>
[ 0.648185] mv_xor_v2 f0420000.xor: Marvell Version 2 XOR driver<br>
[ 0.654712] mv_xor_v2 f0440000.xor: Marvell Version 2 XOR driver<br>
[ 0.661209] mv_xor_v2 f0460000.xor: Marvell Version 2 XOR driver<br>
[ 0.667882] mv_xor_v2 f26a0000.xor: Marvell Version 2 XOR driver<br>
[ 0.674419] mv_xor_v2 f26c0000.xor: Marvell Version 2 XOR driver<br>
[ 0.682280] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled<br>
[ 0.689362] printk: console [ttyS0] disabled<br>
[ 0.713855] f0512000.serial: ttyS0 at MMIO 0xf0512000 (irq = 16, base_baud = 12500000) is a 16550A<br>
[ 0.723017] printk: console [ttyS0] enabled<br>
[ 0.731479] printk: bootconsole [uart8250] disabled<br>
[ 0.744492] loop: module loaded<br>
[ 0.747975] megasas: 07.717.02.00-rc1<br>
[ 0.751982] ahci f2540000.sata: supply ahci not found, using dummy regulator<br>
[ 0.759140] ahci f2540000.sata: supply phy not found, using dummy regulator<br>
[ 0.766386] platform f2540000.sata:sata-port@0: supply target not found, using dummy regulator<br>
[ 0.775294] platform f2540000.sata:sata-port@1: supply target not found, using dummy regulator<br>
[ 0.784080] ahci f2540000.sata: masking port_map 0x3 -> 0x3<br>
[ 0.789717] ahci f2540000.sata: AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl platform mode<br>
[ 0.798288] ahci f2540000.sata: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs<br>
[ 0.806991] scsi host0: ahci<br>
[ 0.810094] scsi host1: ahci<br>
[ 0.813077] ata1: SATA max UDMA/133 mmio [mem 0xf2540000-0xf256ffff] port 0x100 irq 25<br>
[ 0.821038] ata2: SATA max UDMA/133 mmio [mem 0xf2540000-0xf256ffff] port 0x180 irq 25<br>
[ 0.830977] spi-nor spi2.0: s25fl064k (8192 Kbytes)<br>
[ 1.140738] ata1: SATA link down (SStatus 0 SControl 300)<br>
[ 1.310589] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)<br>
[ 1.321358] ata2.00: ATA-10: Dogfish SSD 128GB, ZD0R3G30, max UDMA/133<br>
[ 1.327920] ata2.00: 250069680 sectors, multi 1: LBA48 NCQ (depth 32)<br>
[ 1.339007] ata2.00: configured for UDMA/133<br>
[ 1.343446] scsi 1:0:0:0: Direct-Access ATA Dogfish SSD 128G 3G30 PQ: 0 ANSI: 5<br>
[ 1.351936] sd 1:0:0:0: [sda] 250069680 512-byte logical blocks: (128 GB/119 GiB)<br>
[ 1.359495] sd 1:0:0:0: [sda] Write Protect is off<br>
[ 1.364320] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00<br>
[ 1.369433] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA<br>
[ 1.380246] sd 1:0:0:0: [sda] Attached SCSI removable disk<br>
[ 3.523701] Initramfs unpacking failed: invalid magic at start of compressed archive<br>
[ 3.651236] Freeing initrd memory: 563200K<br>
[ 3.659455] spi-nor spi2.1: unrecognized JEDEC id bytes: ff ff ff ff ff ff<br>
[ 3.666390] spi-nor: probe of spi2.1 failed with error -2<br>
[ 3.672328] libphy: Fixed MDIO Bus: probed<br>
[ 3.677011] tun: Universal TUN/TAP device driver, 1.6<br>
[ 3.682308] thunder_xcv, ver 1.0<br>
[ 3.685573] thunder_bgx, ver 1.0<br>
[ 3.688829] nicpf, ver 1.0<br>
[ 3.691716] hclge is initializing<br>
[ 3.695055] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version<br>
[ 3.702309] hns3: Copyright (c) 2017 Huawei Corporation.<br>
[ 3.707665] e1000: Intel(R) PRO/1000 Network Driver<br>
[ 3.712566] e1000: Copyright (c) 1999-2006 Intel Corporation.<br>
[ 3.718349] e1000e: Intel(R) PRO/1000 Network Driver<br>
[ 3.723336] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.<br>
[ 3.729293] igb: Intel(R) Gigabit Ethernet Network Driver<br>
[ 3.734717] igb: Copyright (c) 2007-2014 Intel Corporation.<br>
[ 3.740326] igbvf: Intel(R) Gigabit Virtual Function Network Driver<br>
[ 3.746622] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.<br>
[ 3.752763] libphy: orion_mdio_bus: probed<br>
[ 3.762553] mvpp2 f2000000.ethernet: using 3 shared buffers<br>
[ 3.773550] sky2: driver version 1.30<br>
[ 3.777454] VFIO - User Level meta-driver version: 0.3<br>
[ 3.783125] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver<br>
[ 3.789697] ehci-pci: EHCI PCI platform driver<br>
[ 3.794174] ehci-platform: EHCI generic platform driver<br>
[ 3.799485] ehci-orion: EHCI orion driver<br>
[ 3.803561] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver<br>
[ 3.809779] ohci-pci: OHCI PCI platform driver<br>
[ 3.814254] ohci-platform: OHCI generic platform driver<br>
[ 3.819723] xhci-hcd f2500000.usb: xHCI Host Controller<br>
[ 3.824985] xhci-hcd f2500000.usb: new USB bus registered, assigned bus number 1<br>
[ 3.832468] xhci-hcd f2500000.usb: hcc params 0x0a000990 hci version 0x100 quirks 0x0000000000010010<br>
[ 3.841668] xhci-hcd f2500000.usb: irq 26, io mem 0xf2500000<br>
[ 3.847421] xhci-hcd f2500000.usb: xHCI Host Controller<br>
[ 3.852673] xhci-hcd f2500000.usb: new USB bus registered, assigned bus number 2<br>
[ 3.860104] xhci-hcd f2500000.usb: Host supports USB 3.0 SuperSpeed<br>
[ 3.866628] hub 1-0:1.0: USB hub found<br>
[ 3.870401] hub 1-0:1.0: 1 port detected<br>
[ 3.874469] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.<br>
[ 3.882765] hub 2-0:1.0: USB hub found<br>
[ 3.886537] hub 2-0:1.0: 1 port detected<br>
[ 3.890681] xhci-hcd f2510000.usb: xHCI Host Controller<br>
[ 3.895944] xhci-hcd f2510000.usb: new USB bus registered, assigned bus number 3<br>
[ 3.903416] xhci-hcd f2510000.usb: hcc params 0x0a000990 hci version 0x100 quirks 0x0000000000010010<br>
[ 3.912625] xhci-hcd f2510000.usb: irq 27, io mem 0xf2510000<br>
[ 3.918371] xhci-hcd f2510000.usb: xHCI Host Controller<br>
[ 3.923625] xhci-hcd f2510000.usb: new USB bus registered, assigned bus number 4<br>
[ 3.931058] xhci-hcd f2510000.usb: Host supports USB 3.0 SuperSpeed<br>
[ 3.937537] hub 3-0:1.0: USB hub found<br>
[ 3.941317] hub 3-0:1.0: 1 port detected<br>
[ 3.945367] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.<br>
[ 3.953663] hub 4-0:1.0: USB hub found<br>
[ 3.957441] hub 4-0:1.0: 1 port detected<br>
[ 3.961577] usbcore: registered new interface driver usb-storage<br>
[ 3.967653] usbcore: registered new interface driver ftdi_sio<br>
[ 3.973434] usbserial: USB Serial support registered for FTDI USB Serial Device<br>
[ 3.980815] usbcore: registered new interface driver option<br>
[ 3.986422] usbserial: USB Serial support registered for GSM modem (1-port)<br>
[ 3.994298] armada38x-rtc f2284000.rtc: registered as rtc0<br>
[ 3.999825] armada38x-rtc f2284000.rtc: setting system clock to 2064-05-06T00:59:44 UTC (2977261184)<br>
[ 4.009159] i2c_dev: i2c /dev entries driver<br>
[ 4.013843] pca953x 0-0020: supply vcc not found, using dummy regulator<br>
[ 4.020542] pca953x 0-0020: using no AI<br>
[ 4.025545] gpio-496 (pcie1.0-clkreq): hogged as input<br>
[ 4.031744] gpio-498 (m2-ful-card-power-off): hogged as output/high<br>
[ 4.038661] gpio-499 (pcie1.0-w-disable): hogged as output/low<br>
[ 4.044829] gpio-501 (usb3-current-limit): hogged as input<br>
[ 4.050957] gpio-502 (usb3-power): hogged as output/high<br>
[ 4.057746] gpio-504 (m2-w-disable): hogged as output/low<br>
[ 4.063787] gpio-506 (m2-reset): hogged as output/high<br>
[ 4.069564] gpio-507 (m.2 devslp): hogged as output/low<br>
[ 4.075001] at24 0-0053: supply vcc not found, using dummy regulator<br>
[ 4.081896] at24 0-0053: 256 byte 24c02 EEPROM, writable, 16 bytes/write<br>
[ 4.089249] mcp3021 0-004c: hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info().<br>
[ 4.114966] sbsa-gwdt f0610000.watchdog: Initialized with 10s timeout @ 25000000 Hz, action=0.<br>
[ 4.124862] sdhci: Secure Digital Host Controller Interface driver<br>
[ 4.131093] sdhci: Copyright(c) Pierre Ossman<br>
[ 4.135667] Synopsys Designware Multimedia Card Interface Driver<br>
[ 4.141888] sdhci-pltfm: SDHCI platform and OF driver helper<br>
[ 4.148399] ledtrig-cpu: registered to indicate activity on CPUs<br>
[ 4.154687] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ….<br>
[ 4.161353] usbcore: registered new interface driver usbhid<br>
[ 4.166955] usbhid: USB HID core driver<br>
[ 4.171800] NET: Registered PF_PACKET protocol family<br>
[ 4.176958] 9pnet: Installing 9P2000 support<br>
[ 4.179130] mmc0: SDHCI controller on f06e0000.sdhci [f06e0000.sdhci] using ADMA 64-bit<br>
[ 4.181274] Key type dns_resolver registered<br>
[ 4.193691] Loading compiled-in X.509 certificates<br>
[ 4.199769] hw perfevents: enabled with armv8_cortex_a72 PMU driver, 7 counters available<br>
[ 4.208659] gpio-59 (phy_reset): hogged as output/high<br>
[ 4.214471] armada8k-pcie f2640000.pcie: host bridge /cp0/pcie@f2640000 ranges:<br>
[ 4.221842] armada8k-pcie f2640000.pcie: MEM 0x00e1000000..0x00e1efffff -> 0x00e1000000<br>
[ 4.230361] armada8k-pcie f2640000.pcie: iATU unroll: disabled<br>
[ 4.236231] armada8k-pcie f2640000.pcie: Detected iATU regions: 8 outbound, 8 inbound<br>
[ 4.288522] mmc0: new HS200 MMC card at address 0001<br>
[ 4.293954] mmcblk0: mmc0:0001 8GTF4R 7.28 GiB<br>
[ 4.300050] mmcblk0boot0: mmc0:0001 8GTF4R 4.00 MiB<br>
[ 4.305731] mmcblk0boot1: mmc0:0001 8GTF4R 4.00 MiB<br>
[ 4.311251] mmcblk0rpmb: mmc0:0001 8GTF4R 512 KiB, chardev (239:0)<br>
[ 5.244293] armada8k-pcie f2640000.pcie: Phy link never came up<br>
[ 5.250434] armada8k-pcie f2640000.pcie: PCI host bridge to bus 0000:00<br>
[ 5.257159] pci_bus 0000:00: root bus resource [bus 00-ff]<br>
[ 5.262683] pci_bus 0000:00: root bus resource [mem 0xe1000000-0xe1efffff]<br>
[ 5.269639] pci 0000:00:00.0: [11ab:0110] type 01 class 0x060400<br>
[ 5.275725] pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x000fffff]<br>
[ 5.282133] pci 0000:00:00.0: supports D1 D2<br>
[ 5.286440] pci 0000:00:00.0: PME# supported from D0 D1 D3hot<br>
[ 5.294246] pci 0000:00:00.0: BAR 0: assigned [mem 0xe1000000-0xe10fffff]<br>
[ 5.301090] pci 0000:00:00.0: PCI bridge to [bus 01-ff]<br>
[ 5.664972] pcieport 0000:00:00.0: PME: Signaling with IRQ 42<br>
[ 5.671054] libphy: SFP I2C Bus: probed<br>
[ 5.675917] sfp sfp-eth@0: Host maximum power 2.0W<br>
[ 5.683171] mvpp2 f2000000.ethernet: using 3 shared buffers<br>
[ 5.706059] mvpp2 f2000000.ethernet eth0: Using random mac address f2:d7:2d:ce:e9:a4<br>
[ 5.716500] mvpp2 f2000000.ethernet eth1: Using random mac address a2:ea:7b:8e:c1:f8<br>
[ 5.725769] mvpp2 f2000000.ethernet eth2: Using random mac address e2:c8:0d:a8:24:f4<br>
[ 5.832193] xenon-sdhci f2780000.sdhci: Got CD GPIO<br>
[ 5.832197] input: keys as /devices/platform/keys/input/input0<br>
[ 5.832465] ALSA device list:<br>
[ 5.845971] No soundcards found.<br>
[ 5.867848] mmc1: SDHCI controller on f2780000.sdhci [f2780000.sdhci] using ADMA 64-bit<br>
[ 5.876443] Freeing unused kernel memory: 2304K<br>
[ 5.881101] Run /init as init process<br>
[ 5.884798] with arguments:<br>
[ 5.887780] /init<br>
[ 5.890059] with environment:<br>
[ 5.893213] HOME=/<br>
[ 5.895583] TERM=linux<br>
[ 5.898297] board=base<br>
[ 5.909139] mmc1: new high speed SDHC card at address 0001<br>
[ 5.915402] mmcblk1: mmc1:0001 00000 29.8 GiB<br>
[ 5.922384] mmcblk1: p1 p2 p3<br>
[ 9.602593] random: crng init done<br>
[ 9.621080] cfg80211: Loading compiled-in X.509 certificates for regulatory database<br>
[ 9.634318] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'<br>
[ 9.709142] /dev/mmcblk0p1: Can't open blockdev<br>
[ 9.728921] /dev/mmcblk0p2: Can't open blockdev<br>
[ 9.740490] /dev/mmcblk0p3: Can't open blockdev<br>
[ 9.819302] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.<br>
[ 9.829140] ext4 filesystem being mounted at /gui_sd supports timestamps until 2038 (0x7fffffff)<br>
[ 9.870261] EXT4-fs (mmcblk1p3): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.<br>
[ 9.880071] ext4 filesystem being mounted at /recovery_sd supports timestamps until 2038 (0x7fffffff)<br>
[ 10.121111] udevd[230]: starting version 3.2.11<br>
[ 10.134275] udevd[231]: starting eudev-3.2.11<br>
[ 10.244982] omap_rng f2760000.trng: Random Number Generator ver. 203b34c<br>
[ 10.759414] mvpp2 f2000000.ethernet eth1: PHY [f212a200.mdio-mii:01] driver <a href="irq=POLL">Marvell 88E1510</a><br>
[ 10.775745] mvpp2 f2000000.ethernet eth1: configuring for inband/sgmii link mode<br>
[ 10.951307] NET: Registered PF_INET6 protocol family<br>
[ 10.962913] Segment Routing with IPv6<br>
[ 10.966610] In-situ OAM (IOAM) with IPv6<br>
[ 35.870599] cp0_sd_vccq: disabling<br>
[ 69.115422] mvpp2 f2000000.ethernet eth2: PHY [f212a200.mdio-mii:00] driver <a href="irq=POLL">Marvell 88E1510</a><br>
[ 69.125029] mvpp2 f2000000.ethernet eth2: configuring for phy/rgmii-id link mode<br>
[ 72.187320] mvpp2 f2000000.ethernet eth2: Link is Up - 1Gbps/Full - flow control rx/tx<br>
[ 72.195364] IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready<br>
[ 82.470437] mvpp2 f2000000.ethernet eth2: Link is Down<br>
[ 118.775407] mvpp2 f2000000.ethernet eth2: PHY [f212a200.mdio-mii:00] driver <a href="irq=POLL">Marvell 88E1510</a><br>
[ 118.784988] mvpp2 f2000000.ethernet eth2: configuring for phy/rgmii-id link mode<br>
[ 121.851338] mvpp2 f2000000.ethernet eth2: Link is Up - 1Gbps/Full - flow control rx/tx<br>
[ 121.859376] IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready<br>
[ 263.951338] mvpp2 f2000000.ethernet eth2: Link is Down<br>
[ 264.957073] mvpp2 f2000000.ethernet eth2: port 2: cleaning queue 0 timed out<br>
[ 271.379540] mvpp2 f2000000.ethernet eth2: PHY [f212a200.mdio-mii:00] driver <a href="irq=POLL">Marvell 88E1510</a><br>
[ 271.389158] mvpp2 f2000000.ethernet eth2: configuring for phy/rgmii-id link mode<br>
[ 274.459398] mvpp2 f2000000.ethernet eth2: Link is Up - 1Gbps/Full - flow control rx/tx<br>
[ 274.467439] IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready<br>
[ 536.579387] mvpp2 f2000000.ethernet eth2: Tx stop timed out, status=0x00000303<br>
[ 536.586656] mvpp2 f2000000.ethernet eth2: Link is Down<br>
[ 546.843274] mvpp2 f2000000.ethernet eth2: Link is Up - 1Gbps/Full - flow control rx/tx<br>
[ 608.795023] mvpp2 f2000000.ethernet eth2: Tx stop timed out, status=0x00000b0b<br>
[ 608.802293] mvpp2 f2000000.ethernet eth2: Link is Down<br>
[ 609.808981] mvpp2 f2000000.ethernet eth2: port 2: cleaning queue 1 timed out<br>
[ 610.817583] mvpp2 f2000000.ethernet eth2: port 2: cleaning queue 3 timed out<br>
[ 623.223570] mvpp2 f2000000.ethernet eth2: PHY [f212a200.mdio-mii:00] driver <a href="irq=POLL">Marvell 88E1510</a><br>
[ 623.233201] mvpp2 f2000000.ethernet eth2: configuring for phy/rgmii-id link mode<br>
[ 626.299327] mvpp2 f2000000.ethernet eth2: Link is Up - 1Gbps/Full - flow control rx/tx<br>
[ 626.307372] IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready<br>
```<br>
Merci par avance. :)</p>
<div><a href="https://linuxfr.org/forums/linux-embarque/posts/port-ethernet-up-mais-aucun-flux.epub">Télécharger ce contenu au format EPUB</a></div> <p>
<strong>Commentaires :</strong>
<a href="//linuxfr.org/nodes/131007/comments.atom">voir le flux Atom</a>
<a href="https://linuxfr.org/forums/linux-embarque/posts/port-ethernet-up-mais-aucun-flux#comments">ouvrir dans le navigateur</a>
</p>
doudootianahttps://linuxfr.org/nodes/131007/comments.atomtag:linuxfr.org,2005:Post/435622023-04-06T11:10:26+02:002023-04-06T11:10:26+02:00Wifi et roaming<p>Bonjour,</p>
<p>Je suis entrain de configurer un écran embarqué sous Linux Debian 11.<br>
Pour le roaming j'utilise wpa_supplican (j'ai essayé avec iwd mais même résultat que ce qui suit).<br>
Pour éviter tout parasitage j'ai supprimé networkmanager.<br>
Le roaming se passe assez bien dans l'ensemble.<br>
Sauf qu'en le terminal perd le réseau (passage dans une zone blanche) et doit se reconnecter au réseau, là il faut prêt d'30 secondes - 1 minutes à l'équipement pour se reconnecter (oui les caristes n'aiment pas attendre).</p>
<p>Configuration /etc/network/interfaces</p>
<pre><code># This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug enx00e04c421374
iface enx00e04c421374 inet static
address 192.168.0.50
# gateway 192.168.0.10
allow-hotplug wls6
iface wls6 inet manual
wpa-driver wext
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
iface societe inet dhcp
netmask 255.255.0.0
</code></pre>
<p>Configuration /etc/wpa_supplicant/wpa_supplicant.conf</p>
<pre><code>ctrl_interface=/var/run/wpa_supplicant
update_config=1
ap_scan=1
country=FR
update_config=0
fast_reauth=1
network={
ssid="PROWLAN"
proto=WPA RSN
key_mgmt=WPA-PSK
psk="moddepasse"
#psk=11afec0ccc675e5f708f7f7c1da4c8cd82261cac78924fc7ed7359a5e9e9b154
bgscan="simple:5:-62:3600"
id_str="societe"
}
</code></pre>
<p>Log au moment des problèmes de connexion :</p>
<pre><code>Apr 6 09:57:21 term wpa_supplicant[532]: wls6: CTRL-EVENT-DISCONNECTED bssid=00:23:68:09:a8:69 reason=0
Apr 6 09:57:23 term wpa_supplicant[532]: wls6: Trying to associate with 00:23:68:09:a8:69 (SSID='PROWLAN' freq=2462 MHz)
Apr 6 09:57:23 term wpa_supplicant[532]: Failed to add supported operating classes IE
Apr 6 09:57:23 term kernel: [ 132.181868] wls6: authenticate with 00:23:68:09:a8:69
Apr 6 09:57:23 term kernel: [ 132.181890] wls6: 80 MHz not supported, disabling VHT
Apr 6 09:57:23 term kernel: [ 132.184256] wls6: send auth to 00:23:68:09:a8:69 (try 1/3)
Apr 6 09:57:23 term kernel: [ 132.315492] wls6: send auth to 00:23:68:09:a8:69 (try 2/3)
Apr 6 09:57:23 term kernel: [ 132.318957] wls6: authenticated
Apr 6 09:57:23 term kernel: [ 132.318978] iwlwifi 0000:02:00.0 wls6: disabling HT/VHT/HE as WMM/QoS is not supported by the AP
Apr 6 09:57:23 term kernel: [ 132.319490] wls6: associate with 00:23:68:09:a8:69 (try 1/3)
Apr 6 09:57:23 term kernel: [ 132.322791] wls6: RX AssocResp from 00:23:68:09:a8:69 (capab=0x11 status=0 aid=1)
Apr 6 09:57:23 term wpa_supplicant[532]: wls6: Associated with 00:23:68:09:a8:69
Apr 6 09:57:23 term kernel: [ 132.325671] wls6: associated
Apr 6 09:57:33 term wpa_supplicant[532]: wls6: Authentication with 00:23:68:09:a8:69 timed out.
Apr 6 09:57:33 term kernel: [ 142.326381] wls6: deauthenticating from 00:23:68:09:a8:69 by local choice (Reason: 3=DEAUTH_LEAVING)
Apr 6 09:57:33 term wpa_supplicant[532]: wls6: CTRL-EVENT-DISCONNECTED bssid=00:23:68:09:a8:69 reason=3 locally_generated=1
Apr 6 09:57:33 term wpa_supplicant[532]: wls6: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="PROWLAN" auth_failures=1 duration=10 reason=CONN_FAILED
Apr 6 09:57:43 term wpa_supplicant[532]: wls6: CTRL-EVENT-SSID-REENABLED id=0 ssid="PROWLAN"
Apr 6 09:57:43 term wpa_supplicant[532]: wls6: Trying to associate with 00:23:68:53:c6:16 (SSID='PROWLAN' freq=2437 MHz)
Apr 6 09:57:43 term wpa_supplicant[532]: Failed to add supported operating classes IE
Apr 6 09:57:43 term kernel: [ 152.859846] wls6: authenticate with 00:23:68:53:c6:16
Apr 6 09:57:43 term kernel: [ 152.859867] wls6: 80 MHz not supported, disabling VHT
Apr 6 09:57:43 term kernel: [ 152.862216] wls6: send auth to 00:23:68:53:c6:16 (try 1/3)
Apr 6 09:57:43 term kernel: [ 152.989057] wls6: send auth to 00:23:68:53:c6:16 (try 2/3)
Apr 6 09:57:44 term kernel: [ 153.090194] wls6: send auth to 00:23:68:53:c6:16 (try 3/3)
Apr 6 09:57:44 term kernel: [ 153.481535] wls6: authentication with 00:23:68:53:c6:16 timed out
Apr 6 09:57:53 term wpa_supplicant[532]: wls6: Authentication with 00:23:68:53:c6:16 timed out.
Apr 6 09:57:53 term wpa_supplicant[532]: wls6: CTRL-EVENT-DISCONNECTED bssid=00:23:68:53:c6:16 reason=3 locally_generated=1
Apr 6 09:57:53 term wpa_supplicant[532]: wls6: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="PROWLAN" auth_failures=2 duration=20 reason=CONN_FAILED
Apr 6 09:57:53 term wpa_supplicant[532]: ioctl[SIOCSIWSCAN]: Device or resource busy
Apr 6 09:57:53 term wpa_supplicant[532]: wls6: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1
Apr 6 09:58:14 term wpa_supplicant[532]: wls6: CTRL-EVENT-SSID-REENABLED id=0 ssid="PROWLAN"
Apr 6 09:58:14 term wpa_supplicant[532]: wls6: Trying to associate with 00:23:68:53:c6:16 (SSID='PROWLAN' freq=2437 MHz)
Apr 6 09:58:14 term wpa_supplicant[532]: Failed to add supported operating classes IE
Apr 6 09:58:14 term kernel: [ 183.621857] wls6: authenticate with 00:23:68:53:c6:16
Apr 6 09:58:14 term kernel: [ 183.621878] wls6: 80 MHz not supported, disabling VHT
Apr 6 09:58:14 term kernel: [ 183.624243] wls6: send auth to 00:23:68:53:c6:16 (try 1/3)
Apr 6 09:58:14 term kernel: [ 183.654006] wls6: authenticated
Apr 6 09:58:14 term kernel: [ 183.654030] iwlwifi 0000:02:00.0 wls6: disabling HT/VHT/HE as WMM/QoS is not supported by the AP
Apr 6 09:58:14 term kernel: [ 183.655493] wls6: associate with 00:23:68:53:c6:16 (try 1/3)
Apr 6 09:58:14 term kernel: [ 183.658950] wls6: RX AssocResp from 00:23:68:53:c6:16 (capab=0x11 status=0 aid=1)
Apr 6 09:58:14 term kernel: [ 183.673224] wls6: associated
Apr 6 09:58:14 term wpa_supplicant[532]: wls6: Associated with 00:23:68:53:c6:16
Apr 6 09:58:24 term wpa_supplicant[532]: wls6: Authentication with 00:23:68:53:c6:16 timed out.
Apr 6 09:58:24 term kernel: [ 193.674568] wls6: deauthenticating from 00:23:68:53:c6:16 by local choice (Reason: 3=DEAUTH_LEAVING)
Apr 6 09:58:24 term wpa_supplicant[532]: wls6: CTRL-EVENT-DISCONNECTED bssid=00:23:68:53:c6:16 reason=3 locally_generated=1
Apr 6 09:58:24 term wpa_supplicant[532]: wls6: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="PROWLAN" auth_failures=3 duration=30 reason=CONN_FAILED
</code></pre>
<p>Une petite idée ?</p>
<p>Bonne journée</p>
<div><a href="https://linuxfr.org/forums/linux-embarque/posts/wifi-et-roaming.epub">Télécharger ce contenu au format EPUB</a></div> <p>
<strong>Commentaires :</strong>
<a href="//linuxfr.org/nodes/130849/comments.atom">voir le flux Atom</a>
<a href="https://linuxfr.org/forums/linux-embarque/posts/wifi-et-roaming#comments">ouvrir dans le navigateur</a>
</p>
totoroavihttps://linuxfr.org/nodes/130849/comments.atomtag:linuxfr.org,2005:Post/433652022-12-30T13:38:10+01:002022-12-31T22:59:43+01:00uboot et commande tlv eeprom<p>Bonjour à toutes et à tous.</p>
<p>Pour un projet, j'utilise deux cartes de même marque mais modèle différent : <br>
clearfog base et la Clearfog pro.</p>
<p>J'ai fait un fichier Fit en commun avec l'image kernel et les dtb pour chaque modèle.</p>
<pre><code> /dts-v1/;
/ {
description = "Kernel et dtb";
#address-cells = <1>;
images {
kernel {
description = "Kernel";
data = /incbin/("/a/Image");
type = "kernel";
arch = "arm64";
os = "linux";
compression = "none";
load = <0x44000000>;
entry = <0x44000000>;
hash-1 {
algo = "sha1";
};
};
fdt-pro {
description = "dtb";
data = /incbin/("/a/diagbox_pro.dtb");
type = "flat_dt";
arch = "arm64";
load = <0x47000000>;
compression = "none";
hash-1 {
algo = "sha1";
};
};
fdt-base {
description = "dtb";
data = /incbin/("/a/diagbox_base.dtb");
type = "flat_dt";
arch = "arm64";
load = <0x47000000>;
compression = "none";
hash-1 {
algo = "sha1";
};
};
};
configurations {
default = "conf-pro";
conf-pro {
description = "Configuration";
kernel = "kernel";
fdt = "fdt-pro";
hash-1 {
algo = "sha1";
};
};
conf-base {
description = "Configuration";
kernel = "kernel";
fdt = "fdt-base";
hash-1 {
algo = "sha1";
};
};
};
};
</code></pre>
<p>Mon but serait qu'à partir d'U-boot, la sélection du profil se fasse automatiquement.</p>
<p>Dans U-boot, j'ai une commande qui me permet d'afficher les infos de la carte stockée dans un eeprom :</p>
<pre><code>> DiagBox>> tlv_eeprom
TLV: 0
TlvInfo Header:
Id String: TlvInfo
Version: 1
Total Length: 12
TLV Name Code Len Value
-------------------- ---- --- -----
Product Name 0x21 4 CFCP
CRC-32 0xFE 4 0x8455DBA5
Checksum is valid.
DiagBox>>
TLV: 0
TlvInfo Header:
Id String: TlvInfo
Version: 1
Total Length: 12
TLV Name Code Len Value
-------------------- ---- --- -----
Product Name 0x21 4 CFCP
CRC-32 0xFE 4 0x8455DBA5
Checksum is valid.
DiagBox>> tlv help
tlv_eeprom - Display and program the system EEPROM data block.
Usage:
tlv_eeprom [read|write|set <type_code> <string_value>|erase|list]
tlv_eeprom
- With no arguments display the current contents.
tlv_eeprom dev [dev]
- List devices or set current EEPROM device.
tlv_eeprom read
- Load EEPROM data from device to memory.
tlv_eeprom write
- Write the EEPROM data to persistent storage.
tlv_eeprom set <type_code> <string_value>
- Set a field to a value.
- If no string_value, field is deleted.
- Use 'tlv_eeprom write' to make changes permanent.
tlv_eeprom erase
- Reset the in memory EEPROM data.
- Use 'tlv_eeprom read' to refresh the in memory EEPROM data.
- Use 'tlv_eeprom write' to make changes permanent.
tlv_eeprom list
- List the understood TLV codes and names.
DiagBox>>
</code></pre>
<p>Est il possible de ne sélectionner que la ligne 'Product Name', afin d'avoir le modèle de la carte et pouvoir utiliser la bonne configuration du FIT?</p>
<p>En vous remerciant par avance :)</p>
<div><a href="https://linuxfr.org/forums/linux-embarque/posts/uboot-et-commande-tlv-eeprom.epub">Télécharger ce contenu au format EPUB</a></div> <p>
<strong>Commentaires :</strong>
<a href="//linuxfr.org/nodes/129821/comments.atom">voir le flux Atom</a>
<a href="https://linuxfr.org/forums/linux-embarque/posts/uboot-et-commande-tlv-eeprom#comments">ouvrir dans le navigateur</a>
</p>
doudootianahttps://linuxfr.org/nodes/129821/comments.atomtag:linuxfr.org,2005:Post/433252022-12-16T09:01:50+01:002022-12-19T14:38:15+01:00JLT 6012 - Intel AX210 - perte wifi<p>Bonjour,</p>
<p>Dans mon entreprise, je suis en train de qualifier un terminal embarqué pour chariot de la marque JLT que nous faisons tourner sous Debian 11.</p>
<p>J'ai configuré wpa_supplican pour avoir le roaming, qui fonctionne mieux que sur autres terminaux (Windows ou Android) chez nous, enfin bref c'est cool.</p>
<p>Le hic c'est que de façon aléatoire (quelque minutes a plusieurs heures), le firmware semble partir en vrille :</p>
<pre><code class="sh"> Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.259718<span class="o">]</span> ------------<span class="o">[</span> cut here <span class="o">]</span>------------
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.259734<span class="o">]</span> Timeout waiting <span class="k">for</span> hardware access <span class="o">(</span>CSR_GP_CNTRL 0xffffffff<span class="o">)</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.259783<span class="o">]</span> WARNING: CPU: <span class="m">1</span> PID: <span class="m">0</span> at __iwl_trans_pcie_grab_nic_access+0x1ea/0x220 <span class="o">[</span>iwlwifi<span class="o">]</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.259826<span class="o">]</span> Modules linked in: rfcomm ccm cmac algif_hash algif_skcipher af_alg bnep intel_rapl_msr intel_rapl_common intel_soc_dts_thermal intel_soc_dts_iosf intel_powerclamp coretemp kvm_intel kvm hid_sensor_gyro_3d irqbypass hid_sensor_accel_3d punit_atom_debug hid_sensor_magn_3d snd_hda_codec_hdmi crct10dif_pclmul hid_sensor_temperature hid_sensor_trigger industrialio_triggered_buffer kfifo_buf hid_sensor_iio_common polyval_generic industrialio snd_hda_codec_realtek ghash_clmulni_intel sha512_ssse3 nls_iso8859_1 snd_hda_codec_generic ledtrig_audio aesni_intel crypto_simd cryptd joydev ftdi_sio snd_hda_intel input_leds intel_cstate hid_multitouch iwlmvm snd_intel_dspcfg mac80211 usbserial cmdlinepart snd_intel_sdw_acpi libarc4 spi_nor btusb snd_hda_codec btmtk pcspkr mtd snd_hda_core efi_pstore iwlwifi snd_hwdep snd_pcm cfg80211 iTCO_wdt snd_timer intel_pmc_bxt mei_txe iTCO_vendor_support snd mei hci_uart soundcore btqca btrtl btbcm btintel bluetooth atomisp_lm3554<span class="o">(</span>C<span class="o">)</span> ecdh_generic
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260079<span class="o">]</span> atomisp_gmin_platform<span class="o">(</span>C<span class="o">)</span> ecc videodev mac_hid mc rfkill_gpio ip_tables x_tables autofs4 hid_sensor_hub usbmouse hid_generic usbkbd usbhid i915 drm_buddy ttm drm_display_helper cec rc_core drm_kms_helper syscopyarea sysfillrect igb spi_intel_platform sysimgblt spi_intel i2c_i801 fb_sys_fops dca crc32_pclmul lpc_ich i2c_smbus drm xhci_pci i2c_algo_bit xhci_pci_renesas sdhci_pci cqhci ahci sdhci libahci video i2c_hid_acpi wmi i2c_hid hid
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260240<span class="o">]</span> CPU: <span class="m">1</span> PID: <span class="m">0</span> Comm: swapper/1 Tainted: G C <span class="m">6</span>.1.0-x64v1-xanmod1 <span class="c1">#0~20221213.629e4bb9</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260247<span class="o">]</span> Hardware name: To be filled by O.E.M. To be filled by O.E.M./PQ7-M106-JLT, BIOS R1.00.E6 <span class="m">12</span>/20/2019
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260252<span class="o">]</span> RIP: <span class="m">0010</span>:__iwl_trans_pcie_grab_nic_access+0x1ea/0x220 <span class="o">[</span>iwlwifi<span class="o">]</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260295<span class="o">]</span> Code: <span class="m">48</span> <span class="m">89</span> df e8 <span class="m">78</span> d1 fe ff 4c <span class="m">89</span> f7 e8 <span class="m">20</span> c5 <span class="m">61</span> c8 e9 e3 fe ff ff <span class="m">89</span> c6 <span class="m">48</span> c7 c7 a8 2e bc c0 c6 <span class="m">05</span> a2 6a <span class="m">03</span> <span class="m">00</span> <span class="m">01</span> e8 bb 6c 5a c8 <0f> 0b e9 <span class="m">01</span> ff ff ff <span class="m">48</span> 8b 7b <span class="m">40</span> <span class="m">48</span> c7 c2 <span class="m">10</span> 2f bc c0 <span class="m">31</span> f6 e8 0d
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260301<span class="o">]</span> RSP: <span class="m">0018</span>:ffffabe1400f8e20 EFLAGS: <span class="m">00010282</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260308<span class="o">]</span> RAX: <span class="m">0000000000000000</span> RBX: ffff9cbd4b814028 RCX: <span class="m">0000000000000000</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260312<span class="o">]</span> RDX: ffff9cbd9bca4a00 RSI: ffff9cbd9bca1660 RDI: <span class="m">0000000000000300</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260317<span class="o">]</span> RBP: 00000000ffffffff R08: <span class="m">0000000000000000</span> R09: ffffabe1400f8cc0
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260321<span class="o">]</span> R10: <span class="m">0000000000000003</span> R11: ffffffff89d36a08 R12: <span class="m">0000000000000001</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260325<span class="o">]</span> R13: <span class="m">0000000000000000</span> R14: ffff9cbd4b816974 R15: <span class="m">0000000000000011</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260330<span class="o">]</span> FS: <span class="m">0000000000000000</span><span class="o">(</span><span class="m">0000</span><span class="o">)</span> GS:ffff9cbd9bc80000<span class="o">(</span><span class="m">0000</span><span class="o">)</span> knlGS:0000000000000000
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260335<span class="o">]</span> CS: <span class="m">0010</span> DS: <span class="m">0000</span> ES: <span class="m">0000</span> CR0: <span class="m">0000000080050033</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260340<span class="o">]</span> CR2: 00007ffad0f44580 CR3: <span class="m">0000000127210000</span> CR4: 00000000001006e0
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260345<span class="o">]</span> Call Trace:
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260351<span class="o">]</span> <IRQ>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260357<span class="o">]</span> iwl_trans_pcie_grab_nic_access+0x11/0x30 <span class="o">[</span>iwlwifi<span class="o">]</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260393<span class="o">]</span> iwl_read_prph+0x17/0x60 <span class="o">[</span>iwlwifi<span class="o">]</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260425<span class="o">]</span> iwl_txq_log_scd_error+0x13a/0x220 <span class="o">[</span>iwlwifi<span class="o">]</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260462<span class="o">]</span> ? iwl_txq_log_scd_error+0x220/0x220 <span class="o">[</span>iwlwifi<span class="o">]</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260496<span class="o">]</span> iwl_txq_stuck_timer+0x38/0x60 <span class="o">[</span>iwlwifi<span class="o">]</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260531<span class="o">]</span> ? iwl_txq_log_scd_error+0x220/0x220 <span class="o">[</span>iwlwifi<span class="o">]</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260568<span class="o">]</span> call_timer_fn.constprop.0+0x11/0x80
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260582<span class="o">]</span> __run_timers.part.0+0x1b4/0x200
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260591<span class="o">]</span> ? recalibrate_cpu_khz+0x10/0x10
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260599<span class="o">]</span> ? ktime_get+0x33/0x90
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260606<span class="o">]</span> run_timer_softirq+0x21/0x50
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260614<span class="o">]</span> __do_softirq+0xbb/0x1eb
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260624<span class="o">]</span> __irq_exit_rcu+0x83/0xb0
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260632<span class="o">]</span> sysvec_apic_timer_interrupt+0x6e/0x90
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260641<span class="o">]</span> </IRQ>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260644<span class="o">]</span> <TASK>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260648<span class="o">]</span> asm_sysvec_apic_timer_interrupt+0x16/0x20
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260656<span class="o">]</span> RIP: <span class="m">0010</span>:cpuidle_enter_state+0xc6/0x2b0
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260665<span class="o">]</span> Code: ff <span class="m">49</span> <span class="m">89</span> c5 e8 cb <span class="m">40</span> <span class="m">80</span> ff <span class="m">45</span> <span class="m">84</span> f6 <span class="m">74</span> <span class="m">16</span> 9c <span class="m">58</span> 0f 1f <span class="m">40</span> <span class="m">00</span> f6 c4 <span class="m">02</span> 0f <span class="m">85</span> da <span class="m">01</span> <span class="m">00</span> <span class="m">00</span> <span class="m">31</span> ff e8 <span class="m">30</span> dc <span class="m">85</span> ff fb 0f 1f <span class="m">44</span> <span class="m">00</span> <span class="m">00</span> <<span class="m">45</span>> <span class="m">85</span> ff 0f <span class="m">88</span> cf <span class="m">00</span> <span class="m">00</span> <span class="m">00</span> <span class="m">49</span> <span class="m">63</span> f7 <span class="m">48</span> 8d <span class="m">04</span> <span class="m">76</span> <span class="m">48</span> 8d <span class="m">04</span> <span class="m">86</span> <span class="m">49</span> 8d
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260670<span class="o">]</span> RSP: <span class="m">0018</span>:ffffabe1400abe90 EFLAGS: <span class="m">00000246</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260678<span class="o">]</span> RAX: ffff9cbd9bca9580 RBX: <span class="m">0000000000000003</span> RCX: <span class="m">0000000000000000</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260682<span class="o">]</span> RDX: 00000a99b294a052 RSI: fffffffa5be5e058 RDI: <span class="m">0000000000000000</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260687<span class="o">]</span> RBP: ffff9cbd9bcb4120 R08: <span class="m">0000000000000000</span> R09: 0000000042c85848
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260691<span class="o">]</span> R10: <span class="m">0000000000000018</span> R11: 00000000000042ef R12: ffffffff89d64ba0
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260695<span class="o">]</span> R13: 00000a99b294a052 R14: <span class="m">0000000000000000</span> R15: <span class="m">0000000000000003</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260704<span class="o">]</span> cpuidle_enter+0x24/0x40
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260713<span class="o">]</span> do_idle+0x1e3/0x260
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260723<span class="o">]</span> cpu_startup_entry+0x14/0x20
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260731<span class="o">]</span> start_secondary+0x111/0x130
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260740<span class="o">]</span> secondary_startup_64_no_verify+0xe5/0xeb
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260751<span class="o">]</span> </TASK>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260755<span class="o">]</span> ---<span class="o">[</span> end trace <span class="m">0000000000000000</span> <span class="o">]</span>---
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260763<span class="o">]</span> iwlwifi <span class="m">0000</span>:03:00.0: iwlwifi transaction failed, dumping registers
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260770<span class="o">]</span> iwlwifi <span class="m">0000</span>:03:00.0: iwlwifi device config registers:
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260958<span class="o">]</span> iwlwifi <span class="m">0000</span>:03:00.0: <span class="m">00000000</span>: 24fd8086 <span class="m">00100000</span> <span class="m">02800078</span> <span class="m">00000000</span> <span class="m">00000004</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260968<span class="o">]</span> iwlwifi <span class="m">0000</span>:03:00.0: <span class="m">00000020</span>: <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00108086</span> <span class="m">00000000</span> 000000c8 <span class="m">00000000</span> <span class="m">00000100</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260975<span class="o">]</span> iwlwifi <span class="m">0000</span>:03:00.0: <span class="m">00000040</span>: <span class="m">00020010</span> 10008ec0 001b0c10 0045e811 <span class="m">10110000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260982<span class="o">]</span> iwlwifi <span class="m">0000</span>:03:00.0: <span class="m">00000060</span>: <span class="m">00000000</span> <span class="m">00080812</span> <span class="m">00000005</span> <span class="m">00000000</span> <span class="m">00010001</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260988<span class="o">]</span> iwlwifi <span class="m">0000</span>:03:00.0: <span class="m">00000080</span>: <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.260994<span class="o">]</span> iwlwifi <span class="m">0000</span>:03:00.0: 000000a0: <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.261000<span class="o">]</span> iwlwifi <span class="m">0000</span>:03:00.0: 000000c0: <span class="m">00000000</span> <span class="m">00000000</span> c823d001 0d000000 <span class="m">00804005</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.261006<span class="o">]</span> iwlwifi <span class="m">0000</span>:03:00.0: 000000e0: <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.261013<span class="o">]</span> iwlwifi <span class="m">0000</span>:03:00.0: <span class="m">00000100</span>: <span class="m">14010001</span> <span class="m">00100000</span> <span class="m">00000000</span> <span class="m">00462031</span> 000030c1 <span class="m">00002000</span> <span class="m">00000014</span> <span class="m">40000001</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.261019<span class="o">]</span> iwlwifi <span class="m">0000</span>:03:00.0: <span class="m">00000120</span>: 0000010f b0700460 <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.261026<span class="o">]</span> iwlwifi <span class="m">0000</span>:03:00.0: <span class="m">00000140</span>: 14c10003 ffed4ddd 60e32bff <span class="m">15410018</span> <span class="m">00000000</span> 0001001e 00481e1f <span class="m">00000000</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.261031<span class="o">]</span> iwlwifi <span class="m">0000</span>:03:00.0: iwlwifi device memory mapped registers:
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.261062<span class="o">]</span> iwlwifi <span class="m">0000</span>:03:00.0: <span class="m">00000000</span>: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.261069<span class="o">]</span> iwlwifi <span class="m">0000</span>:03:00.0: <span class="m">00000020</span>: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.261076<span class="o">]</span> iwlwifi <span class="m">0000</span>:03:00.0: iwlwifi device AER capability structure:
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.261104<span class="o">]</span> iwlwifi <span class="m">0000</span>:03:00.0: <span class="m">00000000</span>: <span class="m">14010001</span> <span class="m">00100000</span> <span class="m">00000000</span> <span class="m">00462031</span> 000030c1 <span class="m">00002000</span> <span class="m">00000014</span> <span class="m">40000001</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.261110<span class="o">]</span> iwlwifi <span class="m">0000</span>:03:00.0: <span class="m">00000020</span>: 0000010f b0700460 <span class="m">00000000</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.261115<span class="o">]</span> iwlwifi <span class="m">0000</span>:03:00.0: iwlwifi parent port <span class="o">(</span><span class="m">0000</span>:00:1c.2<span class="o">)</span> config registers:
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.261191<span class="o">]</span> iwlwifi <span class="m">0000</span>:00:1c.2: <span class="m">00000000</span>: 0f4c8086 <span class="m">00100407</span> <span class="m">06040011</span> <span class="m">00810010</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00030300</span> <span class="m">20003030</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.261201<span class="o">]</span> iwlwifi <span class="m">0000</span>:00:1c.2: <span class="m">00000020</span>: b070b070 b121b111 <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000040</span> <span class="m">00000000</span> <span class="m">00120305</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.261207<span class="o">]</span> iwlwifi <span class="m">0000</span>:00:1c.2: <span class="m">00000040</span>: <span class="m">01428010</span> <span class="m">00008000</span> 001b0000 03313c12 <span class="m">70110042</span> 0014b260 <span class="m">01400000</span> <span class="m">00000000</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.261214<span class="o">]</span> iwlwifi <span class="m">0000</span>:00:1c.2: <span class="m">00000060</span>: <span class="m">00000000</span> <span class="m">00000016</span> <span class="m">00000010</span> <span class="m">00000000</span> <span class="m">00010001</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.261220<span class="o">]</span> iwlwifi <span class="m">0000</span>:00:1c.2: <span class="m">00000080</span>: <span class="m">00019005</span> fee08004 <span class="m">00000021</span> <span class="m">00000000</span> 0000a00d 0f4c8086 <span class="m">00000000</span> <span class="m">00000000</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.261226<span class="o">]</span> iwlwifi <span class="m">0000</span>:00:1c.2: 000000a0: c8030001 <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.261233<span class="o">]</span> iwlwifi <span class="m">0000</span>:00:1c.2: 000000c0: <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">01000000</span> <span class="m">00000842</span> c9118000 <span class="m">00000000</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.261239<span class="o">]</span> iwlwifi <span class="m">0000</span>:00:1c.2: 000000e0: <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000004</span> <span class="m">00000000</span> <span class="m">00000050</span> 0c000040 01110f1a <span class="m">03000000</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.261245<span class="o">]</span> iwlwifi <span class="m">0000</span>:00:1c.2: <span class="m">00000100</span>: <span class="m">00000000</span> <span class="m">00100000</span> <span class="m">00004000</span> <span class="m">00060011</span> <span class="m">00001001</span> <span class="m">00002000</span> <span class="m">00000000</span> <span class="m">00000000</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.261251<span class="o">]</span> iwlwifi <span class="m">0000</span>:00:1c.2: <span class="m">00000120</span>: <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.261257<span class="o">]</span> iwlwifi <span class="m">0000</span>:00:1c.2: <span class="m">00000140</span>: <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.261264<span class="o">]</span> iwlwifi <span class="m">0000</span>:00:1c.2: <span class="m">00000160</span>: <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.261270<span class="o">]</span> iwlwifi <span class="m">0000</span>:00:1c.2: <span class="m">00000180</span>: <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.261276<span class="o">]</span> iwlwifi <span class="m">0000</span>:00:1c.2: 000001a0: <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.261282<span class="o">]</span> iwlwifi <span class="m">0000</span>:00:1c.2: 000001c0: <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.261288<span class="o">]</span> iwlwifi <span class="m">0000</span>:00:1c.2: 000001e0: <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.261293<span class="o">]</span> iwlwifi <span class="m">0000</span>:00:1c.2: <span class="m">00000200</span>: <span class="m">00000000</span> <span class="m">00000000</span> <span class="m">00000000</span>
Dec <span class="m">15</span> <span class="m">20</span>:45:43 jlt-term kernel: <span class="o">[</span><span class="m">11655</span>.313348<span class="o">]</span> iwlwifi <span class="m">0000</span>:03:00.0: Queue <span class="m">4</span> is active on fifo <span class="m">2</span> and stuck <span class="k">for</span> <span class="m">10000</span> ms. SW <span class="o">[</span><span class="m">103</span>, <span class="m">106</span><span class="o">]</span> HW <span class="o">[</span><span class="m">90</span>, <span class="m">90</span><span class="o">]</span> FH <span class="nv">TRB</span><span class="o">=</span>0x05a5a5a5a</code></pre>
<p>J'ai installé un kernel alternatif qui est sencé embarque les dernier drivers intel : <a href="https://xanmod.org/">Xanmod</a> qui monte le kernel en version 6.1.0 mais sans succés.</p>
<p>J'ai essayé également de rajouter le firmware en suivant les instructions d'<a href="https://www.intel.fr/content/www/fr/fr/support/articles/000005511/wireless.html">Intel</a>, j'ai toujours les mêmes soucis.</p>
<p>Donc je demande a plus expérimenté que moi ;)<br>
Avez vous une idée ?</p>
<p>Bonne journée</p>
<div><a href="https://linuxfr.org/forums/linux-embarque/posts/jlt-6012-intel-ax210-perte-wifi.epub">Télécharger ce contenu au format EPUB</a></div> <p>
<strong>Commentaires :</strong>
<a href="//linuxfr.org/nodes/129670/comments.atom">voir le flux Atom</a>
<a href="https://linuxfr.org/forums/linux-embarque/posts/jlt-6012-intel-ax210-perte-wifi#comments">ouvrir dans le navigateur</a>
</p>
totoroavihttps://linuxfr.org/nodes/129670/comments.atomtag:linuxfr.org,2005:Post/431772022-09-29T15:37:08+02:002022-09-29T17:41:55+02:00uboot : inclure initrd dans le fichier fit<p>Hello à toutes et à tous.</p>
<p>Je suis encore novice dans le domaine du Linux embarqué.<br>
J'essaie d'apprendre en cherchant les infos sur le web mais là ça fait une semaine que je bloque.</p>
<p>Je travaille sur une Bananapi r3.<br>
J'ai fait le bootloader avec U-boot et ATF ( j'espère utiliser les bons termes <sup><sup>)</sup></sup> .</p>
<p>J'ai crée un fichier fit qui contient le noyau, le dtb et j'aimerais aussi y mettre l'initrd qui est au format cpio.gz</p>
<p>Lors du boot, j'ai cette erreur :</p>
<pre><code class="sh"> Press UP/DOWN to move, ENTER to <span class="k">select</span>, ESC/CTRL+C to quit
<span class="c1">## Error: "initrd" not defined</span>
<span class="nv">fit</span><span class="o">=</span>diagbox.itb
<span class="m">75430704</span> bytes <span class="nb">read</span> in <span class="m">7555</span> ms <span class="o">(</span><span class="m">9</span>.5 MiB/s<span class="o">)</span>
<span class="c1">## Loading kernel from FIT Image at 46000000 ...</span>
Using <span class="s1">'conf-1'</span> configuration
Trying <span class="s1">'kernel'</span> kernel subimage
Description: Kernel
Type: Kernel Image
Compression: gzip compressed
Data Start: 0x460000c0
Data Size: <span class="m">9023926</span> <span class="nv">Bytes</span> <span class="o">=</span> <span class="m">8</span>.6 MiB
Architecture: AArch64
OS: Linux
Load Address: 0x44000000
Entry Point: 0x44000000
Hash algo: sha1
Hash value: db19bf77644b49dd92e368d44d550ee7622c4975
Verifying Hash Integrity ... sha1+ OK
<span class="c1">## Loading fdt from FIT Image at 46000000 ...</span>
Using <span class="s1">'conf-1'</span> configuration
Trying <span class="s1">'fdt'</span> fdt subimage
Description: Flattened Device Tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x4689b36c
Data Size: <span class="m">19100</span> <span class="nv">Bytes</span> <span class="o">=</span> <span class="m">18</span>.7 KiB
Architecture: AArch64
Load Address: 0x47000000
Hash algo: sha1
Hash value: 2fba374f801b81c839aa55c2f3c7182b44d4a4f3
Verifying Hash Integrity ... sha1+ OK
Error: fdt overwritten
Could not find a valid device tree
RescueOS></code></pre>
<p>Lorsque je retire le rootfs du fichier fit, et que je le charge séparément, la carte boot bien.<br>
J'ai remarqué qu'en enlevant la Load address du fdt, la carte boot aléatoirement. </p>
<p>La Bananapi r3 nécessite une table de partition de type GPT.<br>
Voici la composition de ma table de partition :</p>
<pre><code> {
"bl2" : {
"start": 1024,
"end" : 8191,
"attributes": 4,
"uuid" : "{19a4763a-6b19-4a4b-a0c4-8cc34f4c2b8a}"
},
"u-boot-env" : {
"start": 8192,
"end" : 9215,
"uuid" : "{19a4763a-6b19-4a4b-a0c4-8cc34f4c2ab9}"
},
"factory" : {
"start": 9216,
"end" : 13311,
"uuid" : "{8142c1b2-1697-41d9-b1bf-a88d76c7213f}"
},
"fip": {
"start": 13312,
"end" : 17407,
"uuid" : "{18de6587-4f17-4e08-a6c9-d9d3d424f4c5}"
},
"kernel" : {
"start": 17408,
"end" : 293888,
"uuid" : "{971f7556-ef1a-44cd-8b28-0cf8100b9c7e}"
},
"rootfs" : {
"start": 293889,
"end" : 1342465,
"uuid" : "{309a3e76-270b-41b2-b5d5-ed8154e7542b}"
},
"data" : {
"start": 1342466,
"end" : 6585346,
"uuid" : "{309a3e76-270b-41b2-b5d5-ed8154e7542b}"
}
}
</code></pre>
<p>La configuration du fichier fit :</p>
<pre><code class="sh"> /dts-v1/<span class="p">;</span>
/ <span class="o">{</span>
<span class="nv">description</span> <span class="o">=</span> <span class="s2">"Kernel et dtb pour RescueOS"</span><span class="p">;</span>
<span class="c1">#address-cells = <1>;</span>
images <span class="o">{</span>
kernel <span class="o">{</span>
<span class="nv">description</span> <span class="o">=</span> <span class="s2">"Kernel"</span><span class="p">;</span>
<span class="nv">data</span> <span class="o">=</span> /incbin/<span class="o">(</span><span class="s2">"Image.gz"</span><span class="o">)</span><span class="p">;</span>
<span class="nb">type</span> <span class="o">=</span> <span class="s2">"kernel"</span><span class="p">;</span>
<span class="nv">arch</span> <span class="o">=</span> <span class="s2">"arm64"</span><span class="p">;</span>
<span class="nv">os</span> <span class="o">=</span> <span class="s2">"linux"</span><span class="p">;</span>
<span class="nv">compression</span> <span class="o">=</span> <span class="s2">"gzip"</span><span class="p">;</span>
<span class="nv">load</span> <span class="o">=</span> <0x44000000><span class="p">;</span>
<span class="nv">entry</span> <span class="o">=</span> <0x44000000><span class="p">;</span>
hash-1 <span class="o">{</span>
<span class="nv">algo</span> <span class="o">=</span> <span class="s2">"sha1"</span><span class="p">;</span>
<span class="o">}</span><span class="p">;</span>
<span class="o">}</span><span class="p">;</span>
fdt <span class="o">{</span>
<span class="nv">description</span> <span class="o">=</span> <span class="s2">"Flattened Device Tree blob"</span><span class="p">;</span>
<span class="nv">data</span> <span class="o">=</span> /incbin/<span class="o">(</span><span class="s2">"diagbox.dtb"</span><span class="o">)</span><span class="p">;</span>
<span class="nb">type</span> <span class="o">=</span> <span class="s2">"flat_dt"</span><span class="p">;</span>
<span class="nv">arch</span> <span class="o">=</span> <span class="s2">"arm64"</span><span class="p">;</span>
<span class="nv">load</span> <span class="o">=</span> <0x47000000><span class="p">;</span>
<span class="nv">compression</span> <span class="o">=</span> <span class="s2">"none"</span><span class="p">;</span>
hash-1 <span class="o">{</span>
<span class="nv">algo</span> <span class="o">=</span> <span class="s2">"sha1"</span><span class="p">;</span>
<span class="o">}</span><span class="p">;</span>
<span class="o">}</span><span class="p">;</span>
fdt-nand<span class="o">{</span>
<span class="nv">data</span> <span class="o">=</span> /incbin/<span class="o">(</span><span class="s2">"diagbox-nand.dtbo"</span><span class="o">)</span><span class="p">;</span>
<span class="nb">type</span> <span class="o">=</span> <span class="s2">"flat_dt"</span><span class="p">;</span>
<span class="nv">arch</span> <span class="o">=</span> <span class="s2">"arm64"</span><span class="p">;</span>
<span class="o">}</span><span class="p">;</span>
<span class="o">}</span><span class="p">;</span>
ramdisk <span class="o">{</span>
<span class="nv">description</span> <span class="o">=</span> <span class="s2">"ramdisk"</span><span class="p">;</span>
<span class="nv">data</span> <span class="o">=</span> /incbin/<span class="o">(</span><span class="s2">"rootfs.cpio.gz"</span><span class="o">)</span><span class="p">;</span>
<span class="nb">type</span> <span class="o">=</span> <span class="s2">"ramdisk"</span><span class="p">;</span>
<span class="nv">arch</span> <span class="o">=</span> <span class="s2">"arm64"</span><span class="p">;</span>
<span class="nv">os</span> <span class="o">=</span> <span class="s2">"linux"</span><span class="p">;</span>
<span class="nv">compression</span> <span class="o">=</span> <span class="s2">"gzip"</span><span class="p">;</span>
hash-1 <span class="o">{</span>
<span class="nv">algo</span> <span class="o">=</span> <span class="s2">"sha1"</span><span class="p">;</span>
<span class="o">}</span><span class="p">;</span>
<span class="o">}</span><span class="p">;</span>
configurations <span class="o">{</span>
<span class="nv">default</span> <span class="o">=</span> <span class="s2">"conf-1"</span><span class="p">;</span>
conf-1 <span class="o">{</span>
<span class="nv">description</span> <span class="o">=</span> <span class="s2">"Configuration"</span><span class="p">;</span>
<span class="nv">kernel</span> <span class="o">=</span> <span class="s2">"kernel"</span><span class="p">;</span>
<span class="nv">fdt</span> <span class="o">=</span> <span class="s2">"fdt"</span>, <span class="s2">"fdt-nand"</span><span class="p">;</span>
<span class="nv">ramdisk</span> <span class="o">=</span> <span class="s2">"ramdisk"</span><span class="p">;</span>
hash-1 <span class="o">{</span>
<span class="nv">algo</span> <span class="o">=</span> <span class="s2">"sha1"</span><span class="p">;</span>
<span class="o">}</span><span class="p">;</span>
<span class="o">}</span><span class="p">;</span>
<span class="o">}</span><span class="p">;</span>
<span class="o">}</span><span class="p">;</span></code></pre>
<p>Et le fichier uEnv.txt de uboot :</p>
<pre><code class="sh"> <span class="nv">board</span><span class="o">=</span>bpi-r3
<span class="nv">device</span><span class="o">=</span>mmc
<span class="nv">partition</span><span class="o">=</span><span class="m">0</span>:5
<span class="nv">bootenv</span><span class="o">=</span>uEnv.txt
<span class="nv">bootdevice</span><span class="o">=</span>sd
<span class="nv">fit</span><span class="o">=</span>bpi-r3.itb
<span class="c1">#bootconf="#conf-2"</span>
<span class="c1">#initrd=rootfs.cpio.zst</span>
<span class="nv">loadaddr</span><span class="o">=</span>0x46000000
<span class="nv">kaddr</span><span class="o">=</span>0x46000000
<span class="nv">rdaddr</span><span class="o">=</span>0x48000000
<span class="nv">root</span><span class="o">=</span>/dev/mmcblk0p6 <span class="nv">rootfstype</span><span class="o">=</span>ext4 rootwait
<span class="nv">console</span><span class="o">=</span>ttyS0,115200n1 <span class="nv">earlycon</span><span class="o">=</span>uart8250,mmio32,0x11002000
<span class="nv">bootopts</span><span class="o">=</span><span class="nv">debug</span><span class="o">=</span><span class="m">7</span>
<span class="nv">checkenv</span><span class="o">=</span><span class="nb">test</span> -e <span class="si">${</span><span class="nv">device</span><span class="si">}</span> <span class="si">${</span><span class="nv">partition</span><span class="si">}</span> <span class="si">${</span><span class="nv">bootenv</span><span class="si">}</span>
<span class="nv">loadenvfile</span><span class="o">=</span><span class="k">if</span> fatload <span class="si">${</span><span class="nv">device</span><span class="si">}</span> <span class="si">${</span><span class="nv">partition</span><span class="si">}</span> <span class="si">${</span><span class="nv">loadaddr</span><span class="si">}</span> <span class="si">${</span><span class="nv">bootenv</span><span class="si">}</span><span class="p">;</span><span class="k">then</span> env import -t <span class="si">${</span><span class="nv">loadaddr</span><span class="si">}</span> <span class="si">${</span><span class="nv">filesize</span><span class="si">}</span><span class="p">;</span><span class="k">else</span> <span class="nb">echo</span> <span class="s2">"fatload (</span><span class="si">${</span><span class="nv">bootenv</span><span class="si">}</span><span class="s2">) failed"</span><span class="p">;</span><span class="k">fi</span>
<span class="nv">loadenv</span><span class="o">=</span><span class="k">if</span> run checkenv<span class="p">;</span><span class="k">then</span> run loadenvfile<span class="p">;</span><span class="k">fi</span>
<span class="nv">resetenv</span><span class="o">=</span>env default -a<span class="p">;</span>printenv<span class="p">;</span>
<span class="nv">loadkernel</span><span class="o">=</span>fatload <span class="nv">$device</span> <span class="nv">$partition</span> <span class="nv">$kaddr</span> <span class="si">${</span><span class="nv">kernel</span><span class="si">}</span>
<span class="nv">buildargs</span><span class="o">=</span>setenv bootargs <span class="s2">"board=</span><span class="si">${</span><span class="nv">board</span><span class="si">}</span><span class="s2"> earlycon=uart8250,mmio32,0x11002000 </span><span class="si">${</span><span class="nv">bootopts</span><span class="si">}</span><span class="s2"> root=</span><span class="si">${</span><span class="nv">root</span><span class="si">}</span><span class="s2">"</span>
<span class="c1">#console=${console}</span>
<span class="nv">useusb</span><span class="o">=</span><span class="k">if</span> usb info<span class="p">;</span> <span class="k">then</span> usb reset<span class="p">;</span><span class="k">else</span> usb start<span class="p">;</span><span class="k">fi</span><span class="p">;</span> setenv device usb<span class="p">;</span>setenv partition <span class="m">0</span>:1<span class="p">;</span>ls <span class="si">${</span><span class="nv">device</span><span class="si">}</span> <span class="si">${</span><span class="nv">partition</span><span class="si">}</span>
<span class="nv">useinitrd</span><span class="o">=</span>setenv root <span class="s2">"/dev/ram0 rw"</span><span class="p">;</span>setenv bootopts <span class="s2">"</span><span class="si">${</span><span class="nv">bootopts</span><span class="si">}</span><span class="s2"> initrd=</span><span class="si">${</span><span class="nv">rdaddr</span><span class="si">}</span><span class="s2">,20M"</span><span class="p">;</span>fatload <span class="si">${</span><span class="nv">device</span><span class="si">}</span> <span class="si">${</span><span class="nv">partition</span><span class="si">}</span> <span class="si">${</span><span class="nv">rdaddr</span><span class="si">}</span> <span class="si">${</span><span class="nv">initrd</span><span class="si">}</span><span class="p">;</span>
<span class="nv">checkrd</span><span class="o">=</span><span class="k">if</span> printenv initrd<span class="p">;</span><span class="k">then</span> run useinitrd<span class="p">;</span><span class="k">fi</span>
<span class="nv">newboot</span><span class="o">=</span>run checkrd<span class="p">;</span> run buildargs<span class="p">;</span><span class="k">if</span> printenv fit<span class="p">;</span><span class="k">then</span> setenv kernel <span class="si">${</span><span class="nv">fit</span><span class="si">}</span><span class="p">;</span><span class="k">if</span> run loadkernel<span class="p">;</span> <span class="k">then</span> bootm <span class="si">${</span><span class="nv">kaddr</span><span class="si">}${</span><span class="nv">bootconf</span><span class="si">}</span><span class="p">;</span> <span class="k">fi</span><span class="p">;</span><span class="k">fi</span><span class="p">;</span></code></pre>
<p>Si quelqu'un a une idée :)</p>
<p>En vous remerciant d'avance.</p>
<div><a href="https://linuxfr.org/forums/linux-embarque/posts/uboot-inclure-initrd-dans-le-fichier-fit.epub">Télécharger ce contenu au format EPUB</a></div> <p>
<strong>Commentaires :</strong>
<a href="//linuxfr.org/nodes/128903/comments.atom">voir le flux Atom</a>
<a href="https://linuxfr.org/forums/linux-embarque/posts/uboot-inclure-initrd-dans-le-fichier-fit#comments">ouvrir dans le navigateur</a>
</p>
doudootianahttps://linuxfr.org/nodes/128903/comments.atomtag:linuxfr.org,2005:Post/428932022-05-16T18:34:57+02:002022-05-16T18:34:57+02:00Logiciel de simulation/développement de schéma électronique<p>Bonjour,</p>
<p>J'aimerais me lancer dans la conception d'un schéma électronique contenant entre autre une puce GPS.</p>
<p>J'aimerais savoir si il existe sur Linux des logiciels libres (gratuit ?) permettant de réaliser ce genre de chose ?</p>
<p>L'idée serait de pouvoir créer le PCB (pas besoin de fonctionnalités avancées), importer des composants industriels existant (comme la puce GPS) et pouvoir développer et simuler le firmware.</p>
<p>Je connais très peu ce monde, j'ai donc du mal à démarrer.</p>
<p>Merci pour votre aide :)</p>
<div><a href="https://linuxfr.org/forums/linux-embarque/posts/logiciel-de-simulation-developpement-de-schema-electronique.epub">Télécharger ce contenu au format EPUB</a></div> <p>
<strong>Commentaires :</strong>
<a href="//linuxfr.org/nodes/127764/comments.atom">voir le flux Atom</a>
<a href="https://linuxfr.org/forums/linux-embarque/posts/logiciel-de-simulation-developpement-de-schema-electronique#comments">ouvrir dans le navigateur</a>
</p>
Watchwolfhttps://linuxfr.org/nodes/127764/comments.atomtag:linuxfr.org,2005:Post/424962021-11-11T10:21:26+01:002021-11-11T19:23:47+01:00exécuter un script bash local sur une machine distante via le ssh<p>Hello à toutes et à tous.</p>
<p>Depuis quelques jours, j'essaie via le ssh d'exécuter sur une machine distante, <br>
un script bash que j'ai en local.</p>
<p>Si je me connecte en SSH sur la machine distante,<br>
et que j'exécute la commande directement, ça fonctionne.</p>
<p>Cependant, lorsque j'essaie à partir de mon script local j'ai cette erreur :</p>
<pre><code class="sh">execl<span class="o">()</span><span class="p">;</span> errno <span class="m">2</span>
Couldn<span class="err">'</span>t save environment -1#</code></pre>
<p>Voici la commande que j'aimerais exécuter :</p>
<pre><code class="sh">/opt/lantiq/bin/sfp_i2c -i11 -s XXXXXXXXXX</code></pre>
<p>Voici les scripts :</p>
<ul>
<li>Celui que j'exécute en local pour établir la connexion en ssh :</li>
</ul>
<pre><code class="sh"> <span class="c1">#/bin/bash</span>
<span class="nv">pass</span><span class="o">=</span><span class="nv">$1</span>
sudo sshpass -p <span class="s1">'XXXXXXXXXX'</span> ssh -y ONTUSER@192.168.1.10 <span class="s1">'ash -s'</span> < /tmp/test1.sh <span class="nv">$pass</span></code></pre>
<ul>
<li>Celui que j'aimerais exécuter à distance :</li>
</ul>
<pre><code class="sh"> <span class="c1">#!/bin/ash</span>
<span class="nv">pass</span><span class="o">=</span><span class="nv">$1</span>
<span class="nb">echo</span> <span class="nv">$pass</span>
/opt/lantiq/bin/sfp_i2c -i11 -s <span class="nv">$PASS</span></code></pre>
<p>J'ai essayé en remplaçant #!/bin/ash par #!/usr/bin/env ash, mais le résultat est le même.</p>
<p>Si quelqu'un a une idée :)</p>
<p>Merci par avance</p>
<p>Doudoo</p>
<div><a href="https://linuxfr.org/forums/linux-embarque/posts/executer-un-script-bash-local-sur-une-machine-distante-via-le-ssh.epub">Télécharger ce contenu au format EPUB</a></div> <p>
<strong>Commentaires :</strong>
<a href="//linuxfr.org/nodes/125938/comments.atom">voir le flux Atom</a>
<a href="https://linuxfr.org/forums/linux-embarque/posts/executer-un-script-bash-local-sur-une-machine-distante-via-le-ssh#comments">ouvrir dans le navigateur</a>
</p>
doudootianahttps://linuxfr.org/nodes/125938/comments.atomtag:linuxfr.org,2005:Post/424392021-10-15T15:27:46+02:002021-10-15T15:27:46+02:00Phylink et sfp<p>Bonjour à toutes et à tous.</p>
<p>Pour un projet, j'utilise la sbc clearfog base ainsi que deux modules sfp gpon ONU ( Ubiquiti uf instant et l'autre de marque fs).</p>
<p>Ces deux modules ont des accès telnet et/ou ssh, dont j'ai besoin d'exploiter via ma clearfog.</p>
<p>L'os utilisé est basé sur Linux et les interfaces sont gérés par le fichier /etc/network/interfaces.</p>
<p>Ma clearfog possède trois interfaces ethernet : 0 et 1 pour les RJ45 et le 2 pour la cage sfp.</p>
<p>En utilisant un convertisseur TP link mc220l, j'arrive à accéder en telet ou ssh :</p>
<p>L'adresse IP de l'ubiquiti est 192.168.1.1 donc je donne une IP dans le même sous réseau a mon pc et bingo.<br>
Idem pour le fs dont l'adresse IP est 192.168.1.10</p>
<p>J'ai essayé de faire de même avec ma clearfog en donnant une IP dans le sous réseau de l'IP du module, mais également en donnant l'IP du module.<br>
Quand je donne l'IP du module a mon interface, je peux communiquer en ssh mais avec la carte, pas le module.</p>
<p>En faisant des recherches sur le web, j'ai vu la notion phylink qui, si je ne me trompe pas, lie le module sfp au Mac de la carte.</p>
<p>Après deux semaines de recherches, bidouilles et tests, j'en suis toujours au même point et je tourne en rond.</p>
<p>Besoin d'aide svp :)</p>
<div><a href="https://linuxfr.org/forums/linux-embarque/posts/phylink-et-sfp.epub">Télécharger ce contenu au format EPUB</a></div> <p>
<strong>Commentaires :</strong>
<a href="//linuxfr.org/nodes/125703/comments.atom">voir le flux Atom</a>
<a href="https://linuxfr.org/forums/linux-embarque/posts/phylink-et-sfp#comments">ouvrir dans le navigateur</a>
</p>
doudootianahttps://linuxfr.org/nodes/125703/comments.atomtag:linuxfr.org,2005:Post/424112021-09-28T11:03:41+02:002021-09-28T11:03:41+02:00[HDD] : Passage de l'OS Raspian vers Raspi Debian<p>Bonjour,</p>
<p>J'ai installé le projet Raspi Debian pour ma rpi 4 model B (2018) 2Go de RAM.</p>
<p><a href="https://raspi.debian.net/tested-images/">https://raspi.debian.net/tested-images/</a></p>
<p>Le boot USB au démarrage est activé pour booter directement sur mon HDD Toshiba 2To.</p>
<p>Le HDD est relié en USB à la rpi via un connecteur qui prend Alim+Sata du HDD. (log dmesg en dessous). </p>
<pre><code>scsi 0:0:0:0: Direct-Access ASMT 2115 0 PQ: 0 ANSI: 6
</code></pre>
<p>J'ai une alimentation externe qui vient alimenter le HDD.</p>
<p>Problème : le HDD grate souvent, donc un spin up/dpwn régulier.</p>
<p>J'ai essayé plusieurs solutions sans succès.</p>
<p>Notemment, ajouter dans le fichier /etc/default/raspi-firmware-custom la directive suviante,</p>
<pre><code>--Pass 600mA to 1200mA USB courant--
max_usb_current=1
</code></pre>
<p>Et lancé </p>
<pre><code>update-initramfs -u -k all
</code></pre>
<p>Je pense plutôt à un problème de gestion du disque ou de driver.</p>
<p>Voici les logs dmesg <a href="https://dpaste.org/kTtV">https://dpaste.org/kTtV</a></p>
<p>Auriez-vous une idée ?</p>
<p>Avez-vous déjà utilisé Raspi Debian avec un HDD externe ?</p>
<p>Merci beaucoup pour vos retours</p>
<div><a href="https://linuxfr.org/forums/linux-embarque/posts/hdd-passage-de-l-os-raspian-vers-raspi-debian.epub">Télécharger ce contenu au format EPUB</a></div> <p>
<strong>Commentaires :</strong>
<a href="//linuxfr.org/nodes/125553/comments.atom">voir le flux Atom</a>
<a href="https://linuxfr.org/forums/linux-embarque/posts/hdd-passage-de-l-os-raspian-vers-raspi-debian#comments">ouvrir dans le navigateur</a>
</p>
electro575https://linuxfr.org/nodes/125553/comments.atomtag:linuxfr.org,2005:Post/422502021-07-18T11:11:16+02:002021-07-18T11:17:24+02:00Comment faire du CI/CD et automatiser les tests sur de l'embarqué ?<p>Hello.</p>
<p>Depuis un moment déjà, je m' "amuse" à programmer la <a href="https://embeddedcomputing.weebly.com/bbc-microbit.html">micro:bit</a> en bare-metal et en assembleur. Je ne tiens pas à développer un truc hyper complet mais juste à comprendre d'un peu plus près les processeurs ARM et leur mode de fonctionnement. Je dois dire que de ce côté c'est assez réussi : l'architecture ARM Cortex M0 qui est utilisée sur le SOC de cette carte est suffisamment simple pour appréhender le monde ARM (jeu d'instruction restreint THUMB, pas de MMU …). Ca permet de 'mettre le pied à l'étrier' relativement faciloement, et de comprendre l'archi ARM "de base", tout en sachant qu'un ARM de raspberry pi est bien plus complexe (mais la base reste la même).</p>
<p>J'aimerais cependant aller un peu plus loin que deux ou trois exemples "basiques" et tenter de mettre en place une petite appli de pilotage d'un robot simple ( un suiveur de ligne par exemple ou autre). Une partie de mes développements/tests nécessiteront du matériel, mais je peux aussi utiliser QEMU pour certaines autres parties (initialisation du hardware, utilisation du timer, communication série, etc …).</p>
<p>Je voudrais pour celà avoir un système un peu plus automatisé qu'un build + lancement manuel de qemu + lancement de gdb + mise en place de points d'arret manuels + contrôle pas à pas que tout ce que je voulais se soit bien passé. J'aimerais mettre un peu plus d'automatisme dedans (par exemple vérifier les valeurs de certaines zones mémoires de façon automatique, et ne lancer le mode trace que lorsque la valeur attendue n'est pas présentée par exemple).</p>
<p>Aussi je me tourne vers vous pour savoir comment vois faites/feriez pour mettre en place des tests automatisés pour la programmation "bas niveau", mais aussi pour satisfaire ma curiosité : comment fait-on ce genre de chose dans le monde industriel : via des outils libres ou du proprio ? Quels outils libres si c'est le cas ?</p>
<p>Merci d'avance.</p>
<p>Quelques infos à propos de la micro:bit :<br>
- en mode qemu, il est possible d'utiliser le moniteur intégré pour inspecter la mémoire (je n'ai pas encore approfondi cette piste mais les commandes ont l'air d'être très proches de gdb).<br>
- la micro-bit intègre une puce dédiée ( MKL26Z128 MCU ) qui permet d'utiliser OpenOCD/GDB pour le debug hardware (DAPlLink protocol).</p>
<p>C'est ce genre de raison qui me font largement préférer la Micro:bit à l'Arduino : pour beaucoup de cartes arduino, en dehors du moniteur arduino, c'est assez difficile d'en faire quelque chose (je pense notamment à la Teensy 4 que j'ai achetée mais qui me sert à rien car le debug n'est possible qu'à coup de printf - et si on veut faire du vrai bas niveau, c'est mort).</p>
<div><a href="https://linuxfr.org/forums/linux-embarque/posts/comment-faire-du-ci-cd-et-automatiser-les-tests-sur-de-l-embarque.epub">Télécharger ce contenu au format EPUB</a></div> <p>
<strong>Commentaires :</strong>
<a href="//linuxfr.org/nodes/124897/comments.atom">voir le flux Atom</a>
<a href="https://linuxfr.org/forums/linux-embarque/posts/comment-faire-du-ci-cd-et-automatiser-les-tests-sur-de-l-embarque#comments">ouvrir dans le navigateur</a>
</p>
totof2000https://linuxfr.org/nodes/124897/comments.atomtag:linuxfr.org,2005:Post/422412021-07-09T19:11:24+02:002021-07-09T19:13:59+02:00Firefly station P2: la carte ARM qui ne sera pas<p><em>Je poste l'information sur le forum car ce n'est pas digne d'un journal.</em></p>
<p>Il y a eu en début d'année une campagne de financement participatif pour une carte ARM à base du SoC RockChip RK3568: <a href="https://www.indiegogo.com/projects/station-p2-powerful-open-source-geek-computer#/">https://www.indiegogo.com/projects/station-p2-powerful-open-source-geek-computer#/</a><br>
Ce SoC a moins de coeurs que le RK3399 mais plus de connectique: le projet prévoyait deux ports ethernet gigabit, deux antennes wifi, un port sata et un port pcie m2. Je trouve ça idéal car ça fusionnerait une box, un nas et un boitier multimédia d'un coup. Dommage que l'objectif de financement n'ai pas été atteint.</p>
<div><a href="https://linuxfr.org/forums/linux-embarque/posts/firefly-station-p2-la-carte-arm-qui-ne-sera-pas.epub">Télécharger ce contenu au format EPUB</a></div> <p>
<strong>Commentaires :</strong>
<a href="//linuxfr.org/nodes/124827/comments.atom">voir le flux Atom</a>
<a href="https://linuxfr.org/forums/linux-embarque/posts/firefly-station-p2-la-carte-arm-qui-ne-sera-pas#comments">ouvrir dans le navigateur</a>
</p>
nlgrangerhttps://linuxfr.org/nodes/124827/comments.atom