no frontend0 available when started directly
Bug #1545613 reported by
Bert Scholz
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Me TV |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
Starting me-tv directly (with channels already configured), no channel works but a message like "no frontend0 is available".
Starting to scan the channels again (does not need to do a complete run, but only "initialising"), me-tv works fine.
Seems 'w_scan -F c -c DE' invokes some settings so that me-tv works, but until now i could not figure out which one, maybe me-tv does not detect the cable-signal out-of-the-box.
Revision history for this message
| Frédéric Côté (frederic-cote) wrote | #1 |
| Changed in me-tv: | |
| status: | New → Incomplete |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in me-tv: | |
| status: | Incomplete → Expired |
To post a comment you must log in.
Hi,
Make sure no other software (even other me-tv instance) is locking the device. When you start w_scan it probably unlock it from the other software using it. You can also check the version of me-tv. Version 1.3 and 1.4 are very different. Maybe one of them will work better with your setup.
Also maybe your device is not up all the time and something need to be done to initialise it. w_scan is probably doing the necessary step but not me-tv.
Note that me-tv was developed for DVB-T/ATSC. There was not many test done for cable.
Cheers,
Fred