Segmentation fault wvdial on lfs

Oncom · 07-12-2016, 05:04 AM

I have problems when running wvdial in my lfs 7.9.

The following is a kernel config usb and my ppp.

Code:

#
# USB port drivers
#
CONFIG_USB_USS720=m
CONFIG_USB_SERIAL=m
CONFIG_USB_SERIAL_GENERIC=y
CONFIG_USB_SERIAL_SIMPLE=m
CONFIG_USB_SERIAL_AIRCABLE=m
CONFIG_USB_SERIAL_ARK3116=m
CONFIG_USB_SERIAL_BELKIN=m
CONFIG_USB_SERIAL_CH341=m
CONFIG_USB_SERIAL_WHITEHEAT=m
CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m
CONFIG_USB_SERIAL_CP210X=m
CONFIG_USB_SERIAL_CYPRESS_M8=m
CONFIG_USB_SERIAL_EMPEG=m
CONFIG_USB_SERIAL_FTDI_SIO=m
CONFIG_USB_SERIAL_VISOR=m
CONFIG_USB_SERIAL_IPAQ=m
CONFIG_USB_SERIAL_IR=m
CONFIG_USB_SERIAL_EDGEPORT=m
CONFIG_USB_SERIAL_EDGEPORT_TI=m
CONFIG_USB_SERIAL_F81232=m
CONFIG_USB_SERIAL_GARMIN=m
CONFIG_USB_SERIAL_IPW=m
CONFIG_USB_SERIAL_IUU=m
CONFIG_USB_SERIAL_KEYSPAN_PDA=m
CONFIG_USB_SERIAL_KEYSPAN=m
CONFIG_USB_SERIAL_KEYSPAN_MPR=y
CONFIG_USB_SERIAL_KEYSPAN_USA28=y
CONFIG_USB_SERIAL_KEYSPAN_USA28X=y
CONFIG_USB_SERIAL_KEYSPAN_USA28XA=y
CONFIG_USB_SERIAL_KEYSPAN_USA28XB=y
CONFIG_USB_SERIAL_KEYSPAN_USA19=y
CONFIG_USB_SERIAL_KEYSPAN_USA18X=y
CONFIG_USB_SERIAL_KEYSPAN_USA19W=y
CONFIG_USB_SERIAL_KEYSPAN_USA19QW=y
CONFIG_USB_SERIAL_KEYSPAN_USA19QI=y
CONFIG_USB_SERIAL_KEYSPAN_USA49W=y
CONFIG_USB_SERIAL_KEYSPAN_USA49WLC=y
CONFIG_USB_SERIAL_KLSI=m
CONFIG_USB_SERIAL_KOBIL_SCT=m
CONFIG_USB_SERIAL_MCT_U232=m
CONFIG_USB_SERIAL_METRO=m
CONFIG_USB_SERIAL_MOS7720=m
CONFIG_USB_SERIAL_MOS7715_PARPORT=y
CONFIG_USB_SERIAL_MOS7840=m
CONFIG_USB_SERIAL_MXUPORT=m
CONFIG_USB_SERIAL_NAVMAN=m
CONFIG_USB_SERIAL_PL2303=m
CONFIG_USB_SERIAL_OTI6858=m
CONFIG_USB_SERIAL_QCAUX=m
CONFIG_USB_SERIAL_QUALCOMM=m
CONFIG_USB_SERIAL_SPCP8X5=m
CONFIG_USB_SERIAL_SAFE=m
# CONFIG_USB_SERIAL_SAFE_PADDED is not set
CONFIG_USB_SERIAL_SIERRAWIRELESS=m
CONFIG_USB_SERIAL_SYMBOL=m
CONFIG_USB_SERIAL_TI=m
CONFIG_USB_SERIAL_CYBERJACK=m
CONFIG_USB_SERIAL_XIRCOM=m
CONFIG_USB_SERIAL_WWAN=m
CONFIG_USB_SERIAL_OPTION=m
CONFIG_USB_SERIAL_OMNINET=m
CONFIG_USB_SERIAL_OPTICON=m
CONFIG_USB_SERIAL_XSENS_MT=m
CONFIG_USB_SERIAL_WISHBONE=m
CONFIG_USB_SERIAL_SSU100=m
CONFIG_USB_SERIAL_QT2=m
CONFIG_USB_SERIAL_DEBUG=m

CONFIG_PPP=y
CONFIG_PPP_BSDCOMP=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_FILTER=y
CONFIG_PPP_MPPE=m
CONFIG_PPP_MULTILINK=y
CONFIG_PPPOE=m
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m

I get an error message "segmentation fault"

Code:

root [ ~ ]# wvdialconf 
Editing `/etc/wvdial.conf'.

Scanning your serial ports for a modem.

Modem Port Scan<*1>: S0   S1   S2   S3   
ttyUSB0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyUSB0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 9600 baud
ttyUSB0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyUSB1<*1>: ATQ0 V1 E1 -- ATQ0 V1 E1
ttyUSB1<*1>: failed with 2400 baud, next try: 9600 baud
ttyUSB1<*1>: ATQ0 V1 E1 -- ATQ0 V1 E1
ttyUSB1<*1>: failed with 9600 baud, next try: 9600 baud
ttyUSB1<*1>: ATQ0 V1 E1 -- OK
ttyUSB1<*1>: ATQ0 V1 E1 Z -- OK
ttyUSB1<*1>: ATQ0 V1 E1 S0=0 -- OK
ttyUSB1<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttyUSB1<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- ATQ0 V1 E1 S0=0 &C1 &D2
ttyUSB1<*1>: ATQ0 V1 E1 S0=0 &C1 +FCLASS=0 -- OK
ttyUSB1<*1>: Modem Identifier: ATI -- Manufacturer: ZTE INCORPORATED
ttyUSB1<*1>: Max speed is 9600; that should be safe.
ttyUSB1<*1>: ATQ0 V1 E1 S0=0 &C1 +FCLASS=0 -- OK
ttyUSB2<*1>: ATQ0 V1 E1 -- OK
ttyUSB2<*1>: ATQ0 V1 E1 Z -- OK
ttyUSB2<*1>: ATQ0 V1 E1 S0=0 -- failed with 2400 baud, next try: 9600 baud
ttyUSB2<*1>: ATQ0 V1 E1 S0=0 -- OK
ttyUSB2<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttyUSB2<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttyUSB2<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttyUSB2<*1>: Modem Identifier: ATI -- Model: MF180
ttyUSB2<*1>: Max speed is 9600; that should be safe.
ttyUSB2<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ttyUSB2<*1>: failed with 9600 baud, next try: 9600 baud
ttyUSB2<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK

Found a modem on /dev/ttyUSB1.
Modem configuration written to /etc/wvdial.conf.
ttyUSB1<Info>: Speed 9600; init "ATQ0 V1 E1 S0=0 &C1 +FCLASS=0"
ttyUSB2<Info>: Speed 9600; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
root [ ~ ]# wvdial
--> WvDial: Internet dialer version 1.61
--> Initializing modem.
--> Sending: ATZ
--> Sending: ATQ0
OK
--> Re-Sending: ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 +FCLASS=0
OK
--> Modem initialized.
Segmentation fault

whether additional configuration to run a USB modem?

business_kid · 07-12-2016, 09:02 AM

This can be a hassle with lfs.
Don't know why you have so many usb_serial modules. The 'CONFIG_' bits look otherwise OK. Wvdial-1.61 is stable code. Run

Code:

ldd /path/to/wvdial |grep found

and see if it throws up anything. The correct output is nothing. Otherwise, put a question mark over toolchain, or kernel and look for confirmation before doing major surgery. Does everything else work? Are you in the correct group?

Oncom · 07-13-2016, 06:18 PM

Quote:

Originally Posted by business_kid

This can be a hassle with lfs.
Don't know why you have so many usb_serial modules. The 'CONFIG_' bits look otherwise OK. Wvdial-1.61 is stable code. Run

Code:

ldd /path/to/wvdial |grep found

and see if it throws up anything. The correct output is nothing. Otherwise, put a question mark over toolchain, or kernel and look for confirmation before doing major surgery. Does everything else work? Are you in the correct group?

I've been compiling ppp, but still can not be found in the ppp module /lib/modules/4.4.2.

Image: https://s31.postimg.org/6u9fhcrjf/Sc...6_20_27_59.png

Code:

CONFIG_PPP=y
CONFIG_PPP_BSDCOMP=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_FILTER=y
CONFIG_PPP_MPPE=m
CONFIG_PPP_MULTILINK=y
CONFIG_PPPOE=m
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m

Code:

make
make modules_install
cp -v arch/x86/boot/bzImage /boot/vmlinuz-4.4.2-lfs-7.9
cp -v System.map /boot/System.map-4.4.2
cp -v .config /boot/config-4.4.2

when i check with modprobe

Code:

root [ / ]# modprobe -v ppp
modprobe: FATAL: Module ppp not found in directory /lib/modules/4.4.2

help me sir ..

business_kid · 07-14-2016, 01:09 AM

I your kernel you need to make "PPP Support" a module to have it in /lib/modules while you are compiling it in. What I think you will get is compiled in PPP, but some modules like ppp_this & ppp_that. The main PPP module is compiled in.
EDIT:

make make modules_install
cp -v arch/x86/boot/bzImage /boot/vmlinuz-4.4.2-lfs-7.9
cp -v System.map /boot/System.map-4.4.2
cp -v .config /boot/config-4.4.2

I would also take '-lfs-7.9' off the kernel t meet the suffix identical to the System.map suffix. That might prevent issues.

Oncom · 07-15-2016, 11:24 PM

Quote:

Originally Posted by business_kid

I your kernel you need to make "PPP Support" a module to have it in /lib/modules while you are compiling it in. What I think you will get is compiled in PPP, but some modules like ppp_this & ppp_that. The main PPP module is compiled in.
EDIT:

make make modules_install
cp -v arch/x86/boot/bzImage /boot/vmlinuz-4.4.2-lfs-7.9
cp -v System.map /boot/System.map-4.4.2
cp -v .config /boot/config-4.4.2

I would also take '-lfs-7.9' off the kernel t meet the suffix identical to the System.map suffix. That might prevent issues.

I have it installed but is not in / lib / modules

https://s31.postimg.org/6u9fhcrjf/Sc...6_20_27_59.png

root [ ~ ]# modprobe -v ppp
modprobe: FATAL: Module ppp not found in directory /lib/modules/4.4.2

Tim Abracadabra · 07-16-2016, 12:47 AM

When you configured your kernel (menuconfig?) did you
set PPP Support to M for module?. If not rebuild your kernel with that set.

Hope that clarifies and helps,
Tim

Oncom · 07-16-2016, 05:18 AM

Quote:

Originally Posted by Tim Abracadabra

When you configured your kernel (menuconfig?) did you
set PPP Support to M for module?. If not rebuild your kernel with that set.

Hope that clarifies and helps,
Tim

This occurred because of the possibility of bugs in the wvdial, I tried to switch to using ppp, but what happens when I run pon (provider name) still do not run my usb modem.

when I've done on PPPConfig configuration, this is a syslog mine when running pon (provider name).

Code:

Jul 14 23:36:33 oncom pppd[3567]: pppd 2.4.7 started by root, uid 0
Jul 14 23:36:34 oncom chat[3568]: abort on (BUSY)
Jul 14 23:36:34 oncom chat[3568]: abort on (NO CARRIER)
Jul 14 23:36:34 oncom chat[3568]: abort on (VOICE)
Jul 14 23:36:34 oncom chat[3568]: abort on (NO DIALTONE)
Jul 14 23:36:34 oncom chat[3568]: abort on (NO DIAL TONE)
Jul 14 23:36:34 oncom chat[3568]: abort on (NO ANSWER)
Jul 14 23:36:34 oncom chat[3568]: abort on (DELAYED)
Jul 14 23:36:34 oncom chat[3568]: send (ATZ^M)
Jul 14 23:36:34 oncom chat[3568]: expect (OK)
Jul 14 23:36:34 oncom chat[3568]: ATZ^M^M
Jul 14 23:36:34 oncom chat[3568]: OK
Jul 14 23:36:34 oncom chat[3568]:  -- got it
Jul 14 23:36:34 oncom chat[3568]: send (ATDT*99#^M)
Jul 14 23:36:34 oncom chat[3568]: expect (CONNECT)
Jul 14 23:36:34 oncom chat[3568]: ^M
Jul 14 23:36:34 oncom chat[3568]: ATDT*99#^M^M
Jul 14 23:36:34 oncom chat[3568]: NO CARRIER
Jul 14 23:36:34 oncom chat[3568]:  -- failed
Jul 14 23:36:34 oncom chat[3568]: Failed (NO CARRIER)
Jul 14 23:36:34 oncom pppd[3567]: Script /usr/sbin/chat -v -f /etc/chatscripts/3 finished (pid 3568), status = 0x5
Jul 14 23:36:34 oncom pppd[3567]: Connect script failed

business_kid · 07-17-2016, 01:13 AM

Quote:

Originally Posted by Oncom

I have it installed but is not in / lib / modules

https://s31.postimg.org/6u9fhcrjf/Sc...6_20_27_59.png

root [ ~ ]# modprobe -v ppp
modprobe: FATAL: Module ppp not found in directory /lib/modules/4.4.2

Not a lot of use, I'm afraid.
It's not about just having a module, but not having it compiled into the kernel.
You need to rebuild the kernel with PPP Support as a module & install that kernel.

Oncom · 07-17-2016, 05:30 AM

Quote:

Originally Posted by business_kid

Not a lot of use, I'm afraid.
It's not about just having a module, but not having it compiled into the kernel.
You need to rebuild the kernel with PPP Support as a module & install that kernel.

I had to compile the kernel with ppp as a module like this screenshot https://s31.postimg.org/yakn3xm23/Sc...8_00_16_04.png

when I run pound (provider name) and other tools wvdial does not work, this is my sys.log.

Code:

Jul 18 00:13:48 evan kernel: [  286.307290] wvdial[3621]: segfault at 20da8 ip b74fea0c sp bf8ea940 error 4 in libwvbase.so.4.6[b74cb000+83000]
Jul 18 00:14:05 evan pppd[3629]: pppd 2.4.7 started by root, uid 0
Jul 18 00:14:05 evan pppd[3629]: Removed stale lock on ttyUSB1 (pid 3621)
Jul 18 00:14:06 evan chat[3630]: abort on (BUSY)
Jul 18 00:14:06 evan chat[3630]: abort on (NO CARRIER)
Jul 18 00:14:06 evan chat[3630]: abort on (VOICE)
Jul 18 00:14:06 evan chat[3630]: abort on (NO DIALTONE)
Jul 18 00:14:06 evan chat[3630]: abort on (NO DIAL TONE)
Jul 18 00:14:06 evan chat[3630]: abort on (NO ANSWER)
Jul 18 00:14:06 evan chat[3630]: abort on (DELAYED)
Jul 18 00:14:06 evan chat[3630]: send (ATZ^M)
Jul 18 00:14:07 evan chat[3630]: expect (OK)
Jul 18 00:14:07 evan chat[3630]: ^M^M
Jul 18 00:14:52 evan chat[3630]: alarm
Jul 18 00:14:52 evan chat[3630]: send (AT^M)
Jul 18 00:14:52 evan chat[3630]: expect (OK)
Jul 18 00:14:58 evan chat[3630]: ^M^M^M
Jul 18 00:15:37 evan chat[3630]: alarm
Jul 18 00:15:37 evan chat[3630]: Failed
Jul 18 00:15:37 evan pppd[3629]: Script /usr/sbin/chat -v -f /etc/chatscripts/3 finished (pid 3630), status = 0x3
Jul 18 00:15:37 evan pppd[3629]: Connect script failed
Jul 18 00:15:38 evan pppd[3629]: Exit.
Jul 18 00:16:46 evan shutdown[3966]: shutting down for system reboot
Jul 18 00:16:46 evan init: Switching to runlevel: 6
Jul 18 00:16:52 evan NetworkManager[3314]: <info>  caught SIGTERM, shutting down normally.
Jul 18 00:16:52 evan NetworkManager[3314]: <info>  (eth0): device state change: disconnected -> unmanaged (reason 'unmanaged') [30 10 3]
Jul 18 00:16:52 evan NetworkManager[3314]: <info>  (wlan0): device state change: disconnected -> unmanaged (reason 'unmanaged') [30 10 3]
Jul 18 00:16:52 evan NetworkManager[3314]: <info>  (ttyUSB2): device state change: disconnected -> unmanaged (reason 'unmanaged') [30 10 3]
Jul 18 00:16:52 evan NetworkManager[3314]: <info>  exiting (success)
Jul 18 00:16:52 evan ModemManager[3353]: <warn>  Could not acquire the 'org.freedesktop.ModemManager1' service name 
Jul 18 00:16:52 evan ModemManager[3353]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> disabling) 
Jul 18 00:16:52 evan ModemManager[3353]: <info>  Caught signal, shutting down... 
Jul 18 00:16:52 evan kernel: Kernel logging (proc) stopped.
Jul 18 00:16:52 evan kernel: Kernel log daemon terminating.
Jul 18 00:16:53 evan exiting on signal 15

business_kid · 07-18-2016, 02:00 AM

Any log that starts with a segfault is unlikely to end in success.

Have you filed a bug in wvdial? That might be the quickest way to go.

Oncom · 07-24-2016, 07:36 AM

Quote:

Originally Posted by business_kid

Any log that starts with a segfault is unlikely to end in success.

Have you filed a bug in wvdial? That might be the quickest way to go.

I tried to switch from using pppconfig wvdial. and the error log above you can see for yourself.

business_kid · 07-25-2016, 12:49 AM

Don't get sidetracked. Implement post #8.

Oncom · 07-28-2016, 08:08 PM

Quote:

Originally Posted by business_kid

Don't get sidetracked. Implement post #8.

I run wvdial then I tried to see the error in dmesg

root [ / ]# dmesg | grep wvdial
wvdial[3578]: segfault at 20da8 ip b7482a0c sp bfedfe80 error 4 in
libwvbase.so.4.6[b744f000+83000]

business_kid · 07-29-2016, 01:43 AM

Have you rebuilt the kernel with PPP Support as a module?

Oncom · 07-29-2016, 03:28 AM

Quote:

Originally Posted by business_kid

Have you rebuilt the kernel with PPP Support as a module?

yes sir i've rebuild ppp as a module