danleff

That should work. Yes, another script to stop the service, just as Dan noted. I just bought an HP Officejet 6210 this am. I am going to try the HP drivers with it and post my results.

I have two systems, one with an onboard silicone image chipset and the other with the same chipset on an add-on card. I have the same issue on the system with the add-on card. I am not using raid. There is something funky with PCI detection. But from what I have read, the issue is with raid. Look at raid as software driven and sata as bios or hardware driven. One system requires that a jumper be set on the motherboard for sata, the other is totally bios driven. If raid is set up previously in Windows, then I have seen the issue crop up on posts, as well. Since I don't use raid, I can't comment. Someday! Posted by a non-IT professional.

Well I actually have a flatbed and a seperate printer, but I remember a post on this a while back. I have thought about getting a combo unit, maybe today, since I have some Staples gift cards to use. I do remember reading an article about this a while back, as well. Maybe a couple of shell scripts, one to turn on and another to turn off sane. Not the best solution, but a little better than switching back and forth via a console.

One of the problems is that you are using old distro versions. Most folks have moved on to Mandriva and Fedora. So, there may not be anyone who remembers how to do it. The newer distro versions are better supported and should be easier to set up. Of course, did you seek information on the WineX web site? I don't use WineX, but some others here do. However, if you are polite with your posts perhaps you will get some help. Quote: I think the only persons to understand and use linux, every distros, are all to be IT professionals. Windows is still best for end-users. So if you are trying to use linux, forget it. Unlike me, I'm trying to learn linux not to do away windows but to know both world. Still, free is a great deal. Comments like this don't inspire others to respond to your posts.

