linux-apus-devel

New 2.4.17-apus image on sf.net gives me problems :-(

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

hi,

downloaded the kernel-*2.4.17-apus* files from the APUS site
last night. When I try to use the kernel Image I get a
'compressed kernel too large' error (with yellow software
failure error)


6.Linux:debian> example_script2.4test                                       
                                         
Linux/m68k Amiga Bootstrap version 5.6                                      
Copyright 1993,1994 by Hamish Macdonald and Greg Harp                       
                                         
Amiga 1200 CPU: 68060 with internal FPU, AGA chipset                        
                                         
                                                                            
APUS: No BPPC+ SCSI interface detected.                                     
APUS: PCI Bridge detected.                                                  
Command line is 'root=/dev/hda12 -d debug=mem ide=doubler hdb=ide-scsi video=pm2fb:mode:1024x768-60 video=amifb:off 60 nsram'
                                         
Vertical Blank Frequency: 50Hz                                              
Power Supply Frequency: 50Hz                                                
EClock Frequency: 709379Hz                                                  
                                         
Found 8 AutoConfig 
Device 0: addr = 0x00f00c34                                                 
Device 1: addr = 0xfffe0000                                                 
Device 2: addr = 0xfffa0000                                                 
Device 3: addr = 0xfffc0000                                                 
Device 4: addr = 0xe0000000                                                 
Device 5: addr = 0xe0800000                                                 
Device 6: addr = 0xe1000000                                                 
Device 7: addr = 0x00d80000                                                 
                                         
Found 1 Block of Memory                                                     
Block 0: 0x66000000 to 0x6bf00000 (97280K)                                  
2048K of CHIP memory                                                        
                                         
The kernel will be located at 0x66000000                                    
Kernel is compressed                                                        
Uncompressing kernel image
................................................................        *****************                 
Compressed image too large! Aborting.                                       
                                         
invalid compressed format (err=2)Decompression error -- aborting

******************* == at this point i get the yellow software failure error
:-(



alan

Re: Kernel compilation

[Michel <mi...@da...>]

On Thu, 2002-02-07 at 13:13, Alan Buxey wrote:

> 1) there is still a 'default config' in the APUS tree? wheres
> it tucked away...

arch/ppc/configs/apus_defconfig

> what make file pulls it in?

make apus_defconfig IIRC, or

cp arch/ppc/configs/apus_defconfig .config; make oldconfig


> 2) Compressed kernel for APUS, whats the flag for it?

make vmapus.gz


> question:   Is it worth putting a 2.4.17 -> APUS 2.4.17 patch
> (ie patch to the official kernel tree) onto our APUS pages?
> (its a point/question raised a few times)

There is already ;)


--=20
Earthling Michel D=E4nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member   /  CS student, Free Software enthusiast

Kernel compilation

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

hi,

I see theres a 2.4.17 precompile on the site now.... I havent
tested it yet, but will this evening.  
All of my self-compiles have failed to boot....last night I did
a fresh CVS of the 2.4, but havent had time to compile...will
report later in the week.


a few other points/questions

1) there is still a 'default config' in the APUS tree? wheres
it tucked away...what make file pulls it in?

2) Compressed kernel for APUS, whats the flag for it?


question:   Is it worth putting a 2.4.17 -> APUS 2.4.17 patch
(ie patch to the official kernel tree) onto our APUS pages?
(its a point/question raised a few times)


Alan

[ linux-apus-Bugs-512697 ] minor: A2232 has no parallel port

[<no...@so...>]

Bugs item #512697, was opened at 2002-02-04 02:53
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105907&aid=512697&group_id=5907

Category: 2.4 Kernel
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: minor: A2232 has no parallel port

Initial Comment:
[...]/apus_defconfig

61 #
62 # Parallel port support
63 #

89 CONFIG_A2232=y


Nonsense, A2232 only has serial ports.

CONFIG_A2232=y is set below, in the serial
ports section, anyway. Just delete that line.

Enver


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

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105907&aid=512697&group_id=5907

