Difference between revisions of "Build tips"
(→Video: added info on overdrive/over frequency.) |
|||
Line 44: | Line 44: | ||
freekbox:/dev# MAKEDEV ttyS14 | freekbox:/dev# MAKEDEV ttyS14 | ||
freekbox:/dev# ln -s ttyS14 modem | freekbox:/dev# ln -s ttyS14 modem | ||
+ | |||
+ | ==CDROM== |
Revision as of 11:58, 17 June 2005
Hard drives
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)
bad cables
When trying to enter Bios, and you can't try swaping out the IDE cables.
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)
Video
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)
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).
X overdives 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
Networking
Modems
Not detecting PCI modem (ttyS14)
symptoms: modem isn't found. or, modem shows up on the "serial" step in basiccheck (at ttyS14), but modem doesn't respond. and anyway, what the heck is ttyS14?
solution: 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:~$ grep dmesg 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. 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