Error while doing a apt-get update

[cornelius lee]

Hi all,

I am quite new to the world of Beaglebone and networking so please bare with me.

I tried to do a apt-get update and tried to run ./update_kernel.sh but have encountered the following errors.

Err http://repos.rcn-ee.com wheezy Release.gpg                                                                                                                         

  Cannot initiate the connection to repos.rcn-ee.com:80 (2600:3c00::f03c:91ff:fe37:6ad5). - connect (101: Network is unreachable) [IP: 2600:3c00::f03c:91ff:fe37:6ad5 80]

Any suggestions, please?

Regards,

Cornelius

[c...@isbd.net]

cornelius lee <super....@gmail.com> wrote:
> [-- multipart/alternative, encoding 7bit, 66 lines --]
>
> [-- text/plain, encoding 7bit, charset: UTF-8, 28 lines --]

Your BBB doesn't have a connection to the internet, that's the problem.

If you are connecting to your BBB using a USB lead from a PC (MS or
Linux) then the BBB won't be able to 'see' the internet even if the PC
can. Connect the ethernet socket on the BBB to your router and then
it should be OK.

--
Chris Green
·

[Cornelius Lee]

Hi Chris,

Thank you for your email.

In a linux OS, I ssh into BBB via USB at 192.168.7.2. 

Then I configured it to bridge an internet connection with my laptop and am able to apt-get update peacefully.

However, when I have configured BBB to have a static ip address and connected it to a router, I had to change all http:// to ftp:// in /etc/apt/sources.lst in order to apt-get update smoothly. Also, with this configuration, I also encounter the above-mentioned error message about 45.33.2.10 which is unreachable. Thing is,. I can ping 45.33.2.10,..... this I find strange.

Any idea what I am doing wrong here?

Kind Regards,

Cornelius

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/cvW0j4knXe4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Robert Nelson]

On Thu, Mar 10, 2016 at 9:24 AM, Cornelius Lee <super....@gmail.com> wrote:
> Hi Chris,
>
> Thank you for your email.
>
> In a linux OS, I ssh into BBB via USB at 192.168.7.2.
> Then I configured it to bridge an internet connection with my laptop and am
> able to apt-get update peacefully.
>
> However, when I have configured BBB to have a static ip address and
> connected it to a router, I had to change all http:// to ftp:// in
> /etc/apt/sources.lst in order to apt-get update smoothly. Also, with this
> configuration, I also encounter the above-mentioned error message about
> 45.33.2.10 which is unreachable. Thing is,. I can ping 45.33.2.10,..... this
> I find strange.

Well, 'ftp' is not running http://repos.rcn-ee.com and i have no plans
to enable it..

Sorry...

Regards,

--
Robert Nelson
https://rcn-ee.com/

[Cornelius Lee]

Hi Robert,

Thank you for your email.

I understand now.

So,.. in order to have an internet connection for the BBB, it will only have to be via the USB with a bridged connection?

Also, I have noticed that after flashing BBB with the latest debian images, particularly 7.9 and 8.3, I am not able to ping 192.168.7.2. Is this a bug or am i missing something out here?

Regards,

Cornelius

[Robert Nelson]

On Thu, Mar 10, 2016 at 9:42 AM, Cornelius Lee <super....@gmail.com> wrote:
> Hi Robert,
>
> Thank you for your email.
>
> I understand now.
> So,.. in order to have an internet connection for the BBB, it will only have
> to be via the USB with a bridged connection?
>
> Also, I have noticed that after flashing BBB with the latest debian images,
> particularly 7.9 and 8.3, I am not able to ping 192.168.7.2. Is this a bug
> or am i missing something out here?

I'm really hopping with 2016-03-09 that's now solved, please test,
either the iot or lxqt image from:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Image_Testing_Snapshots

[Cornelius Lee]

Ah, great! Thank you.

I will test it tomorrow in the morning at the office then. 

I will keep you updated too. =)

Goodnight from Singapore.

[Robert Nelson]

On Thu, Mar 10, 2016 at 9:50 AM, Cornelius Lee <super....@gmail.com> wrote:
> Ah, great! Thank you.
> I will test it tomorrow in the morning at the office then.
> I will keep you updated too. =)
>
> Goodnight from Singapore.

BTW, I'm not sure how to reverse connman's direction:

