Debian on Alpha DEC 2000 AXP
Marc Bigler
I downloaded the ISO of the latest Debian potato release (2.2r6) for
Alpha and unfortunately when I boot it get stucks. I own a DEC Alpha
2000 AXP (a.k.a. Jensen if I wright) 64 MB RAM, an old machine but
still runs Tru64 :) So I wanted to change for Linux as I saw that
Debian is the ONE and ONLY linux which runs on this modem I tryed it
immediatly.
So now about the problem, I boot using aboot and choose 0 as boot
option. Then I see that it's booting but when it gets to the last line:
parport0: no IEE-1284 device present.
It simply blocks and I cannot do anything :((
Do you know what that could be ? If you need anymore informations
please feel free to ask, I would like to help if possible.
Thank you in advance !
Regards
Marc
__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Mother's Day is May 12th!
http://shopping.yahoo.com
--
To UNSUBSCRIBE, email to debian-alp...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Falk Hueffner
> I downloaded the ISO of the latest Debian potato release (2.2r6) for
> Alpha and unfortunately when I boot it get stucks. I own a DEC Alpha
> 2000 AXP (a.k.a. Jensen if I wright) 64 MB RAM, an old machine but
> still runs Tru64 :) So I wanted to change for Linux as I saw that
> Debian is the ONE and ONLY linux which runs on this modem I tryed it
> immediatly.
>
> So now about the problem, I boot using aboot and choose 0 as boot
> option. Then I see that it's booting but when it gets to the last line:
>
> parport0: no IEE-1284 device present.
>
> It simply blocks and I cannot do anything :((
The problem is that Jensens can't boot the generic kernel image, they
need a custom one (as only subarchitecture). I'm not sure whether
there's a Jensen kernel on the 2.2r6 ISO, if there is,you could try
booting with boot dxxx -fl "i" and point aboot to it. Or you could use
the hardcore method and dd the Jensen floppy image onto a harddisk and
boot from that.
Incidentally, I have just committed a patch to the debian-cd scripts
for woody that should make it possible to boot a Jensen with boot dxxx
-fl "3". I have not tested it yet, though, perhaps somebody can build
images and put them somewhere, I lack the bandwidth for that.
--
Falk
Richard Fillion
This isnt the first time it happens to me, it seems i'm very limited to
what i can build as far as kernels go. What happens is the following.
I use the same config (or VERY similar) configs every time i go to
compile, so there's really is no chance that its "my" fault. I then do
make dep as usual, and then make vmlinux (anyone know why make vmlinuz
or bzimage dont work on alphas?).
It goes through the compile and gives a few warnings here and there,
which im used to, for example:
In file included from /usr/src/linux/include/linux/locks.h:8,
from /usr/src/linux/include/linux/devfs_fs_kernel.h:6,
from tty_io.c:101:
/usr/src/linux/include/linux/pagemap.h:32: warning: `page_cache_release'
redefined
/usr/src/linux/include/linux/modules/ksyms.ver:38: warning: this is the
location of the previous definition
That comes up often (in this "bad" kernel). Once at the end of the
compile where it puts all the different parts together, it gives:
-o vmlinux
fs/fs.o: In function `generic_cont_expand':
fs/fs.o(.text+0x7074): undefined reference to `page_cache_release'
fs/fs.o(.text+0x7078): undefined reference to `page_cache_release'
fs/fs.o: In function `cont_prepare_write':
fs/fs.o(.text+0x7190): undefined reference to `page_cache_release'
fs/fs.o(.text+0x7194): undefined reference to `page_cache_release'
fs/fs.o(.text+0x7250): undefined reference to `page_cache_release'
fs/fs.o(.text+0x7254): more undefined references to `page_cache_release'
follow
make: *** [vmlinux] Error 1
Sometimes its a whole lot more of these errors, other times its less.
Every time i mention this in #debian i get "thats a gcc problem." and
when i ask whats wrong with gcc, i get "thats a binutils problem." and
when i ask whats wrong with binutils i get "thats a kernel problem." As
you can see, i get nowheres.
Do any of you know whats going on? I've just be told that 2.4.19 is
out, and possibly something newer than that, so im going to try those.
Richard Fillion
ri...@rhix.dhs.org
Christopher C. Chimelis
On Fri, 10 May 2002, Richard Fillion wrote:
> This isnt the first time it happens to me, it seems i'm very limited to
> what i can build as far as kernels go. What happens is the following.
> I use the same config (or VERY similar) configs every time i go to
> compile, so there's really is no chance that its "my" fault. I then do
> make dep as usual, and then make vmlinux (anyone know why make vmlinuz
> or bzimage dont work on alphas?).
Those targets are not properly defined in the Makefiles in the alpha parts
of the kernel source, so they won't work properly. The 'bzimage' target
especially shouldn't work since IIRC, there's no "unbzipping" support in
the bootloaders. Making the vmlinuz target work should be trivial,
though.
> fs/fs.o: In function `generic_cont_expand':
> fs/fs.o(.text+0x7074): undefined reference to `page_cache_release'
> fs/fs.o(.text+0x7078): undefined reference to `page_cache_release'
> fs/fs.o: In function `cont_prepare_write':
> fs/fs.o(.text+0x7190): undefined reference to `page_cache_release'
> fs/fs.o(.text+0x7194): undefined reference to `page_cache_release'
> fs/fs.o(.text+0x7250): undefined reference to `page_cache_release'
> fs/fs.o(.text+0x7254): more undefined references to `page_cache_release'
> follow
> make: *** [vmlinux] Error 1
>
> Sometimes its a whole lot more of these errors, other times its less.
> Every time i mention this in #debian i get "thats a gcc problem." and
> when i ask whats wrong with gcc, i get "thats a binutils problem." and
> when i ask whats wrong with binutils i get "thats a kernel problem." As
> you can see, i get nowheres.
If this is the same problem as most of the unresolved references that I've
seen on i386, then this is most definitely a kernel problem. What
happened is that the kernel was placing the code for some symbols in a
section that is discarded by the kernel's linker script, so the symbols
that are in that discarded section cannot be referenced. To see if this
is the same problem, try removing the " *(.text.exit)" entry from the
/DISCARD/ line at the end of arch/alpha/vmlinux.lds.in. If this allows
the kernel to link, then it's definitely the same problem that many of the
drivers exhibit. If this is the case, I can probably provide a patch that
you could submit upstream to fix this (I don't have the available time to
follow-up on a kernel patch personally right now).
> Do any of you know whats going on? I've just be told that 2.4.19 is
> out, and possibly something newer than that, so im going to try those.
Give those a shot and, if they show the same problem, try the above. FYI,
you should've seen a debconf warning when installing the binutils package
that talked about this very problem...(at least for woody and unstable,
which should be the only two dists affected).
C
Craig Small
> If this is the same problem as most of the unresolved references that I've
> seen on i386, then this is most definitely a kernel problem. What
> happened is that the kernel was placing the code for some symbols in a
> section that is discarded by the kernel's linker script, so the symbols
> that are in that discarded section cannot be referenced. To see if this
> is the same problem, try removing the " *(.text.exit)" entry from the
> /DISCARD/ line at the end of arch/alpha/vmlinux.lds.in. If this allows
> the kernel to link, then it's definitely the same problem that many of the
> drivers exhibit. If this is the case, I can probably provide a patch that
> you could submit upstream to fix this (I don't have the available time to
> follow-up on a kernel patch personally right now).
>
This isn't the binutils problem? It looks a bit like it. You need to
stop it doing some part of the process and you get a working but
slightly bigger kernel.
--
Craig Small VK2XLZ GnuPG:1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA DFA5
Eye-Net Consulting http://www.eye-net.com.au/ <csm...@eye-net.com.au>
MIEEE <csm...@ieee.org> Debian developer <csm...@debian.org>