Difference between revisions of "Build tips"

From FreekiWiki
Jump to navigation Jump to search
 
(4 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
{{migrated}}
 +
 +
[https://docs.google.com/document/d/1h1iRNGDUydB6S1b7fTyfs1eTgrLyIvuTWnoKTHFEJXw/edit?usp=sharing Link]
 +
 
[[Category:Build]]
 
[[Category:Build]]
  
Line 4: Line 8:
  
 
==Hard drives==
 
==Hard drives==
===GRUB GRUB GRUB GRUB===
 
''symptom'': The system does not go into [[grub]], but instead chants GRUB GRUB GRUB GRUB ad infinitum.<br>
 
''solution'': Go into the [[BIOS]], change the hard drive detection from auto to user, and change LBA to LARGE. Dave says this works 90% of the time, and the remaining 10% might be able to be fixed with a BIOS upgrade but - who's got the time for that? switch the hdd. we have more. --[[User:ideath]] 13:06, 12 May 2005 (PDT)
 
 
 
===Hard drive clicks===
 
===Hard drive clicks===
 
''symptom'': cool noises<br>
 
''symptom'': cool noises<br>
Line 198: Line 198:
 
''solution 2:'' Hit escape when it says "GRUB loading" to get into the GRUB menu and hit 'e' to edit the first option. Then highlight the second line which stars "kernel /boot/vmlinuz..." and press 'e'. Insert "iommu=memapper=2" after "ro" and before "quiet splash", then press enter. Press 'b' to boot. Once you're in the operating system you will need to go to the terminal (Application > Accessories > Terminal) to save this command. Open up a terminal window and type in "sudo gedit /boot/grub/menu.lst". Scroll down to the first line that starts with "kernel /boot/vmlinuz..." (NOT the line that starts with #kernel) and insert "iommu=memapper=2" after "ro" and before "quiet splash" like before. Save and close the file. Type in "sudo update-grub" and hit enter. After GRUB is done updating, restart the computer to check if the issue has been solved. <br>
 
''solution 2:'' Hit escape when it says "GRUB loading" to get into the GRUB menu and hit 'e' to edit the first option. Then highlight the second line which stars "kernel /boot/vmlinuz..." and press 'e'. Insert "iommu=memapper=2" after "ro" and before "quiet splash", then press enter. Press 'b' to boot. Once you're in the operating system you will need to go to the terminal (Application > Accessories > Terminal) to save this command. Open up a terminal window and type in "sudo gedit /boot/grub/menu.lst". Scroll down to the first line that starts with "kernel /boot/vmlinuz..." (NOT the line that starts with #kernel) and insert "iommu=memapper=2" after "ro" and before "quiet splash" like before. Save and close the file. Type in "sudo update-grub" and hit enter. After GRUB is done updating, restart the computer to check if the issue has been solved. <br>
 
''solution 3:'' If all else fails, install a new video card. In 10.04, this is more common.  Please start [[Black_screen_10.04 | here.]]
 
''solution 3:'' If all else fails, install a new video card. In 10.04, this is more common.  Please start [[Black_screen_10.04 | here.]]
 +
 +
===1280x1024 mode is not available===
 +
''symptom:'' Ubuntu starts up in 1024x768 mode and 1280x1024 mode is not available in Preferences -> Monitors -> Resolution (as seen on some of the Dell Optiplex GX 620 small form factor computers <br>
 +
''solution:''
 +
* Add mode by creating xorg.conf in /etc/X11 (or modify existing). Note: this fix works under Lucid, other versions of Ubuntu have not been tested.
 +
* Add the following two sections to /etc/X11/xorg.conf to recognize 1280x1024 mode:
 +
Section "Monitor"
 +
Identifier "Configured Monitor"
 +
Modeline "1280x1024_60.00" 109.00 1280 1368 1496 1712 1024 1027 1034 1063 -hsync +vsync
 +
Option "PreferredMode" "1280x1024_60.00"
 +
EndSection
 +
 +
Section "Screen"
 +
Identifier "Default Screen"
 +
DefaultDepth 24
 +
SubSection "Display"
 +
Depth 24
 +
Modes "1280x1024_60.00"
 +
EndSubSection
 +
Monitor "Configured Monitor"
 +
EndSection
  
 
==Networking==
 
==Networking==

Latest revision as of 17:01, 14 May 2014

deletion

This page has been migrated to a document on Free Geek's Google Drive.

Information remaining behind may no longer be relevant.

MIGRATOR:

When you have tagged this page as migrated,
please add a link to the new document on Google Drive.

(Link to new page immediately below.)


Link

Tips for troubleshooting and repairing common problems that we see in the build workshops.

Hard drives

Hard drive clicks

symptom: cool noises
solution: recycle that drive!

SMART warning

symptom: the SMART utilities say the drive is gonna die solution: replace it. --User:ideath 13:06, 12 May 2005 (PDT)

fsck errors

see: Bad blocks hard drive Usually a bad drive.

Can't find or boot hard drive

  • Make sure you are jumpered master and are connected to the primary ide port.
  • Make sure BIOS detects it or is set to AUTO.
  • Try another IDE cable.


BIOS problems

Password lock

With the power off: Remove the button battery. Also, look for a jumper on the motherboard that says either clear CMOS or clear password. Move the jumper over, say "Mary had a little lamb" (i.e. wait a few seconds), put the jumper and battery back and power back up. (if you've got a stubborn one, you might have to power cycle the computer with the battery gone and jumper set before putting them back).

Entering BIOS config

symptom: cannot get into BIOS

When trying to enter BIOS, and you can't, try the following:

  • press all of the function keys and the delete key while the computer is POSTing.
  • modify the hardware somehow, changed the memory or disconnect a drive

symptom: cannot get into BIOS and computer beeping

When the computer is beeping, but not posting:

  • Figure out the BIOS manufacturer by looking at the BIOS chip on the motherboard.
  • Check the beep code you are receiving with the list of known beep codes.

Old BIOS: How to update (flash)

Most systems can only flash from DOS or Windows. Freedos can be booted from a CD and the BIOS flashing program can be run. Freedos .iso can be obtained from the freedos site. Note that freedos can access thumbdrives, so the easiest way is to download the flashing program (a .exe file) and the BIOS data to a thumbdrive. Note that the BIOS flashing program and BIOS files are specific to the motherboard.

Step 1: Run the BIOS flashing program and save a copy of the existing BIOS code on the thumbdrive.

Step 2: Run again and flash the BIOS.

Note that if the BIOS flashing operation is interrupted, it will most likely leave the machine in an unusable state. New version of BIOS aren't always the best, which is why it's important to make a copy of the existing BIOS so it can be restored if needed.

Useful DOS commands. Note that DOS uses the backslash (\) for the directory separator.

ls or dir for directory listings.

cd for change directory

<drive letter>: to change drive, e.g. B:

type <file name> displays contents on the screen

The boot CD will be the A: drive, the thumbdrive will most likely be the B: drive.


Sound

Not finding sound card

symptoms: message reading "/dev/dsp can't be found"; onboard sound; IRQ 5 has nothing on it; alsaconf doesn't detect a PCI or PNP soundcard. This happened on two Dell Optiplexes.
solution: Google says they use a Crystal ISA sound card, which was an option in alsaconf. You may be able to find information about the sound chip used for your onboard sound. --User:ideath 13:06, 12 May 2005 (PDT)

Won't play audio CDs

symptoms: the audio test in basiccheck plays sound, but you don't get any sound from an audio CD. solution: make sure the cable from the sound card to the CDROM is plugged in to both; double check if there are multiple places it can plug into the sound card and look for labels that might give you clues; try a different cable if it still doesn't work. --User:ideath

  • You might also want to try right-clicking on the speaker symbol on the top right of the screen and choosing "Preferences". Make sure nothing's muted.
  • Or, open a terminal and type "alsamixer". Make sure everything's turned on and up. Open another terminal and type "man alsamixer" for instructions on how to use this command-line tool.

Plays audio cds and files, but not with aplay (basiccheck)

  • Try disabling plug-and-play option in BIOS if it exists.
  • If you're using a sound card, you may need to disable an on-board sound option in BIOS if it exists.

Video

Read Xorg for general information.

Radeon mobility U1 chipset: slow compiz/glxgears = drm issues in X (HP laptops and some others)

symptoms: serious lagging which grows worse the more the computer is used: menu highlights and window sizes change slowly.

  • test for this problem:
sudo apt-get install mesa-utils
glxinfo | grep render
    • if it reports "Direct Rendering: No," make sure:
      1. we are using the 'radeon' driver not 'ati' or 'fglrx'. we have good support for this chipset using the open drivers.
      2. we are loading the correct kernel modules:
lsmod | grep radeon
      • we are looking for radeon and radeonfb
      1. we are finding the correct modules when X starts:
less /var/log/Xorg.0.log
    • if it reports "Direct Randering: Yes," try
glxgears
      • an FPS under 250 means we are still using the software raterizer = (

explanation: X is loading the necessary modules for direct rendering but the kernel reports an incomplete device state for the video chip. something about this particular chipset makes the kernel not quite expect it. X expects either an old version of the radeon module (<=1.1) or a new version and KMS (kernel modesetting) to configure the state that X will use for the rest of our uptime.

solution: we like our current module version (~2.0), so we need for this module configure itself during boot. we should poll ALL devices connected to the USB so our chipset is recognized and the module is automatically loaded.

sudo nano -w /etc/default/grub

add "irqpoll" option

"splash quiet irqpoll"

update grub.cnf

sudo update-grub

reboot

sudo reboot

glxgears should now get framerates of ~1000

Lucid intel video chipset black screen on boot ( broken driver for many dells )

symptoms: The boot splash loads fine but then the screen goes black and you cannot CTL-ALT-Fkey to and other terminal.

solution: go to the ever changing solutions page: https://wiki.ubuntu.com/X/Bugs/Lucidi8xxFreezes

Lucid goes to white screen of Nirvana on boot

symptom: After a normal POST and splash screen, some HP laptops gradually fade to white
solution: Reboot and hold shift down after POST to bring up the grub menu. Edit the main boot line and add "nomodeset" after "quiet splash". Hit Ctrl-x for a one-time boot using the revised boot command. If you get a normal login screen, then the command worked and you need to make it permanent. Login, open a terminal window and type "sudo gedit /etc/default/grub". Find the line that contains "quiet splash" and add "nomodeset" right after it. Save the changes and close the file. Type: "sudo update-grub" and hit enter. After grub is done updating, restart the computer to check that the problem has been solved.(Alternatively, if "nomodeset" doesn't work, try "i915.modeset=1" or "i915.modeset=0" or "xforcevesa"

X tries to start & fails

symptoms: you get the grey screen as if kdm were starting, but it eventually blinks out and drops you to the text login.keyboard and mouse are PS/2
solution: make sure the mouse is plugged in properly and in the correct port and reboot. X won't start if it doesn't think it has a mouse. --User:ideath 13:06, 12 May 2005 (PDT)

symptoms: you're returned to the console with the message "no screens found" and you're using certain kinds of ATI card (including the Riva128 card)
solution: Change the default color depth to 15, in /etc/X11/XF86Config-4 --User:Jeff

X won't start; video driver for onboard chip identified as "unknown"

Video problem with onboard video chip : VIA Technologies, Inc. VT8623 [Apollo CLE266] integrated CastleRock graphics (rev 03).
solution: Change the driver to via in /etc/X11/XF86Config-4 Jeff 03:13, 6 Aug 2005 (PDT)
second solution: Change the driver to vesa in /etc/X11/XF86Config-4 if via doesn't work. Jeff 03:14, 6 Aug 2005 (PDT)

Resolution is too small

symptoms: 640x480 screen resolution

solution:

  • System -> Preferences -> Screen Resolution
  • set resolution to a larger value

symptoms: 640x480 is the only available resolution

solution:

  • sudo dpkg-reconfigure xserver-xorg: choose the defaults for the everything but the last question about monitors "Simple/Medium/Advanced".
  • Choose simple
  • then choose 17 inches
  • Choose defaults until finished
  • Ctl-Alt-Bksp to restart X.

symptoms: trying the above causes the system to lock up

solution:

  • Ctl-Alt-F1
  • login as oem
  • sudo /etc/init.d/gdm stop
  • permform the same steps as above
  • sudo /etc/init.d/gdm start


Note: In old systems, using a PCI video card may be contributing to the problem. Try an AGP video card if possible.

X overdrives monitor

symptoms: monitor presents high frequency scan lines

solution: turn down the bit depth to 16

symptoms: monitor presents high frequency scan lines and displays squished version of X

solution: check for IRQ conflict and set IRQ 3 only to legacy. Magix identified the chip but chose "unknown" driver. X wouldn't start. When we substituted "via" for "unknown" in the /etc/X11/XF86Config-4 file, x windows would start but the only resolution we could get was 600x480. A bunch of googling later we tried "vesa" for the driver and kdm worked fine. --Roy Marshall

symptoms: everything's fine until you try to go into X; then the monitor says FREQ OUT OF RANGE. it's the first time this previously-configured system has been used with this particular monitor.

solution: run magix to reconfigure X with the proper frequencies.

Onboard VGA does not function

symptom: Upon power-on, system sends nothing to VGA on-board port, connected monitor does not indicate anything is connected. This has occurred with several Dell small form factor systems.

solution: Install VGA card, load system and switch VGA cable to the on-board port at reboot time. Problem solved (sometimes). -- Kerm Jensen solution 2: Turn on-board video back on in the bios.

Sign-on Screen Return Problem

symptom: The symptom keeps returning to the sign-in screen after the user has signed in.
solution 1: Look in BIOS to see if the UMA (internal video mode) frame buffer size can be changed, and try changing it to 16 MB. The AGP aperture can be left at 64 MB.
solution 2: Install a new video card!

Goes to black screen

symptom: The system goes to a black screen
solution 1: Go into BIOS. Find "AGP Aperture" and set it to 32 MB. Save and exit BIOS.
solution 2: Press Escape after the system POSTs to get into the GRUB menu. Choose the second option (recovery mode). A bunch of scripts will run, then choose "xfix" from the menu. Once xfix has run, choose resume boot to boot normally. solution 2: Hit escape when it says "GRUB loading" to get into the GRUB menu and hit 'e' to edit the first option. Then highlight the second line which stars "kernel /boot/vmlinuz..." and press 'e'. Insert "iommu=memapper=2" after "ro" and before "quiet splash", then press enter. Press 'b' to boot. Once you're in the operating system you will need to go to the terminal (Application > Accessories > Terminal) to save this command. Open up a terminal window and type in "sudo gedit /boot/grub/menu.lst". Scroll down to the first line that starts with "kernel /boot/vmlinuz..." (NOT the line that starts with #kernel) and insert "iommu=memapper=2" after "ro" and before "quiet splash" like before. Save and close the file. Type in "sudo update-grub" and hit enter. After GRUB is done updating, restart the computer to check if the issue has been solved.
solution 3: If all else fails, install a new video card. In 10.04, this is more common. Please start here.

1280x1024 mode is not available

symptom: Ubuntu starts up in 1024x768 mode and 1280x1024 mode is not available in Preferences -> Monitors -> Resolution (as seen on some of the Dell Optiplex GX 620 small form factor computers
solution:

  • Add mode by creating xorg.conf in /etc/X11 (or modify existing). Note: this fix works under Lucid, other versions of Ubuntu have not been tested.
  • Add the following two sections to /etc/X11/xorg.conf to recognize 1280x1024 mode:
Section "Monitor"
Identifier "Configured Monitor"
Modeline "1280x1024_60.00" 109.00 1280 1368 1496 1712 1024 1027 1034 1063 -hsync +vsync
Option "PreferredMode" "1280x1024_60.00"
EndSection

Section "Screen"
Identifier "Default Screen"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1280x1024_60.00"
EndSubSection
Monitor "Configured Monitor"
EndSection

Networking

Flaky ethernet card

symptom: the computer can't connect to the network after it's been imaged.

solution: Some ethernet cards will work to install the image, but not to connect from the OS. I generally end up swapping out the NIC and it will work fine. -- MW

Modems

see:

CD Drives

Troubleshooting

CD Drive not being recognized? First, check all of your connections, are they are secure?

  • Is the jumper set to master?* Check the BIOS and make sure there isn't a misconfiguration.
  • Open up a terminal, and run "dmesg | grep hd"--does anything come up on hdc?
  • Finally, you may have a bad cable, try attaching a new one to the motherboard.
  • If all this fails, grab a new CD drive and start over, going through all these steps. If your result is the same, you may have a bad CD controller, or IDE connection, consult a Build instructor.

note: if the jumper is set to slave, you'll probably have trouble even booting up.

Printing

Problem: When trying to print the printme, there's no "Build" computer to print to.
Solution: Go to System > Administration > Printing. Select the first box which reads "Show all printers in the network." Give it a minute and all the printers in the network, including the Build printer, will populate.

Extras

System won't shut down

symptom: The system is not shutting down completely
solution 1.0: The problem is that a sound module fails to unload during shut down, preventing the machine from doing so. To fix this you need to remove the sound module in question in the command line terminal. first see if the module is loaded.

lsmod

and look for snd_hda_intel. If it exists, go to

Applications > Accessories > Terminal and type in "sudo gedit /etc/init.d/halt". After the first set of comments (signified by the #) add

rmmod snd_hda_intel. This will remove the troublesome sound module.

solution 2.0: If the above doesn't work, try

"sudo gedit /etc/modules" and adding "apm power_off=1".

System Panel is Missing Buttons

from External Blog
Open a Terminal and type the following
$ gconftool –recursive-unset /apps/panel (All panels will disappear)
$ rm -rf ~/.gconf/apps/panel
$ pkill gnome-panel

Partially Disappearing System Panels

  • In a terminal, type "killall gnome-panel"

Pin-Out Settings for External Front Panel USB

+ Front Panel USB pin-Out order - VCC 1 Data -1 Data +1 Ground Not Used - 2 (red) 4 (white) 6 (green) 8 (black) 10 - 1 (red) 3 (white) 5 (green) 7 (black) BLANK - VCC 1 Data -1 Data +1 Ground KEY

Other Helpful Links