Hyperion Entertainment Message Boards

musa wrote: ↑Mon Mar 01, 2021 10:46 am Yes I can Christian.
Here is kernel 5.12-rc1 on Fienix . I have not put modules in libs but the kernel boot fine.
Have a nice day

Great that Darren'ts patch works! Thanks a lot for testing!

xeno74 wrote: ↑Mon Mar 01, 2021 12:55 pm

musa wrote: ↑Mon Mar 01, 2021 10:46 am Yes I can Christian.
Here is kernel 5.12-rc1 on Fienix . I have not put modules in libs but the kernel boot fine.
Have a nice day

Great that Darren'ts patch works! Thanks a lot for testing!

Hi Christian what does this patch do ,that the kernel could not before?

musa wrote: ↑Mon Mar 01, 2021 7:28 pm Hi Christian what does this patch do ,that the kernel could not before?

Connecting the SB600's i8259 controller rather in pasemi's pci.c than in pasemi's setup.c. "pas_pci_init" was before "nemo_init_IRQ". Now "pas_pci_init" is after "nemo_init_IRQ" in the official kernel source code. I think "pas_pci_init" scans (discovers) the PCI(e) devices and after that, "nemo_init_IRQ" assigns interrupt numbers to these devices if required. It's not possible to assigns interrupt numbers to PCI(e) devices which have not been discovered yet.

@Darren

Could you please explain your patch? I am not sure if I understand it correctly.

Thanks,
Christian

xeno74 wrote: ↑Mon Mar 01, 2021 8:59 pm

musa wrote: ↑Mon Mar 01, 2021 7:28 pm Hi Christian what does this patch do ,that the kernel could not before?

Connecting the SB600's i8259 controller rather in pasemi's pci.c than in pasemi's setup.c. "pas_pci_init" was before "nemo_init_IRQ". Now "pas_pci_init" is after "nemo_init_IRQ" in the official kernel source code. I think "pas_pci_init" scans (discovers) the PCI(e) devices and after that, "nemo_init_IRQ" assigns interrupt numbers to these devices if required. It's not possible to assigns interrupt numbers to PCI(e) devices which have not been discovered yet.

@Darren

Could you please explain your patch? I am not sure if I understand it correctly.

You're not far off with your description above.

Originally we initialised the PCI-e ports in setup arch, this is quite early, and it seems uses some kernel functions that were not recommended (They changed a whole lot of different platforms at the same time for the same reason)

After this we added the ISA bridge, then the kernel would init the IRQ contollers.

The patch that broke booting on the X1000 moved the pas_pci_init to a node in the machine description, where it called later in the boot sequence. Unfortunately this is after we've tried to add the i8259 contoller from the pas_init_IRQ. Since our ISA bridge can't be found until we've connected the PCI-e ports the system tries to write to registers that aren't yet mapped - result a kernel panic, but before console I/O has been initialised so it appears to be a hang. We had a similar problem when they were introducing Radix support.

My patch changes our code so that it works with the new kernel code in place. Basically I moved the code that adds the i8259 cascade to after we've scanned for the ISA bridge where I know it will work.

Hopefully this makes sense, shout out if it doesn't

Regards
Darren

Hi Darren,

Thanks a lot for your explanation. I understand it better now.

Cheers,
Christian

Hi All,

Linus Torvalds has withdrawn the RC1 because of the file system corruption issue through a swapfile. This issue has been resolved with today's latest Git code. Please don't use the RC1 if you work with a swapfile. I will create a new RC1 with the swapfile patch.
I don't use any swapfiles and swap partitions on my AmigaOnes so I am luckily not affected.

Link: Linux 5.12 Lands Fix For File-System Corruption Caused By Swapfile Issue

Thanks,
Christian

Hi All,

Here is the RC1-2 of kernel 5.12 for testing.

New:

• The issue with the file-system corruption caused by swapfile has been fixed
• Linux Git log
• Phoronix articles, reviews and news stories covering Linux 5.12

Download: linux-image-5.12-rc1-2-X1000_X5000.tar.gz



Please test the kernels.

Thanks,
Christian

Hi hristian
Here is ubuntu 16.04 with kernel 5.12-rc1-2. Boot with a lot of error messages that I do not think had anything to do with the kernel. Afterwards, I lost access to my hard drive 3 with most of my Linux partitions. Back are Ubuntu 16.04 and Fienix. I have now inserted a new larger completely empty hard drive and formatted it in several partitions. Can I move my Fienix partition to a new empty partition on the new hard disk with the DD command? Or are there any better methods?
Have a nice day

musa wrote: ↑Fri Mar 05, 2021 3:36 pm Hi hristian
Here is ubuntu 16.04 with kernel 5.12-rc1-2. Boot with a lot of error messages that I do not think had anything to do with the kernel. Afterwards, I lost access to my hard drive 3 with most of my Linux partitions. Back are Ubuntu 16.04 and Fienix. I have now inserted a new larger completely empty hard drive and formatted it in several partitions. Can I move my Fienix partition to a new empty partition on the new hard disk with the DD command? Or are there any better methods?
Have a nice day

Hi Musa,

Many thanks for testing the RC1-2. Yes, you can move your Fienix partition to a new empty partition if it is big enough.

Cheers,
Christian

xeno74 wrote: ↑Sat Mar 06, 2021 4:18 am

Hi Musa,

Many thanks for testing the RC1-2. Yes, you can move your Fienix partition to a new empty partition if it is big enough.

Cheers,
Christian

Hi Christian
I decided to use rsync. I have brought to life the old hard drive in a usb hard drive bay. Now I have soon transferred all my linux partitions to the new hard drive. Then I should soon be up and running again.
Have a nice day
Peter