Joggler fun

Wol

In Cryo Sleep
Okay. I dont actually see how you can brick it, cos itll load startup.nsh from either usb or internal, so as long as youve got a usb stick with the startup.nsh file on - then youre okay.

I've now got debian booting off the internal flash! aww yeah!
 

Haven

Administrator
Staff member
Grats :) now enlighten us on what you had to change so we can all learn from your mistakes.
 

Wol

In Cryo Sleep
boot.nsh was configured for usb boot, thus on fs1. If you move to the internal memory, you need to set this to be fs0:, otherwise it goes:

memory: 'sup. I'm the internal memory, how should I boot?
startup.nsh: go look at boot.nsh
boot.nsh: for usb sticks, run grub.efi
memory: .... but im internal memory
boot.nsh: well sucks to be you
memory: sulk :(

;)

However, the size of the image is quite hefty at the moment. Only have about 80mb free. Am running lxde at the moment, with gdm.
 

Haven

Administrator
Staff member
Cool, base image I built is 570M without an X system or Kernel. Its definately not as small and light as I planned ... yet :)
 

Wol

In Cryo Sleep
need some culling. I've got rid of man / doc / src. Going to cull out some locales I think now.

LXDE seems small enough for me though. Kernel is fairly minimal.

dpkg-query -W --showformat='${Installed-Size;10}\t${Package}\n' | sort -k1,1n (http://www.pixelbeat.org/docs/packaging.html)

seems handy

..... hm:

""after this operation, 123mb of additional disk space will be used""

how about...... no!
 
E

elDiablo

Guest
memory: 'sup. I'm the internal memory, how should I boot?
startup.nsh: go look at boot.nsh
boot.nsh: for usb sticks, run grub.efi
memory: .... but im internal memory
boot.nsh: well sucks to be you
memory: sulk :(...

You, sir, are so getting a cookie for this. This is awesome.

Also, thanks Wol! Shall be installng from flash soon!
 

Wol

In Cryo Sleep
OMNOMNOM

ta :)

Yea. flash isnt too tricky once you know what its doing. It doesnt mention it on the "how to boot from internal flash" page on the wiki though.

as far as i know, it looks for startup.nsh on both boot devices. so if you completely wipe the files on the internal /dev/mmcblk0p1 device (including startup.nsh), you can still stick a usb stick in which has a valid boot partition on, and all is fine (this is what happened when i thought I'd bricked it).

What I've got atm is:

Code:
root@sirius:/mnt1# ls -l
total 198
-rwxr-xr-x 1 root root    337 Jun  1 20:43 README.txt
-rwxr-xr-x 1 root root     10 Jun  1 20:45 boot.nsh
-rwxr-xr-x 1 root root     10 Jun  1 20:51 boot2.nsh
-rwxr-xr-x 1 root root    198 Jun  1 20:44 grub.cfg
-rwxr-xr-x 1 root root 190976 Jun  1 20:43 grub.efi
-rwxr-xr-x 1 root root     20 Jun  1 20:50 startup.nsh
root@sirius:/mnt1# cat startup.nsh
fs1:boot2
fs0:boot

root@sirius:/mnt1# cat boot.nsh
fs0:
grub
root@sirius:/mnt1# cat boot2.nsh
fs1:
grub
root@sirius:/mnt1# cat grub.cfg
set timeout=0

menuentry "Debian Squeeze" {
        set root=(hd0,2)
        linux /boot/vmlinuz-2.6.33.5 root=/dev/mmcblk0p2 ro acpi=force processor.max_cstate=3 rootdelay=10
        initrd /boot/initrd.img-2.6.33.5
}

The kernel is then loaded from the root partition (/dev/mmcblk0p2) under the boot folder, and all is happy.

I now need to go kick the window manager a bit now /methinks. Might just try and write my own as im going to try and make my own custom "os" to put on it. And its somewhat tempting to make a nice 3d opengl interface for spotify..... but i dunno whether I want to spend £10 a month to get spotify premium for it :p
 

Wol

In Cryo Sleep
Probably not so much a joggler question, but a general linux one:

Got the IEGD driver installed and being used:

OpenGL vendor string: Tungsten Graphics, Inc.
OpenGL renderer string: Gallium 0.1, pipe/psb/Poulsbo on IEGD

rather than it using the software rasteriser.

When i run an opengl app, e.g. glxgears, I can happily get a decent framerate at the start, and then after about 40 seconds, it has a hissy fit and plummets:

root@jogglewol:~# glxgears
2999 frames in 5.0 seconds = 599.645 FPS
3025 frames in 5.0 seconds = 604.973 FPS
3023 frames in 5.0 seconds = 604.581 FPS
2449 frames in 5.0 seconds = 489.370 FPS
682 frames in 5.0 seconds = 136.133 FPS
382 frames in 5.0 seconds = 76.279 FPS
383 frames in 5.0 seconds = 76.491 FPS


The same happens for flashplayer. Starts off really smooth, and then ends up jittery. I dunno if its like a memory leak in the graphics driver or something, but its quite annoying!

Anyone have any ideas?
 

Haven

Administrator
Staff member
Which iegd driver did you use and where did you get it?

I'm going to stick with xf86-video-intel to start with but will look at iegd later on if the performance is crap. Since its distributed under hokey licenses and hidden in rpm's from what I can see its going to be a pain to use iegd directly.
 

Haven

Administrator
Staff member
Ta, still working towards the point where I'll be able to offer a comparison. Compiling the kernel for it now :)

Grab me on IRC if you want to chat whilst you work.
 

Wol

In Cryo Sleep
IRC? We have an irc channel? :p

I'm tempted to scrap my currrent system and reinstall from the base system again if i cant get the right version of Xorg appearing again. *grumbles*.

stupid thing!
 
Top