Re: 43p-140 install issues

Re: 43p-140 install issues

[Sven Luther]

On Wed, Dec 29, 2004 at 01:51:51PM -0500, Mike Martin wrote:
> I have a 43p-140, It will netboot, start the installer and let be run
> through the motions. It doesn't seem to be able to recognize the cdrom
> or be able to set up the network. This puts a stop on the installation
> pretty quickly. I can't seem to figure it out on my own. Can anyone
> help?
> 
> Attached is a console capture from my latest boot using the Dec. 28th
> image from:
> http://people.debian.org/~luther/debian-installer/daily-powerpc-built/daily/powerpc/netboot/
> 
> Other images are similar.

Could you try to get the /var/log/syslog and /var/log/messages out of that box
? 

> When the installer gets to configuring the network with DHCP, it
> fails. "tcpdump" on the server interface shows no traffic after the
> tftp image is transfered.

Mmm, could this be similar to : 

  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=283329

I am trying the install on a motorola powerstack (utah board), which has a
decchip (de4x5) ethernet, and things are worse, the machine freezes when
trying to ifup the interface :

  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=287933

I get some strange feeling that something is seriously wrong with the 2.6
kernels on prep hardware. Let me CC this to linuxppc-dev mailing lists too. 

I will not have time to look into this problem before next year though :), and
probably not before a week or so at that.

Friendly,

Sven Luther

Re: 43p-140 install issues

[Mike Martin]

[-- Attachment #1: Type: text/plain, Size: 2081 bytes --]

(re-sending for the benefit of those on the lists .. sorry Sven)

Would there be any image I can use to install this machine currently?
Here's my situation, If I can get the machine to boot and install by
next week (back to work) my boss will let me keep working on it -
otherwise he'll declare it useless and it'll go back in the closet. If
I can get anything on it I'm ok - It doesn't need to be 2.6.

Attached is /var/log/syslog and /var/log/messages.


Mike Martin



On Fri, 31 Dec 2004 10:53:10 +0100, Sven Luther <sven.luther@wanadoo.fr> wrote:
> On Wed, Dec 29, 2004 at 01:51:51PM -0500, Mike Martin wrote:
> > I have a 43p-140, It will netboot, start the installer and let be run
> > through the motions. It doesn't seem to be able to recognize the cdrom
> > or be able to set up the network. This puts a stop on the installation
> > pretty quickly. I can't seem to figure it out on my own. Can anyone
> > help?
> >
> > Attached is a console capture from my latest boot using the Dec. 28th
> > image from:
> > http://people.debian.org/~luther/debian-installer/daily-powerpc-built/daily/powerpc/netboot/
> >
> > Other images are similar.
> 
> Could you try to get the /var/log/syslog and /var/log/messages out of that box
> ?
> 
> > When the installer gets to configuring the network with DHCP, it
> > fails. "tcpdump" on the server interface shows no traffic after the
> > tftp image is transfered.
> 
> Mmm, could this be similar to :
> 
>   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=283329
> 
> I am trying the install on a motorola powerstack (utah board), which has a
> decchip (de4x5) ethernet, and things are worse, the machine freezes when
> trying to ifup the interface :
> 
>   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=287933
> 
> I get some strange feeling that something is seriously wrong with the 2.6
> kernels on prep hardware. Let me CC this to linuxppc-dev mailing lists too.
> 
> I will not have time to look into this problem before next year though :), and
> probably not before a week or so at that.
> 
> Friendly,
> 
> Sven Luther
> 
>

