Welcome to GOFASTMOTORSPORTS.com ... ... ... Green Flag - Green Flag - Go Go Go ... ... Brought to you by Ricks Satellite - Where the Big Dish Rules!

Ricks Satellite Wildfeed and Backhaul Forum
Register Latest Topics
 
 
 


Reply
  Author   Comment   Page 5 of 7     «   Prev   2   3   4   5   6   7   Next
rempfer

Avatar / Picture

Registered:
Posts: 896
Reply with quote  #61 
Quote:
Originally Posted by rempfer
I will do this and then try recording 4:2:2 CBS HD to my freshly EXT2-formatted SSD. Thanks, mountaineer! Away from home for a bit just now, so will have to wait.
When the EXT2 SSD disk was attached as an external/USB drive, CBS HD would only record for a few seconds.  Then I removed the disk from the USB enclosure and installed directly into the Me, at which point a 3 minute recording completed successfully.  So USB3 enclosure plugged into the Me's USB (2?) port does not record successfully but if drive is installed into the Me it does succeed.

mountaineer

Avatar / Picture

Registered:
Posts: 2,697
Reply with quote  #62 
Thanks Rempfer. I think 3.3.1 kernel is the best...sounds like 3.92 still has some issues. Maybe dark sky and daz can figure out what is going on with the stuff meantioned a couple of posts ago and the code issues.

Thanks!!!!!

__________________
3 Edison OS mini's, 3 Openbox S10s, 2 Openbox S9's, NFusion HD, 2 Prof 7500's, Genpix Skywalker 1, 2 Optibox Anacondas, Azbox me, Azbox minime, 2 Jynxboxes, ismart m100, izzibox, TBS 6982, Vigica C60s, Optibox Raptor, azbox Bravissimo, TBS 5922SE, TBS 5980 (Broke), and TBS 6902.
 36" KU Dish Linear, 10 ft prime focus Mesh, 7.5ft prime focus mesh dish C and KU.
7 Stationary KU dishes.
dazulrich

Registered:
Posts: 204
Reply with quote  #63 
Quote:
Originally Posted by jdcpa
FWIW to the uninitiated, EXT2 and EXT3 share the same driver; the only material difference between them is EXT3 adds journaling. Translated, that means EXT3 (and EXT4) increase I/O overhead. EXT4 adds other advancements and requires a different driver. In recent years the EXT2/EXT3 driver has been deprecated. Its job has been superceded in all current Linux for PC distros by the EXT4 driver. As the AZBox kernels have the storage driver(s) compiled directly into the kernel, /boot is empty, and there is no /proc/config.gz, I don't know how to tell any details about what is compiled into its running kernel.


I've found differences between the 3.3.1 and the 3.9.2 kernel builds. they may or may not contribute.
Basically in 3.3.1. ext2/ext3 were build into the kernel and no ext4 support was included.
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT3_FS=y
CONFIG_EXT3_DEFAULTS_TO_ORDERED=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT4_FS is not set
CONFIG_JBD=y

in kernel 3.9.2 on the other hand ext2/ext3 were build as modules and ext4 build into the kernel
CONFIG_EXT2_FS=m
# CONFIG_EXT2_FS_XATTR is not set
CONFIG_EXT3_FS=m
# CONFIG_EXT3_DEFAULTS_TO_ORDERED is not set
# CONFIG_EXT3_FS_XATTR is not set
CONFIG_EXT4_FS=y
CONFIG_JBD=m
CONFIG_JBD2=y

If the ext2/3 modules weren't loaded, the ext4 will provide ext2/3 with JBD not included, maybe the whole ext3 isn't working properly.
I could put ext2/ext3 back into kernel and take ext4 out just to see if that makes difference on this level.
mountaineer

Avatar / Picture

Registered:
Posts: 2,697
Reply with quote  #64 
If you can put it into your kernel I will test it.  Thanks!!!!!!!
__________________
3 Edison OS mini's, 3 Openbox S10s, 2 Openbox S9's, NFusion HD, 2 Prof 7500's, Genpix Skywalker 1, 2 Optibox Anacondas, Azbox me, Azbox minime, 2 Jynxboxes, ismart m100, izzibox, TBS 6982, Vigica C60s, Optibox Raptor, azbox Bravissimo, TBS 5922SE, TBS 5980 (Broke), and TBS 6902.
 36" KU Dish Linear, 10 ft prime focus Mesh, 7.5ft prime focus mesh dish C and KU.
7 Stationary KU dishes.
dazulrich

Registered:
Posts: 204
Reply with quote  #65 
of course you would :-) lets see when i'll find a bit of time.
mountaineer

Avatar / Picture

Registered:
Posts: 2,697
Reply with quote  #66 
No rush ...just volunteering if you wish to do it....I'm happy mine is clicking along great....and thanks to you others can get 16apsk and maybe 32 apsk on theirs. 
__________________
3 Edison OS mini's, 3 Openbox S10s, 2 Openbox S9's, NFusion HD, 2 Prof 7500's, Genpix Skywalker 1, 2 Optibox Anacondas, Azbox me, Azbox minime, 2 Jynxboxes, ismart m100, izzibox, TBS 6982, Vigica C60s, Optibox Raptor, azbox Bravissimo, TBS 5922SE, TBS 5980 (Broke), and TBS 6902.
 36" KU Dish Linear, 10 ft prime focus Mesh, 7.5ft prime focus mesh dish C and KU.
7 Stationary KU dishes.
dazulrich

Registered:
Posts: 204
Reply with quote  #67 
Just curious. Did anyone manage to record CBS with the miniME with older images in the past (onto USB HDD)?
Just thinking as rempfer's ME failed to record onto ext2 formatted USB hdd.
rempfer

Avatar / Picture

Registered:
Posts: 896
Reply with quote  #68 
Quote:
Originally Posted by dazulrich
Just curious. Did anyone manage to record CBS with the miniME with older images in the past (onto USB HDD)? Just thinking as rempfer's ME failed to record onto ext2 formatted USB hdd.

Just to remind everyone, however the Me did subsequently record onto that same ext2 formatted SSD when I physically installed it into the Me.
mountaineer

Avatar / Picture

Registered:
Posts: 2,697
Reply with quote  #69 
Daz and Rempfer....I have said for a long time that there is an issue in the me and minime usb port function and data transfer. My prof stutters some on highbitrate feeds in the thru put...it seems that your me can record when sata not usb...and I think you said there are issues with the tbs card which uses usb. I am probably wrong but I do believe that a lot of the issues have 1 thing in common..the usb port and its handling of data input. May be a clue can be found there..I dont know. I think we are treating some of the symptoms  but not curing the ill. If anybody can find it out it will be daz.
__________________
3 Edison OS mini's, 3 Openbox S10s, 2 Openbox S9's, NFusion HD, 2 Prof 7500's, Genpix Skywalker 1, 2 Optibox Anacondas, Azbox me, Azbox minime, 2 Jynxboxes, ismart m100, izzibox, TBS 6982, Vigica C60s, Optibox Raptor, azbox Bravissimo, TBS 5922SE, TBS 5980 (Broke), and TBS 6902.
 36" KU Dish Linear, 10 ft prime focus Mesh, 7.5ft prime focus mesh dish C and KU.
7 Stationary KU dishes.
dazulrich

Registered:
Posts: 204
Reply with quote  #70 
Thanks for the vote of confidence. I should have looked at all that a few years ago when more boxes where still in operation.
So what you are saying is that USB recording never worked for CBS, not even the old images.
mountaineer

Avatar / Picture

Registered:
Posts: 2,697
Reply with quote  #71 
In the minime no..as far as i know. The azme worked back in kernel 2.6.....but little since on a consistent basie as far as I can remember.
__________________
3 Edison OS mini's, 3 Openbox S10s, 2 Openbox S9's, NFusion HD, 2 Prof 7500's, Genpix Skywalker 1, 2 Optibox Anacondas, Azbox me, Azbox minime, 2 Jynxboxes, ismart m100, izzibox, TBS 6982, Vigica C60s, Optibox Raptor, azbox Bravissimo, TBS 5922SE, TBS 5980 (Broke), and TBS 6902.
 36" KU Dish Linear, 10 ft prime focus Mesh, 7.5ft prime focus mesh dish C and KU.
7 Stationary KU dishes.
rempfer

Avatar / Picture

Registered:
Posts: 896
Reply with quote  #72 

Experiment:

Recording experiment of CBS HD 4:2:2

Kernel 3.3.1

OpenRSI 3.0

Storage Devices Both Formatted EXT3:
1. USB 2.0 Key and
2. USB 2.0 enclosure with IDE HDD

Result:

I can state categorically that the AZBox Me's recording of CBS HD 4:2:2 works fine, period. However if used, the USB key has to be capable of  performing writes fast enough to keep up with the input stream.  See below.

Regardless of whether USB2 or USB3, I discovered (with the PNY 16GB key I used for this experiment) that INTERNALLY a USB key may be too slow to write the stream, the Me will lock up with the "spinner" and the video file will be corrupt. Clearly this is NOT the Me's fault.

Even though the other storage device used was a USB enclosure containing an older 32GB EIDE HDD, it had NO TROUBLE whatever keeping up in recording and/or playing back the video stream. I am sure I could have continued recording on this device until it ran out of space.

If there are any other experiments you'd like me to perform on the Me with this kernel and/or these devices please let me know.

  -- Dick Rempfer

dazulrich

Registered:
Posts: 204
Reply with quote  #73 
thanks a lot Rempfer.

I need to change my build environemnt before I can make those suggested kernel changes as I had been playing with building UBIFS images instead of JFFS2.

once I have created test build using the ext2 and ext3 system drivers instead of using ext4, will hopefully show whether we can record using 3.9.2  onto an ext3  formatted internal (SATA) hdd, and whether we can record on ext3 formatted USB hdd. - or not.

The driver patches for sigma chip that are part of the 3.9.2 build could also cause some of theses issue.
Similar to the problem with the SATA drivers that didn't work. but that is speculation for now. lets try changing the kernel driver first.
rempfer

Avatar / Picture

Registered:
Posts: 896
Reply with quote  #74 
I have two (identical) Me's.  One with the 3.9.2 kernel installed and the other with 3.3.1.  The USB2 EIDE HDD enclosure has an activity LED that goes from green to red when disk I/O activity is occurring.

This seems like a big clue:  When recording to the external USB2 EIDE HDD with the 3.3.1 kernel, the disk writes occur in small bursts with the majority of time spent in the green light (no activity)  state.  When recording to this same device with the 3.9.2 kernel, the red (activity) light is on almost constantly at first with tiny green interruptions, and after only a few seconds the red light comes on steady and the recording has failed/stalled at this point.

So the 3.9.2 kernel seems to be either sending a lot -- and I mean a LOT -- more data to the USB storage device than the 3.3.1 kernel does or it is otherwise keeping the port so busy it can't do its job.  I am leaning toward the latter being the case, since I can record successfully with the 3.9.2 kernel to an internal SSD and the resulting file size for a (successful) three minute recording is pretty close to the same size (around 600-800 MBs) regardless of whether created by 3.3.1 or 3.9.2.  

So this great amount of extra activity at the USB port generated by the 3.9.2 kernel is not resulting in a larger file, but would seem to be rogue data keeping the USB port so busy that it can't keep up with the video stream it's trying to pass to the storage device.  

My first question would be, what is the source of these calls to the USB port that cause the port to be so busy it can't pass the data stream?

The AZBox Me's are great little units.   And so again I thank you, dazulrich, and everyone else who's working on this.  You're all the best!
dazulrich

Registered:
Posts: 204
Reply with quote  #75 
Thanks rempfer. Maybe we can find some USB sniffing tool to record the traffic. Just thinking out loud.
But could well be a bit borked. Wouldn't be the only thing with the azbox.
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.

Fellow Members, your posts are welcome here! Do not worry about posting everything perfect. Different receivers and LNB's will give you different Frequencies and Symbol Rates. Some set top boxes, PCI cards and USB receivers, Do Not Require all of the same information that others may need. It is not Required to post everything that others may need to tune in a feed. It is just most important to share the find. We can always adjust the Frequency and Symbol Rates and try the various Modulations and FEC's on our own receivers until we get a lock and then give a polite reply with what works for your receiver, as that information might help others as well. We all appreciate the efforts and energy of the Posters!

Thank You for Visiting GOFASTMOTORSPORTS.com - Keep Your Eyes on the Sky and the Track!