Buchan Milne <[EMAIL PROTECTED]> writes:
camille: i spam you too since that information may be useful for our
doc too (but sadly not using proper english and maybe too
technical and definitively too late for mdk9.2 :-(
till: can you add a section about adding support for a new printer ?
> > C) the resolution picked by Xdrak is 1044 X 768 but it appears as
> > 1280 x 1044 even if tried to change the resolution and restarting
> > X in still wrong and don't want to be changed
> >
> > i have ATI radeon 7500 mobility with 64mb and pentium 4 2.0ghz
>
> Thierry, don't you want to add a wiki topic "How to get your
> hardware recognised in Mandrake" (or a shorter one ;-)) which
> includes the info you post when people ask things like this?
as i'm not a wiki guru, i'll just offer the following piece of chapter
and let someone integrate in the cooker howto (i don't want to fsck up
the current organization):
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> (to be further completed)
* How to get your hardware recognised or better configured in Mandrake
** Monitors
monitors belongs in two categories:
- those who are properly detected trough ddc probing (so called "plug
'n play").
- those who are not.
note that proper ddc probing support needs both monitor *and* graphic
cart support in hardware.
for the laters, we can reference them by adding proper lines to
/usr/share/ldetect-lst/MonitorsDB.
format is "VendorName; ModelName; EISA_ID; HorizSync_Range; VertRefresh_Range;
dpms_support?"
such as "Hewlett-Packard; A4575A 19inch Display; 0; 30-107; 50-160; 1"
you can get your monitor's EISA ID by running the following command:
ddcxinfos | fgrep -i eisa
you can get the proper horizontal and vertical frequencie ranges from
your monitor manual. this manual will also tell you if your monitor
support power saving (the dpms flag).
if you post a mail with the right line[1] to add to the monitors db on
the cooker mailling list with subject "[hardware] XYZ monitor", we can
add support for your monitor.
[1] that is with the proper frequencie ranges (and the EISA ID if
possible)
note that the "not supporting ddc probing" monitors belongs to two
categories:
- those who have an eisa id
- those who have not.
the formers will be automatically preselected in the monitors list,
the laters won't be (one will have to manually select the right
monitor).
** Sound Cards
if your sound card is not working smoothly under mandrake linux,
follow the steps described in the troubleshooting window in draksound,
that is:
classic bug sound tester (we really should morph the trouble shooting
window in a "solve sound problem" tool merged with sndconfig...):
*** "lspcidrake -v | fgrep AUDIO" will tell you which driver your pci
card use by default (and if your card is detected)
if your card is an usb one, just type "lspcidrake -v".
if there's no driver, go look at the "pci devices" section in order to
fix the problem.
*** "grep sound-slot /etc/modules.conf" will tell you what driver it
currently uses
*** "/sbin/lsmod" will enable you to check if its module (driver) is
loaded or not
*** "/sbin/chkconfig --list sound" and "/sbin/chkconfig --list alsa" will
tell you if sound and alsa services're configured to be run on
initlevel 3
*** "aumix -q" will tell you if the sound volume is muted or not
*** "/sbin/fuser -v /dev/dsp" will tell which program uses the sound
card (thus forbiding other programs to use it [unless your card
support hardware mixing]).
** PCI devices
if your pci device is not properly detected, post the "lspcidrake -v"
output to the cooker mailling list with the subject "[hardware] XYZ
device" so that we know its ids.
if you know the module that it should uses, post it too.
if you want its support to be integrated faster in mdk, patch the
/usr/share/ldetect-lst/pcitable file: add a line or fix the existing
line regarding your device.
format is �"vendor_id device_id "module" "Vendor_name|device_name"�.
fields are separated by a single tab character.
ids are in hexadecimal formats (like those given by "lspcidrake -v").
eg: "0x10de 0x006a "snd-intel8x0" "Nvidia Corporation|nForce2 Audio Codec
Interface"
if several devices share the same vendor & device ids, then you may
add the vendor & device sub ids:
�"vendor_id device_id vendor_subid device_subid "module" "Vendor_name|device_name"�.
if after discussion it appears that no support is availlable, ask the
vendor to support linux.
** USB devices
these pets should be automagically detected by hotplug (which should
also.
hotplug rely on usb device drivers from the kernel to export the
devices' ids or classes they handle through modules.usbmap in
/lib/modules/<kernel_version>
if not, 3 cases may happen:
- this failled because the driver does not properly exports its ids
but do know the device.
=> alter the usbtable like explained in the "PCI devices" section
- the device has no proper ids (ie 0x0:0x0)
=> no proper solution ?
- the device needs some workaround to be set up by the driver (eg:
some audio or mass storage devices)
=> contact the driver author so that it fix the driver if possible.f
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
