Posts: 1,028
SamK
Joined: 21 Aug 2011

01 Dec 2015, 07:10 #16

rokytnji wrote:Microphone command I posted earlier spits out no sound (no reaction in terminal to voice test). Might have to tweak something on that.
A suggestion to help, temporarily set ALSA to an unconfigured state before running your test. Hint, make sure the microphone input is activated in alsamixer before starting.

Something along the following lines...


Verify sound is output without tweaking
Control Center-->Hardware-->Test Sound
or manually

Code: Select all

speaker-test --channels 2 --test wav --nloops 3
If the shipped ISO outputs sounds without modifying /etc/asound.conf, move on to the recording test.


Temporarily disable ALSA configuration

Code: Select all

sudo mv / etc/asound.conf / etc/asound.conf.DISABLED
Hint, command purposely malformed to work around forum bug. To use, remove the space between each occurrence of"/ etc"


Restart ALSA to commit the change

Code: Select all

sudo service alsa-utils restart

Test recording via the microphone input

Code: Select all

arecord --vumeter stereo --format dat test_recording.wav
CTRL+C to stop recording

Test play the recorded file

Code: Select all

aplay test_recording.wav

Alternatives
antiX-Full ships with SoX which can also record and play sounds via commands rec and play

Code: Select all

rec test_recording.wav
CTRL+C to stop recording

Code: Select all

play test_recording.wav
Posts: 1,028
SamK
Joined: 21 Aug 2011
#17
rokytnji wrote:Microphone command I posted earlier spits out no sound (no reaction in terminal to voice test). Might have to tweak something on that.
Continuing listing problems noticed with ALSA in antiX-15.1-a1.
Different results observed on the same hardware...

Booted live before installation
I've seen the live boot fail to detect the soundcard i.e. no audio at all

Booted from conventional hard disk installation
Vanilla installation (as shipped) without updates/upgrades applied
The soundcard is detected and works as expected
Posts: 1,139
masinick
Joined: 26 Apr 2008
#18
Hmm, sounds like I have to"carve out a bit of time" for a new antiX test release! I've been a lot busier this past year with much less time to devote to software testing (except on the paid job). I'll try to get some time to run this one through my two systems. Usually I do not encounter any hardware-software configuration issues on either of my 2007-2008 vintage laptop systems, but still, I'll try to find some time to test to make sure they still run great with the upcoming version.

Thanks for the efforts gentlemen! __{{emoticon}}__
Posts: 1,444
skidoo
Joined: 09 Feb 2012
#19
the dual entries on the grub2 boot screen
-- blahblah
-- blahblah (sysvinit)
presence of both those make sense for mx, but introduces confusion when someone boots antix
Posts: 32
bedna
Joined: 30 May 2015
#20
Crash

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://kernelultras.org/index.php?shell=feh%20/var/www/cesspool___zumpa/IMG_20151212_195651.jpg"
linktext was:"http://kernelultras.org/index.php?shell ... 195651.jpg"
====================================

Code: Select all

System:    Host: s29 Kernel: 4.0.5-antix.2-amd64-smp x86_64 (64 bit) Desktop: IceWM 1.3.8
           Distro: antiX-15-V_x64-full Killah P 30 June 2015
Machine:   Mobo: ASUSTeK model: M4N68T-M-V2 v: Rev X.0x Bios: American Megatrends v: 0402 date: 07/30/2010
CPU:       Single core AMD Athlon II X2 250 (-UP-) cache: 1024 KB speed: 3000 MHz (max)
Graphics:  Card: NVIDIA C61 [GeForce 7025 / nForce 630a]
           Display Server: X.Org 1.16.4 drivers: nouveau (unloaded: fbdev,vesa) Resolution: 1600x1200@60.00hz
           GLX Renderer: Gallium 0.4 on NV4C GLX Version: 2.1 Mesa 10.3.2
Audio:     Card NVIDIA MCP61 High Definition Audio driver: snd_hda_intel Sound: ALSA v: k4.0.5-antix.2-amd64-smp
Network:   Card: NVIDIA MCP61 Ethernet driver: forcedeth
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: 20:cf:30:b2:42:ab
Drives:    HDD Total Size: 812.6GB (33.3% used) ID-1: /dev/sda model: ST500LT012 size: 500.1GB
           ID-2: /dev/sdb model: ST3300622A size: 300.1GB ID-3: USB /dev/sdc model: USB_2.0_Flash size: 4.1GB
           ID-4: USB /dev/sdd model: Android_Phone size: 8.4GB
Partition: ID-1: / size: 20G used: 3.5G (19%) fs: ext4 dev: /dev/sda1
           ID-2: /home size: 343G used: 230G (71%) fs: ext4 dev: /dev/sda2
           ID-3: swap-1 size: 9.44GB used: 0.00GB (0%) fs: swap dev: /dev/sda7
           ID-4: swap-2 size: 4.09GB used: 0.00GB (0%) fs: swap dev: /dev/sdb6
Sensors:   System Temperatures: cpu: 36.0C mobo: 25.0C
           Fan Speeds (in rpm): cpu: 1467 sys-1: 0
Info:      Processes: 128 Uptime: 24 min Memory: 837.2/3703.7MB Client: Shell (bash) inxi: 2.2.31
Posts: 307
eugen-b
Joined: 23 Aug 2015
#21
Wishing to help skidoo to confirm the bug he found here misunderstanding-or-installer-bug-t6082.html , I tried to install first antiX 15 base 32bit, then after getting an unbootable system I tried to install antiX 15.1 base alpha1 64bit in several possible ways - every time I got either kernel panic or the following boot error:

Code: Select all

/scripts/init-top/udev : line 14 : can't create /sys/kernel/uevent_helper
Permission denied
Scanning for Btrfs filesystems
Gaveup waiting for root device. Common problems
- Boot args (cat /proc/cmdline)
- Check rootdelay= (...)
- Check root= (...)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/disk/by-uuid/e353... does not exist.
Propping to a shell!
modprobe: module ehci-orion not found in modules.dep
I will reboot to live USB to post my specs, here are those specs on Manjaro

Code: Select all

[eugen@manjaro ~]$ inxi /F
CPU~Dual core AMD Athlon X2 BE-2350 (-MCP-) speed/max~1000/2100 MHz Kernel~4.2.7-1-MANJARO x86_64 
Up~19 min Mem~569.0/3829.3MB HDD~36.1GB(52.5% used) Procs~170 Client~Shell inxi~2.2.31 
On this machine MX-15 installed without issues. I would suspect the 64bit kernel, but there was also an error with an older 32bit antiX 15 kernel. I'll describe the cases how I installed:
#1: antiX 15 base 32bit ISO, installed on HDD (logical) partition with btrfs, only root partition, no bootloader --> kernel panic
#2: antiX 15.1 base 64bit ISO, '' , '' , '' --> kernel panic
#3: '' , '' with ext4, '' , bootloader to root --> boot error see above
#4: '' , '' with btrfs, '' , bootloader to MBR --> boot error see above
#5: '' , on a primary partition with btrfs, '' , bootloader to MBR --> boot error ''
#6: '' , on a primary partition with ext4, '' , bootloader to MBR --> boot error ''

Feedback about look and feel: Many things have improved aestetically on Fluxbox (didn't test the others). I don't know the reason, maybe the icons in the menu. Today I tested Manjaro Deepin, it feels like a Porsche; antiX 15.1 feels like a small electric vehicle. I prefer the second.
Posts: 1,444
skidoo
Joined: 09 Feb 2012
#22
bedna,"module echi-orion not found"
Your hardware contains an unsupported Marvell"Orion" onboard USB host controller.
You may be able to boot successfully if you can disable that device in bios setup.
Later, you can find/install a suitable driver (or maybe the device is a secondary controller, providing extra USB ports, and is non-essential)
Posts: 307
eugen-b
Joined: 23 Aug 2015
#23
I have the same output"module echi-orion not found", thanks skidoo!
But it comes after some other errors, so I guess it won't solve my issue.
Darn, I have the same screen as bedna. And I first wrote down the text and then type it.
Posts: 1,444
skidoo
Joined: 09 Feb 2012
#24
eugen, I just noticed this detail:
"On this machine MX-15 installed without issues. I would suspect the 64bit kernel, but there was also an error with an older 32bit antiX 15 kernel."

Did antix previously (live) work on that same hardware? The problem you mention here, it only surfaced after installed to hdd?

Is MX is shipping a liquorix kernel?
Either that kernel has inbuilt orion driver or MX has bundled an orion driver into the distro.
So, smooth sailing for your hardware with MX either way (live or installed).
Posts: 32
bedna
Joined: 30 May 2015
#25
skidoo wrote:bedna,"module echi-orion not found"
Your hardware contains an unsupported Marvell"Orion" onboard USB host controller.
You may be able to boot successfully if you can disable that device in bios setup.
Later, you can find/install a suitable driver (or maybe the device is a secondary controller, providing extra USB ports, and is non-essential)
Thank you for your reply, skido. In antiX15 32bit and 64bit is supported.
Posts: 307
eugen-b
Joined: 23 Aug 2015
#26
skidoo wrote: Did antix previously (live) work on that same hardware? The problem you mention here, it only surfaced after installed to hdd?
Yes, it dit. How would I be able to post screenshots otherwise.
skidoo wrote: Is MX is shipping a liquorix kernel?
Yes, it does, but I was also able to install a 32bit version of MX-15 b1/2 on that machine.
skidoo wrote: Either that kernel has inbuilt orion driver or MX has bundled an orion driver into the distro.
So, smooth sailing for your hardware with MX either way (live or installed).
I'm testing antiX and MX on that machine, but I probably won't use it there as my daily OS. Nevertheless, I wish the team good luck so they would be able to fix the problem in the next alpha 2 release. These Thinkcentre PCs are cheap but reliable pieces of hardware, perfectly fit for antiX and MX.
I wasn't able to disable the USB etirely in BIOS, because I couldn't use my keyboard then to select antiX from my boot menu. Well with some effort I could try to make it the default OS in / etc/default/grub, but do I need to? I tried setting everything to USB 1.0, but it didn't help, same boot error.
Posts: 32
bedna
Joined: 30 May 2015
#27
Hi skidoo, returns support echi-orion from antiX15?
Posts: 1,444
skidoo
Joined: 09 Feb 2012
#28
"does the antix15 kernel support echi-orion?"
From what I see, no, it does not.
The config I checked is for the"4.3.0-antix.2-amd64-smp" kernel. I don't have the original antix15 kernel installed right now.
Posts: 32
bedna
Joined: 30 May 2015
#29
skidoo wrote:"does the antix15 kernel support echi-orion?"
From what I see, no, it does not.
The config I checked is for the"4.3.0-antix.2-amd64-smp" kernel. I don't have the original antix15 kernel installed right now.
My config in antiX15

Code: Select all

zcat /proc/config.gz | grep -i ehci
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_EHCI_TT_NEWSCHED=y
CONFIG_USB_EHCI_PCI=y
CONFIG_USB_EHCI_HCD_PLATFORM=y
Posts: 1,444
skidoo
Joined: 09 Feb 2012
#30
I don't know what else to say.


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://lmgtfy.com/?q=linux+echi-orion"
linktext was:"http://lmgtfy.com/?q=linux+echi-orion"
====================================


If inbuilt support for the orion driver existed, your kernel config would contain a line specifically mentioning"orion", like
CONFIG_USB_EHCI_HCD_ORION=y
or
CONFIG_USB_EHCI_HCD_ORION=m