Hyperion Entertainment Message Boards

Posted: **Thu Dec 08, 2016 3:34 pm**

kilaueabart wrote: Finally got around to rc-8. I think I never did try rc-7, though I did prepare it for testing.

rc-8 seems to work OK. I am disappointed that I don't get wi-fi with it, but maybe that's an unrelated problem? Or does it have anything to do with
Code: Select all
hid-generic 0003:046D:052B.C003 device has no listeners, quitting
? I don't recall seeing that one before.

Lately, whatever newer kernel I use, right after "Started Braille Device Support" I get another attempt and failure to "Load Kernel Modules." Adds a bit of color to the notices.

Hi Kilaueabart,

Thank you for testing! Is the device 0003:046D:052B.C003 your wi-fi usb device?

Cheers,
Christian

Posted: **Fri Dec 09, 2016 1:37 am**

xeno74 wrote: Is the device 0003:046D:052B.C003 your wi-fi usb device?

I suspected it was when I wrote it down, but now I don't think so. Do you know off the top of your head what any of these interesting messages mean?

CFE, when I plugged the wifi dongle in:

Code: Select all

vender 7392 product 7811 class FF: Not found

Today I booted with kernel 4.8 because it had been working so far. Some interesting boot messages include{code]rtlwifi: Firmware rtl8192cufw_TMSC.bin[/code]Maybe google will give me a hint about that one. (No. "81,400,000 results" but the early ones offer not hope.)

Then, before the boot messages blanked out on me (are they stored anywhere, like one of the logs?) something about

Code: Select all

no ISA IO ranges ...

I think I have seen that before.

Then, down at the bottom, one I see from time to time, and have failed to find out what it means via Google:

Code: Select all

eth0: could not attach to phy

Meanwhile the dongle is working, only in the sense that it finds nearby wifi's including my own. It just won't let me log on.

Posted: **Fri Dec 09, 2016 4:19 pm**

Amigo1 wrote:
xeno74 wrote:
@All
Today, I released the new RC8 for testing.

Cheers,
Christian
I just tested 4.9-RC8 but the booting just stops at "Booting Linux via __start() 0x000000000000000000 ... "

I tried to boot using the other newer kernels: All fail

last working kernel here is 4.7.10

[rant]
I think you (and srtest) will find that actually it is NOT crashing at the Booting Linux.. as I now have a R9 270X card and have seen this..

Look at the HDD light, you will see that it continues to flicker for quite a few seconds, which it wouldn't do if it had crashed. Also during a serial debug I see the following

Code: Select all

Linux agpgart interface v0.103
[drm] Initialized drm 1.1.0 20060810
[drm] radeon kernel modesetting enabled.
[drm] initializing kernel modesetting (PITCAIRN 0x1002:0x6810 0x1462:0x3036 0x00).
[drm] register mmio base: 0xA0000000
[drm] register mmio size: 262144
ATOM BIOS: 113
radeon 0000:01:00.0: VRAM: 4096M 0x0000000000000000 - 0x00000000FFFFFFFF (4096M used)
radeon 0000:01:00.0: GTT: 2048M 0x0000000100000000 - 0x000000017FFFFFFF
[drm] Detected VRAM RAM=4096M, BAR=256M
[drm] RAM width 256bits DDR
[TTM] Zone  kernel: Available graphics memory: 2002902 kiB
[TTM] Initializing pool allocator
[drm] radeon: 4096M of VRAM memory ready
[drm] radeon: 2048M of GTT memory ready.
[drm] Loading pitcairn Microcode
radeon 0000:01:00.0: Direct firmware load for radeon/pitcairn_k_smc.bin failed with error -2
radeon 0000:01:00.0: Direct firmware load for radeon/PITCAIRN_smc.bin failed with error -2
smc: error loading firmware "radeon/PITCAIRN_smc.bin"
si_fw: mixing new and old firmware!
[drm:.si_init] *ERROR* Failed to load firmware!
radeon 0000:01:00.0: Fatal error during GPU init
[drm] radeon: finishing device.
[TTM] Finalizing pool allocator
[TTM] Zone  kernel: Used memory at exit: 0 kiB
[drm] radeon: ttm finalized
radeon: probe of 0000:01:00.0 failed with error -22
[drm] amdgpu kernel modesetting enabled.
loop: module loaded

This would have been easier to identify *if* we'd been given accurate bug reports.
[/rant]

From this log, and from this web site:

wiki.gentoo.org/wiki/Radeon

it seems that from 4.8 Pitcairn cards need an additional firmware pitcairn_k_smc.bin which is missing from Christian's current builds.

Christian: can you rebuild the latest rc with this firmware added, I don't have a copy. I'll give it a test once you have.

Thanks
Darren

Posted: **Fri Dec 09, 2016 10:05 pm**

daz wrote: it seems that from 4.8 Pitcairn cards need an additional firmware pitcairn_k_smc.bin which is missing from Christian's current builds.

Christian: can you rebuild the latest rc with this firmware added, I don't have a copy. I'll give it a test once you have.

Thanks
Darren

Hi Darren,

Many thanks for your help. I updated all firmwares and I added the firmware pitcairn_k_smc.bin to the kernel config.

@All

I released the RC8-2 because of Darren's hint today.

New:

- New binary firmwares for AMD/ATI graphics chips supported by the radeon and amdgpu drivers (firmware-amd-graphics_20161130-1)
- Phoronix articles, reviews and news stories covering Linux 4.9

Download: vmlinux-4.9-rc8-2-AmigaONE_X1000.tar.gz

@Amigo1 and Srtest
Please test the RC8-2.

Thanks,
Christian

Posted: **Sat Dec 10, 2016 7:16 pm**

It boots!! thanks!

Unfortunately it gets stuck at logon while declaring it has no more room left to create whatever it needs to create. I guess they once again broke btrfs after it worked very well. Either that or incompatibilites with ubuntu and fs2k. I'm adding pics that try to capture it from the console. Something about ubuntu upgrader/updater (latest version on latest 16.10). Booting with 4.7 doesn't cause it and it logges-on without an issue.

Posted: **Sat Dec 10, 2016 8:07 pm**

Srtest wrote:It boots!! thanks!

Unfortunately it gets stuck at logon while declaring it has no more room left to create whatever it needs to create. I guess they once again broke btrfs after it worked very well. Either that or incompatibilites with ubuntu and fs2k. I'm adding pics that try to capture it from the console. Something about ubuntu upgrader/updater (latest version on latest 16.10). Booting with 4.7 doesn't cause it and it logges-on without an issue.

Hi Srtest,

Many thanks for testing the RC8-2.

Do you have an ext4 partition for testing the RC8-2? If not, could you please boot the ubuntu MATE 16.04.1 LTS Live DVD with the RC8-2?

You can boot the DVD with the following commands:

Code: Select all

CFE> ramdisk -addr=0x24000000 -fs=iso atapi0.1:casper/powerpc64/initrd.

Code: Select all

CFE> setenv bootargs "root=/dev/ramdisk file=/cdrom/preseed/ubuntu-mate.seed boot=casper quiet ro splash --"

Code: Select all

CFE> boot -elf -noints -fatfs cf0:vmlinux-4.9

Thanks,
Christian

Posted: **Sat Dec 10, 2016 11:03 pm**

daz wrote:
Amigo1 wrote:
xeno74 wrote:
[rant]
I think you (and srtest) will find that actually it is NOT crashing at the Booting Linux.. as I now have a R9 270X card and have seen this..

Look at the HDD light, you will see that it continues to flicker for quite a few seconds, which it wouldn't do if it had crashed. Also during a serial debug I see the following
Code: Select all
Linux agpgart interface v0.103
[drm] Initialized drm 1.1.0 20060810
[drm] radeon kernel modesetting enabled.
[drm] initializing kernel modesetting (PITCAIRN 0x1002:0x6810 0x1462:0x3036 0x00).
[drm] register mmio base: 0xA0000000
[drm] register mmio size: 262144
ATOM BIOS: 113
radeon 0000:01:00.0: VRAM: 4096M 0x0000000000000000 - 0x00000000FFFFFFFF (4096M used)
radeon 0000:01:00.0: GTT: 2048M 0x0000000100000000 - 0x000000017FFFFFFF
[drm] Detected VRAM RAM=4096M, BAR=256M
[drm] RAM width 256bits DDR
[TTM] Zone  kernel: Available graphics memory: 2002902 kiB
[TTM] Initializing pool allocator
[drm] radeon: 4096M of VRAM memory ready
[drm] radeon: 2048M of GTT memory ready.
[drm] Loading pitcairn Microcode
radeon 0000:01:00.0: Direct firmware load for radeon/pitcairn_k_smc.bin failed with error -2
radeon 0000:01:00.0: Direct firmware load for radeon/PITCAIRN_smc.bin failed with error -2
smc: error loading firmware "radeon/PITCAIRN_smc.bin"
si_fw: mixing new and old firmware!
[drm:.si_init] *ERROR* Failed to load firmware!
radeon 0000:01:00.0: Fatal error during GPU init
[drm] radeon: finishing device.
[TTM] Finalizing pool allocator
[TTM] Zone  kernel: Used memory at exit: 0 kiB
[drm] radeon: ttm finalized
radeon: probe of 0000:01:00.0 failed with error -22
[drm] amdgpu kernel modesetting enabled.
loop: module loaded
This would have been easier to identify *if* we'd been given accurate bug reports.
[/rant]

