| gry | Temporary failure resolving 'deb.devuan.org' | 10:38 |
|---|---|---|
| gry | what do i do with this please? | 10:38 |
| gry | i would like to install upgrades, and a new package :-/ | 10:38 |
| gry | for some reason replacing some lan ip with 8.8.8.8 in /etc/resolv.conf works, but i'm confused why my original dns server liked many things except the deb.devuan.org ... | 10:39 |
| djph | gry: you'd need to look at your DNS server's logs / how it's retrieving entries. | 10:48 |
| gry | i have a laptop with an sd card slot, but when i insert sd card, 'dmesg' has no new entries | 10:52 |
| djph | sounds like the sdcard reader is dead | 10:52 |
| djph | or perhaps the kernel module isn't loaded | 10:53 |
| gry | i will use 8.8.8.8 nameserver for now and debug the other one later | 10:53 |
| gry | i think kernel module but i don't know which | 10:53 |
| gry | it's a new laptop, so it never was | 10:53 |
| djph | lsusb should find it, so should be "relatively" easy to go from there | 10:54 |
| Hurgotron | gry: deb.devuan.org has large answers and therefore need tcp in addition to the usual udp for DNS. Some DNS servers don't handle that correctly | 10:55 |
| gry | Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub | 10:55 |
| gry | Bus 001 Device 002: ID 8087:0aaa Intel Corp. | 10:55 |
| gry | Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub | 10:55 |
| gry | i see thanks Hurgotron | 10:55 |
| gry | i insert sd card in sd slot -> nothing happens | 10:58 |
| gry | i insert sd card into a smartphone, connect it to laptop via a usb cable -> nothing happens | 10:58 |
| gry | tried listing /dev/sd* -> no entries (expected sda for internal disk, sdb for external disk) | 11:00 |
| djph | What's the phone? | 11:00 |
| djph | also, what's the internal hdd? | 11:00 |
| gry | samsung galaxy a12 | 11:00 |
| gry | no idea what internal hdd; it's a nvme or sata, and i know it's ssd | 11:00 |
| djph | have you turned the phone on for "USB for MassStorage" or "USB MTP" or whatever their terminology is now | 11:00 |
| gry | yes | 11:00 |
| gry | brb | 11:00 |
| djph | chances are with a "new" laptop, it's nvme, so /dev/nvme* | 11:01 |
| rrq | an sdcard may come up as /dev/mmcblk... | 11:50 |
| rrq | lsblk and blkid as well as fdisk are good at finding block devices | 11:52 |
| rrq | there would be entries at /sys/class/blokc/* too | 11:52 |
| rrq | that's /sys/class/block/* | 11:52 |
| djph | I'v enot seen them as mmcblk ... maybe I don't have a spiffy enough card / reader | 11:55 |
| gry | yes, /dev/nvme* ok :-) | 11:56 |
| gry | ls /dev/ > 1.txt | 11:56 |
| gry | (unplugged smart phone) | 11:56 |
| gry | ls /dev/ > 2.txt | 11:56 |
| gry | diff 1.txt 2.txt | 11:56 |
| gry | ...... returns no difference o.o | 11:57 |
| djph | for the phone, what "USB for data transfer" option(s) do you get? | 11:57 |
| gry | found one difference after changing mdoe from 'transfering images' to 'transfering files/ android auto' | 12:02 |
| gry | new item: /dev/libmtp-1-4: symbolic link to bus/usb/001/007 | 12:02 |
| gry | yet, with 'pmount' installed, it doesn't show up in file manager (thunar) sidebar; nor in /media/gry/ | 12:02 |
| gry | kind of my first time with devuan; in debian it auto-mounted itself | 12:03 |
| gry | ~$ pmount libmtp-1-4 phone1 | 12:05 |
| gry | Error: /dev/bus/usb/001/007 is not a block device | 12:05 |
| rrq | so with debian, the card was recognized in the computer's card slot? | 12:06 |
| rrq | gry: ^ | 12:07 |
| gry | yes, with an adapter | 12:08 |
| gry | from tiny sd card to some larger sd card | 12:08 |
| gry | but yes | 12:08 |
| gry | it was another laptop also | 12:09 |
| gry | didn't try on this one | 12:09 |
| gry | plus. now i have the smartphone plugged into usb via normal usb-a or whatever it is called | 12:09 |
| rrq | forget the smartphone.. that's an mtp connection and not a block device, and probably the phone software won't export the card anyhow | 12:10 |
| rrq | did you ensure that the card sl;ot on this computer is enabled in bios? | 12:11 |
| gry | no idea | 12:12 |
| gry | moved from smartphone-over-usb to sdcard-directly, got "pmount mmcblk0p1 phone1" working ok | 12:14 |
| gry | now files are visible | 12:14 |
| rrq | yes sounds good | 12:15 |
| gry | echo "pmount mmcblk0p1 phone1" > utils-sdcard-mount.sh | 12:15 |
| gry | now i can forget about it for a while | 12:15 |
| gry | thanks for your help | 12:16 |
| devuaninstallerg | Hello. I managed to install devuan live iso yesterday with diskencryption. But I have to provide the crypt passw two times | 13:25 |
| devuaninstallerg | One for grub and again for the disc itself. | 13:25 |
| devuaninstallerg | This was with legacy | 13:26 |
| devuaninstallerg | With MBR. I think I want to try again but with gpt. Does the efi partition need to be fat32 always? | 13:28 |
| rrq | yes | 13:28 |
| devuaninstallerg | Okay. And gpt needs to use uefi? | 13:29 |
| fsmithred | you could just make a keyfile for the second partition | 13:29 |
| fsmithred | oh, it's a little more complicated if you encrypted /boot | 13:30 |
| devuaninstallerg | Okay. And that's true for gpt as well? | 13:30 |
| rrq | the second decryption is for the kernel to access the disk | 13:31 |
| fsmithred | uefi wants gpt (I think it's possible without gpt) | 13:31 |
| devuaninstallerg | I don't need to encrypt booti think | 13:31 |
| fsmithred | that's what leads to needing a grub password | 13:31 |
| rrq | old uefi implementations were limited to use gpt, but uefi standard allows dos partition table | 13:31 |
| fsmithred | and if you want gpt wiht legacy boot you need a special bios_grub partition | 13:32 |
| rrq | and most newer uefi bios allows either/both | 13:32 |
| fsmithred | if you use the live installer and want /boot to be unencrypted, you need to make sure you created a separate partition for /boot | 13:33 |
| devuaninstallerg | Okay. Thanks for clarifying things | 13:34 |
| devuaninstallerg | So, I'll try uefi with gpt separate boot with fat32 and efi. | 13:35 |
| devuaninstallerg | And encrypt the rest. | 13:35 |
| devuaninstallerg | gpt does 4096 sector size I gathered while MBR does not | 13:36 |
| rrq | not sure about that one; | 13:39 |
| devuaninstallerg | I don't know if this web chat will drop me soon but I'll return with good news I hope. | 13:40 |
| devuaninstallerg | Its a dreadful HP pro book | 13:40 |
| gry | ok | 13:42 |
| fsmithred | no not fat32 boot, | 13:47 |
| fsmithred | fat32 for efi partition, some linux filesystem for /boot | 13:48 |
| fsmithred | shit | 13:48 |
| devuaninstallerg | what is udevd specified group 'sgx' unknown? | 14:08 |
| djph | sounds like a typo in a rule | 14:20 |
| fsmithred | devuaninstallerg, you left before I posted - don't use fat32 for /boot partition, only for efi partition. They are not the same. | 14:20 |
| devuaninstallerg | I get dropped all the the | 14:21 |
| devuaninstallerg | time | 14:21 |
| fsmithred | ouch | 14:21 |
| djph | what client are you using, devuaninstallerg ? | 14:21 |
| devuaninstallerg | https://web.libera.chat/ | 14:22 |
| devuaninstallerg | I thought efi resided in /boot/efi | 14:24 |
| devuaninstallerg | https://dev1galaxy.org/viewtopic.php?id=15 I found this post | 14:26 |
| devuaninstallerg | After I came here first | 14:26 |
| fsmithred | efi partition gets mounted to /boot/efi | 14:29 |
| fsmithred | and legacy boot will work with gpt if you create a special partition. | 14:31 |
| fsmithred | At least 1MB in size, no filesystem and flag bios_grub (in gparted) or ef02 (in gdisk) | 14:31 |
| fsmithred | but I can't guarantee that it works on that HP | 14:32 |
| devuaninstallerg | Yeah, HP seems to make it harder than necessary | 14:33 |
| devuaninstallerg | But that guide I found on dev1galaxy is okay to follow or is it outdated? | 14:35 |
| fsmithred | if you have a similar model/age computer, it's probably still good | 14:36 |
| fsmithred | otherwise I would try to fix other things before renaming the bootloader to M$ | 14:36 |
| devuaninstallerg | So, this is what I want: | 14:38 |
| devuaninstallerg | GPT, non encrypted boot and the rest encrypted. | 14:39 |
| devuaninstallerg | That's all :-) | 14:39 |
| fsmithred | ok | 14:39 |
| devuaninstallerg | Its the how that seems to get in my way | 14:39 |
| fsmithred | if you boot uefi, you'll need an efi partition in addition to what you have | 14:40 |
| fsmithred | if you boot legacy you'll need a bios_grub partition in addition to what you have | 14:40 |
| fsmithred | if you think you might put the hard drive into another box that boots the opposite of whatever you decide to do, you can have both of those additional partitions, but only one will get used | 14:41 |
| fsmithred | since a lot of motherboards don't follow standards and don't do well with legacy boot, you might be better off doing uefi. YMMV | 14:42 |
| devuaninstallerg | And that efi partition goes into /boot/efi but should not be fat32? | 14:42 |
| fsmithred | backwards | 14:42 |
| devuaninstallerg | I will never put this sad anywhere else | 14:42 |
| fsmithred | efi partition is separate from boot partition | 14:42 |
| fsmithred | efi partition must be fat32 | 14:42 |
| fsmithred | the /boot partition should be a linux filesystem, probably ext2,3,4 | 14:43 |
| devuaninstallerg | Okay, so the guide is wrong. Where doi put efi partition? | 14:43 |
| fsmithred | I usually put it at the beginning | 14:43 |
| fsmithred | 120-200MB | 14:43 |
| fsmithred | is more than enough | 14:44 |
| fsmithred | you'll need more for /boot because kernels are getting a lot bigger | 14:44 |
| devuaninstallerg | In its own partition? | 14:44 |
| fsmithred | you need three partitions | 14:44 |
| fsmithred | one for efi, one for /boot and one for the OS | 14:44 |
| fsmithred | and you'll encrypt that last one | 14:45 |
| devuaninstallerg | Okay, so: /efi | 14:45 |
| fsmithred | oh, if you want swap, then there are some more choices | 14:45 |
| devuaninstallerg | /boot | 14:45 |
| fsmithred | and / | 14:46 |
| devuaninstallerg | Okay | 14:46 |
| fsmithred | are you still using the live installer or the netinstall iso? | 14:46 |
| devuaninstallerg | Swap is fine as file in root | 14:46 |
| fsmithred | cool | 14:47 |
| devuaninstallerg | Okay, I'll try this approach then :-) | 14:48 |
| devuaninstallerg | :-) | 14:48 |
| fsmithred | are you still using the live installer or the netinstall iso? | 14:48 |
| devuaninstallerg | This is the full installer | 14:48 |
| fsmithred | ok | 14:48 |
| devuaninstallerg | Net is no option because broadcom and only wifi | 14:49 |
| fsmithred | full installer meaning from the installer iso directory and not one of the live isos? | 14:50 |
| devuaninstallerg | Yes | 14:50 |
| fsmithred | ok, sounds good | 14:51 |
| devuaninstallerg | devuan_daedalus_5.0.1_amd64_desktop.iso | 14:51 |
| fsmithred | yeah, you might need to add a few things from the dvd after the base install. | 14:52 |
| fsmithred | and also will need to edit /etc/apt/sources.list after you get the network up | 14:52 |
| fsmithred | so you can install from repo instead of from dvd | 14:52 |
| devuaninstallerg | right, and to get those broadcom drivers I guess | 14:53 |
| fsmithred | they're in the iso | 14:53 |
| fsmithred | oh | 14:53 |
| devuaninstallerg | Oh, good | 14:53 |
| fsmithred | no they are not. the installer is. | 14:53 |
| fsmithred | some of the broadcoms are installable from repo. Some require network to get the actual driver. | 14:54 |
| devuaninstallerg | Okay | 14:54 |
| fsmithred | oh, and if it asks you at the beginning of the install to insert some media to supply firmware, you should ignore it unless you actually have that firmwware | 14:55 |
| fsmithred | much easier to use a wired connection first | 14:56 |
| fsmithred | if wired is not possible, then you might need to get the firmware first. Do you know which broadcom device you have? | 14:56 |
| devuaninstallerg | Right | 14:56 |
| fsmithred | I need to leave. Check the debian wiki for installing the wireless stuff. It's the same. | 14:58 |
| devuaninstallerg | I'll give /efi 120MB /boot 1 GB and the rest / | 14:58 |
| fsmithred | sounds good | 14:58 |
| devuaninstallerg | Thanks for your effort fsmithread :-) | 14:58 |
| fsmithred | yw and good luck | 14:58 |
| devuaninstallerg | I appreciate it | 14:58 |
| ximon49 | 950075a5baecd6a1800d1c980e20b448094585f18866748948a57f21884d4fd0 is this correct? | 18:20 |
| ximon49 | shasum | 18:20 |
| fsmithred | ximon49, are you asking someone in particular or just throwing that out to anyone to answer? | 18:36 |
| ximon49 | fsmithred nah just throwing it out | 18:55 |
| ximon49 | :D | 18:55 |
| ximon49 | what is the easiest way installing telegram-desktop on devuan? | 18:56 |
| debdog | download it there: https://desktop.telegram.org/ extract it, run it | 18:57 |
| fsmithred | just so you know, none of us has memorized all the sha256sums. You might want to mention exactly which iso you're talking about. | 18:57 |
| ximon49 | excalibur | 18:58 |
| fsmithred | apt install telegram-desktop | 18:58 |
| fsmithred | ^^^ that won't work in excalibur | 18:58 |
| fsmithred | the package isn't there. It's in ceres now. It will either move into excalibur in 10 days or less or it will be held for some bugs. Check debian bug tracker. | 18:59 |
| ximon49 | fsmithred isnt it smart to make a devuan testing unstable mix? | 19:27 |
| fsmithred | ximon49, yes if you know how to do pinning it's a good way to go. You have testing as the default and pull stuff from unstable if needed. Use codenames excalibur and ceres not testing and unstable. | 19:31 |
| ximon49 | nice fsmithred did the tum tutorial and it works | 20:16 |
| ximon49 | :D | 20:16 |
| ted-ious | What is the tum tutorial? | 21:23 |
| fsmithred | I have no idea. | 21:59 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!