Re: Prometheus and Linux Driver.

[Michel <mi...@da...>]

On Sam, 2002-02-02 at 19:47, Adam Kowalczyk wrote:

>     The last big hurdle I'm facing is getting the XFree86 4.1.0 to work w=
ith
> the tdfx driver to take advantage of the hardware acceleration.  The issu=
e
> seems to be that the XFree86 driver is looking directly at the BASE ADDRE=
SS
> REGISTERS of the PCI card instead of reading the values from the OS.  The
> other problem may be that the driver doesn't like the 0x40000000 address =
for
> the IO base.  Unfortunately, there is nothing that I can do since that's
> where it happens to be and that address needs to be ioremapped.  This was
> the one thing that I had to change in the tdfxfb.c video driver as well.

Looking at xf86EnableIO() in
xc/programs/Xserver/hw/xfree86/os-support/linux/lnx_video.c,
implementing the pciconfig_iobase syscall should be a first step towards
a solution.


--=20
Earthling Michel D=E4nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member   /  CS student, Free Software enthusiast

Prometheus and Linux Driver.

[Adam K. <ako...@co...>]

Hi,

    This is an update on the Prometheus driver for Linux.  The driver now
recognizes PCI cards in all slots and the generic routines allocate
resources to each card.  I believe my problem with KDE and GNOME core
dumping was related to not having the 2.4.17 modules and System.map
installed in the right locations.  I attempted to try to compile in an 8029
PCI ethernet card driver but have come across conflicts with respect to some
defines being set differently for zorro ethernet cards.  Erkki Vaaja has
received a kernel and corresponding files and has been able to boot up with
the Voodoo 3 card.

    The last big hurdle I'm facing is getting the XFree86 4.1.0 to work with
the tdfx driver to take advantage of the hardware acceleration.  The issue
seems to be that the XFree86 driver is looking directly at the BASE ADDRESS
REGISTERS of the PCI card instead of reading the values from the OS.  The
other problem may be that the driver doesn't like the 0x40000000 address for
the IO base.  Unfortunately, there is nothing that I can do since that's
where it happens to be and that address needs to be ioremapped.  This was
the one thing that I had to change in the tdfxfb.c video driver as well.

Adam Kowalczyk

Re: Status of Grex, Predator, Prometheus and Mediator support? (fwd)

[Andreas <an...@po...>]

Hi

*** forwarded, original message by Alan Buxey on 28-Jan-02 ***

hi,

please feel free to forward this:

Linux support of Amiga PCI BUSBoard systems.

This information is my current knowledge, I'd like to be kept
up to date, so if anyone knows anything differently please
let me know.


Prometheus (PCI board for A4k/a3k)

Developer(s) have this board
Work is currently underway, good progress is being made. a Voodoo3
is able to show its framebuffer


Mediator (PCI board for A1200)

No developers have this board (though several express interest)
No work has been done

Mediator (PCI board for A4000)

No developers have this board (none show interest)
No work has been done

GRex (aka Predator) (PCI board for BlizzardPPC A1200)

No developers have this board
No work has been done



alan

*** end of forwared message ***

-- 
Kind regards,
Andi

Re: Prometheus PCI Driver

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

[ Note for the non-APUS readers: The Prometheus is a Zorro-PCI bridge for
  Amiga ]

On Sun, 27 Jan 2002, Adam Kowalczyk wrote:
> So far so good on the 2.4.17 version of the Prometheus PCI driver.  I'm down
> to one message during the PCI initialization that I'm not too sure of what
> it means.  I'm not sure what the following is telling me:
> 
> > PCI: Cannot allocate resource region 1 of PCI bridge 0

So the PCI bus init code couldn't add the bus resource to the resource tree
(i.e. that region was already occupied).

> If I take a look at /proc/iomem, there are clearly entries for the resource
> that I've set up for the PCI memory and entries for the Voodoo 3 card show
> up as well.  Similarly, /proc/ioports shows the I/O port listing for the
> Voodoo 3 I/O port.  Here is the dmesg file for reference.  Any ideas what
> the message means?

Can you post the contents of /proc/iomem and /proc/ioports as well?
And lspci -vv?

I guess the Prometheus bus resources show up in /proc/ioports but not in
/proc/iomem?

> > Zorro: Probing AutoConfig expansion devices: 4 devices
> > Start: 0x40000000 End: 0x5fffffff
> > Prometheus PCI bridge detected.
> > About to do a zorro_request_device()
> > I made it here!
> > prom_setup_pci_ptrs: PCI mem resource requested
> > About to perform ioremap().
> > ioremap: 400f0000 (00010000) -> c8000000
> > Check out this Data 0xc8000000
> > About to leave prom_pci_setup_ptrs()
> > PCI: Probing PCI hardware
> > About to INIT_LIST_HEAD
> > Inside prom_pcibios_fixup_bus()
> > PCI: Cannot allocate resource region 1 of PCI bridge 0
> > PCI: resource is 40100000..5fffffff (200), parent c01e9c38

That's the PCI memory space of the Prometheus?
(http://prometheus.amiga.pl/developer.html is refusing connections right now,
so I can't verify).

The error message is printed in pcibios_allocate_bus_resources()
(arch/ppc/kernel/pci.c). That routine tries to find the parent resources for
the resources of your PCI host bridge.

Did you fill in bus->parent? 

  - If no (I guess so), the code will use &iomem_resource as the parent
    resource. Then request_resource() will fail because the Zorro part of the
    Prometheus already has requested that region (you should see the Zorro part
    in /proc/iomem).

  - If yes (very unlikely), pci_find_parent_resource() did not find a correct
    resource to use as a parent for the region 40100000..5fffffff.

So you should tell the bus setup code that your bus parent is the Prometheus
Zorro device. Unfortunately that's not as simple as it sounds, since
bus->parent is of type struct pci_bus *, which is not compatible with the Zorro
bus ;-(

The problem is that the PCI code assumes that PCI busses always hang off of
nothing (i.e. the CPU) or other PCI busses, while in the Prometheus' case we
don't have a PCI host bridge (bus->parent is NULL) or a PCI-PCI bridge
(bus->parent is non-NULL), but a Zorro-PCI bridge. (Once we'll have had the
generic device driver framework rewrite, I guess that'll be fixed)

I think the best solution is to copy the pcibios_allocate_bus_resources() code
to your Prometheus driver and modify it to always use &ioport_resource as the
parent resource for PCI I/O resources, and zorro_dev.resource of the Prometheus
Zorro device for PCI memory resources.

It might still break other code that assumes bus->parent contains something
valid, though. But since it works for normal PCI host bridges where bus->parent
is NULL as well, I think everything will be fine.

Question: Are there any other machines where the PCI subsystem doesn't hang off
of the CPU, but of some other sufficiently intelligent bus (so VESA Local Bus
doesn't count)?

> > PCI:00:01.0: Resource 0: 42000000-43ffffff (f=200)
> > PCI:00:01.0: Resource 1: 44000000-45ffffff (f=1208)
> > PCI:00:01.0: Resource 2: 40000000-400000ff (f=101)
> > PCI: Switching off ROM of 00:01.0

So your PCI devices are found and hooked up in the resource tree.

> > ioremap: 42000000 (01000000) -> c801e000
> > ioremap: 44000000 (01000000) -> c901f000
> > ioremap: 40000000 (00001000) -> ca020000
> > fb: Voodoo3 memory = 16384K
> > Console: switching to colour frame buffer device 100x37
> > fb0: 3Dfx Voodoo3 frame buffer device

And the Voodoo3 is working! Very nice!

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

Prometheus PCI Driver

[Adam K. <ako...@co...>]

Hi,

So far so good on the 2.4.17 version of the Prometheus PCI driver.  I'm down
to one message during the PCI initialization that I'm not too sure of what
it means.  I'm not sure what the following is telling me:

> PCI: Cannot allocate resource region 1 of PCI bridge 0

If I take a look at /proc/iomem, there are clearly entries for the resource
that I've set up for the PCI memory and entries for the Voodoo 3 card show
up as well.  Similarly, /proc/ioports shows the I/O port listing for the
Voodoo 3 I/O port.  Here is the dmesg file for reference.  Any ideas what
the message means?

Adam


> Total memory = 127MB; using 512kB for hash table (at c0300000)
> Linux version 2.4.17 (root@localhost.localdomain) (gcc version 2.95.3
20010111 (prerelease/franzo/20010111)) #87 Sun Jan 27 11:12:34 EST 2002
> Amiga hardware found: [A3000] VIDEO BLITTER AMBER_FF AUDIO FLOPPY
A3000_SCSI KEYBOARD MOUSE SERIAL PARALLEL A3000_CLK CHIP_RAM PAULA DENISE_HR
AGNUS_HR_NTSC MAGIC_REKICK ZORRO3
> On node 0 totalpages: 32640
> zone(0): 32640 pages.
> zone(1): 0 pages.
> zone(2): 0 pages.
> Kernel command line: root=/dev/hdf2 video=tdfx:800x600-8@60,noaccel
debug=mem
> APUS: BATs=1, BUS=67MHz, RAM=70ns, PCI bridge=0
> time_init: decrementer frequency = 16.669943 MHz
> Console: colour dummy device 80x25
> Calibrating delay loop... 399.76 BogoMIPS
> Memory: 125276k available (1652k kernel code, 696k data, 240k init, 0k
highmem)
> Dentry-cache hash table entries: 16384 (order: 5, 131072 bytes)
> Inode-cache hash table entries: 8192 (order: 4, 65536 bytes)
> Mount-cache hash table entries: 2048 (order: 2, 16384 bytes)
> Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes)
> Page-cache hash table entries: 32768 (order: 5, 131072 bytes)
> POSIX conformance testing by UNIFIX
> Zorro: Probing AutoConfig expansion devices: 4 devices
> Start: 0x40000000 End: 0x5fffffff
> Prometheus PCI bridge detected.
> About to do a zorro_request_device()
> I made it here!
> prom_setup_pci_ptrs: PCI mem resource requested
> About to perform ioremap().
> ioremap: 400f0000 (00010000) -> c8000000
> Check out this Data 0xc8000000
> About to leave prom_pci_setup_ptrs()
> PCI: Probing PCI hardware
> About to INIT_LIST_HEAD
> Inside prom_pcibios_fixup_bus()
> PCI: Cannot allocate resource region 1 of PCI bridge 0
> PCI: resource is 40100000..5fffffff (200), parent c01e9c38
> PCI:00:01.0: Resource 0: 42000000-43ffffff (f=200)
> PCI:00:01.0: Resource 1: 44000000-45ffffff (f=1208)
> PCI:00:01.0: Resource 2: 40000000-400000ff (f=101)
> PCI: Switching off ROM of 00:01.0
> Linux NET4.0 for Linux 2.4
> Based upon Swansea University Computer Society NET3.039
> Initializing RT netlink socket
> Starting kswapd
> parport0: Amiga built-in port using irq
> ioremap: 42000000 (01000000) -> c801e000
> ioremap: 44000000 (01000000) -> c901f000
> ioremap: 40000000 (00001000) -> ca020000
> fb: Voodoo3 memory = 16384K
> Console: switching to colour frame buffer device 100x37
> fb0: 3Dfx Voodoo3 frame buffer device
> ami_decode_var: fetch start too low
> fb1: Amiga ECS frame buffer device, using 640K of video memory
> clgen: Driver for Cirrus Logic based graphic boards, v1.9.9.1
>  Couldn't find PCI device
> pty: 256 Unix98 ptys configured
> Amiga-builtin serial driver version 4.30
> ttyS00 is the amiga builtin serial port
> Amiga mouse installed.
> Generic RTC Driver v1.02
> block: 128 slots per queue, batch=32
> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> Uniform Multi-Platform E-IDE driver Revision: 6.31
> ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
> ide0: X-Surf IDE interface
> ide1: X-Surf IDE interface
> ide2: Catweasel IDE interface
> ide3: Catweasel IDE interface
> ide4: Catweasel IDE interface
> hde: SAMSUNG SHD-30560A (APRO-5) SSI, ATA DISK drive
> hdf: FUJITSU MPD3091AH, ATA DISK drive
> ide2 at 80ea0800 on irq 0x0000000c
> hde: 1096048 sectors (561 MB) w/126KiB Cache, CHS=1087/16/63
> hdf: 17840696 sectors (9134 MB) w/512KiB Cache, CHS=17699/16/63
> ide-floppy driver 0.97.sv
> Partition check:
>  hde: RDSK hde1 hde2
>  hdf:last_ipl[2] already set to 2f, now 2d!
> 730: 2 -2 2 -2 2 -2 2 -2 2 -2 2 -2 2 3 -3 2
>  RDSK hdf1 hdf2 hdf3
> FD: probing units
> found <5>fd: drive 0 didn't identify, setting default ffffffff
> fd0
> SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256) (6 bit
encapsulation enabled).
> CSLIP: code copyright 1989 Regents of the University of California.
> SLIP linefill/keepalive option.
> loop: loaded (max 8 devices)
> PPP generic driver version 2.4.1
> PPP Deflate Compression module registered
> PPP BSD Compression module registered
> eth0: X-Surf at 0x00e90000, Ethernet Address 52:54:40:28:9e:ac
> No Hydra ethernet card found.
> ide-floppy driver 0.97.sv
> SCSI subsystem driver Revision: 1.00
> wd33c93-0: chip=WD33c93A/9 no_sync=0xff no_dma=0 debug_flags=0x00
>            setup_args=,,,,,,,,,
>            Version 1.25 - 09/Jul/1997, Compiled Jan 26 2002 at 14:07:15
> scsi0 : Amiga 3000 built-in SCSI
>  sending SDTR 0103010000sync_xfer=00last_ipl[2] already set to 2f, now 2d!
> 925: 2 -2 2 -2 2 -2 2 -2 2 -2 2 -2 2 3 -3 2
>   Vendor: PIONEER   Model: CD-ROM DR-124X    Rev: 1.01
>   Type:   CD-ROM                             ANSI SCSI revision: 02
> Attached scsi CD-ROM sr0 at scsi0, channel 0, id 6, lun 0
> sr0: scsi3-mmc drive: 4x/4x xa/form2 cdda tray
> Uniform CD-ROM driver Revision: 3.12
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP
> IP: routing cache hash table of 512 buckets, 4Kbytes
> TCP: Hash tables configured (established 8192 bind 8192)
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> VFS: Mounted root (ext2 filesystem) readonly.
> Freeing unused kernel memory: 240k init
> Warning: unable to open an initial console.
> Adding Swap: 352288k swap-space (priority -1)
>

Re: Status of Grex, Predator, Prometheus and Mediator support?

[Andreas <an...@po...>]

Hi Jean-Paul

>> It seems as there are a lot of users outthere who are owning a pci
>> bridging card. I must confess that I don't know that much about Amiga pci
>> bridging technology, neither if the cards named above are at sale at all
>> (e.g the predator).
> 
> I think that the question is very interesting and not out of topic.What
> hardware
> are supported (or will be supported) is a very good question. I want to
> install
> a PCI bridge on my A4000, but I want to choose a supported hardware (or the
> most
> supported one). So the status of driver developpment is a very good
> question.

Thank you for supporting me in my request!!

Well, we now have at least one status report for a prometheus patch by Adam,
which I appreciate a lot!

Information about Grex, Predator and Mediator are still lacking. I think it
would even be enough, if someone better known to the kernel and driver
development status than me could post that there are *no* patches for the other
boards in development, or *nobody* is knowing of one. If then noone tells us the
opposite we can assume that there *is* nothing (by using TND.. ;) ).

-- 
Kind regards,
Andi

Re: Status of Grex, Predator, Prometheus and Mediator support?

[Jean-Paul P. <st...@cl...>]

Hello Andreas

On 26-jan-02, you wrote:


> It seems as there are a lot of users outthere who are owning a pci
> bridging card. I must confess that I don't know that much about Amiga pci
> bridging technology, neither if the cards named above are at sale at all
> (e.g the predator).

I think that the question is very interesting and not out of topic.What
hardware
are supported (or will be supported) is a very good question. I want to
install
a PCI bridge on my A4000, but I want to choose a supported hardware (or the
most
supported one). So the status of driver developpment is a very good
question.

Regards
-- 

    Jean-Paul Pozzi

\\\          ___________________
 \\\        /
  \\\      /  A2000-060     64M CV3D
   \\\    /   A4000-060 PPC 96M CyberPPC
    \\\  /
     \\\/

Re: Problems with alloc_bootmem() and kmalloc()

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

Adam Kowalczyk wrote:

> Has anyone had problems with using alloc_bootmem() and kmalloc() not having
> any memory left to allocate?  I've tracked down problems I've been having
> with my Prometheus driver to alloc_bootmem() and kmalloc() failing to have
> any memory availalble?  Anyone know why there wouldn't be any memory
> available?

alloc_bootmem is only available until mem_init() is called, after that
kmalloc & co should work. If you send me your source, I can give you
more explicit help.

bye, Roman

Re: Status of Grex, Predator, Prometheus and Mediator support?

[Andreas <an...@po...>]

Hi Adam

> Andreas,
> 
> I've just got my Prometheus/Voodoo 3 card working with a 2.4.x kernel today,
> but there are still some things I need to work out as 2.4.x has more
> features related to PCI than did 2.2.x.  To be honest, I spent more time
> getting a working 2.4.x system than anything else ;)  I've just spent the
> last 3 days getting my Prometheus driver switched over to the 2.4.x stuff.
> 
> Adam Kowalczyk

