You are not logged in.
Recently I have installed Archlinux on my X60s Thinkpad. I have been following the Beginner's Instructions in this Wiki, and also the X60s 'installing experiences' at Elfenbeinturm.cc.
So almost everything worked out nicely.
Yet I still have a few issues I am not able to solve:
1) The Fn-Buttons on my Thinkpad don't work properly. I cannot for example dim my display brightness - using FN+End or FN+Home results in the screen going black. I can return switching to STRG+ALT+F1 and F7 thereafter.
2) The power management does not work properly. CPU seems to be fine, but I am not able to configure the Gnome Power Manager such that the Screen gets dimmed when on battery. It simply does not work. Also, how can I make my wireless (Intel ipw3945) a part of the power management?
3) Not all of my Daemons seem to start up properly. Yet I cannot see which ones. Where can I see the error ouput? A log or something...
4) I tried to install SMLNJ (www.smlnj.org). Yet this doesn't really work. Are there any Arch-packages available? I have found some debs and rpms, but that's it...
5) My network works a bit weird - in case I plug a network cable in the Network Manager does not recognise it. When I restart the system everything works nicely... What's the matter?
6) My system clock is not right... How to change it?
Hope to find some answers. Would be glad if you helped me.
Offline
4) There is a package in the AUR: here
(In case you don't know what the AUR is: http://wiki.archlinux.org/index.php/AUR )
6) http://wiki.archlinux.org/index.php/TIMEZONE
That's all i can offer for the moment.
Greetz Nihathrael
Last edited by Nihathrael (2007-10-27 12:17:57)
Unknown Horizons - Open source real-time strategy game with the comfy Anno 1602 feeling!
Offline
5) My network works a bit weird - in case I plug a network cable in the Network Manager does not recognise it. When I restart the system everything works nicely... What's the matter?
I have no experience with network manager but on my laptop i am using multiple network profiles (wired, 3 wireless, umts) .
switching profile is only succesful when do this :
/etc/rc.d/network stop
wait a few seconds
/etc/rc.d/network start
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Hey,
I had the brightness problem. Don't know how to fix it, but you can set the brightness automatically by putting a script in the autostart folder of kde/gnome (I guess gnome has one too). Have a look at this:
http://bbs.archlinux.org/viewtopic.php?id=38594
Last edited by ibendiben (2007-10-27 19:25:40)
Offline
3) /var/log
6) /etc/rc.conf - timezone OR in your BIOS.
Last edited by ProzacR (2007-10-27 19:53:04)
Offline
1) I have a T41, which is similar but not identical to the X60-series, but on the T41:
By default pressing a FnF{1-12} (except FnF3 -> Sleep) key does nothing as far as linux is concerned. If you load the thinkpad-acpi module then some hotkeys cause acpi events. You can set all the keys to send events by
# echo enable,0xffffff > /proc/acpi/ibm/hotkey
(must be done every boot, so put it in rc.local)
You can find out what events are being sent with the acpi_listen command.
When acpid is running, events are caught and handled by /etc/acpi/handler.sh. You can define any action you want there.
Some further reading which may be useful:
Thinkwiki entry on hotkeys
ArchWiki entry on acpi hotkeys
An archlinux on X60 guide - not the greatest IMHO, has some unusual ways of doing things
The Thinkwiki is a great resource for linux on IBM Thinkpads btw.
Jack
Last edited by Jack B (2007-10-27 20:57:38)
Offline
you can stop the system during boot with ctrl/s or ctrl/q, i'm not sure which of them.
Offline
GNU/Linux on laptops is not as easy or straight-forward as it should be. There are lots of annoyances which, cumulatively, led me to believe that GNU/Linux is simply not the best OS for laptops, yet.
However, you may want to take a look at thinkwiki.org for some hints, and continue with your trial-and-error.
I had my Thinkpad T-23 running quite well, but there were still some minor annoyances which led me to conclude that it was more work that it was worth to keep GNU/Linux on it.
As you are finding out, wireless networking, especially for laptops which roam, is a pain in the ass to get running smoothly. Also, power management became too much of a hassle. The foss community simply does not develop many widely available, powerful, stable, and user-friendly tools for this sort of thing. I, like Lone Wolf, had to manually stop and start my network script. I found networkmanager impossible to use, after 3 days of hacking. Wifi radar worked, but is weak and not configurable. Wlassistant is the best of the 3, but still not as configurable as it should be. Arch, of course, ran the best on my Thinkpad, better than any other distro, and easier to hack.
Thinkpads are supposed to be well-supported, but I still say laptops in general are lacking full community embrace, support and development.
In time I am sure GNU/Linux on laptops will become much more of a pleasure to use. In the meantime, check out thinkwiki.
Offline
===Off Topic===
As you are finding out, wireless networking, especially for laptops which roam, is a pain in the ass to get running smoothly. Also, power management became too much of a hassle.
Hmm. I have a script using netcfg, network profiles and iwlist which will automatically bring up any known wireless network in range. I can then call that by an acpi event from FnF5 Maybe I should put it up somewhere....
===Back On Topic===
Re item 5. If you have the cable in at boot, and your rc.conf set up correctly, arch should bring it up OK. If you plug it in whilst arch is running, then the ifplugd package might help. I don't use Network Manager though, it might break one of both of the above in favor of it's own system.
Jack
Offline
4) Successfully installed from the AUR! Thanks Nihathrael!
6) Easily solved, I simply changed my Thinkpad's in the BIOS. I could have thought about this earlier... Thanks ProzacR!
I am trying to solve everything else when I have some spare time left. Thanks so far guys!
Offline
Jack B:
What you are talking about sounds somewhat interesting. As I am not entirely opposed to the idea of using the Shell to run organize my network...
So, could you state a bit more about this? There is written something in the Wiki, but so far it is not utterly clear to me.
I need to do the following:
I mainly use my computer in lectures and in various areas at university. There the WirelessLan has the same ESSID everywhere. Then I am using a WirebasedLAN in my room (along with my Desktop system; I might get a (WPA-protected) Wireless there too, or maybe only a router). And sometimes I use Wireless at some friends' rooms in case they have it.
When coming home to my parents house there I am using a WPA-secured wireless connection. The connection there was basically speaking awful. I constantly had disconnects.
And sometimes I want just go to a caf`e or a library and use their wlan access points...
So, how to best accomplish this without Network Manager?
Offline
OK... It takes a fair bit of setting up, my way.
There is another, daemon-based way which might be easier.
Firstly, you need a file in /etc/network-profiles that describes each network you wish to use. For my script to work, don't put spaces in filenames.
More info in the wiki
At this point you can bring up any of these networks with:
# netcfg <filename>
Now I have my little script, which will automatically choose a profile depending what is available. The script is:
#!/bin/bash
# A script to detect nearby wireless networks, and use netcfg to bring up the associated network profile
# By Jack Barraclough <jack.barraclough.1ATgmailDOTcom>
# Is the network up for scanning?
ifconfig ath0 up
# Find an array of ESSIDs within range of wireless
ScannedESSIDs=(`iwlist ath0 scan | grep ESSID | sed 's/ESSID://g;s/^[ \t]*//;s/"//g'`)
# ls network profiles, omitting template
netprof=(`ls --hide=template -m /etc/network-profiles/ | sed 's/,//g'`)
# find array of ESSIDs from files
declare -a KnownESSIDs
for i in ${netprof[*]} ; do
KnownESSIDs=(${KnownESSIDs[@]} `cat /etc/network-profiles/$i | grep ESSID= | sed 's/ESSID=//g;s/"//g'`)
done
# Check for matches, running through ESSIDs in the order that files were listed by ls (alphabetical)
# count our way through the known ESSIDs so we know the array index of the matching ESSID
index=0
for i in ${KnownESSIDs[*]} ; do
for j in ${ScannedESSIDs[*]} ; do
if [ $i == $j ]
then
DetectedESSID=$j
break
fi
done
if [ $DetectedESSID ]
then
break
else
let index++
fi
done
# Echo the ESSID which matches, if one is found, and use netcfg to activate it
if [ $DetectedESSID ]
then
netcfg ${netprof[index]}
/bin/su jack -c "export DISPLAY=:0.0; notify-send 'Wireless Hotkey' 'Wireless now connected to ${netprof[index]} ($DetectedESSID)'"
exit
else
/bin/su jack -c "export DISPLAY=:0.0; notify-send 'Wireless Hotkey' 'No known wireless networks found'"
exit
fi
Note that:
-> The script was designed for my use, it may not work on your machine, No warranty etc.
-> It also assumes your wireless interface is ath0. If it isn't, change all cases of 'ath0' to whatever yours is called.
-> It is gnome-centric, so it uses notify-send to pop up notifications in gnome. If you use kde etc. change it.
-> It is designed to be called by an acpi event, so does not check if it is root. If it is run as non-root, it won't work. That's also why it uses notify-send not echo, and why it says things like "wireless hotkey pressed"
-> It only deals with known, wireless networks. use ifplugd for wired networks.
hope this is useful
Jack
Offline
I just re-read my post above, and it sounds like all doom and gloom. Sorry to be such a downer.
I do believe more simple and reliable wireless tools are very desirable though, especially for roaming laptops.
Offline
I have also just noticed a project called wicd, which might be a good option. Not tried it though.
-Jack
edited: typos
Last edited by Jack B (2007-11-05 20:54:27)
Offline
UPDATE: I believe the new version of netcfg, now in testing, supports autodetection. Thus my above script is superfluous.
Offline