ramfree17

ditto. I used to use them but now typing linux (or my distro) first then my keywords deliver the same value that I need. ciao!

this is not meant to be any consolation but if everything still turns out for the worse then i will add adamw's name to this list: civileme, tom. to the young whippersnappers, just know that those are great names when it comes to mandy's user rapport. ciao!

good for you. my solution was to downgrade the encryption of my router to WEP which is relatively safe in my neighborhood. :-| ciao!

in my case that means that whenever i do a system upgrade i scratch my head thinking why i am pulling down a lot of package for software that i don't recognize. i understand dependencies but i am assuming that most of those are small libraries instead of big multi-megabyte files. :) ciao!

ok, i thought .bashrc is read everytime a new bash shell is launched and it was the .bash_profile that was only read during login. my bash literature is getting rusty. :D ciao!

i think sourcing the new .bashrc is enough but the readonly variables will not be reset (like the TMOUT variable). $ . ~/.bashrc or $ source ~/.bashrc i might be mistaken though. :huh: ciao!

here iis the wpa_cli output whever i configure/connect the wireless interface Selected interface 'wlan0' Interactive mode > <2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys <2>CTRL-EVENT-TERMINATING - signal 15 received 'PING' command timed out. Connection to wpa_supplicant lost - trying to reconnect Connection to wpa_supplicant re-established <2>WPA: Key negotiation completed with 00:13:46:41:d2:62 [PTK=TKIP GTK=TKIP] <2>CTRL-EVENT-CONNECTED - Connection to 00:13:46:41:d2:62 completed (auth) [id=0 id_str=] there isnt any activity posted when i try to get a new DHCP offer though. i am using a DLink router so i tried disabling the Turbo G enhancements but the results are the same. i downgraded the encryption to WEP and now i can connect wirelessly (posting it while inside the bedroom, :) ). i think i will hold off using ndiwsrapper untill i can find another WPA access point to isolate that the problem is really with the driver and not my access point. any further suggestions would be welcome though. :) ciao!

this may sound pretty basic but have you checked the md5sum of the installer ISO images before you burned them? i am posting from my Wind and have reinstalled mdv2009.0 at least twice (since the rc versions). everything is working except the WPA but adamw is helping me on that front. btw, i used the cd images since i don't have a free DVD drive hanging around. ciao!

