My StreamSat TV SetUp

My StreamSat Tv Setup

Thanks to the following people / Co. for this Setup:

1.  LataSat / StreamSat tv  for the Signal they provide

2.  My Brother Louie for providing  Original Dream Satellite Dish

3. Bro. Onahd for the Satellite PCI Card Technisat Skystar S2 

4, Boyet05, Jerome and Wolf for their support and giving inspiration.

5.  Urezmus, Haim, Olinor,Kim and to all Satellite Hobbies Guru.

My SetUp Dish

Align mY Dish Pointing to Tagaytay AP
   ....too bad cannot get or shoot Rizal AP...

Here is the Signal using ProgFinder software:

Here is the Scan Result   41 TV Channels and 8 Radio Channels

Way of Shooting:

Since I dont have any small receiver and small TV for Sat. Dish Adjustment.. The only option that i have is the PCI Satellite card and Desktop Win XP machine.. I just extend the Cable of my Head Phone  to the roof of my house and listen to the voice of the Signal Finder quality... (I will try to make a photo of my self wearing headphone at the roof. later..)

Here are some of the  FTA Channels using Prog DVB software:

Too Bad they don't have ABS-CBN Channels

Raspberry Pi + XBMC + DVBWord Receiver + StreamTV Signal = Happy

1.  Prepare all the equipment Needed for this project..

• RPi Model B
• DVBWorld  - DVB-S2 USB BOX
• iPad charger as PSU (2A @ 5V DC) with a micro USB cable.
• Windows Media Centre Remote Control and Keyboard
• 8GB Sandisk Class10 SDHC
• Using HDMI output into TV

2,The firmware for that device can be found here..http://www.satelliteguys.us/.../156980-DVB-World-HD-2104..

Generating locales (this might take a while)...
en_US.UTF-8... done
Generation complete.
Package configuration
Current default time zone: 'Asia/Taipei'
Local time is now: Tue Feb 4 14:52:15 CST 2014.
Universal Time is now: Tue Feb 4 06:52:15 UTC 2014.
All set up now! Thanks for using Raspbmc.
And may I kindly advise you to read the Wiki if you have issues
Note, you still need to configure your locales in XBMC
pi@raspbmc:~$ dmesg
dvb-usb: found a 'DVBWorld DW2104 USB2.0' in cold state, will try to load a firmware
dvb-usb: did not find the firmware file. (dvb-usb-dw2104.fw) Please see linux/Documentation/dvb/ for more details on firmware-problems. (-2)

After copying the firmware
#######################

dvb-usb: downloading firmware from file 'dvb-usb-dw2104.fw'
dw2102: start downloading DW210X firmware
dvb-usb: found a 'DVBWorld DW2104 USB2.0' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (DVBWorld DW2104 USB2.0)
dvb-usb: MAC address: 00:18:bd:5d:bf:78
dw2102: Attached cx24116!

DVB: registering adapter 0 frontend 0 (Conexant CX24116/CX24118)...
input: IR-receiver inside an USB DVB receiver as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/input/input2
dvb-usb: schedule remote query interval to 150 msecs.
dvb-usb: DVBWorld DW2104 USB2.0 successfully initialized and connected.

###########################

uname -a
Linux raspbmc 3.6.11 #2 PREEMPT Wed Aug 21 03:19:24 UTC 2013 armv6l GNU/Linux
pi@raspbmc:/etc$ dmesg | grep -a DVB
dvb-usb: found a 'DVBWorld DW2104 USB2.0' in cold state, will try to load a firmware
dvb-usb: found a 'DVBWorld DW2104 USB2.0' in warm state.
DVB: registering new adapter (DVBWorld DW2104 USB2.0)
dvb-usb: no frontend was attached by 'DVBWorld DW2104 USB2.0'
input: IR-receiver inside an USB DVB receiver as /devices/platform/bcm2708_usb/usb1/1-1/1-1.2/input/input1
dvb-usb: DVBWorld DW2104 USB2.0 successfully initialized and connected.
dvb-usb: DVBWorld DW2104 USB2.0 successfully deinitialized and disconnected.
dvb-usb: found a 'DVBWorld DW2104 USB2.0' in cold state, will try to load a firmware
dvb-usb: found a 'DVBWorld DW2104 USB2.0' in warm state.
DVB: registering new adapter (DVBWorld DW2104 USB2.0)
DVB: registering adapter 0 frontend 0 (Conexant CX24116/CX24118)...
input: IR-receiver inside an USB DVB receiver as /devices/platform/bcm2708_usb/usb1/1-1/1-1.2/input/input2