Thank you very much for your status report Adam!!

So we could say: support for prometheus is being worked on, the developer is
already having a working kernel for the Prometheus/Voodo 3 combination.
Chances for success of the patch is high, it should be rolled out in an useful
amount of time (hmm, how should we define 'useful'?).

-- 
All the best,
Andi

Re: Status of Grex, Predator, Prometheus and Mediator support?

[Adam K. <ako...@co...>]

Andreas,

I've just got my Prometheus/Voodoo 3 card working with a 2.4.x kernel today,
but there are still some things I need to work out as 2.4.x has more
features related to PCI than did 2.2.x.  To be honest, I spent more time
getting a working 2.4.x system than anything else ;)  I've just spent the
last 3 days getting my Prometheus driver switched over to the 2.4.x stuff.

Adam Kowalczyk

----- Original Message -----
From: "Andreas Wüst" <an...@po...>
To: "Linux/APUS devel list" <lin...@li...>;
"Linux/APUS user list" <lin...@li...>
Sent: Friday, January 25, 2002 6:27 PM
Subject: Status of Grex, Predator, Prometheus and Mediator support?


> Hi
>
> I am asking this question because there are a lot of status requests by
many
> Amigans interested in using Linux on their machines.
>
> It seems as there are a lot of users outthere who are owning a pci
bridging
> card. I must confess that I don't know that much about Amiga pci bridging
> technology, neither if the cards named above are at sale at all (e.g the
> predator).
>
> There has been some discussion of mediator or grex topics on this list a
few
> months ago, but since then, nobody knows of the actual status of any of
those
> boards. So, it would be nice if people who are actually working on a
> driver/kernel patch to support an Amiga pci bridge could speak up and tell
a
> bit about the status and the project itself. It would also be nice if
people
> actually using one of those boards could tell how it feels.
>
> I would appreciate it a lot, so then I could tell the people outthere how
it
> is about their board, because I could never answer such questions till
now, I
> could only point them to these mailinglists archives, and after they
looked at the
> various postings here, they came back to tell me that they wouldn't know
> anything more than before.
>
> PS: I am sending this message to both lists to reach the most of the
people
> outthere, but please only respond to the list you are subscribed to or to
the
> devellist, it's always a bit annoying if every post gets doubled on the
> lists..
>
> PPS: Don't flame me about the status question, I am not asking for XFree86
4.2.0
> ;)
>
> --
> Kind regards, would be nice if some of you could 'enlighten' the dust a
bit,
> Andi
>
>
> _______________________________________________
> Linux-APUS-user mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-apus-user

