From: "Дмитрий Терехин" <jqt4@basealt.ru> To: Single-board computer software development discussions <devel-sbc@lists.altlinux.org>, community <community@lists.altlinux.org> Subject: [Comm] ALT Simply alpha для Raspberry Pi 4 Date: Mon, 25 Jan 2021 17:44:44 +0300 Message-ID: <594611611585613@mail.yandex.ru> (raw) [-- Attachment #1: Type: text/plain, Size: 3192 bytes --] Здравствуйте! Доступны сборки под 32 битную (armh) и 64 битную (aarch64) архитектуры для Raspberry Pi 4 на стабильной ветке p9 с брендингом ALT Simply: http://ftp.altlinux.org/pub/people/jqt4/images/rpi4/slinux-rpi4-9.0.8-alpha1-armh.img.xz http://ftp.altlinux.org/pub/people/jqt4/images/rpi4/slinux-rpi4-9.0.8-alpha1-armh.img.xz.md5 http://ftp.altlinux.org/pub/people/jqt4/images/rpi4/slinux-rpi4-9.0.8-alpha1-aarch64.img.xz http://ftp.altlinux.org/pub/people/jqt4/images/rpi4/slinux-rpi4-9.0.8-alpha1-aarch64.img.xz.md5 Особенности armh: Ядро версии 5.4.83 Особенности aarch64: Ядро версии 5.10.7 "из коробки" Ядро версии 5.4.83 также установлено, на него можно переключиться с помощью скриптов из пакета rpi4-boot-switch. Для установки потребуется карта памяти не менее 8 Гб. Метод установки тот же, что и для предыдущих образов для Raspberry Pi 4 https://www.altlinux.org/Write/rootfs#Запись_образа_img_на_SD-карту Проблемы на RPi4: Образы armh субъективно работают медленнее, чем aarch64. Особенно сильно это заметно при воспроизведении видео 1920х1080 на полный экран в firefox: aarch64 - небольшие лаги; armh - лаги неприемлемые. В образах armh проблема с bluetooth: blueberry не ищет устройства, поскольку bluetoothd падает. Можно выполнить поиск устройств из командной строки с помощью bluetoothctl В этом случае устройства удаётся найти и далее использовать blueberry. При загрузке образа aarch64 иногда (примерно 20% случаев) выдаются сообщения о сбоях ядра. Примеры приведены в приложении. Влияния на работу не заметил. Также было выполнено менее подробное тестирование образа aarch64 на RPi3 и образа armh на RPi2. Проблемы: На RPi2 воспроизвелась ошибка https://bugzilla.altlinux.org/show_bug.cgi?id=38418 Для обхода нужно прописать в config.txt [pi2] dtoverlay=vc4-fkms-v3d На RPi3 "из коробки" не работает ускорение 3D. Нужно его включить, прописав в config.txt [pi3] dtoverlay=vc4-fkms-v3d На RPi3 не работает встроенный bluetooth. Отсутствует каталог /sys/class/bluetooth, наличие которого проверяет bluetoothd.service systemctl cat bluetoothd.service ... ConditionPathIsDirectory=/sys/class/bluetooth ... Как исправить непонятно. С уважением Дмитрий Терёхин [-- Attachment #2: log.txt --] [-- Type: text/plain, Size: 7672 bytes --] [ 7.201071] ------------[ cut here ]------------ [ 7.223029] mmc0: new ultra high speed DDR50 SDHC card at address aaaa [ 7.225321] Firmware transaction timeout [ 7.230781] mmcblk0: mmc0:aaaa SB32G 29.7 GiB [ 7.236138] WARNING: CPU: 3 PID: 177 at drivers/firmware/raspberrypi.c:64 rpi_firmware_transaction+0xe0/0x110 [ 7.245843] mmcblk0: p1 p2 [ 7.247106] Modules linked in: [ 7.411083] usb 1-1.3: new low-speed USB device number 3 using xhci_hcd [ 7.414883] CPU: 3 PID: 177 Comm: kworker/3:2 Not tainted 5.10.7-rpi-un-alt1 #2 [ 7.559166] usb 1-1.3: New USB device found, idVendor=1a2c, idProduct=4c5e, bcdDevice= 1.10 [ 7.559984] Hardware name: Raspberry Pi 4 Model B Rev 1.4 (DT) [ 7.559994] Workqueue: events dbs_work_handler [ 7.567490] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 7.573826] [ 7.573831] pstate: 60000005 (nZCv daif -PAN -UAO -TCO BTYPE=--) [ 7.573835] pc : rpi_firmware_transaction+0xe0/0x110 [ 7.582212] usb 1-1.3: Product: USB Keyboard [ 7.589525] lr : rpi_firmware_transaction+0xe0/0x110 [ 7.589527] sp : ffff800015173a50 [ 7.594468] usb 1-1.3: Manufacturer: SEMICO [ 7.600987] x29: ffff800015173a50 x28: 0000000000000000 [ 7.613883] input: SEMICO USB Keyboard as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.0/0003:1A2C:4C5E.0001/input/input0 [ 7.619324] [ 7.619329] x27: ffff000100b24648 x26: ffff000105a45b00 [ 8.704034] x25: ffff0001009fc280 x24: ffff80001420d008 [ 8.710847] printk: console [netcon0] enabled [ 8.717616] x23: 0000000000001000 x22: ffff0001009fc280 [ 8.717620] x21: 00000000ffffff92 x20: ffff800013a69f58 [ 8.723368] netconsole: network logging started [ 8.730136] [ 8.730139] x19: ffff800013479d88 [ 8.737195] of_cfs_init [ 8.742872] x18: 0000000000000010 [ 8.742874] x17: 000000004f97055c x16: 00000000b374c2dd [ 8.742879] x15: ffffffffffffffff [ 8.745776] of_cfs_init: OK [ 8.750558] x14: ffff800013479d88 [ 8.754528] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 8.759165] x13: ffff800095173717 x12: ffff80001517371f [ 8.773833] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 8.775061] [ 8.775070] x11: 0000000000000002 [ 8.779933] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 8.789020] x10: ffff800015173680 [ 8.789023] x9 : ffff8000100fb980 x8 : 3939312029632820 [ 8.789026] x7 : 746867697279706f x6 : ffff8000151736c0 [ 8.795721] cfg80211: failed to load regulatory.db [ 8.803708] [ 8.803709] x5 : 0000000000000000 x4 : ffff000100b03c00 [ 8.855493] x3 : ffff80001347a000 x2 : ffff80001347adf0 [ 8.862190] x1 : af86458623e88100 x0 : 0000000000000000 [ 8.868880] Call trace: [ 8.872645] rpi_firmware_transaction+0xe0/0x110 [ 8.878603] rpi_firmware_property_list+0xc0/0x180 [ 8.884733] rpi_firmware_property+0x78/0x110 [ 8.890410] raspberrypi_fw_get_rate+0x54/0x88 [ 8.896168] clk_recalc+0x40/0xb0 [ 8.900775] __clk_recalc_rates+0x40/0xa8 [ 8.906080] clk_core_get_rate_recalc+0x68/0x78 [ 8.911901] clk_get_rate+0x30/0x50 [ 8.916647] dev_pm_opp_set_rate+0x80/0x570 [ 8.922084] set_target+0x38/0x48 [ 8.926637] __cpufreq_driver_target+0x1a0/0x5e8 [ 8.932509] cs_dbs_update+0xe0/0x168 [ 8.937390] dbs_work_handler+0x48/0x80 [ 8.942455] process_one_work+0x200/0x468 [ 8.947668] worker_thread+0x158/0x508 [ 8.952617] kthread+0x12c/0x130 [ 8.957027] ret_from_fork+0x10/0x34 [ 8.961767] ---[ end trace be2ec2d260c95122 ]--- [ 7.130299] ------------[ cut here ]------------ [ 7.142671] input: SEMICO USB Keyboard Consumer Control as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.1/0003:1A2C:4C5E.0002/input/input1 [ 7.147018] Firmware transaction timeout [ 7.147099] WARNING: CPU: 2 PID: 171 at drivers/firmware/raspberrypi.c:63 rpi_firmware_transaction+0xe0/0x110 [ 7.210574] input: SEMICO USB Keyboard System Control as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.1/0003:1A2C:4C5E.0002/input/input2 [ 7.212697] Modules linked in: [ 7.217031] input: SEMICO USB Keyboard as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.1/0003:1A2C:4C5E.0002/input/input4 [ 7.222761] CPU: 2 PID: 171 Comm: kworker/2:3 Not tainted 5.4.83-rpi-def-alt1 #2 [ 7.222764] Hardware name: Raspberry Pi 4 Model B Rev 1.4 (DT) [ 7.222779] Workqueue: events dbs_work_handler [ 7.230593] hid-generic 0003:1A2C:4C5E.0002: input,hiddev0,hidraw1: USB HID v1.10 Keyboard [SEMICO USB Keyboard] on usb-0000:01:00.0-1.3/input1 [ 7.238295] pstate: 60000005 (nZCv daif -PAN -UAO) [ 7.238304] pc : rpi_firmware_transaction+0xe0/0x110 [ 7.350330] usb 1-1.4: new low-speed USB device number 4 using xhci_hcd [ 7.355668] lr : rpi_firmware_transaction+0xe0/0x110 [ 7.355674] sp : ffff80001374b9e0 [ 7.497085] usb 1-1.4: New USB device found, idVendor=0000, idProduct=3825, bcdDevice= 1.00 [ 7.499751] x29: ffff80001374b9e0 x28: 0000000000000000 [ 7.507359] usb 1-1.4: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 7.515010] x27: ffff0001f71832a8 x26: ffff0001f0a6d480 [ 7.515017] x25: ffff0001f54fa680 x24: ffff800013166008 [ 7.522703] usb 1-1.4: Product: USB OPTICAL MOUSE [ 7.530363] x23: 0000000000001000 x22: ffff0001f54fa680 [ 7.530369] x21: 00000000ffffff92 x20: ffff800012d98748 [ 7.546332] input: USB OPTICAL MOUSE as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:0000:3825.0003/input/input5 [ 7.550037] x19: ffff800012b79d08 x18: 0000000000000010 [ 7.553625] hid-generic 0003:0000:3825.0003: input,hidraw2: USB HID v1.11 Mouse [ USB OPTICAL MOUSE] on usb-0000:01:00.0-1.4/input0 [ 7.556923] x17: 0000000090da5bcb x16: 00000000ddf61111 [ 8.070371] x15: ffffffffffffffff x14: ffff800012b79d08 [ 8.070377] x13: ffff80009374b677 x12: ffff80001374b67f [ 8.070382] x11: ffff800012ba0000 x10: ffff80001374b600 [ 8.070388] x9 : ffff80001374b9e0 x8 : 6d6974206e6f6974 [ 8.075795] printk: console [netcon0] enabled [ 8.081156] x7 : 6361736e61727420 x6 : ffff80001374b740 [ 8.081162] x5 : 0000000000000000 x4 : ffff0001f0593b80 [ 8.081168] x3 : ffff800012b7a000 x2 : ffff800012b7acf8 [ 8.081173] x1 : 606514bfcaf3e200 x0 : 0000000000000000 [ 8.086559] netconsole: network logging started [ 8.091938] Call trace: [ 8.091949] rpi_firmware_transaction+0xe0/0x110 [ 8.091957] rpi_firmware_property_list+0xbc/0x170 [ 8.096807] of_cfs_init [ 8.101749] rpi_firmware_property+0x74/0x108 [ 8.101759] raspberrypi_fw_set_rate+0x5c/0xd0 [ 8.101766] clk_change_rate+0xd8/0x420 [ 8.107172] of_cfs_init: OK [ 8.112525] clk_core_set_rate_nolock+0x194/0x1d0 [ 8.112529] clk_set_rate+0x38/0xb8 [ 8.112538] dev_pm_opp_set_rate+0x368/0x4c8 [ 8.112547] set_target+0x48/0x88 [ 8.118143] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 8.122512] __cpufreq_driver_target+0x1a4/0x590 [ 8.122518] cs_dbs_update+0xe0/0x160 [ 8.122525] dbs_work_handler+0x44/0x78 [ 8.122535] process_one_work+0x1fc/0x498 [ 8.122542] worker_thread+0x140/0x538 [ 8.122550] kthread+0x124/0x128 [ 8.139245] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 8.141432] ret_from_fork+0x10/0x1c [ 8.141439] ---[ end trace 6442d3390808c256 ]---
next reply other threads:[~2021-01-25 14:44 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-25 14:44 Дмитрий Терехин [this message] 2021-01-26 8:37 ` [Comm] RPI3 bluetooth // was: Re: [devel-sbc] " Ivan A. Melnikov
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=594611611585613@mail.yandex.ru \ --to=jqt4@basealt.ru \ --cc=community@lists.altlinux.org \ --cc=devel-sbc@lists.altlinux.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
ALT Linux Community general discussions This inbox may be cloned and mirrored by anyone: git clone --mirror http://lore.altlinux.org/community/0 community/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 community community/ http://lore.altlinux.org/community \ mandrake-russian@linuxteam.iplabs.ru community@lists.altlinux.org community@lists.altlinux.ru community@lists.altlinux.com public-inbox-index community Example config snippet for mirrors. Newsgroup available over NNTP: nntp://lore.altlinux.org/org.altlinux.lists.community AGPL code for this site: git clone https://public-inbox.org/public-inbox.git