You are not logged in.
Hi guys!
When I check out the Synaptic Package Manager I see that both firmware-linux-nonfree 0.43 and xserver-xorg-video-radeon 1:7.5.0-1 are installed.
Hardware is RV710/M92 [Mobility Radeon HD 4530/4570/545v]
When checking out the package content of firmware-linux-nonfree 0.43 firmware for RV710 is included. So I am wondering which firmware is being used here? The 'nonfree' or xorg?
I would like it to be the xorg version, and it would have been nice to learn how it is configured on Devuan.
Thanks
It sounds like the window could be getting accidentally "shaded" via a mouse action.
As I recall, double left clicking or scrolling the scroll wheel on the window title bar causes the window to roll/up down. You could also temporarily switch to window decorations which support the shade button for a while and see how it goes.
Yes, there is no action button in the title bar but Clearlooks-Phenix-Purpy does shade with the scroll wheel and you might have accidentally done that.
Yup! You are right guys.
The first time was with both touch pad and external mouse activated at the same time and accidentally touching the touch pad. Couldn't understand what happened. I now tried vertically on the right edge of the touch pad with the mouse pointer over the title bar and there we went
To avoid confusion a 'shade' button with Clearlooks-Phenix-Purpy would be nice
.
Thank you very much for your help.
On the side. I am wondering who on the forum who are also Devuan developers? I checked the forum user list, but it does not mention.
Anyhows I would like to express my great appreciation and say thank you for the Devuan project. My first real encounter with GNU/Linux was Debian some years ago where I also tried gNewSense, but then systemd came along and all related to GNU/Linux came to a halt. So when I found out about Devuan I was very pleased. Have been monitoring the releases since alpha/beta stages and are now for the first time getting to know how it works. So then having the experience that Devuan is the most responsive system that I have ever used, has been a delightful experience. When working with different systems one get a intuitive feel for how well hardware and software works together, and Devuan gives me a very pleasant feel. As a comparison I was working with NT-networks back in the 90's and I have never been satisfied with any MS system up to and included Win10. So I hope and wish for a long and lasting life for the project ![]()
Also do you have redshift/blueshift installed?
I am not sure what 'redshift/blueshift' is, so I guess that I have not installed it/them ![]()
Is this in LXQT?
Are you running Jessie?
Which firefox do you have?
Have you upgraded recently?
Thanks for your prompt reply fungus.
It is Xfce 4.10 with Devuan Jessie 1.0.
Firefox version is 52.5 which was upgraded the day it was released I guess. Have a habit of doing a 'update/upgrade' almost every day. When you ask, I am suddenly uncertain as to how long ago the first instance was..... So it could be that both instances has been with 52.5, the first time not with 52.4
Hi guys!
I am not sure how this happens, but it has happened twice within a weeks time.
The style and wm theme is both with default Clearlooks-Phenix-Purpy.
The behaviour is just like as if a 'shade' button in the title bar was used, but as you know the Clearlooks-Phenix-Purpy theme does not have a 'shade' button.
When maximizing the 'window' the titlebar jumps up to top edge of the screen as it is supposed to do, but there is no Firefox window. It is just the desktop. When maximizing there is no grey line under the title bar.
The only solution that I have come up with is to close Firefox and start over.
Any ideas?
Thanks
...
iptables-persistent instead enshrines the path names /etc/iptables/rules.v4 and /etc/iptables/rules.v6 as being its "master files".
Thanks. Good to know ![]()
Regarding the "microHOWTO" iptables-persistent guide and just for the record, the service itself is now named 'netfilter-persistent'. Package name is still 'iptables-persistent'.
Forgot to ask about "master" file.
Over at Debian Wiki https://wiki.debian.org/iptables it says:
"...save the new rules to the master iptables file"
A bit confusing, so I have to ask; Is this some specific temporary master file read by netfilter?
Thanks a lot for your prompt reply and support ralph.ronnquist
Appreciate the iptables-persistent package. Having a service taking care of it make sense to me. Great.
although it does introduce a (confusion?) layer between the ufw rules and the actual iptables rules.
Yes, agree. To see if I could understand how ufw is working I ended up with confusion ![]()
Cheers
'update-rc.d remove' will remove the symlinks. You do not need to remove the init script. I'm not sure if the symlinks will be regererated with normal updates, but. I just checked, and wicd is still installed here and turned off since I installed the system almost two years ago.
Thanks a lot fsmithred. Then I know I can do it the way I wished for
. Appreciate it!
Hi,
A strange experience here. My better half has been using the computer for several days now and have been using the Audio Mixer volume control plug-in with no issues.
A couple of days ago I opened the Audio Mixer panel by right-clicking the volume control plug-in and pressed mute for the master volume. But when un-muting it sound did not come back, and has not come back since. Neither master nor speakers are set to mute and volume controls are on full, but no sound with either aplay testing, VLC or Firefox on youtube.
I was afraid there was a hardware failure, but starting the Devuan Live installation image the sound is just fine. Until I right-clicked and opened Audio Mixer panel again and pressing mute on the master volume. When un-muting the sound did not come back. So no hardware failure and the same issue happened with the Live image running as with the permanent installation.
Does anyone have any idea as to what is happening here? This is the first time I have ever experienced this.
Thanks
Thank you very much for your lengthy reply @ralph.ronnquist and sorry for my late follow up. I have been occupied with Wicd and Wi-Fi and thought I would try to come to a conclusion there first.
Regarding what you told me about attaching to the event of bringing up an interface, I was clearly not aware of what I was doing.
So I can focus on how to setup rules, could you please come up with a suggestion on how to do loading of rules the best way with Devuan? Just to have something running I have temporary installed gufw/ufw.
Regarding Iptables How-To's that are out there, are there any differences between a systemd system and Devuan that I need to be aware of?
Boot-up Manager is in the repo if you need an easy GUI way to disable items from startup, I use it in Vuu-do to turn off bluetooth, cups etc.
Thanks for the tip @greenjeans . Appreciate it.
Still not clear on what you're trying to achieve here.
From your second post it's clear that you have stanzas in /etc/network/interfaces for a wlan0 device and it's all configured to connect to the access point using wpa_supplicant configuration? Then you've installed wicd as well and setting that to run as a daemon? wicd won't be able to claim the wlan0 device and manage the connection as you've already configured and connected it in /etc/network/interfaces
The best way to stop wicd running on startup is to just remove the package, which will disable and remove it's rc scripts automatically.
Still not clear on what you're trying to achieve here.
Sorry about that. A personal "get to know" process on my part was revealed here ![]()
Besides of trying to get to know Wicd's behavior I was wondering how to do a manual config-file configuration.
When it comes to Wicd and/with /etc/network/interfaces I now know that the only entry allowed is the loopback interface.
Regarding wpa_supplicant stanzas I believe the configuration it self in /etc/network/interfaces was wrong by using a EPA-TLS configuration. EPA-TLS does not apply to our network ![]()
For the record I believe this configuration after disabling Wicd would be correct:
auto wlan0
iface wlan0 inet dhcp
wpa-ssid myssid
wpa-psk ccb290fd4fe6b22935cbae31449e050edd02ad44627b16ce0151668f5f53c01bManual on this page with link initially provided by you: https://wiki.debian.org/WiFi/HowToUse#W … d_WPA2-PSK
Regarding stopping Wicd from running on startup by just removing package this seems to be the way to make it completely consistent. But it does not seem very flexible. After starting using FreeBSD I have grown fond of doing manual configurations, so the first thing has been trying to learn about the capabilities of Devuan in this regard. I will check out sysv-rc-conf and Boot-up Manager too....
In Debian and Devuan (and many other derivatives), runlevels 2-5 are the same.
To disable wicd in all runlevels:
update-rc.d -f wicd removeTo reverse the above:
update-rc.d wicd defaultsAnother way to do it is to install sysv-rc-conf and un-check all runlevels on the wicd line. (use arrow keys and space bar)
Thank you @fsmithred
If I understand the manual correctly, when using the 'remove' command I have to remove the /etc/init.d script first, otherwise an error message. Do you agree?
I don't remember where, I believe I read that if using the 'disable' command instead it would stop the startup, but when a upgrade of Wicd happens, it would be overwritten and go back to default as before. I am guessing/asking if this would happen with 'remove' and removal of wicd script in /etc/init.d too. Which makes me think of maybe a complete uninstall of Wicd would be better in that regards. If ending up using wpa_supplicant that is.
Last, thank you for mentioning sysv-rc-conf and user guide ![]()
I believe that those are the defaults in most init systems to configure and make a connection, if it is not already on from the previous level, and then to logoff the network (however it is continued) before shutdown or reboot.
One of the reasons that "some" distributions are taking too long to boot and get to a login screen (console or DM) is that if it takes too long to login to network it stays in that stage till some time-limit is reached.
At least that was my experience and that is what I think.You want to disable wicd so you don't have networking until you decide to connect or to stop using wicd and use a different method? If you were to remove wicd I believe part of the procedure would be to remove it from the init system as well, as if you install something else it is probably preconfigured in some default way within the init system.
First sorry to all you guys for my late follow up, and thanks to you @fungus.
Regarding runlevels, thanks for the elaboration. Good to know.
Regarding Wicd, you are correct. Disable Wicd as a step towards trying wpa_supplicant instead.
Hello Guys,
I am wondering why the script S03wicd is located at all folders from rc2.d to rc5.d ? I have understood it as all the folders represent runlevels during boot.
Also, I am wondering how to permanently turn of the Wicd service startup?
Would for example:
update-rc.d wicd disabledisable wicd on all runlevels? Then again, would:
update-rc.d wicd enableenable on all levels? Or is this a overly complicated way of doing it? The latter meaning affecting many files.
Thanks
Thanks a lot for your additional elaboration @fungus.
And thanks a lot to the rest of you too. Appreciate the humor @greenjeans and @MiyoLinux ![]()
Appreciate getting things into perspective. I'll look into the different alternatives starting with wpa_supplicant
Thank you for your reply @fungus
Right out of the box Wicd seems kind of broken. That is, if there is no compatibility issue with the Broadcom BCM4312 adapter.
I have tried to check the 'Never connect to this network' on all the other networks but it does not make any difference.
For the record and repeating details in my initial post:
- At start no wifi networks appear in the Wicd networks window
- Pressing 'Refresh' button does not seem to initialize anything. So no networks appear
- One have to press 'Switch Off Wi-Fi' twice to make it turn off
- When turning on again and then pressing 'Refresh' button networks appear
- Signal strenght with desired wifi network is mostly showing 100%, but has been noted going down to 88%
For a non-technical person doing the steps above would be counter intuitive. Which applies to my better half who is going to use the computer ![]()
People ask me which OS i would recommend and until Devuan arrived I have been uncertain what to recommend. I am currently using FreeBSD my self coming from MS Windows and have not been willing to use time learning a systemd system. My point is that having Wicd working as it should would be a good thing for non-tech people when switching between different wifi networks and wired.
I am not sure what you mean when you say "Wicd seems to work better when you don't actually get into it...".
Until Wicd would work without issues the closest alternative for me would be to do a manual configuration. So I can ask if the configuration below would be correct and recommended?:
In /etc/network/interfaces:
auto wlan0
iface wlan0 inet dhcp
wpa-conf /etc/network/wpa-psk-tkip.confIn /etc/network/wpa-psk-tkip.conf:
ctrl_interface=/var/run/wpa_supplicant
network={
ssid="xxxxxxxxx"
key_mgmt=WPA-PSK
proto=WPA
pairwise=TKIP
group=TKIP
psk="xxxxxxxxx"
}Thanks
Hi guys
After installing Devuan I was eager to find out how to configure Iptables so I could get an ok simple desktop configuration.
I have used FreeBSD for a while now and are starting pf in /etc/rc.conf, but if I am understanding correctly now Iptables is a way of handling rules for telling netfilter, which is running all the time no matter what, in the kernel on how to handle network traffic. So no need for any entry in a rc.-file. Is this correct?
As a first timer I used this guide: https://wiki.debian.org/iptables
When it comes to loading rules I have understood it as such that one have to make a shell script that executes on every reboot, where this script tells which file is the custom iptables rules file. Otherwise there will be no loading of rules. Is this correct?
The Iptables rules file can be named what ever and be located where ever as long as the path in shell script points to it. Is this also correct?
I used the commands:
iptables-restore < /etc/network/iptables.up.rules
iptables-save > /etc/network/iptables.up.rulesI tried to make a script 'iptables' which I placed in /etc/network/if-pre-up.d/
Content of the script was:
#!/bin/sh
/sbin/iptables-restore < /etc/network/iptables.up.rulesTo make the script executable I used:
chmod +x /etc/network/if-pre-up.d/iptablesMy experience is that the computer hanged during boot when using this script. Note: I just noticed that there is no space betwen #! and /bin/sh. Maybe this has something to do with it.
Since this is new to me I am wondering if there is an optimal or preferable way of doing it with Devuan? Also, is there any difference between a systemd system and Devuan when it comes to configuring Iptables?
Thanks
Hi guys
I have set Wicd Network Manager to automatically connect to our home wifi, but nothing happens.
Wicd is starting automatically, but to get the list of wifi networks I have to press 'Switch Of Wi-Fi' twice before it actually turns of. Then I turn it on again and press 'Refresh'. Now the list of different wifi networks appears where our network with the 'Automatically connect to this network' checkbox is checked. If I press 'Connect' it connects.
The wifi signal strength is 100%
Does anyone know what is happening here?
Interfaces in /etc/network only shows:
auto lo
iface lo inet loopbackwlan0 adapter is Broadcom BCM4312 802.11b/g LP-PHY
configuration is:
configuration: broadcast=yes driver=b43 driverversion=3.16.0-4-amd64 firmware=666.2Thanks
Thank you very much for your help @MiyoLinux and sorry for my very late follow up.
I can confirm that a newer version of Firefox-ESR did the trick. We are running Devuan 64-bit with Firefox-ESR 52.4.0 now and it automatically started to download Widevine when in Netflix.
I had to remove the older Firefox-ESR version first to upgrade to the newer version though. I am not sure why. Did a remove on Iceweasel too. Maybe there was a connection between the two. I then did a clean install and now have a 'Play DRM Content' checkbox in Content settings.
Thank you for your reply MiyoLinux.
I have tried to run Netflix with the Firefox-ESR version in the Devuan 1.0.0 Jessie release image from an USB stick, but get the Netflix HTML5 / Silverlight requirement page. I am trying with default settings in Firefox-ESR.
Is there a specific setting that I am not aware of?