But right now, when you plug in the usb connector, your laptop/desktop
will get an ip (192.168.7.x) and use the bbb for internet over your
laptop/desktop's wifi/ethernet.. So if you plug in an ethernet cable
into the bbb, you'll get network access again on your laptop/desktop..

Trying to figure out how to reverse that. ;)

[Cornelius Lee]

Hi Robert, 

I have just flashed https://rcn-ee.com/rootfs/bb.org/testing/2016-03-09/lxqt-4gb/BBB-eMMC-flasher-debian-8.3-lxqt-4gb-armhf-2016-03-09-4gb.img.xz

and i can't ping to 192.168.7.2. Furthermore, ifconfig pulls up no inet address on eth1.

Any idea why?

Regards,

Cornelius

[William Hermans]

Perhaps running dmesg will give you a better idea of what's going on. If nothing else it'll give you some output to post here for others to have  a better idea of whats going on.

example

william@beaglebone:~$ dmesg | grep eth
[    4.483906] cpsw 4a100000.ethernet: Detected MACID = 78:a5:04:ca:fb:dc
[   12.770249] net eth0: initializing cpsw version 1.12 (0)
[   12.780876] net eth0: phy found : id is : 0x7c0f1
[   12.795971] net eth0: phy 4a101000.mdio:03 not found on slave 1
[   12.806243] net eth0: BQL enabled
[   14.773478] cpsw 4a100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[563836.873858] cpsw 4a100000.ethernet eth0: Link is Down
[563838.954250] cpsw 4a100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[566399.033841] cpsw 4a100000.ethernet eth0: Link is Down
[566401.114229] cpsw 4a100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx

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.

[Cornelius Lee]

Hi William,

Thank you for your email,...below is what I get from running that command.

cornelius@cornelius ~ $ dmesg|grep eth

[    0.988379] e1000e 0000:00:19.0 eth0: registered PHC clock

[    0.988382] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) ec:f4:bb:0f:df:a3

[    0.988383] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection

[    0.988419] e1000e 0000:00:19.0 eth0: MAC: 11, PHY: 12, PBA No: FFFFFF-0FF

[    4.860468] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

[    7.445242] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None

[    7.445246] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO

[    7.445274] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

[ 2935.339583] usbcore: registered new interface driver cdc_ether

[ 2935.341774] rndis_host 1-2:1.0 eth1: register 'rndis_host' at usb-0000:00:14.0-2, RNDIS device, a0:f6:fd:4b:fd:c9

[ 3005.699765] NETDEV WATCHDOG: eth1 (rndis_host): transmit queue 0 timed out

[ 3005.699766] Modules linked in: rndis_wlan rndis_host cdc_ether usbnet mii cdc_acm nls_iso8859_1 uas usb_storage xt_multiport iptable_filter ip_tables x_tables pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) pn544_mei mei_phy pn544 hci nfc dell_wmi sparse_keymap uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media hid_logitech_hidpp snd_usb_audio snd_usbmidi_lib dell_laptop dcdbas i8k dm_multipath scsi_dh intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel arc4 kvm bnep snd_hda_codec_hdmi crct10dif_pclmul rfcomm crc32_pclmul ghash_clmulni_intel snd_hda_codec_realtek snd_hda_codec_generic snd_soc_rt5640 iwlmvm bluetooth snd_soc_rl6231 mac80211 aesni_intel snd_soc_core aes_x86_64 lrw gf128mul snd_compress glue_helper ablk_helper snd_pcm_dmaengine cryptd snd_hda_intel snd_hda_controller snd_seq_midi snd_hda_codec snd_seq_midi_event snd_hwdep snd_rawmidi iwlwifi snd_pcm joydev serio_raw cfg80211 lpc_ich shpchp mei_me mei 8250_fintek dw_dmac dell_smo8800 dw_dmac_core snd_seq snd_seq_device snd_soc_sst_acpi snd_timer snd i2c_hid 8250_dw spi_pxa2xx_platform i2c_designware_platform i2c_designware_core binfmt_misc dell_rbtn mac_hid soundcore parport_pc ppdev lp parport dm_mirror dm_region_hash dm_log hid_generic hid_logitech_dj usbhid hid i915 psmouse ahci i2c_algo_bit libahci sdhci_pci drm_kms_helper e1000e drm ptp pps_core wmi video sdhci_acpi sdhci

