Limitations and How To's for SUSE Linux Enterprise Desktop 10 - ThinkPad T60p
General limitations:
Features/Functions not supported
System may not boot when changing the setting of Serial ATA (SATA) in the BIOS Setup Utility
SaX2 may not deactivate Touchpad
Docking the system may switch the display to DVI+CRT


Ethernet limitations:

Ethernet driver (Intel PRO/1000 LAN adapter) may not load under Linux when ethernet cable is not attached

Video limitations and configurations:

How to change display resolution using aticonfig
How to Make a Hotkey for screen switching from LCD to CRT+DVI in Big desktop mode
SaX2 does not work correctly with ATI video driver
Fn+F7 Display Switching may not work
Task bar is not moved to External Display with Big Desktop Reverse
Console text may be garbled and unreadable


Wireless limitations and configurations:
11a hidden
Roaming fails when two Access Points are in different network segments
Roaming may fail when the new Access Point will not be quickly found in range
Changing connection to hidden WPA
Connection after Suspend/Resume


Power management limitations:
Suspend to RAM may be rejected with USB storage device
System may not wake up when PCMCIA storage card is removed during Suspend to RAM state
USB CD-ROM/DVD drive may not be recognized when attached to the system in Suspend to RAM state
Some devices on docking station may not work after hot/warm docking
Ultrabay devices may not work after hot/warm swapping
Express card may not work after hot/warm plug
USB floppy disk drive may not be recognized unless mounted manually


Access Connections limitations:
Access Connections and Fn+F5 OnScreen Applet may not disable Wireless WAN Adapter
Adhoc profile shows as connected even after disconnected
Access Connections may not connect to no WEP AP from Find Wireless Network option
Access Connections may not support Roaming of Wired network


Additional information:
SUSE Linux Enterprise Desktop 10 installation instructions


Features/Functions not supported
The following features/functions are not supported.
  • Fingerprint Reader
  • ThinkVantage Active Protection System
  • Wireless WAN Adapter
    Note: Disabling Wireless WAN adapter is recommended.
  • ThinkVantage Button
  • Hotkeys: Fn+F2 and Fn+F8
    Note: Supported functions for SUSE Linux are:
    • Fn+F3 Power Scheme Control
    • Fn+F4 Suspend To RAM
    • Fn+F5 Radio On/Off Control
    • Fn+F7 Display Switching
    • Fn+F12 Suspend To Disk

     

System may not boot when changing the setting of Serial ATA (SATA) in the BIOS Setup Utility
Symptom
If you change the setting of Serial ATA (SATA) in the BIOS Setup Utility after installation, your computer will not respond during boot process.

Solution
Restore the setting Serial ATA (SATA) in the BIOS Setup Utility.
  1. Start the BIOS Setup Utility menu.
  2. Select Config.
  3. Select Serial ATA (SATA).
  4. Restore the setting to AHCI or Compatibility.
  5. Restart your computer.

Back to top


SaX2 may not deactivate Touchpad
Symptom
You may not be able to disable Touchpad device using SaX2.

Solution
You can use ThinkPad Configuration instead of SaX2.
  1. Launch ThinkPad Configuration from Kmenu, ThinkVantage.
  2. Click Touch Pad from the panel to the left side. The TouchPad window is displayed.
  3. In the combo box, choose Disable.
  4. Click Apply button.

 

Back to top


How to change display resolution using aticonfig
  1. In a terminal window, use the su (switch user) command to obtain root privileges.
  2. Type aticonfig --resolution=screen#, W1xH1,W2xH2,W3xH3,…
  3. Press Alt+Enter to restart X-server.
    Note: Screens starts at 0. You can use 1 for screen#2 in dual-head mode. Do not put space after the comma.
    • Example 1. aticonfig --resolution=0,800x600 (This will change your screen#1 to 800x600 resolution)
    • Example 2. aticonfig --resolution=1,1024x768 (Assuming the system is in Dual-head mode, this will set your screen#2 resolution to 1024x768.)

     

Back to top


How to Make a Hotkey for screen switching from LCD to CRT+DVI in Big desktop mode
Note: This behavior currently has been tested with and assumes that all monitors are capable of matching the panel native resolution. For ThinkPad T60p system, it is 1600x1200. The behavior with different resolutions is undefined at this stage and will possibly expose problems in the implementation.
  1. In a terminal window, use the su (switch user) command to obtain root privileges.
  2. Type aticonfig --dtop=horizontal to explicitly configure the system to Big desktop.
  3. Go to K Menu > Logout, and select Restart Computer to apply change in xorg,.conf.
  4. Create a script file that will enable CRT and DVI in big desktop mode. The example below is a script file that will automatically switch CRT+DVI as display device. The "xrandr -s 3200x1200" will change the resolution 3200x1200 (assuming both CRT and DVI to be UXGA) setting the system to big desktop.
    For example, content of script file:
    #!/bin/bash
    aticonfig --enable-monitor=crt1,tmds1
    xrandr -s 3200x1200
    exit
    Note: To display all possible resolutions, run "xrandr" in konsole.
  5. Save the script file to your desired directory. Example: /usr/lib/powersave/scripts/. This is the same directory with thinkpad_acpi_events.
  6. Run in console "chmod +x (name of script file)
  7. Go to /usr/lib/powersave/scripts.
  8. Open "thinkpad_acpi_events" file with a text editor.
  9. Look for "HOTKEY="Fn+F6"" text.
  10. Add the following lines "run_on_xserver "/usr/lib/powersave/scripts/" (name of script file)
    &". Then add ";;" at the next line. It should look like this:
    4102) HOTKEY="Fn+F6"
    run_on_xserver "/usr/lib/powersave/scripts/(name of script file) " &
    ;;
  11. Exit and save the thinkpad_acpi_events script.
  12. Fn+F6 should now be able to switch from LCD to CRT+DVI as Big Desktop.

To go back to LCD, press Fn+F7.

 

Back to top


SaX2 does not work correctly with ATI video driver
Symptom
  • After installation of ATI Video driver, clicking Graphics Card and Monitor, Keyboard Layout, Mouse Model from YaST Control Center will prompt an error "Cannot Deactivate All Displays. At least one display must be active."
  • After installation of ATI driver, Video Card name property still shows the generic video driver (VESA Framebuffer Graphics).
  • Display Resolution shown in SaX2 and Configure-KDesktop are different.

Solution
Click OK to close the message window.
To configure ATI video use ATI control or aticonfig command

Back to top


Fn+F7 Display Switching may not work
Symptom
Display switching function using Fn+F7 may not work.

Solution
Remove garbage files in /var/lib/xdm/authdir/authfiles/.
  1. In a terminal window, type su (switch user) command to obtain root privileges.
  2. Type rm /var/lib/xdm/authdir/authfiles/*
  3. Go to K Menu > Logout, and select Restart Computer.


Back to top


Task bar is not moved to External Display with Big Desktop Reverse
Symptom
When executing aticonfig --dtop=horizontal,reverse, all icons are transferred to an external Display. However, the taskbar is still on the LCD.

Solution
  1. In a terminal window, use the su (switch user) command to obtain root privileges.
  2. Type aticonfig --dtop=horizontal to configure the system to be in big desktop, instead of "aticonfig --dtop=horizontal,reverse
  3. Press CTRL+ALT+BACKSPACE to restart X-Server.
  4. In a terminal window, use the su (switch user) command to obtain root privileges.
  5. Type aticonfig –swap to swap screen 0 with screen 1 with the taskbar.


Back to top


Console text may be garbled and unreadable
Symptom
Text is unreadable when booting to console mode (ie: Ctrl-Alt F1), or when shutting down the system..

Solution
Change the vga= option of the grub kernel boot parameters.

Warning: Manually editing the boot configuration files can cause your system to become unbootable. Follow these directions carefully, and always have a recent backup available.
  1. Start the YaST tool Kmenu -> System -> YaST. You will be promoted for the root password.
  2. In the left menu choose System.
  3. In the right menu choose Boot Loader.
  4. At the Boot Loader Settings screen, make sure the Label SUSE Linux Enterprise Desktop 10 is highlighted (it should also have a check mark in the Def. column) and then click the Edit button.
  5. In the box VGA Mode change the value to 0x317.
  6. Click OK, and then Finish. The settings will be saved. Reboot to have the settings take effect.
Back to top


Docking the system may switch the display to DVI+CRT

Symptom
If DVI and CRT is detected/connected after docking the system, display will switch to DVI and CRT in clone mode.

Solution
After docking the system, press Fn+F7 to switch the display back to LCD.

 

Back to top


Ethernet driver (Intel PRO/1000 LAN adapter) may not load under Linux when ethernet cable is not attached

Symptom
Ethernet driver (Intel PRO/1000 LAN adapter) may not be loaded intermittently when your system boots up without Ethernet cable attached.

Solution

  1. Start SUSE Linux Enterprise Desktop 10 with Ethernet cable attached.
  2. In a terminal window, use the su (switch user) command to obtain root privileges.
  3. Copy the attached script to the hard drive, for example, /home/drivers directory.
  4. Change directory to the location where you saved the file.
  5. Type './vidalia-eeprom-mod-script eth0'.
  6. Shutdown and reboot your system.

Note: Please attach Ethernet cable so 'eth0' is available.

Click here to download vidalia-eeprom-mod-script.

 

Back to top


11a hidden
Symptom
Cannot establish wireless LAN connection with 802.11a Access Point when ESSID is not set to broadcast.

Solution
In a terminal window, use the su (switch user) command to obtain root privileges.
Type ‘iwpriv eth1 set_mode 1’ to establish the connection.


Back to top


Roaming fails when two Access Points are in different network segments

Symptom
Roaming fails when two Access Points are in different network segments. It will associate properly (so it seems connected), but the IP address will not be properly reset (so in fact, it is disconnected from network).

Solution
If using Access Connections, reconnect by clicking Disconnect button, and then Connect button.
If using YaST2, you may do any of the following:

  1. You may run the YaST2 Utility again (without changing the settings) to reconnect.
  2. Or in a terminal window, use the su (switch user) to obtain root privileges. Type ‘ifdown ethx’ and ‘ifup ethx’ to initialize network adapter (where ethx indicates the ipw3945 WirelessLAN adapter for example, eth1)
Back to top


Roaming may fail when the new Access Point will not be quickly found in range
Symptom
When using KNetworkManager, roaming may fail when the new Access Point will not be quickly found in range, resulting to disconnection.

Solution
Wait until the new Access Point will be detected by KNetworkManager, and then connect to it by choosing it among the list of detected networks. Otherwise, when the ESSID is hidden, reconnect to network by entering its profile details and connecting again.


Back to top


Changing connection to hidden WPA
Symptom
When trying to change connection to a network with WPA feature enabled, and with ESSID not set to broadcast, the new connection may not be established.

Solution
If using Access Connections, the wireless settings can be changed by clicking the Disconnect button, choosing the desired profile/setting to be used for the new connection, and then by clicking the Connect button. If using YaST2, use the su (switch user) command in a terminal window to obtain root privileges. Type ‘modprobe –r ipw3945’ and ‘modprobe ipw3945’ to reload the ipw3945 driver and establish the new connection. (Or you may use Access Connections instead as a workaround, if you do not have root privileges.)


Back to top


Connection after Suspend/Resume
Symptom
Connection intermittently fails after resuming system from suspend.

Solution
If using Access Connections, Access Connections will try to reconnect to the network when the system is resumed. In case it still fails to re-establish the connection, turn off and on the Wireless radio by Fn+F5 key (or Global switch) to reestablish the connection.


Back to top


Suspend to RAM may be rejected with USB storage device
Symptom
An error message “suspend2ram failed on unloading usb_storage. Trying to recover…” will be displayed when the system tries to Suspend to RAM with a USB storage device attached.

Solution
Unmount the USB storage device before Suspend to RAM.
  1. Click OK to close the message window
  2. Open Konqueror
  3. Click Storage Media
  4. Right-click the USB storage device
  5. Choose Safely Remove option. You may now proceed with suspend to ram. Please confirm Suspend LED of the system is turned on.

 

Back to top


System may not wake up when PCMCIA storage card is removed during Suspend to RAM state
Symptom
Cannot wake up from suspend to ram when a PCMCIA storage card that was attached to the system before suspending to ram is removed before wakeup.

Solution
If you want to remove the drive before wake up, unmount and detach it before suspending to ram.


Back to top


USB CD-ROM/DVD drive may not be recognized when attached to the system in Suspend to RAM state
Symptom
If a USB CD-ROM/DVD drive is attached to a system in Suspend to RAM state, it may not be detected after waking up.

Solution
Remove the USB CD-ROM/DVD and attach it again while the system is running.


Back to top


Some devices on docking station may not work after hot/warm docking
Symptom
Under SUSE Linux, attaching a system to a docking station while the system is running - hot docking- is not supported. USB devices, PCI express card and Serial port and Parallel port on the docking station do not work after hot-docking.
Attaching a system to a docking station while the system is in Suspend to RAM or Suspend to Disk state - warm docking - is partially supported. PCI express card, Serial port and Parallel port on the docking station do not work after warm docking.

Solution
  1. Enter a system into Suspend to RAM state using Fn+F4 key.
  2. Attach the system to a docking station
  3. Wake up the system using Fn key.
  4. USB devices attached to the docking station work.

Note: PCI express card, Serial port and Parallel port on the docking station do not work. Restart SUSE Linux Enterprise Desktop 10 to make all devices work.

Back to top


Ultrabay devices may not work after hot/warm swapping
Symptom
Under SUSE Linux, attaching/detaching a bay device to/from Ultrabay while the system is running (hot swap) or while the system is in Suspend to RAM or Suspend to Disk state (warm swap) is not supported. The Ultrabay device may not work after hot swap or warm swap.

Solution
Shutdown your system and replace a bay device (cold swap). Then, start SUSE Linux.

 

Back to top


Express card may not work after hot/warm plug
Symptom
Under SUSE Linux, attaching/detaching an Express Card to/from Express Card slot while the system is running (hot plug) or while the system is in Suspend to RAM or Suspend to Disk state (warm plug) is not supported. The Express Card may not work after hot plug or warm plug.

Solution
Shutdown your system and replace a bay device (cold swap). Then, start SUSE Linux.


Back to top


USB floppy disk drive may not be recognized unless mounted manually
Symptom
An error message “Method “Mount” with signature “ssas” on interface” is displayed when accessing to USB floppy disk drive (FDD).

Solution
Mount USB FDD manually:
  1. In a terminal window, use the su (switch user) command to obtain root privileges.
  2. Create a mount point with ‘md (mount point)'
  3. Mount USB FDD manually with 'mount /dev/sdX (mount point)'
    Note: Replace X with the correct letter corresponding to the next SCSI device on your system.

Back to top


Access Connections and Fn+F5 OnScreen Applet may not disable Wireless WAN Adapter
Symptom
Access Connections and Fn+F5 OnScreen Applet may not disable Wireless WAN adapter when Disable All Wireless Devices is checked.

Solution
Disable Wireless LAN Adapter through BIOS setup. Wireless WAN adapter is not supported on SUSE Linux.


Back to top


Adhoc profile shows as connected even after disconnected
Symptom
Access Connections Status icon still shows as connected for ad-hoc profile even when disconnected from another system.

Solution
Disconnect manually or restart the system


Back to top


Access Connections may not connect to no WEP AP from Find Wireless Network option
Symptom
Access Connections Status icon still shows as connected for ad-hoc profile even when disconnected from another system.

Solution
Select Yes.


Back to top


Access Connections may not support Roaming of Wired network
Symptom
Access Connections Status icon still shows as connected for ad-hoc profile even when disconnected from another system.

Solution
Disconnect manually or restart the system


If you are unable to find what you are looking for, please do try the following options:
1. Lenovo Assisted Search
2. Product usage and general troubleshooting tips
3. Lenovo Support Forum
4. Technical Support Call Centre

Country Availability
AvailableWorldwide
Document ID : HT005338
Legacy Document ID : MIGR-65328
Last Updated :
Copyright © Lenovo 2013, all rights reserved
Was this page helpful to you?YesNo


   
Select Task
 
Drivers & Software  
Guides & Manuals  
Diagnose & Fix  
Warranty & Services  
Parts  
Accessories  

DRIVER RESOURCES
Support Help Index
Driver Matrix
Drivers for LenovoEMC Storage
Newly Released Drivers (RSS)
Update your THINK product
ThinkVantage Tools
Solutions Center
Assisted Search
Popular Solutions
Microsoft Solutions
Self-Diagnose Tool
Community
KnowledgeBase Featured Articles
Community KnowledgeBase
Community Forums
Lenovo EMC
Windows 8 Support