[02:05] Will Kubuntu's Qt get patches from KDE's patch collection? [02:35] The problem with the " dd " command is it is difficult to reformat the pendrive back to the previous state unless you know the technical knowhow and have fiddled with the linux system for quite sometime. [02:42] if you mean that you may then need to know how partitioning works, because you wrote to the full disk, deleting the previous partition table, then yes === michael_ is now known as SnorthWeast [03:00] try to reformat a pendrive formatted with dd command using STARTUP DISK CREATOR - it does show hitches. Also reformatting back to FAT32 using Partition Manager is also a bit of a nuisance as the formatted portion of the pendrive doesn't show up and the pendrive is detected as a drive hard-drive with less than the usual amount of space it actually possesses [03:02] For example - if using " dd " command on an 8 GB pendrive and 4 GB is used up for burning the ISO - then on reformatting back to original state - the pendrive is shown only as 4GB instead of 8 GB. It takes a bit of a hassle to reformat it back to the original 8 GB state [03:03] This problem is of course for a Novice user on linux [03:07] The " dd " command is a very powerful tool - and hence it should be used with caution [03:15] use sync after dd [03:17] Been there, done that [03:18] the image does not include the free space automaticly, there are tools for persistence [03:18] by design [03:20] I dont think persistence is programmed into the " dd " command per se - I may be wrong on this front [03:24] There was once a GUI for the " dd " command 2 to 3 yrs back [03:24] " guidus [03:25] https://help.ubuntu.com/community/mkusb [03:28] Is it still under development ? [03:34] v1.2 seems to be from this month [03:34] though i'm failing to find a source code repository [03:35] Can it be incorporated into the universe ? I don't like to install via ppa - though I will do if I have to... [03:37] you'd need to talk to the author on this [03:37] ๐Ÿ˜‚๐Ÿ˜‚ [03:39] I last saw a note on this when the author had approached the debain group for incorporation - debian denied it citing this https://www.debian.org/releases/stable/amd64/ch04s03.en.html [03:39] Sorry - debian [03:42] there is https://code.launchpad.net/mkusb - which looks pretty dead [03:44] I think the author gave up on this after the note from debian group [03:46] I had used the program before ( Graphical User Interface for " dd " ) and it was good [03:48] these builds are recent https://launchpad.net/~mkusb/+archive/ubuntu/unstable https://launchpad.net/~mkusb/+archive/ubuntu/ppa/+packages [03:56] It's easier to reformat the pendrive back to FAT32 state using the guidus tool [03:59] Just be sure which drive the person doing this is doing - don't do on sda - the primary hard drive where the OS is installed === Hash is now known as EnchanterTim === EnchanterTim is now known as HAsh === HAsh is now known as Hash [09:05] 0A6T === stoned is now known as EnchanterTim === jordan is now known as Alabalistic === mmebsd is now known as linsux [12:49] Hi folks === Hash is now known as OpenSores [14:17] Hello? [14:28] ๐Ÿคš Hi [14:43] Hello everyone ๐Ÿ‘‹ [14:45] hi telegram users ๐Ÿ™‚ [16:17] * alkisg waves from matrix :D === Roey is now known as CountDeMonet === CountDeMonet is now known as CountDeMoney [20:20] hello all [20:21] so i dd'd a boot iso to an SD card, tried rebooting my laptop, and get "OS not found" from the BIOS, after which it loads the normal os from hD [20:21] I want it to boot form the flash stick [20:34] Try this command: [20:34] sudo dd bs=64M if=/path/to/file.iso of=/dev/sdX status=progress oflag=sync && sync === jerome is now known as jerome159 [21:42] Someone know, how to change default file manager in 20.04 other than in the settings? [22:03] CountDeMoney: many computers actually cannot boot from sd cards [22:04] try a usb stick instead [22:04] ok [22:04] yeah it is a usb stick, I meant. [22:05] and it's set in BIOS to boot from USB first [22:05] it just says 'OS missing' or something liket hat. [22:05] no os found [22:08] perhaps the OS must actually be installed on the US [22:08] USB [22:09] not just have the ISO [22:09] CountDeMoney: okay then it's really a problem with how you wrote the iso t the usb stick, i guess [22:10] *to the [22:13] hmnm okay [22:14] tomreyn: so the first time, I tried with usb-creator-kde [22:14] and the second time, I issued simply "dd if=kubuntu-21.10.iso of=/dev/sdb" [22:16] CountDeMoney: either should normally if (a) the iso was downloaded properly and not currpt - have you verified this? - and (b) it was then properly written to the usb stick - have you verified this? - and (c) the bios is set (or overriden) to boot from usb [22:16] ok [22:16] (c) is set this way, I verified it. [22:16] I can check the hash against the one on the web site... [22:16] brb [22:16] for dd it also matters whether you're in the right directory, where the iso file is, and whether sdb is the correct target [22:18] I mean i suppose I can see if that deice has partitions [22:18] device*( [22:21] that doesn't mean that it has all the correct data on it [22:21] nor that it's bootable [22:24] ok [22:25] what if I try with a different usb stick? [22:40] CountDeMoney: then your chances of it working are the same. you should read up above again if you forgot what you should do to make this work. summary: verify iso checksum against download server, verify data written to usb stick against iso. [23:02] ok [23:03] well does usb-creator-kde do this for me? [23:03] i.e. can it verify checksum? [23:04] hsash* === sysadmin is now known as VlanX [23:09] I've been using an old laptop with an AMD Ryzen 5 2500U. I'm having extreme instability with the OS. Disabling C6 did not do much. I often have a completely unresponsive system with black screens with a multi-monitor setup. Does anyone have a solution that they can recommend me? [23:12] Ecto1: any clues in the kernel log [23:15] 21.10 broke the nvidia driver for me. [23:15] ubuntu-drivers devices [23:15] == /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0 == [23:15] modalias : pci:v000010DEd00001292sv000017AAsd0000502Abc03sc02i00 [23:15] vendor : NVIDIA Corporation [23:15] model : GK208M [GeForce GT 740M] [23:17] The kernel log is quite large. Is there anything specific I should filter for? [23:29] As a matter in fact the kernal log is 15,000 lines (0)_(0) [23:39] Hash: hello, Mr. Omnipresent :) [23:43] CountDeMoney: no, it does not [23:44] balena etcher can verify the data written, does so by default [23:44] Ecto1: check since last reboot. "journalctl -k -e" (that restricts to errors) [23:44] but it#s a 250 MB download, i think [23:47] bauchhaus: some of what you posted was cut off irc because you were muted (on irc, only 1 line shold be pasted at a time, otherwise please use a pastebin service - but i'm aware you posted this on telegram, where other guidelines may apply). anyways, if you're using the default kubuntu kernel on 21.10 the i recommend to file a bug: [23:47] !bug | bauchhaus [23:47] bauchhaus: If you find a bug in Ubuntu or any of its official !flavors, please report it using the command ยซ ubuntu-bug ยป - See https://help.ubuntu.com/community/ReportingBugs for other ways to report bugs. [23:48] TJ- https://pastebin.com/rEkZr9Fd [23:48] Ecto1: journalctl -b | grep DMI: will tell your mainboard and bios version [23:49] SAMSUNG ELECTRONICS CO., LTD. 550XTA/550XTZ/NP550XTA-K01US, BIOS P05REJ.060.181217.FL 12/17/2018 [23:50] i bet there#s a newer one to fix these pcie errors [23:53] Here are the hardware errors I found from the kernel log https://pastebin.com/0P08yfvd [23:57] i was wrong, no bios updates since 2018 from samsung [23:58] Here is everything found in the log for amdgpu https://pastebin.com/xs7aCNUN [23:58] There seems to be a lot of retry page faults lurking about