emmanuel_uk

I do not think this would happen with dd and ext3, but do not quote me on this. From small partition into a bigger partitions being unmounted dd if=/dev/hd_input of=/dev/hd_output +options then resize2fs /dev/hd_output takes care of resizing the file system (not the partition) including the journal. AFAIK it looks at the inodes etc. cannot be any problem with the journal, should be clean before dd, and then it is cloned

>>might have to look into that alternative I do not know any other way when you want to shuffles partitions especially if the start of the partition needs moving. There is an excellent thread somewhere called "Learn the dd command" It gets quite interesting when you dd from one partition into another of different size (be it smaller or bigger)

Ianw1974 I thought as you at first, but then https://support.ati.com/ics/support/KBList.asp?folderID=356 says As of driver version 8.29.6 support for the following products is no longer included: Radeon® 8500/9000/9100/9200/9250 Mobility™ Radeon® 9000/9100/9200 Radeon® IGP 9000/9100/9200 Users with these products should use driver version 8.28.8

Thanks for your post. Below more details and thoughts This is very very interesting. Never thought of that as the problem was very new to me (it might have occured once on a single packet with 2006? but did not pay attention at the time. I have been on boards for a while but never seen a post about that, saying that I was not looking for it). The 2007 DVD is an iso (from bittorent, the dual arch 586 / 64 bits) burnt with k3b at 8x. The md5 sum and gpg signature were fine. The media is a generic 8x DVD-R. I have used many of these with other distros, never had a problem. (but yes, this does not mean that very one was/is not well balanced or wrapped). The laptop is an IBM R40e a bit old hence (DVD combo, not even cd writer, but up to 16x read I think). Ok a laptop reader can be a a bit fussy; I first used a DVD-R datawrite yellow 16x burnt at 8x. This would not even boot, whereas that same yellow DVD would boot ok on the desktop (I assume it is an optical problem or something to do with the header/descriptor being incompatible with the dvd firmware; do not know). I am 90% sure I installed mdv 2006 from a backup of cover magazine on a DVD-R datawrite yellow 8x burnt at 8x. This did not have a problem. Anyway back to the random failure to read/decompress rpms during install What is strange is that on failure to read/decompress the rpm, you can see in consoles F3 and F4 mode that the laptop does retry about 4 or 5 times. As the error is random on full install (it is never the same rpms that fail to install), the wobliness should be overcome by the retry. It could be that the retry works from memory without a reread or re-spin of the dvd (I am not sure). From experience distro are more or less fast to install and are probably using different DMA settings with cd/dvd players, so an agressive DMA setting could worsen the situation (I can tell you it is spinning fast) But I have never seen a failure to install a packet in any other distro... and I do not believe the dvd player is bust or dirty (did install freebsd with it) The randomeness is low in the sense that once the problem occurs you can have a series of errors, then it will stop for a while then restart having read errors (got about 15 in total during one install). Either way, this sounds also like a bug in the installer (not retrying properly). What do you think? What makes it worse when a rpm fails to install, one gets a message [continue yes/no], if you say no then you get a kernel error and that it is it, all finished, or you go in a forever loop menupackageselection - kernel error - menupackageselection (cannot remember for sure which menu) Out of curiosity I will see if I can try another dvd media. I hope this is no thread hijacking

