danleff

Did you look at the linked directions posted by zero0w? Also realize that this thread was started a year ago, the last post being 5 months ago. But, the linked directions are current. They recommend Wine 0.9.12, which fixed some issues.

Could you post the model number of your Vaio? This will help us understand the ethernet problem. Did you try to set up wireless or ethernet connections when installing Mandriva? What GUI for ndiswrapper are you referring to? I assume you are using the ndiswrapper version that comes with Mandriva? What Windows driver are you using, if any, for ndiswrapper? Did you input the ESSID name for the router and the WEP or WPA password for the router access, assuming that you have the router set up to use one of these encription keys?

This just goes to show you what differences in hardware will produce in differing systems. My installation of FC5 was as smooth as your Ubuntu one. Both seem to be excellent distros, but I see your point. Always check out your hardware with the distros hardware database to check compatibility before trying a specific distro. But, I do agree with you, Ubuntu is a fine distro!

I found an article on your system that may be helpful. You are correct, there are some issues with these Dell systems. You probably should consider a newer version of Mandrake, say Mandriva 2006. Anyway, the cdrom issue and graphics problems are outlined here. NOTE: This article is for Mandrake 10.1.

From what I recall, there was a problem with the Community version's installer that caused this problem. Did you try booting from the 2nd cdrom disk, then swirch to cd #1, as Mel suggested above? The other possible problem is needing to turn off PNP OS in the bios.

What is the exact problem that you are having? The DVD does not boot? Is the DVD drive set to boot first in the bios? Do you get the initial installation screen on boot? At what speed did you burn the iso image at?

Look at the documentation first, located here. Chapter 2, Page 28!

OK, I'm at a disadvantage right now. I don't have SuSE available to me, as my system will not be totally set up until those taxes are in. It looks like you have an AP, WEP key (which is correct) and ESSID. You have no IP address when doing ifconfig I may have missed this, but you have a broadband connection? Not DSL, correct? Which ISP provider? I can't remember the correct command to bring the network up in SuSE (too many distros...) You set up the wireless card to activate at boot (auto DHCP at boot) in Yast? If not, try the following at the command line, as root user; dhclient wlan0 If this returns ok, then see if ifconfig shows an IP address.

I think that you may be correct, but let's look at a few things. I will share my experience with the same chipset board on my new Biostar board. When deciding to use a new OS, the first thing is to check and see that it is compatible with your system hardware. This prevents a lot of headaches. What is the make and model of DVD drive in the Asus system? The media that you burned the installation DVD to needs to be compatible with the drive. Also, the speed that you burned the DVD could affect how it is detected in some DVD drives. I assume you burned the DVD at a slow speed, say 4 or 8X, not at the full capacity of the media or drive? I have seen this happen many times. If you burned the iso images, then you need to do it right. Check the bios messages as the system starts to boot, to make sure that the DVD drive is detected on boot. I found in my board, that the bios settings on these chipsets have a number of settings that affect detection of ids DVD drives. You may run into a couple of other issues. Realize that this motherboard chipset is new. I would recommend waiting for the next relese of SuSE, which is due out very soon. It likely will have added support for these chipsets. I installed Fedora Core 5 (just released) with no problems. However, on my system, Windows XP would not install without the chipset drivers from the Biostar site. Yes, I needed it for my tax software, unfortunately. Granted XP is an older release, but this can be the issue. Most motherboard companies patch hardware problems with drivers made for Windows only...but that is getting better. Back to the bios settings. Is this a straight system with an ide hard drive or sata hard drive? Again, there may ne a number of bios settings that affect the ide detection of the DVD drive. In my system, the bios was set to use raid, and the channels for ide were off by default. After I changed the settings to match my system, all was fine. Quote: I need some info if anyone can point me in the right direction I would appreciate it. Remember, I am a TOTAL newb to Linux, and have no command line knowledge or experience, nor do I really want to get into that aspect of Linux. I just want a more stable OS. It's nice that you want a more stable OS. However, if you are not willing to learn some basics of a new OS, you can expect being frustrated. While most Linux distros are getting better at detecting hardware and setting it up automatically, your motherboard is new enough that you have to expect some problems. Learning some command line commands will assist others in helping you solve any problems that you may run into (troubleshoot) and make your experience more satisfying, as you realize the power of the command line.

Nice work!!! Glad you got it going. I think that you will enjoy FC5. It's fast becoming my main distro.

Wow, is the Fujitsu site hard to get information on, or what? Anyway, one thing I need to ask, is did you set the sound card up when you installed Mandrake (during the installation)? One simple possible problem. Check to see that the sound is not muted and that the volume is set all the way up in your mixer window. I'm going to guess that RedHat 9 is using the OSS sound system, while Mandrake is using Alsa. So, you may have different sound system software for tose two distros, which means potentually two different solutions. Try running alsamixer in a root console while in Mandrake. Make sure that the sound is not muted and the sound is all the way up on all channels. Often the sound is muted, or the volume turned down by default. You apparently have an old Soundblaster Pro card in this system. Can you confirm this by consulting the owners manual? If the above does not work, we can try a few things. But also let us know what GUI that you are using, Gnome, or KDE?

I believe that RHEL installs using a Logical Volume Management (LVM) and SuSE has a straight partitioning scheme. So, I bet that SuSE did not pick up the RHEL installation. Do you remember if RHEL was listed when you set up the bootloader in SuSE? Did you install Grub in SuSE on the MBR of disk 1, or hda? Can you post the output of the command fdisk -l as root user in the console within SuSE?

It looks like the card is not configured correctly. I think that I know the problem. Is the WEP key on the router set in ASCII or Hex code? The command to look at the wireless side and what it is currently set at is iwconfig. If possible, post what that says, or if it shows wlan0. It should look something like; wlan0 IEEE 802.11b ESSID:"" Mode:Master Channel: 0 Access Point: Not-Associated Bit Rate:0 kb/s Tx-Power:50 dBm Sensitivity=0/3 Retry: off RTS thr: off Fragment thr: off Encryption key: off Power Management: off Link Quality=0/94 Signal level=-95 dBm Noise level=-95 dBm Rx invalid nwid:0 Rx invalid crypt: 0 Rx invalid frag: 0 Tx excessive retries:0 Invalid misc: 0 Missed beacon: 0 If the Encription line has extra numbers in it (more than the actual ones that you put in, say extra zeros at the start), then you probably have a hex WEP password. The ESSID line shoulkd not be like the example, but have the actual ESSID value in it between the quotes. But, if possible, post what you have and we can go from there.

Actually, you don't need rr-pppoe. You can configure a DSL connection by going to System-->Administration-->Network. Then click on the "New" button. At this point you can use the xDSL choice and follow the prompts to enter your settings and user name and passowrd for the DSL account. However, to answer your question, I think that pppoe is run as root user. This means that you need to get to a root console. Chose Applications from the drop down menu-->Accessories. When the termnal window comes up, type in su. Then it will prompt you for your user password. Once you are at the root console (it just returns a prompt), then type in pppoe-start

Ok, so now the question is, do you know the settings for your router? When you set up your card in Windows, most likely you used an installation cd disk which helped set up these values. You need to know what the router (or modem) ESSID is and if you are using WEP or WPA encription, what the password is. Also, does your ISP use a static or dynamic assignment of the IP addresss? Yes, you need to set these values to actually allow the card to access the modem/router. If you edit the settings for the wireless card in Yast, there is a tab where you can set these values. If you ISP uses dynamic assignment, then you chose auto DHCP when you do the settings in Yast, such as with broadband. The final catch is what your ISP is. Is it DSL or broadband? If DSL, you need to set up your username and password, if you have to use these for DSL, such as mine (Verizon). You can do this in Yast, as well. You are about 1/2 way there! thought it was going to be easy?

