New IT forum
26 June 2022, 04:39:31 pm *
Welcome, %1$s. Please login or register.

: PiHub now in stock.
 
Pages: [1]

Author Topic: Mimo Monitor not activating on Dream GUIplug  (Read 13863 times)

dyoung5

  • Newbie
  • *
  • Posts: 9
Mimo Monitor not activating on Dream GUIplug
« on: 08 July 2011, 11:22:20 am »

Hello,

We have a DreamPlug with a Mimo 720F and it used to work using the GUIplug OS, but recently, when trying to load it up, it just says Starting Guiplug init.Mimo 720 located., but nothing displays on the screen. What should I do to try and troubleshoot it?

Thanks,
David
Logged

NewITMalcolm

  • Administrator
  • Sr. Member
  • *****
  • Posts: 394
Re: Mimo Monitor not activating on Dream GUIplug
« Reply #1 on: 08 July 2011, 11:29:14 am »

Hi David,

Does the screen turn green briefly during boot?

Are you using GuiPlug v2.5 or v2.6?

Is device /dev/fb0 created?

Does this display anything?
Code: [Select]
/etc/init.d/gdm3 restart

NewITJames



« Last Edit: 08 July 2011, 11:32:02 am by NewIT_James »
Logged
NewITJames

dyoung5

  • Newbie
  • *
  • Posts: 9
Re: Mimo Monitor not activating on Dream GUIplug
« Reply #2 on: 08 July 2011, 03:31:46 pm »

Hi James,

The screen has the blue light, but doesn't show anything on the display at all.

It happened on 2.5 and 2.6

I'll check those settings on Monday and let you know.

Thanks,
David
Logged

NewITMalcolm

  • Administrator
  • Sr. Member
  • *****
  • Posts: 394
Re: Mimo Monitor not activating on Dream GUIplug
« Reply #3 on: 08 July 2011, 04:07:06 pm »

David,

Try a different mini-usb cable if you have one.

NewITJames
Logged
NewITJames

dyoung5

  • Newbie
  • *
  • Posts: 9
Re: Mimo Monitor not activating on Dream GUIplug
« Reply #4 on: 11 July 2011, 09:48:08 am »

Hi James,

I have swapped the mini-usb cable with no effect.

/dev/fb0 is is not being created and restarting gdm3 does nothing.

Thanks for your help.

David
Logged

dyoung5

  • Newbie
  • *
  • Posts: 9
Re: Mimo Monitor not activating on Dream GUIplug
« Reply #5 on: 31 August 2011, 10:32:08 am »

HI James,

Just wondering if you had any other ideas to try and fix this?

I have tried with a fresh image, and its still not displaying something. I'm starting to suspect h/w problem, but the monitor works on my Windows PC!

Regards,

David
Logged

NewITMalcolm

  • Administrator
  • Sr. Member
  • *****
  • Posts: 394
Re: Mimo Monitor not activating on Dream GUIplug
« Reply #6 on: 31 August 2011, 10:54:48 am »

David,

This sounds like a power issue, the 720F and 720S often need a powered USB hub when used with the Sheevaplug.

http://newit.co.uk/shop/proddetail.php?prod=7_Port_Hub

Try turning the brightness fully down when booting the Sheevaplug with the monitor attached and see if it boots ok then.

NewITJames
Logged
NewITJames

dyoung5

  • Newbie
  • *
  • Posts: 9
Re: Mimo Monitor not activating on Dream GUIplug
« Reply #7 on: 05 September 2011, 05:05:48 pm »

Hi James,

I have tried with a powered hub, and it still does not work. This is really starting to perplex me!!
Logged

NewITMalcolm

  • Administrator
  • Sr. Member
  • *****
  • Posts: 394
Re: Mimo Monitor not activating on Dream GUIplug
« Reply #8 on: 05 September 2011, 05:20:03 pm »

David,


Plug the monitor into the powered up Sheevaplug and post the dmesg results.


NewITJames
Logged
NewITJames

dyoung5

  • Newbie
  • *
  • Posts: 9
Re: Mimo Monitor not activating on Dream GUIplug
« Reply #9 on: 07 September 2011, 04:28:45 pm »

Hi James

Here's the dmesg result:
Code: [Select]
Linux version 2.6.33.6 ([email protected]) (gcc version 4.2.1) #1 PREEMPT Tue Feb 8 03:18:41 EST 2011
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
CPU: VIVT data cache, VIVT instruction cache
Machine: Marvell GuruPlug Reference Board
Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 131072
free_area_init_node: node 0, pgdat c0557688, node_mem_map c0606000
  Normal zone: 1024 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 130048 pages, LIFO batch:31
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
Kernel command line: console=ttyS0,115200 root=/dev/sdc2 rootdelay=10
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 256MB 256MB = 512MB total
Memory: 513408KB available (4832K code, 862K data, 140K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:114
Console: colour dummy device 80x30
Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Kirkwood: MV88F6281-A1, TCLK=200000000.
Feroceon L2: Cache support initialised.
initial MPP regs: 01112222 11113311 33331111 33333333 00003333 00000222 00000000
  final MPP regs: 01112222 11113311 33331111 33333333 00003333 00000222 00000000
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: 00
    (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
    (2457000 KHz - 2482000 KHz @ 20000 KHz), (600 mBi, 2000 mBm)
    (2474000 KHz - 2494000 KHz @ 20000 KHz), (600 mBi, 2000 mBm)
    (5170000 KHz - 5250000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
    (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
cfg80211: Calling CRDA to update world regulatory domain
Switching to clocksource orion_clocksource
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 32
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
JFS: nTxBlock = 4012, nTxLock = 32102
msgmni has been set to 1003
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
console [ttyS0] enabled
brd: module loaded
loop: module loaded
No NAND device found.
MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
net eth0: port 0 with MAC address f0:ad:4e:00:7b:37
net eth1: port 0 with MAC address f0:ad:4e:00:7b:38
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
orion-ehci orion-ehci.0: Marvell Orion EHCI
orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
mice: PS/2 mouse device common for all mice
rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
i2c /dev entries driver
cpuidle: using governor ladder
cpuidle: using governor menu
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mmc0: mvsdio driver initialized, lacking card detect (fall back to polling)
Registered led device: guruplug:red:health
Registered led device: guruplug:green:health
Registered led device: guruplug:red:wmode
Registered led device: guruplug:green:wmode
mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
mmc0: new high speed SDIO card at address 0001
mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
oprofile: using timer interrupt.
TCP cubic registered
NET: Registered protocol family 17
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
Gating clock of unused units
before: 0x00dfc3fd
 after: 0x00cf41d9
rtc-mv rtc-mv: setting system clock to 2011-06-06 21:09:21 UTC (1307394561)
Waiting 10sec before mounting root device...
usb 1-1: new high speed USB device using orion-ehci and address 2
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usb 1-1.1: new high speed USB device using orion-ehci and address 3
scsi0 : usb-storage 1-1.1:1.0
usb 1-1.2: new high speed USB device using orion-ehci and address 4
hub 1-1.2:1.0: USB hub found
hub 1-1.2:1.0: 4 ports detected
usb 1-1.3: new high speed USB device using orion-ehci and address 5
scsi1 : usb-storage 1-1.3:1.0
usb 1-1.4: new full speed USB device using orion-ehci and address 6
input: C-Media USB Headphone Set   as /devices/platform/orion-ehci.0/usb1/1-1/1-1.4/1-1.4:1.3/input/input0
generic-usb 0003:0D8C:000C.0001: input: USB HID v1.00 Device [C-Media USB Headphone Set  ] on usb-orion-ehci.0-1.4/input3
usb 1-1.2.2: new high speed USB device using orion-ehci and address 7
usb 1-1.2.3: new full speed USB device using orion-ehci and address 8
scsi 0:0:0:0: Direct-Access     Generic  STORAGE DEVICE   9910 PQ: 0 ANSI: 0
sd 0:0:0:0: Attached scsi generic sg0 type 0
scsi 0:0:0:1: Direct-Access     Generic  STORAGE DEVICE   9910 PQ: 0 ANSI: 0
sd 0:0:0:0: [sda] 3842048 512-byte logical blocks: (1.96 GB/1.83 GiB)
sd 0:0:0:1: Attached scsi generic sg1 type 0
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 0b 00 00 08
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:1: [sdb] Attached SCSI removable disk
sd 0:0:0:0: [sda] Assuming drive cache: write through
 sda: sda1 sda2
sda: p2 size 3653412 exceeds device capacity, limited to end of disk
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Attached SCSI removable disk
scsi 1:0:0:0: Direct-Access     Kingston DT 100 G2        PMAP PQ: 0 ANSI: 0 CCS
sd 1:0:0:0: Attached scsi generic sg2 type 0
sd 1:0:0:0: [sdc] 15215808 512-byte logical blocks: (7.79 GB/7.25 GiB)
sd 1:0:0:0: [sdc] Write Protect is off
sd 1:0:0:0: [sdc] Mode Sense: 23 00 00 00
sd 1:0:0:0: [sdc] Assuming drive cache: write through
sd 1:0:0:0: [sdc] Assuming drive cache: write through
 sdc: sdc1 sdc2
sd 1:0:0:0: [sdc] Assuming drive cache: write through
sd 1:0:0:0: [sdc] Attached SCSI removable disk
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sdc2): using internal journal
EXT3-fs (sdc2): recovery complete
EXT3-fs (sdc2): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 8:34.
Freeing init memory: 140K
mcypt: version magic '2.6.38.8 preempt mod_unload ARMv5 ' should be '2.6.33.6 preempt mod_unload ARMv5 '
sd8xxx: version magic '2.6.38.8 preempt mod_unload ARMv5 ' should be '2.6.33.6 preempt mod_unload ARMv5 '
Logged

dyoung5

  • Newbie
  • *
  • Posts: 9
Re: Mimo Monitor not activating on Dream GUIplug
« Reply #10 on: 07 September 2011, 04:33:12 pm »

 Heres the messages if you unplug and re-plug the mimo monitor while running:


Code: [Select]
usb 1-1.2.2: USB disconnect, address 7
usb 1-1.2.3: USB disconnect, address 8
usb 1-1.2: new high speed USB device using orion-ehci and address 9
hub 1-1.2:1.0: USB hub found
hub 1-1.2:1.0: 4 ports detected
usb 1-1.2.2: new high speed USB device using orion-ehci and address 10
usb 1-1.2.3: new full speed USB device using orion-ehci and address 11
Logged

NewITMalcolm

  • Administrator
  • Sr. Member
  • *****
  • Posts: 394
Re: Mimo Monitor not activating on Dream GUIplug
« Reply #11 on: 07 September 2011, 04:38:53 pm »

Quote
Linux version 2.6.33.6


That's not the GuiPlug kernel you are booting to.

Should say 2.6.38.8 for v2.6

NewITJames
Logged
NewITJames

dyoung5

  • Newbie
  • *
  • Posts: 9
Re: Mimo Monitor not activating on Dream GUIplug
« Reply #12 on: 08 September 2011, 11:04:11 am »

Thanks James for that pointer.

Turns out that the DP was still loading the uImage from the internal SD card and not the USB stick. I set it to this: x_bootcmd_kernel fatload usb 2 0x6400000 uImage and it now works.

Again, thanks so much for your help.

David
Logged
Pages: [1]
 
 

Powered by MySQL Powered by PHP SMF 2.0.10 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!