March 2002 - openSUSE PPC - openSUSE Mailing Lists

FW: [suse-ppc] Umax Pulsar
by ulrich-harings＠t-online.de 08 Mar '02

08 Mar '02

---------- > Von: Ulrich Harings@t-online <520041532164-0001(a)t-online.de> > Datum: Fri, 08 Mar 2002 14:41:09 +0100 > An: Christian Schmidt <schmidtc(a)chemie.uni-hamburg.de> > Betreff: Re: [suse-ppc] Umax Pulsar > > am 08.03.2002 13:03 Uhr schrieb Christian Schmidt unter > schmidtc(a)chemie.uni-hamburg.de: > >> On Fri, Mar 08, 2002 at 10:44:03AM +0100, Ulrich Harings@t-online wrote: >> >>> I tried to install suse linux on umax pulsar 250 dp. >>> Who has any experiences with linux on this maschine? >> >> My Pulsar is a smaller one (singe processor @ 200 MHz). >> >>> First problem: the machine dosn't start from linux CD. >> >> You should try using BootX to boot the installation system from the CD. >> The Umax Pulsar is an Old World Mac. IMHO this should be mentioned in the >> documentation you received with the CDs... > Thats what I do. BootX switch to CD. Then the following output appears on the > screen and nothing else happens: > > Welcome to Linux, kernel 2.4.12 > > linked at : 0xc0000000 > frame buffer at : 0x88008000 (phys), 0xd0008000 (log > klimit : 0xc03d8000 > MSR : 0x00000072 > HID0 : 0x8000c084 > > pmac_init(): exit > id mach(): done > MMU: enter > MMU: hw init > hash: enter > hash: find piece > hash: patch > hash: done > MMU: mapin > MMU: setio > MMU: exit > xmon uses screen and keyboard > setup_arch: enter > setup_arch: bootmem > arch: exit > > >> >> Which version of SuSE PPC are you trying to install? > Version 7.3 >> >> Good luck, > thanks >> Christian > Ulrich

1 0

Umax Pulsar
by ulrich-harings＠t-online.de 08 Mar '02

08 Mar '02

Hi, I tried to install suse linux on umax pulsar 250 dp. Who has any experiences with linux on this maschine? First problem: the maschine dosn't start from linux CD. thanks for help ulrich harings

1 0

Re: [suse-ppc] ieee1394 / firewire cdrw module problems on blue and white g3
by Kimball Hodge 07 Mar '02

07 Mar '02

Hi, So I executed these commands as root: linux # mknod -m 666 /dev/raw1394 c 171 0 linux # insmod ieee1394 Using /lib/modules/2.4.16/kernel/drivers/ieee1394/ieee1394.o linux # insmod pcilynx Using /lib/modules/2.4.16/kernel/drivers/ieee1394/pcilynx.o linux # insmod raw1394 Using /lib/modules/2.4.16/kernel/drivers/ieee1394/raw1394.o linux # insmod sbp2 Using /lib/modules/2.4.16/kernel/drivers/ieee1394/sbp2.o All looks fine. I can see the drive on /dev/raw1394 using gscanbus. However, when I try linux # mount -t iso9660 /dev/sr0 /mnt mount: /dev/sr0 is not a valid block device When I do dmesg | less I find the error message: ieee1394: sbp2: Driver forced to serialize I/O (serialize_io = 1) ieee1394: sbp2: Error logging into SBP-2 device - login timed-out ieee1394: sbp2: sbp2_login_device failed Stumped again. Thanks for your help, Michael! -Kim >From: Michael Engel <mengel(a)biochem.mpg.de> >To: "Kimball Hodge" <gojoryu(a)hotmail.com> >CC: suse-ppc(a)suse.com >Subject: Re: [suse-ppc] ieee1394 / firewire cdrw module problems on blue >and white g3 >Date: Thu, 7 Mar 2002 12:02:15 +0100 > >On Thursday, 7. March 2002 09:25, Kimball Hodge wrote: > > > Hi, > > > > I'm trying to set up a firewire cdrw on my Blue and White G3. I have > > installed the latest and greatest kernel from the SuSE ftp site > > (2.4.16-55), and have followed the directions at > > http://sdb.suse.de/en/sdb/html/olh_ppc_sleep.html. > > > > I follow the following steps as root: > > > > linux# modprobe ieee1394 (works) > > linux# modprobe ohci1394 > >For the internal firewire port in b&w g3 you have to use pcilynx >instead of ohci1394. >Please tell me if you succeed. I'm interessted in any device, which >will work with the internal firewire port in b&w g3. I tried to connect >an external HD to this port but had yet no success. > >Grüßli, Micha _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com

1 0

PPP: Authentication failure
by Jutta Buschbom 07 Mar '02

07 Mar '02

Hallo! I configured my modem and PPP through YaST and wvdial.conf in Suse 7.3 on my Powerbook Firewire. What I haven't been able to solve so far is an authentication dialog failure between the modem and the provider (my university). University modem pool support could only confirm my settings but otherwise does not support Linux. Thus, maybe somebody here would have an idea what I am still missing to get the modem running. I tried to take over the settings from my MacOS partition for which the modem is connecting fine. Those are: Remote Access: registered user, username, password, phone number Options: redial off, allow error correction and compression in modem, use TCP header compression Modem: 56k, sound on, dialing tone, do not ignore dialing tone TCP/IP: Connect via PPP, Configure: using PPP server (there is a nameserver IP, but university support said that that is bogus) In linux the provider part in wvdial.conf looks like this: [Dialer UofC] Ask Password = 0 Auto DNS = 1 Auto Reconnect = 0 DNS1 = DNS2 = Demand = no Idle Seconds = 180 Inherits = Dialer modem0 Password = [password] Phone = [number] Provider = UofCModem Username =[username] YaST2 Record = provider I am connecting using Kinternet and the log gives me the following messages: ... Entering PPP mode Async interface address is unnumbered (Loop back 1) Your IP address [number]. MTU is 1500 bytes Header compression will match your system. -> Looks like a welcome message -> Starting pppd at [date] -> pid of pppd: 7356 -> PPP was killed (signal 11) -> Disconnecting We are disconnected. -> PPP daemon has died. Peer didn't authenticate itself (exit code 11). Any ideas? Thanks! Jutta

3 5

ieee1394 / firewire cdrw module problems on blue and white g3
by Kimball Hodge 07 Mar '02

07 Mar '02

Hi, I'm trying to set up a firewire cdrw on my Blue and White G3. I have installed the latest and greatest kernel from the SuSE ftp site (2.4.16-55), and have followed the directions at http://sdb.suse.de/en/sdb/html/olh_ppc_sleep.html. I follow the following steps as root: linux# modprobe ieee1394 (works) linux# modprobe ohci1394 /lib/modules/2.4.16/kernel/drivers/ieee1394/ohci1394.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.16/kernel/drivers/ieee1394/ohci1394.o: insmod /lib/modules/2.4.16/kernel/drivers/ieee1394/ohci1394.o failed /lib/modules/2.4.16/kernel/drivers/ieee1394/ohci1394.o: insmod ohci1394 failed /var/log/messages has: Mar 7 01:22:16 linux kernel: ohci1394: PCI module init failed I'm at a loss to know what I am doing wrong. Any suggestions? Thanks, Kim _________________________________________________________________ Join the worlds largest e-mail service with MSN Hotmail. http://www.hotmail.com

2 1

ibook help
by Porter Kussak 07 Mar '02

07 Mar '02

I would like to ask an old question I have one Book G3 300... everything is functioning perfectly in suse 7.3 pcc? will my sound, modem, usb, ethernet and X work fine...? thank's all :) coffeman

5 5

Need help with XFree86 4.2 and Voodoo5
by John Grantham 06 Mar '02

06 Mar '02

