Launch default application from file in command line.
Hello there, Is it possible to launch a default application with a file from the command line, e.g. something like: ./myfile.pdf which would retrieve the default PDF viewer and launch it on myfile? For the moment, I have a bash script called with launch argument, which analyzes the extension of argument and calls the program; e.g. launch myfile.pdf spots pdf and calls evince myfile.pdf. The problem is that it won't follow automatically if I decide to change my default PDF viewer or in case I create a new file/program association (unless I make the script read some configuration file somewhere, I suppose). Any idea? Best, Paul -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4edcd982.4090...@free.fr
Re: Launch default application from file in command line.
Le 05/12/2011 15:51, afuentes a écrit : $ gnome-open file.pdf it the same that double clicking on file.pdf from gnome I have an alias like thsi alias go='gnome-open' so i just have to type $ go file.pdf Wonderful, thank you! Paul -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4edcdab1.8090...@free.fr
Re: Launch default application from file in command line.
Le 05/12/2011 15:55, Andreas Rönnquist a écrit : For a non-gnome-specific alternative, take a look at xdg-open. Better yet, thanks. Le 05/12/2011 16:17, Raf Czlonka a écrit : [0] http://www.zsh.org/ Being a Linux newbie, I'll stick to the default shell for the moment, although I'll probably consider alternatives later :) Best, Paul -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4edce278.9030...@free.fr
Re: Detach Icedove from xterm itself called from terminal.
Em 01-12-2011 11:08, Chris Davies escreveu: Paul Isambertzappathus...@free.fr wrote: But Icedove still stays attached to the first terminal... Just to check, you want to be able to start icedove from the command line in (say) an xterm, but have it continue to run even when that xterm is closed? No: launch icedove from a terminal itself launched from a terminal. I have a Lua script which calls os.execute(program), and as Clive remarked, this calls a shell. The Lua script itself is called from a terminal, and I would like everything to close when the program is launched. I made the double terminal example, because that's basically the same problem (it seems to me). snip Le 01/12/2011 16:59, Iuri Guilherme dos Santos Martins a écrit : Well, if you are willing to learn bash then what I would recommend is exactly what Chris said: you run an external script (whose first line would be #!/bin/bash) with the necessary commands to make exactly what you wanted. Yeah, I think learning bash will be definitely simpler. But I love Lua... and don't really want to learn a new language, even though now that I use Debian, learning bash won't be wasting time... Paul
Re: Detach Icedove from xterm itself called from terminal.
Le 01/12/2011 20:36, Iuri Guilherme dos Santos Martins a écrit : Now I get it, You must use the same command i sent you, however in the Lua language you should have an option to detach the command from the terminal Unfortunately, there is no such thing. That should work (assuming that now i did understand what you are doing). You did :) Paul
Detach Icedove from xterm itself called from terminal.
Hello there, When started from gnome-terminal, Icedove stays attached to it. I can detach it by executing icedove . The problem is, I can't seem to do that recursively, i.e. from the terminal call another terminal which calls icedove . The following works: xterm -e 'icedove' (with Icedove attached to xterm), but xterm -e 'icedove ' doesn't (xterm starts and closes immediately). Any idea? Best, Paul -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ed60166.5040...@free.fr
Re: Detach Icedove from xterm itself called from terminal.
Le 30/11/2011 14:29, Clive Standbridge a écrit : Paul Isambert wrote: Hello there, When started from gnome-terminal, Icedove stays attached to it. I can detach it by executing icedove. The problem is, I can't seem to do that recursively, i.e. from the terminal call another terminal which calls icedove. The following works: xterm -e 'icedove' (with Icedove attached to xterm), but xterm -e 'icedove' doesn't (xterm starts and closes immediately). Any idea? Hi Paul, First, about the error. Given the -e option, xterm runs the next argument instead of the shell that it would run by default. So it's trying to run an executable called 'icedove', can't find it, and exits. The '' is shell syntax; you need to run a shell in the xterm. The shell would need to both run the icedove command in the background, and produce an interactive prompt. I don't know if there is a straightforward way of doing that. The best I can think of is xterm -e bash --rcfile(echo icedove \) or if you want the usual initialisation files to run, you could do xterm -e bash --rcfile(cat /etc/bash.bashrc ~/.bashrc; echo icedove \) or use a dedicated rcfile: xterm -e bash --rcfile ~/.my-icedove-rcfile where ~/.my-icedove-rcfile contains . /etc/bash.bashrc . ~/.bashrc icedove There are a couple of things I haven't figured out: This does not to allow you to bring the icedove to the foreground. Nor does it seem to show stdout/stderr from icedove in the xterm, which I guess you want. Thanks Clive for your help. Unfortunately Icedove stays attached to the uppermost terminal (which I want to close too, perhaps that wasn't clear). Even with the simplest form: bash --rcfile (echo icedove \) when I close the terminal, it closes Icedove. But at least I have learnt something! Best, Paul -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ed63e54.9070...@free.fr
Re: Detach Icedove from xterm itself called from terminal.
Le 30/11/2011 15:52, Iuri Guilherme dos Santos Martins a écrit : I did not understand what you wanted, but i guess `xterm -e `icedove ` ` is close to the command you are looking for. The `` are used by bash to open a sub shell. (Assuming you are using bash). Thank you Iuri, but the terminal still stays open. What I want to do is the following: I have a Lua script which lets me selects programs, then calls them with os.execute(program), and the terminal where the Lua script runs closes too. Only with Icedove it stays attached, so I'm trying very hard to detach it so the terminal can close. Best, Paul
Re: Detach Icedove from xterm itself called from terminal.
Le 30/11/2011 17:02, Clive Standbridge a écrit : I don't know anything about Lua, but searching around suggests that os.execute executes its command in a shell, not directly. In that case you should be able to use a command like icedove No, that didn't work, the terminal closes and icedove never opens. but if that causes icedove to be closed immediately, you could try nohup icedove Doesn't work either. However, without the ampersand, the terminal doesn't close but at least Icedove isn't attached to it, so I can close the terminal manually. Le 30/11/2011 17:25, Iuri Guilherme dos Santos Martins a écrit : Well, the example i gave you opens another terminal (xterm) and opens icedove without closing the first terminal nor the second (assuming that you was using xterm in the first place). If you want the terminal to be closed, you may use: echo exit xterm -e `icedove ` (if you want the xterm you use to open icedove closes) But Icedove still stays attached to the first terminal... I know it would be just simpler to write everything as a shell script directly, but I'm unfamiliar with the language, whereas I have some experience in Lua. Thanks to both, Paul
Re: Xfce steals keyboard shortcuts?
Le 28/11/2011 12:08, Lorenzo Sutton a écrit : Hi, On 27/11/11 16:48, Paul Isambert wrote: Thank you Roman. Removing Alt-F2 in the shortcut settings did give me some Alt-shortcuts back, but Ctrl-shortcuts still won't work, even when I remove everything in the settings. Any idea? I also came across this trying to use Inkscape. The CTRL + Fn key shortcuts are by default take by the Workspace n shortcuts. These are defined in the Settings Window Manager menu under the Keyboard tab It does, as did Roman's last mail, which unfortunately I've missed because I was migrating Thunderbird. In the meanwhile, I've found a solution using xfconf, but the window manager is much simpler. Thanks both, Paul -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ed37a91.8040...@free.fr
Laptop doesn't sleep when lid is closed (Xfce).
Hello, I've set xfce4-power-manager to sleep when the lid is closed, no matter whether I'm on AC or battery. The problem is that it doesn't work. Strangely, though, if I close the lid when on AC (resp. battery), reopen it and go on battery (resp. AC), the computer goes to sleep, and restarts immediately since the lid is open. I've removed gnome-power-manager, but to no avail. Any idea? Best, Paul
Xfce steals keyboard shortcuts?
Hello, I've installed gVim with Xfce. My shortcuts made of Ctrl-F1 to Ctrl-F12 and Alt-F1 to Alt-F12 doesn't work. Instead, they seem to be executed for Xfce: I've noticed that because Alt-F2 launches an app in Xfce, and that's what happens in gVim too. So is it possible to give control to all shortcuts to gVim? Best, Paul -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ed255cf.1000...@free.fr
Re: Xfce steals keyboard shortcuts?
Thank you Roman. Removing Alt-F2 in the shortcut settings did give me some Alt-shortcuts back, but Ctrl-shortcuts still won't work, even when I remove everything in the settings. Any idea? Paul On 27/11/2011 16:41, Roman Khomasuridze wrote: Hi, Yes, Xfce does still some shortcuts (never came acroos problems with F1 to F12). you can define Xfce specific shortcuts in settings - keyboard so that they wont interfere with yours. Regards - Roman On Sun, Nov 27, 2011 at 7:22 PM, Paul Isambert zappathus...@free.fr mailto:zappathus...@free.fr wrote: Hello, I've installed gVim with Xfce. My shortcuts made of Ctrl-F1 to Ctrl-F12 and Alt-F1 to Alt-F12 doesn't work. Instead, they seem to be executed for Xfce: I've noticed that because Alt-F2 launches an app in Xfce, and that's what happens in gVim too. So is it possible to give control to all shortcuts to gVim? Best, Paul -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org mailto:debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org mailto:listmas...@lists.debian.org Archive: http://lists.debian.org/4ed255cf.1000...@free.fr
Re: No more desktop.
Quoting Richard richard.b...@blueyonder.co.uk: On Fri, 25 Nov 2011 16:44:34 +0100 Paul Isambert zappathus...@free.fr wrote: Le 25/11/2011 12:46, Paul Isambert a écrit : Hello there again, I must be cursed. As explained before, I succeeded in having my wifi work by switching to wheezy, following Nicolas's solution. Then I just wanted to install Vim (gVim actually). Synaptic told me there were tons of things to do, which I did, except it broke here and there (on thing was that dialog [box, I suppose] was impossible because TERM was not set, and indeed the details of progress appeared in command-line style); update was cancelled. I started again, it apparently progressed a little bit more, but still failed. I can't remembered exactly what happened, but some things were related to Gnome. Anyway, gVim was installed, but I'd lost e.g. NetworkManager in the taskbar (although I still had an internet connection), so I thought rebooting might be good. Alas, after rebooting, I had no desktop anymore, simply the commandline. I updated Gnome, just in case, but still no desktop. I launched synaptic safe-upgrade, which did a lot of things, but didn't gave me the desktop back, even after reboot. So, what have I done wrong again? startx was the solution (I could have searched the web *before* asking here). Sorry for the noise. Paul Hi you could try deleting /etc/X11/xorg.conf, if there is corruption there, deleting it will force xconfig. just a guess HTH Everything is fine now. I've just replaced Gnome with Xfce, because Gnome doesn't work well with wheezy for the moment. Paul -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1322294564.4ed09d24e3...@imp.free.fr
Re: No more desktop.
Quoting Richard richard.b...@blueyonder.co.uk: On Sat, 26 Nov 2011 09:02:44 +0100 Paul Isambert zappathus...@free.fr wrote: Quoting Richard richard.b...@blueyonder.co.uk: On Fri, 25 Nov 2011 16:44:34 +0100 Paul Isambert zappathus...@free.fr wrote: Le 25/11/2011 12:46, Paul Isambert a écrit : Hello there again, I must be cursed. As explained before, I succeeded in having my wifi work by switching to wheezy, following Nicolas's solution. Then I just wanted to install Vim (gVim actually). Synaptic told me there were tons of things to do, which I did, except it broke here and there (on thing was that dialog [box, I suppose] was impossible because TERM was not set, and indeed the details of progress appeared in command-line style); update was cancelled. I started again, it apparently progressed a little bit more, but still failed. I can't remembered exactly what happened, but some things were related to Gnome. Anyway, gVim was installed, but I'd lost e.g. NetworkManager in the taskbar (although I still had an internet connection), so I thought rebooting might be good. Alas, after rebooting, I had no desktop anymore, simply the commandline. I updated Gnome, just in case, but still no desktop. I launched synaptic safe-upgrade, which did a lot of things, but didn't gave me the desktop back, even after reboot. So, what have I done wrong again? startx was the solution (I could have searched the web *before* asking here). Sorry for the noise. Paul Hi you could try deleting /etc/X11/xorg.conf, if there is corruption there, deleting it will force xconfig. just a guess HTH Everything is fine now. I've just replaced Gnome with Xfce, because Gnome doesn't work well with wheezy for the moment. Paul Strange Paul, I'm running gnome from wheezy/sid and its OK, nice and stable, so wheezy should be OK. Gnome told me on startup that it would run in restricted mode, probably because my video card didn't support it (or so I remember). But I'm quite happy with Xfce, so I don't mind! Paul -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1322302275.4ed0bb4387...@imp.free.fr
Re: Make WiFi work.
Le 24/11/2011 21:52, Selim T. Erdogan a écrit : Paul Isambert, 24.11.2011: You're absolutely right. So here's a detailed account of what I've done, following what was exposed (in French) here: http://doc.ubuntu-fr.org/ndiswrapper (Yeah, it's for Ubuntu, but that seemed good to me anyway.) From your next message, I saw that you solved your problem by upgrading. (That's my favorite way to solve things too!) Still, in case you need it later, and for completeness, let me say a couple of things about ndiswrapper. (In my case, the native driver, rt2500pci, has problems if the signal is low and/or in ad-hoc mode, so it's useful to be able switch to ndiswrapper occasionally.) Good idea, I might need it later. 1. I've copied the WinXP driver files (it was recommended to use those, even if they're 32bits and I have 64bits) into /home/wifi, created just for that. 2. Then, into that directory, I've done ndiswrapper -i net8192cu.inf 3. I've checked with ndiswrapper -l, which returned: net8192cu: driver installed. (There were other failed drivers from previous attempts; I removed them.) 4. I've done ndiswrapper -m, which returned: WARNING: All config files need .conf: /etc/modprobe.d/ndiswrapper, it will be ignored in a future release. module configuration already contains alias directive The existing alias directive must come from a previous manipulation. It's been a long time since I performed these steps but I don't remember needing this -m step for my driver. That was in the webpage I followed. 5. Then modprobe ndiswrapper returned: WARNING: All config files need .conf: /etc/modprobe.d/ndiswrapper, it will be ignored in a future release. FATAL: Module ndiswrapper not found. On the machine where I use ndiswrapper there's nothing related to it in the /etc/modprobe.d/ directory. (Another hint that the -m step was not necessary for me?) The message saying that the module was not found is important. I think that French page that you linked to had instructions for compiling the module, but I don't see any such steps in your message. Did you compile the module? (What does /sbin/modinfo ndiswrapper say?) No, I didn't I installed the package from the repository directly with dpkg (actually I installed two packages:ndiswrapper-common and ndiswrapper-utils). I can't remember if this came up before, but there is a package called ndiswrapper-source. I install that and whenever I upgrade the kernel I need to rebuild the module for the new kernel. I do this with the help of the module-assistant package. Thanks for the info, I'll do that. (BTW, I recommend installing the linux-headers-... meta-package for your architecture, otherwise you won't be able to build the module for your new kernels.) Anyway, with module-assistant m-a a-i ndiswrapper will build a deb package for the module and install it.) The linux-headers stuff is installed. I needed that when I followed another course of action: building the drivers from Realtek. Thanks, Paul -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ecf5ff2.3060...@free.fr
No more desktop.
Hello there again, I must be cursed. As explained before, I succeeded in having my wifi work by switching to wheezy, following Nicolas's solution. Then I just wanted to install Vim (gVim actually). Synaptic told me there were tons of things to do, which I did, except it broke here and there (on thing was that dialog [box, I suppose] was impossible because TERM was not set, and indeed the details of progress appeared in command-line style); update was cancelled. I started again, it apparently progressed a little bit more, but still failed. I can't remembered exactly what happened, but some things were related to Gnome. Anyway, gVim was installed, but I'd lost e.g. NetworkManager in the taskbar (although I still had an internet connection), so I thought rebooting might be good. Alas, after rebooting, I had no desktop anymore, simply the commandline. I updated Gnome, just in case, but still no desktop. I launched synaptic safe-upgrade, which did a lot of things, but didn't gave me the desktop back, even after reboot. So, what have I done wrong again? Thanks in advance, Paul -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ecf7ff8.10...@free.fr
Re: No more desktop.
Le 25/11/2011 12:46, Paul Isambert a écrit : snip I launched synaptic safe-upgrade, snip Sorry, that was aptitude safe-upgrade Paul -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ecf809b.5080...@free.fr
Re: No more desktop.
Le 25/11/2011 12:46, Paul Isambert a écrit : Hello there again, I must be cursed. As explained before, I succeeded in having my wifi work by switching to wheezy, following Nicolas's solution. Then I just wanted to install Vim (gVim actually). Synaptic told me there were tons of things to do, which I did, except it broke here and there (on thing was that dialog [box, I suppose] was impossible because TERM was not set, and indeed the details of progress appeared in command-line style); update was cancelled. I started again, it apparently progressed a little bit more, but still failed. I can't remembered exactly what happened, but some things were related to Gnome. Anyway, gVim was installed, but I'd lost e.g. NetworkManager in the taskbar (although I still had an internet connection), so I thought rebooting might be good. Alas, after rebooting, I had no desktop anymore, simply the commandline. I updated Gnome, just in case, but still no desktop. I launched synaptic safe-upgrade, which did a lot of things, but didn't gave me the desktop back, even after reboot. So, what have I done wrong again? startx was the solution (I could have searched the web *before* asking here). Sorry for the noise. Paul -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ecfb7e2.9000...@free.fr
Re: Make WiFi work.
Le 23/11/2011 17:55, Richard a écrit : On Wed, 23 Nov 2011 09:59:29 -0600 Hugo Vanwoerkomhvw59...@care2.com wrote: Joel Roth wrote: On Wed, Nov 23, 2011 at 08:06:32AM +0100, Paul Isambert wrote: Le 22/11/2011 20:52, Joel Roth a écrit : On Tue, Nov 22, 2011 at 03:29:44PM +0100, Paul Isambert wrote: snip Alternatively, you can buy a cheap USB wireless device that *is* supported, till you can get the Realtek stuff sorted out. have fun snip Seems like a good idea but how harde is that to research? If I look into NewEgg under Computer Hardware Networking Wireless Networking Wireless Adapters, the lowest price USB adapter is: http://www.newegg.com/Product/Product.aspx?Item=N82E16833180074 for US$8.99, not expensive. But it does not mention the chipset and the feedback has 1 user saying that he installed it under Linux with difficulty. Another one: http://www.newegg.com/Product/Product.aspx?Item=N82E16833166049 is US$11.99 and 2 users say it installed out of the box in Linux, but don't mention the distrubution, 1 user says it installed with Ubuntu. The details don't mention the chipset either. Hugo The later uses the RTL8712/8188/8191/8192SU series Funny (so to speak) twist: I've bought a wifi USB stick which said Linux on the box. I thought installing the driver would be easy (like a Windows installer, of course!) -- but no, apprently it's made for 32-bit architecture, and mine is 64-bit. I've tried to compile nonetheless, but that didn't work. So now I have a useless USB stick, still no wifi, not to mention the book I could have bought instead... Paul -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ece07a5.4000...@free.fr
Re: Make WiFi work.
Le 24/11/2011 10:08, richard.b...@blueyonder.co.uk a écrit : What about ndiswrapper ? A promising lead. So I've tried that; ndiswrapper works, but then modprobe doesn't recognize it (it says something about .conf files, too). Perhaps I've done something wrong earlier (I've done so many things). Paul -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ece1749.20...@free.fr
Re: Make WiFi work.
Le 24/11/2011 12:05, Selim T. Erdogan a écrit : Paul Isambert, 24.11.2011: Le 24/11/2011 10:08, richard.b...@blueyonder.co.uk a écrit : What about ndiswrapper ? A promising lead. So I've tried that; ndiswrapper works, but then modprobe doesn't recognize it (it says something about .conf files, too). Perhaps I've done something wrong earlier (I've done so many things). I realize it's difficult to copy-paste-and-email error messages when you don't have the network going yet, but maybe you could take a picture and upload it somewhere, or at least write down one or two lines of the error and send it to the list? You're absolutely right. So here's a detailed account of what I've done, following what was exposed (in French) here: http://doc.ubuntu-fr.org/ndiswrapper (Yeah, it's for Ubuntu, but that seemed good to me anyway.) 1. I've copied the WinXP driver files (it was recommended to use those, even if they're 32bits and I have 64bits) into /home/wifi, created just for that. 2. Then, into that directory, I've done ndiswrapper -i net8192cu.inf 3. I've checked with ndiswrapper -l, which returned: net8192cu: driver installed. (There were other failed drivers from previous attempts; I removed them.) 4. I've done ndiswrapper -m, which returned: WARNING: All config files need .conf: /etc/modprobe.d/ndiswrapper, it will be ignored in a future release. module configuration already contains alias directive The existing alias directive must come from a previous manipulation. 5. Then modprobe ndiswrapper returned: WARNING: All config files need .conf: /etc/modprobe.d/ndiswrapper, it will be ignored in a future release. FATAL: Module ndiswrapper not found. 6. I went to see that /etc/modprobe.d directory, and I saw several whatever.conf files and one extension-less ndiswrapper (don't know where it comes from, probably previous manipulations again). I thought I could solve that (how naive), and copied ndiswrapper into ndiswrapper.conf (by the way, the contents of this file is a simple line: alias wlan0 ndiswrapper). 7. modprobe ndiswrapper returned the same two messages, so I deleted the ndiswrapper file, and now it only returns the second one (FATAL). 8. That's where I stand now (except ndiswrapper -m doesn't return the warning now that ndiswrapper is deleted). I don't know if that's important, but installation of ndiswrapper was done (if I remember correctly) with dpkg, not synaptic, since I couldn't use that offline. I hope that'll help you help me, Paul -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ece7103.5040...@free.fr
Re: Make WiFi work.
Selon Paul Isambert zappathus...@free.fr: Le 24/11/2011 12:05, Selim T. Erdogan a écrit : Paul Isambert, 24.11.2011: Le 24/11/2011 10:08, richard.b...@blueyonder.co.uk a écrit : What about ndiswrapper ? A promising lead. So I've tried that; ndiswrapper works, but then modprobe doesn't recognize it (it says something about .conf files, too). Perhaps I've done something wrong earlier (I've done so many things). I realize it's difficult to copy-paste-and-email error messages when you don't have the network going yet, but maybe you could take a picture and upload it somewhere, or at least write down one or two lines of the error and send it to the list? You're absolutely right. So here's a detailed account of what I've done, following what was exposed (in French) here: snip Ah, nevermind! I've followed Nicolas's solution, upgrading to wheezy, which supports the drivers, and now it works. This is written from Debian! Thanks to all, Paul -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1322156130.4ece8062ba...@imp.free.fr
Re: Make WiFi work.
Le 23/11/2011 09:18, Joel Roth a écrit : On Wed, Nov 23, 2011 at 08:06:32AM +0100, Paul Isambert wrote: Le 22/11/2011 20:52, Joel Roth a écrit : On Tue, Nov 22, 2011 at 03:29:44PM +0100, Paul Isambert wrote: Hello, I've just installed Debian next to Windows 7, with the first DVD (i.e. debian-6.0.3-amd64-DVD-1.iso). It was not without trouble, but now it works. The problem is the wifi. My card (Realtek RTL8191SE Wireless LAN 802.11n PCI-E NIC, says Windows) is apparently not recognized. I've tried various solutions explained here and there, I have installed firmware-realtek and ndiswrapper and wpa_supplicant and I don't know what, nothing worked. Hi Paul, Fellow RTL8191SE sufferer here (in a ThinkPad T410.) In my case, lspci says: 03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8191SEvB Wireless LAN Controller (rev 10) The ndiswrapper approach never worked for me. I compiled kernel 2.6.36 with the driver source I downloaded from Realtek. http://www.realtek.com/downloads/downloadsView.aspx?Langid=1PNid=48PFid=48Level=5Conn=4DownTypeID=3GetDown=falseDownloads=true#RTL8191SE-VA2 I'd already tried to compile those... but compilation failed. Are you telling me I should compile the kernel itself with them? I.e. download Debian's sources, add those drivers somewhere (where?), and recompile everything? Not telling you to. But that's how I managed to get it to work. It took me months, of intermittent random walking down paths to various possible solutions. It is stupid, since you should only need the kernel headers to compile a module. I would like to do it that way, and move the module into the /lib/modules/kernel_version hierarchy, but I never did figure out how to get the driver indexed so that modprobe would find it. I was hoping someone would also comment on how to activate Realtek drivers in the kernel staging directory. Then there's manual kernel compilation (which I've generally been able to make work) and then there is the Debian Way, which creates a kernel package. I've tried to compile the drivers (once I understood I needed linux-headers for whatever reason, compilation went well). Strangely, you indicated firmware that is available with another version of the driver on the Realtek site. Anyway modprobe found nothing (I think it does find other things I have installed earlier, though). Alternatively, you can buy a cheap USB wireless device that *is* supported, till you can get the Realtek stuff sorted out. I think I'll do just that. I'm getting pretty weary of it all, but I'd hate to give up for something so stupid. Thanks to all, Paul -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4eccce99.7030...@free.fr
Make WiFi work.
Hello, I've just installed Debian next to Windows 7, with the first DVD (i.e. debian-6.0.3-amd64-DVD-1.iso). It was not without trouble, but now it works. The problem is the wifi. My card (Realtek RTL8191SE Wireless LAN 802.11n PCI-E NIC, says Windows) is apparently not recognized. I've tried various solutions explained here and there, I have installed firmware-realtek and ndiswrapper and wpa_supplicant and I don't know what, nothing worked. The hard part is that I have to switch to Windows to get an internet connection, gather info and material, restart with Debian, try, fail, switch to Windows again, an so on and so forth. Plus those stuff I'm instructed to do, modprobe, iwconfig, you name it ... are ancient Greek to me, so I apply them blindly, and perhaps what I've done before has gotten in the way, etc. So I'm a bit tired, but I really would like to switch to Debian -- and have an internet connection to find online documentation and start learning how to use it. So: is there a simple solution to make the card mentionned above work? By simple, I mean that if something must be done, it should be explained thoroughly (and not alluded to with check X with Y); I'm a complete newbie, so assume absolutely no prior knowledge. Best, Paul -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ecbb1d8.3010...@free.fr
Re: Make WiFi work.
Thank you Hugo for the answer. Le 22/11/2011 16:34, Hugo Vanwoerkom a écrit : Paul Isambert wrote: Hello, I've just installed Debian next to Windows 7, with the first DVD (i.e. debian-6.0.3-amd64-DVD-1.iso). It was not without trouble, but now it works. The problem is the wifi. My card (Realtek RTL8191SE Wireless LAN 802.11n PCI-E NIC, says Windows) is apparently not recognized. I've tried various solutions explained here and there, I have installed firmware-realtek and ndiswrapper and wpa_supplicant and I don't know what, nothing worked. snip I guess if you see this you solved your problem or you are on window$. I'm on Windows. Did you look at: http://wiki.debian.org/rtl819x That describes how to set it up. I've already tried that. It doesn't work, or I didn't do it properly; I remember the first line (deb etc.) was a bit problematic. Thanks, Paul
Re: Re : Make WiFi work.
Le 22/11/2011 16:35, Nicolas Bercher a écrit : hI, Your card seems to be a pci-e one. According to this page http://wiki.debian.org/rtl819x#Drivers I think you should upgrade your linux kernel to some version 3.0.0 since support for your wireless card has started with kernel 3.0.0~rc1-1~experimental.1. Ouch. That means uninstalling/reinstalling Debian, since I can't update via the network (or I'll really have to buy ethernet cord). Perhaps another solution will be proposed? If it comes to reinstalling, then I'll do so, but I'd prefer not to. Thanks, Paul -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ecbc366.4050...@free.fr
Re: Re : Re : Make WiFi work.
Le 22/11/2011 18:09, Nicolas Bercher a écrit : De : Hugo Vanwoerkomhvw59...@care2.com It seems you're rong since this driver is not reported to be supported in squeeze (requires linux 3.0, etc.). Wiki's explaination are valid only for wheezy. Hence, a squeeze user must use testing and unstable repositories to get fresher packages, this procedure is not described on the wiki. Ah, you are running squeeze. But I see no reason that the wiki procedure can't be followed for squeeze: 1. Install firmware-realtek, unzip and wireless-tools for squeeze 2. wget ftp://ftp.dlink.com/Wireless/dwa130_revC/Drivers/dwa130_revC_drivers_linux_006.zip 3. unzip dwa130_revC_drivers_linux_006.zip 4. su mkdir -p /usr/local/lib/firmware/RTL8192U cp rtl8192u_linux_2.6.0006.1031.2008/firmware/RTL8192U/* /usr/local/lib/firmware/RTL8192U That copies the firmware. Then a reboot should load r8192e_pci, or modprobe it. No dependency in wheezy. Sorry, my explaination where funded on the assumption that, as far as I experienced, it is not possible to successfully load a module into the kernel (without triggering a magic number mismatch) when it was compiled from a different source tree, that is surely the case. So I might missed something recently...? Note that package firmware-realtek (with support for RTL8191SE, v0.31) is available from squeeze-backports too, so Paul could use aptitude to get it, this seems more clean and sustainable. The problem is that it doesn't work anyway (or I can't make it work)... I'll try apt-offline, which at least will perhaps allow me to solve other problems. Thanks to all, Paul
Re: Make WiFi work.
Le 22/11/2011 20:52, Joel Roth a écrit : On Tue, Nov 22, 2011 at 03:29:44PM +0100, Paul Isambert wrote: Hello, I've just installed Debian next to Windows 7, with the first DVD (i.e. debian-6.0.3-amd64-DVD-1.iso). It was not without trouble, but now it works. The problem is the wifi. My card (Realtek RTL8191SE Wireless LAN 802.11n PCI-E NIC, says Windows) is apparently not recognized. I've tried various solutions explained here and there, I have installed firmware-realtek and ndiswrapper and wpa_supplicant and I don't know what, nothing worked. Hi Paul, Fellow RTL8191SE sufferer here (in a ThinkPad T410.) In my case, lspci says: 03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8191SEvB Wireless LAN Controller (rev 10) The ndiswrapper approach never worked for me. I compiled kernel 2.6.36 with the driver source I downloaded from Realtek. http://www.realtek.com/downloads/downloadsView.aspx?Langid=1PNid=48PFid=48Level=5Conn=4DownTypeID=3GetDown=falseDownloads=true#RTL8191SE-VA2 I'd already tried to compile those... but compilation failed. Are you telling me I should compile the kernel itself with them? I.e. download Debian's sources, add those drivers somewhere (where?), and recompile everything? (Actually, the driver sources are also in the staging directory of the Debian 2.6.36 kernel sources. Maybe I did something stupid, but being in staging seemed to interfere with the driver loading in the compiled kernel. Is it enough just to move it elsewhere in the tree?) You also need to install the firmware. I have these files: /lib/firmware/RTL8192SE /lib/firmware/RTL8192SE/Realtek-Firmware-License.txt /lib/firmware/RTL8192SE/rtl8192sfw.bin /lib/firmware/RTL8192SE/rtl8192sfw492.bin /lib/firmware/RTL8192SE/rtl8192sfw74.bin /lib/firmware/rtl8192sfw.bin Now you're ready for: modprobe r8192se_pci In my case, I can see the driver has loaded successfully because the wireless indicator LED on the laptop turns on. Note that mine is already on, and does turn on and off with the associated button. I'll try the rest when at least I get the first steps right. Thank you very much for you solution, I hope it will work... Paul -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ecc9b78.7070...@free.fr
