| debdog | example command line: | 00:02 |
|---|---|---|
| debdog | $ qemu-system-x86_64 -enable-kvm -cpu host -smp 4 -m 4096 -soundhw es1370 -hda /pub/qemu/Devuan_ASCII_Spielwiese.qcow2 -cdrom /dev/cdrom -boot c -vga virtio -netdev user,id=mynet0,net=192.168.178.0/24,dhcpstart=192.168.178.9,hostname=emu,hostfwd=tcp::55522-:22 -device e1000,netdev=mynet0 | 00:02 |
| debdog | Output: | 00:02 |
| debdog | VNC server running on ::1:5900 | 00:02 |
| debdog | I am fairly certain that exact command line worked perfectly on ASCII | 00:03 |
| debdog | I have no clue why VNC is involved | 00:04 |
| debdog | any hints appreciated! | 00:04 |
| debdog | another example, totally different: | 00:06 |
| debdog | qemu-system-i386 -m 1024 -soundhw ac97 -hda /pub/qemu/ReactOS.qcow2 -cdrom /pub/images/reactos-bootcd-0.4.15-dev-478-g9df05ba-x86-gcc-lin-rel.iso -boot d | 00:06 |
| debdog | same result: VNC server running on ::1:5900 | 00:06 |
| debdog | installed packages: https://paste.debian.net/1158375/ | 00:08 |
| ErRandir | does vncviewer at that address show anything? | 00:10 |
| ErRandir | or try running without the GUI. Add: -nographic -append console=ttyS0 | 00:11 |
| debdog | I cannot remeber tha last time I've used vnc in any way and no vnc-anything is installed on my system, AFAIK | 00:12 |
| rrq | maybe '[::1]:5900' works | 00:12 |
| debdog | $ ps -A | grep -i vnc | 00:13 |
| debdog | $ | 00:13 |
| debdog | $ qemu-system-i386 -m 1024 -soundhw ac97 -hda /pub/qemu/ReactOS.qcow2 -cdrom /pub/images/reactos-bootcd-0.4.15-dev-478-g9df05ba-x86-gcc-lin-rel.iso -boot d -nographic -append console=ttyS0 | 00:14 |
| debdog | qemu-system-i386: -append only allowed with -kernel option | 00:14 |
| debdog | it seems to work with just -nographic | 00:14 |
| rrq | btw qemu moved out the built-in graphics to qemu-system-gui | 00:15 |
| debdog | rrq: installing that package did the trick! | 00:20 |
| gnarface | ah, that makes sense, it was failing over to vnc output | 00:21 |
| debdog | I see | 00:21 |
| gnarface | it does have an option to redirect the desktop to a vnc display | 00:21 |
| gnarface | instead of a window | 00:21 |
| gnarface | it must enable by default if you don't have qemu-system-gui... good to know | 00:21 |
| debdog | [beowulf] for some time now on "apg-get update" I get: https://paste.debian.net/1158380/ | 01:00 |
| debdog | I've read, sort of, man apt-secure but I do not understand. is there a way to get rid of these messages? | 01:01 |
| debdog | sources list: https://paste.debian.net/1158381/ | 01:01 |
| debdog | *apt-get | 01:02 |
| fsmithred | debdog, run 'apt update' and you will be asked to accept it. Say yes. | 01:06 |
| gnarface | debdog: i think you need to add non-free and contrib to the other two lines of your sources.list too, if you're gonna use them | 01:07 |
| debdog | fsmithred: thanks, worked | 01:12 |
| debdog | gnarface: right, I think I've removed them for some reason. they're back there now. | 01:13 |
| debdog | thanks for noticing | 01:13 |
| ham5urg | Is it possible to log into a machine via serial+ssh? | 14:56 |
| yeti | ssh is via networl. plain serial is text. | 15:09 |
| yeti | you could run slip or ppp on a serial and then ssh over that. | 15:09 |
| Weeezy | the days of serial port communications is long gone | 15:12 |
| yeti | aaaand? | 15:13 |
| yeti | does that help to answer ham5urg? | 15:13 |
| yeti | I even keep a plip cable as srcret weapon! | 15:14 |
| yeti | .-Þ | 15:14 |
| hemimaniac | and a roll of twine and 2 soup cans? | 15:15 |
| yeti | naaaa... we do modem over that now... | 15:16 |
| hemimaniac | nice | 15:16 |
| fsmithred | right. Weeezy is relatively new here and probably doesn't know that people around here will use old stuff if they have it. | 15:16 |
| yeti | https://hackaday.com/2020/07/18/a-tin-can-modem-just-for-fun/ | 15:16 |
| hemimaniac | I still have a telephony modem going for signals over HAM | 15:17 |
| mason | ham5urg: The closest you'll get to combining serial and ssh is if you have a serial aggregator you can ssh into. | 15:17 |
| yeti | I finally found a real moden with USB... | 15:17 |
| mason | Most I've used were telnet-only, but that was decades ago. | 15:17 |
| yeti | after 2 softmodems which dont work in penguinland... | 15:18 |
| fsmithred | I want to see text-to-speech directed to a transducer connected to the wire that goes to the tin can on the receiving end | 15:18 |
| yeti | if they use a stiff cable, they should be able to do bandwidths good enough for lowend videophones | 15:19 |
| fsmithred | you're talking about tranmitting the video signal in vibrations? | 15:20 |
| hemimaniac | I'd like to see text to speech anything, seems for reasons of licensing and what not TtS is fairly behind in Linux in general | 15:20 |
| yeti | you should be able to get higher frequencies thru steel cable | 15:20 |
| ham5urg | I started to look into socat. | 16:02 |
| ham5urg | ser2net | 16:03 |
| golinux | Are we bored yet? | 16:54 |
| fsmithred | I got my excitement for the day - did laundry and emptied the mouse hotel. | 16:57 |
| paynode | does this channel +q +m +r during spam waves? i have a hard time convincing ops on other channels to allow unreg | 17:11 |
| paynode | and how bad does the spam get? sometimes there isnt an op that can react 24/7, maybe thats why they dont like it | 17:11 |
| MinceR | we used to have +q $~a | 17:39 |
| MinceR | which mutes unregistered users | 17:39 |
| paynode | MinceR: what prompted the change? unreg users asking nicely to remove it? | 18:07 |
| MinceR | not sure, but the spamming seems to have subsided | 18:11 |
| paynode | i agree | 18:15 |
| nemo | brocashelm: hey, you around today? | 21:15 |
| brocashelm | nemo: maybe | 21:38 |
| nemo | brocashelm: was curious if you have same AMD card more or less as I | 21:44 |
| nemo | brocashelm: and if you have a more elegant solution to getting AMD running than mine | 21:44 |
| nemo | 'cause it seemed we were in a similar situation | 21:44 |
| brocashelm | nemo: ah i see. i use rx 480 and rx 540 cards. i mostly just updated my configs in /usr/share/X11/xorg.conf.d/ to tweak their performances and use the non-free firmware-amd-graphics | 21:48 |
| brocashelm | i also have some legacy hd (6450 and 7450) cards and they run just fine for me | 21:49 |
| brocashelm | what issues are you having with your amd? | 21:50 |
| nemo | brocashelm: well, the thing detailed in the link I sent you | 21:53 |
| nemo | brocashelm: but... sounds like your card is actually supported | 21:53 |
| nemo | so different situation | 21:53 |
| brocashelm | yeah, amd drivers still have a way to go before it's fully foss and updates can be made quicker on linux | 22:01 |
| brocashelm | *long way | 22:01 |
| nemo | brocashelm: well in this case it seems to just be new hardware and debian being slow as usual | 22:03 |
| nemo | brocashelm: combined with AMD being kinda crappy at packaging/maintaining their own | 22:03 |
| brocashelm | yup | 22:03 |
| brocashelm | probably better to use a different distro (especially rolling release) if you want to utilize that card | 22:05 |
| nemo | brocashelm: I 'spose. I just figure devuan will eventually catch up | 22:11 |
| nemo | brocashelm: and, for living room machine wanted a relatively low-surprise distro with a lot of documentation that I still was fairly familiar with | 22:12 |
| nemo | brocashelm: the pinning is irritating, but not too much of a deviation, and I'm hoping AMD will fix their ABI level soon | 22:13 |
| brocashelm | i try to avoid pinning as much as i can. i agree that it creates a web of problems | 22:15 |
| nemo | brocashelm: I have to do it on work machines for kernel due to the malware they force us to install | 22:15 |
| nemo | I should see if that situation has changed too | 22:16 |
| brocashelm | do you have another amd card that could work with the driver? | 22:16 |
| nemo | no | 22:16 |
| brocashelm | this is the rx 550 i have that works (although my lga 775 mobo doesn't like it when i try to go into setup): https://www.novatech.co.uk/products/msi-amd-radeon-rx-550-2gb-aero-itx-oc-graphics-card/rx550aeroitx2goc.html | 22:18 |
| gnarface | nemo: did you try out the beowulf-backports kernel and firmware? | 22:21 |
| gnarface | nemo: it might also be worth trying out ceres | 22:21 |
| nemo | gnarface: um... detailed the backports tested in there | 22:22 |
| nemo | I did not try ceres, but that seemed riskier than just using an old Xorg | 22:23 |
| nemo | I did test latest bleeding edge firmware as noted that rolfie said I should try | 22:23 |
| brocashelm | i'm using ceres myself and not having any problems, but i know that it's not meant for everyday/normal use | 22:24 |
| nemo | gnarface: I'd linked you to https://m8y.org/tmp/amdgpu.html mostly in hopes you were trying similar things on a similar card ☺ | 22:24 |
| nemo | brocashelm: yeah, this is the machine everyone in family uses for play, and I was loath to be too experimental with it | 22:24 |
| brocashelm | nemo: fair enough, lol | 22:24 |
| nemo | hm. I should see if there's a new AMDGPU PRO | 22:26 |
| nemo | maybe they fixed the ABI thing | 22:26 |
| brocashelm | i'm also using vulkan drivers | 22:26 |
| brocashelm | for what it's worth, it could have been worse with nvidia | 22:27 |
| gnarface | nemo: oh sorry. i wouldn't have clicked on a unfamiliar domain but i'm not using any recent amd cards here anyway | 22:29 |
| gnarface | nemo: i wouldn't recommend replacing your main install with ceres, but i thought it would be a worthwhile test if you have a spare drive and some spare time | 22:30 |
| gnarface | nemo: (the operating hypothesis being that maybe backports kernel&firmware alone isn't enough and maybe you need newer mesa, libc, xorg, and who knows what else) | 22:31 |
| nemo | gnarface: oh. I tab completed you by mistake. I meant to say brocashelm | 22:31 |
| nemo | but. thanks for responding to the highlight anyway ☺ | 22:31 |
| gnarface | no worries, i'm still curious about support status of these cards | 22:31 |
| nemo | I'm hunting around on AMD website to try and find what the heck the latest version of their AMD GPUPRO package is anyway... | 22:31 |
| nemo | it's not something that I'm finding easy to locate | 22:32 |
| nemo | which seems to be par for course with graphics cards, drivers, and linux. or even windows. | 22:32 |
| brocashelm | sorry, i actually didn't notice the link the first time around. i appreciate bringing it up again | 22:32 |
| nemo | I keep getting release notes and not the download page | 22:32 |
| nemo | brocashelm: well we veered off into a long discussion of general AMD and systemd fail so it may have gotten lost in noise, I tried highlighting you one more time after, but you may have gone to bed or something | 22:33 |
| nemo | https://www.amd.com/en/support/kb/faq/amdgpu-installation this page for example. where are the download links? | 22:33 |
| nemo | Packages:Maintainer: Advenced Micro Devices (AMD) <slava.grigorev@amd.com> | 22:35 |
| nemo | lol | 22:35 |
| nemo | well at least I know who to email | 22:35 |
| nemo | although the typos do not inspire confidence | 22:35 |
| brocashelm | gotta get your voice heard, lol | 22:35 |
| nemo | eh. shouldn't be mean. looks like russian name. maybe that's how he mentally pronounces advanced | 22:35 |
| nemo | I have all kinds of mental transcription issues when I type | 22:36 |
| nemo | looks like they made a dropbox at some point Advanced Micro Devices (AMD) <gpudriverdevsupport@amd.com> | 22:36 |
| nemo | ok. they are up to 20.30 | 22:39 |
| nemo | so maybe I should try updating | 22:39 |
| nemo | "Introducing full support for Ubuntu 20.04.1" | 22:39 |
| nemo | "oups we forgot our Xorg ABI support" | 22:40 |
| nemo | my speculation 😉 | 22:40 |
| nemo | https://www.amd.com/en/support/kb/release-notes/rn-amdgpu-unified-linux-20-30 | 22:40 |
| nemo | hmmm they have 20.04 ubuntu and 18.04 ubuntu | 22:41 |
| nemo | I wonder which one is closest to beowulf | 22:41 |
| nemo | probably kernel is most critical concern | 22:41 |
| nemo | does anyone here happen to know which ubuntu is most likely to have a compatible kernel when installing .deb binaries? | 22:41 |
| * nemo starts researching | 22:42 | |
| nemo | looks like I used 18.04 last time actually. guess I should just keep doing that | 22:42 |
| nemo | since it worked once... | 22:42 |
| nemo | downside is the abi problem might still be there | 22:42 |
| nemo | oooh one cool change in their installer | 22:59 |
| nemo | WARNING: This package was intended to be installed on Ubuntu 18.04 and may not work as expected on Devuan GNU/Linux 3. | 22:59 |
| nemo | ♥ | 23:00 |
| nemo | no more force fix | 23:00 |
| golinux | Hahahah! | 23:00 |
| gnarface | i would have recommended against it... | 23:01 |
| nemo | gnarface: you think 20.04 is better? | 23:01 |
| gnarface | i would have recommended against using ubuntu packages | 23:02 |
| gnarface | but it might work | 23:02 |
| nemo | ah 😃 | 23:02 |
| nemo | gnarface: well it did last time | 23:02 |
| gnarface | you didn't connect to their repo, did you? | 23:02 |
| nemo | gnarface: it's more what AMD "officially" supports | 23:02 |
| gnarface | make sure not to get extra packages from their repo | 23:02 |
| nemo | gnarface: this is just the AMD driver. it sets up a file:/// repo with the packages they deliver | 23:02 |
| gnarface | make sure you didn't* | 23:02 |
| nemo | gnarface: if it effs up, their uninstaller backs them out and removes the file:/// | 23:02 |
| gnarface | probably safer then | 23:02 |
| nemo | in the closed source world support for linux, this is downright polite | 23:03 |
| gnarface | but still might make a mess | 23:03 |
| nemo | gnarface: yeah, the mess nvidia made when I used their installer I still have not fully cleaned up | 23:03 |
| nemo | I suspect I will only fully clean it up when I do a devuan reinstall | 23:03 |
| nemo | but the amd one I've backed out 3 times now without problems | 23:03 |
| nemo | welp. time to remove the pin | 23:04 |
| nemo | if it fails to launch X, back it goes! | 23:04 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!