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 Sat 23 Aug 2014, 13:32
All times are UTC - 4
 Forum index » House Training » Bugs ( Submit bugs )
Wary Puppy 5.1.4 - 29 August 2011
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 15 of 29 [425 Posts]   Goto page: Previous 1, 2, 3, ..., 13, 14, 15, 16, 17, ..., 27, 28, 29 Next
Author Message
Sage

Joined: 04 Oct 2005
Posts: 4781
Location: GB

PostPosted: Thu 11 Aug 2011, 10:07    Post subject:  

Wow! Thanks a A$bn, tp. Nice to know there's a guy around with all the answers. Seems I missed your blast last Feb. Wonder how many other folks are having this trouble? It was easy for me to fix with a drawer-full of alternative NICs, but there are quite a few guys who are less than keen to open their boxes, much less tackle surgery on their mainboard, being the only other option to a SW fix. Without your assistance, the latter would've been well outside my personal ambit.
Could be a show-stopper? What's BK think about it all?

Later: calling Houston.
Used Wary 5.1.2.7 on FULL installation.
Followed your recipe, tp. Initially, 8139cp was already listed as preferred over 8139too. Reversed/rebooted. Tried 'too' and 'cp' drivers - nogo
Reversed preferred order again. Tried both drivers, as well as ne2k-pci, tulip & e1000.
Nada.
Run out of ideas. This NIC works OK on other distros - I think/thought, but will check against boxloads of kit/liveCDs.

Ah! Guess tp may be abed at this hour?
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5234
Location: Australia

PostPosted: Thu 11 Aug 2011, 21:32    Post subject:  

Sage wrote:
8139cp was already listed as preferred over 8139too. Reversed/rebooted. Tried 'too' and 'cp' drivers - nogo
Reversed preferred order again.

What I suspect is happening is that both drivers have loaded, and are competing for the device. The modules-preference is supposed to prevent this, but we now know that the modules-preference is broken in Lucid, and Barry has recently mentioned that it should be fixed for Wary and Drake ... but maybe it's not??

If you want to solve the problem, you will need to take some aggressive technical action -
first remove all modules-preference entries relating to the 8139cp/8139too modules.

Now let's disable the 8139too driver - use ROX to go to /lib/modules/2.6.32/kernel/drivers/net and you will see "8139too.ko". Open a second ROX window, which should default to /root (~) and drag 8139too.ko into /root
Now run this command, which will "register" the new state of drivers -
Code:
depmod-FULL

Now reboot, and the 8139cp driver should automatically load, free from interference from the 8139too driver.
If the Network Wizard still doesn't show an ethernet interface, or the interface fails to connect, it would be worth running this command -
Code:
dmesg

and you might see something obviously wrong with how the 8139cp driver loaded ie. "8139cp: IRQ13 busy"

Of course, you could also reverse this situation - shift 8139cp.ko into /root (effectively disabling it) and shift 8139too.ko back into its correct location, then run the "depmod-FULL" command, and reboot.
Back to top
View user's profile Send private message 
Sage

Joined: 04 Oct 2005
Posts: 4781
Location: GB

PostPosted: Fri 12 Aug 2011, 07:38    Post subject:  

Thanks, again, tp. Working on it. Sometimes old kit exerts additional influences! Might not get an answer till tomorrow.
Back to top
View user's profile Send private message 
peebee


Joined: 21 Sep 2008
Posts: 1391
Location: Malvern, Worcs, UK

PostPosted: Fri 12 Aug 2011, 08:27    Post subject: [SOLVED] pwallpaper - new backgrounds  

SOLVED - it was a file naming problem - see later posts

Pwallpaper does not detect any new wallpapers put into /usr/share/backgrounds even after a reboot.

Nathan's wallpaper setter as used in other puppies does not have his problem.

cheers
peebee

_________________
LxPup-14.03 = Puppy + LXDE

Last edited by peebee on Tue 16 Aug 2011, 14:24; edited 1 time in total
Back to top
View user's profile Send private message 
Sage

Joined: 04 Oct 2005
Posts: 4781
Location: GB

PostPosted: Fri 12 Aug 2011, 09:56    Post subject:  

OK, tp - did all that, and some more.
Nothing good to report. At the end of dmesg one sees the cp driver (re)load but nothing useful about eth0. Manually loading drivers didn't work either.
In the meantime, I tried liveCD of Peppermint and PCL-LXDE. Neither could call up the 8139D.
Although I got the impression that the NIC was working previously, I am driven to the conclusion that either I was mistaken and/or it isn't any longer! I guess the fact that its little green led was alight also gave a false impression. Stuck in an 8139C - no problems.
Sorry to have exercised your talents to no effect, but I now have a crystal and relay in my spares box...

Ah, but wait a mo - vide infra.

Last edited by Sage on Fri 12 Aug 2011, 10:11; edited 1 time in total
Back to top
View user's profile Send private message 
Sage

Joined: 04 Oct 2005
Posts: 4781
Location: GB

PostPosted: Fri 12 Aug 2011, 09:59    Post subject:  

Quote:
Pwallpaper does not detect any new wallpapers put into /usr/share/backgrounds even after a reboot.

Oh yes it does, and without a reboot. Just used it to copy guyonabike - worked without a hitch.
Back to top
View user's profile Send private message 
Sage

Joined: 04 Oct 2005
Posts: 4781
Location: GB

PostPosted: Fri 12 Aug 2011, 10:19    Post subject:  

NIC grief continued:
Having replaced the 8139D with an 8139C, I now find that this blighter won't work with my FULL installation. Moreover, there's a boot error message about this cr*p old Gigabyte Intel board GA-6WMMC7 (833AMD with 398MbSDRAM) that flashes by, not in dmesg, during boot-up with the FULL but not the liveCD.
The C now works OK with the liveCD but not the FULL: the 8139D works with neither.
If you're confused? Can you imagine what it does to my mind! When it comes to code, the best I can do is follow instructions. When it comes to HW, that's different!
In the fullness of time, I might try the D NIC in another board - not Intel chipset!

Later:
Stuck in a Pulse H1138 NIC in the Gigabyte. Signs up in HardInfo as Intel 82557/8/9/0/1 Ethernet Pro 100 - flawless! The mystery deepens.
Back to top
View user's profile Send private message 
Aitch


Joined: 04 Apr 2007
Posts: 6825
Location: Chatham, Kent, UK

PostPosted: Fri 12 Aug 2011, 12:32    Post subject:  

Sage

Found this on the web...

Quote:
I Have making Realtek 8139D work with Mandriva One 2008.0
Mandriva will detect it and uses sc92031 module driver as the driver.
put this line in /etc/modprobe.conf

Code:
alias eth0 sc92031


also referenced here, including possible acpi intereference....

http://murga-linux.com/puppy/viewtopic.php?t=34881


HTH

Aitch Smile
Back to top
View user's profile Send private message 
Sage

Joined: 04 Oct 2005
Posts: 4781
Location: GB

PostPosted: Fri 12 Aug 2011, 13:49    Post subject:  

Good sleuthing, A. Will try it tomorrow as have other projects underway at present.
Back to top
View user's profile Send private message 
zaivala

Joined: 21 Mar 2011
Posts: 117

PostPosted: Fri 12 Aug 2011, 19:07    Post subject: Black Screen
Subject description: Boots, but...
 

I downloaded Wary 5.1.2 a couple days ago, burned it to a CD (my ancient lappy won't boot from USB), and ran it (as a Live CD). It looked pretty good. Did some setup and a couple reboots...

On about the third reboot, and from then on, it boots to a black screen with a mouse X. The mouse works, but there's nothing for it to work on. There is a small icon top left which says I'm connected to the Internet. That's it.

Any ideas what I'm doing wrong or how to fix it? I also run MacPup this way and it works great.
Back to top
View user's profile Send private message 
rjbrewer


Joined: 22 Jan 2008
Posts: 4422
Location: merriam, kansas

PostPosted: Fri 12 Aug 2011, 21:09    Post subject:  

Full install attempts of 5.1.2.7 on my laptop ended with a long
loading modules count while booting, and no sound, network or
usb modules to be found.

Eventually traced the problem to the logical partitions on the hard
drive.

Nuked and tested the drive; reinstalled Xp and Wary > Luci to
new set of logical partitions and everything works fine now.

_________________

Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs

Back to top
View user's profile Send private message 
Sage

Joined: 04 Oct 2005
Posts: 4781
Location: GB

PostPosted: Sat 13 Aug 2011, 02:20    Post subject:  

So far, not so good! None of the NIC driver-o-centric expedients worked. Swapped over to an old Soltek board. The Pulse NIC signing on as 'Intel' brought the entire board to a dead stop. None of the driver fixes worked with the 8139C nor D. Will look into the acpi and apic issues later.
All this suggests that issues remain for older kit. Most boards with onboard NICs seem to work although the ones I possess in this category are mostly later products, except, as I recall, earlier MSI boards with onboard Realtek all worked.
Back to top
View user's profile Send private message 
BarryK
Puppy Master


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

PostPosted: Sat 13 Aug 2011, 02:53    Post subject:  

Wary 5.1.3 released.

I decided not to do an RC, go straight to release. Blog announcement:

http://bkhome.org/blog/?viewDetailed=02399

_________________
http://bkhome.org/news/
Back to top
View user's profile Send private message Visit poster's website 
Sage

Joined: 04 Oct 2005
Posts: 4781
Location: GB

PostPosted: Sat 13 Aug 2011, 04:36    Post subject:  

This morning, decided to concentrate on the Soltek board and the 8139C as the most likely to yield a result. I was wrong - neither acpi nor apic boot codes helped. However, received some interesting messages which may assist tp in some further diagnosis? With the BootManager preferences for cp& too completely removed, then trying to manually load a driver, got FatalError for 8139too and claim that 8139cp already loaded ! Unexpected result. Seems that Wary is determined to load 8139cp regardless, with all the above discussed parameters removed or negated. Despite 8139cp being loaded, the no new interface message still pops up. Seems that some additional action is required to stop 8139C being loaded by default? The coding gurus will know what this action is - probably?!
Sorry to paste this up immediately following BKs important announcement.

Update: see that the above combo has eth0 alive with BK's Wary 5.1.3 liveCD. Ran the FULL install - 8139C is alive. No acpi/apic boot parameters needed, no manual connect needed. BootManager shows cp:too preference, but eth0 is loaded as 8139too.
Seems that BK has intentionally or inadvertently stopped 8139cp preventing 8139too from loading, with 8139too being correctly ID-ed and auto-loaded, despite the BootManager. All very curious. Tp or BK care to comment?

Later still: BINGO - the 8139D NIC is also running with Wary 5.1.3 without human interaction. It, also, signs on as 8139too. Seems that quite a few other distros need to adjust something? Kernel?
Back to top
View user's profile Send private message 
BarryK
Puppy Master


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

PostPosted: Sat 13 Aug 2011, 06:41    Post subject:  

Sage wrote:
Update: see that the above combo has eth0 alive with BK's Wary 5.1.3 liveCD. Ran the FULL install - 8139C is alive. No acpi/apic boot parameters needed, no manual connect needed. BootManager shows cp:too preference, but eth0 is loaded as 8139too.
Seems that BK has intentionally or inadvertently stopped 8139cp preventing 8139too from loading, with 8139too being correctly ID-ed and auto-loaded, despite the BootManager. All very curious. Tp or BK care to comment?

Later still: BINGO - the 8139D NIC is also running with Wary 5.1.3 without human interaction. It, also, signs on as 8139too. Seems that quite a few other distros need to adjust something? Kernel?


Why have you stated "despite the BootManager"? The entry in variable PREFLIST in file /etc/rc.d/MODULESCONFIG has:

Code:
#PREFLIST: sometimes there are two hits, that is, two modules match the same
#'modalias' (that is, they are both claiming the same hardware). In such a case,
#here we can specify a preference. Each entry here is of the form
#'module1:module2' where module2 is the preferred choice.
#101218 format can have multiple ':', ex: 8139cp:8139too:8139xx (last is most preferred).
#note, list needs a space char at beginning and at end.
#w471 removed: ath5k:ath_pci martian_dev:ltserial r8169:r8101
#101209: added 8139cp:8139too  110204 modified
PREFLIST=' 8139cp:8139too rtl8180:r8180 rtl8187:r8187 rt2500usb:rt73usb orinoco_nortel:hostap_plx orinoco_plx:hostap_plx orinoco_tmd:hostap_plx orinoco_pci:hostap_pci bcm43xx:ssb prism54:p54pci tulip:dmfe option:hso hcfpcihw:hsfpcibasic2 cdc_acm:dgcusbdcp slamr:snd_intel8x0m:snd_via82xx_modem '


In other words, 8139too is the preferred driver.

Isn't that what you want, and that's what you have got?

_________________
http://bkhome.org/news/
Back to top
View user's profile Send private message Visit poster's website 
Display posts from previous:   Sort by:   
Page 15 of 29 [425 Posts]   Goto page: Previous 1, 2, 3, ..., 13, 14, 15, 16, 17, ..., 27, 28, 29 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » House Training » Bugs ( Submit bugs )
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1013s ][ Queries: 13 (0.0117s) ][ GZIP on ]