openSUSE PPC September 2004

ppc@lists.opensuse.org

7 participants
9 discussions

by Damir Buskulic

Hi, I got some problems (disk access denied, bus errors,...) that led me to go into single user mode and fsck my partitions. I noticed then that there were some directories created in the tmp directory, called "dev" and "etc", and one file in the / directory called "success" with 0 length. At reboot, these files disapeared. Does anybody know if this could be a sign of a hacked computer ? I mean could someone have installed a rootkit or some such ? I'm not paranoid but this indeed seems strange. Cheers Damir -- ===================================================================== | Damir Buskulic | Universite de Savoie/LAPP | | | Chemin de Bellevue, B.P. 110 | | Tel : +33 (0)450091600 | F-74941 Annecy-le-Vieux Cedex | | e-mail: buskulic(a)lapp.in2p3.fr | FRANCE | ===================================================================== mailto:buskulic@lapp.in2p3.fr

12 years, 10 months

SLES9 / IBM 7025 F50 - Problems with SMP kernel

by Braulio Gergull

I've just installed SLES9 on a IBM 7025 F50 with 2 processors. In contrast to SLES8 there was no problem during the installation process. The only problem is that YaST installed default kernel (non SMP). I've installed the SMP kernel that ships with the distribution, ran mk_initrd and made the relevant changes to yaboot. However this kernel won't boot the machine, in fact the boot process aborts before the kernel is loaded into memory. Is there anybody using SLES9 on a F50 with multi processor support? rgrds, Bráulio Gergull gergull(a)getnet.com.br

16 years

SLES9 on a G5

by Kyle Ellrott

I would like to install SLES on a G5, but I'm thwarted by a Kernel panic that happens before I even get to the installer. I was attempting to load Suse Linux Enterprise Server 9, RC5, on an Apple Xserve 64. It started to load the kernel, but then panicked while loading PCI drivers. It happens pretty quickly, before the installer has had a chance to come up, and I never see any boot options. This is a standard Apple Xserve 64, except that is has a 'non-standard' video card, the MPDDpro (http://www.villagetronic.com/mpdd/mpddpro_appl.html) This card is compatible with MacOSX, and works fine with SLES 9 (I can read the error messages on the monitor), my only reason for thinking it's the problem is that the stack trace from the kernel panic originated in the PCI driver loader. ..pci_direct_alloc_consistent+0x48/0x8c (unreliable) ..gem_init_one+0x49c/0x77c ..pci_device_probe+0x100/0x268 ..bus_match+0x94/0xf8 ..driver_attach+0x8c/0x110 ..bus_add_driver+0xf8/0x134 ..driver_register+0x38/0x4c ..pci_register_diver+0x80/0xe4 ..gem_init+0x1c/0x48 ..init+0x218/0x3d0 ..kernel_thread+0x4c/068 Kyle

16 years, 9 months

IBM AS/400 9406/170

by Vakvarju

Someone has experience with similar midrange IMB server? Is it possible to install Linux on it? Actually it runs OS400 V4.R3.M0 and DB/2. IBM's reference states only iSeries as Linux compatible midrange servers but no any of their predecessors. Any idea? -- ________________________ /"\ Vakvarju \ / ASCII Ribbon Campaign vakvarju_at_spektrum-3d_dot_hu X Against HTML Mail / \

16 years, 10 months

RE: [suse-ppc] problems with initialization while accessing NFS m ounte d root file sys tem during the boot

by Mahmoud, Magdy