[-- Attachment #2: 43plogs.txt --]
[-- Type: text/plain, Size: 39243 bytes --]


~ # cat /var/log/syslog
Dec 31 16:11:07 syslogd started: BusyBox v1.00-pre10 (Debian 20040623-1)
Dec 31 16:11:07 kernel: klogd started: BusyBox v1.00-pre10 (Debian 20040623-1)
Dec 31 16:11:07 kernel: Total memory = 256MB; using 512kB for hash table (at c0300000)
Dec 31 16:11:07 kernel: Linux version 2.6.8-powerpc (sven@pegasos2) (version gcc 3.3.5 (Debian 1:3.3.5-2)) #1 Thu Dec 9 10:27:54 CET 2004
Dec 31 16:11:07 kernel: PReP architecture
Dec 31 16:11:07 kernel: IBM planar ID: 000000d5
Dec 31 16:11:07 kernel: MPIC at 0xfddc0000 (0x3ddc0000), length 0x00040000 mapped to 0xeffc0000
Dec 31 16:11:07 kernel: On node 0 totalpages: 65536
Dec 31 16:11:07 kernel:   DMA zone: 65536 pages, LIFO batch:16
Dec 31 16:11:07 kernel:   Normal zone: 0 pages, LIFO batch:1
Dec 31 16:11:07 kernel:   HighMem zone: 0 pages, LIFO batch:1
Dec 31 16:11:07 kernel: Built 1 zonelists
Dec 31 16:11:07 kernel: Kernel command line: console=ttyS0,9600 root=/dev/ram
Dec 31 16:11:07 kernel: OpenPIC Version 1.0 (4 CPUs and 16 IRQ sources) at effc0000
Dec 31 16:11:07 kernel: PID hash table entries: 2048 (order 11: 16384 bytes)
Dec 31 16:11:07 kernel: time_init: decrementer frequency = 16.617869 MHz
Dec 31 16:11:07 kernel: Console: colour dummy device 80x25
Dec 31 16:11:07 kernel: Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Dec 31 16:11:07 kernel: Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Dec 31 16:11:07 kernel: Memory: 251712k available (1732k kernel code, 1060k data, 164k init, 0k highmem)
Dec 31 16:11:07 kernel: Calibrating delay loop... 330.75 BogoMIPS
Dec 31 16:11:07 kernel: Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Dec 31 16:11:07 kernel: checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Dec 31 16:11:07 kernel: Freeing initrd memory: 4098k freed
Dec 31 16:11:07 kernel: NET: Registered protocol family 16
Dec 31 16:11:07 kernel: PCI: Probing PCI hardware
Dec 31 16:11:07 kernel: Setting PCI interrupts for a "IBM 43P-140 (Tiger1)"
Dec 31 16:11:07 kernel: PCI: Cannot allocate resource region 0 of PCI bridge 1
Dec 31 16:11:07 kernel: PCI: bridge 1 resource 0 moved to 7ff000..7fffff
Dec 31 16:11:07 kernel: PCI: Cannot allocate resource region 0 of device 0000:00:0b.0
Dec 31 16:11:07 kernel: PCI: Cannot allocate resource region 0 of device 0000:00:0c.0
Dec 31 16:11:07 kernel: PCI: Cannot allocate resource region 0 of device 0000:00:10.0
Dec 31 16:11:07 kernel: PCI: Cannot allocate resource region 0 of device 0000:00:12.0
Dec 31 16:11:07 kernel: PCI: Cannot allocate resource region 0 of device 0000:01:03.0
Dec 31 16:11:07 kernel: Registering openpic with sysfs...
Dec 31 16:11:07 kernel: Thermal assist unit not available
Dec 31 16:11:07 kernel: audit: initializing netlink socket (disabled)
Dec 31 16:11:07 kernel: audit(1104509463.578:0): initialized
Dec 31 16:11:07 kernel: devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
Dec 31 16:11:07 kernel: devfs: boot_options: 0x0
Dec 31 16:11:07 kernel: Initializing Cryptographic API
Dec 31 16:11:07 kernel: Generic RTC Driver v1.07
Dec 31 16:11:07 kernel: Macintosh non-volatile memory driver v1.1
Dec 31 16:11:07 kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
Dec 31 16:11:07 kernel: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Dec 31 16:11:07 kernel: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Dec 31 16:11:07 kernel: pmac_zilog: 0.6 (Benjamin Herrenschmidt <benh@kernel.crashing.org>)
Dec 31 16:11:07 kernel: RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
Dec 31 16:11:07 kernel: divert: not allocating divert_blk for non-ethernet device lo
Dec 31 16:11:07 kernel: input: Macintosh mouse button emulation
Dec 31 16:11:07 kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
Dec 31 16:11:07 kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Dec 31 16:11:07 kernel: mice: PS/2 mouse device common for all mice
Dec 31 16:11:07 kernel: NET: Registered protocol family 2
Dec 31 16:11:07 kernel: IP: routing cache hash table of 2048 buckets, 16Kbytes
Dec 31 16:11:07 kernel: TCP: Hash tables configured (established 16384 bind 32768)
Dec 31 16:11:07 kernel: RAMDISK: Compressed image found at block 0
Dec 31 16:11:07 kernel: VFS: Mounted root (cramfs filesystem) readonly.
Dec 31 16:11:07 kernel: Freeing unused kernel memory: 164k init 60k pmac 4k chrp 8k openfirmware
Dec 31 16:11:07 kernel: NET: Registered protocol family 1
Dec 31 16:11:10 kernel: usbcore: registered new driver usbfs
Dec 31 16:11:10 kernel: usbcore: registered new driver hub
Dec 31 16:11:10 kernel: usbcore: registered new driver hiddev
Dec 31 16:11:10 kernel: usbcore: registered new driver usbhid
Dec 31 16:11:10 kernel: drivers/usb/input/hid-core.c: v2.0:USB HID core driver
Dec 31 16:11:10 kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for Generic
Dec 31 16:11:10 kernel: usbcore: registered new driver usbserial_generic
Dec 31 16:11:10 kernel: usbcore: registered new driver usbserial
Dec 31 16:11:10 kernel: drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0
Dec 31 16:11:13 preseed: successfully loaded preseed file from /preseed.cfg
Dec 31 16:11:13 kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Dec 31 16:11:13 kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Dec 31 16:11:14 kernel: atkbd.c: keyboard reset failed on isa0060/serio1
Dec 31 16:11:14 kernel: atkbd.c: keyboard reset failed on isa0060/serio0
Dec 31 16:11:14 init: ^MStarting pid 418, console /dev/tts/0: '/sbin/debian-installer'
Dec 31 16:11:14 init: ^MStarting pid 422, console /dev/vc/3: '/usr/bin/tail'
Dec 31 16:11:14 init: ^MStarting pid 424, console /dev/vc/4: '/usr/bin/tail'
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (libc6): package doesn't exist (ignored) 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (libdebian-installer4): search, dependency from cdebconf-udeb 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (libdebian-installer4-udeb): mark, dependency from cdebconf-udeb 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (libtextwrap1): package doesn't exist (ignored) 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (cdebconf-udeb): mark, dependency from languagechooser 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (languagechooser): mark 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (iso-3166-udeb): mark, dependency from countrychooser 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (countrychooser): mark 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (libdebconfclient0): search, dependency from kbd-chooser 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (libdebconfclient0-udeb): mark, dependency from kbd-chooser 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (console-keymaps): search, dependency from kbd-chooser 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (console-keymaps-usb): mark, dependency from kbd-chooser 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (archdetect): mark, dependency from kbd-chooser 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (kbd-chooser): mark 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (discover): search, dependency from hw-detect 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (libdiscover1): package doesn't exist (ignored) 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (discover1-data-udeb): mark, dependency from discover1-udeb 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (discover1-udeb): mark, dependency from hw-detect 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (rootskel): mark, dependency from hw-detect 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (hw-detect): mark, dependency from ethdetect 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (ethdetect): mark 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (libiw27): search, dependency from netcfg 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (libiw27-udeb): mark, dependency from netcfg 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (dhcp-client-udeb): mark, dependency from netcfg 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (ethernet-card-detection): search, dependency from netcfg 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (netcfg): mark 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (configured-network): search, dependency from network-preseed 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (di-utils): mark, dependency from network-preseed 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (network-preseed): mark 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (choose-mirror): mark 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (net-retriever): mark, dependency from download-installer 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (anna): mark, dependency from download-installer 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (download-installer): mark 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (di-utils-shell): mark 
Dec 31 16:11:17 main-menu[449]: DEBUG: resolver (di-utils-reboot): mark 
Dec 31 16:11:17 main-menu[449]: DEBUG: Menu item 'languagechooser' selected 
Dec 31 16:11:17 main-menu[449]: DEBUG: configure languagechooser, status: 2  
Dec 31 16:11:17 main-menu[449]: DEBUG: configure cdebconf-udeb, status: 2  
Dec 31 16:11:17 main-menu[449]: DEBUG: configure libc6, status: 0  
Dec 31 16:11:17 main-menu[449]: DEBUG: configure libdebian-installer4, status: 0  
Dec 31 16:11:17 main-menu[449]: DEBUG: virtual package libdebian-installer4  
Dec 31 16:11:17 main-menu[449]: INFO: Falling back to the package description for libdebian-installer4-udeb 
Dec 31 16:11:17 main-menu[449]: INFO: Falling back to the package description for libdebian-installer4-udeb 
Dec 31 16:11:17 main-menu[449]: DEBUG: configure libdebian-installer4-udeb, status: 2  
Dec 31 16:11:17 main-menu[449]: DEBUG: configure libc6, status: 0  
Dec 31 16:11:17 main-menu[449]: DEBUG: configure libtextwrap1, status: 0  
Dec 31 16:11:17 debconf: Setting debconf/language to C
Dec 31 16:11:28 debconf: Setting debconf/language to en_US:en_GB:en
Dec 31 16:11:28 languagechooser: info: Asking for language specific packages to be Installed.
Dec 31 16:11:28 languagechooser: info: debian-installer/locale   = 'en'
Dec 31 16:11:28 languagechooser: info: debian-installer/fallbacklocale   = 'en_US@euro'
Dec 31 16:11:28 languagechooser: info: languagechooser/locale   = 'en'
Dec 31 16:11:28 languagechooser: info: debian-installer/language = 'en_US:en_GB:en'
Dec 31 16:11:28 languagechooser: info: debian-installer/country  = 'US'
Dec 31 16:11:28 languagechooser: info: debian-installer/consoledisplay  = 'kbd=lat0-sun16(iso15)'
Dec 31 16:11:28 main-menu[449]: INFO: Priority changed externally, setting main-menu default to 'high' (high) 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (libc6): package doesn't exist (ignored) 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (libdebian-installer4): search, dependency from cdebconf-udeb 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (libdebian-installer4-udeb): mark, dependency from cdebconf-udeb 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (libtextwrap1): package doesn't exist (ignored) 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (cdebconf-udeb): mark, dependency from languagechooser 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (languagechooser): mark 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (iso-3166-udeb): mark, dependency from countrychooser 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (countrychooser): mark 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (libdebconfclient0): search, dependency from kbd-chooser 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (libdebconfclient0-udeb): mark, dependency from kbd-chooser 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (console-keymaps): search, dependency from kbd-chooser 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (console-keymaps-usb): mark, dependency from kbd-chooser 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (archdetect): mark, dependency from kbd-chooser 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (kbd-chooser): mark 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (discover): search, dependency from hw-detect 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (libdiscover1): package doesn't exist (ignored) 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (discover1-data-udeb): mark, dependency from discover1-udeb 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (discover1-udeb): mark, dependency from hw-detect 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (rootskel): mark, dependency from hw-detect 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (hw-detect): mark, dependency from ethdetect 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (ethdetect): mark 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (libiw27): search, dependency from netcfg 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (libiw27-udeb): mark, dependency from netcfg 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (dhcp-client-udeb): mark, dependency from netcfg 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (ethernet-card-detection): search, dependency from netcfg 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (netcfg): mark 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (configured-network): search, dependency from network-preseed 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (di-utils): mark, dependency from network-preseed 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (network-preseed): mark 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (choose-mirror): mark 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (net-retriever): mark, dependency from download-installer 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (anna): mark, dependency from download-installer 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (download-installer): mark 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (di-utils-shell): mark 
Dec 31 16:11:29 main-menu[449]: DEBUG: resolver (di-utils-reboot): mark 
Dec 31 16:11:29 main-menu[449]: DEBUG: Menu item 'countrychooser' selected 
Dec 31 16:11:29 main-menu[449]: DEBUG: configure countrychooser, status: 2  
Dec 31 16:11:29 main-menu[449]: DEBUG: configure iso-3166-udeb, status: 2  
Dec 31 16:11:29 countrychooser: info: LANGUAGECODE_LANGUAGECHOOSER = 'en'
Dec 31 16:11:29 countrychooser: info: COUNTRYCODE_LANGUAGECHOOSER = 'US'
Dec 31 16:11:29 countrychooser: info: LOCALE_LANGUAGECHOOSER = 'en'
Dec 31 16:11:29 countrychooser: info: FALLBACKLOCALE = 'en_US@euro'
Dec 31 16:11:38 countrychooser: info: Set debian-installer/country = 'CA'
Dec 31 16:11:38 countrychooser: info: LANGUAGE = 'en'
Dec 31 16:11:38 countrychooser: info: COUNTRYCODE = 'CA'
Dec 31 16:11:39 countrychooser: info: Set debian-installer/locale = 'en_CA'
Dec 31 16:11:39 countrychooser: info: Set debian-installer/language = 'en_CA:en_US:en_GB:en'
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (libc6): package doesn't exist (ignored) 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (libdebian-installer4): search, dependency from cdebconf-udeb 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (libdebian-installer4-udeb): mark, dependency from cdebconf-udeb 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (libtextwrap1): package doesn't exist (ignored) 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (cdebconf-udeb): mark, dependency from languagechooser 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (languagechooser): mark 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (iso-3166-udeb): mark, dependency from countrychooser 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (countrychooser): mark 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (libdebconfclient0): search, dependency from kbd-chooser 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (libdebconfclient0-udeb): mark, dependency from kbd-chooser 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (console-keymaps): search, dependency from kbd-chooser 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (console-keymaps-usb): mark, dependency from kbd-chooser 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (archdetect): mark, dependency from kbd-chooser 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (kbd-chooser): mark 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (discover): search, dependency from hw-detect 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (libdiscover1): package doesn't exist (ignored) 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (discover1-data-udeb): mark, dependency from discover1-udeb 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (discover1-udeb): mark, dependency from hw-detect 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (rootskel): mark, dependency from hw-detect 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (hw-detect): mark, dependency from ethdetect 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (ethdetect): mark 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (libiw27): search, dependency from netcfg 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (libiw27-udeb): mark, dependency from netcfg 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (dhcp-client-udeb): mark, dependency from netcfg 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (ethernet-card-detection): search, dependency from netcfg 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (netcfg): mark 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (configured-network): search, dependency from network-preseed 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (di-utils): mark, dependency from network-preseed 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (network-preseed): mark 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (choose-mirror): mark 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (net-retriever): mark, dependency from download-installer 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (anna): mark, dependency from download-installer 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (download-installer): mark 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (di-utils-shell): mark 
Dec 31 16:11:39 main-menu[449]: DEBUG: resolver (di-utils-reboot): mark 
Dec 31 16:11:39 main-menu[449]: DEBUG: Menu item 'kbd-chooser' selected 
Dec 31 16:11:39 main-menu[449]: DEBUG: configure kbd-chooser, status: 2  
Dec 31 16:11:39 main-menu[449]: DEBUG: configure libc6, status: 0  
Dec 31 16:11:39 main-menu[449]: DEBUG: configure libdebconfclient0, status: 0  
Dec 31 16:11:39 main-menu[449]: DEBUG: virtual package libdebconfclient0  
Dec 31 16:11:39 main-menu[449]: INFO: Falling back to the package description for libdebconfclient0-udeb 
Dec 31 16:11:39 main-menu[449]: INFO: Falling back to the package description for libdebconfclient0-udeb 
Dec 31 16:11:39 main-menu[449]: DEBUG: configure libdebconfclient0-udeb, status: 2  
Dec 31 16:11:39 main-menu[449]: DEBUG: configure libc6, status: 0  
Dec 31 16:11:39 main-menu[449]: DEBUG: configure libdebian-installer4, status: 0  
Dec 31 16:11:39 main-menu[449]: DEBUG: virtual package libdebian-installer4  
Dec 31 16:11:39 main-menu[449]: DEBUG: configure console-keymaps, status: 0  
Dec 31 16:11:39 main-menu[449]: DEBUG: virtual package console-keymaps  
Dec 31 16:11:39 main-menu[449]: INFO: Falling back to the package description for console-keymaps-usb 
Dec 31 16:11:39 main-menu[449]: INFO: Falling back to the package description for console-keymaps-at 
Dec 31 16:11:39 main-menu[449]: INFO: Falling back to the package description for console-keymaps-usb 
Dec 31 16:11:39 main-menu[449]: DEBUG: configure console-keymaps-usb, status: 2  
Dec 31 16:11:39 main-menu[449]: INFO: Falling back to the package description for console-keymaps-at 
Dec 31 16:11:39 main-menu[449]: DEBUG: configure console-keymaps-at, status: 2  
Dec 31 16:11:39 main-menu[449]: DEBUG: configure archdetect, status: 2  
Dec 31 16:11:39 kbd-chooser[611]: INFO: Setting debian-installer/serial-console to true 
Dec 31 16:11:39 kbd-chooser[611]: DEBUG: Mounting usbdevfs to look for kbd  
Dec 31 16:11:39 kbd-chooser[611]: DEBUG: Failed to open /proc/bus/usb/devices: 2  
Dec 31 16:11:39 kbd-chooser[611]: DEBUG: Adding generic entry for USB keymaps  
Dec 31 16:11:39 kbd-chooser[611]: INFO: keyboard type at: present: false   
Dec 31 16:11:39 kbd-chooser[611]: INFO: keyboard type usb: present: unknown    
Dec 31 16:11:39 kbd-chooser[611]: INFO: Setting debian-installer/serial-console to true 
Dec 31 16:11:39 kbd-chooser[611]: INFO: Setting debian-installer/uml-console to false 
Dec 31 16:11:39 kbd-chooser[611]: INFO: kbd-chooser: not setting keymap (kbd == none selected) 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (libc6): package doesn't exist (ignored) 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (libdebian-installer4): search, dependency from cdebconf-udeb 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (libdebian-installer4-udeb): mark, dependency from cdebconf-udeb 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (libtextwrap1): package doesn't exist (ignored) 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (cdebconf-udeb): mark, dependency from languagechooser 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (languagechooser): mark 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (iso-3166-udeb): mark, dependency from countrychooser 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (countrychooser): mark 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (libdebconfclient0): search, dependency from kbd-chooser 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (libdebconfclient0-udeb): mark, dependency from kbd-chooser 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (console-keymaps): search, dependency from kbd-chooser 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (console-keymaps-usb): mark, dependency from kbd-chooser 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (archdetect): mark, dependency from kbd-chooser 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (kbd-chooser): mark 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (discover): search, dependency from hw-detect 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (libdiscover1): package doesn't exist (ignored) 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (discover1-data-udeb): mark, dependency from discover1-udeb 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (discover1-udeb): mark, dependency from hw-detect 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (rootskel): mark, dependency from hw-detect 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (hw-detect): mark, dependency from ethdetect 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (ethdetect): mark 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (libiw27): search, dependency from netcfg 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (libiw27-udeb): mark, dependency from netcfg 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (dhcp-client-udeb): mark, dependency from netcfg 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (ethernet-card-detection): search, dependency from netcfg 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (netcfg): mark 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (configured-network): search, dependency from network-preseed 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (di-utils): mark, dependency from network-preseed 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (network-preseed): mark 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (choose-mirror): mark 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (net-retriever): mark, dependency from download-installer 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (anna): mark, dependency from download-installer 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (download-installer): mark 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (di-utils-shell): mark 
Dec 31 16:11:40 main-menu[449]: DEBUG: resolver (di-utils-reboot): mark 
Dec 31 16:11:40 main-menu[449]: DEBUG: Menu item 'ethdetect' selected 
Dec 31 16:11:40 main-menu[449]: DEBUG: configure ethdetect, status: 2  
Dec 31 16:11:40 main-menu[449]: DEBUG: configure hw-detect, status: 2  
Dec 31 16:11:40 main-menu[449]: DEBUG: configure discover, status: 0  
Dec 31 16:11:40 main-menu[449]: DEBUG: virtual package discover  
Dec 31 16:11:40 main-menu[449]: INFO: Falling back to the package description for discover1-udeb 
Dec 31 16:11:40 main-menu[449]: INFO: Falling back to the package description for discover1-udeb 
Dec 31 16:11:40 main-menu[449]: DEBUG: configure discover1-udeb, status: 2  
Dec 31 16:11:40 main-menu[449]: DEBUG: configure libc6, status: 0  
Dec 31 16:11:40 main-menu[449]: DEBUG: configure libdiscover1, status: 0  
Dec 31 16:11:40 main-menu[449]: DEBUG: configure discover1-data-udeb, status: 2  
Dec 31 16:11:40 main-menu[449]: DEBUG: configure rootskel, status: 2  
Dec 31 16:11:40 hw-detect: Using discover version 1.
Dec 31 16:11:42 hw-detect: Detecting hardware...
Dec 31 16:11:43 hw-detect: Missing module 'sym53c8xx'.
Dec 31 16:11:43 hw-detect: Missing module 'usb-storage'.
Dec 31 16:11:43 hw-detect: Missing module 'ide-mod'.
Dec 31 16:11:43 hw-detect: Missing module 'ide-probe-mod'.
Dec 31 16:11:44 hw-detect: Missing module 'ide-detect'.
Dec 31 16:11:44 hw-detect: Missing module 'ide-generic'.
Dec 31 16:11:44 hw-detect: Missing module 'ide-floppy'.
Dec 31 16:11:44 hw-detect: Missing module 'ide-disk'.
Dec 31 16:11:44 hw-detect: Missing module 'ide-cd'.
Dec 31 16:11:44 hw-detect: Missing module 'isofs'.
Dec 31 16:11:44 hw-detect: Loading modules...
Dec 31 16:11:44 hw-detect: Detected module 'pcnet32' for 'Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE]'
Dec 31 16:11:44 hw-detect: Trying to load module 'pcnet32'
Dec 31 16:11:45 kernel: pcnet32.c:v1.30i 06.28.2004 tsbogend@alpha.franken.de
Dec 31 16:11:45 kernel: PCI: Enabling device 0000:00:0c.0 (0000 -> 0003)
Dec 31 16:11:45 kernel: pcnet32: PCnet/PCI II 79C970A at 0x1020, 00 06 29 ba 40 05 assigned IRQ 22.
Dec 31 16:11:45 kernel: divert: allocating divert_blk for eth0
Dec 31 16:11:45 kernel: eth0: registered as PCnet/PCI II 79C970A
Dec 31 16:11:45 kernel: pcnet32: 1 cards_found.
Dec 31 16:11:45 hw-detect: Detected module 'floppy' for 'Linux Floppy'
Dec 31 16:11:45 hw-detect: Trying to load module 'floppy'
Dec 31 16:11:45 kernel: inserting floppy driver for 2.6.8-powerpc
Dec 31 16:11:45 kernel: Using anticipatory io scheduler
Dec 31 16:11:45 kernel: Floppy drive(s): fd0 is 2.88M
Dec 31 16:11:45 kernel: FDC 0 is a National Semiconductor PC87306
Dec 31 16:11:45 kernel: Linux Kernel Card Services
Dec 31 16:11:45 kernel:   options:  [pci] [cardbus] [pm]
Dec 31 16:11:46 hw-detect: Starting PCMCIA services: using yenta_socket instead of i82365
Dec 31 16:11:46 hw-detect: cardmgr[1075]: no sockets found!
Dec 31 16:11:46 cardmgr[1075]: no sockets found!
Dec 31 16:11:46 hw-detect: done.
Dec 31 16:11:46 hw-detect: Detected discover version 1, installing discover1.
Dec 31 16:11:46 hw-detect: Detected hotplug support, installing hotplug.
Dec 31 16:11:47 hw-detect: Missing modules 'sym53c8xx (Symbios Logic Inc. / NCR 53c825), usb-storage (USB storage), ide-mod (Linux IDE driver), ide-probe-mod (Linux IDE probe driver), ide-detect (Linux IDE detection), ide-generic (Linux IDE support), ide-floppy (Linux IDE floppy), ide-disk (Linux ATA DISK), ide-cd (Linux ATAPI CD-ROM), isofs (Linux ISO 9660 filesystem)
Dec 31 16:11:47 main-menu[449]: (process:625): find:  
Dec 31 16:11:47 main-menu[449]: (process:625): /proc/device-tree/ 
Dec 31 16:11:47 main-menu[449]: (process:625): : No such file or directory 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (libc6): package doesn't exist (ignored) 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (libdebian-installer4): search, dependency from cdebconf-udeb 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (libdebian-installer4-udeb): mark, dependency from cdebconf-udeb 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (libtextwrap1): package doesn't exist (ignored) 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (cdebconf-udeb): mark, dependency from languagechooser 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (languagechooser): mark 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (iso-3166-udeb): mark, dependency from countrychooser 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (countrychooser): mark 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (libdebconfclient0): search, dependency from kbd-chooser 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (libdebconfclient0-udeb): mark, dependency from kbd-chooser 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (console-keymaps): search, dependency from kbd-chooser 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (console-keymaps-usb): mark, dependency from kbd-chooser 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (archdetect): mark, dependency from kbd-chooser 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (kbd-chooser): mark 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (discover): search, dependency from hw-detect 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (libdiscover1): package doesn't exist (ignored) 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (discover1-data-udeb): mark, dependency from discover1-udeb 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (discover1-udeb): mark, dependency from hw-detect 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (rootskel): mark, dependency from hw-detect 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (hw-detect): mark, dependency from ethdetect 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (ethdetect): mark 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (libiw27): search, dependency from netcfg 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (libiw27-udeb): mark, dependency from netcfg 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (dhcp-client-udeb): mark, dependency from netcfg 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (ethernet-card-detection): search, dependency from netcfg 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (netcfg): mark 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (configured-network): search, dependency from network-preseed 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (di-utils): mark, dependency from network-preseed 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (network-preseed): mark 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (choose-mirror): mark 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (net-retriever): mark, dependency from download-installer 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (anna): mark, dependency from download-installer 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (download-installer): mark 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (di-utils-shell): mark 
Dec 31 16:11:47 main-menu[449]: DEBUG: resolver (di-utils-reboot): mark 
Dec 31 16:11:47 main-menu[449]: DEBUG: Menu item 'netcfg' selected 
Dec 31 16:11:47 main-menu[449]: DEBUG: configure netcfg, status: 2  
Dec 31 16:11:47 main-menu[449]: DEBUG: configure libc6, status: 0  
Dec 31 16:11:47 main-menu[449]: DEBUG: configure libdebconfclient0, status: 0  
Dec 31 16:11:47 main-menu[449]: DEBUG: virtual package libdebconfclient0  
Dec 31 16:11:47 main-menu[449]: DEBUG: configure libdebian-installer4, status: 0  
Dec 31 16:11:47 main-menu[449]: DEBUG: virtual package libdebian-installer4  
Dec 31 16:11:47 main-menu[449]: DEBUG: configure libiw27, status: 0  
Dec 31 16:11:47 main-menu[449]: DEBUG: virtual package libiw27  
Dec 31 16:11:47 main-menu[449]: INFO: Falling back to the package description for libiw27-udeb 
Dec 31 16:11:47 main-menu[449]: INFO: Falling back to the package description for libiw27-udeb 
Dec 31 16:11:47 main-menu[449]: DEBUG: configure libiw27-udeb, status: 2  
Dec 31 16:11:47 main-menu[449]: DEBUG: configure dhcp-client-udeb, status: 2  
Dec 31 16:11:47 main-menu[449]: DEBUG: configure libc6, status: 0  
Dec 31 16:11:47 main-menu[449]: DEBUG: configure ethernet-card-detection, status: 0  
Dec 31 16:11:47 main-menu[449]: DEBUG: virtual package ethernet-card-detection  
Dec 31 16:11:47 kernel: NET: Registered protocol family 17
Dec 31 16:11:47 dhclient: Internet Software Consortium DHCP Client 2.0pl5
Dec 31 16:11:47 dhclient: Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
Dec 31 16:11:47 dhclient: All rights reserved.
Dec 31 16:11:47 dhclient: 
Dec 31 16:11:47 dhclient: Please contribute if you find this software useful.
Dec 31 16:11:47 dhclient: For info, please visit http://www.isc.org/dhcp-contrib.html
Dec 31 16:11:47 dhclient: 
Dec 31 16:11:48 dhclient: Listening on LPF/eth0/00:06:29:ba:40:05
Dec 31 16:11:48 dhclient: Sending on   LPF/eth0/00:06:29:ba:40:05
Dec 31 16:11:48 dhclient: Sending on   Socket/fallback/fallback-net
Dec 31 16:11:48 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Dec 31 16:11:56 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
Dec 31 16:12:11 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 20
Dec 31 16:12:31 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
Dec 31 16:12:37 main-menu[449]: (process:1127): Internet Software Consortium DHCP Client 2.0pl5 
Dec 31 16:12:37 main-menu[449]: (process:1127):  
Dec 31 16:12:37 main-menu[449]: (process:1127): Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium. 
Dec 31 16:12:37 main-menu[449]: (process:1127):  
Dec 31 16:12:37 main-menu[449]: (process:1127): All rights reserved. 
Dec 31 16:12:37 main-menu[449]: (process:1127):  
Dec 31 16:12:37 main-menu[449]: (process:1127):  
Dec 31 16:12:37 main-menu[449]: (process:1127): Please contribute if you find this software useful. 
Dec 31 16:12:37 main-menu[449]: (process:1127):  
Dec 31 16:12:37 main-menu[449]: (process:1127): For info, please visit http://www.isc.org/dhcp-contrib.html 
Dec 31 16:12:37 main-menu[449]: (process:1127):  
Dec 31 16:12:37 main-menu[449]: (process:1127):  
Dec 31 16:12:37 main-menu[449]: (process:1127): Listening on LPF/eth0/00:06:29:ba:40:05 
Dec 31 16:12:37 main-menu[449]: (process:1127):  
Dec 31 16:12:37 main-menu[449]: (process:1127): Sending on   LPF/eth0/00:06:29:ba:40:05 
Dec 31 16:12:37 main-menu[449]: (process:1127): Sending on   Socket/fallback/fallback-net 
Dec 31 16:12:37 main-menu[449]: (process:1127): DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 
Dec 31 16:12:37 main-menu[449]: (process:1127): DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 
Dec 31 16:12:37 main-menu[449]: (process:1127): DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 20 
Dec 31 16:12:37 main-menu[449]: (process:1127): DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13 
Dec 31 16:12:37 main-menu[449]: INFO: Menu item 'netcfg' succeeded but requested to be left unconfigured. 
Dec 31 16:12:37 main-menu[449]: INFO: Modifying debconf priority limit from 'high' to 'medium' 
Dec 31 16:12:37 debconf: Setting debconf/priority to medium
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (libc6): package doesn't exist (ignored) 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (libdebian-installer4): search, dependency from cdebconf-udeb 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (libdebian-installer4-udeb): mark, dependency from cdebconf-udeb 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (libtextwrap1): package doesn't exist (ignored) 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (cdebconf-udeb): mark, dependency from languagechooser 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (languagechooser): mark 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (iso-3166-udeb): mark, dependency from countrychooser 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (countrychooser): mark 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (libdebconfclient0): search, dependency from kbd-chooser 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (libdebconfclient0-udeb): mark, dependency from kbd-chooser 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (console-keymaps): search, dependency from kbd-chooser 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (console-keymaps-usb): mark, dependency from kbd-chooser 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (archdetect): mark, dependency from kbd-chooser 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (kbd-chooser): mark 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (discover): search, dependency from hw-detect 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (libdiscover1): package doesn't exist (ignored) 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (discover1-data-udeb): mark, dependency from discover1-udeb 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (discover1-udeb): mark, dependency from hw-detect 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (rootskel): mark, dependency from hw-detect 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (hw-detect): mark, dependency from ethdetect 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (ethdetect): mark 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (libiw27): search, dependency from netcfg 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (libiw27-udeb): mark, dependency from netcfg 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (dhcp-client-udeb): mark, dependency from netcfg 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (ethernet-card-detection): search, dependency from netcfg 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (netcfg): mark 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (configured-network): search, dependency from network-preseed 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (di-utils): mark, dependency from network-preseed 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (network-preseed): mark 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (choose-mirror): mark 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (net-retriever): mark, dependency from download-installer 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (anna): mark, dependency from download-installer 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (download-installer): mark 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (di-utils-shell): mark 
Dec 31 16:12:37 main-menu[449]: DEBUG: resolver (di-utils-reboot): mark 
Dec 31 16:13:00 main-menu[449]: DEBUG: Menu item 'di-utils-shell' selected 
Dec 31 16:13:00 main-menu[449]: DEBUG: configure di-utils-shell, status: 2  
Dec 31 16:13:00 main-menu[449]: DEBUG: configure libc6, status: 0  
Dec 31 16:13:00 main-menu[449]: DEBUG: configure libdebconfclient0, status: 0  
Dec 31 16:13:00 main-menu[449]: DEBUG: virtual package libdebconfclient0  
Dec 31 16:13:00 main-menu[449]: DEBUG: configure libdebian-installer4, status: 0  
Dec 31 16:13:00 main-menu[449]: DEBUG: virtual package libdebian-installer4  
~ # 
~ # 
~ # 
~ # 
~ # cat /var/log/messages
insmod /lib/modules/2.6.8-powerpc/kernel/lib/crc32.ko 
insmod /lib/modules/2.6.8-powerpc/kernel/drivers/net/pcnet32.ko 
insmod /lib/modules/2.6.8-powerpc/kernel/drivers/block/floppy.ko 
~ # exit

Re: 43p-140 install issues

[Ulrich Teichert]

Hi,

>Would there be any image I can use to install this machine currently?

Sure, check http://www.solinno.co.uk/7043-140/, that's Leigh Browns site.
There's a detailed step-by-step guide which will take you through the whole
process. You can even choose what distro you want to install, but you may
have to update your firmware first (I had to do it as well, but it was
OK). BTW: great job Leigh!

>Here's my situation, If I can get the machine to boot and install by
>next week (back to work) my boss will let me keep working on it -
>otherwise he'll declare it useless and it'll go back in the closet. If
>I can get anything on it I'm ok - It doesn't need to be 2.6.
[del]

There are 2.4.x kernels on that site which are working very well, I
installed Debian Woody on top of it ;-)

HTH,
Uli
-- 
Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert@gmx.de
Stormweg 24               |listening to: Suicide Drive (The Deep Eynde)
24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)

Re: 43p-140 install issues

[Sven Luther]

On Sat, Jan 01, 2005 at 02:15:33PM +0100, Ulrich Teichert wrote:
> Hi,
> 
> >Would there be any image I can use to install this machine currently?
> 
> Sure, check http://www.solinno.co.uk/7043-140/, that's Leigh Browns site.
> There's a detailed step-by-step guide which will take you through the whole
> process. You can even choose what distro you want to install, but you may
> have to update your firmware first (I had to do it as well, but it was
> OK). BTW: great job Leigh!

I would prefer that we fix the debian kernels for them to work correctly
though. More on this on monday.

> >Here's my situation, If I can get the machine to boot and install by
> >next week (back to work) my boss will let me keep working on it -
> >otherwise he'll declare it useless and it'll go back in the closet. If
> >I can get anything on it I'm ok - It doesn't need to be 2.6.
> [del]
> 
> There are 2.4.x kernels on that site which are working very well, I
> installed Debian Woody on top of it ;-)

Yeah, well.

Do the debian 2.4.27 kernel work on it ? I was unable to boot the 2.4.27 d-i
kernel on my powerstack, but this is a different machine, so the issues may be
a bit different. 

Friendly,

Sven Luther

Re: 43p-140 install issues

[Ulrich Teichert]

Hi,

[del]
>I would prefer that we fix the debian kernels for them to work correctly
>though. More on this on monday.

I failed to configure a stock 2.4.28 kernel to detect the SCSI controler.
I think some of Leigh patches for this must be applied, but I haven't
gone any further.

[del]
>Do the debian 2.4.27 kernel work on it ? I was unable to boot the 2.4.27 d-i
>kernel on my powerstack, but this is a different machine, so the issues may be
>a bit different. 

