LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 09-01-2022, 01:58 AM   #16
shipujin
Member
 
Registered: May 2022
Location: China
Distribution: slackwareloong
Posts: 87

Original Poster
Blog Entries: 1

Rep: Reputation: 15

Quote:
Originally Posted by guanx View Post
Doesn't matter. Just check that it's consistent everywhere, e.g., also for qemu, gcc and etc.
And I will follow the triple settings of gcc/qemu and etc in the upstream community (loongarch64-vendor-kernel-os),
Will not damage the ecological separation

Therefore, choosing ARCH=“loong64”will not damage the ecological separation

My plan is to make the name "ARCH = loong64" in .SlackBuild more beautiful and can be liked by everyone.



Cheers~

Last edited by shipujin; 09-01-2022 at 02:01 AM.
 
Old 09-03-2022, 03:10 AM   #17
shipujin
Member
 
Registered: May 2022
Location: China
Distribution: slackwareloong
Posts: 87

Original Poster
Blog Entries: 1

Rep: Reputation: 15
Hi everyone,

It seems that the discussion has been quiet for a while, so we choose ARCH=loong64 instead of ARCH=loongarch64?

If this does not cause too many objections, I will be ready to start building Slackware loong64 (ARCH=loong64)

There will be LoongArch Slackware base system coming soon, I will share the building process here


Cheers~

Last edited by shipujin; 09-03-2022 at 04:18 AM.
 
Old 09-07-2022, 12:35 AM   #18
lucabon
Member
 
Registered: Oct 2021
Location: Italy
Distribution: Slackware
Posts: 97

Rep: Reputation: 74
Quote:
Originally Posted by shipujin View Post
It seems that the discussion has been quiet for a while, so we choose ARCH=loong64 instead of ARCH=loongarch64?
GNU toolchain recognize only "loongarch64". If you want to keep Slackware build scripts untouched as much as possible (e.g like BonSlack ones: https://bonslack.org/source-current/ ), it is better to leave the official ARCH=loongarch64

Quote:
Originally Posted by shipujin View Post
There will be LoongArch Slackware base system coming soon, I will share the building process here
I tried to bootstrap LoongArch64 (https://bonslack.org/bootstrap/current/), but maybe there is something wrong with glibc settings and/or qemu, since any "configure" script gives this error:
Code:
./configure: This script requires a shell more modern than all
./configure: the shells that I found on your system.
./configure: Please tell bug-autoconf@gnu.org and
./configure: christos@astron.com about your system, including any
./configure: error possibly output before this message. Then install
./configure: a modern shell, or manually run the script under such a
./configure: shell if you do have one.
You can download pre-build rootfs from here (qemu-loongarch64-static already inside, to use with chroot): https://bonslack.org/bootstrap/curre...garch64.tar.lz
 
Old 09-07-2022, 02:07 AM   #19
shipujin
Member
 
Registered: May 2022
Location: China
Distribution: slackwareloong
Posts: 87

Original Poster
Blog Entries: 1

Rep: Reputation: 15
Quote:
Originally Posted by lucabon View Post
GNU toolchain recognize only "loongarch64". If you want to keep Slackware build scripts untouched as much as possible (e.g like BonSlack ones: https://bonslack.org/source-current/ ), it is better to leave the official ARCH=loongarch64



I tried to bootstrap LoongArch64 (https://bonslack.org/bootstrap/current/), but maybe there is something wrong with glibc settings and/or qemu, since any "configure" script gives this error:
Code:
./configure: This script requires a shell more modern than all
./configure: the shells that I found on your system.
./configure: Please tell bug-autoconf@gnu.org and
./configure: christos@astron.com about your system, including any
./configure: error possibly output before this message. Then install
./configure: a modern shell, or manually run the script under such a
./configure: shell if you do have one.
You can download pre-build rootfs from here (qemu-loongarch64-static already inside, to use with chroot): https://bonslack.org/bootstrap/curre...garch64.tar.lz

Hi,lucabon

I have built ARCH=loongarch64 and finished building XFCE4 desktop graphics.
You can enjoy:
https://bbs.loongarch.org/assets/fil...fbb51abf8a.png

rootfs:
https://github.com/shipujin/slackware-loongarch64/

Since I finished building ARCH= "loongarch64" without communicating with Slackware enthusiasts, I recently prepared to rebuild

Above I am the ARCH= "loong64" choice I discussed with you,
I have now built StagE1: Cross-Tools
stage2: tools

I look forward to discussing it with you
 
Old 09-07-2022, 02:18 AM   #20
shipujin
Member
 
Registered: May 2022
Location: China
Distribution: slackwareloong
Posts: 87

Original Poster
Blog Entries: 1

Rep: Reputation: 15
Quote:
Originally Posted by lucabon View Post
GNU toolchain recognize only "loongarch64". If you want to keep Slackware build scripts untouched as much as possible (e.g like BonSlack ones: https://bonslack.org/source-current/ ), it is better to leave the official ARCH=loongarch64



I tried to bootstrap LoongArch64 (https://bonslack.org/bootstrap/current/), but maybe there is something wrong with glibc settings and/or qemu, since any "configure" script gives this error:
Code:
./configure: This script requires a shell more modern than all
./configure: the shells that I found on your system.
./configure: Please tell bug-autoconf@gnu.org and
./configure: christos@astron.com about your system, including any
./configure: error possibly output before this message. Then install
./configure: a modern shell, or manually run the script under such a
./configure: shell if you do have one.
You can download pre-build rootfs from here (qemu-loongarch64-static already inside, to use with chroot): https://bonslack.org/bootstrap/curre...garch64.tar.lz
Hi,lucabon

You can refer to the ARCH=loongarch64 I made before in the process of making

Url:https://bbs.loongarch.org/d/95-loong...rent-bootstrap

github:https://github.com/shipujin/slackware-loongarch64/
 
Old 09-07-2022, 07:50 AM   #21
shipujin
Member
 
Registered: May 2022
Location: China
Distribution: slackwareloong
Posts: 87

Original Poster
Blog Entries: 1

Rep: Reputation: 15
slackware-current-bootstrap-loong64

Stage results sharing:

stage1(cross-tools): https://github.com/shipujin/slackwar...0220905.tar.gz

stage2(tools): https://github.com/shipujin/slackwar...0220905.tar.gz

Code:
0 I have no name!:~ # cat /etc/os-release 
NAME=Slackware
VERSION="15.0"
ID=slackware
VERSION_ID=15.0
PRETTY_NAME="Slackware 15.0 loong64 (post 15.0 -current)"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:slackware:slackware_linux:15.0"
HOME_URL="http://slackware.com/"
SUPPORT_URL="http://www.linuxquestions.org/questions/slackware-14/"
BUG_REPORT_URL="http://www.linuxquestions.org/questions/slackware-14/"
VERSION_CODENAME=current
0 I have no name!:~ # gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/tools/libexec/gcc/loongarch64-slackware-linux-gnu/13.0.0/lto-wrapper
Target: loongarch64-slackware-linux-gnu
Configured with: ../configure --prefix=/tools --disable-multilib --build=x86_64-cross-linux-gnu --host=loongarch64-slackware-linux-gnu --target=loongarch64-slackware-linux-gnu --with-local-prefix=/tools --with-native-system-header-dir=/tools/include --enable-install-libiberty --disable-werror --enable-__cxa_atexit --enable-threads=posix --with-system-zlib --enable-libstdcxx-time --enable-checking=release --with-fix-loongson3-llsc --enable-languages=c,c++
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.0.0 20220905 (experimental) (GCC) 
0 I have no name!:~ # 
0 I have no name!:~ # ls /var/lib/pkgtools/packages/
aaa_base-15.1-loong64-2  kernel-headers-6.0.0_rc4-loong64-1
0 I have no name!:~ #
Cheers~

Last edited by shipujin; 09-07-2022 at 07:54 AM.
 
1 members found this post helpful.
Old 09-08-2022, 07:37 AM   #22
lucabon
Member
 
Registered: Oct 2021
Location: Italy
Distribution: Slackware
Posts: 97

Rep: Reputation: 74
Quote:
Originally Posted by shipujin View Post
slackware-current-bootstrap-loong64
stage2(tools): https://github.com/shipujin/slackwar...0220905.tar.gz
Also with your stage2 I got the same problem (shell too old). It is definitively a qemu-loongarch64 (qemu user-space) problem, since with qemu-system-loongarch64 both (your and mine bootstrap) work fine.

Thanks!
Luca
 
Old 10-18-2022, 10:12 AM   #23
lucabon
Member
 
Registered: Oct 2021
Location: Italy
Distribution: Slackware
Posts: 97

Rep: Reputation: 74
Quote:
Originally Posted by lucabon View Post
Also with your stage2 I got the same problem (shell too old). It is definitively a qemu-loongarch64 (qemu user-space) problem, since with qemu-system-loongarch64 both (your and mine bootstrap) work fine.
Fixed qemu-user (missing faccessat2 syscall, the only available on loongarch64):
- Pre-compiled binaries: https://bonslack.org/bootstrap/qemu/...0221018.tar.lz
- Source code: https://bonslack.org/bootstrap/qemu/...0221018.tar.lz
- Patch: https://bonslack.org/bootstrap/qemu/...accessat2.diff
- Configure script: https://bonslack.org/bootstrap/qemu/configure_static.sh
- Static host libraries (glib2, pcre): https://bonslack.org/bootstrap/qemu/...tic-libraries/

Now I can build packages quicker...

Packages actually built for loongarch64 (11% of total): https://bonslack.org/bonslack_loongarch64-current/
 
Old 10-20-2022, 08:00 AM   #24
shipujin
Member
 
Registered: May 2022
Location: China
Distribution: slackwareloong
Posts: 87

Original Poster
Blog Entries: 1

Rep: Reputation: 15
Quote:
Originally Posted by lucabon View Post
Fixed qemu-user (missing faccessat2 syscall, the only available on loongarch64):
- Pre-compiled binaries: https://bonslack.org/bootstrap/qemu/...0221018.tar.lz
- Source code: https://bonslack.org/bootstrap/qemu/...0221018.tar.lz
- Patch: https://bonslack.org/bootstrap/qemu/...accessat2.diff
- Configure script: https://bonslack.org/bootstrap/qemu/configure_static.sh
- Static host libraries (glib2, pcre): https://bonslack.org/bootstrap/qemu/...tic-libraries/

Now I can build packages quicker...

Packages actually built for loongarch64 (11% of total): https://bonslack.org/bonslack_loongarch64-current/

cool~ This is great!

Cheers~
 
Old 10-20-2022, 08:17 AM   #25
shipujin
Member
 
Registered: May 2022
Location: China
Distribution: slackwareloong
Posts: 87

Original Poster
Blog Entries: 1

Rep: Reputation: 15
Hi everyone,

I have finished building slackware current loong64 (stage1, stage2, stage3) and I am compiling the full stage4 system

stage1: https://github.com/shipujin/slackwar...0221012.tar.gz

stage2: https://github.com/shipujin/slackwar...0221012.tar.gz

stage3: https://github.com/shipujin/slackwar...loong64.tar.gz

stage4: ongoing...

Update(slackware-current-bootstrap-2022.10.12-loong64):
* compiler toolchain: supported new relocations types.
* Update e_flags for new relocations.
Code:
0 root:~ # readelf -h /bin/bash | grep Flags
  Flags:    0x43, DOUBLE-FLOAT, OBJ-v1
 
Old 10-20-2022, 08:19 AM   #26
shipujin
Member
 
Registered: May 2022
Location: China
Distribution: slackwareloong
Posts: 87

Original Poster
Blog Entries: 1

Rep: Reputation: 15
Code:
1 root:/ # 
1 root:/ # ls /var/lib/pkgtools/packages/|wc -l
176
0 root:/ # 
0 root:/ # uname -a
Linux Slackware 6.1.0-rc1 #1 SMP PREEMPT Thu Oct 20 03:36:37 UTC 2022 loongarch64 GNU/Linux
0 root:/ # 
0 root:/ # gcc -v
Reading specs from /usr/lib64/gcc/loongarch64-slackware-linux-gnu/13.0.0/specs
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/loongarch64-slackware-linux-gnu/13.0.0/lto-wrapper
Target: loongarch64-slackware-linux-gnu
Configured with: ../configure --prefix=/usr --libdir=/usr/lib64 --mandir=/usr/man --infodir=/usr/info --enable-shared --disable-bootstrap --enable-languages=c,c++,fortra
n,lto,objc,obj-c++ --enable-threads=posix --enable-checking=release --with-system-zlib --enable-libstdcxx-dual-abi --with-default-libstdcxx-abi=new --disable-libstdcxx-p
ch --disable-libunwind-exceptions --enable-__cxa_atexit --disable-libssp --enable-gnu-unique-object --enable-plugin --enable-lto --disable-install-libiberty --disable-we
rror --with-gnu-ld --with-isl --verbose --with-arch-directory=loongarch64 --disable-gtktest --enable-clocale=gnu --target=loongarch64-slackware-linux-gnu --build=loongar
ch64-slackware-linux-gnu --host=loongarch64-slackware-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.0.0 20221012 (experimental) (GCC) 
0 root:/ # 
0 root:/ # neofetch 
                  :::::::                      root@Slackware 
            :::::::::::::::::::                -------------- 
         :::::::::::::::::::::::::             OS: Slackware 15.0 loong64 (post 15.0 -current) loongarch64 
       ::::::::cllcccccllllllll::::::          Host: Loongson Loongson-LS3A5000-7A1000-1w-EVB-V1.21 
    :::::::::lc               dc:::::::        Kernel: 6.1.0-rc1 
   ::::::::cl   clllccllll    oc:::::::::      Uptime: 27 mins 
  :::::::::o   lc::::::::co   oc::::::::::     Packages: 176 (pkgtool) 
 ::::::::::o    cccclc:::::clcc::::::::::::    Shell: bash 5.2.2 
 :::::::::::lc        cclccclc:::::::::::::    Resolution: 1920x1080 
::::::::::::::lcclcc          lc::::::::::::   CPU: yes, iwatch count (4) 
::::::::::cclcc:::::lccclc     oc:::::::::::   Memory: 1558MiB / 16151MiB 
1 root:/ #     l::::::::::l    lc:::::::::::
 :::::cll:o     clcllcccll     o:::::::::::
 :::::occ:o                  clc:::::::::::
  ::::ocl:ccslclccclclccclclc:::::::::::::
   :::oclcccccccccccccllllllllllllll:::::
    ::lcc1lcccccccccccccccccccccccco::::
      ::::::::::::::::::::::::::::::::
        ::::::::::::::::::::::::::::
           ::::::::::::::::::::::
                ::::::::::::
 
1 members found this post helpful.
Old 10-31-2022, 05:03 AM   #27
shipujin
Member
 
Registered: May 2022
Location: China
Distribution: slackwareloong
Posts: 87

Original Poster
Blog Entries: 1

Rep: Reputation: 15
Code:
root@Slackware:~# 
root@Slackware:~# uname -a
Linux Slackware 6.1.0-rc1 #1 SMP PREEMPT Fri Oct 21 09:42:47 UTC 2022 loongarch64 GNU/Linux
root@Slackware:~# 
root@Slackware:~# gcc -v
Reading specs from /usr/lib64/gcc/loongarch64-slackware-linux-gnu/13.0.0/specs
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/loongarch64-slackware-linux-gnu/13.0.0/lto-wrapper
Target: loongarch64-slackware-linux-gnu
Configured with: ../configure --prefix=/usr --libdir=/usr/lib64 --mandir=/usr/man --infodir=/usr/info --enable-shared --disable-bootstrap --enable-languages=c,c++,fortran,lto,objc,obj-c++ --enable-threads=posix --enable-checking=release --with-system-zlib --enable-libstdcxx-dual-abi --with-default-libstdcxx-abi=new --disable-libstdcxx-pch --disable-libunwind-exceptions --enable-__cxa_atexit --disable-libssp --enable-gnu-unique-object --enable-plugin --enable-lto --disable-install-libiberty --disable-werror --with-gnu-ld --with-isl --verbose --with-arch-directory=loongarch64 --disable-gtktest --enable-clocale=gnu --target=loongarch64-slackware-linux-gnu --build=loongarch64-slackware-linux-gnu --host=loongarch64-slackware-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.0.0 20221012 (experimental) (GCC) 
root@Slackware:~# 
root@Slackware:~# neofetch 
                  :::::::                      root@darkstar.example.net 
            :::::::::::::::::::                ------------------------- 
         :::::::::::::::::::::::::             OS: Slackware 15.0 loong64 (post 15.0 -current) loongarch64 
       ::::::::cllcccccllllllll::::::          Host: Loongson Loongson-LS3A5000-7A1000-1w-EVB-V1.21 
    :::::::::lc               dc:::::::        Kernel: 6.1.0-rc1 
   ::::::::cl   clllccllll    oc:::::::::      Uptime: 11 mins 
  :::::::::o   lc::::::::co   oc::::::::::     Packages: 610 (pkgtool) 
 ::::::::::o    cccclc:::::clcc::::::::::::    Shell: bash 5.2.2 
 :::::::::::lc        cclccclc:::::::::::::    Resolution: 1920x1080 
::::::::::::::lcclcc          lc::::::::::::   CPU: yes, iwatch count (4) 
::::::::::cclcc:::::lccclc     oc:::::::::::   Memory: 3181MiB / 16150MiB 
root@Slackware:~# ::::::::l    lc:::::::::::
 :::::cll:o     clcllcccll     o:::::::::::
 :::::occ:o                  clc:::::::::::
  ::::ocl:ccslclccclclccclclc:::::::::::::
   :::oclcccccccccccccllllllllllllll:::::
    ::lcc1lcccccccccccccccccccccccco::::
      ::::::::::::::::::::::::::::::::
        ::::::::::::::::::::::::::::
           ::::::::::::::::::::::
                ::::::::::::
 
Old 11-17-2022, 07:22 AM   #28
shipujin
Member
 
Registered: May 2022
Location: China
Distribution: slackwareloong
Posts: 87

Original Poster
Blog Entries: 1

Rep: Reputation: 15
Quote:
Originally Posted by lucabon View Post
Also with your stage2 I got the same problem (shell too old). It is definitively a qemu-loongarch64 (qemu user-space) problem, since with qemu-system-loongarch64 both (your and mine bootstrap) work fine.

Thanks!
Luca
Hello I made the slockware-current-loong64.iso of the LoongArch platform Difficulties encountered by iso,
When I started iso, it failed to start. Do you have any suggestions? Thank you
Print information:

```
Key type dns_resolver registered
registered taskstats version 1
Loading compiled-in X.509 certificates
zswap: loaded using pool zstd/zbud
Btrfs loaded, crc32c=crc32c-generic, zoned=no, fsverity=no
usb 5-1: new low-speed USB device number 2 using xhci_hcd
ALSA device list:
No soundcards found.
input: SONiX USB Keyboard as /devices/pci0000:00/0000:00:0b.0/0000:02:00.0/usb5/5-1/5-1:1.0/0003:0C45:760B.0001/input/input1
hid-generic 0003:0C45:760B.0001: input,hidraw0: USB HID v1.11 Keyboard [SONiX USB Keyboard] on usb-0000:02:00.0-1/input0
usb 6-3: new SuperSpeed USB device number 2 using xhci_hcd
input: SONiX USB Keyboard Consumer Control as /devices/pci0000:00/0000:00:0b.0/0000:02:00.0/usb5/5-1/5-1:1.1/0003:0C45:760B.0002/input/input2
usb-storage 6-3:1.0: USB Mass Storage device detected
scsi host5: usb-storage 6-3:1.0
ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
ata5.00: ATA-10: GG46T256S3C27, F3C1I1B2, max UDMA/133
input: SONiX USB Keyboard System Control as /devices/pci0000:00/0000:00:0b.0/0000:02:00.0/usb5/5-1/5-1:1.1/0003:0C45:760B.0002/input/input3
ata5.00: 500118192 sectors, multi 1: LBA48 NCQ (depth 32), AA
hid-generic 0003:0C45:760B.0002: input,hidraw1: USB HID v1.11 Device [SONiX USB Keyboard] on usb-0000:02:00.0-1/input1
ata5.00: configured for UDMA/133
scsi 4:0:0:0: Direct-Access ATA GG46T256S3C27 I1B2 PQ: 0 ANSI: 5
sd 4:0:0:0: Attached scsi generic sg1 type 0
sd 4:0:0:0: [sda] 500118192 512-byte logical blocks: (256 GB/238 GiB)
sd 4:0:0:0: [sda] Write Protect is off
sd 4:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 4:0:0:0: [sda] Preferred minimum I/O size 512 bytes
sda: sda1 sda2 sda3 sda4
sd 4:0:0:0: [sda] Attached SCSI disk
/dev/root: Can't open blockdev
VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
usb 6-4: new SuperSpeed USB device number 3 using xhci_hcd
Please append a correct "root=" boot option; here are the available partitions:
0100 8192 ram0
(driver?)
0101 8192 ram1
(driver?)
0102 8192 ram2
(driver?)
0103 8192 ram3
(driver?)
0104 8192 ram4
(driver?)
usb-storage 6-4:1.0: USB Mass Storage device detected
0105 8192 ram5
scsi host6: usb-storage 6-4:1.0
(driver?)
0106 8192 ram6
(driver?)
0107 8192 ram7
(driver?)
0108 8192 ram8
(driver?)
0109 8192 ram9
(driver?)
010a 8192 ram10
(driver?)
010b 8192 ram11
(driver?)
010c 8192 ram12
(driver?)
010d 8192 ram13
(driver?)
010e 8192 ram14
(driver?)
010f 8192 ram15
(driver?)
0b00 1048575 sr0
driver: sr
0800 250059096 sda
driver: sd
0801 512000 sda1 c5cc9b63-15c4-154b-887c-d088581c915a

0802 1048576 sda2 d7f706c6-80d4-7442-a620-5757ebe0d4bc

0803 33554432 sda3 f1c7756c-e1ad-5c4b-9e40-d3284d1e707d

0804 214942720 sda4 0a79017a-ec0a-274a-842a-685bcd06af25

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
CPU: 1 PID: 1 Comm: swapper/0 Not tainted 6.1.0-rc2 #1
Hardware name: Loongson Loongson-3A5000LL-7A1000-1w-A2101/Loongson-LS3A5000-7A1000-1w-A2101, BIOS vUDK2018-LoongArch-V2.0.pre-beta8 06/15/2022
Stack : 0000000000000000 9000000000222be8 90000001000a8000 90000001000abba0
90000001000abba0 0000000000000000 0000000000000000 90000001000abba0
0000000000000040 ffffffffffffffff 0000000000000004 0000000000000002
90000001000abba0 0000000005714000 9000000100134500 00000000ffffdfff
0000000000000000 676e6f6f4c2d3831 2e32562d68637241 65622d6572702e30
0000000000000430 0000000005714000 0000000000000008 0000000000000000
0000000000000000 90000000013bf460 0000000000000000 ffffff000104dd00
90000000010d04b8 9000000104dd0000 0000000000000000 9000000001080098
0000000000000000 9000000000222c00 0000000000000000 00000000000000b0
0000000000000004 0000000000000000 0000000000071c1c 0000000000000800
...
Call Trace:
[<9000000000222c00>] show_stack+0x4c/0x15c
[<9000000001054664>] dump_stack_lvl+0x60/0x88
[<900000000103c2d0>] panic+0x134/0x2fc
[<90000000010814f0>] mount_block_root+0x1e8/0x27c
[<900000000108195c>] prepare_namespace+0x130/0x16c
[<9000000001080f8c>] kernel_init_freeable+0x260/0x294
[<9000000001056220>] kernel_init+0x20/0x110
[<9000000000221550>] ret_from_kernel_thread+0xc/0x9c

---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---
```
 
Old 11-22-2022, 06:46 AM   #29
shipujin
Member
 
Registered: May 2022
Location: China
Distribution: slackwareloong
Posts: 87

Original Poster
Blog Entries: 1

Rep: Reputation: 15
Release the slackware mini install iso: [slackware64-current-loong64-20221122-mini-install.iso](http://pkg.iloongarch.cn/slackwarelo...ni-install.iso)
 
Old 11-28-2022, 12:10 AM   #30
shipujin
Member
 
Registered: May 2022
Location: China
Distribution: slackwareloong
Posts: 87

Original Poster
Blog Entries: 1

Rep: Reputation: 15
Release the slackware mini install iso: [slackware64-current-loong64-20221122-mini-install.iso](https://github.com/shipujin/slackwar...ni-install.iso)
 
  


Reply

Tags
port, slackware, slackware -current


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Porting and tuning applications for Linux on Power, Part 2: 15 Porting and tuning tools for Linux on Power LXer Syndicated Linux News 0 05-18-2018 02:05 PM
In linux boot process what is the role of stage1, stage1.5's file and stage 2 maheshp86 Linux - Hardware 7 07-13-2012 09:47 AM
Gentoo Stage1 install problems... GryphonTech Linux - Distributions 7 09-14-2003 05:40 AM
GENTOO 1.4; Stage1 Installation: Installation freezes arthur1968 Linux - Hardware 1 08-28-2003 12:08 PM
Fatal Error in Stage1 I/O error xtec2 Linux - Newbie 10 07-16-2003 05:09 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 07:08 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration