-
Search Results
-
hello all, i just put together a pretty old pc that im wanting to play old games on, i found out about antix linux while watching a youtube video, and i downloaded and installed it on this box, im running a geforce 6800gs agp graphics, everything is working on this system, but im using the nouveau driver and i would like to install the nvidia 340xx legacy drivers. can the legacy driver be installed on this kernel, or do i need to install an older kernel to get this working, this system will just be used for older games, and light web browsing. thanks in advance, ill post the system specs bellow
System: Host: antix1 Kernel: 4.9.212-antix.1-486-smp i686 bits: 32 compiler: gcc v: 8.3.0 parameters: BOOT_IMAGE=/boot/vmlinuz-4.9.212-antix.1-486-smp root=UUID=c8e5fa8e-9004-48e9-9ed7-66948889843e ro vga=791 quiet Desktop: IceWM 1.6.5 dm: SLiM 1.3.6 Distro: antiX-19.2_386-full Hannie Schaft 27 March 2020 base: Debian GNU/Linux 10 (buster) Machine: Type: Desktop System: VIA product: PM800-8237 v: N/A serial: <filter> Mobo: N/A model: PM800-8237 serial: <filter> BIOS: Phoenix v: 6.00 PG date: 01/18/2005 Memory: RAM: total: 1.47 GiB used: 395.3 MiB (26.2%) RAM Report: permissions: Unable to run dmidecode. Root privileges required. PCI Slots: Permissions: Unable to run dmidecode. Root privileges required. CPU: Topology: Single Core model: Intel Pentium 4 bits: 32 type: MT arch: Netburst Smithfield family: F (15) model-id: 4 stepping: 1 microcode: 17 L2 cache: 1024 KiB bogomips: 11969 Speed: 2992 MHz min/max: N/A Core speeds (MHz): 1: 2992 2: 2992 Flags: acpi apic bts cid clflush cmov constant_tsc cx8 de ds_cpl dtes64 dts fpu fxsr ht mca mce mmx monitor msr mtrr pae pat pbe pebs pge pni pse pse36 sep ss sse sse2 tm tsc vme xtpr Vulnerabilities: Type: itlb_multihit status: KVM: Vulnerable Type: l1tf status: Vulnerable Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable Type: meltdown status: Vulnerable Type: spec_store_bypass status: Vulnerable Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling Type: tsx_async_abort status: Not affected Graphics: Device-1: NVIDIA NV40 [GeForce 6800 GS] vendor: PNY driver: nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:0047 Display: x11 server: X.Org 1.20.4 driver: nouveau unloaded: fbdev,modesetting,vesa alternate: nv resolution: 1280x1024~60Hz OpenGL: renderer: NV40 v: 2.1 Mesa 18.3.6 direct render: Yes Audio: Device-1: Creative Labs EMU10k2/CA0100/CA0102/CA10200 [Sound Blaster Audigy Series] driver: snd_emu10k1 v: kernel bus ID: 00:0a.0 chip ID: 1102:0004 Sound Server: ALSA v: k4.9.212-antix.1-486-smp Network: Device-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter driver: 8139too v: 0.9.28 port: 9000 bus ID: 00:09.0 chip ID: 10ec:8139 IF: eth0 state: unknown speed: 100 Mbps duplex: full mac: <filter> IP v4: <filter> scope: global broadcast: <filter> IP v6: <filter> scope: link Device-2: VIA VT6102/VT6103 [Rhine-II] driver: via-rhine v: N/A port: c400 bus ID: 00:12.0 chip ID: 1106:3065 IF: eth1 state: down mac: <filter> WAN IP: <filter> Drives: Local Storage: total: 74.53 GiB used: 4.77 GiB (6.4%) ID-1: /dev/sda vendor: Seagate model: ST980811AS size: 74.53 GiB block size: physical: 512 B logical: 512 B speed: <unknown> serial: <filter> rev: C scheme: MBR Optical-1: /dev/sr0 vendor: SONY model: DVD RW DRU-820A rev: 1.0b dev-links: cdrom,cdrw,dvd,dvdrw Features: speed: 40 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram state: running RAID: Hardware-1: VIA VIA VT6420 SATA RAID Controller driver: sata_via v: 2.6 port: ac00 bus ID: 00:0f.0 chip ID: 1106.3149 rev: 80 Partition: ID-1: / raw size: 72.50 GiB size: 70.86 GiB (97.74%) used: 4.77 GiB (6.7%) fs: ext4 dev: /dev/sda1 label: rootantiX19 uuid: c8e5fa8e-9004-48e9-9ed7-66948889843e ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 10 (default 60) cache pressure: 50 (default 100) dev: /dev/sda2 label: swapantiX uuid: 1ad226bf-12be-4673-a02c-f6a61d06c90f Unmounted: Message: No unmounted partitions found. USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 8 rev: 2.0 speed: 480 Mb/s chip ID: 1d6b:0002 Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001 Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001 Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001 Device-1: 4-1:2 info: Alcor Micro 8-in-1 Media Card Reader type: Mass Storage driver: usb-storage interfaces: 1 rev: 1.1 speed: 12 Mb/s chip ID: 058f:9360 serial: <filter> Hub: 5-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001 Sensors: System Temperatures: cpu: 40.0 C mobo: 21.1 C Fan Speeds (RPM): N/A Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list 1: deb https: //mirror.genesisadaptive.com/mxlinux/antix/buster/ buster main nonfree nosystemd Active apt repos in: /etc/apt/sources.list.d/buster-backports.list 1: deb http: //deb.debian.org/debian buster-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/ buster-updates main contrib non-free Active apt repos in: /etc/apt/sources.list.d/debian.list 1: deb http: //ftp.us.debian.org/debian/ buster main contrib non-free 2: deb http: //security.debian.org/ buster/updates main contrib non-free 3: deb http: //www.deb-multimedia.org buster main non-free No active apt repos in: /etc/apt/sources.list.d/onion.list No active apt repos in: /etc/apt/sources.list.d/various.listRight – with some serious couch-time at home due to this tragically global crisis, I was reading through some of the old antiX forum archives and ran across this golden nugget to speed up your system. I’m running relatively new hardware only a year or so old (but with 6 year old cpu’s and video) and this certainly made a difference:
In /etc/sysctl.conf
Try changing your
vm.swappiness=Xvariable. Mine was set to 10 as default. So I changed it to 1
vm.swappiness=1and left the rest as is. WOW. Oh SNAP. Not imaginary, but seemingly so fast on my hardware that stuff just pops up, be it on antiX 19, or the “core” version with nothing but cli programs.
I guess it all depends on hardware. At home I’m running mostly small “fanless” mini-pc’s with older low power AMD cpu’s (VNOPN K1 models), albeit the infrastructure (bios / uefi, usb 3 ports yadda yadda) this tweak to swappiness made a big difference.
I’ll let you know if I have any problems, but so far, so good. Also, rummaging through the archives got me some nice metallic Samsung usb-sticks that seem really nice to take away some heat – thanks to Bitjams recomendation – I may want some more to feed my persistence addiction…
Hey AntiX users. I’m a huge fan of both AntiX and its sister distro MXLinux. I’m also a fan of Sparky because it utilizes Debian’s testing branch, aka Bullseye. I have decided to stop using Arch and head back to Debian on a new laptop. One of the distros mentioned above is probably the one I’ll most likely switch to, after narrowing down the plethora of Debian-based distros available.
As an Arch user before, I’m a fan of ‘rolling’ software packages but I’m honestly ready to stop using bleeding-edge versions. As I mentioned above, I’ve vigorously tested many Debian-based distros. I really like the builtin utilities like iso-snapshot available with AntiX but at the same time I like how sparky uses Bullseye as it’s default Debian branch.
I see that AntiX appears to make swapping branches pretty easy after checking out the repo sources in
/etc/apt/sources.list.d/. It’s pretty cool to see that the stable brance is enabled by default but it also includes commented-out and therefor disabled repos of both the testing and unstable branches.So here’s my question. Has anybody swapped over from Buster to Bullseye? When you made the switch did any package stop working? Did you completely brick your computer with an incredible amount of broken packages? Or was it smooth sailing, where everything worked out perfectly fine?
I’d love to get some input on this topic. If it turns out to be as easy as it seems AntiX will probably end up being installed as my primary os. On the other hand, if switching to the testing brance can get dicey I’ll have to go back and reevaluate which is more important to me: AntiX’s great utilities versus Sparky’s rolling method for software packages.
Looking forward to hearing your I out on this question. Thanks very much!
⁓ Ev
Hello Friends
I’ve already uninstalled antiX 17 but I think this was how I accessed ntfs partitions and other ext4 partitions:
Press Ctrl+Alt+Space , type ‘gksu spacefm’, then on the left panel of the spacefm file explorer, I click on the partitions that I want to have access to for the duration of my session.
I would then open spacefm but this time not as root. The ntfs and other ext4 partitions are now accessible.
Now I’m using antiX19. I have these in /etc/fstab :
UUID=103e56a5-788d-4b7b-9aed-9661e7549b28 / ext4 defaults,noatime 1 1 UUID=097873ed-558c-4bff-9c69-64a74565c510 /home ext4 defaults,noatime 1 2 UUID=31e1752b-f976-4c90-bbed-0e3193ae6009 swap swap defaults 0 0 #-> /dev/sda2 label=windows UUID=03DDC9276CCDAAB7 /media/windows ntfs-3g noauto,noexec,uid=1000,gid=users,dmask=002,fmask=113,users 0 0 #-> /dev/sda5 label=data UUID=1592F30A2BBAB661 /media/data ntfs-3g auto,exec,uid=1000,gid=users,dmask=002,fmask=113,users 0 0 #-> /dev/sda7 label=debian_home UUID=6acf2243-4d9c-4d5f-865f-9421a15fae6e /media/debian_home ext4 noauto,exec,users 0 0 #-> /dev/sda8 label=debian_root UUID=d9cca0e2-b2b0-4d4b-b85e-a326829f92b5 /media/debian_root ext4 noauto,exec,users 0 0Opening the spacefm file explorer as non-root, I click on my data partition, which is shown above as /media/data , I get this:
udevil: denied 88: device /dev/sda5 is an internal device and you're not rootI open spacefm as root, I click on my data partition again, it opens, but now it’s mounted in /media/root/data , NOT /media/data as shown in /etc/fstab
While spacefm is still open as root, I click on the ext4 partitions, I get this:
udevil: /dev/sda7 is known to mount - running mount as current user udevil: warning 45: options ignored for device in fstab (or specify mount point) mount: /media/debian_home: mount point does not exist.I open another spacefm but this time not as root, I click my data partition, it says:
Directory doesn't exist /media/root/dataI click on my other ext4 partitions, I get this:
udevil: /dev/sda7 is known to mount - running mount as current user udevil: warning 45: options ignored for device in fstab (or specify mount point) mount: /media/debian_home: mount point does not exist.Thank you for your time!
- This topic was modified 3 years, 2 months ago by kaye.
- This topic was modified 3 years, 1 month ago by kaye.
While experimenting with Antix19 today, I ran into unsuspected and baffling difficulties, which turned out to be caused by the live USB used for installation. Maybe I can help some others by telling about it on the forum.
I have two separate small ssd’s in my computer. The first one has the Antix17 system I use on a daily basis, the other one an old Antix15 installation that hasn’t booted for some years now. I wiped the second one and installed Antix19 from a live USB. I can then experiment freely using dual boot, and make the switch permanently when I feel ready. Data and media files are on other HDD’s and can be shared without any problem by both installations. I have used this procedure before without experiencing any problems whatsoever.
I ran into problems with Antix19 soon, and decided to start over at a later time. However I was unable to boot to my old Antix17 system, although I had been very careful to not let the installer touch its disk. To be precise, I could boot to a console, but was unable to start a graphical interface. I saw complaints about a ‘read-only file system’ and log files were not saved. The only thing I remembered about using the Antix17 disk from within the Antix19 system was a double click on the disk from within SpaceFM, causing it to mount the Antix17 file system (I was planning to copy some configuration files). Apparently this was a huge mistake: doing so gave the Antix17 filesystem a new UUID, thereby preventing it from mounting properly on booting Antix17.
Here if my /etc/fstab file from Antix17:
# /etc/fstab: static file system information
#
# Created by make-fstab on Sat Jul 11 08:52:37 EDT 2015# <file system> <mount point> <type> <options> <dump/pass>
UUID=ab172d74-d0d9-45a1-8b51-2611c6a539df / ext4 defaults 1 1
UUID=0841d91d-5dcc-4fc1-99ee-11257a2b9855 swap swap defaults 0 0
UUID=ab172d74-d0d9-45a1-8b51-2611c6a539df /mnt/sys/Antix-15 ext4 auto,exec,users,rw 0 0/dev/sdc3 /mnt/data ntfs-3g auto,exec,users,rw 0 0
/dev/sdc2 /mnt/apps ntfs-3g auto,exec,users,rw 0 0
UUID=7E701FE8701FA5C5 /mnt/sys/Windows ntfs-3g auto,exec,users,rw 0 0
UUID=68c02545-221d-49bd-ba85-0045c670828f /mnt/media ext4 auto,exec,users,rw 0 0#shares op nasty
//nasty/media /mnt/nasty/media cifs username=dd,password=xxxxx,iocharset=utf8,sec=ntlm 0 0
//nasty/data /mnt/nasty/data cifs username=dd,password=xxxxx,iocharset=utf8,sec=ntlm 0 0
//nasty/web /mnt/nasty/Web cifs username=dd,password=xxxxx,iocharset=utf8,sec=ntlm 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 0And this is the result of running blkid:
/dev/sda1: LABEL=”media2″ UUID=”68c02545-221d-49bd-ba85-0045c670828f” TYPE=”ext4″ PARTUUID=”304f4518-01″
/dev/sdb1: LABEL=”rootantiX17.1″ UUID=”9e72bdbb-b308-4d0c-adf8-95bf7cca9544″ TYPE=”ext4″ PARTUUID=”8e783a29-01″
/dev/sdc1: LABEL=”Sys” UUID=”7E701FE8701FA5C5″ TYPE=”ntfs” PARTUUID=”00000001-01″
/dev/sdc2: LABEL=”Apps” UUID=”4E42BDA2399B3504″ TYPE=”ntfs” PTTYPE=”dos” PARTUUID=”00000001-02″
/dev/sdc3: LABEL=”Data” UUID=”042F889220B256CB” TYPE=”ntfs” PTTYPE=”dos” PARTUUID=”00000001-03″
/dev/sde1: LABEL=”antiX19″ UUID=”39bdad5f-0949-43eb-bbce-713ddd636655″ TYPE=”ext4″ PARTUUID=”7378c34d-01″
/dev/sde2: LABEL=”swap” UUID=”0841d91d-5dcc-4fc1-99ee-11257a2b9855″ TYPE=”swap” PARTUUID=”7378c34d-02″As you can see, both / (the Antix17 root partition) and /mnt/sys/Antix-15 (the old Antix15 root partition) have the same UUID in fstab (which still baffles me, as to how this is possible) which is not actually assigned to any partition, according to the blkid output.
I solved the problem by booting into the rather shaky new Antix19 system and from there editing the Antix17 /etc/fstab so that it contained the correct UUID’s. The next reboot into Antix17 was 100% normal again.
I installed antiX-19.1_386-full.iso to this old laptop (see below). It seemed to work for a brief time period but, after that, no app seemed to could be launched. I could neither open a terminal nor the control-center. No other choice than “PrtSc & reisub” to reboot or press power-button to shutdown. After rebooting, same behavior. I re-installed it twice, but the result was the same. I didn’t have time for more tests, so I installed antiX-17.4.1_386-full.iso and everything is OK. I just inform you about the issue.
$ inxi -Fxz System: Host: puppy Kernel: 4.9.212-antix.1-486-smp i686 bits: 32 compiler: gcc v: 6.3.0 Desktop: IceWM 1.4.2 Distro: antiX-17.4.1_386-full Helen Keller 28 March 2019 base: Debian GNU/Linux 9 (stretch) Machine: Type: Laptop System: TOSHIBA product: Satellite L10 v: PSL10E-021011GE serial: <filter> Mobo: TOSHIBA model: Satellite L10 v: Rev 1.0 serial: <filter> BIOS: TOSHIBA v: 2.40 date: 06/22/2005 Battery: ID-1: BAT0 charge: N/A condition: N/A model: N/A status: N/A CPU: Topology: Single Core model: Intel Pentium M bits: 32 type: MCP arch: M Dothan rev: 6 L2 cache: 2048 KiB flags: sse sse2 bogomips: 2392 Speed: 1200 MHz min/max: 600/1700 MHz Core speed (MHz): 1: 1200 Graphics: Device-1: Intel 82852/855GM Integrated Graphics vendor: Toshiba America Info Systems driver: i915 v: kernel bus ID: 00:02.0 Display: server: X.Org 1.19.2 driver: intel unloaded: fbdev,modesetting,vesa resolution: 1024x768~60Hz OpenGL: renderer: Mesa DRI Intel 852GM/855GM x86/MMX/SSE2 v: 1.3 Mesa 13.0.6 direct render: Yes Audio: Device-1: Intel 82801DB/DBL/DBM AC97 Audio vendor: Toshiba America Info Systems driver: snd_intel8x0 v: kernel bus ID: 00:1f.5 Sound Server: ALSA v: k4.9.212-antix.1-486-smp Network: Device-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter vendor: Toshiba America Info Systems driver: 8139too v: 0.9.28 port: 3800 bus ID: 02:02.0 IF: eth1 state: unknown speed: 100 Mbps duplex: full mac: <filter> Device-2: Intel PRO/Wireless 2200BG [Calexico2] Network driver: ipw2200 v: 1.2.2kmprq port: 3800 bus ID: 02:04.0 IF: eth0 state: down mac: <filter> Drives: Local Storage: total: 55.89 GiB used: 11.14 GiB (19.9%) ID-1: /dev/sda vendor: Hitachi model: DK23EA-60 size: 55.89 GiB Partition: ID-1: / size: 52.76 GiB used: 11.13 GiB (21.1%) fs: ext4 dev: /dev/sda1 ID-2: swap-1 size: 2.00 GiB used: 12.0 MiB (0.6%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 54.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 126 Uptime: 1h 54m Memory: 477.1 MiB used: 254.2 MiB (53.3%) Init: SysVinit runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.36