when I went back from 2006 to 2005 I had the bad surprise to see that something had changed in kmailrc (in /home/myusername (in the syntax) and it was enough to prevent reading my emails. I used a backup to find out what changed in kmailrc So it does not answer your question, but it is close enough to be a bit relevant to this topic, hence my post

Gowator, is this related: during my install of 2007 (on a laptop) random rpms cannot be installed (<al><ctrl><f3>) show a dvd error read (cannot decompress rpm), I know the md5 sum is fine, and I am pretty sure my dvd player is fine, (ok maybe the media was not fine, but that would be the first time here) Different install block on different rpms One of the solution is two install, then do an upgrade, eventually all rpms get installed

sorry to hear it did not as well as you planned Maybe if you post them and explain what you did somebody can help you to learn how to do it. I did say it was risky. But it is an opportunity to learn by trial and error. I really that the main way to learn about moving partition with dd

yes it does, but not when people do not know how to burn an iso. (ie burning sonthing.iso to the cd instead of using the right menu to burn an iso) This is a common error, and it is better asking asap where the cd is coming from, this is just newbie posts I have seen many times but yes I am a bit off re-rereading the post, if the startup screen comes up the cd might be ok This is what I do not get

about anything that work in a given linux distro is going to work in another distro, so in theory yes it will work

Upgrade from 10.0 to 2007 is not really a good idea (far too many difference). Maybe 10.0 was badly burnt (did you get an iso and burnt with Zinblows?). Anyway you are best starting with 2006 or 2007 anyway welcome to the board, I suppose Mods are doing this

a note of warning, when deleting/adding partition you can end up changeing their number, hda6 becomes hda5. Have the rescue mode ready to change /etc/fstab and /boot/grub/menu.lst As far as dd is concerned there are tutorials. You can slot and move partition this way if you have enough room There is a resizefs function in linux, but this is only once you have dd something into a partition of different size from the source It is all risky still my experience is that drakdisk is too clever for its sake and can confuse cfdisk. I agree a live distro may be easier PS: dd works from the rescue console mode of the install cd/dvd of mandy

if you ever want to learn about bash scripting the reference is the advanced bash scripting guide There are also tutorials around for less advanced uses Much more flexible than *.bat

thanks, figured as well that k3bsetup was not that important because there was no newer version for mandy 2005, and the version I had had display bugs. saying that I agree too much compilation is a waste of time We have hijacked the thread: still waiting for forcedeth to give some news (maybe it is forcedeath that nic card)

The 9250 drivers closed/opened where compared there BTW http://www.phoronix.com/scan.php?page=arti...m=463&num=1

Thanks, you gave me half the solution If I use vga=ask single then at some point during boot the font resize to its default. Strangely vga=7xx single makes it permanent (this kind of behaviour difference vga=ask vs vga=7xx I would never had imagined) That is what I am trying to do. Once in single mode. I will post here if I ever find out

look for clues by doing as root cat /var/log/Xorg.0.log | grep EE cat /var/log/Xorg.0.log | egrep 'EE|WW' glxinfo can tell you things as well But I think you are looking at what is called "cinerama"? have no experience with that. I think there is a menu in mandrake configuration center, and I do not know the capability of the ATI driver Also sometimes laptop hotkeys do not work Can you even switch display? (Fn key + something?) re hotkeys for laptop there is a kde application that needs setup, it is called Kmilo (it could be called something else, look for the laptop submenu in kde configuration)

I think for completeness you should tell us which ati card you have

euh, thanks. The proof will be in the pudding (English saying) Like your last post on k3b; got a similar problem having it compiled from source. But can live without k3bsetup. The mutual appreciation society ;)

the focedeth is a module for the nic card. Try to disable it in the bios for example (just ofr the install). Also 2007 shipped with one magazine has an issue with dhcp, so try to install without setting up any network interface, this is not an acpi issue you can try noapic nolapic

on my PC the apm kernel module needs to be loaded, for proper shutdown, despite the fact that the bios is not apm compliant

My experience is that xorg settings can be less agressive/different from one version to another. Sorry we cannot help you further with the open driver (I remained convinced the speed difference is a question of settings; you may want to compare outputs of glxinfo) It may even be that the agp kernel module is not properly loaded (I had this once)

I have never ever ever tried, (seeing lots of post on it made me think no much point trying) but if I do I will let you know. By open I mean I used the xorg driver There is a patch out there to get AGP 8x instead of 4x for the ati open driver, I have never tried but maybe will one long week-end re performance, I have posted a long thread re that for the 9250, even testing w/w overclocking the CPU (on another forum)

I have a 9250 and get about 1000 fps in mandy 2005 with the open driver. It sounds like in 2006 you did not have dri loaded or something like that. The no of color you selected as well play a role. Did you look into /var/log/Xorg.0.log WRT ati driver, the newest one does not support the 9xxx series anymore (it might from time to time in next releases) but ATI has asid they were concentrating on the high-end

I am sorry I have no other suggestions apart from trying another distro live CD (but I imagine you had linux working before) Maybe a bad burn cd. Try it on another PC I am stumped, sorry if you have another distro working maybe you could copy the xorg.conf and see if there is a difference, but really not a great suggestion

had same problem when compiling my own kernel. see with lsmod if the module apm is loaded otherwise load it with modprobe apm most likely something to do with acpi or apm anotherway to find out is using live distros of all sort and see which one shut down ok and look at the kernel modules with modinfo