Hi all, I have a Mac with the following configuration: PowerMac 9500 with G3/500 processor 144 MB RAM Acard UDMA/66 6260M card Voodoo5 video card with 64 MB RAM in PCI slot 0:13:0 (plugged into this is a generic 17" VGA monitor, max. 1024x768) Formac ProFormance III graphic card in 0:14:0 (not actually in use -- for some reason the Mac refuses to boot when the card is not installed, even after a CUDA hardware reset) Farallon 100BaseT Ethernet card I am running SuSE 7.1/PPC with the updated 4.2.0 XFree86 binaries from SuSE's supplementary area and the stock 2.4.2 kernel. (I tried the precompiled 2.4.16 kernel from SuSE, but it failed to work with my Acard UDMA card, which is running the drive with Linux on it.) SaX2 fails to recognize the card at all -- in the error log it just writes "fbdev" instead of "tdfx" for the driver. When I run SaX2, I briefly get the grey screen with the "X" cursor, then the screen goes blank, and SaX says it can't do anything. I have to force it to create an XF86Config file, either with sax2 -af or sax2-m 0=tdfx, neither of which work. If I use fbdev, I get a badly distorted X screen and KDE starts up -- the screen is compressed into the left third of the monitor, with the colors totally off (mostly white). If I use tdfx, I get this error message (these are excerpts taken from the log): (--) PCI:*(0:13:0) 3dfx Interactive Voodoo5 rev 1, Mem @ 0xb0000000/26, 0xa0000000/ 27, I/O @ 0x10000/8, BIOS @ 0x80810000/16 (--) PCI: (0:14:0) 3Dlabs GLINT Permedia 3 rev 1, Mem @ 0x80880000/17, 0x84000000/2 6, 0x90000000/26, I/O @ 0x0800/4, BIOS @ 0x80820000/16 (II) Addressable bus resource ranges are [0] -1 0x00000000 - 0xffffffff (0x0) MX[B] [1] -1 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) OS-reported resource ranges: [0] -1 0xffffffff - 0xffffffff (0x1) MX[B] [1] -1 0x00000000 - 0x00000000 (0x1) MX[B] [2] -1 0x0000ffff - 0x0000ffff (0x1) IX[B] [3] -1 0x00000000 - 0x00000000 (0x1) IX[B] (II) Active PCI resource ranges: [0] -1 0xf3000000 - 0xf301ffff (0x20000) MX[B] [1] -1 0x80800000 - 0x808000ff (0x100) MX[B] [2] -1 0x80820000 - 0x8082ffff (0x10000) MX[B](B) [3] -1 0x90000000 - 0x93ffffff (0x4000000) MX[B](B) [4] -1 0x84000000 - 0x87ffffff (0x4000000) MX[B](B) [5] -1 0x80880000 - 0x8089ffff (0x20000) MX[B](B) [6] -1 0x80810000 - 0x8081ffff (0x10000) MX[B](B) [7] -1 0xa0000000 - 0xa7ffffff (0x8000000) MX[B](B) [8] -1 0xb0000000 - 0xb3ffffff (0x4000000) MX[B](B) [9] -1 0x00000400 - 0x0000040f (0x10) IX[B] [10] -1 0x00000410 - 0x00000413 (0x4) IX[B] [11] -1 0x00000420 - 0x00000427 (0x8) IX[B] [12] -1 0x00000430 - 0x00000433 (0x4) IX[B] [13] -1 0x00000440 - 0x00000447 (0x8) IX[B] [14] -1 0x00000400 - 0x000004ff (0x100) IX[B] [15] -1 0x00000800 - 0x0000080f (0x10) IX[B](B) [16] -1 0x00010000 - 0x000100ff (0x100) IX[B](B) (II) Active PCI resource ranges after removing overlaps: [0] -1 0xf3000000 - 0xf301ffff (0x20000) MX[B] [1] -1 0x80800000 - 0x808000ff (0x100) MX[B] [2] -1 0x80820000 - 0x8082ffff (0x10000) MX[B](B) [2] -1 0x80820000 - 0x8082ffff (0x10000) MX[B](B) [3] -1 0x90000000 - 0x93ffffff (0x4000000) MX[B](B) [4] -1 0x84000000 - 0x87ffffff (0x4000000) MX[B](B) [5] -1 0x80880000 - 0x8089ffff (0x20000) MX[B](B) [6] -1 0x80810000 - 0x8081ffff (0x10000) MX[B](B) [7] -1 0xa0000000 - 0xa7ffffff (0x8000000) MX[B](B) [8] -1 0xb0000000 - 0xb3ffffff (0x4000000) MX[B](B) [9] -1 0x00000400 - 0x0000040f (0x10) IX[B] [10] -1 0x00000410 - 0x00000413 (0x4) IX[B] [11] -1 0x00000420 - 0x00000427 (0x8) IX[B] [12] -1 0x00000430 - 0x00000433 (0x4) IX[B] [13] -1 0x00000440 - 0x00000447 (0x8) IX[B] [14] -1 0x00000400 - 0x000004ff (0x100) IX[B] [15] -1 0x00000800 - 0x0000080f (0x10) IX[B](B) [16] -1 0x00010000 - 0x000100ff (0x100) IX[B](B) (II) OS-reported resource ranges after removing overlaps with PCI: [0] -1 0xffffffff - 0xffffffff (0x1) MX[B] [1] -1 0x00000000 - 0x00000000 (0x1) MX[B] [2] -1 0x0000ffff - 0x0000ffff (0x1) IX[B] [3] -1 0x00000000 - 0x00000000 (0x1) IX[B] --snip-- (WW) ****INVALID IO ALLOCATION**** b: 0x10000 e: 0x100ff correcting (II) TDFX(0): TDFXFindChips: found 1 chip(s) (**) TDFX(0): Depth 8, (--) framebuffer bpp 8 (==) TDFX(0): Default visual is PseudoColor (--) TDFX(0): Chipset: "3dfx Voodoo5" (--) TDFX(0): Linear framebuffer at 0xA0000000 (--) TDFX(0): MMIO registers at addr 0xB0000000 (EE) TDFX(0): No valid PIO address in PCI config space (II) UnloadModule: "tdfx" (II) UnloadModule: "vgahw" As for the kernel module for the console, nothing doing there either. (Reminder: I'm using the 2.4.2 stock kernel from SuSE for 7.1/PPC.) If I try to use the driver with "video=tdfx:1024x768-8@75,noaccel" in BootX, I briefly see the dancing penguin and the bootup, then the screen goes blank and nothing else happens. (I thought maybe the system was still booting, but as far as I can tell that's not happening.) I'm at the end of my rope here. Anyone have any ideas what I can do? Cheers, John -- John Grantham | Dipl.-Designer (FH) | Homepage http://www.grantham.de/ | LinuxMac http://www.macnews.de/_linuxmac/ Web Designer | AGD Member http://www.agd.de/

1 0

Re: [suse-ppc] Konqueror 2.2.2 segfaults/X4.2 3D not working
by Olaf Hering 05 Mar '02

05 Mar '02

On Tue, Mar 05, Joss Winn wrote: > Olaf, here is the output to gdb konqueror. KDE is completely dead right > now. Everything KDE related segfaults. Can you send me the `rpm -qai` output? I just did a fresh installation and updated kde and it does not crash for me. > With regards to my problem with DRi and X, the relevant log file section > is below, too. DRI wants a newer r128.o in 4.2, you could recompile the km_drm in the suse73/4.2.0/other directory. I see no easy way to provide both versions for 4.1 and 4.2 in the same kernel package. did you run SuSEconfig anf ldconfig after the update? Gruss Olaf -- $ man clone BUGS Main feature not yet implemented...

1 0

Use a projector with SuSEPPC/PowerbookG3
by abarthel 05 Mar '02

05 Mar '02

Hello, Did anyone succeed in using a projector with SuSE 7.3PPC Video driver: bmac With one projector I have a all yellow screen on X11/Kde There is maybe a way to change the color settings With another projector; nothing Problem only with X11, not with console mode. Somebody told me once to use a framebuffer but I am not used with that and I am in a hurry. Thanks Alain Barthélemy

1 0

suse7.3ppc on G4/733+nvidia
by Jean-Francois Donati 05 Mar '02

05 Mar '02

Hi everybody, I recently managed to implement suse7.3ppc on a G4/733 tower with a nvidia GeFroce 2 MX graphics card and a 17" flat panel (apple studio display), using the kernel recently posted on, eg www.penguinppc.org, by Ani Joshi. Trying with the original 2.4.12 or 2.4.16 kernels did not work at all, the kernel didnot recognise the flat panel properly (i was getting something on the screen, but the synchronisation parameters were obviously wrong, as all the boot information was squeezed in the upper part of the screen and spread out throughout its full width). I could not test the nv driver though beacuse it requires xf86 4.2 to work and it looks as if the xf86 4.2 rpms that i downloaded from suse web site cannot be installed properly (missing a few libraries, libXtrap.so.6, libXrandr.so.1, libXv.so.1 in particular). However, the colors are fine, and the whole desktop environment is much nicer than it was. Still i have a number of problems. The kernel that AniJoshi provided is 2.4.18-rc2, and i don't have the modules for it. It means that a number of things don't work, among which the cdrom (hdc: no driver present), the modem (cannot find the modem port), and probably many other features. it also tells that hfs is not supported under this kernel. Here are the questions that i have: * would it be possible to get the modules that i would need for 2.4.18-rc2, or alternatively to get a new kernel rpm with modules that incorporates AniJoshi's changes to make it recognise the flat panel and nvidia graphics card. * would it be possible to know where to get the missing libraries so that i can install xf86 4.2, and test the nv driver for graphics acceleration?? thanks for any help. cheers, jeanfrancois donati -------------------- Jean-Francois Donati Observatoire Midi-Pyrenees, 14 avenue Edouard Belin, F-31400 Toulouse, France E-mail: jean-francois.donati(a)obs-mip.fr, Tel: (33) 561332917, Fax: (33) 561332840, URL: http://webast.ast.obs-mip.fr/people/donati

1 0

Konqueror 2.2.2 segfaults/X4.2 3D not working
by Joss Winn 04 Mar '02

04 Mar '02

Hello, I just upgraded to KDE 2.2.2 with SUSE rpms. The install went fine, konqueror worked fine until reboot and now it segfaults. I have also upgraded to X 4.2. It seemed to go ok, but now DRI is not working. Otherwise OK. Are there specific 4.2 upgrade notes available? I followed the 4.1 SDB notes. Thanks Joss --

2 1

more KDE segfault info
by Joss Winn 04 Mar '02

04 Mar '02

Well, all KDE programs are not working. Kcontrol gives some terminal output. I hope this makes sense to someone! 20:53 joss:~ $ kcontrol DCOPServer up and running. kio (KDirWatch): KDirWatch: Can't use FAM kio (KDirWatch): KDirWatch: Can't use FAM kded: Does not exist! (/home/joss/.kde2/share/servicetypes/) kio (KLauncher): KLauncher: Got kdeinit_exec_wait('kbuildsycoca', ...) kio (KLauncher): kbuildsycoca (pid 1821) up and running. kbuildsycoca: Recreating ksycoca file kbuildsycoca: Database is up to date DCOP aborting call from 'anonymous-1819' to 'kded' ERROR: KUniqueApplication: DCOP communication error! DCOP aborting call from 'anonymous-1809' to 'kcontrol' ERROR: KUniqueApplication: DCOP communication error! 20:53 joss:~ $ klauncher: KLauncher::process ---> terminateKDE kdeinit: Fatal IO error: client killed kdeinit: sending SIGHUP to children. kdeinit: sending SIGTERM to children. kdeinit: Exit. any ideas? Thanks Joss --

1 0

Fwd: SuSE7,3PPC does not want to print SOLVED
by Alain Barthelemy 04 Mar '02

04 Mar '02

Solved. I had to mambo-jambo with Yast2 without really understanding (remote printer, files to be transfered or not???) ---------- Message transmis ---------- Subject: SuSE7,3PPC does not want to print Date: Mon, 4 Mar 2002 15:25:04 +0100 From: Alain Barthelemy <abarthelemy(a)sbb2.ihe.be> To: suse-ppc(a)suse.com Before I had SuSE7,1PPC or SuSE7.2 or 7.3 on PC's and I could print without problems on a remote printer (LaserWriter 8500 or HP4100). Then I upgraded from SuSE7,1 PPC to SuSE7.3PPC and ... impossible to print anymore. lpd is running Here is my /etc/printcap: lp|lp2|PS_600dpi-a4-auto-mono-600|PS_600dpi a4 auto mono 600:\ :lp=/dev/lp0:\ :sd=/var/spool/lpd/PS_600dpi-a4-auto-mono-600:\ :lf=/var/spool/lpd/PS_600dpi-a4-auto-mono-600/log:\ :af=/var/spool/lpd/PS_600dpi-a4-auto-mono-600/acct:\ :if=/var/lib/apsfilter/bin/PS_600dpi-a4-auto-mono-600:\ :la@:mx#0:\ :tr=:cl:sh:sf: # ### END apsfilter: ### PS_600dpi a4 mono 600 ### # zoe|remote printer on 192.168.20.101:\ :sd=/var/spool/lpd/zoe:\ :rm=192.168.20.101:\ :rp=lp:\ :bk:sh:mx#0: # gertrude|remote printer on 192.168.20.102:\ :sd=/var/spool/lpd/gertrude:\ :rm=192.168.20.102:\ :rp=lp:\ :bk:sh:mx#0: # My old /etc/printcap on SuSE7.1 (thus working) looks like: lp|lp2|PS_600dpi-a4-auto-mono-600|PS_600dpi a4 auto mono 600:\ :lp=/dev/lp0:\ :sd=/var/spool/lpd/PS_600dpi-a4-auto-mono-600:\ :lf=/var/spool/lpd/PS_600dpi-a4-auto-mono-600/log:\ :af=/var/spool/lpd/PS_600dpi-a4-auto-mono-600/acct:\ :if=/var/lib/apsfilter/bin/PS_600dpi-a4-auto-mono-600:\ :la@:mx#0:\ :tr=:cl:sh:sf: # ### END apsfilter: ### PS_600dpi a4 mono 600 ### # zoe|remote printer on 192.168.20.101:\ :sd=/var/spool/lpd/zoe:\ :rm=192.168.20.101:\ :rp=lp:\ :bk:sh:mx#0: # gertrude|remote printer on 192.168.20.102:\ :sd=/var/spool/lpd/gertrude:\ :rm=192.168.20.102:\ :rp=lp:\ :bk:sh:mx#0: ==== If you see a difference please tell me. ==== Now if I want to print with kmail I have the following error message: Error /usr/bin/lpr -P 'zoe|remote printer on 192.168.20.101' '-#1' /home/alain/.kde2/tmp-pwbook_V11qgOZ: execution stopped with message: Status Information: sending job 'alain@pwbook98+12' to zoe|remote printer on 192.168.20.101@localhost connecting to 'localhost' attempt 1 connected to 'localhost' requesting printer zoe|remote printer on 192.168.20.101@localhost job 'alain@pwbook98+12' transfer to zoe|remote printer on 192.168.20.101@localhost failed error 'NONZERO RFC1179 ERROR CODE FROM SERVER' with ack 'ACK_FAIL' sending '^Bzoe|remote printer on 192.168.20.101@localhost error msg: 'bad command line' Thus ACK fail, my host and the printer fails to communicate. What changed thus between SuSE 7.1 ans SuSE 7.3? There must be some mamboo-mamboo thing that has been installed or a line must be uncommented somewhere Is there a line that must be uncommented in /etc/inetd.conf? # See "man 8 inetd" for more information. # # If you make changes to this file, either reboot your machine or send the # inetd a HUP signal with "/sbin/init.d/inetd reload" or by hand: # Do a "ps x" as root and look up the pid of inetd. Then do a # "kill -HUP <pid of inetd>". # The inetd will re-read this file whenever it gets that signal. # # <service_name> <sock_type> <proto> <flags> <user> <server_path> <args> # # echo stream tcp nowait root internal # echo dgram udp wait root internal # discard stream tcp nowait root internal # discard dgram udp wait root internal # daytime stream tcp nowait root internal # daytime dgram udp wait root internal # chargen stream tcp nowait root internal # chargen dgram udp wait root internal time stream tcp nowait root internal time dgram udp wait root internal # # These are standard services. # # ftp stream tcp nowait root /usr/sbin/tcpd wu.ftpd -a # ftp stream tcp nowait root /usr/sbin/tcpd proftpd ftp stream tcp nowait root /usr/sbin/tcpd in.ftpd # # If you want telnetd not to "keep-alives" (e.g. if it runs over a ISDN # uplink), add "-n". See 'man telnetd' for more details. telnet stream tcp nowait root /usr/sbin/tcpd in.telnetd # nntp stream tcp nowait news /usr/sbin/tcpd /usr/sbin/leafnode # smtp stream tcp nowait root /usr/sbin/sendmail sendmail -bs printer stream tcp nowait root /usr/sbin/tcpd /usr/bin/lpd -i # # Shell, login, exec and talk are BSD protocols. # The option "-h" permits ``.rhosts'' files for the superuser. Please look at # man-page of rlogind and rshd to see more configuration possibilities about # .rhosts files. # shell stream tcp nowait root /usr/sbin/tcpd in.rshd -L # shell stream tcp nowait root /usr/sbin/tcpd in.rshd -aL # # If you want rlogind not to "keep-alives" (e.g. if it runs over a ISDN # uplink), add "-n". See 'man rlogind' for more details. login stream tcp nowait root /usr/sbin/tcpd in.rlogind # login stream tcp nowait root /usr/sbin/tcpd in.rlogind -a # exec stream tcp nowait root /usr/sbin/tcpd in.rexecd # talk dgram udp wait root /usr/sbin/tcpd in.talkd # ntalk dgram udp wait root /usr/sbin/tcpd in.talkd # # # Pop et al # # pop2 stream tcp nowait root /usr/sbin/tcpd in.pop2d pop3 stream tcp nowait root /usr/sbin/tcpd /usr/sbin/popper -s # # Imapd - Interactive Mail Access Protocol server # Attention: This service is very insecure # imap stream tcp nowait root /usr/sbin/tcpd imapd # # Comsat - has to do with mail. # # comsat dgram udp wait root /usr/sbin/tcpd in.comsat # # The Internet UUCP service. # # uucp stream tcp nowait uucp /usr/sbin/tcpd /usr/lib/uucp/uucico -l # # Tftp service is provided primarily for booting. Most sites # run this only on machines acting as "boot servers." # # tftp dgram udp wait root /usr/sbin/tcpd in.tftpd -s /tftpboot # bootps dgram udp wait root /usr/sbin/bootpd bootpd -c /tftpboot # # Finger, systat and netstat give out user information which may be # valuable to potential "system crackers." Many sites choose to disable # some or all of these services to improve security. # Try "telnet localhost systat" and "telnet localhost netstat" to see that # information yourself! # # finger stream tcp nowait nobody /usr/sbin/tcpd in.fingerd -w # systat stream tcp nowait nobody /usr/sbin/tcpd /bin/ps -auwwx # netstat stream tcp nowait root /usr/sbin/tcpd /bin/netstat -a # # For man on the fly and ht://dig (full text search) # http-rman stream tcp nowait.10000 nobody /usr/sbin/tcpd /usr/sbin/http-rman # # For XCept4 # # btx stream tcp nowait root /usr/sbin/tcpd /usr/lib/xcept4/bin/ceptd -i/usr/lib/xcept4/etc/init.ceptd -u/usr/lib/xcept4/etc/users.ceptd -l/var/log/log.ceptd # # For rplay daemon # # Old versions of rplay: # rplay dgram udp wait root /usr/sbin/tcpd rplayd -b 8192 -c 60 -s 8192 # New Versions of rplay (>=3.3.0) # rplay dgram udp wait root /usr/sbin/tcpd rplayd -t 30 -c 60 -s 16384 -F0 --inetd # # vbox (Voice Box) # vboxd stream tcp nowait root /usr/sbin/tcpd /usr/sbin/vboxd # # For midinetd # midinet stream tcp nowait root /usr/sbin/tcpd in.midinetd # # swat is the Samba Web Administration Tool # swat stream tcp nowait.400 root /usr/sbin/swat swat # # # amanda backup server with indexing capabilities # amandaidx stream tcp nowait root /usr/lib/amanda/amindexd amindexd # amidxtape stream tcp nowait root /usr/lib/amanda/amidxtaped amidxtaped # # amanda backup client # amanda dgram udp wait amanda /usr/lib/amanda/amandad amandad # # the rsync daemon # rsync stream tcp nowait root /usr/sbin/tcpd /usr/sbin/rsyncd --daemon # # # Mimer database # mimer stream tcp nowait root /opt/mimer/bin/mimtcp mimtcp -l # # CVS pserver (remote acces to your CVS repositories) # Please read the section on security and passwords in the CVS manual, # before you enable this. # cvspserver stream tcp nowait root /usr/sbin/tcpd /usr/bin/cvs --allow-root=/home/cvsroot pserver # # procstatd deamon (cluster software) # procstatd stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/procstatd -i 7885 # Thus what has happened? maybe a guru from SuSE can tell me what has changed from SuSE 7,1PPC to SuSE7.3PPC -- Alain Barthélemy -------------------------------------------------------

1 0

SuSE7,3PPC does not want to print
by Alain Barthelemy 04 Mar '02

04 Mar '02

Before I had SuSE7,1PPC or SuSE7.2 or 7.3 on PC's and I could print without problems on a remote printer (LaserWriter 8500 or HP4100). Then I upgraded from SuSE7,1 PPC to SuSE7.3PPC and ... impossible to print anymore. lpd is running Here is my /etc/printcap: lp|lp2|PS_600dpi-a4-auto-mono-600|PS_600dpi a4 auto mono 600:\ :lp=/dev/lp0:\ :sd=/var/spool/lpd/PS_600dpi-a4-auto-mono-600:\ :lf=/var/spool/lpd/PS_600dpi-a4-auto-mono-600/log:\ :af=/var/spool/lpd/PS_600dpi-a4-auto-mono-600/acct:\ :if=/var/lib/apsfilter/bin/PS_600dpi-a4-auto-mono-600:\ :la@:mx#0:\ :tr=:cl:sh:sf: # ### END apsfilter: ### PS_600dpi a4 mono 600 ### # zoe|remote printer on 192.168.20.101:\ :sd=/var/spool/lpd/zoe:\ :rm=192.168.20.101:\ :rp=lp:\ :bk:sh:mx#0: # gertrude|remote printer on 192.168.20.102:\ :sd=/var/spool/lpd/gertrude:\ :rm=192.168.20.102:\ :rp=lp:\ :bk:sh:mx#0: # My old /etc/printcap on SuSE7.1 (thus working) looks like: lp|lp2|PS_600dpi-a4-auto-mono-600|PS_600dpi a4 auto mono 600:\ :lp=/dev/lp0:\ :sd=/var/spool/lpd/PS_600dpi-a4-auto-mono-600:\ :lf=/var/spool/lpd/PS_600dpi-a4-auto-mono-600/log:\ :af=/var/spool/lpd/PS_600dpi-a4-auto-mono-600/acct:\ :if=/var/lib/apsfilter/bin/PS_600dpi-a4-auto-mono-600:\ :la@:mx#0:\ :tr=:cl:sh:sf: # ### END apsfilter: ### PS_600dpi a4 mono 600 ### # zoe|remote printer on 192.168.20.101:\ :sd=/var/spool/lpd/zoe:\ :rm=192.168.20.101:\ :rp=lp:\ :bk:sh:mx#0: # gertrude|remote printer on 192.168.20.102:\ :sd=/var/spool/lpd/gertrude:\ :rm=192.168.20.102:\ :rp=lp:\ :bk:sh:mx#0: ==== If you see a difference please tell me. ==== Now if I want to print with kmail I have the following error message: Error /usr/bin/lpr -P 'zoe|remote printer on 192.168.20.101' '-#1' /home/alain/.kde2/tmp-pwbook_V11qgOZ: execution stopped with message: Status Information: sending job 'alain@pwbook98+12' to zoe|remote printer on 192.168.20.101@localhost connecting to 'localhost' attempt 1 connected to 'localhost' requesting printer zoe|remote printer on 192.168.20.101@localhost job 'alain@pwbook98+12' transfer to zoe|remote printer on 192.168.20.101@localhost failed error 'NONZERO RFC1179 ERROR CODE FROM SERVER' with ack 'ACK_FAIL' sending '^Bzoe|remote printer on 192.168.20.101@localhost error msg: 'bad command line' Thus ACK fail, my host and the printer fails to communicate. What changed thus between SuSE 7.1 ans SuSE 7.3? There must be some mamboo-mamboo thing that has been installed or a line must be uncommented somewhere Is there a line that must be uncommented in /etc/inetd.conf? # See "man 8 inetd" for more information. # # If you make changes to this file, either reboot your machine or send the # inetd a HUP signal with "/sbin/init.d/inetd reload" or by hand: # Do a "ps x" as root and look up the pid of inetd. Then do a # "kill -HUP <pid of inetd>". # The inetd will re-read this file whenever it gets that signal. # # <service_name> <sock_type> <proto> <flags> <user> <server_path> <args> # # echo stream tcp nowait root internal # echo dgram udp wait root internal # discard stream tcp nowait root internal # discard dgram udp wait root internal # daytime stream tcp nowait root internal # daytime dgram udp wait root internal # chargen stream tcp nowait root internal # chargen dgram udp wait root internal time stream tcp nowait root internal time dgram udp wait root internal # # These are standard services. # # ftp stream tcp nowait root /usr/sbin/tcpd wu.ftpd -a # ftp stream tcp nowait root /usr/sbin/tcpd proftpd ftp stream tcp nowait root /usr/sbin/tcpd in.ftpd # # If you want telnetd not to "keep-alives" (e.g. if it runs over a ISDN # uplink), add "-n". See 'man telnetd' for more details. telnet stream tcp nowait root /usr/sbin/tcpd in.telnetd # nntp stream tcp nowait news /usr/sbin/tcpd /usr/sbin/leafnode # smtp stream tcp nowait root /usr/sbin/sendmail sendmail -bs printer stream tcp nowait root /usr/sbin/tcpd /usr/bin/lpd -i # # Shell, login, exec and talk are BSD protocols. # The option "-h" permits ``.rhosts'' files for the superuser. Please look at # man-page of rlogind and rshd to see more configuration possibilities about # .rhosts files. # shell stream tcp nowait root /usr/sbin/tcpd in.rshd -L # shell stream tcp nowait root /usr/sbin/tcpd in.rshd -aL # # If you want rlogind not to "keep-alives" (e.g. if it runs over a ISDN # uplink), add "-n". See 'man rlogind' for more details. login stream tcp nowait root /usr/sbin/tcpd in.rlogind # login stream tcp nowait root /usr/sbin/tcpd in.rlogind -a # exec stream tcp nowait root /usr/sbin/tcpd in.rexecd # talk dgram udp wait root /usr/sbin/tcpd in.talkd # ntalk dgram udp wait root /usr/sbin/tcpd in.talkd # # # Pop et al # # pop2 stream tcp nowait root /usr/sbin/tcpd in.pop2d pop3 stream tcp nowait root /usr/sbin/tcpd /usr/sbin/popper -s # # Imapd - Interactive Mail Access Protocol server # Attention: This service is very insecure # imap stream tcp nowait root /usr/sbin/tcpd imapd # # Comsat - has to do with mail. # # comsat dgram udp wait root /usr/sbin/tcpd in.comsat # # The Internet UUCP service. # # uucp stream tcp nowait uucp /usr/sbin/tcpd /usr/lib/uucp/uucico -l # # Tftp service is provided primarily for booting. Most sites # run this only on machines acting as "boot servers." # # tftp dgram udp wait root /usr/sbin/tcpd in.tftpd -s /tftpboot # bootps dgram udp wait root /usr/sbin/bootpd bootpd -c /tftpboot # # Finger, systat and netstat give out user information which may be # valuable to potential "system crackers." Many sites choose to disable # some or all of these services to improve security. # Try "telnet localhost systat" and "telnet localhost netstat" to see that # information yourself! # # finger stream tcp nowait nobody /usr/sbin/tcpd in.fingerd -w # systat stream tcp nowait nobody /usr/sbin/tcpd /bin/ps -auwwx # netstat stream tcp nowait root /usr/sbin/tcpd /bin/netstat -a # # For man on the fly and ht://dig (full text search) # http-rman stream tcp nowait.10000 nobody /usr/sbin/tcpd /usr/sbin/http-rman # # For XCept4 # # btx stream tcp nowait root /usr/sbin/tcpd /usr/lib/xcept4/bin/ceptd -i/usr/lib/xcept4/etc/init.ceptd -u/usr/lib/xcept4/etc/users.ceptd -l/var/log/log.ceptd # # For rplay daemon # # Old versions of rplay: # rplay dgram udp wait root /usr/sbin/tcpd rplayd -b 8192 -c 60 -s 8192 # New Versions of rplay (>=3.3.0) # rplay dgram udp wait root /usr/sbin/tcpd rplayd -t 30 -c 60 -s 16384 -F0 --inetd # # vbox (Voice Box) # vboxd stream tcp nowait root /usr/sbin/tcpd /usr/sbin/vboxd # # For midinetd # midinet stream tcp nowait root /usr/sbin/tcpd in.midinetd # # swat is the Samba Web Administration Tool # swat stream tcp nowait.400 root /usr/sbin/swat swat # # # amanda backup server with indexing capabilities # amandaidx stream tcp nowait root /usr/lib/amanda/amindexd amindexd # amidxtape stream tcp nowait root /usr/lib/amanda/amidxtaped amidxtaped # # amanda backup client # amanda dgram udp wait amanda /usr/lib/amanda/amandad amandad # # the rsync daemon # rsync stream tcp nowait root /usr/sbin/tcpd /usr/sbin/rsyncd --daemon # # # Mimer database # mimer stream tcp nowait root /opt/mimer/bin/mimtcp mimtcp -l # # CVS pserver (remote acces to your CVS repositories) # Please read the section on security and passwords in the CVS manual, # before you enable this. # cvspserver stream tcp nowait root /usr/sbin/tcpd /usr/bin/cvs --allow-root=/home/cvsroot pserver # # procstatd deamon (cluster software) # procstatd stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/procstatd -i 7885 # Thus what has happened? maybe a guru from SuSE can tell me what has changed from SuSE 7,1PPC to SuSE7.3PPC -- Alain Barthélemy

1 0

RE: [suse-ppc] PowerStack Series E, installing 7.3
by Wrobel Heinz-r39252 04 Mar '02

04 Mar '02

Olaf, > This was due to a last minute change to allow booting on a 43p 140, it > broke PReP MTX and similar... > You might be able to boot with "noinitrd" into the installed system. Any chance that SuSE FAQ entries could reflect something like this? *grin* > Do you have a CL5446? Mine can not do more than 1024x768 or I will get > garbage after a while. You need to generate your own modeline, or use > fbset: > > fbset -a 1024x768-75 -depth 8 > sax2 -a It's a CL5434 with 2MB according to what the machine tells me. Didn't open it up. When trying your lines it will 1st switch the video mode into a nicer text dispaly and 2nd complete the sax2 run. It will then freeze shortly after (I pressed return twice at the shell prompt and it was dead after the frist return press). Using startx after a hard shutdown/reboot, X came up again but froze after just a few clicks. The resolution feels initially more like 800x600. Maybe I should let the guru meditate for a while before I try this again. The guy who wants to play with it will just have to live without X for now. > > - "halt" doesn't. The machine will reboot and doesn't stop. > Actually, no PPC > > kernel ever halted on the PowerStacks that I tried. Wonder why. > > Known bug, no idea how to tweak the registers... Maybe I can find the time to solve this within this millenium. It is annoying. If it ever happens, I'll let you know. Heinz

1 0

A little help updating KDE2.2.2 Welcome
by Emilio Silva 03 Mar '02

03 Mar '02

1)My last step updating KDE2.2.2(install kdebase.rpm) faces the following warnings:after installing all other rpms of BASE. - libcdda_interface.so.0 is needed... - libcdda_paranoia.so.0 is needed... I use SuSE7.0 and downloaded the KDE2.2.2 packages for 7.0 version of SuSEppc(glibc 2.1.3-172) so these components should be present.How can I get through this? 2) -libXm.so.1 also lacks for kdebase-nsplugin.rpm(WhatŽs this libXm.so.1 and where can I get it?). Find the best deals on the web at AltaVista Shopping! http://www.shopping.altavista.com

1 0

USB-CD-writers supported by SuSE 7.1 (ppc)?
by Markus Kuschnik 02 Mar '02

02 Mar '02

Dear listmembers, Does anyone of you know about a website listing USB-CD-writers which are compatible with (or incompatible with, in case that is easier) SuSE-Linux 7.1 (2.4-kernel)? I am running the said software on a 2 GB partition on my iMac, and I'd like to find external CD-writers that are accessible via the Mac-partition (OS 9.2) as well as via SuSE-Linux 7.1. Thanks in advance for any suggestions, Markus Kuschnik mkuschnik(a)freenet.de

1 0

Installation problem Suse 7.1 PPC on IBM B50
by Alex Soares 01 Mar '02

01 Mar '02

Hello there, i'm trying to install suse 7.1 ppc on an IBM RS/6000 B50 server. i tried installing it accordingly to the instructions on the manual but was faced with serious problems. after booting from the CD 2 ( CHRP Based computers ) the boot process freezes at: ramdisk loaded at 0x1900000, size 753253 bytes instantiating rtas at 00600000 ... done copying OF device tree... done returning 01400000 from prom_init we have looked all around for help, including Suse's knowledge database, google and other places with no success. the server is installed with AIX and functioning perfectly. it does not look like a hardware problem. please help, i have never seen anything like it before and it is not mentioned anywhere. thank you -- Alex 1100001 1101100 1100101 1111000 1100001 1110100 1011010 1100101 1110010 1101111 1001011 1100101 1101100 1110110 1101001 1101110 1100100 1101111 1110100 1100011 1100011

