Tiny Core Linux
Tiny Core Extensions => TCE Talk => Topic started by: Rabie on December 26, 2021, 06:19:39 PM
-
Hi,
i have an device called "ZBOX CI329 nano" https://www.amazon.de/gp/product/B07H569HM2/ref=as_li_tl?ie=UTF8&creativeASIN=B07H569HM2&linkCode=as2&tag=elefacts-21 (https://www.amazon.de/gp/product/B07H569HM2/ref=as_li_tl?ie=UTF8&creativeASIN=B07H569HM2&linkCode=as2&tag=elefacts-21)
it has the device Intel® Wireless-AC 9462 and the driver there for is "firmware-iwl9000.tcz"
On TinyCore version 10. x86 and 10. 10. x86_64 everything works fine
The driver does not work on both version 11x and 12x , x86 and x86_64
when starting with the driver i get this while booting: https://www.dropbox.com/s/s0e6yn93btg1o4a/Unbenannt3.PNG?dl=0
and the Ethernet adapters doesn't get up
-
Kernel bug, but we don't know where since that's posted earlier (instead of taking a picture, please copypaste text from dmesg). In any case, your easiest options are using 10.x or waiting for 13.x.
-
Kernel bug, but we don't know where since that's posted earlier (instead of taking a picture, please copypaste text from dmesg). In any case, your easiest options are using 10.x or waiting for 13.x.
Hi curaga,
i think this is the relevant text from dmesg:
loop: module loaded
zram0: detected capacity change from 0 to 465920000
random: mkswap: uninitialized urandom read (16 bytes read)
Adding 454996k swap on /dev/zram0. Priority:-2 extents:1 across:454996k SSFS
squashfs: version 4.0 (2009/01/31) Phillip Lougher
EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null)
random: crng init done
Linux agpgart interface v0.103
platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
platform regulatory.0: Falling back to sysfs fallback for: regulatory.db
i801_smbus 0000:00:1f.1: SPD Write Disable is set
i801_smbus 0000:00:1f.1: SMBus using PCI interrupt
i2c i2c-0: 1/2 memory slots populated (from DMI)
i2c i2c-0: Successfully instantiated SPD at 0x50
Intel(R) Wireless WiFi driver for Linux
iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-46.ucode failed with error -2
iwlwifi 0000:00:0c.0: Falling back to sysfs fallback for: iwlwifi-9000-pu-b0-jf-b0-46.ucode
i915 0000:00:02.0: [drm] VT-d active for gfx access
i915 0000:00:02.0: vgaarb: deactivate vga console
Console: switching to colour dummy device 80x25
i915 0000:00:02.0: [drm] couldn't get memory information
i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
mei_hdcp 0000:00:0f.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops 0xfafbe240)
i915 0000:00:02.0: Direct firmware load for i915/glk_dmc_ver1_04.bin failed with error -2
i915 0000:00:02.0: Falling back to sysfs fallback for: i915/glk_dmc_ver1_04.bin
cfg80211: failed to load regulatory.db
i915 0000:00:02.0: [drm] Failed to load DMC firmware i915/glk_dmc_ver1_04.bin. Disabling runtime power management.
i915 0000:00:02.0: [drm] DMC firmware homepage: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
[drm] Initialized i915 1.6.0 20200917 for 0000:00:02.0 on minor 0
ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input9
fbcon: i915drmfb (fb0) is primary device
Console: switching to colour frame buffer device 160x64
ee1004 0-0050: 512 byte EE1004-compliant SPD EEPROM, read-only
i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
BUG: unable to handle page fault for address: fad5227b
#PF: supervisor write access in kernel mode
#PF: error_code(0x0003) - permissions violation
*pde = 06d07067 *pte = 70d8e161
Oops: 0003 [#1] SMP
CPU: 3 PID: 256 Comm: kworker/3:2 Not tainted 5.10.3-tinycore #2021
Hardware name: ZOTAC ZBOX-CI329NANO/Default string, BIOS 5.13 12/20/2019
Workqueue: events 0xc048445a
EIP: 0xf9265150
Code: ff ff ff 40 c3 55 89 e5 57 56 89 d6 53 89 c3 83 ec 08 8b 46 04 8b 7a 10 8b 52 14 8d 48 08 89 4d f0 83 f8 3f 0f 86 a7 00 00 00 <c6> 46 37 00 8b 43 1c 83 ff 3f 76 08 57 68 62 84 27 f9 eb
0e 8d 4a
EAX: 00000040 EBX: c1b04010 ECX: 00000048 EDX: 00000006
ESI: fad52244 EDI: 0000000c EBP: c18efe88 ESP: c18efe74
DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 EFLAGS: 00010212
CR0: 80050033 CR2: fad5227b CR3: 07304000 CR4: 00350ed0
Cal l Trace:
0xf9265cdd
? 0xf926512b
0xf925811b
? 0xc0483f6c
? 0xc0483ce5
? 0xc04841f6
0xc0484486
0xc01572e1
0xc01576e8
0xc015ad02
? 0xc0157584
? 0xc015ac30
0xc0100c09
Modules linked in: ee1004 i915 iwlwifi i2c_i801 i2c_smbus drm_kms_helper fb_sys_fops syscopyarea sysfillrect sysimgblt cfg80211 drm intel_gtt agpgart cec squashfs loop ums_realtek hid_a4tech video backlight mei_hdcp sdhci_pci cqhci sdhci mmc_core serio_raw processor_thermal_device intel_soc_dts_iosf int340x_thermal_zone pcspkr xhci_pci xhci_hcd realtek xhci_pci_renesas mei_me pinctrl_geminilake r8169 mei
CR2: 00000000fad5227b
---[ end trace 980303bd47af2e1e ]---
EIP: 0xf9265150
Code: ff ff ff 40 c3 55 89 e5 57 56 89 d6 53 89 c3 83 ec 08 8b 46 04 8b 7a 10 8b 52 14 8d 48 08 89 4d f0 83 f8 3f 0f 86 a7 00 00 00 <c6> 46 37 00 8b 43 1c 83 ff 3f 76 08 57 68 62 84 27 f9 eb 0e 8d 4a
EAX: 00000040 EBX: c1b04010 ECX: 00000048 EDX: 00000006
ESI: fad52244 EDI: 0000000c EBP: c18efe88 ESP: c18efe74
DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 EFLAGS: 00010212
CR0: 80050033 CR2: fad5227b CR3: 07304000 CR4: 00350ed0
r8169 0000:02:00.0: Direct firmware load for rtl_nic/rtl8168g-2.fw failed with error -2
r8169 0000:02:00.0: Falling back to sysfs fallback for: rtl_nic/rtl8168g-2.fw
Generic FE-GE Realtek PHY r8169-200:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-200:00, irq=IGNORE)
r8169 0000:02:00.0 eth1: Link is Down
or waiting for 13.x.
is there already a release date ?
your easiest options are using 10.x or waiting
What would be my hardest options to get the driver to work?
-
is there already a release date ?
In a day or two
-
What would be my hardest options to get the driver to work?
Build a debug kernel to see which module and line caused the bug, then see if there exists a patch. If one exists, apply it to the version you want to use.
-
What would be my hardest options to get the driver to work?
Build a debug kernel to see which module and line caused the bug, then see if there exists a patch. If one exists, apply it to the version you want to use.
Hi Curaga,
ok i am not that pro yet, i would prefer to wait for the new Kernel 13x :-X ;D
-
is there already a release date ?
In a day or two
how to get notified once TC13 is released for users ?
-
Hi Rabie
The Tiny Core 13.0 Alpha 1 version is available if you want to test it out:
http://forum.tinycorelinux.net/index.php/topic,25422.0.html
-
Hi Rabie
The Tiny Core 13.0 Alpha 1 version is available if you want to test it out:
http://forum.tinycorelinux.net/index.php/topic,25422.0.html
Hi Rich,
is there an instruction how to install it ?
-
Hi Rabie
I think the simplest way for testing would be to:
1. Get a blank USB thumb drive.
2. Do an install use a TC12 ISO.
3. Replace the vmlinuz64 with the one found here:
http://repo.tinycorelinux.net/13.x/x86_64/release_candidates/distribution_files/
4. Using files from above link, replace corepure64.gz with a replacement made like this:
cat rootfs64.gz modules64.gz > corepure64.gz5. Boot the thumb drive.
6. Update the extensions:
tce-audit builddb
tce-audit updatedeps
tce-audit fetchmissing
tce-update7. Reboot.
-
thank you
-
Hi Rabie
You are welcome.