pmpatrick

I think it's the recent OpenSSH security update; it seems to have removed the ssh server and not replaced it. I haven't had a chance to examine it thoroughly but the ssh server is definitely gone on mdv 2006 and 2007 after that update. Edit: Mandriva really screwed up on this one. The updated version is openssh 4.5 which replaces v4.3. Thers is no ssh server with the 4.5 package, i.e. no openssh-server 4.5. There is an openssh-server 4.3 which will not install because it is incompatible with openssh 4.5. If you try to unistall openssh 4.5 it wants to take half of kde with it. This is on mdv2007.

A few things off the top of my head that I would try. First, remove the SATA raid controller if it's a PCI card, or otherwise disable it in your bios setup. Second, Western Digital has been known to not play nice with drives from other manufacturers. Disconnect the WD drive and see if the problem goes away. If it does, try reconnecting the drive on the secondary ide channel. Third, check your jumpering on both drives and make sure you have it right. Check your bios setup to make sure it's OK. Fourth, run the WD hard drive diagnostics on the WD drive and make sure it's OK. One bad drive on an ide channel can cause problems for the other good drive.

The generic syntax for a FAT32 partition with read/write perms is: /dev/hd** <mount point> vfat umask=0,codepage=850,iocharset=iso8859-1,exec 0 0 where hd** corresponds to the device file for the partition. Note, if you have a sata drive, the form of the device file will be sd** instead of hd**. The mount point can be anything you want but most people keep them in /mnt and use the form /mnt/win_* for windows partitions. The important part for read/write permissions is the "umask=0". If you are not sure what the device files are for your new drive partitions, open a console and run: $ su <enter root password> # fdisk -l That will list all the partitions recognized by your system, whether mounted or not. Post the output here if you are not sure where to go from there.

I've run into this with some livecds. One way you can get around it is to unmount the drive you want to chroot to and then remount it like so: # sudo umount /media/hda5 # sudo mount -t <filesystem> /dev/hda5 /media/hda5 # sudo chroot /media/hda5 where "filesystem" correponds to the filesystem on hda5, eg reiserfs, ext3, etc. In fact, I pretty much always unmount and remount per the above when I want to chroot and it seems to solve a lot of problems.

Just my two cents - if you use any linux distro on a regular basis and find it useful, you should pay something to the developers to the extent you are financially able and/or contribute in some way back to the project, eg support, bug reports, howto documentation, etc. Re joining the mandriva club, I agree with the many observations stated above. It's completely unnecessary from a utility standpoint as you don't get a lot for your money that isn't available for free elsewhere. However, if, after trying mandriva for a period of time, you like the distro and find it useful, join the club if you are financially able to afford it. It's a way of giving back to the developers and insuring the continued development of mandriva. Completely unrelated to the above, tyme wrote: I haven't checked this out myself, but I'm curious as to why you find LinDVD superior to libdvdcss. Specifically, what extra features do you get with LinDVD that are absent in say totem or kaffeine when used with libdvdcss? I thought one advantage of libdvdcss was you could get around region coding. I assume that is not the case with LinDVD.

According to this: http://www.acronis.com/homecomputing/produ...q/file-systems/ Acronis Disk Director does not support xfs or jfs. That's for v10.0; I have v9.0 which has the same filesystem support. I also believe the enterprise imaging software from acronis does support xfs and jfs but not the home version(True Image 10.0).

Acronis Disk Director is very good if you have it. Excellent linux support and great flexibility in resizing partitions. It can handle ext2, ext3 and reiserfs. You can perform the operations on linux partitions from within windows or boot the cd version and do it that way. I've found it to be the most reliable partitioning tool for dealing with both linux and windows partitions, especially where both exist on the same hard drive. Even so, resizing partitions is the riskiest operation for any partitioning tool so always back up first.

I had a lot of trouble with wpa on a broadcom chipset wireless card on a dell lapatop. I never did get it to work at all with wpa and ndiswrapper so I went to wep. That was about two years ago and I haven't tried recently as I'm not that concerned about security on a home system. WEP is adequte for my purposes. In my experience, performance and capabilities under ndiswrapper vary greatly depending on the chipset of the wireless nic, the kernel and the version of ndiswrapper used. Historically, broadcom has been one of the least linux friendly wireless vendors. Re what's involved in setting up wpa under linux: http://ndiswrapper.sourceforge.net/mediawiki/index.php/WPA To me, that's pretty involved for a newb. Maybe the process is streamlined in mandirva's gui wireless networking tools, but I just don't trust them so I haven't used them to setup anything complex for some time.

It could be the USB 2.0 module is not loaded. Connect the drive and power it up. Then run as root: # lsmod which lists all loaded modules. See if you see one named "ehci-hcd"; that's the USB 2.0 module. If it's not loaded you will only get USB 1.x speeds which are dog slow.

By and large, setting up wpa in linux is a huge pain. You are using a broadcom wireless nic which indicates to me that you are probably using ndiswrapper with the windows driver. Please confirm this or if you don't know what I'm talking about post back and say so. AFAIK wpa will not work with ndiswrapper. Even if you have a native linux driver that is wpa capable, setting up wpa is still very involved. IIRC you need to install a package called wpa suplicant for starters and then the fun begins. The static ip and cloaked SSID are no problem to configure. If you change to WEP on your home system, you can probably set up in linux without many problems. Basically, you can just edit your /etc/sysconfig/network-scripts/ifcfg-wlan0 file. At least that's the most direct way of doing it; the gui tools just indirectly edit this file for you. Post back with more info and I'll try and help.

