From maschino at jouy.inra.fr Mon Jan 2 10:47:18 2006 From: maschino at jouy.inra.fr (Emeric Maschino) Date: Mon, 02 Jan 2006 11:47:18 +0100 Subject: [Fedora-ia64-list] Still non-bootable kernel/mkinitrd? Message-ID: <1136198838.26641.31.camel@localhost.localdomain> Hi and Happy New Year! Since there's still no installation image in the current Fedora ia64 development tree (https://www.redhat.com/archives/fedora-ia64-list/2005- December/msg00000.html), I've installed as a starting point a minimal RHEL 4 Beta 2 (Nahant) distribution using the default settings on the second HDD of my hp workstation zx6000. I've then updated it to Fedora Core using yum update (SELinux disabled) and all packages were installed/updated and cleaned flawlessly. But now my system isn't bootable: the kernel (2.6.14-1.1806_FC5) fails to find the root LVM volume and crashes miserably. Following advice in https://www.redhat.com/archives/fedora-ia64- list/2005-August/msg00018.html, I've recompiled the 2.6.14-1.1806_FC5 kernel including SCSI support, SCSI disk support, MPT Fusion driver and device-mapper driver into the kernel. No luck. Is there anybody out there having a bootable Fedora Core installation using the standard kernel? It seems there hasn't been a lot of changes in this direction since my previous post dated September 2005 :-( Has something changed in the manner the partitions are created/named between RHEL 4 and Fedora Core that would mess the Fedora Core boot process in my situation? I don't know if my problem is related to https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169059. In order to check this, I need to recompile mkinitrd 4.2.21-1 but I can't find the mkinitrd-4.2.21-1.src.rpm source package anymore. Is it still available somewhere on Earth? Thanks, ?meric From maschino at jouy.inra.fr Mon Jan 2 11:09:29 2006 From: maschino at jouy.inra.fr (Emeric Maschino) Date: Mon, 02 Jan 2006 12:09:29 +0100 Subject: [Fedora-ia64-list] Still non-bootable kernel/mkinitrd? In-Reply-To: <1136198838.26641.31.camel@localhost.localdomain> References: <1136198838.26641.31.camel@localhost.localdomain> Message-ID: <1136200169.26641.37.camel@localhost.localdomain> > I don't know if my problem is related to > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169059. In order to > check this, I need to recompile mkinitrd 4.2.21-1 but I can't find the > mkinitrd-4.2.21-1.src.rpm source package anymore. Is it still available > somewhere on Earth? OK, I finally found this file on an old CD-ROM. Once recompiled, I'll try using this mkinitrd 4.2.21-1 rather than actual mkinitrd 5.0.15-1. Of course, I'll let you know the result. Have a nice day, ?meric From maschino at jouy.inra.fr Tue Jan 3 08:59:20 2006 From: maschino at jouy.inra.fr (Emeric Maschino) Date: Tue, 03 Jan 2006 09:59:20 +0100 Subject: [Fedora-ia64-list] Still non-bootable kernel/mkinitrd [SOLVED]? In-Reply-To: <1136200169.26641.37.camel@localhost.localdomain> References: <1136198838.26641.31.camel@localhost.localdomain> <1136200169.26641.37.camel@localhost.localdomain> Message-ID: <1136278760.5047.11.camel@localhost.localdomain> Hi, > OK, I finally found this file on an old CD-ROM. Once recompiled, I'll > try using this mkinitrd 4.2.21-1 rather than actual mkinitrd 5.0.15-1. > Of course, I'll let you know the result. I successfully recompiled mkinitrd-4.2.21-1src.rpm (just need to remove -Werror in the grubby subdir Makefile, otherwise it won't compile). I then installed it in place of mkinitrd-5.0.15-1 and created a new initrd. The system was bootable :-) I then upgraded mkinitrd to 5.0.15-1 again and created a new initrd. To my surprise, the system was still bootable using this new image. Perhaps mkinitrd 5.0.15-1 needed some bits of kernel 2.6.14-1.1806_FC5 but I initially can't boot with this kernel (due to the initrd problem) and must rely on a chroot environment. Well, all is fine now and new kernel 2.6.14-1.1807_FC5 installed and booted flawlessly. I now have to solve a few other problems (most notably SELinux-related) but I think separate threads are preferable. From maschino at jouy.inra.fr Thu Jan 5 18:39:29 2006 From: maschino at jouy.inra.fr (maschino at jouy.inra.fr) Date: Thu, 5 Jan 2006 19:39:29 +0100 Subject: [Fedora-ia64-list] Debug gnome-volume-manager Message-ID: <1136486369.43bd67e121c0a@www.jouy.inra.fr> Hi, I'm running up-to-date development ia64 Fedora Core (Rawhide) on my hp workstation zx6000. Each time I open a GNOME session, gnome-volume-manager crashes. I've followed the directives in http://fedora.linux.duke.edu/wiki/StackTraces in order to obtain a callstack. I've installed gnome-volume-manager-debuginfo and the debuginfo packages of all the libraries gnome-volume-manager is linked against (found with ldd /usr/bin/gnome-volume-manager). But gdb still outputs "No stack." when bt or thread apply all bt is invoked, as a user or as root. How can I obtain a callstack of gnome-volume-manager? Thanks for any input/suggestion, ?meric From maschino at jouy.inra.fr Tue Jan 10 10:46:57 2006 From: maschino at jouy.inra.fr (Emeric Maschino) Date: Tue, 10 Jan 2006 11:46:57 +0100 Subject: [Fedora-ia64-list] Report of successfull installation :-) Message-ID: <1136890017.5411.16.camel@localhost.localdomain> Hi, Just to let you know that I've successfully installed Fedora Core development IA-64 on the second HDD of my hp workstation zx6000 via network. Since no installation image is provided, here's how I did. You'll need an EFI partition and an other system or Linux installation in order to extract the needed bits: - grab the development/ia64/Fedora/RPMS/kernel package and extract the vmlinuz file to the EFI partition - grab the development/ia64/images/pxeboot/initrd.img and copy it to the EFI partition - copy the elilo.conf and elilo.efi from the RHEL 4 Beta 2 (Nahant) disc 1 (for example) to the EFI partition - run elilo.efi within the built-in EFI shell. At the ELILO prompt, just press enter to start the installation in graphical mode or enter linux text to perform the installation in text mode - follow the anaconda directives Note: The anaconda screens were a little garbaged on my workstation (sporting an ATI FireGL X1 display adapter). In graphical mode, some widgets were missing (like the Next and Back buttons; Alt+N is your friend as you'll operate blindly). Sometimes you only have the Fedora background image wondering what to do. Well, just hit Alt+N in this case! This implies that you'll blindly accept the default choices. Fortunately, the important steps (like disk partitioning, network settings, and so on are roughly readable). In text mode, the problem is similar, but at least you can choose which packages to install. I didn't find the right key combination to perform the same in graphical mode. When the installation is finished and the system reboots, disable SELinux by passing linux selinux=0 as arguments to the ELILO prompt. There's currently something wrong with mingetty that prevent you logging in in enforcing mode. Edit /etc/selinux/config to switch SELinux in permissive mode, touch /.autorelabel to fix the file contexts and reboot normally. You'll get a few additional SELinux denials but that's all (more in http://www.redhat.com/archives/fedora-selinux-list/2006- January/msg00049.html). On my system, I'm getting some graphical glitches with the modular X.org 7.0 RC4 r300 driver. If you have a different graphics adapter, please report how it works. Happy testing! ?meric From prarit at redhat.com Tue Jan 10 14:59:57 2006 From: prarit at redhat.com (Prarit Bhargava) Date: Tue, 10 Jan 2006 09:59:57 -0500 Subject: [Fedora-ia64-list] Report of successfull installation :-) In-Reply-To: <1136890017.5411.16.camel@localhost.localdomain> References: <1136890017.5411.16.camel@localhost.localdomain> Message-ID: <43C3CBED.3040508@redhat.com> Emeric Maschino wrote: > Hi, > > Just to let you know that I've successfully installed Fedora Core > development IA-64 on the second HDD of my hp workstation zx6000 via > network. Since no installation image is provided, here's how I did. > You'll need an EFI partition and an other system or Linux installation > in order to extract the needed bits: > - grab the development/ia64/Fedora/RPMS/kernel package and extract the > vmlinuz file to the EFI partition > - grab the development/ia64/images/pxeboot/initrd.img and copy it to the > EFI partition > - copy the elilo.conf and elilo.efi from the RHEL 4 Beta 2 (Nahant) disc > 1 (for example) to the EFI partition > - run elilo.efi within the built-in EFI shell. At the ELILO prompt, just > press enter to start the installation in graphical mode or enter linux > text to perform the installation in text mode > - follow the anaconda directives > FYI: I'm looking at why the boot.iso image is only 34k right now ... P. > From prarit at redhat.com Tue Jan 10 17:39:45 2006 From: prarit at redhat.com (Prarit Bhargava) Date: Tue, 10 Jan 2006 12:39:45 -0500 Subject: [Fedora-ia64-list] Report of successfull installation :-) In-Reply-To: <43C3CBED.3040508@redhat.com> References: <1136890017.5411.16.camel@localhost.localdomain> <43C3CBED.3040508@redhat.com> Message-ID: <43C3F161.7000501@redhat.com> >> > > FYI: > > I'm looking at why the boot.iso image is only 34k right now ... The bottom line here is that Fedora was/is moving away from a boot.img based boot iso -- however, EFI needs a dosfs (ie, the boot.img) ... I've asked Jeremy to plunk the code back in :) Hopefully we'll get that in the next couple of days. From maschino at jouy.inra.fr Wed Jan 11 15:53:13 2006 From: maschino at jouy.inra.fr (Emeric Maschino) Date: Wed, 11 Jan 2006 16:53:13 +0100 Subject: [Fedora-ia64-list] Debug gnome-volume-manager In-Reply-To: <1136486369.43bd67e121c0a@www.jouy.inra.fr> References: <1136486369.43bd67e121c0a@www.jouy.inra.fr> Message-ID: <1136994793.5094.25.camel@localhost.localdomain> > I'm running up-to-date development ia64 Fedora Core (Rawhide) on my hp > workstation zx6000. Each time I open a GNOME session, gnome-volume-manager > crashes. FYI, I don't know whether it's because I finally managed to perform a clean installation (https://www.redhat.com/archives/fedora-ia64- list/2006-January/msg00004.html) or because gnome-volume-manager has been updated, but there's no more crash. ?meric From maschino at jouy.inra.fr Mon Jan 16 23:31:20 2006 From: maschino at jouy.inra.fr (maschino at jouy.inra.fr) Date: Tue, 17 Jan 2006 00:31:20 +0100 Subject: [Fedora-ia64-list] GNOME broken! Message-ID: <1137454280.43cc2cc89eb04@www.jouy.inra.fr> Hi, The updates from January 14th broke GNOME. When starting a GNOME session, I can see the plain blue color background (that's below the Fedora Core image) and the cross mouse cursor for a few seconds and I'm back to the console. rhgb no more works, so it may be a general GTK2 problem (from the look'n feel, I think rhgb uses GTK2). I don't think the whole X Window system is affected since I can manually start X with /etc/X11/X :0 without a problem. Is there anybody out there experiencing the same problem? Cheers, ?meric From maschino at jouy.inra.fr Tue Jan 17 00:07:12 2006 From: maschino at jouy.inra.fr (maschino at jouy.inra.fr) Date: Tue, 17 Jan 2006 01:07:12 +0100 Subject: [Fedora-ia64-list] GNOME broken! In-Reply-To: <1137454280.43cc2cc89eb04@www.jouy.inra.fr> References: <1137454280.43cc2cc89eb04@www.jouy.inra.fr> Message-ID: <1137456432.43cc3530f1b81@www.jouy.inra.fr> > The updates from January 14th broke GNOME. When starting a GNOME session, I > can > see the plain blue color background (that's below the Fedora Core image) and > the cross mouse cursor for a few seconds and I'm back to the console. rhgb no > more works, so it may be a general GTK2 problem (from the look'n feel, I > think > rhgb uses GTK2). I don't think the whole X Window system is affected since I > can manually start X with /etc/X11/X :0 without a problem. OK, the faulty package is gtk2-2.8.10-2.ia64.rpm. Revert back to gtk2-2.8.9-1.1.ia64.rpm and GNOME and rhgb work again but gnome-volume-manager and the GNOME applets won't work. Just revert back to gnome-volume-manager-1.5.7-2.ia64.rpm and gnome-session-2.12.0-5.ia64.rpm and everything work normally. Should I file a bug? ?meric From prarit at redhat.com Tue Jan 17 00:59:39 2006 From: prarit at redhat.com (Prarit Bhargava) Date: Mon, 16 Jan 2006 19:59:39 -0500 Subject: [Fedora-ia64-list] GNOME broken! In-Reply-To: <1137456432.43cc3530f1b81@www.jouy.inra.fr> References: <1137454280.43cc2cc89eb04@www.jouy.inra.fr> <1137456432.43cc3530f1b81@www.jouy.inra.fr> Message-ID: <43CC417B.4090108@redhat.com> maschino at jouy.inra.fr wrote: >>The updates from January 14th broke GNOME. When starting a GNOME session, I >>can >>see the plain blue color background (that's below the Fedora Core image) and >>the cross mouse cursor for a few seconds and I'm back to the console. rhgb no >>more works, so it may be a general GTK2 problem (from the look'n feel, I >>think >>rhgb uses GTK2). I don't think the whole X Window system is affected since I >>can manually start X with /etc/X11/X :0 without a problem. > > > OK, the faulty package is gtk2-2.8.10-2.ia64.rpm. Revert back to > gtk2-2.8.9-1.1.ia64.rpm and GNOME and rhgb work again but gnome-volume-manager > and the GNOME applets won't work. Just revert back to > gnome-volume-manager-1.5.7-2.ia64.rpm and gnome-session-2.12.0-5.ia64.rpm and > everything work normally. > > Should I file a bug? > Yes, please do. P. > ?meric > > -- > Fedora-ia64-list mailing list > Fedora-ia64-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-ia64-list > From maschino at jouy.inra.fr Tue Jan 17 09:33:49 2006 From: maschino at jouy.inra.fr (Emeric Maschino) Date: Tue, 17 Jan 2006 10:33:49 +0100 Subject: [Fedora-ia64-list] GNOME broken! In-Reply-To: <43CC417B.4090108@redhat.com> References: <1137454280.43cc2cc89eb04@www.jouy.inra.fr> <1137456432.43cc3530f1b81@www.jouy.inra.fr> <43CC417B.4090108@redhat.com> Message-ID: <1137490430.31870.21.camel@localhost.localdomain> > > OK, the faulty package is gtk2-2.8.10-2.ia64.rpm. Revert back to > > gtk2-2.8.9-1.1.ia64.rpm and GNOME and rhgb work again but gnome-volume-manager > > and the GNOME applets won't work. Just revert back to > > gnome-volume-manager-1.5.7-2.ia64.rpm and gnome-session-2.12.0-5.ia64.rpm and > > everything work normally. > > > > Should I file a bug? > > > > Yes, please do. OK, sent. See bug #178005. ?meric From igs at e-iei.com Fri Jan 20 08:35:35 2006 From: igs at e-iei.com (DELIA HU) Date: Fri, 20 Jan 2006 16:35:35 +0800 Subject: [Fedora-ia64-list] IEI/IGS New Product Phase-In Notice : IBOX-650 Message-ID: <46be01c61d9c$7b8cda50$130210ac@ieinet.org> New Product Notice: IBOX-650 Dear Valuable Partner, New product phase-in notice : Embedded Fan-less Intel ULV Celeron 650 MHz Server Box IBOX-650 is Embedded Fan-less Intel ULV Celeron 650 MHz Server box providing industrial computing solutions for the most demanding applications. IBOX-650 advanced features including Intel Ultra Low Voltage Celeron 650 MHz processors, maximum 1GB of DDR333 memory, 2.5" IDE hard drives,compact flash slot and flexible I/O Main Features: Ultra low voltage Intel Celeron 650 MHz processor with high performance Fan-less design keeps high reliability for long time application The simple structure is to save maintenance expense External power adapter decreases thermal concerning IBOX-650 CPU Intel ULV Celeron 650 MHz ( L2-256k ) Core Logic VIA CLE 266 System Memory 1 x DDR266/333 up to 1GB IDE port 1 x 44pin with 2.54 pitch, for 2.5" HDD or DOM Compact Flash slot 1 x Type II Compact Flash up to 1GB Serial 3 x COM( 2x RS232, 1x RJ45 w/ DC +5V or +12V ) Parallel 1 x ECP/EPP/SPP USB 5 x USB 2.0 PS2 Mouse 1 PS2 Keyboard 1 LAN 1 x RJ45, 10/100 Base-T D I/O 1 x RJ11 Audio Jack 1 x Audio Out Audio AC97 2.0 Compliant VGA 1 x D-SUB15 SCSI Port LVDS Display + Touch COM Power Supply Ext. AC Adapter 12V DC, 6.5 A, 80W Max EMI/EMC FCC / CE Class B Weight Approx. 2.4 Kgs Dimension 190(W) x 180(L) x 68(H) mm Operating Temp. 0 to 50?C For further information, please visit our website: www.ieiworld.com.tw I don't want to recevie this news again -------------- next part -------------- An HTML attachment was scrubbed... URL: From prarit at redhat.com Tue Jan 24 17:37:58 2006 From: prarit at redhat.com (Prarit Bhargava) Date: Tue, 24 Jan 2006 12:37:58 -0500 Subject: [Fedora-ia64-list] [PATCH BZ:175632]: ia64: EFI requires boot.img Message-ID: <43D665F6.1070202@redhat.com> This patch re-introduces the creation of the boot.img file for use by EFI. Without this patch, EFI booting is non-functional in recent nightly builds. P. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: anaconda.patch URL: