BeagleBoard Ubuntu netinstall

Hi,

I am installing Ubuntu 10.10 on a BeagleBoard xM rev C. It installed
ok but I realized that it comes with kernel 2.6.38-13-omap and 3.2.0-
x1. The kernel I need is 2.6.38, but my instalation boots with 3.2.0
by default.

Please can anyone tell me how to configure the system to boot with
2.6.38 kernel.

Thanks

Hi,

I am installing Ubuntu 10.10 on a BeagleBoard xM rev C. It installed
ok but I realized that it comes with kernel 2.6.38-13-omap and 3.2.0-
x1. The kernel I need is 2.6.38, but my instalation boots with 3.2.0
by default.

First: Ubuntu's 2.6.38-13-omap won't work on the xM C, (ehci/dvi won't
work, remember maverick was released before the xm C came out..) so
don't try that one..

Please can anyone tell me how to configure the system to boot with
2.6.38 kernel.

Is there a specific reason you need a 2.6.38 kernel?

Next time: if you'd like a specific kernel with my netinstall script,
use the "--deb-file somefile.deb" option on the command line..

I've pulled all my v2.6.38.* releases's from rcn-ee.net (don't have
unlimited space), you can get an archive copy here:
http://rcn-ee.homeip.net:81/dl/mirrors/deb/maverick/v2.6.38.7-x4/linux-image-2.6.38.7-x4_1.0maverick_armel.deb
(cable modem, so slow)

then just on the beagle:
#backup:
sudo mv -v /boot/uboot/uImage /boot/uboot/uImage_old
sudo mv -v /boot/uboot/uInitrd /boot/uboot/uInitrd_old

sudo dpkg -i linux-image-2.6.38.7-x4_1.0maverick_armel.deb
sudo mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e
0x80008000 -n 2.6.38.7-x4 -d /boot/vmlinuz-2.6.38.7-x4
/boot/uboot/uImage
sudo update-initramfs -c -k 2.6.38.7-x4
sudo mkimage -A arm -O linux -T ramdisk -C none -a 0 -e 0 -n initramfs
-d /boot/initrd.img-2.6.38.7-x4 /boot/uboot/uInitrd

then reboot..

If you need to make changes, the git checkout for this version is at:

But that was back in May of 2011

Regards,

Hi Robert,

The reason I need the 2.6.38 kernel is because I have a uEye IDS
camera which only works with 2.6 kernels.

Thanks a lot,
Daniel

Really, they have a binary blob that works on arm? On there website i
see only 32/64 x86 binaries, do you have another connection or?

Regards,

I have started to try these insurrections and have gotten to the point
of booting the image created. In console through putty I get to the
point of Uncompressing Linux... done, booting the kernel and this is
where it stops.

The command I have tried is ./mk_mmc.sh --mmc /dev/sdb --uboot beagle_xm
--distro oneiric

I have also tried the maverick. I am not sure if this is why the boot
process has stopped or not, but this time with the macerick distro, I
noticed a line that read no ethernet found. I presume that the no
ethernet found is why the boot process has stopped.

Here is my console output as I have tried with a 4GB and 16GB Card. Off
to searching net to see if I can resolve this.

Hi Graham,

And what's on your DVI monitor?

I'm not sure what your expecting, but based on your serial log and the
command you passed to my "NetInstall" script (above), so far it's
operating correctly.. Do you have a LCD/DVI monitor connected to the
beagles video port? If you do not, you need to also pass
"--serial-mode"* then the "Debian Installer" will correctly ignore the
frame-buffer and allow you to use the serial console...

Of course, once the "Debian Install" is done, i have a script that'll
enable both serial and DVI output's automatically

* I'm not sure how i can make this more clearly, it's mentioned in the readme
--serial-mode
    <DVI Mode is default, this overrides it for Serial Mode>

but this same question pops up about once a month..

Regards,

Thanks for the reply, To answer the question I get a No Signal on the
DVI Monitor that is connected to the beagleboard. I will try with the
serial-mode switch to see what might be going on.

Still searching Net to get additional information.

Weird, what's the DVI Monitor's make & model number?

by default, with that script i'm forcing "1280x720MR-16@60" it might
be worth it to try "hd720" (just edit uEnv.txt)

Regards,

This is the same issue I reported… never solved.
I believe if you change console to /dev/tty02 in netinstall you will receive same error as i received. Kernel just hangs.
There is open ticket about that… bug report

When I did the --serial-mode I was able to get
additional information on the console. On the HDMI monitor I how have a
Penguin in the upper left hand corner while I am going through the
screens in Putty.

I am also trying this same switch with the oneiric distro to see if I
get the same results.

I have been searching the mailing list and Internet before I post
messages to see if I can resolve it first and some questions I have
solved by reading other peoples posts.

Actually, your bug report should be fixed now..

https://github.com/RobertCNelson/netinstall/issues/5

Been running it a few times this week on my c4 in the lab, while
re-trying to get the sgx bits working the omap35xx c4's..

Regards,

When I did the --serial-mode I was able to get
additional information on the console. On the HDMI monitor I how have a
Penguin in the upper left hand corner while I am going through the
screens in Putty.

Cool, then we just need to find the right resolution, as it does
work.. (what's the make/model #)..

I am also trying this same switch with the oneiric distro to see if I
get the same results.

With my script, that actually won't change anything.. As it'll pull
in the same exact kernel source, just built in an oneiric
environment..

Regards,

To report the Make/Model of the Monitor it is a Vizio E220MV and the URL
with Technical Information is at http://www.vizio.com/e220mv.html#support

I got it to work on my Monitor by taking out the letters after 720 on
the dvimode line.

Just information as I have configured one SD card the serial-mode way
and now doing another SD card without that option.

I got it to work on my Monitor by taking out the letters after 720 on
the dvimode line.

That's very odd, i'll add that to the readme.. btw, after the install
is done, the original uEnv.txt gets replaced by the contents of
normal.txt, so you will have to re-edit the final uEnv.txt, as it'll
have the "MR" letters back in the display settings..

Just information as I have configured one SD card the serial-mode way
and now doing another SD card without that option.

Regards,