7.6-amd64 on FW2B†
- Posted by Budlun at 2025-03-10 (Mon) 05:13:27
- Release: 7.6-amd64-202502261
- Media: USB flashdrive
- Hardware: FW2B (CPU: Intel(R) Celeron(R) CPU J3060 @ 1.60GHz, Memory: 8519704576 (8125MB))
Remarks†
#dtjsetup
2: [rox-filer]
4: [icewm]
Japanese language? y
1: [fcitx-anthy]
#exec rox -t top -p pin $wm
(ROX-Filer:23955): Gtk-WARNING **: 20:08:54.248: cannot open display
export DISPLAY=:0 (failed)
#FuguIta
- How about other Desktop Environment or Window Manager?
and do you have xenodm enabled?
#FuguIta -- kaw
- No further content. By the side, however, two daemons: Messagebus and Dnsmasq. Xenodm successfully starts IceWM. Rox-Filer does not start with Xenodm with the warning Gtk. #xhost -> unable to open display “:0”. xauth: (argv):1: Bad display name “HEMP:0” in “remove” command . #FuguIta -- Budlun
- #cat .Xauthority—-> -Empthy- #FuguIta -- Budlun
- According to the error message, it appears that the X Window authentication mechanism is denying connection to the X server.” Is the value of the DISPLAY environment variable “HEMP:0” valid? If correct, is the connection from the host named HEMP to the X server allowed? #FuguIta -- kaw
- That's what I thought last night. I started boot "0" and tried it with "Waterdrop:0". The Gtk warning with unable DISPLAY:0 can also be read with "Warerdrop:0". #FuguIta -- Budlun
- (EE) Failed to open authorization file “/root/.serverauth.XXXXX”: Permission denied #FuguIta -- Budlun
- Please try this: https://x.com/i/grok/share/wgW3xXSG9W09lhiBzJyErN1AF #FuguIta -- kaw
- That's a weird link, social media? X.org FAQ - no results #FuguIta -- Budlun
- I tried. I followed the instructions and the result was Invalid MIT-MAGIC-COOKIE-1 KEY, Xauth:(argv):1: unable to Open display ":0" #FuguIta -- Budlun
- Above link is Grok AI. Since it seems to be out of order now, please try accessing it again in a while.
By the way, Is the X server running remotely? Or is it local? Please detail your environment.
#FuguIta -- kaw
- With a little luck X.org helps me, I contacted X.org. At first I thought of FuguIta. Thanks for the help, but it's because, I think, ~/.xserverauth.XXXXXX —->X.org. #WITH MAGIC COOKIE 1 Key debug, I guess. #FuguIta -- Budlun
- I don't understand what you mean. Xorg is local? #FuguIta -- Budlun
- "X features network transparency, which means an X program running on a computer somewhere on a network (such as the Internet) can display its user interface on an X server running on some other computer on the network." Wikipedia
This is what I mean.
In any case, this is almost certainly not a problem specific to FW2B, but your configuration problem.
Anyway, without a detailed description of your environment, it is difficult to give any further advice. -- kaw
- How can I ignore Xorg? Example: IGNORE_Xauth=yes —-> ~/man.conf to start Rox-Filer? I actually just want to get to know the Rox-Filer interface and use the web browser. X.org with Window X, I don't need it, I don't understand why it takes X for it. BSD with Rox-Filer should work without the need for xorg. With FreeBSD you have the option. Either way, I'll stay with #FuguIta -- Budlun
- Can you show me how to show the missing environmental description? With Xfce I can copy the expression and post it here. It's just a little work... #FuguIta -- Budlun
- Xfce Desktop works well on my FW2B.(tested) Rox-Filer Desktop, I don‘t know why, don‘t start Desktop. #FuguIta -- Budlun
- So forth, every post has not been successful. Please leave it up here, as meaningless. #FuguIta -- Budlun
- #pkg-config —modversion gtk+-2.0 -> 2.24.33 (I try to update > 2.6.8) #FuguIta -- Budlun
- For quite a while I was satisfied with xfce, what has changed for me, xfce doesn't want to use anymore. The only option was still the Rox-Filer, unfortunately I could not implement that, because I can not use Rox, because it can not start with FuguIta with me. The whole thing has revealed to me that Xorg is not properly set up. I have never been connected to my OpenBSD with X Server and not as it should be. Local I can't change anything about it, it has to be done from the right place. So far I don't care now, because I have enough of it and the path ends there, there is nothing left for me to do, which is so for me, because the point is reached with me and everything else will not be able to beat my experience, what I still want to record, I am no longer open-minded for such a thing. At least I have my FuguIta Original, even if Xorg is turned off and an xsession only runs well with ICEwm, I can do without a mouse. It's a shame that it doesn't work out with Rox, which is not necessarily so nice now, but very clear, more like others, this chapter is over for me and I don't want to have it anymore. So a desktop environment. #FuguIta -- Budlun
- Now let us investigate from a different perspective.
- Can xterm be activated?
- Try running rox on xterm with no command line arguments. Does a filer window appear?
$ rox
- Check that the owner and group of the .Xauthority file are correct. Also, are the permissions 0600?
- If the rox filer window fails to run, try running with X Windows authorization disabled as follows What happens?
$ xhost +
$ rox
#FuguIta -- kaw
- As I said, I didn't care. But here, here you go: •Can xterm be activated? Yes | •$rox -> (ROX-Filer:70416): Gtk-Warning **: XX:XX:XX.XXX: cannot open display: |•??? |•$startx -> xterm: $xhost + -> access control disabled, clients can connect from any host $rox -> window appear: /ram/home$USER #FuguIta (???-> */.Xauthority as root: Read 0 lines as user: none .Xauthority file -- Budlun
- This is not a radical solution, but how about putting an “xhost +” line at the beginning of ~/.xsession? Also, you are running rox as a normal user, right? In addition, please show me the output of “ls -l ~/.Xauthority”.
#FuguIta -- kaw
- It's nice, but I don't want to give any information on this point. xfce continues to convince well. I just look around, if I find another browser that I used, I had to run Debug, because there was something wrong. The Rox option did appeal to me, but is not necessary now. I'm already at peace with the packages, even if the execution doesn't work, I just go to xfce, this time without xfce-extra. I just leave the thing with xorg as it is, then my Magic Cookie is invalid, but necessary for me. If you want to continue, then you can test FuguIta yourself with Rox. So: 1. xfce back 2.xorg, is it just as it is 3.other browser 4. I wish you all the best 5. The report can stay like this, because that must come from Rox. Thank you, everything as so good, again a little smarter even without having solved it, should not bother FuguIta, because sometimes it takes time to become good and I respect that. Cya #FuguIta -- Budlun
-
ROX Filer+IceWM is FuguIta's default desktop environment. I have been using this environment for many years and it is very stable in operation. Please refer to Getting Started with FuguIta to review how to install the desktop environment in #FuguIta. -- kaw
- Thx. I have come to my success. I have now been able to run the Rox-Filer connected to Xorg on my desktop environment on Icewm, with Webbrrowser of an extensive quality class. That's all I need with coreboot, leave everything on factory settings of the desktop environment until further notice. By default, no sound playback is possible for me, which is helpful. For the need I use a tablet, for information now my FW2B with this ingenious software version. Kaw, thank you for allowing me to be so free to contact you. Cya Budlun #FuguIta -- Budlun
- Congrat! I am relieved to hear that Rox Filer works! There is a lot of documentation on this site, including “Getting Started with FuguIta.” Please enjoy #FuguIta based on those information! -- kaw
- Solved: The solution was to set the value machdep.allowaperture=1 in /etc/sysctl.conf. It was in var/log/Xorg.0.log, was pretty tricky and it took me days to get it right... Duck.ai:The parameters machdep.allowaperture=1 and machdep.allowaperture=2 relate to the configuration of aperture and graphics drivers in certain operating systems, particularly in macOS and BSD-based systems. These settings control whether and how access to graphics memory (aperture) is permitted. machdep.allowaperture=1: This setting allows access to graphics memory but with certain restrictions. Some functions or applications that rely on full access to graphics memory may not work properly. machdep.allowaperture=2: This setting allows for extended access to graphics memory, meaning that more functions and applications that access graphics memory should work without restrictions. However, this setting may also lead to stability issues if not all applications or drivers are optimized for the extended access. The choice between these two settings depends on the specific requirements of the software and hardware being used. Generally, it is recommended to start with the lower setting and only switch to the higher one if necessary. #FuguIta -- budlun
- I worked it out and jumped. Made it skilled #FuguIta -- budlun
![[PukiWiki]](image/pukiwiki.png "[PukiWiki]")
myrox.png