Problems when trying Debian image on Gdium

50 views
Skip to first unread message

Sha Liu

unread,
Jul 13, 2009, 1:37:17 PM7/13/09
to One Laptop Per Hacker
Hi everyone,
These days I tried the Debian LXDE image[0] on a second Gkey but
always hang when I load the kernel.At Pmon, I use
"load /dev/fs/ext2@usbg0/boot/vmlinuz-2.6.24-gdium-1"
then it just hang there with no response. I also tried to load
"vmlinux.32" but same. I also use the same partition scheme there.
I didn't change any of the env variable in pmon like "al" or "karg".
As it may help, they'er
al = /dev/fs/ext2@usbg0/boot/vmlinux.32
karg = console=tty1 root=LABEL=mips rootwait video=sm501fb:1024x600
init=/sbin/finit-mdv
BTW, I can boot the default gkey with g-linux with no problem.

Any thoughts?

[0]http://olph.gdium.com/wiki/doku.php/projects:debian_at_gdium:start

--
Best,
Sha Liu

julien forgeat

unread,
Jul 13, 2009, 11:08:53 PM7/13/09
to gd...@googlegroups.com
Hi,

I have just tried to boot the image with the same karg and al as you
and the system also hangs. An easy fix is to replace root=LABEL=mips
by root=/dev/sda2 in your karg.

I have also tried to set the mips label to /dev/sda2 using e2label but
the system still hangs during the boot, it's quite important to have
the system being able to boot with the same PMON settings as Mandriva
so I will keep checking that.

Thanks,

Julien

Sha Liu

unread,
Jul 14, 2009, 1:11:27 PM7/14/09
to One Laptop Per Hacker


On Jul 14, 11:08 am, julien forgeat <julienforg...@gmail.com> wrote:
> Hi,
>
> I have just tried to boot the image with the same karg and al as you
> and the system also hangs. An easy fix is to replace root=LABEL=mips
> by root=/dev/sda2 in your karg.
>
> I have also tried to set the mips label to /dev/sda2 using e2label but
> the system still hangs during the boot, it's quite important to have
> the system being able to boot with the same PMON settings as Mandriva
> so I will keep checking that.
>
I replace the root in karg as you said but still hang there.
It hangs just after I type "load /dev/fs/ext2@usbg0/boot/
vmlinuz-2.6.24-gdium-1" which I think the karg is not used yet. So I
guess the problem is in the kernel image, right?

--
Best,
Sha Liu

julien forgeat

unread,
Jul 14, 2009, 10:56:38 PM7/14/09
to gd...@googlegroups.com
Hi,

Here are my al and karg values, the system boots fine with these on
the Gdiums I have here:

al="/dev/fs/ext2@usbg0/boot/vmlinux.32"
karg="console=tty1 root=/dev/sda2 rootwait video=sm501fb:1024x600@60
init=/sbin/finit-mdv"

al should be the same value as what was configured when you received
the machine.

Cheers,

Julien

Sha Liu

unread,
Jul 16, 2009, 12:57:53 PM7/16/09
to One Laptop Per Hacker
On Jul 15, 10:56 am, julien forgeat <julienforg...@gmail.com> wrote:
> Hi,
>
> Here are my al and karg values, the system boots fine with these on
> the Gdiums I have here:
>
> al="/dev/fs/ext2@usbg0/boot/vmlinux.32"
> karg="console=tty1 root=/dev/sda2 rootwait video=sm501fb:1024x600@60
> init=/sbin/finit-mdv"
>
> al should be the same value as what was configured when you received
> the machine.
>
Today I check the md5sum of "gdium_lenny_sda2_07022009.tar.bz2" and
extract it again but still failed. Down below is all the variables I
got from PMON:

novga=1
splashimage=bfc60000
karg = "console=tty1 root=/dev/sda2 rootwait video=sm501fb:1024x600@60
init=/sbin/finit-mdv"
rd = /dev/fs/ext2@usbg0/boot/inird.gz
al = /dev/fs/ext2@usbg0/vmlinux.32
memsize = 256
highmemsize = 256
cpuclock = 891760000
busclock = 66000000
systype = Bonito
brkcmd = "l -r @cpc 1"
datasize = -b
dlecho = off
dlproto = none
bootp = no
hostport = tty0
inalpha = hex
inbase = 16
moresz = 10
prompt = "PMON> "
regstyle = sw
regsize = 32
rptcmd = trace
trabort = ^K
ulcr = cr
uleof = %
showsym = yes
fpfmt = both
fpdis = yes
Version = "Gdium PMON V1.3 Compiled Feb 11 2009 12:40:40"

I notice there's no initrd.gz in /boot. Is this a problem?
And as it may help, would you please try to "load /dev/fs/ext2@usbg0/
boot/
vmlinux.32" manually?


--
Best,
Sha Liu
Reply all
Reply to author
Forward
0 new messages