DX(G) Wireless drivers for DX. - Page 2

dodddummy · 02-06-2019, 04:51 AM

Now I wonder if the reason I can't connect is that the date is off. I've changed it so that it shows the current date with the date command but it doesn't stick. After every reboot, the date changes to august 2019.

knc1 · 02-06-2019, 09:45 AM

Quote:

Originally Posted by dodddummy

Now I wonder if the reason I can't connect is that the date is off. I've changed it so that it shows the current date with the date command but it doesn't stick. After every reboot, the date changes to august 2019.

Linux has two clocks.
You are only setting the software clock.
You need to set the hardware clock, since that is the one which survives a reboot.

There are standard commands available on the Kindle for doing that, plus a KUAL extension. The KUAL extension does not depend on the cell tower clock but instead, the International Time Server Network.

dodddummy · 02-09-2019, 08:28 PM

Must have forgot to set hwclock. Reinstalling mkk resolved the issue with kual not launching.

knc1 · 02-09-2019, 09:21 PM

Quote:

Originally Posted by dodddummy

Must have forgot to set hwclock. Reinstalling mkk resolved the issue with kual not launching.

Did it make any difference with the connections problem?
Everything sent 3G is proxied by Amazon, a wrong date **might** have been the cause of that problem also.

dodddummy · 02-10-2019, 05:31 AM

Quote:

Originally Posted by knc1

Did it make any difference with the connections problem?
Everything sent 3G is proxied by Amazon, a wrong date **might** have been the cause of that problem also.

Still doesn't connect. Now that everything else is working again, I'll tackle that next weekend.

dodddummy · 02-12-2019, 06:42 AM

I discovered the reason the clock is off. It wasn't that I forgot to set hwclock. It changes to sometime in Aug 2019 when I turn wireless on. So if I want to use kual I have to not attempt to use wireless.

Still not much of an issue because I usually am in duokan and don't need wireless on this device.

I think I'm done fiddling with this for now.

knc1 · 02-12-2019, 06:58 AM

Quote:

Originally Posted by dodddummy

I discovered the reason the clock is off. It wasn't that I forgot to set hwclock. It changes to sometime in Aug 2019 when I turn wireless on. So if I want to use kual I have to not attempt to use wireless.

Still not much of an issue because I usually am in duokan and don't need wireless on this device.

I think I'm done fiddling with this for now.

We do not support Duokan at this site, nor the things which it does to the Amazon firmware.
You will have to get your support from the Duokan project, not here.
Lots of luck with that.

dodddummy · 02-12-2019, 06:15 PM

Quote:

Originally Posted by knc1

We do not support Duokan at this site, nor the things which it does to the Amazon firmware.
You will have to get your support from the Duokan project, not here.
Lots of luck with that.

Didn't mean to give the impression I'm looking for duokan support. And this is the behavior without duokan.

I do think I have an idea of how I created the issue though. Will test that out.

knc1 · 02-12-2019, 06:37 PM

Quote:

Originally Posted by dodddummy

Didn't mean to give the impression I'm looking for duokan support. And this is the behavior without duokan.

I do think I have an idea of how I created the issue though. Will test that out.

One of the beauties of Duokan is that it does not need to be running, only installed.

If you "normally run" Duokan, then Duokan is installed, even when not running it.

(The Duokan Project did not create an independent, bootable, system, they only hung a bag of garbage on the Amazon system. They also intentional created it to interfere with both our add-ins and the Amazon original.)

Note: The Duokan un-install process does not cleanly un-install the Duokan add-in nor correct all of the damage done to the Amazon system.

Included in our idea of "support of Duokan" is wasting our time, fixing how they are screwing up the standard Amazon system.

Let me translate:
You are on your own, with only the help you can get from the Duokan project.

dodddummy · 02-13-2019, 08:10 AM

Quote:

Originally Posted by knc1

If you "normally run" Duokan, then Duokan is installed, even when not running it.

To be clear Duokan is NOT installed. I do normally run Duokan but since I'm rebuilding this from a dxg base image, I didn't install it or anything else yet because I want to resolve the date issue because it's intefering with kual.

At this point I have kual, mkk, jb, and the screensaver hack installed.

I'm a big boy and not afraid to be 'on my own', but, duokan is not on this device.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
drivers windows 7	shotta7	Kobo Reader	4	11-24-2015 04:21 PM
USB Drivers could not be installed....	Psyke	Kobo Reader	0	03-16-2011 11:02 PM
Kobo Wifi Drivers	MikeLC	Kobo Reader	5	01-27-2011 09:19 AM
iLiad cannot connect to the net either wire,wireless (no encription) or wireless(with encr)	tely	iRex	5	04-24-2010 09:27 PM
Still no Vista x64 drivers ?	Lord KiRon	Sony Reader	16	08-08-2008 08:34 AM

02-06-2019, 04:51 AM	#16
dodddummy Member Posts: 12 Karma: 10 Join Date: Dec 2011 Device: KOBO	Now I wonder if the reason I can't connect is that the date is off. I've changed it so that it shows the current date with the date command but it doesn't stick. After every reboot, the date changes to august 2019.

02-09-2019, 08:28 PM	#18
dodddummy Member Posts: 12 Karma: 10 Join Date: Dec 2011 Device: KOBO	Must have forgot to set hwclock. Reinstalling mkk resolved the issue with kual not launching.

02-12-2019, 06:42 AM	#21
dodddummy Member Posts: 12 Karma: 10 Join Date: Dec 2011 Device: KOBO	I discovered the reason the clock is off. It wasn't that I forgot to set hwclock. It changes to sometime in Aug 2019 when I turn wireless on. So if I want to use kual I have to not attempt to use wireless. Still not much of an issue because I usually am in duokan and don't need wireless on this device. I think I'm done fiddling with this for now.