Build tips

GRUB GRUB GRUB GRUB
symptom: The system does not go into grub, but instead chants GRUB GRUB GRUB GRUB ad infinitum. 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? ditch the hdd. we have more. --User:ideath 13:06, 12 May 2005 (PDT)

Hard drive clicks
symptom: cool noises solution: recycle that drive!

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

Hardware problems
When trying to enter BIOS, and you can't, try swapping out the IDE cables. ''I think this needs more detail. There are many cases when it is difficult to get into BIOS; i don't think i've seen one where the culprit was the IDE cables. -laurel''

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. KsCD ("Audio CD") recognizes the CD and looks like it's playing.

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

"device /dev/dsp can't be opened"
symptoms: when KDE starts, an error message pops up saying "Error while initializing the sound driver: device /dev/dsp can't be opened (no such device)". Then sound no work. Wah.

solution: in a FreekBox, this is generally a problem with the sound card (often an AE Vortex PCI sound card), which should be replaced, and the offending card given to Dave so he can figure out a good fix. If you're working on a non-Freekbox/Grantbox/Storebox system and have this problem, here's a method for troubleshooting /dev/dsp can't be opened.

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. 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)

X overdrives monitor
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 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.

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

Not detecting PCI modem (ttyS14)
symptoms: modem isn't found. or, modem shows up on the "serial" step in basiccheck (at ttyS14), but it doesn't respond when tested with the dialer. and anyway, what the heck is ttyS14? or - if the modem isn't found in the serial step (you only have one serial port detected), you can check if this applies using dmesg. try guest@freekbox:~$ dmesg | grep ttyS | less (this searches dmesg for lines that contain the string ttyS) and see if you have a line that refers to ttyS14. If you do, this is your issue.

solution: To talk to this modem, you gotta create ttyS14: guest@freekbox:~$ su freekbox:/home/guest# cd /dev freekbox:/dev# MAKEDEV ttyS14 freekbox:/dev# ln -s ttyS14 modem

CD Burners
CD burners are not a standard part of FreekBoxen, but some builders install them in their own computers. See: Installing a CD burner