VM to gig BB in the UK
so where do VM to gig BB ethernet (over coax) in the uk and how much does this cost?
when are VM expected to release the patch?
Does this affect vm's other <300 mb users too?
Why your gigabit broadband lags like hell – blame Intel's chipset
Intel's Puma 6 chipset, used in gigabit broadband modems around the world, suffers from latency jitter so bad it ruins online gaming and other real-time connections. The semiconductor giant is preparing a firmware update to correct spikes of lag and bouts of packet loss that repeatedly flare up in home internet hubs in America …
-
-
Saturday 3rd December 2016 09:56 GMT diodesign
Re: VM to gig BB in the UK
If you're on a SuperHub 2, you'll be OK. If you get any package that has a Superhub 3, you'll be needing a patch which isn't expected for a short while. By gigabit broadband modem, we mean gigabit-capable; you could get a Homeworks 300Mbps package and get a Superhub 3 box and suffer from extra lag.
C.
-
-
Saturday 3rd December 2016 16:25 GMT lawndart
Re: VM to gig BB in the UK
Superhub 2, black, loads of lights on the end and embossed VM logo on the sides.
Superhub 3: white, only one light on the end and has mesh sides for cooling.
I still have a SH1 and have only had that a couple of years, thanks to VM not upgrading my old Motorola Surfboard from 2001 until it finally died, even when requested.
-
-
Tuesday 6th December 2016 16:35 GMT JamesSmith1
Re: VM to gig BB in the UK
diodesign, this Virgin media problem as the only real cable operator in the UK, is far larger than it would seem as they dont allow you to connect any non VM CPE kit...
and are Insisting that all vm customers that take the 'VIVID 200 Gamer' option or above as per the current 300Mbit/s package, Must take the one and only 'Superhub 3.0' Compal CH7465-LG (TG2492LG) & CGNV4 etc docsis3 box, as their only option, and apparently, VM tech/managers are refusing to lift the apparent VM swap-embargo on these SH3 and take the older Superhub 2 ACs as a fix today....
while its hard to actually pin down the exact chip spec and RAM (can you confirm and add the direct url) it seems that these intel docsis Soc are far to underpowered today, and dont even include generic intel AVX SIMD instructions in 2016, and yet the totally underpowered CPU core is actually doing all the UDP/TCP packet work etc alone....
is that a BOM problem today, as in all the world's Docsis3 cable operators are trying to save pennies , where a current and up to date (Arm Cortex?) quad/octacore with DVB/sat>IP ,UHD1/UHD2 rec 2020 ,HDR compliant integrated SOC's are required today ready for 2017/2020 Docsis 3.0/3.1.
-
-
-
Saturday 3rd December 2016 10:32 GMT NateGee
Not been impressed with my SH3
I can't help but wonder if this related to the issue I have with my SH3 when in modem mode. It absolutely hates my RT1900AC (It was OK with my previous router (RIP)), I was getting random disconnects from t'interweb and everything pointed to the SH3. I even got the SH3 swapped because of it which made little to no difference. I ended up having to switch the SH3 back to normal router mode, disable WiFi and DHCP and stick my router in the SH3's DMZ to get it reliable. I might wait until the next FW update and give it another go.......
-
Tuesday 6th December 2016 17:19 GMT JamesSmith1
Re: Not been impressed with my SH3
yes , this is also a known problem so called 'Hub 3.0 port flapping' as in even when you switch these VM SH3 into modem only mode, the same high pings,TCP,UDP etc exists AND you also get this other bug manifesting ...
The SH3's Port1 plugged into a ethernet port (ether1) on any router,where Everything works fine for about 30 minutes, and then the super hub shuts down its ethernet port for about 30-60 seconds, then brings it back up.
thats the other problem that,s still to be fixed, as relates to your SH3 being connected to some VM cards in their racks... so again you get disconnected from your game server when this happens, so making the existing 200Mbit/s gamer option rather lame and currently not fit for purpose if you are upgrading for the holidays this year it seems, unless all these related MS chipset fix's are expedited PDQ...
-
-
-
-
Saturday 3rd December 2016 22:58 GMT MNGrrrl
Re: From the original article
> Every article. Every.single. article. Whining about windows 10 in the comments regardless of the content of the article.
It's a side effect of Windows 10 installation... it causes the syst...er... user, to become stuck in an infinite reboot loop. Microsoft has been promising a patch er, since it was released... but I wouldn't get my hopes up. At least it's not a -4931337 error... also known as 'Smug Of Death' bug that plagues certain macintosh users. That one is just awful.
-
Sunday 4th December 2016 00:11 GMT Anonymous Coward
Re: From the original article
"Every article. Every.single. article. Whining about windows 10 in the comments regardless of the content of the article."
Why not? A big target is easily hit.
It's up there with DOS for simply wasting your time. I recall spending ages fiddling with himem.sys and emm386.sys to get games to work. Move forward a couple of decades and now I have to spend ages getting printers, scanners and other games working in new and amusing ways. Oh hilarious: after an update a driver is now disabled because "reasons". The start menu thingie keeps on reinstalling shit I've removed because "reasons".
Do I sound unhappy with Win10? Sorry. I use Linux myself. I seriously compare taming a Win10 install to maintaining a Gentoo install or perhaps Arch (Arch is precompiled.)
Yes I will whinge about it but only on other people's behalf
-
-
Monday 5th December 2016 20:48 GMT martinusher
Re: "I use Linux myself"
"now I have to spend ages getting printers, scanners and other games working in new and amusing ways"
Actually my experience with printers has been that they install quickly and automatically in a Linux environment. (...and Microsoft still hasn't figured out how to manage USB devices properly)
-
-
Monday 5th December 2016 09:43 GMT PeteA
Re: From the original article
From the viewpoint of someone who maintains about 8 Arch Linux boxes at home [plus the wife's MacBook] and a few hundred Windows machines at work, I don't think there's any comparison between the two. My Arch boxes have been typical Linux, i.e. lots of mostly simple configuration work and a few head-scratchers followed by years of solid service with occasional WTF's (such as when CUPS dropped support for parallel printers.... grrrrr....) and the Windows boxes at work have been typical Windows, i.e. a nightmare to configure followed by years of misery and "random" problems.
-
-
-
Sunday 4th December 2016 05:14 GMT fnj
Re: From the original article
[Expletive deleted] Whining about windows 10
I choose not to match your rudeness, but jeeze, did it ever occur to you that there is a REASON everybody hates it? I knew enough never to touch Windows at all after 7, and damn little after XP. I have been almost 100% Windows-free for over a decade, having jumped into Linux beginning 22 years ago, and do not miss any part of it.
-
Sunday 4th December 2016 14:57 GMT d3vy
Re: From the original article
Oh my god, the article is nothing to to with windows, or Microsoft it's a bug in some Intel code in router.
Do you all do this in normal life too?
Coffee shop : what do you want to drink?
You : I'll tell you what I don't want. Windows 10
Coffee shop: get out.
Seriously get some perspective, take up a hobby, walk the dog, anything but obsessing about windows, it's not healthy. if you don't like it don't use it, but please stop bringing it up on unrelated articles bringing the whole bloody site down.
-
-
-
-
Saturday 3rd December 2016 14:43 GMT Mage
Other Intel Chip
The Intel I219V on new laptop was disconnecting every second. Only 10MBps mode worked. Switched off "autonegotiate" and tried Slave then Master. Only Master worked at 100Mbps or 1Gbps to my 3Com based 8 port switch.
So have Intel a problem writing drivers right now? Both Lenovo and Windows Update offered "newer" drivers with same problem.
-
-
Monday 5th December 2016 02:34 GMT Anonymous Coward
Re: Other Intel Chip
The sad thing is Intel inherited the old DEC Tulip network chips which worked damned well. No clue what they did to the technically to reach this state.
I had two Fortville-based XL710 cards and two previous gen X520 cards. The Fortville ones (post massive recall) still had major firmware bugs that caused them to pull the firmware with NO way to downgrade (the upgraded made a backup but no way to restore it!), and both had issues with SR-IOV and their own embedddd MAC filters. Trashed them and went with Chelsio and never looked back.
-
Monday 5th December 2016 00:21 GMT Long John Brass
Re: Other Intel Chip
> So have Intel a problem writing drivers right now?
Intel driver have always been crap. If you ever tried to do anything slightly out of the ordinary with the display setup it would shit the bed at semi regular intervals; Assuming it ever worked at all.
Caveat: My experience was with shitsets 810 thru 945 on Linux systems
-
Monday 5th December 2016 10:14 GMT Anonymous Coward
Re: Other Intel Chip
Some Intel integrated display drivers are crap, I'd agree totally. They continue to exhibit a stupid Gamma bug in laptops so that light colours get washed out and disappear on external monitors connected to many laptops.
You open up the graphics properties window and move the Gamma slider slightly and the colours suddenly pop back to life again - go slightly too far again and the screen goes crap again.
However due to a fight between the Intel Graphics properties and Windows Graphic properties whenever the machine resumes from standby the settings get reset.
Intel acknowledge but say there will be no fix...
-
-
Monday 5th December 2016 15:50 GMT Anonymous Coward
Re: Other Intel Chip
Intel has always had issues with drivers. I worked for intel break/fix back back in the early 2000's . We were getting loads of lap tops with errors for wi fi. issue will not connect at star bucks. Well sounds like a starbucks issue cause it works fine here at intel campus. Turns out it was not a starbucks issue but a drive issue. Do to a hiccup the Intel wi fi card will not connect to cisco AP on channel 3 ,6 and 9. The fix was and intel driver hidden away on the intel web site. Now if you used MS or the manufactures drivers the issue would come back. Now those was and Intel issue with intel solution for intel employees that very few people knew about.
-
-
-
-
Sunday 4th December 2016 20:27 GMT Anonymous Coward
Re: Intel seem to be a bit fallable
Should have gone with an ARM SOC.
A bit difficult - cable is a duopoly - Broadcom (which uses mips for cable) or Intel. They both suck in their unique wonderful way - violation of specs, bugs obscure quirks, etc.
This is one of the reasons I have declined SH3 every time Virgin tries to shovel it down my throat. I stay with SH2 as it is the last CPE which can still do bridging. So I use the Broadcom chip within in the most stupid mode possible - as a bridge and hook it up to an OpenWRT. No intelligence allowed (as there ain't any - it's cable).
-
-
Saturday 3rd December 2016 15:30 GMT Anonymous Coward
It happens
Could've been worse; at least it's fixable via software update. I remember severe growing pains back in the day. A lot of 28k-33k-56k dialup modems had far worse bugs that never got fixed. Cable was plagued by latency & congestion problems when it first became popular.
25ms jitter, though... ouch. I've seen ping times lower than that.
-
Saturday 3rd December 2016 18:36 GMT Chris Stephens
Re: It happens
We dont know yet if it can be fixed with software. Im waiting on the firmware now. However at least one tester shows the issue is not fixed. Im the DSLReports guy Xymox1 who found the issue and the guy Chris mentions in the story. Those are my plots. So.. We dont know yet if it can be fixed in firmware. Its a stay tuned moment.
-
-
-
-
Monday 5th December 2016 07:35 GMT jake
Re: It happens
With probably 99% of all useful 'net content being good old 7-bit ASCII text, who can read faster than 19.2K/sec? Even today, I still connect over dial-up from my property in rural Mendocino county about 15% of the time ... sometimes at speeds as low as 2400 bps (fog and aging, cracked, dusty cable plant makes for bad signal/noise ratio). The low speed doesn't seem to affect my "internet experience" much ... And that's barely 200 miles by road from Silly Con Valley!
Mine's the one with the Telebit Trailblazer in one pocket & Kermit code in the other ...
-
-
-
-
Biting the hand that feeds IT
