-
Search Results
-
Topic: iso on cd
Who still uses a cd (not dvd) to write/boot/install antiX?
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Hi all,
I have a newish computer with two GPUs: an integrated Intel one (UHD630) and a discreet Nvidia card (GTX1050). Last year, several different iso’s ran fine in VirtualBox on this computer.
In my current tests I am using a live usb with Antix 19 full iso. This boots ONLY to a command line, although boot messages indicate that the boot is running at level 5.
On another computer with just one graphics card, the same usb boots to a graphical screen in a “normal” fashion.
I suspect the problem is caused by this computer having two GPUs, but I haven’t seen any reports of this or how to tell the boot which GPU to ignore. I have tried adding “nomodeset i915.modeset=1” before the splash term with no apparent effect.
Appreciate advice and suggestions.
Thanks.
stevesr0
- This topic was modified 2 years, 11 months ago by stevesr0. Reason: typo nomodeset for modeset
- This topic was modified 2 years, 11 months ago by stevesr0.
Hi, I took a quick look here in the forum, but found nothing that helped me:
1- I’m on a new(er) desktop pc that, after installing antix 19 (now fully updated), got an internal dvd-rom plugged in.
2- Problem: if I put a disk in the drive, spacefm (my default file manager) correctly show’s it’s name, somthing like “sr0 … [name_of_cd-rom]” but when I try to mount it I get this error:Mount /dev/sr0 Finished with error ( exit status 32 ) udevil: /dev/sr0 is known to mount - running mount as current user udevil: warning 45: options ignored for device in fstab (or specify mount point) mount: /media/sr0: mount point does not exist.3- The same thing happens if I put in an audio CD, but VLC plays it just fine!
4- My Fstab:
# Pluggable devices are handled by uDev, they are not in fstab UUID=4d92d6e1-f69a-4f17-8668-51f82ad2d1e6 / ext4 defaults,noatime 1 1 UUID=800E-8308 /boot/efi vfat defaults,noatime,dmask=0002,fmask=0113 0 0 UUID=cc3b899d-7ab1-4c7b-81ba-1f3eb068ee9c swap swap defaults 0 0 /dev/cdrom /media/cdrom iso9660 noauto,exec,users,ro 0 0 /dev/cdrw /media/cdrw iso9660 noauto,exec,users,rw 0 0 /dev/dvd /media/dvd udf noauto,exec,users,ro 0 0 /dev/dvdrw /media/dvdrw udf noauto,exec,users,rw 0 0 /dev/sr0 /media/sr0 auto noauto,exec,users,ro 0 0 # Added by make-fstab /dev/sdb1 label=antiX-Live-usb UUID=ae3c8dbd-966c-4407-a45d-0aa68c43a322 /media/antiX-Live-usb ext4 noauto,exec,users 0 0 # Added by make-fstab /dev/sdb2 label=ANTIX-UEFI UUID=2510-4932 /media/ANTIX-UEFI vfat noauto,uid=1000,gid=users,dmask=002,fmask=113,users 0 0I don’t publish my inxi, because, if VLC can play audio cds, it’s because the harware is working ok, right?… but I can do that, if I have to…
Any idea how I can mount cd-roms and dvd-roms?
I tried to mount as root, same problem…
Thanks in advance for any help…P.
- This topic was modified 2 years, 11 months ago by anticapitalista.
- This topic was modified 2 years, 11 months ago by PPC.
I am trying to install AntiX-19 on an IBM Thinkpad 600E, type 2425, with 288 MB RAM and a Pentium II processor, 366 MHz.
If I boot from an AntiX-17 Live CD made from antiX-17.4.1_386-base.iso then the Thinkpad boots into a graphic desktop with menus and icons.
But booting from an AntiX-19 Live CD made from antiX-19.2.1_386-base.iso it does not show the graphic desktop. If I key <Alt>F1 to view the boot process, it stops at a text mode login prompt. It appears as if the window manager initialization is failing.
The /var/log/Xorg.0.log files for these two cases look roughly the same up to the messages that start “VESA(0)”. Both version of AntiX log these messages:
[ 135.243] (II) VESA(0): initializing int10
[ 135.248] (II) VESA(0): Primary V_BIOS segment is: 0xc000
[ 135.251] (II) VESA(0): VESA BIOS detected
[ 135.251] (II) VESA(0): VESA VBE Version 2.0
[ 135.251] (II) VESA(0): VESA VBE Total Mem: 2496 kB
[ 135.251] (II) VESA(0): VESA VBE OEM: MagicMedia 256AV 48K
[ 135.251] (II) VESA(0): VESA VBE OEM Software Rev: 1.15
[ 135.251] (II) VESA(0): VESA VBE OEM Vendor: NeoMagic
[ 135.251] (II) VESA(0): VESA VBE OEM Product: MagicMedia 256AV
[ 135.251] (II) VESA(0): VESA VBE OEM Product Rev: 01.0After that, they differ.
AntiX17:
[ 135.287] (II) VESA(0): Creating default Display subsection in Screen section
“Screen0” for depth/fbbpp 24/24Antix19:
[ 151.066] (EE) VESA(0): Specified fbbpp (24) is not a permitted value
[ 151.067] (II) UnloadModule: “vesa”
[ 151.067] (II) UnloadSubModule: “int10”
[ 151.067] (II) Unloading int10
[ 151.067] (II) UnloadSubModule: “vbe”
[ 151.067] (II) Unloading vbe
[ 151.067] (EE) Screen(s) found, but none have a usable configuration.
[ 151.067] (EE)
Fatal server error:
[ 151.068] (EE) no screens found(EE)This looks to me like a bug, but I have no idea how to fix it. Any suggestions?
Topic: File systems and Live USB
Surprisingly I have not seen this topic discussed anywhere.
As of 2020, I understand the typical file system format for most Linux distros is
-
ext4
. However I find I am often being steered towards using FAT32 for live USB; e.g; ISO installers such as Rufus or Pendrive USB installer either don’t include ext4 as an option or pop-up a “do you really want to do this” prompt first.
I was unable to boot-up antix 17 from either an external SSD or USB stick formatted in ext4. I have not tried my external disk harddrive. FAT32 always works.
Is this typical? Does ext4 not work with flash memory and/or live USB? I am aware of the file size and journalling benefits of ext4 over FAT32, is there any i/o performance benefit live USB on FAT32 is missing out on? Do any of the alternative Linux file systems have similar issues (e.g; btrfs)?
cheers Randy

