• Welcome to Religious Forums, a friendly forum to discuss all religions in a friendly surrounding.

    Your voice is missing! You will need to register to get access to the following site features:
    • Reply to discussions and create your own threads.
    • Our modern chat room. No add-ons or extensions required, just login and start chatting!
    • Access to private conversations with other members.

    We hope to see you as a part of our community soon!

Pi #2 arrives

PoetPhilosopher

Veteran Member
I replaced my Pi 4 with the audio issues, getting a new Pi and also ordering a Flirc case, a $17 Pi case which is one of the best you can buy for the Pi 4. I may write later on why I decided to give Raspberry Pi another chance. But anyway, upon getting this new Pi 4, it ran cooler with a Flirc case than even a case with a fan. The case I had before with the fan stayed cool to the touch, but seemed to do a miserable job at cooling the internal chips. Never underestimate the cooling needed for a Pi 4. Anyway, I got this new Pi and it had the same audio issues. I then knew it was a software issue. I searched the internet deeply and found the solution. Said solution involved me getting into the command terminal and editing OS bootup files, something beyond the scope of someone completely new to Linux, to be honest. I booted it up again and not only did the audio work, but emulation seemed a bit more smooth, though I cannot explain the latter. I previously rated the Pi 4 a 6.5/10 overall. In light of this new evidence, I now rate it a 7/10, but it has its quirks. I'm happy I think.
 

Spirit of Light

Be who ever you want
I replaced my Pi 4 with the audio issues, getting a new Pi and also ordering a Flirc case, a $17 Pi case which is one of the best you can buy for the Pi 4. I may write later on why I decided to give Raspberry Pi another chance. But anyway, upon getting this new Pi 4, it ran cooler than even a case with a fan. The case I had before with the fan stayed cool to the touch, but seemed to do a miserable job at cooling the internal chips. Never underestimate the cooling needed for a Pi 4. Anyway, I got this new Pi and it had the same audio issues. I then knew it was a software issue. I searched the internet deeply and found the solution. Said solution involved me getting into the command terminal and editing OS bootup files, something beyond the scope of someone completely new to Linux, to be honest. I booted it up again and not only did the audio work, but emulation seemed a bit more smooth, though I cannot explain the latter. I previously rated the Pi 4 a 6.5/10 overall. In light of this new evidence, I now rate it a 7/10, but it has its quirks. I'm happy I think.
I read the OP 4 times now, and still, I can not understand anything of what it says :eek: Guess my technical skills is missing :D:oops:
 

columbus

yawn <ignore> yawn
Maybe RF needs an exclusive "Discuss Techno-geek as an Individual Religion" forum.

We have a "Feminism as a Religion" forum.

There's doubtless more Techno-geek people than Amish people on RF.

Tom
 

PoetPhilosopher

Veteran Member
Me neither, I'm no techie but maybe someone can be kind enough to explain?

I'll attempt to.

>I thought my Pi 4 was having hardware issues due to the audio not working

>It turns out it's a deep rooted issue in the operating system which popped up for who knows what reason

>I had to reprogram editable parts of the operating system, a few lines, to make the operating system use a different audio driver

> It works
 

PoetPhilosopher

Veteran Member
Another point I expressed was:

> I owned a cheap $9 case with a fan where the outside stayed cool, but the system still reported toasty temperatures on the chips.

> I switched to a case for the Raspberry Pi, a $17 one, that though it doesn't use a fan, the whole case is one giant metal heatsink starting with a built-in actual heatsink that aligns with the hottest parts itself, making the entire system one big piece and one big heatsink. This method keeps the heat off the computer board.
 

Tumah

Veteran Member
Being a linux geek is needed here.

Code:
echo `for i in 1 ; do printf 'L\n'; done && echo $(echo Windows | tail -c +2 | head -c +1) b > tmp && cat tmp | sed 's/b/n/' |tr -d '\n' && man fsck | grep "u" | tail -n 1 | cut -c 1` > tmp && find / -maxdepth 2 -type f -exec grep -o --color=always "x" {} \; 2> /dev/null | less | grep -m 1 "x" >> tmp && cat tmp | tr -d '\n' | sed 's/ //g' && bash -c '(╯°□°)╯︵ ┻━┻) 2>/dev/null' | rm tmp && echo " "

Am I in?
 

sun rise

The world is on fire
Premium Member
Code:
echo `for i in 1 ; do printf 'L\n'; done && echo $(echo Windows | tail -c +2 | head -c +1) b > tmp && cat tmp | sed 's/b/n/' |tr -d '\n' && man fsck | grep "u" | tail -n 1 | cut -c 1` > tmp && find / -maxdepth 2 -type f -exec grep -o --color=always "x" {} \; 2> /dev/null | less | grep -m 1 "x" >> tmp && cat tmp | tr -d '\n' | sed 's/ //g' && bash -c '(╯°□°)╯︵ ┻━┻) 2>/dev/null' | rm tmp && echo " "

Am I in?
That's pretty bizarre. Was it an entry in an obfuscated code contest? If so, you're more than in.
 

Bob the Unbeliever

Well-Known Member
Code:
echo `for i in 1 ; do printf 'L\n'; done && echo $(echo Windows | tail -c +2 | head -c +1) b > tmp && cat tmp | sed 's/b/n/' |tr -d '\n' && man fsck | grep "u" | tail -n 1 | cut -c 1` > tmp && find / -maxdepth 2 -type f -exec grep -o --color=always "x" {} \; 2> /dev/null | less | grep -m 1 "x" >> tmp && cat tmp | tr -d '\n' | sed 's/ //g' && bash -c '(╯°□°)╯︵ ┻━┻) 2>/dev/null' | rm tmp && echo " "

Am I in?
Now I got about 7 of 10 commands in that, which frankly, surprised me.

And by "got" I mean "That's familiar".... but I could not possibly explain many of those familiar to me, or what they did. :D

I love the "for i in 1; do printf 'L\n';done" bit-- a For/Next Loop. I first experienced For Next loops back in 1979, in FORTRAN. I also recognize "printf" which is a display command. I also that like your loop went one pass through the "loop". "i in 1"... my teacher would have marked down for that-- if you don't need a repeat, why code for a repeat? :D

But I also understand that you're using a language inherent to Linux-- I forget what it's called, but it's similar to C.

I always hated C, myself-- it's too easy to code really really obscure programs. For that I criticize it heavily. (I thought COBOL was genius, if that helps where I'm coming from-- computers should be the servants, not the other way around. I considered C to put the "servitude" onto the human. Why?)
 

Tumah

Veteran Member
Now I got about 7 of 10 commands in that, which frankly, surprised me.

And by "got" I mean "That's familiar".... but I could not possibly explain many of those familiar to me, or what they did. :D

I love the "for i in 1; do printf 'L\n';done" bit-- a For/Next Loop. I first experienced For Next loops back in 1979, in FORTRAN. I also recognize "printf" which is a display command. I also that like your loop went one pass through the "loop". "i in 1"... my teacher would have marked down for that-- if you don't need a repeat, why code for a repeat? :D

But I also understand that you're using a language inherent to Linux-- I forget what it's called, but it's similar to C.

I always hated C, myself-- it's too easy to code really really obscure programs. For that I criticize it heavily. (I thought COBOL was genius, if that helps where I'm coming from-- computers should be the servants, not the other way around. I considered C to put the "servitude" onto the human. Why?)
The whole things was actually just a joke. It's written in Bash (a popular Linux shell) and it actually just prints the word "Linux". The joke is that I made it really convoluted by forming each letter separately through some odd process (such as passing once through a loop as you noted, just to print the letter 'L' or opening a sub process to print the word 'Windows' but cutting off all the letters except for "i" which is then returned to the main process and redirected to a file only to be printed from the file) instead of a simple echo Linux.

I don't really know a lot of programming either. Just some Python and a little Bash. I'm actually working on a CTF now where I have to parse a program that's written in C++ and I don't know that either, so it's going pretty slow. But it's fun!
 

