linux-apus-user

Re: was-Won't boot

[David J. <jo...@co...>]

Hi,
I have recently successfully installed and booted from a PFS
partition. (Is this supposed to be possible)
The FFS partition I was using seemed to be getting corrupted
regularily causing my system to stop booting. It wasn't obvious the
files had become corrupted but they wouldn't work. When the boot
files were replaced by the
originals off CD things started to work again. With no change to the
miggy side.
I also have a FFS partition as well for copying files to and from
miggy.
I am using the 2.4.4 Kernal (I've tried 2.4.17 but it won't boot)
Anyway woody seems to have installed (from an 8 disk set) ok apart
from the fact that the clock says 1902. How do I to change this,
using a console (X not working yet). When I use dselect to install
software I get error messages saying the date contained in the deb is
in the future. 
The installed packages seem to work but I need to get this date thing
right. (On closing down, the hardware clock seems to be updated from
the system clock so that should solve my problem) My hardware clock
is built into my ppc, no unusual hardware here.
Also on my old Debian 2.2r3 installation I had to initially copy a
system map2.4.4 into /boot and some libs (containing the kernal
modules) into libs. I have done this but on boot up the system can't
find the modules.dep and seems to be looking in libs/modules/2.2.10
instead of libs/modules/2.4.4.
I'm not sure what needs to be done here as just renaming the dir
doesn't seem to work.
I want to get these niggly problems sorted before
moving on to XFree4 and a full software installation.

Regards

Regards,

Dave

 ( jo...@co... )

I know not with what weapons World War III will be fought, but World
War IV will be fought with sticks and stones.
-- Albert Einstein

Re: was-Won't boot

[David J. <jo...@co...>]

Hi,
I have recently successfully installed and booted from a PFS
partition. (Is this supposed to be possible)
The FFS partition I was using seemed to be getting corrupted
regularily causing my system to stop booting. It wasn't obvious the
files had become corrupted but they wouldn't work. When the boot
files were replaced by the
originals off CD things started to work again. With no change to the
miggy side.
I also have a FFS partition as well for copying files to and from
miggy.
I am using the 2.4.4 Kernal (I've tried 2.4.17 but it won't boot)
Anyway woody seems to have installed (from an 8 disk set) ok apart
from the fact that the clock says 1902. How do I to change this,
using a console (X not working yet). When I use dselect to install
software I get error messages saying the date contained in the deb is
in the future. 
The installed packages seem to work but I need to get this date thing
right. (On closing down, the hardware clock seems to be updated from
the system clock so that should solve my problem) My hardware clock
is built into my ppc, no unusual hardware here.
Also on my old Debian 2.2r3 installation I had to initially copy a
system map2.4.4 into /boot and some libs (containing the kernal
modules) into libs. I have done this but on boot up the system can't
find the modules.dep and seems to be looking in libs/modules/2.2.10
instead of libs/modules/2.4.4.
I'm not sure what needs to be done here as just renaming the dir
doesn't seem to work.
I want to get these niggly problems sorted before
moving on to XFree4 and a full software installation.

Regards

Regards,

Dave

 ( jo...@co... )

I know not with what weapons World War III will be fought, but World
War IV will be fought with sticks and stones.
-- Albert Einstein

Re: XFree86 4.1.0 & Framebuffer

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

On Thu, 2002-08-15 at 19:50, Giorgio Terzi wrote:=20
>=20
> i wish to submit some problems i have found with
> X and framebuffer:
>=20
> 1) It works stable with GLINT and FBDev but when
>    I try to change Virtual Terminal it trashes the
>    terminals and hangs the machine. Is near to be
>    impossible to exchange VTs as with old X 3.3.6.
>=20
> 2) When i want to shutdown the machine the only
>    way i have, when I am using X, is:
>    a) To close the X session restarting (X,G,K)DM
>       session (and in this nothing wrong).
>    b) With a external terminal ( I use ttyS2 connected
>       to another computer) become superuser and
>       kill -KILL the xdm & xfree processes and shutdown
>       from this terminal.
>=20
> Note that if I try to use the -TERM signal with XFree
> it hangs the machine and with the above kill procedure
> the main screen remains trashed so if I wish to work
> on other things i must use ttyS2.

Sounds like problems which have been reported before. Someone probably
needs to hack on pm2fb and/or the glint driver.


> 3) Sometimes when scrolled, the text becomes warbled
>    also with 1024x768 but not as 1152x864.
>    Is this a limitation of Accelerated driver ? =20

I assume this is in console? If so, it's likely a pm2fb bug.


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

Re: was-Won't boot

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

Hello David

Am 16-Aug-02 schrieb David Jones:

> Hi John, (and anyone who can help)
> #On 15-Aug-02, you wrote:#
> #>I asked about PFS and ASAIR it is not supported, 
> I have successfully installed and booted from a PFS partition. The FFS
> partition seemed to be getting corrupted regularily causing my system
> to stop booting. It wasn't obvious the files had become corrupted but
> they wouldn't work. When the boot files were replaced by the
> originals off CD things started to work again. With no change to the
> miggy side.
> #>I use an FFS partition for my boot files and I can also access it
> from within#
> #linux after booting, so its handy for transferring files from miggy#
> #to linux and back. 
> I also have a FFS partition as well for copying to and from miggy.
> #>I am booting with version 2.4.4 of the kernel.#
> ##The same as me. 
> #>If you have the time probably installing just the bare minimum and#
> #>then getting everything via the net with apt would be the best way
> to#
> #>go, that would take quite a bit of time but would need less#
> #>re-configuration I would think.#
> ##I now have a full Woody set of CD's (8 disks) so can install the
> software from these.
> I have partly installed Woody (the basic sytem) but have a couple of
> problems. On installation I was informed my hardware clock date was
> 1902. I didn't know how to change this, so now when I use dselect to
> install software I get error messages saying the date contained in
> the deb is in the future. Do you know how I can amend the date? The
> installed packages seem to work but I need to get this date thing
> right.

Huh? I thought the system gets the time from the internal clock (which I don't
think is damaged otherwise you would experience problems on the AmigaOS side
too)? Do you have
any exotic equipment where the battery clock sits on some kind of memory card
or something?

> Also on my old Debian 2.2r3 installation I had to initially copy a
> system map2.4.4 into /boot and some libs (containing the kernal
> modules) into libs. I have done this but on boot up the system can't
> find the modules.dep and seems to be looking in libs/modudles/2.2.10
> instead of libs/modules/2.4.4.
> I'm not sure what needs to be done here as just renaming the dir
> doesn't seem to work.

If you're running a 2.4.x kernel, it may be easiest to

apt-get install kernel-image-2.4.17-apus from stable (woody)

or kernel.image-2.4.18-apus from unstable, as Michel thankfully pointed
out in "Re: Which version of kernel 2.4.17-apus
in in woody?" This will set everything right and will generate the correct
symlinks the system needs!

> Any further info I might find useful regarding getting woody working
> ok would be great. I want to get these niggly problems sorted before
> moving on to XFree4 and a full software installation.

Sorry, don't know anything about the other issues above.

-- 
Regards,
Andi

Re: was-Won't boot

[David J. <jo...@co...>]

Hi John, (and anyone who can help)
#On 15-Aug-02, you wrote:#
#>I asked about PFS and ASAIR it is not supported, 
I have successfully installed and booted from a PFS partition. The FFS
partition seemed to be getting corrupted regularily causing my system
to stop booting. It wasn't obvious the files had become corrupted but
they wouldn't work. When the boot files were replaced by the
originals off CD things started to work again. With no change to the
miggy side.
#>I use an FFS partition for my boot files and I can also access it
from within#
#linux after booting, so its handy for transferring files from miggy#
#to linux and back. 
I also have a FFS partition as well for copying to and from miggy.
#>I am booting with version 2.4.4 of the kernel.#
##The same as me. 
#>If you have the time probably installing just the bare minimum and#
#>then getting everything via the net with apt would be the best way
to#
#>go, that would take quite a bit of time but would need less#
#>re-configuration I would think.#
##I now have a full Woody set of CD's (8 disks) so can install the
software from these.
I have partly installed Woody (the basic sytem) but have a couple of
problems. On installation I was informed my hardware clock date was
1902. I didn't know how to change this, so now when I use dselect to
install software I get error messages saying the date contained in
the deb is in the future. Do you know how I can amend the date? The
installed packages seem to work but I need to get this date thing
right.
Also on my old Debian 2.2r3 installation I had to initially copy a
system map2.4.4 into /boot and some libs (containing the kernal
modules) into libs. I have done this but on boot up the system can't
find the modules.dep and seems to be looking in libs/modudles/2.2.10
instead of libs/modules/2.4.4.
I'm not sure what needs to be done here as just renaming the dir
doesn't seem to work.
Any further info I might find useful regarding getting woody working
ok would be great. I want to get these niggly problems sorted before
moving on to XFree4 and a full software installation.

Regards

Regards,

Dave

 ( jo...@co... )

I know not with what weapons World War III will be fought, but World
War IV will be fought with sticks and stones.
-- Albert Einstein

Re: Small request ...

[John L. <ch...@la...>]

Hi there

On 14-Aug-02, Daniel Palmer wrote:

>>> If those of your running APUS on Blizzard PPCs ( with blizzardvision
>>> also ) have some spare time could you download :
>>> http://vgr.com/g-rex/boardtype.lzh and run it ... It'll tell you the

>> Version 0 here too.

> and you have newer ( not new new kernels , the newer blizzard workable
> ones e.g. not the very early 2.2.10 ones ) kernels working :\ damn ,
> its looking like giving up time , its going to be console and 1902
> forever lol. Cheers for the help

I have used kernel versions 2.2.10 up to 2.4.4 ok, but later ones give
me problems too, need to try building my own later versions to see if
they will work, but havn't got round to it yet. :-)


Regards
-- 
John

"Chaos often breeds life when order breeds habit. - Henry Brooks Adams

mailto:ch...@la... or mailto:lor...@uk...
http://www.lordofchaos.co.uk ICQ 110130385 
Nick = Chaos A1200 BlizzardPPC 240mhz 060/50 BlizzardVision OS3.9

XFree86 4.1.0 & Framebuffer

[Giorgio T. <de...@ip...>]

Hi,

i wish to submit some problems i have found with
X and framebuffer:

1) It works stable with GLINT and FBDev but when
   I try to change Virtual Terminal it trashes the
   terminals and hangs the machine. Is near to be
   impossible to exchange VTs as with old X 3.3.6.

2) When i want to shutdown the machine the only
   way i have, when I am using X, is:
   a) To close the X session restarting (X,G,K)DM
      session (and in this nothing wrong).
   b) With a external terminal ( I use ttyS2 connected
      to another computer) become superuser and
      kill -KILL the xdm & xfree processes and shutdown
      from this terminal.

Note that if I try to use the -TERM signal with XFree
it hangs the machine and with the above kill procedure
the main screen remains trashed so if I wish to work
on other things i must use ttyS2.

3) Sometimes when scrolled, the text becomes warbled
   also with 1024x768 but not as 1152x864.
   Is this a limitation of Accelerated driver ?  

I attach my XF86Config-4 file if some corrections are
needed.

Many thanks

Regards 

Giorgio Terzi

Re: Woody

[Daniel P. <cor...@ho...>]

I have a complete newbie APUS woody install guide in the works ... its being 
held back by some other things i have to do.

Although if you've managed to install debian before you should be ok , if 
you look on your woody cd one in dists / woody / binarypowerpc / disks/ apus 
or something along those lines there is the boothack and ramdisks and some 
unhelpful launch scripts . basically you need to boot the root.bin ramdisk 
from the debian cd like you did with the ramdisk images for an earlier 
version. That ramdisk contains the debian 3 installer which is pretty easy 
going .. but you can miss out the install kernel and os modules option as 
its usless and doesn't work.

heres what i have of the guide so far , it probaly contains lots of spelling 
mistakes and is in no way complete or greatly detailed , but if it helps :) 
, as you can see i write the start and end of things at the same time , so 
the part about getting the installation going is missing almost completly 
... but you should be able to work it out from what i've said above/.

---> Guide start
1. What do I need ? : The most important thing your going to need for this 
guide is a source to install debian from , these include:

CD-ROMs
FTP/HTTP
NFS share on another machine.
A local harddisk partition.

In this guide i will be using my Debian 3 (woody) CD , but it should be 
quite easy to apply this guide to other sources. You can find out how to get 
the ISO of the CD to burn in one of the apendixes. Ok , so we have a source 
to install our debian base system from what else do we need :

An APUS PPC Kernel
An APUS Boothack
A Debian installer ram disk image.

All these are supplied on the debain CD-ROM in ( insert path here ) and can 
also be found on the debain FTP / HTTP and the APUS source forge site. Now 
we've got all the software side of things its on to the hardware :

Blizzard/Cyberstorm PPC card
32+ Ram for serious usage , 16 should be ok for Console.
An AmigaOS install to launch the boothack from
1 (minimum , you can have more ) linux partition for the root and 1 linux 
swap partition
A supported amiga graphics card is also very useful , but you can ofcourse 
use chipset graphics.

You shouldn't worry about creating the Linux partitions at this point , 
we'll do them in the Debian Installer.

TIP : Try if you can to get a fresh harddrive for linux to keep your normal 
amigaOs install and it far away from each other , this way your less likely 
to wipe your amigaOS side of things or upset the APUS boothack, once the 
system is setup and running you should be ok to put the amigaOs drive back 
in and dual boot so to speak.

2. Whats next ? :

At this point if your using a fresh drive e.g. no partitions you will need 
to boot your harddrive / amigaOs install disk ( install 3.0/3,1 ) , most 
people should have got these if they bought an harddrive in the old days or 
with their machine, if you don't you have one you will need to boot your 
main AmigaOs installation with the new drive connected and use HDTool box 
from there.

Basically you need to :

Create a small amigaOs partition at the begining of the disk, 100 meg should 
do it and have enough space to play with kernels etc . and then install 
amigaOs 3.0 or 3.1 on it , we could use 3.5 or 3.9 but if we're using a 
clean harddrive we should really make sure we keep amigaOs minimal so as not 
to cause trouble with the boothack etc. Leave the rest of the disk clear , 
we will create linux partitions there in the debian installer later.

You can install AmigaOs from disks on to the new partition using the install 
disk , or if you have the os 3.5 cd you can use the os3.1 package from there 
and install 3.1 on the new drive while you are in you normal amiga os 
installation , just make sure you select the location to install it to else 
it will overwrite your system drive.

At this point you need to get the boothack , kernel and ramdisk over to your 
amigaOS install be it a new install or your main working install. If your 
doing this from a new install you will probaly need to boot you main install 
and copy the files from your debian CD to the new drive , the files you need 
are :

I used a completly new drive with just an Os3.1 install , so i needed to 
install Ide-Fix from its floppy disk to get access to the debian CD-Rom ( I 
also downloaded kernels and boothacks from the APUS site but that is out of 
the scope of this guide ) . Within linux you will not need any external 
amigaOs drivers , so it is not nessarcy to install all your amigaOs kit here 
.. You want to keep it as clean as possible,

BlizzardPPC owners shouldn't need to install a PPC.library or WarpOS ( Both 
are supported ) as they have a PPC.Library in ROM , CyberStorms i don't know 
about as i don't have one , but if in doubt install the PPC.library from the 
DCE site ( www.dcecom.de ) .

3. Getting the installation going

bootstrap --apus "kernel options"


bootstrap --apus -k apus/linux -r apus/images-1.44/root.bin root=/dev/ram

bootstrap --apus -k apus/linux root=/dev/sda3

The first thing the installer will do is ask you to select you language , 
the choice here is slightly limited compaired to the X86 Debian , but if 
your reading this in english you will probaly want to select english :).

Next the installer welcomes you and gives you the Debian blurb .. Pressing 
enter will now present the Debian install menu , there are lots of options 
but these are the *ONLY* ones amiga users need to select :

Configure the keyboard

Configure hostname *

Configure the network *

Parition a hard disk

Initalize and activate a Linux swap partition

Initalize a Linux partition

Install Base system

Reboot System.

*If you want to connect to a network

The rest such as installing the kernel ( useless as we have the kernel on 
the amigaOs side already , and i found it broke the installer trying ) and 
making a boot disk aren't needed by us.

3. Keyboard

Chosing your keyboard type is pretty simple , you should be displayed a list 
of keyboards all begining with Amiga and ending with something like us , de 
etc , these extensions are the different countries , so US is unitedstates 
etc . select the one that matches your machine. UK people will probaly feel 
left out here as there is no UK keymap in the list , select the US one , it 
will work enough for now ( we can switch it for a UK map later ) but 
remember that some keys will be switched around such as the £ function of 
the 3 key is now #. People with keyboard adaptors should also select a 
keyboard that matches their original amiga keyboard but keep in mind that 
you may have to search about for keys on some adaptors , some early adaptors 
like mine ; you have to use caps lock as ctrl in amigaOs and linux.

3. Network

The APUS kernels supports PCMCIA network cards ( ones which will work on 
AmigaOS also ) , for this you will either need a clip on CC_Reset fix , Have 
a CC_Reset fix done directly to the board or it may be possible to use an 
AmigaOS side reset patch on start-up.

3. Partitions

To create the partitions the installer presents use with Amiga-Fdisk , 
anyone that has install OpenBSD should be fimilar with this sort of tool.

3. Base Install

This is the last leg of this part of the journey :) , here we get some files 
down on disk and create yourselves a Debian system , i hope your excited.

The first thing the installer asks you is the installation media or source , 
if your using a CD-ROM like me you want to select the CD-ROM option from the 
top of the list , otherwise you will need to select another source , 
information on these will be added later. If you do select the CD-ROM option 
Debian should detect you cd rom and mount it.

Once your selected your source debian should tell you its searching the 
source for the files it needs , It might present you with a messege asking 
if this is the correct path , it hasn't failed me yet and i've installed it 
4 or 5 times so just hit enter . Now you will see the progress as debain 
fetchs , checks and installs the various parts of the base system. If all 
goes will it should bring you back to the main installtion menu. Now select 
reboot system . The system should shutdown and reset , at this point amigaOs 
will kick in again and boot amigaOs off of the harddrive.

Now more on to the post install , i will explain how to create your final 
boot hack line here.

4. Post Install

4.1 Final BootHack Line

Now you have your base system installed you no longer need the Debian 
Installer ram disk image. Your boot hack line should be abit like this:

Bootstrap --APUS -k <kernel path> root=/dev/<harddrive + partition that 
contains the debain base install> <kernel options>

4.2 Base Config

Once booted your new debian system should run the Base-Config script , this 
sets up the little things in the the system like time zone and more 
importantly Apt-get sources which are used to install new software into the 
system. If you need help on Base-Config you should look at the Debian site , 
as its really platfrom indepentant.

TIP : From experience early 2.2.X apus kernels and possibly the one supplied 
on the debian CD-ROM don't read the time correctly , mine currently thinks 
its 1902 , its not a big problem but something to look out for.

4.3 Kernel modules

coming soon

5. What now ?

What now ? Well the next guide will probaly be setting up Xfree86 and a 
desktop environment ... But alas i can't get kernels that do the PCI Probe 
to work on my system and therefor can't run Xfree86 to write a guide on it 
:\ .



Appendix A. Getting and burning a debian iso.

Currently the only way to get any of the Debian Woody iso's is JigDo . JigDo 
basically downloads the individual files inside the iso and rebuilds it. 
This way is not only quicker but your less likely to get CRC error and have 
to download the ISO all over again. you can also upgrade old ISO's by 
scanning them with JigDo and then it will go and download the need files. It 
also saves time when crossing CPU's . Scanning a debian woody PPC cd before 
getting a X86 one will save ~200 meg of downloading.

The problem with JigDo is that at this time there is no amigaOs port , So 
you'll need a Windows or Linux machine to use it.



Appendix B. BootHack settings

Storage / Interfaces

IDE=Doubler - Provides support for 4-way buffered interfaces

nobats - Blizzard users with scsi disks will need to use the "nobats" 
option.



Graphics

video=pm2fb - FrameBuffer driver for Premedia 2 based cards e.g. 
BlizzardVision and CyberVisionPPC

video=amifb - FrameBuffer driver for Amiga Chipset Graphics.

Memory

60nsram - People with 60ns ram can also use the 60nsram option.

Debugging Options

debug=mem

Appendix C. Trouble shooting





-Daniel Palmer


_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com

Re: Small request ...

[Daniel P. <cor...@ho...>]

>Hi there

>On 14-Aug-02, Daniel Palmer wrote:

>>If those of your running APUS on Blizzard PPCs ( with blizzardvision
>>also ) have some spare time could you download :
>>http://vgr.com/g-rex/boardtype.lzh and run it ... It'll tell you the
>>revision of your blizzard PPC . Revision 0's like mine are meant to
>>have problems with the Grex .. I don't have a Grex but mine won't boot
>>kernel which do the PCI stuff and i want to see if the Grex bug and
>>this are related

>Version 0 here too.

and you have newer ( not new new kernels , the newer blizzard workable ones 
e.g. not the very early 2.2.10 ones ) kernels working :\ damn , its looking 
like giving up time , its going to be console and 1902 forever lol. Cheers 
for the help

-Daniel Palmer


_________________________________________________________________
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx

Woody

[David J. <jo...@co...>]

Hi,
I have just purchased "woody" and am about to try to install it.
I find that if I try to install as I did with potato the CD doesn't
seem to include the relevant base system. Does this mean i should
install potato again and use apt to update to woody.
I am currently using kernal 2.4.4, do I need to update this and maybe
boothack to get "woody" to install ok.
Are there any idiot proof docs that cover a complete reinstallation
using "woody".

Regards,

Dave

 ( jo...@co... )

Experience is directly proportional to the value of equipment
destroyed.
-- Carolyn Scheppner

Re: Small request ...

[John L. <ch...@la...>]

Hi there

On 14-Aug-02, Daniel Palmer wrote:

> If those of your running APUS on Blizzard PPCs ( with blizzardvision
> also ) have some spare time could you download :
> http://vgr.com/g-rex/boardtype.lzh and run it ... It'll tell you the
> revision of your blizzard PPC . Revision 0's like mine are meant to
> have problems with the Grex .. I don't have a Grex but mine won't boot
> kernel which do the PCI stuff and i want to see if the Grex bug and
> this are related

Version 0 here too.


Regards
-- 
John

"I am the Black Angel, Chaos Bringer I AM POWER!!" Phoenix

mailto:ch...@la... or mailto:lor...@uk...
http://www.lordofchaos.co.uk ICQ 110130385 
Nick = Chaos A1200 BlizzardPPC 240mhz 060/50 BlizzardVision OS3.9

Small request ...

[Daniel P. <cor...@ho...>]

If those of your running APUS on Blizzard PPCs ( with blizzardvision also ) 
have some spare time could you download : http://vgr.com/g-rex/boardtype.lzh 
and run it ... It'll tell you the revision of your blizzard PPC . Revision 
0's like mine are meant to have problems with the Grex .. I don't have a 
Grex but mine won't boot kernel which do the PCI stuff and i want to see if 
the Grex bug and this are related

thanks :)

-Daniel Palmer


_________________________________________________________________
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx

Re: X without the PCI Probe :)

[<ko...@nv...>]

On Fri, 9 Aug 2002, Daniel Palmer wrote:

> Intall the VNCserver and use X remotly , it works flawlessly, and its pretty
> quick , even on my 603e 240mhz over a 10mbit lan :)

How is this better than using xdm/xdmcp?


-- kolla

Re: Won't boot still

[David J. <jo...@co...>]

Hi
Further to my quiery of why linux will not boot, I did change some
warp datatypes but swapped them back but things didn't improve.
If I run snoopdos while trying to boot linux the final thing mentioned
before things freeze and eventually crash are
bsdsocket.library  failed
socket.library      failed
I'm not sure whether this is significant or not.
Also are ixemul.library and ixnet.library an issue in this or not. 
Anyone who is running linux ok, could they let us know what versions
of any relevant libraries, warpos versions, CGFX, etc that they may
be running.
Getting Linux to work in the first place was trouble enough, but
cocking it up with a little bit of tinkering on the Amiga is very
frustrating.
I am desparate for this info to avoid doing this again. I'm sure it as
happened before but I don't know what put it right.

Regards,

Dave

 ( jo...@co... )

Whenever you find that you are on the side of the majority, it is
time to reform.
-- Mark Twain

Re: Won't boot

[Daniel P. <cor...@ho...>]

Have you flashed the BPPC's flash ROM , Changed you PPC.library or WarpOS 
stuff or started using Blizkick etc ?

You may want to try booting from a workbench floppy with the boothack on it 
and launching the kernel from there as you may have a stray patch/hack.

Also get a debug dump , ( IIRC Debug=mem in the boothack and use dmesg 
 >ram:debug.txt to extract it once your back in amigaOS ) and post it here , 
so the experts can have a look and tell you wants up :).

You may find if you've changed something on the PPC you'll only be able to 
boot the old 2.2.10 kernels from the APUS sourceforge page , anything newer 
causes kernel panics after the PCI probe here which is probaly caused by 
something i've done :\



-Daniel Palmer


_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com

Re: Won't boot

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

Hello David

> Up until recently I have had a working Debian system, after some
> recent tinkering on the Amiga side, my Linux setup has ceased booting
> up. What could I have done on the Amiga side that would cause this.
> I am unable to reinstall either as when I try this the system attempts
> to boot the kernal, runs ppcboot_pup, inhibits the drives but ends up
> crashing, then reboots to the Amiga Workbench.

I don't remember correctly if I had a similar problem once, but as you have
OS3.5 you may be able to get the warpos kernel running instead of pup, so
bootstrap will start with ppcboot_wup if you have that installed (guess it
should automatically be delivered within the bootstrap archive).

> Do I need certain libraries that may have been lost?

No idea! Have you changed some stuff concerning pup/warpos?

> I have not touched the amiga partition that includes all the relevant
> Linux bootup bits and pieces so am at a loss.
> Any help would be great, as I have just ordered "Woody" and want to be
> ready for when it arrives.

-- 
Good luck,
Andi

Re: Won't boot

[David J. <jo...@co...>]

Hi,
Up until recently I have had a working Debian system, after some
recent tinkering on the Amiga side, my Linux setup has ceased booting
up. What could I have done on the Amiga side that would cause this.
I am unable to reinstall either as when I try this the system attempts
to boot the kernal, runs ppcboot_pup, inhibits the drives but ends up
crashing, then reboots to the Amiga Workbench.
Do I need certain libraries that may have been lost?
I have not touched the amiga partition that includes all the relevant
Linux bootup bits and pieces so am at a loss.
Any help would be great, as I have just ordered "Woody" and want to be
ready for when it arrives.

Regards,

Dave

 ( jo...@co... )

(A1200 PPC+Bvision OS3.5)

I know not with what weapons World War III will be fought, but World
War IV will be fought with sticks and stones.
-- Albert Einstein

X without the PCI Probe :)

[Daniel P. <cor...@ho...>]

Well i can't get the PCI Probe to work so no native X for me , but for 
anyone else with this problem there is hope ...

Intall the VNCserver and use X remotly , it works flawlessly, and its pretty 
quick , even on my 603e 240mhz over a 10mbit lan :)

/me just has to get it to stop thinking its 1902 now :\


-Daniel Palmer


_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com

Re: CSPPC scsi

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

Hello Alan

On 02-ao=FBt-02, you wrote:

> hi,

>> Is there any progress on getting Scsi working on the Cyberstorm PPC ca=
rds?

> yes. the card is initialised and the disks can be probed...but for
> full access there are some SCRIPTS (the controller chip) issues.

> One the the developers currently has some dead disks so cannot
> continue until this problem is fixed....again (seems to be a curse
> of anyone working on the code for this). =


If the developper need some help (testing) I can help as soon as I get a
new fan for the PPC. I am sorry that I can't use SCSI disks on my A4000, =
but
only IDE. ALl my other machines are fitted with SQCI.

Regards
-- =


    Jean-Paul Pozzi

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

Re: CSPPC scsi

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

hi,

> Is there any progress on getting Scsi working on the Cyberstorm PPC cards?

yes. the card is initialised and the disks can be probed...but for
full access there are some SCRIPTS (the controller chip) issues.

One the the developers currently has some dead disks so cannot
continue until this problem is fixed....again (seems to be a curse
of anyone working on the code for this). 