How do I unsubscribe from this list? Thanks Magdy Mahmoud -----Original Message----- From: Alexander Povolotsky [mailto:pevnev@juno.com] Sent: Thursday, September 16, 2004 2:45 PM To: suse-ppc(a)suse.com Subject: Re: [suse-ppc] problems with initialization while accessing NFS mounte d root file sys tem during the boot I forgot to mention that I am booting Linux 2.6.8-rc4 - ... sure it is not suse but perharps someone on this list is dealing with vanilla Linux too ... ****************** Hi, I've managed to program U-boot bootloader and now am trying to boot my PQ2FADS-VR board ...but I have problems with the initialization while accessing NFS mounted root file system ... . I have NFS server running on my Windows XP Laptop (that is all I am allowed to have, no Linux hosts machine available to me ...). I copied entire "fadsroot" directory from Arabella's CD-ROM into my "fadsroot" directory on my D-drive and made this directory nfs-shared-mountable (I have propagated permissions from "fadsroot" down to all subfolders within "fadsroot" ...). I noticed several errors during the copy process - complaining that I am over-writing the files being already copied - is it an issue with "letter case" ? - are there files on the Arabella's CD-ROM "fadsroot", which have same names but differ just in the letter case used ? Anyway I am getting the following error during the end of the boot: ...... device=eth0, addr=192.168.1.103, mask=255.255.255.0, gw=255.255.255.255, host=192.168.1.103, domain=, nis-domain=(none), bootserver=255.255.255.255, rootserver=192.168.1.100, rootpath= Looking up port of RPC 100003/2 on 192.168.1.100 Looking up port of RPC 100005/1 on 192.168.1.100 VFS: Mounted root (nfs filesystem). Freeing unused kernel memory: 272k init Warning: unable to open an initial console. Kernel panic: No init found. Try passing init= option to kernel. <0>Rebooting in 180 seconds.. My U-boot environment is: => printenv bootdelay=5 bootcmd=bootm 200000 ipaddr=192.168.1.103 serverip=192.168.1.100 ethaddr=08:00:17:00:00:03 bootargs=root /dev/nfs rw nfsroot=192.168.1.100:/home/apovolot/fadsroot baudrate=19200 stdin=serial stdout=serial stderr=serial Any ideas ? Thanks, Alex ________________________________________________________________ Get your name as your email address. Includes spam protection, 1GB storage, no ads and more Only $1.99/ month - visit http://www.mysite.com/name today! Please do not transmit orders or instructions regarding a UBS account by email. The information provided in this email or any attachments is not an official transaction confirmation or account statement. For your protection, do not include account numbers, Social Security numbers, credit card numbers, passwords or other non-public information in your email. Because the information contained in this message may be privileged, confidential, proprietary or otherwise protected from disclosure, please notify us immediately by replying to this message and deleting it from your computer if you have received this communication in error. Thank you. UBS Financial Services Inc. UBS International Inc.

16 years, 10 months

Re: [suse-ppc] problems with initialization while accessing NFS mounte d root file sys tem during the boot

by Alexander Povolotsky

I forgot to mention that I am booting Linux 2.6.8-rc4 - ... sure it is not suse but perharps someone on this list is dealing with vanilla Linux too ... ****************** Hi, I've managed to program U-boot bootloader and now am trying to boot my PQ2FADS-VR board ...but I have problems with the initialization while accessing NFS mounted root file system ... . I have NFS server running on my Windows XP Laptop (that is all I am allowed to have, no Linux hosts machine available to me ...). I copied entire "fadsroot" directory from Arabella's CD-ROM into my "fadsroot" directory on my D-drive and made this directory nfs-shared-mountable (I have propagated permissions from "fadsroot" down to all subfolders within "fadsroot" ...). I noticed several errors during the copy process - complaining that I am over-writing the files being already copied - is it an issue with "letter case" ? - are there files on the Arabella's CD-ROM "fadsroot", which have same names but differ just in the letter case used ? Anyway I am getting the following error during the end of the boot: ...... device=eth0, addr=192.168.1.103, mask=255.255.255.0, gw=255.255.255.255, host=192.168.1.103, domain=, nis-domain=(none), bootserver=255.255.255.255, rootserver=192.168.1.100, rootpath= Looking up port of RPC 100003/2 on 192.168.1.100 Looking up port of RPC 100005/1 on 192.168.1.100 VFS: Mounted root (nfs filesystem). Freeing unused kernel memory: 272k init Warning: unable to open an initial console. Kernel panic: No init found. Try passing init= option to kernel. <0>Rebooting in 180 seconds.. My U-boot environment is: => printenv bootdelay=5 bootcmd=bootm 200000 ipaddr=192.168.1.103 serverip=192.168.1.100 ethaddr=08:00:17:00:00:03 bootargs=root /dev/nfs rw nfsroot=192.168.1.100:/home/apovolot/fadsroot baudrate=19200 stdin=serial stdout=serial stderr=serial Any ideas ? Thanks, Alex ________________________________________________________________ Get your name as your email address. Includes spam protection, 1GB storage, no ads and more Only $1.99/ month - visit http://www.mysite.com/name today!

