wrc1944

Thanks all, I unchecked the "assign hostname from dhcp" box, as per the recommendations, and my prompt is now back to normal. wrc@localhost wrc]$ su Password: [root@localhost wrc]#

I guess I wasn't too clear before- the problem I'm having is only on the Mandrake box. I've looked around extensively in the Mandrake /etc directory and can't find any files with the "ip24-250-199-108" relating to the bash prompt, or in fact, any file at all referring to it.. Maybe I just don't know where to look. The files you mentioned are in Gentoo, but Mandrake does not use them.

I just went to Cable from years of dialup, and setup winXP and Gentoo connections without too much trouble. I then got my Mandrake 10.1 box connected OK, but now I have this in any terminal (kde-konsole, aterm, gnome, or xterm), but only with the Mandrake box. [wrc@ip24-250-199-108 wrc]$ su Password: [root@ip24-250-199-108 wrc]# Everything seems to be working perfectly OK, but I'd still like to know why I have this strange bash prompt, and how to get rid of it (the "ip24-250-199-108" part) , without messing up my Cable connection. Any advice or insight is greatly appreciated. Thanks, wrc1944

phunni is correct, you can share /boot and swap. You'll find the thread link below a good in-depth tutorial on installing Gentoo on the same hard drive, from a working Mandrake installation. It probably addresses any possible question or misunderstanding you might encounter, because I certainly had a lot of them! http://forums.gentoo.org/viewtopic.php?t=6...5877&highlight= Puggy and Neje really helped me do my first Gentoo install with this method, walking me through the entire process step by step. My main problems arose because I'm on dialup, and the Install Doc didn't address many things I was running into, and I lacked the basic Linux experience to recognize the obvious solutions. Basically, you just boot into your mandrake, and chroot over to the partitions you wish to install Gentoo on. I shared my Mandrake /boot and swap partitions with Gentoo, with lilo as the bootloader- worked fine. I hope it helps you avoid this: Good Luck, wrc1944

You might find this entire thread a good in-depth tutorial on installing Gentoo on the same hard drive from a working Mandrake installation. It probably addresses any possible question or misunderstanding you might encounter, because I certainly had a lot of them! http://forums.gentoo.org/viewtopic.php?t=6...5877&highlight= Puggy and Neje really helped me do my first Gentoo install with this method, walking me through the entire process. Basically, you just boot into your mandrake, and chroot over to the partitions you wish to install Gentoo on. I shared my Mandrake /boot and swap partitions with Gentoo, with lilo as the bootloader- worked fine. I hope it helps you avoid this: Good Luck, wrc1944

I looked for 3.1.4 srpms in cooker, but only found the 3.2 beta1's. I'm seriously considering rebuilding the 3.2 kde srpm set when beta2 or rc1 comes out. I figure why build 3.1.4 when 3.2 is so close. I feel reasonably sure I can do it, as I've done xfree srpms optimized for athlon-xp before, with no problems. I also built kde 3.0.3 from cvs source tarballs once on Mandrake 9.0, and that worked OK. I did download a huge set of 3.2 beta1's precompiled rpms from another site, that were from 10/28-11/03, installed them OK, but ran into too many bugs for them to be usable- turned out to be a big waste of time. They were going to fix them, but never updated anything, AFAIK. (I've been on my Gento box for the last few days, so maybe they did). On dial up, and it's a big long job, so I'm waiting until I hear more about the ones on cooker now, or kde beta2. If anyone has experience with 3.2 beta's, please post. Seeing as how there are no MDK 3.1.4 srpms that I can find, maybe they are just skipping them, and finishing off 3.2. wrc1944

Kormac, I had trouble patching kernels at first too- now it's second nature. Add the patches before you do xconfig. What I do is put the ck .bz2 patches desired into the linux-2.4.21 directory, cd to that directory, and type: bzip2 -dc whatever-patch.bz2 | patch -p1 Be sure and do them in order, with the ck base patch first, and performance patches you want, and then the extra patches, like supermount. Also change the Makefiles before doing make dep. wrc1944

I recently learned you need to update these files to work with 2.5.xx kernels properly. I haven't hooked up my test box and tried it yet, so I can't say if it works, or not. I'm not quite yet willing to install them on my main box, although they are supposedly backwards compatible- but I've heard that before, and messed up my installation. I'll hook the test box up in a day or two as time allows, and give 2.5.75 a try with the upgraded files. http://supermount-ng.sourceforge.net/mdk-25/ These are built specifically for Mandrake 9.1, so it's probably OK- but again, I can't vouch for doing this- I don't know if they coexist with the old versions for 2.4.xx kernels, or they replace the old ones, and are indeed backawards compatible. If anyone finds out before I do, please post here with your results. I'll do the same. wrc1944

I've had varying success with 2.5.67-2.5.73. My problem boiled down to I could either get 2.5.xx's to work OK without serial drivers enabled, therefore no modem and internet connection, or enable serial drivers, get regular modem usage, but then have all sorts of bizarre file manager and console problems. l'd get weird hangs and freeze-ups, 4-8 minutes to open ~/home or different windows, couldn't do copy/paste operations, freezes on shutdown on a blue horizontally streaked screen, etc. If I then recompiled without serial enabled, all the problems vanished. I never figured it out, or came up with a config file that eliminated even part of the problems. I'm waiting for the 2.6pre versions, which should be here very soon. wrc1944

The xp flags will work on the later versions of Durons. For sure the 1300Mhz, as I have done it with that cpu , and I believe anything after and including 1100Mhz. These versions of Durons are actually xp's with a smaller cache- the architecture is supposedly the same. If you have an earlier Duron, leave out the =sse flag, and drop the "-xp" and that should work. They are just cut down Athlon T-birds, AFAIK. wrc1944

For those interested, I recompiled the 2.4.21-0.16mm-mdk kernel with pretty aggresive athlon-xp optflags, and it works fine. These flags also work on other kernels I have tried. The trick in making them take when compiling kernels is putting them in the linux-2.4.21-0.16mm-mdk/arch/i386/Makefile, in the following manner. First, I installed the MDK multimedia kernel and kernel-source rpms in the usual manner. Then I copied the resulting source directory placed in /usr/src to my "kernels" directory in ~/home. Then copy the .config file to another location, go to a console, cd to linux-2.4.21-0.16mm-mdk and do make mrproper. Then go into the above mentioned Makefile, and comment out the current MK7 flags, and add the new flags stanza, like shown below. --------------------------------------------------- #ifdef CONFIG_MK7 #CFLAGS += $(shell if $(CC) -march=athlon -S -o /dev/null -xc /dev/null >/dev/null 2>&1; then echo "-march=athlon"; else echo "-march=i686 -malign-functions=4"; fi) #endif ifdef CONFIG_MK7 CFLAGS += -march=athlon-xp -falign-functions=16 -falign-labels=1 -falign-loops=16 -falign-jumps=16 -mfpmath=sse -maccumulate-outgoing-args -fprefetch-loop-arrays endif The =16 values set things to corelate precisely with the athlon-xp's design parameters, which I would think are pretty important. This is said to allow the on-die cache to be fully utilized and filled with 16 byte segments. ---------------------------------------------------- Then do make xconfig, and import the config file you copied before, and do any editing needed. (In my case, I removed some 3rd party stuff that caused depmod errors for modules concerning ethernet cards etc. not found when rebooting, but it does no harm.) Save the config file, and edit the main extra version Makefile (not the one you put flags in) like below: VERSION = 2 PATCHLEVEL = 4 SUBLEVEL = 21 EXTRAVERSION = -0.16mmxp Then do the usual: make dep make clean make bzImage make modules su to root make modules_install You will get a warning in make modules (among a few other minor ones) as shown here: cc1: warning: -fprefetch-loop-arrays is not supported with -Os This only occurs in one small section where -Os apparently takes over, and does no harm AFAIK. -Os then releases, and -fprefetch-loop-arrays comes right back. (Can anybody explain this?) As long as you get done with no actual errors and compile bail outs, you are OK. I don't do the usual make install, but manually copy bzImage and System.map to /boot, adding the kernel name-version, like below. [root@localhost linux-2.4.21-0.16mm-mdk]# cp System.map /boot/System.map-2.4.21-0.16mmxp [root@localhost linux-2.4.21-0.16mm-mdk]# cd /home/wrc1944/kernels/linux-2.4.21-0.16mm-mdk/arch/i386/boot [root@localhost boot]# cp bzImage /boot/bzImage-2.4.21-0.16mmxp Then edit lilo, adding the stanza for the new "xp optimized" mm kernel, omitting the initrd line: image=/boot/bzImage-2.4.21-0.16mmxp label=2421mmXP root=/dev/hda10 append="devfs=mount hdc=ide-scsi acpi=off quiet" vga=788 read-only Save, run lilo, and then reboot. I don't think I left anything out. wrc1944 :D

SoulSe Well, that's what happened- I finally wiped the drive. After I bzip2'd /home, Mail, and Documents in separate bz2 files, and put them safely in my little 1.5GB /usr/local partition, I felt brave enough to attempt reformatting home, and reinstalling. Big mistake. Everything went OK up until I tried finishing up the reformatting of /home. The MBR and superblocks had changed somehow, and I couldn't get out of it or make progress in DiskDrake (even though I know it very well). It wouldn't go into the final partitioning stage, because it couldn't read /home- it had changed to HOME. I then tried the rescue cd- messed around with it some and finally went to console vim, looked around some, and then tried to restore from usr/local using MDK's little tar script which I had used to bzip2, but since the tables had been rewritten and apparently weren't being recognized by tar xvfj, my fstab was fouled up, and I was really stuck. I then put the drive in another box (that has a burner) as slave, and tried to access the partitions from my main MDK install- still no go. Couldn't mount any partition on the slave, although they were all formatted. Then I decided to reinstall MDK and wipe everything except /usr/local with a minimum install. That worked, and I was able to mount /usr/local on the 9GB drive from the big drive's installation, and burn the bz2's to cd. Whew! What a learning experience. I'm now slating this 9GB drive for Gentoo only, just to see if I can figure that out- then maybe copy all the Mail and Documents back into the Gentoo install (if I get that far). Thanks for the help, wrc1944

tmye, I appreciate the response, but I'm as confused as ever. Re: chown -R wrc1944:goupname ./* What is the groupname supposed to be? rob? And, what does the ./* signify- any dir/file I wanted to copy to rob? qnr, I did login to as rob, and I can read files in /home/wrc, but can't copy them to rob. wrc1944 is in rob's groups. I'm still not understanding how I can copy files in wrc1944 to /home/rob. I guess Ineed an example of the exact code or procedure, say for a file in /home/wrc/xxx to be copied into /home/rob. Do you mean while logged in as wrc1944, I open a console, and type: $ newgrp - rob When I do that, and type rob's password, I get: [wrc1944@localhost wrc1944]$ newgrp - rob Password: Sorry. [wrc1944@localhost wrc1944]$ Any ideas as to what's wrong? wrc1944

This might sound lame, but I've only been using one user (wrc1944) since I started linux. I just added another one (rob), and can't figure out how to be able to be able to copy stuff into each other's /home directory. I tried going into userdrake, and putting them in each other's groups, but when I go to a console in wrc1944 (or even su to root), and do something like: cp- a Documents /home/rob I get a no permissions error, even though "rob" is in wrc1944's groups. Same error, other way around. I know it's some chown or similar command I need, but it just escapes me! I thought root could transfer anything between different users, but I must be missing something very simple. My primary objective is to have user wrc1944 be able to transfer anything into "/home/rob." Thanks, wrc1944

Here's a copy of a post I made over at pclinuxonline, requesting new MDK rpms for Parted, and QTparted. Maybe someone here can offer some insight? Thanks, wrc1944 ------------------------------------------------------------------------------------ Ranger, Maybe I'm dense, but with DiskDrake I can't seem to find a way to move the location of a partition on the hard disk like you can with Partition Magic. As an example, on one test box, I'd like to delete two partions at the end of one hard disk, and then slide my /home partition to the end, leaving free space in front of the /home partition, and after the remaing MDK partitions. My objective is to then delete the remaining MDK partitions, and try installing Gentoo towards the front of the drive, retaining my /home (from MDK). If that fails, I then reinstall MDK. After reading the Gentoo install docs and reading their forum many times, it just seems safer to have all the free space to create the Gentoo partitions at the front of the drive instead of trying to create them with the old MDK /home right in the middle. This drive is only 9GB and almost full, so I don't want to try dual booting on it, as my 3GB /home has gotten almost full. There is no cd burner on this box to make a full /home backup with. Another question: How can DiskDrake, or for that matter Parted, safely resize a partition without loosing data, since your don't defrag linux partitions to consolidate all the data at the front of a partition? If you don't defrag, and after deleting and writing data to /home for a year, it would seem like the data could be anywhere on the disk- or am I still thinking in terms of windows file systems? All these operations would be easy with Partition Magic in windows. If there are ways to do this with DiskDrake, I'd sure like to be enlightened.

I just looked at the Open Office and Mozilla directories for athlonxp at the ftp download site. After I right clicked and selected properites to calculate the sizes, both directories suddenly became locked to me- says I don't have enough permissions to open them. The "locked" icon replaced the regular folder icon. What happened, and why? wrc1944

I thought the first image stanza in the list and the "default=" line had to be the same. In other words, if you want windows to be the default OS, it's stanza should be first in the lilo list. Your lilo's first image stanza is: image="/boot/vmlinuz" label="Mandrake" root="/dev/hda6" initrd="/boot/initrd.img" append="devfs=mount hdc=ide-scsi acpi=off quiet" vga=788 read-only This would explain why it's still the default at boot, even if your default= line refers to windows. Try moving (inserting) the windows stanza to the top position the "Mandrake" stanza now occupies, and reboot.( Of course, don't delete the Mandrake stanza). wrc1944 :wink:

UPDATE: A warning: After two days, when I tried to shut down the box, things went haywire, and I was unable to reboot to any kernel- mesage box said /home did not exist (actually it was still there). I finally had to reinstall Mandrake, but I do that every 6 months anyway as a matter of course. Even Linux gets cluttered up. Apparently, my mistake was doing the final "make install" AFTER "make modules_install" at the end of compiling the kernel, which uses the kernel script to copy to /boot and edit lilo. Anyway, after reinstalling Mandrake, I recompiled 2.4.21-rc7 with the ck1 patch, and the supermount patch, but this time manually did the copy of System.map and bzImage to /boot, naming the kernel image bzImage-2.4.21-ck1. I then manually edited lilo, and rebooted the the new kernel OK- this time I had no problems. I'm building in /home/kernels directory, so maybe the fact of not being in /usr/src messed up the "make install" I did the first time. I'll not trust the kernel install script again! However, supermount still doesn't work even with the SM patch, but everything else is great, and I have access to other kernels as usual. wrc1944 :)

For those interested, there's a brand new Con Kolivas -ck1 patch against kernel 2.4.21-rc7. I just tried it on Mandrake 9.1, and so far so good, except no supermount (if one cares). I just applied the 2.4.21-rc7 patch to 2.4.20 source (did mrproper first), then applied the ck1 patch, and then did make xconfig. I loaded the stock Mandrake 9.1 2.4.21-pre .config file, then I selected for my cpu (athlon), said no to some various hardware devices and options I never use or have. (wound up with a 1.1MB kernel image) Then did the usual: make dep make clean make bzImage make modules su to root, and: make modules_install make install Then I checked /boot and /etc/lilo.conf just to make sure all was correct. In my case, I removed the old 2.4.20-ck7 kernel and 2.4.20-ck7 /lib/modules, and lilo entries. Ran lilo again to finish up, and rebooted, Booted fine, and I'm now using the new patched preemptive kernel from Con Kolivas. Seems really responsive. Robert Crawford :D

You can edit the cflags in /usr/lib/rpm/rpmrc file, or better yet, make a new tree for building rpms in your /home. That worked for me rebuilding the 2.4.21 srpm multimedia kernel from contributors. Works fine. Afterwords, you just install the new athlon kernel and kernel source rpms- it does thhe lilo stuff for you.I posted the procedure on pclinuxonline, and I believe in this forum. Check out aru's explanations in the tips section. oh yeah, here it is- check this out. http://www.mandrakeusers.org/viewtopic.php?t=4655 wrc1944 :D

After my initial impressions, and as I predicted, I seem to be having other issues beyond the two I mentioned. Kde apps (among others) seem to have problems saving things, and/or take forever to open. Opening multiple windows of say kedit, seems to cause weird blank windows and temporary hangs, but then up to three minutes later, they sudden pop up, or complete the requested action. I just tried to send an email with kmail, and it took 2 minutes. When I first noticed the kde issues, I tried to open gedit, and save something in it, but it seeming never opened, so I went on. Then 4 minutes or so later, it suddenly popped open out of nowhere. So apparently it isn't entirely a kde problem.Same deal on saving something in kedit- the save as dialog box suddenly pops up ready to save 5 minutes after I gave up on it. Other than these issues, it seems at least as fast and responsive as the mm 2.4.21 on the internet, but of course these problems I'm having make 2.5.69 unsuable at the present. If I can get advice about fixing this, it would be great- I just am not sure I have enough knowledge to track it down by myself- but I'm only a few hours into using it, so who knows?. wrc1944

I'm amazed! I finally had success is getting 2.5.69 to boot with a generic 9.1 installation! Forgot to compile in ppp, so I'm re-doing it, and I'll post back when I'm done. It's definitely faster and snappier.There are still other problems, like I can't access MCC or anything that needs root from the kde GUI (command line as root works), and the shutdown hangs with a weird bluish horizonal lined screened, but all Apps and my Radeon 9000 Pro video card 3d seem to work fine as user. Anyway, for an amateur like myself this is major progress after many months googling, posting to groups and forums, endless 2.5.xx kernel compiles and trials, and head-banging/ hair pulling! I figure now I can get to some fine tuning, and gradually add things back into this stripped down version of 2.5.69. UPDATE: Recompiled with ppp stuff in, and I'm on the internet with 2.5.69 as I type. If anyone can give me some pointers about the above mentioned problems, please post. I'll probably run into more broken things, but so far, so good! At least now I know I'm not hopelessly incompetent. If anyone is interested, I can post a brief rundown of how I did it, and a copy of my 2.5.69 .config file for reference. wrc1944 (Robert Crawford) :D

drsatch, I've been reading that people were having problems rebuilding the kde 3.1.1s. So, your experience is that doing it as root works? Are there any other roadblocks you encountered, or is everything functioning OK, and has performance increased? wrc1944