Given that we have two people with the same non-mounting behavior, I'm guessing this is the default condition for the mandriva livecd. The hard drive is probably not mounted by default for safety reasons.

AussieJohn, have you tried passing any boot parameters with the misbehaving kernel? I would at least try booting with the usual: noapic nolapic acpi=off It would be truly ironic if the problem was with acpi in the new kernel as that would bring us back to ianw's original problem.

If your a mandriva club member, they have a service called "kiosk" which has kde 3.5.4 rpms. The autoupdate through kiosk to kde 3.5.4 worked very well for me. Here's the kiosk website to give you an idea of what's available: http://kiosk.mandriva.com/

The install kernel probably does not have usb mass storage support. There is not much you can do about that unless there is an alternative kernel you can use. Also, that motherboard chipset is known to have problems in linux IIRC.

Take a look in /proc/ide. I'm curious as to whether you have an ide0 and ide1 in there. You should also have an ide2 where you will find hde inside and an ide3 where you will find hdd. It might be your Silicon Image SATA controller causing the reassignment of hda to hde. It's the only thing that I can think of. If the kernels you have used consistently pick up the drive as hde, that's probably just the way it is, but that is very unusual. I'm fairly certain that your hde drive is not being picked up by the mm kernel; the error messages you are getting are consistent with that theory. Have you tried passing any other boot options with the mm kernel?

I've never run into a situation where the onboard primary ide master drive was designated hde; that is very weird. However, I still believe it is a kernel issue with the ide controller. My guess is the new kernel sees that drive as hda instead of hde. Have you ever seen the drive designated hda with any live cd or any other distro you might have tried? Also, how is the drive listed in the bios setup?

Given the designation of your hard drive as hde, I assume you have an addon pci ide controller card that your hard drive connects to. The first drive connected to a pci ide controller is usually hde with the onboard drives taking up hda thru hdd. Those kernel messages indicate that hde is not being detected at all, i.e. it can't find the swap partition on hde6 and can't find the root partition on hde1. This could indicate some kernel problem with that addon ide controller card, most likely an oversight in failing to compile in support for the card. Please post what, if any, ide controller card you are using and your general hardware setup(motherboard, processor, ide and sata drive configuration). With your good kernel, run as root and post the output of: # lspci You could also try passing some of the usual boot parameters with the problem kernel by hitting the Esc key when you see the lilo boot selection screen which will take you to a boot prompt. At the prompt run: desktop_2.6.17.13-mm-3 noapic nolapic acpi=off Those are the first boot parameters tried when having boot problems as acpi can cause all kinds of trouble with certain hardware/kernel combinations.

You would have to research it, but from what I can gather, it's definitely a kernel bug, not a mandriva kernel patch bug. I don't know how serious it is or how likely you are to have problems with it. Here's a fuller discussion of the issue from the creators of xfs, SGI: http://oss.sgi.com/projects/xfs/faq.html#dir2

Just noticed this buried in the mdv 2007 errata: You won't see it listed in the outline errata page here: http://qa.mandriva.com/twiki/bin/view/Main...Linux2007Errata But it is there in the kernel subsection if you click on it. Just a heads up to everyone using xfs as this is filesystem corruption bug in the 2.6.17 kernel from what I can find doing a little googling; you could lose all your data on xfs partitions. Hopefully, a kernel patch correcting this problem will be out soon. For now, I would not mount any xfs partitions with mdv 2007.

I think ffrr has it right. Gowator, if you know of a way where you can take a file greater thn 4 GB and burn it to a data dvd, I'd really like to know how to do that. I just don't think it is possible with the mkisofs that I'm using(mkisofs-2.01.01-0.a03.3mdk). Of course I can create isos greater than 4 GB which is what you did but I cannot create an iso that contains any single file over 4 GB without getting an error message. And we don't appear to be alone with this problem as evidenced by the link I gave in my prior post.

/usr/bin/mkisofs: Value too large for defined data type. File /mnt/data/video_keeping/1015_20061017193000.mpg is too large - ignoring I think that pretty much says it all; it's a file size limit, apparently 4GB, with mkisofs. Here's another discussion of the same problem where a similar conclusion was reached: http://episteme.arstechnica.com/eve/forums.../m/351004821831

Mine use a reiserfs for the temporary file and it will not burn any file over 4GB. I have many files on that partition over 4GB so it's not a problem with the maximum file size on reiserfs.

I know iso 9660 had a 2GB file size limit. UDF had a 4GB file size limit IIRC. I thought both filesystem formats had been updated to get around these file size limits. When you burn the dvd, try going into the filesystem tab when the burn window pops up and tick the "Generate UDF structures" box and see if that helps. Also, which versions of mandriva and k3b are you using? There are some reported problems with burning dvds in mdv 2007. Edit: Just experimented a bit with LE 2005 using k3b-0.11.20-7mdk. Can burn a 3.5 GB file in a data dvd using dvd-rw; can't burn any file over 4 GB. Checking the UDF box made no difference.

You will have to change your entry in /etc/fstab on the new partition to correpond to your new root partition, /dev/hdb1, as well.

There's nothing really mysterious about this from a linux point of view. If you installed the new drive after your linux install, it won't be automatically set up in linux. You have to configure the new drive. Per paul's above post, open a console and run: $ su <enter root password> # fdisk -l and post the output here. That info is needed to properly setup the new drive. However, your windows install problem is something you need to explore in a windows forum. Vista may not like the configuration of the drive for any number of reasons and those more familiar with vista's quirks are in a better position to help you.