linux-apus-devel

CVS 2.2 mol-branch

[Alan B. <al...@ms...>]

hi,

has anyone had any compile success with the recent 2.2 mol-branch (after
Romans' extra addition last week)?

I ask simply because I had to edit head.S and place a \ just before a
hook_num in a MOL Macro to get it to compile...and also remove any
APUS_PROGRESS calls within head.S too!

it then compiled...however when trying to use it as a kernel, i just got a
back screen followed by reset into AmigaOS.

I heard some APUS devlopers say that it would boot - but then mol would
complain about symbols of its mol.o  (another issue that i am contacting
people about).... did these people use 604's - is this a big 603 v's 604
issue?

alan

Re: keymap

[Geert U. <Gee...@so...>]

On Mon, 4 Dec 2000, Ken Tyler wrote:
> On Sun, 3 Dec 2000, Geert Uytterhoeven wrote:
> > On Wed, 29 Nov 2000, Ken Tyler wrote:
> > > Is the defkeymap.map file in 2.2 drivers/char that's used to generate
> > > defkeymap.c the right one for Amiga keybords ?
> > 
> > Of course not :-)
> > 
> > > loadkeys -d makes a bit of a mess of the keyboard.
> > 
> > I can imagine...
> 
> I've put the appropriate keymap in drivers/char/ and /usr/lib/kbd/keymaps/
> to avoid those awkwawd moments ;)

Why put it in drivers/char/? Amikeyb has it's own keymap tables in amikeyb.c,
which are copied over the tables in defkeymap.c anyway.

> Suppose with the variety of Amiga keyboards it is pointless to change the
> drivers/char defkeymap.map ?

It's the same situation on PC: not everybody has US-QWERTY.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven ------------- Sony Software Development Center Europe (SDCE)
Gee...@so... ------------------- Sint-Stevens-Woluwestraat 55
Voice +32-2-7248626 Fax +32-2-7262686 ---------------- B-1130 Brussels, Belgium

Re: 53c770 driver

[<gri...@ps...>]

> Has anyone tried the driver lately?

Trying..

I have a working kernel, but...

> What happened.   I would like to see a dmesg output.

I tried it as a module with 2.4.0-test11 and I always get an 
undefined symbol when inderting: kernel_set_cachemode

I'll try a compiled-in version soon.

								Bye, Arno.

-- 
PSINetworks Europe         Phone: +31-23-5699846 | One disk to rule them all,
Siriusdreef 34               FAX: +31-20-8640234 | One disk to bind them,
2132WT Hoofddorp+--------------------------------+ One disk to hold the files
The Netherlands |   *  Musical Interlude  *      | And in the darkness grind 'em
----------------+--------------------------------+------------------------------

 We say Retribution, We say Vengeance is bliss, We say Revolution,
 With a Cast-Iron fist!                  (Megadeth, 'The Disintegrators')

--------------------------------------------------------------------------------

Re: bugs 64500 and 64823

[Adam Di C. <ad...@on...>]

Sven LUTHER <lu...@dp...> writes:

> All in all, what i would want to happen is that when dbootstrap detects it is
> running on an apus subarch, it does the same thing as if cdrom was supplied,
> in case it was forgotten. It would be a 3 lines patch or so, surrounded by a
> #ifd __powerpc__ or something such, thus not affecting i386 at all.
> 
> Do you still have any problem with it ?

No problem with it, no.

-- 
.....Adam Di Carlo....ad...@on........<URL:http://www.onShore.com/>

Re: bugs 64500 and 64823

[Sven L. <lu...@dp...>]

