Jump to content

OscarCK

Members
  • Posts

    9
  • Joined

  • Last visited

  1. Oh I though it would only update to stable kernels since I was running mainline and hadn't enabled the "nightly builds" option. Thanks for the great work so far btw! Oscar
  2. Well it was the wrong partition I was scanning first, run a superblock backup check and couldn't find anything, and then run the same on the next one, and found something run the fsck on the correct one and it got fixed. admin@bananapim2plus:~$ sudo fsck /dev/mmcblk1p1 -f fsck from util-linux 2.29.2 e2fsck 1.43.4 (31-Jan-2017) /dev/mmcblk1p1: recovering journal Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Free blocks count wrong (1464622, counted=1464617). Fix<y>? yes Free inodes count wrong (380735, counted=380731). Fix<y>? yes /dev/mmcblk1p1: ***** FILE SYSTEM WAS MODIFIED ***** /dev/mmcblk1p1: 91621/472352 files (0.2% non-contiguous), 424007/1888624 blocks admin@bananapim2plus:~$ sudo fsck /dev/mmcblk1p1 -f fsck from util-linux 2.29.2 e2fsck 1.43.4 (31-Jan-2017) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/mmcblk1p1: 91621/472352 files (0.2% non-contiguous), 424007/1888624 blocks It now boots just just fine, should I try a new update/upgrade or should I wait for more from you, of course there isn't actually any need to update yet but all fixes are good fixes. Oscar
  3. Well going to an older kernel isn't really the problem, it's getting the setup working again, the server has a paid license that shouldn't need to changed since it is hardware based but I have already asked the guy for a new code because I did a no no with the previous installation and feel like he thinks I'm robbing him if I ask it again, even though he said no problem if I'm having problems with my board and I need a new code :-P I ran an fdisk while booted with the SD card and got the following, so it seems the mmc superblock is corrupt, unless I'm reading it wrong. login as: admin admin@192.168.1.50's password: ____ ____ _ __ __ ____ | __ ) __ _ _ __ __ _ _ __ __ _ | _ \(_) | \/ |___ \ _ | _ \ / _` | '_ \ / _` | '_ \ / _` | | |_) | | | |\/| | __) || |_ | |_) | (_| | | | | (_| | | | | (_| | | __/| | | | | |/ __/_ _| |____/ \__,_|_| |_|\__,_|_| |_|\__,_| |_| |_| |_| |_|_____||_| Welcome to ARMBIAN 5.38 stable Debian GNU/Linux 9 (stretch) 4.14.14-sunxi System load: 0.40 0.30 0.12 Up time: 2 min Memory usage: 5 % of 1000MB IP: 192.168.1.50 CPU temp: 41°C Usage of /: 8% of 15G [ 0 security updates available, 32 updates total: apt upgrade ] Last check: 2018-03-27 17:05 Last login: Tue Mar 27 17:16:13 2018 admin@bananapim2plus:~$ sudo fdisk -l Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram1: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram2: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram3: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/mmcblk0: 14.9 GiB, 15931539456 bytes, 31116288 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x0e1c69a6 Device Boot Start End Sectors Size Id Type /dev/mmcblk0p1 8192 30805119 30796928 14.7G 83 Linux Disk /dev/mmcblk1: 7.3 GiB, 7818182656 bytes, 15269888 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x07dfd210 Device Boot Start End Sectors Size Id Type /dev/mmcblk1p1 8192 15117183 15108992 7.2G 83 Linux Disk /dev/mmcblk1boot1: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mmcblk1boot0: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes admin@bananapim2plus:~$ sudo fsck /dev/mmcb1k1 -f fsck from util-linux 2.29.2 e2fsck 1.43.4 (31-Jan-2017) fsck.ext2: No such file or directory while trying to open /dev/mmcb1k1 Possibly non-existent device? admin@bananapim2plus:~$ sudo fsck /dev/mmcblk1 -f fsck from util-linux 2.29.2 e2fsck 1.43.4 (31-Jan-2017) ext2fs_open2: Bad magic number in super-block fsck.ext2: Superblock invalid, trying backup blocks... fsck.ext2: Bad magic number in super-block while trying to open /dev/mmcblk1 The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> or e2fsck -b 32768 <device> Found a dos partition table in /dev/mmcblk1
  4. I checked for yesterdays logs but hadn't turned on logging on putty, there shouldn't be any problem with the power since I had exactly the same things connected, the only thing drawing current through the M2+ is an Arduino Mega2560 which doesn't have any load its just running logic level stuff, I also tried booting without it connected but the same thing happens, it is running from a Meanwell 5V 3A industrial DIN power supply, I checked the power and it is stable at 5.05V the whole time, I connected an SD card with the image (5.38 mainline) I had downloaded 2 weeks ago and it boots just fine. Oh and the No Signal on the monitor stays for about a minute or two before the next boot up shows up.
  5. Hi, I was using my M2 Plus yesterday getting the 3rd USB to work, everything went well with that got it working, and if I remember correctly I also ran the Update & Upgrade through the armbian-config utility before shutting everything down, today when I got back from class with a custom PCB adapter for the 3rd USB, I connect it with the USB device, I connect the power to the board and wait for the VirtualHere server to start up and show up at my computer, when I noticed it wasn't showing up I did a ip scan and couldn't see the ip, connected a screen to the HDMI and got this on the boot up, it just cycles through the same screen. When I installed the image about 2 weeks ago and also ran the script to install it to the emmc, so it is not running from an SD card. I hope its just some kind of boot script that is missing a letter or something and don't have to reinstall the image, I just got the board running just fine for my project. The video is a little bit blurry but should be readable at full screen. Thanks Oscar
  6. Mainline, was just editing my topic because I found what was the problem.
  7. Hi, I searched around for any new info on the 3rd USB port (header pins next to the 40pin header) and couldn't find anything new than the 2016 post that found its existance, the rest I found was acknowledgement that the H3 has 3 real USB ports, I am trying to enable this port since it seems it isn't enabled by default even in the latest Armbian, how exactly can it be enabled, the whole script.bin change from 2016 got me confused, is it the usb3host option in armbian-config? Edit, spoke too soon, even though the info is missing actually, it was the usb3host in armbian-config>system>hardware, I had the pins the wrong way, D+ is on the outside. Also why are the usb1 usb2 option unmarked if they are actually enabled (by default), this was actually what confused me, if usb3 was actually the correct option. Thanks Oscar
  8. I bought a BananaPi M2+ a few days ago and was unable to get the Wifi to work, $ ifconfig was showing only the eth0 and lo. While searching through logs and forums and performing various driver replacements, someone had a similar problem after updating the firmware of another board and someone else when he assigned GPIO pins, I found the BPi forum post about updating the firmwares of the board using BPi-Tools and I installed a fresh image, performed apt-get update/upgrade and updated the firmware using BPi-Tools, after a reboot wlan0 appeared and I was able to connect to my network without any problem. I recommend this info is added to the guide and maybe even having the tool included in Armbian or adding the firmware update procedure to the first time boot script. The WiFi/BT chip on my board is AP6212 rev. 1648 (which is written on the last line), the board itself is rev. 1.1 and 25.2 (the first number is written just under the BPi M2 Plus text under the H3 chip and the second number just over the LAN port) The Kernel/Firmware update tool can be found here BPi Firmware update tool Hope this helps anyone with the same problem, the problem also existed in the Raspbian Jessie/Lite, Ubuntu Desktop images provided by Sinevoip in the M2+ downloads page.
  9. Hi everyone, I have just installed the latest Armbian, to a brand new Banana Pi M2+ (bought from Conrad in Europe), using the "nand-sata-install" script and performed the update/upgrade commands, but I can't get the WiFi to work, doing a ifconfig only show eth0 and lo but no wlan0, I know the WiFi is disabled by default but I thought it only needed the "ifconfig wlan0 up" command which gives me "No such device". We were trying with a friend who is more in to software development than me, like for 3 hours yesterday to make it work, tried the "modprobe bcmdhd" and got "Module bcmdhd not found", tried the git download and replacement of the ap6212 folder in the /firmware/ folder but no luck. Also, when it booted today I got mmc1: card 0001 removed mmc1: queuing unknown CIS tuple 0x80 (2 bytes) mmc1: queuing unknown CIS tuple 0x80 (3 bytes) mmc1: queuing unknown CIS tuple 0x80 (3 bytes) mmc1: queuing unknown CIS tuple 0x80 (7 bytes) mmc1: new high speed SDIO card at address 0001 bcmsdh_sdmmc: probe of mmc1:0001:2 failed with error -12 This is repeated 3-4 times and then it continues to initialize the Bluetooth and the asks for login, yesterday when I was rebooting it, it flashed the beginning of the boot sequence then the HDMI goes black and after a minute I get the login prompt, I had noticed this once before but I thought it had something to do with the microSD. Checking around the interwebs for the probe thing I found others having similar problems with WiFi on other boards and kernels, and that it has something to do with a wake up call send using a gpio pin. Is it possible that my WiFi chip is bad, should I return it and get a new one or am I missing something that is written in the bottom of someones shoe? (PS. Writing things about the bluetooth in a thread that was meant for the WiFi doesn't help much in case the answer is written somewhere here.) Thanks I have also checked the WL_HOST_WAKE pin which is an output pin and I get 3.08V from it, I do have a logic analyzer if you have any suggestion about probing the chip for a particular signal. After another half day of fiddling and trying to connect the dots from various sources I made it work by using the BPi-tools to update the firmware, it now seems to work. I'm making a new thread for Igor to see and update the Armbian build or guide.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines