istefanec Posted March 6, 2020 Posted March 6, 2020 Hello. I need kernel 4.15.0-88 on Orangepi PC. I used "apt-get install linux-generic" to install kernel 4.15.0-88. After reboot Orangepi does not boot. What is wrong? Board: Orangepi PC
Igor Posted March 6, 2020 Posted March 6, 2020 1 hour ago, istefanec said: I need kernel 4.15.0-88 on Orangepi PC. Why do you want to downgrade? 1 hour ago, istefanec said: I used "apt-get install linux-generic" to install kernel 4.15.0-88. After reboot Orangepi does not boot. "linux-generic" has nothing to do with Armbian - those are Debian or Ubuntu generic kernels and - especially this old - usually lack support for most of the hardware we support. Even kernel might have support, boot process is different ... failure is expected.
istefanec Posted March 6, 2020 Author Posted March 6, 2020 Can I compile image for Orangepi PC with KERNELTAG="v4.15.0" or something else? Thank you.
istefanec Posted March 6, 2020 Author Posted March 6, 2020 (edited) 3 hours ago, istefanec said: Can I compile image for Orangepi PC with KERNELTAG="v4.15.0" or something else? Thank you. That is the failure given over serial port: Spoiler U-Boot SPL 2019.10-armbian (Jan 05 2020 - 10:06:25 +0100) DRAM: 1024 MiB Trying to boot from MMC1 U-Boot 2019.10-armbian (Jan 05 2020 - 10:06:25 +0100) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi PC DRAM: 1 GiB MC: mmc@1c0f000: 0 Loading Environment from EXT4... ** File not found /boot/boot.env ** ** Unable to read "/boot/boot.env" from mmc0:1 ** rror: 32 bit/pixel mode, but BMP has 8 bit/pixel In: serial Out: vidconsole Err: vidconsole Net: phy interface0 eth0: ethernet@1c30000 230454 bytes read in 14 ms (15.7 MiB/s) starting USB... Bus usb@1c1a000: USB EHCI 1.00 Bus usb@1c1a400: USB OHCI 1.0 Bus usb@1c1b000: USB EHCI 1.00 Bus usb@1c1b400: USB OHCI 1.0 Bus usb@1c1c000: USB EHCI 1.00 Bus usb@1c1c400: USB OHCI 1.0 Bus usb@1c1d000: USB EHCI 1.00 Bus usb@1c1d400: USB OHCI 1.0 scanning bus usb@1c1a000 for devices... 1 USB Device(s) found scanning bus usb@1c1a400 for devices... 1 USB Device(s) found scanning bus usb@1c1b000 for devices... 1 USB Device(s) found scanning bus usb@1c1b400 for devices... 1 USB Device(s) found scanning bus usb@1c1c000 for devices... 1 USB Device(s) found scanning bus usb@1c1c400 for devices... ERROR: USB-error: DATAOVERRUN: The amount of data returned by the endpoint exceeded either the size of the maximum data packet allowed from the endpoint (found in MaximumPacketSize field of ED) or the remaining buffer size. (8) ERROR: USB-error: DATAOVERRUN: The amount of data returned by the endpoint exceeded either the size of the maximum data packet allowed from the endpoint (found in MaximumPacketSize field of ED) or the remaining buffer size. (8) ERROR: USB-error: DATAOVERRUN: The amount of data returned by the endpoint exceeded either the size of the maximum data packet allowed from the endpoint (found in MaximumPacketSize field of ED) or the remaining buffer size. (8) ERROR: USB-error: DATAOVERRUN: The amount of data returned by the endpoint exceeded either the size of the maximum data packet allowed from the endpoint (found in MaximumPacketSize field of ED) or the remaining buffer size. (8) ERROR: USB-error: DATAOVERRUN: The amount of data returned by the endpoint exceeded either the size of the maximum data packet allowed from the endpoint (found in MaximumPacketSize field of ED) or the remaining buffer size. (8) ERROR: USB-error: DATAOVERRUN: The amount of data returned by the endpoint exceeded either the size of the maximum data packet allowed from the endpoint (found in MaximumPacketSize field of ED) or the remaining buffer size. (8) 2 USB Device(s) found scanning bus usb@1c1d000 for devices... USB Device(s) found scanning bus usb@1c1d400 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3789 bytes read in 3 ms (1.2 MiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 201 bytes read in 3 ms (65.4 KiB/s) 4865286 bytes read in 1657 ms (20.1 MiB/s) 7741936 bytes read in 370 ms (20 MiB/s) Found mainline kernel configuration 28507 bytes read in 8 ms (3.4 MiB/s) 4155 bytes read in 8 ms (506.8 KiB/s) Applying kernel provided DT fixup script (sun8i-h3-fixup.scr) ## Executing script at 44000000 ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 34865222 Bytes = 33.3 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... ad Data CRC Ramdisk image is corrupt or invalid SCRIPT FAILED: continuing... Device 0: unknown device ethernet@1c30000 Waiting for PHY auto negotiation to complete. done BOOTP broadcast 1 BOOTP broadcast 2 OOTP broadcast 3 HCP client bound to address 172.16.2.197 (1354 ms) *** ERROR: `serverip' not set Cannot autoload with TFTPGET missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/01-02-81-10-d2-35-f9 *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/AC1002C5 *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/AC1002C *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/AC1002 *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/AC100 *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/AC10 *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/AC1 *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/AC *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/A *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-sunxi-sunxi *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-sunxi *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/default *** ERROR: `serverip' not set Config file not found BOOTP broadcast 1 DHCP client bound to address 172.16.2.197 (22 ms) *** ERROR: `serverip' not set Cannot autoload with TFTPGET BOOTP broadcast 1 DHCP client bound to address 172.16.2.197 (22 ms) *** ERROR: `serverip' not set Cannot autoload with TFTPGET => -Boot SPL 2019.10-armbian (Jan 05 2020 - 10:06:25 +0100) Unknown command 'U-Boot' - try 'help' => DRAM: 1024 MiB Unknown command 'DRAM:' - try 'help' => Trying to boot from MMC1 Unknown command 'Trying' - try 'help' => Unknown command 'Trying' - try 'help' => Unknown command 'Trying' - try 'help' => U-Boot 2019.10-armbian (Jan 05 2020 - 10:06:25 +0100) Allwinner Technology Unknown command 'U-Boot' - try 'help' => Unknown command 'U-Boot' - try 'help' => CPU: Allwinner H3 (SUN8I 1680) Unknown command 'CPU:' - try 'help' => Model: Xunlong Orange Pi PCDRAMMC: mmc@1c0f000: 0 Unknown command 'Model:' - try 'help' => Loading Environment from EXT4... ** File not found /boot/e* Unknown command 'Loading' - try 'help' => ** Unable to read "/boot/boot.env" from mmc0:1 ** Unknown command '**' - try 'help' => rror: 32 bit/pixel mode, but BMP has 8 bit/pixel Unknown command 'rror:' - try 'help' => In: serial Unknown command 'In:' - try 'help' => Out: vidconsole Unknown command 'Out:' - try 'help' => Err: vidconsole Unknown command 'Err:' - try 'help' => Net: phy interface0 Unknown command 'Net:' - try 'help' => eth0: ethernet@1c30000 Unknown command 'eth0:' - try 'help' => 230454 bytes read in 14 ms (15.7 MiB/s) Unknown command '230454' - try 'help' => starting USB... Unknown command 'starting' - try 'help' => Bus usb@1c1a000: USB EHCI 1.00 Unknown command 'Bus' - try 'help' => Bus usb@1c1a400: USB OHCI 1.0 Unknown command 'Bus' - try 'help' => Bus usb@1c1b000: USB EHCI 1.00 Unknown command 'Bus' - try 'help' => Bus usb@1c1b400: USB OHCI 1.0 Unknown command 'Bus' - try 'help' => Bus usb@1c1c000: USB EHCI 1.00 Unknown command 'Bus' - try 'help' => Bus usb@1c1c400: USB OHCI 1.0 Unknown command 'Bus' - try 'help' => Bus usb@1c1d000: USB EHCI 1.00 Unknown command 'Bus' - try 'help' => Bus usb@1c1d400: USB OHCI 1.0 Unknown command 'Bus' - try 'help' => scanning bus usb@1c1a000 for di.Svscanning bus usb@1c1b000 foressnbbcfe.R -rARTm ttdtnte Unknown command 'scanning' - try 'help' => e hx ptoftdtunmciio hmnfi(R r OUhufau ep ee soemaa wfrom th o(dtx eofrom the ed n mczeof E hagfi(RUr VNeuf rbepedi if macaefrtnnoniaSfof ED) or hagfi8ERROR: USB-oAE:atdre eixdhhz amakl nknown command 'e' - try 'help' => eioixPtf Unknown command 'eioixPtf' - try 'help' => D riu .ERROR: USB-r OUeufaubep deither tso maa eoep dMc0de ef Unknown command 'D' - try 'help' => s co Unknown command 's' - try 'help' => sittn,mmc0 is current eScanning mmc 0:1... Unknown command 'sittn,mmc0' - try 'help' => Fo orbbs378b 1Boot 7741936 bytri 2BFound mainlinecgi28507 byte##Etst40## Loading ini sogI 30 Unknown command 'Fo' - try 'help' Edited March 6, 2020 by Igor spoilers
Igor Posted March 6, 2020 Posted March 6, 2020 28 minutes ago, istefanec said: That is the failure given over serial port: Support we are paying for your amusement is limited to Armbian official builds: https://docs.armbian.com/User-Guide_Getting-Started/#how-to-check-download-authenticity under those conditions: https://github.com/armbian/build#support 40 minutes ago, istefanec said: Can I compile image for Orangepi PC with KERNELTAG="v4.15.0" or something else? After you adjust patches, yes. But this is 100% your job. Its a lot of work and perhaps mission impossible - depending of your skills. We only support build engine, not what you will give into it. When you go outside of supported versions, 4.19.y and 5.4.y, adjustment costs will go up and nobody will be assisting you. I hope you understand this is not our fault.
istefanec Posted March 6, 2020 Author Posted March 6, 2020 Hello. I did find solution for my problem. It was how to use Hauppauge Wintv DualHd USB Tv card on Orangepi PC with Tvheadend app. I had problem with receiving DVB-T2 programs with Tvheadend. On virtual Ubuntu 18.04 was good. Now it works on Orangepi PC. At the end I used: Armbian_5.90_Orangepipc_Ubuntu_bionic_next_4.19.57.img, upgraded kernel to 5.4.20-sunxi, add TV card firmware "dvb-demod-si2168-b40-01.fw", at the end Tvheadend install. Tvheadend works better on Orangepi PC then on virtual Ubuntu. My first approach was wrong. Thank you again.
Igor Posted March 6, 2020 Posted March 6, 2020 47 minutes ago, istefanec said: I did find solution for my problem. I am glad you did. Many people use those devices for TVheadend servers which is why our kernel support is good out of the box. (I also used it for many years) Going on the other route you might end up hating Linux altogether
istefanec Posted March 8, 2020 Author Posted March 8, 2020 Tell me please if you know what is to best way to share successes for something does work. In my case tvheadend on Orangepi PC with hauppauge dvb-t2 card. That is my case: "For Orangepi PC working installation you need: Armbian_5.90_Orangepipc_Ubuntu_bionic_next_4.19.57.img Set static IP address (optional). apt-get update && apt-get upgrade With armbian-config switch to other kernel select 5.4.20-sunxi. In /lib/firmware add "dvb-demod-si2168-b40-01.fw" firmware. Install Tvheadend. I use: sudo apt-add-repository ppa:mamarley/tvheadend-git-stable sudo apt-get update sudo apt install tvheadend Good luck." At the end I did use a lot of community knowledge and I want to share my successes with others. Best regards, Ivica.
Werner Posted March 9, 2020 Posted March 9, 2020 Just for the heck of it, want to try this with a fresh current image? Most users will download current anyways and this makes the extra step of switching kernels obsolete.
Recommended Posts