[Cooker] Beta 2 Installation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Installed Beta 2 on a multi-boot system. Installed /boot partition on hda6, and / partition on hda11. When formatting the partitions, a message came up that it was formatting hda1 (although it really didn't). Made my heart leap out of my chest, still trying to find it. RSS -BEGIN PGP SIGNATURE- Version: PGP 7.0.1 iQA/AwUBOr+xZcu45Q91a0jGEQJXegCg0B1/tScd1zj8EwHDEkYj6qZ5YuQAnRm4 5J/WlMi35MS/RaVUaorakzi5 =202y -END PGP SIGNATURE-
RE: [Cooker] Problems with 3Com 3c905C-TX
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Friday, January 12, 2001 1:12 AM To: [EMAIL PROTECTED] Subject: Re: [Cooker] Problems with 3Com 3c905C-TX Curious... I also have a 3com905C, and i use the 3c59x driver on a 2.2.17 kernel without problem. I also tested it on a 2.4.0pre-release. It is the one from www.scyld.com, written by Donald Becker, that is considered glabally better as 3c90x driver, written by 3COM themselves. Both are in kernel 2.2 sources, so you should be able to compile them without problems. See this post on mandrake archive list, and this page on scyld.com for details: http://www.mail-archive.com/cooker%40linux-mandrake.com/msg22893.html http://www.scyld.com/network/vortex.html I also had problems with DHCP, but as our DHCP servers are are very ill-configured, i assume those are not driver's issues. -- Guillaume Rousse Murphy's law : If anything can go wrong, it will. O'Tool's commentary : Murphy was an optimist. I tried to compile the driver from the source provided by Mandrake, by 3Com, and by www.scyld.com. None of the 3c59x would work. The only driver that I could get to work was the 3c90x, but I couldn't get it to work automatically on bootup. I had to manually load the driver, and manually "ifup eth0." I tried everything I could think of. I tried re-installing several times, with PnP turned off, and turned on. The 3c59x driver just plain wouldn't work under *any* Linux distro I tried. Only the 3c90x would work. I eventually solved the problem by getting an Intel EtherExpress Pro 100 instead. It works beautifully. However, when I first installed it, I couldn't get it to work either. It wouldn't work under Windows 9x/Windows 2000/ or Linux. Finally, I tried unplugging the cable modem and plugging it back in. Now it works. Evidently the cable modem had something stored in NVRAM which got cleared out when I unplugged it. It's possible that that might have been the problem with the 3com 3c59x driver, but since I've removed it, I haven't been able to test out that theory. Raymond S. Swaim
[Cooker] Problems with 3Com 3c905C-TX
I just bought a new PC: a Dell Dimension 4100 which came with a 3com 3C905C-TX Fast Etherlink). I can't get the 3com NIC to initialize and retrieve my IP address via DHCP on bootup. During bootup, when it tries to initialize the NIC, it hangs, and eventually times out with a error that DHCP retrieval failed. The NIC is connected to a cable modem and I use the Austin Roadrunner service. HardDrake identifies my NIC as a 3c905 NIC (which is correct), but it installs the 3c59x module instead of the 3c90x module. From what I've gathered from the newsgroups, it appears that the 3c59x module works for *some* 3c905 NICs, but not all of them. Perhaps it works with earlier kernel revisions, or with earlier 3c905 NICs. All I know is that it definitely does not work with mine. If I unload the 3c59x module, and install the 3c90x module, I can get the NIC to work after two ifup attempts. In other words, I type the following: rmmod 3c59x modprobe 3c90x and then type: ifup eth0 The first time I use the ifup command, it hangs when it tries to retrieve my IP address. I Cntl-Z to stop it, then try again, and it works on the 2nd attempt. I then replaced the line in modules.conf that read: "alias eth0 3c59x" with "alias eth0 3c90x." The module loads when I boot up, but I still hang on bootup when the NIC tries to retrieve my IP address. The only way I've managed to get on the net with the card is to manually load the module and manully "ifup eth0" each time I boot up, which is a pain. I have a multi-boot setup in which I was running Linux-Mandrake on one partition and use another partition as a test-bed. I decided to see if any of the other distributions had the same results, so I decided to reformat my test-bed partition and try the other distros . So far, Suse Linux 6.4 and 7.0 is the only ones I've had success with. Suse loads the 3c90x module instead of the 3c59x, and works on bootup without any problems. I've also tried Storm and Debian, but neither one of them worked because they both loaded the 3c59x module and don't even include a 3c90x module at all. I've tried the drivers from http://www.scyld.com/ but have had no success in compiling them, and the drivers from supplied from 3Com were developed for kernel rev 2.2.12 and earlier. Anyway, I think this might be something you'll want to address before the next release of Linux-Mandrake. These 3Com NICs are very common. Raymond S. Swaim
Re: [Cooker] Can't Install Cooker via FTP
On Sunday 17 December 2000 13:32, you wrote: Guillaume Cottenceau [EMAIL PROTECTED] writes: This install images fix that problem: ftp://ftp.mandrakesoft.com/pub/gc/kernel-boot/ And by the way the problem is listed on our website: http://www.linux-mandrake.com/en/72last.php3 Thanks for the help. It's true that the problem is listed at the address you give, but the link is a bad link. It downloads a file that is only 1200 kb in size. I assume it's really just an html file which gets downloaded as "network.img" but I removed it before checking it more closely. I then tried the network.img file contained in the cooker /image directory, thinking it may have been updated with the new module, but evidently, it hasn't. The first link you gave (ftp.mandrakesoft.com/pub/gc/kernel-boot) was a good link and it has solved the problem.
[Cooker] What's the best way to install Cooker?
Is it better to update from LM 7.2 to cooker, or better to do a clean install? The reason why I ask is that when I tried doing a clean install of cooker a couple weeks ago, I found I had not menu items in KDE, Gnome, or any other window manager. Adding all these items manually by hand wasn't very appealing to me, so I scrapped it and decided to wait until Cooker "cooked" a little more. Has anyone else had this problem? Anyone done a clean install recently? RSwaim
[Cooker] Codeweavers Wine Preview
Wow!! This thing is slicker than my granddaddy's hair! ;-) Any chance of it making it into Cooker? RSwaim
Re: [Cooker] KDE 2 Theme manager
On Wednesday 13 December 2000 09:16, you wrote: Yes. Right now it only handles icons, wallpapers, color schemes, and sounds. I am preparing the KWin code for handling the KDE1.x KWM themes, and as soon as that's done Waldo Bastian will add that to the new theme manager. It's pretty close - I'm running Photon now ;-) Lol! I was just about to send a reply: "Please make sure it works with Photon!" :-D RSwaim
Re: [Cooker] helix
On Thursday 14 December 2000 00:42, you wrote: Well... So far. I just decided to look into that by starting esd with a strace. My problem was that esd uses tcp (by default?!?!?), that is is wrapped by tcpd, that my hosts.deny says ALL: ALL and that my hosts.allow says nothing for esd... I added ALL: localhost and I now get the glorious sound! So. What should hosts.allow actually say for esd? I don't have anything for ESD in hosts.allow. Hmmm Since you say it was working immediately after the install and then stopped, you may be right that installing the Helix updates might solve the problem. Or, you might try installing only the updated esd packages. RSwaim
Re: [Cooker] KDE 2 Theme manager
On Thursday 14 December 2000 03:08, you wrote: http://www.mosfet.org/photon-kde2.png Ohh! You're teasing me and it hurts!! ;-) RSwaim
Re: [Cooker] helix
On Thursday 14 December 2000 15:49, you wrote: snip (1) Save a copy of /etc/X11/wmsession.d/02gnome (2) Save a copy of /usr/bin/startgnome Could you send me a copy of your 02gnome and startgnome files? I found out too late :-( You can use your editor to create them. The contents of my 02gnome file are: NAME=Gnome ICON=gnome-logo-icon-transparent.xpm DESC=Gnome Environment EXEC=/usr/bin/startgnome SCRIPT: exec /usr/bin/startgnome And the contents of startgnome are: export HELP_BROWSER=gnome-help-browser /usr/X11R6/bin/xsetroot -cursor_name left_ptr -solid "#99" /usr/bin/createbackground.sh $HOME/.gnome png exec /usr/bin/gnome-session Place 02gnome in /etc/X11/wmsession.d, and place startgnome in /usr/bin. RSwaim
[Cooker] Live Update - Request
I don't know how difficult this would be to implement, but thought I'd throw the idea out there just in case: Would it be possible to modify the Live Update feature to allow one to skip some steps? In other words, Live Update could be a very helpful feature if all someone wanted to do was switch from XFree86 3.3.6 to 4.0.1. Or, if someone simply wanted to change mouse drivers, etc. I know these things are simple enough as it is, but I don't think a newbie would know how to do it right away, and to be able to just call up Live Update and go directly to the X installation and select the desired X version couldn't be simpler. RSwaim
Re: [Cooker] Live Update - Request
On Wednesday 13 December 2000 13:07, you wrote: On Wed, Dec 13, 2000 at 11:57:38AM -0600, Raymond S. Swaim wrote: In other words, Live Update could be a very helpful feature if all someone wanted to do was switch from XFree86 3.3.6 to 4.0.1. Or, if someone simply wanted to change mouse drivers, etc. Umm on XFree86 run DrakConf and choose Graphics Configuration (upper left corner). It'll prompt you if you want 3.3.6 or 4.0.1 and if you decide to switch will even prompt for the CD to install the other one. Actually, DrakConf doesn't give me that option. It asks me for the resolution I want, but never presents me with an option to switch to 3.3.6 or 4.0.1. In any case, I picked the XFree86 as my example mainly because it's at the very end of the steps in Live Update. If one wanted to use it to switch from 3.3.6 to 4.0.1 or visa versa, they would first have to go through *all* of the prior steps, including package selection. It would be nice to be able to skip directly to a desired step. RSwaim
Re: [Cooker] Live Update - Request
On Wednesday 13 December 2000 13:15, you wrote: Actually, DrakConf doesn't give me that option. It asks me for the resolution I want, but never presents me with an option to switch to 3.3.6 or 4.0.1. I should re-phrase that It's been a while since I used and forgot which options were available. The "Graphics Configuration" option comes up with a window asking me to select my monitor. The "Screen Resolution" option allows me to change resolutions. But neither of these utilities allow me to switch to another X server. RSwaim
Re: [Cooker] Live Update - Request
On Wednesday 13 December 2000 14:38, you wrote: launch XFdrake --expert, but at your own risk Sure, I could do that, but that isn't really what I'd call "user-friendly." I'm not asking for support here, I can change X servers just fine. It's just that Linux-Mandrake is a distribution that prides itself on being user-friendly. It's a distribution that I recommend to people who have never used or seen Linux before. I'm thinking from a tech-support point-of-view, and I'm pretty sure that a novice wouldn't know how to change X servers. I was just making a recommendation of something that I think would make it even *more* user-friendly, and one that I don't think would be difficult to implement (although I could certainly be wrong). It would also be nice to be able to redirect Live Update to another installation source. If I were to download the next release, it would be nice to be able to call up Live Update and point it to my download directory. Anyway, it's just a suggestion, and one that i think would make "Live Update" more useful. RSwaim
Re: [Cooker] helix
On Tuesday 12 December 2000 15:51, you wrote: I too tried it. H ! Now Sawfish produces windows without borders and title bars !!! Rats ! Ack! Hit the wrong button, sorry for that other reply. :-b Before installing the Helix Gnome packages, save a copy of your /etc/X11/wmsession.d/02gnome and /usr/bin/startgnome files. When the Helix installer finishes its installation, these files will be removed. Because of this, the Gnome option will not be present in the gdm or kdm login screens (doesn't matter which one you choose, it'll be removed no matter which one you choose). After completion, the Helix installer will restart your X server, so the next step is to login to KDE (since Gnome won't be an option) and copy the two files you saved back to their original directories. Secondly, rename the .gnome, .gnome-desktop, .gnome-private, and .mc directories in your /root and /home directories. When you log back in to Gnome, these directories will be recreated. If you don't recreate these directories, it'll be VERY unstable. So, to sum up and repeat the steps in order: (1) Save a copy of /etc/X11/wmsession.d/02gnome (2) Save a copy of /usr/bin/startgnome (3) Run Helix installer (4) When Helix installer finishes, it'll restart your X Server. Gnome will not be an option, so login to KDE. (5) Copy the 02gnome and startgnome files back to their original directories (6) Rename .gnome, .gnome-desktop, .gnome-private, and .mc directories in your /root directory and all user directories. (e.g. I renamed mine to .gnome2, .gnome-desktop2, etc.). The directories will be recreated when you login to Gnome. (7) Reboot (8) You should now be able to login to Gnome w/o (many) problems. The Helix Gnome updates work pretty well on Mandrake 7.2 after following the above steps, but I still experience some very minor problems every now and then that I can't quite put my finger on (and I'm not even certain if the problems are caused by Helix Gnome, or something else). I think that if I had it all to do over again, I'd probably just skip the Helix updates. Most of the gnome packages in LM 7.2 are still current and I don't see any major differences. Your system might be more stable if you just leave it the way it is. RSwaim
Re: [Cooker] helix
On Tuesday 12 December 2000 15:51, you wrote: I too tried it. H ! Now Sawfish produces windows without borders and title bars !!! Rats !
Re: [Cooker] helix
On Wednesday 13 December 2000 20:38, you wrote: Do you get sound? That's the main reason why I consider using helix. Since mandrake 7.2, I no longer have sound with gnome (except for the very first time I login after the install). Even root does not get sound with gnome, so it's not a permission problem. Yes, I get sound, but then I was getting sound before installing Helix Gnome anyway (if I remember correctly). However, my sound card does not show up in HardDrake, I had to use sndconfig to get it working. Is it only Gnome that doesn't give you sound? In other words, do you get sound in KDE? Although I do get sound, if I use any of the Gnome desktop sound effects, they tend to stutter quite a bit. Instead of getting one bell ring, I'll get about 5 or 6. I suspect the problem lies with ESD not liking my OPL3-SA card. Btw, this stuttering problem has plagued me in every Linux distro that I've ever run, including Mandrake, Red Hat, SuSE, and Caldera. RSwaim