Boot from HD/Devices in E-uae

KONEY · 22 July 2009, 18:54

Hi all!

I moved myself a bit into Ubuntu so I have installed E-uae to emulate amigas.

Now, I can't find the option to boot from real amiga devices like HDs or CFs. With winuae I used to share a CF betweend a real amiga with IDE-CF converter installed and the pc...is this impossible withing a linux environment?

Thanx

Jerry · 24 July 2009, 11:34

I don't think euae has the raw-access functions of Winuae since they might be quite platform dependent (not so easily portable...). Also the most kernels support amiga partitions out of the box through the affs driver. Unfortunately there is currently no fuse driver for affs so its a bit complicated to use with removable devices. Anyhow, here is what I do:

Step 1: make a mountpoint directory mkdir ~/amigamount

Step 2: mount amiga partition
sudo mount -t affs -o uid=(your_uid_here) /dev/sdXY ~/amigamountpoint (dmesg is your friend to find out on which dev-node your newly attached cf-card resides and the Y denotes the partition number)

Step 3: change euae-config to use the directory as harddisk (add the line to your configfile or do it in the gui):
filesystem2=rw,HD0:VolumeName:/home/$YOURUSERNAME/amigamount,0

Step4: fire up e-uae

KONEY · 01 August 2009, 23:11

hi! thanx a lot for you hints!

This trick should work but unlukily i'm stuck on step 2

Let me abuse of your help and see what I'm doing:

Code:

koney@BEAST2-UBUNTU:~$ ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 2009-08-01 17:27 86146a1b-7850-470a-a818-f77e752e4ef6 -> ../../sdb5
lrwxrwxrwx 1 root root 10 2009-08-01 17:27 9A54E65E54E63C9F -> ../../sda2
lrwxrwxrwx 1 root root 10 2009-08-01 17:27 a0d2082d-f9ef-4112-a7b9-bd1eb62ba4ce -> ../../sdb6
lrwxrwxrwx 1 root root 10 2009-08-01 17:27 AC9470EC9470BA82 -> ../../sdb1
lrwxrwxrwx 1 root root 10 2009-08-01 17:27 D6C8D505C8D4E531 -> ../../sda1
lrwxrwxrwx 1 root root 10 2009-08-01 23:04 FC30-3DA9 -> ../../sdc1
koney@BEAST2-UBUNTU:~$ sudo mount -t affs -o FC30-3DA9 /dev/sdc1 ~/amigamount
mount: wrong fs type, bad option, bad superblock on /dev/sdc1,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

dmesg says:

Code:

[27409.823232]  sdc: sdc1
[27436.295567] AFFS: Unrecognized mount option "FC30-3DA9" or missing value
[27436.295571] AFFS: Error parsing options

so I guess I'm using a bad syntax for mount

anyway, issuing the mount command without specifing the uid at all I get this from dmesg:

Code:

[27648.146071] AFFS: No valid root block on device sdc1

the card has 4 partition, but that shouldn't be a problem since I specify the first one in sdc1...

Jerry · 02 August 2009, 19:26

Oh, I made a little mistake, the uid command is setuid, not uid. Sorry for that one. Also, with uid I meant your user-id (which is typically 1000 for the user first created most distributions - try "grep $USER /etc/passwd") not the uuid of your harddrive. So your mount line should probably read:

sudo mount -t affs -o setuid=1000 /dev/sdc1 ~/amigamount

Hungry Horace · 02 August 2009, 19:39

hmm... this really is quite clever!

thanks Jerry for an informative post - i may try this one out myself.

KONEY · 02 August 2009, 20:45

ah ok here's why! I also tried with user ID before but it made more sense to me that the device id was needed...

Thanx a lot for your extra help...

Anyway now I got this:
[33356.199618] AFFS: No valid root block on device sdc1

the card happily boots on a real amiga...Now I'm going to make a test with winuae but it has always booted from there too...

Jerry · 02 August 2009, 23:03

So close, yet so far

. It seems the card is not formatted with a compatible (speak ofs/ffs/..., see the linux kernel doc->affs.txt) filesystem. Did you use a special filesystem on the card?

KONEY · 02 August 2009, 23:34

not really....standard FFS (using standard wordbench)

I am a little confused by the fact that only sdc1 is reckognized as a device, I have 4 partition on the CF so I should be able to mount sdc0, sdc1, sdc2 and sdc3...isn't it?

KONEY · 03 August 2009, 00:26

EDIT: I tried with another CF (FFS formatted but not partitioned) and i succeded in mounting it! sadly i'ts only a 16mb used for tests

KONEY · 03 August 2009, 00:32

MAybe I need to "revalidate" the CF on the amiga...i tried editing the RDB but it looks OK yet...

Jerry · 03 August 2009, 10:27

Too bad, I also think that something is wrong with the partition table. What also puzzles me is that you have a uuid entry under /dev/disk/by-uuid for the cf. I always thought that uuids are only available for the major filesystems. Incidentally my cf does not show up there.

Maybe you could post the output of
sudo fdisk -l /dev/sdc (gives me something about no valid partition table)

and the output of
tail -f /var/log/messages (gives me sth. about sdc: RDSK (512) sdc1 (DOS^C)(res 2 spb 1))

the moment you attach the card. Good luck.

KONEY · 03 August 2009, 10:35

Thanx, I didnt' know those commands! I am trying them:

Code:

koney@BEAST2-UBUNTU:~$ tail -f /var/log/messages
Aug  3 09:45:36 BEAST2-UBUNTU kernel: [   16.176091] [fglrx] Reserved FB block: Unshared offset:1fffb000, size:5000 
Aug  3 09:45:39 BEAST2-UBUNTU kernel: [   18.514392] r8169: eth0: link up
Aug  3 09:45:39 BEAST2-UBUNTU kernel: [   18.514398] r8169: eth0: link up
Aug  3 10:05:32 BEAST2-UBUNTU -- MARK --
Aug  3 10:15:53 BEAST2-UBUNTU syslogd 1.5.0#5ubuntu3: restart.
Aug  3 10:32:47 BEAST2-UBUNTU kernel: [ 2845.865640] sd 4:0:0:0: [sdc] 3964464 512-byte hardware sectors: (2.02 GB/1.88 GiB)
Aug  3 10:32:47 BEAST2-UBUNTU kernel: [ 2845.866119] sd 4:0:0:0: [sdc] Write Protect is off
Aug  3 10:32:47 BEAST2-UBUNTU kernel: [ 2845.866748] sd 4:0:0:0: [sdc] 3964464 512-byte hardware sectors: (2.02 GB/1.88 GiB)
Aug  3 10:32:47 BEAST2-UBUNTU kernel: [ 2845.867120] sd 4:0:0:0: [sdc] Write Protect is off
Aug  3 10:32:47 BEAST2-UBUNTU kernel: [ 2845.867130]  sdc: sdc1

and

Code:

koney@BEAST2-UBUNTU:~$ sudo fdisk -l /dev/sdc
[sudo] password for koney: 

Disk /dev/sdc: 2029 MB, 2029805568 bytes
64 heads, 63 sectors/track, 983 cylinders
Units = cylinders of 4032 * 512 = 2064384 bytes
Disk identifier: 0x001c2022

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *           1         983     1981696+   6  FAT16

hey it says FAT16!?

Jerry · 03 August 2009, 11:55

Now this becomes interesting.

Is it possible that the cf at one point was formatted fat16 and later partitioned for amiga use? If so, there is probably mbr with the normal pc partitiontable and the amiga rdb with the amiga partitiontable. If I remember correctly both can coexist. That could be the source of your trouble. The only thing I'm unsure about is how to fix the issue. Your safest bet would probably be to backup the cf and reformat it.

You might also want to have a look at amiga-fdisk (see also here ). Other than that I'm out of simple options. Probably a look at the source of affs would help. In any case you SHOULD backup the cf before you try anything. You might even consider dumping the whole cf and first operating on the loopback mounted image (should also be a lot quicker).

KONEY · 03 August 2009, 12:59

Thanx a lot man!
...maybe the CF was low-level factory-formatted because I always used it for amiga since I bought it...

I will try something different, see the docs or try with a new CF formatted with affs maybe...

Jerry · 04 August 2009, 19:57

It seems the affs-code just supports the rdb in block 0 where it typically resides. If you like you could raw dump the first blocks (RDB is allowed in the first 16 blocks if my information is true) or so and have a look at them with a hexeditor. The RDB starts with "RDSK".

KONEY · 04 August 2009, 20:43

man I just remembered (and there's also a post here in EAB) that sometimes ago I switched the pc-xp on with the CF loaded and it automatically scandisked it making it unreadable! Luckily with a disksalv session I managed to get all the data back but now I realize that when I put the CF on XP I see a log file of that time! so I think you're right, this CF is both amiga and fat16!

Now I'm backupping all my partitions as HDFs to HD using winuae the I will try to low-level format it on the real amiga and let's see what happen!

At the end the problem was windows, as usual!

D

KONEY · 05 August 2009, 01:06

I DID IT!!! I had to backup my data, low-level format the CF by issueing a DD command (under linux, on the amiga I didn't manage to have a low-level formatting working...dunno why) and the I re-formatted with FFS (took more than a hour!) and now the amiga CF is reckognized!!

Thanx a lot for your hints!

prowler · 05 August 2009, 01:18

Quote:

Originally Posted by KONEY

I DID IT!!!

Well done, mate!

Congratulations on your dedication to the task!

Another EAB success!

Jerry · 05 August 2009, 11:46

Congrats,
you could have saved some time by only wiping out the first blocks using dd and then doing ffs quickformat, but who cares

KONEY · 05 August 2009, 19:13

Yes I could have, but I lost so much time that I don't count it anymore

22 July 2009, 18:54	#1
KONEY OctaMED Music Composer Join Date: Jan 2009 Location: Venice - Italy Age: 49 Posts: 667	Boot from HD/Devices in E-uae Hi all! I moved myself a bit into Ubuntu so I have installed E-uae to emulate amigas. Now, I can't find the option to boot from real amiga devices like HDs or CFs. With winuae I used to share a CF betweend a real amiga with IDE-CF converter installed and the pc...is this impossible withing a linux environment? Thanx

04 August 2009, 20:43	#16
KONEY OctaMED Music Composer Join Date: Jan 2009 Location: Venice - Italy Age: 49 Posts: 667	man I just remembered (and there's also a post here in EAB) that sometimes ago I switched the pc-xp on with the CF loaded and it automatically scandisked it making it unreadable! Luckily with a disksalv session I managed to get all the data back but now I realize that when I put the CF on XP I see a log file of that time! so I think you're right, this CF is both amiga and fat16! Now I'm backupping all my partitions as HDFs to HD using winuae the I will try to low-level format it on the real amiga and let's see what happen! At the end the problem was windows, as usual! D Last edited by KONEY; 04 August 2009 at 23:13.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
To boot an UAE from USB?	Edwooger	support.OtherUAE	6	26 June 2013 21:17
Hotpluggable joystick devices in FS-UAE?	yesplease	support.FS-UAE	3	29 January 2013 21:15
FS-UAE mounting PC devices to WB	elowan	support.FS-UAE	30	24 January 2013 08:27
[FS-UAE] Control FS-UAE with iOS devices	nexusle	support.FS-UAE	0	18 July 2012 22:57
FS-UAE boot on hard drive	joufflu	support.FS-UAE	3	13 May 2012 17:12

24 July 2009, 11:34	#2
Jerry Registered User Join Date: Mar 2005 Location: Germany Age: 44 Posts: 210	I don't think euae has the raw-access functions of Winuae since they might be quite platform dependent (not so easily portable...). Also the most kernels support amiga partitions out of the box through the affs driver. Unfortunately there is currently no fuse driver for affs so its a bit complicated to use with removable devices. Anyhow, here is what I do: Step 1: make a mountpoint directory mkdir ~/amigamount Step 2: mount amiga partition sudo mount -t affs -o uid=(your_uid_here) /dev/sdXY ~/amigamountpoint (dmesg is your friend to find out on which dev-node your newly attached cf-card resides and the Y denotes the partition number) Step 3: change euae-config to use the directory as harddisk (add the line to your configfile or do it in the gui): filesystem2=rw,HD0:VolumeName:/home/$YOURUSERNAME/amigamount,0 Step4: fire up e-uae

02 August 2009, 19:26	#4
Jerry Registered User Join Date: Mar 2005 Location: Germany Age: 44 Posts: 210	Oh, I made a little mistake, the uid command is setuid, not uid. Sorry for that one. Also, with uid I meant your user-id (which is typically 1000 for the user first created most distributions - try "grep $USER /etc/passwd") not the uuid of your harddrive. So your mount line should probably read: sudo mount -t affs -o setuid=1000 /dev/sdc1 ~/amigamount

02 August 2009, 19:39	#5
Hungry Horace Wipe-Out Enthusiast Join Date: Nov 2005 Location: . Age: 43 Posts: 2,538	hmm... this really is quite clever! thanks Jerry for an informative post - i may try this one out myself.

02 August 2009, 20:45	#6
KONEY OctaMED Music Composer Join Date: Jan 2009 Location: Venice - Italy Age: 49 Posts: 667	ah ok here's why! I also tried with user ID before but it made more sense to me that the device id was needed... Thanx a lot for your extra help... Anyway now I got this: [33356.199618] AFFS: No valid root block on device sdc1 the card happily boots on a real amiga...Now I'm going to make a test with winuae but it has always booted from there too...

02 August 2009, 23:03	#7
Jerry Registered User Join Date: Mar 2005 Location: Germany Age: 44 Posts: 210	So close, yet so far . It seems the card is not formatted with a compatible (speak ofs/ffs/..., see the linux kernel doc->affs.txt) filesystem. Did you use a special filesystem on the card?

02 August 2009, 23:34	#8
KONEY OctaMED Music Composer Join Date: Jan 2009 Location: Venice - Italy Age: 49 Posts: 667	not really....standard FFS (using standard wordbench) I am a little confused by the fact that only sdc1 is reckognized as a device, I have 4 partition on the CF so I should be able to mount sdc0, sdc1, sdc2 and sdc3...isn't it?

03 August 2009, 00:26	#9
KONEY OctaMED Music Composer Join Date: Jan 2009 Location: Venice - Italy Age: 49 Posts: 667	EDIT: I tried with another CF (FFS formatted but not partitioned) and i succeded in mounting it! sadly i'ts only a 16mb used for tests

03 August 2009, 00:32	#10
KONEY OctaMED Music Composer Join Date: Jan 2009 Location: Venice - Italy Age: 49 Posts: 667	MAybe I need to "revalidate" the CF on the amiga...i tried editing the RDB but it looks OK yet...

03 August 2009, 10:27	#11
Jerry Registered User Join Date: Mar 2005 Location: Germany Age: 44 Posts: 210	Too bad, I also think that something is wrong with the partition table. What also puzzles me is that you have a uuid entry under /dev/disk/by-uuid for the cf. I always thought that uuids are only available for the major filesystems. Incidentally my cf does not show up there. Maybe you could post the output of sudo fdisk -l /dev/sdc (gives me something about no valid partition table) and the output of tail -f /var/log/messages (gives me sth. about sdc: RDSK (512) sdc1 (DOS^C)(res 2 spb 1)) the moment you attach the card. Good luck.

03 August 2009, 11:55	#13
Jerry Registered User Join Date: Mar 2005 Location: Germany Age: 44 Posts: 210	Now this becomes interesting. Is it possible that the cf at one point was formatted fat16 and later partitioned for amiga use? If so, there is probably mbr with the normal pc partitiontable and the amiga rdb with the amiga partitiontable. If I remember correctly both can coexist. That could be the source of your trouble. The only thing I'm unsure about is how to fix the issue. Your safest bet would probably be to backup the cf and reformat it. You might also want to have a look at amiga-fdisk (see also here ). Other than that I'm out of simple options. Probably a look at the source of affs would help. In any case you SHOULD backup the cf before you try anything. You might even consider dumping the whole cf and first operating on the loopback mounted image (should also be a lot quicker).

03 August 2009, 12:59	#14
KONEY OctaMED Music Composer Join Date: Jan 2009 Location: Venice - Italy Age: 49 Posts: 667	Thanx a lot man! ...maybe the CF was low-level factory-formatted because I always used it for amiga since I bought it... I will try something different, see the docs or try with a new CF formatted with affs maybe...

04 August 2009, 19:57	#15
Jerry Registered User Join Date: Mar 2005 Location: Germany Age: 44 Posts: 210	It seems the affs-code just supports the rdb in block 0 where it typically resides. If you like you could raw dump the first blocks (RDB is allowed in the first 16 blocks if my information is true) or so and have a look at them with a hexeditor. The RDB starts with "RDSK".

05 August 2009, 01:06	#17
KONEY OctaMED Music Composer Join Date: Jan 2009 Location: Venice - Italy Age: 49 Posts: 667	I DID IT!!! I had to backup my data, low-level format the CF by issueing a DD command (under linux, on the amiga I didn't manage to have a low-level formatting working...dunno why) and the I re-formatted with FFS (took more than a hour!) and now the amiga CF is reckognized!! Thanx a lot for your hints!

05 August 2009, 11:46	#19
Jerry Registered User Join Date: Mar 2005 Location: Germany Age: 44 Posts: 210	Congrats, you could have saved some time by only wiping out the first blocks using dd and then doing ffs quickformat, but who cares

05 August 2009, 19:13	#20
KONEY OctaMED Music Composer Join Date: Jan 2009 Location: Venice - Italy Age: 49 Posts: 667	Yes I could have, but I lost so much time that I don't count it anymore

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)