And the big comment is correct. It may not be this specific chip.
It's this specific chip on this specific machine. Later on we
may know more, to identify the problem better.
Mark Kettenis wrote:
> > Date: Sun, 16 Jun 2024 16:37:10 +
> > From: Klemens Nanni
> >
> > GENERIC cpu(4) fix
> Date: Sun, 16 Jun 2024 16:37:10 +
> From: Klemens Nanni
>
> GENERIC cpu(4) fix and pcidevs have been committed.
> Now only this ahci(4) quirk is pending to fix the SSD.
>
> Neither Linux nor FreeBSD seem to have AHCI and/or MSI specific
> quirks for this, but contrary to OpenBSD they can
GENERIC cpu(4) fix and pcidevs have been committed.
Now only this ahci(4) quirk is pending to fix the SSD.
Neither Linux nor FreeBSD seem to have AHCI and/or MSI specific quirks for this,
but contrary to OpenBSD they can boot and use the SSD.
Until there's a better way, this disabling MSI for
pcidevs alone, sorted (thanks jsg).
https://www.devicekb.com/hardware/pci-vendors/ven_1d17 shows
"ZX-100/ZX-200/ZX-E StorX AHCI Controller" wich is quite long.
There are a bunch of other unknown products on this machine, but so far only
the AHCI controller is needed to fix something, so I'm
16.06.2024 05:50, Jonathan Gray пишет:
> MTRR is not set on ramdisk kernels, try the diff below
No change with your diff.
> Index: sys/arch/amd64/amd64/mtrr.c
> ===
> RCS file: /cvs/src/sys/arch/amd64/amd64/mtrr.c,v
> diff -u -p
16.06.2024 00:35, Klemens Nanni пишет:
> GENERIC and GENERIC_MP both hang with this diff after
> cpu0: 4MB 64b/line 16-way L2 cache
> but I haven't looked into that yet.
brynet had the right idea, this diff makes it boot X, even VMM works
(I folded his indent/additional if into the existing one
On Sat, Jun 15, 2024 at 09:35:30PM +, Klemens Nanni wrote:
> GENERIC and GENERIC_MP both hang with this diff after
> cpu0: 4MB 64b/line 16-way L2 cache
> but I haven't looked into that yet.
...
> cpu0: ZHAOXIN KaiXian KX-6640MA@2.2+GHz, 2594.84 MHz, 07-0b-00
MTRR is not set on ramdisk
16.06.2024 01:02, Mark Kettenis пишет:
> MSIs work for the other devices (e.g. iwm(4) or xhci(4))?
install75.img via USB 3.x, loading iwm-firmware from and 'ping 1.1.1.1'
over iwx0 in an installer shell worked, so I guess that means yes:
>> iwm0 at pci4 dev 0 function 0 "Intel AC 7265" rev 0x59,
> Date: Sat, 15 Jun 2024 21:35:30 +
> From: Klemens Nanni
>
> Unchartevice 6640MA notebook with amd64 ZHAOXIN KaiXian KX-6640MA CPU.
>
> https://unchartevice.ru
> https://www.devicekb.com/hardware/pci-vendors/ven_1d17-dev_9083
>
> BIOS one of three SATA speed modes:
> - Gen1/2: bsd.rd
Unchartevice 6640MA notebook with amd64 ZHAOXIN KaiXian KX-6640MA CPU.
https://unchartevice.ru
https://www.devicekb.com/hardware/pci-vendors/ven_1d17-dev_9083
BIOS one of three SATA speed modes:
- Gen1/2: bsd.rd reaches installer, but SSD does not attach
ahci0: device not communicating on port
10 matches
Mail list logo
