Tiny Core Linux
Tiny Core Base => CorePlus => Topic started by: aug on July 26, 2015, 09:45:19 AM
-
Hi,
i have installed tc with apps to the harddrive of a lenovo b590 and have now two problems for which i can't found a solution here or on google.
a. WLAN
The laptop has a build in wlan-adapter Broadcom BCM43142. The file firmware-broadcom_bcm43xx.tcz is in the tce folder and in onboot.lst. ifconfig shows no wlan-device and the wifi-apps shows only a black screen.
The eth0-device works perfect.
b. Keyboard (german layout)
All Keys workins in terminal mode (like in midnight commander) but not on the x-desktop. Missing the Symbols accessible with AltGr and can't switch the numeric pad with numlock (no reaction).
Any help are welcome.
-
I have a similar wifi chip.
a.)
You might need to blacklist some modules via boot code
blacklist=ssb,b43,bcma
I think this information was once included in the .info file of firmware-broadcom_bcm43xx.tcz but isn't currently.
In my case, the wifi device gets assigned to eth1. For convenience, I rename it using this code in /opt/bootlocal.sh
# Rename wifi eth* to wlan*.
IFNUM=0
for i in /sys/class/net/eth* ; do
if [ -d $i/wireless ]; then
[ -e /sys/class/net/wlan${IFNUM} ] && IFNUM=$((IFNUM+1))
#echo wlan${IFNUM} `cat $i/address`
nameif wlan${IFNUM} `cat $i/address`
IFNUM=$((IFNUM+1))
fi
done
wifi.sh -a &
I have to enable wifi (via Fn keys) before loading the extension.
If it's loading OnBoot, I have to either enable wifi while booting or before shutdown.
A workarounf could be
sudo rmmod wl
# "Enable wifi via Fn keys."
sudo modprobe wl
b.)
If you're using Xorg, you need to tell it about your keyboard locale independently to the Linux console.
/usr/local/share/X11/xorg.conf.d/10-keyboard.conf
Section "InputClass"
Identifier "Keyboard Defaults"
MatchIsKeyboard "yes"
Option "XkbLayout" "de"
Option "XkbOptions" "terminate:ctrl_alt_bksp"
EndSection
And remember to include added files to your backup.
Don't know about NUM-Lock. Works here.
-
a.)
You might need to blacklist some modules via boot code
blacklist=ssb,b43,bcma
i have this line in extlinux.conf:
APPEND initrd=/tce/boot/core.gz quiet waitusb=5:UUID="..." tce=UUID="..." kmap=qwertz/de-latin1 tz=CET host=b590
... = only placeholders here
did i need to add the blacklist here?
b.)
Not sure which version i using but thinking its xvesa. Don't know how to find out what is currently running.
-
a.)
Yes, just add blacklist=ssb,b43,bcma like so:
APPEND initrd=/tce/boot/core.gz quiet waitusb=5:UUID="..." tce=UUID="..." kmap=qwertz/de-latin1 tz=CET host=b590 blacklist=ssb,b43,bcma
b.)
cat /etc/sysconfig/Xserver
I think Xorg provides better functionality for keyboards than Xvesa. So you might want to give it a try.
Otherwise, it might just depend on the software you're using - Aterm can't display unicode characters, Firefox can.
-
a.)
Yes, just add blacklist=ssb,b43,bcma like so:
APPEND initrd=/tce/boot/core.gz quiet waitusb=5:UUID="..." tce=UUID="..." kmap=qwertz/de-latin1 tz=CET host=b590 blacklist=ssb,b43,bcma
i will check it soon....
b.)
cat /etc/sysconfig/Xserver
I think Xorg provides better functionality for keyboards than Xvesa. So you might want to give it a try.
Otherwise, it might just depend on the software you're using - Aterm can't display unicode characters, Firefox can.
i get Xvesa
How can i change to xorg???
-
Exit out of X. Either via Ctrl+Alt+BackSpace or via the Exit tool from Wbar -> Exit to Prompt.
In Linux console, type
tce-load -i Xorg-7.7
If it's not available on your system, you first need to download it
tce-load -w Xorg-7.7
If you have Xorg installed, manually or automatically OnBoot, it will be preferred by Tiny Core over Xfbdev and Xvesa.
-
ok seems that i need to download it. can only find Xorg-7.7-lib.tcz in the tce folder.
-
Oh, and then
startx
to launch the X server.
-
The laptop has a build in wlan-adapter Broadcom BCM43142.
I believe you'll need the wl-modules-3.16.6-tinycore extension for this as per:
https://wireless.wiki.kernel.org/en/users/Drivers/b43
-
The wlan is working now! I only had to add the blacklist to the line in the boot up conf.
Only problem i see at the moment is that it did not reconnect after boot. I have to open the wifi-app and select the network - did not get the password question again. After that i get a ip and it works.
Now i have to work the problem with the keyboard and xorg/xvesa.
-
You can start wifi.sh with the -a switch, to automatically connect to the first entry listed in ~/wifi.db .
For example, you can add this to /op/bootlocal.sh
wifi.sh -a &
-
Fine...but i see a little security issue now. /home/tc contains now a file wifi.db - nothing more than a text file but it contains the plain wlan-password...... :-(
-
Your backup file can be encrypted using the protect boot code.
-
Fine...but i see a little security issue now. /home/tc contains now a file wifi.db - nothing more than a text file but it contains the plain wlan-password...... :-(
lol this comes up every so often. If you think about it a little, how can it possibly be a security issue? if someone is looking at the contents of the file then knowing the contents is irrelevant, additionally the range of your wifi is relatively small making the scope of vulnerability extremely small. besides what is anyone going to do with that information anyhow..??
-
...but with the time it will fill up with the passwords to clients network.... i travel a lot....
-
You could as well exclude it from your backup file instead.
echo wifi.db >> /opt/.xfiletool.lst
-
You can start wifi.sh with the -a switch, to automatically connect to the first entry listed in ~/wifi.db .
For example, you can add this to /op/bootlocal.sh
wifi.sh -a &
I had to add the path in /opt/bootlocal.sh too => /usr/local/bin/wifi.sh -a &
-
Not really satisfied with xorg so i think i stay with xvesa. Where can i find some instructions to solve the keyboard problem?
-
Misalf and OP
I can't read any German, nor use that keyboard but I can't see any mention of you needing to load keyboard map from say
xkeyboard-config or kmaps
kmaps seems to have lots of German maps
/usr/share/kmap/qwertz/de_CH-latin1.kmap
/usr/share/kmap/qwertz/de-latin1-nodeadkeys.kmap
/usr/share/kmap/qwertz/de-mobii.kmap
/usr/share/kmap/qwertz/de.kmap
/usr/share/kmap/qwertz/de-latin1.kmap
de_CH appears to be Swiss
a quick google suggested some seem to like the nodeadkeys map?
good luck and hope that helps
-
Thanks gordon64, you're right that none of us mentioned kmaps.tcz to be loaded. However, I assumed aug has it loaded already, otherwise
kmap=qwertz/de-latin1
wouldn't have any effect, and I think
All Keys workins in terminal mode [...] but not on the x-desktop
couldn't be true.
I suspect Tiny Core is just a mess to set up for internationalization, as most how-tos available on the net are for the big distros, where one has to just click around in a GUI tool without having to know anything about what just happened to possible config files, additional to LC_* variables.
Personally, I don't want my OS to speak any other language than its default one, except the possibility to understand my commands via my 'non-default' keyboard. Just setting the hole system to another language can lead to confusion (and slowing things down due to loading additional text strings).
For example, in Germany, dates are written as 'Day Month Year' wile in US it's 'Month Day Year'.
Numbers are treated differently, too. Germany uses the dot "." to visualize power-of-thousands, and the comma "," for everything below zero. In US it's vice versa.
So far I wasn't able to configure Tiny Core this way without having issues with my keyboard or certain programs.
-
Thanks gordon64, you're right that none of us mentioned kmaps.tcz to be loaded. However, I assumed aug has it loaded already, otherwise
kmap=qwertz/de-latin1
wouldn't have any effect, and I think
All Keys workins in terminal mode [...] but not on the x-desktop
couldn't be true.
I suspect Tiny Core is just a mess to set up for internationalization, as most how-tos available on the net are for the big distros, where one has to just click around in a GUI tool without having to know anything about what just happened to possible config files, additional to LC_* variables.
Personally, I don't want my OS to speak any other language than its default one, except the possibility to understand my commands via my 'non-default' keyboard. Just setting the hole system to another language can lead to confusion (and slowing things down due to loading additional text strings).
For example, in Germany, dates are written as 'Day Month Year' wile in US it's 'Month Day Year'.
Numbers are treated differently, too. Germany uses the dot "." to visualize power-of-thousands, and the comma "," for everything below zero. In US it's vice versa.
So far I wasn't able to configure Tiny Core this way without having issues with my keyboard or certain programs.
Hi All,
on the cli level everything works fine! It's only X. The majority of the keys works so i can work with it.
In Europe english is not really wide used, in some countries it's not even teached at school. For the people it's very important to have a computer in here own language. And... english is not the most used language on earth, but day.month.year is used at the majority of the world same as the 24hour clock and not am/pm.
If Linux spreads more to the desktop its very important to support this.
-
Actually, it is supported by Linux, but Tiny Core is not a ready-to-go distro. It's a Tool-Kit for 'easily' creating a Linux that fits your needs without unneeded blows & whistles. So the users need to find out how to add features not already included or fully supported.
-
It's only X.
aug
then maybe you can reveal your video card to us by
lspci -vvv just take a snip of the section for VGA
Then reveal what is in your "xorg".lst or what ever you call it please?
Also its not clear to me, and I am the stupid one here ;D
when you are in X, that you know to use apps that are <somename>-locale.tcz
I know you must know this by using a terminal which is language capable just as lxterminal-locale
but text editor needs it as well just as leafpad-locale etc......if you wish to use German.
Thats the limit of my brain cells so signing off to the experts.
good luck
-
*-locale.tcz extensions will be used (automatically loaded) if the lang= boot code was used. As far as I get it, this should only affect text translations of menus, options, manuals etc. but not keyboard input?