dvb-usb: DVBWorld DW2104 USB2.0 successfully initialized and connected.

################################

pi@raspbmc:/etc$ tvheadend -C

Feb 12 13:17:43.102 [WARNING]:access: Created default wide open access controle entry

Feb 12 13:17:46.431 [   INFO]:charset: 71 entries loaded

Feb 12 13:17:46.440 [   INFO]:dvb: Found adapter /dev/dvb/adapter0 (Conexant CX24116/CX24118) via USB (480 Mbit/s)

Feb 12 13:17:46.474 [   INFO]:CSA: Using 32bit parallel descrambling

Feb 12 13:17:46.480 [   INFO]:epggrab: module eit created

Feb 12 13:17:46.482 [   INFO]:epggrab: module uk_freesat created

Feb 12 13:17:46.487 [   INFO]:epggrab: module uk_freeview created

Feb 12 13:17:46.489 [   INFO]:epggrab: module viasat_baltic created

Feb 12 13:17:46.600 [   INFO]:epggrab: module opentv-ausat created

Feb 12 13:17:46.607 [   INFO]:epggrab: module opentv-skyit created

Feb 12 13:17:46.610 [   INFO]:epggrab: module opentv-skyuk created

Feb 12 13:17:46.635 [   INFO]:epggrab: module pyepg created

Feb 12 13:17:46.638 [   INFO]:epggrab: module xmltv created

Feb 12 13:17:46.661 [   INFO]:dvr: Creating new configuration ''

Feb 12 13:17:46.680 [WARNING]:dvr: Output directory for video recording is not yet configured for DVR configuration "". Defaulting to to "/home/pi". This can be changed from the web user interface.

Feb 12 13:17:46.691 [ NOTICE]:START: HTS Tvheadend version 3.4-dirty started, running as PID:4062 UID:1000 GID:1000, settings located in '/home/pi/.hts/tvheadend'

Feb 12 13:17:47.771 [   INFO]:AVAHI: Service 'Tvheadend' successfully established.

All config of Tvheadend is done through a web interface. You will need to connect to it with a web browser. On a default install of Raspbmc you can type http://raspbmc:9981 in the address bar of a computer on the same network, otherwise you will need to know the IP address of the Pi and can enter http://<IP of Pi>:9981 when it asks for a username and password just click ok. 

2.5. http://172.29.45.2:9981/extjs.html

Feb 12 13:56:53.010 [ NOTICE]:dvb: New mux "3,660,000 kHz Vertical (Default (Port 0, Universal LNB))" created by built-in configuration from "dvb-s_AsiaSat2_C_100_5E"

How to Update Transponder list in TVheadend?

The DVB locations are currently "hardcoded" into the compiled binary of tvheadend. So updating your initial tuning files will not "automagically" make them appear in tvheadend. With each official release these lists are updated with an script to convert the initial tuning files to a "source file" that is part of the tvheadend source code.

There are bugs/feature request already filed that are aiming to change this hardcoded data to something like what you were already expecting.

But you can manually add at least one transponder you need, and then tvheadend will find all the related transponders if this information is correctly broad-casted. If not all the transponders that you need are found, you can continue manually adding them until you have all that are needed. Currently it is not advised to have a large numbers of transponders listed because that might negatively impact the performance of the GUI (not of tvheadend it self)

An other more complicated method is making your own binary with the details included in that binary by updating the correct files in the thveadend source code (manually of via the conversion script)

tvheadend -f

14. Once in the TV Headend Control panel do this:

• Go to configuration→ General
• Enter en for the default language
• Enter /usr/share/dvb into the ‘DVB Scan Files path.
• Go to configuration -> TV Adapters and select a TV Adapter.
• Set the "NIT-o Network ID". Apparently, you can find that in your provider's manual. I took a guess and for my TinyUSB2 I used ‘0’.
• Ensure "Autodetect muxes" and "Idle scanning" are ticked.
• Then select "Add DVB Network by location" – this will add Muxes from a known database
• Click "save"
• Tvheadend will now start to detect multiplexes and services. Wait for "Muxes awaiting initial scan" to become 0.
• Now click "Map DVB Services to channels". TVheadend will now try to open each channel and will add each channel that can be opened.
• Repeat this process for other adapters if you have them.

15. In XBMC, go to Settings → Live TV → General → Enable it
16. Choose ‘Tvheadend HTSP Client’ as the server and enable it. Allow the channels to be detected by XBMC and then try watching TV.

3.  http://www.robclarkey.com/technology/2012/06/05/installing-tbs6981-dvb-s2-dual-tuner-on-ubuntu-11-04/

