Hi,
I've reactivated my Seagate Dockstar, that was lying around in my cupboard for
some month. I did the following:
1. reinstalled Doozans U-Boot to have a clean system to start
2. prepared an USB stick with sda1=boot, sda2=swap, sda3=rootfs
3. untared the Slackware ARM minirootfs to the correct
On 30 November 2012 13:03, Thorsten Mühlfelder thenk...@salixos.org wrote:
4. changed some U-Boot settings to match my USB stick (rootfs=sda3, ext4)
I am not familiar with that device but shouldn't you add rootwait ?
___
ARMedslack mailing list
But while booting the initrd system fails to mount the rootfs. You can find a
complete log here:
http://pastebin.com/XLyCFiGV
You have four partitions not 3. What is on /dev/sda4?
Is your /etc/fstab setup?
You have a root shell there - can you share what you have done to
investigate it?
But while booting the initrd system fails to mount the rootfs. You can find a
complete log here:
http://pastebin.com/XLyCFiGV
IMHO the relevant part:
mount: mounting /dev/sda3 on /mnt failed: Invalid argument
ERROR: No /sbin/init found on rootdev (or not mounted). Trouble ahead.
nic=auto:mlan0:dhcp
or is this only worth for wired networking?
Then I would have to use use wpa_supplicant to bring the network up anyway.
Exactly - if your WLAN is secured (most likely) then you'd need another
service to help bring up the interface, so it doesn't seem that there's
any
On 30 November 2012 16:47, Stuart Winter m-li...@biscuit.org.uk wrote:
nic=auto:mlan0:dhcp
or is this only worth for wired networking?
Then I would have to use use wpa_supplicant to bring the network up anyway.
Exactly - if your WLAN is secured (most likely) then you'd need another
Exactly - if your WLAN is secured (most likely) then you'd need another
service to help bring up the interface, so it doesn't seem that there's
any value in adding this at boot.
But would it bring mlan0 up anyway, instead of typing:
ifconfig mlan0 up
I don't think it'll make any
On 30/11/2012 17:18, Stuart Winter wrote:
Exactly - if your WLAN is secured (most likely) then you'd need another
service to help bring up the interface, so it doesn't seem that there's
any value in adding this at boot.
But would it bring mlan0 up anyway, instead of typing:
ifconfig mlan0 up
On 30 November 2012 17:21, Dave Dowell dowe...@netscape.net wrote:
Isn't that the reason for rc.local in the standard rc.scripts? Why not just
add it there?
Thanks Dave and Stuart, I just wanted to experiment. I can't boot that
image anyway, so I can't tell you if it makes any difference.
--
On 30 November 2012 17:24, Ottavio Caruso
ottavio2006-usenet2...@yahoo.com wrote:
Thanks Dave and Stuart, I just wanted to experiment. I can't boot that
image anyway, so I can't tell you if it makes any difference.
Good news: I was able to boot the image.
Other news: indeed it made no
10 matches
Mail list logo
