User talk:M86/Archive 3

From WikiDevi.Wi-Cat.RU
Jump to navigation Jump to search

RTL8821AE/8812AE driver in kernel

Hi M86,

At a few wireless adapters including https://wikidevi.com/wiki/Amped_Wireless_PCI20E (the only one with mentioned PCI ID) I see the RTL8812AE chip type without any known driver, but the rtl8821ae module in the kernel since 3.18 is supposed to support the RTL8812AE and RTL8821AE chips.

For 8821AE (https://wikidevi.com/wiki/Realtek_RTL8821AE_Combo_Module) you are already mentioning it, but as a probable Linux driver expected in staging at some point. Since the driver is in the mainline kernel (not staging) at the moment, I think you should change this text too. I do not own any of these devices so I have not tested the driver. I hope this message will been useful to you anyway.

Kind regards,

Albert Pool (co-maintainer of PCI ID database / pci.ids on Linux)

Noted. Will fix..
--M86 (talk) 20:11, 29 January 2015 (EST)

ASUS AC Products Navbox

I took the liberty of creating the Navbox, but the Navbar looks goofy. The Navbar module needs to be updated. To update to the proper version, MediaWiki needs to be updated to 1.24.0+. --DarkShadow (talk) 08:29, 14 January 2015 (EST)

I'll look into it when I can.. --M86 (talk) 20:11, 29 January 2015 (EST)

Missing linux kernel version message

Broadcom BCM94356Z is supposed to show "PCI ID first seen in kernel (...etc)" but doesn't show any message, not even "PCI ID not yet observed in any mainline kernel / this list". Weird.

Hm.. seems to be working now, anyhow. --M86 (talk) 20:11, 29 January 2015 (EST)

Editing when not logged in

Editing without login is buggy and cumbersome: after clicking 'publish', it asks again for change description (even though I already filled it the bottom), then it reloads the same edit with a bot question, then you need to click 'publish' again, then it asks for change description *again*. And if you click 'save' button at the bottom at any stage (instead of publish), you get thrown back to the bot-question even if already answered (ie. 'save' button doesn't work). For every additional click, you lose users...

Template problem

Something is wrong with this page (the bottom of template on the right): MikroTik_RouterBOARD_750GL

Empty template values

Do you know of a way to block those from showing up when you hit edit? The closest I have come is this excerpt from semantic mediawiki.

Optional entries and conditionals
"In the normal course of operating a wiki, most pages will probably not have their infoboxes completely filled, and you might not want to show empty rows in such cases. To remove rows with blank values, you can add conditionals into the template code, which include a row (and its annotation) only if a non-empty value was provided.

This can be achieved with the help of the #if parser function, defined in the MediaWiki ParserFunctions extension. Wikipedia contains many examples of parser functions in templates, as for instance in template "Taxobox". Using parser functions typically results in difficult-to-read template code, but the simplification for users can be substantial."

I've looked through the "Taxobox" template and tried several thing, but none worked.

For example:

{{Infobox Embedded System
|above=
|image=
|image1=Netgear_JWNR2000-01.jpg
|image1_size=100px
|caption=Wireless- N 300 Router
|...
}}

I don't want above and image to show because they are empty. Am i making since? --DarkShadow (talk) 00:20, 24 October 2014 (EDT)

.. I don't get what you're asking. If you simply want to hide empty fields in templates while editing, you would either need to remove the fields from the pages or hack together some extension that can hide them (if something else can't already). If you use Semantic Forms for data entry, it will hide unused fields by default. --M86 (talk) 20:46, 24 October 2014 (EDT)
I am using SF's. I was using Semantec Bundle and Upgraded to the latest MW, SMW, and acompaning Semantic Extension and that behavor stopped. --DarkShadow (talk) 21:48, 24 October 2014 (EDT)
Dumb me. I downloaded it from the Extension Distributor and also just overwrote the directory. After downloading from the proper place and deleting the directory and copying fresh, it works right.*smacks forehead with palm* --DarkShadow (talk) 23:00, 24 October 2014 (EDT)

NOS?

In Atheros page, AR4100 is categorized as "NOS". What is NOS?

In this instance, 'not otherwise specified'. --M86 (talk) 22:13, 21 October 2014 (EDT)

AMIT / AMRISC

There are about 10-15 pages that require the correction:

  • brand: AMRISC -> Amlogic
  • chip: xxxxxx -> AMRISC xxxxxx

in CPU / WI1 / Eth chip models. Do you have a way to automate this? (incorrect, see below)

Also, many pages link to this page: Atmel AT76C502/3/5A device matrix, which doesn't exist anymore. In Atmel, I linked to Atmel AT76C502/3/5A device matrix (archive.org) instead; all other pages require fixing/automated replacement perhaps?

Yes, the Replace Text extension and/or pywikibot will work fine
.. but, are you absolutely sure that is correct? Amlogic's old site makes no mention of any of these chips (nor that target market), just multimedia related ICs w/ (the still in use) AMLxxxx P/Ns. AMRISC is indeed noted as a used trademark, but I would not be sure it is related. AMIT also appears to be the only company that had embedded these SoCs in their products. The schematics under the FCC filings for the various AMIT manuf'ed DI-524 just note the RDC P/N (10100 [/ D-Link-branded DL7500A] noted as the R2600, 20100-G noted as the W5610 [both 208-pin QFP]) - I would think they're just AMIT-rebadged RDC SoCs
--M86 (talk) 23:42, 3 October 2014 (EDT)

It makes much more sense that $mystery_company is AMIT, I agree. This mistake is perpetuated in several websites around the internet.
So, there are about, ahem, 20-25 pages that require the correction:

  • brand: AMRISC/Amlogic -> AMIT
  • chip: xxxxxx -> AMRISC xxxxxx

in CPU / WI1 / Eth chip models. Do you have a way to automate this?

Again, of course.
.. but the chips themselves are ambiguously branded.. and I don't know if there was much involvement on AMIT's part. I would be more inclined to revert them back to 'AMRISC' brand.. with RDC noting this information along w/ everything else.
If specific chips are known to be identical to an RDC part, it may be preferable to use that rather than the 'AMRISC' P/N.
--M86 (talk) 22:35, 4 October 2014 (EDT)

MIMO jibberjabber

How is this possible? 1x2:2 - 150Mbps transmitting, 300Mbps receiving

the maximum number of streams is the minimum of the number of tx or rx antennas. you can't receive more data than you transmit, and you can't independently receive more streams than you have degrees of freedom.

—The preceding unsigned comment was added by 75.144.223.89 (talkcontribs) . Please sign your posts with ~~~~!

There is no requirement for symmetric uplink / downlink. 300 Mbps would be its maximum Rx rate, provided the 1x2 client was talking to a 2x2 (or greater) AP.

--M86 (talk) 16:58, 13 September 2014 (EDT)

amazon images

How did you go about setting these up? --DarkShadow (talk) 17:10, 8 September 2014 (EDT)

It should be fairly straightforward. You would basically just need an Amazon Assoc. account and the ability to embed cross-site images.

--M86 (talk) 22:36, 10 September 2014 (EDT)

Link to chipset manufacturer

How do you link to chipset manufacturer? For example, in Compex_WLE900N5-23 there is this line: "For a list of all currently documented QCA chipsets with specifications, see Qualcomm Atheros."

This line is missing for (random examples):

It's currently linked via Template:802dot11 vendor page link.

--M86 (talk) 01:51, 18 August 2014 (EDT)
Not working - I added ZyDAS and refreshed template and product page, still no link/line.
indeed, the template was duplicated for whatever reason..

Another thing, flash/ram/hd capacity is not displayed correctly when javascript is disabled in the web browser - the whole list is displayed instead of just one capacity.

I'm aware, it's the default behavior for those SMW types - will look into options after SMW+MW upgrade

References

I tried to use < ref >something< /ref > to move some references to the bottom of the page to decrease clutter, but it doesn't seem to be parsed by the wiki engine.

mediawikiwiki:Extension:Cite/Cite.php was not enabled, it should work now --M86 (talk) 18:30, 15 July 2014 (EDT)

Could you link wikipedia interwiki to https://en.wikipedia.org/wiki/$1 instead of http? --X64 (talk) 21:04, 17 July 2014 (EDT)

PCB id field for hard drives

Hi, different resellers use PCB id to provide board for data recovery. Try to google for example 100406538. I think this field can be added to HD template. --Fishor (talk) 01:38, 30 June 2014 (EDT)

It's been piled onto the existent entry form + template. .. it should be good enough for right now --M86 (talk) 19:27, 30 June 2014 (EDT)

Powered by

Can you or do you know who can edit the Powered by MediaWiki icon at the bottom of pages to say Powered By Wikidevi so I can add it to my wiki. I have already added the links in the sidebar. thx --DarkShadow (talk) 11:24, 24 June 2014 (EDT)

No, not really. .. otherwise, something other than the MediaWiki logo would probably be the logo here.
Anything would be fine (including a crappy MS Paint made logo) and appreciated if you want to add one though.
--M86 (talk) 14:33, 26 June 2014 (EDT)

Poweredby wikidevi 88x31.png Now to figure out how to get it in the footer with a link. --DarkShadow (talk) 16:40, 26 June 2014 (EDT)

.. ah, whoops
Not sure right off. ... but you may simply need to add it to $wgFooterIcons.
--M86 (talk) 16:50, 26 June 2014 (EDT)

Done at http://wiki.darkhaven.org, I have submitted a request for it to be added at shoutwiki for http://www.techinfodepot.info. Unfortunately the default skin doesn't have the icons in the footer which is why I added it to the sidebar on both, but it will be viable if registered users select a different skin. --DarkShadow (talk) 17:35, 26 June 2014 (EDT)

Two SoCs on one smartphone

Hi, about Samsung GT-I6410. This system can't have two SoCs: OMAP3430 and MSM6246 at same time. May be there are some variants, but they should have at least different FCC ID.

The MSM6246 is the baseband processor / modem - the main SoC / application processor is underneath the KAC00F008M. .. I more or less screwed up the other bits though, it seems to be using S3C6410AH.. --M86 (talk) 02:47, 20 May 2014 (EDT)
According to this page, it is not just baseband processor. It is ARM926EJS with Video decoder/encoder and GPU. I would say, it is application processor. --Fishor (talk) 03:31, 20 May 2014 (EDT)
I would imagine it has considerable additional capability.. but in the context of this particular phone, it does not appear to be the primary processor. --03:46, 20 May 2014 (EDT)
I just grabbed UART log. You was right :) --Fishor (talk) 05:14, 20 May 2014 (EDT)

System hardware specs

Is your wiki hosted, or do you run it. If you run it what specs is your system. shoutwiki is very unpredictable and I am thinking of upgrading my home server because the one I have is slow.DarkShadow (talk) 20:04, 22 April 2014 (EDT)

Well, right now, it's on a VPS (SimpleNode [on Incero] hosted) w/ 2 GB RAM, 2 cores, and reasonably fast IO.
Back in the old(er) days, the site was crammed into a Linode 768 (768 MB RAM, 2 cores, slow IO). It was somewhat usable, but that was certainly more problematic and slower than it is now.
Depending on your current setup (I don't know what you have now), you may have better results tuning your software rather than hardware.
--M86 (talk) 01:27, 23 April 2014 (EDT)

Windows 7 x86, AMD Athlon 64 Proc 3800+ 2.4GHz, 2GB Ram, xxamp, mediawiki 1.22.0, symantec bundle is my current setup. I have setup and running a Win 7 x64 AMD A3-3400 APU 2.69GHz with 4GB ram that I plan on migrating too. What are your suggestions on tweaking or should I migrate first before tweaking? --DarkShadow (talk) 17:22, 28 April 2014 (EDT)

If you are going to dedicate a machine specifically for it (recommended), a server suitable Linux distro on the thing would be best - I would not recommend sticking with a Win7 setup, even with XAMPP
--M86 (talk) 23:06, 28 April 2014 (EDT)

Any particular distro you recommend. I'm not very familiar with linux.

--DarkShadow (talk) 18:59, 29 April 2014 (EDT)
Debian would probably work well - there should be a ton of documentation out there
--M86 (talk) 19:33, 29 April 2014 (EDT)

older talk

User_talk:M86/old_talk/1