I love the fact that you can choose Stable, Testing, or Sid at the start of the install.
If I choose stable or testing, after install and after first boot, all looks great. But, if I go into Symantic Package Manager and enable the Mepix MX15 test repo, and I try to download OBS-Studio, once I do apt-get update, it cannot find OBS-Studio, and it pulls in files that corrupt my system.
How can I install items from the Mepis MX15 Test repo without corrupting my system?
Thanks
Len
topic title: Antix 16 Beta 5 issues
15 posts
• Page 1 of 1
-
Posts: 11
- Joined: 29 Apr 2015
-
dolphin_oracledolphin_oraclePosts: 2,238
- Joined: 16 Dec 2007
#2
I'm not sure what you are downloading that corrupts your system if syapatic can't find obs-studio.
Here's what happens to me with beta 5. I enable MX Test repo, refresh sources, and obs-studio is present in the list, but if you try to install, it synaptic complains about broken packages. At this point nothing has been downloaded.
The MX Test Repo builds packages against both the debian main repos AND the MX main repo. In obs-studio's case, that means you need to enable BOTH of the mx repos to get all the dependencies.
Here's what happens to me with beta 5. I enable MX Test repo, refresh sources, and obs-studio is present in the list, but if you try to install, it synaptic complains about broken packages. At this point nothing has been downloaded.
The MX Test Repo builds packages against both the debian main repos AND the MX main repo. In obs-studio's case, that means you need to enable BOTH of the mx repos to get all the dependencies.
-
anticapitalista
Posts: 5,956
- Site Admin
- Joined: 11 Sep 2007
#3
If you want to use the MX repos, then you must only use jessie repos in debian.list and antix.list
-
Posts: 11
- Joined: 29 Apr 2015
#4
OK, I'll give that a try __{{emoticon}}__
-
Posts: 11
- Joined: 29 Apr 2015
#5
That works for me __{{emoticon}}__
Thanks guys!
Len
Thanks guys!
Len
-
Posts: 521
- Joined: 20 Apr 2015
#6
Download and made my persistant USB drive.
Had to blacklist wl again.
Guess the mods made for b2 disappeared.
Code: Select all
$ inxi -Fxz
System: Host: antix1 Kernel: 4.4.10-antix.1-amd64-smp x86_64 (64 bit gcc: 4.9.3)
Desktop: IceWM 1.3.8
Distro: antiX-16-b5_x64-full Berta Cáceres 19 May 2016
Machine: System: Dell (portable) product: Latitude D630
Mobo: Dell model: 0KU184 Bios: Dell v: A15 date: 11/24/2008
Battery BAT0: charge: 44.0 Wh 124.4% condition: 35.4/44.0 Wh (80%)
model: Sanyo DELL 62 status: Full
CPU: Dual core Intel Core2 Duo T7250 (-MCP-) cache: 2048 KB
flags: (lm nx sse sse2 sse3 ssse3 vmx) bmips: 7977
clock speeds: max: 2001 MHz 1: 1600 MHz 2: 1600 MHz
Graphics: Card: Intel Mobile GM965/GL960 Integrated Graphics Controller (primary)
bus-ID: 00:02.0
Display Server: X.Org 1.16.4 driver: intel
Resolution: 1280x800@60.02hz
GLX Renderer: Mesa DRI Intel 965GM
GLX Version: 2.1 Mesa 10.3.2 Direct Rendering: Yes
Audio: Card Intel 82801H (ICH8 Family) HD Audio Controller
driver: snd_hda_intel bus-ID: 00:1b.0
Sound: ALSA v: k4.4.10-antix.1-amd64-smp
Network: Card-1: Broadcom NetXtreme BCM5755M Gigabit Ethernet PCI Express
driver: tg3 v: 3.137 bus-ID: 09:00.0
IF: eth0 state: down mac: <filter>
Card-2: Broadcom BCM4321 802.11a/b/g/n
driver: b43-pci-bridge bus-ID: 0c:00.0
IF: wlan0 state: up mac: <filter>
Drives: HDD Total Size: 128.1GB (4.3% used)
ID-1: /dev/sda model: SSD2SC120G1CS175 size: 120.0GB
ID-2: USB /dev/sdb model: JumpDrive size: 8.0GB
Partition: ID-1: / size: 3.1G used: 206M (7%) fs: overlay dev: N/A
ID-2: /home size: 1.1G used: 29M (3%) fs: ext4 dev: /dev/loop1
ID-3: swap-1 size: 4.69GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
Sensors: System Temperatures: cpu: 54.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 147 Uptime: 2 min Memory: 177.5/3945.5MB
Init: SysVinit runlevel: 5 Gcc sys: 4.9.2
Client: Shell (bash 4.3.301) inxi: 2.3.0
Code: Select all
#blacklist b43
blacklist b43legacy
blacklist b44
#blacklist bcma
blacklist brcm80211
blacklist brcmsmac
#blacklist ssb
blcklist wl
-
Posts: 2,238
- Joined: 16 Dec 2007
#7
Shay,
did you make the persistent liveUSB on another machine? then try this one? the Broadcom script changes are present, and should be using b43 for your part by default.
did you make the persistent liveUSB on another machine? then try this one? the Broadcom script changes are present, and should be using b43 for your part by default.
-
Posts: 521
- Joined: 20 Apr 2015
#8
Yes, I used Antix-b2 to make the USB stick. the desktop is Wired only. Intel driver.
Booted it to that old desktop, made it persistent, updated it, shut down.
Booted this laptop, it has AntiX-15 installed, and could not connect to the internet.
Blacklisted wl and made the other change. Rebooted and it Works fine now.
Booted it to that old desktop, made it persistent, updated it, shut down.
Booted this laptop, it has AntiX-15 installed, and could not connect to the internet.
Blacklisted wl and made the other change. Rebooted and it Works fine now.
-
Posts: 521
- Joined: 20 Apr 2015
#9
I will have to do a clean install as this messed up with the USB problem and that is what is needed to fix it.
Code: Select all
Booted this laptop, it has AntiX-15 installed
-
Posts: 2,238
- Joined: 16 Dec 2007
#10
The is a file called etc/bcm-ckd that is created in first run of the system. Its presense prevents the drivers from being modified.
-
Posts: 20
- Joined: 01 Apr 2013
#11
Thanks guys running on a Dell D620. Installed with Unetbootin to USB drive. No problems running it. Full version.
-
Posts: 521
- Joined: 20 Apr 2015
#12
Made the new stick but this time booted it up on the old Dell D630 first thing.
Made it persistent, and everything is working correctly.
Actual installed antiX-16-b5_x64-full Berta Cáceres 19 May 2016 to it also.
Thanks!!
Made it persistent, and everything is working correctly.
Actual installed antiX-16-b5_x64-full Berta Cáceres 19 May 2016 to it also.
Thanks!!
-
Posts: 88
- Joined: 25 Aug 2012
#13
make-fstab is only adding the sda1 thru sda15 partitions to the fstab file it creates
My sda drive has seven additional partitions that aren't included in fstab (the 259:x MAJ:MIN items)
I noticed it when I couldn't mount my MX-15 partition (sda19, MAJ:MIN 259:3) in ROX-Filer
Code: Select all
demo@antix1:~
$ cat etc/fstab
# etc/fstab: static file system information
#
# Created by make-fstab on Thu Jun 2 15:13:21 EDT 2016
# <file system> <mount point> <type> <options> <dump/pass>
# Added by make-fstab /dev/sda1 label=Recovery
UUID=B46E0CE06E0C9D6C /media/Recovery ntfs-3g noauto,noexec,uid=1000,gid=users,dmask=002,fmask=113,users 0 0
# Added by make-fstab /dev/sda2 label=ESP
UUID=880F-4F9A /media/ESP vfat noauto,uid=1000,gid=users,dmask=002,fmask=113,users 0 0
# Added by make-fstab /dev/sda4 label=Gateway
UUID=682EA9182EA8DFF4 /media/Gateway ntfs-3g noauto,noexec,uid=1000,gid=users,dmask=002,fmask=113,users 0 0
# Added by make-fstab /dev/sda5
UUID=F07E44597E441B2C /media/sda5 ntfs-3g noauto,noexec,uid=1000,gid=users,dmask=002,fmask=113,users 0 0
# Added by make-fstab /dev/sda6
UUID=7317a34d-511a-40ec-8869-da077570c7b9 swap swap defaults 0 0
# Added by make-fstab /dev/sda7 label=Frugal
UUID=e6870e1d-9e1b-4d59-a8fb-178d183a6011 /media/Frugal ext4 noauto,exec,users 0 0
# Added by make-fstab /dev/sda8 label=MX14
UUID=51c65029-581a-40cd-90b6-fbc341b970f2 /media/MX14 ext4 noauto,exec,users 0 0
# Added by make-fstab /dev/sda9 label=Xubuntu_14.04
UUID=b676e12b-33b3-42dc-bda6-61b951c49074 /media/Xubuntu_14.04 ext4 noauto,exec,users 0 0
# Added by make-fstab /dev/sda10 label=MX-15_alpha1
UUID=e2fe21b7-539d-45bd-ba90-36b6a275923b /media/MX-15_alpha1 ext4 noauto,exec,users 0 0
# Added by make-fstab /dev/sda11
UUID=72602033-34a6-4f0c-aea2-579beaa2018b /media/sda11 ext3 noauto,exec,users 0 0
# Added by make-fstab /dev/sda12 label=jessie
UUID=66187e6e-9be9-4904-b0f0-8d78b59212eb /media/jessie ext4 noauto,exec,users 0 0
# Added by make-fstab /dev/sda13 label=FAT32TST
UUID=52A3-EFD3 /media/FAT32TST vfat noauto,uid=1000,gid=users,dmask=002,fmask=113,users 0 0
# Added by make-fstab /dev/sda14 label=FAT16TST
UUID=53CC-9D58 /media/FAT16TST vfat noauto,uid=1000,gid=users,dmask=002,fmask=113,users 0 0
# Added by make-fstab /dev/sda15 label=NTFSTST
UUID=73A3F602320A68AF /media/NTFSTST ntfs-3g noauto,noexec,uid=1000,gid=users,dmask=002,fmask=113,users 0 0
# Added by make-fstab /dev/sr0
/dev/sr0 /media/sr0 auto noauto,exec,users,ro 0 0
demo@antix1:~
$
Code: Select all
demo@antix1:~
$ sudo lsblk -blo NAME,MAJ:MIN,LABEL,MOUNTPOINT /dev/sda
NAME MAJ:MIN LABEL MOUNTPOINT
sda 8:0
sda1 8:1 Recovery
sda2 8:2 ESP
sda3 8:3
sda4 8:4 Gateway
sda5 8:5
sda6 8:6 [SWAP]
sda7 8:7 Frugal
sda8 8:8 MX14
sda9 8:9 Xubuntu 14.04
sda10 8:10 MX-15_alpha1
sda11 8:11
sda12 8:12 jessie
sda13 8:13 FAT32TST
sda14 8:14 FAT16TST
sda15 8:15 NTFSTST
sda16 259:0 XFSTST
sda17 259:1 EXT3TST
sda18 259:2 MX15EFI
sda19 259:3 MX-15
sda20 259:4 /test70GB
sda21 259:5 システムで予約済み
sda22 259:6 Push Button Reset
demo@antix1:~
$
-
Posts: 88
- Joined: 25 Aug 2012
#14
103 hex is 259 decimal.
I don't know if this the right way to fix it or not, but adding '103' to the cases it checks, will make it add entries for all 22 of my sda drive partitions.kmathern wrote:make-fstab is only adding the sda1 thru sda15 partitions to the fstab file it creates ...
103 hex is 259 decimal.
Code: Select all
$ diff /sbin/make-fstab make-fstab -u
--- /sbin/make-fstab 2016-05-25 21:53:51.000000000 -0400
+++ make-fstab 2016-06-03 09:28:43.648355046 -0400
@@ -405,7 +405,7 @@
# Major-number 8 = SCSI hard drive, major-number 3 = non-SCSI hard drive
case $(stat -c %t $dev) in
- b3|[38]) ;;
+ b3|103|[38]) ;;
*) continue
esac
Code: Select all
$ bash /home/kent/make-fstab
make-fstab: Remove all dynamic entries from fstab
make-fstab: Create new fstab
make-fstab: Ignore iso9660 filesystem on device /dev/sdb1
make-fstab: Put 22 hard drive entries into fstab
make-fstab: Put 5 removable entries into fstab
-
Posts: 1,308
- Joined: 31 Aug 2009
#15
Thanks Kent! I will also make this change in partition-info and the live initrd.kmathern wrote:I don't know if this the right way to fix it or not, but adding '103' to the cases it checks, will make it add entries for all 22 of my sda drive partitions.kmathern wrote:make-fstab is only adding the sda1 thru sda15 partitions to the fstab file it creates ...