3 4

Freeswan
by Uwe Hees 01 Mar '02

01 Mar '02

Hi, Is anyone running freeswan on SuSE 7.3/PPC with kernel 2.4.16? Mine did not work because the module ipsec.o is missing. Rolling my own did not work because the freeswan kernel patches did not apply. Maybe anyone has already an spm for freeswan 1.95? Uwe

2 1

PowerStack Series E, installing 7.3
by Wrobel Heinz-r39252 01 Mar '02

01 Mar '02

Hi, I had the chance to spend a few hours installing plain 7.3 on a Motorola PowerStack Series E with 64MB RAM and a 604 CPU. Not a whole lot of time, but I noticed a few things up to now that may be of interest as I couldn't find comments anywhere on these topics. - While I could boot the first CD, the machine froze after the message "Uncompressing" when trying to set up the RAMDISK. Couldn't find a way to get around this. Is the PReP CD boot kernel known to be broken? - I used some very old (6.4?) install disks I still had somewhere to boot a kernel far enough to get to the 7.3 CDs. Didn't have much success putting the kernel image available with 7.3 onto floppy disks. They are apparently larger than 1.44MB. Oh well. - The PowerStack in question was AIX formatted. The install process will not allow partitioning and will not(!) issue an error message. I used a separate virtual console to manually pre-partition the disk to a DOS empty state to be able to install the system. Took me a while to figure that out. - Debian documents a "bootargs" PPCBUG variable which apparently the SuSE kernel doesn't support. I hacked the kernel content for the root partition name. Would be nice though if it supported bootargs. - /usr/X11R6/bin/sax doesn't exist. Well, sax.sh does, but that's not what sax2 tells me. Anyway, XF86 V3/4 apparently isn't set up to support the Cirrus chipset as both sax and sax2 freeze the machine with a black screen eventually. Interesting enough, X itself starts up in 640*480with FBDev on top of CLgen,cfb8 but sax/sax2 won't ever. X freezes up the machine *very* easily on just a few mouse clicks. I guess for now I have to avoid X. - "halt" doesn't. The machine will reboot and doesn't stop. Actually, no PPC kernel ever halted on the PowerStacks that I tried. Wonder why. Ok, maybe some of this helps others, maybe you also have some input that could help me. Heinz Wrobel

2 1

Does anyone use an Acard IDE-Adapter?
by Manz＠lifenet.de 01 Mar '02

01 Mar '02

Hello! I have an old PPC 9500 with a built-in scsi-bus (2 actually) and an Acard PCI-IDE-Card (AEC6260R). I have SuSE 7.3 on the old scsi-drive sda. The program does recognize the IDE-card and the drive attached to it, but I get boot-messages like hde: lost interrupt, lost irq func only, dma_chipset ???, and the drive is being probed for ages. I tried to install Macos under MOL on it, but I gave up, because it takes ages. It will probably run all night for an installation. Has anyone solved these problems? Marianne

2 1