linux-apus-devel

GVP IO-Extender

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

I have a GVP IO-Extender parport driver working but with a problem. It
hangs linux if the printer is turned off and on after the module has been
unloaded.  The cause is an interrupt without a handler, once interrupts
from the chip are enabled they can't be disabled, well they can but then
continuous interrupts are generated. There are comments in the 2.2.n code
that say the same thing.

What's the way to handle this situation ?

Ken.  

Re: trying to clean up a bit with the questions concerning 'Initialize...' [success!]

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

Hello Chris

To make it straight: it finally worked (well, not getting the 'Initialize..'
to work, but to get debugging output out of the system)!!

> Only that I said I thought it had been fixed. Let me 'splain a little
> more about that.  I was seeing dbootstrap restart at the point during
> kernel install when it mounted a partition, in December I think. There
> were several bugs at the time about it, IIRC.
> 
> Anyway, I made a bunch of changes in the code that mounts and unmounts 
> partitions, and cleaned that problem up. I think my initial assumption, 
> that you were seeing the same problem, was wrong.
> 
> I just had an inspiration. Someone put in debugging code to help when 
> we get segfault problems. It won't show the registers for your arch, 
> but it will at least give a backtrace which may prove helpful to 
> someone around here.
> 
> The way you activate it, is add debug to your boot arguments. It's 
> supposed to give you a backtrace on stderr. Can you try that with 
> the troublesome kernel?

I now invoked the whole thing with

bootstrap --apus -v -k apus/vmlinuz-2.4.17-apus -r apus/images-1.44/root.bin
root=/dev/ram video=pm2fb:mode:1024x768-75 debug

It started up normally, well hola, I could see some more output now on
vc1 (which is quite interesting when compared to the dmesg output, as it
doesn't match.. the dmesg AmigaOS side output I've posted in my last mail
seemed to be a bit screwed up. Could it be that logging to mem doesn't worked
correctly?), then I went on in the installation until the now 1000 times
mentioned menu point, and tataa, it presented me with:

*** Segmentation fault
Backtrace:
/sbin/dbootstrap [0x1000ac60]
[0x7fffe958]
/sbin/dbootstrap [0x10015520]
/sbin/dbootstrap [0x1001047c]
/sbin/dbootstrap [0x1000f378]
Debian GNU/Lin /lib/libc.so.6 (__libc_start_main+0x170) [0xfecb640]
*** Press RETURN to continue

Well, I don't know if the output is represented correctly this way, as it was
quite screwed up on the display (the beginning of the lines were shifted
against each others). The "Debian GNU/Lin" part in the message seems to come
from the screen displayed before the debug output appeared.

I hope I have copied all the numbers correctly.

In parallel, on vc3 I could read (right before the segfault):

    Mar 19 ... (none) user.info dbootstrap [60]: formatting swap partition
/dev/hda2

then, the segfault output appeared, and, after pressing return, it
went onwards with:

    Mar 19 ... (none) user.info init: Process 'sbin/udbootstrap' (pid 57)
exited. Scheduling it for restart.
    Mar 19 ... (none) user.info init: Starting pid 75, console /dev/console:
'/sbin/udbootstrap'
    Mar 19 ... (none) user.info dbootstrap[78]: dbootstrap starting; built
2002.03.15-16:02+0000 for powerpc

Of course there has been some more output on vc3, but those lines I copied
here are right around the 'Initialize..' (and no other line was between the
lines listed here!).

Well, now I hope you can do something with the runes printed here!! ;)

-- 
Best wishes and kind regards,
Andi

Re: trying to clean up a bit with the questions concerning 'Initialize...'

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

Hi

>> I just had an inspiration. Someone put in debugging code to help when 
>> we get segfault problems. It won't show the registers for your arch, 
>> but it will at least give a backtrace which may prove helpful to 
>> someone around here.
>> 
>> The way you activate it, is add debug to your boot arguments. It's 
>> supposed to give you a backtrace on stderr. Can you try that with 
>> the troublesome kernel?

Where's stderr? vc1?

> Ok, I'll do this tonight! I think debug=mem would be the right thing for my
> machine (and afterwards get the log out of the ram under AmigaOS)?
 
By this opportunity I also took the latest bf's Adam told me to take
(3.0.21.0.1) from #http://people.debian.org/~aph/boot-floppies-woody/disks-powerpc/current/#.

Ok, I've now ran the system using debug=mem.  Well, I don't know if this has
been the right thing, as Chris pointed out with

