Re: Bug#1012347: arm64 CPU Phytium FT-2000/4 cpuinfo
Hello Punit, On Wed, Jun 08, 2022 at 09:40:08AM +0100, Punit Agrawal wrote: > Helge Kreutzmann writes: > > On Tue, Jun 07, 2022 at 09:47:03AM +0100, Punit Agrawal wrote: > >> "xiao sheng wen(肖盛文)" writes: > >> > >> > 在 2022/6/5 21:18, Helge Kreutzmann 写道: > >> >>> CPU implementer: 0x70 > >> >> If you happen to know a table of "CPU implementer" for ARM (i.e. a > >> >> mapping of the number to the company), then I can easily add even > >> >> more :-)) > >> > >> You can see the list of currently assigned implementer codes in the > >> description of the MIDR_EL1 register[0] in the Arm developer > >> documentation. > >> > >> [0] > >> https://developer.arm.com/documentation/ddi0595/2021-06/External-Registers/MIDR-EL1--Main-ID-Register > > > > Thanks a lot, I added those, should greatly improve detection on Arm. > > Interestingly, though, the recently reported "Phytium" is not on the > > list. (Which what this report was initially about) > > Indeed, I noticed it too after sending the mail. Sorry, I don't know > what's going on there. Probably need somebody from Arm.com to add their > 2c. I don't think we need to bother, the current state is now vastly improved, and I take Phytium as a "bonus". Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: PGP signature
Re: Debian 11 on Sheevaplug?
Gilles writes: > On 08/06/2022 00:54, Rick Thomas wrote: >> On Tue, Jun 7, 2022, at 6:32 AM, Gilles wrote: >>> It ends with a single error : "partman: mkswap: can't open '/dev/sda5': >>> No such file or directory": >>> >>> https://pastebin.com/raw/h0beZWnP >> It looks like /dev/sd5 doesn't actually exist. This is probably because the >> USB stick has an MBR partition table which by default only provides >> partitions 1-4. You may need to pre-partition it with a GUID partition >> table. >> >> Rick > > Good call. After using Windows' diskpart*, I removed the MBR and > converted to GPT. The installer went one step further… and failed: > > https://postimg.cc/ns5XMQL7 > > Here's the log: > > https://pastebin.com/raw/htYCmhS3 The ``bad block bitmap checksum'' relating to /dev/sda2, followed by ``Remounting filesystem read-only'' seems to be the source of your problem. After that point nothing's going to work because your new root filesystem (/target/) is faulty, and is now read-only, so there's no way to create the /target/boot directory, so the mount of the boot partition fails. My guess would be an underlying hardware fault on whatever /dev/sda2 is. I don't suppose there's any chance it's a fake USB stick - see: http://oss.digirati.com.br/f3/ (packaged for Debian as ``f3'') Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560] HANDS.COM Ltd. |-| http://www.hands.com/http://ftp.uk.debian.org/ |(| Hugo-Klemm-Strasse 34, 21075 Hamburg,GERMANY signature.asc Description: PGP signature
Re: Debian 11 on Sheevaplug?
On 08/06/2022 00:54, Rick Thomas wrote: On Tue, Jun 7, 2022, at 6:32 AM, Gilles wrote: It ends with a single error : "partman: mkswap: can't open '/dev/sda5': No such file or directory": https://pastebin.com/raw/h0beZWnP It looks like /dev/sd5 doesn't actually exist. This is probably because the USB stick has an MBR partition table which by default only provides partitions 1-4. You may need to pre-partition it with a GUID partition table. Rick Good call. After using Windows' diskpart*, I removed the MBR and converted to GPT. The installer went one step further… and failed: https://postimg.cc/ns5XMQL7 Here's the log: https://pastebin.com/raw/htYCmhS3 * https://www.diskpart.com/articles/remove-mbr-partition-3889i.html
Re: Bug#1012347: arm64 CPU Phytium FT-2000/4 cpuinfo
Helge Kreutzmann writes: > Hello Punit, > On Tue, Jun 07, 2022 at 09:47:03AM +0100, Punit Agrawal wrote: >> "xiao sheng wen(肖盛文)" writes: >> >> > 在 2022/6/5 21:18, Helge Kreutzmann 写道: >> >>> CPU implementer : 0x70 >> >> If you happen to know a table of "CPU implementer" for ARM (i.e. a >> >> mapping of the number to the company), then I can easily add even >> >> more :-)) >> >> You can see the list of currently assigned implementer codes in the >> description of the MIDR_EL1 register[0] in the Arm developer >> documentation. >> >> [0] >> https://developer.arm.com/documentation/ddi0595/2021-06/External-Registers/MIDR-EL1--Main-ID-Register > > Thanks a lot, I added those, should greatly improve detection on Arm. > Interestingly, though, the recently reported "Phytium" is not on the > list. (Which what this report was initially about) Indeed, I noticed it too after sending the mail. Sorry, I don't know what's going on there. Probably need somebody from Arm.com to add their 2c. [...]
