Difference between revisions of "Dell Vostro 1000"

From ArchWiki
Jump to: navigation, search
(Backlight doesn't come back after Resume: aur template + out of date)
(remove beginners' guide link, see Talk:Installation guide#The Great Merge)
 
(13 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 
[[Category:Dell]]
 
[[Category:Dell]]
*'''Use Kernel 2.6.24 or greater'''
+
==Hardware==
*'''Use install disc 2008.03 or greater (see install)'''
+
 
+
'''Questions:''' IM diogo.urb@hotmail.com (MSN) .
+
 
+
=Hardware=
+
  
 
{|
 
{|
Line 14: Line 9:
 
| Ethernet || style="color:green" | '''Working''' || b44  
 
| Ethernet || style="color:green" | '''Working''' || b44  
 
|-
 
|-
| Wireless || style="color:green" | '''Working''' || [https://aur.archlinux.org/packages.php?ID=19514 wl], b43, ndiswrapper
+
| Wireless || style="color:green" | '''Working''' || {{AUR|broadcom-wl}}, b43, ndiswrapper
 
|-
 
|-
 
| Audio || style="color:green" | '''Working''' || snd_hda_intel
 
| Audio || style="color:green" | '''Working''' || snd_hda_intel
Line 25: Line 20:
 
|}
 
|}
  
=Problems=
+
==Problems==
  
=="Unknown Key Pressed"==
+
==="Unknown Key Pressed"===
 
* You may occasionally run across an error (occurring in an extremely high frequency) in your messages.log/dmesg:
 
* You may occasionally run across an error (occurring in an extremely high frequency) in your messages.log/dmesg:
  
Line 37: Line 32:
 
* Yet another suggested fix for the problem is updating your BIOS.. but since this is an extreme measure (found on the ubuntu forums.. so take it with a grain of salt), try the first two solutions before moving on to this potentially dangerous measure.
 
* Yet another suggested fix for the problem is updating your BIOS.. but since this is an extreme measure (found on the ubuntu forums.. so take it with a grain of salt), try the first two solutions before moving on to this potentially dangerous measure.
  
 
+
===High Temperature===
==Legacy Kernels==
+
*You must pass nolapic_timer as a boot option if you're using kernel 2.6.26 (not needed for 2.6.27)
+
 
+
 
+
==High Temperature==
+
 
After the installation you will see that the temperature is around 60°C (Too High). You can get the temperature through:
 
After the installation you will see that the temperature is around 60°C (Too High). You can get the temperature through:
  
Line 48: Line 38:
 
or
 
or
 
  cat /proc/acpi/thermal_zone/THM/temperature
 
  cat /proc/acpi/thermal_zone/THM/temperature
 
  
 
This is because the CPU frequency is at full usage always... so before continuing with the install process install '''cpufrequtils''', you can see further details on [[Cpufrequtils]]
 
This is because the CPU frequency is at full usage always... so before continuing with the install process install '''cpufrequtils''', you can see further details on [[Cpufrequtils]]
  
* Note: using lm_sensors 'sensors' utility, k8temp-pci-00c3 reports much more reasonable temperatures (more along the lines of what windows reports) compared to this Virtual Thermal Zone. [[User:Igneous| I]] have noticed no issues running without cpu scaling while on AC.
+
* Note: using lm_sensors 'sensors' utility, k8temp-pci-00c3 reports much more reasonable temperatures (more along the lines of what windows reports) compared to this Virtual Thermal Zone. [[User:Igneous|I]] have noticed no issues running without cpu scaling while on AC.
  
=Installation=
+
==Installation==
# Use installation disc 2008.03 or greater
+
Follow the [[Installation guide]].
# Follow the [[Beginners_Guide]]
+
  
=Xorg=
+
==Xorg==
  
==Xorg 7.4==
+
Follow [[Xorg]], [[Touchpad Synaptics]] and [[Extra keyboard keys]].
#Install xorg <pre>pacman -S xorg</pre>
+
#Install catalyst drivers <pre>pacman -S catalyst catalyst-utils</pre>
+
#Install Synaptic Mouse Driver <pre>pacman -S xf86-input-synaptics</pre>
+
#Copy and the paste the xorg configuration below and save it /etc/X11/xorg.conf<br>''As of right now, Xorg 7.4 crashes when trying to auto generate (X -configure) a configuration file.''
+
#Copy /usr/share/hal/fdi/policy/10osvendor/10-input-policy.fdi to /etc/hal/fdi/policy/<br>''No Modifications should have to be made''
+
#Follow the step below for the synaptic driver
+
  
===Sample xorg.conf===
+
==Wireless==
Section "InputDevice"
+
  Identifier "Keyboard"
+
  Driver "kbd"
+
  Option "CoreKeyboard"
+
  Option "XkbRules" "xorg"
+
  Option "XkbModel" "pc105"
+
  Option "XkbLayout" "us"
+
EndSection
+
+
Section "InputDevice"
+
  Identifier "Mouse0"
+
  Driver "evdev"
+
  Option "SencCoreEvents"
+
EndSection
+
+
Section "Device"
+
  Identifier "Card0"
+
  Driver "fglrx"
+
  BusID "PCI:1:5:0"
+
  VendorName "ATI Technologies Inc"
+
  BoardName "RS482 [Radeon Xpress 200]"
+
  BusID "PCI:1:5:0"
+
EndSection
+
+
Section "Monitor"
+
  Identifier "LCD Display"
+
  Option "DPMS"
+
EndSection
+
+
Section "Screen"
+
  Identifier "Screen0"
+
  Device "Card0"
+
  Monitor "LCD Display"
+
  DefaultDepth 24
+
EndSection
+
+
Section "ServerLayout"
+
  Identifier "Default Layout"
+
  Screen "Screen0"
+
  InputDevice "Keyboard"
+
  InputDevice "Mouse0"
+
EndSection
+
+
Section "DRI"
+
  Mode    0666
+
EndSection
+
  
===Touchpad===
+
Follow [[Wireless network configuration]] and [[Broadcom wireless]].
The following configuration gives a vertical scroll and one-tap click. Modify to suite your needs. The default file does not give you the scroll or one-tap click.
+
<br><br>
+
Copy ''/usr/share/hal/fdi/policy/10osvendor/11-x11-synaptics.fdi'' to /etc/hal/fdi/policy/''
+
<br><br>
+
Edit /etc/hal/fdi/policy/11-x11-synaptics.fdi and In between
+
<pre>
+
<match key="info.product" contains="Synaptics TouchPad">
+
<!--Insert the following here-->
+
</match>
+
</pre>
+
  
Insert:
+
==Suspend/Hibernate==
<pre>
+
<merge key="input.x11_options.Emulate3Buttons" type="string">true</merge>
+
<merge key="input.x11_options.SHMConfig" type="string">true</merge>
+
<merge key="input.x11_options.HorizEdgeScroll" type="string">false</merge>
+
<merge key="input.x11_options.HorizScrollDelta" type="string">100</merge>
+
<merge key="input.x11_options.TapButton1" type="string">1</merge>
+
<merge key="input.x11_options.VertEdgeScroll" type="string">true</merge>
+
<!--
+
  <merge key="input.x11_options.VertScrollDelta" type="string">100</merge>
+
-->
+
<merge key="input.x11_options.TapButton1" type="string">1</merge>
+
<merge key="input.x11_options.TapButton2" type="string">2</merge>
+
<merge key="input.x11_options.TapButton3" type="string">3</merge>
+
</pre>
+
 
+
 
+
 
+
===Function Keys===
+
To set the Functions keys you can use xmodmap. In xorg 7.4 the function keys are given keycodes. Xmodmap will bind the function key codes to a keysymname.
+
 
+
Create an .Xmodmap and put the following in:
+
keycode 123 = XF86AudioRaiseVolume
+
keycode 122 = XF86AudioLowerVolume
+
keycode 121 = XF86AudioMute
+
+
keycode 213 = XF86Sleep
+
keycode 246 = XF86Launch2
+
keycode 244 = XF86Launch3
+
keycode 170 = XF86Launch9
+
 
+
Next add ''xmodmap .Xmodmap'' to your start up
+
 
+
Then in your window manager you can bind the function key by providing the keysymname.  For example in openbox I just have to pass in the key name XF86AudioMute and provide the action I want preformed when I hit that key.
+
 
+
*Gnome users should be able to open up the keyboard-shortcuts and just hit the Function which they would like to use
+
 
+
=Wireless=
+
==b43==
+
Native Linux Driver - Works with kernels >= 2.6.25
+
 
+
Install b43
+
 
+
#Install b43 fwcutter <pre>pacman -S b43-fwcutter</pre>
+
#Download version 4.80.53.0 of Broadcom's proprietary driver. <pre>wget http://downloads.openwrt.org/sources/broadcom-wl-4.150.10.5.tar.bz2</pre>
+
#Unpack the compressed file.<pre>tar xvf broadcom-wl-4.150.10.5.tar.bz2</pre>
+
#Change the current directory to the newly created directory, and then further to the kmod folder: <pre>cd broadcom-wl-4.150.10.5/driver</pre>
+
#Run <pre>b43-fwcutter-011/b43-fwcutter -w "/lib/firmware/" wl_apsta_mimo.o</pre> You may have to create /lib/firmware first.
+
#Load b43 <pre>modprobe b43</pre>
+
#Edit rc.conf and add b43 <pre>MODULES=(... b43)</pre>
+
 
+
==wl==
+
Broadcom's Official Binary Wireless Driver
+
 
+
#Download the pkgbuild from AUR: {{AUR|broadcom-wl}}
+
#Extract the pkgbuild
+
#Run makepkg
+
#Run pacman -U broadcom-wl-5.10.27.6-6-${arch}.tar.gz
+
#modprobe wl
+
 
+
If you add wl to your MODULES=(... wl) make sure you blacklist b43 (Open Wireless) and b44 (Ethernet)
+
 
+
{{Box Note |'''''The ssb module must be unloaded for this module to work. When the b44 (Ethernet) module gets loaded, it loads sbb. This means you can only use wireless or Ethernet with this module, not both!.'''''}}
+
 
+
{{Box Note |'''''Currently appears that you can use both, wireless and ethernet. Just make sure your wireless network is loaded before the ethernet by adding the following in your rc.conf in the MODULES section: MODULES<nowiki>=</nowiki>(!b43 wl ...) !.'''''}}
+
 
+
==Ndiswrapper==
+
#Install ndiswrapper <pre>pacman -S ndiswrapper ndiswrapper-utils</pre>
+
#Download Dell Wireless Drivers: <pre>http://support.dell.com/support/downloads/download.aspx?c=us&cs=04&l=en&s=bsd&releaseid=R157039&SystemID=VOS_N_1000&servicetag=&os=WLH&osl=en&deviceid=9805&devlib=0&typecnt=0&vercnt=3&catid=-1&impid=-1&formatcnt=1&libid=5&fileid=209641</pre>
+
#Extract drivers using wine: <pre>wine R157039.EXE</pre>
+
#Move the drivers to your home directory <pre>cp -R /home/youruser/.wine/drive_c/DELL/R157039 /home/youruser/wirelessdrivers</pre>
+
#As root run: <pre>ndiswrapper -i bcmwl5.inf</pre>
+
#Run: <pre>ndiswrapper -l </pre> It should show something similar to: <pre> bcmwl5 : driver installed device (14E4:4311) present (alternate driver: bcm43xx)</pre>
+
#Run <pre>modprobe ndiswrapper</pre>
+
#Add ndiswrapper to your MODULES in rc.conf
+
 
+
==Wicd==
+
Wicd is a network manager which allows you to connect to wireless networks very easily, you can follow this wiki page [[Wicd]]
+
 
+
=Suspend/Hibernate=
+
 
* Suspend and Hibernate works with pm-utils
 
* Suspend and Hibernate works with pm-utils
* Also works by issuing <pre>echo mem > /sys/power/state</pre>
+
* Also works by issuing {{bc|echo mem > /sys/power/state}}
  
==Resume not working after suspend to RAM==
+
===Resume not working after suspend to RAM===
To workaround this issue edit the file <pre>/boot/grub/menu.lst</pre> and add the following to the kernel boot line: <pre>hpet=disable</pre>
+
To workaround this issue edit the file {{bc|/boot/grub/menu.lst}} and add the following to the kernel boot line: {{bc|1=hpet=disable}}
  
==Backlight doesn't come back after Resume==
+
===Backlight does not come back after Resume===
  
 
{{Out of date|radeontool no longer exists}}
 
{{Out of date|radeontool no longer exists}}
  
You may need a workaround because the backlight doesn't come back after Resuming.
+
You may need a workaround because the backlight does not come back after Resuming.
  
 
Install [[Pm-utils]], and create this file:
 
Install [[Pm-utils]], and create this file:
Line 246: Line 93:
 
  <nowiki>#</nowiki> chmod +x /etc/pm/sleep.d/radeonlight
 
  <nowiki>#</nowiki> chmod +x /etc/pm/sleep.d/radeonlight
  
Now to make it work you need {{AUR|radeontool}}.
+
Now to make it work you need {{Pkg|radeontool}}.
  
 
And '''DONE''', you can suspend and resume with pm-utils normally.
 
And '''DONE''', you can suspend and resume with pm-utils normally.
 
=Adjust Brightness=
 
Adjust normally with the FN Keys if your using the kernel 2.6.24 or greater
 

Latest revision as of 22:21, 26 August 2016

Hardware

Device Status Modules
Ati Radeon Xpress Working fglrx (cataylst), radeon
Ethernet Working b44
Wireless Working broadcom-wlAUR, b43, ndiswrapper
Audio Working snd_hda_intel
Modem Untested
PCMCIA Slot Untested
Card Reader Working

Problems

"Unknown Key Pressed"

  • You may occasionally run across an error (occurring in an extremely high frequency) in your messages.log/dmesg:
 atkbd.c: Unknown key pressed (translated set 2, code 0xee on isa0060/serio0).
 atkbd.c: Use 'setkeycodes e06e <keycode>' to make it known.
  • The fix for this issue is fairly simple. Power down your dell laptop, and reseat the battery.
  • Another possible cause may be due to your AC adapter being unplugged from the outlet, yet attached to the back of your laptop.
  • Yet another suggested fix for the problem is updating your BIOS.. but since this is an extreme measure (found on the ubuntu forums.. so take it with a grain of salt), try the first two solutions before moving on to this potentially dangerous measure.

High Temperature

After the installation you will see that the temperature is around 60°C (Too High). You can get the temperature through:

cat /proc/acpi/thermal_zone/THRM/temperature

or

cat /proc/acpi/thermal_zone/THM/temperature

This is because the CPU frequency is at full usage always... so before continuing with the install process install cpufrequtils, you can see further details on Cpufrequtils

  • Note: using lm_sensors 'sensors' utility, k8temp-pci-00c3 reports much more reasonable temperatures (more along the lines of what windows reports) compared to this Virtual Thermal Zone. I have noticed no issues running without cpu scaling while on AC.

Installation

Follow the Installation guide.

Xorg

Follow Xorg, Touchpad Synaptics and Extra keyboard keys.

Wireless

Follow Wireless network configuration and Broadcom wireless.

Suspend/Hibernate

  • Suspend and Hibernate works with pm-utils
  • Also works by issuing
    echo mem > /sys/power/state

Resume not working after suspend to RAM

To workaround this issue edit the file
/boot/grub/menu.lst
and add the following to the kernel boot line:
hpet=disable

Backlight does not come back after Resume

Tango-view-refresh-red.pngThis article or section is out of date.Tango-view-refresh-red.png

Reason: radeontool no longer exists (Discuss in Talk:Dell Vostro 1000#)

You may need a workaround because the backlight does not come back after Resuming.

Install Pm-utils, and create this file:

/etc/pm/sleep.d/radeonlight
#!/bin/bash
case $1 in
 hibernate)
  echo "Suspending to disk!"
 ;;
 suspend)
  echo "Suspending to RAM"
 ;;
 thaw)
  echo "Suspend to disk is over, Resuming. .."
 ;;
 resume)
  echo "Suspend to RAM is over, Resuming..."
  radeontool light on
  radeontool dac on
 ;;
 *)  echo "somebody is calling me totally wrong."
 ;;
esac
# chmod +x /etc/pm/sleep.d/radeonlight

Now to make it work you need radeontool.

And DONE, you can suspend and resume with pm-utils normally.