> dbootstrap looks at the boot arguments and changes its behavior if it sees
> 'debug' among them. I don't think it creates a specific log. Other arguments
> it looks for are 'verbose' and 'quiet'. Whenever I've used it, I just type
> e.g.
> 
> Linux debug
> 
> at the boot prompt.

Unfortunately, this mail arrived after I have done the testing.

But I will do another run with the command supposed above.


For the Amiga spcialists, my boot command went as follows:

bootstrap --apus -v -k apus/vmlinuz-2.4.17-apus -r apus/images-1.44/root.bin
debug=mem root=/dev/ram video=pm2fb:mode:1024x768-75

It gave me the following output, which I personally consider not very useful,
as I can see no significant messages. As a side effect, nothing has been
printed on vc1 during startup, but I assume this was caused by redirecting the
output to ram by debug=ram.

I wonder that there is no debug output at all, as I thought debug=xxx would
also raise the debug level, as a simple 'debug' does.

Searching for SAVEKMSG magic...
Found 4312 bytes at 0x001e0010
>>>>>>>>>>>>>>>>>>>>
Total memory = 71MB; using 512kB for hash table (at c0300000)
Linux version 2.4.17-apus (root@pismo) (gcc version 2.95.4 (Debian prerelease)) #1 Son Feb 17 17:00:37 CET 2002
Amiga hardware found: [A4000] VIDEO BLITTER AUDIO FLOPPY A4000_IDE KEYBOARD MOUSE SERIAL PARALLEL A3000_CLK CHIP_RAM PAULA LISA ALICE_PAL ZORRO3 
On node 0 totalpages: 18304
zone(0): 18304 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: debug=mem root=/dev/ram video=pm2fb:mode:1024x768-75
ioremap: fffc0000 (00001000) -> fdfff000
ioremap: fffe0000 (00001000) -> fdffe000
APUS: BATs=1, BUS=67MHz, RAM=70ns, PCI bridge=1
time_init: decrementer frequency = 16.503756 MHz
Console: colour dummy device 80x25
Calibrating delay loop... 395.67 BogoMIPS
Memory: 67036k available (1864k kernel code, 848k data, 280k 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
PCI: Probing PCI hardware
Memory resource not set for host bridge 0
apus_pcibios_fixup: PCI mem resource requested
PCI: Cannot allocate resource region 1 of PCI bridge 0
PCI: resource is e0000000..fffc0000 (200), parent c023fc1c
PCI:00:01.0: Resource 0: ef000000-ef01ffff (f=200)
PCI:00:01.0: Resource 1: e1000000-e17fffff (f=200)
PCI:00:01.0: Resource 2: e1000000-e17fffff (f=200)
PCI: Cannot allocate resource region 2 of device 00:01.0
PCI:  parent is c023f8c8: e0000000-fffc0000 (f=200)
PCI: Switching off ROM of 00:01.0
Zorro: Probing AutoConfig expansion devices: 2 devices
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
Journalled Block Device driver loaded
ioremap: fffc0000 (00001000) -> c501a000
ioremap: fffe0000 (00001000) -> c501c000
ioremap: e0000000 (00800000) -> c501e000
ioremap: ef010000 (00010000) -> c581f000
Console: switching to colour frame buffer device 128x48
fb0: CVisionPPC/BVisionPPC (Permedia2), using 8192K of video memory.
fb1: Amiga AGA frame buffer device, using 1280K 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
Commodore A2232 driver initializing.
Total: 0 A2232 boards initialized.
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: Gayle IDE interface (A4000 style)
ide1: X-S-rf IDE interface
ide2: X-Surf IDE interface
hda: QUANTUM FIREBALLP LM15, ATA DISK drive
hdb: LTN526, ATAPI CD/DVD-ROM drive
ide0 at 80dd2020 on irq 0x0000000c
hda: 29336832 sectors (15020 MB) w/1900KiB Cache, CHS=29104/16/63
hdb: ATAPI 52X CD-ROM drive, 120kB Cache
Uniform CD-ROM driver Revision: 3.12
ide-floppy driver 0.97.sv
Partition check:
 hda: RDSK hdh1 hda2 hda3
FD: probing units
found fd0d
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 **:**:**:**:**:**
No Hydra ethernet card found.
ide-floppy driver 0.97.sv
SCSI subsystem driver Revision: 1.00
request_module[scsi_hostadapter]: Root fs not mounted
request_module[scsi_hostadapter]: Root fs not mounted
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDPD TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 4096)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 1440k freed
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 280k init
Warning: unable to open an initial console.
Restarting system.
<<<<<<<<<<<<<<<<<<<<

Btw: the MAC-Address hiding was done by myself in this email.. So, no kernel error
here!

-- 
Best wishes, hope this helped a bit,
Andi

Re: A late night idea about debian bf's and the "Install OperatingSystem Modules" lines

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

On Mon, 2002-03-18 at 22:59, Andreas W=FCst wrote:
>=20
> But, concerning the modules: how are they supposed to be integrated durin=
g the
> installation? I assume they have to be on an affs disk/hd, no?

modutils look for them in /lib/modules/`uname -r`, wherever that is.

> But, they can't, because affs is not case sensitive!? Or am I now
> mixing something up?

Yes, IIRC the problem isn't related to the any filesystem but due to the
*.bin files being broken. Unfortunately, I don't remember the reason,
but you might find it in the archives of this list.


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

Re: A late night idea about debian bf's and the "Install OperatingSystem Modules" lines

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

Hi

Am 18-M=E4r-02 schrieb Michel D=E4nzer:

> On Mon, 2002-03-18 at 00:22, Andreas W=FCst wrote:
>>=20
>> I have been browsing a bit trough the debian boot-floppy cvs (out of p=
ure
>> interest), and then I had the idea to look after the code related to t=
he
>> options menu, having in mind the enervating "Install Operating System
>> Modules" lines. Wouldn't it be possible to apply a fix like the follow=
ing
>> to get rid of them (only if they really aren't needed, of course!)?
>=20
> The kernel obviously doesn't have to be installed on the system, but th=
e
> modules could be nice to have. :)

Nono, sorry, no modules today!! ;)

Well, looking at it today a second time, I really saw the mistake I have =
made:
I managed to look at one part of the code in my webbrowser while editing =
a
completely other part of code in my email client (the one which obviously
already had all the modifications done). Weew, this was funny. And afterw=
ards
I even had the nerve to ask what the apus stands for.. Well, apus obvious=
ly
stands for apus, why?, because it has already been the code written for t=
he
apus flavor..

It was really late night, sorry for the mess!!

> [ diff-like snippet omitted ]

Thank you for omitting it!! :)

>> And btw, couldn't this be solved by an #if definition?
>>=20
>> Well, of course there have to be made some other adjustements in the c=
ode
>> below this paragraph, I am especially thinking about the 'bufA=3D' and=
 so on
>> lines.
>=20
> I wonder if this is the right list for these questions... ;)

I wonder if I asked the right questions?? Hahaha... ;) Ok, now leaving yo=
u
guys alone, I think you are doing a better job!! But I still think it wou=
ld
have been nice to have a code snippet written especially for apus, and th=
en is
going to ckeck if it's running on apus..

But, concerning the modules: how are they supposed to be integrated durin=
g the
installation? I assume they have to be on an affs disk/hd, no? But, they
can't, because affs is not case sensitive!? Or am I now mixing something =
up?


--=20
Kind regards, and keep up the good work,
Andi

Re: trying to clean up a bit with the questions concerning 'Initialize...'

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

On Mon, 2002-03-18 at 18:55, Andreas W=FCst wrote:
>=20
> *Michel D=E4nzer said:*
>=20
> >> I've already reported this problem with bf-3.0.19 to both of these lis=
ts. On
> >> linux-apus-devel I was told this would be a kernel issue,
> >
> > Well, I said it seems to be a kernel issue, seeing as it works with one
> > kernel but not the other.
>=20
> Aieeeh. Now we have a statement against statement. Chris claims it dboots=
trap
> related, Michel kernel related. I'm jumping out of the line of fire now!!

You put too much weight on my words. ;) I said it _seems_... I had no
additional information to base a judgement on.

> But thinking about the 2.4.9 vs. 2.4.17 thingy, I am going to belief it c=
ould
> be kernel related after all.

But as you say that mke2fs and mount work with 2.4.17, it definitely
looks like dbootstrap.


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

trying to clean up a bit with the questions concerning 'Initialize...'

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

Hi

I am now trying to stick together all the questons which has been arising
about the 'Initialize a..' bug. Hope this helps to clean up a bit. So her=
e we
go.


*Chris Tillman asked:*

>> Well, if it doesn't get fixed, it would mean that a whole release woul=
d be
>> uninstallable by network for all the x-surf users outthere without tri=
cking
>> around? (but to be fair: there doesn't seem to be too much users with =
a
>> x-surf NIC, so I can understand your point!)
>>=20
>
> If it really is a kernel issue, that's pretty easy to fix (for us). If =
it's=20
> a dbootstrap bug, that's where we'll have difficulty, with no developer=
s=20
> on that architecture.
>
> That's why I'm curious to see if you can mke2fs and mount from console =
2;
> if so, it's probably dbootstrap and hard, if not it's probably kernel a=
nd=20
> easy.

As I wrote in my bug report afterwards, it does work with mke2fs totally
problemfree.

So, it seems to be dbootstrap and hard..


*Chris Tillman asked:*

>> I was told that this bug should have already been fixed after 3.0.19, =
but this
>> doesn't seem to be case, at least not for apus flavor.
>>=20
>> Interesting thing is that everything works normally with apus kernel 2=
.4.9.
>
> Hmmm. I just had a look at the APUS notes at=20
>
> disks-powerpc/current/apus/install.txt
>
> It looks like maybe Sven never got that part to work, he says use the A=
migaOS=20
> partitioner. Are you still around here, Sven?

Oh, I think you mean partition here? Yes, that has to be done on the Amig=
aOS
side. But I can't format a linux partition under AmigaOS, so this has to =
be
done by the installer system. But, this leads me to the question: what is
dbootstrap doing asides mke2fs when selecting this ominous 'Initialize a.=
.'?

I tried to find out by myself, but couldn't find the init_linux() method =
which
seems to be called when executing this menu entry.


*Michel D=E4nzer said:*

>> I've already reported this problem with bf-3.0.19 to both of these lis=
ts. On
>> linux-apus-devel I was told this would be a kernel issue,
>
> Well, I said it seems to be a kernel issue, seeing as it works with one
> kernel but not the other.

Aieeeh. Now we have a statement against statement. Chris claims it dboots=
trap
related, Michel kernel related. I'm jumping out of the line of fire now!!

But thinking about the 2.4.9 vs. 2.4.17 thingy, I am going to belief it c=
ould
be kernel related after all.


*Adam Di Carlo said:*

>> After initializing the swap partition, it is not possible to execute
>> the point "Initialize a Linux Partition". After selecting this point
>> in the menu, the screen goes1
> black, and the installer system
>> restarts!
>
> Isn't this caused by my build with bad versions of pmac-fdisk and
> other *fdisk packages?

No idea!

> Please try the version 3.0.21.0.1, now available at
> <URL:#http://people.debian.org/~aph/boot-floppies-woody/disks-powerpc/c=
urrent/#>.

I am going to try this!


Did I forget anything?


--=20
Thanks for all your help and understanding!! Hope we can find an easy sol=
ution
for this. Kind regards, and aging thank you,
Andi

Re: 2.4.17 & kbdrate

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

On Sun, 17 Mar 2002, Reinhard Nissl wrote:
> has anyone an idea, why "kbdrate" crashes?
> 
> My config:
> SuSE Linux PPC 7.1
> 2.4.17 (cvs) kernel
> 
> BTW: "kbdrate" doesn't crash with a good old 2.2.10 kernel.

> Oops: kernel access of bad area, sig: 11
> NIP: C00989F0 XER: 00000000 LR: C0035E7C SP: C2DFFF20 REGS: c2dffe70 TRAP: 0300    Not tainted
       ^^^^^^^^
> MSR: 00009072 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
> DAR: 00000064, DSISR: 40000000
> TASK = c2dfe000[66] 'kbdrate' Last syscall: 3 
> last math c2dfe000 last altivec 00000000
> GPR00: 0000FFFF C2DFFF20 C2DFE000 7FFFFD28 7FFFFD28 00000000 C01DBE40 00000000 
> GPR08: 00000064 00000000 C0035DB4 00000064 40000022 01819210 00000000 00000000 
> GPR16: 00000000 00000000 00000000 00000000 00009072 0ADFFF40 00000000 C00040B4 
> GPR24: C0003E20 01800E90 30028FCC 017EA65C 7FFFFD28 00000001 FFFFFFEA C01DBE20 
> Call backtrace: 
> C0035C60 C0003E7C 01800B2C 016DBA08 00000000 
  ^^^^^^^^ ^^^^^^^^ ^^^^^^^^ ^^^^^^^^
Not without you looking up the marked addresses using your System.map.

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

2.4.17 & kbdrate

[Reinhard N. <rn...@gm...>]

Hi,

has anyone an idea, why "kbdrate" crashes?

My config:
SuSE Linux PPC 7.1
2.4.17 (cvs) kernel

BTW: "kbdrate" doesn't crash with a good old 2.2.10 kernel.

Bye.
--
Dipl.-Inform. (FH) Reinhard Nissl
mailto:rn...@gm...