I've only tried the Woody PREP kernel, which failed in a way which I can't
remember, but I'll give it a try.

HTH,
Uli
-- 
Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert@gmx.de
Stormweg 24               |listening to: Suicide Drive (The Deep Eynde)
24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)

Re: 43p-140 install issues

[Sven Luther]

On Sat, Jan 01, 2005 at 05:30:25PM +0100, Ulrich Teichert wrote:
> Hi,
> 
> [del]
> >I would prefer that we fix the debian kernels for them to work correctly
> >though. More on this on monday.
> 
> I failed to configure a stock 2.4.28 kernel to detect the SCSI controler.
> I think some of Leigh patches for this must be applied, but I haven't
> gone any further.

I had some report on a power3 box, that only the SMP sym53c8xx driver worked.
When configuring in UP mode, 

> [del]
> >Do the debian 2.4.27 kernel work on it ? I was unable to boot the 2.4.27 d-i
> >kernel on my powerstack, but this is a different machine, so the issues may be
> >a bit different. 
> 
> I've only tried the Woody PREP kernel, which failed in a way which I can't
> remember, but I'll give it a try.

Yes, please, i would greatly appreciate it, preferably the 2.6.8 kernel too.
Let' try to get this fixed before the sarge release, which is not so far off
now.

Friendly,

Sven Luther

Re: 43p-140 install issues

[Mike Martin]

I can boot with this image:
http://debian.yorku.ca/debian/dists/testing/main/installer-powerpc/current/images/powerpc/netboot/vmlinuz-prep.initrd

And things seems to go very well. Network configures, hard drives
partition, it dies at "Install the base system"  with "The debootstrap
program exited with an error (return value 255)." It instructs me to
check /var/log/messages which now contains: "execv: No such file or
directory"

The previous step, partitioning, added:
  "No matching physical volumes found
  No volume groups found
  Reading all physical volumes.  This may take a while..."

Anyone?

MikeMartin

On Sat, 1 Jan 2005 17:57:58 +0100, Sven Luther <sven.luther@wanadoo.fr> wrote:
> On Sat, Jan 01, 2005 at 05:30:25PM +0100, Ulrich Teichert wrote:
> > Hi,
> >
> > [del]
> > >I would prefer that we fix the debian kernels for them to work correctly
> > >though. More on this on monday.
> >
> > I failed to configure a stock 2.4.28 kernel to detect the SCSI controler.
> > I think some of Leigh patches for this must be applied, but I haven't
> > gone any further.
> 
> I had some report on a power3 box, that only the SMP sym53c8xx driver worked.
> When configuring in UP mode,
> 
> > [del]
> > >Do the debian 2.4.27 kernel work on it ? I was unable to boot the 2.4.27 d-i
> > >kernel on my powerstack, but this is a different machine, so the issues may be
> > >a bit different.
> >
> > I've only tried the Woody PREP kernel, which failed in a way which I can't
> > remember, but I'll give it a try.
> 
> Yes, please, i would greatly appreciate it, preferably the 2.6.8 kernel too.
> Let' try to get this fixed before the sarge release, which is not so far off
> now.
> 
> Friendly,
> 
> Sven Luther
> 
>

Re: 43p-140 install issues

[Sven Luther]

On Sat, Jan 01, 2005 at 08:15:13PM -0500, Mike Martin wrote:
> I can boot with this image:
> http://debian.yorku.ca/debian/dists/testing/main/installer-powerpc/current/images/powerpc/netboot/vmlinuz-prep.initrd

Cool.

> And things seems to go very well. Network configures, hard drives
> partition, it dies at "Install the base system"  with "The debootstrap
> program exited with an error (return value 255)." It instructs me to
> check /var/log/messages which now contains: "execv: No such file or
> directory"

Strange, can you check at what percentage of "install base system" this error
happned ? can you attach the full /var/log/messages and /var/log/syslog ?

Mmm, CCing debian-boot as this seems more relevant there.@

> The previous step, partitioning, added:
>   "No matching physical volumes found
>   No volume groups found
>   Reading all physical volumes.  This may take a while..."
> 
> Anyone?
> 
> MikeMartin
> 
> On Sat, 1 Jan 2005 17:57:58 +0100, Sven Luther <sven.luther@wanadoo.fr> wrote:
> > On Sat, Jan 01, 2005 at 05:30:25PM +0100, Ulrich Teichert wrote:
> > > Hi,
> > >
> > > [del]
> > > >I would prefer that we fix the debian kernels for them to work correctly
> > > >though. More on this on monday.
> > >
> > > I failed to configure a stock 2.4.28 kernel to detect the SCSI controler.
> > > I think some of Leigh patches for this must be applied, but I haven't
> > > gone any further.
> > 
> > I had some report on a power3 box, that only the SMP sym53c8xx driver worked.
> > When configuring in UP mode,
> > 
> > > [del]
> > > >Do the debian 2.4.27 kernel work on it ? I was unable to boot the 2.4.27 d-i
> > > >kernel on my powerstack, but this is a different machine, so the issues may be
> > > >a bit different.
> > >
> > > I've only tried the Woody PREP kernel, which failed in a way which I can't
> > > remember, but I'll give it a try.
> > 
> > Yes, please, i would greatly appreciate it, preferably the 2.6.8 kernel too.
> > Let' try to get this fixed before the sarge release, which is not so far off
> > now.

Friendly,

Sven Luther

Re: 43p-140 install issues

[Mike Martin]

Now I'm very confused .... on my next reboot ... the network wouldn't
work. After much trial and error, I got the current unstable d-i image
to work. It did it all right up to the reboot (where is warns you that
it doesn't have a boot loader installed).

Now what!

I have an installed system, but I can't figure out how to boot it! I
have /boot/vmlinux on /dev/sdb1 and a root on /dev/sdb1. How do I
write a boot sector or tell OpenFirmware to boot from this file? I
tried to netboot and set root=/dev/sdb1 - but without the scsi modules
loaded it fails to read the drives and panics.

I think I neet to create a type 41 PReP boot partition and get the
kernel onto it. I've found this thread:
http://lists.gnu.org/archive/html/bug-parted/2002-09/msg00016.html

and this:
http://www.yellowdoglinux.com/support/solutions/champion_server/rs6k.shtml

I tried booting up with the installer, going to a shell after the scsi
was active and the installed system was mounted. I used sfdisk from
/target/sbin to create a 10 Meg type 41 partition on the first HD
(/dev/sdb0 eventually). I used dd to copy /target/boot/vmlinux to this
partition. But it still won't boot.

I'm very close. If I can get the system to boot (really it needs to
boot itself - not netboot) I'd call this a success.

Thanks!
MikeM




On Sat, 1 Jan 2005 20:15:13 -0500, Mike Martin <sydneymartin@gmail.com> wrote:
> I can boot with this image:
> http://debian.yorku.ca/debian/dists/testing/main/installer-powerpc/current/images/powerpc/netboot/vmlinuz-prep.initrd
> 
> And things seems to go very well. Network configures, hard drives
> partition, it dies at "Install the base system"  with "The debootstrap
> program exited with an error (return value 255)." It instructs me to
> check /var/log/messages which now contains: "execv: No such file or
> directory"
> 
> The previous step, partitioning, added:
>   "No matching physical volumes found
>   No volume groups found
>   Reading all physical volumes.  This may take a while..."
> 
> Anyone?
> 
> MikeMartin
> 
> On Sat, 1 Jan 2005 17:57:58 +0100, Sven Luther <sven.luther@wanadoo.fr> wrote:
> > On Sat, Jan 01, 2005 at 05:30:25PM +0100, Ulrich Teichert wrote:
> > > Hi,
> > >
> > > [del]
> > > >I would prefer that we fix the debian kernels for them to work correctly
> > > >though. More on this on monday.
> > >
> > > I failed to configure a stock 2.4.28 kernel to detect the SCSI controler.
> > > I think some of Leigh patches for this must be applied, but I haven't
> > > gone any further.
> >
> > I had some report on a power3 box, that only the SMP sym53c8xx driver worked.
> > When configuring in UP mode,
> >
> > > [del]
> > > >Do the debian 2.4.27 kernel work on it ? I was unable to boot the 2.4.27 d-i
> > > >kernel on my powerstack, but this is a different machine, so the issues may be
> > > >a bit different.
> > >
> > > I've only tried the Woody PREP kernel, which failed in a way which I can't
> > > remember, but I'll give it a try.
> >
> > Yes, please, i would greatly appreciate it, preferably the 2.6.8 kernel too.
> > Let' try to get this fixed before the sarge release, which is not so far off
> > now.
> >
> > Friendly,
> >
> > Sven Luther
> >
> >
>

Re: 43p-140 install issues

[Sven Luther]

On Sun, Jan 02, 2005 at 11:15:35PM -0500, Mike Martin wrote:
> Now I'm very confused .... on my next reboot ... the network wouldn't
> work. After much trial and error, I got the current unstable d-i image
> to work. It did it all right up to the reboot (where is warns you that
> it doesn't have a boot loader installed).

There may be some problems with 2.6 kernels and pci irqs on prep. I will
investigate this shortly.

There is indeed no prep boot-loader installer available. I hear there is a
partman-prep prepared, but not yet part of d-i. more to this below.

> Now what!
> 
> I have an installed system, but I can't figure out how to boot it! I
> have /boot/vmlinux on /dev/sdb1 and a root on /dev/sdb1. How do I
> write a boot sector or tell OpenFirmware to boot from this file? I
> tried to netboot and set root=/dev/sdb1 - but without the scsi modules
> loaded it fails to read the drives and panics.

You need to install mkvmlinuz, i think it is already, but not use
/boot/vmlinux-2.6.8-powerpc, but /boot/vmlinuz-2.6.8-powerpc, which is the
result of mkvmlinuz adding the initrd containing the modules onto the kernel,
and then adding the prep simple bootloader. Check if you have the
vmlinuz-2.6.8-powerpc, which should have been generated at install time, and
copy it to your netboot tftp server, and try again. It should even recognize
the root= partition automatically.

> I think I neet to create a type 41 PReP boot partition and get the
> kernel onto it. I've found this thread:
> http://lists.gnu.org/archive/html/bug-parted/2002-09/msg00016.html
> 
> and this:
> http://www.yellowdoglinux.com/support/solutions/champion_server/rs6k.shtml

Yep. Until partman-prep is ready, you should simply try to add the prep flag
to the a small partition. I think the normal scheme is to create /dev/sdb1 as
a small (8MB ?) prep partition, /dev/sdb2 as swap, and /dev/sdb3 as /. If
partman is not able to do it, jump to console 2, and launch parted directly,
and do a set 1 prep on.

Then i suppose that copying the kernel is just a matter of :

  dd if=/boot/vmlinuz-2.6.8-powerpc of=/dev/sdb1

but you have to have a small prep partition as /dev/sdb1, or the above will
erase whatever you have on /dev/sdb1.

> I tried booting up with the installer, going to a shell after the scsi
> was active and the installed system was mounted. I used sfdisk from
> /target/sbin to create a 10 Meg type 41 partition on the first HD
> (/dev/sdb0 eventually). I used dd to copy /target/boot/vmlinux to this
> partition. But it still won't boot.

Ah, no sure what is wrong. I don't think /dev/sdb0 exists. Not sure really.

> I'm very close. If I can get the system to boot (really it needs to
> boot itself - not netboot) I'd call this a success.

Friendly,

Sven Luther

Re: 43p-140 install issues

[Mike Martin]

On Mon, 3 Jan 2005 08:05:35 +0100, Sven Luther <sven.luther@wanadoo.fr> wrote:

[snip]
> There may be some problems with 2.6 kernels and pci irqs on prep. I will
> investigate this shortly.

There is definitely something strange happening. The image I used to
do the (nearly) complete install will no longer configure the network.
Very inconsistent. I will try it (same image) again later today and
see if it "just works" next time - like it did last time.

[snip]
> 
> Yep. Until partman-prep is ready, you should simply try to add the prep flag
> to the a small partition. I think the normal scheme is to create /dev/sdb1 as
> a small (8MB ?) prep partition, /dev/sdb2 as swap, and /dev/sdb3 as /. If
> partman is not able to do it, jump to console 2, and launch parted directly,
> and do a set 1 prep on.

Can't jump to console 2 - I can only comunicate through the serial
console. However I'll give this a shot through the "execute shell"
menu item. "set 1 prep on"? Haven't seen that documented anywhere,
what does it do?

> 
> Then i suppose that copying the kernel is just a matter of :
> 
>   dd if=/boot/vmlinuz-2.6.8-powerpc of=/dev/sdb1
> 
> but you have to have a small prep partition as /dev/sdb1, or the above will
> erase whatever you have on /dev/sdb1.
> 

I' have the partition ready ...

Unfortunately, until the network comes back up, I can't get far enough
in the install to access the SCSI drives (is there another way? Load
the modules by hand? Which ones?). Without this, I can't get at the
image I need to boot in order to get it onto the right partition. I
also can't get it to another machine to net boot it.

> > I tried booting up with the installer, going to a shell after the scsi
> > was active and the installed system was mounted. I used sfdisk from
> > /target/sbin to create a 10 Meg type 41 partition on the first HD
> > (/dev/sdb0 eventually). I used dd to copy /target/boot/vmlinux to this
> > partition. But it still won't boot.
> 
> Ah, no sure what is wrong. I don't think /dev/sdb0 exists. Not sure really.
> 

Actually /dev/sdbX doesn't exist at all during the install from what I
have seen. The drives are refered to as
/dev/scsi/host0/etc/.../etc/part1. I have two drives, one is 9 Gig
with scsi id (0,4,0) (/dev/sda) . This is blank except for a 10 Meg
boot partition; type 41. The second drive is 20 Gig with scsi id
(0,5,0)(/dev/sdb) which is where the install is.

I copied (with dd) the file (the wrong file I suspect) to
/dev/scsi/...../part1 which should correspond to the first partiton on
the 9 Gig drive.

I see how much more time I can buy with this machine. It may need to
go back into storage this week if I can't make it run. Not fun.

Thanks for everyone's help. 
MikeMartin

Re: 43p-140 install issues

[Sven Luther]

On Mon, Jan 03, 2005 at 08:39:43AM -0500, Mike Martin wrote:
> On Mon, 3 Jan 2005 08:05:35 +0100, Sven Luther <sven.luther@wanadoo.fr> wrote:
> 
> [snip]
> > There may be some problems with 2.6 kernels and pci irqs on prep. I will
> > investigate this shortly.
> 
> There is definitely something strange happening. The image I used to
> do the (nearly) complete install will no longer configure the network.
> Very inconsistent. I will try it (same image) again later today and
> see if it "just works" next time - like it did last time.

What exact machine do you have again ? 

> [snip]
> > 
> > Yep. Until partman-prep is ready, you should simply try to add the prep flag
> > to the a small partition. I think the normal scheme is to create /dev/sdb1 as
> > a small (8MB ?) prep partition, /dev/sdb2 as swap, and /dev/sdb3 as /. If
> > partman is not able to do it, jump to console 2, and launch parted directly,
> > and do a set 1 prep on.
> 
> Can't jump to console 2 - I can only comunicate through the serial

Ok, then go to execute a shell then.

> console. However I'll give this a shot through the "execute shell"
> menu item. "set 1 prep on"? Haven't seen that documented anywhere,
> what does it do?

set <minor> <flag> <on|off>

minor is the partition, starting at 1, flag is the flag, (prep in this case)
and on|off is obvious.

It simply sets the prep flag, which is then translated as a 0x41 partition
type. I think this is a deficiency in the parted/libparted API, but well,
there is not much we can do about that unless a major libparted change.

> > Then i suppose that copying the kernel is just a matter of :
> > 
> >   dd if=/boot/vmlinuz-2.6.8-powerpc of=/dev/sdb1
> > 
> > but you have to have a small prep partition as /dev/sdb1, or the above will
> > erase whatever you have on /dev/sdb1.
> > 
> 
> I' have the partition ready ...
> 
> Unfortunately, until the network comes back up, I can't get far enough
> in the install to access the SCSI drives (is there another way? Load
> the modules by hand? Which ones?). Without this, I can't get at the
> image I need to boot in order to get it onto the right partition. I
> also can't get it to another machine to net boot it.

He, understood, we definitively need to investigate the pci irq problems. 

> > > I tried booting up with the installer, going to a shell after the scsi
> > > was active and the installed system was mounted. I used sfdisk from
> > > /target/sbin to create a 10 Meg type 41 partition on the first HD
> > > (/dev/sdb0 eventually). I used dd to copy /target/boot/vmlinux to this
> > > partition. But it still won't boot.
> > 
> > Ah, no sure what is wrong. I don't think /dev/sdb0 exists. Not sure really.
> > 
> 
> Actually /dev/sdbX doesn't exist at all during the install from what I

Yep, d-i uses devfs, still partitions start at 1.

> have seen. The drives are refered to as
> /dev/scsi/host0/etc/.../etc/part1. I have two drives, one is 9 Gig
> with scsi id (0,4,0) (/dev/sda) . This is blank except for a 10 Meg
> boot partition; type 41. The second drive is 20 Gig with scsi id
> (0,5,0)(/dev/sdb) which is where the install is.
> 
> I copied (with dd) the file (the wrong file I suspect) to
> /dev/scsi/...../part1 which should correspond to the first partiton on
> the 9 Gig drive.

Indeed.

> I see how much more time I can buy with this machine. It may need to
> go back into storage this week if I can't make it run. Not fun.

What about donating it to debian or something such ?

Friendly,

Sven Luther

Re: 43p-140 install issues

[Mike Martin]

On Mon, 3 Jan 2005 15:01:02 +0100, Sven Luther <sven.luther@wanadoo.fr> wrote:

[snip]
> What exact machine do you have again ?

An IBM 7043. It's a 43p-140 labeled as a 604e 332 Mhz.

[snip]

> 
> set <minor> <flag> <on|off>
> 
> minor is the partition, starting at 1, flag is the flag, (prep in this case)
> and on|off is obvious.
> 
> It simply sets the prep flag, which is then translated as a 0x41 partition
> type. I think this is a deficiency in the parted/libparted API, but well,
> there is not much we can do about that unless a major libparted change.

Cool. That's good to know.

[snip]

> Yep, d-i uses devfs, still partitions start at 1.

Ok. Oops

> > I see how much more time I can buy with this machine. It may need to
> > go back into storage this week if I can't make it run. Not fun.
> 
> What about donating it to debian or something such ?

I'd love to however it's not mine to donate. It's the companies (They
have 2 actually, I might try the other one since it has slightly
different hardware).

The problem is: at work, I can't netboot. There is no server that will
respond and I can't set one up. I had the machine at home for the
holidays and thus can boot it from my LAN. If I can't get it to
self-boot before I have to take it back to the office - then I'm
stuck.

If I can get it to boot the system (even from floppy or cd) I will
have it to help test stuff. Otherwise it goes back under the desk
where it came from.

MikeMartin

Re: 43p-140 install issues

[Sven Luther]

On Mon, Jan 03, 2005 at 09:07:31AM -0500, Mike Martin wrote:
> On Mon, 3 Jan 2005 15:01:02 +0100, Sven Luther <sven.luther@wanadoo.fr> wrote:
> 
> [snip]
> > What exact machine do you have again ?
> 
> An IBM 7043. It's a 43p-140 labeled as a 604e 332 Mhz.

Well, prep_pci.c does know about : 

  IBM RS/6000 7043-240 (ibm_doral)
  IBM RS/6000 7024-E30

As far as IBM boxes are concerned. Doe the -140 have stuff in common with
leigh's -240 (the -140 being mono-cpu while the -240 being dual ?).

> [snip]
> 
> > 
> > set <minor> <flag> <on|off>
> > 
> > minor is the partition, starting at 1, flag is the flag, (prep in this case)
> > and on|off is obvious.
> > 
> > It simply sets the prep flag, which is then translated as a 0x41 partition
> > type. I think this is a deficiency in the parted/libparted API, but well,
> > there is not much we can do about that unless a major libparted change.
> 
> Cool. That's good to know.

It was added recently though.

> > Yep, d-i uses devfs, still partitions start at 1.
> 
> Ok. Oops
> 
> > > I see how much more time I can buy with this machine. It may need to
> > > go back into storage this week if I can't make it run. Not fun.
> > 
> > What about donating it to debian or something such ?
> 
> I'd love to however it's not mine to donate. It's the companies (They
> have 2 actually, I might try the other one since it has slightly
> different hardware).

Well, you could argue that donating one might make the other one usefull :)

> The problem is: at work, I can't netboot. There is no server that will
> respond and I can't set one up. I had the machine at home for the
> holidays and thus can boot it from my LAN. If I can't get it to
> self-boot before I have to take it back to the office - then I'm
> stuck.

Ok, understandable, still, getting it to netboot would be a first step to
getting it working right later.

> If I can get it to boot the system (even from floppy or cd) I will
> have it to help test stuff. Otherwise it goes back under the desk
> where it came from.

Understandable too. What is the deadline ? I built a d-i kernel with the
powerstack2 - utah pci irq patch, and it now works fine here. Still some work
is needed, but basically this means i can scratch the disk on the box, and do
some real d-i development, bringing in the partman-prep patch, and maybe even
building a prep-installer that does the needed stuff to make it self-boot.

I think you have to give your box back by monday next week though, right ?
this could be too short, but let's see if we can make something happen.

Right now, there are two issues : 

  1) the kernel may have some irq problems, or some other patching may be
  needed.

  2) partman-prep is not included in d-i.

  3) there is no automated prep-installer in d-i.
  
Watch out on : http://people.debian.org/~luther/prep for uploads i make.

Friendly,

Sven Luther

Re: 43p-140 install issues

[Philippe Guyot]

On Monday 03 January 2005 15:30, Sven Luther wrote:
> On Mon, Jan 03, 2005 at 09:07:31AM -0500, Mike Martin wrote:
> > On Mon, 3 Jan 2005 15:01:02 +0100, Sven Luther <sven.luther@wanadoo.fr>
> > wrote:
> >
> > [snip]
> >
> > > What exact machine do you have again ?
> >
> > An IBM 7043. It's a 43p-140 labeled as a 604e 332 Mhz.


I suppose you meen 233 Mhz ?
>
> Well, prep_pci.c does know about :
>
>   IBM RS/6000 7043-240 (ibm_doral)
>   IBM RS/6000 7024-E30
>
> As far as IBM boxes are concerned. Doe the -140 have stuff in common with
> leigh's -240 (the -140 being mono-cpu while the -240 being dual ?).

More different than that, 140 is more recent.

But works fine with Debian woody.(sorry Sven...)


>
> > [snip]
> >
> > > set <minor> <flag> <on|off>
> > >
> > > minor is the partition, starting at 1, flag is the flag, (prep in this
> > > case) and on|off is obvious.
> > >
> > > It simply sets the prep flag, which is then translated as a 0x41
> > > partition type. I think this is a deficiency in the parted/libparted
> > > API, but well, there is not much we can do about that unless a major
> > > libparted change.
> >
> > Cool. That's good to know.
>
> It was added recently though.
>
> > > Yep, d-i uses devfs, still partitions start at 1.
> >
> > Ok. Oops
> >
> > > > I see how much more time I can buy with this machine. It may need to
> > > > go back into storage this week if I can't make it run. Not fun.
> > >
> > > What about donating it to debian or something such ?
> >
> > I'd love to however it's not mine to donate. It's the companies (They
> > have 2 actually, I might try the other one since it has slightly
> > different hardware).
>
> Well, you could argue that donating one might make the other one usefull :)
>
> > The problem is: at work, I can't netboot. There is no server that will
> > respond and I can't set one up. I had the machine at home for the
> > holidays and thus can boot it from my LAN. If I can't get it to
> > self-boot before I have to take it back to the office - then I'm
> > stuck.
>
> Ok, understandable, still, getting it to netboot would be a first step to
> getting it working right later.
>
> > If I can get it to boot the system (even from floppy or cd) I will
> > have it to help test stuff. Otherwise it goes back under the desk
> > where it came from.

If there is such a deadline, why not consider to install first a woody (many 
successes exist) then upgrading to sarge after ?


>
> Understandable too. What is the deadline ? I built a d-i kernel with the
> powerstack2 - utah pci irq patch, and it now works fine here. Still some
> work is needed, but basically this means i can scratch the disk on the box,
> and do some real d-i development, bringing in the partman-prep patch, and
> maybe even building a prep-installer that does the needed stuff to make it
> self-boot.
>
> I think you have to give your box back by monday next week though, right ?
> this could be too short, but let's see if we can make something happen.
>
> Right now, there are two issues :
>
>   1) the kernel may have some irq problems, or some other patching may be
>   needed.
>
>   2) partman-prep is not included in d-i.
>
>   3) there is no automated prep-installer in d-i.
>
> Watch out on : http://people.debian.org/~luther/prep for uploads i make.
>
> Friendly,
>
> Sven Luther

Re: 43p-140 install issues

[Mike Martin]

> > > An IBM 7043. It's a 43p-140 labeled as a 604e 332 Mhz.
> 
> I suppose you meen 233 Mhz ?

I know 332 MHz doesn't sound right ... but I'm sure that's what it
says on the IBM nameplate on the front. I'll verify this tonight

> More different than that, 140 is more recent.

Have you got specs and stuff on the -140 you could link to? Maybe this
would help.

> 
> But works fine with Debian woody.(sorry Sven...)
[snip]
> If there is such a deadline, why not consider to install first a woody (many
> successes exist) then upgrading to sarge after ?

This is my preference. I'd like to install woody on one drive so I can
boot it up and say "Look Linux runs, it's stable and useful" and then
have the other to install, boot, and otherwise help test the new
stuff.

Unfortunately, I can't get _anything_ to install (I even tried a BSD,
but quickly realized I was in too deep there!). The unstable stuff I'm
trying now has gotten me the furthest along.

MikeM

Re: 43p-140 install issues

[vinai]

>>>> An IBM 7043. It's a 43p-140 labeled as a 604e 332 Mhz.
>>
>> I suppose you meen 233 Mhz ?
>
> I know 332 MHz doesn't sound right ... but I'm sure that's what it
> says on the IBM nameplate on the front. I'll verify this tonight

According to this page:

    http://www.sinca.biz/IBM/rs6000_43p_140.html

the 7043-140 does come in 2 flavours, a 233 and 332 MHz model.  I've
been looking into getting my own 150 to play with :)

cheers
vinai

Re: 43p-140 install issues

[Sven Luther]

On Mon, Jan 03, 2005 at 03:30:54PM +0100, Philippe Guyot wrote:
> On Monday 03 January 2005 15:30, Sven Luther wrote:
> > On Mon, Jan 03, 2005 at 09:07:31AM -0500, Mike Martin wrote:
> > > On Mon, 3 Jan 2005 15:01:02 +0100, Sven Luther <sven.luther@wanadoo.fr>
> > > wrote:
> > >
> > > [snip]
> > >
> > > > What exact machine do you have again ?
> > >
> > > An IBM 7043. It's a 43p-140 labeled as a 604e 332 Mhz.
> 
> 
> I suppose you meen 233 Mhz ?
> >
> > Well, prep_pci.c does know about :
> >
> >   IBM RS/6000 7043-240 (ibm_doral)
> >   IBM RS/6000 7024-E30
> >
> > As far as IBM boxes are concerned. Doe the -140 have stuff in common with
> > leigh's -240 (the -140 being mono-cpu while the -240 being dual ?).
> 
> More different than that, 140 is more recent.
> 
> But works fine with Debian woody.(sorry Sven...)

Yeah, that is not the problem, the problem is that it doesn't work with the
2.6.8 kernel used by debian/sarge. So, now, the first order of business to fix
this is to find out what exactly is broken in the 2.6.8 kernel on this
hardware, fish out patches which may or may not solve the issue, and get it
solved. I will soon be making a kernel-source-2.6.8 upload for the powerstack
II problem i have hardware for, so it would be nice to fix these issues at the
same time. 

Once we have a working kernel, we will upload partman-prep from Cajus
Pollmeier, and add a prep-installer, and there will be propper prep support in
sarge, at least for the powerstack II.

> > Ok, understandable, still, getting it to netboot would be a first step to
> > getting it working right later.
> >
> > > If I can get it to boot the system (even from floppy or cd) I will
> > > have it to help test stuff. Otherwise it goes back under the desk
> > > where it came from.
> 
> If there is such a deadline, why not consider to install first a woody (many 
> successes exist) then upgrading to sarge after ?

That is always a solution. Getting the 2.6 debian kernel fixed would be nice
though. 

Friendly,

Sven Luther

Re: 43p-140 install issues

[Mike Martin]

[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]

(Re-posting with shorter attachment to please the list gods. Sorry)

> If there is such a deadline, why not consider to install first a woody (many
> successes exist) then upgrading to sarge after ?

Ok... trying again with Leigh Brown's boot image and a woody root
floppy and a woody CD.

The console capture is below. Leigh's kernel boots up great, asks for
a root floppy and then ...

VFS: Insert root floppy and press ENTER

FAT: bogus logical sector size 1981
FAT: bogus logical sector size 1981
read_super_block: can't find a reiserfs filesystem on (dev 02:00,
block 64, size 1024)
read_super_block: can't find a reiserfs filesystem on (dev 02:00,
block 8, size 1024)
Kernel panic: VFS: Unable to mount root fs on 02:00

Reiserfs? Huh? I tried it twice, two different floppies. Both written
as follows (as suggested in Debian manual):
sudo dd if=root.bin of=/dev/fd0 bs=1024 conv=sync ; sync
\1440+0 records in
1440+0 records out
1474560 bytes transferred in 120.042950 seconds (12284 bytes/sec)

I can however boot the installation I made earlier using Leigh's
image. I have completed the installation and it runs ... for a short
period of time. After about 5 minutes or so it stops responding to the
console and to pings.

MikeMartin

[-- Attachment #2: 43pflo~1.txt --]
[-- Type: text/plain, Size: 5732 bytes --]

RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000

     memory      keyboard     network      scsi      speaker       ok
0 > boot floppy 

loaded at:     00600400 00734EC8
relocated to:  00800100 00934BC8
board data at: 00231370 00237D7C
relocated to:  0092B02C 00931A38
zimage at:     00805B90 0092AA9D
avail ram:     00400000 00800000

Linux/PPC load: console=ttyS0,9600 root=/dev/fd0
Uncompressing Linux...done.
Now booting the kernel
Memory BAT mapping: BAT2=256Mb, BAT3=0Mb, residual: 0Mb
Total memory = 256MB; using 512kB for hash table (at c0300000)
Linux version 2.4.19 (leigh@micro.solinno.co.uk) (gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-81)) #3 Sun Aug 4 08:28:30 BST 2002
PReP architecture
IBM planar ID: 000000d5
PReP boot cpu: 0
MPIC at 0xfddc0000 (0x3ddc0000), length 0x00040000 mapped to 0xeffc0000
On node 0 totalpages: 65536
zone(0): 65536 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: console=ttyS0,9600 root=/dev/fd0
OpenPIC Version 1.0 (4 CPUs and 16 IRQ sources) at effc0000
time_init: decrementer frequency = 16.617869 MHz
Console: colour dummy device 80x25
Calibrating delay loop... 331.77 BogoMIPS
Memory: 255552k available (1944k kernel code, 880k data, 160k init, 0k highmem)
Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)
Inode cache hash table entries: 16384 (order: 5, 131072 bytes)
Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)
Buffer-cache hash table entries: 16384 (order: 4, 65536 bytes)
Page-cache hash table entries: 65536 (order: 6, 262144 bytes)
POSIX conformance testing by UNIFIX
PCI: Probing PCI hardware
Bridge 00:17.0 resource 2 was deactivated by firmware
Setting PCI interrupts for a "IBM 43P-140 (Tiger1)"
PCI: Cannot allocate resource region 0 of PCI bridge 1
PCI: bridge 1 resource 0 moved to 7ff000..7fffff
PCI: Cannot allocate resource region 0 of device 00:0b.0
PCI: Cannot allocate resource region 0 of device 00:0c.0
PCI: Cannot allocate resource region 0 of device 00:10.0
PCI: Cannot allocate resource region 0 of device 00:12.0
PCI: Cannot allocate resource region 0 of device 01:03.0
PCI: moved device 00:0b.0 resource 0 (101) to 1000
PCI: moved device 00:0c.0 resource 0 (101) to 1020
PCI: moved device 00:10.0 resource 0 (101) to 1400
PCI: moved device 00:12.0 resource 0 (101) to 1040
PCI: moved device 01:03.0 resource 0 (101) to 7ff000
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
VFS: Diskquotas version dquot_6.4.0 initialized
Journalled Block Device driver loaded
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
IBM_E15: initializing
IBM_E15: could not find S3 864 in system
initialize_kbd: Keyboard reset failed, no ACK
Detected PS/2 Mouse Port.
pty: 256 Unix98 ptys configured
keyboard: Timeout - AT keyboard not present?(ed)
keyboard: Timeout - AT keyboard not present?(f4)
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
Floppy drive(s): fd0 is 2.88M
FDC 0 is a National Semiconductor PC87306
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
pcnet32.c:v1.27a 10.02.2002 tsbogend@alpha.franken.de
PCI: Enabling device 00:0c.0 (0000 -> 0003)
pcnet32: PCnet/PCI II 79C970A at 0x1020, 00 06 29 ba 40 05 assigned IRQ 22.
eth0: registered as PCnet/PCI II 79C970A
pcnet32: 1 cards_found.
SCSI subsystem driver Revision: 1.00
PCI: Enabling device 00:10.0 (0010 -> 0013)
ncr53c8xx: at PCI bus 0, device 16, function 0
ncr53c8xx: setting PCI_COMMAND_MASTER...(fix-up)
ncr53c8xx: 53c825a detected 
ncr53c825a-0: rev 0x13 on pci bus 0 device 16 function 0 irq 23
ncr53c825a-0: ID 7, Fast-10, Parity Checking
scsi0 : ncr53c8xx-3.4.3b-20010512
  Vendor: IBM       Model: CDRM00203     !K  Rev: 1.00
  Type:   CD-ROM                             ANSI SCSI revision: 02
ncr53c825a-0-<4,*>: FAST-10 WIDE SCSI 20.0 MB/s (100 ns, offset 8)
  Vendor: IBM       Model: DCHS09U           Rev: 6363
  Type:   Direct-Access                      ANSI SCSI revision: 02
ncr53c825a-0-<5,*>: FAST-10 WIDE SCSI 20.0 MB/s (100 ns, offset 8)
  Vendor: IBM       Model: DPSS-318350N      Rev: S96F
  Type:   Direct-Access                      ANSI SCSI revision: 03
Attached scsi disk sda at scsi0, channel 0, id 4, lun 0
Attached scsi disk sdb at scsi0, channel 0, id 5, lun 0
SCSI device sda: 17774160 512-byte hdwr sectors (9100 MB)
Partition check:
 sda: sda1
sdb: Spinning up disk..............ready
SCSI device sdb: 35548320 512-byte hdwr sectors (18201 MB)
 sdb: sdb1 sdb2 < sdb5 >
Attached scsi CD-ROM sr0 at scsi0, channel 0, id 3, lun 0
ncr53c825a-0-<3,*>: FAST-10 SCSI 10.0 MB/s (100 ns, offset 8)
sr0: scsi-1 drive
Uniform CD-ROM driver Revision: 3.12
Macintosh non-volatile memory driver v1.0
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
mice: PS/2 mouse device common for all mice
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP: Hash tables configured (established 16384 bind 16384)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Insert root floppy and press ENTER
FAT: bogus logical sector size 1981
FAT: bogus logical sector size 1981
read_super_block: can't find a reiserfs filesystem on (dev 02:00, block 64, size 1024)
read_super_block: can't find a reiserfs filesystem on (dev 02:00, block 8, size 1024)
Kernel panic: VFS: Unable to mount root fs on 02:00
 <0>Rebooting in 180 seconds..

Re: 43p-140 install issues

[Ulrich Teichert]

Hi,

[del]
>Ok... trying again with Leigh Brown's boot image and a woody root
>floppy and a woody CD.
>
>The console capture is below. Leigh's kernel boots up great, asks for
>a root floppy and then ...
>
>VFS: Insert root floppy and press ENTER
>
>FAT: bogus logical sector size 1981
>FAT: bogus logical sector size 1981

Strange.

[del]
>Reiserfs? Huh? I tried it twice, two different floppies. Both written
>as follows (as suggested in Debian manual):
>sudo dd if=root.bin of=/dev/fd0 bs=1024 conv=sync ; sync
>\1440+0 records in
>1440+0 records out
>1474560 bytes transferred in 120.042950 seconds (12284 bytes/sec)

How did you format the floppys before?

>I can however boot the installation I made earlier using Leigh's
>image. I have completed the installation and it runs ... for a short
>period of time. After about 5 minutes or so it stops responding to the
>console and to pings.

Ugh. I would recommend to dd Leighs kernel to your disk then. This has been
running reliable for me. The bootup log looks good to me, minus the floppy issue,
it's very much like mine.

HTH,
Uli
-- 
Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert@gmx.de
Stormweg 24               |listening to: Suicide Drive (The Deep Eynde)
24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)

Re: 43p-140 install issues

[Philippe Guyot]

On Tuesday 04 January 2005 05:03, Mike Martin wrote:
> (Re-posting with shorter attachment to please the list gods. Sorry)
>
> > If there is such a deadline, why not consider to install first a woody
> > (many successes exist) then upgrading to sarge after ?
>
> Ok... trying again with Leigh Brown's boot image and a woody root
> floppy and a woody CD.
>
> The console capture is below. Leigh's kernel boots up great, asks for
> a root floppy and then ...
>
> VFS: Insert root floppy and press ENTER
>
> FAT: bogus logical sector size 1981
> FAT: bogus logical sector size 1981
> read_super_block: can't find a reiserfs filesystem on (dev 02:00,
> block 64, size 1024)
> read_super_block: can't find a reiserfs filesystem on (dev 02:00,
> block 8, size 1024)
> Kernel panic: VFS: Unable to mount root fs on 02:00
>
> Reiserfs? Huh? I tried it twice, two different floppies. Both written
> as follows (as suggested in Debian manual):
> sudo dd if=root.bin of=/dev/fd0 bs=1024 conv=sync ; sync
> \1440+0 records in
> 1440+0 records out
> 1474560 bytes transferred in 120.042950 seconds (12284 bytes/sec)
>
> I can however boot the installation I made earlier using Leigh's
> image. I have completed the installation and it runs ... for a short
> period of time. After about 5 minutes or so it stops responding to the
> console and to pings.
>

 BTW, what about your firmware? Is it the most recent one ?


> MikeMartin

Re: 43p-140 install issues

[Ulrich Teichert]

Hi,

[del]
> BTW, what about your firmware? Is it the most recent one ?

Yes, it is. I have asked this before ;-)

CU,
Uli
-- 
Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert@gmx.de
Stormweg 24               |listening to: Suicide Drive (The Deep Eynde)
24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)

Re: 43p-140 install issues

[Mike Martin]

The firmware is the most recent.

The kernel (boot) is Leigh's 2.4.19 kernel.

The root is from Woody.

Both floppies were written with dd to blank, unforatted disks.

I'll give 2.4.22 a try tonight.

Thanks!
MikeMartin

On Tue, 4 Jan 2005 10:23:37 +0100, Philippe Guyot <pguyot@cvf.fr> wrote:
> On Tuesday 04 January 2005 05:03, Mike Martin wrote:
> > (Re-posting with shorter attachment to please the list gods. Sorry)
> >
> > > If there is such a deadline, why not consider to install first a woody
> > > (many successes exist) then upgrading to sarge after ?
> >
> > Ok... trying again with Leigh Brown's boot image and a woody root
> > floppy and a woody CD.
> >
> > The console capture is below. Leigh's kernel boots up great, asks for
> > a root floppy and then ...
> >
> > VFS: Insert root floppy and press ENTER
> >
> > FAT: bogus logical sector size 1981
> > FAT: bogus logical sector size 1981
> > read_super_block: can't find a reiserfs filesystem on (dev 02:00,
> > block 64, size 1024)
> > read_super_block: can't find a reiserfs filesystem on (dev 02:00,
> > block 8, size 1024)
> > Kernel panic: VFS: Unable to mount root fs on 02:00
> >
> > Reiserfs? Huh? I tried it twice, two different floppies. Both written
> > as follows (as suggested in Debian manual):
> > sudo dd if=root.bin of=/dev/fd0 bs=1024 conv=sync ; sync
> > \1440+0 records in
> > 1440+0 records out
> > 1474560 bytes transferred in 120.042950 seconds (12284 bytes/sec)
> >
> > I can however boot the installation I made earlier using Leigh's
> > image. I have completed the installation and it runs ... for a short
> > period of time. After about 5 minutes or so it stops responding to the
> > console and to pings.
> >
> 
>  BTW, what about your firmware? Is it the most recent one ?
> 
> > MikeMartin
>

Re: 43p-140 install issues

[Mike Martin]

> I'll give 2.4.22 a try tonight.
> 
> Thanks!
> MikeMartin

I gave Leigh's 2.4.22 a try. It gave me the same result with the
debian root disk:

VFS: Insert root floppy and press ENTER

FAT: bogus logical sector size 1981
FAT: bogus logical sector size 1981
read_super_block: can't find a reiserfs filesystem on (dev 02:00,
block 64, size 1024)
read_super_block: can't find a reiserfs filesystem on (dev 02:00,
block 8, size 1024)
Kernel panic: VFS: Unable to mount root fs on 02:00

Tonight I'll grab a different root floppy and see what happens.

Leigh's 2.4.22 will also boot the system installed on /dev/sdb1,
however it also stopped responding after awhile. I think it lasted
longer than with 2.4.19.

MikeMartin

Re: 43p-140 install issues

[Ulrich Teichert]

Hi,

>I gave Leigh's 2.4.22 a try. It gave me the same result with the
>debian root disk:
>
>VFS: Insert root floppy and press ENTER
>
>FAT: bogus logical sector size 1981
>FAT: bogus logical sector size 1981
>read_super_block: can't find a reiserfs filesystem on (dev 02:00,
>block 64, size 1024)
>read_super_block: can't find a reiserfs filesystem on (dev 02:00,
>block 8, size 1024)
>Kernel panic: VFS: Unable to mount root fs on 02:00

Could you try to format them before dd'ing on them, like fdformat /dev/fd0h1440?
I am not sure if that will change anything, though.

>Tonight I'll grab a different root floppy and see what happens.
>
>Leigh's 2.4.22 will also boot the system installed on /dev/sdb1,
>however it also stopped responding after awhile. I think it lasted
>longer than with 2.4.19.

I am begining to believe that there is some sort of hardware problem with your
box or it is an upgraded version which was a -140 in it's previous life, but my
-140 is rock solid with Leigh's 2.4.19 kernel - once it's up, that is.
I will leave it running tonight to see what happens,

HTH,
Uli
-- 
Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert@gmx.de
Stormweg 24               |listening to: Suicide Drive (The Deep Eynde)
24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)

Re: 43p-140 install issues

[Mike Martin]

On Tue, 4 Jan 2005 16:23:50 +0100 (MET), Ulrich Teichert 
> Could you try to format them before dd'ing on them, like fdformat /dev/fd0h1440?
> I am not sure if that will change anything, though.

Will do.

> 
> I am begining to believe that there is some sort of hardware problem with your
> box or it is an upgraded version which was a -140 in it's previous life, but my
> -140 is rock solid with Leigh's 2.4.19 kernel - once it's up, that is.
> I will leave it running tonight to see what happens,
> 
> HTH,
> Uli

I am starting to believe this as well. I'm going to see if I can get
some history on the machine from before it was shelved. As well, I
know there is a second machine, I'm going to see if I can swap this
one for that one and see if the same issues exist.

MikeMartin

Re: 43p-140 install issues

[Mike Martin]

On Tue, 4 Jan 2005 10:39:41 -0500, Mike Martin <sydneymartin@gmail.com> wrote:
> On Tue, 4 Jan 2005 16:23:50 +0100 (MET), Ulrich Teichert
> > Could you try to format them before dd'ing on them, like fdformat /dev/fd0h1440?
> > I am not sure if that will change anything, though.
> 
> Will do.

Done - no difference. Same message. Written multiple images, multiple
times on multiple machine. Each one with the same result. At least I'm
not completely alone, I found this:
http://wikihip.cern.ch/twiki/bin/view/RS6000/KernelTestsOn43P240 exact
same error.
 
> >
> > I am begining to believe that there is some sort of hardware problem with your
> > box or it is an upgraded version which was a -140 in it's previous life, but my
> > -140 is rock solid with Leigh's 2.4.19 kernel - once it's up, that is.
> > I will leave it running tonight to see what happens,
> >
> > HTH,
> > Uli
> 
> I am starting to believe this as well. I'm going to see if I can get
> some history on the machine from before it was shelved. As well, I
> know there is a second machine, I'm going to see if I can swap this
> one for that one and see if the same issues exist.
> 
> MikeMartin
> 
The machine was working fine under AIX when it was decomissioned. It
had some issues with a disk going bad due to heat (blocked vents). But
once they were cleared there were no issues. I am going to try the
other machine. I'll keep my finger's crossed.

MikeMartin

Re: 43p-140 install issues

[Ulrich Teichert]

Hi,

[del]
>Done - no difference. Same message. Written multiple images, multiple
>times on multiple machine. Each one with the same result. At least I'm
>not completely alone, I found this:
>http://wikihip.cern.ch/twiki/bin/view/RS6000/KernelTestsOn43P240 exact
>same error.

Perhaps there are two different board revisions of -140's out? I'll check
what's written on the system board when I'm home again today.

>> > I am begining to believe that there is some sort of hardware problem with your
>> > box or it is an upgraded version which was a -140 in it's previous life, but my
>> > -140 is rock solid with Leigh's 2.4.19 kernel - once it's up, that is.
>> > I will leave it running tonight to see what happens,
[del]

Still running fine:

wehrle:~> uname -a
Linux wehrle 2.4.19 #3 Sun Aug 4 08:28:30 BST 2002 ppc unknown
wehrle:~> uptime
 08:58:25 up 13:08,  1 user,  load average: 0.00, 0.00, 0.00

I did a kernel compile with a parallel scp transfer as well to put the box
under a bit of load before, no issues.

HTH,
Uli
-- 
Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert@gmx.de
Stormweg 24               |listening to: Suicide Drive (The Deep Eynde)
24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)

Re: 43p-140 install issues

[Ulrich Teichert]

Hi,

the only reference number on my board is the IBM FRU number:

FRU 93H7143

I would expect that you will have the same marking on your mainboard.
My box ran all day with various loads from high to low or no load
at all:

wehrle:~> uptime
 22:29:24 up 1 day,  2:39,  2 users,  load average: 0.15, 0.32, 0.61

with Leigh's 2.4.19 kernel. As I searched for the number, I noticed
that the CPU fan was *covered* with dirt. Perhaps you should have
a look at yours too, because the front fan will pick up all dust and
throw it right on the CPU fan. I still wonder why mine was still
spinning....

HTH,
Uli
-- 
Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert@gmx.de
Stormweg 24               |listening to: Suicide Drive (The Deep Eynde)
24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)

Re: 43p-140 install issues

[Leigh Brown]

Mike Martin said:
> On Tue, 4 Jan 2005 10:39:41 -0500, Mike Martin <sydneymartin@gmail.com>
> wrote:
>> On Tue, 4 Jan 2005 16:23:50 +0100 (MET), Ulrich Teichert
>> > Could you try to format them before dd'ing on them, like fdformat
>> /dev/fd0h1440?
>> > I am not sure if that will change anything, though.
>>
>> Will do.
>
> Done - no difference. Same message. Written multiple images, multiple
> times on multiple machine. Each one with the same result. At least I'm
> not completely alone, I found this:
> http://wikihip.cern.ch/twiki/bin/view/RS6000/KernelTestsOn43P240 exact
> same error.

I think I know what's going on here.  What boot arguments are you using?
You should have "load_ramdisk=1" in there somewhere at the very least.

Cheers,

Leigh.

Re: 43p-140 install issues

[Mike Martin]

> > > I am begining to believe that there is some sort of hardware problem with your
> > > box or it is an upgraded version which was a -140 in it's previous life, but my
> > > -140 is rock solid with Leigh's 2.4.19 kernel - once it's up, that is.
> > > I will leave it running tonight to see what happens,

[snip]

> The machine was working fine under AIX when it was decomissioned. It
> had some issues with a disk going bad due to heat (blocked vents). But
> once they were cleared there were no issues. I am going to try the
> other machine. I'll keep my finger's crossed.
> 
> MikeMartin

An update (Sucess!!!):
After jogging some people's memory I found out that this machine has a
PCI token ring card (which I wasn't using) because the on-board
ethernet went flaky. This certainly helps explain my intermitent
network, and quite possibly the short up-times before crashing. As we
guessed - a hardware problem.

Is there any way (jumper ?) to disable the onboard ethernet? I may try
not loading the modules for it and see if the machine becomes stable.
Would a standard PCI ethernet card work as a substitute (likely won't
netboot)?

Now the success:
I put Leigh's boot floppy and the Woody root floppy (from
debian.yorku.ca mirror) into the second machine at noon today. By 1pm
I had a fully installed, configured and self-booting installation of
Woody on a 43p-140.

By 1:30 I had it re-pinned to "testing" and "dist-upgrad"ing. It was
finished and running great when I left work.

Since the machine is at work, I don't have much time to mess with it,
(since that's not my job!) but I will try in the next week to test
Sven's d-i disks on a second hard disk. It's the least I can do for
the help you've all given.

Thanks!
MikeMartin

Re: 43p-140 install issues

[Sven Luther]

On Wed, Jan 05, 2005 at 10:35:50PM -0500, Mike Martin wrote:
> > > > I am begining to believe that there is some sort of hardware problem with your
> > > > box or it is an upgraded version which was a -140 in it's previous life, but my
> > > > -140 is rock solid with Leigh's 2.4.19 kernel - once it's up, that is.
> > > > I will leave it running tonight to see what happens,
> 
> [snip]
> 
> > The machine was working fine under AIX when it was decomissioned. It
> > had some issues with a disk going bad due to heat (blocked vents). But
> > once they were cleared there were no issues. I am going to try the
> > other machine. I'll keep my finger's crossed.
> > 
> > MikeMartin
> 
> An update (Sucess!!!):
> After jogging some people's memory I found out that this machine has a
> PCI token ring card (which I wasn't using) because the on-board
> ethernet went flaky. This certainly helps explain my intermitent
> network, and quite possibly the short up-times before crashing. As we
> guessed - a hardware problem.
> 
> Is there any way (jumper ?) to disable the onboard ethernet? I may try
> not loading the modules for it and see if the machine becomes stable.
> Would a standard PCI ethernet card work as a substitute (likely won't
> netboot)?

You have to blacklist the module in discover/hotplug, and it won't be loaded
at install time. In d-i, i believe you could rmmod it as soon as possible, not
sure if you can blacklist it, i will investigate.

I want to know something else from you though. In the end, did the debian
2.6.8 kernel (and d-i) work for you or not, i sort of lost track of this.

> Now the success:
> I put Leigh's boot floppy and the Woody root floppy (from
> debian.yorku.ca mirror) into the second machine at noon today. By 1pm
> I had a fully installed, configured and self-booting installation of
> Woody on a 43p-140.
> 
> By 1:30 I had it re-pinned to "testing" and "dist-upgrad"ing. It was
> finished and running great when I left work.
> 
> Since the machine is at work, I don't have much time to mess with it,
> (since that's not my job!) but I will try in the next week to test
> Sven's d-i disks on a second hard disk. It's the least I can do for
> the help you've all given.

Hehe. Also, if we fix the issue, it will come in handy next time you want to
install it, not to count that you may like eventual security builds of the
debian kernel down the road.

Friendly,

Sven Luther

Re: 43p-140 install issues

[Mike Martin]

Another update, More success

> An update (Sucess!!!):
> After jogging some people's memory I found out that this machine has a
> PCI token ring card (which I wasn't using) because the on-board
> ethernet went flaky. This certainly helps explain my intermitent
> network, and quite possibly the short up-times before crashing. As we
> guessed - a hardware problem.
> 
> Is there any way (jumper ?) to disable the onboard ethernet? I may try
> not loading the modules for it and see if the machine becomes stable.
> Would a standard PCI ethernet card work as a substitute (likely won't
> netboot)?

I checked the machine's docs - there appears to be no jumper to
disable the onboard ethernet. However, If I simply unplug the ethernet
cable the instability seems to diappear. The machine just did a
flawless install booting from Leigh's disk, Woody root on a floppy and
base on cd-rom.

I have a PCI ethernet card left over from an old PentiumPro. It says
it is a 3Com "Fast EtherLink XL PCI" "3C905-TX". Would this card work
in this machine? Would it be able to netboot (doubtfull).

MikeMartin

Re: 43p-140 install issues

[Sven Luther]

On Fri, Jan 07, 2005 at 12:10:49AM -0500, Mike Martin wrote:
> Another update, More success
> 
> > An update (Sucess!!!):
> > After jogging some people's memory I found out that this machine has a
> > PCI token ring card (which I wasn't using) because the on-board
> > ethernet went flaky. This certainly helps explain my intermitent
> > network, and quite possibly the short up-times before crashing. As we
> > guessed - a hardware problem.
> > 
> > Is there any way (jumper ?) to disable the onboard ethernet? I may try
> > not loading the modules for it and see if the machine becomes stable.
> > Would a standard PCI ethernet card work as a substitute (likely won't
> > netboot)?
> 
> I checked the machine's docs - there appears to be no jumper to
> disable the onboard ethernet. However, If I simply unplug the ethernet
> cable the instability seems to diappear. The machine just did a
> flawless install booting from Leigh's disk, Woody root on a floppy and
> base on cd-rom.

What about d-i or a debian kernel ? I will make a new upload of the powerpc
kernel this weekend, and if there is a fix needed for 43P-140, i would like to
fix it before that.

> I have a PCI ethernet card left over from an old PentiumPro. It says
> it is a 3Com "Fast EtherLink XL PCI" "3C905-TX". Would this card work
> in this machine? Would it be able to netboot (doubtfull).

Not sure if you need a forth-rom enabled card or not. I plugged a cheap
realtek card in the powerstack, but it didn't even appear in lspci, but that
was before the pci irq remapping, so ...

Friendly,

Sven Luther

Re: 43p-140 install issues

[Ulrich Teichert]

Hi,

>[snip]
>> There may be some problems with 2.6 kernels and pci irqs on prep. I will
>> investigate this shortly.
>
>There is definitely something strange happening. The image I used to
>do the (nearly) complete install will no longer configure the network.
>Very inconsistent. I will try it (same image) again later today and
>see if it "just works" next time - like it did last time.

Yes, I've seen inconsistencies as well, like booting the default kernel
from a sarge CD worked *once* and rebooting not. I found out why:
during the first cold boot, the firmware asks if it should make my
serial console the active console (which I acknowledged), but with a
warm boot, this question is not asked again.

This seems to result in a different setting and the kernel is not able
to figure out that it is running on a serial console. According to Leigh
Browns, it is not possible to give the kernel parameters on boot-up, unless
you are using his patches, so this may be another issue.

But this is how far the default kernel (which is all I can load from CD)
boots:

0 > setenv load-base 1000000  ok
0 > setenv real-base c00000  ok
0 > boot cdrom: 

loaded at:     01000400 01492FF4
relocated to:  00800000 00C92BF4
zimage at:     0080A94C 0093E3DC
initrd at:     0093F000 00C884AE
avail ram:     00400000 00800000

Linux/PPC load: console=ttyS0,9600 console=tty0
Uncompressing Linux...done.
Now booting the kernel
Total memory = 256MB; using 512kB for hash table (at c0300000)
Linux version 2.6.8-powerpc (sven@pegasos2) (version gcc 3.3.5 (Debian 1:3.3.5-2)) #1 Thu Dec 9 10:27:54 CET 2004
PReP architecture
IBM planar ID: 000000d5
MPIC at 0xfddc0000 (0x3ddc0000), length 0x00040000 mapped to 0xeffc0000
Built 1 zonelists
Kernel command line: console=ttyS0,9600 console=tty0
OpenPIC Version 1.0 (4 CPUs and 16 IRQ sources) at effc0000
PID hash table entries: 2048 (order 11: 16384 bytes)
time_init: decrementer frequency = 16.618715 MHz
Console: colour dummy device 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 252416k available (1732k kernel code, 1060k data, 164k init, 0k highmem)
Calibrating delay loop... 397.31 BogoMIPS
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 3365k freed
NET: Registered protocol family 16
PCI: Probing PCI hardware
Setting PCI interrupts for a "IBM 43P-140 (Tiger1)"
PCI: Cannot allocate resource region 0 of device 0000:00:0b.0
PCI: Cannot allocate resource region 0 of device 0000:00:0c.0
PCI: Cannot allocate resource region 0 of device 0000:00:10.0
PCI: Cannot allocate resource region 0 of device 0000:00:12.0
Thermal assist unit not available
audit: initializing netlink socket (disabled)
audit(943920606.514:0): initialized
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x0
Initializing Cryptographic API
Generic RTC Driver v1.07
Macintosh non-volatile memory driver v1.1
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
pmac_zilog: 0.6 (Benjamin Herrenschmidt <benh@kernel.crashing.org>)
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
input: Macintosh mouse button emulation
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP: Hash tables configured (established 16384 bind 32768)
RAMDISK: Compressed image found at block 0
VFS: Mounted root (cramfs filesystem) readonly.
VFS: Cannot open root device "<NULL>" or unknown-block(8,3)
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on unknown-block(8,3)
 <0>Rebooting in 180 seconds..

[del]
>> Then i suppose that copying the kernel is just a matter of :
>> 
>>   dd if=/boot/vmlinuz-2.6.8-powerpc of=/dev/sdb1
>> 
>> but you have to have a small prep partition as /dev/sdb1, or the above will
>> erase whatever you have on /dev/sdb1.

This is not enough. You need to set the kernel arguments with Leigh's
preptool (which is a simple perl script), because of the problems mentioned
before.

>I' have the partition ready ...
>
>Unfortunately, until the network comes back up, I can't get far enough
>in the install to access the SCSI drives (is there another way? Load
>the modules by hand? Which ones?). Without this, I can't get at the
>image I need to boot in order to get it onto the right partition. I
>also can't get it to another machine to net boot it.

All this initrd thing is a mess when it gets complicated, if you ask me.
I really don't know why your floppy stops working after booting Leighs
kernel. But on the other hand, I don't know why I can't netboot my box
either - I can netboot anything else from DECstations to SGIs with the
same setup, but my 7043-44 refuses to load the kernel. It contacts the
server, figures out the name of the file, but does not request it.

For your network trouble, try to disconnect power from the box completely
for an hour or so. This was enough for my box to fall back to asking me
for the active console, maybe this works for your flaky network as well?

HTH,
Uli
-- 
Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert@gmx.de
Stormweg 24               |listening to: Suicide Drive (The Deep Eynde)
24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)

Re: 43p-140 install issues

[Leigh Brown]

Ulrich Teichert said:
>>[snip]
>>> There may be some problems with 2.6 kernels and pci irqs on prep. I
>>> will
>>> investigate this shortly.
>>
>>There is definitely something strange happening. The image I used to
>>do the (nearly) complete install will no longer configure the network.
>>Very inconsistent. I will try it (same image) again later today and
>>see if it "just works" next time - like it did last time.
>
> Yes, I've seen inconsistencies as well, like booting the default kernel
> from a sarge CD worked *once* and rebooting not. I found out why:
> during the first cold boot, the firmware asks if it should make my
> serial console the active console (which I acknowledged), but with a
> warm boot, this question is not asked again.

That's because the firmware will only ask that question if detects that
a mouse or keyboard is present/not present where it previously was/n't.

> This seems to result in a different setting and the kernel is not able
> to figure out that it is running on a serial console. According to Leigh
> Browns, it is not possible to give the kernel parameters on boot-up,
> unless you are using his patches, so this may be another issue.

I have a patch you can use to specify parameters on the *command line*
(e.g. boot floppy: root=/dev/sda3 ...).  However, you can always type
parameters on the serial console as it boots (see below).

> But this is how far the default kernel (which is all I can load from CD)
> boots:
>
> 0 > setenv load-base 1000000  ok
> 0 > setenv real-base c00000  ok
> 0 > boot cdrom:
>
> loaded at:     01000400 01492FF4
> relocated to:  00800000 00C92BF4
> zimage at:     0080A94C 0093E3DC
> initrd at:     0093F000 00C884AE
> avail ram:     00400000 00800000
>
> Linux/PPC load: console=ttyS0,9600 console=tty0

*** This is the point you get 5 seconds to start editing the parameters.
I guess if you specify root=/dev/ram0 or something then it will boot
from the ramdisk, rather than trying to boot from /dev/sda3.

> Uncompressing Linux...done.
> Now booting the kernel
> Total memory = 256MB; using 512kB for hash table (at c0300000)
> Linux version 2.6.8-powerpc (sven@pegasos2) (version gcc 3.3.5 (Debian
> 1:3.3.5-2)) #1 Thu Dec 9 10:27:54 CET 2004
> PReP architecture
[...]
> VFS: Cannot open root device "<NULL>" or unknown-block(8,3)
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on unknown-block(8,3)
>  <0>Rebooting in 180 seconds..

Other than that, it's a nice clean boot.

> [del]
>>> Then i suppose that copying the kernel is just a matter of :
>>>
>>>   dd if=/boot/vmlinuz-2.6.8-powerpc of=/dev/sdb1
>>>
>>> but you have to have a small prep partition as /dev/sdb1, or the above
>>> will
>>> erase whatever you have on /dev/sdb1.
>
> This is not enough. You need to set the kernel arguments with Leigh's
> preptool (which is a simple perl script), because of the problems
> mentioned before.

Well, you need to have my patch for that.  There are other ways to
manually change the boot arguments (like hexedit etc).

>>I' have the partition ready ...
>>
>>Unfortunately, until the network comes back up, I can't get far enough
>>in the install to access the SCSI drives (is there another way? Load
>>the modules by hand? Which ones?). Without this, I can't get at the
>>image I need to boot in order to get it onto the right partition. I
>>also can't get it to another machine to net boot it.
>
> All this initrd thing is a mess when it gets complicated, if you ask me.
> I really don't know why your floppy stops working after booting Leighs
> kernel. But on the other hand, I don't know why I can't netboot my box
> either - I can netboot anything else from DECstations to SGIs with the
> same setup, but my 7043-44 refuses to load the kernel. It contacts the
> server, figures out the name of the file, but does not request it.
>
> For your network trouble, try to disconnect power from the box completely
> for an hour or so. This was enough for my box to fall back to asking me
> for the active console, maybe this works for your flaky network as well?

It should never ask the console question again unless you change the
config (plug in a mouse for example), unless your nvram battery is a
bit flat of course!

Re: 43p-140 install issues

[Sven Luther]

On Mon, Jan 03, 2005 at 04:50:00PM -0000, Leigh Brown wrote:
> Ulrich Teichert said:
> > This seems to result in a different setting and the kernel is not able
> > to figure out that it is running on a serial console. According to Leigh
> > Browns, it is not possible to give the kernel parameters on boot-up,
> > unless you are using his patches, so this may be another issue.
> 
> I have a patch you can use to specify parameters on the *command line*
> (e.g. boot floppy: root=/dev/sda3 ...).  However, you can always type
> parameters on the serial console as it boots (see below).

Mmm, is this one already present in the debian 2.6.8 kernel packages ? If not
we would probably want to include it. I am currently preparing a bunch of prep
patches, so it is a good idea to include this one too. How is it related to
the below command line prompt thingy ...

> > But this is how far the default kernel (which is all I can load from CD)
> > boots:
> >
> > 0 > setenv load-base 1000000  ok
> > 0 > setenv real-base c00000  ok
> > 0 > boot cdrom:
> >
> > loaded at:     01000400 01492FF4
> > relocated to:  00800000 00C92BF4
> > zimage at:     0080A94C 0093E3DC
> > initrd at:     0093F000 00C884AE
> > avail ram:     00400000 00800000
> >
> > Linux/PPC load: console=ttyS0,9600 console=tty0

... This one i mean.

> *** This is the point you get 5 seconds to start editing the parameters.
> I guess if you specify root=/dev/ram0 or something then it will boot
> from the ramdisk, rather than trying to boot from /dev/sda3.

d-i is perfectly happy to just boot without any argument.

> > Uncompressing Linux...done.
> > Now booting the kernel
> > Total memory = 256MB; using 512kB for hash table (at c0300000)
> > Linux version 2.6.8-powerpc (sven@pegasos2) (version gcc 3.3.5 (Debian
> > 1:3.3.5-2)) #1 Thu Dec 9 10:27:54 CET 2004
> > PReP architecture
> [...]
> > VFS: Cannot open root device "<NULL>" or unknown-block(8,3)
> > Please append a correct "root=" boot option
> > Kernel panic: VFS: Unable to mount root fs on unknown-block(8,3)
> >  <0>Rebooting in 180 seconds..
> 
> Other than that, it's a nice clean boot.

Indeed.

> > [del]
> >>> Then i suppose that copying the kernel is just a matter of :
> >>>
> >>>   dd if=/boot/vmlinuz-2.6.8-powerpc of=/dev/sdb1
> >>>
> >>> but you have to have a small prep partition as /dev/sdb1, or the above
> >>> will
> >>> erase whatever you have on /dev/sdb1.
> >
> > This is not enough. You need to set the kernel arguments with Leigh's
> > preptool (which is a simple perl script), because of the problems
> > mentioned before.
> 
> Well, you need to have my patch for that.  There are other ways to
> manually change the boot arguments (like hexedit etc).

Could you post it ? Anything else you are aware that we should add in our
2.6.8 powerpc kernels which is PReP related ? 

Friendly,

Sven Luther

Re: 43p-140 install issues

[Ulrich Teichert]

Hi,

[del]
>> Linux/PPC load: console=ttyS0,9600 console=tty0
>
>*** This is the point you get 5 seconds to start editing the parameters.
>I guess if you specify root=/dev/ram0 or something then it will boot
>from the ramdisk, rather than trying to boot from /dev/sda3.

Right, now I can even boot over network:

0 > setenv load-base 1000000  ok
0 > setenv real-base c00000  ok
0 > boot net: 
LOAD: Waiting 60 seconds for Spanning Tree
BOOTP R = 1 BOOTP S = 1  
FILE: /tftpboot/wehrle/vmlinuz-prep.initrd
Load Addr=0x1000000 Max Size=0xf000000 
Packet Count = 100 [snipped the packet count lines]

loaded at:     01000400 01554FF4
relocated to:  00800000 00D54BF4
zimage at:     0080A94C 0093DC0A
initrd at:     0093E000 00D4AB7A
avail ram:     00400000 00800000

Linux/PPC load: console=ttyS0,9600 console=tty0 root=/dev/ram
Uncompressing Linux...done.
Now booting the kernel
Total memory = 256MB; using 512kB for hash table (at c0300000)
Linux version 2.6.8-powerpc (jens@yorick) (gcc version 3.3.4 (Debian 1:3.3.4-11)) #1 Sun Oct 3 13:22:21 CEST 2004
PReP architecture
IBM planar ID: 000000d5
MPIC at 0xfddc0000 (0x3ddc0000), length 0x00040000 mapped to 0xeffc0000
Built 1 zonelists
Kernel command line: console=ttyS0,9600 console=tty0 root=/dev/ram
OpenPIC Version 1.0 (4 CPUs and 16 IRQ sources) at effc0000
PID hash table entries: 2048 (order 11: 16384 bytes)
time_init: decrementer frequency = 16.618701 MHz
Console: colour dummy device 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 251648k available (1732k kernel code, 1060k data, 164k init, 0k highmem)
Calibrating delay loop... 397.31 BogoMIPS
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 4146k freed
NET: Registered protocol family 16
PCI: Probing PCI hardware
Setting PCI interrupts for a "IBM 43P-140 (Tiger1)"
PCI: Cannot allocate resource region 0 of device 0000:00:0b.0
PCI: Cannot allocate resource region 0 of device 0000:00:0c.0
PCI: Cannot allocate resource region 0 of device 0000:00:10.0
PCI: Cannot allocate resource region 0 of device 0000:00:12.0
Thermal assist unit not available
audit: initializing netlink socket (disabled)
audit(943920304.671:0): initialized
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x0
Initializing Cryptographic API
Generic RTC Driver v1.07
Macintosh non-volatile memory driver v1.1
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
pmac_zilog: 0.6 (Benjamin Herrenschmidt <benh@kernel.crashing.org>)
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
input: Macintosh mouse button emulation
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP: Hash tables configured (established 16384 bind 32768)
RAMDISK: Compressed image found at block 0
VFS: Mounted root (cramfs filesystem) readonly.
Freeing unused kernel memory: 164k init 60k pmac 4k chrp 8k openfirmware
NET: Registered protocol family 1

And that's it. Seems like the d-i doesn't know that it should use the
serial console. BTW, the instructions for booting PREP systems in the
debian installation manual aren't quite right, they are missing the
"net:" string. If the TFTP-server is setup right, the firmware can figure
out the rest, so giving the server IP, the name and the IP should not
be necessary and I would try `boot net:` first.

[del]
>It should never ask the console question again unless you change the
>config (plug in a mouse for example), unless your nvram battery is a
>bit flat of course!

This seems to be the case. But it really simplifies things, as I've never
been able to warm-boot anything ;-) Only a cold boot helps. Maybe Daniel
should remove the battery to reset things completely?

Anyway, without your site, Leigh, I would still have a big doorstop only,
thanks again,

CU,
Uli
-- 
Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert@gmx.de
Stormweg 24               |listening to: Suicide Drive (The Deep Eynde)
24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)

Re: 43p-140 install issues

[Leigh Brown]

Ulrich Teichert said:
[...]
> Linux/PPC load: console=ttyS0,9600 console=tty0 root=/dev/ram

Delete the "console=tty0", so you end up with:

 Linux/PPC load: console=ttyS0,9600 root=/dev/ram

and try again!

[...]
>>It should never ask the console question again unless you change the
>>config (plug in a mouse for example), unless your nvram battery is a
>>bit flat of course!
>
> This seems to be the case. But it really simplifies things, as I've never
> been able to warm-boot anything ;-) Only a cold boot helps. Maybe Daniel
> should remove the battery to reset things completely?
>
> Anyway, without your site, Leigh, I would still have a big doorstop only,
> thanks again,

No problem.  The amazing thing is, once you actually get them running,
RS/6000's run Linux really reliably.  It's getting them booting that's
the problem :-/

Re: 43p-140 install issues

[Ulrich Teichert]

Hi,

>Delete the "console=tty0", so you end up with:
>
> Linux/PPC load: console=ttyS0,9600 root=/dev/ram
>
>and try again!
[del]

Right, then the installer knows what to do. I think this should go into
the Debian installation docs, there are a lot of boxes with graphic cards
out which are not supported by Linux.

But the low level SCSI-driver is missing in this image, or any low level
SCSI drivers for that matter. There are only the high level modules there,
like sd_mod.ko and sr_mod.ko:

Nov 30 00:06:32 hw-detect: Using discover version 1.
Nov 30 00:06:35 hw-detect: Detecting hardware...
Nov 30 00:06:36 hw-detect: Missing module 'sym53c8xx'.
Nov 30 00:06:36 hw-detect: Missing module 'usb-storage'.
Nov 30 00:06:36 hw-detect: Missing module 'ide-mod'.
Nov 30 00:06:36 hw-detect: Missing module 'ide-probe-mod'.
Nov 30 00:06:36 hw-detect: Missing module 'ide-detect'.
Nov 30 00:06:36 hw-detect: Missing module 'ide-generic'.
Nov 30 00:06:37 hw-detect: Missing module 'ide-floppy'.
--More-- (57% of 44385 bytes)                             Nov 30 00:06:37 hw-detect: Missing module 'ide-disk'.
Nov 30 00:06:37 hw-detect: Missing module 'isofs'.
Nov 30 00:06:37 hw-detect: Loading modules...
Nov 30 00:06:37 hw-detect: Detected module 'pcnet32' for 'Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE]'
Nov 30 00:06:37 hw-detect: Trying to load module 'pcnet32'
Nov 30 00:06:37 kernel: pcnet32.c:v1.30i 06.28.2004 tsbogend@alpha.franken.de
Nov 30 00:06:37 kernel: PCI: Enabling device 0000:00:0c.0 (0000 -> 0003)
Nov 30 00:06:37 kernel: pcnet32: PCnet/PCI II 79C970A at 0x1020, 00 06 29 2e 98 9d assigned IRQ 22.
Nov 30 00:06:37 kernel: divert: allocating divert_blk for eth0
Nov 30 00:06:37 kernel: eth0: registered as PCnet/PCI II 79C970A
Nov 30 00:06:37 kernel: pcnet32: 1 cards_found.
Nov 30 00:06:38 hw-detect: Detected module 'floppy' for 'Linux Floppy'
Nov 30 00:06:38 hw-detect: Trying to load module 'floppy'
Nov 30 00:06:38 kernel: inserting floppy driver for 2.6.8-powerpc
Nov 30 00:06:38 kernel: Using anticipatory io scheduler
Nov 30 00:06:38 kernel: Floppy drive(s): fd0 is 2.88M
Nov 30 00:06:38 kernel: FDC 0 is a National Semiconductor PC87306
Nov 30 00:06:38 hw-detect: Detected module 'ide-cd' for 'Linux ATAPI CD-ROM'
Nov 30 00:06:38 hw-detect: Trying to load module 'ide-cd'
Nov 30 00:06:39 kernel: Linux Kernel Card Services
Nov 30 00:06:39 kernel:   options:  [pci] [cardbus] [pm]
Nov 30 00:06:39 hw-detect: Starting PCMCIA services: using yenta_socket instead of i82365
Nov 30 00:06:39 hw-detect: cardmgr[1070]: no sockets found!
Nov 30 00:06:39 cardmgr[1070]: no sockets found!
Nov 30 00:06:39 hw-detect: done.
Nov 30 00:06:39 hw-detect: Detected discover version 1, installing discover1.
Nov 30 00:06:39 hw-detect: Detected hotplug support, installing hotplug.
Nov 30 00:06:40 hw-detect: Missing modules 'sym53c8xx (Symbios Logic Inc. / NCR 53c825), usb-storage (USB storage), ide-mod (Linux IDE driver), ide-probe-mod (Linux IDE probe driver), ide-detect (Linux IDE detection), ide-generic (Linux IDE support), ide-floppy (Linux IDE floppy), ide-disk (Linux ATA DISK), isofs (Linux ISO 9660 filesystem)

/lib/modules/2.6.8-powerpc/kernel/drivers/scsi # ls
scsi_mod.ko  sd_mod.ko    sr_mod.ko

So, either this is the wrong image (I've taken the same as Daniel mentioned
in one of his mails: http://debian.yorku.ca/debian/dists/testing/main/installer-powerpc/current/images/powerpc/netboot/vmlinuz-prep.initrd),
or it's missing some vital modules.

HTH,
Uli
-- 
Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert@gmx.de
Stormweg 24               |listening to: Suicide Drive (The Deep Eynde)
24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)

Re: 43p-140 install issues

[Sven Luther]

On Mon, Jan 03, 2005 at 11:11:06PM +0100, Ulrich Teichert wrote:
> Hi,
> 
> >Delete the "console=tty0", so you end up with:
> >
> > Linux/PPC load: console=ttyS0,9600 root=/dev/ram
> >
> >and try again!
> [del]
> 
> Right, then the installer knows what to do. I think this should go into
> the Debian installation docs, there are a lot of boxes with graphic cards
> out which are not supported by Linux.

Err, it should default to vga tedxt mode if the graphic card fbdev is not
builtin, at least it does it here.

> But the low level SCSI-driver is missing in this image, or any low level
> SCSI drivers for that matter. There are only the high level modules there,
> like sd_mod.ko and sr_mod.ko:

Sure, these should be loaded through the network. Try the
powerpc/cdrom/vmlinuz-prep.initrd for images with scsi modules included.

