[fedora-arm] fedora 27 on inet 3f tablet with newer kernel from repo does not boot anymore

[Steven Vanden Branden]

hello all,

i have a inet 3f tablet (pov protab 255xxl) and managed to get fedora 27 running on the board with a inet1 dtb,

The kernel from the initial image boots and everything (except for the touchscreen) works.
this is version 4.13.3-300.fc27.amv7hl,
i also installed version 4.13.9-300.fc27.amv7hl,

and these also work fine,

Then i updated to the latest fedora 27 kernel 4.15.15-300.fc27.armv7hl and this kernel starts booting, but then the screen goes blank, and i cannot login via ssh either,
the same happened with a self compiled kernel 4.17.0-0.rc0.git0.300.fc27.armv7hl with lima drivers patched.

I have tried to find the serial port pins on the board, but could not locate them, also kernel versions 4.14 i have not tried yet because i cannot find them precompiled.

Are there any parameters i can change to try to make it boot, or get more output in the process? Or a link to documentation :)

greetings,
Steven
_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to arm-leav

[Peter Robinson]

Hi,

Post by Steven Vanden Branden
i have a inet 3f tablet (pov protab 255xxl) and managed to get fedora 27 running on the board with a inet1 dtb,

That means nothing to me, I'm guessing it's a cheap AllWinner based
device, do you have any more details? Are you using a Fedora u-boot or
your own? If Fedora what's it called? What Fedora image are you using?

Post by Steven Vanden Branden
The kernel from the initial image boots and everything (except for the touchscreen) works.

Touch screen is no real surprise if it's an AllWinner based tablet,
they change them constantly based on cost and availability.

Post by Steven Vanden Branden
this is version 4.13.3-300.fc27.amv7hl,
i also installed version 4.13.9-300.fc27.amv7hl,

If one 4.13 works it's not surprising others do, what about 4.14.x

Post by Steven Vanden Branden
and these also work fine,
Then i updated to the latest fedora 27 kernel 4.15.15-300.fc27.armv7hl and this kernel starts booting, but then the screen goes blank, and i cannot login via ssh either,

Can you some how grab the output up until it goes blank, I suspect
that last output might give us some idea.

Post by Steven Vanden Branden
the same happened with a self compiled kernel 4.17.0-0.rc0.git0.300.fc27.armv7hl with lima drivers patched.

What about a Fedora 4.16.2 (built yesterday) kernel? Unfortunately we
can't help with custom built kernels, it's almost impossible to remote
debug the Fedora ones, custom is the never step of impossible.

Post by Steven Vanden Branden
I have tried to find the serial port pins on the board, but could not locate them, also kernel versions 4.14 i have not tried yet because i cannot find them precompiled.

Kernels can always be found in koji to download:
https://koji.fedoraproject.org/koji/packageinfo?packageID=8
You'll find every thing to the latest 4.17 linus snapshot there.

Post by Steven Vanden Branden
Are there any parameters i can change to try to make it boot, or get more output in the process? Or a link to documentation :)

Sadly there's no MakeItWork kernel command line option, it's a matter
of getting debug and trying to work out what went wrong and why. We
don't explicitly support these devices due to the lack of ease of
supporting them as you're finding out, but we don't do anything to
actively stop them working, it's very much a best effort, I suspect
there's something upstream that has regressed, the question is working
out what, and the last of that early boot output will be the best spot
to start.

Peter
_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to arm-***@l

[William Cohen]

Post by Peter Robinson
Hi,

Post by Steven Vanden Branden
i have a inet 3f tablet (pov protab 255xxl) and managed to get fedora 27 running on the board with a inet1 dtb,

That means nothing to me, I'm guessing it's a cheap AllWinner based
device, do you have any more details? Are you using a Fedora u-boot or
your own? If Fedora what's it called? What Fedora image are you using?

Post by Steven Vanden Branden
The kernel from the initial image boots and everything (except for the touchscreen) works.

Touch screen is no real surprise if it's an AllWinner based tablet,
they change them constantly based on cost and availability.

Post by Steven Vanden Branden
this is version 4.13.3-300.fc27.amv7hl,
i also installed version 4.13.9-300.fc27.amv7hl,

If one 4.13 works it's not surprising others do, what about 4.14.x

Post by Steven Vanden Branden
and these also work fine,
Then i updated to the latest fedora 27 kernel 4.15.15-300.fc27.armv7hl and this kernel starts booting, but then the screen goes blank, and i cannot login via ssh either,

Can you some how grab the output up until it goes blank, I suspect
that last output might give us some idea.

Post by Steven Vanden Branden
the same happened with a self compiled kernel 4.17.0-0.rc0.git0.300.fc27.armv7hl with lima drivers patched.

What about a Fedora 4.16.2 (built yesterday) kernel? Unfortunately we
can't help with custom built kernels, it's almost impossible to remote
debug the Fedora ones, custom is the never step of impossible.

