June 2001 - openSUSE PPC - openSUSE Mailing Lists

7.2 to PPC
by Antonin Dostal 05 Jul '01

05 Jul '01

Hi, I need know - when will be v7.2 on PPC. Thanks in replay. -- Bc. Antonin Dostal developer --------------------------------------------------------------------- SuSE CR, s.r.o. e-mail: adostal(a)suse.cz Drahobejlova 27 tel:+420 2 83095 373 190 00 Praha 9 fax:+420 2 83095 374 Ceska republika http://www.suse.cz ---------------------------------------------------------------------

4 3

DRI support in xfree4.1 on blue&white g3(r128)
by Sebastian Kobs 04 Jul '01

04 Jul '01

Hi all, I've installed the new xfree4.1 on a b/w g3, everything works fine, but when you start any app which requires openGL, it will hang imediately. When I disable DRI, everything works fine, also DRI works in 16bit mode, which I unfortunately can't use because of colormap problems(weird colors). I'm doing this on a Suse6.4 System with the BETA 2.4.6 kernel from ftp.suse.com. BTW: on a G4(identical setup) everything works as expected. My questions are: - is there a way to enable DRI in 24/32 bpp mode - or otherwise, is there a way to fix that 16bpp problem. I would be thankful for any hints or suggestions you may have. regards, Sebastian

2 2

Problem rebooting RS/6K b50 SUSE 7.1
by Alberto magnus 03 Jul '01

03 Jul '01

Good afternoon Linux experts, I have an apparently dumb problem rebooting my IBM RS/6k b50 running SUSE 7.1 . Doing this without keyboard, mouse and display (using a telnet terminal) the machine come to 0c5 (LCD display) and stops waiting for an 'enter' for ever. It seems a yaboot problem, in fact when the yaboot timeout occurs yaboot issues an error message and asks " press enter to continue".... (I connected a console to the box to be able to read the message obviously) This is a big problem if someone want to put the box into an unattended web farm.... SUSE 7.0 worked fine... Is there someone able to fix this bug or to find a workaround? Thanks in advance and best Regards Alberto Milano ITALY

2 1

2.4.2 kernel on PowerBook 3400c?
by isaac＠unstoppable.com 03 Jul '01

03 Jul '01

Hi, I'm having trouble getting 2.4.2 to work on my 3400c. I was able to get it running beautifully on my 7200 desktop, and followed the same procedure on the 3400. No luck. It only boots to the point of the first line written to the screen: "Welcome to Linux, kernel 2.4.2" or something like that. Then it freezes and I have to do a hard reboot and go back to 2.2.16. Oh, these are both running the basic SuSE 7.0 installation. Anybody know whassup? Thanks for any help. --Isaac

2 1

trouble booting 7.1 on B&W G3
by Scott Reist 03 Jul '01

03 Jul '01

On a B&W G3 -400 Mhz (mac ppc) 1.1f4 BootRom OF 3.1.1 Can yaboot boot a kernal found on a partition of a slave drive? /dev/hdb aka ultra1: boot ultra1:9,/boot/vmlinux I always get the error: Boot error on block 1 Image not found (may not be the exact wording) OpenFirmware has no trouble finding the suseboot folder on ultra1:7 Ran lilo, no problem Thanks, Scott Reist

2 1

accented characters, SuSE 7.1
by Bob Torres 03 Jul '01

03 Jul '01

Hi, First off, if anyone from SuSE is reading this list, congratulations on an excellent distro. I'm really floored by how easy it was to install and configure SuSE, especially given my experience with other distributions for PPC. With that said, I need some help now. By and large, I communicate in English, but on occasion, I need to compose emails in Spanish. What I need to figure out how to do is switch keyboard configurations on the fly, or how to send the accented characters and tildes. I tried the directions in the support database, but they didn't work for me. I also tried the International settings in KDE2, but they ended up screwing up my English keymap, and I had a hard time getting it back. For what its worth, I'm running SuSE 7.1 out of the box, with Gnome. Accented characters appear correctly in the terminal, but I just can't seem to make them myself! I'm also using an external extended USB keyboard, by Macally. Any ideas? TIA... Bob ......................................... PhD Candidate, Development Soc, Cornell U. [e] bob(a)rjtorres.net [www] www.rjtorres.net [aim] djbobyt [icq] 95880740 [advice] assume nothing

2 1

Re: LVM on PowerMac/Yaboot bug
by Andrei Verovski 03 Jul '01

03 Jul '01

