Hi everybody,
I have a Mac G4 Cube (Nov 2000) with an Apple LCD Display
(connected through the Apple Display Connector) with the following system
* SuSE PPC 7.0
* yaboot 0.8.SuSE
* a patched XFree86 Version 4.0.2
* 2.4.2 kernel (k_deflt-2.4.2-2.rpm from SuSE)
It all works fine, but after a cold boot the systems comes up normally but
the monitor remains off.
This problem is also common to Open Firmware; in fact cold booting in
OF (alt-apple-O-F) gives the same problem: operational OF (blind
typing OF commands produces the expected results) but blank monitor.
My solution: cold boot in OS 9.1 (which never fails to switch the
monitor on) and reboot in Linux (sometimes iterating the process two
or more times until I finally get an ON monitor in Linux).
(Notes: this is not an X problem, even the text console or the yaboot
prompt is invisible; I already have "output screen" in os-chooser.)
Any hints on how to solve the problem?
Will a firmware upgrade solve the problem? Will the updated firmware
be compatible with my system/kernel/yaboot ?
A second, related, question.
How do I switch off the monitor with a screen-saver?
(Using standard DPMS off-mode give raise to a white screen with backlight
on)
How can I control display brightness?
Thanks to all on this list and to SuSE people.
S. M.
--
Stefano Miccoli
chicco98(a)inwind.it
When I select
mac/mac-dk-latin1
in
Yast -> Installation settings -> Select Keymap
I expect a Danish keyboard-design, but it seams that Suse mix up the "z"
and "y"-key. Is this a bug or do I misunderstand something? ;-)
-j
Dear all,
just installed Suse 7.1 an my PB G3 266 and some issues have come up (sigh)
- the 2.4.2 Kernel won't really work even when I use the "No video
driver" setting in BootX, X has problems with the display, the
graphics looks dithered and hardly readable when the systems starts X
using the default setting ("No video driver" unchecked) produces 4
split up start-up screens
- under 2.2.18 /lib/modules/2.2.18/pcmcia is missing:-(
so loading during booting fails
- can I used power management (under those kernels?)
- can I used a "normal" WLAN Card (Lucent) with the airport module???
Thanks in advance
Cheers, Christian
p.s 7.1 feels much better then 6.4 which I used before!
I'm on 7.1 using kernel 2.4.2 on a TiBook. This configuration is stock and
should include the PCMCIA drivers, but I'm getting the following during the
boot sequence:
PCMCIA: using schem: SuSE
modprobe: Can't locate module i82365
modprobe: Can't locate module i82365
/lib/modules/2.4.2/kernel/drivers/pcmcia/ds.o: init_module: Operation not
permitted
/lib/modules/2.4.2/kernel/drivers/pcmcia/ds.o: insmod
/lib/modules/2.4.2/kernel/drivers/pcmcia/ds.o failed
/lib/modules/2.4.2/kernel/drivers/pcmcia/ds.o: insmod ds failed
cardmgr[216]: starting, version is 3.1.22
PCMCIA: cardmanager is running
cardmgr[216]: no pcmcia driver in /proc/devices
cardmgr[216]: exiting
a review of the contents of /proc/devices reveals that there is in fact
nothing about pcmcia. At this stage I've exhausted my limited
expertise. Can anyone offer a suggestion? thanks very much
Regards,
Shawn Gordon
President
theKompany.comwww.thekompany.com
949-713-3276
Dear all,
Spoilage warning: Maybe this has come up before. I can hardly believe this
issue has not been adressed before. If so, feel free to ignore.
I am currently using Linux on several x86 machines (server, scada systems,
workstations, etc) and just recently on an Apple Powerbook G3 Pismo. I have
had quite some experience with Linux on Intel machines, but as an old mac
fanatic, I just had to try this! And then my Powerbook caught fire...
Since I need to keep my kernel version up-to-date , I always try to keep up
to the latest release, often even the development kernels. And here comes
the sad bit: No problem on those Intel machines, but I have definitely been
wasting too much CPU time trying to compile the _official_ kernel sources
from Linus and running into issues time and again. Even the default
configure runs into errors. This bugs me. Really.
I am in awe of Paul, Ben, Cort and many others who do a fantastic job in
supplying us with suitable sources for _our_ machines. But this question
comes to mind: Why don´t their changes make it into the official tree? Lack
of communication? Dumped into the bitbucket by (I know he hates big patches)
Linus or Alan? Political issues? Whatsoever.
Anyway, how it got there seems absolutely secondary to me: What is more
important now, is how these things can be handled in the future and prevent
PPC users from having to dig the net for decent kernel sources. I want my
2.4.5-final NOW!
One more thing. Congratulations to the SuSE PPC mailinglist. The support is
tremendous, quick response from SuSE always guaranteed (Thanks: Olaf, Matze)
and the quality of the posted articles is (almost always) amazing. Rock On!
Michel Pape
Visual Systems GmbH
e-mail: pape(a)vsys.de
web: http://www.vsys.de
--
"Sundays kill more men than bombs." (Charles Bukowski)
Hi all,
OK. I give up. I've repeatedly tried downloading the KDE 2.1.1 update
for SuSE 7.1 (which came with KDE 2.01) and it breaks partway through
certain long files every time. After two days of trying every mirror
site I can find, I'm throwing in the towel.
Has somebody in this group downloaded and saved the KDE 2.1.1 update?
Could you please mail me a CD with it? I'll happily reimburse you, of
course. I'm using a 56 kbps modem and it's a slow process, even when it
works right.
This may be a "Catch-22" phenomenon, where KDE 2.01 is flawed and
won't download its replacement; there are certainly plenty of other bugs
in 2.01, which is the reason I'm anxious to upgrade.
-- Tom Dove
*** Home page at toad.net/~tdove/ ***
* Sailing, genealogy, ham radio *
I've been having to boot off the CD since I installed this, no matter what
I do. Let me run it down and maybe someone can help me.
1. Stock TiBook and normal SuSE 7.1 for PPC installation. I can boot to
linux or Mac OS as long as I boot from their CD's.
2. Booting with no CD yields the following message:
DEFAULT CATCH!, code=method <draw-rectangle> not found;
ihandle=ffbc2a80 phandle=0
3. Does Suse require both yaboot.conf and lilo.conf? The manual seems to
indicate this, but LinuxPPC only needs yaboot.conf
4. I've gotten some sample yaboot.conf files from kind folks but it
doesn't seem to help. With the Linux CD in the drive I get the 'boot'
prompt where I can specify the type and path, which works, but also seems
to ignore yaboot.conf and lilo.conf as far as I can see.
I would really like to start using Ben's updated kernel, which I've
compiled and put in place, but I'm really getting stuck on this. Any help
would be greatly appreciated. We're trying to port some of our stuff to
PPC and this is the only PPC machine we have at the moment.
Regards,
Shawn Gordon
President
theKompany.comwww.thekompany.com
949-713-3276
I am having a real struggle getting ethernet running with Suse Linux 7.1
on my Pismo. On LinuxPPC 2000 it took me five minutes.
Question: What type of ethernet-card should I choose in
Yast -> System Adm. -> Integrate hardware into system -> Configure network
device?
- Apple onboard Ethernet mace
- Apple onboard Ethernet bmac
- Apple onboard Ethernet gmac
?
Thank!
-j
The MacOS has a facility under the Energy Saver CP which allows the
machine to restart automatically after a power failure. I believe
this sets a parameter in the machines PRAM. Is there a way to
configure this setting in SuSE PPC?
Thanks,
Amar
Hi,
I've got SuSE PPC 2.4.2 kernel sources, SuSE ReiserFS patch, applied
patch and succesfully compiled kernel with most drivers built-in rather
separate modules. Now I would like to reinstall SuSE PPC on ReiserFS
partition.
I would like to start installation from suseboot folder located at
/macboot HFS partition, not from CD (because boot kernel on CD does not
have ReiserFS support).
The only question is how to create ReiserFS partition with Yast2, since
there is statement in manual that Yast2 do not supports ReiserFS on PPC.
Or may be it just checks kernel for presence of ReiserFS code, and will
work once they will be found?
Can I use my vmlinux kernel instead of original vmlinux located at
suseboot (I do not know, may be there is something special in suseboot
vmlinux)? Do I need to regenerate ramdisk.image.gz?
Thanks
Andrei Verovski
