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 25 Apr 2018, 14:41
All times are UTC - 4

 Forum index » Advanced Topics » Puppy Derivatives
BoxPuppeee
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 4 of 5 [75 Posts]   Goto page: Previous 1, 2, 3, 4, 5 Next
Author Message
01micko


Joined: 11 Oct 2008
Posts: 8670
Location: qld
PostPosted: Wed 27 Jan 2010, 21:02    Post subject:  
Hi jemimah
Code:
MODEL=`cat /sys/class/power_supply/BAT0/model_name`

it returns
Code:
701SD
in boxpuppeee, I just checked. Perhaps you could find it useful for the Fn-F2 bug and perhaps splash an error message.
That is the code I used for the condition of a 701SD in eee-control I worked on with tempestuous.

HTH Smile

Cheers
_________________
Puppy Linux Blog - contact me for access
Back to top
View user's profile Send private message Visit poster's website 
jemimah


Joined: 26 Aug 2009
Posts: 4309
Location: Tampa, FL
PostPosted: Wed 27 Jan 2010, 21:53    Post subject:  
Thanks that could be useful.

If you get a chance could you try adding 'acpi_osi=Linux' to your kernel line in syslinux.cfg (or grub if you use that). Apparently this is needed on 2.6.32 but maybe it would help with this problem.
Back to top
View user's profile Send private message Visit poster's website 
01micko


Joined: 11 Oct 2008
Posts: 8670
Location: qld
PostPosted: Wed 27 Jan 2010, 22:05    Post subject:  
Ok,

added that to the line but no cigar, still crashes, worth a try though

Cheers
_________________
Puppy Linux Blog - contact me for access
Back to top
View user's profile Send private message Visit poster's website 
dougeeebear

Joined: 08 Apr 2009
Posts: 170
Location: Mid-South, USA
PostPosted: Mon 01 Feb 2010, 16:33    Post subject:  
* please disregard this post *
Back to top
View user's profile Send private message 
2lss

Joined: 20 Sep 2009
Posts: 225
PostPosted: Thu 04 Feb 2010, 18:59    Post subject:  
First off let me say THANK YOU! This is my favorite distro for the eee 900. Only one small problem,

My university uses wpa2 enterprise encryption for our wireless network. Using puppeee 4.2 I made a wpa_supplicant script and was able to connect without a problem for the past couple months.
Code:
#! /bin/bash

