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, 20:27
All times are UTC - 4
 Forum index » Advanced Topics » Hardware » Networking
EeePC/Atheros drivers needed for use in Puppy NOPr5
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
Page 1 of 2 Posts_count   Goto page: 1, 2 Next
Author Message
stlchuck

Joined: 28 Feb 2006
Posts: 97

PostPosted: Fri 22 Feb 2008, 00:46    Post_subject:  EeePC/Atheros drivers needed for use in Puppy NOPr5  

Since I prefer NOP Puppy over the regular SeaMonkey version I need to get the correct Wifi and LAN drivers installed so that I can get out on the net with the EeePC running Puppy NOPr5 - Tried using the Atheros driver in the network wizard and the Windows (?) drivers from the ASUS support DVD with Ndiswrapper and they load OK but still no go where recognizing an active interface is concerned. Is there a package of the drivers such as were used in Puppy eee and if so where might they be found? Or how to copy them from Puppy eee to my NOPr5 install. Some instruction on the copying/loading would also be needed - my experience with wireless is quite limited and entirely with Windows XP and Vista up to now.

Thanks,
Back to top
View user's profile Send_private_message 
stlchuck

Joined: 28 Feb 2006
Posts: 97

PostPosted: Fri 22 Feb 2008, 12:19    Post_subject: Addendum  

Did some more looking around including a Google search for and downloading of the Windows driver for the Atheros AR5007EG module that is in the EeePC - version downloaded is 5.3.0.45 - and it included the .inf file that ndiswrapper asks for - loads OK but still no connections are recognized. Given my limited experience with wireless in Linux/Puppy I'm at a loss as to where to proceed from here - anyone with any ideas or suggestions feel free to comment.

Thanks,
Back to top
View user's profile Send_private_message 
dvw86


Joined: 04 May 2005
Posts: 636
Location: Washington State

PostPosted: Fri 22 Feb 2008, 15:33    Post_subject:  

What version of Puppy is NOP based on? I can point you to the needed files if NOP is compatible with Puppy 301.
Back to top
View user's profile Send_private_message 
stlchuck

Joined: 28 Feb 2006
Posts: 97

PostPosted: Fri 22 Feb 2008, 16:24    Post_subject: Puppy NOP  

Like your Puppy eee, NOP is based on the 3.01 version of Puppy - Full designation is 3.01NOPr5 for the version I'm using - My preference for it is based on the fact that it is set up from the get go with the XFCE window manager and Opera browser. I'd welcome the info on the Wifi and LAN drivers and if you are willing the info on setting up Xorg for the 800x480 screen resolution, although the 640x480 that I'm currently getting is something I can live with quite well.

Many thanks,

Chuck
Back to top
View user's profile Send_private_message 
dvw86


Joined: 04 May 2005
Posts: 636
Location: Washington State

PostPosted: Fri 22 Feb 2008, 18:30    Post_subject:  

Sure, everything is on the forum, but in various posts. I downloaded and saved them all to make things easier for me when building Pupeee. It may just be easier for you to start with Pupeee and install XFCE and Opera, but if you don't want to then here you go.

For video open up /usr/X11R7/bin/xwin.

go to the lines that read:
Code:

#Puppy Xorg Video Wizard...
if [ -f /usr/X11R7/bin/Xorg ];then

And change it to:
Code:

#Puppy Xorg Video Wizard...
915resolution 43 800 480 16 # 43 is for 16-bit, 38 is for 8-bit
if [ -f /usr/X11R7/bin/Xorg ];then


Exit to prompt and type "xorgwizard" without the quotes. Choose "Other" at the bottom of the menu, press ENTER for two more dialog boxes (accepting what you see), then in the final window, you will be able to select either the 800x480x16 or the 800x480x24 resolution.

For sound edit /etc/modprobe.conf and add this line:
Code:

options snd-hda-intel model=3stack-dig

Reboot (saving settings)

For the wireless download and install the madwifi-ng-r2756-eeepatch-k2.6.21.7.pet from the link below. The wireless card should be recognized on the next boot.

http://waltonpond.com/eeepc/drivers/madwifi-ng-r2756-eeepatch-k2.6.21.7.pet

For the Ethernet port download and and install the atl2-2.0.3-k2.6.21.7.pet from the link below. Open up /etc/networkmodules and add the line:
Code:

atl2 "pci: Support for Atheros Wired Ethernet (1 Gb) used with EeePC."

On next boot you should be able to use the Internet Connect Wizard to load the driver and configure the Ethernet card.

http://waltonpond.com/eeepc/drivers/atl2-2.0.3-k2.6.21.7.pet

For a battery monitor download the asapm.tar.gz. Extract it and move it to either usr/bin, /root/ my-applications/bin, or even usr/local/bin. Open your /root/.jwm-tray file and change the height setting in the second line to:
Code:

height="32"


http://waltonpond.com/eeepc/extras/asapm.tar.gz

For the webcam download and install the uvcvideo_20070706-k2.6.21.7.pet from the link below. Reboot the computer.

http://waltonpond.com/eeepc/drivers/uvcvideo_20070706-k2.6.21.7.pet

Here is my recommended /etc/rc.d/rc.local file. It will load the needed modules for the battery monitor and and start it on boot. It will also load the needed modules for the webcam and trackpad.
Code:

#this file called from rc.local0
#you can edit this file
#When firewall is installed, will append lines to this file...
rmmod rt2570
modprobe battery
modprobe ac
asapm
modprobe evdev
modprobe v4l2-common
modprobe v4l1-compat
modprobe videodev
modprobe compat_ioctl32
modprobe uvcvideo

When the evdev module is loaded with the default xorgconfig file the tap no longer works. To get the tap function working again open up /etc/X11/xorg.conf and change the setting from:
Code:

Option "MaxTapTime" "0"

to
Code:

Option "MaxTapTime" "220"

It should be around line number 116.

Function keys are a bit of a problem. Some such as wireless on-off (F2), screen dim (F3), and screen bright (F4) work by default. You can enable some others such as number lock (F11) and scroll lock (F12) by downloading and installing the asus_acpi-071127-k2.6.21.7.pet from the link below. Reboot the computer.

http://waltonpond.com/eeepc/drivers/asus_acpi-071127-k2.6.21.7.pet

You can use xbindkeys and my setvolume script to use the volume up (F9), down (F8 ), and mute (F7) keys in combination with the alt key. I also use xbindkeys to set the print screen (insert) key to take a snapshot with MTpaint.

http://waltonpond.com/eeepc/extras/setvolume
http://waltonpond.com/eeepc/extras/xbindkeys-1.7.2.pup

The Eeepc shut down bug can be fixed by replacing the /etc/rc.d/rc.shutdown with the one linked below.

http://waltonpond.com/eeepc/extras/rc.shutdown

This may be more than you were looking for, but it was good for me to write it all down anyways.
Back to top
View user's profile Send_private_message 
stlchuck

Joined: 28 Feb 2006
Posts: 97

PostPosted: Fri 22 Feb 2008, 18:53    Post_subject: Puppy NOP  

Thank You dvw86!! Looks as though I've got my work cut out for me - I'll post results in your Pupeee thread as I get them.
Back to top
View user's profile Send_private_message 
stlchuck

Joined: 28 Feb 2006
Posts: 97

PostPosted: Fri 22 Feb 2008, 23:33    Post_subject: A mixed bag so far  

So far a mixed bag - The changes to Xorg worked fine but the network connection still isn't cooperating - a check of the pkg manager shows that the .pet pkgs are there and the line "atl2..." was added to /etc/networkmodules but still no connections. Driver atl2 will not load successfully and the wireless card is not being recognized. I'm going to shut down and work on this more another time when I'm not so tired.

Thanks,
Back to top
View user's profile Send_private_message 
stlchuck

Joined: 28 Feb 2006
Posts: 97

PostPosted: Sat 08 Mar 2008, 02:45    Post_subject:
Sub_title: Further fiddling with the LAN and Wifi drivers for the EeePC
 

As I stated a few days ago in dvw86's Pupeee thread I finally managed to get the LAN driver working in Puppy 3.01NOP but not the wireless. What seems to be happening is that since Puppy 3.01 comes with an "ath_pci" driver as part of its network package it is defaulting to that and not loading the modified/patched driver from this link -

http://waltonpond.com/eeepc/drivers/madwifi-ng-r2756-eeepatch-k2.6.21.7.pet

thus no working wifi connection. My feeling on this is based on the fact that the LAN driver does not have a counterpart in the network modules package for Puppy to default to. Thus when setting/configuring the LAN the correct driver module is loaded.

My question is this - how do you go about removing/deactivating the existing "ath_pci" driver in Puppy 3.01 and/or Dingo Alpha 7? If I can do that I suspect that the wireless will work correctly as the patched driver would then be loaded. Opinions, suggestions, comments anyone?
Back to top
View user's profile Send_private_message 
tempestuous

Joined: 10 Jun 2005
Posts: 5263
Location: Australia

PostPosted: Sat 08 Mar 2008, 04:48    Post_subject:  

The madwifi-ng-r2756-eeepatch-k2.6.21.7.pet package (which was originally compiled and packaged by me) installs the ath_pci module and all other associated modules to /lib/modules/2.6.21.7/net
which is the same location as the "standard" ath_pci module already in Puppy 3.x.
So the standard version should be overwritten.
After first installation, however, you would need to reboot, since the old ath_pci module (and associated modules) would still probably be loaded in RAM.

EDIT: This same driver package can be used in Puppy4.0, because it has the same 2.6.21.7 kernel as Puppy3.x

Edited_time_total
Back to top
View user's profile Send_private_message 
stlchuck

Joined: 28 Feb 2006
Posts: 97

PostPosted: Sat 08 Mar 2008, 12:49    Post_subject: Still no luck...  

Tempestuous,

Many thanks for your reply - went into lib/modules/2.6.21.7/net and found a total of six items that start "ath_..." - tried loading each one individually using the specify option in the network wizard and each one produces the same error message "loading failed try a different driver". Also tried using the modprobe command in a terminal which produces a message of "module/driver not found". Just for grins I'm going to do a fresh download of the pet pkg and try it on a new save file just in case the original download was corrupt for some reason - despite numerous reboots the needed driver is not being loaded with the current setup as the network wizard is not seeing the wireless interface at all - interface is an Atheros 5007EG if that info is of any use. The LAN driver in this package "atl2-2.0.3-k2.6.21.7.pet" works just fine when loaded according to dvw86's directions so I've got a working net connection - just not a wireless one! Many thanks for your reply and assistance.

Chuck
Back to top
View user's profile Send_private_message 
tempestuous

Joined: 10 Jun 2005
Posts: 5263
Location: Australia

PostPosted: Sat 08 Mar 2008, 20:29    Post_subject: Re: Still no luck...  

stlchuck wrote:
went into lib/modules/2.6.21.7/net and found a total of six items that start "ath_..." - tried loading each one individually

Don't do that. The correct module to load is "ath_pci", the others are modules that ath_pci depends on.
The reason that those modules fail to load is that they are probably already loaded!
You can confirm this by running the "lsmod" command.

There's a fair chance that it's unnecessary to load the ath_pci module from the Network Wizard at all ... because Puppy should automatically load this module at boot up.

If you do need to load the ath_pci module, forget about the Network Wizard, do it manually. Close the Network Wizard and run this command -
Code:
modprobe ath_pci

If you see no error messages, it means that the module loaded successfully. And the module should create a network interface called "ath0".
Now run the Network Wizard to configure the ath0 interface.

If still no success, it might be worth running the "dmesg" command to see if there are any error messages relating to the ath_pci module.
Back to top
View user's profile Send_private_message 
stlchuck

Joined: 28 Feb 2006
Posts: 97

PostPosted: Sun 09 Mar 2008, 02:04    Post_subject: Still no wireless connection  

Tempestuous,
ath_pci module isloaded - at least if the network wizard is to e believed. Since I'm not sure where the problem is I'm posting the output from both lsmod and dmesg in hope that your experienced eye will spot the problem. Makes for a very lengthy post but giving you the entire output makes sure I don't miss something important.

dmesg first-

sh-3.00# dmesg
BIOS: Disabled by ACPI PNP
SCSI subsystem initialized
libata version 2.20 loaded.
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
pnp: 00:01: iomem range 0xfed13000-0xfed19fff has been reserved
pnp: 00:08: iomem range 0xfed1c000-0xfed1ffff has been reserved
pnp: 00:08: iomem range 0xfed20000-0xfed8ffff has been reserved
pnp: 00:09: iomem range 0xfec00000-0xfec00fff has been reserved
pnp: 00:09: iomem range 0xfee00000-0xfee00fff could not be reserved
pnp: 00:0a: iomem range 0xe0000000-0xefffffff has been reserved
pnp: 00:0b: iomem range 0xe0000000-0xefffffff has been reserved
pnp: 00:0c: iomem range 0x0-0x9ffff could not be reserved
pnp: 00:0c: iomem range 0xc0000-0xcffff could not be reserved
pnp: 00:0c: iomem range 0xe0000-0xfffff could not be reserved
pnp: 00:0c: iomem range 0x100000-0x7f7fffff could not be reserved
Time: tsc clocksource has been installed.
PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0
PCI: Bridge: 0000:00:1c.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:00:1c.1
IO window: disabled.
MEM window: fbf00000-fbffffff
PREFETCH window: disabled.
PCI: Bridge: 0000:00:1c.2
IO window: disabled.
MEM window: f8000000-fbefffff
PREFETCH window: f0000000-f6ffffff
PCI: Bridge: 0000:00:1e.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 5
PCI: setting IRQ 5 as level-triggered
ACPI: PCI Interrupt 0000:00:1c.0[A] -> Link [LNKA] -> GSI 5 (level, low) -> IRQ 5
PCI: Setting latency timer of device 0000:00:1c.0 to 64
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:00:1c.1[B] -> Link [LNKB] -> GSI 11 (level, low) -> IRQ 11
PCI: Setting latency timer of device 0000:00:1c.1 to 64
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered
ACPI: PCI Interrupt 0000:00:1c.2[C] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10
PCI: Setting latency timer of device 0000:00:1c.2 to 64
PCI: Setting latency timer of device 0000:00:1e.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
checking if image is initramfs... it is
Freeing initrd memory: 1199k freed
highmem bounce pool size: 64 pages
NTFS driver 2.1.28 [Flags: R/W].
io scheduler noop registered
io scheduler cfq registered (default)
PCI: Setting latency timer of device 0000:00:1c.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:1c.0:pcie00]
Allocate Port Service[0000:00:1c.0:pcie02]
PCI: Setting latency timer of device 0000:00:1c.1 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:1c.1:pcie00]
Allocate Port Service[0000:00:1c.1:pcie02]
PCI: Setting latency timer of device 0000:00:1c.2 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:1c.2:pcie00]
Allocate Port Service[0000:00:1c.2:pcie02]
isapnp: Scanning for PnP cards...
Switched to NOHz mode on CPU #0
isapnp: No Plug & Play device found
Real Time Clock Driver v1.12ac
intel_rng: FWH not detected
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
floppy0: no floppy controllers found
RAMDISK driver initialized: 16 RAM disks of 13824K size 1024 blocksize
loop: loaded (max 8 devices)
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ide0: I/O resource 0x1F0-0x1F7 not free.
ide0: ports already in use, skipping probe
Probing IDE interface ide1...
hdc: SILICONMOTION SM223AC, ATA DISK drive
ide1 at 0x170-0x177,0x376 on irq 15
hdc: max request size: 128KiB
hdc: 7815024 sectors (4001 MB) w/1KiB Cache, CHS=7753/16/63
hdc: hdc1
ahci 0000:00:1f.2: version 2.1
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 7
PCI: setting IRQ 7 as level-triggered
ACPI: PCI Interrupt 0000:00:1f.2[B] -> Link [LNKD] -> GSI 7 (level, low) -> IRQ 7
ACPI: PCI interrupt for device 0000:00:1f.2 disabled
ahci: probe of 0000:00:1f.2 failed with error -22
ata_piix 0000:00:1f.2: version 2.10ac1
ata_piix 0000:00:1f.2: MAP [ P0 P2 IDE IDE ]
ACPI: PCI Interrupt 0000:00:1f.2[B] -> Link [LNKD] -> GSI 7 (level, low) -> IRQ 7
ata: 0x170 IDE port busy
ata: conflict with ide1
PCI: Setting latency timer of device 0000:00:1f.2 to 64
ata1: SATA max UDMA/133 cmd 0x000101f0 ctl 0x000103f6 bmdma 0x0001ffa0 irq 14
ata2: DUMMY
scsi0 : ata_piix
ATA: abnormal status 0x7F on port 0x000101f7
scsi1 : ata_piix
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard as /class/input/input0
Synaptics Touchpad, model: 1, fw: 6.3, id: 0x180b1, caps: 0xa04753/0x200000
input: SynPS/2 Synaptics TouchPad as /class/input/input1
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI Shortcut mode
Freeing unused kernel memory: 204k freed
squashfs: version 3.2-r2 (2007/01/15) Phillip Lougher
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 3
PCI: setting IRQ 3 as level-triggered
ACPI: PCI Interrupt 0000:00:1d.0[A] -> Link [LNKH] -> GSI 3 (level, low) -> IRQ 3
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:1d.0: irq 3, io base 0x0000e400
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.1[B] -> Link [LNKD] -> GSI 7 (level, low) -> IRQ 7
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.1: irq 7, io base 0x0000e480
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.2[C] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10
PCI: Setting latency timer of device 0000:00:1d.2 to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.2: irq 10, io base 0x0000e800
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.3[D] -> Link [LNKA] -> GSI 5 (level, low) -> IRQ 5
PCI: Setting latency timer of device 0000:00:1d.3 to 64
uhci_hcd 0000:00:1d.3: UHCI Host Controller
uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1d.3: irq 5, io base 0x0000e880
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
usb 1-2: new low speed USB device using uhci_hcd and address 2
ACPI: PCI Interrupt 0000:00:1d.7[A] -> Link [LNKH] -> GSI 3 (level, low) -> IRQ 3
PCI: Setting latency timer of device 0000:00:1d.7 to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 5
ehci_hcd 0000:00:1d.7: debug port 1
PCI: cache line size of 32 is not supported by device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: irq 3, io mem 0xf7eb7c00
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 8 ports detected
Initializing USB Mass Storage driver...
usb 1-2: device not accepting address 2, error -71
usb 5-3: new high speed USB device using ehci_hcd and address 3
usb 5-3: configuration #1 chosen from 1 choice
usb 5-5: new high speed USB device using ehci_hcd and address 4
usb 5-5: configuration #1 chosen from 1 choice
usb 5-8: new high speed USB device using ehci_hcd and address 5
usb 5-8: configuration #1 chosen from 1 choice
scsi2 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
scsi3 : SCSI emulation for USB Mass Storage devices
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
usbcore: registered new interface driver hiddev
usb 1-2: new low speed USB device using uhci_hcd and address 4
usb 1-2: configuration #1 chosen from 1 choice
input: Logitech USB Receiver as /class/input/input2
input: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:1d.0-2
input: Logitech USB Receiver as /class/input/input3
input,hiddev96: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:1d.0-2
usbcore: registered new interface driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
Registering unionfs 2.1.2 (for 2.6.21.7)
fuse init (API version 7.Cool
scsi 3:0:0:0: Direct-Access USB2.0 CardReader SD0 0100 PQ: 0 ANSI: 0
SCSI device sda: 15758336 512-byte hdwr sectors (8068 MB)
sda: Write Protect is off
sda: Mode Sense: 03 00 00 00
sda: assuming drive cache: write through
SCSI device sda: 15758336 512-byte hdwr sectors (8068 MB)
sda: Write Protect is off
sda: Mode Sense: 03 00 00 00
sda: assuming drive cache: write through
sda: sda1
sd 3:0:0:0: Attached scsi removable disk sda
usb-storage: device scan complete
usb 5-3: reset high speed USB device using ehci_hcd and address 3
scsi 2:0:0:0: Direct-Access USB Flash Memory 5.00 PQ: 0 ANSI: 0 CCS
SCSI device sdb: 3914752 512-byte hdwr sectors (2004 MB)
sdb: Write Protect is off
sdb: Mode Sense: 23 00 00 00
sdb: assuming drive cache: write through
SCSI device sdb: 3914752 512-byte hdwr sectors (2004 MB)
sdb: Write Protect is off
sdb: Mode Sense: 23 00 00 00
sdb: assuming drive cache: write through
sdb: sdb1
sd 2:0:0:0: Attached scsi removable disk sdb
usb-storage: device scan complete
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
unionfs: do delay copyup of "nls_cp437.ko"
unionfs: do delay copyup of "nls_iso8859-1.ko"
Linux agpgart interface v0.102 (c) Dave Jones
unionfs: do delay copyup of "agpgart.ko"
agpgart: Detected an Intel 915GM Chipset.
agpgart: Detected 7932K stolen memory.
agpgart: AGP aperture is 256M @ 0xd0000000
unionfs: do delay copyup of "intel-agp.ko"
unionfs: do delay copyup of "soundcore.ko"
snd: no version for "unregister_sound_special" found: kernel tainted.
unionfs: do delay copyup of "snd.ko"
unionfs: do delay copyup of "snd-hwdep.ko"
unionfs: do delay copyup of "snd-page-alloc.ko"
unionfs: do delay copyup of "snd-timer.ko"
unionfs: do delay copyup of "snd-pcm.ko"
ACPI: PCI Interrupt 0000:00:1b.0[A] -> Link [LNKA] -> GSI 5 (level, low) -> IRQ 5
PCI: Setting latency timer of device 0000:00:1b.0 to 64
hda_codec: Unknown model for ALC662, trying auto-probe from BIOS...
unionfs: do delay copyup of "snd-hda-intel.ko"
unionfs: do delay copyup of "i2c-core.ko"
ACPI: PCI Interrupt 0000:00:1f.3[B] -> Link [LNKD] -> GSI 7 (level, low) -> IRQ 7
unionfs: do delay copyup of "i2c-i801.ko"
ath_hal: module license 'Proprietary' taints kernel.
ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
unionfs: do delay copyup of "ath_hal.ko"
wlan: 0.8.4.2 (0.9.3.2)
unionfs: do delay copyup of "wlan.ko"
ath_pci: 0.9.4.5 (0.9.3.2)
ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10
PCI: Setting latency timer of device 0000:01:00.0 to 64
wifi%d: unable to attach hardware: 'Hardware revision not supported' (HAL status 13)
ACPI: PCI interrupt for device 0000:01:00.0 disabled
unionfs: do delay copyup of "ath_pci.ko"
unionfs: do delay copyup of "drm.ko"
unionfs: do delay copyup of "i810.ko"
unionfs: do delay copyup of "messages"
unionfs: new lower inode mtime (bindex=0, name=log)
unionfs: do delay copyup of "usbcore.ko"
usbcore: registered new interface driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
unionfs: do delay copyup of "usblp.ko"
unionfs: do delay copyup of "usbhid.ko"
unionfs: create_parents failed for bindex = 1
unionfs: do delay copyup of "snd-mixer-oss.ko"
unionfs: do delay copyup of "snd-seq-device.ko"
Atheros(R) L2 Ethernet Driver - version 2.0.3
Copyright (c) 2007 Atheros Corporation.
ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [LNKB] -> GSI 11 (level, low) -> IRQ 11
PCI: Setting latency timer of device 0000:03:00.0 to 64
unionfs: do delay copyup of "snd-seq.ko"
unionfs: do delay copyup of "snd-seq-midi-event.ko"
unionfs: do delay copyup of "snd-seq-oss.ko"
unionfs: do delay copyup of "snd-pcm-oss.ko"
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
unionfs: do delay copyup of "atl2.ko"
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
hda_codec: num_steps = 0 for NID=0xc
unionfs: lower dentry NULL (or error) for bindex = 1
unionfs: do delay copyup of "parport.ko"
unionfs: do delay copyup of "parport_pc.ko"
lp: driver loaded but no devices found
unionfs: do delay copyup of "lp.ko"
unionfs: create_parents failed for bindex = 1
unionfs: create_parents failed for bindex = 1
unionfs: do delay copyup of "evdev.ko"
unionfs: do delay copyup of "utmp"
unionfs: do delay copyup of "wtmp"
atl2: eth0 NIC Link is Up<100 Mbps Full Duplex>
atl2: eth0 NIC Link is Up<100 Mbps Full Duplex>
unionfs: saving rdstate with cookie 7 [2.664]
unionfs: do delay copyup of ".ICEauthority"
unionfs: create_parents failed for bindex = 1
unionfs: create_parents failed for bindex = 1
unionfs: create_parents failed for bindex = 1
hda_codec: num_steps = 0 for NID=0xc
unionfs: do delay copyup of ".qt_plugins_3.3rc.lock"
unionfs: do delay copyup of "mailbase.dat"
unionfs: do delay copyup of "lexicon.dat"
unionfs: do delay copyup of "indexer.dat"
unionfs: unhashed dentry being revalidated: tls
unionfs: unhashed dentry being revalidated: tls

Then lsmod -

sh-3.00# lsmod
Module Size Used by
evdev 10240 1
parport_pc 31716 0
lp 12616 0
parport 35528 2 parport_pc,lp
snd_mixer_oss 16896 0
atl2 24344 0
usblp 14080 0
ath_pci 96800 0
wlan 206020 1 ath_pci
ath_hal 191568 1 ath_pci
i2c_i801 8720 0
i2c_core 22032 1 i2c_i801
snd_hda_intel 289308 0
snd_pcm 75656 1 snd_hda_intel
snd_timer 22020 1 snd_pcm
snd_page_alloc 10120 2 snd_hda_intel,snd_pcm
snd_hwdep 9220 1 snd_hda_intel
snd 52068 5 snd_mixer_oss,snd_hda_intel,snd_pcm,snd_timer,snd_hwdep
soundcore 7520 1 snd
intel_agp 24860 1
agpgart 34128 2 intel_agp
fuse 44052 0
unionfs 83732 1
nls_iso8859_1 4224 1
nls_cp437 5888 1
usb_storage 83264 1
usbhid 24928 0
ehci_hcd 31116 0
uhci_hcd 24076 0
usbcore 127128 6 usblp,usb_storage,usbhid,ehci_hcd,uhci_hcd
sr_mod 17188 0
ide_cd 39200 0
cdrom 36768 2 sr_mod,ide_cd
squashfs 47620 1

Hope this helps to diagnose the problem - as I've stated the wired (LAN) connection works fine - had to wait to get home from work to ge a working net connection so I could post this.

Thanks,

Chuck
Back to top
View user's profile Send_private_message 
tempestuous

Joined: 10 Jun 2005
Posts: 5263
Location: Australia

PostPosted: Sun 09 Mar 2008, 07:23    Post_subject:  

Your dmesg output looks good, except this -
Code:
wifi%d: unable to attach hardware: 'Hardware revision not supported' (HAL status 13)

I suspect something basic like maybe the wifi device has been disabled in bios?
Or what about the function keys -
dvw86 wrote:
Function keys are a bit of a problem. Some such as wireless on-off (F2), screen dim (F3), and screen bright (F4) work by default.

Maybe just toggling F2 will fix the problem?

Or maybe 3.01NOP has a boot command that is messing things up ... like "acpi=off".
Check /boot/grub/menu.lst
Back to top
View user's profile Send_private_message 
rover

Joined: 06 Dec 2007
Posts: 32
Location: Upstate New York, USA

PostPosted: Sun 09 Mar 2008, 08:16    Post_subject:  

I have pretty much the same problem with a lot but not all of the puppys that I have tried.

I believe that if I knew how to remove a module by hand and then to load a module by hand again ,that I could get the puppies that I try to use up and going.

Sure would like to see that answer posted somewhere.

Another problem I have experienced seems to be what you are talking about. It appears that once the program boots and loads a module, there is no way to unload that module and get the correct one, or at least a working one to load.

At one time I did this with success:

I was booting puppy from cd on a xp machine.
I went to find in windows and found the xp drivers for my wi fi card. There were 2 files. One was a .inf file that went along with the other file that named the driver I was looking for. (sorry, it was a long time ago)
I did a google to find the correct windows drivers for my net card.
Then after windows found the driver files, I created a directory in windows named 1apuppy. (that way ,that directory will always sort first and be easy to find in puppy.)
Then I booted puppy, ran the wifi wizard, and that version of puppy let me unload the drivers that were automatically loaded at boot, I unloaded the ones chosen by puppy and then went to ndiswrapper and assigned the windows drivers I had saved in 1apuppy. At that time my wifi card worked with ndiswrapper.

Hope this helps, as it is a long way around the horn to get from point a to b.

If I ever find a solution, I promise to write it up nice and neat and post it somewhere where some other poor person does not go as bald as I have over this stuff!
Back to top
View user's profile Send_private_message 
stlchuck

Joined: 28 Feb 2006
Posts: 97

PostPosted: Sun 09 Mar 2008, 09:35    Post_subject:  

Tempestuous,

I'll do some looking at BIOS and boot parameters later today if time permits - I sort of doubt that it is a BIOS problem though since the wireless works well in both Pupeee and in Windows XP without any changes needed. I'll get back to you here when I've done so.

Thanks

Chuck
Back to top
View user's profile Send_private_message 
Display_posts:   Sort by:   
Page 1 of 2 Posts_count   Goto page: 1, 2 Next
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
 Forum index » Advanced Topics » Hardware » Networking
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.1568s ][ Queries: 11 (0.0045s) ][ GZIP on ]