linuxdc-dev — Developer discussion list

[linuxdc-dev] Looking to help out

[Mike B. <mik...@ho...>]

Hi
    I'm just getting started with my dreamcast.  I've built both Bill's =
distribution as well as the Debian port.  Haven't been able to get a =
build from scratch to boot yet, it just resets my DC after the Sega =
splash screen.  I've seen messages in the archives where other's have =
had the same problem.  Once I get that solved, I'll be on my way to =
doing something productive.

    So, what's a productive thing to do to help the cause?  I'm a good =
embedded systems developer with lots of years under my belt, but am new =
at this Linux stuff.  I would like to work on a driver project (or a =
part of one) that's not too difficult.  Anyone have suggestions as to =
where I can lend a hand once I get a good build environment up and =
running?

-Mike

Re: [linuxdc-dev] Successful booting of Linux on Dreamcast

[M. R. B. <mr...@0x...>]

* Gregg C Levine <dr...@wo...> on Sat, Sep 21, 2002:

> Hello from Gregg C Levine
> My point? Adrian you disappoint me. To quote Lord Vader, "I find your lack
> of faith disturbing.". I thought it was obvious. It works here, on my
> machine. It should work on everyone's, but there must be a few that it won't
> work on. Why? Have you tried it? Was it your first one, that you tried? Of
> course it was. This is mine. Even the kernel-boot stuff stored in the kernel
> booter tar file, does not even come close.

Please take this offlist.

M. R.

Re: [linuxdc-dev] Successful booting of Linux on Dreamcast

[Gregg C L. <dr...@wo...>]

Hello from Gregg C Levine
My point? Adrian you disappoint me. To quote Lord Vader, "I find your lack
of faith disturbing.". I thought it was obvious. It works here, on my
machine. It should work on everyone's, but there must be a few that it won't
work on. Why? Have you tried it? Was it your first one, that you tried? Of
course it was. This is mine. Even the kernel-boot stuff stored in the kernel
booter tar file, does not even come close.
Gregg C Levine dr...@wo...
"Oh my!" The Second Doctor's nearly favorite phrase.
----- Original Message -----
From: "Adrian McMenamin" <ad...@mc...>
To: <lin...@li...>
Sent: Saturday, September 21, 2002 7:50 PM
Subject: Re: [linuxdc-dev] Successful booting of Linux on Dreamcast


> On Saturday 21 Sep 2002 11:22 pm, Gregg C Levine wrote:
> > [Cross posting to LinuxDC, and Ecos Discussion, and DCdev, apologies if,
as
> > I, people receive multiple copies.]
> > Hello from Gregg C Levine
> > I have successfully booted on my Dreamcast, the Linux arrangement,
created
> > by the group at www.m17n.org for the Dreamcast, using the ECOS Red Boot
> > loader, Debian Linux, as the source materials. It came up with out any
> > problems. The image was written to a CD-R, using a DiskJuggler image,
> > graciously created and provided by Adrian O'Grady, from his website,
> > www.fivemouse.com It happens that this DiskJuggler image, is ready burn
to
> > a CD-R, and works out of the sleeve. However, he does provide two pieces
of
> > documentation to explain most of the things people would need to know.
> > Gregg C Levine dr...@wo...
> > "Oh my!" The Second Doctor's nearly favorite phrase.
>
> Yes, we know it boots. The photos on the site tell you that much. What,
> exactly, is your point?
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Linuxdc-dev mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxdc-dev
>

Re: [linuxdc-dev] Successful booting of Linux on Dreamcast

[Adrian M. <ad...@mc...>]

On Saturday 21 Sep 2002 11:22 pm, Gregg C Levine wrote:
> [Cross posting to LinuxDC, and Ecos Discussion, and DCdev, apologies if, as
> I, people receive multiple copies.]
> Hello from Gregg C Levine
> I have successfully booted on my Dreamcast, the Linux arrangement, created
> by the group at www.m17n.org for the Dreamcast, using the ECOS Red Boot
> loader, Debian Linux, as the source materials. It came up with out any
> problems. The image was written to a CD-R, using a DiskJuggler image,
> graciously created and provided by Adrian O'Grady, from his website,
> www.fivemouse.com It happens that this DiskJuggler image, is ready burn to
> a CD-R, and works out of the sleeve. However, he does provide two pieces of
> documentation to explain most of the things people would need to know.
> Gregg C Levine dr...@wo...
> "Oh my!" The Second Doctor's nearly favorite phrase.

Yes, we know it boots. The photos on the site tell you that much. What, 
exactly, is your point?

[linuxdc-dev] Successful booting of Linux on Dreamcast

[Gregg C L. <dr...@wo...>]

[Cross posting to LinuxDC, and Ecos Discussion, and DCdev, apologies if, as
I, people receive multiple copies.]
Hello from Gregg C Levine
I have successfully booted on my Dreamcast, the Linux arrangement, created
by the group at www.m17n.org for the Dreamcast, using the ECOS Red Boot
loader, Debian Linux, as the source materials. It came up with out any
problems. The image was written to a CD-R, using a DiskJuggler image,
graciously created and provided by Adrian O'Grady, from his website,
www.fivemouse.com It happens that this DiskJuggler image, is ready burn to a
CD-R, and works out of the sleeve. However, he does provide two pieces of
documentation to explain most of the things people would need to know.
Gregg C Levine dr...@wo...
"Oh my!" The Second Doctor's nearly favorite phrase.

Re: [linuxdc-dev] Admitting defeat

[Adrian M. <ad...@mc...>]

On Friday 20 Sep 2002 9:44 pm, M. R. Brown wrote:
> * Adrian McMenamin <ad...@mc...> on Fri, Sep 20, 2002:
> > I have created a sf project called vmublk in case I need to mess about
> > with these files in the future - unlikely, but I wanted to keep the
> > option without having to poke about in the main linuxdc cvs.
>
> Heh, well, since all of this is development code, you could've:
>
> a) left in vmublk in the HEAD trunk, and just provided alternate Config.in
>    options to select your impl. vs. mtdblock,
>
Well, that would be quite easy, I suppose. But I can see no real reason (at 
present) to use my implementation.

> b) or, just create your own branch (sth. like "vmublk-testing") and do
>    development there.  Paul or myself can help you out with that if you
>    want.

Well, I suppose I could do that - tell me how.

>
> > Okay, now for the filesystem!
>
> I'm looking forward to your results (as I'm sure everyone else is).
>
So am I!

I have a problem though - as I have just posted on irc....
<zx80user> I've started work on the fs now. But I have one problem.... how to 
set a magic number
<zx80user> I can find no guide to this on net at all
<zx80user> and the vmu doesn't appear to really have a native one either
<zx80user> <presumably because it's not really designed to be mounted by a 
linux vfs driver :-) >

Anybody here know the answer to this? Do I have to bother one of the 
uberhackers on lkml (scary!)?



> M. R.

Adrian

Re: [linuxdc-dev] Admitting defeat

[M. R. B. <mr...@0x...>]

* Adrian McMenamin <ad...@mc...> on Fri, Sep 20, 2002:

>=20
> I have created a sf project called vmublk in case I need to mess about wi=
th=20
> these files in the future - unlikely, but I wanted to keep the option wit=
hout=20
> having to poke about in the main linuxdc cvs.
>=20

Heh, well, since all of this is development code, you could've:

a) left in vmublk in the HEAD trunk, and just provided alternate Config.in
   options to select your impl. vs. mtdblock,

b) or, just create your own branch (sth. like "vmublk-testing") and do
   development there.  Paul or myself can help you out with that if you
   want.

> Okay, now for the filesystem!
>=20

I'm looking forward to your results (as I'm sure everyone else is).

M. R.

Re: [linuxdc-dev] Admitting defeat

[Adrian M. <ad...@mc...>]

On Thursday 19 Sep 2002 10:45 pm, Adrian McMenamin wrote:
> Well, my vmublk saves a whole 1.25k in the compiled zImage kernel, so I
> suppose that hardly justifies using it (though my nick does indicate that I
> used to write programs for a machine with 1K of RAM :->).
>
> Bear with me and I'll remove it in the next few days.
>
Made a slight mess of this with the cvs (though successfully deleted the files 
- or kicked them into the attic).

