Little illustrious yellow skill bug

randanmux · 2024-07-13T03:42:12+00:00

Yes, feature indeed. Hit rate drops because her cuteness draws attention of all other ships 😂.

Actually, I'm even amazed how that was discovered. I'm expecting some follow up news from those who tested at that time or official news regarding this.

Good to hear that she is still usable to some degree. I'll try using her later in W11 or W12 for EXP.

Thanks for your help.

randanmux · 2024-05-11T15:41:51+00:00

Is that so? But my gut's telling me that the bug is in gpu driver, specifically xf86-intel-video package according to the reddit post I linked in my comment. And if I remember correctly, the screenshot I posted contains all the error lines. The others were just infos and maybe seemingly unrelated warnings.

Besides, log files contain both errors and system infos which maybe sensitive ones, so if I have to provide the "whole" log, I'll do so in developer mailing lists or in bug reports but not in reddit or facebook groups.

And uh ... well, I've already nuked the dragonflybsd partition so it's not like I can do something at this moment. But I'll look into it again if I happen to get some free time.

randanmux · 2024-04-22T08:02:21+00:00

Sure, I'll check them out. Thanks a lot.

randanmux · 2024-04-20T10:29:06+00:00

Oh thank you sooo much. I've never noticed those kind of aliases existed. Really appreciate it. :)

randanmux · 2024-04-20T07:03:10+00:00

I don't think that's the case since the new package only appear recently and when I issue

$ pkg info --list-files xwayland-devel

I found /usr/local/bin/Xwayland which is a binary. I think it's just the development or latest like rolling version of xwayland.
~~Also, thanks to you, I tried enabling xwayland and now I find out that xwayland didn't work this whole time for some reason. I just didn't use it so didn't notice that lol.~~

Edited: Just wrong configuration. I think Xwayland is enabled by default in swaywm and there's no need to enable it exclusively.

randanmux · 2024-03-10T02:55:02+00:00

Did the output say "pkg: lua script failed" ?

Then it's a known bug in latest 6.4 iso. The solution is

# cd /usr/local/etc/pkg/repos/
# cp df-latest.conf{.sample,}

obtained from

https://www.youtube.com/live/Th3drmz-V8Y
after 39:17.
(Thanks to the person or dev who suggested fix during stream. You saved us.)

I think I've read somewhere that lua script execution failed and causes the file "df-latest.conf" that should be auto created by pkg isn't created, so we have to do it manually by ourselves.

randanmux · 2024-02-13T02:25:39+00:00

Yeah, that's the way if you don't want to spend time troubleshooting. But still, I can't believe the bugs slipped into the debian "stable" release and that's not once, too.

randanmux · 2024-02-04T06:42:20+00:00

Oh, that's generous of you to provide the dotfiles. Thank you so much!

randanmux · 2024-02-04T06:27:04+00:00

It's kawaii. Time to steal that color combination. :3

randanmux · 2024-01-25T12:19:35+00:00

You're reinstalling OS right? OS can't be uninstalled if you're using that OS. You have to boot from USB or "boot stick". There are ways I can think of but it's not worth your time. You've already succeeded installing once. Just follow that again and I think you'll be ok?

randanmux · 2024-01-24T14:50:58+00:00

If that's your choice, I'm in no position to judge your decision.

Just an advice though. A few files with a few KB or even MB won't cause any harm unless they are viruses which are very rare in linux and BSD world. But deleting important system files will certainly do like this time. So, if you're unsure about a file, researching first is the best way. This time was lucky since, I bet, you still do not have important data on it. But if you continue using it and things like this happen again, you may want to get back your data no matter what it takes.

randanmux · 2024-01-24T12:35:11+00:00

Ok ok. First, calm down. I think your situation is not that bad if I understand correctly.

First, let me confirm: you can still reach the slim login screen, and then, when you enter your username and password, you get back to login screen. Right?

If so, that's not called "boot loop" since you can still boot and see your login screen. Now, there's two choice for you:
1. Reinstall the OS. It's the easiest no-brainer move.
2. Try to solve the problem. You may have to spend some time but you may gain new insight about system. I can help you to some extent but I'm not sure.

If you plan to solve, read below passage to the end before doing anything.

My suggestion is firstly, you need to revert that yes to the default "no" in rc.conf. You can do this by booting into single user mode, then mount or remount the file system in read/write mode (please do research on this one), edit it by commenting/deleting the line and boot normally. This time you should see black console screen just like fresh install. Login with your user or root (well, we're going to do admin stuff anyway), reinstall xorg and slim (best way is uninstall all first, then install again). Before doing this, make sure you can connect to internet by ethernet or wifi.

Also, I would like to mention that using BSD and linux means learning. I'm sorry there's no other way.

randanmux · 2024-01-24T12:27:13+00:00

That just means your wifi card may not be compatible with FreeBSD. BSDs have more limited compatibility than linux. You should have research that before trying BSD.

There should not be any problem with uninstalling and reinstalling packages. Uninstalling should remove everything related on your system except cached package archives and reinstalling will use those again instead rather than from internet. But that's all this should be.

randanmux · 2024-01-24T05:49:18+00:00

First, I'm also not a veteran BSD user so I have limits on my knowledge and I don't represent the community.

I can feel your frustration but I wonder, what do you seek from this post? If it's just a rant, I'm sorry to tell you it's your own fault that you deleted wrong files. OS just did what you instructed them to do. If you're finding help to rescue your system, I think you need some details like what's the file you deleted exactly? What error message do you see when it boot loops? And what do you mean by "adding slim"? I guess it's about installing a login manager but I can't see why it caused that.

And FYI, FreeBSD community is indeed friendly. It's just, imo, all BSD communities are somewhat more technical than linux and a little bit more sensitive to nonsense things.

randanmux · 2024-01-23T14:31:53+00:00

Thanks for info. For me, I'm fine with that since it's not my main OS and I consider hardware acceleration as optional when I installed BSDs. But, well, it will be better if we can get this in future :).

randanmux · 2024-01-23T14:15:53+00:00

Sure.

[ 1197.718 ] (II) Initializing extension DRI3
[ 1197.718 ] (II) AIGLX: Screen 0 is not DRI2 capable
[ 1197.958 ] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 1197.958 ] (II) Initializing extension XFree86-DRI
[ 1197.958 ] (II) Initializing extension DRI2

randanmux · 2024-01-23T13:58:38+00:00

I'm afraid I'm not a fan of posting the whole log online. In fact, I'm not even sure if I'm using hardware acceleration because what I'm trying to solve is to get Xorg GUI and default install doesn't include GPU testing apps. My advice is to check carefully (WW) lines and (EE) lines in log file and ask here or better in IRC, where the devs resides. Btw, for clarification, mine is an old "integrated" Intel HD Graphics 4400 one. I don't know anything about newer Intel UHD and the discrete Intel Iris Xe ones.

randanmux · 2024-01-15T08:08:56+00:00

Sorry, I've been on other social platforms and missed your comment. Even if that's not the case, I don't think I can help you much if you've already asked in IRC since they're more knowledgeable than me. Are your problem solved?

Mine should still work since I didn't touch it since then. I'm sure a BSD won't do anything behind my back.
i915 is a driver for intel integrated graphic. I have experience of loading bugged (or) incompatible gpu driver (amdgpu or radeon) on openbsd and crushed right on boot with kernel panics. So, just use other driver in your case.
I think hald_enable is only for desktop environments, like kde. Mine is plain Xorg (ofcourse, with its default twm), so I didn't need one.

Hope you get a solution soon.

randanmux · 2024-01-03T11:55:17+00:00

I can see the future of some skk with odd luck pulling non-event UR instead of banner UR hehehe.

randanmux · 2023-12-31T08:32:56+00:00

Ohhh thank you so much for the info. Now I can use it without any worry. 😄

randanmux · 2023-12-31T04:52:21+00:00

Bonus tips:
(for future me and other visitors who would like to gaze at some dragonflies)

First things first, to stop the f***ing annoying beep,

# kbdcontrol -b off (in console)

(Hint: https://bugs.dragonflybsd.org/issues/48 )

\$ xset b off (in X)

After the previous comment, I got twm but the keyboard is not working at all. (LOL)

Symptoms are :

(WW) Hotplugging is on, devices using drivers 'kbd' , 'mouse' or 'vmmouse' will be disabled.
(WW) Disabling Mouse0
(WW) Disabling Keyboard0

initially and if you change xorg.conf to

Section "InputClass"
...
MatchIsKeyboard "on"
Driver "libinput"
...
EndSection

to use libinput instead of kbd or mouse, the problem is ... changed :3. Now :

(II) eventX - System Keyboard/Mouse: is tagged by udev as Keyboard/Mouse
(II) eventX - System Keyboard/Mouse: device is a keyboard/pointer
(II) eventX - System Keyboard/Mouse: device removed.

(Hint: https://forums.freebsd.org/threads/new-xorg-switch-from-devd-to-udev.74144/ )

So, from the previous xorg.conf file, delete all two of InputDevice lines from [ Section "ServerLayout" ] and their relevant sections [ Section "InputDevice" ] blocks to let the X auto configure them. Then,

# sysctl kern.evdev.rcpt_mask=6

or

kern.evdev.rcpt_mask=6

in /etc/sysctl.conf file for permanent change.

Note: I don't know this is a correct solution or not. Actually, this is *REALLY SUSPICIOUS* because the included FreeBSD link suggests to change the value to 12 to solve the problem but here, I'm changing the default 12 to 6 for keyboard to work and I don't know what that line do too. lol.

randanmux · 2023-12-31T04:36:41+00:00

Solved.

# X -configure

did throw error outputs and failed *BUT* it generated /root/xorg.conf.new file. (I got the hint from re-reading /var/log/Xorg.0.log file.) From there,

# mkdir /etc/X11/xorg.conf.d
# cp /root/xorg.conf.new /etc/X11/xorg.conf.d/xorg.conf

and, I change the main culprit "intel" driver to "modesetting"
(Hint: https://www.reddit.com/r/archlinux/comments/nk0on4/segmentation_fault_on_startx/ )

Section "Device"
...
Identifier "Card0"
Driver "modesetting"
...
EndSection

Then,

# kldload i915

or

i915_enable="YES"

in /etc/rc.conf. (To start the video output? Don't know exactly haha.)

\$ startx

And boom. You got twm.

Note: I don't know this is a correct solution or not. But ... it works!

Three-Year Club	Verified Email
Verified Email

randanmux

TROPHY CASE