Additional Information
Updated: 5. Jun 2005 ContentsSoundcardThis is about getting the amilo soundcard (Multimedia audio controller: ALi Corporation M5451) working with Gentoo Linux and a series 2.6 kernel using ALSA (which is the default sound subsystem in the 2.6 series). Firstly, Sound card Support needs to be enabled in the kernel (config-2.6.11-gentoo-r9 kernel config), without ALSA or OSS support. It's better to use the portage alsa-driver instead of the drivers provided in the kernel, as it's probably more up to date. You can find the sound stuff under Device Drivers --> Sound. Ok, so now you've booted your amilo baby using your new kernel. Before installing ALSA, edit your /etc/make.conf file by applying a new option to it: ALSA_CARDS="ali5451"alsa should also be found in your USE variable (and perhaps oss for OSS compatibility, too). Then emerge (it's always a good idea to pretend first using the -p switch!) the alsa stuff: # emerge alsa-lib alsa-driver alsa-oss alsa-utils When you're done, run etc-update: # etc-updateThen edit /etc/modules.d/alsa and change the line alias snd-card-0 snd-cmipcito read alias snd-card-0 snd-ali5451The full alsa config is also available. Then update your modules, add alsasound to boot and start it: # modules-update # rc-update add alsasound boot # /etc/init.d/alsasound startNow that you have alsasound running, use alsamixer to unmute the sound channels. When you're ready, test if everything works using your favourite player. If you do not have one yet, you could try alsaplayer: # emerge alsaplayerand # alsaplayer somefile.mp3Added: 5. Jun 2005
Firewire
Like told before, I connected my external firewire harddisk (Maxtor, 40 GB) to my laptop
to see how it does with Linux. I have used it as a extra storage space for some video stuff under
Windoze environment. Anyway, as I suspected, no problems occurred. Just hooked it up and mounted it.
modprobe ohci1394The module ieee1394 should be loaded already. Also the sbp2 module should be already loaded, but if it's not, just do modprobe sbp2.. respectively. Then you can find out some info about the devices by executing the following commands. The first one gives an overview of the detected scsi devices, the second one lists detected firewire devices:
Then just mount it: mount /dev/sda1 /mnt/hdand that's it. Then you can do cat /etc/mtabfor extra information on mounted devices. Please note that it is very wise to unmount the drive before pulling any cables out.
Modem
The modem is an ALi M5457 software modem. Conexant
informs Linux users to "access Linux modem application information for Conexant modem devices" by going to
www.linuxant.com.
00:03.0 Modem: Acer Laboratories Inc. [ALi] M5457 AC-Link Modem Interface Controllerand lspci -n: 00:03.0 Class 0703: 10b9:5457Notice the last string. It is said that this particular PCI id represents the ALI+ MC97 controller, to which various AC-Link modems can be connected. However, only those based on Conexant chips are supported by the driver available from LinuxAnt. So the question is: is our modem based on that chip? I tried a program (on Windoze) that looks for a modem that uses a Conexant chipset and returns some helpful information for identifying which modem one is using. Didn't get too lucky:
Presumably we're not dealing with a Conexant chip here! (WinXP says that the modem is a Agere Systems AC'97 modem.) Next I downloaded the current version of the pci.ids file, and ran Marv Stodolsky's modem detection script. The script primarily utilizes the lspci tool. The script says: "Three types of information are acquired from your System: 1) General system information necessary for your guidance; 2) The PCI_ID of the modem card or its controller; for the increasingly prevalent "soft modems", the primary PCI_ID only identifies the controller but not the modem subSystem. 3) For soft modems co-serving with a digital audio card, a codec SIL_id is acquired, to direct towards supporting software.". Ok, on with it:
TV-OUTTV-OUT can be used either using composite or S-Video (Separate Video) as an output. To get started, download, compile and install atitvout 0.4, which is a command line tool for executing some configuration commands for the ATi TV-OUT connector. Next, hook up all the cables and reboot. Then you can use command atitvout -f detectto see a list of attached displays (the flag -f forces "Rage Mobility/Rage LT" mode, which worked for me). Your TV should be on the list:
Then you can do atitvout -f tto switch using your television as your display. Use letter "l" in place of "t" to switch back to LCD (l = LCD; c = CRT; t = TV). NOTE: TV-OUT stuff won't be detected at all unless you have all the cables hooked up during bootup. This true also when using composite output. 13. Oct 2003 |
[Mandrake 9.0]
lspcidrake:
|
|
lspci -n:
|
lspci -v:
|