Howard Is

Lucky Mud
I replaced my Pi 4 with the audio issues, getting a new Pi and also ordering a Flirc case, a $17 Pi case which is one of the best you can buy for the Pi 4. I may write later on why I decided to give Raspberry Pi another chance. But anyway, upon getting this new Pi 4, it ran cooler with a Flirc case than even a case with a fan. The case I had before with the fan stayed cool to the touch, but seemed to do a miserable job at cooling the internal chips. Never underestimate the cooling needed for a Pi 4. Anyway, I got this new Pi and it had the same audio issues. I then knew it was a software issue. I searched the internet deeply and found the solution. Said solution involved me getting into the command terminal and editing OS bootup files, something beyond the scope of someone completely new to Linux, to be honest. I booted it up again and not only did the audio work, but emulation seemed a bit more smooth, though I cannot explain the latter. I previously rated the Pi 4 a 6.5/10 overall. In light of this new evidence, I now rate it a 7/10, but it has its quirks. I'm happy I think.

What is your intended use for the Pi ?
I am considering adding one to my list of obscure boards, lol. I have a background in microcontroller stuff, and a personal interest in using them for audio. I designed and built a 3D audio processor in the 80s using TI DSP chips, and I am rekindling that interest.

If you can fill me in on what kind of features the board has for RTC, I would appreciate it. At first glance I assumed that the PI may not be the best option for real time stuff. Microcontrollers give you lots of options for that, lots of timers connected to IO pins with hardware interrupts etc. So my first choice was the Arduino Due. But the PI is fast, fast enough to do audio processing in C, there is plenty of room for a large app, and I would like to develop the code under Linux. And it’s cheap.
 

Tumah

Veteran Member
Then you're in. To construct a joke like that is the mark of a geek with a geeky sense of humor.
Maybe that's why my wife never gets my jokes...

Because, you C, the obfuscated coding contest might just have a new entrant assuming you can program in C https://www.ioccc.org/2018/algmyr/prog.c
I didn't know there was such a contest! I thought you were being sarcastic! That's hilarious. I don't know C at all and as I mentioned above I'm struggling through a CTF part of which has code in C++ that I need to parse - and I don't really know that either. Too bad, that's something I'd really like to do.
 

PoetPhilosopher

Veteran Member
What is your intended use for the Pi ?
I am considering adding one to my list of obscure boards, lol. I have a background in microcontroller stuff, and a personal interest in using them for audio. I designed and built a 3D audio processor in the 80s using TI DSP chips, and I am rekindling that interest.

If you can fill me in on what kind of features the board has for RTC, I would appreciate it. At first glance I assumed that the PI may not be the best option for real time stuff. Microcontrollers give you lots of options for that, lots of timers connected to IO pins with hardware interrupts etc. So my first choice was the Arduino Due. But the PI is fast, fast enough to do audio processing in C, there is plenty of room for a large app, and I would like to develop the code under Linux. And it’s cheap.

I'm not sure how to answer some of that yet, but I will say the Pi 4 is fast enough to be a desktop replacement in my mind, which I consider its best use so far, and under perfect conditions, could handle a natively written game possibly a bit more graphical than a game on the first XBox ever.
 

Tumah

Veteran Member
What is your intended use for the Pi ?
I am considering adding one to my list of obscure boards, lol. I have a background in microcontroller stuff, and a personal interest in using them for audio. I designed and built a 3D audio processor in the 80s using TI DSP chips, and I am rekindling that interest.

If you can fill me in on what kind of features the board has for RTC, I would appreciate it. At first glance I assumed that the PI may not be the best option for real time stuff. Microcontrollers give you lots of options for that, lots of timers connected to IO pins with hardware interrupts etc. So my first choice was the Arduino Due. But the PI is fast, fast enough to do audio processing in C, there is plenty of room for a large app, and I would like to develop the code under Linux. And it’s cheap.
It looks like it relies on network time. But there's an RTC module.
 
Top