On Sat, Dec 02, 2000 at 02:12:02PM -0500, Adam Di Carlo wrote:
> Sven LUTHER <lu...@dp...> writes:
> 
> > Well, the problem is that it is not an official CDROM, but a copy of the
> > archive on harddisk. There is no sense to generate rescue.bin on apus, since
> > it is only used for getting the modules out of it. The kernel stays in the
> > native partition anyway, and it is not the one from rescue.bin who is used.
> > 
> > And it did work for potato r0 when i did an install (are we speaking about the
> > same thing, i booted on the cdrom, and installed potato as normal. When it
> > should have mounted rescue.bin, it unpacked drivers.tgz instead.
> 
> Well, I can't reproduce this problem on i386.  maybe I don't
> understand the report.  Please try booting with 'debug', filing a bug
> report, and include the installer log in the report.

Huh, ...

i think we are not speaking about the same thing here, this is a solution to
solve the bug 64500, which is that the potato boot floppies on the ppc/apus
subarch have a problem when doing the install os kenrel & modules.

The main problem of it is that the boot-floppies consider the install as using
floppies, which is a non-sense on apus, unless you want to to make 720Kb boot
floppies. Anyway, the kernel installed as part of the process would never be
used, since there is no lilo equivalent on apus.

I discovered that it is possible to use not rescue.bin, but the kernel (a file
called linux) and the driver tarball directly (a file called drivers.tgz).
This is achieved by passing the cdrom option to the kernel.

All apus installs are done from a copy of the files from the harddisk, or
maybe from a CD (altough i don't think the ppc cdroms are bootable on apus
anyway, but you can launch a install program from the cdrom).

All in all, what i would want to happen is that when dbootstrap detects it is
running on an apus subarch, it does the same thing as if cdrom was supplied,
in case it was forgotten. It would be a 3 lines patch or so, surrounded by a
#ifd __powerpc__ or something such, thus not affecting i386 at all.

Do you still have any problem with it ?

Friendly,

Sven Luther

Re: keymap

[Ken T. <ke...@we...>]

On Sun, 3 Dec 2000, Geert Uytterhoeven wrote:

> On Wed, 29 Nov 2000, Ken Tyler wrote:
> > Is the defkeymap.map file in 2.2 drivers/char that's used to generate
> > defkeymap.c the right one for Amiga keybords ?
> 
> Of course not :-)
> 
> > loadkeys -d makes a bit of a mess of the keyboard.
> 
> I can imagine...

I've put the appropriate keymap in drivers/char/ and /usr/lib/kbd/keymaps/
to avoid those awkwawd moments ;)

Suppose with the variety of Amiga keyboards it is pointless to change the
drivers/char defkeymap.map ?

Ken.

Re: keymap

[Geert U. <ge...@li...>]

On Wed, 29 Nov 2000, Ken Tyler wrote:
> Is the defkeymap.map file in 2.2 drivers/char that's used to generate
> defkeymap.c the right one for Amiga keybords ?

Of course not :-)

> loadkeys -d makes a bit of a mess of the keyboard.

I can imagine...

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li...

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

Re: Linux 2.4.0-test11

[Ken T. <ke...@we...>]

On Sun, 3 Dec 2000, Roman Zippel wrote:

> Are you sure? That file is new with test11, but it's in the cvs
> repository.

You're right, I've stuffed something up.

Thanks, ken.

Re: Linux 2.4.0-test11

[Roman Z. <zi...@fh...>]

Hi,

On Sat, 2 Dec 2000, Ken Tyler wrote:

> The current kernel sources in 2.3 cvs don't compile because
> kernel/Makefile attempts to link context.o which doesn't exits, nor does
> context.c.

Are you sure? That file is new with test11, but it's in the cvs
repository.

> Apart from that it boots and runs.

Nice to hear. :)

bye, Roman

Re: bugs 64500 and 64823

[Adam Di C. <ad...@on...>]

Sven LUTHER <lu...@dp...> writes:

> Well, the problem is that it is not an official CDROM, but a copy of the
> archive on harddisk. There is no sense to generate rescue.bin on apus, since
> it is only used for getting the modules out of it. The kernel stays in the
> native partition anyway, and it is not the one from rescue.bin who is used.
> 
> And it did work for potato r0 when i did an install (are we speaking about the
> same thing, i booted on the cdrom, and installed potato as normal. When it
> should have mounted rescue.bin, it unpacked drivers.tgz instead.

Well, I can't reproduce this problem on i386.  maybe I don't
understand the report.  Please try booting with 'debug', filing a bug
report, and include the installer log in the report.

-- 
.....Adam Di Carlo....ad...@on........<URL:http://www.onShore.com/>

Linux 2.4.0-test11

[Ken T. <ke...@we...>]

The current kernel sources in 2.3 cvs don't compile because
kernel/Makefile attempts to link context.o which doesn't exits, nor does
context.c.

Apart from that it boots and runs.

Ken.

Re: bugs 64500 and 64823

[Sven L. <lu...@dp...>]

On Thu, Nov 30, 2000 at 01:40:52PM -0500, Adam Di Carlo wrote:
> Sven LUTHER <lu...@dp...> writes:
> 
> > BTW, i guess another option would be to look at the place where we read
> > /proc/cmdline, and then set things up as if the boot arg cdrom was entered if
> > and only if we are on ppc and on the apus subarch. Which file should i look
> > for that ? mmm, maybe i should try some grepping, ...
> 
> Please, lets solve this generally rather than on an arch-by-arch
> basis.
> 
> dbootstrap should be clever enough to sense that a given CD-ROM is a
> normal, official one and act accordingly, e.g., suck that stuff in
> without further prompting.  This should be the case no matter what the
> cmdline argument were.  Rigth now this is not working, at least, not
> on i386 when I tested it from 2.2r0 or r1 (not sure).

Well, the problem is that it is not an official CDROM, but a copy of the
archive on harddisk. There is no sense to generate rescue.bin on apus, since
it is only used for getting the modules out of it. The kernel stays in the
native partition anyway, and it is not the one from rescue.bin who is used.

And it did work for potato r0 when i did an install (are we speaking about the
same thing, i booted on the cdrom, and installed potato as normal. When it
should have mounted rescue.bin, it unpacked drivers.tgz instead.

> > What is the time schedule for potato r2 ? any chance to have this included (at
> > least the documentation fix telling about the cdrom boot option, but we are
> > working on a kernel + bootstrapper upgrade for apus also).
> 
> This is a 2.2r3 issue... 2.2r2 is going out within a few hours and I'm
> not doing any more boot-floppies builds for it.

Not even a hand update of the install-apus.txt file ? 

Well i guess it is too late anyway, no problem, 

When is r3 scheduled for ?

Friendly,

Sven Luther

Re: bugs 64500 and 64823

[Adam Di C. <ad...@on...>]

Sven LUTHER <lu...@dp...> writes:

> BTW, i guess another option would be to look at the place where we read
> /proc/cmdline, and then set things up as if the boot arg cdrom was entered if
> and only if we are on ppc and on the apus subarch. Which file should i look
> for that ? mmm, maybe i should try some grepping, ...

Please, lets solve this generally rather than on an arch-by-arch
basis.

dbootstrap should be clever enough to sense that a given CD-ROM is a
normal, official one and act accordingly, e.g., suck that stuff in
without further prompting.  This should be the case no matter what the
cmdline argument were.  Rigth now this is not working, at least, not
on i386 when I tested it from 2.2r0 or r1 (not sure).

> What is the time schedule for potato r2 ? any chance to have this included (at
> least the documentation fix telling about the cdrom boot option, but we are
> working on a kernel + bootstrapper upgrade for apus also).

This is a 2.2r3 issue... 2.2r2 is going out within a few hours and I'm
not doing any more boot-floppies builds for it.

-- 
.....Adam Di Carlo....ad...@on........<URL:http://www.onShore.com/>

Searching debian boot-floppies tester.

[Sven L. <lu...@dp...>]

Hello, ...

As you may all be aware, i did the debian boot-floppies port for apus. 

The version of it released with potato has still some problems, apart from
both the kernel and boothack beginh a bit updated. The problem as the ones of
you which have installed debian/potato may know is a problem with loop
mounting resceu.bin when using the install os kernel & modules menu entry.
Because of this problem the later configure module menu entry is also broken.

Now i have discovered that when supplying the kernel with the additional cdrom
option, things should work ok. But i am not able to test it until this
weekend, and not really sure i will have time for it. Thus i am searching
people willing to contribute in this testing.

If you don't have a free partition, installing on your swap partition should
be enough for testing this. (i installed on a 32MB partition, but am not sure
if this will be ok fro potato, but anyway, you don't need to do the install
base system step, so much less could be enough).

Ok, now let's explain how this magic thing works :

dbootstrap looks at /proc/cmdline for the options passed to the kernel by
boothack. It will fint the cdrom option you pass to it (at the end, after the
root= ... stuff) and go into install from CDROM modde. It makes more sense
since the apus install (from harddisk) is more akin to a cdrom install and not
to a floppy based install.

So instead of trying to loop mount rescue.bin and failing, the install setup
will just copy the linux kernel from the disk and get the modules from the
drivers.tgz tarball. (they have to be in the apus subdir, they are if you copy
all the archive).

Ok, hope someone will find time to test this, 

Also if someone would reread the install.apus file and point typos, bad
documentation, obscure points and other such stuff to me, i will try fixing
that also.

And notice, it is kind of urgent, because i hope to have the docs at least
updated fro potato r2, which was supposed to be out last weekend already.

Friendly,

Sven Luther

Re: bugs 64500 and 64823

[Sven L. <lu...@dp...>]

On Thu, Nov 30, 2000 at 10:17:09AM -0500, Adam Di Carlo wrote:
> Sven LUTHER <lu...@dp...> writes:
> 
> > On Thu, Nov 30, 2000 at 02:59:20AM -0500, Adam Di Carlo wrote:
> > > Sven LUTHER <lu...@dp...> writes:
> > > 
> > > > Is there somethign special involved when dbootstrap installs from a CD ? how
> > > > can we make dbootstrap install think it is installing from a CD when we are on
> > > > apus ?
> > > 
> > > Have it pass the 'cdrom' boot argument is the easiest way.
> > 
> > Err, ...
> > 
> > how do i do that ?
> > 
> > for information, we launch the install process from a bootloader, some variant
> > of the amiboot used by m68k/amiga. The option of it are the name of the
> > kernel, the name of the root image and the usual kernel options. 
> 
> Yes, its a kernel boot argument.  surely you're boot loader lets you

ok, ...

> pass arguments to the kernel, such that they show up in /proc/cmdline ?

Yes, usre, i didn't understand how you read it back though, but if you parse
/proc/cmdline, it is easy ...

> > > There's a check in dbootstrap but I don't think that's working
> > > quite, at least, it didn't seem to work properly on i386.
> > 
> > Well, i installed potato on a i386 box from a cd, and it worked in the way i
> > would like it to behave.
> 
> Glad to hear that.

Will ask for a new round of testing, ...
And then upgrade the docs.

BTW, i guess another option would be to look at the place where we read
/proc/cmdline, and then set things up as if the boot arg cdrom was entered if
and only if we are on ppc and on the apus subarch. Which file should i look
for that ? mmm, maybe i should try some grepping, ...

What is the time schedule for potato r2 ? any chance to have this included (at
least the documentation fix telling about the cdrom boot option, but we are
working on a kernel + bootstrapper upgrade for apus also).

Friendly,

Sven Luther

Re: bugs 64500 and 64823

[Adam Di C. <ad...@on...>]

Sven LUTHER <lu...@dp...> writes:

> On Thu, Nov 30, 2000 at 02:59:20AM -0500, Adam Di Carlo wrote:
> > Sven LUTHER <lu...@dp...> writes:
> > 
> > > Is there somethign special involved when dbootstrap installs from a CD ? how
> > > can we make dbootstrap install think it is installing from a CD when we are on
> > > apus ?
> > 
> > Have it pass the 'cdrom' boot argument is the easiest way.
> 
> Err, ...
> 
> how do i do that ?
> 
> for information, we launch the install process from a bootloader, some variant
> of the amiboot used by m68k/amiga. The option of it are the name of the
> kernel, the name of the root image and the usual kernel options. 

Yes, its a kernel boot argument.  surely you're boot loader lets you
pass arguments to the kernel, such that they show up in /proc/cmdline
?

> > There's a check in dbootstrap but I don't think that's working
> > quite, at least, it didn't seem to work properly on i386.
> 
> Well, i installed potato on a i386 box from a cd, and it worked in the way i
> would like it to behave.

Glad to hear that.

-- 
.....Adam Di Carlo....ad...@on........<URL:http://www.onShore.com/>

Re: bugs 64500 and 64823

[Sven L. <lu...@dp...>]

On Thu, Nov 30, 2000 at 02:59:20AM -0500, Adam Di Carlo wrote:
> Sven LUTHER <lu...@dp...> writes:
> 
> > Is there somethign special involved when dbootstrap installs from a CD ? how
> > can we make dbootstrap install think it is installing from a CD when we are on
> > apus ?
> 
> Have it pass the 'cdrom' boot argument is the easiest way.

Err, ...

how do i do that ?

for information, we launch the install process from a bootloader, some variant
of the amiboot used by m68k/amiga. The option of it are the name of the
kernel, the name of the root image and the usual kernel options. 

> There's a check in dbootstrap but I don't think that's working
> quite, at least, it didn't seem to work properly on i386.

Well, i installed potato on a i386 box from a cd, and it worked in the way i
would like it to behave.

Friendly,

Sven Luther

Re: bugs 64500 and 64823

[Adam Di C. <ad...@on...>]

Sven LUTHER <lu...@dp...> writes:

> Is there somethign special involved when dbootstrap installs from a CD ? how
> can we make dbootstrap install think it is installing from a CD when we are on
> apus ?

Have it pass the 'cdrom' boot argument is the easiest way.

There's a check in dbootstrap but I don't think that's working
quite, at least, it didn't seem to work properly on i386.

-- 
.....Adam Di Carlo....ad...@on........<URL:http://www.onShore.com/>

Re: 53c770 driver

[Michel <dae...@st...>]

Michael Nielsen wrote:
> 
> fh...@at... wrote:
> 
> > In <200...@ge...>, on 11/29/00
> >    at 02:00 AM, "Michael Nielsen" <mi...@an...> said:
> >
> > >This message was sent from Geocrawler.com by "Michael Nielsen"
> > ><mi...@an...>
> >
> > >I have been trying to test the driver, but
> > >unfortunately I seem to have some problems in
> > >booting the kernel that contains this code
> > >2.4.0-test?? (aka unstable).
> >
> > Most likely the kernel will not boot with the driver but
> > I would be interested in the dmesg output.
> >
> > What you have to do is put debug=mem in  your boothack
> > command line and install the AmigaOS dmesg command.
> > Sorry I don't know where it is; possibley Aminet or sourceforge. Then boot
> > APUS.  Let the system hang for a bit.  Reboot and
> > open a CLI and type dmesg.  You should see some gibberish from the kernel.
> > You can save the message to a file by typing
> > dmesg > dmesg.txt.  Then mail the dmesg.txt file to me.
> 
> I will do that, though I'm using the version that has a bootmesg program
> available, it seems to pick up som gibberish, which I cannot understand..   
> Is there any guide to what this acutally means ??

It's a code which shows how far the boot process proceeds before the kernel
starts. It was used in the beginning of Linux/APUS when the kernel didn't come
up all of the time.

I've now uploaded dmesg to the Boothack module so you can grab it if you don't
have it already.


> - I am intending to involve my self with the apus project, once I get up to
> speed on the kernel source..

That would be great, what area(s) would you like to work on?


> It really bugs me that I cant get the unstable one to boot :-<, I've
> recompiled and build kernels 100's of times in the last year, but the APUS
> one seems to dislike me :-<.

Post the problems you encounter on this list.


Michel


-- 
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86 and The DRI Project

Re: 53c770 driver

[Michael N. <mi...@an...>]

fh...@at... wrote:

> In <200...@ge...>, on 11/29/00
>    at 02:00 AM, "Michael Nielsen" <mi...@an...> said:
>
> >This message was sent from Geocrawler.com by "Michael Nielsen"
> ><mi...@an...>
>
> >I have been trying to test the driver, but
> >unfortunately I seem to have some problems in
> >booting the kernel that contains this code
> >2.4.0-test?? (aka unstable).
>
> Most likely the kernel will not boot with the driver but
> I would be interested in the dmesg output.
>
> What you have to do is put debug=mem in  your boothack
> command line and install the AmigaOS dmesg command.
> Sorry I don't know where it is; possibley Aminet or sourceforge. Then boot
> APUS.  Let the system hang for a bit.  Reboot and
> open a CLI and type dmesg.  You should see some gibberish from the kernel.
> You can save the message to a file by typing
> dmesg > dmesg.txt.  Then mail the dmesg.txt file to me.
>

> Fred

Hi Fred.

I will do that, though I'm using the version that has a bootmesg program
available,
it seems to pick up som gibberish, which I cannot understand..   Is there any
guide to
what this acutally means ??  - I am intending to involve my self with the
apus project,
once I get up to speed on the kernel source..

I can't get it to boot even without the 53c770 drivers in place :-<..

the stable kernel (2.2.10?) boots fine with no problem at all.

It really bugs me that I cant get the unstable one to boot :-<, I've
recompiled and build
kernels 100's of times in the last year, but the APUS one seems to dislike me
:-<.

regards
    mike.


--
#include
-----------------------------------------------------------------------
                 (Ingeniør) Michael Nielsen BE(Hons)
                                             telf: +45 9828 3431
USE THIS -> Private email : mi...@an...
-----------------------------------------------------------------------
           At arbejede er godt, så længe man husker at leve!
           (To work is good as long as we remember to live!)

RE: 53c770 driver

[<fh...@at...>]

In <200...@ge...>, on 11/29/00 
   at 02:00 AM, "Michael Nielsen" <mi...@an...> said:

>This message was sent from Geocrawler.com by "Michael Nielsen"
><mi...@an...>

>I have been trying to test the driver, but
>unfortunately I seem to have some problems in
>booting the kernel that contains this code
>2.4.0-test?? (aka unstable).

Most likely the kernel will not boot with the driver but
I would be interested in the dmesg output.

What you have to do is put debug=mem in  your boothack
command line and install the AmigaOS dmesg command.
Sorry I don't know where it is; possibley Aminet or sourceforge. Then boot
APUS.  Let the system hang for a bit.  Reboot and
open a CLI and type dmesg.  You should see some gibberish from the kernel. 
You can save the message to a file by typing
dmesg > dmesg.txt.  Then mail the dmesg.txt file to me.

Fred

Re: CVS Update: 2.3

[Michel <dae...@st...>]

Roman Zippel wrote:

> > Log message:
> >       make pci code compile...
> 
> The ppc pci code changed recently, so it would be great if someone could
> check if my changes make any sense... :-)

Looks good to me (thanks for reorganizing and cleaning up the code!), but I'm
not familiar with the new PCI code, maybe Benjamin Herrenschmidt or someone
else should have a look at it.

The only potential problem I see is that CSPPC_PCI_BRIDGE is not a real PCI
bridge, so if the upper PCI code wants to do something with it...


Michel


-- 
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86 and The DRI Project

Re: CVS Update: 2.3

[Roman Z. <zi...@fh...>]

Hi,

> Log message:
> 	make pci code compile...

The ppc pci code changed recently, so it would be great if someone could
check if my changes make any sense... :-)

by, Roman

CVS Update: 2.3

[Roman Z. <zi...@us...>]

CVSROOT:	/cvsroot/linux-apus
Module name:	2.3
Repository:	2.3/arch/ppc/kernel/
Changes by:	zi...@sl....	00/11/28 16:35:45

Modified files:
	2.3/arch/ppc/kernel/: apus_pci.c pci.c 

Log message:
	make pci code compile...

keymap

[Ken T. <ke...@we...>]

Is the defkeymap.map file in 2.2 drivers/char that's used to generate
defkeymap.c the right one for Amiga keybords ?

loadkeys -d makes a bit of a mess of the keyboard.

ken.