On Tue, Aug 07, Jean-Francois Donati wrote:
I booted from a 2.4 ppc kernel that i got from the web. But i didnot have the corresponding system map nor the set of modules. Meanwhile, i dowloaded benh kernel 2.4.6 with system map AND modules. Is this one ok?? Or should i use the 2.4.7-pre6 that you have on the suse/ppc/kernel/BETA/sleep ftp area (there is no specific set of modules available though)? By the way, I'm not too sure of what I actually need to do to properly upgrade suse7.0 to the 2.4.6 kernel. I tried this on my pismo (where i had a a working suse7.0 config with xfree4.0 activated, with an upgrade to kernel 2.2.17pre20-ben3, which works nice except for firewire, sound, sleep and dvd drive). Although it booted correctly, trackpad was no longer active (/usr/bin/trackpad was giving the message "no trackpad!" at boot). I tried to install several additional rpm's (in particular devs-2001.1.2-11.ppc.rpm and modutils-2.4.2-11.ppc.rpm) but it did not improve the situation. Also, sleep was behaving strangely: the pismo went to sleep at bizarre times, even while i was typing. When waking up, strangely enough the trackpad was active although i did nothing specific in that aim (the `trackpad notap' setting seems to be lost each at each wake up though). The copy/paste mouse utility was no longer active with the 2.4.6 kernel, while it was working ok with the 2.2.17 one. Obviously, I missed some crucial steps in the upgrade. Any ideas of what it can be??
My workstation runs still 7.0 with current kernels. All you need is newer modutils and maybe ppp. Just install /mirror/SuSE/ftp.suse.com/pub/suse/ppc/kernel/BETA/sleep/kernel-benh.rpm and you have all needed kernel modules. There are reports with that random sleep bug, but I cant reproduce it here.
I usually don't use lilo to boot, but rather yaboot (using the space bar to toggle between macos and linux). It looks as if it does not work on the G4. As if the open firmware did not get the message from the os-chooser. I have to boot in the open firmware enviroment, and mention explicitely that i need to boot using yaboot. Any ideas of what is causing this?? The normal procedure works perfectly with the pismo, but not with the G4. Is this due to a newer openfirmware??
You mean it doesnt boot yaboot at all when you simply type "boot"?
I don't have the G4 here, but will bring it back tomorrow for new tests. I tried the suse_hw_info.sh script on my pismo and it worked fine, so hopefully,it will work for the G4 as well. I will send you all the information tomorrow.
Fine. Gruss Olaf -- $ man clone BUGS Main feature not yet implemented...