WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Recent Posts

Pages: [1] 2 3 ... 10
1
General TC Talk / Re: how to completely disable lid switch?
« Last post by Rich on Today at 02:04:38 PM »
Hi GNUser
I see  laptop-mode-tools.tcz  includes:
Code: [Select]
/usr/local/share/laptop-mode-tools/files/acpi/actions/lm_lid.sh
/usr/local/share/laptop-mode-tools/files/acpi/events/lm_lid
Maybe they are of some use?
2
General TC Talk / how to completely disable lid switch?
« Last post by GNUser on Today at 11:06:28 AM »
I run Pure64 10.1 on my laptop. I'd like the laptop's behavior to be identical regardless of whether its lid is open or closed. In the past, I found that the only way to achieve completely identical behavior is to disable the lid switch at the level of the kernel.

In Debian, I can find the lid's sysfs node (e.g., PNP0C0D:00) by running cat /proc/acpi/wakeup, then this command completely disables the lid switch by unbinding its driver:
Code: [Select]
echo 'PNP0C0D:00' | sudo tee /sys/bus/acpi/drivers/button/unbindIn Pure64, cat /proc/acpi/wakeup shows me that laptop lid's sysfs node is PNP0C0D:00 as expected, but notice what happens when I try to unbind the driver:
Code: [Select]
echo 'PNP0C0D:00' | sudo tee /sys/bus/acpi/drivers/button/unbind
PNP0C0D:00
tee: /sys/bus/acpi/drivers/button/unbind: I/O error
Can you please help me completely disable the lid switch? I'm aware of the acpi=off kernel boot parameter, but that has the unpleasant side effect of also disabling kernel's battery stats (which I need for one of my shell scripts). I'd like to disable only the lid switch.
3
TCE Corepure64 / Re: How to configure urxvt
« Last post by Looper on Today at 07:10:44 AM »
Tanks my friend
Now
Code: [Select]
echo -e '\xe2' return square
4
TCE Corepure64 / Re: How to configure urxvt
« Last post by jazzbiker on Today at 05:41:40 AM »
urxvt can read its settings from ~/.Xdefaults
For example, my ~/.Xdefaults is
Code: [Select]
tc@box:~$ cat ~/.Xdefaults
Aterm*scrollBar: false
Aterm*transparent: false
Aterm*title: Terminal
Aterm*foreground: black
Aterm*background: aquamarine
Aterm*font: Terminus-bold-20
Aterm*cursorColor: green
Aterm*fading: 70
Aterm*shading: 50
Aterm*color12: DodgerBlue1
Aterm*saveLines: 1000
fltk*scheme: gtk+
Xft.dpi: 96.0
urxvt*background: aquamarine
urxvt*foreground: black
urxvt*font: Terminus-bold-20
urxvt*scrollBar: false

Assigning colors you can use ones found in /usr/local/share/X11/rgb.txt
5
TCE Corepure64 / Re: How to configure urxvt
« Last post by Looper on Today at 05:21:59 AM »
I can't find config file urxvt
Where is that ?
6
TCE Corepure64 / Re: How to configure urxvt
« Last post by Rich on Today at 04:59:40 AM »
Hi Looper
If you go here:
http://pod.tst.eu/http://cvs.schmorp.de/rxvt-unicode/doc/rxvt.1.pod#RESOURCES
It tells you where  urxvt  looks for configuration information. If you scroll down to where it says  font: fontlist , It provides
an explanation.

This shows ho to select fonts when starting  urxvt:
http://pod.tst.eu/http://cvs.schmorp.de/rxvt-unicode/doc/rxvt.7.pod#How_does_rxvt_unicode_choose_fonts
7
TCE Corepure64 / Re: How to configure urxvt
« Last post by Looper on Today at 04:48:30 AM »
Tanks for replaying
Just install ? Or need configuration ?
Please explain step by step , sorry I'm  low experience
8
TCE Corepure64 / Re: How to configure urxvt
« Last post by jazzbiker on Today at 04:42:25 AM »
Hi, Looper!

Probably you need utf-compatible fixed font. I use Terminus fonts, and like them very much. Install terminus-fonts extension.
9
TCE Corepure64 / How to configure urxvt
« Last post by Looper on Today at 04:18:37 AM »
I need to interpret utf8 in terminal local on corepure 10.1
I use getlocale and doesn't work for me
Please explain for me ; how can use ( configure ) urxvt or aka ,... in tiny core ?
10
Hello Rich:

I don't know the answer to that.
OK, fair enough.

Maybe it was deemed that  xf86-video-nv.tcz  was adequate.
OK, maybe that was what happened.

But freedesktop.org clearly says that xf86-video-nv driver should not be used and that the nouveau driver is the correct one to use. As they are the one who wrote it I expext they have good reason to say that.

It did successfully detect your hardware.
Maybe Juanito or curaga will weigh in on this.
I'm sure that you will concurr with me that detecting the hardware is just the start of a complex path to working properly.
Something that xf86-video-nv was shown unable to do.

Juanito had no way of knowing the  Nouveau  driver required a kernel compilation. The  CONFIG_DRM_VM=y  option
does not show up in the configuration menu so you don't even know it exists, let alone getting set to yes.
OK.
What you say makes complete sense.

But we are all at a different spot now and know (thanks to your looking into it) what is needed for the nouveau driver to work properly (ie: actually load) with the TC kernel so it seems that the road is paved to an easy solution to the problem of NVidia card support in TinyCore using open source drivers.

I was more than anything looking forward to reading your answer to the last question I asked in my previous post, one which I consider the most important:

... not configured to support the Nouveau driver. Unless a serious problem is found, the kernel doesn't get updated for a current release.
If perchance this is not considered a serious (or serious enough) problem, would it be realistic for me to expect that the TC10.2 release, whenever that comes along, will be compiled to support the open source Nouveau drivers?

Thanks in advance.

Best,

MM
Pages: [1] 2 3 ... 10