Boot C3000 Into Text Console

[Jonathan]

Hi all,

I've set up my C3000 to boot into a text console or Qtopia as per these threads:

Any Way To Get Out Of The 860 Gui On Startup
rebooting Zaurus in text mode
How to boot in console mode?

which gives me a text login, but I only get a single line below the initial Sharp splash screen.  Not much good for debugging or checking log scripts after a crash.

Can someone tell me if I can get a full screen text console on the C3000 at boot time in single user mode.  I don't know if it's different on the other Cxx0 models.  


Also, I'd *really* like to do away with both the startup splash screens (the second one can be removed/changed by exiting qpe.sh) and see the boot messages as they occur.  You know, like on other linux versions, showing fsck and other things going on at boot time.

I've searched the forums and web for ideas and came up blank.

I'd appreciate your help on this.

Thanks in advance,

Jonathan

[m-morino]

Hi,

To fix the problem, you need to apply a patch to kernel source and recomplie it.

If you have no time, use precompiled kernels with splash screens disabled in this page.
These kernels also have nice ability to overclock the CPU up to ~624MHz!  
But I make no mention of it

How to update:

First, you have to download a updater script and kernel below.

http://developer.ezaurus.com/sl_j/source/c...pdater.sh.c3000
http://tetsu.homelinux.org/zaurus/kernel/v...-v17f-C3000.bin
http://tetsu.homelinux.org/zaurus/kernel/v17f/size.html (md5sum for kernels)

Then, rename these files like below and put them on a CF or SD/MMC.
Note that the updater is case-sensitive, so make sure the files are same name below.

updater.sh.c3000  -> updater.sh
zImage-v17f-C3000.bin -> zImage

After that, enter the maintenance menu and update your C3000 (see the install document of pdaXrom).

HTH,

--
 m-morino

[Jonathan]

Hi m-morino,

Thank you so much for the quick response.  I suspected I might need a new kernel to remove the first startup screen.  The screen seems to come up just after the kernel loads and before the rest of the boot process.

I've been intending to try the overclocking/enhanced kernel since before I got the C3000, but have been waiting for others to try first   Now I have no excuse not to try...  maybe I'll give it a go tonight.

Thanks for the simple and clear instructions!

Jonathan.

[Jonathan]

I installed the new kernel as instructed - very easy - and *hurrah!* I now have a pretty penguin and the usual boot messages.  Makes it a "real" Linux box.

The overclocking doesn't seem to make much different at the moment, but time will tell.  Changing the LCD frequency from the default 104Mhz makes the screen flicker a bit (as you might expect really).  A CCCR value of 02000310 (624MHz) seems to work fine.

I like Piro-san's battery change applet and setup the Settings/freqchange.conf file for the cpu frequencies of 416MHz, 520MHz and 624MHz but made sure the LCD frequency matched the default.

Anyway here are a couple of pics for other people who may be interested (couldn't figure out how to do screen dumps quickly, and they it wouldn't work on the text console anyway.)  Appologies for terrible quality.

Many thanks to you m-morino (and to Tetsu and others for the new kernel)!  

Now all I need to do is compile my own kernel with video4linux enabled.

Jonathan

1.  Penguin and scrolling boot messages

[img]http://www.enm.bris.ac.uk/teaching/enjmr/Zaurus_SL-C3000/pics/NewKernel_sa.jpg\" border=\"0\" class=\"linked-image\" /]

2. single user mode console

[img]http://www.enm.bris.ac.uk/teaching/enjmr/Zaurus_SL-C3000/pics/NewKernel_sb.jpg\" border=\"0\" class=\"linked-image\" /]

3. qclockchange

[img]http://www.enm.bris.ac.uk/teaching/enjmr/Zaurus_SL-C3000/pics/NewKernel_sc.jpg\" border=\"0\" class=\"linked-image\" /]

[slackwaresupport]

i noticed that your using a VORE of 1.45 the website says to use 1.55 for the 624mhz.


0e: 1.550V (624MHz時の定格)
0f: 1.600V
解説: クロックアップ時はコア電圧を上げないと安定しないようです。
使用例:
# echo 0e > /proc/zaurus/VCORE

[Jonathan]

i noticed that your using a VORE of 1.45 the website says to use 1.55 for the 624mhz.


0e: 1.550V (624MHz時の定格)
0f: 1.600V
解説: クロックアップ時はコア電圧を上げないと安定しないようです。
使用例:
# echo 0e > /proc/zaurus/VCORE
[div align=\"right\"][a href=\"index.php?act=findpost&pid=65582\"][{POST_SNAPBACK}][/a][/div]

haha!  Very observant!  

Nope, I haven`t been running at the lower voltage - it`s just that the qclockchange application lets you cange values on screen without applying them.  I was just playing around before taking the photo.

I certainly _do_ use the values recommended on the web page.

Many thanks though for your response - I hope I would be as observant and kind as you are in pointing out such a thing.

Cheers,

Jonathan

[ArchiMark]

Hope someone can please Help!

Just tried to install m-marino's pre-compiled kernel as per instructions...

Reset and Z booted up...see 'SHARP' in red letters as usual...

At bottom of screen I see message "HDD1 Error!!"

Not good!....  


Should I try reflash again...or???

Any suggestions???

Thanks!!

Mark

[m-morino]

Hi Mark,

At bottom of screen I see message "HDD1 Error!!"

Not good!....  
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

To troubleshoot it, I made a rescue [a href=\"http://morimasa.net/zaurus/binaries/updater.sh.rescue]updater.sh[/url].
Rename it updater.sh and put it on a CF or SD, then do the usual kernel update process.
You will see a pretty 'ash' command prompt.

/dev/mtdblock2 is root filesystem, and /dev/mtdblock3 is usually mounted on /home. To investigate the root fs, try

# mkdir /mnt/mtdblock2
# mount -o noatime,rw /dev/mtdblock2 /mnt/mtdblock2

and enter the filesystem.

 Maybe /etc/mtab is broken. Mount /dev/mtdblock3 on /mnt/mtdblock3 and make a trial of

# ln -fs /proc/mounts /mnt/mtdblock3/etc/mtab

and reboot.

HTH,

--
m-morino

[ArchiMark]

Thanks for your help, m-morino. Really can use it!

Understand your directions I hope, but want to be clear...

Do you mean that I should repeat the same commands for 'mtdblock3' as I did for 'mtdblock2' ?

Do you mean to type in 'reboot' after mounting commands or to do the 'reset' procedure with taking out battery, etc?

Meanwhile, did this and after entering in the 'ln -fs /proc/mounts mnt/mtdblock3/etc/mtab'
line I get the following error message:

'ln: mnt/mtdblock3/etc/mtab: No space left on device'

Now what??

Thanks,

Mark
Anxious C3000 Owner....

[m-morino]

Hi Mark,

Meanwhile, did this and after entering in the 'ln -fs /proc/mounts mnt/mtdblock3/etc/mtab'
line I get the following error message:

'ln: mnt/mtdblock3/etc/mtab: No space left on device'
[div align=\"right\"][a href=\"index.php?act=findpost&pid=65836\"][{POST_SNAPBACK}][/a][/div]

You put some large files into /home/*, didn't you?
/dev/mtdblock3 (/home) has a capacity of only 4MB.
Remove unnecessary files from /home, because the boot process needs to be able to write some files on /home/system/var.
Then reboot. You may possibly see a QTopia screen.

HTH,

--
m-morino

[ArchiMark]

Thanks for your help, m-morino.

Don't remember putting any large files on /home.

Just checked and only thing listed in /home is:

drwxr-xr-x  2 root  root  1024 Oct 24 2004 root

So don't see anything to remove?

Thanks,

Mark

[m-morino]

Just checked and only thing listed in /home is:

drwxr-xr-x  2 root  root  1024 Oct 24 2004 root

So don't see anything to remove?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=65846\"][{POST_SNAPBACK}][/a][/div]

Ok, just try:

Code: [Select]

# mkdir /mnt/mtdblock3
# mount -o rw,noatime /dev/mtdblock3 /mnt/mtdblock3
# dfIf /mnt/mtdblock3 isn't fully filled, do below:

Code: [Select]

# ls -l /mnt/mtdblock3/etc/mtabIf it isn't a symbolic link to /proc/mounts, try

Code: [Select]

# ln -fs /proc/mounts /mnt/mtdblock3/etc/mtab
# exit
It reboots after the "exit" command.
Then check the boot process works fine.

HTH,

--
m-morino

[ArchiMark]

Thanks so much for your continued help, m-morino!

OK, tried what you suggest...got the following:

Code: [Select]

# mkdir /mnt/mtdblock3
mkdir: Cannot create directory `/mnt/mtdblock3': File exists
# mount -o rw,noatime /dev/mtdblock3 /mnt/mtdblock3
mount: Mounting /dev/mtdblock3 on /mnt/mtdblock3 failed: Device or resource busy
# df
Filesystem        1k-blocks     Used   Available    Use%   Mounted on
rootfs                     7931     7800            0        100%       /
/dev/root                7931     7800            0        100%      /
/dev/shm              16384          4     16380            0%      /tmp
/dev/hda1               7768     6368      1400           82%     /mnt/cf
/dev/mtdblock2       5120     5120            0        100%      /mnt/mtdblock2
/dev/mtblock3         4096     4096            0        100%     /mnt/mtdblock3
So this seems strange that here it shows that mtblock3 is full. But when I checked /home it seems that it is only about 25% full right??

UPDATE: Decided to bite the bullet and do a 'Reset' back to factory condition....figured that might be good idea to get things fixed....

Thanks,

Mark

[m-morino]

Mark,

Code: [Select]

# df
Filesystem        1k-blocks     Used   Available    Use%   Mounted on
rootfs                     7931     7800            0        100%       /
/dev/root                7931     7800            0        100%      /
/dev/shm              16384          4     16380            0%      /tmp
/dev/hda1               7768     6368      1400           82%     /mnt/cf
/dev/mtdblock2       5120     5120            0        100%      /mnt/mtdblock2
/dev/mtblock3         4096     4096            0        100%     /mnt/mtdblock3[div align=\"right\"][a href=\"index.php?act=findpost&pid=65862\"][{POST_SNAPBACK}][/a][/div]

Ok, then type

Code: [Select]

# cd /mnt/mtdblock3
# du | sort -nYou will have the sorted file space usage report.

By the way, your /home is strange... my C3000 in the rescue environment shows

Code: [Select]

# ls /mnt/mtdblock3
QtPalmtop etc samba system userdata
dev root sharp tmpIt works fine  

You'd better backup necessary files into a CF, and reflash...  
I can't figure out the cause of the problem...

--
 m-morino

[ArchiMark]

OK, m-morino.

THANKS for all your help!

It is a BIG help!

 

Mark