February 2002 - openSUSE IA64 - openSUSE Mailing Lists

RE: [suse-ia64] boot, kdm problems
by COBURN,JEFF (HP-Loveland,ex1) 13 Feb '02

13 Feb '02

> > I noticed that KDE takes a long time even when using startx, but > I waited half an hour. I also tried to connect the monitor > to the second > output, but nothing was there either. So I powercycled the machine. > The IBM 6894-10X uses Matrox G450, according to the specs at IBM's > site. SuSE installed a G400. I will try to set to G450, although > with startx everything seems to work fine. > > I've seen a similiar issue to your kdm problem on our (HP's) i2000 workstations. A workaround is using gdm instead of kdm, and it seems to have been fixed when we updated to the 2.4.16 kernel. Good luck. Regards, Jeff

1 0

boot, kdm problems
by Stefano Lodi 11 Feb '02

11 Feb '02

I am having difficulties in installing correctly the SuSE distribution. In particular, I can't utilize a DOS partition to boot the machine and I can't use kdm. The details of the problem: - The machine is an IBM Intellistation with 2 ITANIUM processors at 800MHz and 2 16GByte SCSI disks attached to a 160MHz Adaptec controller. - OS is SuSE Linux ia64 7.2. - The system was installed on a 6GByte ext2 partition /dev/sda1 and uses a 2 GByte swap on the same disk (/dev/sda2). Both partitions were created inside YAST2 manually. - When the installation program rebooted the machine the first time, the reboot failed. (This is fine since we had not created any DOS partition.) Therefore we booted again from CD1 (`boot an installed system') and finished the installation. - At this point the first real problem occurred. The installation program rebooted again but the boot process freezed after starting kdm. The monitor switched to powersave mode and Ctrl-Alt-Del was disabled. (Jan-Christoph Westermann reported a similar problem on January 31st in this list, I believe.) - We renamed /etc/init.d/xdm and rebooted (using CD1). The boot succeeded. We could started X as root from terminal by startx and play with the configuration manager sax2. - Now the really unexpected part. We created a partition with label "FAT16" and formatted it with mkdosfs -v -F 16 /dev/sda3. - We copied /boot/elilo.efi and /boot/vmlinuz to the DOS partition. - Rebooted. EFI could not see the DOS partition. However, the physical device is there, in the output of the map command. (EFI recognized only fs0:, the boot partition made visible by the installation cd.) We also checked later that the partition was readable. - We tried many times with different partition labels (does EFI check it?). No change. We also tried creating the DOS partition on /dev/sdb1. (But the EFI primer from Intel's site does not mention EFI preferences concerning drives or even partition numbers, if I understand it correctly.) Same effect. I would really appreciate any hint on how to solve these problems. Although I have some experience with Linux on IA-32 machines, IA-64 is entirely new to me. Thanks a lot. Stefano -- Stefano Lodi, PhD Researcher Dept. of Electronics, C.S. and Systems & Faculty of Statistical Sciences University of Bologna, ITALY

2 2

Kernel compile howto?
by Jan-Christoph Westermann 08 Feb '02

08 Feb '02

I downloaded the kernel2.4.16 sources from ftp://ftp.suse.com/pub/projects/kernel/2.4.16 The config was the default from SuSE. 'make bzImage' doens't work (i386 only) 'make boot' creates an error message (at the end of this mail). Do I need any more files to create an new kernel. Are there any rpm's for ia64? greetings, Jan Last lines of output from 'make boot': In file included from /usr/src/linux-2.4.16.SuSE/include/linux/pagemap.h:17, from /usr/src/linux-2.4.16.SuSE/include/linux/locks.h:9, from /usr/src/linux-2.4.16.SuSE/include/linux/devfs_fs_kernel.h:7, from init/main.c:17: /usr/src/linux-2.4.16.SuSE/include/linux/highmem.h: In function `clear_user_highpage': /usr/src/linux-2.4.16.SuSE/include/linux/highmem.h:49: too few arguments to function `clear_user_page' /usr/src/linux-2.4.16.SuSE/include/linux/highmem.h: In function `copy_user_highpage': /usr/src/linux-2.4.16.SuSE/include/linux/highmem.h:91: too few arguments to function `copy_user_page' init/main.c: In function `do_linuxrc': /usr/src/linux-2.4.16.SuSE/include/asm/unistd.h:292: warning: `dummy2' might be used uninitialized in this function /usr/src/linux-2.4.16.SuSE/include/asm/unistd.h:292: warning: `dummy3' might be used uninitialized in this function /usr/src/linux-2.4.16.SuSE/include/asm/unistd.h:292: warning: `dummy4' might be used uninitialized in this function /usr/src/linux-2.4.16.SuSE/include/asm/unistd.h:292: warning: `dummy5' might be used uninitialized in this function /usr/src/linux-2.4.16.SuSE/include/asm/unistd.h:292: warning: `dummy2' might be used uninitialized in this function /usr/src/linux-2.4.16.SuSE/include/asm/unistd.h:292: warning: `dummy3' might be used uninitialized in this function /usr/src/linux-2.4.16.SuSE/include/asm/unistd.h:292: warning: `dummy4' might be used uninitialized in this function /usr/src/linux-2.4.16.SuSE/include/asm/unistd.h:292: warning: `dummy5' might be used uninitialized in this function /usr/src/linux-2.4.16.SuSE/include/asm/unistd.h:292: warning: `dummy2' might be used uninitialized in this function /usr/src/linux-2.4.16.SuSE/include/asm/unistd.h:292: warning: `dummy3' might be used uninitialized in this function /usr/src/linux-2.4.16.SuSE/include/asm/unistd.h:292: warning: `dummy4' might be used uninitialized in this function /usr/src/linux-2.4.16.SuSE/include/asm/unistd.h:292: warning: `dummy5' might be used uninitialized in this function /usr/src/linux-2.4.16.SuSE/include/asm/unistd.h:285: warning: `dummy2' might be used uninitialized in this function /usr/src/linux-2.4.16.SuSE/include/asm/unistd.h:285: warning: `dummy3' might be used uninitialized in this function /usr/src/linux-2.4.16.SuSE/include/asm/unistd.h:285: warning: `dummy4' might be used uninitialized in this function /usr/src/linux-2.4.16.SuSE/include/asm/unistd.h:285: warning: `dummy5' might be used uninitialized in this function /usr/src/linux-2.4.16.SuSE/include/asm/unistd.h:291: warning: `dummy4' might be used uninitialized in this function /usr/src/linux-2.4.16.SuSE/include/asm/unistd.h:291: warning: `dummy5' might be used uninitialized in this function /usr/src/linux-2.4.16.SuSE/include/asm/unistd.h:289: warning: `dummy2' might be used uninitialized in this function /usr/src/linux-2.4.16.SuSE/include/asm/unistd.h:289: warning: `dummy3' might be used uninitialized in this function /usr/src/linux-2.4.16.SuSE/include/asm/unistd.h:289: warning: `dummy4' might be used uninitialized in this function /usr/src/linux-2.4.16.SuSE/include/asm/unistd.h:289: warning: `dummy5' might be used uninitialized in this function /usr/src/linux-2.4.16.SuSE/include/asm/unistd.h:289: warning: `dummy2' might be used uninitialized in this function /usr/src/linux-2.4.16.SuSE/include/asm/unistd.h:289: warning: `dummy3' might be used uninitialized in this function /usr/src/linux-2.4.16.SuSE/include/asm/unistd.h:289: warning: `dummy4' might be used uninitialized in this function /usr/src/linux-2.4.16.SuSE/include/asm/unistd.h:289: warning: `dummy5' might be used uninitialized in this function /usr/src/linux-2.4.16.SuSE/include/asm/unistd.h:290: warning: `dummy4' might be used uninitialized in this function /usr/src/linux-2.4.16.SuSE/include/asm/unistd.h:290: warning: `dummy5' might be used uninitialized in this function make: *** [init/main.o] Error 1

1 0

(e)lilo configuration
by Jan-Christoph Westermann 07 Feb '02

07 Feb '02

I am intending to compile a new kernel for SuSE 7.3, but want too keep the old one as a fall back option. Obviously /etc/lilo.conf or /etc/elilo.conf don't exist. Instead I found /boot/elilo.conf This File is similar to lilo.conf on 386 like systems, but when I add an entry for the new kernel, do I need to run lilo? /sbin/lilo or /sbin/elilo do not exist. Is this done by the efi-shell automatically? jan -- Jan-C. Westermann jwester(a)sgi1.chemie.uni-hamburg.de

2 1

Problems NIC and HP server
by Michael Heiming 05 Feb '02

05 Feb '02

Hello, having problems with HP rx4610 server and the built-in NIC, lspci reports it as: Intel Corporation 82557 Ethernet Pro 100 (rev 08) Using the eepro100.o module and the 2.4.4 SMP Kernel that came with SuSE 7.2/ia64, the network isn't working at all, until I switch the NIC to promiscuous mode, then a few packets will work in both directions and tcpdump crashes with SEGMENTATION fault. mii-tool reports the link would be fine, even if I needed to force the speed settings, which were 100HD, but the router (cisco catalyst) is set to 100FD, but it doesn't change the above behavior. I'll compile 2.4.17 and perhaps apply the ia64 patches from kernel.org soon or has someone other suggestions/expirience, he would like to share? Thx for your time Michael Heiming

2 4

REad - only file system immediately after installation
by rams＠poori.biochem.uiowa.edu 05 Feb '02

05 Feb '02

Hi All, I managed to install 7.2 on the i2000 Itanium. I never succeeded in booting the machine. I got in thro the single user mode. I can init 3 and get in too. But I cannot edit any file. Cannot configure the network, or do startx I get the error Read-only file system. What am I doing wrong? Thanks. Rams. -- S. Ramaswamy Department of Biochemistry. University of Iowa.

1 0