OESF | ELSI | pdaXrom | OpenZaurus | Zaurus Themes | Community Links | Ibiblio

IPB

Welcome Guest ( Log In | Register )

18 Pages V  « < 14 15 16 17 18 >  
Reply to this topicStart new topic
> Debian On C3xxx (merged Topics), ... & the state of the art
zogs
post Oct 30 2007, 08:27 AM
Post #226





Group: Members
Posts: 106
Joined: 17-December 04
Member No.: 5,953



some problem with update and wifi (rmmod hostap && rmmod hostap_cs) but all run well.

I have translate http://wiki.neilandtheresa.co.uk/Titchy_Linux/Installing
in italian : Debian-Zaurus.pdf

edit: ..i try with debian+kde
Go to the top of the page
 
+Quote Post
gojira
post Jan 25 2008, 09:43 PM
Post #227





Group: Members
Posts: 124
Joined: 16-January 05
Member No.: 6,248



QUOTE(ZDevil @ Sep 24 2007, 07:22 AM) *
Multi-language input method, such as SCIM, UIM and GCIN, all work smoothly. I can enter CJK characters freely in most apps, including GTK and QT apps, and even in the terminal (using Nano, etc). IIRC they are all broken in the new versions of pdaX, and are not easy to fix and build.


what did you need to do to get those to work? is there anything that'll recognise hand-written characters like the qpe crim does?

thanks!
Go to the top of the page
 
+Quote Post
ArchiMark
post Mar 20 2008, 08:12 AM
Post #228





Group: Members
Posts: 1,026
Joined: 25-June 03
From: Silicon Valley
Member No.: 208



Just tried Titchy install on my new 3200....

Finally managed to get ethernet network connection working I think...

Now, I'm having problem with hard drive part of install....

When it does the step 'Detect Disks and other Hardware' it gives me a screen that says

CODE
No disks detected. If you know the name of the driver needed by your disk drive , you can select it from the list.


Then it has a big list to choose from.... besides many specific items, it includes:

- Continue without disk
- Generic
- None of the above

I've tried using each of the above, but each time I get more error messages later, regarding install to unclean disk, if I say go ahead anyway, it fails, and I if I say No, it takes me back to installer...

In installer screen, I don't get the choice under Detect Disks to Format Drive, etc....

Any suggestions before I give up on Titchy????

Thanks!

Mark


Go to the top of the page
 
+Quote Post
ZDevil
post Mar 20 2008, 10:03 AM
Post #229





Group: Members
Posts: 2,003
Joined: 16-April 04
From: the Netherlands && /dev/null
Member No.: 2,882



Does your "new" 3200 come with the factory microdrive or a replacement CF (which brand)?
This is how I installed Titchy: http://www.flickr.com/photos/50659119@N00/...157702606/show/ (click on the slides for more explanation).
Or you can try out the faster EABI: http://www.oesf.org/forum/index.php?showtopic=25029 (first post)
Go to the top of the page
 
+Quote Post
ArchiMark
post Mar 20 2008, 10:32 AM
Post #230





Group: Members
Posts: 1,026
Joined: 25-June 03
From: Silicon Valley
Member No.: 208



QUOTE(ZDevil @ Mar 20 2008, 11:03 AM) *
Does your "new" 3200 come with the factory microdrive or a replacement CF (which brand)?
This is how I installed Titchy: http://www.flickr.com/photos/50659119@N00/...157702606/show/ (click on the slides for more explanation).
Or you can try out the faster EABI: http://www.oesf.org/forum/index.php?showtopic=25029 (first post)



Thanks for your help, ZDevil...

I assume that it came with factory microdrive as I haven't changed drive...

Meanwhile, I decided to try the alternative install "The "10-Step-Self-Help Guide to Enjoying a Popular Penguin" in this post using the other files listed there....

Downloaded those files and renamed them as instructed and put them on my 1GB SD card

Did Step B 'Prepare the Disk'

Then did Step 2 & 3, Flashing....

Here's what happens:

CODE
Zaurus SD Updater.....
Finish!
Rebooting....
*Then lots of text.....
*Then the last few lines are:
VFS: Mounted root (ext3 filesystem)
Freeing init memory: 80k
Warning: unable to open an initial console
Kernel panic - not syncing: Try passing init=option to kernel



Now what?????

Or should I just give up and try 'the faster EABI' you mention????

Thanks!

Mark
Go to the top of the page
 
+Quote Post
ZDevil
post Mar 20 2008, 10:44 AM
Post #231





Group: Members
Posts: 2,003
Joined: 16-April 04
From: the Netherlands && /dev/null
Member No.: 2,882



That ten step guide is obelete. Actually the easiest way is to flash an EABI kernel (yonggun/poky/angstrom) using Sharp bootloader (so no uboot) and then install the rootfs tarball.
Instead of using the kernel(s) as described in that post, use this newer one:
http://yonggun.tistory.com/66 (zImage.bin.hda1, rename to zImage.bin and flash in the [OK] flash menu.)
(will update that post soon...)
Go to the top of the page
 
+Quote Post
ArchiMark
post Mar 20 2008, 02:01 PM
Post #232





Group: Members
Posts: 1,026
Joined: 25-June 03
From: Silicon Valley
Member No.: 208



QUOTE(ZDevil @ Mar 20 2008, 11:44 AM) *
That ten step guide is obelete. Actually the easiest way is to flash an EABI kernel (yonggun/poky/angstrom) using Sharp bootloader (so no uboot) and then install the rootfs tarball.
Instead of using the kernel(s) as described in that post, use this newer one:
http://yonggun.tistory.com/66 (zImage.bin.hda1, rename to zImage.bin and flash in the [OK] flash menu.)
(will update that post soon...)


Thanks for your help, ZDevil....will try what you suggest....already did the HD format though from the instructions...hope that's OK.....

Will be great if you can update that post as you mention to us noobs....

smile.gif
Go to the top of the page
 
+Quote Post
ArchiMark
post Mar 20 2008, 03:29 PM
Post #233





Group: Members
Posts: 1,026
Joined: 25-June 03
From: Silicon Valley
Member No.: 208



QUOTE(ZDevil @ Mar 20 2008, 11:44 AM) *
That ten step guide is obelete. Actually the easiest way is to flash an EABI kernel (yonggun/poky/angstrom) using Sharp bootloader (so no uboot) and then install the rootfs tarball.
Instead of using the kernel(s) as described in that post, use this newer one:
http://yonggun.tistory.com/66 (zImage.bin.hda1, rename to zImage.bin and flash in the [OK] flash menu.)
(will update that post soon...)


In the meantime, tried to flash with yonggun kernel; 'zImage.bin.hda1' renamed to zImage.bin....but still get same error message as I noted in earlier post:

CODE
Warning: unable to open initial console.
kernel panic - not syncing: no init found. Try passing init=option to kernel.


So, wondering doe this have anything to do with:

A) doing Step 1 of 10 Step install instructions on my internal microdrive; partitioned into 2 partitions. Did this per Step B Preparing the Disk of the Alternative Install approach described earlier in this thread...

and/or

cool.gif having the right files on my SD card?

I have the kernel file 'zImage.bin' as described above and the 'updater.sh' file from the Titchy install files..

Do I need to reset my Z back to original factory condition???

Appreciate any and all help!!! I'm stuck now....

blink.gif
Go to the top of the page
 
+Quote Post
ZDevil
post Mar 20 2008, 08:31 PM
Post #234





Group: Members
Posts: 2,003
Joined: 16-April 04
From: the Netherlands && /dev/null
Member No.: 2,882



Try these:

#1 Use the updater.sh from Angstrom to flash the kernel again: http://www.oesf.org/forum/index.php?act=at...ost&id=5291

#2 If it's the same initial console error, try rebooting once; if no luck, do this:
boot into the linux emergency mode ([D+B] mode)
cd /mnt/cf/dev
MAKEDEV console
reboot
Go to the top of the page
 
+Quote Post
ArchiMark
post Mar 21 2008, 07:41 AM
Post #235





Group: Members
Posts: 1,026
Joined: 25-June 03
From: Silicon Valley
Member No.: 208



QUOTE(ZDevil @ Mar 20 2008, 09:31 PM) *
Try these:

#1 Use the updater.sh from Angstrom to flash the kernel again: http://www.oesf.org/forum/index.php?act=at...ost&id=5291

#2 If it's the same initial console error, try rebooting once; if no luck, do this:
boot into the linux emergency mode ([D+B] mode)
cd /mnt/cf/dev
MAKEDEV console
reboot


Thanks for your help.... I need it!!

Tried #1 and still same error....

Tried rebooting once and no luck...

Tried #2 and get the following error, have just shown 4 lines out of many similar lines, just number changes:

CODE
.....
mknod: vcs54-: operation not permitted
mknod: vcsa54-: operation not permitted
mknod: tty55-: operation not permitted
mknod: vcs55-: operation not permitted

.......


Any other suggestions??

THANKS!
Go to the top of the page
 
+Quote Post
ZDevil
post Mar 21 2008, 07:54 AM
Post #236





Group: Members
Posts: 2,003
Joined: 16-April 04
From: the Netherlands && /dev/null
Member No.: 2,882



Did you mount the CF first (e.g. mount /dev/hda1 /mnt/cf ) before MAKEDEV?

Some users have reported that booting may continue after waiting a while at the error...
Go to the top of the page
 
+Quote Post
ArchiMark
post Mar 21 2008, 08:29 AM
Post #237





Group: Members
Posts: 1,026
Joined: 25-June 03
From: Silicon Valley
Member No.: 208



QUOTE(ZDevil @ Mar 21 2008, 08:54 AM) *
Did you mount the CF first (e.g. mount /dev/hda1 /mnt/cf ) before MAKEDEV?


Thought it was mounted....

But just tried doing this again and doing mount /dev/hda1 /mnt/cf before MAKEDEV....still same error message....


QUOTE
Some users have reported that booting may continue after waiting a while at the error...


rebooted after getting error message above...get same error messages as before:

CODE

Warning: unable to open initial console.
kernel panic - not syncing: no init found. Try passing init=option to kernel.


I can wait awhile, but I thought when you get a kernel panic message you've crashed???

Also, just to be clear I'm trying to install kernel before install of rootfs tarball per alternate instructions....original instructions say to install tarball first....

Suggestions???

Thanks!

PS. Also, you don't think I need to reset my 3200 back to original factory state??
Go to the top of the page
 
+Quote Post
ZDevil
post Mar 21 2008, 09:03 AM
Post #238





Group: Members
Posts: 2,003
Joined: 16-April 04
From: the Netherlands && /dev/null
Member No.: 2,882



Yep. You have the disk with the rootfs ready first (extract them to a CF card if you are using a ready made rootfs tarball) and then the kernel.

Returning to the factory state (NAND restore) is not such a big deal; i've done it over a few dozen times on my Zs...
Go to the top of the page
 
+Quote Post
ArchiMark
post Mar 21 2008, 09:19 AM
Post #239





Group: Members
Posts: 1,026
Joined: 25-June 03
From: Silicon Valley
Member No.: 208



QUOTE(ZDevil @ Mar 21 2008, 10:03 AM) *
Yep. You have the disk with the rootfs ready first (extract them to a CF card if you are using a ready made rootfs tarball) and then the kernel.


OK, will try that....and I need to partition CF card first, right?



QUOTE
Returning to the factory state (NAND restore) is not such a big deal; i've done it over a few dozen times on my Zs...


Yes, I've done it before when I had a Z in the past...but haven't had a Z in a year until this week....my question though was whether or not you think I should restore my microdrive partitions to factory state before installing kernel?

One reason for asking this question is whether the fact that I repartition my microdrive to 2 partitions per the instructions is causing install problem?

Second reason for asking is whether it's necessary for install or after install condition?

Also, I'd like to have Debian running off of microdrive and not depent upon having SD or CF card inserted in Z...in other words can everything run offo of internal drive or does this Debian setup depend upon having a storage card inserted?

Thanks!

Mark
Go to the top of the page
 
+Quote Post
ZDevil
post Mar 21 2008, 10:14 AM
Post #240





Group: Members
Posts: 2,003
Joined: 16-April 04
From: the Netherlands && /dev/null
Member No.: 2,882



QUOTE(ArchiMark @ Mar 21 2008, 06:19 PM) *
Yes, I've done it before when I had a Z in the past...but haven't had a Z in a year until this week....my question though was whether or not you think I should restore my microdrive partitions to factory state before installing kernel?

Nope.

QUOTE
One reason for asking this question is whether the fact that I repartition my microdrive to 2 partitions per the instructions is causing install problem?

It's recommended (i.e. one big root partition and one swap partition), if you want Debian to run smoothly off the internal disk without any card. But things are fine as long as you put things right in Step 3 (editing /etc/fstab)

QUOTE
Second reason for asking is whether it's necessary for install or after install condition?

Dun get it. tongue.gif

QUOTE
Also, I'd like to have Debian running off of microdrive and not depent upon having SD or CF card inserted in Z...in other words can everything run offo of internal drive or does this Debian setup depend upon having a storage card inserted?

Nope.
Go to the top of the page
 
+Quote Post

18 Pages V  « < 14 15 16 17 18 >
Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 16th September 2014 - 05:33 PM