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?
Since the firmware can't mount >ext2r0, it would be better if this
was enforced more strictly, you almost certainly need a /boot
partition.
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.
you don't have a boot loader, and thus use nobootloader to tell you the kernel
and stuff ?
Can you try the daily builds, a see if the new nobootloader with explicit /boot partition mention makes sense for you.
But i agree that you probably need link_in_boot to be set.
Do you have /var/log/syslog?
I think we could make that the default on ARM.
I'll put in some checks.
Since the firmware can't mount >ext2r0, it would be better if this
was enforced more strictly, you almost certainly need a /boot
partition.
I'll put in some checks.
I just recalled that I wrote those checks already. Did you not see
them and what exactly did you try to do?
I guess I was expecting it to actually remind me. I'll do another
install tomorrow afternoon est and try to trip it.
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).
I guess I was expecting it to actually remind me. I'll do another
install tomorrow afternoon est and try to trip it.
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
FWIW, I tried one today and the right kernel got installed.
* Kyle McMartin <[email protected]> [2004-08-15 14:18]:
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
There was no change... I'm sure it will install the right kernel if
you try again.
base-installer is quite fragile with regards to installing the kernel. Sometimes such things happen for no apparent reason.
Martin, did you do any work on nobootloader ? If not, and you tell me what are
the boot instructions needed for the different arm boxes that need it, i will be glad to add the necessary code to it.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 715 |
| Nodes: | 16 (3 / 13) |
| Uptime: | 43:02:54 |
| Calls: | 12,111 |
| Calls today: | 2 |
| Files: | 15,008 |
| Messages: | 6,518,438 |