Debian kernel 3.8 to 3.14 no ssh via usb

GoogleGroups
1

Hello ,

I’m want to switch to Kernel 3.14 from 3.8, so i upgraded the kernel by issuing commands

sudo apt-get update
sudo apt-get install linux-image-3.14.19-ti-r27 a

this updated the kernel but thereafter i was not unable to SSH via USB what i also noted is the Flash Storage didn’t Mount
as usually it used to in 3.8.

I tried this twice with different kernel images of 3.14 releases. But no success same thing

Thereafter i downloaded the image from website with 3,14 kernel, flashed the eMMC (BBB-eMMC-flasher-debian-jessie-lxqt-armhf-2014-10-22-2gb.img)
Note : - Im using a 4GB Flash BBB, Rev C

Now the Drive is mounted in PC but still i cant connect the BBB via SSH the IP I’m using is 192.168.7.2 Port 22

I’m unable to debug via SERIAL as i don’t have a USB-TTL 3.3 V Cable yet.

Regards

Altaf

2

correct, in the notes i noted a missing package.. anywho, uploaded a
new image last night, just haven't finished documenting things..

https://rcn-ee.net/deb/testing/2014-11-11/lxqt/BBB-eMMC-flasher-debian-jessie-lxqt-armhf-2014-11-11-2gb.img.xz

Regards,

3

Hello , Robert

It work’s now !!
I’m able to connect via USB to SSH with Kernel 3.14

Thanks a lot !!!
Really appreciate all your work and your instant help always.
Thankyou once again

Regards
Altaf

4

Hello ,

Well after successful installation and getting SSH the first thing i tried was USB WiFi which seems not to be working on this kernel worked well with 3.8

USB Stick Details = TP-LINK TL-WN722N

lsusb
Bus 001 Device 003: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

dmesg | grep phy0
[ 119.039706] ieee80211 phy0: Atheros AR9271 Rev:1

this was working well with Kernel 3.8, after doing all the basic Wireless Configurations required and issuing the command

ifup wlan0

The command in 3.14 Kernel after doing all required configurations produces the error “Operation not possible due to RF-kill” detailed description listed below

Internet Systems Consortium DHCP Client 4.3.1
Copyright 2004-2014 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

RTNETLINK answers: Operation not possible due to RF-kill
Listening on LPF/wlan0/e8:de:27:05:af:fc
Sending on LPF/wlan0/e8:de:27:05:af:fc
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
send_packet: Network is down
dhclient.c:1966: Failed to send 300 byte long packet over wlan0 interface.
receive_packet failed on wlan0: Network is down

Regards
Altaf

5

I've been seeing this from a few users on this group, I just better
kill-rf-kill... till the newer v3.14.x hit's repo you can downgrade to
v3.8.x via:

sudo apt-get update
sudo apt-get install linux-image-3.8.13-bone67
sudo reboot

*wish wifi wasn't blocked at work so i could actually test wifi their. :wink:

Regards,

6

Hello,Robert

Thanks,

Alright will wait for a new repo..
initially switch back to 3.8

Regards
Altaf

7

Robert, wasnt there just a post the other night how to bypass this on 3.14.x ? Something about downloading rfkill via apt ( yeah didnt make sense to me either ), then configure-ring it to ignore a device ?

8

Thanks! I'll look up that conversation again..

One of things i changed with this snapshot, we added bluez/bluetooth..

So i've playing with a couple settings trying to get my wifi adapter
to scan in cmst again..

rfkill wasn't installed, so i just tried that.. no change yet..
removed bluez/bluetooth still no go...

Just finished rebuilding connman 1.26 so lets see if that helps too..

Regards,

9

Humm, why didn't "wpasupplicant" get installed... manually add's it
back to the config..

Regards,

10

Now it works... okay, no idea what i did... reflash and start again. :wink:

Regards,

11

hahaha, yeah sounds like me sometimes.

12

See here

https://groups.google.com/forum/#!category-topic/beagleboard/beaglebone-black/Bl8wJo-245c

apt-get install rfkill
rfkill unblock all

But if you can get the TP-Link stick to work without Ooopsing the kernel, you’re ahead of me.

13

Thanks!

So with 2014-11-11 (v3.14.x) and just adding the "wpasupplicant" i can
now scan and attempt to connect to the one white-listed router we have
(which of course i forgot the password to).. This is using an older
Atheros AR9170..

I have a few atk9's similar to the tp-link at home, i'll try later..

Regards,

14

It would be pretty awesome if you could find and fix the issue I linked above and in this separate post as well
https://groups.google.com/forum/#!category-topic/beagleboard/beaglebone-black/e7RVYNowOEQ

And if you are adding packages into the distribution, might I suggest these as well?

  • rf-kill (kernel kills RF by default now, so probably a gotta-have)
  • wireless-tools (pretty much always needed for wireless)
  • usbutils (very useful for anything usb)
  • iw (iwconfig in wireless-tools is going away and doesn’t work with sticks like the TP-Link now)
  • atheros-firmware (nice to have because of the TP-Link’s popularity)

Thanks!

15

Just added rfkill and firmware-atheros, i was pulling a few files for
atheros, but now the debian packaged version has sane versions again..

https://github.com/beagleboard/image-builder/commit/08164238f95bf7e5daa78e40df998b145d01746f

Regards,

16

Hello Robert,
I am also facing with similar problem as Altaf faced. I run command “update kernel” on my BBB (debian), and now cannot access to BBB through usb cable. I tried to reinstall debian from microSD to BBB but no success. In BBB page it is stated that after flashing the eMMC, all 4 leds will lit solid and it will take approximately 45 minutes. But in my first try only three leds (except USER3 led) lit solid for 1 hour. After that powered down BBB but the problem remained. I thought that maybe there was a problem while downloading image and downloaded it again. In my seacond try after 2-3 minutes all leds lit solid (indicating that flashing is finished) but I waited for an hour to be sure. But no use still I cannot connect to my BBB through usb cable. I searched for my previous debian image which was installed in it before upgrading (linux 3.8.13-bone70) but could not find it.

I will be so glad of your help.
Regards,
Upol

17

Hello,
I have solved this problem. I downloaded image file from this link http://elinux.org/Beagleboard:BeagleBoneBlack_Debian and checked it by md5sum command whether it is downloaded successfully. But all images that I downloaded from that link gave me different md5 than expected checksum number. So I downloaded image from armhf link http://www.armhf.com/download/ and finally cheksum matched. I followed same steps stated in Installation steps to install debian wheezy 3.14 but it also did not worked. Did I did something wrong? Or does lates image of debian have a bug? At last I was able to find linux 3.8.13-bone-70, I downloaded it from this link https://rcn-ee.net/deb/jessie-armhf/v3.8.13-bone70/install-me.sh and ran it. Finally, after reboot I got my preinstalled debian version on BBB.

18

Hello,
I have solved this problem. I downloaded image file from this link http://elinux.org/Beagleboard:BeagleBoneBlack_Debian and checked it by md5sum command whether it is downloaded successfully. But all images that I downloaded from that link gave me different md5 than expected checksum number.

Odd, if you still have the files’ can you please respond with the file names and md5sums?

So I downloaded image from armhf link http://www.armhf.com/download/ and finally cheksum matched. I followed same steps stated in Installation steps to install debian wheezy 3.14 but it also did not worked. Did I did something wrong? Or does lates image of debian have a bug? At last I was able to find linux 3.8.13-bone-70, I downloaded it from this link https://rcn-ee.net/deb/jessie-armhf/v3.8.13-bone70/install-me.sh and ran it. Finally, after reboot I got my preinstalled debian version on BBB.