The internet issue seems to be a firewall problem. Are you running this system at home, or from the school dorm? Do you remember what settings you chose when setting up the level of security during the installation? And yes, by default, the software installer wants an internet connection. I don't know why, but I ran into this as well and have not had time to look at this...it is tax time, so forgive any delay in responding this weekend.

Take a look at the install page on the Ubuntu Wiki Page. See if this helps at all. If the installer is having a problem with your system, try to post at what point that the installer stops, or if there are any error messages. I'm sure the builder that sent you the cd disks knows about the hardware and system requirements for Ubuntu, but it also may be helpful if you can post what make and model system you have, or any specifications of the system, such as how much ram is in the box and how large the hard drive is. How is the hard drive now partitioned? Did you do anything with the hard drive after the system crash, or do you know why the system crashed?

CentOS is based on RedHat Enterpise Linux, hence the link that I gave you is a direct one from the CentOS home page. Did you try the solution noted on the linked page? Especially look and see if the sound settings are muted, or the sound is not turned up all the way for each channel. The modem will most likely be a challenge. It is a "win-modem" designed to work with Windowes and it will need some special work to get it going. If you like all the technical jargon, take a look at this users experience.

Unfortunately, you probably won't get a response from the last post, which is over 9 months old. What model is it that you have? Is it a P10-S429? This guide may help. Often, the sound is muted and needs to be set unchecked for mute.

Let's go back a little. Do you have the acpi=noirq command in Grub at the end of the kernel command line? kernel (hdx,x)..... root=/dev/hdax... acpi=noirq The line is just an example, but make sure that there is a space between the last entry and the acpi=noirq line. See if the yenta line errors go away. If not, try going into the bios and disabling the quickboot option.

Quote: cs: pcmcia_socket1: cardbus cards are not supported. Try the other PCMCIA socket.

What distro and version of Linux are you using? Debian, Fedora, Ubuntu....? Did you by chance try to upgrade the system, or only update packages? These are two seperate functions.

Yep, you are again correct. The issue, I think, is that the PCMCIA port on your laptop is not being sensed correctly. Try doing a search on google, or your favorite search engine on "Linux Thinkpad 600E." Your last command results post confirm this. I'll look around, as well. It most likely has to do with the PCMCIA chipset in the system and the ability of SuSE to detect it. There must be a kernel command setting to fix this, such as one like I asked you to try. Also realize, that these old Thinkpads were made to work with Windows, so that Linux support was not thought of at the time.

This is one of the most difficult modems that I have ever researched. Apparently, it was made by ActionTec for AOL. There is no support on the ActionTec site for it. These sort of legacy modems are a real hassle. The "hybrid" probably means just that..it is a legacy modem made for a specific company for their systems. One way to look at the modem is the hardware ID number. This is sometimes the only way to figure out if it will work in Linux, by comparing it to a like modem. jilow, this is a Linux site that you posted on. Are you looking for a Windows driver, or Linux driver? If Windows, there is no driver for it for Windows XP. I looked on DriverGuide.com and there are only drivers for Windows 98 and 2000. The user who posted the driver contacted ActionTec to get the driver. I would contact them and inquire about the modem. If you get a helpful tech. they will most likely send you a driver, if it exists. You could also contact AOL, if this is your ISP provider. Is you issue that the modem is not listed in the hardware/device section of Windows, or getting it to connect?

Ok, let's try my above suggestions using the pccardctl command, rather than the cardctl one. Apparently, the manager has been changed in SuSE 10. If this works, load the module (modprobe ndiswrapper). Then check the dmesg output. Look at the ndiswrapper troubleshooting page to see if you get output, such as in the example. The correct command options can be found by typing in man pccardctl, or by looking at this readme. However, i have the feeling that I am missing something, or that you need to uninstall SuSE's ndiswrapper and install the sorce package. One final question. Do you have either the kernel headers or source package(s) installed in this system?