Installing ubuntu 13.04 server

Hi,

Due to software dependencies I need to install Ubuntu 13.04 on the BeagleBoard-xM, but there is only a server install and no pre-installed desktop version as with 12.04. I installed the installer on 1 sd card, then connected a cardreader with another sd (call it nr2) card to a usb port and started installing 13.04. However, after installing and putting nr2 into the sd card slot, it won’t boot. This is probably because the device is set to /de/sdc instead of /dev/mmcblk0p2 or so. So my question is: how can I change the boot so that it boots from nr2 in the sd card slot.

Thanks.

Hi,

Due to software dependencies I need to install Ubuntu 13.04 on the
BeagleBoard-xM, but there is only a server install and no pre-installed
desktop version as with 12.04.

Use your network and run: "sudo apt-get install xyz-desktop"....

I installed the installer on 1 sd card, then
connected a cardreader with another sd (call it nr2) card to a usb port and
started installing 13.04. However, after installing and putting nr2 into the
sd card slot, it won't boot. This is probably because the device is set to
/de/sdc instead of /dev/mmcblk0p2 or so. So my question is: how can I change
the boot so that it boots from nr2 in the sd card slot.

pastebin.com your "serial" boot log, uEnv.txt, & /etc/fstab

Or just rebuild the image from scratch again with my "NetInstall" script..

https://github.com/RobertCNelson/netinstall

(and select the "desktop" once the package selection screen popsup)

Regards,

Hi,

Due to software dependencies I need to install Ubuntu 13.04 on the
BeagleBoard-xM, but there is only a server install and no pre-installed
desktop version as with 12.04.

Use your network and run: “sudo apt-get install xyz-desktop”…

Once I get it to work, I will use that…

I installed the installer on 1 sd card, then
connected a cardreader with another sd (call it nr2) card to a usb port and
started installing 13.04. However, after installing and putting nr2 into the
sd card slot, it won’t boot. This is probably because the device is set to
/de/sdc instead of /dev/mmcblk0p2 or so. So my question is: how can I change
the boot so that it boots from nr2 in the sd card slot.

pastebin.com your “serial” boot log, uEnv.txt, & /etc/fstab

Can’t find “serial” boot.log or uEnv.txt. But http://pastebin.com/UGGHDd38 has my /etc/fstab, which clearly shows how it was installed. No clue though by what it should be replaced

Or just rebuild the image from scratch again with my “NetInstall” script…

https://github.com/RobertCNelson/netinstall

Thanks for the hint.

(and select the “desktop” once the package selection screen popsup)

Regards,

hvn

"serial boot log" grab a usb-serial port adapter and log the board's
output as it boots..

Yuck, uuid, that's going to be fun to debug.. Just change them to
/dev/mmcblk0p2 & /dev/mmcblk0p1 to see if helps..

Regards,

Hi,

Due to software dependencies I need to install Ubuntu 13.04 on the
BeagleBoard-xM, but there is only a server install and no pre-installed
desktop version as with 12.04.

Use your network and run: “sudo apt-get install xyz-desktop”…

Once I get it to work, I will use that…

I installed the installer on 1 sd card, then
connected a cardreader with another sd (call it nr2) card to a usb port
and
started installing 13.04. However, after installing and putting nr2 into
the
sd card slot, it won’t boot. This is probably because the device is set
to
/de/sdc instead of /dev/mmcblk0p2 or so. So my question is: how can I
change
the boot so that it boots from nr2 in the sd card slot.

pastebin.com your “serial” boot log, uEnv.txt, & /etc/fstab

Can’t find “serial” boot.log or uEnv.txt. But http://pastebin.com/UGGHDd38
has my /etc/fstab, which clearly shows how it was installed. No clue though
by what it should be replaced

“serial boot log” grab a usb-serial port adapter and log the board’s
output as it boots…

Oh, that. It gives 60. From the xm Troubleshooting: “If a 60 is displayed over the
serial cable, processor is booting. Issue could be the SD/MMC card.” Which is not booting…

Yuck, uuid, that’s going to be fun to debug… Just change them to
/dev/mmcblk0p2 & /dev/mmcblk0p1 to see if helps.

And this again gives error 60 on the serial boot log.

'60' your microSD is not properly formatted or Missing MLO/etc...

Better just start over with the NetInstall..

Regards,

Hi,

Due to software dependencies I need to install Ubuntu 13.04 on the
BeagleBoard-xM, but there is only a server install and no
pre-installed
desktop version as with 12.04.

