Kyocera KR1 - Automatic Reconnect problem?

acorda · EVDO Newbie Joined: 01 Mar 2006 Posts: 8

Hi!
Just received my KR1 and KPC650 card at the beginning of Feb. and
after some short term use in the beginning of the month, I am finally
beginning to use them heavily. Initially everything was fine, but in
the past week, I have had the KR1 lock up on me 4 times.... had to
power-down reset it to get the connection back. My signal level
is consistantly between 4-5 bars (~76dbm) and I live about 2 miles
from the tower, so I don't think signal level is a problem. I'm also
stuck in 1xRTT land (EVDO hasn't reached us yet). Symptoms
are:
WAN light goes out, status light goes red, KPC650 starts blinking slowly.

If I check the status page, it shows a 0.0.0.0 for IP address/DNS server
and gateway.
Trying to manually reconnect results in a "Connection Failed"
Message. (BTW, I am waiting for the connect time-out to complete,
and then some).
Going through a disconnect/connect cycle results in the same thing.
Waiting for an automatic reconnect is fruitless (waited ~20 Minutes...
no luck).

I did notice that during my manual reconnect attempts, the KR1
seems to be going through a reboot-cycle (the light pattern seems
to match the power-up reboot cycle) but, unlike the power-up
reboot cycle, the light on the KPC650 continues blinking slowly,
instead of going solid green like it does during a power-down reset.
(To the hardware hacker in me, this indicates that the KPC650 isn't
being reset by the KR1, but that's just guesswork on my part)

In all cases, power-cycling seems to bring the system back to
life.

Anyone have any idea what's going on here? Any way to
isolate the problem to the KPC650, KR1 (or even the verizon tower?)

I'm open to suggestions... I need to get this fixed since I intend to
use dyndns to access my home system from remote locations, and
having the KR1/KPC650 randomly lock up without reconnecting
makes this approach non-workable.

Thanks!
-al-

ScottS · Posted: Thu Mar 02, 2006 7:32 am Post subject:

FYI, I have the same setup as Acorda and am experiencing the same issue severa times a day. Since I work out of my house it has only been an inconvenience.

I have the Inteligain amp and Arc antenna and typically have a signal strength of -82 to -90. I also tend to bounce between 1xRTT and EVDO depending on the time of day. Never had this issue when the KPC650 was in my laptop.

tz1 · Posted: Thu Mar 02, 2006 7:40 am Post subject:

first, reseat the EVDO card.

Someone is going to ask this: enable logging (I think it is in the status or tools section), and watch it when the problem happens, and post (without editing it) here.

ScottS · Posted: Thu Mar 02, 2006 7:53 am Post subject:

I have already tried the card reseating and even enabled the log, although I forgot I had. I just cleared the log so that I can capture a clean log when it happens again.

As always thanks for the help!

ScottS · Posted: Thu Mar 02, 2006 8:36 am Post subject:

I just happened, internet connection dies, KR1 appears to reboot but eventually stops with Red Status LED. Here is the log dump after the lockup and before I power cycled:

Mar 2 09:00:26 (none) syslog.info -- MARK --
Mar 2 09:20:26 (none) syslog.info -- MARK --
Mar 2 09:26:03 (none) daemon.info pppd[3674]: Terminating on signal 15.
Mar 2 09:26:03 (none) user.warn klogd: Delete port 0 from peripheral port set. (0xc0)
Mar 2 09:26:03 (none) user.warn klogd: Total WLAN/WDS links: 1
Mar 2 09:26:03 (none) user.warn klogd: Device ppp's main Link ID 2 unregistered.
Mar 2 09:26:18 (none) daemon.notice pppd[5507]: pppd 2.4.1 started by root, uid 0
Mar 2 09:26:18 (none) daemon.warn pppd[5507]: Couldn't restrict write permissions to /dev/ttyUSB0: Read-only file system
Mar 2 09:26:49 (none) daemon.err pppd[5507]: Connect script failed
Mar 2 09:26:50 (none) daemon.info pppd[5507]: Exit.

Mackieman · EVDO Junkie Joined: 31 Oct 2005 Posts: 451

Yeah, I've seen that happen once in a while. Often it is due to signal coverage issues. Sometimes the router just gets into a bad state and the simplest fix is to powercycle it; it should come back up just fine.

mrg3013 · EVDO Fledgling Joined: 25 Oct 2005 Posts: 11

Mackieman · EVDO Junkie Joined: 31 Oct 2005 Posts: 451

There's no doubt it's a software bug. And no, I don't think it has anything to do with your service or service provider. The issue is how reproducible is that issue and can exact steps be defined. Moreover, is it limited to specific units or is it a problem experienced by all users? Finally, if a fix can be identified, what other risk does it introduce?

Anyway, I'll keep an eye on it and do post any updates you have.

acorda · EVDO Newbie Joined: 01 Mar 2006 Posts: 8

Ok, folks, here is a log file I finally managed to capture of the connection failure.

For the Kyocera/D-link folks out there who might need the revision, etc,
The KR1 is model TXRTR10004, P/N: CV90-P8060-01, S/N: B2DS161000183

Please note the following conditions. The KR1 has it's WiFi turned off, and there
are no other WiFi devices in the house powered up. When the failure happens, it
usually happens 2-3 hours after the KR1 is powered up. Signal levels are the same
as in my previous posting (~76dbm (4-5bars)), I am ~2 miles from the Tower.
This is a solid 1xRTT neighborhood (no EVDO bouncing in/out)
KR1 Status is: 0.0.0.0 for all IP addessses downloaded from the KPC650.
The KPC650 blue led is always _slowly_blinking (does this mean it's dormant?).
The following process seems to repeat itself:

KR1 clears it's log file, Status led is Orange, Wan and WLAN leds go green.
At this point the KR1 is unreachable until the WAN and WLAN leds both go out, and
The following log entries appear:

[My annotations are in brackets]

Dec 31 19:00:14 (none) user.warn klogd: bInterfaceNumber = 01
Dec 31 19:00:14 (none) user.warn klogd: bAlternateSetting = 00
Dec 31 19:00:14 (none) user.warn klogd: bNumEndpoints = 02
Dec 31 19:00:14 (none) user.warn klogd: bInterface Class:SubClass:Protocol = ff:ff:ff
Dec 31 19:00:14 (none) user.warn klogd: iInterface = 03
Dec 31 19:00:14 (none) user.warn klogd: Endpoint:
Dec 31 19:00:14 (none) user.warn klogd: bLength = 7
Dec 31 19:00:14 (none) user.warn klogd: bDescriptorType = 05
Dec 31 19:00:14 (none) user.warn klogd: bEndpointAddress = 84 (in)
Dec 31 19:00:13 (none) user.warn klogd: MaxPower = 100mA
Dec 31 19:00:13 (none) user.warn klogd:
Dec 31 19:00:13 (none) user.warn klogd: Interface: 0
Dec 31 19:00:13 (none) user.warn klogd: Alternate Setting: 0
Dec 31 19:00:13 (none) user.warn klogd: bLength = 9
Dec 31 19:00:13 (none) user.warn klogd: bDescriptorType = 04
Dec 31 19:00:13 (none) user.warn klogd: bInterfaceNumber = 00
Dec 31 19:00:13 (none) user.warn klogd: bAlternateSetting = 00
Dec 31 19:00:13 (none) user.warn klogd: bNumEndpoints = 03
Dec 31 19:00:13 (none) user.warn klogd: bInterface Class:SubClass:Protocol = ff:ff:ff
Dec 31 19:00:14 (none) user.warn klogd: iInterface = 03
Dec 31 19:00:14 (none) user.warn klogd: Endpoint:
Dec 31 19:00:14 (none) user.warn klogd: bLength = 7
Dec 31 19:00:14 (none) user.warn klogd: bDescriptorType = 05
Dec 31 19:00:14 (none) user.warn klogd: bEndpointAddress = 81 (in)
Dec 31 19:00:14 (none) user.warn klogd: bmAttributes = 03 (Interrupt)
Dec 31 19:00:14 (none) user.warn klogd: wMaxPacketSize = 0010
Dec 31 19:00:14 (none) user.warn klogd: bInterval = 80
Dec 31 19:00:14 (none) user.warn klogd: Endpoint:
Dec 31 19:00:14 (none) user.warn klogd: bLength = 7
Dec 31 19:00:14 (none) user.warn klogd: bmAttributes = 02 (Bulk)
Dec 31 19:00:14 (none) user.warn klogd: wMaxPacketSize = 0040
Dec 31 19:00:14 (none) user.warn klogd: bInterval = 00
Dec 31 19:00:14 (none) user.warn klogd: Endpoint:
Dec 31 19:00:14 (none) user.warn klogd: bLength = 7
Dec 31 19:00:14 (none) user.warn klogd: bDescriptorType = 05
Dec 31 19:00:14 (none) user.warn klogd: bEndpointAddress = 04 (out)
Dec 31 19:00:14 (none) user.warn klogd: bmAttributes = 02 (Bulk)
Dec 31 19:00:14 (none) user.warn klogd: wMaxPacketSize = 0040
Dec 31 19:00:14 (none) user.warn klogd: bInterval = 00
Dec 31 19:00:14 (none) user.debug klogd: usb.c: kusbd: /sbin/hotplug add 2
Dec 31 19:00:14 (none) user.warn klogd: bInterval = 80
Dec 31 19:00:14 (none) user.warn klogd: Endpoint:
Dec 31 19:00:14 (none) user.warn klogd: bLength = 7
Dec 31 19:00:14 (none) user.warn klogd: bDescriptorType = 05
Dec 31 19:00:14 (none) user.warn klogd: bEndpointAddress = 82 (in)
Dec 31 19:00:14 (none) user.warn klogd: bmAttributes = 02 (Bulk)
Dec 31 19:00:14 (none) user.warn klogd: wMaxPacketSize = 0040
Dec 31 19:00:14 (none) user.warn klogd: bInterval = 00
Dec 31 19:00:14 (none) user.warn klogd: Endpoint:
Dec 31 19:00:14 (none) user.warn klogd: bLength = 7
Dec 31 19:00:14 (none) user.warn klogd: bDescriptorType = 05
Dec 31 19:00:14 (none) user.warn klogd: bEndpointAddress = 02 (out)
Dec 31 19:00:14 (none) user.warn klogd: bmAttributes = 02 (Bulk)
Dec 31 19:00:14 (none) user.warn klogd: wMaxPacketSize = 0040
Dec 31 19:00:14 (none) user.warn klogd: bInterval = 00
Dec 31 19:00:14 (none) user.warn klogd:
Dec 31 19:00:14 (none) user.warn klogd: Interface: 1
Dec 31 19:00:14 (none) user.warn klogd: Alternate Setting: 0
Dec 31 19:00:14 (none) user.warn klogd: bLength = 9
Dec 31 19:00:14 (none) user.warn klogd: bDescriptorType = 04
Dec 31 19:00:14 (none) user.info klogd: usb.c: new USB bus registered, assigned bus number 3
Dec 31 19:00:14 (none) user.warn klogd: IRR(1)=f0040000
Dec 31 19:00:14 (none) user.warn klogd: write minterval 27782edf swap df2e7827
Dec 31 19:00:14 (none) user.warn klogd: read fminterval 27782edf swap df2e7827
Dec 31 19:00:14 (none) user.warn klogd: [ED]usb.c ::2278 :: gettime : 946684807.630000 ( sec.microsec )
Dec 31 19:00:14 (none) user.warn klogd: [ED]usb.c ::2287 :: gettime : 946684807.650000 ( sec.microsec )
Dec 31 19:00:14 (none) user.debug klogd: usb.c: kusbd policy returned 0xfffffffe
Dec 31 19:00:14 (none) user.debug klogd: usb.c: kusbd: /sbin/hotplug add 2
Dec 31 19:00:14 (none) user.debug klogd: usb.c: kusbd policy returned 0xfffffffe
Dec 31 19:00:14 (none) user.warn klogd: [ED]usb.c ::2292 :: gettime : 946684807.710000 ( sec.microsec )
Dec 31 19:00:14 (none) user.debug klogd: usb.c: kmalloc IF 8115d400, numif 1
Dec 31 19:00:14 (none) user.debug klogd: usb.c: new device strings: Mfr=0, Product=2, SerialNumber=1
Dec 31 19:00:14 (none) user.debug klogd: usb.c: USB device number 1 default language ID 0x0
Dec 31 19:00:14 (none) user.info klogd: Product: USB OHCI Root Hub
Dec 31 19:00:14 (none) user.info klogd: SerialNumber: bd000000
Dec 31 19:00:14 (none) user.info klogd: hub.c: USB hub found
Dec 31 19:00:14 (none) user.info klogd: hub.c: 1 port detected
Dec 31 19:00:14 (none) user.warn klogd: 1 port detected<7>hub.c: standalone hub
Dec 31 19:00:14 (none) user.debug klogd: hub.c: ganged power switching
Dec 31 19:00:14 (none) user.debug klogd: hub.c: individual port over-current protection
Dec 31 19:00:14 (none) user.debug klogd: hub.c: Port indicators are not supported
Dec 31 19:00:14 (none) user.debug klogd: hub.c: power on to power good time: 4ms
Dec 31 19:00:14 (none) user.debug klogd: hub.c: hub controller current requirement: 0mA
Dec 31 19:00:14 (none) user.debug klogd: hub.c: port removable status: F
Dec 31 19:00:14 (none) user.debug klogd: hub.c: local power source is good
Dec 31 19:00:14 (none) user.debug klogd: hub.c: no over-current condition exists
Dec 31 19:00:14 (none) user.info klogd: hub.c: : FILL_INT_URB(hub_irq)
Dec 31 19:00:14 (none) user.debug klogd: hub.c: enabling power on all ports
Dec 31 19:00:14 (none) user.debug klogd: usb.c: hub driver claimed interface 8115d400
Dec 31 19:00:14 (none) user.debug klogd: usb.c: kusbd: /sbin/hotplug add 1
Dec 31 19:00:14 (none) user.debug klogd: usb.c: kusbd policy returned 0xfffffffe
Dec 31 19:00:14 (none) user.warn klogd: ..:: dump ohci_reg ( un_parsed && using readl )::..
Dec 31 19:00:14 (none) user.warn klogd: OHCI_Reg | MSB(31) LSB
Dec 31 19:00:14 (none) user.emerg klogd: 4> ==============================
Dec 31 19:00:14 (none) user.warn klogd: HC revision : 0x00000010
Dec 31 19:00:14 (none) user.warn klogd: HC control : 0x0000008f
Dec 31 19:00:14 (none) user.warn klogd: HC cmdstatus : 0x00000000
Dec 31 19:00:14 (none) user.warn klogd: HC intrstatus : 0x00000044
Dec 31 19:00:14 (none) user.warn klogd: HC intrenable : 0x80000013
Dec 31 19:00:14 (none) user.warn klogd: HC intrdisable: 0x80000013
Dec 31 19:00:14 (none) user.warn klogd: HC intrstatus : 0x00000044
Dec 31 19:00:14 (none) user.warn klogd: HC intrenable : 0x80000013
Dec 31 19:00:14 (none) user.warn klogd: HC intrdisable: 0x80000013
Dec 31 19:00:14 (none) user.warn klogd: HC hcca : 0x0115b000
Dec 31 19:00:14 (none) user.warn klogd: HC ed_periodcurrent : 0x00000000
Dec 31 19:00:14 (none) user.warn klogd: HC ed_controlhead : 0x00000000
Dec 31 19:00:14 (none) user.warn klogd: HC ed_controlcurrent: 0x00000000
Dec 31 19:00:14 (none) user.warn klogd: HC ed_bulkhead : 0x00000000
Dec 31 19:00:14 (none) user.warn klogd: HC ed_bulkcurrent : 0x00000000
Dec 31 19:00:14 (none) user.warn klogd: HC donehead : 0x00000000
Dec 31 19:00:14 (none) user.warn klogd: HC fminterval : 0x27782edf
Dec 31 19:00:14 (none) user.warn klogd: HC fmremaining : 0x00000a4e
Dec 31 19:00:14 (none) user.warn klogd: HC fmnumber : 0x00000158
Dec 31 19:00:14 (none) user.warn klogd: HC periodicstart : 0x00002a2f
Dec 31 19:00:14 (none) user.warn klogd: HC lsthresh : 0x00000628
Dec 31 19:00:14 (none) user.warn klogd: HC roothub.a : 0x02000a01
Dec 31 19:00:14 (none) user.warn klogd: HC roothub.b : 0x00000002
Dec 31 19:00:14 (none) user.warn klogd: HC roothub.status : 0x00000000
Dec 31 19:00:14 (none) user.warn klogd: HC roothub.portstatus: 0x00000101
Dec 31 19:00:14 (none) user.warn klogd: .... dump ohci_reg ( un_parsed && using readl )....
Dec 31 19:00:14 (none) user.info klogd: usb.c: registered new driver serial
Dec 31 19:00:14 (none) user.info klogd: usbserial.c: USB Serial support registered for Generic
Dec 31 19:00:14 (none) user.info klogd: usbserial.c: Generic converter detected
Dec 31 19:00:14 (none) user.info klogd: usbserial.c: Generic converter now attached to ttyUSB0 (or usb/tts/0 for devfs)
Dec 31 19:00:14 (none) user.debug klogd: usb.c: serial driver claimed interface 8116ba70
Dec 31 19:00:14 (none) user.info klogd: usbserial.c: Generic converter detected
Dec 31 19:00:14 (none) user.info klogd: usbserial.c: Generic converter now attached to ttyUSB1 (or usb/tts/1 for devfs)
Dec 31 19:00:14 (none) user.debug klogd: usb.c: serial driver claimed interface 8116ba88
Dec 31 19:00:14 (none) user.info klogd: usbserial.c: USB Serial Driver core v1.4
Dec 31 19:00:14 (none) user.info klogd: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Dec 31 19:00:14 (none) user.info klogd: Initializing Cryptographic API
Dec 31 19:00:14 (none) user.info klogd: NET4: Linux TCP/IP 1.0 for NET4.0
Dec 31 19:00:14 (none) user.info klogd: IP Protocols: ICMP, UDP, TCP, IGMP
Dec 31 19:00:14 (none) user.info klogd: IP: routing cache hash table of 512 buckets, 4Kbytes
Dec 31 19:00:14 (none) user.info klogd: TCP: Hash tables configured (established 4096 bind 8192)
Dec 31 19:00:14 (none) user.info klogd: GRE over IPv4 tunneling driver
Dec 31 19:00:14 (none) user.info klogd: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Dec 31 19:00:14 (none) user.notice klogd: ds: no socket drivers loaded!
Dec 31 19:00:14 (none) user.warn klogd: FAT: bogus logical sector size 16912
Dec 31 19:00:14 (none) user.warn klogd: FAT: bogus logical sector size 16912
Dec 31 19:00:14 (none) user.notice klogd: ds: no socket drivers loaded!
Dec 31 19:00:14 (none) user.warn klogd: FAT: bogus logical sector size 16912
Dec 31 19:00:14 (none) user.warn klogd: FAT: bogus logical sector size 16912
Dec 31 19:00:14 (none) user.err klogd: kmod: failed to exec /sbin/modprobe -s -k nls_iso8859-1, errno = 2
Dec 31 19:00:14 (none) user.warn klogd: VFS: Mounted root (romfs filesystem) readonly.
Dec 31 19:00:14 (none) user.info klogd: Freeing unused kernel memory: 84k freed
Dec 31 19:00:14 (none) user.warn klogd: IRR(4)=f0c40000
Dec 31 19:00:14 (none) user.info klogd: wlan: 0.8.4.2 (Atheros/multi-bss)
Dec 31 19:00:14 (none) user.info klogd: wlan: mac acl policy registered
Dec 31 19:00:14 (none) user.info klogd: ath_hal: 0.9.16.1 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
Dec 31 19:00:14 (none) user.info klogd: ath_rate_atheros: Version 2.0.1
Dec 31 19:00:14 (none) user.warn klogd: Copyright (c) 2001-2004 Atheros Communications, Inc, All Rights Reserved
Dec 31 19:00:14 (none) user.info klogd: ath_pci: 0.9.4.5 (Atheros/multi-bss)
Dec 31 19:00:14 (none) user.warn klogd: rtlpci_read_config_word addr=bbd40000 where=6
Dec 31 19:00:14 (none) user.warn klogd: [ED]touch PCI:rtlpci_read_config_word:745:jiffies(1032) addr(0x1bd40000)
Dec 31 19:00:14 (none) user.warn klogd: [ED]touch PCI:rtlpci_read_config_byte:680:jiffies(1033) addr(0x1bd40000)
Dec 31 19:00:14 (none) user.warn klogd: [ED]touch PCI:rtlpci_read_config_byte:680:jiffies(1034) addr(0x1bd40000)
Dec 31 19:00:14 (none) user.warn klogd: [ED]touch PCI:rtlpci_write_config_word:916:jiffies(1035) addr(0x1bd40000)
Dec 31 19:00:14 (none) user.warn klogd: pcibios_enable_resources: already enabled when device probed.
Dec 31 19:00:14 (none) user.warn klogd: [ED]touch PCI:rtlpci_read_config_byte:680:jiffies(1037) addr(0x1bd40000)
Dec 31 19:00:14 (none) user.warn klogd: [ED]touch PCI:rtlpci_write_config_byte:858:jiffies(1038) addr(0x1bd40000)
Dec 31 19:00:14 (none) user.warn klogd: rtlpci_read_config_word addr=bbd40000 where=4
Dec 31 19:00:14 (none) user.warn klogd: [ED]touch PCI:rtlpci_read_config_word:745:jiffies(1039) addr(0x1bd40000)
Dec 31 19:00:14 (none) user.warn klogd: pcibios_set_master: already done when device probed.
Dec 31 19:00:14 (none) user.warn klogd: [ED]touch PCI:rtlpci_read_config_dword:806:jiffies(1042) addr(0x1bd40000)
Dec 31 19:00:14 (none) user.warn klogd: [ED]touch PCI:rtlpci_read_config_byte:680:jiffies(1043) addr(0x1bd40000)
Dec 31 19:00:14 (none) user.warn klogd: wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
Dec 31 19:00:14 (none) user.warn klogd: wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
Dec 31 19:00:14 (none) user.warn klogd: wifi0: mac 7.8 phy 0.0 radio 5.6
Dec 31 19:00:14 (none) user.warn klogd: wifi0: Use hw queue 1 for WME_AC_BE traffic
Dec 31 19:00:14 (none) user.warn klogd: wifi0: Use hw queue 0 for WME_AC_BK traffic
Dec 31 19:00:14 (none) user.warn klogd: wifi0: Use hw queue 2 for WME_AC_VI traffic
Dec 31 19:00:14 (none) user.warn klogd: wifi0: Use hw queue 3 for WME_AC_VO traffic
Dec 31 19:00:14 (none) user.warn klogd: wifi0: Use hw queue 8 for CAB traffic
Dec 31 19:00:14 (none) user.warn klogd: wifi0: Use hw queue 9 for beacons
Dec 31 19:00:14 (none) user.info klogd: wifi0: Atheros 5212: mem=0x1bf00000, irq=5
Dec 31 19:00:14 (none) user.warn klogd: IRR(3)=f3c40000
Dec 31 19:00:14 (none) user.warn klogd: rtl8651_user_pid set to 41
Dec 31 19:00:14 (none) user.warn klogd: id 8 port 90,[1]= eth0 [2] = eth0, 1695
Dec 31 19:00:14 (none) user.warn klogd: Bring up ext port 7..
Dec 31 19:00:14 (none) user.warn klogd: rtl8651_user_pid set to 41
Dec 31 19:00:14 (none) user.warn klogd: id 8 port 90,[1]= eth0 [2] = eth0, 1695
Dec 31 19:00:14 (none) user.warn klogd: Bring up ext port 7..
Dec 31 19:00:14 (none) user.warn klogd: id 9 port 4f,[1]= eth1 [2] = eth1, 1695
Dec 31 19:00:14 (none) user.warn klogd: Bring up ext port 6..
Dec 31 19:00:14 (none) user.warn klogd: Rx shift=10002
Dec 31 19:00:14 (none) user.warn klogd: init_flash_info: I28F128J3A
Dec 31 19:00:14 (none) user.warn klogd: init_flash_info: I28F128J3A
Dec 31 19:00:14 (none) user.warn klogd:
Dec 31 19:00:14 (none) user.warn klogd: Set IGMP Default Upstream interface (eth0) ... SUCCESS!!
Dec 31 19:00:14 (none) user.warn klogd: ##############################################################
Dec 31 19:00:14 (none) user.warn klogd: # MADWIFI )RC5(watchDog) version :: Jan 16 2006 11:04:19 #
Dec 31 19:00:14 (none) user.warn klogd: ##############################################################
Dec 31 19:00:14 (none) user.warn klogd: Entry ath_vap_create(), linkNum=0
Dec 31 19:00:14 (none) user.warn klogd: Reserve port 6 for peripheral device use. (0x40)
Dec 31 19:00:14 (none) user.warn klogd: Total WLAN/WDS links: 1
Dec 31 19:00:14 (none) user.warn klogd: Device ath0 on vlan ID 9 using Link ID 1. Loopback/Ext port is 6

[The following log entries repeat approx. 6 times, with each repeat timing out after about 1 minute,
until the router seems to do a reset, at which time the entire process (from the beginning of this log file) repeats]

Dec 31 19:00:31 (none) daemon.notice pppd[84]: pppd 2.4.1 started by root, uid 0
Dec 31 19:00:31 (none) daemon.warn pppd[84]: Couldn't restrict write permissions to /dev/ttyUSB0: Read-only file system
Dec 31 19:01:02 (none) daemon.err pppd[84]: Connect script failed

[Note that I have seen a few variations on this, having to do with USB connect failures
rather than pppd failures during the repetition process (in this case, the status Led
remains unlit, rather than turning orange , but ~90% of the time, the failure seems to be
a pppd failure.]

This is beginning to look like a major problem to me... I can count on
the KR1 failing regularly, which is _not_ a good thing, I do, of course realize
that is is a brand-new shiny product with associated growing pains, and
Rev 1.0 firmware. I have done enough embedded hardware design to understand
the problems inherent in debugging an intermittent like this, but from what I've seen
on the forum, I'm not the only one experiencing this failure. I would have to second
the suggestion by the previous poster that this reminds me of what happened when
we overwrote the bounds of an array, or had a pointer go bad in our embedded
designs. I will be happy to provide whatever info I can to the Kyocera/D-link
folks who have been valiant and gracious enough to visit this forum and help
us out. You may be our only hope...

And before anyone suggests it... yes, I tried calling the tech support number
at the Kyocera site, which routed me to D-link tech support. The support
engineer was barely understandable (poor english(2nd language) skills. At
first he didn't believe it was a D-link product. Then he wanted to help me "configure" it
(you could tell he was reading something from a screen about a product
with which he had no familiarity) I politely told him I had some pressing business
and that I'd call back later (no point in ruining his day also).

Al

acorda · EVDO Newbie Joined: 01 Mar 2006 Posts: 8

An update on my problems with the KR1 hanging during automatic
reconnect...

I tried calling the Kyocera (Actually, D-Link) support number again
and talked to the tech. on duty. He indicated that before he could
redirect me to level-2 support, I needed to do two things... First
try a hardware reset (using the button on the back of the unit). If
this did not work, He said I should re-flash the firmware using the
version posted on the KR1/D-link support website (shipping firmware
version 1.00).

Well, sure enough, the hardware reboot didn't rectify matters... The
unit hung after about 6 hours after reboot. I then did a power-off
reset, and reflashed the firmware using the instructions on the
D-link site. The unit never came back to life after the firmware
reflash... It is now a brick (a _colorful_ brick, with all the lights
stuck on, but a brick nonetheless).

Now, before anyone asks... no, I did not re-flash via WiFi... I used
a cat-5 twisted pair cable to port 1 on the router. The system
I used to execute the flash was a Dell Latitude D600 with the latest
version of Windows XP (all patches/updates applied).

One issue that confused me slighly was that the file on the D-link
website is a .zip file containg the firmware file (with a .bix extension).
I've never heard of .bix before, so I assumed it was a compressed
format of some type that the KR1 would understand. The Firmware
update Readme on the D-link site only refers to a .bin or .dlf file... no
mention of .bix.
I also assumed that the KR1 would be smart enough to detect a bad
firmware flash file and ignore it (most modern hardware that
allows for reflash usually checks a bitstream at the start of the
firmware file to see if it recognizes the file, and ignores it otherwise)
This may have been a bad assumption on my part.

In summary, either:

(1) my KR1 was hosed initially in a manner which precluded
a sucessful firmware update..

(2) The firmware on the D-link site is bad, or...

(3) A .bix file needs some sort of processing/expansion before it
should be flashed into the KR1. If the above is the case, it
indicates that the KR1 does _no_ validation check on the firmware
file it uses as a source for reflash.

In either case, another call to the Kyocera folks got me an RA number,
and the router is on the way back to them (with a replacement coming
soon). I am posting this as a precautionary tale directed to anyone
who is contemplating flashing the firmware on a KR1... I still don't know
the proper procedure for re-flashing the KR1, but you can be d*mn
certain that I'm going to wait until someone else tries it (successfully)
before I give it another shot.

-al-