its showing the same output. i read about iwconfig and wpa_supplicant thinking that maybe i can force it manually but found out that wpa_supplicant is already running as a daemon and the configuration for my AP is correctly entered in the wpa_supplicant configuration file. if there are no other option to try then over the weekend i am thinking of downgrading my access point to WEP since nobody near our house seems to use any computer so its fairly "safe". if that fails then i will try the ndiswrapper route again. :( ciao!

wouldnt that overwrite the whole file (aka redirection)? the original problem is to truncate a file up to a certain point so that the file contents is still usable and space is freed up. ciao!

the gui drakconnect hits the same "blank" wireless network list[1] so i switched to using the console mode. everything went according to the expected screens and i got a congratulatory remark at the end. the wireless card is still unable to get any IP address from the server and the only errors in the console is the SIOCETHTOOL: Operation not supported message. :( ciao!

netbook computers preloaded with linux get returned not because its hard to configure but because people expect it to be windows, missed reading the OS part and concentrates on the price difference. gizmodo or engadget had a side comment that its a sorry state that people fail the basic reading comprehension and blame it on the operating system. ciao!

uploading take 2. ciao! dmesg.txt

oh crap, its missing. i spent 5 minutes uploading that 41kb file last night as my internet connection was dog slow. ill re-upload it later and duplicate in my blog. sorry. ciao!

uploading the output of my dmesg. the last lines was produced when i tried using the kde applet to connect to the wireless ap. ciao!

thanks adamw. ill post the dmesg message tonight. the iwconfig output is already in the quoted terminal commands (third from the bottom). ciao!

Getting Linux wireless connectivity in my Wind has been my only gripe and some of you might have already read about it in this thread. With the official release of 2009.0, i decided to download the two CDs and reinstall mandriva. I configured the sources from the easyurpmi site because the official update api site keeps on throwing me to a site that fails to add (maybe its in the middle of a synchronization process). Anyway, I configured the wireless card using the network center instead of going straight to drakconnect. It downloaded all the prerequisite software to use the native drivers (rtls8187se), installs everything properly (assumed since i did not see any error) and at the end it detects the correct signal. I configured it with the correct passkey (please see wifi-config.png, i changed it for the screenshot :) ) but nothing happens when I press connect except this message in the console SIOCETHTOOL: Operation not supported i tried executing dhclient and dhcpcd in the cli since i was able to do that in my fujitsu laptop but i didnt get any offers. dhcpcd just fails. below is the output of the various commands that I tried: [root@localhost /tmp]# ifconfig eth0 Link encap:Ethernet HWaddr 00:1D:92:58:4F:32 inet addr:192.168.0.102 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::21d:92ff:fe58:4f32/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2129 errors:0 dropped:1374996811 overruns:0 frame:0 TX packets:1495 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1848620 (1.7 MiB) TX bytes:109616 (107.0 KiB) Interrupt:16 Base address:0x4000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:22 errors:0 dropped:0 overruns:0 frame:0 TX packets:22 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1100 (1.0 KiB) TX bytes:1100 (1.0 KiB) wlan0 Link encap:Ethernet HWaddr 00:1D:92:C6:6C:35 inet6 addr: fe80::21d:92ff:fec6:6c35/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5 errors:0 dropped:844 overruns:0 frame:0 TX packets:287 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:645 (645.0 b) TX bytes:10775 (10.5 KiB) Interrupt:17 Memory:f8bf8000-f8bf8100 [root@localhost /tmp]# dhcpcd wlan0 Error, wlan0: timed out Error, wlan0: lease information file `/var/lib/dhcpcd/dhcpcd-wlan0.info' does not exist Warning, wlan0: using IPV4LL address 169.254.83.14 [root@localhost /tmp]# dhclient wlan0 Internet Systems Consortium DHCP Client V3.0.7 Copyright 2004-2008 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Listening on LPF/wlan0/00:1d:92:c6:6c:35 Sending on LPF/wlan0/00:1d:92:c6:6c:35 Sending on Socket/fallback DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7 No DHCPOFFERS received. No working leases in persistent database - sleeping. [root@localhost /tmp]# iwconfig lo no wireless extensions. eth0 no wireless extensions. wlan0 802.11b/g linked ESSID:"kaboom" Mode:Managed Frequency=2.437 GHz Access Point: 00:13:46:41:D2:62 Bit Rate=54 Mb/s Retry:on RTS thr:off Fragment thr:off Encryption key:off Power Management timeout:0us mode:All packets received Link Quality=94/100 Signal level=-156 dBm Noise level=6 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 [root@localhost /tmp]# iwlist wlan0 scanning wlan0 Scan completed : Cell 01 - Address: 00:13:46:41:D2:62 ESSID:"kaboom" Protocol:IEEE 802.11bg Mode:Master Channel:6 Encryption key:on Bit Rates:54 Mb/s Extra: Rates (Mb/s): 1 2 5.5 9 11 6 12 18 24 36 48 54 Quality=94/100 Signal level=-173 dBm Noise level=17 dBm IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : PSK Extra: Last beacon: 44ms ago [root@localhost /tmp]# ifup wlan0 Determining IP information for wlan0... failed. [root@localhost /tmp]# any other suggestions on how to proceed? just this thing and my wind will finally be windows free when i am not using it for work. :) thanks! ciao!

mousepad is a nice gui-based text editor. and im a long-time vi(m) user. :) ciao!

wine+utorrent is still my preferred torrent combination. if i need to reboot to windows to do some work, i can still continue my torrents. :) ciao!

just a quick update: - the terminal drakconnect works as it can see my access point. dhclient can't find any offers so i still cant get an ip address on the wifi. im basically on the smae boat as xubuntu. :( - i noticed a message in the startup that it cant load the rtl8187se drivers because the kernel source rpm is not installed. unfortunately the kernel has already been upgraded since i can't find the matching kernel src rpm for the one i installed. i also found a rtls8187se-enabled kernel and downloaded that but as adamw said i have to do something to the modprobe.conf so ill post it when i have some free time to tinker. thanks. ciao!

i haven't seen any message and when i try to replicate it again it goes directly to the wireless selection screen. i already tried unloading the ndiswrapper driver and uninstalling ndiswrapper but to no avail. i will try the console drakconnect tip when i get home. thanks. ciao!

i was able to install rc9, and it detected the wifi card to be needing the r8080 modules. however when configuring the card after the installation failed because it cannot install the dkms modules. i tried setting up via the ndiswrapper route and the dialog reported a success but i am just getting a blank page in the "select your wireless network" part. :( ciao!

i havent been able to install mandriva in my wind yet but my model is with the first batch that uses the 8187SE module. The bottom sticker has these details: FCC ID: TX2-RTL8187SE IC ID: 6317A-RTL8187SE my understanding is that the new models may have one of the two new modules with better linux support. :( ciao!

fdany, did you install anything special for the wireless to work? are you using the MSI-released linux drivers or ndiswrapper on the windows drivers? ciao!