[opensuse-arm] Using image 13.2 headless
I copied the 13.2 JeOS-raspberrypi image onto my SD card and tried to use it headless by connecting to it via ssh root@IP-address, which gives me a prompt for the password. However the password linux does not give me access. What is the password or is there something else I should so? Copying the image to a 16 GB SD card gives me four partitions, a small FAT16 BOOT partition at the beginning and a very small empty partition, a large ext4 partition and a swap partition of about 520 MB at the end. The large ext4 partition takes all the remaining space on the SD card. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Using image 13.2 headless
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 11/22/2014 05:38 PM, Freek de Kruijf wrote: I copied the 13.2 JeOS-raspberrypi image onto my SD card and tried to use it headless by connecting to it via ssh root@IP-address, which gives me a prompt for the password. However the password linux does not give me access. What is the password or is there something else I should so? i don't remember if it was the factory or 13.2 image, but i had to recreate the ssh keys on the pi to log in. of course, you'll need a screen and keyboard connected to your pi for that ... # ssh-keygen -t dsa -f /etc/ssh/ssh_host_dsa_key # ssh-keygen -t rsa -f /etc/ssh/ssh_host_rsa_key - -- Sebastian Kratz @ProhtMeyhet -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJUcMpuAAoJEPy7f1qF9ovT35gP/1Q3HEA2asOPYHmxzzF24ldV Wjh1A2rHU4PSKsZ9+Y8SFreogcHOlRL6DOjVJOW+xgWdMfinxN2yqP0DlemPsUk6 VDbAKqMzvIuUF780ZMLWhnptJF4CfMr9r5en73/Lov1aFnRMNton+XJK7ZfA7W25 GR3G5yxD4fMSlWtAjpjGzjDrzLZN+T/FBm1vqzN8VgwyHoYAQ+HcI5yfWa0OKq6J EnMACsr7v04RPU4+fLC5aujq6cwcm1PUXiCZ8tRytlnhELnUq9Xmo547X+9OPk/m 6hYc6z81I56/FpBXc4mOQJFGkea1rkU9AEiHqbOhQdeFr8SPqlrY463CJoaT61C0 bXUOnhnu9SojxS7epNYgcFXipeoXXnaWMkNNb48At8xKk8JpGagHgT+0KVyDvq5E HAKEGQKX5hoSXErT99aeB3ZUBg2z8g+9Qd177qa5GT8wR9Yi/a/3YqN+YefXup4P iuyeCsR5OpQv9r0MrsELzZNc0pJ8PvqwGpDIbf6MJFM+JXJ7UVcuV1h3d+wUi4L5 7mQQXMF+eqxrkKgs0km7/gpa+Yi0u4tGEsksdX2ClE9rnKbl0hCvOCtDb8N5MyvZ 3iqVfLggd/HVfVShOS+qjmvqdIvP/8poe5zzsM6h2R6Wu3av7AkXeMkgeQJFsyfI yHQknblsi2XFIJ97Kn8p =WL9C -END PGP SIGNATURE- -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Using image 13.2 headless
Hi, Am 22.11.2014 um 18:39 schrieb Sebastian Kratz: On 11/22/2014 05:38 PM, Freek de Kruijf wrote: I copied the 13.2 JeOS-raspberrypi image onto my SD card and tried to use it headless by connecting to it via ssh root@IP-address, which gives me a prompt for the password. However the password linux does not give me access. What is the password or is there something else I should so? i don't remember if it was the factory or 13.2 image, but i had to recreate the ssh keys on the pi to log in. of course, you'll need a screen and keyboard connected to your pi for that ... # ssh-keygen -t dsa -f /etc/ssh/ssh_host_dsa_key # ssh-keygen -t rsa -f /etc/ssh/ssh_host_rsa_key The more straightforward way would be to disable YaST firstboot by removing some file. Check the openSUSE Wiki for details. That then allows the pending systemd services to run. Regards, Andreas -- SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 21284 AG Nürnberg signature.asc Description: OpenPGP digital signature
[opensuse-arm] BeagleBone Black stuck at 3 LEDs.
Hi, I'm currently debugging my BeagleBone Black, when booting, it gets stuck at 3 LEDs. Is there anyway to debug it without a miniHDMI cable or serial cable? Thanks. -- I have nothing fancy or intelligent to put here. pgpIokEpcB3zR.pgp Description: PGP signature
[opensuse-arm] Re: BeagleBone Black stuck at 3 LEDs.
22.11.2014 21:28, Zack Piper пишет: Hi, I'm currently debugging my BeagleBone Black, when booting, it gets stuck at 3 LEDs. Is there anyway to debug it without a miniHDMI cable or serial cable? Thanks. I don't think so, you need serial cable. By the way, did you remember to press boot-switch button on powering on? And what image did you try? -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Re: BeagleBone Black stuck at 3 LEDs.
2014-11-22 23:44 GMT+03:00 Zack Piper z...@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://0x2...@jabber.ru -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Re: BeagleBone Black stuck at 3 LEDs.
On Sun, Nov 23, 2014 at 12:50:44AM +0400, Matwey V. Kornilov wrote: 2014-11-22 23:44 GMT+03:00 Zack Piper z...@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://0x2...@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. pgpOeQbiXTMlO.pgp Description: PGP signature
Re: [opensuse-arm] Using image 13.2 headless
Op zaterdag 22 november 2014 18:59:47 schreef Andreas Färber: Hi, I made a mistake in copying the image to the SD card, so I booted an old image. Sorry about that. However after that, I copied the image in the right way and and found that the SD card now contains a GPT formatted image with a FAT partition, a small ext3 /boot partition and the ext4 system / partition. After starting gparted it advised to move the backup GPT table to the end of the device, which I did. With gparted I enlarged the system partition, added a swap partition and after that removed the empty file /var/lib/YaST2/reconfig_system . However after booting the system headless, the network did not appear. I documented this on the wiki. Please help me to get it running. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Re: BeagleBone Black stuck at 3 LEDs.
Am 22.11.2014 um 22:09 schrieb Matwey V. Kornilov: 2014-11-23 0:00 GMT+03:00 Zack Piper z...@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+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Re: BeagleBone Black stuck at 3 LEDs.
On Sun, Nov 23, 2014 at 01:09:20AM +0400, Matwey V. Kornilov wrote: 2014-11-23 0:00 GMT+03:00 Zack Piper z...@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 z...@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://0x2...@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://0x2...@jabber.ru -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@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. pgp8uXXLO7ECp.pgp Description: PGP signature
[opensuse-arm] Re: BeagleBone Black stuck at 3 LEDs.
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+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Re: BeagleBone Black stuck at 3 LEDs.
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 afaer...@suse.de: Am 22.11.2014 um 22:09 schrieb Matwey V. Kornilov: 2014-11-23 0:00 GMT+03:00 Zack Piper z...@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://0x2...@jabber.ru -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@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. pgpO8oFXqdK8m.pgp Description: PGP signature
Re: [opensuse-arm] Re: BeagleBone Black stuck at 3 LEDs.
On Sun, 23 Nov 2014 01:09:20 +0400 Matwey V. Kornilov matwey.korni...@gmail.com wrote: 2014-11-23 0:00 GMT+03:00 Zack Piper z...@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 z...@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://0x2...@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+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Using image 13.2 headless
Am 22.11.2014 um 22:07 schrieb Freek de Kruijf fr...@opensuse.org: Op zaterdag 22 november 2014 18:59:47 schreef Andreas Färber: Hi, I made a mistake in copying the image to the SD card, so I booted an old image. Sorry about that. However after that, I copied the image in the right way and and found that the SD card now contains a GPT formatted image with a FAT partition, a small ext3 /boot partition and the ext4 system / partition. After starting gparted it advised to move the backup GPT table to the end of the device, which I did. With gparted I enlarged the system partition, added a swap partition and after that removed the empty file /var/lib/YaST2/reconfig_system . However after booting the system headless, the network did not appear. I documented this on the wiki. Please help me to get it running. Please just dd the image onto your sd card and then boot it up straight from there. The first boot will fix up the gpt headers and repartition the card :). Do you happen to have a ttl serial cable you could connect to the board to see what it's doing? Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Re: BeagleBone Black stuck at 3 LEDs.
On Sat, 22 Nov 2014 14:25:31 -0800 lists li...@lazygranch.com wrote: On Sun, 23 Nov 2014 01:09:20 +0400 Matwey V. Kornilov matwey.korni...@gmail.com wrote: 2014-11-23 0:00 GMT+03:00 Zack Piper z...@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 z...@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://0x2...@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.00] Initializing cgroup subsys cpuacct [0.00] 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.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [0.00] Machine model: TI AM335x BeagleBoory policy:ll CPU(s) started in SVC mode. [0.00] AM335X E PERCPU: Embedded 9 pages/cpu @dfaa9000 s13760 r8192 d14912 u36864 [0.00] Built 1 zonelists in Zone order, mobility groupinable=0 console=ttyO0 showopts [0.00] PID hash table entries: 2048 (order: 1, 8192 bytes) [0.00] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) [0.00] Inode-cache hash table entries: 327allocated 1 'cgroup_disable=memory cgroups 00] Memory: 389572K/52able (7820K kernel cod9K init, 84Virtual kernel memory layout: [0.00] vector : 0x - 0x1000 ( 4 kB) [0.00] fixmae0 (2048 kB) [0.00] vmalloc : 0xe080 - 0xff00 ( - 0xe00 - 0xbext : 0xc0208000 - 0xcd1a000 - 0xc0ff4b9c RCU restricRCU callbacks from CPUs: 0. [0.00] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1 [ nr_irqs:16 INTC at 0x [0.000] OMAP cloc69942ns [0.30] OMAP clocksource: timer1 at 2400 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
Re: [opensuse-arm] Re: BeagleBone Black stuck at 3 LEDs.
Am 23.11.2014 um 06:37 schrieb lists li...@lazygranch.com: On Sat, 22 Nov 2014 14:25:31 -0800 lists li...@lazygranch.com wrote: On Sun, 23 Nov 2014 01:09:20 +0400 Matwey V. Kornilov matwey.korni...@gmail.com wrote: 2014-11-23 0:00 GMT+03:00 Zack Piper z...@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 z...@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://0x2...@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+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
