LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking
User Name
Password
Linux - Wireless Networking This forum is for the discussion of wireless networking in Linux.

Notices



Reply
 
Search this Thread
Old 01-16-2006, 09:38 PM   #16
jasonhouse
LQ Newbie
 
Registered: Jan 2006
Posts: 4

Rep: Reputation: 0

I just solve me issue! /var/log/messages showed many many lines of errors from Shorewall. By doing the GUI for firewall reconfig, I got it to work (the last screen asked which interface connects to the internet)
 
Old 01-17-2006, 05:09 AM   #17
Capecod
LQ Newbie
 
Registered: Jan 2006
Location: Nantes, FRANCE
Distribution: Mandriva 2006//Fedora Core 4
Posts: 13

Original Poster
Rep: Reputation: 0
Thanks Hangdog42
here are the result for ifconfig/iwconfig/route -n for mandriva2006 then for Suse10.0

Mandriva
[root@localhost capecod]# ifconfig
eth2 Link encap:UNSPEC HWaddr 00-E0-18-00-00-6E-11-A4-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

lo Link encap:Boucle locale
inet adr:127.0.0.1 Masque:255.0.0.0
adr inet6: ::1/128 Scope:Hôte
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:264 errors:0 dropped:0 overruns:0 frame:0
TX packets:264 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:14784 (14.4 KiB) TX bytes:14784 (14.4 KiB)

ra0 Link encap:Ethernet HWaddr 00:118:C0:BF:9B
inet adr:192.168.0.59 Bcast:192.168.0.255 Masque:255.255.255.0
adr inet6: fe80::211:d8ff:fec0:bf9b/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4045 errors:0 dropped:0 overruns:0 frame:0
TX packets:1252 errors:11 dropped:11 overruns:0 carrier:0
collisions:95 lg file transmission:1000
RX bytes:346427 (338.3 KiB) TX bytes:109474 (106.9 KiB)
Interruption:18 Adresse de base:0x8000

[root@localhost capecod]# iwconfig
lo no wireless extensions.

eth2 no wireless extensions.

ra0 RT2500 Wireless ESSID:"capecod_wifi" Nickname:"localhost"
Mode:Managed Frequency=11 MHz Access Point: 00:07:CB:52:85:E9
Bit Rate=11 Mb/s
RTS thrff Fragment thrff
Encryption key:xxxxxxxxxxxxxxxxxxxxxxxx Security modepen
Link Quality=0/70 Signal level:-209 dBm Noise level:-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

sit0 no wireless extensions.

[root@localhost capecod]# route -n
Table de routage IP du noyau
Destination Passerelle Genmask Indic Metric Ref Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 10 0 0 ra0
0.0.0.0 192.168.0.254 0.0.0.0 UG 10 0 0 ra0
[root@localhost capecod]#

And Suse

linux:/home/capecod # ifconfig
lo Lien encap:Boucle locale
inet adr:127.0.0.1 Masque:255.0.0.0
adr inet6: ::1/128 Scope:Hôte
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:70 errors:0 dropped:0 overruns:0 frame:0
TX packets:70 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:4820 (4.7 Kb) TX bytes:4820 (4.7 Kb)

ra0 Lien encap:Ethernet HWaddr 00:118:C0:BF:9B
inet adr:192.168.0.59 Bcast:192.168.0.255 Masque:255.255.255.0
adr inet6: fe80::211:d8ff:fec0:bf9b/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:241 errors:0 dropped:0 overruns:0 frame:0
TX packets:131 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
RX bytes:16388 (16.0 Kb) TX bytes:6273 (6.1 Kb)
Interruption:11 Adresse de base:0xc000

linux:/home/capecod # iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

ra0 RT2500 Wireless ESSID:"capecod_wifi" Nickname:"linux"
Mode:Managed Frequency=2.462 GHz Access Point: 00:07:CB:52:85:E9
Bit Rate=11 Mb/s
RTS thrff Fragment thrff
Encryption key:xxxxxxxxxxxxxxxxxxxxxxxxx Security modepen
Link Quality=79/100 Signal level=-71 dBm Noise level:-193 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

eth1 no wireless extensions.

sit0 no wireless extensions.

linux:/home/capecod # route -n
Table de routage IP du noyau
Destination Passerelle Genmask Indic Metric Ref Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 ra0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.0.254 0.0.0.0 UG 0 0 0 ra0
linux:/home/capecod #

I'am sure it's only a matter of ip adress or dns or gateway but i cant fine what

What do you think ?

capecod
 
Old 01-17-2006, 08:04 AM   #18
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,791
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
The one thing here that strikes me is that your Mandriva box doesn't have lo in the route output. That might be causing trouble as lo is used internally for a number of things. That said, the only thing that occurrs to me is that your firewall may not be set up to accept all traffic for lo.

Other things:

The interrupt (from ifconfig) for Madriva is 18, while for Suse is 11. You might want to look into the output of cat /proc/interrupts and see if something in Mandriva is going on with the interrupts. I don't know that this is a bad thing, but it certainly is a difference.
 
Old 01-18-2006, 09:15 AM   #19
Capecod
LQ Newbie
 
Registered: Jan 2006
Location: Nantes, FRANCE
Distribution: Mandriva 2006//Fedora Core 4
Posts: 13

Original Poster
Rep: Reputation: 0
Hi

The firewall on mandriva and suse in not active (i'm behind a router)
The interrupts file in /proc/ is empty
The kernel for mandriva is 2.6.12-12 and suse is 2.6.13-15
But wy this line with -lo- in the suse route -n ?
can i try to clean this line ?

i still dont understand the solution

thank's to help

capecod
 
Old 01-18-2006, 09:58 AM   #20
Capecod
LQ Newbie
 
Registered: Jan 2006
Location: Nantes, FRANCE
Distribution: Mandriva 2006//Fedora Core 4
Posts: 13

Original Poster
Rep: Reputation: 0
Sorry
the result for cat /proc/interrupt is for mandriva :
[root@localhost capecod]# cat /proc/interrupts
CPU0
0: 2126538 IO-APIC-edge timer
1: 1570 IO-APIC-edge i8042
8: 1 IO-APIC-edge rtc
9: 0 IO-APIC-level acpi
14: 30544 IO-APIC-edge ide0
15: 207471 IO-APIC-edge ide1
16: 0 IO-APIC-level cx88[0]
18: 80424 IO-APIC-level ra0
20: 14 IO-APIC-level ehci_hcd:usb3
21: 22099 IO-APIC-level ohci_hcd:usb2, NVidia nForce2
22: 61839 IO-APIC-level ohci_hcd:usb1, ohci1394
NMI: 0
LOC: 2115744
ERR: 0
MIS: 0
[root@localhost capecod]#

and for suse :
linux:/home/capecod # cat /proc/interrupts
CPU0
0: 38106 XT-PIC timer
1: 85 XT-PIC i8042
2: 0 XT-PIC cascade
5: 27462 XT-PIC ohci_hcd:usb1, skge, cx88[0]
7: 2 XT-PIC parport0
8: 2 XT-PIC rtc
9: 419 XT-PIC acpi, NVidia nForce2, ehci_hcd:usb3, ohci1394
11: 3992 XT-PIC ohci_hcd:usb2, ra0
14: 9949 XT-PIC ide0
15: 2604 XT-PIC ide1
NMI: 0
LOC: 0
ERR: 1
MIS: 0
linux:/home/capecod #
 
Old 01-18-2006, 10:22 AM   #21
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,791
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Here is a test to try. Boot the mandriva box with the noapic directive. So in the initial boot screen (Grub?) Select linux (or whatever the actual name of your boot profile is) and on the command line add the word noapic.

Quote:
But wy this line with -lo- in the suse route -n ?
can i try to clean this line ?
You don't want to get rid of the lo line in Suse, you do want it to be there in Mandriva. The lo device is the loopback device and it is a critical component of the system. Its absence in Mandriva may be part of the problem you are having. Unfortunately, I don't know enough about Mandriva to give you good advice, but I would start by looking in your network configuration tools and see if there is somewhere you can enable it.
 
Old 01-18-2006, 10:32 AM   #22
Capecod
LQ Newbie
 
Registered: Jan 2006
Location: Nantes, FRANCE
Distribution: Mandriva 2006//Fedora Core 4
Posts: 13

Original Poster
Rep: Reputation: 0
yes but mandriva work fine, the probleme is with suse10 !!
 
Old 01-18-2006, 02:33 PM   #23
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,791
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Ooops. Sorry, I somehow got in my brain that Mandriva was still giving you trouble.

Actually, this isn't good because now I REALLY don't understand where this is going wrong. The output you've posted from your Suse box actually looks more normal that the output from your Mandriva box. The iwconfig, ifconfig and route outputs look the way they should if the network were properly configured and the interrupts look fine.

About the only thing I can think of is that there is a nameserver problem somewhere. I know you said you compared your /etc/resolv.conf files and they were the same, but lets try a little test. Try to navigate to http://64.179.4.149 and see if you can get to LQO. If that works, but navigating to http://www.linuxquestions.org doesn't work, then we have a nameserver problem.

If neither work, then I'm really lost.
 
Old 01-18-2006, 04:07 PM   #24
Capecod
LQ Newbie
 
Registered: Jan 2006
Location: Nantes, FRANCE
Distribution: Mandriva 2006//Fedora Core 4
Posts: 13

Original Poster
Rep: Reputation: 0
Well, i can't connect !!
i use kinternet and the plug dont connect toghether it's like if the system try to etablish the connection but cant.
i'm sad because i'm sure we are not far from the solution, the system "see" the network but something is wrong to etablish the contact. the nameserver are the good one the gw is the good one too. even when i try with dhcp active it's the same
that's too bad

capecod
 
Old 01-18-2006, 04:25 PM   #25
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,791
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
I agree, from what you've posted I see absolutely no reason why you can't connect. The only other suggestions I have would be to check the logs and see if the driver is leaving any messages (both /var/log/syslog and /var/log/messages) or to recompile the driver and try again.
 
Old 01-19-2006, 04:41 AM   #26
Capecod
LQ Newbie
 
Registered: Jan 2006
Location: Nantes, FRANCE
Distribution: Mandriva 2006//Fedora Core 4
Posts: 13

Original Poster
Rep: Reputation: 0
here is the result for var/log/messages and syslog :

Jan 19 08:00:54 linux syslog-ng[3206]: syslog-ng version 1.6.8 starting
Jan 19 08:00:57 linux hcid[5312]: Bluetooth HCI daemon
Jan 19 08:00:57 linux sdpd[5318]: Bluetooth SDP daemon
Jan 19 08:00:57 linux hcid[5312]: HCI dev 0 up
Jan 19 08:00:57 linux hcid[5312]: Starting security manager 0
Jan 19 08:00:57 linux hcid[5312]: return_link_keys (sba=00:A0:96:1E5:2C, dba=00:0A:95:00:A7:34)
Jan 19 08:00:57 linux hidd[5388]: Bluetooth HID daemon
Jan 19 08:00:59 linux syslog-ng[3206]: Changing permissions on special file /dev/xconsole
Jan 19 08:00:59 linux syslog-ng[3206]: Changing permissions on special file /dev/tty10
Jan 19 08:00:59 linux mDNSResponder (Engineering Build) (Sep 9 2005 15:59:08) [5587]: starting
Jan 19 08:00:59 linux mDNSResponder: Unable to parse DNS server list. Unicast DNS-SD unavailable
Jan 19 08:00:59 linux kernel: klogd 1.4.1, log source = /proc/kmsg started.
Jan 19 08:00:59 linux kernel: parport: PnPBIOS parport detected.
Jan 19 08:00:59 linux kernel: parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,ECP,DMA]
Jan 19 08:00:59 linux kernel: lp0: using parport0 (interrupt-driven).
Jan 19 08:00:59 linux kernel: Linux agpgart interface v0.101 (c) Dave Jones
Jan 19 08:00:59 linux kernel: agpgart: Detected NVIDIA nForce2 chipset
Jan 19 08:00:59 linux kernel: agpgart: AGP aperture is 64M @ 0xd8000000
Jan 19 08:00:59 linux kernel: bootsplash: status on console 0 changed to on
Jan 19 08:00:59 linux kernel: usbcore: registered new driver usbfs
Jan 19 08:00:59 linux kernel: usbcore: registered new driver hub
Jan 19 08:00:59 linux kernel: ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
Jan 19 08:00:59 linux kernel: ACPI-0212: *** Warning: Device is not power manageable
Jan 19 08:00:59 linux kernel: ACPI: PCI Interrupt Link [LUBA] enabled at IRQ 5
Jan 19 08:00:59 linux kernel: PCI: setting IRQ 5 as level-triggered
Jan 19 08:00:59 linux kernel: ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [LUBA] -> GSI 5 (level, low) -> IRQ 5
Jan 19 08:00:59 linux kernel: PCI: Setting latency timer of device 0000:00:02.0 to 64
Jan 19 08:00:59 linux kernel: ohci_hcd 0000:00:02.0: OHCI Host Controller
Jan 19 08:00:59 linux kernel: ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 1
Jan 19 08:00:59 linux kernel: ohci_hcd 0000:00:02.0: irq 5, io mem 0xe2087000
Jan 19 08:00:59 linux kernel: i2c_adapter i2c-0: nForce2 SMBus adapter at 0x5000
Jan 19 08:00:59 linux kernel: i2c_adapter i2c-1: nForce2 SMBus adapter at 0x5500
Jan 19 08:00:59 linux kernel: hub 1-0:1.0: USB hub found
Jan 19 08:00:59 linux kernel: hub 1-0:1.0: 3 ports detected
Jan 19 08:00:59 linux kernel: ACPI-0212: *** Warning: Device is not power manageable
Jan 19 08:00:59 linux kernel: ACPI: PCI Interrupt Link [LUBB] enabled at IRQ 11
Jan 19 08:00:59 linux kernel: PCI: setting IRQ 11 as level-triggered
Jan 19 08:00:59 linux kernel: ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [LUBB] -> GSI 11 (level, low) -> IRQ 11
Jan 19 08:00:59 linux kernel: PCI: Setting latency timer of device 0000:00:02.1 to 64
Jan 19 08:00:59 linux kernel: ohci_hcd 0000:00:02.1: OHCI Host Controller
Jan 19 08:00:59 linux kernel: ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 2
Jan 19 08:00:59 linux kernel: ohci_hcd 0000:00:02.1: irq 11, io mem 0xe2082000
Jan 19 08:00:59 linux kernel: hub 2-0:1.0: USB hub found
Jan 19 08:00:59 linux kernel: hub 2-0:1.0: 3 ports detected
Jan 19 08:00:59 linux kernel: ACPI-0212: *** Warning: Device is not power manageable
Jan 19 08:00:59 linux kernel: ACPI: PCI Interrupt Link [LUB2] enabled at IRQ 9
Jan 19 08:00:59 linux kernel: PCI: setting IRQ 9 as level-triggered
Jan 19 08:00:59 linux kernel: ACPI: PCI Interrupt 0000:00:02.2[C] -> Link [LUB2] -> GSI 9 (level, low) -> IRQ 9
Jan 19 08:00:59 linux kernel: PCI: Setting latency timer of device 0000:00:02.2 to 64
Jan 19 08:00:59 linux kernel: ehci_hcd 0000:00:02.2: EHCI Host Controller
Jan 19 08:00:59 linux kernel: ehci_hcd 0000:00:02.2: debug port 1
Jan 19 08:00:59 linux kernel: ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 3
Jan 19 08:00:59 linux kernel: ehci_hcd 0000:00:02.2: irq 9, io mem 0xe2083000
Jan 19 08:00:59 linux kernel: PCI: cache line size of 64 is not supported by device 0000:00:02.2
Jan 19 08:00:59 linux kernel: ehci_hcd 0000:00:02.2: park 0
Jan 19 08:00:59 linux kernel: ehci_hcd 0000:00:02.2: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004
Jan 19 08:00:59 linux kernel: hub 3-0:1.0: USB hub found
Jan 19 08:00:59 linux kernel: hub 3-0:1.0: 6 ports detected
Jan 19 08:00:59 linux kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jan 19 08:00:59 linux kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jan 19 08:00:59 linux kernel: shpchp: shpc_init : shpc_cap_offset == 0
Jan 19 08:00:59 linux kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jan 19 08:00:59 linux kernel: forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.35.
Jan 19 08:00:59 linux kernel: ACPI-0212: *** Warning: Device is not power manageable
Jan 19 08:00:59 linux kernel: ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 5
Jan 19 08:00:59 linux kernel: ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [LMAC] -> GSI 5 (level, low) -> IRQ 5
Jan 19 08:00:59 linux kernel: PCI: Setting latency timer of device 0000:00:04.0 to 64
Jan 19 08:00:59 linux kernel: ieee1394: Initialized config rom entry `ip1394'
Jan 19 08:00:59 linux kernel: SCSI subsystem initialized
Jan 19 08:00:59 linux kernel: libata version 1.12 loaded.
Jan 19 08:00:59 linux kernel: Linux video capture interface: v1.00
Jan 19 08:00:59 linux kernel: ivtv_tveeprom: module not supported by Novell, setting U taint flag.
Jan 19 08:00:59 linux kernel: cx2388x v4l2 driver version 0.0.5 loaded
Jan 19 08:00:59 linux kernel: skge: module not supported by Novell, setting U taint flag.
Jan 19 08:00:59 linux kernel: eth0: forcedeth.c: subsystem: 01043:80a7 bound to 0000:00:04.0
Jan 19 08:00:59 linux kernel: ACPI-0212: *** Warning: Device is not power manageable
Jan 19 08:00:59 linux kernel: ACPI: PCI Interrupt Link [LACI] enabled at IRQ 9
Jan 19 08:00:59 linux kernel: ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [LACI] -> GSI 9 (level, low) -> IRQ 9
Jan 19 08:00:59 linux kernel: PCI: Setting latency timer of device 0000:00:06.0 to 64
Jan 19 08:00:59 linux kernel: BIOS EDD facility v0.16 2004-Jun-25, 3 devices found
Jan 19 08:00:59 linux kernel: intel8x0_measure_ac97_clock: measured 78585 usecs
Jan 19 08:00:59 linux kernel: intel8x0: clocking to 48000
Jan 19 08:00:59 linux kernel: ohci1394: $Rev: 1299 $ Ben Collins <bcollins@debian.org>
Jan 19 08:00:59 linux kernel: ACPI-0212: *** Warning: Device is not power manageable
Jan 19 08:00:59 linux kernel: ACPI: PCI Interrupt Link [LFIR] enabled at IRQ 9
Jan 19 08:00:59 linux kernel: ACPI: PCI Interrupt 0000:00:0d.0[A] -> Link [LFIR] -> GSI 9 (level, low) -> IRQ 9
Jan 19 08:00:59 linux kernel: PCI: Setting latency timer of device 0000:00:0d.0 to 64
Jan 19 08:00:59 linux kernel: ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[9] MMIO=[e2084000-e20847ff] Max Packet=[2048]
Jan 19 08:00:59 linux kernel: usb 3-3: new high speed USB device using ehci_hcd and address 4
Jan 19 08:00:59 linux kernel: ACPI: PCI Interrupt Link [LNK3] enabled at IRQ 11
Jan 19 08:00:59 linux kernel: ACPI: PCI Interrupt 0000:01:08.0[A] -> Link [LNK3] -> GSI 11 (level, low) -> IRQ 11
Jan 19 08:00:59 linux kernel: rt2500 1.1.0 BETA3 2005/07/31 http://rt2x00.serialmonkey.com
Jan 19 08:00:59 linux kernel: ACPI: PCI Interrupt Link [LNK1] enabled at IRQ 5
Jan 19 08:00:59 linux kernel: ACPI: PCI Interrupt 0000:01:0a.0[A] -> Link [LNK1] -> GSI 5 (level, low) -> IRQ 5
Jan 19 08:00:59 linux kernel: cx88[0]: Your board has no valid PCI Subsystem ID and thus can't
Jan 19 08:00:59 linux kernel: cx88[0]: be autodetected. Please pass card=<n> insmod option to
Jan 19 08:00:59 linux kernel: cx88[0]: workaround that. Redirect complaints to the vendor of
Jan 19 08:00:59 linux kernel: cx88[0]: the TV card. Best regards,
Jan 19 08:00:59 linux kernel: cx88[0]: -- tux
Jan 19 08:00:59 linux kernel: cx88[0]: Here is a list of valid choices for the card=<n> insmod option:
Jan 19 08:00:59 linux kernel: cx88[0]: card=0 -> UNKNOWN/GENERIC
Jan 19 08:00:59 linux kernel: cx88[0]: card=1 -> Hauppauge WinTV 34xxx models
Jan 19 08:00:59 linux kernel: cx88[0]: card=2 -> GDI Black Gold
Jan 19 08:00:59 linux kernel: cx88[0]: card=3 -> PixelView
Jan 19 08:00:59 linux kernel: cx88[0]: card=4 -> ATI TV Wonder Pro
Jan 19 08:00:59 linux kernel: cx88[0]: card=5 -> Leadtek Winfast 2000XP Expert
Jan 19 08:00:59 linux kernel: cx88[0]: card=6 -> AverTV Studio 303 (M126)
Jan 19 08:00:59 linux kernel: cx88[0]: card=7 -> MSI TV-@nywhere Master
Jan 19 08:00:59 linux kernel: cx88[0]: card=8 -> Leadtek Winfast DV2000
Jan 19 08:00:59 linux kernel: cx88[0]: card=9 -> Leadtek PVR 2000
Jan 19 08:00:59 linux kernel: cx88[0]: card=10 -> IODATA GV-VCP3/PCI
Jan 19 08:00:59 linux kernel: cx88[0]: card=11 -> Prolink PlayTV PVR
Jan 19 08:00:59 linux kernel: cx88[0]: card=12 -> ASUS PVR-416
Jan 19 08:00:59 linux kernel: cx88[0]: card=13 -> MSI TV-@nywhere
Jan 19 08:00:59 linux kernel: cx88[0]: card=14 -> KWorld/VStream XPert DVB-T
Jan 19 08:00:59 linux kernel: cx88[0]: card=15 -> DViCO FusionHDTV DVB-T1
Jan 19 08:00:59 linux kernel: cx88[0]: card=16 -> KWorld LTV883RF
Jan 19 08:00:59 linux kernel: cx88[0]: card=17 -> DViCO FusionHDTV 3 Gold-Q
Jan 19 08:00:59 linux kernel: cx88[0]: card=18 -> Hauppauge Nova-T DVB-T
Jan 19 08:00:59 linux kernel: cx88[0]: card=19 -> Conexant DVB-T reference design
Jan 19 08:00:59 linux kernel: cx88[0]: card=20 -> Provideo PV259
Jan 19 08:00:59 linux kernel: cx88[0]: card=21 -> DViCO FusionHDTV DVB-T Plus
Jan 19 08:00:59 linux kernel: cx88[0]: card=22 -> pcHDTV HD3000 HDTV
Jan 19 08:00:59 linux kernel: cx88[0]: card=23 -> digitalnow DNTV Live! DVB-T
Jan 19 08:00:59 linux kernel: cx88[0]: card=24 -> Hauppauge WinTV 28xxx (Roslyn) models
Jan 19 08:00:59 linux kernel: cx88[0]: card=25 -> Digital-Logic MICROSPACE Entertainment Center (MEC)
Jan 19 08:00:59 linux kernel: cx88[0]: card=26 -> IODATA GV/BCTV7E
Jan 19 08:00:59 linux kernel: cx88[0]: card=27 -> PixelView PlayTV Ultra Pro (Stereo)
Jan 19 08:00:59 linux kernel: cx88[0]: card=28 -> DViCO FusionHDTV 3 Gold-T
Jan 19 08:00:59 linux kernel: cx88[0]: card=29 -> ADS Tech Instant TV DVB-T PCI
Jan 19 08:00:59 linux kernel: cx88[0]: card=30 -> TerraTec Cinergy 1400 DVB-T
Jan 19 08:00:59 linux kernel: cx88[0]: card=31 -> DViCO FusionHDTV 5 Gold
Jan 19 08:00:59 linux kernel: cx88[0]: subsystem: 0000:0000, board: UNKNOWN/GENERIC [card=0,autodetected]
Jan 19 08:00:59 linux kernel: TV tuner -1 at 0x1fe, Radio tuner -1 at 0x1fe
Jan 19 08:00:59 linux kernel: ACPI: PCI Interrupt Link [LNK2] enabled at IRQ 5
Jan 19 08:00:59 linux kernel: ACPI: PCI Interrupt 0000:01:04.0[A] -> Link [LNK2] -> GSI 5 (level, low) -> IRQ 5
Jan 19 08:00:59 linux kernel: skge addr 0xe1000000 irq 5 chip Yukon-Lite rev 7
Jan 19 08:00:59 linux kernel: skge eth1: addr 00:0e:a6:a7:99:66
Jan 19 08:00:59 linux kernel: i2c-algo-bit.o: (0) scl=1, sda=1
Jan 19 08:00:59 linux kernel: i2c-algo-bit.o: (1) scl=1, sda=0
Jan 19 08:00:59 linux kernel: i2c-algo-bit.o: (2) scl=1, sda=1
Jan 19 08:00:59 linux kernel: i2c-algo-bit.o: (3) scl=0, sda=1
Jan 19 08:00:59 linux kernel: i2c-algo-bit.o: (4) scl=1, sda=1
Jan 19 08:00:59 linux kernel: i2c-algo-bit.o: cx88[0] passed test.
Jan 19 08:00:59 linux kernel: tveeprom(cx88xx internal): Huh, no eeprom present (err=-121)?
Jan 19 08:00:59 linux kernel: cx88[0]/0: found at 0000:01:0a.0, rev: 2, irq: 5, latency: 32, mmio: 0xe0000000
Jan 19 08:00:59 linux kernel: cx88[0]/0: registered device video0 [v4l2]
Jan 19 08:00:59 linux kernel: cx88[0]/0: registered device vbi0
Jan 19 08:00:59 linux kernel: usb 1-1: new low speed USB device using ohci_hcd and address 3
Jan 19 08:00:59 linux kernel: usb 1-2: new full speed USB device using ohci_hcd and address 4
Jan 19 08:00:59 linux kernel: ohci1394: fw-host0: SelfID received outside of bus reset sequence
Jan 19 08:00:59 linux kernel: ieee1394: Host added: ID:BUS[0-00:1023] GUID[00e01800006e11a4]
Jan 19 08:00:59 linux kernel: usb 1-3: new full speed USB device using ohci_hcd and address 5
Jan 19 08:00:59 linux kernel: Bluetooth: Core ver 2.7
Jan 19 08:00:59 linux kernel: NET: Registered protocol family 31
Jan 19 08:00:59 linux kernel: Bluetooth: HCI device and connection manager initialized
Jan 19 08:00:59 linux kernel: Bluetooth: HCI socket layer initialized
Jan 19 08:00:59 linux kernel: Bluetooth: HCI USB driver ver 2.8
Jan 19 08:00:59 linux kernel: usbcore: registered new driver hci_usb
Jan 19 08:00:59 linux kernel: usbcore: registered new driver hiddev
Jan 19 08:00:59 linux kernel: input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:02.0-1
Jan 19 08:00:59 linux kernel: usbcore: registered new driver usbhid
Jan 19 08:00:59 linux kernel: drivers/usb/input/hid-core.c: v2.01:USB HID core driver
Jan 19 08:00:59 linux kernel: Initializing USB Mass Storage driver...
Jan 19 08:00:59 linux kernel: scsi0 : SCSI emulation for USB Mass Storage devices
Jan 19 08:00:59 linux kernel: usb-storage: device found at 5
Jan 19 08:00:59 linux kernel: usb-storage: waiting for device to settle before scanning
Jan 19 08:00:59 linux kernel: usbcore: registered new driver usb-storage
Jan 19 08:00:59 linux kernel: USB Mass Storage support registered.
Jan 19 08:00:59 linux kernel: Bluetooth: L2CAP ver 2.7
Jan 19 08:00:59 linux kernel: Bluetooth: L2CAP socket layer initialized
Jan 19 08:00:59 linux kernel: Bluetooth: HIDP (Human Interface Emulation) ver 1.1
Jan 19 08:00:59 linux kernel: Bluetooth: RFCOMM ver 1.5
Jan 19 08:00:59 linux kernel: Bluetooth: RFCOMM socket layer initialized
Jan 19 08:00:59 linux kernel: Bluetooth: RFCOMM TTY layer initialized
Jan 19 08:00:59 linux kernel: ACPI: Power Button (FF) [PWRF]
Jan 19 08:00:59 linux kernel: ACPI: Power Button (CM) [PWRB]
Jan 19 08:00:59 linux kernel: IA-32 Microcode Update Driver: v1.14 <tigran@veritas.com>
Jan 19 08:01:00 linux kernel: microcode: CPU0 not a capable Intel processor
Jan 19 08:01:00 linux kernel: microcode: No new microcode data for CPU0
Jan 19 08:01:00 linux kernel: IA-32 Microcode Update Driver v1.14 unregistered
Jan 19 08:01:00 linux kernel: NET: Registered protocol family 10
Jan 19 08:01:00 linux kernel: Disabled Privacy Extensions on device c036b920(lo)
Jan 19 08:01:00 linux kernel: IPv6 over IPv4 tunneling driver
Jan 19 08:01:00 linux kernel: bootsplash: status on console 0 changed to on
Jan 19 08:01:00 linux kdm: :0[5518]: pam_unix2: session started for user capecod, service xdm-np
Jan 19 08:01:00 linux sshd[5909]: Server listening on :: port 22.
Jan 19 08:01:00 linux smpppd[5855]: smpppd version 1.59 started
Jan 19 08:01:00 linux /usr/sbin/cron[5962]: (CRON) STARTUP (V5.0)
Jan 19 08:01:01 linux kernel: powernow-k8: Processor cpuid 6a0 not supported
Jan 19 08:01:01 linux ifup: No configuration found for eth0
Jan 19 08:01:01 linux rcpowersaved: CPU frequency scaling is not supported by your processor.
Jan 19 08:01:01 linux rcpowersaved: enter 'CPUFREQD_MODULE=off' in /etc/sysconfig/powersave/cpufreq to avoid this warning.
Jan 19 08:01:01 linux rcpowersaved: Cannot load cpufreq governors - No cpufreq driver available
Jan 19 08:01:01 linux kernel: bootsplash: status on console 0 changed to on
Jan 19 08:01:02 linux ifup: No configuration found for eth1
Jan 19 08:01:02 linux [powersave]: ERROR (CPUFreq_Kernel:21) Can not set ondemand governor, maybe your cpufreq driver is too slow.
Jan 19 08:01:02 linux [powersave]: ERROR (CPUFreq_Kernel:23) Try CPUFREQ_CONTROL=userspace in /etc/sysconfig/powersave/cpufreq.
Jan 19 08:01:02 linux [powersave]: ERROR (PM_Interface:231) Cannot create cpufreq objects
Jan 19 08:01:02 linux kernel: Vendor: USB-DISK Model: FREEDIK-LWFORMAT Rev: 2.23
Jan 19 08:01:02 linux kernel: Type: Direct-Access ANSI SCSI revision: 02
Jan 19 08:01:02 linux kernel: usb-storage: device scan complete
Jan 19 08:01:02 linux kernel: SCSI device sda: 260832 512-byte hdwr sectors (134 MB)
Jan 19 08:01:02 linux kernel: sda: Write Protect is off
Jan 19 08:01:02 linux kernel: sda: Mode Sense: 0b 00 00 08
Jan 19 08:01:02 linux kernel: sda: assuming drive cache: write through
Jan 19 08:01:02 linux kernel: SCSI device sda: 260832 512-byte hdwr sectors (134 MB)
Jan 19 08:01:02 linux kernel: sda: Write Protect is off
Jan 19 08:01:02 linux kernel: sda: Mode Sense: 0b 00 00 08
Jan 19 08:01:02 linux kernel: sda: assuming drive cache: write through
Jan 19 08:01:02 linux kernel: sda: sda1
Jan 19 08:01:02 linux kernel: Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
Jan 19 08:01:02 linux kernel: Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0
Jan 19 08:01:03 linux kernel: Buffer I/O error on device sda1, logical block 260864
Jan 19 08:01:03 linux kernel: Buffer I/O error on device sda1, logical block 260865
Jan 19 08:01:03 linux kernel: Buffer I/O error on device sda1, logical block 260866
Jan 19 08:01:03 linux kernel: Buffer I/O error on device sda1, logical block 260867
Jan 19 08:01:03 linux kernel: Buffer I/O error on device sda1, logical block 260868
Jan 19 08:01:03 linux kernel: Buffer I/O error on device sda1, logical block 260869
Jan 19 08:01:03 linux kernel: Buffer I/O error on device sda1, logical block 260870
Jan 19 08:01:03 linux kernel: Buffer I/O error on device sda1, logical block 260871
Jan 19 08:01:03 linux kernel: Buffer I/O error on device sda1, logical block 260864
Jan 19 08:01:03 linux kernel: Buffer I/O error on device sda1, logical block 260865
Jan 19 08:01:05 linux ifup: No configuration found for sit0
Jan 19 08:01:06 linux hal-subfs-mount[6698]: SYMLINKS:: disk/by-id/usb-USB-DISK_FREEDIK-LWFORMAT_SN12345678901 disk/by-path/usb-SN12345678901:0:0:0
Jan 19 08:01:06 linux hal-subfs-mount[6698]: MOUNT_POINT:: /media/usbdisk
Jan 19 08:01:06 linux hal-subfs-mount[6698]: MOUNTPOINT:: /media/usbdisk
Jan 19 08:01:06 linux kernel: subfs 0.9
Jan 19 08:01:06 linux hal-subfs-mount[6698]: Collected mount options and Called(0) /bin/mount -t subfs -o fs=floppyfss,sync,procuid,nosuid,nodev,exec,utf8=true /dev/sda1 "/media/usbdisk"
Jan 19 08:01:06 linux udevd[2634]: get_netlink_msg: no ACTION in payload found, skip event 'mount'
Jan 19 08:01:09 linux modprobe: FATAL: Error inserting sonypi (/lib/modules/2.6.13-15-default/kernel/drivers/char/sonypi.ko): No such device
Jan 19 08:01:09 linux udevd[2634]: get_netlink_msg: no ACTION in payload found, skip event 'umount'
Jan 19 08:01:10 linux kernel: ra0: no IPv6 routers present
Jan 19 08:01:27 linux hp: unable to open /var/run/hpiod.port: No such file or directory: prnt/hpijs/hplip_api.c 75
Jan 19 08:09:43 linux modprobe: FATAL: Error inserting sonypi (/lib/modules/2.6.13-15-default/kernel/drivers/char/sonypi.ko): No such device

**************

## Path: System/Logging
## Description: System logging
## Type: list(0,1,2,3,4,5,6,7)
## Default: 1
## Config: ""
## ServiceRestart: syslog
#
# Default loglevel for klogd
#
KERNEL_LOGLEVEL=1

## Type: string
## Default: ""
## Config: ""
## ServiceRestart: syslog
#
# if not empty: parameters for syslogd
# for example SYSLOGD_PARAMS="-r -s my.dom.ain"
#
SYSLOGD_PARAMS=""

## Type: string
## Default: -x
## Config: ""
## ServiceRestart: syslog
#
# if not empty: parameters for klogd
# for example KLOGD_PARAMS="-x" to avoid (duplicate) symbol resolution
#
KLOGD_PARAMS="-x"

## Type: list(syslogd,syslog-ng)
## Default: syslogd
## Config: syslog-ng
## Command: /sbin/rcsyslog restart
## PreSaveCommand: /sbin/rcsyslog status && /sbin/rcsyslog stop
#
# The name of the syslog daemon used as
# syslog service: "syslogd", "syslog-ng"
#
SYSLOG_DAEMON="syslog-ng"

## Type: yesno
## Default: yes
## Config: syslog-ng
## ServiceRestart: syslog
#
# If you don't want to let SuSEconfig generate your
# syslog-ng configuration file, set this to "no".
#
# SuSEconfig is using a template configuration file
# /etc/syslog-ng/syslog-ng.in
# you can adopt it to your needs instead...
#
SYSLOG_NG_CREATE_CONFIG="yes"

## Type: string
## Default: ""
## Config: ""
## ServiceRestart: syslog
#
# Parameters for Syslog New-Generation - see syslog-ng(8)
#
SYSLOG_NG_PARAMS=""

Unfortunatly i think i will stpo to try suse because even when the router if off and dhcp activ i still cant connect
that's too bad because i like this box !! but....

thank's for your help hangdog42

capecod
 
Old 01-19-2006, 10:53 AM   #27
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,791
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
I agree that not using Suse may be the only real solution here. Nothing really jumps out of the logs as the wireless card complaining about anything. To be honest, this has been one of the strangest and most frustrating problems I've seen in this forum. As far as I can tell you've got everything correct, but it still doesn't work. Weird.
 
Old 01-19-2006, 12:02 PM   #28
Capecod
LQ Newbie
 
Registered: Jan 2006
Location: Nantes, FRANCE
Distribution: Mandriva 2006//Fedora Core 4
Posts: 13

Original Poster
Rep: Reputation: 0
i try this
linux:/home/capecod # arp -n
Address..........HWtype.........HWaddress..........Flags Mask..........Iface
192.168.0.254..................(incomplete).................................. ra0

i have this in cat /var/log/messages
Jan 19 17:22:14 linux kernel: ra0: no IPv6 routers present

and i try this
linux:/home/capecod # ifup-dhcp ra0
Starting DHCP Client Daemon on ra0... . . . . . no IP address yet... backgrounding.

linux:/home/capecod # ifup-dhcp ra0
DHCP client is already running on ra0
linux:/home/capecod #
 
Old 01-19-2006, 03:07 PM   #29
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,791
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Well the arp output means that your router isn't responding to the request. Unfortunately I don't think that it is telling us anything we didn't already know, namely that the card isn't communicating with anything.

The IPv6 message is really meaningless unless you are on a network that uses IPv6. All it really means is that the IPv6 protocol has been enabled in the kernel.

And the ifup commands are also not telling us anything new. The bottom line is that the card is not communicating with the router effectively. The only thing you haven't tried is to recompile the ra driver.
 
Old 01-20-2006, 02:04 AM   #30
Capecod
LQ Newbie
 
Registered: Jan 2006
Location: Nantes, FRANCE
Distribution: Mandriva 2006//Fedora Core 4
Posts: 13

Original Poster
Rep: Reputation: 0
Ok, and is it easy to make this ?

How am i suppose to do ?

Can yu give me the way ?

Thanks again

Capecod
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Bridging a wired network to a wifi network bobmcobob Linux - Wireless Networking 2 07-18-2008 07:36 PM
mandriva2006 cannot partition Sata HD w. Intel controller erwan.chauty Mandriva 17 02-23-2006 06:38 PM
INFRARED & Screen Resolution - Mandriva2006 kmaltese Mandriva 1 11-23-2005 07:44 PM
WIFI: Interface could not be set up. Bundy Linux - Wireless Networking 1 10-06-2005 08:11 PM
how do you set up your Linux box to route secure wifi? richard3403 Linux - Wireless Networking 0 11-15-2003 03:40 PM


All times are GMT -5. The time now is 03:58 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration