Re: [beagleboard] unable to login to root after I updated my beagle board black to debian 9 images

[Nicole]

Thank you!

On Monday, February 18, 2019 at 9:28:00 PM UTC-5, Jim F wrote:
>
> It's considered poor form to log in to root directly these days, 
> particularly over ssh. Instead you log into a user account and either sudo 
> or su to do what you require. It is wise to change the root password, so 
> just log in as debian, sudo -s and then set the root password. If you 
> choose to log in as root thereafter, you can do so, but you should check to 
> see that root logins are allowed in sshd.conf.
>
> In direct answer: logging in as debian should be fine, but it's not root. 
> (Generally that's a good thing)
>
> Best,
>
> Jim
>
> On Tue, Feb 19, 2019 at 2:06 AM > wrote:
>
>> Hello,
>>
>> I am new to using a beagle board and I just updated it to the debian 9 
>> images. Before I updated it, I was successfully logging in to root without 
>> a password through Putty. *I never created a password for root.* After I 
>> updated and flashed it to the board, i was asked for a password for root 
>> whenever I logged in and I do not know what password to put in. I have 
>> tried 'temppwd' and that did not work. I tried logging in to debian and 
>> that has worked successfully.
>>
>> *it looked like this in Putty after the update:*
>>
>> *login: root*
>> *ro...@192.168.7.2 's password:*
>> *Password denied*
>>
>> Can I just use debian or am I supposed to login to root every time? I 
>> have a project involving this beagle board and I was wondering if logging 
>> in as debian is fine.
>>
>> -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to beagleboard...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/5f9e3324-5440-4b06-a6e6-4bb8bebcb441%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/989c9a74-1c0c-4159-be11-1a9e5eb889ad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] unable to login to root after I updated my beagle board black to debian 9 images

[Jim F]

It's considered poor form to log in to root directly these days,
particularly over ssh. Instead you log into a user account and either sudo
or su to do what you require. It is wise to change the root password, so
just log in as debian, sudo -s and then set the root password. If you
choose to log in as root thereafter, you can do so, but you should check to
see that root logins are allowed in sshd.conf.

In direct answer: logging in as debian should be fine, but it's not root.
(Generally that's a good thing)

Best,

Jim

On Tue, Feb 19, 2019 at 2:06 AM  wrote:

> Hello,
>
> I am new to using a beagle board and I just updated it to the debian 9
> images. Before I updated it, I was successfully logging in to root without
> a password through Putty. *I never created a password for root.* After I
> updated and flashed it to the board, i was asked for a password for root
> whenever I logged in and I do not know what password to put in. I have
> tried 'temppwd' and that did not work. I tried logging in to debian and
> that has worked successfully.
>
> *it looked like this in Putty after the update:*
>
> *login: root*
> *root@192.168.7.2 's password:*
> *Password denied*
>
> Can I just use debian or am I supposed to login to root every time? I have
> a project involving this beagle board and I was wondering if logging in as
> debian is fine.
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/5f9e3324-5440-4b06-a6e6-4bb8bebcb441%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAGS%2B2h8oCpg7imm7bZ3YBRT4zLmLOg%3Dz5iv2RHVwOD1JXxjRoQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] unable to login to root after I updated my beagle board black to debian 9 images

[quiteadream]

Hello,

I am new to using a beagle board and I just updated it to the debian 9 
images. Before I updated it, I was successfully logging in to root without 
a password through Putty. *I never created a password for root.* After I 
updated and flashed it to the board, i was asked for a password for root 
whenever I logged in and I do not know what password to put in. I have 
tried 'temppwd' and that did not work. I tried logging in to debian and 
that has worked successfully.

*it looked like this in Putty after the update:*

*login: root*
*root@192.168.7.2's password:*
*Password denied*

Can I just use debian or am I supposed to login to root every time? I have 
a project involving this beagle board and I was wondering if logging in as 
debian is fine.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/5f9e3324-5440-4b06-a6e6-4bb8bebcb441%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: On BBB - How to use I2C-1 ? It exists but maybe needs pins setup ? BBB Rev C & Debian 9

[graham]

I2C-1 is used for internal power management and on board EEPROM access 
purposes.
Unless you have a specific need, I suggest you use I2C-2 for external 
control purposes.
It is already pinned-out by default on P9-17 and P9-18
--- Graham

==

On Monday, February 18, 2019 at 1:22:57 PM UTC-6, bruce...@yahoo.com wrote:
>
> On Beaglebone Black (BBB) - How to use I2C-1 ? It exists but maybe needs 
> pins setup ? BBB Rev C & Debian 9.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/bb3f0287-ad99-4ccb-9481-965cca177611%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] On BBB - How to use I2C-1 ? It exists but maybe needs pins setup ? BBB Rev C & Debian 9

[brucejs777 via BeagleBoard]

On Beaglebone Black (BBB) - How to use I2C-1 ? It exists but maybe needs 
pins setup ? BBB Rev C & Debian 9.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/0b9afe43-1d07-48d6-b52a-79904d943fd1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBB: Using DMA with SPI

[alberkurt]

Hi! Could anyone add an example how to use dma-spi on bbb? I run bbb 
4.14.71-ti-r80 and have no clue how to use it.
On the web there are mixed answers to the performance of spi-dma on bbb. Is 
it worth the effort, to me it seems rather complex implementing it.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/9fb7deb9-b4f7-4f67-aafa-2a85af732105%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Why dns is not working in this BBB -> laptop hotspot configuration

[ithinu]

Possibly, I do not know a lot about it. At the beginning of the file, there 
is "# Generated by Connection Manager" though.


On Monday, February 18, 2019 at 1:35:05 PM UTC+1, ith...@gmail.com wrote:
>
> So it is like that: even if I put nameservers 10.42.0.1 or 8.8.8.8, 
> whatever, into connmanctl config and asking it then shows that exact IP as 
> the DNS server, what is put into resolv.conf is some three values which 
> look like IP6 adresses, I have no idea what they mean. Anyway, DNS is not 
> working with them and I need to replace everything in resolv.conf with 
> nameserver 10.42.0.1 after every rewrite of the file by connmanctl, then it 
> works fine.
>
>
> On Wednesday, February 13, 2019 at 7:36:37 PM UTC+1, ith...@gmail.com 
> wrote:
>>
>> Strangely the hotspot was set as DNS before, but it did not work back 
>> then.
>>
>> Thank you all for your support.
>>
>> .On Wednesday, February 13, 2019 at 6:09:32 PM UTC+1, Sicelo Mhlongo 
>> wrote:
>>>
>>> On Wed, Feb 13, 2019 at 09:01:36AM -0800, ith...@gmail.com wrote: 
>>> > Is there a way of just replacing connmanm with wpa_supplicant using 
>>> apt_get? 
>>> > 
>>>
>>> Yes there is. Note that there is nothing wrong with connman. You can 
>>> learn it, like you learned any other tool, e.g. wpa_supplicant, nmcli. 
>>>
>>> One more thing, connmanctl can connect to an Enterprise network. You 
>>> need to prepare the corresponding file, just like you will need to with 
>>> wpa_supplicant 
>>>
>>>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/7e1ec7fa-3371-44c0-aa79-435ae87c4a45%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Why dns is not working in this BBB -> laptop hotspot configuration

[Tarmo Kuuse]

On Monday, 18 February 2019 14:35:05 UTC+2, ith...@gmail.com wrote:
>
> So it is like that: even if I put nameservers 10.42.0.1 or 8.8.8.8, 
> whatever, into connmanctl config and asking it then shows that exact IP as 
> the DNS server, what is put into resolv.conf is some three values which 
> look like IP6 adresses, I have no idea what they mean. Anyway, DNS is not 
> working with them and I need to replace everything in resolv.conf with 
> nameserver 10.42.0.1 after every rewrite of the file by connmanctl, then it 
> works fine.
>

Well, the contents of resolv.conf come from your DHCP server (unless you've 
arranged it differently). To fix that, you'd need to re-configure your DHCP 
server.

--
Kind regards
Tarmo

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/853ef0ad-c000-48ce-a732-62efcd85944c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Why dns is not working in this BBB -> laptop hotspot configuration

[ithinu]

So it is like that: even if I put nameservers 10.42.0.1 or 8.8.8.8, 
whatever, into connmanctl config and asking it then shows that exact IP as 
the DNS server, what is put into resolv.conf is some three values which 
look like IP6 adresses, I have no idea what they mean. Anyway, DNS is not 
working with them and I need to replace everything in resolv.conf with 
nameserver 10.42.0.1 after every rewrite of the file by connmanctl, then it 
works fine.


On Wednesday, February 13, 2019 at 7:36:37 PM UTC+1, ith...@gmail.com wrote:
>
> Strangely the hotspot was set as DNS before, but it did not work back then.
>
> Thank you all for your support.
>
> .On Wednesday, February 13, 2019 at 6:09:32 PM UTC+1, Sicelo Mhlongo wrote:
>>
>> On Wed, Feb 13, 2019 at 09:01:36AM -0800, ith...@gmail.com wrote: 
>> > Is there a way of just replacing connmanm with wpa_supplicant using 
>> apt_get? 
>> > 
>>
>> Yes there is. Note that there is nothing wrong with connman. You can 
>> learn it, like you learned any other tool, e.g. wpa_supplicant, nmcli. 
>>
>> One more thing, connmanctl can connect to an Enterprise network. You 
>> need to prepare the corresponding file, just like you will need to with 
>> wpa_supplicant 
>>
>>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/ed1f82b7-7cc9-4a64-8126-66c486345e71%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] 4.19 bone kernel with uio_pruss?

['Roger Quadros' via BeagleBoard]

On 13/02/2019 19:13, Robert Nelson wrote:
>> Sorry, I'm still a bit lost here ;).
>> How do I see the PRUSS kernel patches that you have picked up?
> 
> Okay for v4.19.x & v4.20.x, i've picked up RFC 1: (I need to backport
> the am33xx-l4 dts changes to then backport RFC2..)
> 
> https://github.com/RobertCNelson/bb-kernel/blob/am33x-v4.20/patch.sh#L382-L392
> 
> https://github.com/RobertCNelson/bb-kernel/tree/am33x-v4.20/patches/drivers/ti/pruss
> 
> from : https://lkml.org/lkml/2018/11/22/948
> 
> https://github.com/RobertCNelson/bb-kernel/tree/am33x-v4.20/patches/drivers/ti/remoteproc
> 
> from : https://lkml.org/lkml/2018/11/26/319
> 
> and we needed: https://lkml.org/lkml/2018/12/2/361
> 
> https://github.com/RobertCNelson/bb-kernel/tree/am33x-v4.20/patches/drivers/ti/pruss-from-v4.14.x-ti
> 
> For 5.0.x/5.1.x: I've picked up RFC 2 directly from your git tree:
> 
> https://github.com/rogerq/linux/commits/for-v5.1/pruss-2.0
> 
> https://github.com/RobertCNelson/bb-kernel/tree/am33x-v5.0/patches/drivers/ti/rogerq_pruss
> 
> https://github.com/RobertCNelson/bb-kernel/blob/am33x-v5.0/patch.sh#L352-L379
> 

Thanks.

>>
 All upstream PRUSS series that I posted will not work without changes in
 the resource tables in pru-software-support packages.

 e.g.
 https://github.com/rogerq/pru-software-support-package/commit/6346adba63c1e91414df8f3ea3cd73ccc40d0f2f

 If you can wait for 2 weeks then we could have something in
 TI 2019 that should work smoothly.
>>>
>>> So around the time that your first RFC came out, we actually added
>>> that repo by default under /opt/source/ so users could test out your
>>> patchset on the beagle default images:
>>>
>>> https://github.com/RobertCNelson/omap-image-builder/commit/edd84bc5c2d925d67d00d0c2008f48cdd75e3e99
>>>
>>> So any Stretch/Buster/Bionic image after Nov 24 2018, has your repo
>>> installed by default in the root file system. ;)
>>
>> OK. But I haven't fixed all examples as I wasn't sure if the changes that
>> I'm making will be accepted or not.
> 
> I assumed that repo would be a work in progress, it was more to make
> it easy for pru users to give it a quick test and give some feedback
> 
>> Suman has insisted that he wants to continue using the old resource table 
>> format
>> for TI's 2019 release.
>>
>> What do you think is the best approach to take?
> 
> I think what TI has been doing with pru-remoteproc just isn't
> working... To give you some perspective on what users of this forum
> have dealt with: TI's "changed" the pru-remoteproc interface/etc for
> end users in every TI kernel: From v3.14.x-ti, v4.1.x-ti, v4.4.x-ti,
> v4.9.x-ti, to v4.14.x-ti..  It's really Painful..> 
> Whereas the uio interface is compatible all the way back to our
> ancient 3.8.x based kernel..  and yes the uio driver isn't perfect,
> secure, etc..
> 
> So yeah, we will make what every you guys do in v4.19.x-ti as the
> default for our "v4.19.x-ti" kernel, but just note, there is a big
> user base, that won't care and will just use the uio interface in real
> designs and products.  Unless "SOMETHING" goes mainline, then the user
> base doesn't have to worry about it changing on every release.

Yes, having PRUSS support in mainline is very important for us.

> 
>> I would suggest.
>> -Get PRUSS kernel drivers via ti-linux-4.19.y
> 
> That's the default plan..
> 
>> -Switch pru-software-package to use 
>> git://git.ti.com/pru-software-support-package/pru-software-support-package.git
> 
> That also the default ;)  It's actually packaged into a deb package..
> using git of: df5794ce7611f8587950f491ef9bf11807e1d0cf
> 
> https://github.com/rcn-ee/repos/blob/master/ti-pru-software-support-package/version.sh
> 
> Regards,
> 

-- 
cheers,
-roger

Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/2917467a-8e11-25ff-bf51-d12fae9a70af%40ti.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBBW antenna placement on a enclosure panel

[don_wrt]

Hello,

I want to learn that is there a constraint of placement of BBBW' antennas 
on a enclosure's panel? I mean that how much two antennas should be close 
to each other? or what is the maximum distance between the two antennas on 
the enclosure panel to obtain a correct radiation? Should two antennas be 
parallel each other? 

Thank you,

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/ff4be50b-1601-486f-b572-83b55aa14aea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.