On Wed, Feb 24, 2016 at 11:10 AM, Robert Nelson <[email protected]> wrote:
> On Wed, Feb 24, 2016 at 9:53 AM, Jason Kridner <[email protected]> wrote:
>>
>>
>> On Feb 24, 2016, at 9:50 AM, Robert Nelson <[email protected]> wrote:
>>
>> On Wed, Feb 24, 2016 at 8:48 AM, Rafael Gimenes Leite <[email protected]>
>> wrote:
>>
>> Hi,
>>
>> Anyone can share the latest image for beagole board xM rec C1 ?
>>
>>
>> I want to setup it to download media into external hard disk
>>
>>
>> Monthy snapshots with directions here:
>>
>> http://elinux.org/BeagleBoardDebian#Debian_.28jessie.29
>>
>> Sorry, i don't really test the xM anymore, other then basic boot tests..
>>
>>
>> I created a simple console disk image at
>> http://debian.beagleboard.org/images/beaglexm-debian-8.3-console-2016-02-11-2gb.img.xz.
>>
>> If I get positive feedback, I will link from BeagleBoard.org/latest-images.
>> I have not tested it myself yet.
This time with a good microsd card:
monitor alive via edid:
debian@arm:~$ cat /sys/class/drm/card0-DVI-D-1/edid | parse-edid
Checksum Correct
Section "Monitor"
Identifier "DELL 1707FP"
ModelName "DELL 1707FP"
VendorName "DEL"
# Monitor Manufactured week 48 of 2006
# EDID version 1.3
# Digital Display
DisplaySize 340 270
Gamma 2.20
Option "DPMS" "true"
Horizsync 30-81
VertRefresh 56-76
# Maximum pixel clock is 140MHz
#Not giving standard mode: 1152x864, 75Hz
#Not giving standard mode: 1280x1024, 60Hz
Modeline "Mode 0" +hsync +vsync
EndSection
usb:
debian@arm:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 002 Device 004: ID 0424:2504 Standard Microsystems Corp. USB 2.0 Hub
Bus 002 Device 003: ID 0424:ec00 Standard Microsystems Corp.
SMSC9512/9514 Fast Ethernet Adapter
Bus 002 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ethernet:
debian@arm:~$ sudo ifconfig -a
eth0 Link encap:Ethernet HWaddr 3a:76:00:fb:79:d2
inet addr:192.168.0.142 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::3876:ff:fefb:79d2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST DYNAMIC MTU:1500 Metric:1
RX packets:29 errors:0 dropped:0 overruns:0 frame:0
TX packets:61 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3164 (3.0 KiB) TX bytes:10140 (9.9 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:160 errors:0 dropped:0 overruns:0 frame:0
TX packets:160 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:12960 (12.6 KiB) TX bytes:12960 (12.6 KiB)
usb0 Link encap:Ethernet HWaddr 9a:b9:4c:c7:09:ef
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
debian@arm:~$ cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to [email protected], please.
analyzing CPU 0:
driver: cpufreq-dt
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 300 us.
hardware limits: 300 MHz - 800 MHz
available frequency steps: 300 MHz, 600 MHz, 800 MHz
available cpufreq governors: conservative, ondemand, userspace,
powersave, performance
current policy: frequency should be within 300 MHz and 800 MHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 300 MHz.
cpufreq stats: 300 MHz:82.59%, 600 MHz:2.69%, 800 MHz:14.72% (41)
Sorry no 1Ghz, no one is really working on opp stuff for omap3's
anymore on mainline... (and our local hack doesn't work anymore..)
Regards,
--
Robert Nelson
https://rcn-ee.com/
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