> Nov 30 00:06:32 hw-detect: Using discover version 1.
> Nov 30 00:06:35 hw-detect: Detecting hardware...
> Nov 30 00:06:36 hw-detect: Missing module 'sym53c8xx'.
> Nov 30 00:06:36 hw-detect: Missing module 'usb-storage'.
> Nov 30 00:06:36 hw-detect: Missing module 'ide-mod'.
> Nov 30 00:06:36 hw-detect: Missing module 'ide-probe-mod'.
> Nov 30 00:06:36 hw-detect: Missing module 'ide-detect'.
> Nov 30 00:06:36 hw-detect: Missing module 'ide-generic'.
> Nov 30 00:06:37 hw-detect: Missing module 'ide-floppy'.
> --More-- (57% of 44385 bytes)                             Nov 30 00:06:37 hw-detect: Missing module 'ide-disk'.
> Nov 30 00:06:37 hw-detect: Missing module 'isofs'.
> Nov 30 00:06:37 hw-detect: Loading modules...
> Nov 30 00:06:37 hw-detect: Detected module 'pcnet32' for 'Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE]'
> Nov 30 00:06:37 hw-detect: Trying to load module 'pcnet32'
> Nov 30 00:06:37 kernel: pcnet32.c:v1.30i 06.28.2004 tsbogend@alpha.franken.de
> Nov 30 00:06:37 kernel: PCI: Enabling device 0000:00:0c.0 (0000 -> 0003)
> Nov 30 00:06:37 kernel: pcnet32: PCnet/PCI II 79C970A at 0x1020, 00 06 29 2e 98 9d assigned IRQ 22.
> Nov 30 00:06:37 kernel: divert: allocating divert_blk for eth0
> Nov 30 00:06:37 kernel: eth0: registered as PCnet/PCI II 79C970A
> Nov 30 00:06:37 kernel: pcnet32: 1 cards_found.
> Nov 30 00:06:38 hw-detect: Detected module 'floppy' for 'Linux Floppy'
> Nov 30 00:06:38 hw-detect: Trying to load module 'floppy'
> Nov 30 00:06:38 kernel: inserting floppy driver for 2.6.8-powerpc
> Nov 30 00:06:38 kernel: Using anticipatory io scheduler
> Nov 30 00:06:38 kernel: Floppy drive(s): fd0 is 2.88M
> Nov 30 00:06:38 kernel: FDC 0 is a National Semiconductor PC87306
> Nov 30 00:06:38 hw-detect: Detected module 'ide-cd' for 'Linux ATAPI CD-ROM'
> Nov 30 00:06:38 hw-detect: Trying to load module 'ide-cd'
> Nov 30 00:06:39 kernel: Linux Kernel Card Services
> Nov 30 00:06:39 kernel:   options:  [pci] [cardbus] [pm]
> Nov 30 00:06:39 hw-detect: Starting PCMCIA services: using yenta_socket instead of i82365
> Nov 30 00:06:39 hw-detect: cardmgr[1070]: no sockets found!
> Nov 30 00:06:39 cardmgr[1070]: no sockets found!
> Nov 30 00:06:39 hw-detect: done.
> Nov 30 00:06:39 hw-detect: Detected discover version 1, installing discover1.
> Nov 30 00:06:39 hw-detect: Detected hotplug support, installing hotplug.
> Nov 30 00:06:40 hw-detect: Missing modules 'sym53c8xx (Symbios Logic Inc. / NCR 53c825), usb-storage (USB storage), ide-mod (Linux IDE driver), ide-probe-mod (Linux IDE probe driver), ide-detect (Linux IDE detection), ide-generic (Linux IDE support), ide-floppy (Linux IDE floppy), ide-disk (Linux ATA DISK), isofs (Linux ISO 9660 filesystem)
> 
> /lib/modules/2.6.8-powerpc/kernel/drivers/scsi # ls
> scsi_mod.ko  sd_mod.ko    sr_mod.ko
> 
> So, either this is the wrong image (I've taken the same as Daniel mentioned
> in one of his mails: http://debian.yorku.ca/debian/dists/testing/main/installer-powerpc/current/images/powerpc/netboot/vmlinuz-prep.initrd),
> or it's missing some vital modules.

Notice, the canonical address for the daily builds is : 

  http://people.debian.org/~luther/d-i/images/daily

Friendly,

Sven Luther

Re: 43p-140 install issues

[Leigh Brown]

Sven Luther said:
> On Mon, Jan 03, 2005 at 11:11:06PM +0100, Ulrich Teichert wrote:
>> Hi,
>>
>> >Delete the "console=tty0", so you end up with:
>> >
>> > Linux/PPC load: console=ttyS0,9600 root=/dev/ram
>> >
>> >and try again!
>> [del]
>>
>> Right, then the installer knows what to do. I think this should go into
>> the Debian installation docs, there are a lot of boxes with graphic
>> cards
>> out which are not supported by Linux.
>
> Err, it should default to vga tedxt mode if the graphic card fbdev is not
> builtin, at least it does it here.

The PReP specs says that the cards should be initialised to a
minimum resolution of 640x480 iirc.  The boot loader has code to
manually reprogram the card *back* into VGA text mode, but only
for a very limited number of cards.  So, if your card is not
supported by fbdev, and isn't one of the very few supported
cards in the boot loader, it simply won't work under PReP.

[...]

Cheers,

Leigh.

Re: 43p-140 install issues

[Sven Luther]

On Tue, Jan 04, 2005 at 10:39:15PM -0000, Leigh Brown wrote:
> Sven Luther said:
> > On Mon, Jan 03, 2005 at 11:11:06PM +0100, Ulrich Teichert wrote:
> >> Hi,
> >>
> >> >Delete the "console=tty0", so you end up with:
> >> >
> >> > Linux/PPC load: console=ttyS0,9600 root=/dev/ram
> >> >
> >> >and try again!
> >> [del]
> >>
> >> Right, then the installer knows what to do. I think this should go into
> >> the Debian installation docs, there are a lot of boxes with graphic
> >> cards
> >> out which are not supported by Linux.
> >
> > Err, it should default to vga tedxt mode if the graphic card fbdev is not
> > builtin, at least it does it here.
> 
> The PReP specs says that the cards should be initialised to a
> minimum resolution of 640x480 iirc.  The boot loader has code to
> manually reprogram the card *back* into VGA text mode, but only
> for a very limited number of cards.  So, if your card is not
> supported by fbdev, and isn't one of the very few supported
> cards in the boot loader, it simply won't work under PReP.

Ah, ok ... Well i have a cirrus logic card also, and it seems to work. I have
anot yet tried the matrox cards though. Do they need to be special cards with
forth rom, or will any do ? 

BTW, i have another question. I am trying to fix debian-installer to create
the prep partition, but i would like to have some info on the expected
constraints of said partition. Some tell it has to be entirely in the first
8MB, others the first 5MB, and my powerstack has a 17MB boot partition right
now.

I guess it is really not all that important what the size of the partition is,
it just needs to be first, and the kernel needs to fit in what the firmware
supports.

This goes for various prep boxes, but also for later IBM chrp machines,
including current pseries. It may be problematic, though if the size is too
small, as debian uses an initrd kernel, and altough the kernel itself is
rather small (around 1MB compressed), the current initrd generation method is
not all that fine-grained.

Ah, another thing. I am about to make a new kernel upload, which fixes the
powerstack II (utah) pci irq issue (backported from 2.6.10), but i hear about
problems with other systems, among them the popular 43p-140. Do you know of
any other patch that needs to be applied ? We use a 2.6.8 kernel as basis, so
the stuff will need to be backported, and i think i saw a bunch of prep fixes
in 2.6.9. What about the patches which enables prep-tool ? 

Friendly,

Sven Luther

Re: 43p-140 install issues

[Philippe Guyot]

On Wednesday 05 January 2005 10:03, Sven Luther wrote:
> On Tue, Jan 04, 2005 at 10:39:15PM -0000, Leigh Brown wrote:
> > Sven Luther said:
> > > On Mon, Jan 03, 2005 at 11:11:06PM +0100, Ulrich Teichert wrote:
> > >> Hi,
> > >>
> > >> >Delete the "console=tty0", so you end up with:
> > >> >
> > >> > Linux/PPC load: console=ttyS0,9600 root=/dev/ram
> > >> >
> > >> >and try again!
> > >>
> > >> [del]
> > >>
> > >> Right, then the installer knows what to do. I think this should go
> > >> into the Debian installation docs, there are a lot of boxes with
> > >> graphic cards
> > >> out which are not supported by Linux.
> > >
> > > Err, it should default to vga tedxt mode if the graphic card fbdev is
> > > not builtin, at least it does it here.
> >
> > The PReP specs says that the cards should be initialised to a
> > minimum resolution of 640x480 iirc.  The boot loader has code to
> > manually reprogram the card *back* into VGA text mode, but only
> > for a very limited number of cards.  So, if your card is not
> > supported by fbdev, and isn't one of the very few supported
> > cards in the boot loader, it simply won't work under PReP.
>
> Ah, ok ... Well i have a cirrus logic card also, and it seems to work. I
> have anot yet tried the matrox cards though. Do they need to be special
> cards with forth rom, or will any do ?



Well, my box seems to have a matrox video card and I did the install with my 
graphical console, not the tty.


>
> BTW, i have another question. I am trying to fix debian-installer to create
> the prep partition, but i would like to have some info on the expected
> constraints of said partition. Some tell it has to be entirely in the first
> 8MB, others the first 5MB, and my powerstack has a 17MB boot partition
> right now.


All I can say, it's that my boot PReP partition is the 1st and about 4 MB in 
size (cannot size it less than 1% of the disk.....)
second partition is /
third is swap.

That works for me.


>
> I guess it is really not all that important what the size of the partition
> is, it just needs to be first, and the kernel needs to fit in what the
> firmware supports.



>
> This goes for various prep boxes, but also for later IBM chrp machines,
> including current pseries. It may be problematic, though if the size is too
> small, as debian uses an initrd kernel, and altough the kernel itself is
> rather small (around 1MB compressed), the current initrd generation method
> is not all that fine-grained.
>
> Ah, another thing. I am about to make a new kernel upload, which fixes the
> powerstack II (utah) pci irq issue (backported from 2.6.10), but i hear
> about problems with other systems, among them the popular 43p-140. Do you
> know of any other patch that needs to be applied ? We use a 2.6.8 kernel as
> basis, so the stuff will need to be backported, and i think i saw a bunch
> of prep fixes in 2.6.9. What about the patches which enables prep-tool ?
>
> Friendly,
>
> Sven Luther

Re: 43p-140 install issues

[Leigh Brown]

Philippe Guyot said:
> On Wednesday 05 January 2005 10:03, Sven Luther wrote:
>> On Tue, Jan 04, 2005 at 10:39:15PM -0000, Leigh Brown wrote:
[...]
>> > The PReP specs says that the cards should be initialised to a
>> > minimum resolution of 640x480 iirc.  The boot loader has code to
>> > manually reprogram the card *back* into VGA text mode, but only
>> > for a very limited number of cards.  So, if your card is not
>> > supported by fbdev, and isn't one of the very few supported
>> > cards in the boot loader, it simply won't work under PReP.
>>
>> Ah, ok ... Well i have a cirrus logic card also, and it seems to work. I
>> have anot yet tried the matrox cards though. Do they need to be special
>> cards with forth rom, or will any do ?
>
> Well, my box seems to have a matrox video card and I did the install with
> my graphical console, not the tty.
[...]

That's because your Matrox card is fully supported by fbdev.

Cheers,

Leigh.

Re: 43p-140 install issues

[Sven Luther]

On Wed, Jan 05, 2005 at 10:49:19AM +0100, Philippe Guyot wrote:
> > BTW, i have another question. I am trying to fix debian-installer to create
> > the prep partition, but i would like to have some info on the expected
> > constraints of said partition. Some tell it has to be entirely in the first
> > 8MB, others the first 5MB, and my powerstack has a 17MB boot partition
> > right now.
> 
> 
> All I can say, it's that my boot PReP partition is the 1st and about 4 MB in 
> size (cannot size it less than 1% of the disk.....)
> second partition is /
> third is swap.

BTW, for debian, it makes more sense to have the second partition as swap, and
the third as /, i think, since it was decided some time back to default to
root=/dev/sda3, and not sda2.

> That works for me.

Until the kernel grows beyond 4MB.

Friendly,

Sven Luther

Re: 43p-140 install issues

[Philippe Guyot]

On Wednesday 05 January 2005 12:47, Sven Luther wrote:
> On Wed, Jan 05, 2005 at 10:49:19AM +0100, Philippe Guyot wrote:
> > > BTW, i have another question. I am trying to fix debian-installer to
> > > create the prep partition, but i would like to have some info on the
> > > expected constraints of said partition. Some tell it has to be entirely
> > > in the first 8MB, others the first 5MB, and my powerstack has a 17MB
> > > boot partition right now.
> >
> > All I can say, it's that my boot PReP partition is the 1st and about 4 MB
> > in size (cannot size it less than 1% of the disk.....)
> > second partition is /
> > third is swap.
>
> BTW, for debian, it makes more sense to have the second partition as swap,
> and the third as /, i think, since it was decided some time back to default
> to root=/dev/sda3, and not sda2.

Yes, I did that on my two 150.

>
> > That works for me.
>
> Until the kernel grows beyond 4MB.
>

Friendly.
Felipe

Re: 43p-140 install issues

[Hollis Blanchard]

On Jan 5, 2005, at 5:47 AM, Sven Luther wrote:

> On Wed, Jan 05, 2005 at 10:49:19AM +0100, Philippe Guyot wrote:
>>> BTW, i have another question. I am trying to fix debian-installer to 
>>> create
>>> the prep partition, but i would like to have some info on the 
>>> expected
>>> constraints of said partition. Some tell it has to be entirely in 
>>> the first
>>> 8MB, others the first 5MB, and my powerstack has a 17MB boot 
>>> partition
>>> right now.
>>
>> All I can say, it's that my boot PReP partition is the 1st and about 
>> 4 MB in
>> size (cannot size it less than 1% of the disk.....)
>> second partition is /
>> third is swap.
>
> BTW, for debian, it makes more sense to have the second partition as 
> swap, and
> the third as /, i think, since it was decided some time back to 
> default to
> root=/dev/sda3, and not sda2.
>
>> That works for me.
>
> Until the kernel grows beyond 4MB.

The size of that partition depends on firmware limitations. I have 
definitely seen reports of systems not booting when the PReP boot 
partition was too large. I think on some systems that has even happened 
at 8MB.

In other words, should you need more space than 4-5MB at some point in 
the future, you cannot simply make a bigger boot partition.

-Hollis

Re: 43p-140 install issues

[Sven Luther]

On Wed, Jan 05, 2005 at 09:45:13AM -0600, Hollis Blanchard wrote:
> On Jan 5, 2005, at 5:47 AM, Sven Luther wrote:
> 
> >On Wed, Jan 05, 2005 at 10:49:19AM +0100, Philippe Guyot wrote:
> >>>BTW, i have another question. I am trying to fix debian-installer to 
> >>>create
> >>>the prep partition, but i would like to have some info on the 
> >>>expected
> >>>constraints of said partition. Some tell it has to be entirely in 
> >>>the first
> >>>8MB, others the first 5MB, and my powerstack has a 17MB boot 
> >>>partition
> >>>right now.
> >>
> >>All I can say, it's that my boot PReP partition is the 1st and about 
> >>4 MB in
> >>size (cannot size it less than 1% of the disk.....)
> >>second partition is /
> >>third is swap.
> >
> >BTW, for debian, it makes more sense to have the second partition as 
> >swap, and
> >the third as /, i think, since it was decided some time back to 
> >default to
> >root=/dev/sda3, and not sda2.
> >
> >>That works for me.
> >
> >Until the kernel grows beyond 4MB.
> 
> The size of that partition depends on firmware limitations. I have 
> definitely seen reports of systems not booting when the PReP boot 
> partition was too large. I think on some systems that has even happened 
> at 8MB.

Is the problem really the size of the partition, or the space used by the
kernel. I mean we could make a 100MB partition at start, and since we just dd
the kernel to it, the kernel would be found at the start of the partition, and
the firmware probably doesn't care about the real size of the partition, as
long as it can access all the kernel data we dded to it, no ? 

Do we have some documentation of the firmware limitations ? 

> In other words, should you need more space than 4-5MB at some point in 
> the future, you cannot simply make a bigger boot partition.

8MB would be good, 4-5MB only would probably be a bit just.

Friendly,

Sven Luther

Re: 43p-140 install issues

[Philippe Guyot]

On Wednesday 05 January 2005 17:08, Sven Luther wrote:
> On Wed, Jan 05, 2005 at 09:45:13AM -0600, Hollis Blanchard wrote:
> > On Jan 5, 2005, at 5:47 AM, Sven Luther wrote:
> > >On Wed, Jan 05, 2005 at 10:49:19AM +0100, Philippe Guyot wrote:
> > >>>BTW, i have another question. I am trying to fix debian-installer to
> > >>>create
> > >>>the prep partition, but i would like to have some info on the
> > >>>expected
> > >>>constraints of said partition. Some tell it has to be entirely in
> > >>>the first
> > >>>8MB, others the first 5MB, and my powerstack has a 17MB boot
> > >>>partition
> > >>>right now.
> > >>
> > >>All I can say, it's that my boot PReP partition is the 1st and about
> > >>4 MB in
> > >>size (cannot size it less than 1% of the disk.....)
> > >>second partition is /
> > >>third is swap.
> > >
> > >BTW, for debian, it makes more sense to have the second partition as
> > >swap, and
> > >the third as /, i think, since it was decided some time back to
> > >default to
> > >root=/dev/sda3, and not sda2.
> > >
> > >>That works for me.
> > >
> > >Until the kernel grows beyond 4MB.
> >
> > The size of that partition depends on firmware limitations. I have
> > definitely seen reports of systems not booting when the PReP boot
> > partition was too large. I think on some systems that has even happened
> > at 8MB.
>
> Is the problem really the size of the partition, or the space used by the
> kernel. I mean we could make a 100MB partition at start, and since we just
> dd the kernel to it, the kernel would be found at the start of the
> partition, and the firmware probably doesn't care about the real size of
> the partition, as long as it can access all the kernel data we dded to it,
> no ?

I agree, see the IEEE P1275 on solinno's site. OF determines the load image 
length and transfers only that. I was able to verify that by dumping storage 
after a "load" when debugging boot process.

>
> Do we have some documentation of the firmware limitations ?

Yes, on solinnos's site.

>
> > In other words, should you need more space than 4-5MB at some point in
> > the future, you cannot simply make a bigger boot partition.
>
> 8MB would be good, 4-5MB only would probably be a bit just.
>

Clear.

Friendly.
Felipe

Re: 43p-140 install issues

[Hollis Blanchard]

On Jan 5, 2005, at 10:18 AM, Philippe Guyot wrote:
> On Wednesday 05 January 2005 17:08, Sven Luther wrote:
>> On Wed, Jan 05, 2005 at 09:45:13AM -0600, Hollis Blanchard wrote:
>>>
>>> The size of that partition depends on firmware limitations. I have
>>> definitely seen reports of systems not booting when the PReP boot
>>> partition was too large. I think on some systems that has even 
>>> happened
>>> at 8MB.
>>
>> Is the problem really the size of the partition, or the space used by 
>> the
>> kernel. I mean we could make a 100MB partition at start, and since we 
>> just
>> dd the kernel to it, the kernel would be found at the start of the
>> partition, and the firmware probably doesn't care about the real size 
>> of
>> the partition, as long as it can access all the kernel data we dded 
>> to it,
>> no ?
>
> I agree, see the IEEE P1275 on solinno's site. OF determines the load 
> image
> length and transfers only that. I was able to verify that by dumping 
> storage
> after a "load" when debugging boot process.

Are you specifically talking about booting from a PReP partition and 
not a floppy disk or netboot? Did you dump the bytes from the disk just 
after the kernel and see if they were also present in memory?

I have no doubt that OF will correctly load an ELF file, but a PReP 
boot partition does not contain an ELF file.

>> Do we have some documentation of the firmware limitations ?
>
> Yes, on solinnos's site.

That page (http://www.solinno.co.uk/7043-140/getstarted.php) doesn't 
mention any restrictions on the size of the PReP boot partition, so 
it's clearly not a complete list. :)

-Hollis

Re: 43p-140 install issues

[Leigh Brown]

Sven Luther said:
> On Wed, Jan 05, 2005 at 09:45:13AM -0600, Hollis Blanchard wrote:
>> On Jan 5, 2005, at 5:47 AM, Sven Luther wrote:
>> >On Wed, Jan 05, 2005 at 10:49:19AM +0100, Philippe Guyot wrote:
>> >>>BTW, i have another question. I am trying to fix debian-installer
>> >>>to create the prep partition, but i would like to have some info
>> >>>on the expected constraints of said partition. Some tell it has
>> >>>to be entirely in the first 8MB, others the first 5MB, and my
>> >>>powerstack has a 17MB boot partition right now.
>> >>
>> >>All I can say, it's that my boot PReP partition is the 1st and about
>> >>4 MB in size (cannot size it less than 1% of the disk.....)
>> >>second partition is /
>> >>third is swap.
>> >
>> >BTW, for debian, it makes more sense to have the second partition
>> >as swap, and the third as /, i think, since it was decided some
>> >time back to default to root=/dev/sda3, and not sda2.
>> >
>> >>That works for me.
>> >
>> >Until the kernel grows beyond 4MB.
>>
>> The size of that partition depends on firmware limitations. I have
>> definitely seen reports of systems not booting when the PReP boot
>> partition was too large. I think on some systems that has even happened
>> at 8MB.
>
> Is the problem really the size of the partition, or the space used by
> the kernel. I mean we could make a 100MB partition at start, and since
> we just dd the kernel to it, the kernel would be found at the start of
> the partition, and the firmware probably doesn't care about the real
> size of the partition, as long as it can access all the kernel data we
> added to it, no ?
>
> Do we have some documentation of the firmware limitations ?
>
>> In other words, should you need more space than 4-5MB at some point in
>> the future, you cannot simply make a bigger boot partition.
>
> 8MB would be good, 4-5MB only would probably be a bit just.

Surely if you make the default mkinitrd behaviour a bit more sensible
there won't be a problem.  A compressed 2.6 kernel is about 1.5MB, and
an initrd using MODULES=dep is about 1.5MB, which makes about 3MB,
giving a comfortable amount of space for future growth...

Cheers,

Leigh.

Re: 43p-140 install issues

[Sven Luther]

On Wed, Jan 05, 2005 at 04:30:05PM -0000, Leigh Brown wrote:
> Sven Luther said:
> > On Wed, Jan 05, 2005 at 09:45:13AM -0600, Hollis Blanchard wrote:
> >> On Jan 5, 2005, at 5:47 AM, Sven Luther wrote:
> >> >On Wed, Jan 05, 2005 at 10:49:19AM +0100, Philippe Guyot wrote:
> >> >>>BTW, i have another question. I am trying to fix debian-installer
> >> >>>to create the prep partition, but i would like to have some info
> >> >>>on the expected constraints of said partition. Some tell it has
> >> >>>to be entirely in the first 8MB, others the first 5MB, and my
> >> >>>powerstack has a 17MB boot partition right now.
> >> >>
> >> >>All I can say, it's that my boot PReP partition is the 1st and about
> >> >>4 MB in size (cannot size it less than 1% of the disk.....)
> >> >>second partition is /
> >> >>third is swap.
> >> >
> >> >BTW, for debian, it makes more sense to have the second partition
> >> >as swap, and the third as /, i think, since it was decided some
> >> >time back to default to root=/dev/sda3, and not sda2.
> >> >
> >> >>That works for me.
> >> >
> >> >Until the kernel grows beyond 4MB.
> >>
> >> The size of that partition depends on firmware limitations. I have
> >> definitely seen reports of systems not booting when the PReP boot
> >> partition was too large. I think on some systems that has even happened
> >> at 8MB.
> >
> > Is the problem really the size of the partition, or the space used by
> > the kernel. I mean we could make a 100MB partition at start, and since
> > we just dd the kernel to it, the kernel would be found at the start of
> > the partition, and the firmware probably doesn't care about the real
> > size of the partition, as long as it can access all the kernel data we
> > added to it, no ?
> >
> > Do we have some documentation of the firmware limitations ?
> >
> >> In other words, should you need more space than 4-5MB at some point in
> >> the future, you cannot simply make a bigger boot partition.
> >
> > 8MB would be good, 4-5MB only would probably be a bit just.
> 
> Surely if you make the default mkinitrd behaviour a bit more sensible
> there won't be a problem.  A compressed 2.6 kernel is about 1.5MB, and

The compressed kernel should be arounf 1.0MB only.

> an initrd using MODULES=dep is about 1.5MB, which makes about 3MB,
> giving a comfortable amount of space for future growth...

well, when i use MODULES=dep, i still get all the filesystem and a bunch of
extra ide drivers, so it is no less than 4MB. Mmm, you are right about this
one, it is only 1499136 now, which makes a total of 2856844, quite reasonable.
Mmm, i wonder it may even boot on the pegasos 1 with the broken OF now.

Still, partman-prep is currently written to make sure the prep partition is in
the first 8MB.

Friendly,

Sven Luther

Re: 43p-140 install issues

[Philippe Guyot]

On Monday 03 January 2005 05:15, Mike Martin wrote:
> Now I'm very confused .... on my next reboot ... the network wouldn't
> work. After much trial and error, I got the current unstable d-i image
> to work. It did it all right up to the reboot (where is warns you that
> it doesn't have a boot loader installed).
>
> Now what!
>
> I have an installed system, but I can't figure out how to boot it! I
> have /boot/vmlinux on /dev/sdb1 and a root on /dev/sdb1. How do I
> write a boot sector or tell OpenFirmware to boot from this file? I
> tried to netboot and set root=/dev/sdb1 - but without the scsi modules
> loaded it fails to read the drives and panics.
>
> I think I neet to create a type 41 PReP boot partition and get the
> kernel onto it. I've found this thread:
> http://lists.gnu.org/archive/html/bug-parted/2002-09/msg00016.html
>
> and this:
> http://www.yellowdoglinux.com/support/solutions/champion_server/rs6k.shtml
>
> I tried booting up with the installer, going to a shell after the scsi
> was active and the installed system was mounted. I used sfdisk from
> /target/sbin to create a 10 Meg type 41 partition on the first HD
> (/dev/sdb0 eventually). I used dd to copy /target/boot/vmlinux to this
> partition. But it still won't boot.


I succeeded last year to install a woody on a 143P-140 whith the help of Leigh 
Brown (thanks to him again). And two 150 whit sarge also.

I'm not sure, but I have the feeling that your image on the prep partition 
(should be type 0x41) is not able to determine where the root is, so Leigh 
did a piece of code named "preptools" in order to patch the image with the 
location of root.

To see if this can help, can you boot from openfirmware (BTW, is it the last 
version? and have you updated the load_base and real-base values?) with this 
parameter ?
     boot disk root=/dev/whatever_root_sda_is 

Hope this helps.

>
> I'm very close. If I can get the system to boot (really it needs to
> boot itself - not netboot) I'd call this a success.
>
> Thanks!
> MikeM
>
> On Sat, 1 Jan 2005 20:15:13 -0500, Mike Martin <sydneymartin@gmail.com> 
wrote:
> > I can boot with this image:
> > http://debian.yorku.ca/debian/dists/testing/main/installer-powerpc/curren
> >t/images/powerpc/netboot/vmlinuz-prep.initrd
> >
> > And things seems to go very well. Network configures, hard drives
> > partition, it dies at "Install the base system"  with "The debootstrap
> > program exited with an error (return value 255)." It instructs me to
> > check /var/log/messages which now contains: "execv: No such file or
> > directory"
> >
> > The previous step, partitioning, added:
> >   "No matching physical volumes found
> >   No volume groups found
> >   Reading all physical volumes.  This may take a while..."
> >
> > Anyone?
> >
> > MikeMartin
> >
> > On Sat, 1 Jan 2005 17:57:58 +0100, Sven Luther <sven.luther@wanadoo.fr> 
wrote:
> > > On Sat, Jan 01, 2005 at 05:30:25PM +0100, Ulrich Teichert wrote:
> > > > Hi,
> > > >
> > > > [del]
> > > >
> > > > >I would prefer that we fix the debian kernels for them to work
> > > > > correctly though. More on this on monday.
> > > >
> > > > I failed to configure a stock 2.4.28 kernel to detect the SCSI
> > > > controler. I think some of Leigh patches for this must be applied,
> > > > but I haven't gone any further.
> > >
> > > I had some report on a power3 box, that only the SMP sym53c8xx driver
> > > worked. When configuring in UP mode,
> > >
> > > > [del]
> > > >
> > > > >Do the debian 2.4.27 kernel work on it ? I was unable to boot the
> > > > > 2.4.27 d-i kernel on my powerstack, but this is a different
> > > > > machine, so the issues may be a bit different.
> > > >
> > > > I've only tried the Woody PREP kernel, which failed in a way which I
> > > > can't remember, but I'll give it a try.
> > >
> > > Yes, please, i would greatly appreciate it, preferably the 2.6.8 kernel
> > > too. Let' try to get this fixed before the sarge release, which is not
> > > so far off now.
> > >
> > > Friendly,
> > >
> > > Sven Luther

Re: 43p-140 install issues

[Sven Luther]

On Mon, Jan 03, 2005 at 10:56:30AM +0100, Philippe Guyot wrote:
> On Monday 03 January 2005 05:15, Mike Martin wrote:
> > Now I'm very confused .... on my next reboot ... the network wouldn't
> > work. After much trial and error, I got the current unstable d-i image
> > to work. It did it all right up to the reboot (where is warns you that
> > it doesn't have a boot loader installed).
> >
> > Now what!
> >
> > I have an installed system, but I can't figure out how to boot it! I
> > have /boot/vmlinux on /dev/sdb1 and a root on /dev/sdb1. How do I
> > write a boot sector or tell OpenFirmware to boot from this file? I
> > tried to netboot and set root=/dev/sdb1 - but without the scsi modules
> > loaded it fails to read the drives and panics.
> >
> > I think I neet to create a type 41 PReP boot partition and get the
> > kernel onto it. I've found this thread:
> > http://lists.gnu.org/archive/html/bug-parted/2002-09/msg00016.html
> >
> > and this:
> > http://www.yellowdoglinux.com/support/solutions/champion_server/rs6k.shtml
> >
> > I tried booting up with the installer, going to a shell after the scsi
> > was active and the installed system was mounted. I used sfdisk from
> > /target/sbin to create a 10 Meg type 41 partition on the first HD
> > (/dev/sdb0 eventually). I used dd to copy /target/boot/vmlinux to this
> > partition. But it still won't boot.
> 
> 
> I succeeded last year to install a woody on a 143P-140 whith the help of Leigh 
> Brown (thanks to him again). And two 150 whit sarge also.
> 
> I'm not sure, but I have the feeling that your image on the prep partition 
> (should be type 0x41) is not able to determine where the root is, so Leigh 
> did a piece of code named "preptools" in order to patch the image with the 
> location of root.

Hey, cool, where is this tool ? We need to package it for debian if it is not
already, and use it in d-i, and maybe even mkvmlinuz directly.

Friendly,

Sven Luther

Re: 43p-140 install issues

[Philippe Guyot]

On Monday 03 January 2005 11:48, Sven Luther wrote:
> On Mon, Jan 03, 2005 at 10:56:30AM +0100, Philippe Guyot wrote:
> > On Monday 03 January 2005 05:15, Mike Martin wrote:
> > > Now I'm very confused .... on my next reboot ... the network wouldn't
> > > work. After much trial and error, I got the current unstable d-i image
> > > to work. It did it all right up to the reboot (where is warns you that
> > > it doesn't have a boot loader installed).
> > >
> > > Now what!
> > >
> > > I have an installed system, but I can't figure out how to boot it! I
> > > have /boot/vmlinux on /dev/sdb1 and a root on /dev/sdb1. How do I
> > > write a boot sector or tell OpenFirmware to boot from this file? I
> > > tried to netboot and set root=/dev/sdb1 - but without the scsi modules
> > > loaded it fails to read the drives and panics.
> > >
> > > I think I neet to create a type 41 PReP boot partition and get the
> > > kernel onto it. I've found this thread:
> > > http://lists.gnu.org/archive/html/bug-parted/2002-09/msg00016.html
> > >
> > > and this:
> > > http://www.yellowdoglinux.com/support/solutions/champion_server/rs6k.sh
> > >tml
> > >
> > > I tried booting up with the installer, going to a shell after the scsi
> > > was active and the installed system was mounted. I used sfdisk from
> > > /target/sbin to create a 10 Meg type 41 partition on the first HD
> > > (/dev/sdb0 eventually). I used dd to copy /target/boot/vmlinux to this
> > > partition. But it still won't boot.
> >
> > I succeeded last year to install a woody on a 143P-140 whith the help of
> > Leigh Brown (thanks to him again). And two 150 whit sarge also.
> >
> > I'm not sure, but I have the feeling that your image on the prep
> > partition (should be type 0x41) is not able to determine where the root
> > is, so Leigh did a piece of code named "preptools" in order to patch the
> > image with the location of root.
>
> Hey, cool, where is this tool ? We need to package it for debian if it is
> not already, and use it in d-i, and maybe even mkvmlinuz directly.
>

Just over there....

http://www.solinno.co.uk/7043-140/downloads.php
But ask Leigh for details.


Friendly.
Felipe

Re: 43p-140 install issues

[Sven Luther]

On Mon, Jan 03, 2005 at 11:56:07AM +0100, Philippe Guyot wrote:
> On Monday 03 January 2005 11:48, Sven Luther wrote:
> > On Mon, Jan 03, 2005 at 10:56:30AM +0100, Philippe Guyot wrote:
> > > On Monday 03 January 2005 05:15, Mike Martin wrote:
> > > > Now I'm very confused .... on my next reboot ... the network wouldn't
> > > > work. After much trial and error, I got the current unstable d-i image
> > > > to work. It did it all right up to the reboot (where is warns you that
> > > > it doesn't have a boot loader installed).
> > > >
> > > > Now what!
> > > >
> > > > I have an installed system, but I can't figure out how to boot it! I
> > > > have /boot/vmlinux on /dev/sdb1 and a root on /dev/sdb1. How do I
> > > > write a boot sector or tell OpenFirmware to boot from this file? I
> > > > tried to netboot and set root=/dev/sdb1 - but without the scsi modules
> > > > loaded it fails to read the drives and panics.
> > > >
> > > > I think I neet to create a type 41 PReP boot partition and get the
> > > > kernel onto it. I've found this thread:
> > > > http://lists.gnu.org/archive/html/bug-parted/2002-09/msg00016.html
> > > >
> > > > and this:
> > > > http://www.yellowdoglinux.com/support/solutions/champion_server/rs6k.sh
> > > >tml
> > > >
> > > > I tried booting up with the installer, going to a shell after the scsi
> > > > was active and the installed system was mounted. I used sfdisk from
> > > > /target/sbin to create a 10 Meg type 41 partition on the first HD
> > > > (/dev/sdb0 eventually). I used dd to copy /target/boot/vmlinux to this
> > > > partition. But it still won't boot.
> > >
> > > I succeeded last year to install a woody on a 143P-140 whith the help of
> > > Leigh Brown (thanks to him again). And two 150 whit sarge also.
> > >
> > > I'm not sure, but I have the feeling that your image on the prep
> > > partition (should be type 0x41) is not able to determine where the root
> > > is, so Leigh did a piece of code named "preptools" in order to patch the
> > > image with the location of root.
> >
> > Hey, cool, where is this tool ? We need to package it for debian if it is
> > not already, and use it in d-i, and maybe even mkvmlinuz directly.
> >
> 
> Just over there....
> 
> http://www.solinno.co.uk/7043-140/downloads.php
> But ask Leigh for details.

Ok, thanks. ...

Friendly,

Sven Luther

Re: 43p-140 install issues

[Michael Schmitz]

> > > > is, so Leigh did a piece of code named "preptools" in order to patch the
> > > > image with the location of root.
> > >
> > > Hey, cool, where is this tool ? We need to package it for debian if it is
> > > not already, and use it in d-i, and maybe even mkvmlinuz directly.
> > >
> >
> > Just over there....
> >
> > http://www.solinno.co.uk/7043-140/downloads.php
> > But ask Leigh for details.
>
> Ok, thanks. ...

Do we need that added to powerpc-utils perhaps?

	Michael

Re: 43p-140 install issues

[Sven Luther]

On Mon, Jan 03, 2005 at 12:57:35PM +0100, Michael Schmitz wrote:
> > > > > is, so Leigh did a piece of code named "preptools" in order to patch the
> > > > > image with the location of root.
> > > >
> > > > Hey, cool, where is this tool ? We need to package it for debian if it is
> > > > not already, and use it in d-i, and maybe even mkvmlinuz directly.
> > > >
> > >
> > > Just over there....
> > >
> > > http://www.solinno.co.uk/7043-140/downloads.php
> > > But ask Leigh for details.
> >
> > Ok, thanks. ...
> 
> Do we need that added to powerpc-utils perhaps?

Whatever is powerpc-utils ? Mmm, maybe, but then maybe mkvmlinuz would benefit
from being added there too, not sure. In any way i believe it has more its
place inside mkvmlinuz, than inside the more userland powerpc-utils.

Friendly,

Sven Luther

Re: 43p-140 install issues

[Michael Schmitz]

> > > > http://www.solinno.co.uk/7043-140/downloads.php
> > > > But ask Leigh for details.
> > >
> > > Ok, thanks. ...
> >
> > Do we need that added to powerpc-utils perhaps?
>
> Whatever is powerpc-utils ? Mmm, maybe, but then maybe mkvmlinuz would benefit

WTF is mkvmlinuz?

> from being added there too, not sure. In any way i believe it has more its
> place inside mkvmlinuz, than inside the more userland powerpc-utils.

Whatever. Just thought people might want to use it to change kernel
options on the fly, without invoking mkvmlinuz.

	Michael

Re: 43p-140 install issues

[Sven Luther]

On Mon, Jan 03, 2005 at 04:24:40PM +0100, Michael Schmitz wrote:
> > > > > http://www.solinno.co.uk/7043-140/downloads.php
> > > > > But ask Leigh for details.
> > > >
> > > > Ok, thanks. ...
> > >
> > > Do we need that added to powerpc-utils perhaps?
> >
> > Whatever is powerpc-utils ? Mmm, maybe, but then maybe mkvmlinuz would benefit
> 
> WTF is mkvmlinuz?

mkvmlinuz is a nice little kernel-derived tool by Jens and me, which allows
one to create a zImage.chrp, or zImage.coff or whatever, from the
arch/ppc/boot/* stuff and the plain vmlinux kernel. It avoids having to chip
the same kernel X times as we did on 2.4 kernels, and can be used as a
kernel-package postinst hook to automate this process.

> > from being added there too, not sure. In any way i believe it has more its
> > place inside mkvmlinuz, than inside the more userland powerpc-utils.
> 
> Whatever. Just thought people might want to use it to change kernel
> options on the fly, without invoking mkvmlinuz.

Well, we would need at least a .udeb containing it. IF you can add it to
powerpc-tools, then nice. I think that maybe mkvmlinuz would be also a
candidate to be part of the powerpc-tools, not sure though.

Friendly,

Sven Luther

Re: 43p-140 install issues

[Michael Schmitz]

> > > from being added there too, not sure. In any way i believe it has more its
> > > place inside mkvmlinuz, than inside the more userland powerpc-utils.
> >
> > Whatever. Just thought people might want to use it to change kernel
> > options on the fly, without invoking mkvmlinuz.
>
> Well, we would need at least a .udeb containing it. IF you can add it to
> powerpc-tools, then nice. I think that maybe mkvmlinuz would be also a

Does it work independently of mkvmlinuz (that is, operate on the bootable
files generated by mkvmlinuz)? Does it make sense for non-PREP/CHRP
machines? Otherwise, I'd suggest adding it to mkvmlinuz.

> candidate to be part of the powerpc-tools, not sure though.

Does the mkvmlinuz trick help with bootable CDs on Macs (OldWorld), BTW?

	Michael

Re: 43p-140 install issues

[Sven Luther]

On Thu, Jan 06, 2005 at 01:19:32PM +0100, Michael Schmitz wrote:
> > > > from being added there too, not sure. In any way i believe it has more its
> > > > place inside mkvmlinuz, than inside the more userland powerpc-utils.
> > >
> > > Whatever. Just thought people might want to use it to change kernel
> > > options on the fly, without invoking mkvmlinuz.
> >
> > Well, we would need at least a .udeb containing it. IF you can add it to
> > powerpc-tools, then nice. I think that maybe mkvmlinuz would be also a
> 
> Does it work independently of mkvmlinuz (that is, operate on the bootable

Sure.

> files generated by mkvmlinuz)? Does it make sense for non-PREP/CHRP
> machines? Otherwise, I'd suggest adding it to mkvmlinuz.

Not, it is usefull only for prep machines, but the kernel needs patching
anyway, so i will just drop that for now.

> > candidate to be part of the powerpc-tools, not sure though.
> 
> Does the mkvmlinuz trick help with bootable CDs on Macs (OldWorld), BTW?

No, it is just a small tool which do the last part linking phase of the kernel
build so you can generate chrp, prep, coff, whatever zImage and zImage.initrd.
So you can ship only yhe vmlinux, and not chip the vmlinux, the zImage.chrp,
the zImage.prep, the zImage.coff, the zImage.ppcbug and so on.

Friendly,

Sven Luther

Re: 43p-140 install issues

[Ulrich Teichert]

Hi,

[del]
>Yes, please, i would greatly appreciate it, preferably the 2.6.8 kernel too.
>Let' try to get this fixed before the sarge release, which is not so far off
>now.

OK, 9 hours later I had a current sarge buisnesscard CD image, with
interesting results. I booted the standard kernel from the cdrom
with `boot cdrom:`, it came up and failed to load the initrd, so it died
on the spot as nothing could be mounted. It was detecting that I was using
a serial console.
Of course, I forgot to capture that session, so I did it again with logging
on in kermit. Then I could not boot anything from the CD, but I can still
boot fine from disk, so it's not a hardware problem. The LED displays F05
after reading something from the CDROM in this case and the machine hangs.
Strange.

I will try to boot via tftp, the firmware seems to be unable to boot
a specific file from CDROM,

CU,
Uli
-- 
Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert@gmx.de
Stormweg 24               |listening to: Suicide Drive (The Deep Eynde)
24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)

Re: 43p-140 install issues

[Sven Luther]

On Sun, Jan 02, 2005 at 04:38:00PM +0100, Ulrich Teichert wrote:
> Hi,
> 
> [del]
> >Yes, please, i would greatly appreciate it, preferably the 2.6.8 kernel too.
> >Let' try to get this fixed before the sarge release, which is not so far off
> >now.
> 
> OK, 9 hours later I had a current sarge buisnesscard CD image, with
> interesting results. I booted the standard kernel from the cdrom
> with `boot cdrom:`, it came up and failed to load the initrd, so it died
> on the spot as nothing could be mounted. It was detecting that I was using
> a serial console.

You need to boot install/powerpc/vmlinuz-prep.initrd, not the vmlinux one.

> Of course, I forgot to capture that session, so I did it again with logging
> on in kermit. Then I could not boot anything from the CD, but I can still
> boot fine from disk, so it's not a hardware problem. The LED displays F05
> after reading something from the CDROM in this case and the machine hangs.
> Strange.
> 
> I will try to boot via tftp, the firmware seems to be unable to boot
> a specific file from CDROM,

Ah, strange. That said, tftp is the prefered boot method for prep hardware.

Friendly,

Sven Luther