Re: [opensuse-arm] Re: BeagleBone Black stuck at 3 LEDs.
2014-11-22 23:44 GMT+03:00 Zack Piper <zack@apertron.net>:
The BeagleBone Black JeOS image, I have not been using the boot switch button, I have tried it, no LEDs lightup.
Which version? 13.1 13.2 Factory?
Another qustion, does the openSUSE image automatically activate a tty-over-USB at all?
No -- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Sun, Nov 23, 2014 at 12:50:44AM +0400, Matwey V. Kornilov wrote:
2014-11-22 23:44 GMT+03:00 Zack Piper <zack@apertron.net>:
The BeagleBone Black JeOS image, I have not been using the boot switch button, I have tried it, no LEDs lightup.
Which version? 13.1 13.2 Factory?
Another qustion, does the openSUSE image automatically activate a tty-over-USB at all?
No
-- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru Oops, sorry, I am using 13.2.
Is there a guide on enabling tty-over-USB? -- I have nothing fancy or intelligent to put here.
2014-11-23 0:00 GMT+03:00 Zack Piper <zack@apertron.net>:
On Sun, Nov 23, 2014 at 12:50:44AM +0400, Matwey V. Kornilov wrote:
2014-11-22 23:44 GMT+03:00 Zack Piper <zack@apertron.net>:
The BeagleBone Black JeOS image, I have not been using the boot switch button, I have tried it, no LEDs lightup.
Which version? 13.1 13.2 Factory?
Another qustion, does the openSUSE image automatically activate a tty-over-USB at all?
No
-- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru Oops, sorry, I am using 13.2.
Hm, I've tried this couple hours ago, it worked. However, first boot takes several minutes.
Is there a guide on enabling tty-over-USB?
It is disabled in config, I don't know why. -- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 22.11.2014 um 22:09 schrieb Matwey V. Kornilov:
2014-11-23 0:00 GMT+03:00 Zack Piper <zack@apertron.net>:
Is there a guide on enabling tty-over-USB?
It is disabled in config, I don't know why.
Which config option is that? Regards, Andreas -- SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 21284 AG Nürnberg -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
It is CONFIG_USB_G_SERIAL I've just sent the patch to opensuse-kernel 2014-11-23 0:27 GMT+03:00 Andreas Färber <afaerber@suse.de>:
Am 22.11.2014 um 22:09 schrieb Matwey V. Kornilov:
2014-11-23 0:00 GMT+03:00 Zack Piper <zack@apertron.net>:
Is there a guide on enabling tty-over-USB?
It is disabled in config, I don't know why.
Which config option is that?
Regards, Andreas
-- SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 21284 AG Nürnberg
-- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Sun, Nov 23, 2014 at 01:29:16AM +0400, Matwey V. Kornilov wrote:
It is CONFIG_USB_G_SERIAL I've just sent the patch to opensuse-kernel
2014-11-23 0:27 GMT+03:00 Andreas Färber <afaerber@suse.de>:
Am 22.11.2014 um 22:09 schrieb Matwey V. Kornilov:
2014-11-23 0:00 GMT+03:00 Zack Piper <zack@apertron.net>:
Is there a guide on enabling tty-over-USB?
It is disabled in config, I don't know why.
Which config option is that?
Regards, Andreas
-- SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 21284 AG Nürnberg
-- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Do I wait for the patches to be applied, then grab a factory build? Or can I get a prebuilt version? If there isn't, I'll try and compile the kernel myself. -- I have nothing fancy or intelligent to put here.
23.11.2014 01:16, Zack Piper пишет:
Do I wait for the patches to be applied, then grab a factory build? Or can I get a prebuilt version?
If there isn't, I'll try and compile the kernel myself.
It will take a time to apply the patch. If you want you always can play with the kernel. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Sun, Nov 23, 2014 at 01:09:20AM +0400, Matwey V. Kornilov wrote:
2014-11-23 0:00 GMT+03:00 Zack Piper <zack@apertron.net>:
On Sun, Nov 23, 2014 at 12:50:44AM +0400, Matwey V. Kornilov wrote:
2014-11-22 23:44 GMT+03:00 Zack Piper <zack@apertron.net>:
The BeagleBone Black JeOS image, I have not been using the boot switch button, I have tried it, no LEDs lightup.
Which version? 13.1 13.2 Factory?
Another qustion, does the openSUSE image automatically activate a tty-over-USB at all?
No
-- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru Oops, sorry, I am using 13.2.
Hm, I've tried this couple hours ago, it worked. However, first boot takes several minutes.
Is there a guide on enabling tty-over-USB?
It is disabled in config, I don't know why.
-- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Does the first boot have any LEDs, or do they come on after some minutes? -- I have nothing fancy or intelligent to put here.
23.11.2014 00:34, Zack Piper пишет:
Does the first boot have any LEDs, or do they come on after some minutes?
For me, U1 and U2 blink when it booted, but not at boot process itself. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Sun, 23 Nov 2014 01:09:20 +0400 "Matwey V. Kornilov" <matwey.kornilov@gmail.com> wrote:
2014-11-23 0:00 GMT+03:00 Zack Piper <zack@apertron.net>:
On Sun, Nov 23, 2014 at 12:50:44AM +0400, Matwey V. Kornilov wrote:
2014-11-22 23:44 GMT+03:00 Zack Piper <zack@apertron.net>:
The BeagleBone Black JeOS image, I have not been using the boot switch button, I have tried it, no LEDs lightup.
Which version? 13.1 13.2 Factory?
Another qustion, does the openSUSE image automatically activate a tty-over-USB at all?
No
-- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru Oops, sorry, I am using 13.2.
Hm, I've tried this couple hours ago, it worked. However, first boot takes several minutes.
Is there a guide on enabling tty-over-USB?
It is disabled in config, I don't know why.
I see a new image (26.3 of JEOS 13,2) has been uploaded. I'm downloading it now, will flog it and report my findings. Note there is no sha256 for the download. However just to be clear, on rev 26.2, the USB was totally not functional. It would not recognize usb devices plugged into it. lsusb only detected the usb chip on the SBC, There is some confusion on the interwebs about which serial cable to get. I can say the FTDI one from Adafruit works fine. But the ethernet connection worked on the initial installation, so if somebody got lucky, they wouldn't need the serial cable. You would be installing the OS in the blind, which is why I mentioned luck. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Sat, 22 Nov 2014 14:25:31 -0800 lists <lists@lazygranch.com> wrote:
On Sun, 23 Nov 2014 01:09:20 +0400 "Matwey V. Kornilov" <matwey.kornilov@gmail.com> wrote:
2014-11-23 0:00 GMT+03:00 Zack Piper <zack@apertron.net>:
On Sun, Nov 23, 2014 at 12:50:44AM +0400, Matwey V. Kornilov wrote:
2014-11-22 23:44 GMT+03:00 Zack Piper <zack@apertron.net>:
The BeagleBone Black JeOS image, I have not been using the boot switch button, I have tried it, no LEDs lightup.
Which version? 13.1 13.2 Factory?
Another qustion, does the openSUSE image automatically activate a tty-over-USB at all?
No
-- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru Oops, sorry, I am using 13.2.
Hm, I've tried this couple hours ago, it worked. However, first boot takes several minutes.
Is there a guide on enabling tty-over-USB?
It is disabled in config, I don't know why.
I see a new image (26.3 of JEOS 13,2) has been uploaded. I'm downloading it now, will flog it and report my findings. Note there is no sha256 for the download.
However just to be clear, on rev 26.2, the USB was totally not functional. It would not recognize usb devices plugged into it. lsusb only detected the usb chip on the SBC,
There is some confusion on the interwebs about which serial cable to get. I can say the FTDI one from Adafruit works fine. But the ethernet connection worked on the initial installation, so if somebody got lucky, they wouldn't need the serial cable. You would be installing the OS in the blind, which is why I mentioned luck.
The 26.3 rev has issues. The serial port doesn't work well. This problem wasn't evident in the 26.2 rev. USB still doesn't work. Here is what I copied from the serial port during installation. [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.16.7-2-default (geeko@buildhost) (gcc version 4.8.3 20140627 [gcc-4_8-branch revision 212064] (SUSE Linux) ) #1 SMP Sun Nov 9 17:32:10 UTC 2014 (b648071) [ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] Machine model: TI AM335x BeagleBoory policy:ll CPU(s) started in SVC mode. [ 0.000000] AM335X E PERCPU: Embedded 9 pages/cpu @dfaa9000 s13760 r8192 d14912 u36864 [ 0.000000] Built 1 zonelists in Zone order, mobility groupinable=0 console=ttyO0 showopts [ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes) [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Inode-cache hash table entries: 327allocated 1 'cgroup_disable=memory cgroups 00] Memory: 389572K/52able (7820K kernel cod9K init, 84Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmae00000 (2048 kB) [ 0.000000] vmalloc : 0xe0800000 - 0xff000000 ( 0000 - 0xe000000 - 0xbext : 0xc0208000 - 0xcd1a000 - 0xc0ff4b9c RCU restricRCU callbacks from CPUs: 0. [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1 [ nr_irqs:16 INTC at 0x [ 0.000] OMAP cloc69942ns [ 0.000030] OMAP clocksource: timer1 at 24000000 Hz [ 0.000300x30 [ 0.000342] Calibrating delay loop... 997.78 BogoMIPS (lpj=2494464) [ 0.054388] pid_max: defaultimum: 301 [ 0.054514] Security Framework initialized [ 0.054618] AppArmor: AppArmor initialized [ 0.054784] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.054797] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.055742] Initializing cgrou7] Initializing cgroup subsys net_cls [ 0.055927] Initializing cgroup subsys blkio up static p for 0x8096a7e0 - 0x8096a878 [ 0.128551] Brought up 1 CPUs [ 0.128572] SMP: To0] CPU: All 0.129339 initialized [ 0.133112] VFP _hwmod: tptc1 using broken dt data from edma arget_disabnctrl subsystem tptc2 using broken dt data from edma [ 0.207071] regulator-dummy: no parameters [ 0.219128] NET: Registered protocol family 16 [ 0.221356] DMA: preallocated 256 KiB pool for atomic coherent allocations [ [ 0.229 [ 0.229edma: aliasy exists [version 0.17882] No A 0.237909] hw-breakpoi 0x4 unsupp 0.238722] EXYNOS: PMrs ubsystem initialized: loaded i2c: could tldev for n0.i2c: Drivrobe deferr264508] Netnlabeled trlt [ 0itched to clocksource 0.309856]23193] TCP established hash table096 (order:TCP bind ha[ 0.3233eno registe256 (order:tes) [ h table entorder: 1, 8 [ 0.323rotocol fam Unpacking . [ 4.0oating Point Emulator V0.97 (extended precision) [ available tialise system trusted keyring ubsys (disabled) [ initialized70] Dquot-cs: 1024 (order 0, 4096] msgmni ha 4.014358er SCSI gen252) [ 4.014565] io scheduler noop registered [ io scheduler deadline registered [ 4.014722] io scheduler cfq registered (default) [ 4.016108] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568 [ 4.020683] Serial: 8250/16550 driver, 32 ports, IRQ sharing disabled [ 4.030044] Serial: IMX driver [ 4.030458] msm_serial: driver initialized [ 4.030722] omap_uart 44e09000.serial: no wakeirq for uart0 [ 4.030880] 4 enabled [ 4.771501] serialtered successfully. [ 4.798608] libphy: Fixed MDIO Bus: probed [ 4.803817] mousedev: PS/2 mouse device common for all mice [ 4.815526] ledtrig-cpu: registered to indicate activity on CPUs [ 4.821964] hidraw: raw HID events driver (C) Jiri Kosina [ 4.829821] TCP: cubic registered [ 4.833424] NET: Registered protocol family 10 [ 4.839264] omap_voltage_late_idded [ 4.846020] sr_dev_init: No voltage domain specified for smartreflex0. Cannot initialize [ 4.854523] sr_dev_init: No voltage domain specified for smartreflex1. Cannot initialize [ 4.863709] ThumbEE CPU extension supported. [ 4.868279] Registering SWP/SWPB emulation handler [ 4.873349] SmartReflex Class3 initialized on 1 4.878471] Loading compiled-in X.509 certificates [ 4.888141] AppArmor: AppArmor sha1 policy hashing enabled [ 4.894722] slave hdmi: could not get i2c [ 4.899028] platform hdmi: Driver slave requests probe deferral [ 4.905546] platform 4830e000.lcdc: Driver tilcdc requests probe deferral [ 4.923982] .11 at 400 kHz 0.lcdc: no encoders/connectors found [ 4.947953] tilcdc 4830e000.lcdc: failed to initialize mode setting [ 4.955449] ../drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 4.962359] sr_init: No PMIC hynos5-bus-int failed with error -2 [ 4.989931] vmmcsd_fixed: disabling [ 4.995127] Freeing unused kernel memory: 948K (c0d1a000 - c0e07000) 10.445823] cpsw 4a100000.ethernet: Detected MACID = 1c:ba:8c:a1:ba:28 pport reading read-only switch. assuming write-enable. assigned buice strings: Mfr=3, Product=2, SerialNumber=1 [ 11.222132] usb usb2: Product: MUSB HDRC host drib usb2: Manufacturer: Linux 3.16.7-2-default musb-hcd [ 11.233umber: musb54] hub 2-00731] device-mapper: ioctl: 4.27.0-ioctl (20.135910] lousb2-port1:isk accordi 17.180316] mmcblk0: p1 p2 [ 17.458841] mmcblk0: p1 p2 [ 17.730007] mmcblk0: p1 [ 18.295240] mmcblk0: p1 [ 18.459729] mmcblk0: p1 p2 [ 18.999672] mmcblk0: p1 p2 [ 19.283079] mmcblk0: p1427023] mmcblk0: p1 p2 p3 [ 226441612.9813/mmcblk0p2: 23254/52752 files (0.2% non-contiguous), 169002/210176 blocks [1416441614.641118] Resizing ext4 filesystem on /dev/mmcblk0p2... Resizing the filesystem on /dev/mmcblk0p2 to 7554769 (4k) blocreating boot loader configuration 646943] Pre for /dev/mmcblk0p1, bile or directory 8.338771] device-mapper: uevent: version 1.0.3 [ 148.350213] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com -manager.service, ignoring: Unit e failed toched target Remote File Systems (Pre). d[1]: Reach Systems. ed target Remote File Systems. [ 148.8ormats File System Automount Point. [tomount Po Arbitrary Executable File Formats File System AutomounDirectory Watch. ed target Paths. [ r and Sessioystemd[1]: Starting System Slice. emd[1]: Created slice System Slice. [ 149.211039] systeCreate list of required static device nodes...rrent kernel... ating swap /dev/mmcblk0p3... m OK 2m OK ] Activated swap /dev/mmcblk0p3. [ OK ] Started Create dynamic rule for /dev/root link. ] Reacheev... OK ] S OK ] Started udev Kernel Device Manager. ] Started Load/Save.327381] omP Watchdog [ 151.3arted udev Wait for Complete DevicOK ] Reached target Encrypted Volumes. Starting Activation of LVM2 logi32m OK tarting Restore Sound Card State... [ OK ] Reached target Basic System. Starting Permit User Sessions... Compatibility... Starting YaST2 Firstboot... s. Starting wicked AutoIPv4 supplicant service... Starting wicked DHCPv6 supplicant service... .. nit.d/boot.l OK ] Service. ttyO0... Getty on tty openSUSE 13Welcome to linux logi ux login: rootPassword: Password: sword: default (ttyO0). linux login: roo m m ls ;34m.local bin -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 23.11.2014 um 06:37 schrieb lists <lists@lazygranch.com>:
On Sat, 22 Nov 2014 14:25:31 -0800 lists <lists@lazygranch.com> wrote:
On Sun, 23 Nov 2014 01:09:20 +0400 "Matwey V. Kornilov" <matwey.kornilov@gmail.com> wrote:
2014-11-23 0:00 GMT+03:00 Zack Piper <zack@apertron.net>:
On Sun, Nov 23, 2014 at 12:50:44AM +0400, Matwey V. Kornilov wrote:
2014-11-22 23:44 GMT+03:00 Zack Piper <zack@apertron.net>:
The BeagleBone Black JeOS image, I have not been using the boot switch button, I have tried it, no LEDs lightup.
Which version? 13.1 13.2 Factory?
Another qustion, does the openSUSE image automatically activate a tty-over-USB at all?
No
-- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru Oops, sorry, I am using 13.2.
Hm, I've tried this couple hours ago, it worked. However, first boot takes several minutes.
Is there a guide on enabling tty-over-USB?
It is disabled in config, I don't know why.
I see a new image (26.3 of JEOS 13,2) has been uploaded. I'm downloading it now, will flog it and report my findings. Note there is no sha256 for the download.
However just to be clear, on rev 26.2, the USB was totally not functional. It would not recognize usb devices plugged into it. lsusb only detected the usb chip on the SBC,
There is some confusion on the interwebs about which serial cable to get. I can say the FTDI one from Adafruit works fine. But the ethernet connection worked on the initial installation, so if somebody got lucky, they wouldn't need the serial cable. You would be installing the OS in the blind, which is why I mentioned luck.
The 26.3 rev has issues. The serial port doesn't work well. This problem wasn't evident in the 26.2 rev. USB still doesn't work.
Looks like it's working to me ;). The serial port issues usually come from a loose cable. If you press against the serial pin connectors they should go away. Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Sun, 23 Nov 2014 08:46:25 +0100 Alexander Graf <agraf@suse.de> wrote:
Am 23.11.2014 um 06:37 schrieb lists <lists@lazygranch.com>:
On Sat, 22 Nov 2014 14:25:31 -0800 lists <lists@lazygranch.com> wrote:
On Sun, 23 Nov 2014 01:09:20 +0400 "Matwey V. Kornilov" <matwey.kornilov@gmail.com> wrote:
2014-11-23 0:00 GMT+03:00 Zack Piper <zack@apertron.net>:
On Sun, Nov 23, 2014 at 12:50:44AM +0400, Matwey V. Kornilov wrote:
2014-11-22 23:44 GMT+03:00 Zack Piper <zack@apertron.net>: > The BeagleBone Black JeOS image, I have not been using the boot > switch button, I have tried it, no LEDs lightup.
Which version? 13.1 13.2 Factory?
> Another qustion, does the openSUSE image automatically activate > a tty-over-USB at all?
No
-- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru Oops, sorry, I am using 13.2.
Hm, I've tried this couple hours ago, it worked. However, first boot takes several minutes.
Is there a guide on enabling tty-over-USB?
It is disabled in config, I don't know why.
I see a new image (26.3 of JEOS 13,2) has been uploaded. I'm downloading it now, will flog it and report my findings. Note there is no sha256 for the download.
However just to be clear, on rev 26.2, the USB was totally not functional. It would not recognize usb devices plugged into it. lsusb only detected the usb chip on the SBC,
There is some confusion on the interwebs about which serial cable to get. I can say the FTDI one from Adafruit works fine. But the ethernet connection worked on the initial installation, so if somebody got lucky, they wouldn't need the serial cable. You would be installing the OS in the blind, which is why I mentioned luck.
The 26.3 rev has issues. The serial port doesn't work well. This problem wasn't evident in the 26.2 rev. USB still doesn't work.
Looks like it's working to me ;). The serial port issues usually come from a loose cable. If you press against the serial pin connectors they should go away.
Alex
I have a SD card with Debian and it works just great on the serial port. No hardware problems on my end. I just loaded Angstrom. Serial output at the end of the message. Are you using JEOS? I find the serial port failing to display characters on the JEOS 13.2 rev 26.3. The data is sent, but don't get echoed. b6a02182988f24e7260e5989f3d498e26ed53afd16219c29e2921beb5cd5ff85 openSUSE-13.2-ARM-JeOS-beaglebone.armv7l-1.12.1-Build26.3.raw.xz Here is the clean Angstrom output on the serial port. =================================================== Starting kernel ... Uncompressing Linux...latform dat-BONELT-HDMIN:00A0 (pr 0.451594]21 (gpio-leds.8) status -22 [ 0.535464] 1 on device830e000.fb: timeout waiting for framedone [ 6.6453lebone logiC-Flasher: clean, 12814/218592 files, 167134/873534 blocks CCCCCCCCCCCSoftConn) m1 max ep, 16384/16384 mipheral modeyn FIFOs, HftConn) musroller at 47401800 using PIO, IRQ 0 Net: <ethaddr> not set. Validating first E-fuse M270840 bytes read in 76from mmc ..c0 ... Image Name: Load Af80000, end T-HDMI) [ tion [ LT-HDMIN:00A0 (prio 2)[ 0.528136] pinctrl-single 44e10800.pinmux[ 0.904563] tilcdc 4830e000.fb: timeout waiting for framedone systemd-fsck[86]: eMMC-Flasher: clean, 12816/218592 files, 167742/873534 blocks [ 602.051133] tilcdc 4830e000.fb: timeout waiting for framedone [ 1626.087616] tilcdc 4830e000.fb: timeout waiting for framedone -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 23.11.14 10:03, lists wrote:
On Sun, 23 Nov 2014 08:46:25 +0100 Alexander Graf <agraf@suse.de> wrote:
Am 23.11.2014 um 06:37 schrieb lists <lists@lazygranch.com>:
On Sat, 22 Nov 2014 14:25:31 -0800 lists <lists@lazygranch.com> wrote:
On Sun, 23 Nov 2014 01:09:20 +0400 "Matwey V. Kornilov" <matwey.kornilov@gmail.com> wrote:
2014-11-23 0:00 GMT+03:00 Zack Piper <zack@apertron.net>:
On Sun, Nov 23, 2014 at 12:50:44AM +0400, Matwey V. Kornilov wrote: > 2014-11-22 23:44 GMT+03:00 Zack Piper <zack@apertron.net>: >> The BeagleBone Black JeOS image, I have not been using the boot >> switch button, I have tried it, no LEDs lightup. > > Which version? 13.1 13.2 Factory? > >> Another qustion, does the openSUSE image automatically activate >> a tty-over-USB at all? > > No > > > -- > With best regards, > Matwey V. Kornilov > http://blog.matwey.name > xmpp://0x2207@jabber.ru Oops, sorry, I am using 13.2.
Hm, I've tried this couple hours ago, it worked. However, first boot takes several minutes.
Is there a guide on enabling tty-over-USB?
It is disabled in config, I don't know why.
I see a new image (26.3 of JEOS 13,2) has been uploaded. I'm downloading it now, will flog it and report my findings. Note there is no sha256 for the download.
However just to be clear, on rev 26.2, the USB was totally not functional. It would not recognize usb devices plugged into it. lsusb only detected the usb chip on the SBC,
There is some confusion on the interwebs about which serial cable to get. I can say the FTDI one from Adafruit works fine. But the ethernet connection worked on the initial installation, so if somebody got lucky, they wouldn't need the serial cable. You would be installing the OS in the blind, which is why I mentioned luck.
The 26.3 rev has issues. The serial port doesn't work well. This problem wasn't evident in the 26.2 rev. USB still doesn't work.
Looks like it's working to me ;). The serial port issues usually come from a loose cable. If you press against the serial pin connectors they should go away.
Alex
I have a SD card with Debian and it works just great on the serial port. No hardware problems on my end.
I just loaded Angstrom. Serial output at the end of the message. Are you using JEOS?
Yeah.
I find the serial port failing to display characters on the JEOS 13.2 rev 26.3. The data is sent, but don't get echoed.
How do you see this is happening? I'll get a new BBB tomorrow that I'll slam 13.2 onto. Then I can let you know whether it works for me ;). Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 23.11.14 19:32, Alexander Graf wrote:
On 23.11.14 10:03, lists wrote:
On Sun, 23 Nov 2014 08:46:25 +0100 Alexander Graf <agraf@suse.de> wrote:
Am 23.11.2014 um 06:37 schrieb lists <lists@lazygranch.com>:
On Sat, 22 Nov 2014 14:25:31 -0800 lists <lists@lazygranch.com> wrote:
On Sun, 23 Nov 2014 01:09:20 +0400 "Matwey V. Kornilov" <matwey.kornilov@gmail.com> wrote:
2014-11-23 0:00 GMT+03:00 Zack Piper <zack@apertron.net>: > On Sun, Nov 23, 2014 at 12:50:44AM +0400, Matwey V. Kornilov > wrote: >> 2014-11-22 23:44 GMT+03:00 Zack Piper <zack@apertron.net>: >>> The BeagleBone Black JeOS image, I have not been using the boot >>> switch button, I have tried it, no LEDs lightup. >> >> Which version? 13.1 13.2 Factory? >> >>> Another qustion, does the openSUSE image automatically activate >>> a tty-over-USB at all? >> >> No >> >> >> -- >> With best regards, >> Matwey V. Kornilov >> http://blog.matwey.name >> xmpp://0x2207@jabber.ru > Oops, sorry, I am using 13.2.
Hm, I've tried this couple hours ago, it worked. However, first boot takes several minutes.
> Is there a guide on enabling tty-over-USB?
It is disabled in config, I don't know why.
I see a new image (26.3 of JEOS 13,2) has been uploaded. I'm downloading it now, will flog it and report my findings. Note there is no sha256 for the download.
However just to be clear, on rev 26.2, the USB was totally not functional. It would not recognize usb devices plugged into it. lsusb only detected the usb chip on the SBC,
There is some confusion on the interwebs about which serial cable to get. I can say the FTDI one from Adafruit works fine. But the ethernet connection worked on the initial installation, so if somebody got lucky, they wouldn't need the serial cable. You would be installing the OS in the blind, which is why I mentioned luck.
The 26.3 rev has issues. The serial port doesn't work well. This problem wasn't evident in the 26.2 rev. USB still doesn't work.
Looks like it's working to me ;). The serial port issues usually come from a loose cable. If you press against the serial pin connectors they should go away.
Alex
I have a SD card with Debian and it works just great on the serial port. No hardware problems on my end.
I just loaded Angstrom. Serial output at the end of the message. Are you using JEOS?
Yeah.
I find the serial port failing to display characters on the JEOS 13.2 rev 26.3. The data is sent, but don't get echoed.
How do you see this is happening?
I'll get a new BBB tomorrow that I'll slam 13.2 onto. Then I can let you know whether it works for me ;).
Works like a charm here. I see every single character very clearly. Maybe you have 2 screen sessions active on the same tty device? Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Sat, Nov 22, 2014 at 09:37:23PM -0800, lists wrote:
On Sat, 22 Nov 2014 14:25:31 -0800 lists <lists@lazygranch.com> wrote:
On Sun, 23 Nov 2014 01:09:20 +0400 "Matwey V. Kornilov" <matwey.kornilov@gmail.com> wrote:
2014-11-23 0:00 GMT+03:00 Zack Piper <zack@apertron.net>:
On Sun, Nov 23, 2014 at 12:50:44AM +0400, Matwey V. Kornilov wrote:
2014-11-22 23:44 GMT+03:00 Zack Piper <zack@apertron.net>:
The BeagleBone Black JeOS image, I have not been using the boot switch button, I have tried it, no LEDs lightup.
Which version? 13.1 13.2 Factory?
Another qustion, does the openSUSE image automatically activate a tty-over-USB at all?
No
-- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru Oops, sorry, I am using 13.2.
Hm, I've tried this couple hours ago, it worked. However, first boot takes several minutes.
Is there a guide on enabling tty-over-USB?
It is disabled in config, I don't know why.
I see a new image (26.3 of JEOS 13,2) has been uploaded. I'm downloading it now, will flog it and report my findings. Note there is no sha256 for the download.
However just to be clear, on rev 26.2, the USB was totally not functional. It would not recognize usb devices plugged into it. lsusb only detected the usb chip on the SBC,
There is some confusion on the interwebs about which serial cable to get. I can say the FTDI one from Adafruit works fine. But the ethernet connection worked on the initial installation, so if somebody got lucky, they wouldn't need the serial cable. You would be installing the OS in the blind, which is why I mentioned luck.
The 26.3 rev has issues. The serial port doesn't work well. This problem wasn't evident in the 26.2 rev. USB still doesn't work.
Here is what I copied from the serial port during installation.
[ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.16.7-2-default (geeko@buildhost) (gcc version 4.8.3 20140627 [gcc-4_8-branch revision 212064] (SUSE Linux) ) #1 SMP Sun Nov 9 17:32:10 UTC 2014 (b648071) [ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] Machine model: TI AM335x BeagleBoory policy:ll CPU(s) started in SVC mode. [ 0.000000] AM335X E PERCPU: Embedded 9 pages/cpu @dfaa9000 s13760 r8192 d14912 u36864 [ 0.000000] Built 1 zonelists in Zone order, mobility groupinable=0 console=ttyO0 showopts [ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes) [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Inode-cache hash table entries: 327allocated 1 'cgroup_disable=memory cgroups 00] Memory: 389572K/52able (7820K kernel cod9K init, 84Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmae00000 (2048 kB) [ 0.000000] vmalloc : 0xe0800000 - 0xff000000 ( 0000 - 0xe000000 - 0xbext : 0xc0208000 - 0xcd1a000 - 0xc0ff4b9c RCU restricRCU callbacks from CPUs: 0. [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1 [ nr_irqs:16 INTC at 0x [ 0.000] OMAP cloc69942ns [ 0.000030] OMAP clocksource: timer1 at 24000000 Hz [ 0.000300x30 [ 0.000342] Calibrating delay loop... 997.78 BogoMIPS (lpj=2494464) [ 0.054388] pid_max: defaultimum: 301 [ 0.054514] Security Framework initialized [ 0.054618] AppArmor: AppArmor initialized [ 0.054784] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.054797] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.055742] Initializing cgrou7] Initializing cgroup subsys net_cls [ 0.055927] Initializing cgroup subsys blkio up static p for 0x8096a7e0 - 0x8096a878 [ 0.128551] Brought up 1 CPUs [ 0.128572] SMP: To0] CPU: All 0.129339 initialized [ 0.133112] VFP _hwmod: tptc1 using broken dt data from edma arget_disabnctrl subsystem tptc2 using broken dt data from edma [ 0.207071] regulator-dummy: no parameters [ 0.219128] NET: Registered protocol family 16 [ 0.221356] DMA: preallocated 256 KiB pool for atomic coherent allocations [ [ 0.229 [ 0.229edma: aliasy exists [version 0.17882] No A 0.237909] hw-breakpoi 0x4 unsupp 0.238722] EXYNOS: PMrs ubsystem initialized: loaded i2c: could tldev for n0.i2c: Drivrobe deferr264508] Netnlabeled trlt [ 0itched to clocksource 0.309856]23193] TCP established hash table096 (order:TCP bind ha[ 0.3233eno registe256 (order:tes) [ h table entorder: 1, 8 [ 0.323rotocol fam Unpacking . [ 4.0oating Point Emulator V0.97 (extended precision) [ available tialise system trusted keyring ubsys (disabled) [ initialized70] Dquot-cs: 1024 (order 0, 4096] msgmni ha 4.014358er SCSI gen252) [ 4.014565] io scheduler noop registered [ io scheduler deadline registered [ 4.014722] io scheduler cfq registered (default) [ 4.016108] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568 [ 4.020683] Serial: 8250/16550 driver, 32 ports, IRQ sharing disabled [ 4.030044] Serial: IMX driver [ 4.030458] msm_serial: driver initialized [ 4.030722] omap_uart 44e09000.serial: no wakeirq for uart0 [ 4.030880] 4 enabled [ 4.771501] serialtered successfully. [ 4.798608] libphy: Fixed MDIO Bus: probed [ 4.803817] mousedev: PS/2 mouse device common for all mice [ 4.815526] ledtrig-cpu: registered to indicate activity on CPUs [ 4.821964] hidraw: raw HID events driver (C) Jiri Kosina [ 4.829821] TCP: cubic registered [ 4.833424] NET: Registered protocol family 10 [ 4.839264] omap_voltage_late_idded [ 4.846020] sr_dev_init: No voltage domain specified for smartreflex0. Cannot initialize [ 4.854523] sr_dev_init: No voltage domain specified for smartreflex1. Cannot initialize [ 4.863709] ThumbEE CPU extension supported. [ 4.868279] Registering SWP/SWPB emulation handler [ 4.873349] SmartReflex Class3 initialized on 1 4.878471] Loading compiled-in X.509 certificates [ 4.888141] AppArmor: AppArmor sha1 policy hashing enabled [ 4.894722] slave hdmi: could not get i2c [ 4.899028] platform hdmi: Driver slave requests probe deferral [ 4.905546] platform 4830e000.lcdc: Driver tilcdc requests probe deferral [ 4.923982] .11 at 400 kHz 0.lcdc: no encoders/connectors found [ 4.947953] tilcdc 4830e000.lcdc: failed to initialize mode setting [ 4.955449] ../drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 4.962359] sr_init: No PMIC hynos5-bus-int failed with error -2 [ 4.989931] vmmcsd_fixed: disabling [ 4.995127] Freeing unused kernel memory: 948K (c0d1a000 - c0e07000) 10.445823] cpsw 4a100000.ethernet: Detected MACID = 1c:ba:8c:a1:ba:28 pport reading read-only switch. assuming write-enable. assigned buice strings: Mfr=3, Product=2, SerialNumber=1 [ 11.222132] usb usb2: Product: MUSB HDRC host drib usb2: Manufacturer: Linux 3.16.7-2-default musb-hcd [ 11.233umber: musb54] hub 2-00731] device-mapper: ioctl: 4.27.0-ioctl (20.135910] lousb2-port1:isk accordi 17.180316] mmcblk0: p1 p2 [ 17.458841] mmcblk0: p1 p2 [ 17.730007] mmcblk0: p1 [ 18.295240] mmcblk0: p1 [ 18.459729] mmcblk0: p1 p2 [ 18.999672] mmcblk0: p1 p2 [ 19.283079] mmcblk0: p1427023] mmcblk0: p1 p2 p3 [ 226441612.9813/mmcblk0p2: 23254/52752 files (0.2% non-contiguous), 169002/210176 blocks [1416441614.641118] Resizing ext4 filesystem on /dev/mmcblk0p2... Resizing the filesystem on /dev/mmcblk0p2 to 7554769 (4k) blocreating boot loader configuration 646943] Pre for /dev/mmcblk0p1, bile or directory 8.338771] device-mapper: uevent: version 1.0.3 [ 148.350213] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com -manager.service, ignoring: Unit e failed toched target Remote File Systems (Pre). d[1]: Reach Systems. ed target Remote File Systems. [ 148.8ormats File System Automount Point. [tomount Po Arbitrary Executable File Formats File System AutomounDirectory Watch. ed target Paths. [ r and Sessioystemd[1]: Starting System Slice. emd[1]: Created slice System Slice. [ 149.211039] systeCreate list of required static device nodes...rrent kernel... ating swap /dev/mmcblk0p3... m OK 2m OK ] Activated swap /dev/mmcblk0p3. [ OK ] Started Create dynamic rule for /dev/root link. ] Reacheev... OK ] S OK ] Started udev Kernel Device Manager. ] Started Load/Save.327381] omP Watchdog [ 151.3arted udev Wait for Complete DevicOK ] Reached target Encrypted Volumes. Starting Activation of LVM2 logi32m OK tarting Restore Sound Card State... [ OK ] Reached target Basic System. Starting Permit User Sessions... Compatibility... Starting YaST2 Firstboot... s. Starting wicked AutoIPv4 supplicant service... Starting wicked DHCPv6 supplicant service... .. nit.d/boot.l OK ] Service. ttyO0... Getty on tty
openSUSE 13Welcome to linux logi ux login: rootPassword: Password: sword:
default (ttyO0).
linux login: roo
m m ls ;34m.local bin
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Is there a bug for this on one of the issue trackers? -- I have nothing fancy or intelligent to put here.
participants (5)
-
Alexander Graf -
Andreas Färber -
lists -
Matwey V. Kornilov -
Zack Piper