DX(G) Wireless drivers for DX.

[dodddummy]

I gave installing 3.2.1 a go on a DX taking the ill advised rout of installing a binary I got from the net. There were a couple of issues so I decided to recover and discovered I'd forgotten to copy the recovery files and lost them.

I also have a DXG so I made a recovery image from that and have restored my DX. I've since installed the top 6 or so hacks plus duokan on it and all seems to be well except for the fact that wireless doesn't work.

I don't use the kindle site so it's not much of an issue but I getting wireless would be nice. My assumption is I just need the wireless files. Are those available for download?

Or is there another way to get wireless working in this case?

If not my plan is to wait until I encounter another one to buy or borrow and recover from that.

[NiLuJe]

Define "wireless".

(FW 3.2.1's SSL support is outdated, rendering it fairly useless).

[knc1]

Backporting firmware from a firmware series 3 device to a firmware series 2 device will not fix your problem(s) with network access.
Even the most recent series 3 firmwares are out of date with changes that have been made to the world's Internet.

If you need reliable network operation, get one of the much more recent firmware series 5 devices.
Note: You can still use your series 2 devices to read books, so you haven't lost all that much.

[dodddummy]

Originally Posted by NiLuJe

Define "wireless".

(FW 3.2.1's SSL support is outdated, rendering it fairly useless).

Meaning when I turn wireless on it tries and then fails and goes back to 'OFF' I think that makes sense because it's a different card than the dxg has and it now has the dxg software and not dx.

[dodddummy]

Originally Posted by knc1

Backporting firmware from a firmware series 3 device to a firmware series 2 device will not fix your problem(s) with network access.

I didn't try series 3 to fix network access issues. I didn't have network access issues until I tried series 3. But that's not the reason I reverted back to 2.5.8.

If you need reliable network operation, get one of the much more recent firmware series 5 devices.
Note: You can still use your series 2 devices to read books, so you haven't lost all that much.

Not sure what you mean by reliable network operation but 2.5.8 has reliable enough for my needs, which are to my home servers. Once in a blue moon I will get something from amazon.

The issue I have isn't with reliable network operation. It's any network operation because I have the dxg drivers on a dx.

[knc1]

Originally Posted by dodddummy

- - - - - -
The issue I have isn't with reliable network operation. It's any network operation because I have the dxg drivers on a dx.

Makes no difference, since there isn't any "driver" as such.
You must be thinking non-*nix world, maybe even "Winmodem" world (which does have drivers).

There might be some differences in a configuration file (a chance of different network providers) but I have all K2 and DX models and they all work with the local provider.

You are misleading yourself with technical terms that do not apply.

All series 2 devices are 3G-GSM only, no wifi, no 2G fall-back.
I have posted here both the technical manual and the user (command) manual for the QualComm modem used.

Do you recall the modem commands established by Hayes?
That is, the: "AT" command set used by "dial up" modems?
Well, guess what, the QualComm modem (in both the Kindles and in your cell 'phone) are just such "dial up" modems.
The original "AT" command set has been extended over the years to accommodate the requirements of digital cell 'phones but it is only an extension, not something new and different.

As far as Linux is concerned, they are just another "AT" command set modem.
Do not think "Internal WinModem", think "External Complete Modem" (even thought it is internal).
So they are controlled by the pppd deamon and its chat program.
Which use the common *nix control files.
The thing to do is compare those on a working/non-working setups -
Your looking for a borked network access number or some other part of the command sequence that got hosed up by indiscriminate file modifiers.

- - - - -

And of course, you have to prevent your servers from requiring TLS, since neither the series 2 nor series 3 firmwares have that ability, they are all SSL only. (Well, Amazon did issue firmware patches when they went to TLS only on their network - but that is another groddy tail/tale)

[dodddummy]

Originally Posted by knc1

Makes no difference, since there isn't any "driver" as such.
You must be thinking non-*nix world, maybe even "Winmodem" world (which does have drivers).
...

There might be some differences in a configuration file (a chance of different network providers) but I have all K2 and DX models and they all work with the local provider.
...
.
think "External Complete Modem" (even thought it is internal).

I'm not new to linux. Just hit my 2 decade mark. Outside of work, it's been my only OS since 2002. So, no, I wasn't thinking of a non *nix system. I do my best not to do that.

But I didn't know these are like external modems. Just knew they are different modems and assume there must be some differences in software/config files to support them. Must be config files or program differences to support the differences in wireless configuration.

I'm happy enough as it is because wireless is the only thing not working and I don't really need it. These days I mostly use it to do a google search when I'm out and about. I'll wait until I get my hands on a dump of another DX. Without a working DX file to compare to I'd never figure out what needs to change.

[knc1]

In the case of the Kindles, the modem-on-a-card looks just like another USB device (which it is).
The mini-pcie interface is not used.


Just google qualcomm (they make the only modem chips worth having) to find any model modem command manual.
By International agreement, 99% of the commands are "standardized" so that any command manual will do.
The other 1% is "vendor reserved" which does not require disclosure.
Even so, they may want you to register and ask you for an NDA before you can down load the manual.


I was able to locate manuals that could be posted here, back in 2012.
Just search the attachments I made to posts that year.

[dodddummy]

Originally Posted by knc1

Just search the attachments I made to posts that year.

You make it sound so easy I'll take a look this weekend.

[knc1]

Originally Posted by dodddummy

You make it sound so easy I'll take a look this weekend.

The "AT" commands are "human readable" in the sense that they use the character set of printable, 7-bit ASCII, not that they spell out anything that makes sense to the reader (without the crib-sheet).

As in:
"ATD19035551212"
Which anyone might guess, but the hundreds of newer ones are a different story.

[PoP]

Originally Posted by knc1

...
As in:
"ATD19035551212"
Which anyone might guess,
...

Guessing is hard

[j.p.s]

Originally Posted by PoP

Guessing is hard

In the US, the phone number 555-1212 in any areacode is guaranteed not to be in service so that it can be used in movies, TV shows, books, and apparently web page templates, without directing harassment to some hapless telephone user.

[PoP]

@j.p.s Interesting, but only 555-0100 through 555-0199 are guaranteed fictitious. 555-1212 seems valid for national use directory assistance.

[j.p.s]

Originally Posted by PoP

@j.p.s Interesting, but only 555-0100 through 555-0199 are guaranteed fictitious. 555-1212 seems valid for national use directory assistance.

Yeah, I'm behind the times and misremembered to boot.

555-1212 has always been directory assistance and the rest were fake numbers.

I didn't know the number of fakes was reduced. I feel sorry for whoever has been stuck with them as their phone number.

[knc1]

Originally Posted by j.p.s

In the US, the phone number 555-1212 in any areacode is guaranteed not to be in service so that it can be used in movies, TV shows, books, and apparently web page templates, without directing harassment to some hapless telephone user.

Originally Posted by PoP

@j.p.s Interesting, but only 555-0100 through 555-0199 are guaranteed fictitious. 555-1212 seems valid for national use directory assistance.

Once upon a time (in the USA, there was a national plan ...) <area code>+555-1212 was intended to be information (or dead - depended on carrier).

And then came along the Bell System divestiture ...
Followed by the need to use the full ten digits, which created a bunch of usable numbers by tossing the plan out of the window.

I was on one of the divestiture planning committees, BUT

I had nothing at all to do with the "throw baby out with bathwater" solution to changing the national numbering plan.
(I was hiding in a culvert, under a bridge, as far from any type of telephone service as I could get when that worthless idea was adopted.)