Obtaining the Szap-s2 packages

 http://www.robclarkey.com/technology/2012/06/05/installing-tbs6981-dvb-s2-dual-tuner-on-ubuntu-11-04/

pi@raspbmc:~$ mkdir dvbworld

pi@raspbmc:~$ cd dvbworld/

sudo wget https://pikacode.com/mercurial.intuxication.org/szap-s2.tar.gz --no-check-certificate -O szap-s2.tar.gz
sudo tar xjvf szap-s2.tar.gz

sudo wget http://pikacode.com/mercurial.intuxication.org/scan-s2.tar.gz --no-check-certificate -O scan-s2.tar.gz

sudo tar -xzf scan-s2.tar.gz


HTTP request sent, awaiting response... 200 OK
Length: 53903 (53K) [application/octet-stream]
Saving to: `szap-s2.tar.gz'

100%[============================>] 53,903      40.7K/s   in 1.3s  

2014-02-07 16:07:14 (40.7 KB/s) - `szap-s2.tar.gz' saved [53903/53903]

pi@raspbmc:~$ sudo tar -xzf szap-s2.tar.gz

szap-s2 -- simple zapping tool for the Linux DVB S2 API


szap-s2 requires Linux DVB driver API version 5.0.

If compiler not found DVB headers in ../s2/linux/include/linux/dvb,
then it looks at usual location /usr/include/linux/dvb.

Install as follows:

(Option)  make
          make install
Uninstall
          make uninstall

location of channel list file is ~/.szap/channels.conf

one line of the szap channel file has the following format:
name:frequency_MHz:polarization[coderate][delivery][modulation][rolloff]:sat_no:symbolrate:vpid:apid:service_id
one line of the VDR channel file has the following format:
name:frequency_MHz:polarization[coderate][delivery][modulation][rolloff]:sat_no:symbolrate:vpid:apid:?:?:service_id:?:?:?

usage:
szap -q
         list known channels
szap [options] {-n channel-number|channel_name}
         zap to channel via number or full name (case insensitive)
     -a number : use given adapter (default 0)
     -f number : use given frontend (default 0)
     -d number : use given demux (default 0)
     -c file   : read channels list from 'file'
     -V        : use vdr channels list file format (default zap)
     -b        : enable Audio Bypass (default no)
     -x        : exit after tuning
     -H        : human readable output
     -D        : params debug
     -r        : set up /dev/dvb/adapterX/dvr0 for TS recording
     -l lnb-type (DVB-S Only) (use -l help to print types) or
     -l low[,high[,switch]] in Mhz
     -i        : run interactively, allowing you to type in channel names
     -p        : add pat and pmt to TS recording (implies -r)
                 or -n numbers for zapping
     -S        : delivery system type DVB-S=0, DVB-S2=1
     -M        : modulation 1=BPSK 2=QPSK 5=8PSK
     -C        : fec 0=NONE 12=1/2 23=2/3 34=3/4 35=3/5 45=4/5 56=5/6 67=6/7 89=8/9 910=9/10 999=AUTO
     -O        : rolloff 35=0.35 25=0.25 20=0.20 0=UNKNOWN

http://www.linuxtv.org/wiki/index.php/Scan


http://www.linuxtv.org/wiki/index.php/Szap
http://www.linuxtv.org/wiki/index.php/Scan-s2

4, Scan for the channels you can receive 

mkdir ~/.{a,c,s,t}szap
(dvb)scan /path_to_the_initial_scan_file > ~/.{a,c,s,t}szap/channels.conf

5... Tune a frequency and program

 $ /usr/bin/{a,c,s,t}szap -r -c ~/.{a,c,s,t}szap/channels.conf "channel name"

6.  After you've tuned a frequency and program

a) You could now start up your simple TV watching application and decode the stream you have tuned.

For example, while keeping {a,c,s,t}zap running in the first console shell, open up another console and run

mplayer /dev/dvb/adapter0/dvr0 <options>

TO Be Continued.......... tawag ng Boss meeting daw....

Playing Internet Streams in XBMC and OpenElec

1 Playing Internet Streams in XBMC

There are two ways this can be done, either via a custom .STRM file or a standard playlists (.PLS or .M3U).

1.1 The .STRM file method:

Create a normal text-file and rename the .txt extension to .strm then open it up with a text-editor (like Notepad in Microsoft Windows) and input the the direct URL-link of the stream.

This should look like:

http://host/path/stream

or

mms://host/path/stream

or

rtsp://host/path/stream

