Message from the bottle
The debug output catched by 64-bit qemu showed today the following output (from emulated serial console):
[BOOT] AROS Bootstrap.
[BOOT] Command line '/aros-x86_64 vesa=640x480x16'
[VESA] module (@ 0010A4BC) size=2144
[VESA] Module installed
[VESA] BestModeMatch for 640x480x16 = 111
[VESA] Module uninstalled
[BOOT] GRUB provides the following memory map:
[BOOT] 0000000000000000 - 000000000009FC00: 1
[BOOT] 0000000000100000 - 0000000007F00000: 1
[BOOT] Setting up descriptor tables.
[BOOT] Mapping first 4G area with MMU
[BOOT] Loading kernel
[BOOT] GRUB has loaded 4 files
[BOOT] * module asmsupport.o
[BOOT] * module aros.o
[BOOT] * package kernel.pkg:
[BOOT] * module aros.o
[BOOT] * module asmsupport.o
[BOOT] * module aros.o
[BOOT] Loading asmsupport.o
[BOOT] Loading aros.o
[BOOT] Leaving 32-bit environment. LJMP $8,$0000000000F80000
--------------------
[AROS64] 64-bit AROS. Copyright (C) 2006 The AROS Development Team. All rights reserved.
Please note, that the bootstrap is now capable to switch VESA mode on demand (best mode match of command line argument), parse modules loaded by grub and even parse packages of modules. :-)
[BOOT] AROS Bootstrap.
[BOOT] Command line '/aros-x86_64 vesa=640x480x16'
[VESA] module (@ 0010A4BC) size=2144
[VESA] Module installed
[VESA] BestModeMatch for 640x480x16 = 111
[VESA] Module uninstalled
[BOOT] GRUB provides the following memory map:
[BOOT] 0000000000000000 - 000000000009FC00: 1
[BOOT] 0000000000100000 - 0000000007F00000: 1
[BOOT] Setting up descriptor tables.
[BOOT] Mapping first 4G area with MMU
[BOOT] Loading kernel
[BOOT] GRUB has loaded 4 files
[BOOT] * module asmsupport.o
[BOOT] * module aros.o
[BOOT] * package kernel.pkg:
[BOOT] * module aros.o
[BOOT] * module asmsupport.o
[BOOT] * module aros.o
[BOOT] Loading asmsupport.o
[BOOT] Loading aros.o
[BOOT] Leaving 32-bit environment. LJMP $8,$0000000000F80000
--------------------
[AROS64] 64-bit AROS. Copyright (C) 2006 The AROS Development Team. All rights reserved.
Please note, that the bootstrap is now capable to switch VESA mode on demand (best mode match of command line argument), parse modules loaded by grub and even parse packages of modules. :-)
posted by Michal Schulz at 07:23
5 Comments:
Michal a jak postep prac nad sterami dla kart ATI?Ostatnio nie piszesz nic w tym temacie...
Pozdrawiam
Bo karta ATI ktora mialem ma zlacze AGP, ktorego brak w moim nowym systemie. Dlatego prace stanely w miejscu.
Jak tylko dotrze do mnie nowa karta (powinna byc na dniach) zabieram sie do roboty.
Hi Michal
I hope that you have the time to answer som questions about SFS fs.
Do you know about a linux/windoze tool to make SFS partitions? I've looked at PQmagic but no luck there. Maby linux fdisk will create SFS? Can aros kernel read SFS?
My plan is to create a SFS partition. Then boot aros max and copy stuff over to the hard drive. Finaly, then make a floppy with Grub installed, and point it to the SFS partition.
I think this would ba an easy way for non devs to install aros on their computer. Using this method, there is almost no way to lose partitions and data from the drives.
Thanks for reading!
PS, how is the ATI driver comming along? :-)
Tor/Norway
Hello Tor,
If you want a SFS partition for AROS, you may easily prepare it on linux. The only thing you need is a primary (that's important!) partition with type 0x2f. I don'T know whether PQMagic allows changing of partition types.
AROS kernel can read SFS partitions if only the sfs filesystem is linked with it.
Once you have a primary partition with type 2f, it will show up on AROS with some name in form of ATAxPy (device number x on ATA bus, partition y) which may be formatted with both C:format and C:sfsformat.
ATI driver waits. In my new machine I cannot use ATI I have. Currently I'm waiting for next one (donated by Kalamatee)
That's the same carpet freshener we use. We love experimenting with different scents.
.........
Suman
Wow, check out this site called www.fluc.combr/>. Free SMS and free mobile ads!! Its fantastic
Post a Comment
<< Home