rm /var/run/wpa_supplicant/*

wpa_supplicant -Dwext -iath0 -c/etc/wpa_supplicant2.conf  -B -dd

sleep 5

rm -f /var/lib/dhcpcd/*.info
rm -f /var/run/*.pid

dhcpcd -t 30 -h puppypc -d ath0


When I tried running the same script(other than changing ath0 to wlan0) in boxpuppeee I couldn't connect. When I compared the log from puppeee 4.2 with boxpuppeee I found an error:

Code:
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - wpa_driver_wext_set_drop_unencrypted
Setting scan request: 0 sec 100000 usec
Using existing control interface directory.
Added interface wlan0
Daemonize


After searching around I found bugs that suggest wpa_supplicant is conflicting with the mac80211
http://lists.shmoo.com/pipermail/hostap/2008-June/017954.html
I tried changing ap_scan=2 to 1 but it did not make a difference. I also found another report that it may be a kernel issue http://www.linuxquestions.org/questions/linux-wireless-networking-41/wpasupplicant-ioctlsiocsiwauth-operation-not-supported-613144/

Has anyone else experienced this? If I can get this working I'm going to upgrade from 4.2 so any help would be appreciated.
Back to top
View user's profile Send private message 
jemimah


Joined: 26 Aug 2009
Posts: 4309
Location: Tampa, FL
PostPosted: Thu 04 Feb 2010, 21:29    Post subject:  
Boxpuppeee has the Pwireless2 network manager, which starts wpa_supplicant when the computer is booted. Running your script is probably trying to start another copy which I imagine is a bad idea.

The Pwireless2 gui doesn't have options for wpa enterprise yet, but you can manually edit it's wpa_supplicant.conf. You can find the file at /usr/local/Pwireless2/wpa_supplicant.conf.

You want ap_scan=1 for ath5k.

Edit the file, then reboot, and it should automatically connect.
Back to top
View user's profile Send private message Visit poster's website 
2lss

Joined: 20 Sep 2009
Posts: 225
PostPosted: Fri 05 Feb 2010, 11:47    Post subject:  
jemimah: Thank you, adding the profile to wpa_supplicant.conf did the trick. After using boxpuppeee for a couple days I'm really liking Pwireless2. The default puppy network manager would always connect me to the wrong network at bootup. Mad

One more question, My cursor is very erratic when trying moving small distances, i.e. it's hard to click on small things. I thought it was a problem with the touchpad settings but after I tried changing them it didn't make a difference. I also experience the same issue with a usb mouse so I'm thinking its not a touchpad issue. Do you know what the culprit could be?
Back to top
View user's profile Send private message 
jemimah


Joined: 26 Aug 2009
Posts: 4309
Location: Tampa, FL
PostPosted: Fri 05 Feb 2010, 13:20    Post subject:  
Here's what to try for the mouse: go to http://drop.io/puppeee and grab the vmlinuz-no-elantech kernel. Rename it to vmlinuz and replace the kernel you're currently booting with. Jakfish, who also has an Eee 900, has this problem - caused by some kind of incompatibility between the touchpad and the touchpad driver. I'm not sure why that would affect a USB mouse, but it seems to me that it's highly likely to me that the elantech driver is the problem.
Back to top
View user's profile Send private message Visit poster's website 
2lss

Joined: 20 Sep 2009
Posts: 225
PostPosted: Fri 05 Feb 2010, 20:06    Post subject:  
Thanks jemimah, I tried your kernel w/out the elantech driver and my touchpad works great now. Only problem is that my usb mouse still exhibits the same behavior. When I get a chance, I will dig in and see if I can find the problem.
Back to top
View user's profile Send private message 
2lss

Joined: 20 Sep 2009
Posts: 225
PostPosted: Sat 13 Feb 2010, 00:50    Post subject:  
Ok, after using boxpuppeee for a week I have a few more questions.

I am having problems trying to connect to bluetooth devices using the bluez bluetooth-wizard. The dongle I am using is a kensington k33348b and is listed in dmesg as: BCM92045B3 ROM. When I plug it in, the btusb and bluetooth modules are loaded automatically. I have also tried loading the modules rfcomm and l2cap but I am not sure they are needed. To start bluetooth-wizard, the first thing I have to do is start dbus by:
Code:
rm -f /var/run/dbus/*
dbus-uuidgen --ensure
dbus-daemon --system

When I start bluetooth-wizard from the terminal I get some gtk errors but I'm not sure if they are related the problem:
Code:
# bluetooth-wizard
(bluetooth-wizard:13451): Gtk-CRITICAL **: gtk_tree_model_filter_set_visible_func: assertion `GTK_IS_TREE_MODEL_FILTER (filter)' failed
(bluetooth-wizard:13451): Gtk-CRITICAL **: gtk_tree_model_sort_new_with_model: assertion `GTK_IS_TREE_MODEL (child_model)' failed
(bluetooth-wizard:13451): Gtk-CRITICAL **: gtk_tree_sortable_set_sort_column_id: assertion `GTK_IS_TREE_SORTABLE (sortable)' failed
(bluetooth-wizard:13451): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(bluetooth-wizard:13451): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

The wizard starts up but doesn't list any bluetooth devices to set up.
If I use 'hcitool scan' I get an error 'Device is not available: No such device.' So I have to:
Code:
# hciconfig hci0 down
# hciconfig hci0 up 
# hcitool scan
Scanning ...
   00:1C:CC:FB:B8:D4   BlackBerry 8130
   00:19:1D:CF:12:AD   Nintendo RVL-CNT-01


Even after this, the bluetooth-wizard still doesn't find any devices. Does anyone know what could be causing this problem? I am new to the world of bluetooth so maybe I am missing something.
Back to top
View user's profile Send private message 
2lss

Joined: 20 Sep 2009
Posts: 225
PostPosted: Fri 19 Feb 2010, 13:07    Post subject:  
I dived back in to the world of bluetooth-wizard today to see if I can get this thing working. After playing around with strace and gdb I got to this point.
Code:
(gdb) disass 20022
Dump of assembler code for function show_browse_dialog:
0x00004c10 <show_browse_dialog+0>:   Cannot access memory at address 0x4c10

Unfortuantely this is beyond my linux skills atm. I will do some reading up to see if I can figure this out.
Back to top
View user's profile Send private message 
jemimah


Joined: 26 Aug 2009
Posts: 4309
Location: Tampa, FL
PostPosted: Fri 19 Feb 2010, 13:42    Post subject:  
Sorry I didn't see your message earlier. Bluetooth is supposed to load automatically if you plug your dongle in and reboot - but I haven't tested dongles recently.

If it doesn't load on it's own, try running /root/Startup/bluetooth which should cause all the daemons and the applet to load.

BTW, You need to also run bluetoothd to get the wizard to see stuff. Smile
Back to top
View user's profile Send private message Visit poster's website 
2lss

Joined: 20 Sep 2009
Posts: 225
PostPosted: Fri 19 Feb 2010, 15:32    Post subject:  
jemimah: I tried both methods, start w/ the dongle plugged in and running /Startup/bluetooth. Starting w/ the dongle in does automatically load everything but I still did not see my device under bluetooth-wizard. After starting bluetooth the manual way(after a reboot) I saw the problem was bluetoothd. Here is what I get with the debug flag.
Code:

# bluetoothd -nd
bluetoothd[7587]: Bluetooth daemon 4.55
bluetoothd[7587]: Enabling debug information
bluetoothd[7587]: parsing main.conf
bluetoothd[7587]: discovto=0
bluetoothd[7587]: pairto=0
bluetoothd[7587]: pageto=8192
bluetoothd[7587]: name=%h-%d
bluetoothd[7587]: class=0x000100
bluetoothd[7587]: discov_interval=0
bluetoothd[7587]: Key file does not have key 'DeviceID'
bluetoothd[7587]: Unable to get on D-Bus


So after searching, I found this link that explains the problem. http://markmail.org/thread/r47mqsku6xfsz5kp (second page)
I searched for the bluetooth.conf file and sure enough it was in /usr/etc/alsa (???? I don't know how it got there). So I tried moving it to /usr/etc/dbus-1/system.d and /usr/etc/bluetooth but I'm still getting the same error. Is there a different path that bluetooth.conf needs to placed in for dbus to find it?
Back to top
View user's profile Send private message 
jemimah


Joined: 26 Aug 2009
Posts: 4309
Location: Tampa, FL
PostPosted: Fri 19 Feb 2010, 16:49    Post subject:
Subject description: p		  
Hmmm, I'll have to look closer at the dbus install on boxpupeee. I haven't messed with the configuration, it probably needs tweaking. I opened all the permissions on Puppeee's dbus, but I'm not sure how Gray set it up on boxpup.

I'll get back to you on this. When I get a chance to check it out.
Back to top
View user's profile Send private message Visit poster's website 
jemimah


Joined: 26 Aug 2009
Posts: 4309
Location: Tampa, FL
PostPosted: Tue 02 Mar 2010, 22:26    Post subject:  
BoxPuppeee 2.1 has been posted.

I updated Pwireless2, the acpi scripts, and bluetooth.
Back to top
View user's profile Send private message Visit poster's website 
Display posts from previous:   Sort by:   
Page 4 of 5 [75 Posts]   Goto page: Previous 1, 2, 3, 4, 5 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Derivatives
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.0719s ][ Queries: 12 (0.0214s) ][ GZIP on ]