Jump to content

MCredbear

Members
  • Posts

    18
  • Joined

  • Last visited

Posts posted by MCredbear

  1. At first, the card was recognized as a Mass Storage, I used usb_modeswitch to make it recognized as a wifi card, but iwconfig still didn't show this card, and /sys/kernel/debug/ieee80211 did exist, but was empty. I don't think it's a driver issue because when I plugged this card into my debian laptop, it worked even without usb_modeswitch. journalctl and lsusb logs are in the files.

    journalctl.log lsusb.log

  2. 4 hours ago, Daniel Will said:

    Hey there... I'm just a quiet co reader who burns to get into this. Be aware, I'm a linux-noob! 

    Well I have a so called leelbox 4k 4gb / 64gb, Rk3328 (I just opened it and there's also a big "T9" on the sticker on the board) , 4 cores, arm v8a 64bit, stock Android 8.1 (so damn boring). Since a few days I browsed the net and found not a lot, but here a few and there a little bit. (surely don't mean the rock chips... 😴) For about 1 ½ days now I'm only here in the armbian forum, struggle a little with Linux language (as a lazy androidian) and I'm just wow blown away, by what these crazy freaks with God-like skills, jmcc, balbes & mates, promise to pimp this little box just by using its skills properly. Well it took me a good while to decide, which box to choose for downloading the buster desktop that's recommended for flashing. Because no box fits perfectly to mine. I struggled between M1, P1 and even Z28 pro, because it really does not really match to one of them. What's your opinion? (It would be a honor to me if I would be allowed to send some photos for better understanding). And perhaps you soon will have one more device in this 'list of pre-choice'. Well I just organized a sdcard and in a few hours we'll see if it's a Z28 or not, when I might have to make it naked again for short curcuiting😉. I love your enthusiasm and engagement in this, you "kerneling romaniacs". 

    One more question please: if this will work for me, I have an clean Linux surface and optional kodi. And all the awesome kodi goodies pre-installed and ready to go. I hope I got this right. Now my question, as I mainly use this box for IPTV(using Android apps) and testing around Modded apps(also Android). I mean: is this Linux surface, that I soon will have, a good/acceptable/possible/not-too-bad base  for something like an android Rom (or let it be an emu, even better:change roms without fucking with the kernel...) 

    Thanks for listening and for feedback! 

    YOU ARE AWSOME, developers!!

    All the best wishes from Germany ✌🏽👍🏼😎

     

    I can't find any information about your board from the search engine from my country,if you could provide your SoC model,maybe it helps.But,I don't think such an unknown device can run Linux properly.

  3. 3 minutes ago, JMCC said:

    It's strange, that it only has the filesystem error the first time. Did you use it for a while? Normally, the error appears after some intensive I/O, like using the desktop for a while (e.g.: browsing with Chromium), or installing a big number of packages through APT.

    Maybe,I run touch as soon as the desktop was just prepared.

  4. 1 hour ago, JMCC said:

    That is what we want to do. And that is the reason why I asked you to do the tests above. So if you can please make these tests and post here the results, we can move on to debugging and fixing the problem. If you want to help, please perform the tests indicated in this post: 

     

    ummm,though I can't understand why rock64's and station M1's images still need be tested while renegade's image is already works(?),I will do these test later.Also,I tried install 5.x kernel on the image with 4.x kernel,still couldn't display.But,I run it through chroot and updated system diagnosis (http://ix.io/2PWu),hope that would help.

  5. 3 hours ago, MCredbear said:

    Yes,I do have emmc.So it won't destroy its filesystem when booting from emmc?I will have the try.

    Great,it works!Though kernel is still 4.x (but from armbian),everything works well.Now should we just fix the boot script for SDcard and try to make 5.x kernel usable?

  6. 13 hours ago, JMCC said:

    Also, since you seem to be using a old Rock64 image without problems, please try the new Rock64 image I linked above, and post here the results.

    Actually,I did that with the productor's partition format still on the SDcard.I used kpartx to mount the image and only flash it to root partition,and then boot with the kernel from boot partition.I'm confused about how armbian's image for this board boot with only one partition,is it because the 16MB free space before the partition?Theoretically,will it boot successfully by replacing /boot?

  7. 5 hours ago, balbes150 said:

    I don't have this hardware, so I won't claim that it's the same thing, but from the descriptions and source code for them, I can see that these models are very close.

    I had a research,actually,they are the same one.This board is producted by libre and firefly together,but I bought it from firefly's official website,there is nothing about libre or renegade on the website(also this board is called roc-rk3328-cc on this website).And this board's image is only listed in libre's download page,so......

  8. 20 hours ago, JMCC said:

    As @balbes150 pointed out, your model is the Renegade, that is the commercial nickname. You should download a Renegade buster legacy desktop image.

    I tried that,but the image with 4.x kernel and desktop have something wrong with its boot script(a wrongly filesystem fix),which destroy its filesystem everytime when it's booting and I don't know how to edit it.And the other one with 5.x kernel but no desktop,after I installed xserver-xorg-core or xserver-xorg-core-rockchip and rebooted,it stoped display through HDMI (keyboard seemed work because it reacted after I pressed NumLock)(I had installed xfce4 before I install those packages),but when I checked /var/log/message, I found no error.I also tried to copy /boot from the image with 5.x kernel to the other one, still didn't work.

  9. 28 minutes ago, JMCC said:

    That error was present only in older kernels, it is solved already. I looked at your logs, and for some reason you are using a very old kernel (4.4.194). Try this image instead: https://redirect.armbian.com/region/EU/rock64/Buster_legacy_desktop

     

    Notice that Rock64 is not offcially supported by Armbian anymore, due to issues with hardware quality and lack of compatibility between different HW revisions. So I cannot guarantee the image will work for you.

    ummm, in fact,my board isn't rock64,it's firefly's roc-rk3328-cc,which even doesn't have an armbian image,I just find a rootfs which MIGHT BE suitable to my board. 

    If it is convenient for you,could you tell me which version of kernel is suitable?I will try to build it.

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines