danleff

Is this a bios chip that you bought, or did you flash the existing bios? If you bought a chip, where did you get it from? If you bought the chip, was it for the specific motherboard that you have?

For driver packages to be installed, the kernel-source package often needs to be installed. It often is not instaled unless you told the ReHat installer to do so during the install process. Are you using the stock kernel that came with RedHat (did not update the kernel through up2date or other means)? If so, then you can install the kernel source package and try again. Can you provide the link to thre driver package that you are trying to install?

What always suprises me is that forums and links found through Google often say "it works" but never tell you how it works. This question has come up a few times on this forum. First, realize that you are using an older version of RedHat, which is a fine version, but USB support is limited. You will save yourself a lot of headaches, if you plan on using RedHat 9, or Linux at all, by not using USB with your DSL or cable connection. What I have always done, is to buy an inexpensive NIC card (one with a realtek chipset or Lynksys) and a router and connect it up the "traditional" way. NIC cards ar cheap, at about $10 USD. Also routers are very inexpensive these days, as well. You connect the system up as follows; DSL cable to the modem. Modem CAT5 cable to the main router connection. NIC card on your system to the secondary router connection. Then use the Network configuration to set up the NIC card. Make sure that you choose dhcp on startup when going through the Network Configuration utility. This works for me every time on Roadrunner.

The last that I looked, the NVIDIA packages supported the 2.6 kernels, since their release 1.0-5336. Any reason why you don't want to use NVIDIA'S packages?

I'm going through the same issues right now. I'm a bit of a newbie on wirless, especially when it comes to pcmcia. I just tried an Intel Pro 2011b on my old laptop with the same results. I even found the correct module to load, I thought, but Libranet does not see it on my lan. I got a Xircom combo 10/100 + modem card ($15) and it worked right out of the box (wired). Wireless is a little tricky. The issue seems to be what exact chipset that you have on the card and if the pcmcia socket gets loaded. If the socket gets loaded, usually you hear an audible beep or two on boot. dmesg also seems to note that it is loaded. Look for any reference to pcmcia by typing in lsmod as root user, and see if any modules get loaded, such as pcmcia_core and other related pcmcia modules. You should also see a reference to 3com as a module. if not, then you either have to load the module(s) (by knowing which exact 3com chipset that you have) or toubleshoot pcmcia first. If I figure this out, or get some good references, I'll let you know. The Libranet site is pretty good about this, so I'll take a look again this weekend. Anybody got any ideas?

I looked at the Transcend web site and your device. The faq state that it is not supported in Linux, while some of their other products are clearly supported in kernel 2.4. This is not to say that it won't work at all, just that it is not supported. I would pose the question to the Transcend folks and find out what chipset that the wlan uses, exactly. There are a few variations of the 802.11b standard and chipsets used. The issue is that the pendrive uses USB totally and this may be your main problem. If anyone knows what chipset this is, give us a hand. It is not stated on the website.

Before you go re-formatting the hard drive, especially if you have a lot of important effort into XP (programs and such), try Dan's suggestion. If this does not work, you can also use the XP bootloader to load RedHat. If you have access to PartitionMagic, you have other possibilities as well, if Dan's suggestion fails. Depends on how much you want to get into this and how comfortable you are in implementing a solution. Let us know how it goes, or what you would like to try. Another possibility is to do the upgrade and tell RedHat that you want to install Lilo on a floppy. This way you can play with Redhat, without worrying about messing with bootloaders right away. When you are comfortable with it, then we can address the dual boot issue. But 99% of the time the dual boot works right off. You are obviously one of the folks where something went wrong. Just to get some more information, did you defrag your XP partition befoe installing RedHat? This is sometimes the issue. Failures can occur when this step is not taken first. Before installing any Linux flavor, it is wise to defrag first.

As Dan eluded to, you have a good amount of hardware that will not work with Mandrake 9.2 out of the box. You have a couple of choices. 1. Try Mandrake 10, which will allow your nForce motherboard hardware to work properly. I'm guessing you have onbioard NIC and sound on this system? 2. Compile drivers for the motherboard (which are available for Mandrake 9.2) from the NVIDIA website. The interface etho: failed message occurs because Mandrake is trying to get the onboard lan card to work, but it is unable to do so. Look at it this way. Your hardware is newer than the distro (Mandrake 9.2) that you are using. So, drivers are needed. The stock kernel (which contains the drivers) has no real support for the nForce chipset on the motherboard. Another option is Fedra Core 2. But, if you have Windows XP already on the system, there are some steps that need to be taken to assure that Linux plays nice with an NTFS filesystem, if that is what you have with the XP installation. If you want to test Linux in general, you can also try Mepis or Knoppix, which are a cd based distros that will give you an idea on your hardware compatibility. Maybe, just maybe, the winmodem will also work. If so, and you like one of them and your hardware works, you can than do a hard drive install, if you choose. But I agree with Dan, invest in an external modem, specifically a model that he suggested, which will work fine in Linux. This may save a lot of hassles for you. If you choose to invest in an external modem, make sure that it is a model with a controller chip onboard the modem. Most are, but some are not. So, depending on how daring you are, we can try one of these options. By the way, does your sound work??

Try here.

There is a documented bug with Fedora and installing it next to Win XP (and I assume Windows 2000) when you allow Fedora to make it's partitions next to an NTFS partition. Is Win 2000 on an NTFS partition? The solutions are not what I feel are user friendly for a Linux newbie. If this is the case in your system, you can try a couple of things. 1. Make a change in the bios to change how the bios reads your hard drive. This may work - it has for some and is the easiest solution. Linux likes to read many hard drives in LBA mode, so if your bios detects your hard drive as "auto" rather than LBA, some have had luck just changing this designation in the bios. If your Windows install is "mission critical" for you, then I consider the technique somewhat risky. 2. You can use the Windows bootloader to boot Linux (Fedora) by making some additions to the boot.ini file. This requires some knowledge of manipulating the boot.ini bootloader from within Fedora and adding an appropriate entry for Fedora, using some commands from within Fedora. 3. If you elect not to keep Fedora, then you can restore your MBR (master boot record) using the Windows rescue mode (recovery console), or some have done so with a Windows boot disk. Some have had no trouble with the dual boot senario at all. Let us know what you would like to do and we can try some methods. But first, let's make sure what your grub file says for the Win boot commands, as shobhit asked about.

Ahhh.. Nice photos! I notice a few things. Take out the disconnected pci card (SB audigy?) and all connections to it totally. Don't leave it sitting in the box. Or, reconnect it fully in the system. Secure your video card with a retaining screw and make sure that the card is seated correctly and fully. Disconnect the card reader from the USB slot in the front. This is likely a problem. USB2 in the front? How is the boot now? If nogo; Try Dapper Dan's excellent recomendation. See if the booting speed improves a lot. This Asus board has been problematic for some. I can't remember the specifics, but is this a KT-400 chipset or is there raid or sata support on this board?

Ok a couple of possible issues I can think of. Forgive the brief response, as I am getting ready for a work related trip for Thursday and Friday. First, how were the cd's burned? On cdrw media or cdr media. At what speed were the iso images burned? Older lappy's sometimes do not like cdrw media burned on modern cdrw drives. If I remember right, Mandrake 10 had a quirk in the booting/install process. There is also a problem with 24X cdrom drives booting install cd's properly. I just had this problem on my lappy. Switched from a 24X to a 20X drive and all went fine. Is the cdrom a 24X or 20X drive? If you burned the cd's at 4X or 8X (no faster), then attempt a boot from cd, using the second Mandrake cd (yes, NOT the first install cd). You will get a message that this is not an install disk. At this time switch the cd to the first Mandrake install disk. Hit enter on the keyboard and see if ther install starts properly. ISO images need to be burned at a slow rate, no faster than 8X and cdr disks work much better. Booting into Win 95 and starting the Mandrake install by rebooting will not work. So try booting from the second Mandrake cd directly and follow the steps outlined above. Let us know what happens.

Since Fedora seems to be having trouble with some piece of hardware, we need to know more information. if you have a prebuilt system, such as a Dell, Gateway...post the model number. If this is a self built system, gve us some details on the system, such as the motherboard model, amount of ram, processor, hard drive size and any other hardware that you have on the system, especially any external hardware connected to the system. Durig the install, did you have any problems? How did you partition the hard drive? Is there another OS that you are running on the system that functions properly? in otherwords, are you dual-booting wndows and fedora? The issue is that it could be a number of things, from a bios setting, faulty or inadequate power supply, IRQ conflict and any number of hardware issues. One way to troubleshoot is to take off any external hardware on the system and see how Fedora boots. If it boots in about 1 minute, then you have narrowed the problem down. If there is no change, we can go from there.

