[ LeMaker BananaPi ] USB ports seem to be DOA
Hardware Banana Pi - installed with Slackwarearm per Stuart Winter's excellent install doc.
Started with Slackwarearm -current version (Sun Oct 11 07:06:05 UTC 2015) USB working correctly, had a couple usb powered hubs externals connected. Well I decided to upgrade to Fri Nov 27 00:27:27 UTC 2015 Black Friday release! Initially I forgot to un-blacklist aaa_elflibs from /etc/slackpkg.conf so after reboot got a few complaints like GPG not working and a couple other complaints from some sbo packages. updated aaa_elflibs, recompiled the SBO packages and things seemed back to normal, although I noticed my UBSs are not working? That is they seem to not notice devices connected or removed? (watching from dmesg I see nothing) -rebooted, re-installed libusb and libusb-compat -still no activity in dmesg when devices connected or removed? Code:
rich@banana ~ $ lsusb Code:
rich@banana ~ $ sudo dmesg | tail -n 50 Wonder if it is hardware (Bpi) board related or kernel related? Any one have any suggestions to debug usb? I tried a known working USB mouse, jump-drive and couple other devices, but see no changes in dmesg. Not opposed to complete reload, but thought this is a good time to improve t/s procedure. Suggestions thoughts welcome. |
Quote:
It's also broken here but I hadn't used it with USB connected peripherals for a while so unfortunately hadn't noticed it. I can't see what the problem is immediately so if you figure out what it is, please report back. |
That makes me feel better, about it not being physical issue, I'll do the best I can and let you know if I find anything.
|
Quote:
That explains it then. I'm glad it's not just Slackware as the thought of digging around with eudev right now wasn't an enjoyable thought ;-) I'll keep an eye on what comes up and include any patches that are made. |
Just a note to any interested. With Black Friday release I have not experienced this problem on a BananaPro
|
Thanks for the update Justwantin
--- I have the original bananapi (non-pro version) and the USB is still non-functional. I fell like I have more questions than answers but this does not bother me in the least :) To start off I thought I ordered the (pro) but got normal version, [PCB says BP-A20 and it has the smaller row of 10 pins under the gpio] https://drive.google.com/file/d/0B-i...ew?usp=sharing When I originally loaded I had to use BananaPiPro.sdcard_latest.img.xz - NOTE the [PRO] version used. When I tried to use the non-pro I got CRC check fail. (tried a couple more times, and fresh downloads but no dice) Additionally - In step 4.0 of install doc ftp://ftp.arm.slackware.com/slackwar...L_BANANAPI.TXT I had to pick Code:
tftp ${fdt_addr} slackwarearm-current/dtb/sun7i-a20-bananapro.dtb These issues are no big deal just really ODD, so it works with pro when it is not the pro model? (confusing) (anybody else see this?) Now back to thread issue USBs out to lunch after blackfriday update, might but be a non pro-issue. -I see in this thread http://www.spinics.net/lists/arm-kernel/msg470215.html the def-config may be off in kernel upgrade. So I tried this: (directions from notes not live) ((note: -rah is local appended name)) (((change to dir where kernel source is unpacked))) Code:
Code:
cp -r arch/arm/boot/dts /boot/dtb-4.3.3-rah That's all I need to do correct? (believe the uImage and uinitrd not needed for banana..) I saw notes in bug report to modify this file: vim /home/rich/4.4.xxx_stuff/linux-4.4.xxx/arch/arm/configs/sunxi_defconfig But I think that's just if I don't do make menuconfig and hit the option myself I'll attempt and see if USB is better after this. If I blow the kernel config I'll just pull the sata drive off mount it on my other system and change the symbolic links back to original. (will report back when kernel compiles up eta 8hs) |
In kernel 4.3.3 I think it's this one:
CONFIG_REGULATOR_AXP20X is not set Needs to be 3719c3719 < CONFIG_REGULATOR_AXP20X=m (in make menuconfig: Device Drivers -> Voltage and Current Regulator Support -> X-POWERS APX20X PMIC Regulators) Let me test and I'll report back |
Thanks for the info. I was planning on installing the most recent current today but it seems that after booting the 4.3.3-armv7 kernel that my USB stick is not recognised. I did my Black Friday install from a tree on the same stick after mounting it. Happily I have not done anything to the 2.5' drive yet so I'll hold on the new install for now.
I don't know if mi problem es tu problem but I need to compile a new kernel with GPIO_SYSFS [=y] on Black Friday after I get distcc set up so I'll be interested to see how you fare. A while back I got an install up with the bananapi.dtb on my pro so maybe its possible the other way as well but you may lose some functionality. Dunno much about this arm stuff yet. :<{ Quote:
|
Quote:
|
That's really good info no wonder...
make modules is still cooking... I'll update the thread in the am. (midnight on the east coast US) Peep this https://www.kickstarter.com/projects...d-super-comput Tapped out from St Nick's visit but looks pretty good. I just like the sata port from the banana. |
ssh banana
ssh: connect to host banana port 22: No route to host Surprise Surprise, must have dropped the ball somewhere. Better hook up to the console and see whats up. --Amending above to exact commands Code:
[ 1.490882] Freeing unused kernel memory: 864K (c0902000 - c09da000) |
looks like my initrd is considerably smaller than the stock one from current
-rw-r--r-- 1 root root 8955354 Dec 27 06:53 initrd-armv7-4.3.3 -rw-r--r-- 1 root root 5012495 Jan 10 08:42 initrd-armv7-4.3.3-rah changed link back to the original initrd, thinking it will work since it's the same kernel version just one usb difference. reverted all symbolic links back, it boots up again. I think I'm not doing the initrd correctly. mkinitrd -c -k 4.3.3-armv7-rah -f ext4 -r /dev/sda2 -m mmc_core:sunxi-mmc.ko.gz:scsi_mod:libata:libahci:libahci_platform.ko.gz:ahci_sunxi:mbcache.ko.gz:jbd2:ext4.ko.gz -u -o /boot/initrd-armv7-4.3.3-rah |
Reading the vim slackwarearm-current/source/k/kernel.SlackBuild
ARMv7 and greater systems (section-- line 401) going to try a better mkinitrd |
Ok, UNCLE, compiling the kernel again, my attempt to pull just initrd is failing...
Thought I had the goods from here: slackwarearm-current/source/k/configs/armv7-initrd-bananpi But no matter I just modified the config-armv7 found here: root@banana /home/rich/public_html/Slackware/slackwarearm/slackwarearm-current/source/k/configs and ran this "arm/build armv7" from here: /home/rich/public_html/Slackware/slackwarearm/slackwarearm-current/source/k You need to grab ftp://ftp.arm.slackware.com/slackwar...1.05-arm-1.txz (and have a local copy of the tree) or maybe just k Can be adapted from these directions: http://mindplusplus.wordpress.com/20...-raspberry-pi/ |
Quote:
I need another config option introduced in Linux 4.4 which apparently makes USB work. I will be upgrading to Linux 4.4 in -current once it's mainstream. |
Neato!, good news, I was hoping for more sunxi merges though.
Code:
# gpio load i2c |
Thank you Stuart !!!
- I did get 4.3.3 compiled with CONFIG_REGULATOR_AXP20X, and as you said no help. - I had a really hard time with initrd (glad zboot is enabled on banana at least I did not have to use uinitrd and uImage) I ended up using the initrd-arm7 from /slackwarearm/slackwarearm-current/kernels/armv7 I got kernel zImage ok, pretty sure I made a DFD mistake (didn't follow directions) Suspect I need to feed root=/dev/sda2 rootfs=ext4 to initrd So I'll try again, seems like arm does not support this ? Code:
zcat /proc/config.gz | grep CONFIG_REGULATOR_AXP20X PS I realize this is not the USB fix, just practice |
Quote:
You could specify them in the initrd and omit them from u-boot, but the initrd supplied in Slackware ARM is generic and the settings it contains are relevant to the build machine on which the kernel was built, and isn't necessarily going to represent the user's environment -- hence why they are configured as kernel parameters through u-boot. Code:
zcat /proc/config.gz | grep CONFIG_REGULATOR_AXP20X |
Gotcha, thanks for the info and assistance!
|
Quote:
I'm going to upgrade to Linux 4.3.5 and set the additional options -- I'm pretty sure it'll work. Unfortunately there's a blocker on the Kirkwood platform with adopting 4.4, which I have raised a bug for: https://bugzilla.kernel.org/show_bug.cgi?id=111701 Unless that gets fixed before Slackware 14.2 is released, the kernel will be the latest 4.3 series. |
There's a lot to getting working configs. (and a couple cycles compile time)
I'll likely stick with which ever kernel comes with 14.2, but if you still have it handy can you diff this against your config-armv7-4.4.0 https://www.dropbox.com/s/azwdno36ym...-4.4.0-v3?dl=0 I have not yet figured out which options to change in 4.4.0 to get some joy on the USBs with the banana. Not critical since you always got irons in the fire ;) (I just made this by make oldconfig and trying to tweak) |
Quote:
http://armed.slackware.com/slackware...ig-armv7-4.4.1 If you look at the thread I posted, all I had to do was enable the additional regulator module. The 4.4.0 config was make oldconfig'd from the 4.3 config, with nothing to do with USB or power (as I remember) added during the make oldconfig However, in Linux 4.3 (trying to get USB working) I've added a number of modules which looked useful from a hardware PoV. What I needed was: CONFIG_PHY_SUN4I_USB and its dependencies (in order to present that in the configuration tool). The full diff between 4.3.4 and 4.3.5 is: Code:
prisere [configs] # diff -u0 /tmp/config-armv7-4.3.4 config-armv7 |
I'm uploading the 4.3.5 packages today because USB is working on the Banana Pi.
|
updated to 4.3.5
I suspect I have something wrong with my Hardware... -usb seems to still not pick anything up in dmesg. --tried connecting a jumpdrive, usbmouse, and a powered usb hub. --If things are working for you I must have a board issue... Code:
root@banana ~ $ lsusb -vvv Code:
root@banana ~ $ dmesg |
Well got back from Holiday to find my BPi has power issues and will not power up. (I'll see if I can find any bad cap's on here not sure I can fix but...)
One thing I noticed looking closely at the board I found D5 is absolutely blown. (I did have a powered hub setup here at one time) Which prompted me to look at what D5 was, found this.. http://linux-sunxi.org/LeMaker_Banana_Pi VCC-5V power failure Some users have been reporting hardware defects due to loss of VCC-5V, e.g. failure to power the USB (host) ports etc. Frequently this is related to a "D5 diode problem". The Banana Pi schematic lists this part (1N5819, SO-123) in the "VCC-5V" section, showing it feeds the VCC-5V line from the AXP209's IPSOUT. If you suspect a problem with D5, check the test points: if IPSOUT is okay and 5.0V absent, then D5 likely is the culprit. It might have blown, e.g. due to drawing too much current or using a "bad" USB hub that backpowered the Pi (when self-powered). Apparently there was even a batch of devices - first 1000 according to SinoVoip - where D5 was actually dimensioned too small. See e.g. http://forum.lemaker.org/thread-9257-1-1.html, https://google.com/search?q=diode+d5+site:lemaker.org Schematic if anyone wants: https://drive.google.com/file/d/0B-i...ew?usp=sharing |
All times are GMT -5. The time now is 01:24 PM. |