Post by Steven Vanden Branden
I have tried to find the serial port pins on the board, but could not locate them, also kernel versions 4.14 i have not tried yet because i cannot find them precompiled.

Hi,

It looks like sunxi.org has a web page for this device:

http://linux-sunxi.org/INet_3F

According to the wiki article the serial port pins are hidden under the touch screen cable.

-Will

Post by Peter Robinson
https://koji.fedoraproject.org/koji/packageinfo?packageID=8
You'll find every thing to the latest 4.17 linus snapshot there.

Post by Steven Vanden Branden
Are there any parameters i can change to try to make it boot, or get more output in the process? Or a link to documentation :)

Sadly there's no MakeItWork kernel command line option, it's a matter
of getting debug and trying to work out what went wrong and why. We
don't explicitly support these devices due to the lack of ease of
supporting them as you're finding out, but we don't do anything to
actively stop them working, it's very much a best effort, I suspect
there's something upstream that has regressed, the question is working
out what, and the last of that early boot output will be the best spot
to start.
Peter
_______________________________________________

_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to arm-leave

[Steven Vanden Branden]

Post by William Cohen
Hi,
http://linux-sunxi.org/INet_3F

I opened the device and it seems i was wrong about the version, it is actually a Inet 10F rev 3 , using a cortex A10 chip. I did found 3 port pins which i believe are also the serial pins, i will try out tomorrow when i have a soldering iron, to get a serial console up and running,

thanks for the information

Post by William Cohen
According to the wiki article the serial port pins are hidden under the touch screen cable.
-Will

_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to arm-***@lists.fedor

[Steven Vanden Branden]

Post by Peter Robinson
Hi,
That means nothing to me, I'm guessing it's a cheap AllWinner based
device, do you have any more details? Are you using a Fedora u-boot or
your own? If Fedora what's it called? What Fedora image are you using?

I is indeed a cheap cortex A10 Alwinner tablet, with 1Gb ram.
I started from image https://download.fedoraproject.org/pub/fedora/linux/releases/27/Spins/armhfp/images/Fedora-Xfce-armhfp-27-1.6-sda.raw.xz
and used the bootloader for A10-OLinuXino-Lime in the arm-imamge-installer, later on i replaced it with a bootloader compiled for the sun4i-a10-inet1 target, compiled from the uboot repo.
I update by sudo dnf update and everything still works except for the newer kernel.

Also its a inet 10F rev 03 model chipset.

Post by Peter Robinson
Touch screen is no real surprise if it's an AllWinner based tablet,
they change them constantly based on cost and availability.

the touchscreen is DPT 300-N3765A-C00, from the dpt group, i will see later if i can get the driver information from the android fex file, but the fex files have multiple touchscreens defined, so i will have to verify which one later.

Post by Peter Robinson
If one 4.13 works it's not surprising others do, what about 4.14.x

i will try the 4.14 kernel from koji as well.

Post by Peter Robinson
Can you some how grab the output up until it goes blank, I suspect
that last output might give us some idea.

the latest output is:

starting kernel..
then a black screen with the pinguin only (from uboot?), then that also disappears, it seems the back-light is still on though, until i reset the tablet,
could it be that the load address of the kernel is wrong (kernel size got bigger?).

Post by Peter Robinson
What about a Fedora 4.16.2 (built yesterday) kernel? Unfortunately we
can't help with custom built kernels, it's almost impossible to remote
debug the Fedora ones, custom is the never step of impossible.

I understand, i will try with the that koji kernel as well.

Post by Peter Robinson
https://koji.fedoraproject.org/koji/packageinfo?packageID=8
You'll find every thing to the latest 4.17 linus snapshot there.
Sadly there's no MakeItWork kernel command line option, it's a matter
of getting debug and trying to work out what went wrong and why. We
don't explicitly support these devices due to the lack of ease of
supporting them as you're finding out, but we don't do anything to
actively stop them working, it's very much a best effort, I suspect
there's something upstream that has regressed, the question is working
out what, and the last of that early boot output will be the best spot
to start.
Peter

Thanks for all the info, I have spotted what i think is the serial connectors, and i will try tomorrow to get serial working so i can give a better log (of the koji kernel) boot sequence.
_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to arm-***@lists.fedorap

[Steven Vanden Branden]

Post by Steven Vanden Branden
starting kernel..
then a black screen with the pinguin only (from uboot?), then that also disappears, it
seems the back-light is still on though, until i reset the tablet,

I am sorry but it seems my console was only set to the serial output (which i have not yet connected),
I have added console tty0 and tty1 as well to the startup console and now see for the 4.16.2 kernel:
please note that i made a video and the last 2 lines where blurred, screen was going nuts in final sequence,
but last readable is this ( i will redo this tomorrow with a serial connection )

sr_init: no PMIC hook to init smartreflex,
sr_init: platform driver register failed for SR

On 13.9 kernel this is the area around it in the dmesg output, maybe a clue to what should follow:

[ 5.109155] hctosys: unable to open rtc device (rtc0)
[ 5.117460] sr_init: No PMIC hook to init smartreflex
[ 5.125779] sr_init: platform driver register failed for SR
[ 5.135103] PM: Hibernation image not present or could not be loaded.
[ 5.135278] vcc3v0: disabling
[ 5.141402] vcc3v3: disabling
[ 5.147344] vcc5v0: disabling
[ 5.153217] usb0-vbus: disabling
[ 5.159321] usb1-vbus: disabling
[ 5.165320] usb2-vbus: disabling
[ 5.179038] Freeing unused kernel memory: 2048K
[ 5.186859] rodata_test: all tests were successful
[ 5.231177] systemd[1]: System time before build time, advancing clock.
[ 5.271629] systemd[1]: systemd 234 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN
default-hierarchy=hybrid)
[ 5.298946] systemd[1]: Detected architecture arm.
[ 5.306847] systemd[1]: Running in initial RAM disk
_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to

[Steven Vanden Branden]

hello everyone,

thanks for the assistance, but i managed to load the new kernel with the old dtb file for the inet1,

I made a diff between the new and old version , and there are a lot of changes, even gpio pins for that are changed (which i find strange, since the original device cannot be changed i guess, maybe gpio pin is changed in the dtsi files), and is suspect that new hardware is supported on the inet1, that now breaks my hacked together version using the inet1 dtb file.

but it turns out i need to spend time to add support for my board in uboot and in the kernel as well (mostly dts work i guess).

So if you have any tips/guidance on how to go about adding a new board (first in uboot i guess , then kernel), i would like to know.

Greetings,
Steven
_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to arm-l

[s***@gmail.com]

Post by Steven Vanden Branden
hello everyone,
thanks for the assistance, but i managed to load the new kernel with
the old dtb file for the inet1,
I made a diff between the new and old version , and there are a lot
of changes, even gpio pins for that are changed (which i find
strange, since the original device cannot be changed i guess, maybe
gpio pin is changed in the dtsi files), and is suspect that new
hardware is supported on the inet1, that now breaks my hacked
together version using the inet1 dtb file.
but it turns out i need to spend time to add support for my board in
uboot and in the kernel as well (mostly dts work i guess).
So if you have any tips/guidance on how to go about adding a new
board (first in uboot i guess , then kernel), i would like to know.
Greetings,
Steven

when i enable the original dtb file, the board is now working, I am
however succeeded in soldering a serial connection to the board.

The only strange thing is when i send from one side:

echo -en '\x00' > /dev/ttyS0 i receive 0x00 in hex
echo -en '\x01' > /dev/ttyS0 i receive 0x7F in hex

--> this makes the serial output unreadable since the mapping of
characters seems to be off, does anyone has an idea how to fix this?

--> i tried this with a baudrate of 300 to be sure the connection is
stable.

--> i tried to attach my serial output to the input of the pc and that
return fine, so it seems the 2 serial ports are actually speaking
another dialect.

Post by Steven Vanden Branden
_______________________________________________

_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an e

[Peter Robinson]

Post by s***@gmail.com

Post by Steven Vanden Branden
hello everyone,
thanks for the assistance, but i managed to load the new kernel with
the old dtb file for the inet1,
I made a diff between the new and old version , and there are a lot
of changes, even gpio pins for that are changed (which i find
strange, since the original device cannot be changed i guess, maybe
gpio pin is changed in the dtsi files), and is suspect that new
hardware is supported on the inet1, that now breaks my hacked
together version using the inet1 dtb file.
but it turns out i need to spend time to add support for my board in
uboot and in the kernel as well (mostly dts work i guess).
So if you have any tips/guidance on how to go about adding a new
board (first in uboot i guess , then kernel), i would like to know.
Greetings,
Steven

when i enable the original dtb file, the board is now working, I am
however succeeded in soldering a serial connection to the board.
echo -en '\x00' > /dev/ttyS0 i receive 0x00 in hex
echo -en '\x01' > /dev/ttyS0 i receive 0x7F in hex
--> this makes the serial output unreadable since the mapping of
characters seems to be off, does anyone has an idea how to fix this?
--> i tried this with a baudrate of 300 to be sure the connection is
stable.

All Allwinner devices I've seen use a rate of 115200, it may be that
the serial port isn't enabled by default in u-boot and/or the
DeviceTree because of it being a tablet and it not having one by
default so you might nee to look at what needs to change for that to
work.

Post by s***@gmail.com
--> i tried to attach my serial output to the input of the pc and that
return fine, so it seems the 2 serial ports are actually speaking
another dialect.

Post by Steven Vanden Branden
_______________________________________________

_______________________________________________

_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe

[s***@gmail.com]

Post by Peter Robinson

Post by s***@gmail.com
when i enable the original dtb file, the board is now working, I am
however succeeded in soldering a serial connection to the board.
echo -en '\x00' > /dev/ttyS0 i receive 0x00 in hex
echo -en '\x01' > /dev/ttyS0 i receive 0x7F in hex
--> this makes the serial output unreadable since the mapping of
characters seems to be off, does anyone has an idea how to fix this?
--> i tried this with a baudrate of 300 to be sure the connection is
stable.

All Allwinner devices I've seen use a rate of 115200, it may be that
the serial port isn't enabled by default in u-boot and/or the
DeviceTree because of it being a tablet and it not having one by
default so you might nee to look at what needs to change for that to
work.

its not really clear to me, but since i am capable to send data over in
hex, its seems that its enabled and also working on a rate of 300.
Because when i send '\x01\x01' i receive 0x7f7f on the receiver side.
Just to be clear i opened the serial terminal on my tablet as well
(from within fedora running on tablet) at a baudrate of 300.

Could it be that the dts is using the wrong serial device driver?
Are there many different serial drivers for the allwinner a10?
I am using this one:
***@01c28000 {
compatible = "snps,dw-apb-uart";
reg = <0x1c28000 0x400>;
interrupts = <0x1>;
reg-shift = <0x2>;
reg-io-width = <0x4>;
clocks = <0x3c 0x10>;
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <0x3d>;
};

I might be able to find out which serial device is used in the android
fex files.

Post by Peter Robinson

Post by s***@gmail.com
--> i tried to attach my serial output to the input of the pc and that
return fine, so it seems the 2 serial ports are actually speaking
another dialect.

Post by Steven Vanden Branden
_______________________________________________

_______________________________________________

_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscr

[Peter Robinson]

On Sat, Apr 14, 2018 at 1:18 PM, Steven Vanden Branden

Post by Steven Vanden Branden

Post by Peter Robinson
Hi,
That means nothing to me, I'm guessing it's a cheap AllWinner based
device, do you have any more details? Are you using a Fedora u-boot or
your own? If Fedora what's it called? What Fedora image are you using?

I is indeed a cheap cortex A10 Alwinner tablet, with 1Gb ram.
I started from image https://download.fedoraproject.org/pub/fedora/linux/releases/27/Spins/armhfp/images/Fedora-Xfce-armhfp-27-1.6-sda.raw.xz
and used the bootloader for A10-OLinuXino-Lime in the arm-imamge-installer, later on i replaced it with a bootloader compiled for the sun4i-a10-inet1 target, compiled from the uboot repo.

For reference I enabled a bunch of these devices in the Fedora u-boot
builds. I've not yet set them up in arm-image-installer but you can
just symlink a device to the AllWinner SoC there so it's quite
straight forward.

Post by Steven Vanden Branden
I update by sudo dnf update and everything still works except for the newer kernel.
Also its a inet 10F rev 03 model chipset.

Post by Peter Robinson
Touch screen is no real surprise if it's an AllWinner based tablet,
they change them constantly based on cost and availability.

the touchscreen is DPT 300-N3765A-C00, from the dpt group, i will see later if i can get the driver information from the android fex file, but the fex files have multiple touchscreens defined, so i will have to verify which one later.

Post by Peter Robinson
If one 4.13 works it's not surprising others do, what about 4.14.x

i will try the 4.14 kernel from koji as well.

Post by Peter Robinson
Can you some how grab the output up until it goes blank, I suspect
that last output might give us some idea.

starting kernel..
then a black screen with the pinguin only (from uboot?), then that also disappears, it seems the back-light is still on though, until i reset the tablet,
could it be that the load address of the kernel is wrong (kernel size got bigger?).

Post by Peter Robinson
What about a Fedora 4.16.2 (built yesterday) kernel? Unfortunately we
can't help with custom built kernels, it's almost impossible to remote
debug the Fedora ones, custom is the never step of impossible.

I understand, i will try with the that koji kernel as well.

Post by Peter Robinson
https://koji.fedoraproject.org/koji/packageinfo?packageID=8
You'll find every thing to the latest 4.17 linus snapshot there.
Sadly there's no MakeItWork kernel command line option, it's a matter
of getting debug and trying to work out what went wrong and why. We
don't explicitly support these devices due to the lack of ease of
supporting them as you're finding out, but we don't do anything to
actively stop them working, it's very much a best effort, I suspect
there's something upstream that has regressed, the question is working
out what, and the last of that early boot output will be the best spot
to start.
Peter

Thanks for all the info, I have spotted what i think is the serial connectors, and i will try tomorrow to get serial working so i can give a better log (of the koji kernel) boot sequence.
_______________________________________________

_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubsc