Re: [Cooker] Mandrake 8.1 keeps crashing hard on my Dell C800 laptop!
Well, I gave up and went back to the Generic|Generic Laptop Display Panel 1600x1200 as I never had problems when using this Monitor setting in Mdk 8.0. Now X hasn't crashed on me yet! Somehow, I thought selecting the Dell Laptop monitor settings would help me out, but apparently not. I still prefer the higher refresh rate that is achieved with the Dell Monitor setting, but I'll sacrifice using a lower refresh rate to not have a hard crash of my laptop (I'll just have to sacrifice the health of my eyes!). Thanks for the tip Randy, GenEric Randy Welch wrote: generic wrote: Hi, I recently installed Mandrake 8.1 on my Dell Lattitude C800 laptop, and occasionally (once out of every 5 or 6 times) when I log-out from the X-session (in either KDE or in Gnome), the screen begins to turn all white, and the computer locks up hard ... and then after about 30 seconds or so, it powers off! When I reapply power, a message eventually appears claiming that /dev/hda9 (my / partition) was not cleanly unmounted, so a check is forced. I learned that on a laptop it's a good idea to have a journaling filesystem installed. Much less pain on a hard shutdown. Also, I select Dell|Dell 1280X Laptop Display Panel as my type of monitor using XFdrake 1280x1024 16bpp resolution. During install of Mandrake 8.1, I used the suggested XFree86 4.1.0 w/ acceleration for my server. Might want try the the generic 1280x1024 laptop display settings. They seem to quite well ( or at least on my A22p with the Rage chip.) -randy
Re: [Cooker] Mandrake 8.1 keeps crashing hard on my Dell C800 laptop!
François Pons wrote: generic [EMAIL PROTECTED] writes: Please help! This is a pretty serious show-stopper for me at the moment, and I can definitely provide more detail. Can you try without DRI enabled, try XFdrake --expert and select XFree 4.0.1 François. Thanks François, I'm just using the Generic 1600x1200 Monitor settings now without any problems. GenEric
Re: Athlon optimized Mandrake [Re: [Cooker] i486 Release?]
Vadim Plessky wrote: On Saturday 04 November 2000 17:05, T Korte wrote: | On Wed, 18 Oct 2000, you wrote: | | For that matter, why not also have a 686 version ;) | | Thanks... Dan. | | I'd like to see an Athlon version, but perhaps I'll try to optimise some | things myself. | Tom I'd like to support Tom. Athlon (Duron) optimized mandrake would be very nice. AMD selling more and more processors, just for one quarter they sold aroun 3.5 million. May be, at least key packages can be optimized for Athlon and available through Cooker. -- Vadim Plessky http://kde2.newmail.ru (English) http://kde2.newmail.ru/index_rus.html (Russian) I also agree! I use an Athlon 850 at work that runs Mandrake 7.2. It would definitely be nice if programs were optimized for it, as I'm using it mostly for running logic simulations with VCS (thanks for now supporting Linux, Synopsys!) I guess I'll have to wait 'til kernel 2.4.x is stable :( GenEric
Re: [Cooker] Does someone know how to turn DGA on?
Actually, NO, do NOT uncomment the dga line. You need to have it commented out because the option is to "omit xfree86-dga". In the case of VMware, you want to use DGA, not omit it, so leave that option line commented out. VMware still considers XFree 4.0.x as unstable, even though in my opinion (and probably others out there) it's quite stable. In fact, some applications REQUIRE 4.x.x to run at this point. Come on VMware guys/gals, get your act together and support XFree 4.x.x! I've noticed some definite strangeness with VMware when it comes to correctly displaying PDF files in Adobe Acrobat Reader (the pages show up as black, which ain't too pretty). GenEric pgeorges wrote: "Eduardo M. A. M. Mendes" a écrit : Hello I need to turn the option DGA on in XF86Config so as to use vmware. Would someone know how to do it? Many thanks Eduardo Nothing to do with cooker, but : In /etc/X11/XF86Config-4, I guess uncomment the dga line (?): - Section "Module" Load "graphireusb" # This loads the DBE extension module. Load"dbe" Load"glx" # This loads the miscellaneous extensions module, and disables # initialisation of the XFree86-DGA extension within that module. SubSection "extmod" # Option "omit xfree86-dga" EndSubSection # This loads the Type1 and FreeType font modules Load"type1" Load"freetype" EndSection
Re: [Cooker] Cursor Problem in run level 3 , Mandrake 7.2
Yes, I noticed the same bug too. Hello Mandrake guys/gals, let's try to squash this bug, O.K.? Hoyt wrote: When I reach the login screen in run level 3, the cursor is positioned at the far left of the screen so that I type over the characters on the screen prior to the prompt. As such, the login name is invalid. Of course, I can press enter twice to get to a correct login prompt, but I shouldn't have to do this. Hoyt
Re: [Cooker] No switchdesk in Mandrake 7.2?
generic wrote: Hmmm I was just able to get GNOME started by creating a file: $HOME/.xinitrc that starts GNOME: #!/bin/sh exec gnome-session [ the rest of my rant snipped ] O.K., I finally figured out how to start the Window Manager of my choice via shell commands. Upon careful review of the scripts: /usr/X11R6/bin/startx, /etc/X11/xinit/xinitrc, and /etc/X11/Xsession, it appears that the command: /usr/sbin/chksession -l will give a list of the Window Managers available. In my case: $ /usr/sbin/chksession -l KDE Gnome WindowMaker Enlightenment BlackBox XFce AfterStep IceWM Sawfish Fvwm2 Fvwm1 default failsafe To start X with GNOME, I simply have to type: $ startx Gnome and it works! (The same works with KDE, WindowMaker, etc.) One word of caution, however, if you use "startx Enlightenment", it will create the file: $HOME/.xinitrc, $HOME/.Xclients, and some other file (I think $HOME/.xsession, but I'm not positive at the moment). Just be sure to delete those files/links before trying startx with any other Window Manager, or you'll just get Enlightenment starting. Of course, you can make an alias for each of the startx sessions. For me 'g' is aliased to "startx Gnome", 'k' is aliased to "startx KDE". Cheers, GenEric
Re: [Cooker] 7.2 cannot do nfs mounts
Ray wrote: When you log in just select gnome from the drop down menu What drop down menu? I don't have Mandrake 7.2 start X on bootup, if that's what you're talking about. There has to be an "easy" way to do this for those of us who use "startx" instead. GenEric Now, if I can just get a response on how to switch to GNOME instead of KDE2, I'll be golden! (There is no more 'switchdesk' utility, but hopefully, there's something similar in 7.2? Anyone?) Thanks, GenEric pgeorges wrote: generic a écrit : Oddly enough, I have absolutely no problems at all mounting a partition exported from a Solaris 2.7 box at work. I would have expected problems with the latter instead of the former. There are absolutely no log messages generated in /var/log/messages (on either box) so it's a bit difficult to diagnose! OK Mandrake NFS gurus, what's the deal? Will a Mandrake 7.2 box even be able to mount partitions exported from another Mandrake 7.2 box? I'm a bit apprehensive about upgrading my 7.0 box at work to 7.2 if I can't mount partions exported from it to another 7.2 box!! Yes. I just mounted by nfs a directory from one LM 7.2 to another 7.2 Sorry if this is obvious, but did you check perms of directories you mount ? -- Ray
Re: [Cooker] No switchdesk in Mandrake 7.2?
Hmmm I was just able to get GNOME started by creating a file: $HOME/.xinitrc that starts GNOME: #!/bin/sh exec gnome-session This works, but I was looking for a more automated way of doing this, like the "switchdesk" utility that existed in 7.0 and 7.1. I know this was a RedHat mechanism, but don't you Mandrake folks have a similar mechanism for 7.2? If not, PLEASE PUT IT BACK IN!!! It's easy enough for me to make a small shell script to copy or link to this .xinitrc file, but most newbies probably would find this a bit unsettling. I don't start X from bootup, so that is not an option for me to use the Login Manager mechanism to choose a session, unless it can be done from a console login session as a normal user (not root). It would have been nice to have provided documentation on doing this, as I and probably many out there, like the ability to choose a window manager per login session. To my knowledge and search, there is no mention of doing what I want in this regard. The only subject related to this in the help docs under KDE was related to the login manager, which is greyed out when the KDE control center is launched as a normal user. Why should I have to be root to control the session of an individual user? That's kind of George Orwellian/Bill Gatish in my opinion. Other than this issue, the Release looks quite solid. GenEric generic wrote: I just installed Mandrake 7.2 last night and am quite impressed! Good work Mandrake guys/gals! I like KDE 2, but I really prefer to use GNOME. There are no more switchdesk*.rpm packages anymore on either of the 2 installation CD's, like there were in 7.0 and 7.1. My question is, what is the "new" mechanism for switching the desktop from KDE - GNOME, and vice-versa? I would still like the ability to switch from KDE - GNOME for most of the time, but be able to switch from GNOME - KDE for other times. Please help, Thanks, GenEric
[Cooker] No switchdesk in Mandrake 7.2?
I just installed Mandrake 7.2 last night and am quite impressed! Good work Mandrake guys/gals! I like KDE 2, but I really prefer to use GNOME. There are no more switchdesk*.rpm packages anymore on either of the 2 installation CD's, like there were in 7.0 and 7.1. My question is, what is the "new" mechanism for switching the desktop from KDE - GNOME, and vice-versa? I would still like the ability to switch from KDE - GNOME for most of the time, but be able to switch from GNOME - KDE for other times. Please help, Thanks, GenEric
Re: [Cooker] 7.2 cannot do nfs mounts
Yep! I'm having the same problems trying to mount a partition exported from a Mandrake 7.0 box at work. Oddly enough, I have absolutely no problems at all mounting a partition exported from a Solaris 2.7 box at work. I would have expected problems with the latter instead of the former. There are absolutely no log messages generated in /var/log/messages (on either box) so it's a bit difficult to diagnose! OK Mandrake NFS gurus, what's the deal? Will a Mandrake 7.2 box even be able to mount partitions exported from another Mandrake 7.2 box? I'm a bit apprehensive about upgrading my 7.0 box at work to 7.2 if I can't mount partions exported from it to another 7.2 box!! GenEric Ron Stodden wrote: After installing 2 Mandrake 7.2 (custom, development) installations I am amazed to discover that nfs mounts do not work (RPC: timed out) between them or to Mandrake 7.1 partitions. portmap, nfs, mountd daemons are running. nfs_utils and nfs-utils- clients are installed. This is quite serious. What to do? -- Regards, Ron. [AU]
Re: [Cooker] 7.2 cannot do nfs mounts
This same exact setup worked yesterday, when the 7.2 box was a 7.1 box, so yes, the permissions on the exported directories should be O.K., unless I'm missing something very basic. Well, the fact that you were successful definitely gives me hope for upgrading the other box to 7.2. Now, if I can just get a response on how to switch to GNOME instead of KDE2, I'll be golden! (There is no more 'switchdesk' utility, but hopefully, there's something similar in 7.2? Anyone?) Thanks, GenEric pgeorges wrote: generic a écrit : Oddly enough, I have absolutely no problems at all mounting a partition exported from a Solaris 2.7 box at work. I would have expected problems with the latter instead of the former. There are absolutely no log messages generated in /var/log/messages (on either box) so it's a bit difficult to diagnose! OK Mandrake NFS gurus, what's the deal? Will a Mandrake 7.2 box even be able to mount partitions exported from another Mandrake 7.2 box? I'm a bit apprehensive about upgrading my 7.0 box at work to 7.2 if I can't mount partions exported from it to another 7.2 box!! Yes. I just mounted by nfs a directory from one LM 7.2 to another 7.2 Sorry if this is obvious, but did you check perms of directories you mount ?
Re: [Cooker] cooker won't boot on promise ultra66
I had a similar problem after I recompiled a kernel recently, for the first time after installing Mandrake 7.1. If you've read the Ultra66 Howto(mini-HOWTO?), there are 4 addresses that are used (err, you probably only need 2, since it looks like you're only using 1 hard-drive on the promise: hde, the other: hda is hooked to your motherboard's IDE/ATA controller). Anyway, when Mandrake 7.1 is installed, it uses the 4 addresses without adding 2 to address 2 4, which is recommended in the HOWTO (although the author says it worked for him without adding 2 to address 2 4). When I added 2 to address 2 4 in my /etc/lilo.conf reran lilo, my computer magically got past the Partition check, so for me, the original Mandrake 7.1 addresses DIDN'T work when recompiling the kernel. Example: Here's my original /etc/lilo.conf: boot=/dev/hde5 map=/boot/map install=/boot/boot.b vga=normal default=exp keytable=/boot/us.klt disk=/dev/hde bios=0x80 ### original parameters set by mandrake ... append="ide2=0xffe0,0xffac ide3=0xffa0,0xffa8" prompt timeout=50 message=/boot/message image=/boot/vmlinuz-experimental label=exp root=/dev/hde9 read-only image=/boot/vmlinuz label=linux root=/dev/hde9 read-only Here's how I got it work: boot=/dev/hde5 map=/boot/map install=/boot/boot.b vga=normal default=exp keytable=/boot/us.klt disk=/dev/hde bios=0x80 ### changed parameters to work with recompiled kernel ... append="ide2=0xffe0,0xffae ide3=0xffa0,0xffaa" prompt timeout=50 message=/boot/message image=/boot/vmlinuz-experimental label=exp root=/dev/hde9 read-only image=/boot/vmlinuz label=linux root=/dev/hde9 read-only Good luck, Gen "Matthew R. Sprague" wrote: howdy folks I just installed cooker on a udma66 hard drive controlled by a promise ultra66 pci controller card. It installs without any hitches but upon booting with lilo it gets to Partition check hda: hda1 hda2 hde: At this point the computer freezes and the keyboard won't respond. I can only hit he reset switch to reboot. I re-installed 7.1 which works without any glitches. What do I need to do here?
[Cooker] conf.modules, modules, modules.conf ... what's the deal?
When upgrading to Mdk 7.1, and recompiling my kernel, Mandrake complained about /etc/conf.modules and mentioned that it's now deprecated. fine. I copied conf.modules to modules.conf ... exact copy, ... everything works fine EXCEPT my soundblaster live! value card (emu10k1 module). I then copied modules.conf back to conf.modules and everything starts up fine, even the soundcard, except that Mandrake complains that conf.modules is deprecated. What's the deal? And why is there also a /etc/modules file, that currently only has vfat as the sole module in it? I'd be happy to use /etc/modules.conf if and only if everything works! I'm a bit confused, please help, thanks, Gen
Re: [Cooker] conf.modules, modules, modules.conf ... what's the deal?
Don Head wrote: When upgrading to Mdk 7.1, and recompiling my kernel, Mandrake complained about /etc/conf.modules and mentioned that it's now deprecated. fine. I copied conf.modules to modules.conf ... exact copy, ... everything works fine EXCEPT my soundblaster live! value card (emu10k1 module). I then copied modules.conf back to conf.modules and everything starts up fine, even the soundcard, except that Mandrake complains that conf.modules is deprecated. What's the deal? And why is there also a /etc/modules file, that currently only has vfat as the sole module in it? I'd be happy to use /etc/modules.conf if and only if everything works! Rather than copying, you should try symlinks. For situations like this, they're much more reliable, and the preferred method. When a change is made to one, it's also being made to the other, because they're the same file. This way, no matter what file is read, the contents will always be the same. Actually, I did use links. I sort of lied in my earlier post. I didn't literally copy anything. ln -s /etc/conf.modules /etc/modules.conf (or the other way around) ln -s /etc/modules.conf /etc/conf.modules Yep, I did that. Anyway, Mandrake complains when the conf.modules file (link) exists, however, the sound module is not loaded properly without it. My main question was: why are there 3 separate files in /etc related to modules? If Mandrake (newer) requires only a modules.conf file, it should be made to work for loading sound drivers too. At present, for me, (and possibly others out there) it doesn't. Gen Gen