Use your network and run: “sudo apt-get install xyz-desktop”…

Once I get it to work, I will use that…

I installed the installer on 1 sd card, then
connected a cardreader with another sd (call it nr2) card to a usb
port
and
started installing 13.04. However, after installing and putting nr2
into
the
sd card slot, it won’t boot. This is probably because the device is
set
to
/de/sdc instead of /dev/mmcblk0p2 or so. So my question is: how can I
change
the boot so that it boots from nr2 in the sd card slot.

pastebin.com your “serial” boot log, uEnv.txt, & /etc/fstab

Can’t find “serial” boot.log or uEnv.txt. But
http://pastebin.com/UGGHDd38
has my /etc/fstab, which clearly shows how it was installed. No clue
though
by what it should be replaced

“serial boot log” grab a usb-serial port adapter and log the board’s
output as it boots…

Oh, that. It gives 60. From the xm Troubleshooting: “If a 60 is displayed
over the
serial cable, processor is booting. Issue could be the SD/MMC card.” Which
is not booting…

Yuck, uuid, that’s going to be fun to debug… Just change them to
/dev/mmcblk0p2 & /dev/mmcblk0p1 to see if helps.

And this again gives error 60 on the serial boot log.

‘60’ your microSD is not properly formatted or Missing MLO/etc…

Well, there indeed is no MLO etc in the boot partition. It looks like a regular one for non-BBxM. But it was installed from the Ubuntu13.04 ARM server install image. So I’d expect that it would work.

Better just start over with the NetInstall…

I assume that will work for Ubuntu 13.04 ?

Regards,

hvn

Ok, that should work. Just a question: this is for armel or armhf ? How many options do you recommend ?

Regards,

hvn

'60' your microSD is not properly formatted or Missing MLO/etc...

Well, there indeed is no MLO etc in the boot partition. It looks like a
regular one for non-BBxM. But it was installed from the Ubuntu13.04 ARM
server install image. So I'd expect that it would work.

Better just start over with the NetInstall..

I assume that will work for Ubuntu 13.04 ?

13.04 : "--distro raring"

For the xM, use either:

--dtb omap3-beagle-xm

Which will install: v3.7.10-x13 and supports every "expansion" device
supported, plus the sgx drivers can be used..

or:

--dtb dt-beagleboard-xm

which will pull in v3.12.0-armv7-x7, doesn't support any expansion
devices, but 1Ghz operation works and the evil usb errata bug is
patched, it's also kms based so no 3d drivers exist..

Regards,

Ok, that should work. Just a question: this is for armel or armhf ? How many
options do you recommend ?

13.04/raring has always been armhf "only".. armel was dropped from
ports.ubuntu.com in 12.10...

Regards,

Ok, the netinstall boots fine, but it fails to find the default mirror. And considering a post from 4-2012 I’m not the first to experience this.
On installation: will this install raring on the mmc I’m booting from or do I need a different medium to install on ? Because that was the case with the server install as well. If so, I should install the netinstall on a USB stick and try to boot from that.

> Ok, that should work. Just a question: this is for armel or armhf ? How
> many
> options do you recommend ?

13.04/raring has always been armhf "only".. armel was dropped from
ports.ubuntu.com in 12.10...

Ok, the netinstall boots fine, but it fails to find the default mirror. And
considering a post from 4-2012 I'm not the first to experience this.

Nope, "still" works for me.. Can you ping http://ports.ubuntu.com/
locally? As there is NO other mirrors. In that past it's always
turned out the end user has had a crappy/limited internet connection.

Side note, did it actually say "cannot connect to mirror?" or did you
get tired of waiting the 10 minutes for ubuntu to do it's thing i
mention in the notes:

Note: with Ubuntu Releases
During Install, after proxy setup, there seems to be a VERY LONG delay...
(on average it seems to be taking anywhere between 10-20 Minutes)...
In the background: Ubuntu is trying really-really hard to find a
compatible kernel...

On installation: will this install raring on the mmc I'm booting from or do
I need a different medium to install on ? Because that was the case with the
server install as well. If so, I should install the netinstall on a USB
stick and try to boot from that.

The NetInstall has one big limitation, the psychical device you
flashed the installer with the "mk_mmc.sh" command has to be used at
all times to "boot" the device. As the bootloader/etc is in that
small 100Mb boot fat partition..

However the "rootfs" can be almost anywhere else, from what's left on
that microSD, or on a usb-sata drive, or on another microSD (for some
platforms that have two slots..)..

Just remember, at partition stage, DO NOT TOUCH the 100MB fat/boot
partition, if you do you break the install and will have to start all
over with the "mk_mmc.sh" command as everything needed to "finish" the
install is located in that partition..

Regards,

Ok, that should work. Just a question: this is for armel or armhf ? How
many
options do you recommend ?

13.04/raring has always been armhf “only”… armel was dropped from
ports.ubuntu.com in 12.10…

Ok, the netinstall boots fine, but it fails to find the default mirror. And
considering a post from 4-2012 I’m not the first to experience this.

Nope, “still” works for me… Can you ping http://ports.ubuntu.com/
locally? As there is NO other mirrors. In that past it’s always
turned out the end user has had a crappy/limited internet connection.

Side note, did it actually say “cannot connect to mirror?” or did you
get tired of waiting the 10 minutes for ubuntu to do it’s thing i
mention in the notes:

Note: with Ubuntu Releases
During Install, after proxy setup, there seems to be a VERY LONG delay…
(on average it seems to be taking anywhere between 10-20 Minutes)…
In the background: Ubuntu is trying really-really hard to find a
compatible kernel…

Ok. This was a network error. I had to renew the DHCP lease, and then it started fine. However, it stops with an error on Select and install software.
I checked in BusyBox terminal with df which shows 11% used in the target partition, the other partitions show 0% use.

On installation: will this install raring on the mmc I’m booting from or do
I need a different medium to install on ? Because that was the case with the
server install as well. If so, I should install the netinstall on a USB
stick and try to boot from that.

The NetInstall has one big limitation, the psychical device you
flashed the installer with the “mk_mmc.sh” command has to be used at
all times to “boot” the device. As the bootloader/etc is in that
small 100Mb boot fat partition…

However the “rootfs” can be almost anywhere else, from what’s left on
that microSD, or on a usb-sata drive, or on another microSD (for some
platforms that have two slots…)…

Just remember, at partition stage, DO NOT TOUCH the 100MB fat/boot
partition, if you do you break the install and will have to start all
over with the “mk_mmc.sh” command as everything needed to “finish” the
install is located in that partition…

Ok, the SD card is 8GB which so far was enough for the things I want.

Regards,

hvn

If it "stops" is the board hardlocking? "ctrl-alt-f4" will get you to
the log window when using the video/mouse/keyboard...

What's the error showing? My first guess it's that old v3.7.x based
kernel with the usb errata bug.. just use the v3.12.x kernel option...

Regards,

dpkg-divert: error: unable to create new file ‘/var/lib/dpkg/diversions-new’: Read-only file system
cleanup failed
can’t remove ‘/target/usr/sbin/policy-rc.d’: Read-only file system

Cannot open question file /target/var/cache/debconf/config.dat: Read-only file system
Unexpected error: command not executed: ‘sh -c debconf-apt-progress tasksel’

Configuring ‘pkgsel’ failed with error code 1

So is this the usb errata bug ?

Regards,

hvn

dpkg-divert: error: unable to create new file
'/var/lib/dpkg/diversions-new': Read-only file system
cleanup failed
can't remove '/target/usr/sbin/policy-rc.d': Read-only file system
<omitted>
Cannot open question file /target/var/cache/debconf/config.dat: Read-only
file system
Unexpected error: command not executed: 'sh -c debconf-apt-progress
<omitted> tasksel'
<omitted>
Configuring 'pkgsel' failed with error code 1

So is this the usb errata bug ?

Nah your microSD card took a drive, looks like it just could not
handle the sustained writes so flipped to ro.. Is this with v3.7.x or
v3.12.x?

Regards,

This is with omap3-beagle-xm

Regards,

hvn

give "dt-beagleboard-xm" it's newer/faster and the future..

Regards,

Ok, went wrong as well:

dpkg: error: ‘/var/lib/dpkg/reassemble.deb’ doesn’t exist: Read-only file system

This error shows for many packages. Any suggestions ?

Ok, tried this twice, once with only the SDcard. This stops with “Read-only file system” as well. Then I tried using a USB stick as storage (although I actually don’t want to) and this goes fine untill finishing. Then it can’t write the boot disk (or have to do this somehow manually). Since it should be able to boot from the SDcard, I tried this and fails to boot. Then tried again with only SDcard, and this fails again the same way. To be clear: the installer suggests to install / and swap on mmcblk 5 and 6 and I say Ok to that because it doesn’t touch the boot partition (right?)