Jump to content

Werner

Administrators
  • Posts

    5220
  • Joined

  • Last visited

Posts posted by Werner

  1. Best chances is getting yourself familiar with the build framework and try to port the necessary patch to 6.12.y

    What I'd do is probably using kernel-patch command along with ./compile.sh (like "./compile.sh BOARD=udoo BRANCH=current kernel-patch") and then manually adding the patch contents. Then copy over the newly created patch into patch/kernel/archive/imx6-6.12 and try to compile. If it works try booting and see if USB are back again.

    PR is welcome :)

     

    Did a look myself and it seems like it's not that simple. the dts looks good already. But the  drivers/usb/misc/onboard_usb_hub.c file is gone entirely. Therefore I guess CONFIG_USB_ONBOARD_HUB=y doesn't make sense in the kernel configuration either.

     

    Ahaa, there we go. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/usb/misc?h=v6.12.13&id=31e7f6c015d9eb35e77ae9868801c53ab0ff19ac

    So things need adaption to the new name

  2. 2 hours ago, bsammon said:

    Am I supposed to un-compress it before dd-ing?

    Yes. Tools like etcher or USBimager can decompress images on-the-fly. dd cannot do that.

     

    2 hours ago, bsammon said:

    Am I supposed to partition the SD-card and write the image to a partition, or write the image to the entire card?

    Latter since the image may already contain partitions, depending on board.

     

    2 hours ago, bsammon said:

    Does it matter what size the card is?  (I'm sure too-small is a problem, but I'm not sure where the threshold is.  In any case the relevant question for me is - is there such a thing as too large (other than hardware compatibility with my computer))

    Not really. If it is big enough to fit the image it is good enough. However microSD cards with bigger size are usually a lot faster as well. I personally use and can recommend sandisk extreme (the golden ones) with either 32G or 64G capacity.

    Too large is also possible since the SoCs may have a limit. So if your SD card is 2TB or something...try something a little smaller ;)

     

    1 hour ago, bsammon said:

    Does it matter what size the card is?  (I'm sure too-small is a problem, but I'm not sure where the threshold is.  In any case the relevant question for me is - is there such a thing as too large (other than hardware compatibility with my computer))


     

     

    it never occurred to me that I had to install any kind of dependency to use it. Strange.

    Maybe there is another option available: https://gitlab.com/bztsrc/usbimager

     

  3. Of course, dd works too. The major issue with using this though is the lack of verification. While rare either dd or the target device can cause issues which are not detected while writing but when trying to read from the written device.

    USBimager and others like etcher verify all written data  to make sure there is no issue.

    So if you run into weird hard to explain troubles, this could be a reason.

     

    arm64 download: https://gitlab.com/bztsrc/usbimager/-/blob/binaries/usbimager_1.0.10-aarch64-linux-x11.zip

  4. Wireguard is shipped by default with almost all Armbian images.  Simply do sudo modprobe wireguard

     

    All you need is wireguard-tools which can be installed with --no-install-recommends to avoid unnecessary bloat/dependencies.

  5. Ah. I guess nobody ported the overlays from old bsp over yet. Well also nobody was asking for them yet either lol

     

    Anyway this may work with "modern" bsp too:

     

    /dts-v1/;
    /plugin/;
    
    / {
    	fragment@0 {
    		target = <&spi3>;
    
    		__overlay__ {
    			status = "okay";
    
    			spidev@0 {
    				compatible = "rockchip,spidev";
    				status = "okay";
    				reg = <0>;
    				spi-max-frequency = <50000000>;
    			};
    		};
    	};
    };

     

  6. Hm vendor seem lacking all rk356x overlays except rk3566-roc-pc-sata2.dtbo. Need to check current.

    Edit: current and edge only have a few more but also none spi related for rk3566. Odd...

  7. Armbian is evolving rapidly, now supporting an ever-growing list of single-board computers (SBCs) - each with unique hardware, kernels, and configurations. As the variety of supported boards expands, so does the complexity of troubleshooting and providing effective user assistance. To keep up with this demand, we’re raising 5,000 EUR to hire part-time support agents who can help manage this increasing workload and ensure high-quality support for the community.

     

    Read more: https://forum.armbian.com/crowdfunding/project/16-help-armbian-grow-support-join-our-team/

  8. If you run from sdcard, put it into an existing system and make necessary adjustments.

    Easiest would be to use another arm64 based computer since you can simply chroot into your sdcard and use armbian-config to switch back to stable.

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines