topic title: antiX-15-beta1 to beta2 patch available
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#31
rokytnji wrote:No biggy though as things carried over OK. But maybe not like you think. But alls well that ends well.
The xorg.conf on your installed system looks good to me. Am I missing something? Either way, I'm glad it worked.
Posts: 4,164
rokytnji
Joined: 20 Feb 2009
#32
"Am I missing something?"

You see safe anywhere? That was the first thing I noticed in the xorg.conf naming. I was looking for it.
Then just grinned and said &^%$# to myself.
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#33
rokytnji wrote:"Am I missing something?"

You see safe anywhere? That was the first thing I noticed in the xorg.conf naming. I was looking for it.
Then just grinned and said &^%$# to myself.
I'm sorry for the confusion. Setting"xorg=safe" is currently shorthand for setting"xorg=vesa,auto". This sets the driver to"vesa" and sets the highest resolution to 1280x1024. Run"make-xorg-conf --help" for more details.

Also the"failsafe" cheat is shorthand for both"xorg=save" and"load=all".

We may end up tweaking what xorg=safe does but by having this one extra layer of abstraction we only need to make the change in the make-xorg-conf script and the interface seen by the users, xorg=safe, stays the same. Likewise with"failsafe". Goodness knows what other changes will be coming down the pike that add to the difficulty of booting a Live system OOTB on most computers. By using the"failsafe" boot option we will keep the interface seen by the users consistent even if we have to scramble around behind the scenes to have"failsafe" do more things or have"xorg=safe" do something different.

I try hard to make our boot parameters both clear and concise. The requirement that many older system need to use the"nomodeset" boot parameter in order to boot the way they used to is a perfect example of the opposite of my strategy. IMO"kms" or"nokms" or even"modeset" would have been much better.

I can see why these changes we made were confusing, especially since there was no explanation or documentation. But I think it is an improvement since users should not normally need to know the details of what needs to be done for a"safe" video mode or a"failsafe" boot. And these details may change over time. For those who want to get down and dirty the raw"xorg=xxx,yyy" and"load=xxx,yyy" are still available.

Again, I'm sorry for the confusion this caused.

Edit: When"nomodeset" was first introduced some of the modesetting drivers were broken and didn't respect it so were were supposed to use:

Code: Select all

nomodeset nouveau.modeset=0 radeon.modeset=0 i915.modeset=0
just to get the previous default behavior. This seemed extremely silly. It also clogged up the boot parameters. This is the exact opposite of my approach.
Posts: 1,445
skidoo
Joined: 09 Feb 2012
#34
Has this (reported against previous releases) been fixed?
usr/local/bin/antixccmouse.sh
mouse acceleration set via ControlCentre is not retained across sessions

ControlCentre"mouse acceleration" utility:
displays a hard-coded value (rather than current value) each time its dialog window is opened

ControlCentre"select kb layout" utility:
displays 'british' each time opened (regardless the actual current setting)
Posts: 4,164
rokytnji
Joined: 20 Feb 2009
#35
Ctrl+Alt+h opens up in icewesel and cannot find help html doc.

USB 2.0 Pcmcia Card bus on the T23 (Adaptec Brand, not Chinese) with the test I tried on the Panasonic with the usb card reader with a sd card with files on it mounted up in spacefm OK.

I guess the via chipset is not kernel friendly on the chinese generic pcmcia usb 2.0 & firewire cardbus that I tried on the panasonic. No biggy. Just info.
Sound, Youtube, everything else tested a little on the T23 seems OK.
Not a lot of testing time for me on a Friday.
Posts: 19
pcpavnz
Joined: 09 Nov 2012
#36
Running in virtualbox on my low res 1366x768 display, the default res of 1280x1024 is too high for my display and no login prompt was visible without switching to full screen. During the live session, I could resize the desktop using the control panel > session > set screen resolution and get things in order but once installed, arandr opened but there was no window to make any changes.
Installed the vbox guest additions and rebooted the vm, then the arandr was usable and I could set the resolution to 1024x768. On logging out, the resolution change had no effect on the login screen and it the next login it reverted to 1280x1024.
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#37
pcpavnz wrote:Running in virtualbox on my low res 1366x768 display, the default res of 1280x1024 is too high for my display and no login prompt was visible without switching to full screen.
We created a special vbox mode for making the xorg.conf file when we detect we are running in Virtual Box. The 1280x1024 resolution works well for both anti and me in Virtual Box. I believe selecting"Save Video Mode" from the main bootloader menu will bring you down to 1024x768 inside of Virtual Box. You can also manually type in a resolution such as"xorg=1024x768". If you use"noxorg" then X will default to using the fbdev which will get you the same resolution that was set in the"F7 Console" menu (assuming that resolution works for you).

Some of this may be broken. My latest initrd.gz is available at
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://www.dropbox.com/sh/ilo68y5ubmc4q5i/AADvYTt7gHbnRfZmJwcFOsRha?dl=0"
linktext was:"https://www.dropbox.com/sh/ilo68y5ubmc4 ... OsRha?dl=0"
====================================
which fixed a lot of the problems. There is also an xtra.tgz tarball which should *not* be unpacked. Just drop it in the same /antiX/ directory that the initrd.gz goes in and it should get unpacked on every boot. You don't need the tarball but it provides a few nice extra features.

Edit: fixed URL.
Last edited by BitJam on 18 Apr 2015, 18:41, edited 1 time in total.
Posts: 2,238
dolphin_oracle
Joined: 16 Dec 2007
#38
forcing Vesa in VirtualBox is working pretty well for me. I also have a 1366x768 screen. I get scrollbars on the vbox window so accessing winodes is not to bad.. or I use scale mode until I get the resolution set. it's better than the old 800 x 600 I used to get.
Posts: 4,164
rokytnji
Joined: 20 Feb 2009
#39
Just a live test on a IBM E50 I picked up yesterday. Still needs assembling finishes. So just testing hardware before I install Beta 2 on this new/old IBM low profile tower with just a cdrom drive.

Code: Select all

demo@antiX1:~
$ inxi -Fxz
System:    Host: antiX1 Kernel: 3.19.1-antix.1-486-smp i686 (32 bit gcc: 4.9.2)
           Desktop: IceWM 1.3.8
           Distro: antiX-15-beta2-V_386-full Killah P 11 April 2015
Machine:   System: Lenovo product: 9218D1U
           Mobo: Lenovo model: 8S661FXMTIU v: x.x
           Bios: Award v: C661KTF6A date: 10/27/2005
CPU:       Single core Intel Pentium 4 (-HT-) cache: 2048 KB
           flags: (lm nx pae sse sse2 sse3) bmips: 6001
           clock speeds: max: 3000 MHz 1: 3000 MHz 2: 3000 MHz
Graphics:  Card: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter
           bus-ID: 01:00.0
           Display Server: X.Org 1.16.4 drivers: fbdev (unloaded: vesa)
           Resolution: 800x600@75.00hz
           GLX Renderer: Gallium 0.4 on llvmpipe (LLVM 3.5, 128 bits)
           GLX Version: 3.0 Mesa 10.3.2 Direct Rendering: Yes
Audio:     Card Silicon Integrated Systems [SiS] SiS7012 AC'97 Sound Controller
           driver: snd_intel8x0 ports: e000 e400 bus-ID: 00:02.7
           Sound: ALSA v: k3.19.1-antix.1-486-smp
Network:   Card-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter
           driver: 8139too v: 0.9.28 port: e800 bus-ID: 00:0f.0
           IF: eth0 state: down mac: <filter>
           Card-2: Realtek RTL8187B Wireless 802.11g 54Mbps Network Adapter
           driver: rtl8187 usb-ID: 004-005
           IF: wlan0 state: N/A mac: N/A
Drives:    HDD Total Size: 62.1GB (1.2% used)
           ID-1: /dev/sda model: SAMSUNG_SV6003H size: 60.1GB
           ID-2: USB /dev/sdb model: DataTraveler_2.0 size: 2.0GB
Sensors:   None detected - is lm-sensors installed and configured?
Info:      Processes: 102 Uptime: 27 min Memory: 203.5/466.5MB
           Init: SysVinit runlevel: 5 Gcc sys: 4.9.2
           Client: Shell (bash 4.3.301) inxi: 2.2.16 
demo@antiX1:~
$
As you can see BitJam. This one has SIS graphics chip. Ha Ha. Now we have all bases covered for testing boxes. Anyways. Got the red error messages again on load again
like I posted before about savage chip and the IBM T23 Laptop.
Nice thing about this. It has a stronger cpu so only hammering at 61% showing in Conky.

I still have to finish reassembling this unit. Sound, Youtube, work OK.
I have a POS hard drive in here that may die any minute, but will try a install later on
anyways. I hope the
make-xorg-conf -o /etc/X11/xorg.conf safe
works out when I reboot, reassemble this oldy but goody desktop, and proceed
with the install process without being in a 800x600 screen on this acer square little lcd I am using to test,

So just a update on one that I could get working quickly. The other 2 required me to bid/best offer on ebay on some cables for the graphics cards on the Dell T3400s.
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#40
rokytnji wrote:As you can see BitJam. This one has SIS graphics chip. Ha Ha. Now we have all bases covered for testing boxes. Anyways. Got the red error messages again on load again
That bug should be fixed in my latest initrd.gz which is available here:
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://www.dropbox.com/sh/ilo68y5ubmc4q5i/AADvYTt7gHbnRfZmJwcFOsRha?dl=0"
linktext was:"https://www.dropbox.com/sh/ilo68y5ubmc4 ... OsRha?dl=0"
====================================
Don't feel obligated to try it. It's there if you want it.
Posts: 21
Jon_J
Joined: 21 Jan 2014
#41
rokytnji wrote:As you can see BitJam. This one has SIS graphics chip. Ha Ha. Now we have all bases covered for testing boxes.
What about GMA500 poulsbo graphics, released in 2009?
I searched this and the other thread and didn't see any mention of this graphics chip.
antix-15-beta1-v-ready-for-testing-t5565.html

I also have an old box with a SIS 620 chip which is very stubborn to get graphics drivers for in Linux.
I'm not concerned about that old box though. It still has win95 and Puppy 3.01 running on it.
Jon
Posts: 4,164
rokytnji
Joined: 20 Feb 2009
#42
BitJam wrote:
rokytnji wrote:As you can see BitJam. This one has SIS graphics chip. Ha Ha. Now we have all bases covered for testing boxes. Anyways. Got the red error messages again on load again
That bug should be fixed in my latest initrd.gz which is available here:
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://www.dropbox.com/sh/ilo68y5ubmc4q5i/AADvYTt7gHbnRfZmJwcFOsRha?dl=0"
linktext was:"https://www.dropbox.com/sh/ilo68y5ubmc4 ... OsRha?dl=0"
====================================
Don't feel obligated to try it. It's there if you want it.
Sorry Bro. I used the boot cheat instead abd it worked out OK for me instead. I would not know how to try your other fix without instructions anyways but I am already posting from a install now.

Code: Select all

harry@misohorny:~
$ inxi -Fxz
System:    Host: misohorny Kernel: 3.19.1-antix.1-486-smp i686 (32 bit gcc: 4.9.2)
           Desktop: IceWM 1.3.8
           Distro: antiX-15-beta2-V_386-full Killah P 11 April 2015
Machine:   System: Lenovo product: 9218D1U
           Mobo: Lenovo model: 8S661FXMTIU v: x.x
           Bios: Award v: C661KTF6A date: 10/27/2005
CPU:       Single core Intel Pentium 4 (-HT-) cache: 2048 KB
           flags: (lm nx pae sse sse2 sse3) bmips: 6001
           clock speeds: max: 3000 MHz 1: 2800 MHz 2: 2800 MHz
Graphics:  Card: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter
           bus-ID: 01:00.0
           Display Server: X.Org 1.16.4 drivers: vesa (unloaded: fbdev)
           Resolution: 1280x1024@0.00hz
           GLX Renderer: Gallium 0.4 on llvmpipe (LLVM 3.5, 128 bits)
           GLX Version: 3.0 Mesa 10.3.2 Direct Rendering: Yes
Audio:     Card Silicon Integrated Systems [SiS] SiS7012 AC'97 Sound Controller
           driver: snd_intel8x0 ports: e000 e400 bus-ID: 00:02.7
           Sound: ALSA v: k3.19.1-antix.1-486-smp
Network:   Card-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter
           driver: 8139too v: 0.9.28 port: e800 bus-ID: 00:0f.0
           IF: eth0 state: down mac: <filter>
           Card-2: Realtek RTL8187B Wireless 802.11g 54Mbps Network Adapter
           driver: rtl8187 usb-ID: 001-003
           IF: wlan0 state: N/A mac: N/A
Drives:    HDD Total Size: 60.1GB (7.6% used)
           ID-1: /dev/sda model: SAMSUNG_SV6003H size: 60.1GB
Partition: ID-1: / size: 7.6G used: 2.4G (33%) fs: ext4 dev: /dev/sda1
           ID-2: /home size: 15G used: 67M (1%) fs: ext4 dev: /dev/sda2
           ID-3: swap-1 size: 2.10GB used: 0.00GB (0%) fs: swap dev: /dev/sda3
Sensors:   None detected - is lm-sensors installed and configured?
Info:      Processes: 100 Uptime: 7 min Memory: 190.1/466.5MB
           Init: SysVinit runlevel: 5 Gcc sys: 4.9.2
           Client: Shell (bash 4.3.301) inxi: 2.2.16
Running vesa and the right screen resolution now after install. Running live with the boot cheat code was still 800x600 but the cpu was not at 60% during the install process. It was way low like 4% or so. Installed. It is even lower. So a happy camper here.

Can't say how long this hard drive will last. I have a new hard drive (80 gig 7200 rpm IDE) being shipped and a 1 gig ram stick also coming via
the mail.

One down, two to go I guess. __{{emoticon}}__
What about GMA500 poulsbo graphics, released in 2009?
I searched this and the other thread and didn't see any mention of this graphics chip.
antix-15-beta1-v-ready-for-testing-t5565.html

I also have an old box with a SIS 620 chip which is very stubborn to get graphics drivers for in Linux.
I'm not concerned about that old box though. It still has win95 and Puppy 3.01 running on it.
Jon
Like I mentioned at Mepis Forums John J. I do not have a paulsboro graphics chip to test with. All I can do is post about SIS and how I got it working. Go back to the 2nd page in this thread. What I did to get savage graphics chip working. Is exactly how I got this SIS chip working.

I don't know if those 2 fixes will apply to Paulsboro. But hell. You can give it a hell of a try.
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"antix.freeforu ms.org/post40385.html#p40385"
linktext was:"Like I said. Info is on page 2."
====================================
Posts: 21
Jon_J
Joined: 21 Jan 2014
#43
Sorry for the interruption. it's spelled poulsbo, not paulsboro
Google won't find it under that name..
I'll try anyway though.

Edit:
run level 3 just worked!
In the top line of the boot screen, I removed the VGA=788 and I put in VGA=3
antiX just booted to the desktop.
I'm installing it now.
system information -> Graphics shows this.

Code: Select all

################### PC INFORMATION - graphics #####################
#################### Press CTRL  + C to exit ######################

Graphics:  Card: Intel System Controller Hub (SCH Poulsbo) Graphics Controller
           Display Server: X.Org 1.16.4 drivers: (unloaded: fbdev,vesa)
           Resolution: 1366x768@59.97hz
           GLX Renderer: Gallium 0.4 on llvmpipe (LLVM 3.5, 128 bits)
           GLX Version: 3.0 Mesa 10.3.2
Jon
Posts: 21
Jon_J
Joined: 21 Jan 2014
#44
I have antiX-15 installed on my Dell Inspiron mini 1010 netbook.
Everything seems to work so far. I had to set the time in IceWM. There is an error on boot. It didn't seem to be very serious.
The error is similar to this: fsck cannot run on this drive. no such file or directory. I'll have to write the exact error down and post it later.
here is my inxi -F

Code: Select all

$ inxi -F
System:    Host: antix15 Kernel: 3.19.1-antix.1-486-smp i686 (32 bit) Desktop: IceWM 1.3.8
           Distro: antiX-15-beta2-V_386-full Killah P 11 April 2015
Machine:   Mobo: Dell model: 0P374N v: A09 Bios: Dell v: A09 date: 09/10/2009
CPU:       Single core Intel Atom Z530 (-HT-) cache: 512 KB 
           clock speeds: max: 1600 MHz 1: 800 MHz 2: 1600 MHz
Graphics:  Card: Intel System Controller Hub (SCH Poulsbo) Graphics Controller
           Display Server: X.Org 1.16.4 drivers: (unloaded: fbdev,vesa) Resolution: 1366x768@59.97hz
           GLX Renderer: Gallium 0.4 on llvmpipe (LLVM 3.5, 128 bits) GLX Version: 3.0 Mesa 10.3.2
Audio:     Card Intel System Controller Hub (SCH Poulsbo) HD Audio Controller driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k3.19.1-antix.1-486-smp
Network:   Card-1: Realtek RTL8101E/RTL8102E PCI Express Fast Ethernet controller driver: r8169
           IF: eth0 state: down mac: 00:24:e8:cc:1b:a3
           Card-2: Broadcom BCM4312 802.11b/g LP-PHY driver: b43-pci-bridge
           IF: wlan0 state: down mac: 00:26:5e:3a:d4:57
Drives:    HDD Total Size: 160.0GB (1.6% used) ID-1: /dev/sda model: WDC_WD1600BEVT size: 160.0GB
Partition: ID-1: / size: 30G used: 2.4G (9%) fs: ext4 dev: /dev/sda7
Sensors:   System Temperatures: cpu: 46.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 103 Uptime: 4 min Memory: 105.1/996.1MB Client: Shell (bash) inxi: 2.2.16 
bill@antix15:~
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#45
Jon_J wrote:There is an error on boot. It didn't seem to be very serious.
The error is similar to this: fsck cannot run on this drive. no such file or directory. I'll have to write the exact error down and post it later.
Is the error in red? Do you remember if it comes before or after it says"The initrd init program took xx.xx seconds"? I've attached a screen shot which shows this message.