16 years, 10 months

problems with initialization while accessing NFS mounted root file sys tem during the boot

by Alexander Povolotsky

Hi, I've managed to program U-boot bootloader and now am trying to boot my PQ2FADS-VR board ...but I have problems with the initialization while accessing NFS mounted root file system ... . I have NFS server running on my Windows XP Laptop (that is all I am allowed to have, no Linux hosts machine available to me ...). I copied entire "fadsroot" directory from Arabella's CD-ROM into my "fadsroot" directory on my D-drive and made this directory nfs-shared-mountable (I have propagated permissions from "fadsroot" down to all subfolders within "fadsroot" ...). I noticed several errors during the copy process - complaining that I am over-writing the files being already copied - is it an issue with "letter case" ? - are there files on the Arabella's CD-ROM "fadsroot", which have same names but differ just in the letter case used ? Anyway I am getting the following error during the end of the boot: ...... device=eth0, addr=192.168.1.103, mask=255.255.255.0, gw=255.255.255.255, host=192.168.1.103, domain=, nis-domain=(none), bootserver=255.255.255.255, rootserver=192.168.1.100, rootpath= Looking up port of RPC 100003/2 on 192.168.1.100 Looking up port of RPC 100005/1 on 192.168.1.100 VFS: Mounted root (nfs filesystem). Freeing unused kernel memory: 272k init Warning: unable to open an initial console. Kernel panic: No init found. Try passing init= option to kernel. <0>Rebooting in 180 seconds.. My U-boot environment is: => printenv bootdelay=5 bootcmd=bootm 200000 ipaddr=192.168.1.103 serverip=192.168.1.100 ethaddr=08:00:17:00:00:03 bootargs=root /dev/nfs rw nfsroot=192.168.1.100:/home/apovolot/fadsroot baudrate=19200 stdin=serial stdout=serial stderr=serial Any ideas ? Thanks, Alex ________________________________________________________________ Get your name as your email address. Includes spam protection, 1GB storage, no ads and more Only $1.99/ month - visit http://www.mysite.com/name today!

16 years, 10 months

Linux performance benchmarks runnable on PowerPC platform ?

by Alexander Povolotsky

Hello, Anyone from this list cross-compiled (for PPC) lmbench using cygwin (yes on Windows - sorry this is "set in the stone" for me - and I have to follow the orders ...) and run lmbench on Linux on 82xx diskless board ? Ditto re "Cerberus Test Control System" ? Thanks, Alex ________________________________________________________________ Get your name as your email address. Includes spam protection, 1GB storage, no ads and more Only $1.99/ month - visit http://www.mysite.com/name today!

16 years, 10 months

Thanks, plus questions

by Erik Hentell

Hi all, First I want to thank everyone for helping me out. I posted a question about setting up a linux router for my home network some time back. Everyone's suggestions helped, and I eventually found some tutorials over at Yolinux.com that helped me get a handle on things. As for my questions, they are a little off topic, but I thought people here might know, if anyone. I recently tried to put an NIC in my Linux Powermac. It was a PCI card so I thought it would work, but it was also being sold for PC systems only(including Linux OS). After I put it in, my other computer couldn't be ping'd or connect the the Internet through the router. I thought a setting was off or something until I decided to replace the cable. Then everything worked fine. I'm writing this email through the other computer now. So my question is this; was my card simply defective, or is there a significant difference between PCI cards for PCs, and PCI cards for Macs? SuSE found the card with little prompting; I was able to designate it eth1 and give it an IP. Occassionally I'd have to reboot when the system was just starting up, but that was it. Next, could the card have fried my Ethernet cable? I find it hard to believe, but it was definitely working fine before I installed the NIC. Regardless, can the cable be fixed, or is it now junk? Again, I know these questions are off-topic, but I'm a newbie to linux and networking, so I thought someone might be able to fill me in. Thanks again, Erik -- ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm

16 years, 10 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

openSUSE PPC September 2004