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 - Vogtinator
Pages: 1 ... 54 55 [56] 57 58 ... 83
826
« on: April 10, 2013, 10:50:09 am »
-> nspire linux questionsPost it there, we're trying to keep it seperated
827
« on: April 10, 2013, 10:38:49 am »
If your usb drive is working with linux already, you only have to remove "root=/dev/ram" in your bootscript and replace it with "root=/dev/sda" or "root=/dev/sda1", depends on whether you are using partitions.
You should remove the "initrd" line, too. It doesn't do anything but increasing the boot time.
829
« on: April 06, 2013, 01:37:01 pm »
No. You should connect the pendrive before using the bootloader.
Connecting to the computer would be the exact opposite.
830
« on: April 05, 2013, 06:35:27 pm »
You can try the next expanded version.
The defconfig kernels may work, too, but I don't know
whether USB keyboard support is enabled.
831
« on: April 05, 2013, 06:30:44 pm »
If TI's OS doesn't recognize the hub it's not supported. Maybe you can try another one? Link is here
832
« on: April 05, 2013, 06:23:29 pm »
No messages at all?
Could you try some older kernels?
Does ti's os notify you about the hub been plugged in?
833
« on: April 05, 2013, 05:50:41 pm »
I found that kernels that worked with initrds did not work with usb, and kernels with usb did not work with initrds. Really? Mine works fine with both. The dmesg output seems right, but lsusb should definitely output something relevant. Could you try to unplug the hub before booting and plugging it in after it's booted? Do you have a powered usb hub (which you need)?
834
« on: April 05, 2013, 03:13:31 pm »
i've downloaded the initrd (http://tiplanet.org/nspire-linux-builds/start_initrd.ll2.tns), That's the bootscript again  But I think you downloaded it right, else it wouldn't boot at all. i've connected the keyboarb to the powered usb hub Could you see some messages? Could you post the output of "lsusb"(all lines) and "dmesg"(the lines that seem relevant)?
835
« on: March 20, 2013, 05:55:16 pm »
Ok, I edited the post. It didn't happen to me and my friend, maybe we have another HW revision?
Or were we just plain lucky?
836
« on: March 19, 2013, 04:00:59 pm »
Guess how I found the correct pins: I ran diags (test insertion contact), connected every pin to ground and looked what has changed.
I could have (sort of)bricked my calc O.o
837
« on: March 19, 2013, 03:14:52 pm »
Cr*p, that's actually a serious issue now.
But why do you play with the pins while your calc is turned on and has the battery plugged in?
I soldered my calc with the battery pulled and it works without problems..
I'm still wondering how the touchpad can break by grounding pins?
838
« on: March 18, 2013, 01:16:53 pm »
Exactly, the calc is too slow.. But it would work on the older (non-cx) models, they actually have 6 33MHz timers Second timer, but I don't have one :-(
839
« on: March 18, 2013, 12:55:57 pm »
How would you do that? You're only able to execute 132/33=4 cpu cycles each timer interrupt (and the JMP already needs 5)
840
« on: March 18, 2013, 12:41:10 pm »
Yes it would be possible, but we only have two 33 MHz timers (for pwm), we would have to use the 33 kHz timer as sample update.
That would mean wav loading is impossible (if they're not 33kHz) or it'd sound weird. Mono is noisy enough (8 bit).
But one thing is interesting, with some resistors and two GPIOs it's possible to do 16 bit pwm, but that would destroy the simplicity :-/
Pages: 1 ... 54 55 [56] 57 58 ... 83
|
Show Posts