Status of Grex, Predator, Prometheus and Mediator support?

[Andreas <an...@po...>]

Hi

I am asking this question because there are a lot of status requests by many
Amigans interested in using Linux on their machines.

It seems as there are a lot of users outthere who are owning a pci bridging
card. I must confess that I don't know that much about Amiga pci bridging
technology, neither if the cards named above are at sale at all (e.g the
predator).

There has been some discussion of mediator or grex topics on this list a few
months ago, but since then, nobody knows of the actual status of any of those
boards. So, it would be nice if people who are actually working on a
driver/kernel patch to support an Amiga pci bridge could speak up and tell a
bit about the status and the project itself. It would also be nice if people
actually using one of those boards could tell how it feels.

I would appreciate it a lot, so then I could tell the people outthere how it
is about their board, because I could never answer such questions till now, I
could only point them to these mailinglists archives, and after they looked at the
various postings here, they came back to tell me that they wouldn't know
anything more than before.

PS: I am sending this message to both lists to reach the most of the people
outthere, but please only respond to the list you are subscribed to or to the
devellist, it's always a bit annoying if every post gets doubled on the
lists..

PPS: Don't flame me about the status question, I am not asking for XFree86 4.2.0
;)

-- 
Kind regards, would be nice if some of you could 'enlighten' the dust a bit,
Andi

