Sergei Steshenko

  • Content Count

  • Joined

  • Last visited

About Sergei Steshenko

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. Yes, I do use the SDcard too. As I wrote above, I didn't want to risk changing the box internal state yet again, so I decided to keep the SDcard while having the system on HDD. Is there a way to copy what I have on SDcard at the moment to a smaller SDcard ? It's a pity to have a 16GB SDcard just to host the /boot partition, i.e. a 4GB card, or even a smaller one, should suffice. Back to the issue of newer kernels. Probably 2 decades ago I compiled a Linux kernel after making small changes in TV capture card (ironically, I stopped watching TV in 2006 or so). Since with HDD the TV box is a full fledged computer, there shouldn't be a problem to compile the kernel natively. Is there a way to have multi-boot WRT to kernels ? Like on regular x86 boxes GRUB(2). Regarding the USB OTG port - in order to use it as yet another USB master port do I have to configure it somehow or just to plug the drive into it using the appropriate adapter cable ? Could you please have a look into arm-cortex-a7 'gcc' vs arm-cortex-a17 real HW issue mentioned in my previous post ?
  2. @jock, thanks for the update. At the moment I have my gig working, and the system is on HDD. Since I'm using optical SPDIF out, I'm not affected by the vertical magenta strip issue at the moment. So there is no real need for me to try a new setup at the moment - I'd rather spend time on "perfecting" my audio stuff. I mean that trying a new image would mean destroying already installed and configured stuff on HDD because of the way '' script copies data. ... Some more questions. I tried 'gcc -v' and it shows arm-cortex-a7 (or something like this - I'm writing from my desktop PC - not from the TV box), but RK3288 is of ARM-cortex-A17 kind. So, does it mean that the available 'gcc' is not fully optimized for A17, or it's a no issue ? ... I have tried 'Suspend' from XFCE menu. Though the session is terminated, I don't have a clue how to resume. Does suspend work ? If yes, how does one resumes the session ?
  3. Another issue is that apparently "Log Out" -> "Reboot" and 'sudo reboot' do not work, or, rather, do not work fully. Session is indeed terminated, the control button on the TV box lights first red and then blue - as it should, but new boot doesn't occur. Sometimes I can achieve boot by cycling the button blue -> red -> blue several times, but the easiest and quickest way is to power the whole thing off and then on.
  4. I've made some progress. The good news is that booting having the system on external HDD works. The needed for my scenario option was '1' in the '' script actually present on the SD card. I decided to ago along my original intent of booting from SD card and system on HDD - didn't want to change the TV box internal state. When '' works, it sees existing partitions and asks to what partition to copy data. When it copies data, it completely overwrites the partition, i.e. it copies data as image - not file by file. Which, by the way, means that user home directory is copied too. The script also created /etc/fstab, and even though the drive is HDD, the contents of /etc/fstab are such as if it is tailored for a flash drive. So I later edited the file to make it look like more or less normal desktop Linux PC file. Even after the system is moved to HDD, it still uses ZRAM and RAM logging - I found a couple of posts describing how to disable both. The tricky part was enabling swap partition on the HDD. And the trickiest part was realization that there should be NO entry in /etc/fstab file for swap - unlike on my desktop Linux PC. I.e. UDEV rules automatically take care of swap partitions and if there is an entry on swap in /etc/fstab it is in conflict UDEV resulting in "Dependency failed for swap" message during boot. I think Armbian documentation on '' script should be amended to explain all these issues. In my case the USB HDD is connected via a powered USB hub - otherwise there's not enough current to spin it up.
  5. "It looks to me that ALSA is quite messy" - your characterization is quite mild. The probably most fundamentally wrong thing about ALSA is that its configuration files are not debuggable. I.e. there is no way to find what is wrong, even from the point of view of syntax. At least, this was the case years ago - I got confirmation of this statement from ALSA developers. ... Regarding '' - here is the source: . The destination drive is formatted by the script. I do not see the word 'swap' in the script. Some device names are explicitly checked and adjustments are made. Which means that some adjustments might be necessary for RK3288. I will try the script - I have a drive from somebody else's Windows machine, so I'll first let the script do with it whatever it wants. I am not a shell programmer, so it's not clear to me what happens after the script is run and then the destination drive is not connected. Will the source SD card be still bootable in the sense that the whole system can start from it ? Anyway, I haven't done much configuration on the SD card. I haven't even installed updates and the media script (the main goal of the whole thing is audio anyway).
  6. "maybe you're interested in giving the sound devices the right names," - @jock, IIRC, earlier in this thread you've proposed a workaround. I haven't implemented it yet. I've been studying pulse audio in general, made some simple adjustments on my desktop PC, etc. My final goals include adding some LADSPA stuff of mine to pulse audio, so I have more things to learn. Or taking usage scenarios I might decide to dump pulse audio altogether using pure ALSA - which IIRC also allows to use LADSPA stuff.
  7. Another set of questions. I want to use an external USB drive (to be exact, an HDD with USB adapter) to host the system. I've read and if I understand correctly my best option is 3 - "boot from SD - system on SATA or USB". The perfect option would be to also boot from SATA or USB. So, do I have to partition the USB drive myself and the 'nand-sata-install' script imposes its partitioning ? When I deal with desktop/laptop Linux distros, I partition the drive myself. If 'nand-sata-install' script partitions the drive, will it be possible for me afterwards to change partitions adding, for example, swap partition ? I mean if I do not destroy data changing partitions will the whole boot mechanism find needed for booting data ?
  8. I didn't try this monitor with a regular PC - it's physically inconvenient for me to try. The monitor is a "no-name" - I got it as a present, its IR control (it was used by the original owners as TV screen) stopped working, so the original owners bought a new monitor. The good news is that when I use optical out, sound is not affected by presence/absence of the magenta stripe. And my "production" use means using optical out. "Sometimes, expecially with older (<4.20) kernels, it may happen that sound disappears even without the purple line" - appears to be that way. I.e. I have an impression that sound sometimes disappears even without the magenta stripe. With optical out it appears to be more stable. The image I'm using has a 4.19.20 kernel, i.e. a version that can be affected according to your statement. I don't official Armbian images with newer kernel exist. Anyway, is the buggy kernel driver being worked on ? Or it's a closed source part and everything depends on Rockchip ?
  9. Still no good news with 'xrabdr'. Fundamentally, my monitor supports only one mode, so other modes have no effect when I use 'xrandr'. I.e. the whole thing always reverts to default. Another strange thing happened. I was doing 'rmmod' and then 'modprobe' of several kernel module in the hope to reinitialize the and thus maybe change the system behavior. I wasn't changing any configuration file on the way. After a number of attempts sound reproduction disappeared completely - regardless of presence of the vertical magenta strip. There were no error messages during 'modprobe' operations. So, in order to restore sound I simply re-flashed the SD card - now I again have sound. Very strange.
  10. I am playing with display modes - no good news (yet ?). However, turning monitor off and then on indeed solves the problem. When X11 screen look OK after turning monitor off and on, virtual consoles (i.e. text mode) display the infamous magenta stripe.
  11. @jock thanks for the 'xrandr' suggestion - I will try it. Another observation. Using the XFCE GUI entries I tried to change the refresh rate from 60 to 30 - not changing the resolution. This screwed up X11 - it failed to start after the change. However the change also caused appearance of that infamous vertical magenta strip in text mode as Linux boots. There was no vertical magenta strip before my change. So, it seems, some X11 setting isn't quite right - because intentional changing of refresh rate causes the same defect.
  12. I have tried image and, alas, the problem with vertical magenta strip at the left display edge and resulting no sound output is still there. In a sense for me it's a deal breaker - because not only I am going to use the whole gig at home, and it's not an option to ask a non-technical person to disconnect and then to connect the HDMI cable. Besides that, unplugging and plugging HDMI cable means unnecessary contact wear. If I understand correctly, disconnecting and then connecting HDMI cable somehow re-initializes video and audio systems. So probably the same can be achieved by program means. So, what drivers one needs to unload/load and/or what scripts/daemons one needs to restart in order to achieve the same results ? I have also looked into /var/log/kern.log file, and I didn't notice any new messages resulting from unplugging and plugging again the HDMI cable, though maybe I wasn't looking too well. ... Maybe one can by program means set wrong and then again correct display resolution and this will work around the problem ? If yes, or if it's worth trying, what is the command sequence to try this ? ... Maybe somebody has a link to another Linux image which works out of the box ?
  13. Could you please provide links to info on the build ?
  14. I have read - what is "bo" in, say, "Summary of bo reference counting" - ? Is it Buffer Overlays ? Also, regarding "Decompress this archive (armsoc compiled driver against X.Org 1.19.6, works only on mainline kernels)" vs "I suggest you to start from a fresh image with mainline or dev kernel" - does it mean that for dev (not mailine) kernel one has to compile xf86-video-armsoc himself ? What are practical advantages of using xf86-video-armsoc compared to what comes out of the box ? Regarding the issues I've mentioned. I meant issues like sound devices names, for example. And IIRC somebody else was talking about IR remote control codes.