bootloader config / EEPROM:
PSU_MAX_CURRENT=5000
Posts by elliottmc
-
-
To follow this up, two weeks and no issues at all now. So that clearly was the issue.
-
You are welcome. By the way, for the fan control of that case you can install this Addon: RE: [RPi4B] Argon One Case Shutdown
But please do place the lock file there before the Addon installation, to ensure that your current remote control configuration is not affected:
touch /storage/.config/argon40_rc.lockI'm going to have a look at this, but I'll leave it a week or so.
So far, it's looking good now. TV recording all seems fine!
Thanks once again for your help. Hopefully this thread will be useful to others.
-
Well, every day is a school day!
So, I've made the changes, plugged the tuners back in, rebooted and configured TVH. So far, it's looking good. I'll reserve proper judgment until I've recorded a few shows.
Thanks so much for your help!
-
Thanks so much!!!
So, I've pulled the microSD card out, put it in a PC and added
usb_max_current_enable=1
to config.txt.
Does it matter where I put it? I don't want to mess up again!
Rookie question - how do I change the bootloader config? I don't see a file there to edit!
-
Please keep in mind, that the RPi5 itself needs more power, than previous generations. If the system is very CPU agile and not in the idle state, then attaching of USB devices could be the worst case for the power supply and/or the PMIC.
If your USB HUB is really a powered one, you should try to only attach 1 tuner to the RPI5 directly and 2 tuners at the powered HUB.
Only to be sure, you attached the RPi5 power supply directly to the RPi5 pcb, right? You doesn't use a additional case or gadget like RemotePi board ?
I'm using the ArgonOne case, so yes there is an additional gadget! Maybe the power isn't getting through.
The reason I discounted the USB power was because I did use a powered hub with all three, and then two, of the tuners attached.
Now I'm questioning whether it really is delivering the power.
-
This doesn't looking good regarding the USB power. Was this an attempt with the powered HUB?
Code[ 323.045985] usb usb1-port1: over-current change #1 [ 323.046043] usb usb3-port1: over-current change #1 [ 323.075888] usb usb4-port1: over-current change #1 [ 323.075928] usb usb2-port1: over-current change #1Good spot. No it was not.
Does it make sense for this to only happen when TVHeadEnd is running? The tuner wasn't actually doing anything (as far as I know).
I will wait to see if anyone else spots anything, and do follow-up testing if needed.
Very odd that a RPi5 performs worse in this respect, even with a higher-rated power supply.
-
Hope it's okay to add this as attachments.
So I don't have TVHeadEnd running on the RPi5 (I disabled it to switch back to the RPi4 as my TV server and the RPi5 as client).
And then I don't get all the text over the boot screen.
Obviously the next test is to enable TVH and see what changes, if anything.
Thanks for your help.
And as soon as I start TVHeadEnd, it goes to hell. dmesg attached.
Even I can see there is something not right here!
-
Hi Chewitt,
Thanks for the comments.
So, the short version is I tried pretty much every permutation I could think of.
I've been using a RPi4 with the three tuners for some years now, and it's rock stable.
With two tuners connected, no matter how, the RPi5 works fine. As soon as I connect the third tuner, it all goes pear shaped. That is with all three tuners on the Pi, all three tuners on the powered hub, and everything in between.
Looking at the logs, it seems that as soon as the third tuner is connected, it goes through a cycle of disconnecting the other ones.
Best wishes,
Mark
-
Right, I've had a bit more time to look into this. I also updated to LE 12.0 final, as I figured it wouldn't hurt!
So, with a powered USB hub, I seem to have the same problems with three tuners. Fine with two, but I have trouble connecting over the network with three plugged in. It doesn't seem to hang in the same way, but it's not good.
So I guess I try to debug this with the tuners plugged in directly, so avoid complications?
Would someone be able to advise me on what information is likely to be needed?
Right, this may help. I know that partial logs are not always useful, but this is with two tuners.
2024-05-05 13:25:15.711 [ NOTICE] START: HTS Tvheadend version 4.3-2180 ~ LibreELEC Tvh-addon v12.0.0.0 started, running as PID:399 UID:0 GID:39, CWD:/ CNF:/storage/.kodi/userdata/addon_data/service.tvheadend43
2024-05-05 13:25:16.188 [ INFO] linuxdvb: adapter added /dev/dvb/adapter1
2024-05-05 13:25:16.505 [ INFO] avahi: Service 'Tvheadend' successfully established.
2024-05-05 13:25:16.654 [ INFO] scanfile: DVB-S - loaded 1 regions with 222 networks
2024-05-05 13:25:16.654 [ INFO] scanfile: DVB-T - loaded 44 regions with 1081 networks
2024-05-05 13:25:16.654 [ INFO] scanfile: DVB-C - loaded 18 regions with 62 networks
2024-05-05 13:25:16.654 [ INFO] scanfile: ATSC-T - loaded 2 regions with 13 networks
2024-05-05 13:25:16.654 [ INFO] scanfile: ATSC-C - loaded 2 regions with 6 networks
2024-05-05 13:25:16.655 [ INFO] scanfile: ISDB-T - loaded 2 regions with 2540 networks
2024-05-05 13:25:30.936 [ INFO] mpegts: 634.167MHz in DVB-T Network - tuning on Panasonic MN88472 #0 : DVB-T #0
2024-05-05 13:25:30.937 [ INFO] subscription: 0001: "epggrab" subscribing to mux "634.167MHz", weight: 4, adapter: "Panasonic MN88472 #0 : DVB-T #0", network: "DVB-T Network", service: "Raw PID Subscription"
2024-05-05 13:25:30.937 [ INFO] mpegts: 642.167MHz in DVB-T Network - tuning on Panasonic MN88472 #1 : DVB-T #0
2024-05-05 13:25:30.937 [ INFO] subscription: 0002: "epggrab" subscribing to mux "642.167MHz", weight: 4, adapter: "Panasonic MN88472 #1 : DVB-T #0", network: "DVB-T Network", service: "Raw PID Subscription"And the following is with a shutdown, plug in the third tuner and then boot. At boot, I get a lot of fast scrolling text on the screen before the Kodi start screen, which isn't normal!
2024-02-27 17:26:06.653 [ NOTICE] START: HTS Tvheadend version 4.3-2180 ~ LibreELEC Tvh-addon v12.0.0.0 started, running as PID:399 UID:0 GID:39, CWD:/ CNF:/storage/.kodi/userdata/addon_data/service.tvheadend43
2024-02-27 17:26:06.995 [ INFO] linuxdvb: adapter added /dev/dvb/adapter1
2024-02-27 17:26:07.505 [ INFO] avahi: Service 'Tvheadend' successfully established.
2024-02-27 17:26:07.711 [ INFO] linuxdvb: adapter added /dev/dvb/adapter2
2024-02-27 17:26:08.046 [ INFO] linuxdvb: adapter removed /dev/dvb/adapter1
2024-02-27 17:26:08.113 [ INFO] scanfile: DVB-S - loaded 1 regions with 222 networks
2024-02-27 17:26:08.113 [ INFO] scanfile: DVB-T - loaded 44 regions with 1081 networks
2024-02-27 17:26:08.113 [ INFO] scanfile: DVB-C - loaded 18 regions with 62 networks
2024-02-27 17:26:08.113 [ INFO] scanfile: ATSC-T - loaded 2 regions with 13 networks
2024-02-27 17:26:08.113 [ INFO] scanfile: ATSC-C - loaded 2 regions with 6 networks
2024-02-27 17:26:08.113 [ INFO] scanfile: ISDB-T - loaded 2 regions with 2540 networks
2024-02-27 17:26:08.331 [ INFO] linuxdvb: adapter removed /dev/dvb/adapter0
2024-02-27 17:26:09.654 [ INFO] linuxdvb: adapter added /dev/dvb/adapter0
2024-02-27 17:26:09.927 [ INFO] linuxdvb: adapter added /dev/dvb/adapter1
2024-02-27 17:26:09.927 [ INFO] linuxdvb: adapter removed /dev/dvb/adapter2
2024-02-27 17:26:11.147 [ INFO] linuxdvb: adapter added /dev/dvb/adapter2
2024-02-27 17:26:11.933 [ INFO] linuxdvb: adapter removed /dev/dvb/adapter1
2024-02-27 17:26:11.944 [ INFO] linuxdvb: adapter removed /dev/dvb/adapter0
2024-02-27 17:26:13.634 [ INFO] linuxdvb: adapter added /dev/dvb/adapter0
2024-02-27 17:26:13.810 [ INFO] linuxdvb: adapter added /dev/dvb/adapter1
2024-02-27 17:26:13.813 [ INFO] linuxdvb: adapter removed /dev/dvb/adapter2
2024-05-05 13:32:22.538 [ INFO] epgdb: snapshot start
2024-05-05 13:32:22.601 [ INFO] epgdb: queued to save (size 8247916)
2024-05-05 13:32:22.601 [ INFO] epgdb: broadcasts 21973
2024-05-05 13:32:22.601 [ INFO] epgdb: save start
2024-05-05 13:32:22.745 [ INFO] epgdb: stored (size 1847841)
2024-05-05 13:32:22.940 [ INFO] linuxdvb: adapter added /dev/dvb/adapter2
2024-05-05 13:32:23.414 [ INFO] linuxdvb: adapter removed /dev/dvb/adapter1
2024-05-05 13:32:23.555 [ INFO] mpegts: 634.167MHz in DVB-T Network - tuning on Panasonic MN88472 #0 : DVB-T #0That's the last line in the log, and I cannot connect to TVHeadEnd via the web interface. I just get a spinning wheel in my web browser.
Best wishes,
Mark
-
TVH seems to hang straight away. I'll try again later and get logs.
-
Update with more testing after resolving my network issues and updating to the latest nightly build.
If I have three tuners connected, I can ssh in and lsusb shows them all fine. But for some weird reason I cannot connect through the web interface to TVHeadEnd.
If I remove one tuner, it all works fine. As soon as I plug the third tuner in, I don't get a response from TVHeadEnd.
But the stability issues seem to be resolved. LibreElec doesn't seem to be crashing now.
-
Right, as a follow-up, it seems that this may have been related to ipv6. Or potential issues with my network and ipv6 at least.
I was finding that the RPi5 was having a network connection, but my router showed it having a private IP address. I've now turned off ipv6, so it uses ipv4, and also manually set the IP address on the Pi. Hopefully that will be stable.
-
Your note that the FLIRC USB is not working makes this seem like a USB issue not related to PVR. Did you try USB devices individually in each port and see what lsusb shows.
The FLIRC works fine until the third TV tuner is plugged in.
Unfortunately at that point, the Pi doesn't get an IP address, so I cannot connect to it via ssh.
I've been plugging the tuners in first to the USB3 ports, and then only to the USB2. I wonder if it is a problem with the tuner and the USB2 port of the Pi, rather than simply the third tuner.
Thanks for the suggestion. I will have a look and report back.
Best wishes,
Mark
-
It's not the answer you are wanting, I know, but with that amount of storage and such a large database, you will probably get a much better experience if you use a NAS for storage rather than locally attached drives (easier to maintain) and run MySQL on the NAS to have a shared database.
-
Power source issue? If you could connect those tuners thru (external) powered usb hub...
The RPi5 has the official 27W (5A) power supply, so I don't think this is very likely. The RPi4 has a 3A power supply and has been working for years.
I did try connecting the tuners to a hub, but not a powered one. I'm reluctant to spend more money on one in order to test this, although I may be able to put my hands on one.
-
As a follow-up, I've reconnected the same three tuners to the RPi4, and reinstalled, and they are working fine as before.
So there's definitely something going on with the RPi5 and/or LE12 in this configuration.
Best wishes,
Mark
-
Hi all,
I've been running a RPi4 with three XBox TV tuners for quite a few years. Ive upgraded to a Pi5 and when I plug in two tuners it seems reasonably okay. As soon as I plug the third tuner in, it doesn't boot properly, doesn't connect to the network, etc. It doesn't better whether I plug the third tuner into the USB socket on the Pi, or if I plug all three into a UBS3 hub (so all on a USB3 socket).
Has anyone else had a similar problem? I'm starting to think I will need to run one system (RPi4) as the TV server, and the RPi5 as the client!
To give a bit more information about the problem, I have just enabled debug logging, and rebooted after plugging in the third tuner. I'm running LE21 RC (latest nightly build) although the stable build doesn't do better. The remote control (flirc adapter) now doesn't work, and it isn't connected to the network (it shows in my modem settings as connected but "This device either does not support or is not configured for IPv4 addressing."), so I'm going to have trouble getting the log files.
This may help, although I don't understand the timeline. This was a freshly installed system this morning, so Feb 27 logging may indicate problems with the date and time.
https://paste.libreelec.tv/normal-raven.log
Best wishes,
Mark
