LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   We will call this update Slackware 13.1 RC1, Now RC2 (https://www.linuxquestions.org/questions/slackware-14/we-will-call-this-update-slackware-13-1-rc1-now-rc2-807902/)

Ilgar 05-15-2010 01:32 AM

Quote:

Originally Posted by tuxrules (Post 3969130)
Thanks Jeebizz, my locale is not set to utf-8. /etc/profile.d/lang.sh shows this

Code:

# en_US is the Slackware default locale:
export LANG=en_US


Do you have TERM=linux in your profile?

ginkgo 05-15-2010 02:27 AM

@tuxrules
maybe you can add the
Code:

export LC_CTYPE=en_US.UTF-8
BTW. I use the firefox 3.6.4 build 4 that is release on today. the slackware current use the 3.6.3.
In the 3.6.4 the flash is running on a separate process. It is more stable than 3.6.3.
But the 3.6.4 will be released on june 1. bad news.

mcnalu 05-15-2010 02:37 AM

Good hello! I like it :)

Testing today.

Ilgar 05-15-2010 03:44 AM

I'm not on -current but I am running a custom compiled 2.6.33.4 kernel which the same as that in -current. Since I switched to this version the ondemand governor stopped working (I have an Asus eeePC 1005HA). Some Googling suggested that this might be a kernel issue. Are you experiencing a similar problem? If so, 2.6.33 might be a particularly bad choice for laptop/netbook owners. Pat doesn't make any kernel updates (to stable releases) except for security fixes but a backport might be a good idea for this case (I think there is a fix in the 2.6.34-rc tree).

brianL 05-15-2010 04:36 AM

Are we there yet? :)

sycamorex 05-15-2010 05:14 AM

That's excellent news!

I've done the updates, but I've got a question about aaa_elflibs.

It changelogs it says that aaa_elflibs has been upgraded to 13.1.

Is it the only case when I should comment out blacklisting of it in /etc/slackpkg/blacklist?
It says there that it can't be upgraded.

What's the deal with aaa_elflibs then?
I've got everything upgraded apart from elflibs now:
aaa_elflibs-13.0-x86_64-2

Shall I comment it out and run slackpkg again?

thanks

tuanld91 05-15-2010 05:20 AM

Do not ever try to, lol.

samac 05-15-2010 05:21 AM

Quote:

It changelogs it says that aaa_elflibs has been upgraded to 13.1.

Is it the only case when I should comment out blacklisting of it in /etc/slackpkg/blacklist?
It says there that it can't be upgraded.

What's the deal with aaa_elflibs then?
I've got everything upgraded apart from elflibs now:
aaa_elflibs-13.0-x86_64-2

Shall I comment it out and run slackpkg again?
Yes. In Slackware current any update to aaa_elflibs includes all the most up to date libraries, so it should be OK to update it.

Anyway this is what I believe is the case.

samac

tuanld91 05-15-2010 05:30 AM

Well, i don't know, but you have to take the risk if you do then.
http://connie.slackware.com/~mozes/docs/aaa_elflibs.txt

Edit: Oh, i didn't saw samac's post, now understand a some more about slackware-current :D.

samac 05-15-2010 05:39 AM

Here is a bit of confirmation read the last 3 posts.

samac

sahko 05-15-2010 05:59 AM

Quote:

Originally Posted by Ilgar (Post 3969282)
I'm not on -current but I am running a custom compiled 2.6.33.4 kernel which the same as that in -current. Since I switched to this version the ondemand governor stopped working (I have an Asus eeePC 1005HA). Some Googling suggested that this might be a kernel issue. Are you experiencing a similar problem? If so, 2.6.33 might be a particularly bad choice for laptop/netbook owners. Pat doesn't make any kernel updates (to stable releases) except for security fixes but a backport might be a good idea for this case (I think there is a fix in the 2.6.34-rc tree).

If you see /sys/devices/system/cpu/cpu0/cpufreq/ then you'll see that many things changed with 2.6.33.
The rc.modules section on cpufreq handling is outdated. I think its better to use cpufrequtils directly now.

Ilgar 05-15-2010 06:30 AM

Quote:

Originally Posted by sahko (Post 3969384)
If you see /sys/devices/system/cpu/cpu0/cpufreq/ then you'll see that many things changed with 2.6.33.
The rc.modules section on cpufreq handling is outdated. I think its better to use cpufrequtils directly now.

I use a custom kernel and the cpufreq support is built-in, so rc.modules shouldn't make a difference. I already checked that directory and the active governor seems to be ondemand, but the frequency is stuck at maximum when the processor is idle.

Anyway, I discovered another problem related to hda_intel: Sound keeps coming out of the speakers even when a headphone is plugged in. So I'm back to 2.6.32 for now.

sycamorex 05-15-2010 06:35 AM

Ok, thanks guys. I decided to upgrade aaa_elflibs.

tuxrules 05-15-2010 09:31 AM

Quote:

Originally Posted by Ilgar (Post 3969202)
Do you have TERM=linux in your profile?

Yes TERM=linux set in .bashrc. I removed/added it back but it didn't change anything...still the weird chars.

Quote:

Originally Posted by ginkgo (Post 3969236)
@tuxrules
maybe you can add the
Code:

export LC_CTYPE=en_US.UTF-8

No, that messes up the terminal even badly.

Thanks guys!

linus72 05-15-2010 09:34 AM

I am having issues too only when in console mode
everything is garbled when I use slackpkg, sbopkg, etc
its hard to read and looks like chinese?


All times are GMT -5. The time now is 04:59 PM.