Re: New kernel-wedge uploaded, time to upload linux-{kernel,modules}-di
On Sun, Jul 06, 2008 at 09:34:56PM -0300, Otavio Salvador wrote: Domenico Andreoli [EMAIL PROTECTED] writes: On Wed, Jul 02, 2008 at 05:19:43PM -0300, Otavio Salvador wrote: Hello, Hi Otavio, Latest kernel-wedge has been uploaded today to sid and we should start the updating the installer to 2.6.25 kernel. I have uploaded the packages for amd64 and i386 and would like to ask porters to handle it for your pet architecture(s). please could you explain me the details? i am not sure who is going to take the ball for hppa. in case nobody steps forward in the next few days, i could give a try myself. anyway i am pretty new to the job. who previously did this jobs for hppa? Frans Pop [EMAIL PROTECTED] Kyle McMartin [EMAIL PROTECTED] Bdale Garbee [EMAIL PROTECTED] I'll try to get to it in the next day or so. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: D-I Beta 3 preparation - please update 2.6.16 kernel udebs
On Tue, Jul 18, 2006 at 12:00:23AM +0200, Frans Pop wrote: [1] I will take care of i386, hppa, sparc and s390 myself. Thanks Frans. Cheers, Kyle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: creating kernel udebs from kernel-source
On Mon, Nov 29, 2004 at 06:23:32PM -0500, Andres Salomon wrote: - Having all kernel-images generated from k-s is a goal; I realize it's not immediately obtainable, given the current state of some of the kernel archs. While hppa is improving... 3.4M off 2.4.27 fuzzy 636K off 2.6.9 - I'm not forcing this upon anyone; port maintainers can maintain images however they see fit, because no one has any intentions of stepping in if they throw their hands up and quit. However, I do believe this will make everyones lives easier. k-s contains split up patches (in many cases w/ bk changeset references and other such comments) that make forward porting to new kernels much easier. I've no objection to working (it would be more work) out of the kernel-source tree. hppa's diff to the non-arch code are not particularly intrusive, if I remember correctly (and at a cursory glance of lsdiff). Cheers, Kyle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#265174: netwinder rc1 fail
On Sun, Aug 15, 2004 at 06:28:11PM +0100, Martin Michlmayr wrote: FWIW, I tried one today and the right kernel got installed. Awesome, can't wait for rc2 then Cheers, -- Kyle McMartin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#265174: netwinder rc1 fail
On Sat, Aug 14, 2004 at 05:28:09PM +0100, Martin Michlmayr wrote: No, it checks after you'r finishing partitioning and complains if it wasn't done properly. The documentation should say what you need (but of course it doesn't do so yet). Excellent, in that case just the kernel is an issue. -- Kyle McMartin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#265174: netwinder rc1 fail
On Sat, Aug 14, 2004 at 12:05:05AM +0100, Martin Michlmayr wrote: I just recalled that I wrote those checks already. Did you not see them and what exactly did you try to do? I'm not sure, I didn't bump into anything. I knew enought o make the partition, so if I'm supposed to accidently trigger it, then I missed it. I guess I was expecting it to actually remind me. I'll do another install tomorrow afternoon est and try to trip it. Cheers, -- Kyle McMartin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#265174: netwinder rc1 fail
On Thu, Aug 12, 2004 at 12:24:06PM +0200, Sven Luther wrote: you don't have a boot loader, and thus use nobootloader to tell you the kernel and stuff ? Yes, but if I have my firmware already set to use /vmlinuz, it would be much simpler to just put the symlink someplace where it's useful. Can you try the daily builds, a see if the new nobootloader with explicit /boot partition mention makes sense for you. Ok. But i agree that you probably need link_in_boot to be set. Nod. Cheers, -- Kyle McMartin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#265174: netwinder rc1 fail
On Thu, Aug 12, 2004 at 10:39:54AM +0100, Martin Michlmayr wrote: Do you have /var/log/syslog? I can fetch it, it will be mildly involved though. I think we could make that the default on ARM. Alrighty. I'll put in some checks. Cheers, -- Kyle McMartin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#265174: netwinder rc1 fail
Package: installation-reports Debian-installer-version: rc1 uname -a: nil Date: Wed, Aug 11, 2004 Method: Netbooted netwinder from tftp Machine: corel netwinder Processor: intel sa110 Memory: 64m Root Device: /dev/hda Root Size/partition table: /dev/hda1 20M ext2r0 /dev/hda2 2G ext3 /dev/hda3 swap Output of lspci: .. Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[E] Install boot loader:[ ] Reboot: [O] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: Installer installed riscstation kernel on my netwinder. As a result the machine did not come back after reboot. Also, if a /boot partition exists, could the vmlinuz symlink be put in /boot? Due to the way the netwinder firmware works, it looks for a file on a partition, following symlinks. Since the vmlinuz symlink is on / it's useless because it's looking with /boot as it's base. Since the firmware can't mount ext2r0, it would be better if this was enforced more strictly, you almost certainly need a /boot partition. Regards, -- Kyle McMartin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#262387: hppa b180 success
On Thu, Aug 05, 2004 at 07:31:53AM +0200, Laurent Gateau wrote: Hence my question is (as you said [O] it passed the partition process) What exactly do you choose when partitioning the disk I didn't actually partition, just used it to format my root fs, set up swap, and mount root and /home. Submit a bug if partitioning fails... -- Kyle McMartin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#262387: hppa b180 success
Package: installation-reports Debian-installer-version: http://people.debian.org/~jbailey/d-i/hppa/daily/boot.img uname -a: Linux caradhras 2.4.26-32-smp #1 SMP Sun Jun 20 20:45:33 CEST 2004 parisc GNU/Linux Date: July 28, 2004. Method: netboot from local tftpd Machine: HP B180L+ Processor: Merlin L2+ 180 (9000/778/B180L) (0) at 0xfffbe000 [62], versions 0x504, 0x0, 0x4 Memory: 416M Root Device: SCSI /dev/sda Root Size/partition table: Device Boot Start End Blocks Id System /dev/sda1 1 31 31728 f0 Linux/PA-RISC boot /dev/sda2 32 275 249856 82 Linux swap /dev/sda3 * 2761740 1500160 83 Linux /dev/sda417414091 2407424 83 Linux sda3 is /, sda4 is /home Output of lspci: [EMAIL PROTECTED]:~$ lspci :00:13.0 SCSI storage controller: LSI Logic / Symbios Logic 53c875 (rev 04) :00:14.0 Ethernet controller: Digital Equipment Corporation DECchip 21142/43 (rev 41) Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: Worked fine, once again. Will try a cd install tomorrow. System had mdetect installed, which tried to pull in read-edid, which obviously didn't work. Cheers, -- Kyle McMartin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#262387: hppa b180 success
On Fri, Jul 30, 2004 at 05:43:31PM -0400, Joey Hess wrote: reopen 262387 thanks I missed this when I closed the report before. How didn't it work? /var/log/base-config.log should have a log of whatever happened. read-edid is only available in i386. Cheers, -- Kyle McMartin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#262387: hppa b180 success
On Fri, Jul 30, 2004 at 08:36:03PM -0400, Joey Hess wrote: Since base-config 2.37 that should only result in a warning message and mdetect should still be installed; before that mdetect would not be installed if read-edid was not available. Any particular problem with how it works now, besides perhaps being ugly? Ahh, you're right, it was only a warning, my bad. Cheers -- Kyle McMartin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#246823: Re. bug#246823: boot failure
On Tue, Jul 27, 2004 at 01:41:16AM +0200, Frederik Dannemare wrote: Much has changed with the installer since May, and it is not unlikely that the problems you mention have been dealt with by the Debian Developers working on the installer. Someone is currently using my netwinder for arm builds, when they finish, I will re-try this. Regards, -- Kyle McMartin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#256111: tc1 hppa cdrom install success
Package: installation-reports Debian-installer-version: tc1 Method: CD-ROM Booted from internal cdrom (SESCSI.2.0) Machine: HP B180 (all details are same as previous installs using netboot) Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: Everything checks out. I guess this hppa can go rc1 now? Cheers, -- Kyle McMartin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#255545: hppa d-i install success!
Package: installation-reports Debian-installer-version: jbailey's 21.06.2004 daily build uname -a: Linux caradhras 2.4.26-32-smp #1 SMP Thu Apr 29 03:20:53 UTC 2004 parisc GNU/Linux Date: Mon Jun 21 13:33:07 EDT 2004 Method: Network booted from local TFTP server. Machine: HP Visualize B180L+ Processor: PA7300LC 180MHz Memory: 416784k Root Device: /dev/sda Root Size/partition table: Device Boot Start End Blocks Id System /dev/sda1 1 31 31728 f0 Linux/PA-RISC boot /dev/sda2 32 275 249856 82 Linux swap /dev/sda3 * 2761740 1500160 83 Linux /dev/sda417414091 2407424 83 Linux sda3 is root, sda4 is /home Output of lspci: caradhras:~# lspci :00:13.0 SCSI storage controller: LSI Logic / Symbios Logic 53c875 (rev 04) :00:14.0 Ethernet controller: Digital Equipment Corporation DECchip 21142/43 (rev 41) Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: System came up fine! Used tasksel to install a few tasks with no issues. The only conceivable problem is that in my xterm running minicom to the B180, tasksel does not highlight what you currently have tabbed, which meant I had to play guessing games to figure out how to hit Finish. Will try using aptitude on tomorrow's build. Will try tc2 with a cd-rom boot, when it's released. Thanks! -- Kyle McMartin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#255545: hppa d-i install success!
On Mon, Jun 21, 2004 at 07:24:21PM +0100, Martin Michlmayr wrote: I guess you're not using colour with minicom? I'm using the sane defaults. Regards, -- Kyle McMartin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#255408: first boot of new hppa install failed
Package: installation-reports Debian-installer-version: 2004-06-16 daily build http://people.debian.org/~jbailey/d-i/hppa/2004-06-16/ Date: Sun Jun 20 14:15:52 EDT 2004 Method: Network boot. Booted from local tftp server. Machine: HP PA-RISC B180L+ Processor: 180MHz PA7300LC Memory: 420M (don't remember exactly) Root Device: SCSI (sda) Root Size/partition table: not relevant Output of lspci: not relevant Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [E] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: Install went fine. Upon rebooting into new system however, the machine fails to give me a getty. Starting periodic command scheduler: cron. /bin/sh: line 1: /dev/tts/0: No such file or directory /bin/sh: line 1: /dev/tts/0: No such file or directory /bin/sh: line 1: /dev/tts/0: No such file or directory /bin/sh: line 1: /dev/tts/0: No such file or directory /bin/sh: line 1: /dev/tts/0: No such file or directory /bin/sh: line 1: /dev/tts/0: No such file or directory /bin/sh: line 1: /dev/tts/0: No such file or directory /bin/sh: line 1: /dev/tts/0: No such file or directory /bin/sh: line 1: /dev/tts/0: No such file or directory /bin/sh: line 1: /dev/tts/0: No such file or directory INIT: Id 1 respawning too fast: disabled for 5 minutes The console is on SERIAL_1, with no keyboard, mouse, or monitor hooked up. The kernel properly spat out to the serial port. This renders the system unusable. I apologize if this has been fixed, but there are no netboot images more recent than this, and I wanted to test to see if the kernel-image detection was working properly (it is). Thanks! -- Kyle McMartin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#255408: first boot of new hppa install failed
On Sun, Jun 20, 2004 at 07:49:35PM +0100, Martin Michlmayr wrote: Can you boot the installer, mount the disk, chroot into the install and check what /etc/inittab looks like. It seems it uses devfs names when it shouldn't. /target/etc # cat inittab # /etc/inittab: init(8) configuration. # # WARNING: This file is installed by the Debian installer. # It is not meant to be used by default, but only to make # sure that certain configurations are done after the initial # boot into a new system. The real inittab is most likely # named /etc/inittab.real. # # $Id: inittab.install 14565 2004-05-01 18:31:25Z joshk $ id:2:initdefault: si::sysinit:/etc/init.d/rcS ~:S:wait:/sbin/sulogin l0:0:wait:/etc/init.d/rc 0 l1:1:wait:/etc/init.d/rc 1 l2:2:wait:/etc/init.d/rc 2 l3:3:wait:/etc/init.d/rc 3 l4:4:wait:/etc/init.d/rc 4 l5:5:wait:/etc/init.d/rc 5 l6:6:wait:/etc/init.d/rc 6 ca:12345:ctrlaltdel:/sbin/shutdown -t1 -r now kb::kbrequest:/bin/echo Keyboard Request--edit /etc/inittab to let this work. pf::powerwait:/etc/init.d/powerfail start pn::powerfailnow:/etc/init.d/powerfail now po::powerokwait:/etc/init.d/powerfail stop 1:2345:respawn:/usr/sbin/termwrap /usr/sbin/base-config new /dev/tts/0 /dev/t1 2:23:respawn:/sbin/getty 38400 tty2 3:23:respawn:/sbin/getty 38400 tty3 I guess the base-config line should be using traditional names. :/ -- Kyle McMartin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#255408: first boot of new hppa install failed
/dev/cdrom link to point to the device used for /media/cdrom0 in # /target; various programs including base-config want a /dev/cdrom. CDDEV=$(grep [[:space:]]/media/cdrom0[[:space:]] /target/etc/fstab | cut -d 'e if [ -z $CDDEV ]; then CDDEV=$(grep [[:space:]]/media/cdrom[[:space:]] /target/etc/fstab | ce fi if [ -z $CDDEV ]; then CDDEV=$(grep [[:space:]]/cdrom[[:space:]] /target/etc/fstab | cut -d e fi if [ -n $CDDEV ] [ -e /target/$CDDEV ]; then chown 0:24 /target$CDDEV || true ln -s $CDDEV /target/dev/cdrom fi -- Kyle McMartin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#255408: first boot of new hppa install failed
On Sun, Jun 20, 2004 at 09:58:39PM +0100, Colin Watson wrote: What does 'ls -l /dev/tts/0' in the installer environment say? ~ # ls -l /dev/tts/0 crw---1 root root 4, 64 Jun 20 22:07 /dev/tts/ -- Kyle McMartin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#255408: first boot of new hppa install failed
On Sun, Jun 20, 2004 at 11:30:12PM +0100, Colin Watson wrote: quotes libdebian-installer4-udeb 0.29. Unfortunately, this was the latest version that built a netbootable image. http://people.debian.org/~jbailey/d-i/hppa/daily/build_netboot.log I'll try again when the image is built properly, Thanks! -- Kyle McMartin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#254073: tc1 fail on hppa
On Sun, Jun 13, 2004 at 01:25:01PM +0100, Colin Watson wrote: base-installer has no intelligence about hppa, and it should. How would one go about detecting whether the 32-bit or the 64-bit kernel is appropriate? Is it OK to install SMP kernels regardless, or do we need to detect UP vs. SMP too? Hmm. It's a problem because the firmware of some machines will only boot 64-bit kernels, some will only boot 32-bit, and some will boot either. The best thing to do, would be to always install 32bit by default. As when a person tries to boot on a machine that only has 64-bit firmware, they will have to manually edit the PALO commandline to use vmlinux64, which will result in them having a parisc64 uname -m entry. So I'd think install based on the uname -m entry would work. There's no problem, afaik, booting SMP on UP machines, so that should be fine. I was going to take a look at this, but I cannot seem to figure out how to check out d-i, and the daily svn snapshot is b0rked. I'm going to copy the parisc-linux list with this, for comments. Cheers, -- Kyle McMartin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#254073: tc1 fail on hppa
Package: installation-reports Debian-installer-version: Test Candidate 1 uname -a: Linux caradhras 2.4.25-32 #1 Mon Apr 19 18:11:19 UTC 2004 parisc unknown Date: Sat Jun 12 15:33:23 EDT 2004 Method: Netboot. Booted off the network from a local TFTP server. Machine: Hewlett-Packard B180L+ Processor: PA7300LC 180MHz Memory: 416M Root Device: SCSI (sda) Root Size/partition table: Not relevant. Output of lspci: Not relevant. Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [ ] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[E] Install boot loader:[ ] Reboot: [ ] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: Everything worked fine until installing the base system. It attempted to install kernel-image-2.4.26-64-smp, which is a parisc64 kernel. This resulted in depmod failing, and hence, the install failing. The correct kernel to have installed on this machine would have been 2.4.26-32-smp. Cheers, -- Kyle McMartin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#253789: netwinder tc1 success
On Fri, Jun 11, 2004 at 12:14:30PM +0100, Colin Watson wrote: If this applies to arm in general, then we could do this: ... If not, it'll be more complicated. Nod. The Netwinder firmware is pretty braindead, so instead of having to edit the kernfile variable to point to different versions, it would nice to just leave /boot/vmlinuz. The logic behind this is that the NW firmware can only read the kernel off a ext2 revision 0 filesystem, so you basically *must* have a seperate boot. No, this has been reported elsewhere; I believe it's currently considered to be either a toolchain bug or a bug with libssl using incorrect optimizations, but I don't know the details. Ok. Thanks, -- Kyle McMartin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#253789: netwinder tc1 success
On Fri, Jun 11, 2004 at 11:59:55AM +0100, Martin Michlmayr wrote: That's something I wanted to look in for a while. Nod. This is actually a compiler bug, see #250185 Aye. I didn't mean to imply otherwise. The whole reason I'm using this to test is that the nw running unstable was quite thoroughly broken. :) Regards, -- Kyle McMartin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#253789: netwinder tc1 success
Package: installation-reports Debian-installer-version: test candidate 1 uname -a: Linux orodruin 2.4.25-netwinder #1 Tue May 18 00:49:19 BST 2004 armv4l GNU/Linux Date: Fri Jun 11 00:53:40 EDT 2004 Method: netboot Booted off the network (tftp) and installed from archive.progeny.com. Machine: Rebel Netwinder Processor: StrongARM-110 rev 3 Memory: 64M Root Device: IDE Root Size/partition table: 100M /dev/hda1 /boot 1.9G /dev/hda2 / 128M /dev/hda3 swap Output of lspci: [typed by hand, excuse errors] :00:00.0 Co-processor: Digital Equipment Corporation StrongARM DC21285 (rev 03) :00:09.0 VGA compatible controller: Intergraphics Systems CyberPro 2000 (rev 01) :00:0a.0 Ethernet controller: Digital Equipment Corporation DECchip 21142/43 (rev 30) :00:0c.0 ISA bridge: Symphony Labs W83C553 (rev 05) :00:0c.1 IDE interface: Symphony Labs SL82c105 (rev 05) :00:0d.0 Ethernet controller: Winbond Electronics Corp W89C940F Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: Everything went swimmingly. When I rebooted to finish the install, I had to manually set the kernfile variable to /vmlinuz-2.4.25-netwinder. A better solution would be for the installer to detect that it's installing to a seperate /boot partition and to add a /boot/vmlinuz symlink instead of an /vmlinuz one. As well, when I finished the base install (opting out of using tasksel or dselect), I was unable to install ssh. It installed to the point where it tried to generate keys, and then died with Illegal instruction. I suspect this is a hardware problem with my netwinder, however. Cheers for the good work, the progress is fantastic! -- Kyle McMartin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: if something is not done, hppa will not have an installer for sarge
[Instead of directly CC'ing you Joey, I'm cross-posting to debian-boot] On Sun, Apr 11, 2004 at 12:54:59PM -0400, Joey Hess wrote: I just want to make sure that you hppa folk realise that hppa is further from having a working installer for sarge than any architecture aside from perhaps s390. AFAIK only one person is working on it at all (and he's currently away, and his time is split amoung other ports anyway). The d-i port really needs more than one person working on it, if it's going to ship with beta 4 of d-i. That's in two weeks. Note that hppa basically worked in mid-January, but it's not been kept up. The problem with hppa now, seems to be the same as what Richard Hirst reported in January. The initrd issues seem to have been taken care of, and now it's simply a segmentation fault causing problems. VFS: Mounted root (ext2 filesystem) readonly. Mounted devfs on /dev Freeing unused kernel memory: 252k freed Setting up filesystem, please wait ... umount: /initrd: Invalid argument Segmentation fault Segmentation fault [...] Is what I get when booting the latest netboot build on my 715/100XC. Regards, -- Kyle McMartin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
