Re: Test report: Alpha boot floppies
On Wed, Feb 09, 2000 at 10:47:06PM +0000, Peter Maydell wrote:
> (3) When MILO loaded, I got the warning message
> "MSDOS: No such file
> Oops: trying to close an non-open file!!"
> (complete with grammatical error :->)
> just before the timeout-before-booting-or-press-a-key-for-MILO-prompt stage.
We noticed this one, too. It's a cosmetic problem AFAIK. Anybody got any
clues what's the problem?
>
> (4) the BOOTP/RARP timeout is dire, but I think this is a known issue, right?
This is fixed in the 2.2.14 configs. We've build new boot-floppies. See the
separate email.
> (5) If you hit alt-F2 for a shell, backspace/delete don't work properly
> in the shell.
Known issue on alpha. Not investigated yet. Happened before the slink release
too ;-)
>
> (6) cfdisk gives an irrelevant-for-Alpha warning:
> "Not precisely one primary partition is bootable. DOS MBR cannot boot this."
There are a couple more problems with the fdisk family on Alpha.
>
> (7) HTTP download seems to be broken (looking at my server logs, it seems
> to be including the whole URL in the GET command:
> "GET http://zircon.tao.co.uk:80/alphafloppies/disks-1.44/rescue.bin HTTP/1.0"
> and the server is rightly returning 404...)
This is a general netfetch problem and probably already fixed !?
>
> (8) I tried to do an NFS install of the drivers disk but got an error
> "dbootstrap[26]: umount: invalid argument /drivers.tgz".
NFS install is broken in pre2.2.6. Could you retry with the newer set.
> (9) Once you've started the thing looking through the archive for
> things that look like base2_2.tgz, there doesn't seem to be any way
> to cancel this short of going to VC2 and killing dbootstrap.
General boot-floppies problem. Hard to solve I guess.
>
> (10) I opted for a floppy install of drivers at this point :->
> The dialog box has an odd information string:
> "This is disk 1 of 1 in the drv14alpha_generic series of
> 03-Feb 2000 02:08 /etc/localtime". What's with the /etc/localtime bit?
A broken timezone configuration on our Alpha build machine ;-)
Ignore it.
> (11) When we got to the reboot-and-do-apt-stuff bit, I got a lot
> of messages (4 or 5) like:
> apt-get(719): unaligned trap at 000002000000e954: 00000200004a032c 29 1
> although apt still seems to work. There were a few from gzip as well.
These traps are AFAIK in the C++ startup code. Jason investigated them but
there's no solution yet.
> (12) I selected the UK debian mirror for apt configuration, and it accesses
> ftp.uk.debian.org via HTTP. Surely it ought to use www.uk.debian.org for
> this? [really trivial, I know :->]
Hmm, in Germany we access ftp.de.debian.org via HTTP too. I guess it's
correct.
>
> The apt sources configuration is really nice, though...
>
> I haven't yet got the thing booting from hard disk, though. When I rebooted
> I had to tell MILO "boot fd0:linux root=/dev/sda4" because
> "boot sda4:vmlinuz root=/dev/sda4" didn't work. (and I need to sort out
> MILO on the disk itself too.)
vmlinuz is a hard link or a file or a symlink ?
Thanks for the detailed report. If you got more notes please send them too.
Greetings,
Christian
PS.: I'm offline for a week while skiing ;-)
Reply to: