What does the lid have to do with it?

[SHEEPMAN!]

Mint 17.1
cutecom sees /dev/ttyS2 (note: click the hardware box)
gpsd /dev/ttyS2
xgps looks right but no words OR SATS.
CLOSE AND RE-OPEN LID AND XGPS IS LOCKED ON, ALSO THE GPSD IS SCROLLING FASTER. (gpsd -n -N D 5 /dev/ttyS2)

Mk3 CF-30KTPAXAM doesn't matter....same on mark 2.

So what is the shutdown doing?

[Shawn]

It can't work with screen flicker...

[SHEEPMAN!]

Maybe.....they must/may be interconnected.

Same caddy/drive in Mk 1.....somethings happening (not happening)here too.

The lid trick does not work.

O.K. back to the MK3 next, set to internal monitor and test.

[SHEEPMAN!]

MK 3:
Bios settings:
1. Internal Monitor-----Usually none but occasionally I get 4 Sats-------------close re-open and I have 12 or more.
2. GPS set to on......./dev/ttyS2 still works.
----------------------------------------------------------------------------------------------------------------------------
Terminal
3. dpkg-reconfigure gpsd......Serial to on USB to off....no letters....
4. xgps.................if no SATS then close re-open.

This only happens with Mint 17 / 17.1 and any other OS that has screen flicker (not fully tested)

I have a ewe lambing.

See ya.

[Shawn]

I know very little about the underpinnings of Linux.
The video flicker issue going away with closing and opening the lid is somewhat 'understandable" Resetting the driver or a memory issue.
The GPS issue is bizarre. If is was a driver, it would not work at all. It can't be halfway enabled.
If it had the incorrect serial/usb port or incorrect baud, it would not work at all....

The only thing that could hinder but not disable would be with the antenna.
Is this factory GPS antenna?
Is the factory antenna active or passive?
Active means it has voltage going to it for an amplifier built into the ceramic patch.
If it is active, for some reason the antenna amplifier does not get power until the lid is closed and opened.

I saw similar results when I went from a passive(non amplified) antenna to an active(amplified) Taoglas.

[SHEEPMAN!]

W00t! A thinker.

OEM GPS in Mark 1, 2 and three. Mk 1 flicker, MK 2 works, Mk 3 flicker. These are all OEM Serial GPS..

1. Linux doesn't do com ports....except through .wine. FYI
2. I have three MK3, five MK2 and five or more MK1. They all perform the same.
3. Mint 16 works.
4. Mint 17 they went to Intel (hold on a minit) (sic)

27.419] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 27.419] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 27.419] compiled for 1.15.1, module version = 0.0.2
[ 27.419] ABI class: X.Org Video Driver, version 15.0
[ 27.420] (WW) Falling back to old probe method for vesa
[ 27.420] (--) intel(0): Integrated Graphics Chipset: Intel(R) GM45
[ 27.420] (--) intel(0): CPU: x86, sse2, sse3, ssse3, sse4.1
[ 27.420] (II) intel(0): Creating default Display subsection in Screen

Yes, I totally know that I am out of my element here....but the common denominator is 15.0.

Anything previous to 15.0 works. Of course it could be anything in the entire package...

CF-53J, CF-30MK2, any CF-29 work....

Uh oh PM's inbound.

Bye. BTW no lambs.

[Shawn]

Link to Sony GXB 5005 datasheet.

http://pdf.datasheetcatalog.com/datashe ... 5120_1.pdf

The Sony does have a signal for an active antenna.

[kode-niner]

I like these exercises. Try to determine if it's the monitor on/off or suspending that triggers it.

Test the monitor

Code: Select all

xset dpms force off; xset dpms force on

Test full suspend without closing the lid then hit the power button briefly to wake up

Code: Select all

sudo echo -n mem > /sys/power/state

[mklym]

A fresh install of Mint17.1 64 bit on an Intel 180GB SSD in a CF-30MK3, OEM GPS. Installed all udates, then gpsd, gpsd-clients, cutecom and FoxtrotGPS. In the BIOS I set the display to internal to elminate the flicker, yes closing the lid and opening gets rid of the screen flicker, and everything else to default.
Booted to desktop and ran Cutecom, could not find any device. Back into BIOS and set GPS to enable, back to desktop, no joy. I tried all 4 resourse settings but Cutecom or gpsd/xgps found no GPS device, even when I disabld both serial ports, the parallel post, as well as BT and WWAN.
This morning I set the GPS to Auto, left everyting else disabled and Cutecom found the GPS on /dev/ttyS0. Did gpsd /dev/ttyS0 and xgps, nothing, closed lid reopened and there was 4 sats showing, not locked but showing, closed lid and reopened again, now 12 sats and 3D lock.
I am going to enable the disabled ports and see what happens. Will report results.

[SHEEPMAN!]

I thought I was the only one. That ttyS0 threw me for a bit. Then I re-read everything else was off. Do you have hardware box checked in cutecom? Curious.