linux-apus-user

Installation woes

[Kulwant B. <kul...@bt...>]

Hello all,

I am still having trouble installing the 2.4 kernel. Everything I have tried
so far, results in a problem one way or the other. 

I can boot (using boothack bh010623) an installer with bootstrap --apus -k linux.bin -r root.bin root=/dev/ram 60nsram nobats video=pm2fb:mode:1024x768-75

and can subsequently mount the hda1 root and hda3 swap partitions and even an Amiga FFS
partition. I can initialise the network connection (Broadband via PCMCIA ethernet). 

If I try to use the menu command for "Base System Installtion" and choose

1. network as the source, it gets as far as extracting the various files (after validating)
and the progress bar gets all the way to the right with the last file being
extracted being
/target/var/cache/apt/archives/whiptail_0.50.17-9.6_powerpc.deb...

and then I get an error message: 
    debootsrap exited with an error (return value 1)
    <continue>


I have copied the contents of the kernel-image-apus_2.4.20-1.lha from
sourceforge.net to sda2 which I mount as /user or /home. 

2. If I choose the /home or /user as source, then it says that it could not
find a directory containing rescue.bin or apus/drivers.tgz even though I put
them there and I know they are there! 

If I try to "install kernel & driver modules" by using the http source, then I
get a file not found error for apus/images-1.44/rescue.bin and
apus/drivers.tgz. 

I remember seeing a message about not being able to find basedebs.tar at one
point too, but cannot remember how I got that. 

What am I doing wrong? 

Kind regards,

Kulwant

Re: Installation woes

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

On Mit, 2003-01-22 at 00:10, Kulwant Bhogal wrote: 
> 
> If I try to use the menu command for "Base System Installtion" and choose
> 
> 1. network as the source, it gets as far as extracting the various files 
> (after validating) and the progress bar gets all the way to the right with 
> the last file being extracted being
> /target/var/cache/apt/archives/whiptail_0.50.17-9.6_powerpc.deb...
> 
> and then I get an error message: 
>     debootsrap exited with an error (return value 1)
>     <continue>

Have you tried booting into the base system after this?


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

Re: Installation woes

[Kulwant B. <kul...@bt...>]

Hello Michel,

Re: Your e-mail (25/01/2003)

> On Mit, 2003-01-22 at 00:10, Kulwant Bhogal wrote: 
>> 
>> If I try to use the menu command for "Base System Installtion" and
>> choose 
>> 1. network as the source, it gets as far as extracting the various files 
>> (after validating) and the progress bar gets all the way to the right
>> with  the last file being extracted being
>> /target/var/cache/apt/archives/whiptail_0.50.17-9.6_powerpc.deb...
>> 
>> and then I get an error message: 
>>     debootsrap exited with an error (return value 1)
>>     <continue>

> Have you tried booting into the base system after this?

Yes, it starts to boot up but I get a kernel panic when it tries to set the
system clock from the hardware clock. I can boot into a bash shell on the
installation partition though. I downloaded the 2.4.20 kernel (because
somebody suggested trying a newer kernel) and renamed
vmlinuz to linux.bin (because I read in one of the archived mails that
vmlinux is the linux.bin file) and that would not boot either - it kernel panics
almost straight away. I am not sure if I need to get a new root.bin file
from somewhere to go with it.

Krystian suggested installing ksymoops, but as you can see from my other
post, this was not successful either. I have been going through the archived
mails to this ML and I saw somewhere that I could remove the commands from
the boot scripts to stop it trying to set the system clock, but I have not
figured out how to do this yet.  

Any help will be much appreciated.

Kind regards, 

Kulwant

Re: Installation woes

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

On Sat, 2003-01-25 at 10:55, Kulwant Bhogal wrote: 
> 
> > On Mit, 2003-01-22 at 00:10, Kulwant Bhogal wrote: 
> >> 
> >> If I try to use the menu command for "Base System Installtion" and
> >> choose 
> >> 1. network as the source, it gets as far as extracting the various files 
> >> (after validating) and the progress bar gets all the way to the right
> >> with  the last file being extracted being
> >> /target/var/cache/apt/archives/whiptail_0.50.17-9.6_powerpc.deb...
> >> 
> >> and then I get an error message: 
> >>     debootsrap exited with an error (return value 1)
> >>     <continue>
> 
> > Have you tried booting into the base system after this?
> 
> Yes, it starts to boot up but I get a kernel panic when it tries to set the
> system clock from the hardware clock. 

Doing anything more with the installer is unlikely to change that.

> I can boot into a bash shell on the installation partition though. I 
> downloaded the 2.4.20 kernel (because somebody suggested trying a newer 
> kernel) and renamed vmlinuz to linux.bin (because I read in one of the 
> archived mails that vmlinux is the linux.bin file) 

Yes, it's the kernel image, but you need not rename it, just change the
argument to bootstrap.

> and that would not boot either - it kernel panics almost straight away. I 
> am not sure if I need to get a new root.bin file from somewhere to go with it.

root.bin is the installer ramdisk, you don't need it after installation.

> I have been going through the archived mails to this ML and I saw somewhere 
> that I could remove the commands from the boot scripts to stop it trying 
> to set the system clock, but I have not figured out how to do this yet.  

Try mv /etc/init.d/hwclock* /root/ .


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

Re: Installation woes

[Kulwant B. <kul...@bt...>]

Hello Michel,

>> Yes, it starts to boot up but I get a kernel panic when it tries to set
>> the system clock from the hardware clock. 

> Doing anything more with the installer is unlikely to change that.

Well I was told an more recent kernel might help, so was only trying to use
the installer to install a more up to date kernel - except I'm not sure if I
am starting with the right files as the installer always complains in one
way or another (e.g. debootsrap exited with an error (return value 1) or
can't find basedebs.tar or file not found on http:http.us.debian.org/debian). 

>> kernel) and renamed vmlinuz to linux.bin (because I read in one of the 
>> archived mails that vmlinux is the linux.bin file) 

> Yes, it's the kernel image, but you need not rename it, just change the
> argument to bootstrap.

Well in any case it simply kernel panics at an even earlier stage than the
clock bit so something somewhere is not right. 

> root.bin is the installer ramdisk, you don't need it after installation.

So can you think why 2.4.20 would crash almost straight away when 2.2 gets as far as
trying to set the system clock? 

>> I have been going through the archived mails to this ML and I saw
>> somewhere  that I could remove the commands from the boot scripts to
>> stop it trying  to set the system clock, but I have not figured out how
>> to do this yet.  

> Try mv /etc/init.d/hwclock* /root/ .

OK, I tried this and the system still crashes when it tried to set the
system clock. I rebooted again into bash and the hwclock* files were back in
/etc/init.d

I remember somebody saying that Linux has to be told to save all changes to
disk. How do I do this? 

Are there any negative consequences to be expected from not having the
hwclock stuff run at startup? Why does Linux not trust the HWClock to do
it's job? 

Kulwant



 

Re: Installation woes

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

On Sun, 2003-01-26 at 18:41, Kulwant Bhogal wrote: 
> 
> >> Yes, it starts to boot up but I get a kernel panic when it tries to set
> >> the system clock from the hardware clock. 
> 
> > Doing anything more with the installer is unlikely to change that.
> 
> Well I was told an more recent kernel might help, so was only trying to use
> the installer to install a more up to date kernel - except I'm not sure if I
> am starting with the right files as the installer always complains in one
> way or another (e.g. debootsrap exited with an error (return value 1) or
> can't find basedebs.tar or file not found on http:http.us.debian.org/debian). 

You don't really need to installer for that as the kernel itself is
needed on the AmigaOS side (the installer may help for installing the
modules, in case you need one of those for booting into the base system,
but you certainly don't need the base system steps of the installer to
do it).


> >> kernel) and renamed vmlinuz to linux.bin (because I read in one of the 
> >> archived mails that vmlinux is the linux.bin file) 
> 
> > Yes, it's the kernel image, but you need not rename it, just change the
> > argument to bootstrap.
> 
> Well in any case it simply kernel panics at an even earlier stage than the
> clock bit so something somewhere is not right. 

Hard to say anything about that without dmesg output at least.


> >> I have been going through the archived mails to this ML and I saw
> >> somewhere  that I could remove the commands from the boot scripts to
> >> stop it trying  to set the system clock, but I have not figured out how
> >> to do this yet.  
> 
> > Try mv /etc/init.d/hwclock* /root/ .
> 
> OK, I tried this and the system still crashes when it tried to set the
> system clock. I rebooted again into bash and the hwclock* files were back in
> /etc/init.d
> 
> I remember somebody saying that Linux has to be told to save all changes to
> disk. How do I do this? 

With sync, for example, but that's not necessary when the filesystem is
unmounted cleanly, i.e. you reboot cleanly.


> Are there any negative consequences to be expected from not having the
> hwclock stuff run at startup? 

Yes, the system time will likely be off. :)

> Why does Linux not trust the HWClock to do it's job? 

It does, that's why it tries to read the time from the hw clock...


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