I installed FC4 a couple of weeks ago and it properly detected my HP Deskjet 820cse.
After installing the latest ALSA, it had no problem finding my sound card and making sounds.
I had to wipe out the install and start again for other reasons (a usb hub had gone bad
and I didn't know it until a lot of troubleshooting...since replaced it and fixed that problem).
I have clean installed (wiped the hard disk partitions clean) three more times trying to fix the printer and sound card problems, hoping Anaconda would find my printer and help install it like it did the first time. These last three times, Anaconda & FC4 won't detect my printer. It finds my sound card but it won't work (I get a failure, "sound won't work on this computer." I know that isn't true, something though is different. I'm sure it isn't any left over files from a prior install because I completely erase and reformatted the partitions.
In Windows XP Device Manager, it shows the serial port as a device. How do I find the serial device(s) in FC4? How do I send a test signal to the serial port to even see if FC4
is recognizing this port? I have one standard serial port on my motherboard and it is hooked up directly to my printer.
My sound card is an Audigy 2 ZS Gamer. It was detected and worked, like I said. So I know ALSA makes it work, but I don't understand why a different install, using all the same parameters in Anaconda, would not install the same and work the same.
Can anyone help me figure this out?
I have one further question. I want to edit my YUM.conf file so that it will download
the .i686 versions instead of the .i386 versions. All the examples I can find on the net
refer to or give example to .i386.
I have found this:
Either `1' or `0'. Set to `1' to make yum update only update the architectures of packages that you have installed. ie: with this enabled yum will not install an i686 package to update an i386 package. Default is `1'.
So I am going to assume, that if I set exactarch to '0' that it will allow YUM to update to .i686 files, if available, and replace the .i386 packages...is this correct?
I have the .i386 installation disks but I know there must be a complete .i686 set of files for YUM to download since there is a .i686 ISO install set of disks. So I have the .i386 architecture, but I have an AMD664 3000 processor, so I could do total 64 bit.
I would rather not download the entire .i686 install ISO's...but rather, try to replace .i386 packages with YUM, if I can do it. What I would like to see, is an example, if someone has it, where YUM automatically looks for .i686 packages to replace .i386 installed packages.
Hoping here not to have to download +4 Gigs of .i686 ISO's.
Thanks everyone, kindly, in advance. Jim