index
previous
2024-04-27    
18:03:04 <ted-ious> Xenguy: I guess?
18:03:39 <Xenguy> You are tedious, take to offtopic please
18:04:37 <ted-ious> I'm only tedious when my irc client loses its connection and I have to put the - back in.

20:32:42 <darwin> tried installing Devuan 6 on a PC with Radeon RX Vega 64 and 2560x1600 monitor but the screen is all garbled (was working fine before)
20:33:00 <darwin> do medium resolutions not work?
20:35:05 <al1r4d> hmm, i dont have experience on that, sorry
20:55:27 <darwin> should I try Devuan 5?
20:57:36 <al1r4d> maybe driver issues(?)
20:59:17 <ted-ious> Isn't devuan 6 many months before it's finished?
21:06:17 <brocashelm> a whole year plus a few months at the earliest

21:55:50 <darwin> same happened on Devuan 5. The first screen displays fine, but as soon as I choose install it goes garbled
21:57:27 <ted-ious> Which installer are you using?
22:04:32 <darwin> devuan_daedalus_5.0.1_amd64_desktop.iso
22:05:06 <darwin> image linked at http://dev1galaxy.org/viewtopic.php?pid=49732#p49732
22:06:40 <darwin> the image seems to have disappeared from imgur.com ... where should I upload instead?
22:18:44 <ted-ious> darwin: Try this. https://envs.sh
22:19:23 <ted-ious> And have you booted a live image yet to make sure your video card works?
22:19:35 <darwin> it does
22:19:37 <darwin> the first screen is fine
22:19:42 <darwin> the second screen gets garbled
22:19:53 <darwin> same happened on another PC with a different new video card and different monitor
22:21:03 <darwin> it's been happening since at least Devuan 4. Someone said it's because of old kernel display drivers
22:21:12 <darwin> previously ran other OS fine but those have more problems than Devuan
22:26:50 <ted-ious> What first and second screen do you mean?
22:27:09 <ted-ious> I don't think the live image has more than one screen.
22:32:13 <darwin> of course it does
22:32:44 <darwin> the first screen shows several/many options including at least three choices of installation type (standard, expert, another type) and more options
22:32:55 <darwin> i just pressed enter which went to the next screen
22:33:39 <darwin> the first screen is blue and white. The next probably has some red
22:49:27 <ted-ious> That sounds like the installer not the live image.
22:52:28 <darwin> i said I was installing
22:53:35 <n4dir> did you try a live image?
22:53:43 <n4dir> as in: too.
22:55:18 <CueXXIII> darwin: sounds like your video card has problems with linux, what card are you using?
22:55:31 <darwin> no, it doesn't; works fine on all other GNU/Linux
22:55:40 <rrq> darwin: that first screen is part of bootloading; the second is the first one brought up by the kernel
22:55:40 <darwin> a Radeon RX Vega 64
22:56:00 <rrq> you may need to instead press TAB on the first screen and then used a different vga= setting
22:56:40 <rrq> ... before pressing ENTER to start the installation
22:56:47 <darwin> i see
23:09:42 <darwin> thanks; now able to install
23:11:24 <CueXXIII> oh, there is a vga=788 per default in the boot line from grub, i guess you should remove that; and maybe remove the nomodeset, too
23:16:09 <CueXXIII> seems vga=788 means 800x600 at 16 bit, i think newer graphic cards might no longer support that legacy mode
23:30:25 <rrq> just to be really detail picky: the installer uses syslinux and not grub
23:31:25 <rrq> (mostly because grub doesn't offer boot menu help pages)
23:40:33 <darwin> why not make default 'vga=ask'?
23:46:53 <rrq> I guess so far most installations have worked fine with the current default so there hasn't been a need to make the installation process more complex
23:49:30 <ted-ious> darwin: vga=ask was removed from the kernel years ago.
23:49:57 <ted-ious> I keep hoping they'll put it back in but I don't know what it would take.
23:51:17 <darwin> it's not removed
23:51:29 <darwin> i used it to install
23:54:00 <ted-ious> Oh they finally did put it back in?
23:54:25 <ted-ious> Wow I didn't think that would ever happen.
23:55:46 <onefang> The problem with vga=ask is there's sooo many modes listed for modern cards that most of them scroll off the screen. So you need to know the mode you want anyway, unless you get lucky.
23:55:48 <darwin> i've used it every year since about 1997 or '8
23:56:40 <onefang> I used it last year with a recent kernel.
23:58:16 <ted-ious> https://unix.stackexchange.com/questions/92817/what-happened-to-vga-ask-in-newer-kernels
23:59:51 <ted-ious> It has been replaced with video= which requires resolutions instead. https://www.kernel.org/doc/Documentation/fb/modedb.txt
---------- 2024-04-28 ----------
00:00:19 <ted-ious> Maybe debian has patches to add it back in?

00:02:49 <CueXXIII> still the devuan installer specifies vga=788 for the kernel…
00:03:16 <rrq> (and nomodeset)
00:03:24 <CueXXIII> which is a 16bit mode - https://pendrivelinux.com/vga-boot-modes-to-set-screen-resolution/
00:05:32 <CueXXIII> debian 12.5.0 netinstall does so, too
00:29:13 <darwin> i doubt it's patched--Slackware isn't but always worked
00:30:35 <darwin> how can I install OpenCL ( to work like on repo.radeon.com/amdgpu-install/6.1/ubuntu )? I know some Debian users did a certain way?
00:38:02 <CueXXIII> darwin: no idea if it works, but you could try the ubuntu install instructions
00:38:33 <CueXXIII> https://rocm.docs.amd.com/projects/install-on-linux/en/latest/how-to/native-install/ubuntu.html

01:11:12 <darwin> even I know you can't just follow those

01:47:00 <darwin> i could tell you why but it's also a lot more complicate than what I know
02:14:52 <darwin> never used CD but it keeps saying 'Media change: please insert the disc labeled 'Devuan GNU/Linux 5.0.1 daedalus amd64 - desktop 20230914' in the drive '/media/cdrom/' and press [Enter]'
02:32:29 <rrq> I think it easier to mount the CD manually and then use it with file:///path in sources.list ... (I've never had any luck with cdrom://)
02:34:40 <rrq> iirr the cdrom variant requires a good fstab setup as well so it's messier
02:40:44 <darwin> i did except linked it to /media/cdrom but it keeps asking me when in the middle of files
02:41:03 <darwin> the ISO
02:41:17 <rrq> check sources.list to make sure the cdrom entry is commented out
02:41:32 <CueXXIII> do you have multiple cdrom: entires in /etc/apt/sources.list(.d/) ?
02:45:17 <darwin> okay, but now it said: E: The repository 'file:/dcd daedalus Release' is not signed.
02:45:47 <darwin> i didn't use a CD
02:56:36 <darwin> i got that working now, but still not OpenCL
03:04:01 <darwin> what you left out is you have to say '[trusted=yes]'
03:16:45 <rrq> ta
03:22:49 <rrq> which package(s) are you looking for?

04:34:16 <dvbst> hello! is the update from devuan 4 to 5 100% seemless or is there a possibility that something might not work? should i back up my system?

05:11:15 <joerg> you should always backup your system

08:54:41 <archdummy> How to get grub-btrfs displaying near each snapshot what pre/post package apt was installing, as a comment? (As on arch)
08:55:37 <archdummy> It seems that on debian and all, the grub only comments "apt" without any additional info on the CLI that was used...
08:56:38 <archdummy> See screenshots here https://github.com/david-cortes/snapper-in-debian-guide
08:57:32 <archdummy> https://github.com/david-cortes/snapper-in-debian-guide?tab=readme-ov-file#debian-with-automated-snapper-rollbacks

09:53:51 <archdummy> Any spac-pac equivalent for apt?
09:59:02 <archdummy> Any snap-pac * equivalent for apt?

11:10:46 <toinou> test

12:20:46 <plasma41> archdummy: This source file https://sources.debian.org/src/snapper/0.10.6-1.1/debian/80snapper/ looks to be the one responsible for creating snapshots before and after an apt operation. It would probably need to be editted to be able to do what you want.
12:33:06 <plasma41> archdummy: Thanks for the link to that guide. I'll stash it away for my personal use later.
12:38:36 <plasma41> Also, I haven't checked in a while, but at one point the Debian maintainer for snapper had disabled the package's cron jobs as a workaround to some issue, expecting users to be able to rely on using systemd timers instead. That obviously won't work on Devuan. One of my back burner-ed projects is to get the cron jobs fixed and reintroduced into the Debian package.
12:53:43 <golinux> archdummy: FYI . . . http://deb.devuan.org/bannedpackages.txt

14:42:55 <archdummy> plasma41: Damn,
14:43:39 <archdummy> golinux: y'all are strong enough to quote me the codeline o-o
14:44:10 <archdummy> I'm not skilled enough, but if y'all know someone who could do it, here is the snap-pac repo https://github.com/wesbarnett/snap-pac
14:44:44 <archdummy> I can't tell for sure but I suspect it's the missing piece for getting detailed comments on grub screen / when issuing ~ snapper ls

15:58:02 <archdummy> Why a broadcom wifi card has NO issues detecting networks when booting on debian live iso, but after proceeding to the install, it won't detect nothing?
16:20:17 <joerg> firmware?
16:34:06 <plasma41> archdummy: I've cloned both of those repositories to my local system. I'll take a look at them whenever I find time to set up snapper on my machine.
17:00:33 <integfred> Thunar file manager doesn't copy files using the GUI to external media properly. Copying by GUI results in file corruption. You can test this with cmp comman
17:00:41 <integfred> Using a different file manager (spacefm-gtk3) works for the time being
17:01:21 <integfred> It's important as I just ripped a computer apart trying to find the source of corruption
17:01:58 <integfred> Pretty severe
17:07:44 <ted-ious> integfred: What filesystem are you using?
17:07:50 <integfred> ext4
17:07:58 <ted-ious> On both?
17:08:09 <integfred> yes, I used a 6GB file to test
17:08:27 <integfred> copying by CLI was fine and copying using spacefm was fine
17:08:32 <integfred> but NOT Thunar
17:08:39 <ted-ious> What kind of file?
17:09:01 <integfred> I tried an ISO originally, then I dded some random stuff to a file to try that as well
17:09:25 <integfred> It only happens with external media
17:09:34 <ted-ious> And you're testing for corruption with something like sha*sum?
17:09:39 <integfred> cmp
17:09:49 <ted-ious> Oh right.
17:09:49 <integfred> I'm testing one file against the other with cmp
17:10:01 <integfred> but shasum would work too
17:10:23 <ted-ious> Ok let's see if we can devise a test that will determine the nature of the corruption.
17:10:38 <integfred> I also mentioned this on xfce IRC just now
17:11:14 <integfred> dd if=/dev/urandom of=somefile bs=1M count=6000
17:11:20 <integfred> copy the file via gui
17:11:23 <integfred> then
17:11:39 <integfred> cmp somefile /path/to/externalmedia/somefile
17:11:50 <ted-ious> Does it corrupt with just one small file?
17:12:00 <integfred> I haven't tried one small file
17:12:07 <integfred> but it's possible
17:12:32 <integfred> I was getting corruptions because I wrote a script to check for silent corruption
17:12:35 <ted-ious> I would try making a simple script to do larger and larger files until the cmp fails.
17:12:48 <ted-ious> That's good.
17:13:07 <integfred> https://github.com/publicsite/consistencyChecker
17:13:26 <ted-ious> I started using archive file formats for copying files around for the same reason.
17:13:59 <ted-ious> Or else creating a md5sum file and comparing it on the other end.
17:14:25 <ted-ious> 7z and tarlz are really good for this.
17:14:36 <integfred> i'm in the process of trying to make it use CRC-24 sum, converted to base64 (which is 4 bytes) and using a 4 byte CRC per 4KB
17:15:08 <ted-ious> You could just use tarlz and it will do all the checksums internally for you.
17:15:20 <integfred> yeah, i don't want the compression
17:15:37 <ted-ious> That just needs a -0. :)
17:16:20 <ted-ious> Although you can get minor compression for free with -3 since your cpu will be bored waiting for the usb and wants to do something more than twiddle its thumbs. :)
17:18:16 <integfred> yeah ... I have slight paranoia haha
17:19:00 <ted-ious> Trying to avoid any possible corruption?
17:19:12 <ted-ious> I respect such paranoia. :)
17:19:25 <ted-ious> You should read about tarlz then.
17:21:01 <ted-ious> I think it's the only foss archive format with compression that can both detect corrupt bits and recover from bad blocks.
17:21:27 <integfred> actually i was part way through writing recovery too
17:21:50 <integfred> but this is not in the git yet
17:21:55 <ted-ious> Have you looked at par2 yet?
17:22:38 <ted-ious> There's supposed to be a par3 in development but it will take years before everybody is satisfied and trusts it as much as par2.
17:23:49 <integfred> I have never tried par2, I guess what I'm after is similar
17:24:02 <integfred> but part of the fun for me is to try and reinvent the wheel :)
17:24:50 <ted-ious> Don't let me stop you then. :)
17:27:06 <ted-ious> Does your script do things that rsync -c doesn't?
17:37:05 <integfred> i don't know what rsync -c does
17:54:22 <ted-ious> It forces rsync to compare every file instead of just looking at the date and time.
17:59:24 <integfred> the script I wrote in the git at the moment, as it stands, basically does that (compare every file in 2 different directories against each other). I am working on the other things I mentioned like CRC check and recovery to replace the cmp aspect to clarify. I am doing quite a bit of the work in C, but I haven't uploaded that bit yet.
2024-04-28    
search in #devuan logs:
index
next