NGFileSystem

AmigaOne X5000 platform specific issues.

Re: NGFileSystem

Postby tonyw » Thu Dec 29, 2016 11:12 am

U-Boot has no say in what sort of file systems are bootable. The program that scans all the disk partitions and makes up the list (the "AmigaOS 4.x U-Boot BootLoader" screen) is amigaboot.ub, which is written into the SD card on the mobo. When you type "boota", amigaboot runs and does its work, never returning to U-Boot. Amigaboot scans all the devices, lists the bootable volumes and loads all the Kickstart modules from the disk. It lastly jumps to the Loader, which is one of the Kickstart modules.. That is the start of OS4 running by itself.

Unfortunately U-Boot can only initialise (and provide access to) the on-board SATA controller. If your shiny new system partition is on an HD or SSD that is connected to a PCI card, you won't be able to boot from it (directly, anyway).
cheers
tony
User avatar
tonyw
AmigaOS Core Developer
AmigaOS Core Developer
 
Posts: 1184
Joined: Wed Mar 09, 2011 2:36 pm
Location: Sydney, Australia

Re: NGFileSystem

Postby Alloye » Thu Dec 29, 2016 6:13 pm

tonyw wrote:U-Boot has no say in what sort of file systems are bootable. The program that scans all the disk partitions and makes up the list (the "AmigaOS 4.x U-Boot BootLoader" screen) is amigaboot.ub, which is written into the SD card on the mobo.


Thanks for the information. It really clears things up! Using FFS, I get an entry in that list, but with NGFS I don't.

Is there any way I can update amigaboot.ub? I've had my X5K for over a year, so I'm sure it's out-of-date.

Unfortunately U-Boot can only initialise (and provide access to) the on-board SATA controller. If your shiny new system partition is on an HD or SSD that is connected to a PCI card, you won't be able to boot from it (directly, anyway).


Also good to know, but I was using a drive connected directly to the motherboard in this case.
Alloye
 
Posts: 7
Joined: Tue Apr 12, 2016 1:45 am
Location: Colorado, USA

Re: NGFileSystem

Postby radzikpl » Tue Mar 21, 2017 8:06 pm

I think I have found big bug in NGFS. I have problems with SQL files in for example Odyssey. After fresh installation the cookies.db was somehow broken. First of all Odyssey was not able to save cookies. Second, program Cookie Monster was crashing itself. I have copied my old cookies.db (from Pegasos / SFS) and all is working. The same problems are with passwords.db etc. It looks like every SQL file is not correct. Meanwhile I was working with Odyssey based on NGFS, but yesterday the same error (after many days). Cookies.db broken.

I have also tested new RSS reader, it uses also SQL files. After install, configurations of RSS program works. But after close/start (2x - 3x times) database is broken. I can only copy old file. Program is working perfect with SFS.

Probobably the same problem is with Timberwolf, it's working only from SFS (maybe FFS too). First install and run on NGFS is ok, but after close/restart TW is crashed.

Any sugestions? I'm writing X5000 / OS4 book and I must put correct informations for my readers.
radzikpl
 
Posts: 11
Joined: Sun Jan 18, 2015 1:53 pm

Re: NGFileSystem

Postby tonyw » Wed Mar 22, 2017 12:29 am

Thanks for that report, I have tested NGFS with Timberwolf on the X5000 and it crashes just as you say.

I am currently investigating the problem.
cheers
tony
User avatar
tonyw
AmigaOS Core Developer
AmigaOS Core Developer
 
Posts: 1184
Joined: Wed Mar 09, 2011 2:36 pm
Location: Sydney, Australia

Re: NGFileSystem

Postby tonyw » Mon Mar 27, 2017 12:53 am

I have found and fixed the problem causing those data corruptions and crashes. Thanks again for reporting it.
cheers
tony
User avatar
tonyw
AmigaOS Core Developer
AmigaOS Core Developer
 
Posts: 1184
Joined: Wed Mar 09, 2011 2:36 pm
Location: Sydney, Australia

Previous

Return to Platform: AmigaOne X5000

Who is online

Users browsing this forum: No registered users and 1 guest

cron