[ linux-apus-Bugs-508283 ] bootstrap fails with: CD failed ...

[<no...@so...>]

Bugs item #508283, was opened at 2002-01-24 19:17
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105907&aid=508283&group_id=5907

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: bootstrap fails with: CD failed ...

Initial Comment:
Hi,

my bootstrap fails with the following output when I
start it and press return:

bootstrap --apus --checksum -k ram:vmlinux

obejct not found
CD failed returncode 20



If I don't press return bootstrap just sits there forever.

Anyone a idea whats wrong?

I have a very early Cyberstorm-ppc board with an 060
and PPC604@200. Maybe I have to flash the rom?

The installation of the ppc libs could also be messed
up or too old since they are probably just as old as
the board.

The bootstrap and kernel are latest cvs releases.

MfG
    Goswin

PS: The email mask below (for not loged in users) is to
short. gos...@st... is a
safer place to reach me.

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

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105907&aid=508283&group_id=5907

Problems with alloc_bootmem() and kmalloc()

[Adam K. <ako...@co...>]

Hi,

Has anyone had problems with using alloc_bootmem() and kmalloc() not having
any memory left to allocate?  I've tracked down problems I've been having
with my Prometheus driver to alloc_bootmem() and kmalloc() failing to have
any memory availalble?  Anyone know why there wouldn't be any memory
available?

