Send connman mailing list submissions to
[email protected]
To subscribe or unsubscribe via email, send a message with subject or
body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."
Today's Topics:
1. Re: [PATCH] iwd: Use path to look up network when updating signal strength
(Daniel Wagner)
2. Re: [PATCH] iwd: transform signal strength from iwd range to connman range
(Daniel Wagner)
3. Re: [yocto] lost busybox mysteriously (JH)
4. RE: [PATCH] iwd: Use path to look up network when updating signal strength
(David Weidenkopf)
5. Re: [PATCH] iwd: Use path to look up network when updating signal strength
(Daniel Wagner)
6. RE: [PATCH] iwd: Use path to look up network when updating signal strength
(David Weidenkopf)
----------------------------------------------------------------------
Date: Tue, 28 Jan 2020 09:11:20 +0100
From: Daniel Wagner <[email protected]>
Subject: Re: [PATCH] iwd: Use path to look up network when updating
signal strength
To: David Weidenkopf <[email protected]>
Cc: connman <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Hi David,
On Tue, Jan 28, 2020 at 12:22:41AM +0000, David Weidenkopf wrote:
> Look up network instance using path in order to update signal
> strength for network. Previously, only connected networks signal
> strength was updated.
I've applied the patch after changing a bit of the commit
message. Note the commit message line length is also at 80 characters.
Unfortantly, your patch wont apply directly. I had to recreate this
patch. I think it's because the footer. Anyway, could you please try
to send them with git send-email?
Thanks,
Daniel
------------------------------
Date: Tue, 28 Jan 2020 09:12:25 +0100
From: Daniel Wagner <[email protected]>
Subject: Re: [PATCH] iwd: transform signal strength from iwd range to
connman range
To: David Weidenkopf <[email protected]>
Cc: connman <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Hi David,
On Tue, Jan 28, 2020 at 12:43:46AM +0000, David Weidenkopf wrote:
> This transforms the signal strength, according to the comment
> regarding expected iwd values.
Patch applied too. Same comment as in the other mail.
Thanks,
Daniel
------------------------------
Date: Tue, 28 Jan 2020 21:40:19 +1100
From: JH <[email protected]>
Subject: Re: [yocto] lost busybox mysteriously
To: Gabriele Zampieri <[email protected]>
Cc: Quentin Schulz <[email protected]>, Andy Pont
<[email protected]>, Yocto discussion list
<[email protected]>, linux-mtd <[email protected]>,
connman <[email protected]>
Message-ID:
<CAA=hcwtxx5grnejzkcjfhbe9mfvy8a7hg+exbmczzsafysp...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Hi Gabriele,
On 1/28/20, Gabriele Zampieri <[email protected]> wrote:
> HI JH,
>
> - Can you stop on uboot and try "nand bad"? This will list the bad blocks
> on your device.
=> nand bad
Device 0 bad blocks:
> - How do you flash your ubi partition(s)?
I boot zImage-initramfs kernel to Linux user space, then run:
ubidetach -p /dev/mtd5
ubiformat /dev/mtd5 -y
ubiattach -m 5
ubimkvol /dev/ubi0 -s 160MiB -N rootfs_data
mount -t ubifs ubi0:rootfs_data /mnt
cp -adr /yocto_rootfs/* /mnt
> - During boot, does ubifs layer complain about the partition is it trying
> to mount? It will in case of corrupted metadata and may result in a read
> only mount.
There is no partition involved during the boot, all partitions start
in user space after booting.
> - It's pretty weird that busybox has gone and the partition is intact.
> Didn't you messed with any script? Can you replicate on another board?
I don't think it was bad block problem, because it is a new version
hardware, which has some problem in power supply, could unstable or
insufficient power supply cause MTD / NAND crash?
Thank you Gabriele,
Kind regards,
- jh
>
> On Tue, Jan 28, 2020 at 7:25 AM JH <[email protected]> wrote:
>
>> On 1/27/20, Quentin Schulz <[email protected]> wrote:
>> > Hi JH,
>> >
>> > On Mon, Jan 27, 2020 at 10:13:37PM +1100, JH wrote:
>> >> Hi Andy,
>> >>
>> >> Thanks for the response.
>> >>
>> >> On 1/27/20, Andy Pont <[email protected]> wrote:
>> >> > JH wrote...
>> >> >
>> >> >>That the same problem of missing busybox was not just occurred
>> >> >> during
>> >> >>the device running in the middle of operation, it was also occurred
>> >> >>during booting image from NAND, I saw several times that the first
>> >> >> and
>> >> >>second cycles of booting image from NAND were working well, then
>> >> >> some
>> >> >>following booting process would be crashed by missing busybox, then
>> >> >>could not run whole shell commands. I have been pondering if it
>> >> >> could
>> >> >>be caused by NAND issue or network virus / fishy? Appreciate any
>> >> >>clues.
>> >> > The first step is for us to understand what “missing” means? Have
>> >> > you
>> >> > got any mechanism (U-Boot, SD card boot, etc.) that will allow you
>> >> > to
>> >> > mount and look at the contents of the NAND file system?
>> >>
>> >> Means that busybox was not there anymore, it mysteriously lost, all
>> >> shell commands would no longer available. It cannot to run mount or
>> >> any shell commands. There was two scenarios when that happened:
>> >>
>> >> - In the middle of running, the device all of certain could not run
>> >> shell commands and failed mysteriously
>> >>
>> >> - During the u-boot booting kernel process, there were full errors of
>> >> failing shell commands. Let me make it clear, that booting error did
>> >> not occur in the first or second kernel booting after the new image
>> >> installation, it happened in the following kernel booting, but there
>> >> was nothing to delete busybox accidentally, busybox was just
>> >> mysteriously disappeared. Because I could not run ls, I did not know
>> >> if there are other things missing. If you ask how I could know the
>> >> busybox was missing, I ran the zImage-initramfs to boot the linux in
>> >> RAM, then mount the ubi0 to find out busybox was gone.
>> >>
>> >>
>> >> > If you look at the /bin directory (ls -la /bin/busy*) what do you
>> >> > see?
>> >> > Have the files been deleted? Truncated? Zero length?
>> >>
>> >> Could not run ls or any shell commands when the busybox was missing.
>> >>
>> >
>> > /bin/ls -la /bin/busy* ?
>> >
>> > Maybe something is messing with the PATH environment variable. Or
>> > something is removing the symlinks from some binaries to busybox.
>>
>> No, could not run /bin/ls as it was linked to /bin/busybox.nosuid,
>> the /bin/busybox.nosuid was damaged for some reason.
>>
>> >> > What file system are you using on the NAND flash? How are the
>> >> > devices
>> >> > being reset during the various boot cycles? If it is a hardware
>> >> > reset
>> >> > then some file systems are less resilient to it than others but I
>> would
>> >> > expect in that case more fundamental boot issues.
>> >>
>> >> UBIFS, most device reset or boot cycles were calling halt or reboot,
>> >> but it sometime it could just use power cycle.
>> >>
>> >
>> > IIRC, UBIFS is safe from power cycles.
>>
>> Good to know. Thank you.
>>
>> > Quentin
>> >
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>>
>> View/Reply Online (#48171):
>> https://lists.yoctoproject.org/g/yocto/message/48171
>> Mute This Topic: https://lists.yoctoproject.org/mt/70128245/3618237
>> Group Owner: [email protected]
>> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [
>> [email protected]]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>
>
------------------------------
Date: Tue, 28 Jan 2020 16:56:01 +0000
From: David Weidenkopf <[email protected]>
Subject: RE: [PATCH] iwd: Use path to look up network when updating
signal strength
To: Daniel Wagner <[email protected]>
Cc: connman <[email protected]>
Message-ID:
<06C3949C7271B8419F288F951ED39EC20C6671@AME-MBX-PRD02.arthrex.local>
Content-Type: text/plain; charset="us-ascii"
________________________________________
From: Daniel Wagner [[email protected]]
Sent: Tuesday, January 28, 2020 12:11 AM
To: David Weidenkopf
Cc: connman
Subject: Re: [PATCH] iwd: Use path to look up network when updating signal
strength
>Hi David,
>On Tue, Jan 28, 2020 at 12:22:41AM +0000, David Weidenkopf wrote:
>> Look up network instance using path in order to update signal
>> strength for network. Previously, only connected networks signal
>> strength was updated.
>I've applied the patch after changing a bit of the commit
>message. Note the commit message line length is also at 80 characters.
I will comply with the limit in the future, thanks for fixing for me.
>Unfortantly, your patch wont apply directly. I had to recreate this
>patch. I think it's because the footer. Anyway, could you please try
>to send them with git send-email?
Sorry about that. I am probably going to use a different email from now on
because of that footer. And I will use git send-email in the future.
>Thanks,
>Daniel
Welcome. I am hoping to help get iwd support in great shape. Like others, I
would like to adopt it as soon as possible. Thanks for getting so much done on
it.
This e-mail and any files transmitted with it are the property of Arthrex, Inc.
and/or its affiliates, are confidential, and are intended solely for the use of
the individual or entity to whom this e-mail is addressed. If you are not one
of the named recipient(s) or otherwise have reason to believe that you have
received this message in error, please notify the sender at 239-643-5553 and
delete this message immediately from your computer. Any other use, retention,
dissemination forwarding, printing or copying of this e-mail is strictly
prohibited. Please note that any views or opinions presented in this email are
solely those of the author and do not necessarily represent those of the
company. Finally, while Arthrex uses virus protection, the recipient should
check this email and any attachments for the presence of viruses. The company
accepts no liability for any damage caused by any virus transmitted by this
email.
------------------------------
Date: Tue, 28 Jan 2020 18:35:57 +0100
From: Daniel Wagner <[email protected]>
Subject: Re: [PATCH] iwd: Use path to look up network when updating
signal strength
To: David Weidenkopf <[email protected]>
Cc: connman <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi David,
On 28.01.20 17:56, David Weidenkopf wrote:
>> Unfortantly, your patch wont apply directly. I had to recreate this
>> patch. I think it's because the footer. Anyway, could you please try
>> to send them with git send-email?
>
> Sorry about that. I am probably going to use a different email from now on
> because of that footer. And I will use git send-email in the future.
No problem. I am no stranger to corporate email setups. It is usually a
mess...
Anyway, it should be no problem to setup git send-email so that you send
it let's say from gmail and still getting your corporate email into the
git history. The first line in the commit needs to be 'From: <>'. There
is excellent documentation on the internet.
> Welcome. I am hoping to help get iwd support in great shape. Like others, I
> would like to adopt it as soon as possible. Thanks for getting so much done
> on it.
Thanks for testing and fixing the iwd plugin. It's clearly the way
forward. Though there is a few things to do but this is for the
next iteration. I'd like to stabilize the current tree and release
soon. So if you have still see things not working with iwd please
let us know.
Thanks,
Daniel
------------------------------
Date: Tue, 28 Jan 2020 18:01:02 +0000
From: David Weidenkopf <[email protected]>
Subject: RE: [PATCH] iwd: Use path to look up network when updating
signal strength
To: Daniel Wagner <[email protected]>
Cc: connman <[email protected]>
Message-ID:
<06C3949C7271B8419F288F951ED39EC20C66C8@AME-MBX-PRD02.arthrex.local>
Content-Type: text/plain; charset="us-ascii"
________________________________________
From: Daniel Wagner [[email protected]]
Sent: Tuesday, January 28, 2020 9:35 AM
To: David Weidenkopf
Cc: connman
Subject: Re: [PATCH] iwd: Use path to look up network when updating signal
strength
Hi Daniel,
>Hi David,
>On 28.01.20 17:56, David Weidenkopf wrote:
>>> Unfortantly, your patch wont apply directly. I had to recreate this
>>> patch. I think it's because the footer. Anyway, could you please try
>>> to send them with git send-email?
>>
>> Sorry about that. I am probably going to use a different email from now on
>> because of that footer. And I will use git send-email in the future.
>No problem. I am no stranger to corporate email setups. It is usually a
>mess...
>Anyway, it should be no problem to setup git send-email so that you send
>it let's say from gmail and still getting your corporate email into the
>git history. The first line in the commit needs to be 'From: <>'. There
>is excellent documentation on the internet.
Thanks for your patience.
> Welcome. I am hoping to help get iwd support in great shape. Like others, I
> would like to adopt it as soon as possible. Thanks for getting so much done
> on it.
>Thanks for testing and fixing the iwd plugin. It's clearly the way
>forward. Though there is a few things to do but this is for the
>next iteration. I'd like to stabilize the current tree and release
>soon. So if you have still see things not working with iwd please
>let us know.
My focus this week is actually on 8021x. I got distracted when I
noticed signal strength not updating :), and troubleshooting
freeradius setup is a challenge.I will have comments, bug reports
or fixes soon, I hope.
>Thanks,
>Daniel
This e-mail and any files transmitted with it are the property of Arthrex, Inc.
and/or its affiliates, are confidential, and are intended solely for the use of
the individual or entity to whom this e-mail is addressed. If you are not one
of the named recipient(s) or otherwise have reason to believe that you have
received this message in error, please notify the sender at 239-643-5553 and
delete this message immediately from your computer. Any other use, retention,
dissemination forwarding, printing or copying of this e-mail is strictly
prohibited. Please note that any views or opinions presented in this email are
solely those of the author and do not necessarily represent those of the
company. Finally, while Arthrex uses virus protection, the recipient should
check this email and any attachments for the presence of viruses. The company
accepts no liability for any damage caused by any virus transmitted by this
email.
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list -- [email protected]
To unsubscribe send an email to [email protected]
------------------------------
End of connman Digest, Vol 51, Issue 36
***************************************