This system can have a max of 80 mb of ram, correct? 16 mb onboard and 64 top added. This is partially what Dapper Dan is getting at also. So, as he suggested IceWM will run well on this much ram. You really would have 64 mb tops, as video shares 16. You may be able to reduce this in the bios if needed. The install will guide you through the partitioning stage, just let it take over partitioning for you and choose your filesystem type. Do a minimal install with IceWM. I also just installed Libranet (it is being offeed as a free unlimited trial) in my CTX lappy system (64 mb ram and 8 shared video onboard = 72 total). It only has a minimal hard drive install of 600 mb and requires 32 mb ram for the install, but does better with 64. I was very impressed with it on this limted system.

Let us know if this turns out to be the issue. I use the linuxant driver for my D-Link wireless on Lindows with my laptop. Works like a charm! Of course, I paid for the drivers (or the development). Saved me a lot of headaches!

The release notes from Fedora Core 1 admits a problem with Greek display. I wonder if the issue is display, rather than what is being written. A google search reveals no real answer. Let's see if anyone has a possible solution.

Nice find! I've been strugging with my bios and pen drives and this may help a lot. Sometimes the need of the few outweigh the needs of the many. And...(signature)

From the instructions on that page; Quote: Please choose only the package matching exactly your system's kernel version below. You can determine your kernel version with the following case-sensitive shell command: uname -r So, you need to use the uname -r command to see what kernel version that you have. Then choose the cooresponding package that matches the kernel.

Could you give us the name of the driver that you downloaded or a link to the download page? Did you perhaps follow the link on the Conexant page to the Linuxant driver page and download one of their drivers? These drivers require that the full kernel source be installed. This may also be the issue, as the driver will look for the symbolic link to the kernel source. If it is not there, then the drivers will give you that message.

Try as root in a console, the following; modprobe ntfs Does the command line come up blank with no errors? If so, then try to mount the partition.

My advice, forget the BroadCom 1000 lan and get an inexpensive NIC card, such as a realtek or a linksys. They are cheap and work out of the box, very well. Then when you get into it, you can play with the BroadCom. There are drivers that BroadCom lists for Linux, but I have no idea how they work or in what distros. Are you using a router or cable modem only connected to the computer via usb? Any modern version of Linux will work well if the connection to the net is set up properly. They will work well, as long as you have a router and no USB connection to the system using the cable modem. Since you are using your girlfiend's connection, I assume you will be using a router. So, you would want a router connected as follows; Router connected to the cable modem with the primary cat 5 connection. The system (NIC card) connected to the router on a secondary connection. The router allows multiple systems to be connected to the router, of course. I have a variety of NIC cards in my system that work well. They are either linksys cards or realtek based, using RoadRunner. Gaming is another issue. I don't do it, but Dapper Dan will have some good suggestions.

Looks like Tubby never got an answer here either. When the cd starts, try enabling acpi. At the login screen prompt, type in; linux acpi=on and see if the install continues. A word of caution. If you have Windows XP (NTFS filesystem) on the system, I suggest that you format a linux partition on the drive before trying the install. There have been problems with NTFS and using the partitioning utility in distros using the 2.6 series kernel for the install. So, use PartitionMagic or another utility to resize and format, say an ext3 partition for Fedora. If the install goes, then choose that pre-formatted partition to install to.

Hmm...A bad keyboard controller for PS/2? It does happen. My wife's box had the same problem with the controller on an Asus board. Is this a powered hub or does it run off the motherboard (no ac power plug)? What Asus motherboard is this? Does the keyboard and mouse work in another OS when not connected to the hub? There are issues related with power on thes hubs that rely on the motherboard for it's power source. I would guess a power supply problem if the hub was self powered, but you tried it without the hub. Any idea what rating the power supply has? 200 watts, 300 watts? Mandrake should detect and allow the install with the USB keyboard attached, but the beeps suggest a bios issue or power problem. I assume that USB support (legacy USB or USB keyboard support) is enabled in the bios?

My advice regarding NTFS support is to make a fat32 partition on the hard drive to store your NTFS files that need to be accessed. NTFS support is still new and I would trust fat32 for such storage first. This way the files are available to both windows and Fedora. But, if you prefer, check out the following; http://linux-ntfs.sourceforge.net/rpm/fedora2.html. Make sure that you choose the correct driver for the kernel that you are using. Read the instructional link that is available on the left had margin for the install and setup of the driver.

Not at all! The point was that there are two versions of this board, with two different nic cards onboard. One should work out of the box and the other requires some effort, from what I have read. One has sata capability (which may be an issue and needs to be turned off in the bios, if sata is enabled). They are two essentually different boards (same chipset), in terms of onboard hardware (nic and sound) with a minor name difference.