Re: A late night idea about debian bf's and the "Install Operating System Modules" lines

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

On Mon, 2002-03-18 at 00:22, Andreas W=FCst wrote:
>=20
> I have been browsing a bit trough the debian boot-floppy cvs (out of pure=
 interest), and then
> I had the idea to look after the code related to the options menu, having=
 in
> mind the enervating "Install Operating System Modules" lines. Wouldn't it=
 be
> possible to apply a fix like the following to get rid of them (only if th=
ey really
> aren't needed, of course!)?

The kernel obviously doesn't have to be installed on the system, but the
modules could be nice to have. :)


[ diff-like snippet omitted ]

> And btw, couldn't this be solved by an #if definition?
>=20
> Well, of course there have to be made some other adjustements in the code
> below this paragraph, I am especially thinking about the 'bufA=3D' and so=
 on lines.

I wonder if this is the right list for these questions... ;)


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

Re: Still unable to 'Initialize a Linux Partition' with bf 3.0.21

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

On Son, 2002-03-17 at 00:32, Andreas W=FCst wrote:
>=20
> I've already reported this problem with bf-3.0.19 to both of these lists.=
 On
> linux-apus-devel I was told this would be a kernel issue,

Well, I said it seems to be a kernel issue, seeing as it works with one
kernel but not the other.


> I wonder about this, because the 'Initialize..' part worked perfectly wel=
l with an
> 2.4.9 apus kernel

I've compared the configs of the 2.4.{9,17} APUS kernels, and the only
changes even remotely related to the problem at hand are that ext3 and
the not-yet-working driver for the Cyberstorm SCSI are enabled.


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

A late night idea about debian bf's and the "Install Operating System Modules" lines

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

Hi

