| 05:23.01 | *** join/#devuan infobot (ibot@c-174-52-60-165.hsd1.ut.comcast.net) |
| 05:23.01 | *** topic/#devuan is Welcome to Devuan! https://devuan.org | Releases: https://files.devuan.org (Jessie 1.0 old-stable, ASCII 2.1 stable) | | Conference (2019) https://www.dyne.org/the-first-devuan-conference/ | Forum https://dev1galaxy.org | Chanlogs http://maemo.cloud-7.de/irclogs/freenode/_devuan/ |
| 05:23.02 | *** mode/#devuan [+v infobot] by ChanServ |
| 05:27.12 | tuxd3v | yeti, $750.00 the 16 core arm miniitx.. excluding Ram memory |
| 05:28.02 | tuxd3v | I can blame you...I was looking and still thinking in going with this: |
| 05:29.07 | tuxd3v | https://www.powerpc-notebook.org/campaigns/donation-campaign-for-pcb-design-of-the-powerpc-notebook-motherboard/ |
| 05:29.18 | tuxd3v | it will be around 1500⬠|
| 05:29.36 | tuxd3v | but will be Cern Open Hardware based |
| 05:29.43 | tuxd3v | and open specs |
| 05:29.48 | tuxd3v | its a laptop |
| 05:30.26 | tuxd3v | <PROTECTED> |
| 05:30.28 | tuxd3v | :) |
| 05:31.40 | mrpfilser | sorry tuxd3v someone called me away |
| 05:32.17 | tuxd3v | <PROTECTED> |
| 05:32.37 | mrpfilser | sorry tuxd3v someone distracted me |
| 05:32.42 | mrpfilser | file vmlinuz-5.3.0-3-arm64 |
| 05:32.43 | mrpfilser | vmlinuz-5.3.0-3-arm64: MS-DOS executable |
| 05:32.59 | mrpfilser | that's from devuan repo iirc |
| 05:33.26 | mrpfilser | the others also say MS-DOS executeable |
| 05:33.57 | tuxd3v | you compiled that kernel ? |
| 05:34.07 | mrpfilser | i did not |
| 05:34.55 | mrpfilser | these .dtb files maybe they are needed for nvidia |
| 05:37.12 | tuxd3v | the dtb files are descriptions of the devicetree |
| 05:37.28 | tuxd3v | yes they are needed for botting the kernel |
| 05:37.36 | tuxd3v | and you need one by kernel |
| 05:37.38 | mrpfilser | why doesnt i have them for other kernels |
| 05:37.46 | mrpfilser | what can i get them with |
| 05:37.55 | tuxd3v | your vmlinuz-5.3.0-3-arm64, should also I beliebe provide one :) |
| 05:38.14 | mrpfilser | is it hidden in there? |
| 05:38.19 | mrpfilser | it has no .dtb files |
| 05:38.21 | tuxd3v | no |
| 05:38.39 | tuxd3v | if you compile the kernel yourself, you have the option to generate them |
| 05:38.55 | mrpfilser | ah this is helpful. in make menuconfig somewhere eys? |
| 05:39.02 | tuxd3v | when you get it from somewere they should be there in some format |
| 05:39.56 | mrpfilser | there are many dtbs in /usr/lib/linux-image-5.3.0-3-arm64 and /usr/lib/linux-image-4.19.0-6-arm64 |
| 05:40.12 | tuxd3v | you can do a: |
| 05:40.19 | mrpfilser | but none for tegra jetson at all |
| 05:40.22 | tuxd3v | 'zcat /proc/config.gz >> .config' |
| 05:40.34 | tuxd3v | and then copy that file to the linux kernel |
| 05:40.44 | tuxd3v | source code root directory |
| 05:40.52 | tuxd3v | then you need to compile it.. |
| 05:41.24 | mrpfilser | ty |
| 05:42.28 | tuxd3v | to compile it you need to follow some rules |
| 05:42.41 | tuxd3v | I believe that nvidea has them in the documentation |
| 05:42.42 | mrpfilser | but i need to change the config |
| 05:42.46 | mrpfilser | to add scsi cdrom support |
| 05:42.50 | tuxd3v | and it will build everything for you.. |
| 05:43.09 | tuxd3v | ok |
| 05:43.42 | mrpfilser | i edit config directly, menuconfig is a pita |
| 05:43.46 | tuxd3v | you can go with menuconfig |
| 05:44.01 | tuxd3v | then go to device drivers |
| 05:44.09 | tuxd3v | indeed its a pita |
| 05:44.11 | tuxd3v | :) |
| 05:44.49 | tuxd3v | and I don't recall now were exatcly that options are but they are in 'device drivers' for sure |
| 05:44.55 | mrpfilser | you think this missing .dtb is why boot did not give me other kernel as an option? |
| 05:45.00 | mrpfilser | i have it written down somewhere |
| 05:45.10 | tuxd3v | yes you can edit manually if you know ere they are ;) |
| 05:45.18 | tuxd3v | I do that very often.. |
| 05:46.22 | mrpfilser | thank you for the help tuxd3v |
| 05:46.45 | tuxd3v | mrpfilser, no problem, any time :) |
| 05:48.09 | mrpfilser | otherwise the extlinux.conf was sane? |
| 05:48.24 | tuxd3v | yes extlinux seems nice |
| 05:48.27 | tuxd3v | ;) |
| 05:48.31 | tuxd3v | good job! |
| 05:49.23 | mrpfilser | there is also some tweak needed to read seagate drives over usb-sata adapter |
| 05:49.31 | mrpfilser | because apparently their firmware is broken |
| 05:49.51 | tuxd3v | well yes :) |
| 05:50.03 | tuxd3v | seagate OpenSeaChest |
| 05:50.10 | tuxd3v | uses undernet |
| 05:50.13 | tuxd3v | scsi |
| 05:50.16 | tuxd3v | protocol |
| 05:50.32 | tuxd3v | and they don't pass on the usb-sata adapator |
| 05:50.39 | tuxd3v | Or at least some don't |
| 05:50.43 | mrpfilser | yea |
| 05:50.55 | mrpfilser | i read there's a boot option or module blacklist workaround |
| 06:02.06 | *** join/#devuan Inepu (~Mithrandi@host67-78-static.1-79-b.business.telecomitalia.it) |
| 06:47.35 | *** join/#devuan wildjames (~wildjames@145.87.225.116) |
| 06:56.25 | *** join/#devuan engidea (~damiano@ip-46-141-11-154.rev.wolnext.com) |
| 07:08.35 | *** join/#devuan retak (~ite@2a01:c23:7c6a:b100:f2de:f1ff:feb2:f9aa) |
| 07:10.59 | *** join/#devuan humma (gun@gateway/shell/blinkenshell.org/x-ouohnfkfonjstehv) |
| 07:12.05 | *** join/#devuan chomwitt (~chomwitt@2a02:587:dc46:500:d8a:4686:135b:5824) |
| 07:15.51 | *** join/#devuan KnoP_01 (~KnoP@b2b-78-94-129-218.unitymedia.biz) |
| 07:17.11 | *** join/#devuan hokeyp (~hokeyp@gateway/tor-sasl/hokeyp) |
| 07:32.00 | *** join/#devuan Joril (~joril@80.66.213.130) |
| 07:47.44 | *** join/#devuan Pali (~pali@Maemo/community/contributor/Pali) |
| 07:47.44 | *** join/#devuan hokeyp (~hokeyp@gateway/tor-sasl/hokeyp) |