EMPEG Boot Messages ?!?

Posted by: jfranke

EMPEG Boot Messages ?!? - 29/07/1999 07:41

Hey this is a silly question now, but when i switch the thing on (one day hopefully....i'm 401 or so) will i do see cool boot messages, like 'Booting VMLinux' and 'INIT runlevel 6' or something COOL?!? Or will it just start plaxing like my ordinary car-stereo (not very exciting) ? Folks, you HAVE to implement some kind of audio theme while that thing is starting - annoying but nice i guess....soo many possibilities. Tanks! Yo

Posted by: altman

Re: EMPEG Boot Messages ?!? - 29/07/1999 09:57

Ok, you asked for it - here's Kate's bootup messages. I've got 2x2.1gb drives in my development machine, which is about 7 months old. It was the unit which did the CE/FCC tests and is pretty well travelled :)

empeg-car v0.04 19990121 ([email protected])
If there is anyone present who wants to upgrade the flash, let them speak now,
or forever hold their peace...it seems not. Let fly the Penguins of Linux!


Clearing 8Mb of RAM...
Copying kernel...
Calling linux kernel...
Uncompressing Linux...done.
Now booting the kernel
Linux version 2.2.9-rmk3-np9-empeg5 (altman@sleeper) (gcc version egcs-2.91.60 19990113/philb (egcs-1.1.1 release)) #271 Wed Jul 28 18:49:00 BST 1999
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
Calibrating delay loop... 208.08 BogoMIPS
Memory: 7120k/8M available (784k code, 20k reserved, 264k data, 4k init)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
Starting kswapd v 1.5
SA1100 serial driver version 4.26 with no serial options enabled
ttyS00 at 0xf8010000 (irq = 15) is a SA1100 UART
ttyS01 at 0xf8050000 (irq = 17) is a SA1100 UART
ttyS02 at 0xf8030000 (irq = 16) is a SA1100 UART
Linux video capture interface: v1.00
empeg FM radio driver.
empeg audio driver initialized
empeg infra-red support initialised.
empeg usb initialised, USBN9602 revision 1
empeg display initialised.
empeg state support initialised.
empeg RDS driver initialised
empeg ACP driver initialised
RAM disk driver initialized: 16 RAM disks of 4096K size
empeg dual channel IDE
hda: TOSHIBA MK2104MAV, ATA DISK drive
hdc: TOSHIBA MK2104MAV, ATA DISK drive
ide0 at 0x040-0x047,0x078 on irq 7
ide1 at 0x000-0x007,0x038 on irq 6
hda: TOSHIBA MK2104MAV, 2067MB w/0kB Cache, CHS=4200/16/63
hdc: TOSHIBA MK2104MAV, 2067MB w/0kB Cache, CHS=4200/16/63
PPP: version 2.3.7 (demand dialling)
TCP compression code copyright 1989 Regents of the University of California
PPP line discipline registered.
Partition check:
hda: hda1 hda3 hda4
hdc: hdc4
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 320 blocks [1 disk] into ram disk... done.
VFS: Mounted root (ext2 filesystem).
empeg-pump v0.03 (19980601)
Press Ctrl-A to enter pump...VFS: Mounted root (ext2 filesystem) readonly.
change_root: old root has d_count=1
Freeing unused kernel memory: 4k init


(from here onwards is just my debug build, it does a debian boot. Shipping versions just go directly to the player)


version 2.76
Activating swap...
Checking root file system...
Parallelizing fsck version 1.14 (9-Jan-1999)
/dev/hda1: clean, 4732/126480 files, 298973/503968 blocks
Calculating module dependencies... done.
Loading modules:
Checking all file systems...
Parallelizing fsck version 1.14 (9-Jan-1999)
/dev/hda4: clean, 4761/277440 files, 1077485/1108800 blocks
/dev/hdc4: clean, 291/530432 files, 678387/2116768 blocks
Mounting local file systems...
/dev/hda4 on /drive0 type ext2 (ro)
/dev/hdc4 on /drive1 type ext2 (ro)
cp: /etc/nologin: No such file or directory
Cleaning: /tmp /var/lock /var/run
Initializing random number generator...
done.
Recovering nvi editor sessions... done.
Booting complete
Linux 2.2.9-rmk3-np9-empeg5

Hello, my name is kate
Thread 'ActiveTimeout' is pid 85.
Thread 'ActiveTimeout' is pid 86.
Thread 'ActiveTimeout' is pid 87.
Thread 'ActiveTimeout' is pid 88.
Thread 'ActiveTimeout' is pid 89.
Thread 'Main' is pid 83.
Thread 'Audio' is pid 90.
Thread 'Cache' is pid 91.
cache.cpp 30 ( 91): Caching thread started.
Thread 'Control' is pid 92.
Thread 'Keyboard' is pid 93.
Thread 'Remote' is pid 94.
Thread 'Mixer' is pid 95.
Thread 'Radio' is pid 96.
Thread 'VisualManager' is pid 97.
Thread 'Server' is pid 98.


Posted by: Dearing

Re: EMPEG Boot Messages ?!? - 29/07/1999 10:11

So, do all those messages fly up the main display, or does it just go in a log?

_~= Dearing =~_
"WAY too happy about being #1225."
Posted by: mac

Re: EMPEG Boot Messages ?!? - 29/07/1999 10:22

There's no text display capability in our kernel so all text is done from user space. This means that on production units until the player runs no text is displayed. The player currently displays text like "Starting mixer...", "Starting audio..." on startup but this may change.

My development unit has Jim Pick's (http://www.jimpick.com) debian image on it and runs full init scripts. I've created a script called echox that calls echo and runs a little program called scrawl that writes text on the empeg-car screen. Using this in the init scripts means that I see messages like "Checking root file system..." during bootup. This is not done on production units since they do not run a standard init (and don't need to fsck on startup anyway).

--
Mike Crowe
I may not be speaking on behalf of empeg above :-)
Posted by: altman

Re: EMPEG Boot Messages ?!? - 29/07/1999 10:22

Sorry, I misread the original post - those messages come out of the serial port. The display shows the empeg logo/penguin (as in the pics on the site) then the player kicks in. The player does flash past some messages, but they're gone in under a second...

Hugo


Posted by: jfranke

Re: EMPEG Boot Messages ?!? - 29/07/1999 23:30

Right, thanks a lot for the ifo, Jo

Posted by: mcomb

Re: EMPEG Boot Messages ?!? - 31/08/1999 00:20

Hmmmmm, I can't help but notice that the kernel seems to have IP support. Hugo, are you holding out on us? Where did you hide the ethernet port :-) Actually wireless would be swell, drive into the garage and auto sync with the fileserver.

-Mike

Posted by: mac

Re: EMPEG Boot Messages ?!? - 31/08/1999 06:47

Hmm, I thought I knocked out IP support from the release kernels. There's no point in it taking up memory since it isn't used.

IP support was in there originally so we could run PPP over the serial port. In the end though we found it easier to just use minicom and zmodem.


--
Mike Crowe
I may not be speaking on behalf of empeg above :-)
Posted by: Jazzwire

Re: EMPEG Boot Messages ?!? - 31/08/1999 06:54

Won't we need that for the PPP over USB stuff.. =)

Only kidding.. =)

Jazz
(List 112, S/N 00030, 4 gig blue)
Posted by: raphael

Re: EMPEG Boot Messages ?!? - 05/09/1999 05:11

Linux version 2.2.9-rmk3-np9-empeg5 (altman@sleeper) (gcc version egcs-2.91.60 19990113/philb (egcs-1.1.1 release)) #271

...-empeg5?
Hugo: This time you are FORCED to publish that patch.
Where is the patch?


--
Raphael Wegmann
[email protected]
Posted by: altman

Re: EMPEG Boot Messages ?!? - 05/09/1999 07:03

It's not a seaprate patch - this is rolled into the np- patchset: I think it's actually in np-10 now. Have a look on ftp.cam.org/users/nico

Hugo


Posted by: raphael

Re: EMPEG Boot Messages ?!? - 05/09/1999 12:13

What do I need in the rc scripts in order to leave empeg in a usable state after replacing init?
Could you publish scrawl (and your echox) somewhere?

I'd love to have a minimal debian on my radio. :-)


--
Raphael Wegmann
[email protected]
Posted by: altman

Re: EMPEG Boot Messages ?!? - 05/09/1999 16:29

Mike's the only guy who would really know about this: he's the debian one :) (and he's on holiday for a week). As I remember, we just used the stock init scripts from the minimal ARM-debian install for netwinder by Jim Pick.

With a minimal init of:

#!/bin/sh
/bin/sh

The unit is usable... if there's no init, the kernel will run the shell anyway.

hugo