-
Search Results
-
In reply to: antiX will not set the native monitor resolution
ant_222
So—I have installed antix-22-runit_x64-base.iso—the exact version I want, with defaluts. Immediagtely after the new system booted, and fired up the terminal and typed entered the command for the installation of prerequisites:
curl 'https://liquorix.net/add-liquorix-repo.sh' | sudo bash
which this time went without errors and printed:
[INFO ] Liquorix kernel intalled successfully
which surprised me as I was intalling only the prerequisites and not the kernel itself. On second thought, I suggested that the script above had indeed installed the entire kernel with Debian prerequisites, and rebooted. This proved correct, as the GRUB menu now showed an additional option for: 6.0.0-12.1-liquorix-amd64, and uname -r after boot confirmed this.The new kernel, however, did not resolved my problem, and my display is still unrecognised by X and named default, with 1024×768 remaining the only available resolution. Yet the graphical driver seems loaded correctly:
$ inxi -G Graphics: Device-1: Intel JasperLake [UHD Graphics] driver: i915 v: kernel Display: server: X.Org v: 1.20.11 driver: X: loaded: fbdev gpu: i915 resolution: 1024x768 OpenGL: renderer: llvmpipe (LLVM 11.0.1 128 bits) v: 4.5 Mesa 20.3.5I then added the i915 driver to the GRUB config file as per DaveW:
GRUB_CMDLINE_LINUX_DEFAULT="quiet insmod i915 i915.modeset=1 selinux=0"
and, although Dave did not indicate it, ran
sudo update-grub.
After reboot, the resolution was the same. Here are my dmesg and Xort.0.log. Observe in the former the same errors as I had with other non-antiX kernels:[ 0.000000] x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks [ 0.021360] Unknown kernel command line parameters "insmod i915 BOOT_IMAGE=/boot/vmlinuz-6.0.0-12.1-liquorix-amd64", will be passed to user space.Observe in the latter lots of invalid argument errors and the following:
[ 4.346] (==) Using config file: "/etc/X11/xorg.conf" [ 4.347] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 4.347] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 4.348] (==) No Layout section. Using the first Screen section. [ 4.348] (==) No screen section available. Using defaults. [ 4.348] (**) |-->Screen "Default Screen Section" (0) [ 4.348] (**) | |-->Monitor "<default monitor>" [ 4.348] (==) No device specified for screen "Default Screen Section". Using the first device section listed. [ 4.348] (**) | |-->Device "Device0" [ 4.348] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. ................. [ 4.379] (II) FBDEV(0): hardware: i915drmfb (video memory: 9216kB) [ 4.379] (II) FBDEV(0): checking modes against framebuffer device... [ 4.379] (II) FBDEV(0): checking modes against monitor... [ 4.379] (II) FBDEV(0): Virtual size is 1024x768 (pitch 1024)I have not installed Debian Dog yet, but will do so as time permits. Thanks again for your help.
In reply to: antiX will not set the native monitor resolution
Brian Masinick
Brian,
I have already made special provisions for installing two OSes side-by-side. I have a separate ESP partition, two 48 Gb OS partitions, and a data partition to store whatever should should OS (re)intallations. If Debian Dog does not destroy my boot configuration but accurately adds itself to the GRUB menu, all should be well.Excellent! Step one to “comparison” learning; this will eventually lead to being able to get ideas from other systems, and sometimes it will allow physically copying files, programs, and data – when they are compatible across the systems – they should be compatible in the antiX – Debian Sid scenario since we’re considering the definition and configuration of peripheral devices.
--
Brian Masinickimpassable-highchair93
How about spitting out a inxi report after install is done so any mac user can see what the hardware is using with your cheat codes.
On my live antiX USB, I ran:
inxi -zv7 -rand got
System: Kernel: 4.9.0-326-antix.1-amd64-smp arch: x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: IceWM v: 3.0.1 dm: slimski v: 1.5.0 Distro: antiX-22_x64-full Grup Yorum 18 October 2022 base: Debian GNU/Linux 11 (bullseye) Machine: Type: Desktop System: Apple product: iMac5,1 v: 1.0 serial: <superuser required> Chassis: type: 13 v: Mac-F4228EC8 serial: <superuser required> Mobo: Apple model: Mac-F4228EC8 v: DVT serial: <superuser required> UEFI: Apple v: IM51.88Z.0090.B09.0706270921 date: 06/27/07 Battery: Message: No system battery data found. Is one present? Memory: RAM: total: 991.4 MiB used: 646 MiB (65.2%) RAM Report: permissions: Unable to run dmidecode. Root privileges required. CPU: Info: dual core model: Intel Core2 T7400 bits: 64 type: MCP smt: <unsupported> arch: Core2 Merom rev: 6 cache: L1: 128 KiB L2: 4 MiB Speed (MHz): avg: 1583 high: 2167 min/max: 1000/2167 cores: 1: 1000 2: 2167 bogomips: 8655 Flags: acpi aperfmperf apic arch_perfmon bts clflush cmov constant_tsc cx16 cx8 de ds_cpl dtes64 dtherm dts est fpu fxsr ht kaiser lahf_lm lm mca mce mmx monitor msr mtrr nopl nx pae pat pbe pdcm pebs pge pni pse pse36 sep ss sse sse2 ssse3 syscall tm tm2 tpr_shadow tsc vme vmx xtpr Graphics: Device-1: AMD RV530/M56-P [Mobility Radeon X1600] vendor: Apple MacBook Pro driver: N/A arch: Rage 7 bus-ID: 01:00.0 chip-ID: 1002:71c5 class-ID: 0300 Display: server: X.Org v: 1.20.11 driver: X: loaded: N/A unloaded: fbdev gpu: N/A display-ID: :0.0 screens: 1 Screen-1: 0 s-res: 1680x1050 s-dpi: 96 s-size: 445x278mm (17.52x10.94") s-diag: 525mm (20.66") Monitor-1: default res: 1680x1050 size: N/A modes: N/A OpenGL: renderer: llvmpipe (LLVM 11.0.1 128 bits) v: 4.5 Mesa 20.3.5 compat-v: 3.1 direct render: Yes Audio: Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: SigmaTel STAC9221 Codec driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:27d8 class-ID: 0403 Sound Server-1: ALSA v: k4.9.0-326-antix.1-amd64-smp running: yes Network: Device-1: Marvell 88E8053 PCI-E Gigabit Ethernet driver: sky2 v: 1.30 port: 1000 bus-ID: 02:00.0 chip-ID: 11ab:4362 class-ID: 0200 IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> IP v4: <filter> scope: global broadcast: <filter> IP v6: <filter> type: dynamic mngtmpaddr scope: global IP v6: <filter> scope: link Device-2: Broadcom BCM4321 802.11a/b/g/n vendor: Apple AirPort Extreme driver: b43-pci-bridge v: N/A bus-ID: 03:00.0 chip-ID: 14e4:4328 class-ID: 0280 IF-ID-1: wlan0 state: down mac: <filter> WAN IP: <filter> Bluetooth: Device-1: Apple Bluetooth HCI type: USB driver: btusb v: 0.8 bus-ID: 5-1:4 chip-ID: 05ac:8206 class-ID: fe01 Report: hciconfig ID: hci0 rfk-id: 1 state: down bt-service: stopped rfk-block: hardware: no software: yes address: <filter> Logical: Message: No logical block device data found. RAID: Message: No RAID data found. Drives: Local Storage: total: 290.64 GiB used: 0 KiB (0.0%) ID-1: /dev/sda vendor: Western Digital model: WD2500JS-40TGB0 size: 232.89 GiB speed: 1.5 Gb/s type: N/A serial: <filter> rev: 6C04 scheme: GPT ID-2: /dev/sdb type: USB vendor: Kingston model: DT Elite G2 size: 57.75 GiB type: N/A serial: <filter> rev: PMAP scheme: MBR Optical-1: /dev/sr0 vendor: MATSHITA model: DVD-R UJ-85J rev: FCQ5 dev-links: cdrom,cdrw,dvd,dvdrw Features: speed: 24 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r state: running Partition: Message: No partition data found. Swap: Alert: No swap data was found. Unmounted: ID-1: /dev/sda1 size: 157.69 GiB fs: ext4 label: N/A uuid: 8c9302b7-fe4b-46d1-9c86-5b7721f25946 ID-2: /dev/sda2 size: 48.83 GiB fs: ext4 label: N/A uuid: bdd0b6cf-b7c5-4241-83c3-11c3af047293 ID-3: /dev/sda3 size: 3.9 GiB fs: swap label: N/A uuid: bd23167b-b056-407b-bfdd-a317533f5a2e ID-4: /dev/sda4 size: 5 MiB fs: exfat label: N/A uuid: 7B9B-F86D ID-5: /dev/sdb1 size: 1.4 GiB fs: iso9660 ID-6: /dev/sdb2 size: 4.1 MiB fs: vfat label: EFI-LIVE uuid: 7249-CF0E USB: Hub-1: 1-0:1 info: Full speed or root hub ports: 8 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 Device-1: 1-1:2 info: Kingston DataTraveler Elite G2 type: Mass Storage driver: usb-storage interfaces: 1 rev: 2.1 speed: 480 Mb/s power: 300mA chip-ID: 0951:16d5 class-ID: 0806 serial: <filter> Device-2: 1-4:4 info: Apple Built-in iSight (no firmware loaded) type: <vendor specific> driver: N/A interfaces: 1 rev: 2.0 speed: 480 Mb/s power: 100mA chip-ID: 05ac:8300 class-ID: ff00 Hub-2: 2-0:1 info: Full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001 class-ID: 0900 Hub-3: 3-0:1 info: Full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001 class-ID: 0900 Device-1: 3-1:2 info: Apple Aluminium Keyboard (ANSI) type: Keyboard,HID driver: apple,usbhid interfaces: 2 rev: 1.1 speed: 1.5 Mb/s power: 20mA chip-ID: 05ac:024f class-ID: 0300 Hub-4: 4-0:1 info: Full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001 class-ID: 0900 Device-1: 4-1:2 info: Logitech Cordless Mouse Receiver type: Mouse,HID driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 98mA chip-ID: 046d:c537 class-ID: 0300 Hub-5: 5-0:1 info: Full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001 class-ID: 0900 Device-1: 5-1:4 info: Apple Bluetooth HCI type: Bluetooth driver: btusb interfaces: 3 rev: 2.0 speed: 12 Mb/s chip-ID: 05ac:8206 class-ID: fe01 Device-2: 5-2:3 info: Apple Built-in IR Receiver type: HID driver: appleir,usbhid interfaces: 1 rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 05ac:8240 class-ID: 0300 Sensors: System Temperatures: cpu: 50.0 C mobo: N/A Fan Speeds (RPM): cpu: 905 Repos: Packages: apt: 1571 Active apt repos in: /etc/apt/sources.list.d/antix.list 1: deb http://la.mxrepo.com/antix/bullseye bullseye main nosystemd nonfree Active apt repos in: /etc/apt/sources.list.d/bullseye-backports.list 1: deb http://deb.debian.org/debian bullseye-backports main contrib non-free Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 1: deb http://ftp.us.debian.org/debian/ bullseye-updates main contrib non-free Active apt repos in: /etc/apt/sources.list.d/debian.list 1: deb http://ftp.de.debian.org/debian/ bullseye main contrib non-free 2: deb http://security.debian.org/ bullseye-security main contrib non-free No active apt repos in: /etc/apt/sources.list.d/various.list Info: Processes: 146 Uptime: 1h 49m wakeups: 1 Init: SysVinit v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: Bash v: 5.1.4 running-in: roxterm inxi: 3.3.19Unfortunately, I am having new troubles actually installing antiX to this hard drive… After fiddling with the partition table a bit, I did get the GUI installer to complete successfully (I did get some warnings about the hard drive…). But on reboot after install, I’m kicked in to a CLI (no GUI desktop).
I edited to GRUB parameters to match my live USB stick parameters I used (“nosplash failsafe disable=lxF”), but no change.I consider 1 Gb of RAM as the bare mininum to use the modern web in antiX- you’ll have to be very careful with RAM usage
Yeah, despite all this work, this machine is very slow — almost unusable. I’m considering using ShredOS to just shred it and landfill it, especially if I can’t get antiX actually installed on the hard drive… But this was a fun project. And if this thread can help others rescue their old Mac(s), all the better!
- This reply was modified 4 months, 4 weeks ago by impassable-highchair93.
- This reply was modified 4 months, 4 weeks ago by impassable-highchair93.
In reply to: antiX will not set the native monitor resolution
BobC
Lastly, if you have problems burning the USB, use the advanced panel to turn off automount.
Tell us exactly what iso you are booting from and what kernel and what additional boot parameters you give it.
In reply to: antiX will not set the native monitor resolution
1. Use Live-USB-Maker from the antiX you have and take all default settings to burn the iso to the USB. Reboot from that with the settings I gave for the kernel you will be booting with and try it to see if it fixes the video resolution.
2. If video is fixed, next get internet working. If problems, sudo dmesg and use grep to search for firmware. Maybe something newer is needed.
3. If video not fixed get internet working and try updating the USB to boot with stable liquorix kernel and use my settings to boot from that.
In reply to: antiX will not set the native monitor resolution
Now that I have purged Windows, I no longer can use Rufus to produce bootable USB sticks, so I used antiX Live USB maker in dd mode. No, I do not need USB persistence at all. You are absolutely right, BobC, in that troubles ought to be shot one a at a time (and preferably in the head rather than in the foot), but I did not intend to change my installation procedure and was surprised that the list of available services in the installer suddenly became empty: no cron, no dbus, no connman. All right, Brian—I will install tonight whatever the defaults are except selecting the desired partitions, and then try again to install the Liquorix kernel.
As to your trick of specifying the driver in GRUB, DaveW, it looks but a crutchy, temporary solution to me. randr still identifies your display as default, which means it fails properly to register it. Since Debian Dog Sid with kernel 6.0.0-2-amd64 works on my PC well, with your help we should be able to track down the exact component that needs to be upgraded, migrated, or reconfigured. If it helps, you can improve your own setup, too.
- This reply was modified 5 months ago by ant_222.
- This reply was modified 5 months ago by ant_222.
So. After selecting kernel. No f key selection on grub screen shows up like on his video?
Yes, that’s correct. See attached photo.
Makes me wonder if iso downloaded is corrupted. Md5sum check of downloaded iso done?
I wish it was an iso download issue, but I did check the md5sum and sha sum and they matched what was on SourceForge (and even used this exact USB stick successfully install antiX 22 on a different Mac (a 2008 laptop) today, which was awesome and went smoothly).
As per that post, I tried adding “xdrvr=vesa” as a GRUB parameter (i.e. right after “nosplash”). I hit F10, but in the series of text on screen, one said that “xdrvr=vesa” was an unrecognized/ignore parameter. And then it hung on “Waiting for /dev to be fully populated”, as usual.
I’d love to try running:
CMDLINE=xdrvr=vesa /usr/sbin/buildxconfig cat xorg.conf sudo cp xorg.conf /etc/X11But I can’t figure out how to get to a command line AND have the changes I make actually take effect in the boot process (“sudo grub-update” throws an error, as described above). Any ideas there?
Thank you so much for these replies.
Attachments:
Hi antiXforum!
I’m trying to try out antiX on a ~2011 iMac 5,1 desktop. It has 1 GB of RAM and a Intel Core 2 Duo (64 bit) processor.
I know this “Waiting for /dev to be fully populated” issue has been discussed before. I think I’m having the same symptom but the same solutions don’t seem to help in my case.
STEPS I’VE TAKEN:
1. Download antiX-22_x64-full.iso from SourceForge, and verify md5 and sah256 sums (they checked out exactly).
2. Flash ISO to a 64-GB USB drive (using Pop_OSs USB Flasher)
3. Reboot the 2007 iMac, holding down the Alt/Option key on boot. Click the EFI boot option
4. The UEFI antiX boot screen loads just fine. Going with the default boot options takes me to a black (but lit) screen.
5. Keying ‘e’ and editing GRUB settings to “nosplash” and removing “quiet” and hitting F10 shows me a flurry of text before hanging on “Waiting for /dev to be fully populated”. (I wish I could get more info here, to see what’s causing the hang…)
6. Next, I tried to get to a command line in order to poke around. Adding “nomodeset nosplash” to the GRUB options gets me to a command line where I’m instructed to log in as root with password root.Now, from this command line, I can access a cli installer, BUT I was really hoping to try antiX on this machine before making a partition and installing it. So, with that in mind, I tried a few things like
1. adding “intel_iommu=igfx_off” to GRUB options -> hangs at “Waiting for /dev to be fully populated”
2. Adding “video=SVIDEO-1:d” to GRUB options -> hangs at “Waiting for /dev to be fully populated”Next, based on someone else’s post, I went be to that command line I got to in step 6 and ran “rm /usr/lib/udev/hid2hci”. I then tried to run “sudo update-grub” — on the assumption that this “rm” change would not survive a reboot — but I got an error: “error: failed to get canonical path of overlay”. Googling this error, most advice had to do with re-installing GRUB, which seemed strange (not to mention difficult and easy to mess up), so I didn’t try that (yet).
Following other advice from this forum/the internet, I’ll provide a few commands and thier outputs when I’m on the command line from step 6 below:
“xrandr” => “Can’t open display”
“inxi -Gxxx” =>
Graphics: Device-1 AMD RV530/M56-P [Mobility Radeon X1600] vendor Apple MacBook Pro driver: N/A arch: Rage 7 bus-ID 01:00.0 chip-ID 1002:71c5 classiID: 0300 Display: server: X.org v: 1.20.11 driver: X: loaded: vesa unloaded: fbdev,modesetting,radeon gpu: N/A tty: 113x34 Message: GL data unavailable in console for rootlspci –nk | grep -i -EA3 “3D|display|vga” =>
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] RV530/M56-P [Mobility Radeon X1600] [1002:715c] Subsystem: Apple Inc. MacBook Pro [106b:0080] Kernel modules: radeon 02:00 Ethernet controller [0200]: Marvell Technology Group Ltd. 88E8053 PCI-E Gigabit Ethernet Controller [11ab:4363] (rev 22)I hope this is an acceptable forum post. The thing that really gives me hope for antiX is that, for fun, I try MX Linux (“MX-21.2.1_fluxbox_x64.iso”) on this same machine first. By simply adding “nomodeset” to the GRUB options, it loaded right up! As expected, MX Linux ate up the 1 GB of RAM and very quickly become un-usably slow, so I didn’t install it, but it did give me lots of hope that there is some simple tweak to be made to my antiX process to get it working too!
- This topic was modified 5 months ago by impassable-highchair93. Reason: formatting
- This topic was modified 5 months ago by impassable-highchair93. Reason: formatting take 3
- This topic was modified 5 months ago by BobC.
In reply to: Pipewire without systemd
stevesr0
Hi Brian (The Mas),
I will definitely switch to using “The Mas” <g>.
Looked up remastering. It is only available when running a live system, not one installed to the hard drive. On my live USB, I don’t remember setting up persistence of any sort. I think that means that nothing changes between boots.
But even within a booted session, it didn’t look as if my deletions were sticking.
I saw that a general remastering doesn’t include stuff in the home directory. Not sure if all the login and other application related personal stuff NOT accessed thru the browser is all there (grub, other sites…)
I will play with this and figure out how to obtain an “iso” without personal files (an empty /home/stevesr0) and how to get rid of the personal stuff in my browser and other application profiles.
Any (helpful <g>) advice welcomed.
stevesr0
In reply to: Pipewire without systemd
Thank you Brian M. (I don’t know your preference in the use of your name – as there might be other “Brian” members, I figured that your last initial might be more specific; happy to change to what you like.)
I have produced a live usb that is an apparent clone of my Fujitsu antiX Sid install. I have tried running it on all three of my computers. It booted immediately to a terminal login (as it is supposed to) on all three computers. On the Fujitsu and Lenovo Yoga, I had no trouble starting Xorg using startx. The first time I tried launching on my newest computer, which has both an integrated intel GPU and an Nvidia GPU, it ended with a connection refused error.
On my second boot, it went as smoothly as with the other two computers.
So superficially, this might work on a variety of computers!
Parenthetically, since this liveusb DOES have libelogind0 installed, Pipewire works. This was the first time I looked at the “new” computer’s audio settings in Pipewire and they DID reflect the hardware on that machine, which is different from the Fujitsu. A little wow moment. (I will include libelogind0 so people can see if Pipewire works with this iso, assuming the iso boots ok to X for them. They can then try removing libelogind0 and see if they can find a way to run Pipewire without it.)
My plan (pending comments from y’alls) is to strip off the files from my home directory and other personal stuff and generate a snapshot from THAT running system and use live-usb-maker to produce an iso I can post somewhere. A family member is being discharged from the hospital soon and I will be visiting and trying to help out, so there may be a delay.
stevesr0
————————————————————————————-
**As an aside, I have noticed a number of posts by folks seeking to use Pipewire. I think it would be neat to “build” a team to (as Brian suggested) look at the Pipewire source code in order to understand where the various problems might be in trying to use it in antiX. Some issues I have heard of include setting a runtime directory as an environment variable (in the absence of systemd), dependencies declared in the source code that require systemd, and issues with the programs used for seat management when running Xorg (including lack of support for Wireplumber?). If several people were interested in looking into these and educating each other, a successful general approach to Pipewire without systemd on antiX might be developed for the benefit of all who might want to try Pipewire. Especially if a newer version could be backported to stable. And of course, the directions would have to include how not to update to incompatible versions <g>.stevesr0
In reply to: Pipewire without systemd
Brian Masinick
Hi Brian M.,
On my minimalistic system running Openbox, I have iso-snapshot-cli-antix installed and finally found how to launch it (/usr/bin/iso-snapshot-cli). It has completed and deposited an iso in my /home/snapshot directory.
I see it says now run live-usb-maker in order to generate a bootable live usb. I will do that to test the transferability of this iso to my other machines and to enable me to generate a version without any personal data <g>, which I will seek to post somewhere people can download it to try on their machines.
(But not tonight…)
Note Bene:
Sometime ago, anticapitalista posted a nice guide to building a simple system on the forum.
stevesr0
P.S. to olsztyn – I don’t believe I am ahead of you in anything computer related <g>.
I say to both of you that you know enough to do some interesting things, and the more you experiment with the “interesting things”, the more you learn.
Keep at it; I am favorably impressed with everything each of you do!--
Brian MasinickIn reply to: Pipewire without systemd
Hi Brian M.,
On my minimalistic system running Openbox, I have iso-snapshot-cli-antix installed and finally found how to launch it (/usr/bin/iso-snapshot-cli). It has completed and deposited an iso in my /home/snapshot directory.
I see it says now run live-usb-maker in order to generate a bootable live usb. I will do that to test the transferability of this iso to my other machines and to enable me to generate a version without any personal data <g>, which I will seek to post somewhere people can download it to try on their machines.
(But not tonight…)
Note Bene:
Sometime ago, anticapitalista posted a nice guide to building a simple system on the forum.
stevesr0
P.S. to olsztyn – I don’t believe I am ahead of you in anything computer related <g>.
In reply to: Updated antiX-sid iso files available
olsztyn
IMO trying to have some sort of base with X environment antiX-sid is doomed to fail (which is why I have not made available any iso files with a graphical environment).
antiX has built a systemd/elogind-free xserver-xorg version so that needs to be working before anything else (graphically speaking).Thank you for confirming. I spent lots of time the past two days trying (unsuccessfully) to build a SID antiX with IceWM from SID Core ISO. Regardless whether upgrades were done before or after Xorg and the entire kaboodle of graphical environment installation the resulting SID antiX was not booting to IceWM. The same as before…
Not ready yet to give up on such challenge I decided on a different approach, which seems to be finally working. The process to arrive to SID antiX Base I used was the following:
– Started from antiX 22 Runit Base ISO, instead of SID Core ISO.
– Ran update and all upgrades with apt dist-upgrade.
– Installed Synaptic. This allowed to better see and control upgrading steps to SID going forward.
– Replaced kernel from 4.9 to 5.10.142 for the time being, but will also include kernel 6.0.
– Changed repositories to SID/Debian Unstable in preparation to move to SID world.From experience, an indiscriminate upgrade to SID across the board leads to the same failure as before. The upgrade to SID must be done manually and selectively, being sensitive to antiX architecture.
Manual process. I may be missing a few details but the idea is the same and can be repeated by anyone:
– Upgrade all antiX specific files to their new antiX SID versions, so those appended with ‘Nosystemd’ or ‘antix’.
– Upgrade those packages that are antiX specific in SID but not yet in antiX 22 Base.
– Do not upgrade yet those files that are antiX specific as above in antiX 22 Stable but their SID version is not yet antiX specific.
– Gradually select for upgrade the remaining packages (not antiX specific) that have new versions in SID. This I have done in steps, after each step verifying the new system is still working fine.
In principle:
The objective is to create an antiX SID Base that would be antiX specific after all, so:
– Do not upgrade packages that replace systemd/elogind-free versions with their systemd Debian versions
– Do not upgrade packages that in turn remove Runit init files or remove seatd.
– Do not install packages that in their turn install elogind or libelogind0.Is there any problem with this approach to create a SID antiX base, that I am missing?
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersIn reply to: Updated antiX-sid iso files available
This is about what I was just about to do. I was planning to set up Xorg and IceWM on the ISO base as published by anticapitalista, not yet running any upgrade of packages across the board. Just using anticapitalista’s Core ISO and installing Xorg + IceWM. This way I would try to establish if the Core ISO as published by anticapitalista is working with Xorg and boots to IceWM, in other words it is good.
My attempt failed to prove (check) that the SID ISO provided by anticapitalista is good.
The outcome is the same. It does not 100% prove that the SIS ISO is bad either (as Xorg and a few other packaged still come from the Debian Unstable) but I think it greatly increases such probability.
I hope I am still overlooking something in the process and BobC will still be able to succeed though…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersIn reply to: Updated antiX-sid iso files available
Would it be wiser to get a simple Xorg working next, then add the rest of the base packages?
This is about what I was just about to do. I was planning to set up Xorg and IceWM on the ISO base as published by anticapitalista, not yet running any upgrade of packages across the board. Just using anticapitalista’s Core ISO and installing Xorg + IceWM. This way I would try to establish if the Core ISO as published by anticapitalista is working with Xorg and boots to IceWM, in other words it is good.
Unfortunately just when I was trying to install Xorg and other files as outlined by @Christophe earlier, it looks like Debian Unstable InRelease is not valid for another 4 hours, so I need to wait with this…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters
Forum for users of antiX Linux. Mean and Lean and Proudly anti-fascist.