I have created a sf project called vmublk in case I need to mess about with 
these files in the future - unlikely, but I wanted to keep the option without 
having to poke about in the main linuxdc cvs.

Okay, now for the filesystem!

Adrian

[linuxdc-dev] Admitting defeat

[Adrian M. <ad...@mc...>]

Well, my vmublk saves a whole 1.25k in the compiled zImage kernel, so I 
suppose that hardly justifies using it (though my nick does indicate that I 
used to write programs for a machine with 1K of RAM :->).

Bear with me and I'll remove it in the next few days.

Adrian

Re: [linuxdc-dev] Tried my best. Can't get anything to work

[<ad...@mc...>]

art...@gm... wrote:
> Please allow me to slip in with a few more questions. I'm currently
> using Bgat's toolchain. Why? Because when I heard about this project, I
> also stumbled across Mr. Gatliff's article, which was well written
> (IMHO) and got me going right away. But this was written back in 2001.
> 
My toolchain is now 10 months old, but is slightly more up to date than bgat's - and while I had problem's with bgat's toolchain, others haven't, so it was probably just down to me.

RE: [linuxdc-dev] Tried my best. Can't get anything to work

[Starman <sta...@co...>]

The reason I haven't tried it again lately is because I installed a new
Radeon 9700 in my PC that I use to triple-boot with (Linux of course
being one of the options) and Linux's X choked on the new video card. I
have no X. I know I can do the work without it, but using lynx is a
serious pain in the neck. I'm working on making a new dedicated Linux
PC.

Mike

Re: [linuxdc-dev] Tried my best. Can't get anything to work

[Arthur O. <art...@gm...>]

Please allow me to slip in with a few more questions. I'm currently
using Bgat's toolchain. Why? Because when I heard about this project, I
also stumbled across Mr. Gatliff's article, which was well written
(IMHO) and got me going right away. But this was written back in 2001.

I'm sure alot has progressed since then, and I want to know what
toolchain everyone is using as of now. I ask this because I want to be
at par with the rest :) I managed to build TinyLogin with BGat's
toolchain, but haven't got the chance to test it yet. Has anyone been
successfull in this area?

I came across the toolchain at sf, a disorganised archive at
ftp.m17n.org and also heard about the GCC 3.2/uClibc that's being worked 
on. All I need is some clarification as to which one to use.
Thanks.

Arthur

Adrian McMenamin wrote:

  > On Monday 16 Sep 2002 4:30 pm, Starman wrote:
  >
  >>I built the cross-compiling tools and the kernel. I did everything the
  >>article said to do.
  >>I don't know what else there is to explain. I followed the steps in the
  >>article one by one.
  >>
May I ask which article you are refering to? Because with BGat's article
I managed to get a bootable system...
  >
  > Sorry, not to be more helpful, but.... did you do all the following:
  >
  > Download a stock 2.4.18 kernel from kernel.org or mirror?
  >
  > Download the linux-sh sources from their CVS?
  >
  > Download the linux-sh-dc sources from our CVS?
  >
  > Use treelink.sh to drop these on top of 2.4.18 kernel?
And yes, Adrian pointed this out to me (Hub5_) on #linuxdc some time back ;)
  > Or did you use the files with bgat's article (which would work)
  >
  > PS there is an irc channel #linuxdc at irc.openprojects.net if you
want to
  > drop by for a chat.
  >
  >
  > -------------------------------------------------------
  > This sf.net email is sponsored by:ThinkGeek
  > Welcome to geek heaven.
  > http://thinkgeek.com/sf
  > _______________________________________________
  > Linuxdc-dev mailing list
  > Lin...@li...
  > https://lists.sourceforge.net/lists/listinfo/linuxdc-dev
  >
  >
  >

Re: [linuxdc-dev] vmublk

[M. R. B. <mr...@0x...>]

* Adrian McMenamin <ad...@mc...> on Wed, Sep 18, 2002:

