Jump to content

Ruediger

Members
  • Posts

    17
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. After realizing that I'm obviously very bad at understanding the way they count for DD, I got the image copied to a smaller card without the filesystem being corrupted or anything else. I am now back on a 64GB Card instead of the last current 128GB card, so, yay! I should be able to clean up the system and discard trash, and then I maybe even can get back to a 32GB card. So: Thank you @usual userand @NicoD! Now I still have a question left. I compared the old boot.ini of my system and then copied the one from a current image into its place. The major change there was the addition of this sequence: # Show what uboot default fdtfile is echo "U-boot default fdtfile: ${fdtfile}" echo "Current variant: ${variant}" # there is a mismatch between u-boot and kernel in the n2-plus/n2_plus DTB filename. # Also u-boot can't seem to decide between having, or not, 'amlogic/' in there. if test "${variant}" = "n2_plus"; then setenv fdtfile "amlogic/meson-g12b-odroid-n2-plus.dtb" echo "For variant ${variant}, set default fdtfile: ${fdtfile}" fi if test "${variant}" = "n2-plus"; then setenv fdtfile "amlogic/meson-g12b-odroid-n2-plus.dtb" echo "For variant ${variant} (dash version, 2021.07 or up), set default fdtfile: ${fdtfile}" fi I am admittedly confused that boot.ini and boot.cmd contain and set pretty much similar settings. I fixed the boot.cmd setting s to reflect what I found in the newer image ( a53 and a73 cores instead of references to a55 cores - I have no idea where that boot.cmd originated from ) and now hope that once the servers current business is finished and the next restart comes up, the N2+ will finally start running at its full 2.4GHz instead of a pesky 1.8GHz . Should I maybe move al lfiles obviously from older images ( simply compared to a current one ) into a folder like "OLD" as to see if maybe interference with old copnfig files stops the device from running at full speed?
  2. Well, as for the speed issue, I grabbed this: # max cpu frequency for big core, A73 in MHz unit # setenv max_freq_a73 "2004" # 2.004 GHz # setenv max_freq_a73 "1992" # 1.992 GHz # setenv max_freq_a73 "1908" # 1.908 GHz setenv max_freq_a73 "2400" # 1.8 GHz, default value # setenv max_freq_a73 "1704" # 1.704 GHz # max cpu frequency for little core, A53 in MHz unit setenv max_freq_a53 "1992" # 1.992 GHz # setenv max_freq_a53 "1896" # 1.896 GHz, default value # setenv max_freq_a53 "1704" # 1.704 GHz from a current image, as in my own older image there were just slower speeds given. So, with the newer image I thought that would work, too. However, the syste mstill runs at a mere 1908 MHz - both large and small cores. As for the image sinze: when I do dd if=/dev/sdc of=/media/backup/64gbmsd.img bs=1M I cannot write /media/backup/64gbmsd.img back to /dev/sdc with etcher because the file is larger than the drive. I have to use a larger microsd card to write it. The resulting card does boot without problems. Shrinking the partitions doesn't affect this, as the partitions are a subset of the drive. When I just do dd if=/dev/sdc1 of=/media/backup/armbian.img bs=1M the resulting img file is just 7.2GB in size, and can be written back with etcher, but the system doesn't boot from the resulting card. What I need is the trick how the armbian images do not contain empty space. Enlarging them I can do easiyl later on, thats not a issue. But I need to get the image stripped of al lthe empty space. And zipping or other compressions dont work because, on unpacking ,al lthe empty space is back and Etcher will need again a card larger than the one the image was made from - as described above.
  3. Well, it is the operating image of my Odroid-N2 that I wanted to move to my Odroid-N2+ The problem is that there's 5 years of additional services and modifications in the system, and as I am no longer a student I do not have the time needed to analyse what I did and then trying to recreate it. The DTD seems to have helped: I got ethernet working and was now able to update to Linux odroid-n2 5.10.81-meson64 #21.08.6 So, operation on the same level as on the n2 is now possible again. Updating the DTD however did not make it possible to select the 2.4GHz speed for the 4 big cores. I modified that in the boot.ini file, but the system ignores that, even after a full update to Bullseye - which worked, debian typical, like a charm. So my next question is: Where does the system actually set the CPUs speed if not in the boot.ini file? As for decreasing the partition sizes, this does not decrease the resulting image file size. When I would make a backup of only the partition, that would help. But a sole partition backup doesn't create a bootable sdcard. I suspect the uboot header isn't part of the partition, but the drive. Only when I make an image of the whole drive, can I write the image back ( each time on a larger drive, I worked my way up from a 8GB card to 128BG by now ) and have a bootable system. So far it didnt bother me, but the next size a 256GB card will get expensive and the read/write times start to get ridiculous.
  4. As I didn't find a more suitable thread to ask my bit of questions about the odroid-n2+...: 1) When I use my Buster image with 5.6 Kernel from my Odroid-N2 and plug it into the Odroid-n2+, the result is that the device starts, but has no working Ethernet. When I try to ifconfig eth0 up it never finishes. Again: Can somebody advise me what to do about that? 2) Maybe not N2 specific, but I never had that on my Banana Pi or Odroid C2: When I make a backup of my 64GB MicroSD card using DD, Etcher cant write the image back: The MicroSD card is too small by a few MB. Even a new card of the same model is reported as too small. Can somebody explain this to me? How can I strip the image of empty space to get it writable onto the card? Any help muchly appreciated!
  5. Hello! Shortform: SDCard recreated from .iso image does not boot. #### Detailed: I use an Odroid as my Minecraft server. I have a fast 32GB card in it, and a usb hdd for swap and media files. After the setup was working, and after each update, I pulled the card from the machine (after shutting down) and plugged it into my PC to make a backup: dd if=/dev/sdc bs=4M | gzip -c >/media/backup/odroid.img.gz In case I ever needed to recreate the card, I have this line to run: gunzip -c /media/backup/odroid.img.gz | dd of=/dev/sdc bs=4M /dev/sdc is a placeholder for whichever drive my USB Cardreader is appearign as. I do have a https enabled Apache webserver with some static content, a Mumble voicechat server for gaming voicechat, Dokuwiki for my occasional bouts of hobby writing and a lot of other little tidbits on the machine, such as a VPN and one of these mediaserver thingies for my TV. That is a LOT of hand crafting that went into it over the years, and I am effectively unable to recreate all the little things I added over the years, which is why a new setup is something I am scared shitless imagining. Also, I named every backup separately, so I do have a LOT of backups - my backup drive is 4TB in size and my systems run on average on a space budged of 32 to 64 GB, my home partition being rsynced to a NAS via 1GB ethernet on each shutdown. When my SDCard died after years of trusty service and I replaced it with a newer, faster card, writing the isoimage went smoothly, the ext4 partition was flawless un doing fsck on it before doing sync and then pulling the card. However, the machine doesn't start. Power LED goes on, but nothing else happens. #### The error I see - Power LED on, no Keepalive LED blinking - makes me guess the bootloader isn't - or wasn't - backed up with the method I used. However, the way I use DD I am very sure it should copy the whole drive inclusive the bootloader, grub, lilo, uboot or whatever else there might be on it. Even cloning Amiga HDDs works flawlessly with DD this way. So, assuming I am correct and the way the backup was made was correct: 1) is there a known way to get an image written to SDCard that wil lhave the odroid bootloader workable? 2) is there a trick, like creating a new SDCard from an Armbian image and then copying the /dev/sd*1 partition from the image file to the newly made sdcard, that might get the image working? 3) Which other recommendations or suggestions ( I don't know, like mounting a rewritten image and a newly made SDCard and then doing cp -a /mnt/source/* /mnt/target/ ?) that might help me get my system back to working do you people have? With kind regards, a frustrated SDCard-user (with HDDs doing DD in the manner described above works nicely since almost 20 years for me, cloning systems between machines, replacing deceased drives and so on )
  6. On another note: Are 1LED1 and 1LED2 connected anywhere? Similarly JP1: Does this connector have any defined function? Because, ideally, I'd love to give my TX6 some powerbutton to start it again after having shut it down or sent it to suspend.
  7. Sound through HDMI seems perfectly okay. I tested with a cheap HDMI Beamer and a HDMI2VGA adapter, which includes a headphone jack. The device is a TX6-H, given labelling, thus RealTek WiFi. As for display I have a Full HD display and a 1024x768 display. Both are properly recognized - if connected at boot.
  8. Well, the device is labelled as TX6-H ; 4GiB RAM / 64GiB eMMC - Wifi: RTL8822 (47822BS-10) Thats my configuration. The RTL Chip is supported by Linux, but I guess its hooked up to SPI interface where there is no autoconfig. *goes into the DTB folder to take a look*
  9. Well, it was sold as a 4GB version, but inside Armbian using "free" I only see Mem: 2993392 which is a really odd number. As I understand it from going through all pages of this thread, I can skip on WLAN - but would the Bluetooth work? hcitool dev does not yield a result, so I guess its the same as with the WLAN Module. Soothing is that I can see the mmcblk1px partitions of the in-system NAND flash. Whilst I do not plan on using that, liking the option to swap between Android and Debian, It's good to know for long term usability of the device. Overall this is an awesome build for a lovely device. Whilst running hot, it is splendid to see Youtube videos running buttersmooth and even Tinkercad running fluently inside Chrome and Firefox. It would have been lovely to be able to use the 2-antenna setup inside Linux, too. But as it is it'll be my small hardwarelab pc.
  10. Finally - FINALLY! My Tanix TX6 has arrived and its nice and smooth and shiny. Armbian works so far, using the https://yadi.sk/d/GJbDt3-FjQ-dQA/H6/Linux/20.05/20200311 Debian Desktop image. I'm very happy - but the WLAN doesnt work. Do I manually have to load the modul? What is the TX6 es wlan module? Bluetooth I haven't seen either, but assume both are on the same chip. How can I actually identify a wlan chipset - just by simply trying to load modules? For the moment I use a wlan USB dongle. 4GB Ram works and the 64GB of flash, too. Next test will be 3D capabilites.
  11. I sometimes think that there should be some ... more obvious centralized ressource pointing to the various architectures, platforms and such. Like a directory "images", and each architecture gets its own subthread ( allwinner A33 ; s905W ) there, and whenever an new installation directory is created ( like somebody swapping from yadisk to google drive, or somebody posting a new image on baidu ) a new posting is made. I admit I suck at using the search, for when I look for "s905w .img" I get dozens of results, just none pointing to images for the s905w chipset.
  12. Oh sure the H6 is a nice processor, and the Tanix is a sweet hardware!
  13. I'm happy to try, but I don't get the images from https://yadi.sk/d/DSO6euzB3ahemo/ARMBIAN/19.11.3 to boot from either USB or SDcard. And I am too timid to duke it out by flashing uBoot via Serial or how this Maskrom mode is utilized.
  14. Then I'll try with a USB-Stick, otherwise waiting for @VoidOPv feedback. If neither works, I'll maybe wait for the Allwinner H6 to become more mainstream for Armbian, or go with a S922X based board instead. I can't afford wrecking my H96 Max 4k Android installation.
  15. I have an H96 Max 4k , RK3328, 4GB RAM, 32GB ROM, Android 7.1 originally. Going over this thread I see several people ponder over the Maskrom pins and reflashing UBoot, but most don't. Do I _have_ to reflash uboot to be able to start from SD Card? Or do I _have_ to short the Maskrom pads? So far, the box doesn't start using the buster legacy image from https://yadi.sk/d/DSO6euzB3ahemo/ARMBIAN/19.11.3 . Again, most people seem to use easyb's DTB file with good results. Which, again, I do not see in the image . At least not named easyb. But I know that after poring over this thread for 6 hours I am not exactly at my best and most attentive. I don't need / want to install the Debian OS onto the internal memory when possible. I really enjoyed the purely sdcard based os on my Sunvell R96 so far, but need more ram after four years of usage. Or would I - as a rather noobish person that does not look forward banging config files into ROM using the serial port - be better advised to get myself an Allwinner H6 based box to avoid all that uboot trouble?
×
×
  • Create New...