[ 3361.518375] rndis_host 1-2:1.0 eth1: unregister 'rndis_host' usb-0000:00:14.0-2, RNDIS device

[ 3395.837660] rndis_host 1-2:1.0 eth1: register 'rndis_host' at usb-0000:00:14.0-2, RNDIS device, a0:f6:fd:4b:fd:c9

and running dmesg|grep usb gives me the following,...

[ 2935.309616] usb 1-2: Product: BeagleBoneBlack

[ 2935.309617] usb 1-2: Manufacturer: Circuitco

[ 2935.309618] usb 1-2: SerialNumber: 5315BBBK0EEE

[ 2935.311093] usb-storage 1-2:1.4: USB Mass Storage device detected

[ 2935.311147] scsi host5: usb-storage 1-2:1.4

[ 2935.332057] usbcore: registered new interface driver cdc_acm

[ 2935.339583] usbcore: registered new interface driver cdc_ether

[ 2935.341774] rndis_host 1-2:1.0 eth1: register 'rndis_host' at usb-0000:00:14.0-2, RNDIS device, a0:f6:fd:4b:fd:c9

[ 2935.341859] usbcore: registered new interface driver rndis_host

[ 2935.344118] usbcore: registered new interface driver rndis_wlan

[ 3005.699766] Modules linked in: rndis_wlan rndis_host cdc_ether usbnet mii cdc_acm nls_iso8859_1 uas usb_storage xt_multiport iptable_filter ip_tables x_tables pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) pn544_mei mei_phy pn544 hci nfc dell_wmi sparse_keymap uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media hid_logitech_hidpp snd_usb_audio snd_usbmidi_lib dell_laptop dcdbas i8k dm_multipath scsi_dh intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel arc4 kvm bnep snd_hda_codec_hdmi crct10dif_pclmul rfcomm crc32_pclmul ghash_clmulni_intel snd_hda_codec_realtek snd_hda_codec_generic snd_soc_rt5640 iwlmvm bluetooth snd_soc_rl6231 mac80211 aesni_intel snd_soc_core aes_x86_64 lrw gf128mul snd_compress glue_helper ablk_helper snd_pcm_dmaengine cryptd snd_hda_intel snd_hda_controller snd_seq_midi snd_hda_codec snd_seq_midi_event snd_hwdep snd_rawmidi iwlwifi snd_pcm joydev serio_raw cfg80211 lpc_ich shpchp mei_me mei 8250_fintek dw_dmac dell_smo8800 dw_dmac_core snd_seq snd_seq_device snd_soc_sst_acpi snd_timer snd i2c_hid 8250_dw spi_pxa2xx_platform i2c_designware_platform i2c_designware_core binfmt_misc dell_rbtn mac_hid soundcore parport_pc ppdev lp parport dm_mirror dm_region_hash dm_log hid_generic hid_logitech_dj usbhid hid i915 psmouse ahci i2c_algo_bit libahci sdhci_pci drm_kms_helper e1000e drm ptp pps_core wmi video sdhci_acpi sdhci

[ 3361.518323] usb 1-2: USB disconnect, device number 5

[ 3361.518375] rndis_host 1-2:1.0 eth1: unregister 'rndis_host' usb-0000:00:14.0-2, RNDIS device

[ 3395.707524] usb 1-2: new high-speed USB device number 6 using xhci_hcd

[ 3395.835858] usb 1-2: New USB device found, idVendor=1d6b, idProduct=0104

[ 3395.835863] usb 1-2: New USB device strings: Mfr=3, Product=4, SerialNumber=5

[ 3395.835865] usb 1-2: Product: BeagleBoneBlack

[ 3395.835867] usb 1-2: Manufacturer: Circuitco

[ 3395.835869] usb 1-2: SerialNumber: 5315BBBK0EEE

[ 3395.837660] rndis_host 1-2:1.0 eth1: register 'rndis_host' at usb-0000:00:14.0-2, RNDIS device, a0:f6:fd:4b:fd:c9

[ 3395.838325] usb-storage 1-2:1.4: USB Mass Storage device detected

[ 3395.838386] scsi host6: usb-storage 1-2:1.4

It seems to me that usb0 isn't getting an ip address(192.168.7.2) correctly?

Any suggestions?

Regards,

Cornelius

[William Hermans]

It seems to me that usb0 isn't getting an ip address(192.168.7.2) correctly?

Any suggestions?

Woah nelly ! That's a lot of output, ;)

So, I'm not all that familiar with the Jessie images, but it seems as though the cdc_ether device is working fine. Have you attempted manually bring up eth1 ? e.g.

sudo ifconfig eth1 192.168.7.2

sudo ifconfig eth1 up

??

But even then I'm not sure what could be the cause for eth1 not coming up, other than a couple guesses. I might have to defer to Robert, as he honestly knows these images better than all.

[William Hermans]

sudo ifconfig eth1 up might actually need to be changed to sudo ifup eth1 to bring the device up.

[Robert Nelson]

It's coming thru..

what does:

sudo dhclient eth1
sudo ifconfig -a

show?

[Cornelius Lee]

Hi William and Robert,

Sorry about the long output a while ago,..I was trying to be as accurate as possible.

William:

cornelius@cornelius ~ $ sudo ifup eth1

Ignoring unknown interface eth1=eth1.

Robert:

ifconfig -a gives:

eth0      Link encap:Ethernet  HWaddr ec:f4:bb:0f:df:a3  

          inet addr:10.102.16.110  Bcast:10.102.17.255  Mask:255.255.254.0

          inet6 addr: fe80::eef4:bbff:fe0f:dfa3/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:1545343 errors:0 dropped:0 overruns:0 frame:0

          TX packets:584402 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000 

          RX bytes:1895631248 (1.8 GB)  TX bytes:46481091 (46.4 MB)

          Interrupt:20 Memory:f7e00000-f7e20000 

eth1      Link encap:Ethernet  HWaddr a0:f6:fd:4b:fd:c9  

          inet6 addr: fe80::a2f6:fdff:fe4b:fdc9/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:44 errors:3 dropped:0 overruns:0 frame:3

          TX packets:2 errors:638 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000 

          RX bytes:10678 (10.6 KB)  TX bytes:256 (256.0 B)

lo        Link encap:Local Loopback  

          inet addr:127.0.0.1  Mask:255.0.0.0

          inet6 addr: ::1/128 Scope:Host

          UP LOOPBACK RUNNING  MTU:65536  Metric:1

          RX packets:5072 errors:0 dropped:0 overruns:0 frame:0

          TX packets:5072 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0 

          RX bytes:475569 (475.5 KB)  TX bytes:475569 (475.5 KB)

wlan0     Link encap:Ethernet  HWaddr ac:7b:a1:39:3e:47  

          BROADCAST MULTICAST  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000 

          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

and,...sudo dhclient eth1 just gives me a blinking cusor staring blankly at me. Hhhmm,...

[William Hermans]

Ok, from here, I believe you could in fact set a static IP on the host and have it mostly, with perhaps having to manually route, if you decided to use ICS . . . but I've a feeling Robert may have a better solution . . .

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.

[William Hermans]

Cornelius, your host computer is a Mac ? Which OSX version ? just noticing your ethernet IP range . . .

[Robert Nelson]

yeah nothing..

So g_gadget serial is enabled:

gtkterm -s 115200 -p /dev/ttyACM0

root

It would be interesting to see what dhcp is doing:

journalctl | grep usb0
journalctl | grep -i dhcp

[Cornelius Lee]

hmm,..I must admit I am still quite new to networking principles at this stage. 

However, wouldn't that be impossible as I can't even access my BBB at all?

[Cornelius Lee]

William:

I am using Linux Mint in my host.

cornelius@cornelius /etc $ cat lsb-release

DISTRIB_ID=LinuxMint

DISTRIB_RELEASE=17.3

DISTRIB_CODENAME=rosa

DISTRIB_DESCRIPTION="Linux Mint 17.3 Rosa"

Robert:

cornelius@cornelius /etc $ journalctl|grep usb0

journalctl: command not found

cornelius@cornelius /etc $ journalctl|grep -i dhcp

journalctl: command not found

It seems to me that I will need to install a package that has that tool?

[Cornelius Lee]

sudo apt-get install gtkterm and,..

gtkterm -s 115200 -p /dev/ttyACM0 brings up a window but i can't type anything in it...

[Robert Nelson]

On Thu, Mar 10, 2016 at 9:51 PM, Cornelius Lee <super....@gmail.com> wrote:
> William:
> I am using Linux Mint in my host.
> cornelius@cornelius /etc $ cat lsb-release
> DISTRIB_ID=LinuxMint
> DISTRIB_RELEASE=17.3
> DISTRIB_CODENAME=rosa
> DISTRIB_DESCRIPTION="Linux Mint 17.3 Rosa"
>
> Robert:
> cornelius@cornelius /etc $ journalctl|grep usb0
> journalctl: command not found
> cornelius@cornelius /etc $ journalctl|grep -i dhcp
> journalctl: command not found

Oh, so "journalctl" is how we access the log with a systemd system.

By default, we setup a multi usb interface: usb flash, usb ethernet
(which we are debuggin) and a usb serial gadget.

So use "gtkterm" it's the easist gui program, and run:

gtkterm -s 115200 -p /dev/ttyACM0

This will give you a serial interface into the bbb..

Next run: (inside the bbb)

journalctl | grep usb0
journalctl | grep -i dhcp

That'll tell us what "usb0" is doing and we will see why "udhcpd"
isn't doing what it's suppost to..

[William Hermans]

Cornelius, if you're unable to access your beaglebone how is it that you're able to give us this information ? Anyway, what Robert is saying he thinks ( or knows ) the gadget serial device is active.

And now I see, you're running these commands from your host which is not what at least I intended.

This complicates things some. I have some ways around your problem ( yes multilple ways ), but they're rather complex. Perhaps Robert would have an easier suggestion than manually setting the IP on host, and beagleboard via sdcard reader, and all that . . .

[Cornelius Lee]

Ahhh i see,..thing is,..i don't have a serial cable connection from the BBB to my laptop though...hence, I will not be able to debug any further, correct?

Currently, BBB is plugged in through USB.

[Robert Nelson]

On Thu, Mar 10, 2016 at 9:58 PM, Cornelius Lee <super....@gmail.com> wrote:
> sudo apt-get install gtkterm and,..
> gtkterm -s 115200 -p /dev/ttyACM0 brings up a window but i can't type
> anything in it...

Doh, yeah there's that bug too..

I've been seeing that happen on my debian stretch workstations at home/work..

the serial works in windows 10 ;) (bang my head against the wall...)

i think that's actually kernel related, there's been a lot of gadget
driver changes in kernel land..

[Cornelius Lee]

William, what information were you referring to? Well, the BBB is detected in my linux file-system but i can't access it via ssh through USB after flashing the latest debian image that Robert proposed earlier on. However, with debian 7.8 running off the eMMC, I get a 192.168.7.2 as soon as I plug the BBB into the USB port of my laptop... this I found quite perplexing. Hence,..here I am. =-)

Hope this explains things a little better?

[William Hermans]

@Robert, would it be easier to just use an older, or newer image from sdcard ? Or would that do anything in the way of being able to read the logs from eMMC ?

--
For more options, visit http://beagleboard.org/discuss
---

[Cornelius Lee]

@Robert,

I see,..that was why I recalled posting a finding on the forum mentioning that after flashing debian 7.9 and 8.3, one would face that missing 192.168.7.2 issue. This does not occur in debian 7.8.

Yeah,..I had a funny feeling it might be linked to some kernel issues with the recent debian images.:(

You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/cvW0j4knXe4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.

[William Hermans]

William, what information were you referring to? Well, the BBB is detected in my linux file-system but i can't access it via ssh through USB after flashing the latest debian image that Robert proposed earlier on. However, with debian 7.8 running off the eMMC, I get a 192.168.7.2 as soon as I plug the BBB into the USB port of my laptop... this I found quite perplexing. Hence,..here I am. =-)

Hope this explains things a little better?

Well yes, and no. Robert apparently picked up right away those commands were being issued on your host, but I did not realize that, until you mentioned you were running Mint. I assumed you were running a Mac, based on the ethernet IP address your machine pulled, but that was just a guess. Some Linuxes pull in the 10.* range too . . .

Anyway, I do have some suggestions where we might proceed from here, but hoping Robert comes up with a better / easier suggestion. These suggestions I have are rather complex, easier to screw up, and rather long winded . . .

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.

[Cornelius Lee]

@William,

Yep, you are absolutely right! 

I was intending to ssh BBB via USB the same way I did after flashing debian 7.8 with the latest debian image but found that I couldn't cos' of the missing ip-address.

Yes, it would be wonderful for newbies like me if there would be an ip-address dished out by the DHCP in the BBB with the latest debian images as soon as one plugs it into the USB though.=) 