alan

CSPPC scsi

[Francois P. <fp...@pr...>]

Guys,

Is there any progress on getting Scsi working on the Cyberstorm PPC cards?

Cheers

Francois

Re: Newbie problems , 2.4.x and Xfree86

[Daniel P. <cor...@ho...>]

"..this would be an option if that same kernel/boothack didnt work on a lot 
of other systems that also have latest upgrade.  my BPPC/BVision has 
latestfirmware update...and am pleased to report it works fine (well, 
pre-2.4.14 of course :-) )"

i've tried the latest DCE and Phase5 firmware :/ its confused the hell out 
of me , as everything runs under amigaOS fine.
Maybe i have a bad blizzard vision and it crashes the PCI probe



-Daniel Palmer

Tip of the day : Scanning your woody cd 1 with jigdo when downloading for a 
second arch. will save you ~200 meg of download time :)

_________________________________________________________________
Send and receive Hotmail on your mobile device: http://mobile.msn.com

Re: Getting kernel source tree with only 56k modem

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

On Thu, 2002-08-01 at 12:53, Alan Buxey wrote:

Great rundown on using CVS, Alan. Just one comment:

> > Or maybe there is another possibility to get the sources probably as a =
whole
> > archived and compressed file (than I would be able to use the download
> > manager function within IBrowse, that allows me to continue an aborted =
download)?
>=20
> there are CVS tarballs built nightly....
>=20
> ( http://cvs.sourceforge.net/cvstarballs/linux-apus-cvsroot.tar.gz )

That's the repository though, not a checked out tree. Not what you
normally want.


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

Re: Getting kernel source tree with only 56k modem

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

hi,

> sorry for my probably mean question, but I want to know if there is another
> possibility getting latest APUS kernel sources besides downloading the whole
> CVS tree. Due to the fact that I only own a 56k modem doing the above
> mentioned would block my phone for hours (at least)!

actually, using 'cvs' with the compressions options, downloading
the CVS version is as fast as downloading a .tar.gz archive of the kernel.

> Unfortunately I'm not very common using CVS but I think that there is an
> option that allows downloading only changed parts compared to an locally
> existent version (the latest source version I own completely is something around
> 2.4.9)!?
> Do I have to use sshell while connecting to CVS?

its best to use ssh....

setenv CVS_RSH=ssh


if your 2.4.9 was a CVS download, then yes, you can just download the 
changed parts...if not, then CVS doesnt know what you've got
and your really best off getting the new kernel.

I recommend having a .cvsrc file with the following lines in it...
------8<----cut here---
# lately it looks like sf.net has some problems with compressed access
# to CVS so if you are experiencing some hangs in cvs update remove '-z3'
cvs -z3 -q
diff -u -b -B
update -P -d
checkout -P
------8<---cut here----

then:

mkdir /home/my_place/kernel2.4
cd /home/my_place/kernel2.4
cvs -d:pserver:ano...@cv...:/cvsroot/linux-apus login
(just press enter for password)
cvs -d:pserver:ano...@cv...:/cvsroot/linux-apus co 2.4

from this point on, just 'cd' to your 2.4 directory and run 'cvs update'

 
> Or maybe there is another possibility to get the sources probably as a whole
> archived and compressed file (than I would be able to use the download
> manager function within IBrowse, that allows me to continue an aborted download)?

there are CVS tarballs built nightly....

( http://cvs.sourceforge.net/cvstarballs/linux-apus-cvsroot.tar.gz )


alan

Re: Newbie problems , 2.4.x and Xfree86

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

hi,


> I'm CC:'ing the list, hoping that others can benefit.

A usually try to...but for some reason my procmail is munging my emails
so when i (r)eply, it only goes to orig sender, and not the list :-(
(some mutt problem too i think!)
 
> The funny thing is that the PCI code is taken from pm2fb. The X problem
> might be related, my only guess is that it's somehow related to the
> Firmware upgrade.

..this would be an option if that same kernel/boothack didnt work on a lot
of other systems that also have latest upgrade.  my BPPC/BVision has latest
firmware update...and am pleased to report it works fine (well, pre-2.4.14
of course :-) )

alan