Hi all,
I've generated Fedora 20 images for Allwinner A{10,20,...} devices using Hans' scripts. It's basically a stock Xfce image with sunxi u-boot and sunxi-3.4 linux kernel. Available here: [1], please read the README [2] file for installation instructions. I've only tested on an A10 based Cubieboard so far and I would be thankful for any feedback; reports about other boards that should be supported in particular.
[1] http://fedorapeople.org/~lkundrak/a10-images/ [2] http://fedorapeople.org/~lkundrak/a10-images/README
♥, Lubo
Hi all,
On 02/07/2014 07:22 AM, Lubomir Rintel wrote:
Hi all,
I've generated Fedora 20 images for Allwinner A{10,20,...} devices using Hans' scripts. It's basically a stock Xfce image with sunxi u-boot and sunxi-3.4 linux kernel. Available here: [1], please read the README [2] file for installation instructions. I've only tested on an A10 based Cubieboard so far and I would be thankful for any feedback; reports about other boards that should be supported in particular.
[1] http://fedorapeople.org/~lkundrak/a10-images/ [2] http://fedorapeople.org/~lkundrak/a10-images/README
♥, Lubo
Lubo, many thanks for working on this!
Regards,
Hans
On Fri, Feb 07, 2014 at 02:12:50PM +0100, Hans de Goede wrote:
Hi all,
On 02/07/2014 07:22 AM, Lubomir Rintel wrote:
Hi all,
I've generated Fedora 20 images for Allwinner A{10,20,...} devices using Hans' scripts. It's basically a stock Xfce image with sunxi u-boot and sunxi-3.4 linux kernel. Available here: [1], please read the README [2] file for installation instructions. I've only tested on an A10 based Cubieboard so far and I would be thankful for any feedback; reports about other boards that should be supported in particular.
[1] http://fedorapeople.org/~lkundrak/a10-images/ [2] http://fedorapeople.org/~lkundrak/a10-images/README
♥, Lubo
Lubo, many thanks for working on this!
Hum, I'm getting 403 Forbidden right now when trying to fetch the .xz, but the README permissions are right !
thinkpad:~/Cubie -> wget http://fedorapeople.org/~lkundrak/a10-images/Fedora-Xfce-armhfp-20-a10-1-sda... ... Connecting to fedorapeople.org (fedorapeople.org)|152.19.134.191|:80... connected. HTTP request sent, awaiting response... 403 Forbidden 2014-02-08 20:35:29 ERROR 403: Forbidden.
thinkpad:~/Cubie ->
same with Firefox, also tried from a server in France in case it could be related to a chinese IP address, same 403 ...
thanks for looking ;-)
Daniel
On Sat, 2014-02-08 at 20:39 +0800, Daniel Veillard wrote:
On Fri, Feb 07, 2014 at 02:12:50PM +0100, Hans de Goede wrote:
Hi all,
On 02/07/2014 07:22 AM, Lubomir Rintel wrote:
Hi all,
I've generated Fedora 20 images for Allwinner A{10,20,...} devices using Hans' scripts. It's basically a stock Xfce image with sunxi u-boot and sunxi-3.4 linux kernel. Available here: [1], please read the README [2] file for installation instructions. I've only tested on an A10 based Cubieboard so far and I would be thankful for any feedback; reports about other boards that should be supported in particular.
[1] http://fedorapeople.org/~lkundrak/a10-images/ [2] http://fedorapeople.org/~lkundrak/a10-images/README
♥, Lubo
Lubo, many thanks for working on this!
Hum, I'm getting 403 Forbidden right now when trying to fetch the .xz, but the README permissions are right !
Whoops! Should be fixed now. Thanks for the heads up!
Lubo
On Sat, Feb 08, 2014 at 05:54:07PM +0100, Lubomir Rintel wrote:
On Sat, 2014-02-08 at 20:39 +0800, Daniel Veillard wrote:
On Fri, Feb 07, 2014 at 02:12:50PM +0100, Hans de Goede wrote:
Hi all,
On 02/07/2014 07:22 AM, Lubomir Rintel wrote:
Hi all,
I've generated Fedora 20 images for Allwinner A{10,20,...} devices using Hans' scripts. It's basically a stock Xfce image with sunxi u-boot and sunxi-3.4 linux kernel. Available here: [1], please read the README [2] file for installation instructions. I've only tested on an A10 based Cubieboard so far and I would be thankful for any feedback; reports about other boards that should be supported in particular.
[1] http://fedorapeople.org/~lkundrak/a10-images/ [2] http://fedorapeople.org/~lkundrak/a10-images/README
♥, Lubo
Lubo, many thanks for working on this!
Hum, I'm getting 403 Forbidden right now when trying to fetch the .xz, but the README permissions are right !
Whoops! Should be fixed now. Thanks for the heads up!
yup, got it now :-) thanks for fixing it ! I will give it a try on Cubietruck (hopefully today) and will report !
Daniel
On Sun, Feb 09, 2014 at 06:29:32PM +0800, Daniel Veillard wrote:
On Sat, Feb 08, 2014 at 05:54:07PM +0100, Lubomir Rintel wrote:
On Sat, 2014-02-08 at 20:39 +0800, Daniel Veillard wrote:
On Fri, Feb 07, 2014 at 02:12:50PM +0100, Hans de Goede wrote:
Hi all,
On 02/07/2014 07:22 AM, Lubomir Rintel wrote:
Hi all,
I've generated Fedora 20 images for Allwinner A{10,20,...} devices using Hans' scripts. It's basically a stock Xfce image with sunxi u-boot and sunxi-3.4 linux kernel. Available here: [1], please read the README [2] file for installation instructions. I've only tested on an A10 based Cubieboard so far and I would be thankful for any feedback; reports about other boards that should be supported in particular.
[1] http://fedorapeople.org/~lkundrak/a10-images/ [2] http://fedorapeople.org/~lkundrak/a10-images/README
♥, Lubo
Lubo, many thanks for working on this!
Hum, I'm getting 403 Forbidden right now when trying to fetch the .xz, but the README permissions are right !
Whoops! Should be fixed now. Thanks for the heads up!
yup, got it now :-) thanks for fixing it ! I will give it a try on Cubietruck (hopefully today) and will report !
it boots on the truck, i get graphical mode and could do the config. It seems however that the resize of filesystem + reboot failed, but except for this this looks like it is working !
Daniel
On 02/07/2014 07:22 AM, Lubomir Rintel wrote:
Hi all,
I've generated Fedora 20 images for Allwinner A{10,20,...} devices using Hans' scripts. It's basically a stock Xfce image with sunxi u-boot and sunxi-3.4 linux kernel. Available here: [1], please read the README [2] file for installation instructions. I've only tested on an A10 based Cubieboard so far and I would be thankful for any feedback; reports about other boards that should be supported in particular.
[1] http://fedorapeople.org/~lkundrak/a10-images/ [2] http://fedorapeople.org/~lkundrak/a10-images/README
Hi, I just got my first arm board - Phoenix A20 http://linux-sunxi.org/Phoenix_Board http://www.swiftboard.org/wiki/index.php?title=%E9%A6%96%E9%A1%B5
It uses Allwinner A20 SoC, but the README file for the remix image does not mention this board. Can I use it with u-boot for different A20 board?
Michal
Hi,
On 03/20/2014 07:11 PM, Michal Hlavinka wrote:
On 02/07/2014 07:22 AM, Lubomir Rintel wrote:
Hi all,
I've generated Fedora 20 images for Allwinner A{10,20,...} devices using Hans' scripts. It's basically a stock Xfce image with sunxi u-boot and sunxi-3.4 linux kernel. Available here: [1], please read the README [2] file for installation instructions. I've only tested on an A10 based Cubieboard so far and I would be thankful for any feedback; reports about other boards that should be supported in particular.
[1] http://fedorapeople.org/~lkundrak/a10-images/ [2] http://fedorapeople.org/~lkundrak/a10-images/README
Hi, I just got my first arm board - Phoenix A20 http://linux-sunxi.org/Phoenix_Board http://www.swiftboard.org/wiki/index.php?title=%E9%A6%96%E9%A1%B5
It uses Allwinner A20 SoC, but the README file for the remix image does not mention this board. Can I use it with u-boot for different A20 board?
You can try, but it usually best to use a u-boot + fex file tailored fpr the board. You can start by following: http://linux-sunxi.org/New_Device_howto
Then once we have the necessary info on the board, we can add a config for it to u-boot, and then you can build your own u-boot for it.
Regards,
Hans
p.s.
The upstream linux-sunxi mailinglist is a better place for sunxi specific questions like these.
Hi all,
I've generated Fedora 20 images for Allwinner A{10,20,...} devices using Hans' scripts. It's basically a stock Xfce image with sunxi u-boot and sunxi-3.4 linux kernel. Available here: [1], please read the README [2] file for installation instructions. I've only tested on an A10 based Cubieboard so far and I would be thankful for any feedback; reports about other boards that should be supported in particular.
[1] http://fedorapeople.org/~lkundrak/a10-images/ [2] http://fedorapeople.org/~lkundrak/a10-images/README
♥, Lubo
Thanks so much for this. I was able to use this successfully on an MK802 stick.
When I try it on my hackberry though I am unable to use the USB ports (yes I used the hackberry option in the select-board script). I have tried both of the ports after cycling power, also both ports with unpowered USB hub, and also both ports with a powered USB hub to no avail.
Then to double check I booted into the original android and USB worked fine.
Any suggestions gratefully appreciated.
Has anyone been able to use this remix on their hackbery?
Tim Krantz
Anyone working on a FC21 image for the A10? My device does not give me access to a serial monitor so am hoping to change the dtb file for the A10 on a remix build and get this unit booting on 3.17. Thanks
Hi all,
I've generated Fedora 20 images for Allwinner A{10,20,...} devices using Hans' scripts. It's basically a stock Xfce image with sunxi u-boot and sunxi-3.4 linux kernel. Available here: [1], please read the README [2] file for installation instructions. I've only tested on an A10 based Cubieboard so far and I would be thankful for any feedback; reports about other boards that should be supported in particular.
[1] http://fedorapeople.org/~lkundrak/a10-images/ [2] http://fedorapeople.org/~lkundrak/a10-images/README
♥, Lubo
Is development at the point where I can install this: http://mirror.optus.net/fedora/linux/releases/test/21-Beta/Images/armhfp/Fed...
to an sdcard
then install u-boot for the A10 and be able to boot the device headless since hdmi is not yet working? Again I have no serial console available.
Thanks
On 06/12/14 09:57, Robert Brown wrote:
Anyone working on a FC21 image for the A10? My device does not give me access to a serial monitor so am hoping to change the dtb file for the A10 on a remix build and get this unit booting on 3.17. Thanks
Hi all,
I've generated Fedora 20 images for Allwinner A{10,20,...} devices using Hans' scripts. It's basically a stock Xfce image with sunxi u-boot and sunxi-3.4 linux kernel. Available here: [1], please read the README [2] file for installation instructions. I've only tested on an A10 based Cubieboard so far and I would be thankful for any feedback; reports about other boards that should be supported in particular.
[1] http://fedorapeople.org/~lkundrak/a10-images/ [2] http://fedorapeople.org/~lkundrak/a10-images/README
♥, Lubo
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
On 12/06/2014 06:31 AM, Robert Brown wrote:
Is development at the point where I can install this: http://mirror.optus.net/fedora/linux/releases/test/21-Beta/Images/armhfp/Fed...
to an sdcard
then install u-boot for the A10 and be able to boot the device headless since hdmi is not yet working? Again I have no serial console available.
Well we are in final RC5 now with production on the 9th!
The uboot developer has HDMI working now, but we won't see it until F22 beta. It needs the current development uboot and a 3.19 kernel (current Rawhide kernel is 3.18). Reverse engineering what Allwinner did for video was considered 'HARD' on the Sunxi uboot website. He also has a sata multiplexer! He told me to be patient :)
For the serial console, some are reporting things are working in the latest release, but I am still doing the following:
Mount the SD card after the build then:
vi /.../__boot/extlinux/extlinux.conf
append:
console=ttyS0,115200
to the append line.
save this then do your first boot on your A10. BTW, I am using the Cubieboard2 and Cubietrucks which are A20 boards. So I also want my CT WiFi and BT to work. Patience grasshopper...
Thanks
On 06/12/14 09:57, Robert Brown wrote:
Anyone working on a FC21 image for the A10? My device does not give me access to a serial monitor so am hoping to change the dtb file for the A10 on a remix build and get this unit booting on 3.17. Thanks
Hi all,
I've generated Fedora 20 images for Allwinner A{10,20,...} devices using Hans' scripts. It's basically a stock Xfce image with sunxi u-boot and sunxi-3.4 linux kernel. Available here: [1], please read the README [2] file for installation instructions. I've only tested on an A10 based Cubieboard so far and I would be thankful for any feedback; reports about other boards that should be supported in particular.
[1] http://fedorapeople.org/~lkundrak/a10-images/ [2] http://fedorapeople.org/~lkundrak/a10-images/README
♥, Lubo
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
On 12/05/2014 05:57 PM, Robert Brown wrote:
Anyone working on a FC21 image for the A10? My device does not give me access to a serial monitor so am hoping to change the dtb file for the A10 on a remix build and get this unit booting on 3.17. Thanks
And F21 for our arm boards is NOT a remix, but mainline. No more excluding the kernel when doing a 'yum update'!
On Fri, Dec 5, 2014 at 10:57 PM, Robert Brown rebrown@exemail.com.au wrote:
Anyone working on a FC21 image for the A10? My device does not give me access to a serial monitor so am hoping to change the dtb file for the A10 on a remix build and get this unit booting on 3.17. Thanks
You don't mention what your device is but a change in the .dtb won't fix the lack of display, there's a complete lack of driver,
Peter
I've generated Fedora 20 images for Allwinner A{10,20,...} devices using Hans' scripts. It's basically a stock Xfce image with sunxi u-boot and sunxi-3.4 linux kernel. Available here: [1], please read the README [2] file for installation instructions. I've only tested on an A10 based Cubieboard so far and I would be thankful for any feedback; reports about other boards that should be supported in particular.
[1] http://fedorapeople.org/~lkundrak/a10-images/ [2] http://fedorapeople.org/~lkundrak/a10-images/README
♥, Lubo
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Thanks for the reply. On 08/12/14 14:43, Peter Robinson wrote:
On Fri, Dec 5, 2014 at 10:57 PM, Robert Brown rebrown@exemail.com.au wrote:
Anyone working on a FC21 image for the A10? My device does not give me access to a serial monitor so am hoping to change the dtb file for the A10 on a remix build and get this unit booting on 3.17. Thanks
You don't mention what your device is but a change in the .dtb won't fix the lack of display, there's a complete lack of driver,
Yes my wording could have been better. Changing the .dtb was only about getting the device to boot as I realise hdmi is not yet ready. The device is a Rikomagic MK802II. Booting it headless with 3.17 is my aim but the soldering job for a serial console is a challenge beyond my soldering skills - see http://www.rikomagic.co.uk/forum/viewtopic.php?f=6&t=2488 so am hoping some-one with a compatible device such as Mele A1000 or CB1 could develop an image. A howto for the build and to get wireless configured for an ssh connection is an alternative.
Thanks Rob
I've generated Fedora 20 images for Allwinner A{10,20,...} devices using Hans' scripts. It's basically a stock Xfce image with sunxi u-boot and sunxi-3.4 linux kernel. Available here: [1], please read the README [2] file for installation instructions. I've only tested on an A10 based Cubieboard so far and I would be thankful for any feedback; reports about other boards that should be supported in particular.
[1] http://fedorapeople.org/~lkundrak/a10-images/ [2] http://fedorapeople.org/~lkundrak/a10-images/README
♥, Lubo
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
On 12/08/2014 05:16 AM, Robert Brown wrote:
Thanks for the reply. On 08/12/14 14:43, Peter Robinson wrote:
On Fri, Dec 5, 2014 at 10:57 PM, Robert Brown rebrown@exemail.com.au wrote:
Anyone working on a FC21 image for the A10? My device does not give me access to a serial monitor so am hoping to change the dtb file for the A10 on a remix build and get this unit booting on 3.17. Thanks
You don't mention what your device is but a change in the .dtb won't fix the lack of display, there's a complete lack of driver,
Yes my wording could have been better. Changing the .dtb was only about getting the device to boot as I realise hdmi is not yet ready. The device is a Rikomagic MK802II. Booting it headless with 3.17 is my aim but the soldering job for a serial console is a challenge beyond my soldering skills - see http://www.rikomagic.co.uk/forum/viewtopic.php?f=6&t=2488 so am hoping some-one with a compatible device such as Mele A1000 or CB1 could develop an image. A howto for the build and to get wireless configured for an ssh connection is an alternative.
You could just try booting without serial console if you provide --norootpass on building the SD card. SSHD permits logging in as root, just don't do this on the Internet, as you are sitting wide open!
Thinking about the firstboot script the only really needed things it does is set the timezone and root password. You can add your user after logging in as root.
I would suspect that if no serial console, it just comes up as ready as possible. All you need is your WiFi to be working; that is a pretty big assumption. You might have to get a supported ethernet dongle.
What has happened in booting without a serial console so far?
Thanks Rob
I've generated Fedora 20 images for Allwinner A{10,20,...} devices using Hans' scripts. It's basically a stock Xfce image with sunxi u-boot and sunxi-3.4 linux kernel. Available here: [1], please read the README [2] file for installation instructions. I've only tested on an A10 based Cubieboard so far and I would be thankful for any feedback; reports about other boards that should be supported in particular.
[1] http://fedorapeople.org/~lkundrak/a10-images/ [2] http://fedorapeople.org/~lkundrak/a10-images/README
♥, Lubo
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
On 08/12/14 22:11, Robert Moskowitz wrote:
On 12/08/2014 05:16 AM, Robert Brown wrote:
Thanks for the reply. On 08/12/14 14:43, Peter Robinson wrote:
On Fri, Dec 5, 2014 at 10:57 PM, Robert Brown rebrown@exemail.com.au wrote:
Anyone working on a FC21 image for the A10? My device does not give me access to a serial monitor so am hoping to change the dtb file for the A10 on a remix build and get this unit booting on 3.17. Thanks
You don't mention what your device is but a change in the .dtb won't fix the lack of display, there's a complete lack of driver,
Yes my wording could have been better. Changing the .dtb was only about getting the device to boot as I realise hdmi is not yet ready. The device is a Rikomagic MK802II. Booting it headless with 3.17 is my aim but the soldering job for a serial console is a challenge beyond my soldering skills - see http://www.rikomagic.co.uk/forum/viewtopic.php?f=6&t=2488 so am hoping some-one with a compatible device such as Mele A1000 or CB1 could develop an image. A howto for the build and to get wireless configured for an ssh connection is an alternative.
You could just try booting without serial console if you provide --norootpass on building the SD card. SSHD permits logging in as root, just don't do this on the Internet, as you are sitting wide open!
I think I would need to manually configure and select my local network SSID and passphrase to get it on the network so I can ssh to it. A new world for me under systemd.
Thinking about the firstboot script the only really needed things it does is set the timezone and root password. You can add your user after logging in as root.
I would suspect that if no serial console, it just comes up as ready as possible. All you need is your WiFi to be working; that is a pretty big assumption. You might have to get a supported ethernet dongle.
As above.
What has happened in booting without a serial console so far?
I am running blind so I either see a new connection open up when I do an nmap search from my PC or more likely there is no new connection for the reasons I mention. The real trick is to know if I have even had a successful boot.
Thanks Rob
I've generated Fedora 20 images for Allwinner A{10,20,...} devices using Hans' scripts. It's basically a stock Xfce image with sunxi u-boot and sunxi-3.4 linux kernel. Available here: [1], please read the README [2] file for installation instructions. I've only tested on an A10 based Cubieboard so far and I would be thankful for any feedback; reports about other boards that should be supported in particular.
[1] http://fedorapeople.org/~lkundrak/a10-images/ [2] http://fedorapeople.org/~lkundrak/a10-images/README
♥, Lubo
On 12/08/2014 06:30 AM, Robert Brown wrote:
On 08/12/14 22:11, Robert Moskowitz wrote:
On 12/08/2014 05:16 AM, Robert Brown wrote:
Thanks for the reply. On 08/12/14 14:43, Peter Robinson wrote:
On Fri, Dec 5, 2014 at 10:57 PM, Robert Brown rebrown@exemail.com.au wrote:
Anyone working on a FC21 image for the A10? My device does not give me access to a serial monitor so am hoping to change the dtb file for the A10 on a remix build and get this unit booting on 3.17. Thanks
You don't mention what your device is but a change in the .dtb won't fix the lack of display, there's a complete lack of driver,
Yes my wording could have been better. Changing the .dtb was only about getting the device to boot as I realise hdmi is not yet ready. The device is a Rikomagic MK802II. Booting it headless with 3.17 is my aim but the soldering job for a serial console is a challenge beyond my soldering skills - see http://www.rikomagic.co.uk/forum/viewtopic.php?f=6&t=2488 so am hoping some-one with a compatible device such as Mele A1000 or CB1 could develop an image. A howto for the build and to get wireless configured for an ssh connection is an alternative.
You could just try booting without serial console if you provide --norootpass on building the SD card. SSHD permits logging in as root, just don't do this on the Internet, as you are sitting wide open!
I think I would need to manually configure and select my local network SSID and passphrase to get it on the network so I can ssh to it. A new world for me under systemd.
After first boot, you can see what interface name it used, the create an appropriate ifcfg- file. They still work.
Thinking about the firstboot script the only really needed things it does is set the timezone and root password. You can add your user after logging in as root.
I would suspect that if no serial console, it just comes up as ready as possible. All you need is your WiFi to be working; that is a pretty big assumption. You might have to get a supported ethernet dongle.
As above.
What has happened in booting without a serial console so far?
I am running blind so I either see a new connection open up when I do an nmap search from my PC or more likely there is no new connection for the reasons I mention. The real trick is to know if I have even had a successful boot.
What else are you going to do right now but try?
Thanks Rob
I've generated Fedora 20 images for Allwinner A{10,20,...} devices using Hans' scripts. It's basically a stock Xfce image with sunxi u-boot and sunxi-3.4 linux kernel. Available here: [1], please read the README [2] file for installation instructions. I've only tested on an A10 based Cubieboard so far and I would be thankful for any feedback; reports about other boards that should be supported in particular.
[1] http://fedorapeople.org/~lkundrak/a10-images/ [2] http://fedorapeople.org/~lkundrak/a10-images/README
♥, Lubo
On 08/12/14 22:36, Robert Moskowitz wrote:
On 12/08/2014 06:30 AM, Robert Brown wrote:
On 08/12/14 22:11, Robert Moskowitz wrote:
On 12/08/2014 05:16 AM, Robert Brown wrote:
Thanks for the reply. On 08/12/14 14:43, Peter Robinson wrote:
On Fri, Dec 5, 2014 at 10:57 PM, Robert Brown rebrown@exemail.com.au wrote:
Anyone working on a FC21 image for the A10? My device does not give me access to a serial monitor so am hoping to change the dtb file for the A10 on a remix build and get this unit booting on 3.17. Thanks
You don't mention what your device is but a change in the .dtb won't fix the lack of display, there's a complete lack of driver,
Yes my wording could have been better. Changing the .dtb was only about getting the device to boot as I realise hdmi is not yet ready. The device is a Rikomagic MK802II. Booting it headless with 3.17 is my aim but the soldering job for a serial console is a challenge beyond my soldering skills - see http://www.rikomagic.co.uk/forum/viewtopic.php?f=6&t=2488 so am hoping some-one with a compatible device such as Mele A1000 or CB1 could develop an image. A howto for the build and to get wireless configured for an ssh connection is an alternative.
You could just try booting without serial console if you provide --norootpass on building the SD card. SSHD permits logging in as root, just don't do this on the Internet, as you are sitting wide open!
I think I would need to manually configure and select my local network SSID and passphrase to get it on the network so I can ssh to it. A new world for me under systemd.
After first boot, you can see what interface name it used, the create an appropriate ifcfg- file. They still work.
Thinking about the firstboot script the only really needed things it does is set the timezone and root password. You can add your user after logging in as root.
I would suspect that if no serial console, it just comes up as ready as possible. All you need is your WiFi to be working; that is a pretty big assumption. You might have to get a supported ethernet dongle.
As above.
What has happened in booting without a serial console so far?
I am running blind so I either see a new connection open up when I do an nmap search from my PC or more likely there is no new connection for the reasons I mention. The real trick is to know if I have even had a successful boot.
What else are you going to do right now but try?
So on my attempts using Fedora-LXDE-armhfp-21-5-sda.raw.xz written to the sdcard using the manual instructions here https://fedoraproject.org/wiki/Architectures/ARM/F21/Installation including writing the appropriate u-boot to the media
and setting up wpa using tips from http://wiki.centos.org/HowTos/Laptops/WpaSupplicant with edits of /etc/wpa_supplicant/wpa_supplicant.conf and /etc/sysconfig/network-scripts/ifcfg-wlan0
I don't believe the boot is getting very far as messages in /var/log is empty.
Maybe because I am not yet logged in. Tried setting autologin in lxdm.conf.
Still tryin' stuff.
On 12/13/2014 01:52 AM, Robert Brown wrote:
On 08/12/14 22:36, Robert Moskowitz wrote:
On 12/08/2014 06:30 AM, Robert Brown wrote:
On 08/12/14 22:11, Robert Moskowitz wrote:
On 12/08/2014 05:16 AM, Robert Brown wrote:
Thanks for the reply. On 08/12/14 14:43, Peter Robinson wrote:
On Fri, Dec 5, 2014 at 10:57 PM, Robert Brown rebrown@exemail.com.au wrote: > Anyone working on a FC21 image for the A10? My device does not > give me > access to a serial monitor so am hoping to change the dtb file > for the A10 > on a remix build and get this unit booting on 3.17. > Thanks You don't mention what your device is but a change in the .dtb won't fix the lack of display, there's a complete lack of driver,
Yes my wording could have been better. Changing the .dtb was only about getting the device to boot as I realise hdmi is not yet ready. The device is a Rikomagic MK802II. Booting it headless with 3.17 is my aim but the soldering job for a serial console is a challenge beyond my soldering skills - see http://www.rikomagic.co.uk/forum/viewtopic.php?f=6&t=2488 so am hoping some-one with a compatible device such as Mele A1000 or CB1 could develop an image. A howto for the build and to get wireless configured for an ssh connection is an alternative.
You could just try booting without serial console if you provide --norootpass on building the SD card. SSHD permits logging in as root, just don't do this on the Internet, as you are sitting wide open!
I think I would need to manually configure and select my local network SSID and passphrase to get it on the network so I can ssh to it. A new world for me under systemd.
After first boot, you can see what interface name it used, the create an appropriate ifcfg- file. They still work.
Thinking about the firstboot script the only really needed things it does is set the timezone and root password. You can add your user after logging in as root.
I would suspect that if no serial console, it just comes up as ready as possible. All you need is your WiFi to be working; that is a pretty big assumption. You might have to get a supported ethernet dongle.
As above.
What has happened in booting without a serial console so far?
I am running blind so I either see a new connection open up when I do an nmap search from my PC or more likely there is no new connection for the reasons I mention. The real trick is to know if I have even had a successful boot.
What else are you going to do right now but try?
So on my attempts using Fedora-LXDE-armhfp-21-5-sda.raw.xz written to the sdcard using the manual instructions here https://fedoraproject.org/wiki/Architectures/ARM/F21/Installation including writing the appropriate u-boot to the media
and setting up wpa using tips from http://wiki.centos.org/HowTos/Laptops/WpaSupplicant with edits of /etc/wpa_supplicant/wpa_supplicant.conf and /etc/sysconfig/network-scripts/ifcfg-wlan0
Do you know what ethernet name is being used? Since your WiFi is a USB dongle, there are a lot of possiblities. All the more reason for journalctl.
If you know the MAC address you can create:
/etc/udev/rules.d/70-persistent-net.rules
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="02:c3:04:01:77:c3", ATTR{type}=="1", KERNEL=="eth*", NAME="wlan0"
This will 'fix' the name you need for ifcfg-wlan0
I don't believe the boot is getting very far as messages in /var/log is empty.
No /var/log/messages anymore. It is all journalctl. Look in that directory.
Maybe because I am not yet logged in. Tried setting autologin in lxdm.conf.
Would not know about lxdm.conf
For the benefit of others this is about booting this device without having serial console or a monitor to view first boot prompts. On 14/12/14 11:27, Robert Moskowitz wrote:
On 12/13/2014 01:52 AM, Robert Brown wrote:
On 08/12/14 22:36, Robert Moskowitz wrote:
On 12/08/2014 06:30 AM, Robert Brown wrote:
On 08/12/14 22:11, Robert Moskowitz wrote:
On 12/08/2014 05:16 AM, Robert Brown wrote:
Thanks for the reply. On 08/12/14 14:43, Peter Robinson wrote: > On Fri, Dec 5, 2014 at 10:57 PM, Robert Brown > rebrown@exemail.com.au wrote: >> Anyone working on a FC21 image for the A10? My device does not >> give me >> access to a serial monitor so am hoping to change the dtb file >> for the A10 >> on a remix build and get this unit booting on 3.17. >> Thanks > You don't mention what your device is but a change in the .dtb > won't > fix the lack of display, there's a complete lack of driver, Yes my wording could have been better. Changing the .dtb was only about getting the device to boot as I realise hdmi is not yet ready. The device is a Rikomagic MK802II. Booting it headless with 3.17 is my aim but the soldering job for a serial console is a challenge beyond my soldering skills - see http://www.rikomagic.co.uk/forum/viewtopic.php?f=6&t=2488 so am hoping some-one with a compatible device such as Mele A1000 or CB1 could develop an image. A howto for the build and to get wireless configured for an ssh connection is an alternative.
You could just try booting without serial console if you provide --norootpass on building the SD card. SSHD permits logging in as root, just don't do this on the Internet, as you are sitting wide open!
I think I would need to manually configure and select my local network SSID and passphrase to get it on the network so I can ssh to it. A new world for me under systemd.
After first boot, you can see what interface name it used, the create an appropriate ifcfg- file. They still work.
Thinking about the firstboot script the only really needed things it does is set the timezone and root password. You can add your user after logging in as root.
I would suspect that if no serial console, it just comes up as ready as possible. All you need is your WiFi to be working; that is a pretty big assumption. You might have to get a supported ethernet dongle.
As above.
What has happened in booting without a serial console so far?
I am running blind so I either see a new connection open up when I do an nmap search from my PC or more likely there is no new connection for the reasons I mention. The real trick is to know if I have even had a successful boot.
What else are you going to do right now but try?
So on my attempts using Fedora-LXDE-armhfp-21-5-sda.raw.xz written to the sdcard using the manual instructions here https://fedoraproject.org/wiki/Architectures/ARM/F21/Installation including writing the appropriate u-boot to the media
and setting up wpa using tips from http://wiki.centos.org/HowTos/Laptops/WpaSupplicant with edits of /etc/wpa_supplicant/wpa_supplicant.conf and /etc/sysconfig/network-scripts/ifcfg-wlan0
Do you know what ethernet name is being used? Since your WiFi is a USB dongle, there are a lot of possiblities. All the more reason for journalctl.
If you know the MAC address you can create:
/etc/udev/rules.d/70-persistent-net.rules
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="02:c3:04:01:77:c3", ATTR{type}=="1", KERNEL=="eth*", NAME="wlan0"
This will 'fix' the name you need for ifcfg-wlan0
I will have ago at this but atm I don't think I am getting far into the boot. Certainly does not seem to be logging in. Not sure if networking can be enabled prior to login to allow ssh connection.
I don't believe the boot is getting very far as messages in /var/log is empty.
No /var/log/messages anymore. It is all journalctl. Look in that directory.
From my reading on journalctl I have not seen how to view any logs it may have created. /var/log contains a folder named journal but this is also empty so maybe same conclusion.
Maybe because I am not yet logged in. Tried setting autologin in lxdm.conf.
Would not know about lxdm.conf
Yes I have considered using Minimal or xfce instead.
Found I had an error on writing u-boot so corrected that and after next boot attempt found that a __/var/log/journal/a1a25eeb66844538a8c8a85672fcaf38/system.journal file of 8MB had been written. Looks like I have had a boot. Bit clumsy trying to read this file but in among the gobblydegook it was looking good and then (apologies for the long text):
MESSAGE=Starting System Logging Service... MESSAGE=can't open any entropy source MESSAGE=Maybe RNG device modules are not loaded MESSAGE=Failed to find user 'avahi' MESSAGE=Starting OpenSSH Server Key Generation... MESSAGE=Starting Login Service... MESSAGE=Generated key 1 MESSAGE=Fatal error : getpwnam(chrony) failed MESSAGE=Can't find user 'abrt': No such file or directory MESSAGE=Could not get password database information for UID of current process: User "???" unknown or no memory to allocate password entry MESSAGE=Unknown username "pulse" in message bus configuration file MESSAGE=Problem creating device name scan list MESSAGE=In the system's table of devices NO devices found to scan MESSAGE=Monitoring 0 ATA and 0 SCSI devices MESSAGE=Unknown username "root" in message bus configuration file MESSAGE=Unknown username "colord" in message bus configuration file MESSAGE=Unknown group "lp" in message bus configuration file MESSAGE=Unknown username "systemd-resolve" in message bus configuration file SYSLOG_IDENTIFIER=sshd-keygen MESSAGE=Generating SSH2 RSA host key: [FAILED] MESSAGE=Unknown username "polkitd" in message bus configuration file MESSAGE=Unknown username "avahi" in message bus configuration file MESSAGE=Unknown username "rtkit" in message bus configuration file MESSAGE=Failed to start message bus: Could not get UID and GID for username "dbus" MESSAGE=Failed to register match for Disconnected message: Connection timed out MESSAGE=Failed to add match for NameOwnerChanged: Connection timed out MESSAGE=Started System Logging Service. MESSAGE=Started Console System Startup Logging. MESSAGE=firewalld.service: main process exited, code=exited, status=1/FAILURE MESSAGE=abrtd.service: main process exited, code=exited, status=1/FAILURE MESSAGE=rngd.service: main process exited, code=exited, status=1/FAILURE MESSAGE=avahi-daemon.service: main process exited, code=exited, status=255/n/a MESSAGE=Failed to start Avahi mDNS/DNS-SD Stack. MESSAGE=Started Install ABRT coredump hook. MESSAGE=chronyd.service: control process exited, code=exited status=1 MESSAGE=sshd-keygen.service: main process exited, code=exited, status=1/FAILURE MESSAGE=Failed to start OpenSSH Server Key Generation. MESSAGE=systemd-logind.service: main process exited, code=exited, status=1/FAILURE MESSAGE=systemd-logind.service failed. MESSAGE=dbus.service: main process exited, code=exited, status=1/FAILURE MESSAGE=systemd-logind.service has no holdoff time, scheduling restart. CMDLINE=/bin/xinit /bin/firstboot-windowmanager /bin/initial-setup -- /bin/Xorg :9 -ac -nolisten tcp SYSTEMD_CGROUP=/system.slice/initial-setup-graphical.ser MESSAGE=Kernel command line: ro root=UUID=d072ca14-7c80-40e2-b291-a4eaa4837b0d console=ttyS0,115200 MESSAGE=rtkit-daemon.service start operation timed out. Terminating.
A few service went into failed state from this but maybe all due to not logging in? Anyone have any clues for what I might be able to edit in the fs on the card before a next boot attempt?
Thanks for your patience.
Rob
No wireless connection being made as evidenced by nmap.
On 14/12/14 15:54, Robert Brown wrote:
For the benefit of others this is about booting this device without having serial console or a monitor to view first boot prompts. On 14/12/14 11:27, Robert Moskowitz wrote:
On 12/13/2014 01:52 AM, Robert Brown wrote:
On 08/12/14 22:36, Robert Moskowitz wrote:
On 12/08/2014 06:30 AM, Robert Brown wrote:
On 08/12/14 22:11, Robert Moskowitz wrote:
On 12/08/2014 05:16 AM, Robert Brown wrote: > Thanks for the reply. > On 08/12/14 14:43, Peter Robinson wrote: >> On Fri, Dec 5, 2014 at 10:57 PM, Robert Brown >> rebrown@exemail.com.au wrote: >>> Anyone working on a FC21 image for the A10? My device does not >>> give me >>> access to a serial monitor so am hoping to change the dtb file >>> for the A10 >>> on a remix build and get this unit booting on 3.17. >>> Thanks >> You don't mention what your device is but a change in the .dtb >> won't >> fix the lack of display, there's a complete lack of driver, > Yes my wording could have been better. > Changing the .dtb was only about getting the device to boot as I > realise hdmi is not yet ready. > The device is a Rikomagic MK802II. Booting it headless with 3.17 > is my aim but the soldering job for a serial console is a > challenge beyond my soldering skills - see > http://www.rikomagic.co.uk/forum/viewtopic.php?f=6&t=2488 > so am hoping some-one with a compatible device such as Mele > A1000 or CB1 could develop an image. A howto for the build and > to get wireless configured for an ssh connection is an alternative.
You could just try booting without serial console if you provide --norootpass on building the SD card. SSHD permits logging in as root, just don't do this on the Internet, as you are sitting wide open!
I think I would need to manually configure and select my local network SSID and passphrase to get it on the network so I can ssh to it. A new world for me under systemd.
After first boot, you can see what interface name it used, the create an appropriate ifcfg- file. They still work.
Thinking about the firstboot script the only really needed things it does is set the timezone and root password. You can add your user after logging in as root.
I would suspect that if no serial console, it just comes up as ready as possible. All you need is your WiFi to be working; that is a pretty big assumption. You might have to get a supported ethernet dongle.
As above.
What has happened in booting without a serial console so far?
I am running blind so I either see a new connection open up when I do an nmap search from my PC or more likely there is no new connection for the reasons I mention. The real trick is to know if I have even had a successful boot.
What else are you going to do right now but try?
So on my attempts using Fedora-LXDE-armhfp-21-5-sda.raw.xz written to the sdcard using the manual instructions here https://fedoraproject.org/wiki/Architectures/ARM/F21/Installation including writing the appropriate u-boot to the media
and setting up wpa using tips from http://wiki.centos.org/HowTos/Laptops/WpaSupplicant with edits of /etc/wpa_supplicant/wpa_supplicant.conf and /etc/sysconfig/network-scripts/ifcfg-wlan0
Do you know what ethernet name is being used? Since your WiFi is a USB dongle, there are a lot of possiblities. All the more reason for journalctl.
If you know the MAC address you can create:
/etc/udev/rules.d/70-persistent-net.rules
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="02:c3:04:01:77:c3", ATTR{type}=="1", KERNEL=="eth*", NAME="wlan0"
This will 'fix' the name you need for ifcfg-wlan0
I will have ago at this but atm I don't think I am getting far into the boot. Certainly does not seem to be logging in. Not sure if networking can be enabled prior to login to allow ssh connection.
I don't believe the boot is getting very far as messages in /var/log is empty.
No /var/log/messages anymore. It is all journalctl. Look in that directory.
From my reading on journalctl I have not seen how to view any logs it may have created. /var/log contains a folder named journal but this is also empty so maybe same conclusion.
Maybe because I am not yet logged in. Tried setting autologin in lxdm.conf.
Would not know about lxdm.conf
Yes I have considered using Minimal or xfce instead.
Found several log files with date 01/01/1970 (attached).
/var/log/chrony was empty. Messages log reports:
EXYNOS: PMU not supported and edma-dma-engine edma-dma-engine.0: Can't allocate PaRAM dummy slot edma-dma-engine: probe of edma-dma-engine.0 failed with error -22
fairly early on. And
ahci-sunxi 1c18000.sata: PHY power up failed. ahci-sunxi: probe of 1c18000.sata failed with error -5
Generated key 1 Fatal error : getpwnam(chrony) failed getpwnam(chrony) failed
A search found all of these were empty:
/media/rbrown/__/etc/systemd/user /media/rbrown/__/etc/xdg/systemd/user /media/rbrown/__/var/kerberos/krb5/user /media/rbrown/__/usr/share/perl5/User /media/rbrown/__/usr/lib/systemd/user /media/rbrown/__/run/user
First things to check for?
On 15/12/14 08:57, Robert Brown wrote:
Found I had an error on writing u-boot so corrected that and after next boot attempt found that a __/var/log/journal/a1a25eeb66844538a8c8a85672fcaf38/system.journal file of 8MB had been written. Looks like I have had a boot. Bit clumsy trying to read this file but in among the gobblydegook it was looking good and then (apologies for the long text):
MESSAGE=Starting System Logging Service... MESSAGE=can't open any entropy source MESSAGE=Maybe RNG device modules are not loaded MESSAGE=Failed to find user 'avahi' MESSAGE=Starting OpenSSH Server Key Generation... MESSAGE=Starting Login Service... MESSAGE=Generated key 1 MESSAGE=Fatal error : getpwnam(chrony) failed MESSAGE=Can't find user 'abrt': No such file or directory MESSAGE=Could not get password database information for UID of current process: User "???" unknown or no memory to allocate password entry MESSAGE=Unknown username "pulse" in message bus configuration file MESSAGE=Problem creating device name scan list MESSAGE=In the system's table of devices NO devices found to scan MESSAGE=Monitoring 0 ATA and 0 SCSI devices MESSAGE=Unknown username "root" in message bus configuration file MESSAGE=Unknown username "colord" in message bus configuration file MESSAGE=Unknown group "lp" in message bus configuration file MESSAGE=Unknown username "systemd-resolve" in message bus configuration file SYSLOG_IDENTIFIER=sshd-keygen MESSAGE=Generating SSH2 RSA host key: [FAILED] MESSAGE=Unknown username "polkitd" in message bus configuration file MESSAGE=Unknown username "avahi" in message bus configuration file MESSAGE=Unknown username "rtkit" in message bus configuration file MESSAGE=Failed to start message bus: Could not get UID and GID for username "dbus" MESSAGE=Failed to register match for Disconnected message: Connection timed out MESSAGE=Failed to add match for NameOwnerChanged: Connection timed out MESSAGE=Started System Logging Service. MESSAGE=Started Console System Startup Logging. MESSAGE=firewalld.service: main process exited, code=exited, status=1/FAILURE MESSAGE=abrtd.service: main process exited, code=exited, status=1/FAILURE MESSAGE=rngd.service: main process exited, code=exited, status=1/FAILURE MESSAGE=avahi-daemon.service: main process exited, code=exited, status=255/n/a MESSAGE=Failed to start Avahi mDNS/DNS-SD Stack. MESSAGE=Started Install ABRT coredump hook. MESSAGE=chronyd.service: control process exited, code=exited status=1 MESSAGE=sshd-keygen.service: main process exited, code=exited, status=1/FAILURE MESSAGE=Failed to start OpenSSH Server Key Generation. MESSAGE=systemd-logind.service: main process exited, code=exited, status=1/FAILURE MESSAGE=systemd-logind.service failed. MESSAGE=dbus.service: main process exited, code=exited, status=1/FAILURE MESSAGE=systemd-logind.service has no holdoff time, scheduling restart. CMDLINE=/bin/xinit /bin/firstboot-windowmanager /bin/initial-setup -- /bin/Xorg :9 -ac -nolisten tcp SYSTEMD_CGROUP=/system.slice/initial-setup-graphical.ser MESSAGE=Kernel command line: ro root=UUID=d072ca14-7c80-40e2-b291-a4eaa4837b0d console=ttyS0,115200 MESSAGE=rtkit-daemon.service start operation timed out. Terminating.
A few service went into failed state from this but maybe all due to not logging in? Anyone have any clues for what I might be able to edit in the fs on the card before a next boot attempt?
Thanks for your patience.
Rob
No wireless connection being made as evidenced by nmap.
On 14/12/14 15:54, Robert Brown wrote:
For the benefit of others this is about booting this device without having serial console or a monitor to view first boot prompts. On 14/12/14 11:27, Robert Moskowitz wrote:
On 12/13/2014 01:52 AM, Robert Brown wrote:
On 08/12/14 22:36, Robert Moskowitz wrote:
On 12/08/2014 06:30 AM, Robert Brown wrote:
On 08/12/14 22:11, Robert Moskowitz wrote: > On 12/08/2014 05:16 AM, Robert Brown wrote: >> Thanks for the reply. >> On 08/12/14 14:43, Peter Robinson wrote: >>> On Fri, Dec 5, 2014 at 10:57 PM, Robert Brown >>> rebrown@exemail.com.au wrote: >>>> Anyone working on a FC21 image for the A10? My device does >>>> not give me >>>> access to a serial monitor so am hoping to change the dtb >>>> file for the A10 >>>> on a remix build and get this unit booting on 3.17. >>>> Thanks >>> You don't mention what your device is but a change in the .dtb >>> won't >>> fix the lack of display, there's a complete lack of driver, >> Yes my wording could have been better. >> Changing the .dtb was only about getting the device to boot as >> I realise hdmi is not yet ready. >> The device is a Rikomagic MK802II. Booting it headless with >> 3.17 is my aim but the soldering job for a serial console is a >> challenge beyond my soldering skills - see >> http://www.rikomagic.co.uk/forum/viewtopic.php?f=6&t=2488 >> so am hoping some-one with a compatible device such as Mele >> A1000 or CB1 could develop an image. A howto for the build and >> to get wireless configured for an ssh connection is an >> alternative. > > You could just try booting without serial console if you provide > --norootpass on building the SD card. SSHD permits logging in as > root, just don't do this on the Internet, as you are sitting > wide open! I think I would need to manually configure and select my local network SSID and passphrase to get it on the network so I can ssh to it. A new world for me under systemd.
After first boot, you can see what interface name it used, the create an appropriate ifcfg- file. They still work.
> > Thinking about the firstboot script the only really needed > things it does is set the timezone and root password. You can > add your user after logging in as root. > > I would suspect that if no serial console, it just comes up as > ready as possible. All you need is your WiFi to be working; > that is a pretty big assumption. You might have to get a > supported ethernet dongle. As above. > > What has happened in booting without a serial console so far? I am running blind so I either see a new connection open up when I do an nmap search from my PC or more likely there is no new connection for the reasons I mention. The real trick is to know if I have even had a successful boot.
What else are you going to do right now but try?
So on my attempts using Fedora-LXDE-armhfp-21-5-sda.raw.xz written to the sdcard using the manual instructions here https://fedoraproject.org/wiki/Architectures/ARM/F21/Installation including writing the appropriate u-boot to the media
and setting up wpa using tips from http://wiki.centos.org/HowTos/Laptops/WpaSupplicant with edits of /etc/wpa_supplicant/wpa_supplicant.conf and /etc/sysconfig/network-scripts/ifcfg-wlan0
Do you know what ethernet name is being used? Since your WiFi is a USB dongle, there are a lot of possiblities. All the more reason for journalctl.
If you know the MAC address you can create:
/etc/udev/rules.d/70-persistent-net.rules
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="02:c3:04:01:77:c3", ATTR{type}=="1", KERNEL=="eth*", NAME="wlan0"
This will 'fix' the name you need for ifcfg-wlan0
I will have ago at this but atm I don't think I am getting far into the boot. Certainly does not seem to be logging in. Not sure if networking can be enabled prior to login to allow ssh connection.
I don't believe the boot is getting very far as messages in /var/log is empty.
No /var/log/messages anymore. It is all journalctl. Look in that directory.
From my reading on journalctl I have not seen how to view any logs it may have created. /var/log contains a folder named journal but this is also empty so maybe same conclusion.
Maybe because I am not yet logged in. Tried setting autologin in lxdm.conf.
Would not know about lxdm.conf
Yes I have considered using Minimal or xfce instead.
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
On Mon, Dec 15, 2014 at 4:52 AM, Robert Brown rebrown@exemail.com.au wrote:
Found several log files with date 01/01/1970 (attached).
/var/log/chrony was empty.
Would be until network comes up and chrony can start
Messages log reports: EXYNOS: PMU not supported and edma-dma-engine edma-dma-engine.0: Can't allocate PaRAM dummy slot edma-dma-engine: probe of edma-dma-engine.0 failed with error -22
All spurious, for HW other than AllWinner
fairly early on. And
ahci-sunxi 1c18000.sata: PHY power up failed. ahci-sunxi: probe of 1c18000.sata failed with error -5
Do you have a SATA device attached?
Generated key 1 Fatal error : getpwnam(chrony) failed getpwnam(chrony) failed
A search found all of these were empty:
/media/rbrown/__/etc/systemd/user /media/rbrown/__/etc/xdg/systemd/user /media/rbrown/__/var/kerberos/krb5/user /media/rbrown/__/usr/share/perl5/User /media/rbrown/__/usr/lib/systemd/user /media/rbrown/__/run/user
First things to check for?
Maybe I missed in it earlier posts but what A10 device are you using?
On 15/12/14 08:57, Robert Brown wrote:
Found I had an error on writing u-boot so corrected that and after next boot attempt found that a __/var/log/journal/a1a25eeb66844538a8c8a85672fcaf38/system.journal file of 8MB had been written. Looks like I have had a boot. Bit clumsy trying to read this file but in among the gobblydegook it was looking good and then (apologies for the long text):
MESSAGE=Starting System Logging Service... MESSAGE=can't open any entropy source MESSAGE=Maybe RNG device modules are not loaded MESSAGE=Failed to find user 'avahi' MESSAGE=Starting OpenSSH Server Key Generation... MESSAGE=Starting Login Service... MESSAGE=Generated key 1 MESSAGE=Fatal error : getpwnam(chrony) failed MESSAGE=Can't find user 'abrt': No such file or directory MESSAGE=Could not get password database information for UID of current process: User "???" unknown or no memory to allocate password entry MESSAGE=Unknown username "pulse" in message bus configuration file MESSAGE=Problem creating device name scan list MESSAGE=In the system's table of devices NO devices found to scan MESSAGE=Monitoring 0 ATA and 0 SCSI devices MESSAGE=Unknown username "root" in message bus configuration file MESSAGE=Unknown username "colord" in message bus configuration file MESSAGE=Unknown group "lp" in message bus configuration file MESSAGE=Unknown username "systemd-resolve" in message bus configuration file SYSLOG_IDENTIFIER=sshd-keygen MESSAGE=Generating SSH2 RSA host key: [FAILED] MESSAGE=Unknown username "polkitd" in message bus configuration file MESSAGE=Unknown username "avahi" in message bus configuration file MESSAGE=Unknown username "rtkit" in message bus configuration file MESSAGE=Failed to start message bus: Could not get UID and GID for username "dbus" MESSAGE=Failed to register match for Disconnected message: Connection timed out MESSAGE=Failed to add match for NameOwnerChanged: Connection timed out MESSAGE=Started System Logging Service. MESSAGE=Started Console System Startup Logging. MESSAGE=firewalld.service: main process exited, code=exited, status=1/FAILURE MESSAGE=abrtd.service: main process exited, code=exited, status=1/FAILURE MESSAGE=rngd.service: main process exited, code=exited, status=1/FAILURE MESSAGE=avahi-daemon.service: main process exited, code=exited, status=255/n/a MESSAGE=Failed to start Avahi mDNS/DNS-SD Stack. MESSAGE=Started Install ABRT coredump hook. MESSAGE=chronyd.service: control process exited, code=exited status=1 MESSAGE=sshd-keygen.service: main process exited, code=exited, status=1/FAILURE MESSAGE=Failed to start OpenSSH Server Key Generation. MESSAGE=systemd-logind.service: main process exited, code=exited, status=1/FAILURE MESSAGE=systemd-logind.service failed. MESSAGE=dbus.service: main process exited, code=exited, status=1/FAILURE MESSAGE=systemd-logind.service has no holdoff time, scheduling restart. CMDLINE=/bin/xinit /bin/firstboot-windowmanager /bin/initial-setup -- /bin/Xorg :9 -ac -nolisten tcp SYSTEMD_CGROUP=/system.slice/initial-setup-graphical.ser MESSAGE=Kernel command line: ro root=UUID=d072ca14-7c80-40e2-b291-a4eaa4837b0d console=ttyS0,115200 MESSAGE=rtkit-daemon.service start operation timed out. Terminating.
A few service went into failed state from this but maybe all due to not logging in? Anyone have any clues for what I might be able to edit in the fs on the card before a next boot attempt?
Thanks for your patience.
Rob
No wireless connection being made as evidenced by nmap.
On 14/12/14 15:54, Robert Brown wrote:
For the benefit of others this is about booting this device without having serial console or a monitor to view first boot prompts. On 14/12/14 11:27, Robert Moskowitz wrote:
On 12/13/2014 01:52 AM, Robert Brown wrote:
On 08/12/14 22:36, Robert Moskowitz wrote:
On 12/08/2014 06:30 AM, Robert Brown wrote: > > On 08/12/14 22:11, Robert Moskowitz wrote: >> >> On 12/08/2014 05:16 AM, Robert Brown wrote: >>> >>> Thanks for the reply. >>> On 08/12/14 14:43, Peter Robinson wrote: >>>> >>>> On Fri, Dec 5, 2014 at 10:57 PM, Robert Brown >>>> rebrown@exemail.com.au wrote: >>>>> >>>>> Anyone working on a FC21 image for the A10? My device does not >>>>> give me >>>>> access to a serial monitor so am hoping to change the dtb file >>>>> for the A10 >>>>> on a remix build and get this unit booting on 3.17. >>>>> Thanks >>>> >>>> You don't mention what your device is but a change in the .dtb >>>> won't >>>> fix the lack of display, there's a complete lack of driver, >>> >>> Yes my wording could have been better. >>> Changing the .dtb was only about getting the device to boot as I >>> realise hdmi is not yet ready. >>> The device is a Rikomagic MK802II. Booting it headless with 3.17 is >>> my aim but the soldering job for a serial console is a challenge beyond my >>> soldering skills - see >>> http://www.rikomagic.co.uk/forum/viewtopic.php?f=6&t=2488 >>> so am hoping some-one with a compatible device such as Mele A1000 >>> or CB1 could develop an image. A howto for the build and to get wireless >>> configured for an ssh connection is an alternative. >> >> >> You could just try booting without serial console if you provide >> --norootpass on building the SD card. SSHD permits logging in as root, just >> don't do this on the Internet, as you are sitting wide open! > > I think I would need to manually configure and select my local > network SSID and passphrase to get it on the network so I can ssh to it. A > new world for me under systemd.
After first boot, you can see what interface name it used, the create an appropriate ifcfg- file. They still work.
>> >> Thinking about the firstboot script the only really needed things it >> does is set the timezone and root password. You can add your user after >> logging in as root. >> >> I would suspect that if no serial console, it just comes up as ready >> as possible. All you need is your WiFi to be working; that is a pretty big >> assumption. You might have to get a supported ethernet dongle. > > As above. >> >> >> What has happened in booting without a serial console so far? > > I am running blind so I either see a new connection open up when I do > an nmap search from my PC or more likely there is no new connection for the > reasons I mention. The real trick is to know if I have even had a successful > boot.
What else are you going to do right now but try?
So on my attempts using Fedora-LXDE-armhfp-21-5-sda.raw.xz written to the sdcard using the manual instructions here https://fedoraproject.org/wiki/Architectures/ARM/F21/Installation including writing the appropriate u-boot to the media
and setting up wpa using tips from http://wiki.centos.org/HowTos/Laptops/WpaSupplicant with edits of /etc/wpa_supplicant/wpa_supplicant.conf and /etc/sysconfig/network-scripts/ifcfg-wlan0
Do you know what ethernet name is being used? Since your WiFi is a USB dongle, there are a lot of possiblities. All the more reason for journalctl.
If you know the MAC address you can create:
/etc/udev/rules.d/70-persistent-net.rules
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="02:c3:04:01:77:c3", ATTR{type}=="1", KERNEL=="eth*", NAME="wlan0"
This will 'fix' the name you need for ifcfg-wlan0
I will have ago at this but atm I don't think I am getting far into the boot. Certainly does not seem to be logging in. Not sure if networking can be enabled prior to login to allow ssh connection.
I don't believe the boot is getting very far as messages in /var/log is empty.
No /var/log/messages anymore. It is all journalctl. Look in that directory.
From my reading on journalctl I have not seen how to view any logs it may have created. /var/log contains a folder named journal but this is also empty so maybe same conclusion.
Maybe because I am not yet logged in. Tried setting autologin in lxdm.conf.
Would not know about lxdm.conf
Yes I have considered using Minimal or xfce instead.
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
Thanks for the reply Peter.
On 15/12/14 15:58, Peter Robinson wrote:
On Mon, Dec 15, 2014 at 4:52 AM, Robert Brown rebrown@exemail.com.au wrote:
Found several log files with date 01/01/1970 (attached).
/var/log/chrony was empty.
Would be until network comes up and chrony can start
Messages log reports: EXYNOS: PMU not supported and edma-dma-engine edma-dma-engine.0: Can't allocate PaRAM dummy slot edma-dma-engine: probe of edma-dma-engine.0 failed with error -22
All spurious, for HW other than AllWinner
fairly early on. And
ahci-sunxi 1c18000.sata: PHY power up failed. ahci-sunxi: probe of 1c18000.sata failed with error -5
Do you have a SATA device attached?
No sata device attached.
Generated key 1 Fatal error : getpwnam(chrony) failed getpwnam(chrony) failed
A search found all of these were empty:
/media/rbrown/__/etc/systemd/user /media/rbrown/__/etc/xdg/systemd/user /media/rbrown/__/var/kerberos/krb5/user /media/rbrown/__/usr/share/perl5/User /media/rbrown/__/usr/lib/systemd/user /media/rbrown/__/run/user
First things to check for?
Maybe I missed in it earlier posts but what A10 device are you using?
This is a Rikomagic MK802II hdmi device. Trying to boot headless with no serial console!
On 15/12/14 08:57, Robert Brown wrote:
Found I had an error on writing u-boot so corrected that and after next boot attempt found that a __/var/log/journal/a1a25eeb66844538a8c8a85672fcaf38/system.journal file of 8MB had been written. Looks like I have had a boot. Bit clumsy trying to read this file but in among the gobblydegook it was looking good and then (apologies for the long text):
MESSAGE=Starting System Logging Service... MESSAGE=can't open any entropy source MESSAGE=Maybe RNG device modules are not loaded MESSAGE=Failed to find user 'avahi' MESSAGE=Starting OpenSSH Server Key Generation... MESSAGE=Starting Login Service... MESSAGE=Generated key 1 MESSAGE=Fatal error : getpwnam(chrony) failed MESSAGE=Can't find user 'abrt': No such file or directory MESSAGE=Could not get password database information for UID of current process: User "???" unknown or no memory to allocate password entry MESSAGE=Unknown username "pulse" in message bus configuration file MESSAGE=Problem creating device name scan list MESSAGE=In the system's table of devices NO devices found to scan MESSAGE=Monitoring 0 ATA and 0 SCSI devices MESSAGE=Unknown username "root" in message bus configuration file MESSAGE=Unknown username "colord" in message bus configuration file MESSAGE=Unknown group "lp" in message bus configuration file MESSAGE=Unknown username "systemd-resolve" in message bus configuration file SYSLOG_IDENTIFIER=sshd-keygen MESSAGE=Generating SSH2 RSA host key: [FAILED] MESSAGE=Unknown username "polkitd" in message bus configuration file MESSAGE=Unknown username "avahi" in message bus configuration file MESSAGE=Unknown username "rtkit" in message bus configuration file MESSAGE=Failed to start message bus: Could not get UID and GID for username "dbus" MESSAGE=Failed to register match for Disconnected message: Connection timed out MESSAGE=Failed to add match for NameOwnerChanged: Connection timed out MESSAGE=Started System Logging Service. MESSAGE=Started Console System Startup Logging. MESSAGE=firewalld.service: main process exited, code=exited, status=1/FAILURE MESSAGE=abrtd.service: main process exited, code=exited, status=1/FAILURE MESSAGE=rngd.service: main process exited, code=exited, status=1/FAILURE MESSAGE=avahi-daemon.service: main process exited, code=exited, status=255/n/a MESSAGE=Failed to start Avahi mDNS/DNS-SD Stack. MESSAGE=Started Install ABRT coredump hook. MESSAGE=chronyd.service: control process exited, code=exited status=1 MESSAGE=sshd-keygen.service: main process exited, code=exited, status=1/FAILURE MESSAGE=Failed to start OpenSSH Server Key Generation. MESSAGE=systemd-logind.service: main process exited, code=exited, status=1/FAILURE MESSAGE=systemd-logind.service failed. MESSAGE=dbus.service: main process exited, code=exited, status=1/FAILURE MESSAGE=systemd-logind.service has no holdoff time, scheduling restart. CMDLINE=/bin/xinit /bin/firstboot-windowmanager /bin/initial-setup -- /bin/Xorg :9 -ac -nolisten tcp SYSTEMD_CGROUP=/system.slice/initial-setup-graphical.ser MESSAGE=Kernel command line: ro root=UUID=d072ca14-7c80-40e2-b291-a4eaa4837b0d console=ttyS0,115200 MESSAGE=rtkit-daemon.service start operation timed out. Terminating.
A few service went into failed state from this but maybe all due to not logging in? Anyone have any clues for what I might be able to edit in the fs on the card before a next boot attempt?
Thanks for your patience.
Rob
No wireless connection being made as evidenced by nmap.
On 14/12/14 15:54, Robert Brown wrote:
For the benefit of others this is about booting this device without having serial console or a monitor to view first boot prompts. On 14/12/14 11:27, Robert Moskowitz wrote:
On 12/13/2014 01:52 AM, Robert Brown wrote:
On 08/12/14 22:36, Robert Moskowitz wrote: > On 12/08/2014 06:30 AM, Robert Brown wrote: >> On 08/12/14 22:11, Robert Moskowitz wrote: >>> On 12/08/2014 05:16 AM, Robert Brown wrote: >>>> Thanks for the reply. >>>> On 08/12/14 14:43, Peter Robinson wrote: >>>>> On Fri, Dec 5, 2014 at 10:57 PM, Robert Brown >>>>> rebrown@exemail.com.au wrote: >>>>>> Anyone working on a FC21 image for the A10? My device does not >>>>>> give me >>>>>> access to a serial monitor so am hoping to change the dtb file >>>>>> for the A10 >>>>>> on a remix build and get this unit booting on 3.17. >>>>>> Thanks >>>>> You don't mention what your device is but a change in the .dtb >>>>> won't >>>>> fix the lack of display, there's a complete lack of driver, >>>> Yes my wording could have been better. >>>> Changing the .dtb was only about getting the device to boot as I >>>> realise hdmi is not yet ready. >>>> The device is a Rikomagic MK802II. Booting it headless with 3.17 is >>>> my aim but the soldering job for a serial console is a challenge beyond my >>>> soldering skills - see >>>> http://www.rikomagic.co.uk/forum/viewtopic.php?f=6&t=2488 >>>> so am hoping some-one with a compatible device such as Mele A1000 >>>> or CB1 could develop an image. A howto for the build and to get wireless >>>> configured for an ssh connection is an alternative. >>> >>> You could just try booting without serial console if you provide >>> --norootpass on building the SD card. SSHD permits logging in as root, just >>> don't do this on the Internet, as you are sitting wide open! >> I think I would need to manually configure and select my local >> network SSID and passphrase to get it on the network so I can ssh to it. A >> new world for me under systemd. > > After first boot, you can see what interface name it used, the create > an appropriate ifcfg- file. They still work. > >>> Thinking about the firstboot script the only really needed things it >>> does is set the timezone and root password. You can add your user after >>> logging in as root. >>> >>> I would suspect that if no serial console, it just comes up as ready >>> as possible. All you need is your WiFi to be working; that is a pretty big >>> assumption. You might have to get a supported ethernet dongle. >> As above. >>> >>> What has happened in booting without a serial console so far? >> I am running blind so I either see a new connection open up when I do >> an nmap search from my PC or more likely there is no new connection for the >> reasons I mention. The real trick is to know if I have even had a successful >> boot. > > What else are you going to do right now but try? So on my attempts using Fedora-LXDE-armhfp-21-5-sda.raw.xz written to the sdcard using the manual instructions here https://fedoraproject.org/wiki/Architectures/ARM/F21/Installation including writing the appropriate u-boot to the media
and setting up wpa using tips from http://wiki.centos.org/HowTos/Laptops/WpaSupplicant with edits of /etc/wpa_supplicant/wpa_supplicant.conf and /etc/sysconfig/network-scripts/ifcfg-wlan0
Do you know what ethernet name is being used? Since your WiFi is a USB dongle, there are a lot of possiblities. All the more reason for journalctl.
If you know the MAC address you can create:
/etc/udev/rules.d/70-persistent-net.rules
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="02:c3:04:01:77:c3", ATTR{type}=="1", KERNEL=="eth*", NAME="wlan0"
This will 'fix' the name you need for ifcfg-wlan0
I will have ago at this but atm I don't think I am getting far into the boot. Certainly does not seem to be logging in. Not sure if networking can be enabled prior to login to allow ssh connection.
I don't believe the boot is getting very far as messages in /var/log is empty.
No /var/log/messages anymore. It is all journalctl. Look in that directory.
From my reading on journalctl I have not seen how to view any logs it may have created. /var/log contains a folder named journal but this is also empty so maybe same conclusion.
Maybe because I am not yet logged in. Tried setting autologin in lxdm.conf.
Would not know about lxdm.conf
Yes I have considered using Minimal or xfce instead.
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
On Mon, Dec 15, 2014 at 5:24 AM, Robert Brown rebrown@exemail.com.au wrote:
Thanks for the reply Peter.
On 15/12/14 15:58, Peter Robinson wrote:
On Mon, Dec 15, 2014 at 4:52 AM, Robert Brown rebrown@exemail.com.au wrote:
Found several log files with date 01/01/1970 (attached).
/var/log/chrony was empty.
Would be until network comes up and chrony can start
Messages log reports: EXYNOS: PMU not supported and edma-dma-engine edma-dma-engine.0: Can't allocate PaRAM dummy slot edma-dma-engine: probe of edma-dma-engine.0 failed with error -22
All spurious, for HW other than AllWinner
fairly early on. And
ahci-sunxi 1c18000.sata: PHY power up failed. ahci-sunxi: probe of 1c18000.sata failed with error -5
Do you have a SATA device attached?
No sata device attached.
Generated key 1 Fatal error : getpwnam(chrony) failed getpwnam(chrony) failed
A search found all of these were empty:
/media/rbrown/__/etc/systemd/user /media/rbrown/__/etc/xdg/systemd/user /media/rbrown/__/var/kerberos/krb5/user /media/rbrown/__/usr/share/perl5/User /media/rbrown/__/usr/lib/systemd/user /media/rbrown/__/run/user
First things to check for?
Maybe I missed in it earlier posts but what A10 device are you using?
This is a Rikomagic MK802II hdmi device. Trying to boot headless with no serial console!
What uboot are you using, are you specifying a .dtb file, if so what one?
Peter
On 15/12/14 16:32, Peter Robinson wrote:
On Mon, Dec 15, 2014 at 5:24 AM, Robert Brown rebrown@exemail.com.au wrote:
Thanks for the reply Peter.
On 15/12/14 15:58, Peter Robinson wrote:
On Mon, Dec 15, 2014 at 4:52 AM, Robert Brown rebrown@exemail.com.au wrote:
Found several log files with date 01/01/1970 (attached).
/var/log/chrony was empty.
Would be until network comes up and chrony can start
Messages log reports: EXYNOS: PMU not supported and edma-dma-engine edma-dma-engine.0: Can't allocate PaRAM dummy slot edma-dma-engine: probe of edma-dma-engine.0 failed with error -22
All spurious, for HW other than AllWinner
fairly early on. And
ahci-sunxi 1c18000.sata: PHY power up failed. ahci-sunxi: probe of 1c18000.sata failed with error -5
Do you have a SATA device attached?
No sata device attached.
Generated key 1 Fatal error : getpwnam(chrony) failed getpwnam(chrony) failed
A search found all of these were empty:
/media/rbrown/__/etc/systemd/user /media/rbrown/__/etc/xdg/systemd/user /media/rbrown/__/var/kerberos/krb5/user /media/rbrown/__/usr/share/perl5/User /media/rbrown/__/usr/lib/systemd/user /media/rbrown/__/run/user
First things to check for?
Maybe I missed in it earlier posts but what A10 device are you using?
This is a Rikomagic MK802II hdmi device. Trying to boot headless with no serial console!
What uboot are you using, are you specifying a .dtb file, if so what one?
Peter
I have applied /usr/share/uboot/Mele_A1000/u-boot-sunxi-with-spl.bin using dd. This Mele device has shown a very high compatibility previously with the MK802II. Other u-boot options that I could try might be Cubieboard (1) and maybe A10-OLinuXino-Lime but less sure of this last one. Is my understanding correct that this step would have applied sun4i-a10-a1000.dtb or have I missed a step?
Rob
-
Daniel Veillard -
Hans de Goede -
Lubomir Rintel -
Michal Hlavinka -
Peter Robinson -
Robert Brown -
Robert Moskowitz -
Timothy Krantz