> There is now a block device driver for the vmu in the cvs. This is very=
=20
> closely modelled on the existing mtdblock driver - though is, IMHO, bette=
r=20
> suited to a small footprint system like the DC (it's amaller code),=20
> particularly with its small erase size on its flash (it doesn't employ th=
e=20
> same cacheing mechanism).
>=20

How much less of a footprint does your driver offer than the standard
mtdblock?  Is it on the order of megabytes, hundreds of kilobytes, what?
Is there any other reason we should deviate from the standard code?  How's
the caching mechansim different?

M. R.

[linuxdc-dev] vmublk

[Adrian M. <ad...@mc...>]

There is now a block device driver for the vmu in the cvs. This is very 
closely modelled on the existing mtdblock driver - though is, IMHO, better 
suited to a small footprint system like the DC (it's amaller code), 
particularly with its small erase size on its flash (it doesn't employ the 
same cacheing mechanism).

But I know other disagree, so use it before it gets bombed out of the CVS by 
someone more important than me!

Adrian

[linuxdc-dev] vmu file system

[Adrian M. <ad...@mc...>]

Having read up some more on how file systems are implemented in Linux, I 
realise that I have not got everything right (no change there then). The code 
I have got works, but it is only a small part of what needs to go into a 
filesystem.

This is what i am now going to try to do:

1. Restructure (and rename) vmuflash-fs.c in CVS to vmublk.c and add it as a 
block device driver option for mtd devices

2. Build a read only vmufs first (read only fses are meant to be 'easy' - the 
guy who wrote the BFS fs driver said he wrote his RO BFS driver in 10 hours).

3. Turn that into a RW fs driver (said to be the remaining 95% of the work).


So if you are subscribed to the CVS list and start seeing lots of messages 
flying about, you will know what is going on.

Adrian

[linuxdc-dev] Kernel boot loader works, a few questions remain

[Gregg C L. <dr...@wo...>]

Hello from Gregg C Levine
I have downloaded the Kernel Boot loader, and examined its contents.I have
created the necessary tools, actually installed them, via the RPM file also
available there. It works on my Dreamcast, and via my system. I now need to
build the gdb stub, as described via the readme contained within. How so?
How can that stub be built? Or has anyone actually built one? Also, are the
"sources" available for the initial root device? I would like to update the
busybox item contained within, to a newer version, from 0.50 to 0.60.1. This
is running on Slackware 8.0, here.
Gregg C Levine dr...@wo...
"Oh my!" The Second Doctor's nearly favorite phrase.

Re: [linuxdc-dev] Question about bootstrapping. . .

[Matt G. <mg...@cm...>]

I've got this same problem right now.  I upgraded to the latest
toolchain patches available at ftp.m17n.org, got linux-2.4.18
from a kernel mirror, got the linux-sh and linux-sh-dc trees from
their respective SF CVS servers, used treelink appropriately,
compiled my kernel and tried to boot it using dcload.  As soon as
the file loads and begins to execute, the DC reboots.  To be
clear, no kernel startup messages appear to be printed before the
thing reboots.  Also, I was able to recompile and boot the kernel
source I got from Gatliff's article with my upgraded toolchain
just not 2.4.18-sh-dc.  Any suggestions?  

fyi, I'm 'inflex' on #dclinux.

-Matt

On Mon, Sep 16, 2002 at 02:46:41PM -0400, ZhayTee wrote:
> Using the kernel-boot and sh4-cross-tools package provided on the
> sourceforge linuxdc project page, I managed to create a working
> 1ST_READ.BIN, or so I thought. Unfortunately, my dreamcast reboots after
> showing the SEGA license screen, so it's obviously not working properly. I
> can successfully burn and boot a disc featuring a 1ST_READ.BIN which hasn't
> been created on my system (such as the one which exists on the distribution
> by the cool and froody guys at m17n.org; it's just the ecos bootloader, but
> it does load properly), so it's rather obvious that I'm doing something
> wrong at some point when building my 1ST_READ.BIN.
> 
> The only place I can see an error is here:
> 
> [root@slartibartfast] ~/dc/kernel-boot# make kernel-boot.bin
> sh4-linux-objcopy -I binary -O elf32-sh-linux zImage.bin zImage.o
> sh4-linux-objcopy: Warning: Output file cannot represent architecture
> UNKNOWN!
> sh4-linux-objcopy -I binary -O elf32-sh-linux initrd.bin initrd.o
> sh4-linux-objcopy: Warning: Output file cannot represent architecture
> UNKNOWN!
> sh4-linux-gcc -ml -m4 -o kernel-boot.elf kernel-boot.S zImage.o
> initrd.o -nostdlib -nostartfiles -T boot.lds
> sh4-linux-objcopy -O binary kernel-boot.elf kernel-boot.bin
> [root@slartibartfast] ~/dc/kernel-boot#
> 
> The kernel-boot.bin file is created, but those warnings from objcopy don't
> exactly look healthy.
> 
> Any help would be appreciated. I'm so close, yet so far. :P
> 
> --JT
> http://zhaymusic.com/
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Linuxdc-dev mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxdc-dev

-- 
Matt Gumbel <mg...@cm...>
Computer Engineering student at the University of Illinois

Re: [linuxdc-dev] Tried my best. Can't get anything to work

[<ad...@mc...>]

dr...@wo... wrote:
 Are there plans to have anything else hosted there?

No. I don't have the bandwidth.

Re: [linuxdc-dev] Tried my best. Can't get anything to work

[Gregg C L. <dr...@wo...>]

Hello from Gregg C Levine
Adrian, I visited your site. Downloaded the "kernel-boot.elf", and
"kernel-boot.elf.gz" files. Recieved a 404 error from that Demon, when I
attempted to explore the other parts of your website. It indicated that the
documents, and downloads portions of the site from
http://www.mcmen.demon.co.uk.for dc section, that is on dcweb. I also tried
out the actual file, "kernel-boot.elf", via the serial loader functions that
I use here, that's the "dc load 1.0.3" version from Napalm. And it worked,
as expected, complaining about not finding your NFS server, and panicing
when it reached the space where it was supposed to find the NFS supplied
stuff. Are there plans to have anything else hosted there?
Gregg C Levine dr...@wo...
"Oh my!" The Second Doctor's nearly favorite phrase.
----- Original Message -----
From: <ad...@mc...>
To: "Starman" <sta...@co...>; <lin...@li...>
Sent: Monday, September 16, 2002 11:16 AM
Subject: Re: [linuxdc-dev] Tried my best. Can't get anything to work


> sta...@co... wrote:
> > Hi all,
> >   I had stated in a previous email that I couldn't get some of the files
> > to download from the article's web site. I guess it was just that one
> > time because I was finally able to get all the files, including busybox
> > 0.60.? from the site that Adrian had mentioned.
> >
> >   My system is RedHat 7.3, no modifications or updates - straight from
> > the CD iso images. I ran as root as the article stated and followed
> > everything to the letter - many times.
> >
> >   What I get is that the DC boots, I get the "Napalm" screen, and then
> > the DC just sits there at that screen. I checked the .config file for
> > the kernel configuration, made sure that the binary images were up to
> > date, and still I can't boot Linux at all. The CD-Rs I'm using have
> > worked before with other homebrew projects (except my DC can't run Quake
> > but my nephew's can).
> >
> You have built the cross compiling tools and your kernel? It's not clear.
>
> Assuming all these are built, what commands are you issuing? And what is
the response on the RH box?
>
> If you can boot the ip-loader, or whatever, you don't need to make more
coasters. It's just not clear what you are doing here, please explain some
more.
>
> (NB: there is a working kernel (NFS) on my web site at
http://www.mcmen.demon.co.uk.
>
>
> >   It's very frustrating. I burned about a dozen coasters already. I
> > really just want to get Apache running, but the Disk Juggler image
> > that's out there (20010615 I think it's called) gives me a segementation
> > fault when I try to start the Apache server using "apachecfg start".
> >
> >   Anything I might be missing?
> >
> > Mike
> >
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Linuxdc-dev mailing list
> > Lin...@li...
> > https://lists.sourceforge.net/lists/listinfo/linuxdc-dev
> >
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Linuxdc-dev mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxdc-dev
>

RE: [linuxdc-dev] Tried my best. Can't get anything to work

[Starman <sta...@co...>]

Starman

-----Original Message-----
From: Adrian McMenamin [mailto:ad...@mc...] 
Sent: Monday, September 16, 2002 3:54 PM
To: Starman; lin...@li...
Subject: Re: [linuxdc-dev] Tried my best. Can't get anything to work


On Monday 16 Sep 2002 8:44 pm, Starman wrote:
> I did download the 2.4.18 kernel from kernel.org.
>
> I didn't grab the CVS sources from those two sites, I just used the
ones
> in the article.
>
> I'll try the CVS thing today.
>
> I was on #linuxdc 4x already. I guess everyone's idle when I'm there.
>
What nic?

(So next time I know and talk directly)

Adrian (zx80user)

Re: [linuxdc-dev] Tried my best. Can't get anything to work

[Adrian M. <ad...@mc...>]

On Monday 16 Sep 2002 8:44 pm, Starman wrote:
> I did download the 2.4.18 kernel from kernel.org.
>
> I didn't grab the CVS sources from those two sites, I just used the ones
> in the article.
>
> I'll try the CVS thing today.
>
> I was on #linuxdc 4x already. I guess everyone's idle when I'm there.
>
What nic?

(So next time I know and talk directly)

Adrian (zx80user)

RE: [linuxdc-dev] Tried my best. Can't get anything to work

[Starman <sta...@co...>]

I did download the 2.4.18 kernel from kernel.org.

I didn't grab the CVS sources from those two sites, I just used the ones
in the article.

I'll try the CVS thing today.

I was on #linuxdc 4x already. I guess everyone's idle when I'm there.

I guess the next step would be to show logs of everything. Maybe that'll
help others.

Mike

-----Original Message-----
From: Adrian McMenamin [mailto:ad...@mc...] 
Sent: Monday, September 16, 2002 3:39 PM
To: Starman
Cc: lin...@li...
Subject: Re: [linuxdc-dev] Tried my best. Can't get anything to work


On Monday 16 Sep 2002 4:30 pm, Starman wrote:
> I built the cross-compiling tools and the kernel. I did everything the
> article said to do.
>
> I don't know what else there is to explain. I followed the steps in
the
> article one by one.
>

Sorry, not to be more helpful, but.... did you do all the following:

Download a stock 2.4.18 kernel from kernel.org or mirror?

Download the linux-sh sources from their CVS?

Download the linux-sh-dc sources from our CVS?

Use treelink.sh to drop these on top of 2.4.18 kernel?

Or did you use the files with bgat's article (which would work)

PS there is an irc channel #linuxdc at irc.openprojects.net if you want
to 
drop by for a chat.

Re: [linuxdc-dev] Tried my best. Can't get anything to work

[Adrian M. <ad...@mc...>]

On Monday 16 Sep 2002 4:30 pm, Starman wrote:
> I built the cross-compiling tools and the kernel. I did everything the
> article said to do.
>
> I don't know what else there is to explain. I followed the steps in the
> article one by one.
>

Sorry, not to be more helpful, but.... did you do all the following:

Download a stock 2.4.18 kernel from kernel.org or mirror?

Download the linux-sh sources from their CVS?

Download the linux-sh-dc sources from our CVS?

Use treelink.sh to drop these on top of 2.4.18 kernel?

Or did you use the files with bgat's article (which would work)

PS there is an irc channel #linuxdc at irc.openprojects.net if you want to 
drop by for a chat.

[linuxdc-dev] Question about bootstrapping. . .

[ZhayTee <zh...@zh...>]

Using the kernel-boot and sh4-cross-tools package provided on the
sourceforge linuxdc project page, I managed to create a working
1ST_READ.BIN, or so I thought. Unfortunately, my dreamcast reboots after
showing the SEGA license screen, so it's obviously not working properly. I
can successfully burn and boot a disc featuring a 1ST_READ.BIN which hasn't
been created on my system (such as the one which exists on the distribution
by the cool and froody guys at m17n.org; it's just the ecos bootloader, but
it does load properly), so it's rather obvious that I'm doing something
wrong at some point when building my 1ST_READ.BIN.

The only place I can see an error is here:

[root@slartibartfast] ~/dc/kernel-boot# make kernel-boot.bin
sh4-linux-objcopy -I binary -O elf32-sh-linux zImage.bin zImage.o
sh4-linux-objcopy: Warning: Output file cannot represent architecture
UNKNOWN!
sh4-linux-objcopy -I binary -O elf32-sh-linux initrd.bin initrd.o
sh4-linux-objcopy: Warning: Output file cannot represent architecture
UNKNOWN!
sh4-linux-gcc -ml -m4 -o kernel-boot.elf kernel-boot.S zImage.o
initrd.o -nostdlib -nostartfiles -T boot.lds
sh4-linux-objcopy -O binary kernel-boot.elf kernel-boot.bin
[root@slartibartfast] ~/dc/kernel-boot#

The kernel-boot.bin file is created, but those warnings from objcopy don't
exactly look healthy.

Any help would be appreciated. I'm so close, yet so far. :P

--JT
http://zhaymusic.com/

RE: [linuxdc-dev] Tried my best. Can't get anything to work

[Starman <sta...@co...>]

I built the cross-compiling tools and the kernel. I did everything the
article said to do.

I don't know what else there is to explain. I followed the steps in the
article one by one.

I can't say what the RH's responses were for each command since I don't
have it in front of me at the moment.

I do know that my kernel-boot.elf file is about 680k, which is far
smaller than the one on the web site you pointed at.

If there's anything else I might be leaving out, let me know and I'll
write something up when I get home later, but like I said, I followed
the article's steps PRECISELY. The only differences in the commands were
when I had to add /sbin/ to the names of some commands since /sbin
wasn't in my path. Also, I had to run roash.sh with a 'sh' in front of
it since running 'roast.sh' alone wouldn't work. Whatever files are in
the article are what I used. The only time I did something outside the
bounds of the article was when things weren't going well and after
reading back issues of the mailing list I found that people were using a
different .config file. I downloaded the .config file from the CVS
repository to see if that worked (it didn't). Come to think about it,
there's nothing in the article stating what I should be doing to
configure the kernel so should I assume that what's there by default is
what I should use?

Mike

-----Original Message-----
From: ad...@mc... [mailto:ad...@mc...] 
Sent: Monday, September 16, 2002 11:17 AM
To: Starman; lin...@li...
Subject: Re: [linuxdc-dev] Tried my best. Can't get anything to work


sta...@co... wrote:
> Hi all,
>   I had stated in a previous email that I couldn't get some of the
files
> to download from the article's web site. I guess it was just that one
> time because I was finally able to get all the files, including
busybox
> 0.60.? from the site that Adrian had mentioned.
> 
>   My system is RedHat 7.3, no modifications or updates - straight from
> the CD iso images. I ran as root as the article stated and followed
> everything to the letter - many times.
> 
>   What I get is that the DC boots, I get the "Napalm" screen, and then
> the DC just sits there at that screen. I checked the .config file for
> the kernel configuration, made sure that the binary images were up to
> date, and still I can't boot Linux at all. The CD-Rs I'm using have
> worked before with other homebrew projects (except my DC can't run
Quake
> but my nephew's can).
> 
You have built the cross compiling tools and your kernel? It's not
clear.

Assuming all these are built, what commands are you issuing? And what is
the response on the RH box?

If you can boot the ip-loader, or whatever, you don't need to make more
coasters. It's just not clear what you are doing here, please explain
some more.

(NB: there is a working kernel (NFS) on my web site at
http://www.mcmen.demon.co.uk.


>   It's very frustrating. I burned about a dozen coasters already. I
> really just want to get Apache running, but the Disk Juggler image
> that's out there (20010615 I think it's called) gives me a
segementation
> fault when I try to start the Apache server using "apachecfg start".
> 
>   Anything I might be missing?
> 
> Mike
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Linuxdc-dev mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxdc-dev
>