BobGuy©

Have you looked into rezound yet? It's on one the 3 mandrake cd's ready to be installed. That is, if this is what you are looking for. http://rezound.sourceforge.net/ http://sourceforge.net/docman/?group_id=5056

KPPP is on the 3rd cd. Don't know why its done this way, but it is.

Well you are not wrong. :) initrd worked but still no mouse, couldnt even modprobe the mouse module in there. I wouldn't think that I'd have to run mousedrake, as the mouse is detected fine in the default kernel. This sure has me stumped. Back to the menuconfig.

Thanks, I'll give them a try and see if it works. Hey if it dosent, I'll just boot to the original mandrake kernel and try again. :)

I compiled the 2.4.21-rc6 kernel for mandrake 9.1, the problem I'm having is that the mouse will stop functioning as soon as the GUI login dialog screen pops up. I have built the mouse as a module, and then re-built it into the monolithic kernel, either way I lose it at the login screen. I wanted to avoid having to use the initrd.img during the boot process, but it seems that it will be necessary. :( So my question is, what happens when I use this code. mkinitrd /boot/initrd-KERNEL-VERSION.img KERNEL-VERSION Where is the initrd.img located after I run this command? In /boot? Or do I have to move it into /boot? I presume that the command should look like this: mkinitrd /boot/initrd-2.4.21-rc6.img 2.4.21-rc6 Is that correct? BTW this the first time that I have had problems getting a mouse to work after compiling a kernel, and have never had to do the 'mkinitrd' part in the past using slackware, is this a mandrake thing? Hope someone can help with this issue, and thanks.

Forgot to mention, when you edit rc.local or any script file, TURN OFF THE WORD WRAP SETTING first! Word wrapping a script can mess you up fast after you save the edit. And you need the same permissions after you save the file, usually it is not a problem though. $ ls -l /etc/rc.d/rc.local -rwxr-xr-x 1 root root 1676 Apr 13 17:05 /etc/rc.d/rc.local the rc.local script must be executable or it will not load during the boot process.

The IO_support = line can speed things up by 30 to 50%, yours is set to a very conservative 16 bit setting. So that it will work with the oldest of hard drives. But, it's slow. # hdparm -c3 /dev/hda /dev/hda: setting 32-bit IO_support flag to 3 IO_support = 3 (32-bit w/sync) # hdparm -v /dev/hda /dev/hda: multcount = 16 (on) IO_support = 3 (32-bit w/sync) unmaskirq = 1 (on) using_dma = 1 (on) keepsettings = 0 (off) readonly = 0 (off) readahead = 8 (on) geometry = 1868/255/63, sectors = 30015216, start = 0 Try the new setting, you should notice a big difference, and you can add the command to the boot up so it will use the new setting every time. Add hdparm -c3 /dev/hda to the end of /etc/rc.d/rc.local touch /var/lock/subsys/local hdparm -c3 /dev/hda <---like so: See man hdparm for more information. Using the free command with the -m switch will print to screen the numbers in megabytes which is a lot easier to read, ie, free -m

I think that this will take time to figure out, its just a annoyance, not a konqueror critical bug. So until many more people experience this anomoly, and report it, it will not be fixed. You might try mandrake update and see what they have to offer, other than that, I have no idea. :)

Don't see why not. I did in version 9.0, looked good too. The sans in 9.1 look ok to me so I havent bothered to install ms fonts yet. Also have anti-aliasing on by default, well in KDE anyways. You might try selecting the iso8859-1 entry, and see what difference it makes. In the font tab in xmms. If your ms fonts are already installed try the tahoma or verdana. :D

I noticed the same thing. Not knowing what app is suspose to open when its clicked, or if its suppose to be automatically compressed into what type of archive, I couldn't say. Could be as simple as a broken symlink, or no mime type set, who knows? This is just one more reason to learn how to do things at the command line. And how to file a bug report. :D

The first thing that I would do is see if dma is enabled. On whatever your dvd drive is. :D This is from my CD-ROM drive, without any media inserted. # cd / # hdparm -v /dev/hdc /dev/hdc: HDIO_GET_MULTCOUNT failed: Invalid argument IO_support = 1 (32-bit) unmaskirq = 1 (on) using_dma = 1 (on) keepsettings = 0 (off) readonly = 1 (on) readahead = 8 (on) HDIO_GETGEO failed: Invalid argument Also do # hdparm -i /dev/hdc My drive is hdc, use whatever your dvd drive letter is for the /dev/hd? part. :) If dma is not on, enable it, test it by playing a dvd movie. See man hdparm for more information. You can add the missing commands in /etc/rc.d/rc.local at the bottom so it will be applied automatically when you boot up.

You can also try KDE at the prompt. Cause its aliased. $ alias alias kde='xinit /usr/bin/startkde' There are quite a few alias in ~/.bashrc, more than I posted here.

I installed 9.1 the other day and it went very well, no problems during the install, and I have the 3 downloaded CDs. It found and properly installed my soundblaster live card modules, instead of the audigy modules. Why others are having problems with this I couldn't say. What it didn't install was kppp and ppp for dial-up, which I'm stuck with for now. New users probably wouldn't even know where to look for these packages to install. Mandrake put them in the 3rd CD. Not a big deal but users stuck with only dial-up need those packages, so for them getting the 3rd CD would be worth the effort. I removed my 9.0 hard drive and installed a spare hard drive just incase the install b0rked. :D All I want now is X-Chat 1.8.11 only version 2.0 is on the CDs and from what I have heard that newer version is not ready for prime time, other than that and a lack of mandrake docs like 9.0 has, the install was very smooth and rather effortless.

Thanks ramfree17 :D You explained that very well, even I understood it. problem solved.

This is a new one for me, those files, user lib, file /etc/ptmp or /etc/gtmp? Are we talking about 2 or 3 files here? Actually I'm still having trouble understanding that error message. :? I'm using mandrake v9.0 still and I don't see those files, so I take it that these files get created but not deleted if UserDrake should get interrupted suddenly and does not get to clean up these files properly, like it would if UserDrake did not exit abruptly? I should add that 'normal' here means that the new user and groups did not get added to those three files. Thanks for the quick reply ramfree17 :D If I can figure this out, I'll have him rename them and see what happens when he tries to get back in to UserDrake.

Trying to help a friend out, when he clicks on K-> Configuration-> Other-> Userdrake in mandrake 9.1 he gets this error message after he enters his root password properly: "Can't lock user lib, file /etc/ptmp or /etc/gtmp exist" Had him check /etc/group /etc/passwd and /etc/shadow and everything looks normal. This happened after he tried to add a new user, then went to the groups tab and did a shift+click on the available groups side. Userdrake closed out immediately and he can not get back in as su root anymore, can get in su root MCC, but not userdrake in MCC. He can get in as a unpriveledged user though. Any ideas on where to look next to fix this issue? Thanks folks, he has only been using linux for about a week now and would rather fix this than reinstall 9.1

When will they finally get it together? I had hoped that 9.1 would be a polished release, but from what I'm reading, mandrake has once again managed to liberate defeat from the jaws of victory. That is, for those who manage to get V9.1 installed. :(

Thats your first problem, Linux should have empty space to install to. Go back and make that 10 gigs ntfs empty, unallocated space, then try again, mandrake should start to install now. :lol: Don't forget to setup your BIOS so that the cdrom is the first drive in the boot up sequence.

Maybe that will work on your setup, but it will not on mine. :) Filesystem Type Size Used Avail Use% Mounted on /dev/hda5 reiserfs 95M 38M 57M 40% /boot

Ran across this site, but the apps look kinda dated. http://radio.linux.org.au/?sectpat=All&ordpat=title

Thats ok, but I'd just rename them, that way I could transfer any important stuff such as bookmarks. mv .kde .kdeold mv .kderc .kdercold If you need something in there, you still have the old directroy to search through. If you delete them they are history, your choice. :)

Installing the kernel package is very easy. The problem, especially for the new to Linux user is trying to figure out exactly what the heck needs to be edited in /etc/lilo.conf I have built quite a few kernels and it took me a while to figure out exactly what needed to be done. Once I finally realized what those Mandrake URLs were trying to say it was smooth sailing. Fact is only my previous experience lead to the correct lilo solution, otherwise I would of been dead in the water so to speek. It is very easy to do. It's to bad that they for whatever reason can not explain this in plain english for the newest users. :( If anyone is still trying to figure out how to properly install a mandrake V9 kernel package update, respond here. And I'll whip up a howto on how I did this in plain english. And thanks for the help folks, I now have the 2.4.19-24mdksmp kernel properly installed, up and running. Good luck Mandrake on making it to 2004.

Yeah I hope it works too. :D I have always built my kernels from source in slackware, so this will be my first try using a pre compiled kernel. From all that I have read about this, it looks like the way to go, just fix the broken symlinks. Run lilo again, reboot and enjoy the new updated kernel goodness. And, I have a working boot floppy, just in case. :)

A checksum on what, a .iso a rpm ?

The APG card is a matrox G-200 8MB -- The PCI card is a VooDoo3 2000 16MB Both monitors are identical ViewSonic PF790 -- This combination does work well in my Slackware V8 setup. My plan is to just replace the Slackware HDD with a different one thats been wiped clean. If I run into any major problems I'll just wipe the HDD and hook up the Slackware HDD and be back in working shape.