danleff

CentOS s based on Fedora/RedHat? Are you trying to use the modinfo as root user? In Fedora, I know that I need to point to the direct path to the command. Do whereis modinfo and see what it returns. If it returns; /sbin/modinfo or /usr/sbin modinfo...then try the path to modinfo, such as; /usr/sbin/modinfo soundcore The other information that may help is in the lsmod command. This will tell you what modules are loaded and what modules are attached to soundcore. It looks like your card does not use the older emu10k1 soundblaster module, but I am looking to find which one that it uses.

May I ask a few questions? What version of ndiswrapper did you install? Was it an rpm, or by source? What Windows drivers did you use, Windows 2000 or XP? Did you get the message; Driver installed; hardware present ...when doing ndiswrapper -l? Do you have the kernel source package installed on Mandriva and follow the directions on the ndiswrapper wiki page? What model USB device is this? What I am trying to get at, is the USB device listed as supported with ndiswrapper? For example, for the F5D7050, the wiki states; Quote: Card: Belkin F5D7050 (USB 2.0 Adaptor 802.11g 54Mbps) Chipset: RT2500 usbid: 050d:7050 Driver: Install the drivers for windows included in the box and fetch the .inf files from the installation directory. Other: Works fine. When entering in resume mode, freeze the system.

Originally posted by mulatto: Quote: OMG, I just reinstalled the whole OS and the file is still blank. I think im gonna give up on this. Oops, I think I know what happened here, but it's too late. When you re-installed Mandrake, you did not tell the installer to reformat the partition, so it retained your xorg file. If you re-install any distro for problems like this and want to start from scratch, pick total install + format, not to upgrade the version that Mandrake found.

This is a hardware issue. Could be the promise card that the DSL kernel does not like. Swap space is fine, as long as the boot device can detect and use it. Otherwise there is not enough memory to load in total RAM. Another clue; Quote: can get the system to boot from a Win98 floppy, and I can even run an install CD for Win98SE, but I can't get Linux to boot from a CD in the drive (yes, BIOS is configured to check) nor from a floppy. Older PC system cdrom drives do not like home burned cd's. Commercially burned ones, such as the Win 98 disk are made to be compatible with most drives. This would explain if you used the cd burned at more than 4X (in your case 16X) in a newer cdrom drive/system and it booted fine, but failed in an older cdrom drive. In fact, some are so finicky that they seem only to boot in the cdrw drive that they were burned from. Older cdrom drives also do not always like cdrw disks, but will boot cd-r disks fine burned at a slow speed. Finally, if you burned the cd in a newer (host) system with a cdrw drive and also make the boot floppy in the same system, then attempted to boot DSL in the older system with the same boot floppy and DSL cd, this can be an issue. If the disk geometry or partition scheme is different from the host machine, then the bad EIP value can occur. Enter how the promise bios reads the drive partitions.

justbill, first of all, nice system! Did you buy the SB card retail, or whitebox? What I mean, is was the card in a retail box, or surplus, either in a "white box, or without the full retail package? Some of these cards are legacy cards, believe it or not, bought cheaply, that are made just for Gateways or Dells. They are made for use in Windows. If possible, look at the card and post what exact model/product ID number it is, say SBxxx or CTxxx. However, this motherboard is Intel chipset board all around? Does it have onboard graphics? You can try moving the card into another PCI slot. The other thing, is set PNP OS off in the bios.

Did you include the vi program command vi /etc/X11/xorg.conf ...at the command line? vi is the editor program that will open the xorg.conf file.

Ok, this is a problem. I found this link. It is a problem with the bios and how it allocates memory for video, which is very limited. The fix will be complicated for you. What bios revisison did you update to? You can try the following, but I doubt that it will work. When you are logged in as root user, type in; XFdrake (hit the enter key) The syntax is important...capital X and F, small drake. Try setting the video card to vesa and the default depth to 16. Just remember that these systems are made to run Windows only, so it takes a little work to get it going. Not good for someone just starting out with Linux. Are you willing to try another distro of Linux other than Mandrake?

The article that you referenced about the graphics in RedHat 7.3 is very old an does not apply to the newer distros. What is important is the error message that you are getting. You are getting dumped to a terminal window, with a message? Try to post the message, such as "no screens found." I'll see if there are any articles on your system with Mandrake installation that may shed some light on the issue.

This is where posting as much information on the subject is helpful. Redhat 9, not RedHat 9.1... Is this USB stick USB 1.0 or 2.0 compliant? Is the port that you are mounting the stick in USB 1.0 or 2.0? Are you using a USB port attached to the motherboard (primary port) or an add-on card? See a discussion on the subject here. Did you try to modprobe usb-storage by going to a terminal window as root user? It sounds like you have some experience with Linux, but let us know if you need clarification on my questions.