>No. lilo assumes that the directory /boot is on the same partition as /. > >You need a special boot partition anyway for yaboot itself which can >contain the kernel. So I dont see a urgent reason to act. > Hi, Olaf, I would like to deploy the following partitioning scheme: HFS /macboot for yaboot within fake System Folder containing os-chooser, ext2 for /boot (Linux kernel) and ReiserFS for /root on LVM RAID 1. At this moment /boot and /root are on the same ReiserFS partition. And as I reported before, yaboot may work and may not (in my case not). Your colleague (I do not remember who, sorry), replied that he knows the reason of this yaboot's artifact and will fix it soon (Jeff Mahoney ???). I do not use LILO PPC on Mac, it is COMPLETELY useless, manual editing of yaboot.conf and os-chooser is just simpler (LILO PPC does nothing but updates these two files from lilo.conf). LILO PPC should be completely GUI to be a real value. Right now I see no reasons for a front-end for two conf files. ******************************************************** * Best Regards --- Andrei Verovski * * e-mail --- andrei.verovski(a)bigfoot.com * * * * Personal Home Page * * http://homepage.mac.com/macgurutemple/ * ********************************************************

2 1

ReiserFS patch for 2.4.6pre6
by Andrei Verovski 29 Jun '01

29 Jun '01

Hi, Olaf and Jeff, Can you please post Endian-safe ReiserFS patch for 2.4.6pre6 kernel, or sources of your version of 2.4.6pre6 with this patch applied? It would be very nice if you post PPC kernel sources the same way as Mr.mantel doing for X86. Thanks in advance. ******************************************************** * Best Regards --- Andrei Verovski * * e-mail --- andrei.verovski(a)bigfoot.com * * * * Personal Home Page * * http://homepage.mac.com/macgurutemple/ * ********************************************************

2 1

Re: Boot disket for IBM RS/6000 (fwd)
by Antonin Dostal 28 Jun '01

28 Jun '01