I have been browsing a bit trough the debian boot-floppy cvs (out of pure interest), and then
I had the idea to look after the code related to the options menu, having in
mind the enervating "Install Operating System Modules" lines. Wouldn't it be
possible to apply a fix like the following to get rid of them (only if they really
aren't needed, of course!)?

And to say it straight: sorry about my bad c form, but I am not a c coder..

(the file is:
http://cvs.debian.org/boot-floppies/utilities/dbootstrap/main_menu.c )

#if (#cpu(powerpc))

+ if (strcmp(Arch2, "apus") != 0) {
        struct { char *string; int key; } entries_apus[] = {
> btw: why is it referring to            ^^^^^^^^^^^^^  apus here ?

                {_("Configure the Keyboard"),                           OPT_CONFIGURE_KEY},
                {_("Partition a Hard Disk"),                            OPT_PARTITION_DISK},
                {_("Initialize and Activate a Swap Partition"),         OPT_INITIALIZE_SWAP},
                {_("Activate a Previously-Initialized Swap Partition"), OPT_ACTIVATE_SWAP},
                {_("Do Without a Swap Partition"),                      OPT_DO_WITHOUT_SWAP},
                {_("Initialize a Linux Partition"),                     OPT_INITIALIZE_LINUX},
                {_("Mount a Previously-Initialized Partition"),         OPT_MOUNT_LINUX},
                {_("Unmount a Partition"),                              OPT_UMOUNT_LINUX},
                {_("Install Operating System Modules"),                 OPT_INSTALL_OS},
                {_("Configure Device Driver Modules"),                  OPT_CONFIGURE_MODULES},
                {_("Install Foreign Modules"),                          OPT_FOREIGN_MODULES},
                {_("Configure the Hostname"),                           OPT_CONFIGURE_HOSTNAME},
                {_("Configure the Network"),                            OPT_CONFIGURE_NET},
                {_("Install the Base System"),                          OPT_INSTALL_BASE},
                {_("Reboot the System"),                                OPT_REBOOT},
                {_("View the Partition Table"),                         OPT_VIEW_PARTITIONS},
                {_("Execute a Shell"),                                  OPT_EXECUTE_SHELL},
                {_("Restart Installation System"),                      OPT_RESTART_DBOOTSTRAP},
                {_("Report a Problem"),                                 OPT_PROBLEM_REPORT},
                {NULL,0}
        };
+ }
+ else {
+        struct { char *string; int key; } entries_apus[] = {
+                {_("Configure the Keyboard"),                           OPT_CONFIGURE_KEY},
+                {_("Partition a Hard Disk"),                            OPT_PARTITION_DISK},
+                {_("Initialize and Activate a Swap Partition"),         OPT_INITIALIZE_SWAP},
+                {_("Activate a Previously-Initialized Swap Partition"), OPT_ACTIVATE_SWAP},
+                {_("Do Without a Swap Partition"),                      OPT_DO_WITHOUT_SWAP},
+                {_("Initialize a Linux Partition"),                     OPT_INITIALIZE_LINUX},
+                {_("Mount a Previously-Initialized Partition"),         OPT_MOUNT_LINUX},
+                {_("Unmount a Partition"),                              OPT_UMOUNT_LINUX},
+                {_("Configure the Hostname"),                           OPT_CONFIGURE_HOSTNAME},
+                {_("Configure the Network"),                            OPT_CONFIGURE_NET},
+                {_("Install the Base System"),                          OPT_INSTALL_BASE},
+                {_("Reboot the System"),                                OPT_REBOOT},
+                {_("View the Partition Table"),                         OPT_VIEW_PARTITIONS},
+                {_("Execute a Shell"),                                  OPT_EXECUTE_SHELL},
+                {_("Restart Installation System"),                      OPT_RESTART_DBOOTSTRAP},
+                {_("Report a Problem"),                                 OPT_PROBLEM_REPORT},
+                {NULL,0}
+        };
+ }
#endif

And btw, couldn't this be solved by an #if definition?

Well, of course there have to be made some other adjustements in the code
below this paragraph, I am especially thinking about the 'bufA=' and so on lines.

-- 
A good idea, or should I better close my mouth now?
Andi

Re: Still unable to 'Initialize a Linux Partition' with bf 3.0.21

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

Hi Colin

> On Sun, 2002-03-17 at 14:09, Andreas W=C3=BCst wrote:
>=20
>>> Anyways, have you tried diffing the .configs between the 2.4.9 apus
>>> kernel and your 2.4.17 kernel?
>>=20
>> Nope! What should I be looking for?
>=20
> I don't know; like important platform-specific config options that you
> might have missed.

Having a look at it in the next days!

>> I am now going to file a bug against bf's, as Chris advised me.
>=20
> OK, but as far as I know no one is actively working on and testing apus
> support in the boot-floppies, so it is unlikely this bug will be fixed
> (ever, since the b-f code base is being terminated after woody).

Testing? Well, I do!! Quite intensively unfortunately..

Well, if it doesn't get fixed, it would mean that a whole release would b=
e
uninstallable by network for all the x-surf users outthere without tricki=
ng
around? (but to be fair: there doesn't seem to be too much users with a
x-surf NIC, so I can understand your point!)

--=20
Thanks again for input, best wishes,
Andi

Re: Still unable to 'Initialize a Linux Partition' with bf 3.0.21

[Colin W. <wa...@de...>]

On Sun, 2002-03-17 at 14:09, Andreas W=C3=BCst wrote:

> > Anyways, have you tried diffing the .configs between the 2.4.9 apus
> > kernel and your 2.4.17 kernel?
>=20
> Nope! What should I be looking for?

I don't know; like important platform-specific config options that you
might have missed.

> I am now going to file a bug against bf's, as Chris advised me.

OK, but as far as I know no one is actively working on and testing apus
support in the boot-floppies, so it is unlikely this bug will be fixed
(ever, since the b-f code base is being terminated after woody).

Re: Still unable to 'Initialize a Linux Partition' with bf 3.0.21

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

Hi Colin

> On Sat, 2002-03-16 at 18:32, Andreas W=C3=BCst wrote:
>> I wonder about this, because the 'Initialize..' part worked perfectly =
well
>> with an 2.4.9 apus kernel (but this isn't much use to me, as 2.4.9 doe=
sn't
>> support dhcp, and so I can't install the rest of the system after the
>> reboot *snif*).
>=20
> By "2.4.9 doesn't support dhcp", I'm assuming you mean it was compiled
> without CONFIG_FILTER or CONFIG_PACKET; I'll look into fixing that if
> so.

Yep, exactly. But Michel had already uploaded a dhcp enabled kernel, the
latest 2.4.17 kernel to say.

I just can't imagine that compiling those network options broke the abili=
ty to
initialize a partition..

Either it has something to do with the kernel itself (2.4.9 vs. 2.4.17), =
or
its surroundings (whatever that may be, kernel detection on installer sys=
tem,
compiler options, etc.)

> Anyways, have you tried diffing the .configs between the 2.4.9 apus
> kernel and your 2.4.17 kernel?

Nope! What should I be looking for?

I am now going to file a bug against bf's, as Chris advised me.

--=20
Thanks for your answer,
Andi

Re: Still unable to 'Initialize a Linux Partition' with bf 3.0.21

[Colin W. <wa...@de...>]

On Sat, 2002-03-16 at 18:32, Andreas W=C3=BCst wrote:
> I wonder about this, because the 'Initialize..' part worked perfectly wel=
l with an
> 2.4.9 apus kernel (but this isn't much use to me, as 2.4.9 doesn't suppor=
t dhcp, and so I can't install
> the rest of the system after the reboot *snif*).

By "2.4.9 doesn't support dhcp", I'm assuming you mean it was compiled
without CONFIG_FILTER or CONFIG_PACKET; I'll look into fixing that if
so.

Anyways, have you tried diffing the .configs between the 2.4.9 apus
kernel and your 2.4.17 kernel?

Still unable to 'Initialize a Linux Partition' with bf 3.0.21

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

Hi

I've already reported this problem with bf-3.0.19 to both of these lists. On
linux-apus-devel I was told this would be a kernel issue, but on debian-boot, Chris told
me it would be a dbootsrap issue and should be fixed.

Today I've downloaded the root.bin from http://people.debian.org/~aph/debian/dists/woody/main/disks-powerpc/3.0.21-2002-03-13/apus/images-1.44/
Adam built and replaced the 3.0.19 root.bin in the apus/images-1.44/ folder with the new one. Still
using the 2.4.17 apus kernel.

But, unlucky me, nothings seems to have changed, the bug still appears,
and so I still can't Initialize a Linux partition.

I've quoted myself in the following lines just to give a short overview over the
problem itself:

> [First thing is,] that it is not possible to execute the point "Initialize a
> Linux Partition". After selecting this point in the menu, the screen goes
> white, and the installer system restarts!
>
> On console 3 I could read:
>
>    Mar 3 ... (none) user.info init: Process '/sbin/udbootstrap' (pid 140) exited. Scheduling it for restart
>
>    Mar 3 ... (none) user.info init: Starting pid 146, console /dev/console: '/sbin/udbootstrap'

Here I have to say that it now also didn't want to work with a virgin disk
without an already valid root partition (but of course already partitioned
from the AmigaOS side).

I wonder about this, because the 'Initialize..' part worked perfectly well with an
2.4.9 apus kernel (but this isn't much use to me, as 2.4.9 doesn't support dhcp, and so I can't install
the rest of the system after the reboot *snif*).

I hope you can see my dilemma: kernel 2.4.9 is the only one which supports my
NIC and I can 'Initialize...', but it doesn't support DHCP. 2.4.17 does support my NIC and DHCP, but I
can't 'Initialize...'..

ps: Why are the driver-1.bin and rescue.bin files in .../apus/images-1.44/ still built, although
they doesn't seem to be needed?

pps: Does the new color of the selection bar really have to be red? It gives a
very bad contrast with the underlying text. Lucky me I've already tried to
install debian that much that I can recall the selection lines from my mind.

And oh, concerning the ongoing 'malformed release file' discussion: I very often
got this message in the last few weeks (when I've been trying to install with
other kernels than 2.4.17, but, as I said, no success with them, because of
the lacking dhcp support..)!!

-- 
Thanks for any idea, kind regards,
Andi

2.4.17 & MAGIC_SYSRQ

[<du...@ds...>]

i probably found little bug in arch/ppc/kernel/apus_setup.c
at the end of function platform_init:
now is:

        ppc_md.kbd_unexpected_up = apus_kbd_unexpected_up;
        ppc_md.kbd_init_hw       = apus_kbd_init_hw;
        ppc_md.ppc_kbd_sysrq_xlate = amiga_sysrq_xlate;
        SYSRQ_KEY                = 0xff;
}

i think that should be:

        ppc_md.kbd_unexpected_up = apus_kbd_unexpected_up;
        ppc_md.kbd_init_hw       = apus_kbd_init_hw;
#ifdef CONFIG_MAGIC_SYSRQ
        ppc_md.ppc_kbd_sysrq_xlate = amiga_sysrq_xlate;
        SYSRQ_KEY                = 0xff;
#endif
}

when i compile it without CONFIG_MAGIC_SYSRQ i have errors
(SYSRQ_KEY and ppc_md.ppc_kbd_sysrq_xlate are undeclared)

dus

Re: Problems quitting XFree4.x

[Rene B. <re...@we...>]

Hi!

Sorry I can't help you but I have the same problem. I have tried several 
distributions, like LinuxPPC-2000(Q4), Debian, MkLinux and now Mandrake 
8.0-PPC, but on every I got the problem you described.
Mostly I also got these crasches if I switch from X to console (pressing 
ctrl-alt-Fx). These crashes do also apear if only X runs (no Gnome, KDE or 
so).
I have posted my X problems many month ago.

I have tried many kernels up to 2.4.14 and played a lot with XF86Config-4. 
Nothing helps. I think there is something in the kernel (maybe the 
pci-stuff) that does not work properly with CSPPC/CVPPC combination.

Maybe some of the other guys can fix this, because there is realy a 
problem.


Ciao, Renè



On 2002.03.02 10:00 Linux-Mailing-Lists wrote:
> Hi everybody,
> 
> I'm using SuSE7.1/KDE on my A4000PPC/CVPPC.Almost every time I end an
> X-Session, SuSE doesn't switch back to console but shows a wild colored
> screen (like a rainbow) and the whole system stops (hangs up or so, not
> even any more heartbeat).
> 
> I tried using different kernels (2.4.4, 2.4.9) and drivers (glint,
> fbdev). I
> also recognized that this problem was already mentioned some times within
> these lists, but there still doesn't seem to exist any solution, or does
> it?
> 
> I hope someone can help me, I don't want to use fbdev, cause is awfully
> slow!
> But I also doesn't want to get a fsck every time I start into linux!
> 
> Many thanx in advance
> 
> Kind regards
> --
> René Thol
> Mail: Ren...@gm...
> 
> _______________________________________________
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-apus-devel
> 

Problems quitting XFree4.x

[Linux-Mailing-Lists <Ren...@gm...>]

Hi everybody,

I'm using SuSE7.1/KDE on my A4000PPC/CVPPC.Almost every time I end an
X-Session, SuSE doesn't switch back to console but shows a wild colored
screen (like a rainbow) and the whole system stops (hangs up or so, not
even any more heartbeat).

I tried using different kernels (2.4.4, 2.4.9) and drivers (glint, fbdev)=
=2E I
also recognized that this problem was already mentioned some times within=

these lists, but there still doesn't seem to exist any solution, or does
it?

I hope someone can help me, I don't want to use fbdev, cause is awfully
slow!
But I also doesn't want to get a fsck every time I start into linux!

Many thanx in advance

Kind regards
-- =

Ren=E9 Thol
Mail: Ren...@gm...=

gvpio extender

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

Hello,

The parallel part of the IO-Extender *almost* almost works but I'm stuck. 

Tried two approches, one based on parport_amiga with hints of
parport_mfc3, the other is much the same with some parport_pc bits, the
justification for this being that the Ti data sheet says the parallel port
is standard 8255 PC hardware compatible.

They both behave the same way. I can insmod lp, parport and parport_gvpio,
see all the right things in /proc/iomen, /proc/interrupts, /proc/devices
and /proc/sys/dev/parport/.  Some printk's suggest interrupts are working
when I turn the printer off and on, and status bits look reasonable.

But if I try to lpr a file or cat a file directly into /dev/lp linux hangs
or blocks, heartbeat still running, cursor flashing but can't type or
switch consoles.  Magic sysreq won't sync or unmount but will reboot and
put task, register and backtrace info into dmesg.

The magic sysreq dmesg is the only debug info available and suggests it is
having a problem in chardev_open.

Where do I look ?

Ken.

APUS homepage and FAQ

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

hi,

updated the main homepage so that text based (and image-off) 
browsers show the pages properly...and users can
get what they want


updated the FAQ with some more entries...further suggestions
etc very welcome


alan

CVS Update: 2.3 (branch: trunk)

[Alan b. <ala...@us...>]

CVSROOT:	/cvsroot/linux-apus
Module name:	2.3
Repository:	2.3/arch/ppc/
Changes by:	alanbuxey@usw-pr-cvs1.	02/02/18 02:18:58

Log message:
  Fixed missing/wrong "]" warning/error on make config.  spaces were absent

Modified files:
      2.3/arch/ppc/:
        config.in 
  
  Revision      Changes    Path
  1.31          +2 -2      2.3/arch/ppc/config.in

Re: joystick

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

On Son, 2002-02-17 at 12:13, Ken Tyler wrote:
>=20
> Where do I find the 2.5 dj tree, the one with fixed joysticks ?

http://www.ch.kernel.org/pub/linux/kernel/people/davej/patches/2.5/


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

Re: joystick

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

On Sun, 17 Feb 2002, Ken Tyler wrote:
> Where do I find the 2.5 dj tree, the one with fixed joysticks ?

ftp://ftp.*.kernel.org/pub/linux/kernel/people/davej/patches/2.5/

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