From this log, and from this web site:

wiki.gentoo.org/wiki/Radeon

it seems that from 4.8 Pitcairn cards need an additional firmware pitcairn_k_smc.bin which is missing from Christian's current builds.

Christian: can you rebuild the latest rc with this firmware added, I don't have a copy. I'll give it a test once you have.

Thanks
Darren

Hi,

As soon as I connected a Null Modem cable and observed what happened when I booted 4.7 after 4.9-rc1, I had the same thought about the issue you suggested, namely that linux is booting in the background.
Oddly the succefull boot does not indicate an improper shutdown (via reset button) .

Unfortunately my AmigaOne X1000 Fractal design R4 case does not have an HDD LED, and the SSD on which Linux is install is far to silent to hear it. a(I will add one so I can monitor the drive in the future)

However, I will be more careful in my future reports.

regards

Posted: **Sat Dec 10, 2016 11:15 pm**

xeno74 wrote:
Amigo1 wrote: I just tested 4.9-RC8 but the booting just stops at "Booting Linux via __start() 0x000000000000000000 ... "

I tried to boot using the other newer kernels: All fail

last working kernel here is 4.7.10

Linux Mate 16.04.1 LTS
AmigaOne X1000
4GB RAM
Gigabyte R9 270X GFX-card
Tested with AMD Sapphire Radeon 250 does not work either.
Hi Amigo1,

Thank you for testing the RC8. Could you please post a serial log? I will discuss this problem in the A-EON Linux team.

Thanks,

Christian

Hi Christian,

A few hours ago I got the materials and the time to solder a NULL-Modem cable (they are getting rare as it seems, no shop had one in the surroundings()
As it seems it was too late,
4.9-RC2 works.

Should you need it, I could now post the -I think now unnecessary- serial log of the "non-booting" 4.9-RC1 Kernel, but as it appears it was booting after all, just not displaying anything.

Posted: **Sun Dec 11, 2016 1:00 am**

Amigo1 wrote: Hi Christian,

A few hours ago I got the materials and the time to solder a NULL-Modem cable (they are getting rare as it seems, no shop had one in the surroundings()
As it seems it was too late,
4.9-RC2 works.

Should you need it, I could now post the -I think now unnecessary- serial log of the "non-booting" 4.9-RC1 Kernel, but as it appears it was booting after all, just not displaying anything.

Hi Amigo1,

Thanks a lot for testing!

Is it possible to login to the desktop?

Cheers,
Christian

Posted: **Sun Dec 11, 2016 1:59 am**

I will answer for him: yes

They again changed something with btrfs even though it was working as it should be.

While this link is unrelated to the topic it's very interesting: http://askubuntu.com/questions/464074/u ... ut-its-not

"Btrfs is different from traditional filesystems. It is not just a layer that translates filenames into offsets on a block device, it is more of a layer that combines a traditional filesystem with LVM and RAID. And like LVM, it has the concept of allocating space on the underlying device, but not actually using it for files... When considering free space in Btrfs, we have to clarify which free space we are talking about - the block layer, or the file layer?".

Hyperion Entertainment Message Boards

Kernel 4.9

Re: Kernel 4.9

Re: Kernel 4.9

Re: Kernel 4.9

Re: Kernel 4.9

Re: Kernel 4.9

Re: Kernel 4.9

Re: Kernel 4.9

Re: Kernel 4.9

Re: Kernel 4.9

Re: Kernel 4.9