@Robert,

Forgive me for my ignorance, but how do I get this serial connector thingy working, please?

Is there some kind of gadget which I can buy off the shelf in an electronics store or do I have to assemble one by hand?

[William Hermans]

Cornelius,

I think probably for the time being, the best, and easiest solution would be for you to switch back to Wheezy 7.8, or 7.9. Then, you can upgrade to a newer 4.1.x kernel from there, and still have everything work correctly.

Then come back everyone once in a while an try a standalone image. Which if you're unaware of the differences.  A standalone image runs off an sdcard, instead of flashing the eMMC.

These newer Jessie images seem to still have issues, but if you give Robert a little while, I'm sure he'll eventually get the problems ironed out.

[Cornelius Lee]

Alright then, William.

As advised, I will reflash BBB with debian 7.8 and work from there.

Thank you and Robert so much for your patience and help.

Regards,

Cornelius

[Cornelius Lee]

Hi all,

Just an update.

I have re-flashed the BBB with debian 7.8 and upgraded the kernel from 

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Kernel_Upgrade

After a reboot, I am not able to log into the BBB via USB through ssh 192.168.7.2.

Regards,

Cornelius

[Dennis Lee Bieber]

On Fri, 11 Mar 2016 12:03:37 +0800, Cornelius Lee
<super....@gmail.com> declaimed the
following:

>Ahhh i see,..thing is,..i don't have a serial cable connection from the BBB
>to my laptop though...hence, I will not be able to debug any further,
>correct?
>
>Currently, BBB is plugged in through USB.
>

You shouldn't need a dedicated serial cable.

At least, in a quick test (using the Nov Wheezy image), and on a
Windows box, connecting my BBB resulted in device manager showing a COM12
("Gadget Serial") device. Opening a simple terminal program using COM12
(115200@8N1) gave me a log-in prompt. Of course, on whatever OS you are
using, the serial ports will likely have different nomenclature. If you are
"lucky" the serial port will appear/disappear when you connect/disconnect
the BBB -- so monitoring the device entry in your OS should identify what
name the port is getting.

Now to my knowledge, the BBB USB connection activates: a card reader
interface (at least it did with those older images; don't know if the new
"no FAT partition" images still mount that); a direct serial port
interface; and the Ethernet over USB interface.

I'll admit I've not tried to use the USB Ethernet connection; Don't
want to hassle with Windows Connection Sharing, so it is faster just to
CAT5 to my 8-port switch and use the router. (Yes, switch and router...
WiFi router had limited number of ports and was out-of-the-way, so one of
its ports feeds a more accessible switch).
--
Wulfraed Dennis Lee Bieber AF6VN
wlf...@ix.netcom.com HTTP://wlfraed.home.netcom.com/

[William Hermans]

g_ether works fine on the Wheezy images, but I think an image or two default to g_serial being setup by default. So either you'll have to use the serial over USB interface, or change the default configuration to use g_ether instead. This can be done from a host computer, if the given host computer has an sdcard reader. You'd setup an sdcard imge so you can boot from sdcard in order to modify the eMMC image . . . as I said initially, it is semi complex. But perfectly doable.

--
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.

[Robert Nelson]

On Fri, Mar 11, 2016 at 2:16 PM, William Hermans <yyr...@gmail.com> wrote:
> g_ether works fine on the Wheezy images, but I think an image or two default
> to g_serial being setup by default. So either you'll have to use the serial
> over USB interface, or change the default configuration to use g_ether
> instead. This can be done from a host computer, if the given host computer
> has an sdcard reader. You'd setup an sdcard imge so you can boot from sdcard
> in order to modify the eMMC image . . . as I said initially, it is semi
> complex. But perfectly doable.

ah crap.. it's the "RT"...

gtkterm -s 115200 -p /dev/ttyACM0

linux-image-4.1.18-ti-r52 = works on linux
linux-image-4.1.18-ti-rt-r52 = FAILS on linux (except for on windows)