Other protocols are supported such as http://host/path/to/somefile.mp3. Then save/copy the .strm file to somewhere where you can open it from XBMC, (like on a SMB/SAMBA, XBMS or UPnP share, or just your local hard drive), like you would with any video/audio file. Open it using play in XBMC under My Videos (if it is a video stream) or My Music (if it is an audio stream). If the video stream does not work then the URL-link could be wrong, or possibly the codec/format or the network-protocol it uses it not supported by XBMC.

If you are creating a list of playlists (for example internal and external Shoutcast streams), save the pls or strm files into a directory accessible by XBMC and add the directory as the source, not the files themselves.

1.2 The standard playlists (.PLS or .M3U) method:

Download a supported playlist (like .PLS or .M3U) file from the internet, (these playlist files can often be found on the website of the web-radio stations or TV web-casts websites). For example stream.pls or something else, (you can rename it to whatever you want but keep the same extension). Then save/copy the .strm file to somewhere where you can open it from XBMC, (like on a SMB/SAMBA, XBMS or UPnP share, or FTP it to the local hard-drive in the XBMC device), like you would with any video/audio file. Open it using play in XBMC under My Videos or My Music (if it is a video stream, respectively a audio stream). If the video stream does not work then the URL-link could be wrong, or possible the codec/format or the network-protocol it uses it not supported by XBMC. You can check and edit playlists with a normal text-editor (like Notepad in Microsoft Windows).

2 Adding STRM files to the library

You can associate meta-data, such as cover art and summaries, to a .strm file just like normal entries in a library by using an NFO file, just as you would for a normal video file.

######################################################

If you have a stream on the internet which is shown in a flash video player: most of those streams use adobes rmtp prtotocol which is supported by xbmc. So basicly, if you want those channels as a file in your OE box you will have to find out the correct parameters for the stream. The best solution i found:
Download Mediabox and install: www.hensence.com/en/mbox/
Run it (requires admin rights)
Run your browser with admin rights (right click 'run with admin rights')
go to your streaming site and watch stream,
now, mediabox will detect the stream, if it is rmtp you are lucky and can use it in xbmc...
open mediabox(double click in system tray) right click on corresponding stream > download with blader...
blader will open and display a context menu window with a textarea where the right options are displayed. Copy those and put everithing into a *.strm file
I discovered that flash version and tcUrl can be dismissed. YOu will have to try on your own.

Here is an example:
Blader shows:

url: rtmp://109.163.230.194/live/pro7
app: live
flashVer: WIN 10,3,183,7
pageUrl: http://www.youfreetv.net/index.php?section=channel&value=pro7
swfUrl: http://www.youfreetv.net/includes/player.php?id=1
tcUrl: rtmp://109.163.230.194/live
playPath: pro7

Line in *.strm file:

rtmp://109.163.230.194/live/pro7 app=live pageUrl=http://www.youfreetv.net/index.php?section=channel&value=pro7 swfUrl=http://www.youfreetv.net/includes/player.php?id=1 playpath=pro7

save your file in OE filesystem and play it just like you would with a video. But DONT try to use your up/down keys to switch 'programs'. You would have to use stop and select another file...

OpenElec on My Raspberry Pi

   

• HOME
  • WHAT IS OPENELEC?
  • THE OPENELEC TEAM
  • MEMBER LOGIN
    1. MEMBER LOGIN
    2. CREATE ACCOUNT
    3. REMIND USERNAME
    4. RESET PASSWORD
• NEWS
• GET OPENELEC
  • DOWNLOAD
  • BUY A SYSTEM
• SUPPORT
  • CHAT
  • WIKI
  • FORUM
  • FREQUENTLY ASKED QUESTIONS
• DONATE
  • WHY I SHOULD DONATE?
  • THANK YOU
• DEVELOPMENT
  • OPENELEC ON GITHUB
  • ISSUE REPORTS
  • FEATURE REQUESTS
  • MAILINGLIST - COMMITS

Home Forum User Contribution Guides, Tips and Tricks Wireless Networking 101

• Index
• Recent Topics
• Rules
• Help
• Search

Welcome, Guest Username:  Password:  Remember me   Forgot your password? Forgot your username? Create an account

Page: 1 2 3

TOPIC: Wireless Networking 101

Wireless Networking 101 2 years 4 months ago#1

chewitt OFFLINE Moderator Posts: 3718 Thank you received: 610 Karma: 167

Below are some observations and things to understand about how WIFI (and networkIng) works in the OpenELEC OS: A. The /storage/config/network.conf file has not been used since RC4. The OpenELEC configuration addon was released and integrated into the OS as part of RC5. If you still have this file hanging around, you can delete it. B. Wireless networks with a hidden SSID (network name) are NOT SUPPORTED. Hiding the network name is pointless for security READ THIS. Yes we know it might work in Ubuntu, but OE IS NOT UBUNTU so any comparison you make is irrelevant. For WIFI security, as long as you are using WPA2 (not WEP) with a decent length of passphrase the chances of some neighbour or local kid running a brute-froce attack to steal your WIFI is exceedingly slim. XKCD has a great cartoon to educate you on PASSWORD SECURITY C. The # $ characters and <spaces> in the SSID name or passphrase will cause problems. It is possible to use them, but you need to \escape them when you enter details in the OE configuration plugin. As an example; to use "Password$" (no quotes) as your WIFI passphrase you need to input "Password\$" via the plugin. This is will be fixed eventually, but it's not a high priority right now. D. If you change network settings in the OS plugin YOU MUST REBOOT. If you don't the changes will not take effect! E. OpenELEC is designed to use a single network connection and it automatically uses an Ethernet/LAN connection if one is available EVEN IF YOU CONFIGURED WIFI. This is a hard-coded behaviour and it cannot be changed. This also means trying to debug a wireless connection issue with an ethernet cable connected is not going to work.. F. Your network connection is configured via the following files: /storage/.xbmc/userdata/addon_data/os.openelec.settings/settings.xml /var/lib/connman/default.profile The settings you entered into the OE plugin are saved in settings.xml. During boot the /etc/init.d/21_network shell script is run. This script reads data from settings.xml and creates default.profile which is used to configure the OS's connection manager; /usr/sbin/connmand. G. The network does not start as fast as XBMC does! OE boots fast (really fast) and a typical system shows the XBMC home screen in 7-10 seconds once POST has completed. However, many network cards (particularly USB ones) will take 15-20 seconds to load the kernel driver and become active, then see/join your wireless network, then get an IP address (unless your DHCP server is broken a static IP does not make things any quicker). This means things like the RSS news feed and Weather feed will fail the first time XBMC tries to refresh them and by default it will be ~30 minutes before XBMC tries again. Also affected are "on boot" library updates. If you experience this problem it is possible to add a startup script to /storage/.config called autostart.sh with the following content to force a refresh of the RSS feed (after 30 seconds) and update the libraries. Please note the Weather refresh line will only work in XBMC "Eden" based versions of OpenELEC, there is no equivalent command in XBMC "Dharma" releases: ( sleep 30 xbmc-send --host=127.0.0.1 -a "RefreshRSS" xbmc-send --host=127.0.0.1 -a "Weather.Refresh" xbmc-send --host=127.0.0.1 -a "UpdateLibrary(music)" xbmc-send --host=127.0.0.1 -a "UpdateLibrary(video)" )& H. XBMC shows 127.0.0.1 as the DNS server! This is because the OE connection manager implements a local DNS proxy, so XBMC is correctly (it is not a bug in either OE or XBMC) showing localhost as the DNS server. You may have other DNS issues but THIS IS NOT THE PROBLEM. I. If you see "wlan0 runs an unsupported 802.11 driver" in /var/log/messages this means the driver is not currently supported by the kernel maintenance team. In laymans terms; the driver is still being tested by the Linux kernel dev team before becoming officially supported and it has "staging" status. This message can be ignored; it DOES NOT mean the driver isn't working or isn't supported by your hardware. J. Things to check if wireless does not work: - You do not have an Ethernet cable plugged in! - You set network to WLAN (not LAN) - You set the right network interface (normally wlan0) - Check there are no spaces and strange characters in the network name or passphrase in settings.xml - Check there are no spaces and strange characters in the network name or passphrase in default.profile - Check that the network name and passphrase in default.profile matches settings.xml - Check your network is not hidden - Check your network does not have MAC address control active (if it does, make sure the wlan0 MAC is listed) K. If the steps above don't achieve anything, check that a wireless driver is being loaded: - Check 'ifconfig' and make sure you have wlan0 - Check 'dmesg' and /var/log/messages to check for any mention of wlan0 - Check 'lsmod', 'lsusb' or 'lspci' (for USB and PCI cards respectively) for mentions of wireless drivers - Check in the BIOS to ensure Wireless is set to be active on boot If there is no mention of wlan0 (or wlan1) anywhere the kernel is not loading a wireless driver. To assist with us with understanding why, it helps to boot the system from an Ubuntu LiveCD and run the same commands; this will tell the OE devs which wireless driver is being used in Ubuntu. If the equivalent driver is not already present in the OpenELEC OS it can be added easily by the dev team. Please post a request to the 'requests' section of the forum and/or speak to the dev team on the IRC support channel. If the driver is already in the OS please join the IRC channel for assistance. L. How do I found out what driver I need to look for? The first thing to understand is that Linux is more concerned about the chipset inside the device than the brand-name on it. There are approximately 4-5 primary vendors who make all the chipsets that used by the 30,000+ hardware manufacturers, so knowing the chipset is much more useful than knowing the brand. So how do you find out what chipset is in your device? This is easily found by running some Google searches on the model number of your wireless device and "chipset" or "chipset linux", e.g. for my Sitecom W352 USB NIC I ran a search on "sitecom w352 chipset linux" and within the first few links I discovered that it has a realtek RTL8188SE chipset. The term "linux" is good to include in the search as for any device many other Linux users have probably searched or blogged looking for the same info. Once I know the chipset I can run another search on "RTL8188SE linux driver" or "RTL8188SE ubuntu" (the Ubunto forums have lots of posts on this kind of thing) and within a few postings I can figure out that the Linux driver for my wireless card uses the "r8172u" driver. Now I can look in lsmod, lsusb or dmesg output for any mention of "r8172u" to see if the driver is being loaded. M. How do I get information off a system with no network connection? - Connect Ethernet and SSH to the console - Run the command "mount -o remount,rw /flash" (no quotes) to make /flash re-writable - Change to the /flash directory - Edit and add "debugging" (no quotes) to the kernel boot parameters line (in extlinux.cfg or patchstick.sh depending on your bootloader) - Save and reboot Once the system has restarted you will have local console access on CTRL+ALT+F3 to run commands and dump/save the contents of any logs you are being asked for to a text file. Once you reconnect an Ethernet cable you can "cat <filename> | paste" the files to pastebin.com to share the info the the dev team - please post pastebin.com URLs to the forum instead of ~800 line log output. Please also check/validate the pastebin URLs - if you make several pastes in quick succession you will probably trip spam filters on pastebin.com and you need to complete a captcha to validate the paste. If you don't validate the paste will be deleted which isn't so helpful. To ensure useful data on your wireless problem is collected, boot the system without Ethernet connected and then wait 60 seconds after the XBMC home screen appears before running commands to save/dump the files. Then (and only then) connect Ethernet to share the data. N. To restart connmand without rebooting: - Run "ps -ef | grep connmand" (no quotes) to find the Process ID (PID) for connmand. The PID is the 3-5 digit number at the start of the line that contains /usr/sbin/connmand. - Kill the process using "kill -9 <PID>" (no quotes) - Restart connmand by running "/usr/sbin/connmand" (no quotes) This is useful if you need to change/test settings in default.profile from the console. ====== Comments and feedback welcomed..

