freenode/#devuan/ Sunday, 2019-02-24

specingbefore I nuke the broken VM... is there a way for apt to repair damaged rootfs?01:10
specingi.e. does it know checksums of everything that was installed and can it re-check and reinstall?01:11
furrywolfI've seen a utility that can do that, but it was for detecting maliciously modified files.01:13
watchcattripwire01:16
specingWell, well, well01:21
specingthis is interesting01:21
specingI unmounted the VM's filesystem from the host01:21
specingbooted the VM again, ran btrfs scrub inside VM and it comes back clean. No errors01:21
specingand it is the same 4.9.x kernel series on both host and VM01:21
specing?_?01:21
specingI'll have a chat with btrfs devs01:21
fsmithredspecing, you want debsums01:33
gnarfacespecing: is it possible the volume came up for auto-fsck on boot at one point and the script just failed?  the scripts for reiserfs and xfs had been recently broken due to some boneheaded systemd related change.  mabye the btrfs one got the same treatment?06:00
gnarfaceanyway, that could explain it in theory anyway06:01
gnarface(the fix for reiserfs was to delete it and just replace the symlink that was there before)06:02
va7lnxhi gnarface06:22
gnarfacesorry, va7lnx, i had wandered away07:45
straubeHi all... someone know something about problem with bridge.ko?19:08
straubeI have problem with lxc-net19:08
straubewhen I launch I have this answer: [....] Starting LXC network bridge: :RTNETLINK answers: Operation not supported19:09
straubeFailed to setup lxc-net.  And if I try to do modprobe bridge I have this answer: modprobe: ERROR: could not insert 'bridge': Unknown symbol in module, or unknown parameter (see dmesg)19:09
straubeThis problem is same in two different server after upgrade  modprobe: ERROR: could not insert 'bridge': Unknown symbol in module, or unknown parameter (see dmesg)20:47
helios21 straube: did you actually look in dmesg as the error message told you to do?20:54
straubeof course, but dmseg do not show any message20:54
straubeI mean, anyone related20:56
helios21hmmm… that is strange21:09
va7lnxgnarface: I wandered to bed :P23:11
gnarfacehow's it all working for you now va7lnx?23:12
gnarfacei forget what your setup was, but i trust it's all ironed out now?23:12
va7lnxI have most of it worked out.23:17
va7lnxI can't seem to mount my android phone though23:17
va7lnxI can use bluetooth, so I'm not SOL23:17
gnarfacehmmm23:18
va7lnxthis computer is barely being used now. between Devuan's light footprint and the much better motherboard, I rarely break 25% RAM23:18
va7lnxI guess I'll play with VMs :)23:19
gnarfacesometimes phones need to be manually switched to some sort of "mass storage mode" to be mountable.  often they will come with windows tools that can do that somehow from the client side, but on linux you'll have to edit the phone's config first afaik23:19
va7lnxyes. I did this, but it won't mount.23:19
va7lnx not sure why. It's not really important. As I said, I can use bluetooth connectivity.23:19
gnarfacehmm.  what error does it give you?  it could be a permissions problem too23:19
va7lnxbut I would like it if I could mount over USB23:19
gnarfaceyea bluetooth is really slow23:19
gnarfaceand the tools are usually crippled23:19
gnarfaceusb mounts might not work but usually they do if the phone has a mass storage mode23:20
va7lnxno error.23:20
gnarfacehmm23:20
va7lnxit's weird.23:21
gnarfaceyou sure it didn't mount?23:21
va7lnxI don't think it even tried quite frankly23:21
gnarfaceusually silence is the expected output of a successful call to the mount command.  it might look like it didn't try23:21
gnarfaceif you run dmesg before and after plugging it in, the new lines added to the output should shed some light on the subject23:21
watchcatif the phone is rooted and android, you can use 'ums enabler' to get mass storage mode23:22
gnarfacethere's also the very real possibility that you don't have the right filesystem driver loaded, but i would expect a specific error about that23:22
va7lnxthat is possible.23:23
va7lnxyeah, there's no "errors"23:23
va7lnx[1346758.021083] usb 4-1.2: new high-speed USB device number 21 using ehci-pci23:23
va7lnx[1346758.135332] usb 4-1.2: New USB device found, idVendor=04e8, idProduct=686023:23
va7lnx[1346758.135343] usb 4-1.2: New USB device strings: Mfr=2, Product=3, SerialNumber=423:23
va7lnx[1346758.135345] usb 4-1.2: Product: SAMSUNG_Android23:23
va7lnx[1346758.135347] usb 4-1.2: Manufacturer: SAMSUNG23:23
va7lnx[1346758.135348] usb 4-1.2: SerialNumber: 98867844575258393723:23
va7lnx[1346767.270467] usb 4-1.2: USB disconnect, device number 2123:23
va7lnx[1346767.493019] usb 4-1.2: new high-speed USB device number 22 using ehci-pci23:23
va7lnx[1346767.603309] usb 4-1.2: New USB device found, idVendor=04e8, idProduct=686023:23
va7lnx[1346767.603312] usb 4-1.2: New USB device strings: Mfr=2, Product=3, SerialNumber=423:23
va7lnx[1346767.603314] usb 4-1.2: Product: SAMSUNG_Android23:23
va7lnx[1346767.603315] usb 4-1.2: Manufacturer: SAMSUNG23:23
gnarfaceyikes, use paste.debian.net for big pastes like that.  you risk getting auto-kicked by security23:24
va7lnxyeah. I just got a warning23:24
va7lnxanyhow.23:24
gnarfacethat looks like normal output from a phone being plugged in, unplugged, then part of the output of it being plugged in again23:25
va7lnxprobably when I switched modes23:26
gnarfaceit's not an unrecognized device23:26
va7lnxmaybe I need to apt-cache search for mtp23:26
KatolaZva7lnx: is that a phone?23:27
gnarfaceoh, that sounds familiar.  yea some phones might need mtp or something like that23:27
KatolaZ(sorry not looking at the backlog)23:27
va7lnxKatolaZ: yes. android lineage23:27
va7lnxthat's okay23:27
KatolaZjmtpf23:27
KatolaZjmtpfs23:27
KatolaZ(to access it as a storage device)23:27
va7lnxthat's what I'm thinking23:28
KatolaZdon't think, just do it ;)23:28
va7lnxdo I need to restart anything when I install it?23:28
KatolaZnope23:28
KatolaZyou need to run the command from cli23:29
va7lnxah. okay.23:31
va7lnxsweet! there it is!23:31
va7lnxnow to get it to do it automagically23:31
va7lnxmounted it under my home directory too23:32
KatolaZva7lnx: there was a trick with a udev rule23:34
KatolaZnever used it though23:34
KatolaZI guess the more phone-savvies here might have a hint23:34
va7lnxyeah. I'll have a look at that. at least I can do it manually23:34
KatolaZyep23:35

Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!