Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Wed 01 Oct 2014, 16:21
All times are UTC - 4
 Forum index » House Training » Bugs ( Submit bugs )
Wary 0.9.8 (098) feedback
Moderators: Flash, Ian, JohnMurga
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
Page 12 of 15 Posts_count   Goto page: Previous 1, 2, 3, ..., 10, 11, 12, 13, 14, 15 Next
Author Message
rerwin


Joined: 24 Aug 2005
Posts: 1517
Location: Maine, USA

PostPosted: Mon 22 Nov 2010, 00:37    Post_subject: modprobe_protect patch for Intel537 module timeout  

Barry,
I have been concerned about the timeout of the Intel537 module showing up in the protect.log. Somehow, the modules.dep did not get/stay updated with the variant choice, something I need to investigate further. To prevent the timeout in such a case, I would like to insert a line into the script. Considering that the RC is approaching, I am describing the fix here, instead of making a package for it.

In /sbin/pup_event_backend_modprobe_protect, near the beginning of the "--modcheck=" case, please insert a line after line 110:
Code:
 --modcheck=*)
  ENTITY="" #make visible here
  check_entity_claimed_func M || exit 1
  check_entity_claimed_func R && exit 1
  [ "`lsmod | grep "^$ENTITY "`" != "" ] && exit 0
  grep -q "^install $ENTITY /bin/true" /etc/modprobe.d/* && exit 1 #101008
  grep -q "/$ENTITY\.ko" /lib/modules/`uname -r`/modules.dep || exit 1 #101121
  sleep 1
  MAXRETRIES=90; RETRIES=1
It is the line annotated by "#101121" (line 7 above). That responds with "module not loaded".

The good news is that, while the welcome window mouseover popup had not appeared at bootup, with the fix, it returns! That might be what you were impacted by when you discovered the "woof woof" issue.

With this fix, the welcome should appear, but the connect wizard may show "no modem found", or the last device detected previously. I suspect that the workaround is CHOOSE-ERASE and then reboot. In my case, none of the variants had been selected, probably as a result my experimentation. Maybe there is some way the selection gets skipped; I will investigate. But this fix will lessen the impact. Thank you.
Richard
Back to top
View user's profile Send_private_message 
bignono1


Joined: 17 May 2009
Posts: 362
Location: New ME

PostPosted: Mon 22 Nov 2010, 02:33    Post_subject:  

Please check the download link,it is not working.
Back to top
View user's profile Send_private_message 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 7047
Location: Perth, Western Australia

PostPosted: Mon 22 Nov 2010, 03:32    Post_subject: Re: modprobe_protect patch for Intel537 module timeout  

rerwin wrote:
Barry,
I have been concerned about the timeout of the Intel537 module showing up in the protect.log. Somehow, the modules.dep did not get/stay updated with the variant choice, something I need to investigate further. To prevent the timeout in such a case, I would like to insert a line into the script. Considering that the RC is approaching, I am describing the fix here, instead of making a package for it.

In /sbin/pup_event_backend_modprobe_protect, near the beginning of the "--modcheck=" case, please insert a line after line 110:
Code:
 --modcheck=*)
  ENTITY="" #make visible here
  check_entity_claimed_func M || exit 1
  check_entity_claimed_func R && exit 1
  [ "`lsmod | grep "^$ENTITY "`" != "" ] && exit 0
  grep -q "^install $ENTITY /bin/true" /etc/modprobe.d/* && exit 1 #101008
  grep -q "/$ENTITY\.ko" /lib/modules/`uname -r`/modules.dep || exit 1 #101121
  sleep 1
  MAXRETRIES=90; RETRIES=1
It is the line annotated by "#101121" (line 7 above). That responds with "module not loaded".

The good news is that, while the welcome window mouseover popup had not appeared at bootup, with the fix, it returns! That might be what you were impacted by when you discovered the "woof woof" issue.

With this fix, the welcome should appear, but the connect wizard may show "no modem found", or the last device detected previously. I suspect that the workaround is CHOOSE-ERASE and then reboot. In my case, none of the variants had been selected, probably as a result my experimentation. Maybe there is some way the selection gets skipped; I will investigate. But this fix will lessen the impact. Thank you.
Richard


Richard,
My to-do list has grown long again, and the next Wary will not be RC, and it is falling back a bit. The next release will be another beta, and may not come out for up to a week or so.

_________________
http://bkhome.org/news/
Back to top
View user's profile Send_private_message Visit_website 
Sage

Joined: 04 Oct 2005
Posts: 4790
Location: GB

PostPosted: Mon 22 Nov 2010, 03:48    Post_subject:  

rerwin:
These issues are not restricted to Barry, nor to Winmodems/whatever. The failure of 'woof,woof', the non-appearance of the 'welcome' overlay, muted sound, etc., etc., are being reported by a wide range of our correspondents. Testing on a single machine will, in my experience, not suffice. The adverse effects are very new. My investigations with over a dozen boards, new and old, suggest that the effects are highly irreproducible, albeit heavily skewed towards the non-functional side. Notwithstanding, older systems seem less prone to some of the problems, although this might be subjective or small-sample slewed? Some combinations of the features not generally reported affect FULL installations in different, but irreproducible ways, eg settings not retained. I NEVER use Win/3G/USB modems - their interference with Linux systems is legendary; attempting, however successfully, to make these devices function should be regarded as an intellectual exercise alone. Rigour suggests that these are a red herring and should be disconnected in order to address the more fundamental issue that has now emerged.
All efforts to fix the present undesirable situation are welcome because Wary is proving to be a fantastic distro for old kit, for which it is/was intended. If it also works on new stuff, that should be regarded as a bonus - saving the planet must always take precedent!
Back to top
View user's profile Send_private_message 
rerwin


Joined: 24 Aug 2005
Posts: 1517
Location: Maine, USA

PostPosted: Mon 22 Nov 2010, 10:48    Post_subject:  

Sage,
Thank you for laying it all out, there, about the sound issues. I was afraid I might be walking into a buzzsaw when I dared tinker with the ALSA initialization script, to pace it based on events instead of waiting regardless. I am responding to Barry's implication that the "protect" function, that attempts to ensure related operations occur in a predictable sequence where necessary, was at fault.

I over-promised when I suggested that I offer to resolve all sound problems. My attention to the init script is unrelated to modems, but to protect the reputation of the "protect" service as totally dependable.

The other issue I addressed was the intermittant detection of the sound card reported by zekebaby. My fix apparently resolved that. My goal there is simply that the script wait no longer than necessary to ensure it has what it needs to function.

BTW, I, too, have an issue with the cs4236 driver that my Aptiva seems to use. Not only does it not produce any sound, but on shutdown/reboot it spews trace lines implying an error, but that part scrolls away before I can see it. So, other that tightening up the start of the initialization script, I leave everything related to the ALSA wizard to Barry, as I normally do not need sound, nor understand much about linux support of it.
Richard
Back to top
View user's profile Send_private_message 
rerwin


Joined: 24 Aug 2005
Posts: 1517
Location: Maine, USA

PostPosted: Tue 23 Nov 2010, 16:46    Post_subject: Small contribution to solving sound issues  

I think I have sorted out the factors behind Barry's missing-welcome-woofwoof concern with his Agere modem. While it seemed to be triggered by the implementation of what I call "event gated pacing" of the ALSA initialization script, there was an underlying problem that appears to have been responsible. When I recreated CD booting, I also found that loading of a module timed out.

In my tests, I used my Intel537 modem, which is handled similarly to the Ageres. It was the Intel537 driver that failed to load. I found that the modules.dep entries for the agrmodem and intelmodem variants were not as designed. Consequently, the wrong variant was loaded for my 537EP card, which killed its loading. Modules.dep contained entries for all of the variants, instead of a selected one. Here's why:
Quote:
intelmodem/537SP/Intel537.koHIDE:
intelmodem/537EP/Intel537.koHIDE:
intelmodem/537EA/Intel537.koHIDE:
intelmodem/537/Intel537.ko:
intelmodem/536EP/Intel536.ko:
. . .
agrmodem/11c11040/agrserial.ko:
agrmodem/11c11040/agrmodem.ko: initrd/kernel/drivers/usb/core/usbcore.ko kernel/sound/pci/hda/snd-hda-codec.ko kernel/sound/core/snd-pcm.ko kernel/sound/core/snd-page-alloc.ko kernel/sound/core/snd-timer.ko kernel/sound/core/snd.ko kernel/sound/soundcore.ko
agrmodem/06pci/agrserial.koHIDE:
agrmodem/06pci/agrmodem.koHIDE: kernel/sound/core/snd.ko kernel/sound/soundcore.ko
agrmodem/048pci/agrserial.koHIDE: agrmodem/11c11040/agrmodem.ko initrd/kernel/drivers/usb/core/usbcore.ko kernel/sound/pci/hda/snd-hda-codec.ko kernel/sound/core/snd-pcm.ko kernel/sound/core/snd-page-alloc.ko kernel/sound/core/snd-timer.ko kernel/sound/core/snd.ko kernel/sound/soundcore.ko
agrmodem/048pci/agrmodem.koHIDE:
The busybox depmod selects anything with the suffix beginning with .ko! This is the state of modules.dep on first boot from a CD.

I created a fix for this that uses, instead, the suffix ".HIDE", which does not confuse busybox depmod, and modified the agrsm and intel537ep firmware pinstall scripts accordingly. It is "6-delta" on my page 4 posting of modem updates.
http://www.murga-linux.com/puppy/viewtopic.php?p=467639#467639

Package "-6-delta" is an addition to "-5" (since that is now in woof). It also contains a log message for the case where a module is checked (waited for) but is not in the modules.dep file, meaning it never actually started to load. The "protect" function so indicates to the caller, instead of waiting until timeout.

This is my best shot at eliminating some of the intermittent nature of sound card detection, by waiting for a sound driver to be loaded, before starting ALSA. I hope zekebaby can verify that it helps.
Richard
Back to top
View user's profile Send_private_message 
rerwin


Joined: 24 Aug 2005
Posts: 1517
Location: Maine, USA

PostPosted: Tue 23 Nov 2010, 17:39    Post_subject: Intel537 and SmartLink PCI modems not working  

Now that I have concluded my obsession with "module variants", I need to report issues with my above-named modems. The 537 starts to connect to the ISP, but claims "No dialtone". It works fine in 4.3.1+. The SmartLink does the repeating "NO CARRIER" thing, spewing connect-no-carrier sequences until manually disconnected.

The message log for the Intel contains this, FWIW:
Quote:
Nov 23 10:29:05 puppypc user.info kernel: Intel 537EP card found
Nov 23 10:29:05 puppypc user.err kernel: 537ep:softcore_init_struct: driver serial already allocated device.
Nov 23 10:29:05 puppypc user.warn kernel: 537ep:softcore_init_struct: Unregistering serial driver.
Nov 23 10:29:05 puppypc user.info kernel: serial 0000:00:0a.0: PCI INT A disabled


I don't have solutions, but want to have this documented.
Richard

EDIT: On the other hand, my Intel 536 modem connects just fine.

Edited_time_total
Back to top
View user's profile Send_private_message 
tempestuous

Joined: 10 Jun 2005
Posts: 5263
Location: Australia

PostPosted: Tue 23 Nov 2010, 20:12    Post_subject:  

rerwin wrote:
The 537 starts to connect to the ISP, but claims "No dialtone".

I'm out of touch with Puppy's current dialup regime. Is the dialup connection done with pppd, or with wvdial?
I had that same problem several years ago (using a hardware modem, not soft modem).
The solution was to configure wvdial to not wait for dialtone.
The relevant configuration line in wvdial.conf is "Dial Command = ATDP"
Change it to "Dial Command = ATX3DT"
Back to top
View user's profile Send_private_message 
glenco

Joined: 14 May 2010
Posts: 38
Location: Milwaukee

PostPosted: Tue 23 Nov 2010, 23:30    Post_subject:  

tempestuous
Pupdial already defaults to the ATX3DT command in WARY.
Back to top
View user's profile Send_private_message 
rerwin


Joined: 24 Aug 2005
Posts: 1517
Location: Maine, USA

PostPosted: Wed 24 Nov 2010, 00:16    Post_subject:  

Tempestuous, glenco,
Thanks for the suggestion. I tried "unchecking" "Check dialtone" (which generates the "X3") just now, but instead of stopping at "NO DIALTONE", wvdial waits a minute after dialing, times out, then displays repeated NO CARRIER sequences until I disconnect.
Richard
Back to top
View user's profile Send_private_message 
Sit Heel Speak


Joined: 30 Mar 2006
Posts: 2595
Location: downwind

PostPosted: Wed 24 Nov 2010, 23:08    Post_subject: posted: makedepend for the wary-098 devx
Sub_title: this should be in the devx
 

Hi Barry,

makedepend is missing from the wary-098 devx, it is necessary for the compile of mesa-6.5.2.

Here is a .pet, compiled under wary-098.

Source:
http://xorg.freedesktop.org/releases/individual/util/makedepend-1.0.3.tar.bz2
29-Oct-2010 22:47 121K

Procedure:
CFLAGS= '-o2 -march=i486 -mtune=i486'
./configure --prefix=/usr
make
make check (1 test passed OK)
new2dir make install
(manually deleted the man file; 'strip --strip-unneeded *' has no effect on the binary)
dir2pet makedepend-1.0.3-i486

Philip
makedepend-1.0.3-i486.pet.gz
Description  makedepend-1.0.3-i486.pet for the devx of wary-098
gz

 Download 
Filename  makedepend-1.0.3-i486.pet.gz 
Filesize  12.53 KB 
Downloaded  392 Time(s) 
Back to top
View user's profile Send_private_message 
shinobar


Joined: 28 May 2009
Posts: 2630
Location: Japan

PostPosted: Thu 25 Nov 2010, 02:43    Post_subject: Unetbootin fails to boot up Wary  

@Barry
Reported regarding Luci-238, but i confirmed Wary-098 also has the same problem.
It failes because of the 'pmedia=cd' option. Replacing 'pmedia=cd' to 'pmedia=usbflash' got success.

I remember the 'pmedia=cd' option searched all the media including usb devices. See the post:
http://www.murga-linux.com/puppy/viewtopic.php?p=470545#470545

BTW, why you get back to underscore instead of minus for the name of main sfs files? 'wary_098.sfs' instead of 'wary-098.sfs'.

_________________
Google Chrome portable
Downloads for Puppy Linux http://shino.pos.to/linux/downloads.html
Back to top
View user's profile Send_private_message Visit_website 
rerwin


Joined: 24 Aug 2005
Posts: 1517
Location: Maine, USA

PostPosted: Thu 25 Nov 2010, 11:57    Post_subject:  

I hope I have made my final revision to the modem_update...-6 package: http://www.murga-linux.com/puppy/viewtopic.php?p=467639#467639
1. It addresses Barry's issues with ttyUSB1 being detected instead of ttyUSB3, always picking the highest number as the data port.
2. It removes the E160E mode-switch and module-loading rules described as interfering rather than helping. Any mode switching is probably handled elsewhere.
3. It "fleshes out" the new capability to load (wireless) modem drivers for modems retaining their modem-state across reboots.
Richard
Back to top
View user's profile Send_private_message 
Sit Heel Speak


Joined: 30 Mar 2006
Posts: 2595
Location: downwind

PostPosted: Thu 25 Nov 2010, 13:28    Post_subject: wary 098: compiled forcedeth doesn't work, from bkhome does  

An oddity, I'm curious what the explanation is.

I just compiled the wary-098 kernel, with the only change to .config being an attempt to enable configfs and cgroups via changes to 3 sections in make menuconfig as detailed in the three screencaps here.

But then I changed my mind and decided to boot using the "stock" kernel. However, all the drivers the compile produced under
/lib/modules are still there.

The forcedeth.ko (reverse-engineered nVidia integrated NIC driver) which the compile produced, will not load.

And yet the forcedeth.ko available inside

http://bkhome.org/sources/kernel-2.6.31.14/BINARIES/2.6.31.14.tar.gz

does load.

Has anyone an explanation?

I am compiling in a frugal wary-098 install to HDD with a 10 G savefile (9.7 G free),
and
kernel_src-2.6.31.14-patched.sfs
and
wary_devx_098.sfs
are mounted by Boot Manager.
Back to top
View user's profile Send_private_message 
Sit Heel Speak


Joined: 30 Mar 2006
Posts: 2595
Location: downwind

PostPosted: Thu 25 Nov 2010, 14:50    Post_subject: wary-098 --can't compile mesa, the X headers are borked?  

Hmm...probably something I miss in simple ignorance, but...

I can add makedepend to the devx.
I can fix /usr/include/limits.h.
I can link other headers where mesa-6.5.2 thinks they ought to be.
I can add the missing matypes.h from mesa-6.5.1.

...but when I'm faced with this many broken X headers in
xorg73_base_t2_DEV-7.3-w5.pet...

http://i54.tinypic.com/14m3r6o.jpg

...I am strongly encouraged to "attack in another direction," as the Marines say.

Maybe Lighthouse, maybe Joe's Slackware Puppy, maybe (*shudder*) Lucid.

Or maybe it's time to (*tosses off a two-finger shot of Laphroaig*) do my own CLFS Puppy?
Back to top
View user's profile Send_private_message 
Display_posts:   Sort by:   
Page 12 of 15 Posts_count   Goto page: Previous 1, 2, 3, ..., 10, 11, 12, 13, 14, 15 Next
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
 Forum index » House Training » Bugs ( Submit bugs )
Jump to:  

Rules_post_cannot
Rules_reply_cannot
Rules_edit_cannot
Rules_delete_cannot
Rules_vote_cannot
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1098s ][ Queries: 12 (0.0068s) ][ GZIP on ]