You are not logged in.
Quick note to inform those interested LMG has their channels back. Source of the issue was a "prepped" PDF opened by an unsuspecting team member who happened to have some session cookies the scammers were able to steal and exploit.
LTT video explaining more:
https://www.youtube.com/watch?v=yGXaAWbzl5A
HTH!
Quick note:
https://linustechtips.com/announcement/ … ls-hacked/
For those unfamiliar with LMG, it's a 100+staff Vancouver (Can) based media-house that operates popular YT channels like LTT. Somehow scammers have gained access to the YT accounts of several channels LMG operates and are now actively promoting crypto-scams. DO NOT fall for these scams, crypto is essentially dead (as it should be, IMO).
This thread is not about how popular Linus is or how much you loath him for whatever reason. If that's your only contribution to this thread, please don't. In any case, normal forum rules still apply, so be civil.
I see some problems with that. Primary, you're creating an archive of packages, not necessarily suitable for installation. The Debian DVD's are, at least DVD 1. Then, as you mentioned, you're missing the main and contrib sections (which, IMO, can easily be solved by replacing the non-free in the path to {main,contrib,non-free} so the script goes through all 3). I don't see a way to determine the size of the image in relation to the (optical) media available/requested so prepping it for anything else then a DVD is not gonna work, for now. These might be future updates though, I dunno what you have in the pipeline here
Sure, but don't blame me for being upfront/frank on it
Yes, true, agreed. But spreading FUD like in the OP (the EU is making a law and it's the death of FOSS) is something the FOSS community should stay well away from.
Just me tuppence folks!
The EU does NOT make LAW, they issue a DIRECTIVE. It's then up to individual member states to implement these directives into their own national laws. This means the directive is open for interpretation by local lawmakers and will be implemented differently between each member state.
Clearly, a directive that impedes on privacy as much as is implied here is bound to end up in the EU Court system (in Luxembourg, IIRC) with a serious chance of being thrown out at least partially, perhaps even in entirety. We'll have to await those verdicts to understand its true impact on the world of FOSS.
The AM2+ platform is about a decade old now, so I'm not surprised if your hardware is indeed on its way out. You may want to research upgrading your system to AM4, even if AM5 has launched. AM4 is relatively cheap (especially against AM5 and current gen Intel stuff) and I'd recommend a B450 mainboard, a 3000 series GPU and 2x 16GB DDR4 RAM, while reusing the GPU, case and PSU. Alternatively, obtain a R5 4600G APU and leave the GPU out, it has better video output anyway. Your existing SATA drives will still work, but the average AM4 mainboard only has 4 SATA ports, so it's wise to invest in a 1TB NVMe drive (those are now below 100USD as well as <100€) for the OS. In fact, I just purchased a 2TB NVMe drive (Chinese, of course) for just over 110€. More the adequate space for your regular desktop and you can use any HDD's from your current system for backups.
As for the logs: they repeat the same stuff several times. But you didn't include the lshw output. And store these files as text (.txt), the .log is pretty much useless (they're text files anyway, so why not designate them as such)
HTH!
I did try the sed command, before the unset ones.
I used quotes, cuz that's what the kernel said
Now we're getting somewhere! The last code block gave an error:
Major Version 7
Minor Version 3
Build Number 0003
Build Date Jul 21 2020
Build Time 11:15:07
OS Type 3
OS Major Version 5
OS Minor Version 10
OS Build Version 0
OS Patch Version 0
Crash Signal 11
Crash Time 1672858758
Up Time 0.483592Stacktrace from glibc:
/opt/google/earth/pro/libgoogleearth_pro.so(+0x1a733a)[0x7f5f72e2333a]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x13140)[0x7f5f7345d140]
/opt/google/earth/pro/libge_cache.so(_ZN5earth5cache12LdbDiskCache9ReadEntryERK10QByteArrayPS2_+0x103)[0x7f5f5e5df363]
/opt/google/earth/pro/libge_cache.so(_ZN5earth5cache12CacheManager7ReadJob5DoRunEv+0xb2)[0x7f5f5e5db9d2]
/opt/google/earth/pro/libge_cache.so(_ZN5earth5cache12CacheManager10ManagerJob3RunEv+0xa)[0x7f5f5e5db8ea]
/opt/google/earth/pro/libbase.so(_ZN5earth12WorkerThread14ProcessNextJobEv+0x7b)[0x7f5f6d3cd4eb]
/opt/google/earth/pro/libbase.so(_ZN5earth12WorkerThread17SpawnFuncInternalEv+0x47)[0x7f5f6d3cd447]
/opt/google/earth/pro/libbase.so(_ZN5earth12WorkerThread9SpawnFuncEPS0_+0x6)[0x7f5f6d3cd336]
/opt/google/earth/pro/libbase.so(_ZN5earth10ThreadInfo16ThreadEntryPointEPv+0x1f)[0x7f5f6d3c70af]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7ea7)[0x7f5f73451ea7]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f5f7322da2f]
Helpful?
The program starts just fine, but apparently can't connect to certain parts it needs as it's basically stuck and unresponsive. I have to force-close it, which leads to the lock remaining in place, which I then have to remove manually. Pacman/Arch/AUR is no option for me, sorry. Unfortunately, when I launch from the cli, no errors are reported at all and it appears there's no logs either. So I'm stuck.
Possible solution would be to purge GE and all its dependencies and start again?
I happen to have Google Earth installed, first the CE, now the Pro version. But since a few weeks/months it's broken. I can launch the application just fine as root, but as normal user, it hangs/crashes. This indicates a permissions issue. It started after upgrading GE via the Google repo 2 versions ago. Upgrading to the latest version didn't help, it probably made it worse. I'm aware Google wants GE phased out and everyone using Maps instead, so they can kill GE like everything else they've launched
As it happens, I have downloaded version 7.3.3.7786-r0 (Juli 2020) but alas, installing that didn't solve the issue either. I also have version 6.something, from April 2012 (!!) but that relies on the ia32 libs.
Any ideas solving this?
you can install nginx as a standalone package, as are other server-related packages like mariadb, PHP, etc
nginx and apache can safely co-exist on the same machine, but require careful configuration to avoid competing for port access
Not used Timeshift, so can't advise you on that, but the partitioning looks OK to me.
Not using EFI. Works fine, all my systems work w/o EFI. The installer recognizes there's no EFI partition, so Grub will use a regular MBR-style install instead.
EFI mandates an M$ file system (FAT). They made sure (read as: paid sh#tloads of money) only FAT was specified in the EFI standard, so until the standard changes to allow non-M$ file systems, I refuse to use EFI.
But that's just me being old school I guess
Yeah, that'll be good. I didn't take account of EFI, as I'm not using it myself.
Is there valuable data on that LVM partition that needs saving? If not, wipe the whole lot (i.e. delete all partitions on sda).
Partition sda as follows:
sda1: 512MB for /boot
sda2: 48GB for /
sda3: 8GB for swap
sda4: remainder for /home
Partitions sda1, sda2 and sda4 need a file system, choose one from the list: ext4, jfs or btrfs. You can mix different file systems, just ensure the appropriate tool package is installed (ie.e jfsutils, btrfs has a similar package). This allows the kernel to control and check the file system.
CPU and RAM are not particularly connected to JFS, but being a journaling file system the required checks take time if you have low RAM and/or a low capacity CPU. Make sure you have the jfsutils package installed, but given you can boot eventually I think it already is.
Modprobe is usually a symlink to kmod. See if that's the case on your system:
ls -l /sbin/modprobe
The output should look like this:
lrwxrwxrwx 1 root root 9 Jan 8 2021 /sbin/modprobe -> /bin/kmod
If it doesn't, see if kmod itself is there:
ls -l /bin/kmod
That should show this:
-rwxr-xr-x 1 root root 170168 Jan 8 2021 /bin/kmod
Note that the numbers&dates shown will differ from your system, that's not important. If you don't get the first output but do get the second one, create the required symlink so modprobe will work:
ln -s /bin/kmod /sbin/modprobe
Of course, all of the above commands as root!
However, I'm beginning to wonder if you're installing in a container, like Docker, Proxmox, Unraid or similar? If so, your network connections should be done in a whole different way.
Your modprobe command probably needs to be 'sudo modprobe ...'
No, he's already root. Modprobe should already be installed, as it's a core functionality of a kernel, any kernel.
Do note that ethernet NIC's are named ethX where X is a digit, not a letter. You've written etho, not 0, in that command and yes, then it's totally expected the NIC can't be found.
Anyway, your system supports 64-bit while you're running a 32-bit OS. As stated earlier, you may want to re-install using the amd64 ISO.
From the aforementioned Ubuntu forum:
As root, obviously:
dmesg | grep e1000e
modprobe e1000e
What results does that yield?
Further down that thread there's a link to the Intel drivers site, try building it from scratch as per the instructions.
HTH!
No. I'm using JFS on all my partitions/disks and it boots pretty quickly. Having said that, I had some issues with one drive (with a JFS partition) but that turned out to be a hardware failure. Fortunately I already had anticipated said failure coming so I had saved my data to a different drive and after a last sync between them the failed drive is now out of my desktop.
In any case, I don't see the JFS warnings/issues you mentioned in your posted dmesg abstract.
For starters, post the contents of the /etc/fstab file. I'm also interested in your CPU make/model and installed RAM capacity.
The western media has completely glossed over and hidden the fact that Neo Nazi militias actually rule Ukraine, through a puppet. And when I say "Neo Nazi militias", that's precisely what I mean - i.e. fanatics who style themselves on the SS, worship Adolph Hitler and would ethnically cleanse most of Europe in a heartbeat if they had the chance.
Yeah, these fanatical Ukrainian SS-militia, worshiping Hitler and probably provoking a dirty war with your KGB-President Vladimir Putin are ruled by a puppet.
A
JEWISH
puppet
Yeah right...
In case you're wondering, you're completely contradicting yourself by your statements. Never mind, I didn't expect anything less from Russian trolls.
Some of you need need to turn off the fucking TV news / put down the biased tabloids, which only ever repeat the state sponsored narrative and start thinking for yourselves.
I already do, hence my stance on Russia, in particular your spectacularly failing president and his criminal cronies, sorry (not really!) businessmen
Russia is rotten to the core and it will be a matter of time before it crumbles.
Again.
Like it did in the 1990's. Because the cause of the rot hasn't gone: greedy criminals are still in charge, the real puppet is Putin.
And that's my final word on it.
Welcome!
Unfortunately, due to events instigated in Moscow, Russia isn't very popular right now. Nothing personal, but it seems you've chosen the wrong time for this adventure. Consider putting it on hold while the situation improves. That might be a while though.
For starters, you need to install the build-essential package. It doesn't have any code itself, but its dependencies create a complete build-environment.