Last Edit: 1 year 11 months ago by chewitt. The administrator has disabled public write access. The following user(s) said Thank You: ilya, vitalizm, kisho, sdb, xaro, gruby102

Re: Wireless Networking 101 2 years 4 months ago#2

trinybwoy	thank you! this was an excellent post. i learned a lot!
	The administrator has disabled public write access.

Re: Wireless Networking 101 2 years 1 week ago#3

YoYo25 OFFLINE Fresh Boarder Posts: 18 Karma: 0	Hi... Thanks for the post....but I still didn't get what I should do in order to setup my WiFi on openELEC (used on Xtreamer Ultra). Can anyone refer me or send me explanation of what I should do... Thanks:)
	The administrator has disabled public write access.

Re: Wireless Networking 101 2 years 1 week ago#4

chewitt OFFLINE Moderator Posts: 3718 Thank you received: 610 Karma: 167	From the XBMC home screen: SYSTEM > ADD-ONS > ENABLED ADD-ONS > PROGRAM ADD-ONS > OPENELEC OS SETTINGS > CONFIGURE > NETWORK. Set Network Technology to "WLAN" and Network Interface to "wlan0" ..then scroll down to set the Network Name (WLAN SSID) and security type and passphrase (password) if you use them.
	The administrator has disabled public write access.

Re: Wireless Networking 101 1 year 11 months ago#5

vitalizm OFFLINE Fresh Boarder Posts: 8 Karma: 0	Awesome post! Thanks!
	The administrator has disabled public write access.

Some added tips now that mine is working... 1 year 10 months ago#6

sdb OFFLINE Fresh Boarder Posts: 2 Thank you received: 1 Karma: 0

For restarting connmand, I used killall: killall -9 connmand And I found that it restarts automatically (in /etc/init.d/21_network it is started inside a 'while' loop so when it stops it gets started again). And I wanted both wired and wireless networks active (they are on separate networks) but wireless is too slow to start so the wired started first and then the wireless never started. To get both of my multiple networks, wifi and wired, I used autostart.sh: #!/bin/bash ( # fix for wireless network wlan0 being unconfigured when eth0 is active # sleep to let things stabilize sleep 5 ETHIP= if ! ip addr list wlan0 | grep -q inet; then ETHIP=$(ip addr list eth0 | grep -o "inet [0-9./]\+ " | grep -o "[0-9./]\+") echo "wlan0, ETHIP=$ETHIP" >&2 ifconfig wlan0 0.0.0.0 down ifconfig eth0 0.0.0.0 down ps xua | grep -q "[w]pa_supplicant" && killall wpa_supplicant ps xua | grep -q "[c]onnmand" && killall connmand x=0 # give wlan0 a chance by keep eth0 down while [ $x -lt 30 ] && ! ip addr list wlan0 | grep -q inet; do x=$((x + 1)) #echo "- $x --------------" >&2; ip addr list >&2 ifconfig eth0 0.0.0.0 down >&2 sleep 1 done # now let eth0 get going ifconfig eth0 up sleep 5 fi # manually recover eth0 if possible and needed if [ "$ETHIP" ] && ! ip addr list eth0 | grep -q inet; then echo "eth0 => $ETHIP" >&2 ip addr add $ETHIP dev eth0 fi ) &

The administrator has disabled public write access.

Re: Some added tips now that mine is working... 1 year 6 months ago#7

Bossanova808 OFFLINE Expert Boarder Posts: 356 Thank you received: 10 Karma: 6

This guide is great however the problems with USB wireless dongles taking time to start up are more than jsut firing off a weather/rss update - if you're using network shares, these don't come up either of course, and there doesn't appear to be an obvious way to tell XBMC Also - my micronext USB-N adaptor - mn-wd152B - comes up quickly enough sometimes, but then others it doesn't come up at all. Is there perhaps a more foolproof way of delaying XBMC's start until wlan0 is up and has an IP??

My XBMC stuff: ...inc: [*]XSqueeze - Squeezebox Controller/Player for XBMC [*]OzWeather - weather with Australian BOM data [*]Fanless, silent, powerful XBMC Build [*]Get Win7 to run RemoteApps The administrator has disabled public write access.

Re: Some added tips now that mine is working... 1 year 6 months ago#8

chewitt OFFLINE Moderator Posts: 3718 Thank you received: 610 Karma: 167

/storage/.config/autostart.sh is the only user-friendly way to manipulate the boot process. To do more you need to think about a custom build and tweaks to the init scripts: ( sleep 10 echo "this runs in the background while other processes are still doing their thing" &) sleep 10 echo "this results in EVERYTHING stopping for 10 seconds as the sleep timer counts down" What chipset is in the USB? (lsusb)

Last Edit: 1 year 6 months ago by chewitt. The administrator has disabled public write access. The following user(s) said Thank You: Bossanova808

Re: Some added tips now that mine is working... 1 year 6 months ago#9

Bossanova808 OFFLINE Expert Boarder Posts: 356 Thank you received: 10 Karma: 6	Not at home right now, but haven't found the chipset yet - www.bluenext.co.uk/wifi-products/wifi-ad...ireless-adapter.html ..actually I have just unzipped the driver package and it looks like Realtek RTL8818CUS It's jsut odd that sometime is comes up before XBMC boots, other times not at all. I guess I should be looking in dmesg but it's a pain cause there's no network!
	My XBMC stuff: ...inc: [*]XSqueeze - Squeezebox Controller/Player for XBMC [*]OzWeather - weather with Australian BOM data [*]Fanless, silent, powerful XBMC Build [*]Get Win7 to run RemoteApps Last Edit: 1 year 6 months ago by Bossanova808. The administrator has disabled public write access.

Re: Some added tips now that mine is working... 1 year 6 months ago#10

chewitt OFFLINE Moderator Posts: 3718 Thank you received: 610 Karma: 167

Realtek USB chipsets seem to take substantially longer than others to initialise. The couple I have take 22-25 seconds whereas the Atheros card I have takes 5-6 seconds, and "over time" there's been a persistent drip-feed of postings about this kind of thing and it's always a Realtek NIC. If you look in /var/log/messages you'll see dmesg and info on the init scripts running at the same time. The networking init script tests once each second for 30 seconds for the NIC device to be shows as present, then it starts connman. If it's over 30 seconds connman starts with no profile for the NIC and WLAN simply won't work during that boot cycle, even when the NIC has finally initialised. I suspect your NIC is right on the 30 second boundary; hence sometimes it works, others it doesn't. Googling that chipset turns up only 4 posts in chinese. I think when you plug it in and run lsusb the chipset will be something else (more known)

The administrator has disabled public write access. The following user(s) said Thank You: Bossanova808

Re: Some added tips now that mine is working... 1 year 6 months ago#11

Bossanova808 OFFLINE Expert Boarder Posts: 356 Thank you received: 10 Karma: 6

I'll try lsusb out tonight with any luck... I am not qutie sure you're right on the timing thouhg, in that there's a little green LED on teh dongle - sometimes it lights up almsot straight after the SYSLINUX screen, and other times not at all - pretty much nothing inbetween. I will try putting a pause in place, I don't care if it takes 10 extra seconds to boot as long as it does come up. Eventually I will just get a cabler in to do Cat6 but it will be a tricky install so was keen to get things running at least moderately before I can organise that...

My XBMC stuff: ...inc: [*]XSqueeze - Squeezebox Controller/Player for XBMC [*]OzWeather - weather with Australian BOM data [*]Fanless, silent, powerful XBMC Build [*]Get Win7 to run RemoteApps The administrator has disabled public write access.

Re: Some added tips now that mine is working... 1 year 6 months ago#12

Bossanova808 OFFLINE Expert Boarder Posts: 356 Thank you received: 10 Karma: 6

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLANBus 002 Device 002: ID 147a:e03e Formosa Industrial Computing, Inc. Infrared Receiver [IR605A/Q] Bus 002 Device 003: ID 04d9:1203 Holtek Semiconductor, Inc. Keyboard On a succesful startup: [ 6.161131] ADDRCONF(NETDEV_UP): wlan0: link is not ready .... [ 9.126303] wlan0: direct probe to 00:04:ed:d0:03:9a (try 1/3) [ 9.132031] wlan0: direct probe responded [ 9.167293] wlan0: authenticate with 00:04:ed:d0:03:9a (try 1) [ 9.181935] wlan0: authenticated [ 9.182377] wlan0: associate with 00:04:ed:d0:03:9a (try 1) [ 9.201123] wlan0: RX AssocResp from 00:04:ed:d0:03:9a (capab=0x411 status=0 aid=5) [ 9.201133] wlan0: associated [ 9.215089] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready ...that's 9 seconds right? So it CAN be up in that sort of time, but clearly it often isn't.... It dropped the connection while I was getting these files....I am really dubios this is ever gonna work well enough. I have tried EOP devices as well, I've never had a set last longer than 6 months....I think I have to bite the bullet and get the cabling done...

My XBMC stuff: ...inc: [*]XSqueeze - Squeezebox Controller/Player for XBMC [*]OzWeather - weather with Australian BOM data [*]Fanless, silent, powerful XBMC Build [*]Get Win7 to run RemoteApps The administrator has disabled public write access.

Re: Some added tips now that mine is working... 1 year 6 months ago#13

chewitt OFFLINE Moderator Posts: 3718 Thank you received: 610 Karma: 167

Yup, 9.2 secs It should be using the r8192cu driver which has been in the OS for a while, but some Google research on this specific chipset gives a mixed bag of results that vary wildly from kernel to user to distro combination. The general synopsis seems to be that if it works OOTB it'll work really great, but if it doesn't work you're in for a visit to driver purgatory. OE uses the kernel driver not the Realtek binary driver, but there are an equal number of complaints for each so I'm not sure that would be the solution. In short; no ideas what the issue is  Cat6 gets a thumbs up as WLAN is always a little sucky for streaming.

The administrator has disabled public write access.

Re: Some added tips now that mine is working... 1 year 6 months ago#14

Bossanova808 OFFLINE Expert Boarder Posts: 356 Thank you received: 10 Karma: 6	Yeah thanks, I will call the cabler - once done it will always be right...
	My XBMC stuff: ...inc: [*]XSqueeze - Squeezebox Controller/Player for XBMC [*]OzWeather - weather with Australian BOM data [*]Fanless, silent, powerful XBMC Build [*]Get Win7 to run RemoteApps The administrator has disabled public write access.

Re: Wireless Networking 101 1 year 6 months ago#15

gruby102 OFFLINE Fresh Boarder Posts: 9 Karma: 0	Thank You very much for this post!!!
	The administrator has disabled public write access.

Page: 1 2 3

Moderators: MikeBuzz, turbomettwurst, lrusak

Powered by Kunena Forum  Protected by R Antispam

Our Sponsors & Partners

Back to Top

Copyright © 2009-2013 OpenELEC - The living room PC for everyone. All Rights Reserved.