This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - tangrs
Pages: 1 2 3 [4] 5 6 ... 16
46
« on: February 24, 2013, 04:25:24 pm »
Pretty much all packages available for ARM debian are available for the calculators.
47
« on: February 24, 2013, 04:52:55 am »
Very nice!
48
« on: February 21, 2013, 06:08:28 am »
@Naruto: Try doing the following:
1. Rename your "linux" folder to "linux old"
2. Create a new "linux" folder
3. Download all the files needed to run Linux (Do not use any of the ones you already have)
4. Place them in the new "linux" folder and try booting linux (use a initrd first to make sure it works)
This worked in my case.
The initrd works.
As I tried lauchning it using it using the latest rootfs, it displayed a lot more stuff than before. At the end it just repeated the line "can't run '/sbin/getty' no such file or directory", so I pressed the reset button. When the calculator reboots now, it just shows the loading screen background and the clock icon in the middle. I already tried accessing the service menu and doing a complete format. But after installing a new OS it still won't boot. What to do now?
There's a maintenance menu and a diagnostics menu. Which one did you boot to? Booting into diags and running the NAND tests has always worked for me.
49
« on: February 19, 2013, 05:56:03 am »
That time comparison seems a little off, depending on where nLaunch's exploit is. (I haven't used it since I currently don't have an nspire)
If nlaunch starts loading before the RSA validation on the OS file would begin, then you should see a much faster boot time than the standard OS per MB.
I'm pretty sure nLaunch exploits a hole in boot2 before it starts loading the OS so it does it early enough to be useful.
50
« on: February 19, 2013, 05:28:46 am »
UpdateI've started working on nLaunch integration. Basically, I'm writing up some software that will package up the kernel into a format that boot2 likes and will be launchable with nLaunch directly. Pretty much everything is done but unfortunately, boot2 doesn't like the file I built and won't boot just yet. Once I solve this, we'll be able to boot Linux directly from boot2 without the Nspire software even existing (i.e. a 'permanent' installation). This can save some a lot of loading time since we don't have to wait for boot2 to load a ~9MB OS into memory then load the ~2MB kernel + initrd afterwards - we can simply have boot2 load our 2MB kernel directly! This will reduce the time from cold boot to a Linux shell down to about 12-15 seconds. For reference, it normally takes ~50 seconds to get to a Linux shell from a cold boot. I hope that post made sense. The hours of coding has messed with my brain a little 
51
« on: February 18, 2013, 11:55:05 pm »
From what I've read, GCC is not a good compiler to use on the nspire.
What compiler would you use instead?
EDIT: Also, a couple other things:
1. Is there a way to disable the USB debug messages
2. Is there a way to change the welcome message right before the "linucx login:"
3. Is there a way to make the X terminal not extend off the screen
4. Are the X programs supposed to have windows borders (to move them around and close them)
5. Is there a way to draw pixels in C or C++ code as of yet
1. Yes. Recompile the kernel with no USB debugging messages. 2. Yes. You should be able to just mount the rootfs on your virtual machine and modify the welcome message from there. 3. Not as far as I know. X was probably designed for larger screen sizes so the default window size is probably a reflection of that. 4. The borders and being able to drag stuff around is controlled by a window manager (which runs on X). twm is the one that looks most X-y but you can use others right up to Gnome/KDE (though, it'd probably be pretty slow). 5. I believe the directfb library will let you do that.
52
« on: February 15, 2013, 08:47:05 pm »
On which device?
On your virtual machine.
To make sure USB host always works, try reading up http://hackspire.unsads.com/wiki/index.php/Linux#USB
fdisk -l shows nothing, is that normal? 
EDIT: Can't get it to work setting the disk value as /dev/sdb (or sdb1)
I read that article, that is actually why the read light is working again.
Are you running it as root?
53
« on: February 15, 2013, 08:30:37 pm »
Ohh, I've never used the initrds on the nightly builds I'd imagine you can just login as 'root' with no password.
54
« on: February 15, 2013, 08:18:13 pm »
never mind, now it says hi, wtf are you doing with me? nanocx login: what do i do lol
Huh?
55
« on: February 15, 2013, 08:07:31 pm »
So I open my linux loader and run this.
kernel linux/zImage.tns
initrd linux/initrd.tns
cmdline root=/dev/ram
boot
it runs a bunch of code and freezes at r4:00000000 r3:00000000
what do I do? thx in advance to anyone that helps
Sorry... I'm totally a n00b at this...
What if you add a rdsize 0x4000 before the boot?
57
« on: February 15, 2013, 07:32:08 pm »
What does fdisk -l show?
58
« on: February 15, 2013, 06:47:13 pm »
How are you preparing the USB drive?
59
« on: February 13, 2013, 05:08:19 pm »
Do you have the old version of the bootloader by any chance? If you enter the bootloader (without the script), and use the mach command, what does it give you?
It says "Machine ID is set to 3503"
Is there more than one version of Linux bootloader v2?
I have gotten Linux to work before with an older kernel, likely an older bootloader, and an initrd.
Also, I had an older version of TiLP, so that may have been my problem.
Yeah, that's an older version of the bootloader. The machine number changed in the recent version. You'll need to grab a more recent version.
60
« on: February 13, 2013, 03:31:13 am »
kernel linux/zImage.tns
cmdline root=/dev/sda earlyprintk debug console=tty0 console=ttyAMA0,115200n8 rootdelay=10
boot
The latest kernels are not working for me.
Do you have the old version of the bootloader by any chance? If you enter the bootloader (without the script), and use the mach command, what does it give you?
Pages: 1 2 3 [4] 5 6 ... 16
|
Show Posts
