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 Tue 25 Nov 2014, 20:21
All times are UTC - 4
 Forum index » House Training » Bugs ( Submit bugs )
4.3 Beta 1 -- bugs and reports
Moderators: Flash, Ian, JohnMurga
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
Page 8 of 13 Posts_count   Goto page: Previous 1, 2, 3, ..., 6, 7, 8, 9, 10, 11, 12, 13 Next
Author Message
01micko


Joined: 11 Oct 2008
Posts: 7841
Location: qld

PostPosted: Wed 19 Aug 2009, 04:54    Post_subject:  

Just testing Firefox alpha "Namarooka" (codename) and it works fine so far in 4.3 beta 1- k 2.6.29.6 Smile

Guess it's a firefox problem (or mozilla-1.9.1 source problem?) with these later kernels.

Cheers and be patient Laughing

edit; A post on Barry's Blog reports that it is a unionfs problem with firefox.

Edited_time_total
Back to top
View user's profile Send_private_message Visit_website 
veronicathecow


Joined: 21 Oct 2006
Posts: 535

PostPosted: Wed 19 Aug 2009, 05:25    Post_subject:
Sub_title: MP4 not linked to Gxine 4.3 beta 1- k 2.6.29.6
 

MP4 not linked to Gxine 4.3 beta 1- k 2.6.29.6
Plays fine but no link.

Edited_time_total
Back to top
View user's profile Send_private_message 
veronicathecow


Joined: 21 Oct 2006
Posts: 535

PostPosted: Wed 19 Aug 2009, 05:27    Post_subject:
Sub_title: BBCi catchup requires Flash 9.0115 or higher
 

BBCi catchup requires Flash 9.0115 or higher
Back to top
View user's profile Send_private_message 
veronicathecow


Joined: 21 Oct 2006
Posts: 535

PostPosted: Wed 19 Aug 2009, 05:32    Post_subject: Cups and Samsung 2510  

Cups and Samsung 2510 not printing test page. Works on PCLinux with SpliX 2.0.0
This Puppy seems the snappiest so far on my Intel Atom
Thanks for all the hard work
Tony
Back to top
View user's profile Send_private_message 
charlie6


Joined: 30 Jun 2008
Posts: 1021
Location: South of Belgium

PostPosted: Wed 19 Aug 2009, 05:39    Post_subject:
Sub_title: "libusb speedup error" using Xsane on Canon scanner
 

Hi,
on puppy4.3beta-k.2.6.29 frugal booting on live-cd (grub problem...! see a few posts above)
I have installed the ...1.10... and pixam-MP150 -.pet files given here
http://www.murga-linux.com/puppy/viewtopic.php?search_id=47754986&t=42703
and have connected a MP160 Canon mutlifonction (which works nice on Puppy412 with the same pets installed).
I got this:
Code:

# scanimage -L
device `pixma:04A91714_F30F67' is a CANON Canon PIXMA MP160 multi-function peripheral
# scanimage > mypicture.pnm
error - libusb speedup error handling needs improvement
error - libusb speedup error handling needs improvement
error - libusb speedup error handling needs improvement
error - libusb speedup error handling needs improvement
error - libusb speedup error handling needs improvement
error - libusb speedup error handling needs improvement
error - libusb speedup error handling needs improvement
error - libusb speedup error handling needs improvement
error - libusb speedup error handling needs improvement
error - libusb speedup error handling needs improvement
error - libusb speedup error handling needs improvement
error - libusb speedup error handling needs improvement
error - libusb speedup error handling needs improvement
error - libusb speedup error handling needs improvement
scanimage: sane_read: Error during device I/O
#
 handling needs improvement
scanimage: sane_read: Error during device I/O
#


looking at libusb (using PFind): there are more libusb present on Puppy412 than on the current Pup43bK2.6.29

Running Xsane:
no file is loaded / have to wait a longlonglong time before taking hand again (on a previous trial I simply killed the process...as it seemed so long to me...)

Hope this helps

Cheers
Charlie
Back to top
View user's profile Send_private_message 
Kenny-M


Joined: 15 May 2009
Posts: 147
Location: United States

PostPosted: Wed 19 Aug 2009, 07:55    Post_subject:  

Charlie6,

""while running the PUI, the choice of the partition to install Puppy was proposed on "ext4 partition" (sda3 is announced in PUI as an "ext4 partition" whereas GParted confirms it is an ext3 partition)...!!??? ""

I think this is already a well known problem. Have not seen a solution.

I am testing 4.3Beta1.k2.6.25.16 SCSI

_________________
Puppy 4.2.1 SeaMonkey on 160GB Ext USB Disk on Dell 745 SFF.
Puppy 4.3.0-SCSI on Dell Precision 610 workstation.
Puppy 4.2.1 running on Windows XP under Qemu.
Back to top
View user's profile Send_private_message 
Ray MK


Joined: 05 Feb 2008
Posts: 766
Location: UK

PostPosted: Wed 19 Aug 2009, 10:09    Post_subject:  

Hi

Just for your info - switched from dpupE to dpupG and it seems to boot noticeably faster and appears generally snappier - nice.

Everything seems ok to a n00bie - file copying, internet set-up and browsing - and a slightly prettier presentation.

As always - many thanks for all your work.

Very best regards - Ray
Back to top
View user's profile Send_private_message 
Jim1911

Joined: 19 May 2008
Posts: 2457
Location: Texas, USA

PostPosted: Wed 19 Aug 2009, 16:55    Post_subject:  

Just a note about an ext4 partition that was sized and formatted by the Gparted on this release. I have installed Ubuntu karmic (development branch), kernel 2.6.31-6-generic on this partition (without allowing Ubuntu to format it) and it's running fine.

Puppy is becoming more friendly with ext4.
Back to top
View user's profile Send_private_message 
rerwin


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

PostPosted: Thu 20 Aug 2009, 00:07    Post_subject: Wireless modem support update
Sub_title: Script changes support hybrid-device modems and other refinements
 

Barry,
I am attaching my latest script updates for wireless modems. They include moving the APN field in pupdial to the individual accounts, allowing use of pulse dialing in pupdial (ATDP), limiting PIN issuance to the first connection, to avoid disruptive error states on subsequent use. In addition, I added handling of the special case of hybrid devices, which I discuss below.

I have made the scripts ready for substitution, so you should not need to edit them unless you object to some code. They are in a dotpet, so users can try them immediately. The difference listings are in the tarball.

About the hybrids:
The script /sbin/pup_event_backend_modprobe always chooses the last module in a list generated from the module.alias file (or another representation of it). For most devices, which have only a single modules.alias entry, the generated list has the named module last, preceded by the modules it depends on. But hybrid devices such as some wireless modems may be represented by two modaliases, both of which are valid.

Hybrid modems are both a usb-storage device and a modem. The dual modaliases usually contain a filter to differentiate the module to be loaded in a particular circumstance. But the filters are limited such that either only one of the possible modules is placed in the generated list, or both are included -- not one or the other! Backend_modprobe selects only the second in the list, which is determined by automatic factors related to the "depmod" operation (I think). If the required module is the first of the two, it is never loaded!

To solve this, I inserted logic that is activated only when usb-storage is last in the list and module usbserial (a depencency of most USB wireless modem drivers) is also in the list. When that situation exists, the actual modem module follows usbserial in the list. The logic finds it there and makes it the selection. This works when usb-storage appears later in the modules.alias file than do the modem drivers.

I have found two cases where the dual modaliases are identical, meaning that one of the two modules will never be loaded. I think that can be overcome by special udev rules to detect when the neglected module should be loaded, and invoke backend_modprobe with the module-name parameter. That will require feedback from users encountering the problem.

Thanks for considering these updates for beta2.
Richard
3G_update_to_4.3_beta1-1.pet
Description  The scripts
pet

 Download 
Filename  3G_update_to_4.3_beta1-1.pet 
Filesize  14.49 KB 
Downloaded  364 Time(s) 
3G_update_to_4.3_beta1-1-diffs.tar.gz
Description  Difference listings
gz

 Download 
Filename  3G_update_to_4.3_beta1-1-diffs.tar.gz 
Filesize  3.31 KB 
Downloaded  371 Time(s) 
Back to top
View user's profile Send_private_message 
bert07

Joined: 26 Jul 2008
Posts: 97
Location: Belgium

PostPosted: Thu 20 Aug 2009, 07:07    Post_subject: Beta bugs and reports
Sub_title: cd did not boot; b43 gave error
 

puppy-4.3beta1-k2.6.29.6-v423
Could not get b43 to work.
Did not recognize b43 automatically.
When loaded and started "scan" it gave the following error:
"Failed to raise interface wlan0. Failed command was: ifconfig wlan0 up. Error returned was: ifconfig: SIOCSIFFLAGS: No such file or directory."
Filling in the network manually, gives the same error.


puppy-4.3beta1-k2.6.25.16-v423
The CD would not boot. Downloaded it twice. Burned it three times.
Also, when trying to copy pp4c-423.sfs manually, gave a read/write error.

_________________
PC: Dell Inspiron 531 - Motherboard: NVIDIA MCP61 chipset - Sound: Realtec High Definition Audio ALC888 - Display Adapter: ATI Radeon HD 2400 Pro - Wired: NVIDIA nForce networking controller - Wireless: Broadcom AirForce One 54g (ASUS WL-138g-V2)
Back to top
View user's profile Send_private_message 
Kenny-M


Joined: 15 May 2009
Posts: 147
Location: United States

PostPosted: Thu 20 Aug 2009, 08:04    Post_subject:  

Can I make the assumption with work going forward on
4.3 beta 1- k 2.6.29.6 that the SCSI beta Barry made for
me 4.3 Beta 1- k2.6.25.16 SCSI which also included the
drivers for the Matrox G5xx series viedo cards will be
skipped?

How does one make sure that for example SCSI drivers
for Adaptec cards/chipsets (AIC-7880 & AIC-7890) and
video drivers for Matrox cards, specifically the G5xx (G550)
will continue to be included?

Also the Printer drivers for HP PSC series (specifically PSC-1310)
are included? Could not find this printer in 4.3 Beta 1- k2.6.25.16
SCSI. It does and work in 4.2.1. Downloading 'foo2zjs-i486.pet',
and 'hpijs-2.8.2_static-1-patched421.pet' does not seem to work
under 4.3 Beta 1- k2.6.25.16 SCSI.

Thanks

_________________
Puppy 4.2.1 SeaMonkey on 160GB Ext USB Disk on Dell 745 SFF.
Puppy 4.3.0-SCSI on Dell Precision 610 workstation.
Puppy 4.2.1 running on Windows XP under Qemu.
Back to top
View user's profile Send_private_message 
sinc


Joined: 22 Jul 2009
Posts: 523
Location: Tampa, FL USA

PostPosted: Thu 20 Aug 2009, 20:09    Post_subject:  

i can't get my wireless internet to work on 4.3 and was wondering if someone could help me with that.

on ttuuxxx's 2.14 i have to download the bcm43xx.pet in order to get wireless working.

it doesn't auto-detect any wireless driver for me. when i load bcm43legacy it finds the module but when i try to set up wireless it comes up with an error ... "can't raise something or other"

please let me know if any further info is needed. thanks.
Back to top
View user's profile Send_private_message 
01micko


Joined: 11 Oct 2008
Posts: 7841
Location: qld

PostPosted: Fri 21 Aug 2009, 06:54    Post_subject:  

01micko wrote:
BarryK wrote:
01micko wrote:
DC wrote:

P.S. /etc/puppyversion - missing


Not in mine, this little script I wrote depends on it...


/etc/puppyversion not used anymore. Look in /etc/DISTRO_SPECS


guess I'll update my script then

(um, for me /etc/puppyversion is definitely still there, I just checked, "puppy pfix=ram", is it used in the welcome note?)


Well, /etc/puppyversion is not in dpup, gposil's woof build, so I updated my script... Versioninfo

Cheers

_________________
Woof Mailing List | keep the faith Cool |
Back to top
View user's profile Send_private_message Visit_website 
paulh177


Joined: 22 Aug 2006
Posts: 875
Location: ST862228

PostPosted: Fri 21 Aug 2009, 15:42    Post_subject:  

installed frugally on an acer aspire one 1gb ram 120gb hdd, on the preexisting Linpus ext2 fs

loading devx-4.3beta1-k2.6.29.6_423.sfs

trying compiles:
Code:
Configure: error: C compiler cannot create executables
and in config.log i see:

Code:
gcc: error trying to exec 'cc1': execvp: No such file or directory

_________________
Want to report a bug or problem? Have a read of this first ...
Back to top
View user's profile Send_private_message 
Bert


Joined: 30 Jun 2006
Posts: 975

PostPosted: Sat 22 Aug 2009, 16:55    Post_subject: VirtualBox  

Perhaps not a bug, but rather an oversight..It was reported earlier in this thread, by playdayz, at the bottom of page 2.

Puppy 4.3 beta1 does not start up X in Xorg when running in VirtualBox. (Neither did the pre-beta.)
This is kind of important, as VirtualBox has become very reliable, fast and user-friendly and must by now be the most popular way to check out new releases and distros.
Someone new to Puppy will probably just hit the 'enter' key to choose the default settings. Xorg is the default setting and this results in a black screen, leaving the newcomer clueless.

So, while not essential to Puppy, I think it is an important service for new users, testers and distro-hoppers.

Playdayz even mentioned the solution: a missing Xorg-file...

_________________


Back to top
View user's profile Send_private_message 
Display_posts:   Sort by:   
Page 8 of 13 Posts_count   Goto page: Previous 1, 2, 3, ..., 6, 7, 8, 9, 10, 11, 12, 13 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.1151s ][ Queries: 12 (0.0178s) ][ GZIP on ]