Show Posts

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 - danr

Pages: 1 [2] 3 4 ... 10
16
Debian / How To Install Debian On Your Zaurus (obsolete)
« on: January 21, 2008, 04:31:56 am »
I've managed to get kernel 2.6.23 and Debian on SD card to work on my C860.  See https://www.oesf.org/forum/index.php?showtopic=25399 for details.

Cheers,

Dan

17
Android / Google Android Installable Image Available!
« on: January 21, 2008, 04:24:32 am »
Quote from: stuffman
Rotten luck, the altboot bugs pop up on my 860 and prevent proper installation. When rebooting from the SD after extracting android-root.tar.gz, it hangs on the copying /home to the loop-image.

The furthest I got so far was booting the standard image and typing reboot, which goes back to the boot selector thing. Selecting the SD option says something that the card is already mounted, but copying /home works and you get the command line eventually. Typing /start gets Android's gears turning, setting up the binder things, then complains that it can't mount stuff, and ultimately hangs up after saying ***post-zygote, the same error stuff as when I tried running Android under Angstrom from flash.

I really hope I get this working some time, it's just too cool to not be able to mess with!


---

Also, on many of my cards (formatted with gparted to ext3), trying to boot from the SD gives:

Checking file system on /dev/mmcblk0p1
/dev/mmcblk0p1 has gone 35814 days without being checked, check forced

then proceeds to freeze. Fooey

I may have found a way of preventing the system freeze - see https://www.oesf.org/forum/index.php?showtopic=25399.

Cheers,

Dan

18
Hi all,

For some time I've tried to get the Angstrom 2.6.23 kernel to work with Debian on my C860, but I've been bitten by the altboot bug (see http://bugs.openembedded.org/show_bug.cgi?id=1718 for example), where the system freezes a few seconds after booting.

I think I've found a solution to this issue.  After doing some experimenting, it looks like the system hang can be prevented by executing /etc/init.d/sysklogd script early on during initialisation.  I don't know why this should stop the hanging, but it does.  So to ensure this is run early in initialisation,

[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']
cd /etc/rcS.d
ln -sf ../init.d/sysklogd S01sysklogd
[/div]

Note that you still have to be fast at selecting option 1 (boot from flash) or 3 (boot from SD card) in the altboot menu, and that you usually have to make the selection twice.  I also commented out line 474 of /etc/altboot.func, so that it says

[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']
#$FSCK $1 || sleep 2
[/div]

otherwise when booting from SD card, it always checks the filesystem, which takes forever, and may lead to the system freezing because the syslog daemon is not executed in time.

 My current setup is as follows:

Latest Angstrom kernel and console image including altboot installed on flash.
Debian tarball unzipped to SD card (in /debian directory).
Angstrom filesystem unzipped to SD card (in /angstrom directory).

The failsafe mode is to boot Angstrom from flash.  To experiment with the minimum requirements needed for booting, I

[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']
cd /media/card
ln -sf angstrom/* .
[/div]

Then I play around with which scripts I keep inside /etc/rcS.d and /etc/rc5.d, run altboot, select option 3, and see if the system boots.  If it doesn't, I remove the power, select altboot option 1, boot from flash, and make further changes.

To boot Debian, I

[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']
cd /media/card
ln -sf debian/* .
[/div]

and then boot from the SD card.

At the moment I haven't got the CF card working, so maybe this functionality has been removed from the kernel so that I need to load a module or something.

In theory this technique could also be used for other distros, such as  Android.

I might have missed other dependencies, such as one or two binaries from Angstrom /sbin, but if other people try this method for determining what the boot requirements are, then we would get a definitive answer.  If anyone gets this to work, please add further comments to this thread.

Cheers,

Dan

19
Debian / Bricked Z? Please Help - Update Success!
« on: December 12, 2007, 04:22:37 pm »
If D+M fails then press Fn+D+M on power-up to access the boot loader in ROM memory, from which you can flash the Zaurus.

20
Debian / New Kernel 2.6.23 !
« on: November 27, 2007, 05:04:34 pm »
Quote from: scottlfa
At least not for my C1k.

It doesn't work on my C860 either.  I've added a bit more information on an open bug at http://bugs.openembedded.org/show_bug.cgi?id=1718.

Dan

21
Debian / Big Windows
« on: November 21, 2007, 03:48:11 am »
Or you could use a full-screen window manager - I use ion3 on Debian, which is great once you get used to it.  Not sure if you can view all parts of extra-large windows, but it saves on messing around with resizing windows.

22
Debian / How To Install Debian On Your Zaurus (obsolete)
« on: November 05, 2007, 08:51:38 am »
Quote from: ZDevil
BTW thanks to flux's testing, now we found some low-level bugs in the after installation scripts. I am revising the files now and am still thinking of the way to handle the hwclock.rules.
The scenario is this:

The 1st-cfg.sh from the afterinstall tarball instructs to copy a hwclock.rules to /etc/udev/rules.d and then executes "hwclock -w" right after that. But the second step fails due to some /dev/rtc error. After a reboot "hwclock -w" works as expected though. The ideal case is not to have the user reboot after running 1st-cfg.sh, but to ensure the hardware clock setting takes effect on the spot. The hwclock man page and google is of little help here.
Any hint?

I always found that hwclock looked for /dev/rtc, but I can only find rtc0 in my dev tree.  After doing ln -s /dev/rtc0 /dev/rtc, hwclock works for me.

23
Debian / First Try Of Debian Eabi From Ads
« on: October 24, 2007, 10:26:19 am »
Quote from: jpmatrix
i now managed to have X running, though kdrive taken from angstrom armv4tel
and i could finally launch icewm-experimental

the bad news:
-stylus pointer doesn't point where i tap on the screen, i have a "failed to open tslib device" while launching X
-the mouse jumping bug is still there!

i don't know it i should continue or go back to my debian tichy... however it seems (although not totally sure) that overall speed seems bettter than debian tichy

Did you export TSLIB_TSDEVICE=/dev/input/event1 before starting X?

24
Debian / Debian On Sd Alternatives
« on: September 28, 2007, 03:44:58 am »
Quote from: cal
I'm a C1000 owner looking for the "full disto" experience.  I dabbled with OpenBSD, and got it working for a while, but I never got the hang of it.  I went back to pdaX because it offered the closest thing to a desktop environment on a Z.  Debian seems like something to be excited about.  

The standard install method seems to be from the z1000_debian.txt document.  The problem is that I don't want to commit to uboot.  Also, it seems like a much better idea to install debian to a SD card then NAND, just for the extra space.

Does anyone have a method for booting a debian filesystem on SD to share? Maybe Altboot?

Well I managed to get Debian armel working on my 860 using just an SD for the filesystem.  It required installing Angstrom to flash first, but Debian doesn't use that filesystem, only the kernel.  Plus I didn't use uboot either.  See https://www.oesf.org/forum/index.php?showto...mp;#entry161379 for details.  The files will differ for your machine but it should follow the same principle.

Dan

25
Linux Applications / How To Use Multiple .cpp Files?
« on: August 20, 2007, 04:48:34 am »
Quote
EDIT: I'm getting errors when I try to compile with the files like they are:

Code: [Select]
Fish LOZR # g++ lozr.cpp sprite.cpp screen.cpp input.cpp  -o lozr -lSDL -lSDL_image
lozr.cpp: In function 'int main(int, char**)':
lozr.cpp:42: warning: deprecated conversion from string constant to 'char*'
/tmp/ccXyIXFl.o:(.bss+0x0): multiple definition of `spriteMain'
/tmp/cc2NlQAW.o:(.bss+0x20): first defined here
/tmp/ccXyIXFl.o:(.bss+0x2c): multiple definition of `surfScreen'
/tmp/cc2NlQAW.o:(.bss+0x4c): first defined here
/tmp/ccEAhPKQ.o:(.bss+0x0): multiple definition of `surfScreen'
/tmp/cc2NlQAW.o:(.bss+0x4c): first defined here
/tmp/ccxIcIsw.o:(.bss+0x0): multiple definition of `myEvent'
/tmp/cc2NlQAW.o:(.bss+0x0): first defined here
collect2: ld returned 1 exit status
Fish LOZR #

What's wrong?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=166459\"][{POST_SNAPBACK}][/a][/div]

If your .cpp files are #including the same header file, then the header file needs guards around it to stop it being included more than once.

So for example, if your header is called header.h, you would have the following in it:

Code: [Select]
#ifndef HEADER_H
#define HEADER_H

#endif

This would then ensure that the header file is included only once during compilation.

Dan

26
Cxx0 General discussions / C860 Charging Problem (not Battery)
« on: July 16, 2007, 08:31:55 am »
Quote
I've still got spare fuses left over from my 860 repair; I can throw a couple in an envelope if you PM me your address.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=164491\"][{POST_SNAPBACK}][/a][/div]

Many thanks - have done just that  

Cheers,

Dan

27
Cxx0 General discussions / C860 Charging Problem (not Battery)
« on: May 30, 2007, 10:40:00 am »
Looks like my charging fuse has gone as well.  Does anyone have a spare 630mA fuse which they would be willing to send to me in the UK?  Thanks.

28
Zaurus - pdaXrom / 4gb Sd
« on: May 16, 2007, 05:24:41 am »
Quote
I didn't have problem with charge battery.
How you recognize that battery is not charged?
What is apm output?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=161422\"][{POST_SNAPBACK}][/a][/div]

I will collect some results and create a new thread once I've done this.

29
Zaurus - pdaXrom / Debian And Uboot
« on: May 16, 2007, 04:02:23 am »
Quote
ops

kernel panic - not syncing: No init found. Try passing init= option to kernel


looks like it tried to use the cf as root instead of sd
[div align=\"right\"][a href=\"index.php?act=findpost&pid=161401\"][{POST_SNAPBACK}][/a][/div]

I presume you have /sbin/init on your SD card.  Does the SD card has a partition on it? (/dev/mmcblk0p1 should be available).

30
Zaurus - pdaXrom / 4gb Sd
« on: May 16, 2007, 03:50:34 am »
Quote
Problem with SD is solved!
I compiled and installed kernel 2.6.22-rc1.
It has new option:
CONFIG_MMC_UNSAFE_RESUME=y
Now SD card works correct.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=161411\"][{POST_SNAPBACK}][/a][/div]

Does your battery get charged using this kernel version?  All the 2.6 kernel images I've tried so far don't charge the battery.

Pages: 1 [2] 3 4 ... 10