Wed 27. Jun 2001 15:27 : > > ---------- Forwarded message ---------- > > Date: Wed, 27 Jun 2001 13:29:26 +0200 > > From: Antonin Dostal <adostal(a)suse.cz> > > To: "Ursula [iso-8859-2] Brückner" <ubrueck(a)suse.de> > > Subject: Re: Boot disket for IBM RS/6000 > > > > 26. 7 2001 17:04 : > > > I have sent you an article how to create boot-floppy. I'm not sure if > > > this will help. That means I don't know if you have the CD1 to create > > > the floppy. > > > If not please write again. > > > I don't know, if there's a uwe.hering too at suse.de but here's a Olaf > > > Hering <olh(a)suse.de>. > > > > > > Bye from Ursel > > > > Hi, > > I create this two diskettes and cut in diskette with zimage. But whit > > this diskette is it ditto ( no booting ). At first (after switching) is > > on display writing Power PC and step by step emerge a picture with a > > keybord, a diskette etc. (clearly check system). After that is on display > > picture a diskette with writing System Management Services. Now i used > > diskette with zimage, but nothing happened. > > I can't nothing do, when system is not after this step. > > > > I have this PPC only two days ago ( for other kolege and is it my first > > PPC). This PPC is only with floppy disk drive (without disk and cdrom). > > > > Also I know not as I find exact indication (I haven't manual). > > > > This is all what I have. Would you be so kind and send me a problem > > solving? Thank you and good day. > > Hi, > > can you setup a netboot server? > You need bootpd, tfpd, tcpd from packages tcpd.rpm, nkita.rpm and > nkitserv.rpm, just look in ARCHIVES.gz on CD1. > Dont use dhcpd even if it can do bootp, the client can handle it, it > _needs_ the bootpd. > > Edit /etc/bootptab, it should look like that: > cantaloupe:hd=/:ha=006094E922FF:bf=zImage.prep:ip=10.10.1.166:sm=255.255.0. >0:gw=10.10.0.8: > > cantaloupe should be the hostname, make sure the bootp server can > resolve it via DNS or /etc/hosts > ha is the hardware address, just check the syslog the unknown requests > and edit the bootptab again and kill bootpd. > > /etc/inetd.conf should look like that: > tftp dgram udp wait root /usr/sbin/tcpd in.tftpd -s /tftpboot > bootps dgram udp wait root /usr/sbin/bootpd bootpd -d 9 -c /tftpboot > > restart inetd. > > create a directory /tftpboot and put that file in it: > http://www.penguinppc.org/~olaf/trashcan/zImage.initrd.prep > > You can change the boot order with F5 or F4 or F6 or whatever Fn key > drops you into the SMS menu. > > I dont think that machine will work at all, at least the IDE models are > not supported. > > > Gruss Olaf But I come not even to prompt. There is not even command line. It stops in the moment when on screen is picture that I have to insert floppy with "System Management Services". Bye Tony -- Bc. Antonin Dostal developer --------------------------------------------------------------------- SuSE CR, s.r.o. e-mail: adostal(a)suse.cz Drahobejlova 27 tel:+420 2 83095 373 190 00 Praha 9 fax:+420 2 83095 374 Ceska republika http://www.suse.cz ---------------------------------------------------------------------

1 0

Re: [suse-ppc] Firewall
by hysterion 28 Jun '01

28 Jun '01

Joss Winn wrote: > > On Mon, Jun 25, 2001 at 09:26:17AM +0100, Smith, Bradley wrote: > > > > Hi, > > > > What's the easiest way for me to configure a firewall (SuSE 7.1, 2001 iMac)? > > > > I *will* get around to reading up on ipchain etc. but for the moment it's > > most important that I have something protecting me from those nasty hackers! > > > > Cheers > > Brad > > You can (I think it is turned on by default anyway), use the > Personal Firewall. It uses the 2.2 ipchains. I just got cable access and set up SuSEfirewall for masquerading, and I second the recommendation. It's very easy to set up - just a few instructions in the config file, and it automatically generates appropriate ipchain rules (97 of them, in my case) at boot time. Probably the best examples you could study anyway... One caveat I found, however: it seems that I also need to connect to my isp (using dhcp) *at boot time*. Otherwise SuSEfirewall produces a different set of rules, one of which seems to get in the way when I later try to connect and ping: $ /sbin/dhcpcd -d -h CC******-A eth0 produces messages like Jun 26 22:17:12 gris dhcpcd[886]: broadcasting DHCP_DISCOVER Jun 26 22:17:12 gris kernel: Packet log: input DENY eth0 PROTO=17 10.118.32.1:67 *.*.*.*:68 L=576 S=0x00 I=43879 F=0x0000 T=255 (#37) Jun 26 22:17:12 gris dhcpcd[886]: broadcastAddr option is missing in DHCP server response. Assuming *.*.*.255 Jun 26 22:17:12 gris dhcpcd[886]: broadcasting second DHCP_DISCOVER Jun 26 22:17:12 gris kernel: Packet log: input DENY eth0 PROTO=17 10.118.32.1:67 *.*.*.*:68 L=576 S=0x00 I=43881 F=0x0000 T=255 (#37) Jun 26 22:17:12 gris dhcpcd[886]: DHCP_OFFER received from (24.2.0.9) Jun 26 22:17:12 gris dhcpcd[886]: broadcasting DHCP_REQUEST for *.*.*.* Jun 26 22:17:12 gris kernel: Packet log: input DENY eth0 PROTO=17 10.118.32.1:67 *.*.*.*:68 L=576 S=0x00 I=43883 F=0x0000 T=255 (#37) Jun 26 22:17:12 gris dhcpcd[886]: DHCP_ACK received from (24.2.0.9) $ ping www.suse.de then produces (no output and) messages like Jun 26 22:18:14 gris kernel: Packet log: input DENY eth0 PROTO=17 24.2.160.33:53 *.*.*.*:1024 L=246 S=0x00 I=12157 F=0x0000 T=52 (#37) Jun 26 22:18:19 gris kernel: Packet log: input DENY eth0 PROTO=17 24.2.160.34:53 *.*.*.*:1024 L=246 S=0x00 I=8282 F=0x0000 T=52 (#37) Jun 26 22:18:24 gris kernel: Packet log: input DENY eth0 PROTO=17 24.2.160.33:53 *.*.*.*:1024 L=246 S=0x00 I=14064 F=0x0000 T=52 (#37) Jun 26 22:18:29 gris kernel: Packet log: input DENY eth0 PROTO=17 24.2.160.34:53 *.*.*.*:1024 L=246 S=0x00 I=10180 F=0x0000 T=52 (#37) This seems to indicate that the culprit rule (#37) (which reads: -A input -s 0.0.0.0/0.0.0.0 -d 0.0.0.0/0.0.0.0 -p 17 -j DENY -l) gets in the way of dhcp and dns services -- even though I did set FW_SERVICE_DHCLIENT="yes" and FW_INCOMING_HIGHPORTS_UDP="dns". (The "10.118.32.1" seems very strange, too, but that's consistently what I get.) If I let connection happen at boot time, on the other hand, this rule disappears from the list, and everything works fine. Questions: - Is it true that the firewall prevents (dhcp-)connecting to the internet, except at boot time? If yes, I would suggest emphasizing this in the documentation (I couldn't find it). If no, I'll gladly send more details of exactly what I did - the above seems 100% reproducible. - Do later versions of the firewall behave in the same way? (I am using the stock versions from SuSE 7.0 ppc - kernel 2.2.16 and firewall 2.6.) - Any other reason I should upgrade to a later version? (The .rpm updates mentioned at http://www.suse.de/~marc/SuSE.html don't seem to exist on the ppc side.) hysterion

2 3