Adam

Re: rescue CD

[Michel <mi...@da...>]

On Mon, 2002-01-14 at 13:58, F. Heitkamp wrote:=20
> Is there a rescue CD available for APUS?  I have found a couple for
> PC Linux and I was thinking it would be nice if there was one for APUS.
> I understand that there is no way an Amiga can boot from CD ROM so
> boot floppys might be necessary.
>=20
> Also, I only have 64 MB of RAM in my Amiga so, the RAM disk would
> have to be fairly small.

What do you need a ramdisk for when you've got a CD? ;)

> Actually, the term "recue" CD might be a little misleading.  What I
> want is a useable small Linux setup that does not need to reside
> on a harddisk.

Someone (Brendan O'Dea IIRC) has made such a CD with a small Debian
system. You may want to contact him about it.


--=20
Earthling Michel D=E4nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member   /  CS student, Free Software enthusiast

Re: 2.4.17 problems..nasty

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

Hi,

Adam Kowalczyk wrote:

> I got 2.4.17 from cvs today and it compiled and booted.  It spit up some
> numbers around the point in time where it is doing the IDE stuff and hung up
> the first time.  The second time I booted it ran.

If it hangs, I'm interested in these numbers!

bye, Roman

Re: 2.4.17 problems..nasty

[Adam K. <ako...@co...>]

Hi,

I got 2.4.17 from cvs today and it compiled and booted.  It spit up some
numbers around the point in time where it is doing the IDE stuff and hung up
the first time.  The second time I booted it ran.

Adam

----- Original Message -----
From: "Ken Tyler" <ke...@we...>
To: "Alan Buxey" <al...@ms...>
Cc: <lin...@li...>
Sent: Thursday, January 17, 2002 3:54 PM
Subject: Re: 2.4.17 problems..nasty


>
>
> On Thu, 17 Jan 2002, Alan Buxey wrote:
>
> Hi,
>
> > these two lines dont appear at all (they do on <=2.4.13)
> >
> > 2.4.17   well, this is now my CVS copy.... this one is even less alive.
> >          It gets as far as the line
> >
> > Console: colour dummy device 80x25
>
> That's how it was but Roman just did some fixes and its running again.
>
> Ken.
>
>
>
>
> _______________________________________________
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-apus-devel

NEW Re: Proper keyboard in X?

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

On Thu, 17 Jan 2002, Alan Buxey wrote:

> simple question that I guess some of you know the simple
> answer too.

Under X widows on my KB to get control '-' I have to use controll-shift,
in a console I only need control.

Is there a fix for this ?

I've tried a few things, often ending up with a PC map - aaggghhhh !

Ken. 

Re: 2.4.17 problems..nasty

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

On Thu, 17 Jan 2002, Alan Buxey wrote:

Hi,

> these two lines dont appear at all (they do on <=2.4.13)
> 
> 2.4.17   well, this is now my CVS copy.... this one is even less alive.
>          It gets as far as the line
> 
> Console: colour dummy device 80x25

That's how it was but Roman just did some fixes and its running again.

Ken.

Re: Proper keyboard in X?

[Michel <mi...@da...>]

On Thu, 2002-01-17 at 10:34, Alan Buxey wrote:

> proper keyboard mappings for XFree86 4.1  - how?
>=20
> I've got my old standard X config for XFree4.x=20
> but my Shift keys are mapped to Alt , my ctrl is
> nowhere to be found, pipe is on vacation to
> other side of keyboard etc. =20

As answered a couple times on the user list:

	Option	"CustomKeycodes"


--=20
Earthling Michel D=E4nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member   /  CS student, Free Software enthusiast

Re: rescue CD

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

On Wed, 16 Jan 2002, F. Heitkamp wrote:
>  However I need to
> either compile a kernel or find a good one some where.  I tried 
> compiling an APUS
> kernel on my Power Mac Linux machine but when I type "make" the kernel won't
> compile.  I think make complains about not being compiled on an Amiga or 
> something.
> Should I be able to compile APUS kernels on my PowerMac?  Is there a
> HOW-TO?

Yes, you should be able to compile kernels everywhere.

I compile PPC kernels on the ia32-notebook from work (fast) and on my CHRP
(slower).
I compile m68k kernels on the ia32-notebook from work (fast) and (very rare) on
my Amiga (very slow).

Ok, that's cross-compiling, but compiling for a different system with the same
arch should work, too.

Can you post the error message from make.

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: rescue CD

[Michel <mi...@da...>]

On Thu, 2002-01-17 at 01:15, F. Heitkamp wrote:

> Should I be able to compile APUS kernels on my PowerMac?

Yes, but you need to change the platform from APUS to PowerMac. ;)


--=20
Earthling Michel D=E4nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member   /  CS student, Free Software enthusiast