I just installed FC4 on my sata drive and also installed madwifi. I am posting from my wireless card now. Give me a little bit and I will post a link to my web page article. What I essentually found is that you need the kernel source installed. You are also probably correct, you downloaded the wrong package(s) and downloaded only one of the two packages needed. You can install the kernel sources from up2date. Try uninstalling your current version by doing as root user, in a console; rpm -e madwifi You need both the madwifi-0.9.6.0-18.rhfc4.at.i386.rpm and the madwifi-kmdl-2.6.13-1.1532_FC4-0.9.6.0-18.rhfc4.at.i686.rpm packages. The package that you have is for 64 bit processors, if that is what you have (madwifi-kmdl-2.6.13-1.1532_FC4-0.9.6.0-18.rhfc4.at.x86_64.rpm. I'll try to write a little how-to.

Check the running kernel to make sure that it is the same as the package for madwifi that you are using. Look at this thread and follow Frank's suggestions. The other problem is that you may not have the kernel headers or source installed. I will have to look at this more closely.

You most likely need to set the pciid for the PCMCIA services. Did you modprobe ndiswrapper to load the driver? Let us know what you have done so far. Try to set the pciid on the card. I have some instructions that I used located on my web page here. Quote: To check the manufacturer's ID of the card, run; cardctl info in a terminal, as root user. Mine returned the value; MANFID = 0271,0012 Now make ndiswrapper use the pcmcia device with the -d command manufacturer's id; ndiswrapper -d 0271:0012 net5211 Then load the ndiswrapper module with modprobe. Substitute my net5211 example with your Windows driver name. Are you using the rpm for ndiswrapper or by source? Are you using the Win XP driver with ndiswrapper?

No, you don't cd into modprobe. Use the command /sbin/modprobe ath_pci as root user in a console. Make sure that you are root. Type in; su (hit the enter key) When prompted, enter your root password, then the modprobe command, as above.

This is by design. If a new kernel does not boot, then you can boot easily to the older one. You can just go into the /boot/grub/menu/lst file and comment out the entries for the older kernels, once you know the newer ones work, Each kernel update gets named in the list. Use your favorite editor as root user. Just comment out the lines that point to the older kernel by placing a # in front of that series commands. So, say you want want to comment out the first entry; #title Fedora older kernel #kernel (hd0,0)/boot..... #initrd (hd0,0)/boot..... title Fedora newer kernel kernel (hd0,0)/boot..... initrd (hd0,0)/boot..... Each section starts with the title, so make sure you don't comment out a command listed for the next kernel entry.

If you already unstalled a madwifi package, please don't add anymore, as it will confuse the system, unless you know what you are doing. OK, this is Fedora. They are a little quirky about this. Find where the executable file is for modprobe by running as root user; whereis modprobe It will return a path something like; /usr/sbin/modprobe Whatever it tells you, run the command with the direct path. So, if whereis returns say /usr/sbin/modprobe...then type in a root user; /usr/sbin/modprobe ath_pci

USB memory sticks sometimes are a problem. What make and model is it? Is the original filesystem on it? Did you reformat the disk at some point to other than fat16? CentOS should pick it up right off. But, I found this thread on the CentOS forum. Try following the advice given by the post by theorist. Note the use on the thread of the command dmesg You can run this as root user in a terminal window to get some useful information. Also, the command fdisk -l is also useful and can let you know if the stick is seen and what the mount point is. That is the letter l, not the number one in the command after fdisk. If this is the only USB hard drive or stick that you are using, then it should return the value like sda1 as the device name.

Ok, let's recap. I don't use madwifi, but the methods ar the same. It looks like the package that you installed is for an Athlon 64 system? I don't know if it is "all-in-one" or not, but let's move on. If you already installed madwifi, you don't have to do it again. From your earlier post, you noted that it was already installed? Quote: yum'd a driver madwifi-kmdl-2.6.13-1.1532_FC4-0.9.6.0-18.rhfc4.at.x86_64.rpm and it installed OK. Once it installs, you don't need to do it again. In order to use Yum, you must point Yum to a repository that has any special packages. What you essentially do, is add the link to the repository to the /etc/yum.conf file. But, if you already installed madwifi, you don't need to do it again. If this is the case, stop trying to install more madwifi packages. Once madwifi is installed, you need to load the module (driver). In other words, you tell the Linux kernel to use it. As per the wiki, go to a console (terminal window) as root user and type; modprobe ath_pci If it just returns to a command prompt with no errors, then it is loaded. If you get this far, let us know. At this point, the you would use dleon's instructions to configure the settings of the card from his step 6. You can check the network manager to see if ath0 is there, but I bet it is not. This is a problem with Fedora. But, most users that I see do the configuration from the command line, then add a script to run the commands. If you are usig a router, then you need to know the settings of the essid and such to allow the NIC card access to the router. Are you using a router? If so, do you know the essid and if you are using WEP excription, the WEP password values? I will try to find a how-to that is more clear, if you are getting confused. Or better yet, install madwifi myself.

Did you look at the xine faq page located here? See the section under "video related questions."

Accessing grub from the menu when the system boots does not change the menu permanetly. It is only for testing out different commands to see if they work. When you are in CentOS, access a root console. If you open a terminal window (again, I don't know how CentrOS is set up and if you are using Gnome or KDE as your interface) and get root. Type in; su enter your password (enter key again) Type in emacs Navigate to the /boot/grub/menu.lst file and open it. Or you can type in; emacs /boot/grub/menu.lst Make sure that you are not opening, or attempting to open the backup file, menu~.lst. Edit the line that as I suggested and save the file. Reboot and see if Windows is now default.

I don't know CentOS and it's grun file. Can you post your Grub file? It's easy to change the boot default. If your Grub works like most, edit the /boot/grub/menu.lst file while in CentOS using your favorite editing tool as root user. Look for the line near the beginning of the file that says; default 0 Change it to; default 2 This assumes that Windows is the third boot entry, as you posted. If this works, then we can move on to the USB stick.

Windows over-writes the MBR (master boot record) on install. Try recovering Grub back to the MBR (if that is where you had it) by doing the following' Boot the Fedora cd disk #1 (installation disk). At the installation menu, type in linux rescue (hit the enter key) Once the system loads, at the terminal prompt, log in as root uer. Then Type in; chroot /mnt/sysimage This will get you to the root filesystem console. then; grub-install /dev/hda We eliminate the recheck code, as grub apparently was on another boot partition. Note if you get any error messages, or if you get some output with no errors. Then type in the command; reboot See if the grub menu comes up and you can choose your os, either Windows, or Linux. NOTE: This works only if Windows was installed on the primary master originally and when you re-installed Windows. The /dev/hda reference assumes the first master primary hard drive partition.

Try this link. You can search google for links by searching for; index redhat 9 iso Check the download sppeds. If you have broadband, you may want to try a few mirrors until you find one that downloads the images at a reasonable speed. For burning the iso images, see my article, located here.

Quote: Another note: I installed an updated kernel, and I had to reinstall the wifi drivers to get it to work again. Yes, as the drivers are bound to the running kernel in /lib/modules..., you need to do this. Each time you install an updated kernel, a new kernel driver reference is made for that kernel version. You can also make a shell script to start the wireless settings. See my article located here. Go down about 1/2 of the page.

What exact model of HP is this? Do you know what video card is in the system? Did you burn the cd disks correctly? See my article located here. If you did burn the iso images correctly (used a low burning speed, are using quality disks, checked the md5sum of the iso images), try typing in at the boot welcome screen via the command line; linux noapci Then hit the enter key, rather than just accepting the default. The other option to try is; linux acpi=off

Two issues are usually involved in an install failure. 1. A bad cdrom disk, bad download, or a bad burn of the disk. 2. Incompatible hardware. Since the forum was changed, I no longer see stats that tell me if you have posted before. I seem to remember that you have, so I can't reference your system specifications. Did you burn these disks yourself, or are they a commercial set? Can you give the specs of your system? We especially need to know how much memory is in your system, video card (a source of some issues) and if it was self built or a pre-built system. Please be specific. Also, do you have sata drives on this system? If so, it is helpful to know if you built this system yourself (motherboard model and make), or post what brand and model that the system is. Burning iso images, if this is what you did, takes some care. You need to burn the disks slowly for a valid burn. See my article located here.

I think that this link at the madwifi wiki will help. Take a look and let us know what other guidance that you need. It sound like you have Fedora installed and configured correctly now.

Yes, that would have been my second guess, if the cd disks were OK. But this post is 11 months old, so it looks like they have moved on.

What model number is it? Do you have a link for the users manual? The MDG site is not very helpful. Most likely, you can get things to work by altering the bios settings a little. There are two settings that I can think of right off. Try disabling PNP OS in the bios. It can usually be found under PNP Configuration in the bios, or advanced features. You may also need to boot with the noapic kernel command. This is not unusual with some laptops. Are you using the Grub bootloader?

Duplicare post deleted. Are you running Fedora Core 3 or 4? Your previous post shows the kernel for Fedora Core 3. Did you by chance upgrade the kernel for the wrong version of Fedora? What is the output of uname -a at a terminal window? ...and yoe are sure that your card is an atheros chipset? What is the revision number on the card? The following is a snipit from the madwifi wiki; Hardware Firmware Status B1 Unknown Works B1 4.0 Works B1 4.10 Works B1 2.10 Works C1 5.00 Not supported, try RaLink drivers It would also help if you tell us what the error message was that you got when attempting the install. That would tell us what the problem might be.

Fedora should come with Gaim. See this link which should get you started. See question # 9 under "Using Fedora and installing software. Fedora's software management system is very efficient and I suggest sticking with it for now. You can use a Synaptic like interface, but this is better suited, in my opinion, for Debian Linux. However, you can read about apt4rpm here.