@ SFR and belham2
It looks like it requires something that is inside of the devx. (see pics below)
Hope this helps
CatDude
.
P.S I always ride with the devx loaded

Well, it's been included since 720 IIRC (/etc/xdg/Startup/firetray).jamesbond wrote:@SFR:
@belham2:
please include SFR's "firetray"
jamesbond stares at SFR
The one on the screenshot is redshiftgui, not redshift.jamesbond wrote:@belham2:
include redshift
Not a bad idea. At 126K I think we can afford it. I built it but never use it - does come with a GUI or do we need to get another GUI?
And SFR and step tooLateAdopter wrote:Hello Jamesbond and kirk
Just checking in to say thanks for this.
LOLSFR wrote:Well, it's been included since 720 IIRC (/etc/xdg/Startup/firetray).jamesbond wrote:@SFR:
@belham2:
please include SFR's "firetray"
jamesbond stares at SFR
Control Panel -> Desktop -> Manage desktop startup programs -> System startup programs -> firetray.
That's way too big. I'd check your attached redshift-gui script and see how it goes.It's 451K compressed.
I guess you can check for the applesmc module ("lsmod | grep applesmc" or similar) and add it to the sven key_config file byjamesbond wrote: 2. BTW screen brightness keys work fine OOTB, as well as the keyboard backlight with the following little script
I can certainly put the script inside. How does one activate the script?
Done.mavrothal wrote:I guess you can check for the applesmc module
No matter that is cd, usb or sda - happens the same thing. I'm using syslinux bootloader from fatdog installer.SFR wrote: Does it hang if you boot FD directly from CD/USB instead of sda1?
What bootloader are you using and have you tried a different one?
You are right. It does work (I forgot that fd's ps has the standard behaviorjamesbond wrote:Done.mavrothal wrote:I guess you can check for the applesmc module
Can you please check, when you boot 800 on MBP (withoust savefile), did you get /etc/init.d/15-mbpfan enabled? If yes, is the mbpfan running?
I just checked my code again, mbpfan should work already.
Thanks!
Hmm, you could append loglevel=7 to your bootloader line, so if the kernel starts at all, we could at least see at which point it hangs.Acodin wrote:No matter that is cd, usb or sda - happens the same thing. I'm using syslinux bootloader from fatdog installer.SFR wrote:Does it hang if you boot FD directly from CD/USB instead of sda1?
What bootloader are you using and have you tried a different one?
Thank you for your interest in my problem in this vortex of excitement.
I would like to add that the problem occurs on the Internet, but I still don't know how to fix that.
I will chech that, but i now have only two 2gb dices. And yes this is possible, because i mix hynix with kingston in both cases (3gb and 4gb). After all, please check my bug report.SFR wrote: If the former, perhaps the modules are incompatibile with each other in some way..?
Yes. As I've just added, this seems to be a long running bug that was "worked-around-but-never-really-fixed" from kernel 4.4.x onwards. The proposed fix for the current mainline dates is less than a week's old; so expect the problem to continue for a while longer, unfortunately.Acodin wrote:@up:
with 'loglevel=7' ?
Looks like the kernel is crashing. It happens after the intel graphics module i915 is loaded. Your bug report is from 721. If the same thing is happening in 800, that's pretty bad since 721 and 800 have different kernels, drivers, xorg, etc. Try booting with this on the kernel line:First, I tried to boot it on the 4gb ram, then I took out one ram dice and run bugreport.sh
Just to expand on what has already been posted. This will be fixed in the next release. You can install libicu-full using Gslapt, or unzip the attached file and place it in /usr/share/icu/62.1/icudt62l/Is anyone else having problems with Seamonkey in Fatdog-800 and activating or even downloading "ADD-ONs"?
Yes, also note that Seamonkey's user agent string is no longer recognized by Google and probably others. This causes web pages to displayed incorrectly and is a problem in 721 now too. That's the reason for the inclusion of "User Agent Switcher".Was this edition of Seamonky compiled by the Fatdog-Team? The reason I ask is that there are "Add-Ons" already included with the Seamonkey that I did not put there and/or download.
There's 100% chance the kernel will be upgraded before final, probably whatever the latest 4.19.x is at the time.Regarding modules and drivers, how likely (1-10) is for the kernel to change till 800 final?
Read everything please. I wrote that the problem occurs on different kernels and both versions.kirk wrote: Looks like the kernel is crashing. It happens after the intel graphics module i915 is loaded. Your bug report is from 721. If the same thing is happening in 800, that's pretty bad since 721 and 800 have different kernels, drivers, xorg, etc. Try booting with this on the kernel line:
doesn't helploglevel=7 savefile=none nomodeset blacklist=i915
Yes I understood that, I was trying to say that it's not a good sign that it's happening with different kernels since it seems to be a kernel bug.Read everything please. I wrote that the problem occurs on different kernels and both versions.