Ixthusdan

I switched back to mirrors in the US yesterday and all was well. I think the burp will go away over the next 24-36 hours world-wide.

I have no idea what your system looks like, so I can only guess at what you see. But if you did not install a boot loader, you will not be able to access an installed system. Better yet, please boot with the live disk, and tell me what disk drake sees on your hard drive. Please use Linux labels, not windows.

You need to install the bootloader in order to choose which system to boot. It should be installed to your primary boot partition, which would be either hda1 or sda1, depending if you have an IDE or SATA buss. Some terminology is useful. You have one "drive" with several partitions. A partition is a division on a drive. Windows is rather misleading in that they lable partitions and drives with the same lettering scheme. That is why one cannot tell in a windows file manager what is in the computer. In windows, you have to right-click on My Computer, choose properties, and then select the hardware manager to actuall see what is on a drive. While in the My Computer file manager, you can right-click on C, choose properties, and it should take you to the hard drive gui where you can see the different partitions, rather than confusing letters.

Welcome! First, do not partition with windows. Linux uses a different systems, and windows cannot use Linux nor can Linux use windows. Also, you do not need to have any more than 1 partition for Linux. There will be an area called swap, but that can be very small, say 512K. What I need to know is your drive layout. As you have discovered, the windows nomenclature tells nothing about the drive. Linux uses a nomenclature that describes the drive location and the partition number on that drive. So, sda1 is the first partition on your first sata hard drive. Generally, windows must be installed on the first partition of the primary boot drive, or it won't work. But Linux can be located anywhere. When you chose "existing space," it actually tried to use windows space. Select "unused space on the windows drive." The 16G free on your "C" drive should be fine for an installation. Allow the installer to auto-allocate that space.

Ahh. Well, it is a good device to setup, then! :P

More wireless news. I have the typical inexpensive (OK, cheap) Broadcom wireless in my laptop. At one time, only ndiswrapper would work for me; the bcm43xx native Linux driver simply would work. And, I would have to blacklist the native driver before ndiswrapper could assume control of the device. Otherwise, one would get a loaded module and a known device, but no internet link! But, with 2008, I can simply choose either driver and switch, all fro the GUI, without any hassles! That is a major improvement for wireless networking and Broadcom devices. 2008 is great. :D

I think the point is that the device has issues. Any distro simply needs for you to make some entries in order to assure that the device is setup correctly. A live distro loads a plethora of devices for function; an installation is tailored to only what is needed. If the device happens to be detected correctly, then the distro setup is fine. It is common place to be sure that problem devices have the correct entries so that they are not a problem! :P Unfortunately, you seem to be assuming that Linux has problems. I beleive the device is a problem. There was a day when only hardware modems would work in Linux. Today, most winmodems (Which are not true hardware devices) work, thanks to the efforts of the community. (The manufacturers do not release the appropriate details in these cases!)

I have a Broadcom wireless NIC, which is quite frankly a nightmare piece of hardware. I installed bcmw34xx, which worked, from MCC. I then decided to see if ndiswrapper would be just as easy to install. It was. All I did was type "urpmi ndiswrapper" in a terminal as root, and I could then use ndiswrapper as a driver choice. I did all of this with a fresh installation and no network access until I brought the wireless up. (It is a peeve of mine to have to ac cess the internet in order to get a laptop on-line!!) MCC=>Network and Internet=>Set up a Network interface Choose the wireless option and follow the steps. BTW, Mandriva Control Center is also called Configure Your Computer. The Control Center is just for KDE. Use MCC.

That is a good question. I think that I read somewhere that one may patent a code, but not a result. After all, there is more than one way to code a result, isn't there? (At least I hope there is!)

Yes, the md5sum on the sight is correct. I would switch to ftp.nluug.nl/ They have good bandwidth and I have rarely had a problem getting through. And I live in the US!

If you install the kernel source package, urpmi will install everything you need to compile stuff. "urpmi kernel-source" However, I must admit that I think there is something else amiss. All the packages to use either bcm43xx or ndiswrapper are on the dvd/cdrom. You should not be compiling anything. I have used both bcm43xx and ndiswrapper on my laptop, and did not even have to download anything. It was all on the dvd. There is something else wrong with your installation, IMO.

When I read about the card, it seemed to be a real RAID card. But, if it is indeed software RAID, then yes, the driver must be in place for the card to do its thing. I went to Adaptec's sight. Looks like you get the source code here. So you'll have to install on one drive; compile the driver; then move the system to RAID. I would set up two RAID sets initially. The second set will have to be built after compiling the driver. Sounds like a lot of work! B)

I encountered the same problem, but the dkms packages work just fine. I am running an SLI setup, and the dkms drivers would not work in 2007.1, but they work fine in 2008.

If those things are happening under Linux, it'd be a good time to replace the RAM! Might be a CPU issue as well.

Why not set the controller fo 2 RAID sets and install Mandriva on the set of your choice? It is the card that determines the RAID id to the bus. Turn on RAID, and Mandriva should recognize it.

Do not use a /boot partition for Mandriva. I use /, /home, and /usr. (with a swap of course) In your case, you could use just a /. Get rid of /boot.

With Nvidia cards, I use the vesa driver in order to get a gui from which one can install the proprietary drivers. Or, you can boot to CLI and install from there.

error 24 is an attempt to use a block outside of the address; in other words, a borked partition. B) Try reinstalling GRUB from the emergency boot menu. But repartitioning may be the only real fix.

I can confirm that the US servers were not responding today. I switched to nluug.

I am absolutely amazed. For the first time, I installed Mandriva on my laptop and got my wireless going with the native driver..... and it actually works!!!! I did not have to mess with anything. Now I am feeling a little insecure. B)

*yawn* Of course Microsoft is behind it. They have not had an original idea since Gates left Apple.

With an nvidia card, you should not install so it will automatically boot to GUI until after you get the good driver in place. The nv driver is just a problem. I install to CLI. When I launch the GUI via "startx," I can edit for errors and get a desktop. But then I also down load the latest nvidia driver and install it at first launch. If the kernel sources do not install by default (why not??) then you can "urpmi kernel-sources" and then run the nvidia driver installer. Frankly, it is just easier to get a GUI using the vesa driver and going from there. It will be ugly until you install the proprietary driver anyway.

I have not had problems of a normal nature. I do run an SLI set up and 2008 plays for 3-4 minutes and then reboots the computer!! 2007 did not do this, and since windows runs fine I know it is not the hardware. I might switch to the nvidia drivers rather than the pre-packaged drivers. They would not work at all in 2007 but in 2008 they do work..... for a few minutes! B) For clarity, the above only happens during game play. Otherwise, 2008 runs all day long under normal computer usage. (SLI and gaming are not normal!)

Thanks for the heads up!

Updated the last RC tonight, and I now am running 2008 official!!