I just rebuilt XFree86-4.3 srpm again, with the following flags: optflags: athlon -O3 -march=athlon-xp -mmmx -msse -m3dnow -falign-functions=64 -fprefetch-loop-arrays -mfpmath=sse,387 -fomit-frame-pointer -pipe -ffast-math -fforce-addr -fno-strength-reduce I've done it 5 times, changing the flags slightly, but every time I get gcc warnings like below, or similar. No matter how many or how few warnings I get, the rebuild of the srpm goes to completion with no errors, and writes all the new athlon-xp rpms, just like before when I did it weeks ago. I haven't installed them yet, as I already have rebuilt for athlon XFree86 which works great- I was just messing with new flags like -fprefetch-loop-arrays -mfpmath=sse,387 -flaign-functions=64, as I read they were specific for athlon-xp, and increased performance. Removing -mfpmath=sse,387 -flaign-functions=64 doesn't eliminate the warnings, and once increased the number. I've googled for days, and can't find any info on gcc warnings, and which ones are critical, or not. If it was anything other than XFree86, I'd just go ahead and install, and see what happens. One groups list mentioned 90% of them are not going to ruin the build, and can usually be ignored. My questions are: Just how serious are gcc warnings, and do they mean you should not install the new rpms you rebuild if you get them? Or, are they just that, "warnings," and don't necessarily mean the rebuilding went bad? Does anyone have advice or experience with this, or is there a good article where I could read up on this topic? The gcc manual has only a few sentences, that don't really answer my questions. Thanks, wrc1944 TYPICAL WARNINGS DURING THE REBUILD: rman.c: In function `RTF': rman.c:2701: warning: string length `583' is greater than the length `509' ISO C89 compilers are required to support -------------------------------------------------- lcUTF8.c: In function `iconv_cstombs': lcUTF8.c:1845: warning: assignment discards qualifiers from pointer target type lcUTF8.c:1873: warning: pointer targets in passing arg 1 of `wctomb' differ in signedness ----------------------------------- ../../../../../../extras/Mesa/src/tnl_dd/t_dd_vb.c: In function `mga_interp_extras': ../../../../../../extras/Mesa/src/tnl_dd/t_dd_vb.c:343: warning: unused variable `mmesa' ../../../../../../extras/Mesa/src/tnl_dd/t_dd_vb.c: In function `mga_copy_pv_extras': ../../../../../../extras/Mesa/src/tnl_dd/t_dd_vb.c:370: warning: unused variable `mmesa' --------------------------------------------- In file included from mgavb.c:137: ../../../../../../extras/Mesa/src/tnl_dd/t_dd_vb.c: In function `copy_pv_rgba4_spec5': ../../../../../../extras/Mesa/src/tnl_dd/t_dd_vb.c:52: warning: pointer targets in initialization differ in signedness -------------------------------------------------------------- mga_xmesa.c: In function `mgaInitDriver': mga_xmesa.c:129: warning: pointer targets in assignment differ in signedness ----------------------------------------------------------- In file included from radeon_tcl.c:239: ../../../../../../extras/Mesa/src/tnl_dd/t_dd_dmatmp2.h: In function `tcl_render_points_verts': ../../../../../../extras/Mesa/src/tnl_dd/t_dd_dmatmp2.h:117: warning: unused variable `rmesa' -------------------------------------------------------- radeon_tex.c: In function `radeonAllocTexObj': radeon_tex.c:193: warning: void format, gl_texture_object arg (arg 4) radeon_tex.c:193: warning: void format, radeon_tex_obj arg (arg 5) radeon_tex.c: In function `radeonBindTexture': radeon_tex.c:567: warning: void format, gl_texture_object arg (arg 4) radeon_tex.c: In function `radeonDeleteTexture': radeon_tex.c:585: warning: void format, gl_texture_object arg (arg 4) ------------------------------------------------- r200_ioctl.c: In function `r200CopyBuffer': r200_ioctl.c:403: warning: void format, GLcontext arg (arg 4) ---------------------------------------------------- tdfx_context.c: In function `tdfxInitContext': tdfx_context.c:375: warning: void format, tdfx_context arg (arg 4) tdfx_context.c: In function `tdfxDestroyContext': tdfx_context.c:490: warning: void format, tdfx_context arg (arg 4) tdfx_context.c: In function `tdfxUnbindContext': tdfx_context.c:532: warning: void format, __DRIcontextPrivate arg (arg 4) tdfx_context.c: In function `tdfxMakeCurrent': tdfx_context.c:550: warning: void format, __DRIcontextPrivate arg (arg 4) tdfx_context.c: In function `tdfxInitGlide': tdfx_context.c:765: warning: ISO C forbids assignment between function pointer and `void *' ---------------------------- warning: string length `926' is greater than the length `509' ISO C89 compilers are required to support

fubar::chi, Can't believe I missed the quote button! My eyes must be going bad on me. johnnyv, Thanks for the link! Please keep us posted on how your rebuilds go. I had toyed with idea of building the entire Mandrake 9.1 for athlon, but I don't have all the source files, and only dial-up 56k. Next time I'll buy the Power pack and get the source rpm cds (I did that with 8.2, and that's what really got me started with linux in a serious way). wrc1944)