Anaconda-devel May 2006

anaconda-devel@lists.fedoraproject.org

40 participants
57 discussions

Start a nNew thread

RE: Serial console install - text is getting munged
by Oden, James 06 May '06

06 May '06

Looks like your terminal server needs to be set to a better term type (vt* I think works fine...james

4 4

Few noobie questions
by Philip Prindeville 05 May '06

05 May '06

Hi. Sorry if this is a common question, but I was wondering what the current documentation on making Kickstart installer stuff for (for example) FC5 would be. I've looked around on the net, and a lot of the documentation still refers to the initrd.img as being an "ext2" filesystem and not a cpio archive. Even the details of what kind of archive (an newc one compressed with -9) aren't always obvious. I have a hand-generated ks.cfg file (it wasn't clear either if that goes in the DVD root or in the isolinux/ directory) that seems to be causing heartburn for the install, as well... but I can't tell where exactly. Lastly, is there a way to get debugging/tracing information when trying out DVD's so you can figure out where things are crapping out? There may be various things failing (like detecting the panel on a laptop when I specify 1400x1050 resolution, etc) but I have no way of knowing... I'm writing some scripts, which I'll be happy to post when they're working more reliably. Thanks, -Philip

1 0

Serial console install - text is getting munged
by Josh Martinek 05 May '06

05 May '06

I'm doing a serial console install on Fedora Core 5 and the text is getting munged. Has anyone else seen this, or know what the problem might be? My console settings in my terminal program, are COM1, 38400 8n1 , Flow control = hardware. I have tried turning the flow control off, and using different baud rates but that didn't help. This is the contents of my isolinux.cfg file: serial 0 38400 default ks prompt 1 timeout 300 display boot.msg label ks kernel vmlinuz append ks=cdrom:/ks.cfg initrd=initrd.img console=ttyS0,38400 The output on the serial console looks like this: Welcome to Fedora Core â"Œâ"€â"€â"€â"€â"€â"€â"€â"€â"€â"€â"€â"€â"€â"€â"¤ CD Found â"œ â"€â"€â"€â"€â"€â"€ââ"‚ â"‚ â"‚ To begin testing the CD media before â"‚ â"‚ installation press OK. â"‚ â"‚ â"‚ ver â"œâ"€â"€â "€â"€â"€â"€â"€â"€â"â"‚ Choose Skip to skip the media test â"‚ â"‚ and start the installation. â"‚ â"‚ â"‚ â"‚ â"Œâ"€â"€â"€â"€â" â"Œâ"€â"€â"€â"€â"€â"€ â" â"‚ â"€â"â"‚ â"‚ OK â"‚ â"‚ Skip â"‚ â"‚ â"‚ â""â"€â"€â"€â"€â"˜ â""â"€â"€â"€â"€â"€â"€ â"˜ â"‚ â"‚ â"‚ â"‚ â"‚ â""â"€â"€â"€â"€â"€â"€â"€â"€â"€â"€â"€â"€â"€â"€â"€â"€â"€â"€â"€â "€â"€â"€â"€â"€â"€â"€ Josh kidmartinek gmail com

2 1

Sequence of file is loaded
by Bin Doremon 05 May '06

05 May '06

Hi all, When we insert CD1 to CD-ROM drive to install Redhat Linux (boot from CD-ROM), some files are loaded to install OS. I want to know the sequence of file is loaded. Please help me, thank you! --------------------------------- New Yahoo! Messenger with Voice. Call regular phones from your PC and save big.

2 1

anaconda: warning building loader: static linking and getpwnam
by Steven Augart 05 May '06

05 May '06

I built anaconda by hand, using the CVS sources, in an attempt to track down my installation CD's /sbin/loader crash. In doing the build, I got a warning about using "getpwuid" in statically linked applications: ==== begin quoted build output cc -g -static -o loader loader.o log.o moduleinfo.o loadermisc.o modules.o moduledeps.o windows.o lang.o kbd.o modstubs.o driverdisk.o selinux.o md5.o mediacheck.o kickstart.o driverselect.o getparts.o dirbrowser.o pcmcia.o usb.o firewire.o hardware.o method.o cdinstall.o hdinstall.o nfsinstall.o urlinstall.o net.o urls.o ftp.o telnet.o telnetd.o -lpopt \ -lkudzu_loader -lpci ../isys/libisys.a -lz ../stubs/libunicode-lite.a \ -lpump -lresolv -lnewt -lslang -ldevmapper -lselinux -lsepol ftp.o: In function `ftpOpen': /home/saugart/boot-CD/Anaconda-CVS/anaconda/loader2/ftp.c:244: warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking ==== end quoted build output Is this a known problem with Anaconda? Is it benign, or might it be one of the reasons why /sbin/loader is crashing in the middle of my installation? (Since I'm not using the FTP functionality, so getpwuid() is never called, it does seem unlikely, but I might as well check.) I'm using an up-to-date FC5, with glibc-2.4-4, gcc-4.1.0-3, binutils-2.16.91.0.6-5, and kernel-2.6.16-1.2096_FC5. It seems to me that, in general, it is good if we can have our code build without linker warnings, and if there is a good reason why the warning is benign but necessary, then I think we might want to put it in a README file in the root directory of the source tree. I'm glad to write up such a README and contribute it to the project. Thanks, Steven Augart Mazu Networks Cambridge, Massachusetts, USA

1 0

FC 5 Costumization
by Fabricio Lopes de Souza 05 May '06

05 May '06

Hi all , Anyone can tell me the minimall packages to build a customized FC5 ?? thanks :)

3 2

How to debug crashes in /sbin/loader?
by Steven Augart 04 May '06

04 May '06

Dear Anaconda Developers, A colleague and I have been building an install CD based on FC5. Unfortunately, when we boot into the install CD, which is a trivial tweak on the same set of RPM packages and kickstart file that works on FC4, we get a crash in /sbin/loader, during the first stage of the installation process, after the kernel itself has started up. I'm glad to help improve Anaconda and /sbin/loader by debugging the problem. However, I would very much appreciate advice from anyone who has actually debugged /sbin/loader. This error is happening early in the boot process, after the kernel is up but before any shells have been launched in other windows. Oddly enough, my colleague has been successfully distributing a very similar installation CD that's based on FC 4. But we'd prefer to base the installation on FC 5. (We're upgrading the whole system from RH 9.) We're glad to put time into debugging the problem -- all we need is some advice about a good approach for making /sbin/loader run under GDB, or whatever other debugging approach someone with experience doing this could recommend. Our best guess so far is that there's been a minor Kickstart syntax change between FC 4 and FC 5, and perhaps our Kickstart files have a minor syntax error that's triggering the crash, but we haven't found any evidence to support that. We're glad to contribute back to Anaconda as a token of our appreciation for the great tool which you and others have collaborated to give us. Sincerely Yours, Steven Augart Mazu Networks, Cambridge, Massachusetts, USA

2 1

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Anaconda-devel May 2006