vladvanderwolf
03/23/2023, 7:25 PMpeter.duckett
03/28/2023, 8:40 AM_dhanos_
03/28/2023, 3:53 PMPSU_cover - [01] blank
PSU_cover - [02] blank with PicoPSU
PSU_cover - [03] small partial mesh
PSU_cover - [04] small partial mesh with PicoPSU
PSU_cover - [05] small full mesh
PSU_cover - [06] small full mesh with PicoPSU
PSU_cover - [07] big partial mesh
PSU_cover - [08] big partial mesh with PicoPSU
PSU_cover - [09] big full mesh
PSU_cover - [10] big full mesh with PicoPSU
PSU_cover - [11] small FAN mesh
PSU_cover - [12] small FAN mesh with PicoPSU
PSU_cover - [13] small full with FAN mesh
PSU_cover - [14] small full with FAN mesh with PicoPSU
PSU_cover - [15] big FAN mesh
PSU_cover - [16] big FAN mesh with PicoPSU
PSU_cover - [17] big full with FAN mesh
PSU_cover - [18] big full with FAN mesh with PicoPSU
PSU_cover - [19] small FAN mesh with center FAN cover
PSU_cover - [20] small FAN mesh with center FAN cover with PicoPSU
PSU_cover - [21] small full with FAN mesh with center FAN cover
PSU_cover - [22] small full with FAN mesh with center FAN cover with PicoPSU
PSU_cover - [23] big FAN mesh with center FAN cover
PSU_cover - [24] big FAN mesh with center FAN cover with PicoPSU
PSU_cover - [25] big full with FAN mesh with center FAN cover
PSU_cover - [26] big full with FAN mesh with center FAN cover with PicoPSU
PSU_cover - [27] FAN cover
PSU_cover - [28] FAN cover with PicoPSU
PSU_cover - [29] FAN cover with full small mesh
PSU_cover - [30] FAN cover with full small mesh with PicoPSU
PSU_cover - [31] FAN cover with full big mesh
PSU_cover - [32] FAN cover with full big mesh with PicoPSU
PSU_cover - [33] big FAN mesh with small full mesh
PSU_cover - [34] big FAN mesh with small full mesh with PicoPSU
PSU_cover - [35] big FAN mesh with center FAN cover with small full mesh
PSU_cover - [36] big FAN mesh with center FAN cover with small full mesh with PicoPSU
Some photos and screenshots:Hizzie
03/30/2023, 9:11 PM01dcod3r
04/07/2023, 12:55 PMpandermusubi
04/09/2023, 6:43 AMdaboone72
04/09/2023, 9:41 AMblueatria
04/10/2023, 5:20 AMleroy
04/10/2023, 3:37 PMmachinchose
04/11/2023, 6:16 PMtrezm
04/12/2023, 7:12 PMjasonmccallister
04/12/2023, 7:47 PM_dhanos_
04/13/2023, 10:10 AMpadigru
04/13/2023, 5:03 PMStephenStrangeWare
04/13/2023, 8:36 PMcyphersnep
04/13/2023, 9:43 PMdaboone72
04/14/2023, 9:24 AMdejandayoff
04/14/2023, 9:18 PMpi@test-pi:~ $ lspci
00:00.0 PCI bridge: Broadcom Inc. and subsidiaries BCM2711 PCIe Bridge (rev 20)
01:00.0 IDE interface: ASMedia Technology Inc. ASM1061 SATA IDE Controller (rev 02)
pi@test-pi:~ $ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931.5G 0 disk
mmcblk0 179:0 0 59.7G 0 disk
├─mmcblk0p1 179:1 0 256M 0 part /boot
└─mmcblk0p2 179:2 0 59.4G 0 part /
As you can see above, sda is found when running lsblk. Here is some information about the version:
pi@test-pi:~ $ uname -a
Linux test-pi 5.15.84-v8+ #1613 SMP PREEMPT Thu Jan 5 12:03:08 GMT 2023 aarch64 GNU/Linux
pi@test-pi:~ $
However, when installing Ubuntu, it doesn't work:
ubuntu@ubuntu-test:~$ lspci
00:00.0 PCI bridge: Broadcom Inc. and subsidiaries BCM2711 PCIe Bridge (rev 20)
01:00.0 IDE interface: ASMedia Technology Inc. ASM1061 SATA IDE Controller (rev 02)
ubuntu@ubuntu-test:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 59.1M 1 loop /snap/core20/1826
loop1 7:1 0 43.2M 1 loop /snap/snapd/18363
loop2 7:2 0 109.6M 1 loop /snap/lxd/24326
loop3 7:3 0 43.2M 1 loop /snap/snapd/18600
loop4 7:4 0 59.1M 1 loop /snap/core20/1856
mmcblk0 179:0 0 59.7G 0 disk
├─mmcblk0p1 179:1 0 256M 0 part /boot/firmware
└─mmcblk0p2 179:2 0 59.4G 0 part /
/dev/sda is not found in lsblk. I'm running Ubuntu 22.04 64 bit
ubuntu@ubuntu-test:~$ uname -a
Linux ubuntu-test 5.15.0-1024-raspi #26-Ubuntu SMP PREEMPT Wed Jan 18 15:29:53 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux
In dmesg I find BAR 4: no space for [io size 0x0020]
errors:
I saw mentions that the SATA controller should work in Both OS's. Has anyone been able to get Ubuntu to work?StephenStrangeWare
04/16/2023, 3:19 PM.surgicalstrike
04/16/2023, 10:53 PMrkkochie
04/17/2023, 6:16 AMLeK
04/17/2023, 12:16 PMgeekbri
04/17/2023, 2:18 PMphearzero
04/18/2023, 1:04 AMopt
query param and use HTTP Methods.
- GET
returns the current state (get power|nodeinfo)
- PUT
updates the node state (set power, etc)
- POST
perform an operation, set bulk data, or upload data (network reset, firmware update)
Second is make the routes more deterministic by moving the type
query param into a path. Example:
bash
# BMC USB State
curl -X GET 127.0.0.1/api/bmc/usb
# Array response
curl -X GET 127.0.0.1/api/bmc/info
curl -X GET 127.0.0.1/api/bmc/power
# Single node response
curl -X GET 127.0.0.1/api/bmc/node/1/info
# Set Power using Array
curl -X POST -d '[1,1,0,0]' 127.0.0.1/api/bmc/power
# Individual control
curl -X PUT -d '1' 127.0.0.1/api/bmc/node/1/power
https://github.com/PhearZero/turing-pi-api/blob/main/v1.0.1.oas.ymlappinteractive
04/18/2023, 1:56 PMStephenStrangeWare
04/18/2023, 4:42 PMStephenStrangeWare
04/18/2023, 5:56 PMfrenger
04/18/2023, 6:04 PMStephenStrangeWare
04/18/2023, 7:36 PMappinteractive
04/19/2023, 11:03 AMssh 192.168.178.81 -v
which I configures and is also showing up in the network (host name is not showing correctly in frizbox) and I only getting Permission denied (publickey,password)
I also tried to use the ssh keys and configured those in the pi imager but with no luck, they are there in the user_data
file but login is not possible.
Any ideas or suggestions?