That's where I was going to go. On some distros, you even have to modprobe the module... modprobe usb-storage Then I check dmesg to see if it recognized the stick, then mount it at that device. It can get a little more complicated, if you have another usb device attached, say a multi-card flash reader.

Try disabling onboard sound in the bios, then boot Fedora and login. What audio have you tried to test? playing a cd, midi files...? Or is it that there is no start-up sound when KDE comes up?

Try looking at the question "How do I configure sound to work properly in Gnome" here.

Bad EIP values can be hardware related. Perhaps the Promise Ultra ATA-66 controller card. But I also notice that you may not have enough ram to run the system totally in ram. i don't know much about DSL, but I thought that you needed at least 128 mb of ram to run totally in ram space? Also, what speed did you burn the iso image at to the cd> Are you using cdrw or cd-r media? I would pose the question on the DSL forum to get a quick answer.

How about a little more information. What linux distro and version number are you using? Are you "hotplugging" the stick, or is it in the usb port when you boot into the distro? Has the stick been re-formatted, or does it have it's original factory formatting? Is this the only usb device plugged into the computer?

Did you re-install the NVIDIA drivers after the upgrade? The drivers need to be recompiled for the kernel that you are using. When you upgrade to SuSE 9.3, you change the kernel version and need to recompile the NVIDIA drivers for that kernel version.

What exact wireless card do you have? Do you know the exact chipset for the card? AR5210, 5211, 5212 or 5213? I tried madwifi and had no success with it. ...and the kernel source is installed on your installation of Slackware? Do you have WEP or WPA set on the router?

LiveMeeting is embedded into XP. Looks like SIP is being worked on with GnomeMeeting. See here.

OK, let's recap. The battery went dead for the bios, which means that you lost the old settings. You apparently reset what the old settings were supposed to be. Try getting into the bios setup (make a note of what the current settings are). Pick the option to set the default values. Then see what happens. If the problem does not resolve, try getting back into the bios settings and set PNP OS to off. While you are in there, make sure that the new drive is recognized correctly (brand and total capacity). Note if the drive(s) are set to auto for detection or LBA. It should be the setting on the far right of the drive descriptions. See if then setting PNP OS to off has any effect. If not, report back. There is one more thing we can try.

SuSE 9.1 should use reiserfs, not reiserfs4 on install. Ddid you use reiserfs during the install, or with PartitionMagic, what filesystem did you use to prepare the IDE drive partition for SuSE? What drive and partition did you install Grub to?

What package (program) are you trying to install? Compressed source files come in a few formats, gz, bz2... They are all tar files underneath. However Mandrake has many packages (programs) on the cd disks that you either downloaded and burned to cd disks (the iso image files), or paid for and have already on a commercial set. You can also get many packages via the web in rpm format that Mandriva can install with ease for you. Let us know what package you are looking to install and we can go from there. You do have Mandriva currently installed OK?

I assume that you are having trouble setting up video? What make and model monitor do you have? Did you use the video config. tool during the install to test some video settings?

Take a look at this thread and see if it works for you.

There are two ays of looking at this. UPGRADE = move from one version of Fedora to another. UPDATE = update Fedora Core 3 packages (programs) to newer versions. Once you start to customize Fedora with outside packages (not in the Fedora family) the chance of breaking somethng by up[censored] things (such as the kernel version)increases. This is not a problem with the Linuxant drivers, as you have one wireless card that is licensed. You can download or re-install Linuxant drivers fine with your license. Generally up[censored] packages is not a problem. Keep your existing kernel, as Linuxant is configured for it. Have some fun and get used to working with the distro. The security updates should be fine, as are the package updates, say for OpenOffice. If you upgrade to the next release, you may need to re-install the drivers, since you moved from one version to another and much usually changes. If you have used Windows, you know the score. Upgrading usually means upgrading drivers as well. This is not always the case in Linux, but many can tell you that they trashed a perfectly working (customized) install by worrying too much about up[censored] and upgrading things. If it works, don't worry about the latest or the greateest until you are comfortable re-customizing a new install again. Just my two cents.

Realize that Mandriva and Fedora are two different distros designed for different users level of comfort. In Fedora, ndiswrapper is not installed by default. You have to install ndiswrapper as an add-on package. The kernel is also an issue, as it is limited to 4 stacks, with no option to change it by recompiling the kernel. So, ndiswrapper with a Win XP driver will most likely hang the system, as Win XP drivers are designed to use 8 or even 16 stacks. There is a workaround that Linuxant has provided. They have custom kernels with the stack size increased to deal with the problem. However, I found that the test release of Fedora Core 4 fixed the issue. So, I recommend waiting for the full release of Fedora Core 4 and try that, unless you are adept at installing the custom kernel that linuxant provides.

I think that I understand about the router/modem for ADSL. Quote: 1x 10/100BaseT Ethernet interface Is the ethernet card an ISA or PCI card? Do you have any idea what brand and model ethernet (NIC) card is in the system?