You are not logged in.
@Locri, anything interesting come up in dmesg? eg, "dmesg | grep eth0"
Also, have you installed Arch before? (want to find out if there's a missed step somewhere)
@oschiro, yeah, no xD cards handy, but aren't those were a different format than SD? or does the SL500 have an xD card reader also? (my SL300 has only the SD reader)
Also, I seem to remember xD cards being notorious for their proprietary nature, I'd check if there's even support for it in general
Offline
Hello sctincman,
yeah it has indeed and he is working with windows. lspci says:
0d:00.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev ff)
It would be great if you might find out something interesting.
EDIT:
lspci -v says:
0d:00.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev ff) (prog-if ff)
!!! Unknown header type 7f
So there seems to be no module for that?
And now? Is there any chance to get xD-support working?
Last edited by orschiro (2010-01-11 19:59:52)
Offline
Thanks for the reply sctincman.
I've installed Arch a great many times on my desktop, but this is my first time installing it on a laptop. As far as I know I didn't miss anything in the installation.
So far dmesg doesn't show anything useful (I can't copy the exact text easily). It basically identifies the network card (no problems there) but after that there are two messages stating that the link is down and that's all. I know the jack/card is fine because it worked perfect during the install and it continues to work fine on the Windows 7 side (what I'm typing from now). I'm trying to during off power saving features to see if that makes any difference but I haven't had enough time to test everything yet.
It's kind of weird, I can't find anyone else reporting this issue on the laptop elsewhere so I'm a bit baffled as to why I'm being bitten by it.
Offline
@orschiro, I have no idea, the most I could turn up is the info on the wikipedia page saying there's only experimental support for one type of xD card controller And I'm also no linux guru, so I have no clue what your lspci -v output means
@Locri, I once again have no clue :x I've only installed Arch once on my SL, and I don't remember any trouble with eth0, and really not sure what could be wrong
so with that! pardon the seemingly patronizing questions, but
dmesg output?
"ifconfig -a" output?
is the module in lsmod output?
what are you using to manage the connection?
if it's just the startup scripts, what's in rc.conf network section?
and more to come if I think of it
Offline
Hello sctincman,
yeah it has indeed and he is working with windows. lspci says:
0d:00.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev ff)
It would be great if you might find out something interesting.
EDIT:
lspci -v says:
0d:00.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev ff) (prog-if ff) !!! Unknown header type 7f
So there seems to be no module for that?
And now? Is there any chance to get xD-support working?
I'm in the same situation. The info I gathered from a google search(some ubuntu bug report) is that there are no drivers for this xD card reader.
There are drivers for usb xD card readers but none for readers connected via pci(?) as the ricoh one.
I need xD support as that's the type of cards my camera uses. For now I have reverted to using the usb cable that plugs in the camera. Less comfortable as I have to use (and find) an extra cable when I want to pull pictures off the cam but at least it works
Offline
Offline
@ Klepper,
that's exactly the same situation I'm confronted with. But connecting with a cable seems to work?
I'll have to try that out. And perhaps there will be an experimental driver in the future.
When connecting one by usb, there's likely an onboard controller that handles communicating with the card and just exposes itself to linux as a generic usb storage drive
Offline
I have a small problem with the bluetooth status LED. When I power on the machine, the status LED also turns on but the switch is turned off. What I want is that the LED stays off until I turn the switch.
When the LED is on, switch in off position and I toggle the switch on - off the LED turns off...
Any ideas?
I am loading the "bluetooth" daemon in rc.conf but that isn't the problem?
Offline
I also detected some problems with my hotkeys for mute/increase/decrease sound.
Pressing them once is interpreted twice or more times. A bit unhandy when a script should be performed that normally mutes my sound but due to the sensitive buttons isn't working anymore because it is executed several times.
I didn't change anything special, the script is binded through dwm to the keys.
Last edited by orschiro (2010-01-27 11:11:49)
Offline
Hi guys,
what happens if you press Fn + F5 to toggle wireless connection on/off?
I can turn it off but not on again. Do you notice the same behaviour?
And what's with other keys such as Fn + F11 or Fn + F12, do they have functionality on your systems?
Oh and yes I'm using the driver in its latest version.
Offline
The Fn+F5 key generated an XF86WLAN signal in xev for me, and only seemed to put down the interface, which wicd then puts back up when it tries to reconnect. I don't think it's a hardware/driver thing, but I could be wrong, didn't look into it too much. What are you using to manage your network connections?
I don't think Fn+F11 does anything, no signal in xev and I don't see anything happen, most other buttons (aside from Fn+F8 I think) only generate a relevant x signal, I've tied most of mine to the relevant program/command: xscreensaver for Fn+F2, pm-suspend for Fn+F4, and pm-hibernate for Fn+F12.
much like for the sound buttons, use xev and see what key signal those combinations generate and attach them to useful commands and such
Offline
The Fn+F5 key generated an XF86WLAN signal in xev for me, and only seemed to put down the interface, which wicd then puts back up when it tries to reconnect. I don't think it's a hardware/driver thing, but I could be wrong, didn't look into it too much. What are you using to manage your network connections?
Ok so it seems to be normal that the key only puts down the interface but not up again. I use just plain netcfg script and tried ifconfig wlan0 up after I pressed the button but I got a SIOCSIFADDR or something like that. Don't remember exactly.
I don't think Fn+F11 does anything, no signal in xev and I don't see anything happen, most other buttons (aside from Fn+F8 I think) only generate a relevant x signal, I've tied most of mine to the relevant program/command: xscreensaver for Fn+F2, pm-suspend for Fn+F4, and pm-hibernate for Fn+F12.
Well I did it the same way. Just for interess, what's the Fn+F8 for? And could you please try what xev prints when you press audio raise button one time?
This is mine, but interpreted several times like stated above.
MappingNotify event, serial 34, synthetic NO, window 0x0,
request MappingKeyboard, first_keycode 8, count 248
FocusOut event, serial 34, synthetic NO, window 0x1800001,
mode NotifyGrab, detail NotifyAncestor
FocusOut event, serial 34, synthetic NO, window 0x1800001,
mode NotifyUngrab, detail NotifyPointer
FocusIn event, serial 34, synthetic NO, window 0x1800001,
mode NotifyUngrab, detail NotifyAncestor
KeymapNotify event, serial 34, synthetic NO, window 0x0,
keys: 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
MappingNotify event, serial 34, synthetic NO, window 0x0,
request MappingKeyboard, first_keycode 8, count 248
FocusOut event, serial 34, synthetic NO, window 0x1800001,
mode NotifyGrab, detail NotifyAncestor
FocusOut event, serial 34, synthetic NO, window 0x1800001,
mode NotifyUngrab, detail NotifyPointer
FocusIn event, serial 34, synthetic NO, window 0x1800001,
mode NotifyUngrab, detail NotifyAncestor
KeymapNotify event, serial 34, synthetic NO, window 0x0,
keys: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Last edited by orschiro (2010-02-06 20:00:41)
Offline
And another problem, still regarding my fan control. They are simply too noisy even with controlling cpu via cpufreq and conservative setting.
So I looked at the Wiki page for Fan controlling but sensors doesn't display any rpm monitoring.
[root@thinkpad]# sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +34.0°C (crit = +110.0°C)
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +30.0°C (high = +100.0°C, crit = +100.0°C)
coretemp-isa-0001
Adapter: ISA adapter
Core 1: +30.0°C (high = +100.0°C, crit = +100.0°C)
sensors-detect just finds the coretemp driver.
Driver `coretemp':
* Chip `Intel Core family thermal sensor' (confidence: 9)
How is that on your thinkpad?
Last edited by orschiro (2010-02-09 07:09:49)
Offline
Same for me. But if you have installed this module http://aur.archlinux.org/packages.php?ID=23667 you can control the fan.
You just have to
#echo 1 > /sys/devices/platform/lenovo-sl-laptop/hwmon/hwmon1/pwm1_enable
This enables manual fancontrol.
Then you can control it via
# echo 250 > /sys/devices/platform/lenovo-sl-laptop/hwmon/hwmon1/pwm1
Values between 0 and 255 are valid.
# cat /sys/devices/platform/lenovo-sl-laptop/hwmon/hwmon1/fan1_input
Shows current rotation speed.
Hope this helps in some way.;)
Last edited by Urfaust (2010-02-09 16:38:14)
Offline
Offline
Hi,
got it from some script posted at ubuntuusers.de -> http://forum.ubuntuusers.de/topic/tpslc … st-1994124 I found this while researching for my problem from posting #34 which is solved by putting
echo 0 > /sys/devices/platform/lenovo-sl-laptop/rfkill/rfkill1/state
in /etc/rc.local.
EDIT: Sorry, I don't know which values are safe. I have the manual controls turned off. My fan is rotating at about 2700 rpm and I have this temperatures
acpitz-virtual-0
Adapter: Virtual device
temp1: +41.0°C (crit = +110.0°C)
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +32.0°C (high = +105.0°C, crit = +105.0°C)
coretemp-isa-0001
Adapter: ISA adapter
Core 1: +32.0°C (high = +105.0°C, crit = +105.0°C)
Last edited by Urfaust (2010-02-09 17:28:57)
Offline
Hello Urfaust,
I experienced a bit and 70 seems to be a safe and very cushy noise level as it is then not louder than the other fan. Does anyone of you know what's the other fan for and how I can control it too?
Well let's see what's left on my agenda.
I still have the problem that my sound keys were interepreted way too often. Could anyone of you please check that on your systems with xev and compare it with my output above?
And any other opinion on this thing?
Ok so it seems to be normal that the key only puts down the interface but not up again. I use just plain netcfg script and tried ifconfig wlan0 up after I pressed the button but I got a SIOCSIFADDR or something like that. Don't remember exactly.
Last edited by orschiro (2010-02-11 10:47:33)
Offline
Yes the keys are interpreted twice. Maybe you could ask the developer of lenovo-sl-laptop because the keys are controlled via this module....
Regarding the fan: what if you do some CPU intensive work for a longer time? The fan will stay at minimum RPM and the temperature will rise. Did you test this?
Sorry, can't say anything about WLAN because I always use a wired connection with this machine...
Offline
Yes the keys are interpreted twice. Maybe you could ask the developer of lenovo-sl-laptop because the keys are controlled via this module....
I sent the developer an email. I'll inform you about any further steps.
Regarding the fan: what if you do some CPU intensive work for a longer time? The fan will stay at minimum RPM and the temperature will rise. Did you test this?
Yes, I did some intensive work such as compiling, viewing flash and working with gimp beside that and the temperature did not rise more than 45 °C. Maximum could be 100 °C so I'm pretty comfortable with this setting. At last a quiet machine, wonderful.
Offline
Urfaust wrote:Yes the keys are interpreted twice. Maybe you could ask the developer of lenovo-sl-laptop because the keys are controlled via this module....
I sent the developer an email. I'll inform you about any further steps.
Thanks.
Regarding the fan: what if you do some CPU intensive work for a longer time? The fan will stay at minimum RPM and the temperature will rise. Did you test this?
Yes, I did some intensive work such as compiling, viewing flash and working with gimp beside that and the temperature did not rise more than 45 °C. Maximum could be 100 °C so I'm pretty comfortable with this setting. At last a quiet machine, wonderful.
Nice. I'll try that. The fan never bothered me but the more quiet the better it is.
Offline
Nice. I'll try that. The fan never bothered me but the more quiet the better it is.
Exactly.
So I assume the rest of the sound is coming from the mainboard fan? Do you know any way to control it too?
Ah and another thing. Does KMS work with the right resolution in tty? I get only about one fourth of the resolution during startup. When I start X everything is just fine. Please let me know what you configured to get it working.
You'll find further information here.
Last edited by orschiro (2010-02-13 10:16:19)
Offline
So I assume the rest of the sound is coming from the mainboard fan? Do you know any way to control it too?
No, sorry.
But what BIOS Version do you use? Maybe it's a good idea to upgrade to the latest....
Ah and another thing. Does KMS work with the right resolution in tty? I get only about one fourth of the resolution during startup. When I start X everything is just fine. Please let me know what you configured to get it working.
You'll find further information here.
As for KMS i did the following:
Add intel_agp and i915 modules to the MODULES line in /etc/mkinitcpio.conf
MODULES="intel_agp i915"
rebuild initramfs
# mkinitcpio -p kernel26
and adding
i915.modeset=1
to the kernel line in /boot/grub/menu.lst. You also have to remove the vga=773 parameter.
With that I don't have the native resolution while booting but very close to it.
Offline
Offline
Yeah, works flawlessly. Never had problems.
This my kernel line from menu.lst
kernel /vmlinuz26 root=/dev/disk/by-uuid/123456-7890-1234-5678-1234567890 ro acpi_backlight=vendor i915.modeset=1 logo.nologo
Last edited by Urfaust (2010-02-13 10:40:16)
Offline