Search

[cutterjohn]

Minor bumpage, the 1/28/08 and 2/2/08 are more borked than ever, and I think that Sonny Jim is getting a little pissed, but at least some of the devs actually seem to be paying attention to the thread somewhat now v. (apparently) entirely ignoring it earlier...

[Sonny_Jim]

Hassling people to fix things normally makes them pissed off, especially when they are not being paid for it.

The DSLinux developers DO read your posts but one of the reasons they don't reply as it's annoying being pestered by people to fix something that is out of their control.

I'll post here what I posted in the DSLinux forums:

Unless the current dev's have access to a Supercard DS one it's very hard for us to diagnose and fix problems. You could try contacting the Supercard team to see if they would like to assist or to donate some hardware to a capable developer.

Unless this situation changes, I'm afraid there's not much I can personally do.

[cutterjohn]

How exactly am I hassling you pray tell?  By posting about legitimate problems with dslinux builds and hardware?  It's a good thing that you're exemplerary of mainline linux developers or it would LONG since have been dead.

Hell, you didn't even bother looking, or if you did, you didn't comment, until the other day.

While I appreciate what you have done, don't let it go to your head, as uClinux is a pretty old tree which originally ran on 68XXX Palms.

[Sonny_Jim]

First off, calm down, I'm actually trying to help you and the situation all the SCSD one users are in.  By hassling, I mean your bumping and double posting in the DSLinux forums.  I appreciate it's frustrating that it's not working but unfortunately unless a developer has access to the hardware it's incredibly difficult and time consuming to try and fix these kinds of problems.

Stop being the squeaky wheel.

[cutterjohn]

First off, calm down, I'm actually trying to help you and the situation all the SCSD one users are in.  By hassling, I mean your bumping and double posting in the DSLinux forums.  I appreciate it's frustrating that it's not working but unfortunately unless a developer has access to the hardware it's incredibly difficult and time consuming to try and fix these kinds of problems.

Stop being the squeaky wheel.

Not to be annoying, but the squeaky wheel is usually the one that gets fixed as the old euphemism(and real life) generally goes...

As to double posting, I felt that I was making it quite clear that a) usually several days, if not weeks had past between posts, and I was double posting to ensure that the thread was not ignored as even w/o the hardware it should be of some help to have someone else with the hardware to test builds, and b) before now, no one complained.  (I was also clearly mentioning that I was purposefully double posting such that if anyone had any problems with it, that they'd maybe have jumped in long ago.)

In the future, I'll just not update the dslinux forums thread unless specifically invited to do so.

[EDIT]
One thing to do would be to provide conditional compile options for a DEBUG build with at least printf/k statements or something, sort of like the old LILO (you LInux LOader used to do, and where it crapped out in printing LILO gave some debug hints) with the builds.  I'd be happy to try to run them as often as they came out v. prior releases, or as requested(within reason).

Failing that, I do eventually trying to setup a cross-compiler toolchain on my desktop linux machine, although it has been some years since I've had to bother monkeying around with setting up a cross-compiler environment that doesn't interfere with the normal tool-chain, especially if it cannot be integrated in with the native toolchain.  (Last that I used IIRC were ARM for the iPaq(useless POS the battery/charging subsystem were crap so I always had brand new batteries dying left and right), and the Agenda VR3(MIPS), but it's been a while and the Agenda used a funky toolchain.)
[/EDIT]

[dai_uk]

As to double posting, I felt that I was making it quite clear that a) usually several days, if not weeks had past between posts, and I was double posting to ensure that the thread was not ignored as even w/o the hardware it should be of some help to have someone else with the hardware to test builds, and b) before now, no one complained.  (I was also clearly mentioning that I was purposefully double posting such that if anyone had any problems with it, that they'd maybe have jumped in long ago.)

Ummm, no offence meant but I'd consider  that hassling. Please consider the fact that the people developing this sort of stuff may have other commitments which come before this - I know working sucks but hey it pays the bills!

[Sonny_Jim]

It's relatively easy to setup a cross compilation environment for DSLinux and it shouldn't interfere with other toolchains on the computer (all the tools are prefixed arm-linux-elf).  I'd recommend using the prebuilt toolchain if possible as it's more likely to work.

Instructions on setting it all up are here:
http://dslinux.org/cgi-bin/moin.cgi/CompilingDSLinux

In a nutshell:
Download and unpack a svn snapshot
Download (or build) a toolchain
Change path to include the new toolchain
and then make menuconfig in the linux dir

[dantheman]

Just to confirm that compiling DSLinux is easy, a few months ago I downloaded VMWare and a Ubuntu image.  After using the built-in software manager to grab all the necessary programs and libraries, I was able to follow the instructions on the Wiki to build a working binary.  My only prior Linux knowledge was using Knoppix for a few days when my hard drive died on me (and using DSLinux for web browsing).

[cutterjohn]

It's relatively easy to setup a cross compilation environment for DSLinux and it shouldn't interfere with other toolchains on the computer (all the tools are prefixed arm-linux-elf).  I'd recommend using the prebuilt toolchain if possible as it's more likely to work.

Instructions on setting it all up are here:
http://dslinux.org/cgi-bin/moin.cgi/CompilingDSLinux

In a nutshell:
Download and unpack a svn snapshot
Download (or build) a toolchain
Change path to include the new toolchain
and then make menuconfig in the linux dir

Thank you, howver it does NOT apply to my partuicular soltution other than the svn access, which I already knew of ffs.
The generic download a buildchain is so FOS, I'm not even going to comment on other than ammateurs should find a fucking life!

Why the fuck don't you wander off to something that you actually understand, eh?

[dantheman]

cutterjohn, quit it.  Now.  We will not tolerate you attacking another member like that, especially one who has contributed quite a bit to the DS homebrew scene. 

He's still attempting to help you find the problem, so why are you acting this way?

[cutterjohn]

He's attempting to help me?! How!  AFAICS he's fucking attacking me!  His instructions are a hindrance at best, if not downright destructive!

[dantheman]

Quoting the DSLinux forums:

Right, I'm going to attempt to gather all the information in this thread into something legible:

11/22/07 and 12/14/07 Builds
Boots, trying to use the network freezes it

1/23/08 Build
Works fine, dslinuxm.nds hangs at loading screen.  RAM detected properly

All other builds past this point
dslinux and dslinuxm boot and hang when you try to use the network.  Is ram detected properly?

Can you try completely wiping, reformatting and unpacking this build on an empty card?

http://rapidshare.com/files/88939670/dslinux-dldi-Sonny_Jim.tgz.html

I'd call that an attempt at helping.  I also fail to see how providing instructions on how to compile your own build is going to hurt anything, or how the compilation instructions could be an attack on you.  Lose the temper please.

[cutterjohn]

kthxbye