I recently got a new hard drive for my notebook, and was playing a little with it taking advantage of the fact that my working system is intact on my old drive. So, I installed Slackware 13.0, and ran slackpkg to get -current. Everything runs fine, except for my wireless network.
With slack13 I was using the broadcom-sta driver (wl module) and it was working perfectly. In -current I can build the wl module, and load it, but it will do nothing. The interface (eth1 in 13.0) is not created, the card is not registered, and actually nothing is logged to /var/log/messages by the wl module itself. When I load it I only get a few lines from a module it loads (ieee something, for wireless cryptography I think), but the WiFi LED is off, and it does not reacts to the keyboard (Fn-F2 is supposed to switch the wifi off and on). Basically it seems like it is actually doing *nothing*, or that maybe there is something I need to do to activate it.
The other option is b43 with b43-fwcutter. I tried it, it worked for a few minutes before dying on me saying that it can't use DMA with my device, and that I need to reconfigure the kernel to use PIO instead. And it also behaved in a weird way. The interface was not created immediately (wlan0) and I had to play with the iwconfig command to bring it up (although I don't actually remember what exactly I did to do it). Also it looks like it takes a few minutes to load the firmware, is not immediate. The third thing i got was rfkill messages in the output of dmesg, reacting to my keyboard (logging stuff like "the radio thinghy is ENABLED or DISABLED) when I tried to bring wifi up, but without actually switching the LED on.
I don't really know what is wrong. I am thinking on building my own kernel with the option b43 suggests, but before I'd like to know why wl is failing. I could very well go back to Slack13, but staying with an old kernel version due to silly hardware issues does not seems like the right choice.
I think I must say as well that the wifi is working flawless with Windows Vista and Slackware 13.
It's only been a couple of days since I formatted my toshiba laptop's hard drive (i was running fedora without significant problems) and installed slackware 13.1 32bit. I did a network install because the dvd drive is not functioning properly. everything installed fine with the hugesmp kernel, but I started not being able to boot the laptop every single time I wanted to (especially after a reboot but also after a power up).
my observations:
-the pc might freeze in the very first toshiba logo screen (where you are prompted to press F2 to enter BIOS)
-or it might freeze when I get the lilo boot loader (not even the count down to choose kernel starts) - but i CAN use the arrows and press 'enter' to choose to load a kernel manually
-or just after it loads the kernel and the bios checks
-or during boot after in loads ACPI thermal zone
-or a little later during boot when the dhcpcd if broadcasting for a dhcp lease.
the first 3 are freezes, the last 2 are resets. especially if i need to reboot (or get the resets of the 2 last case), I will surely get stack in one of the first 3 cases afterwards! i have observed that rarely, after such a reset, if it actually gets stack in the toshiba logo, i might be able - pressing the poiwer buttonj repeatedly to actually overcome the 'freezing' there at which time i'll get to the lilo loader (the count down timer will not.. count down), but i can press 'enter' and I will finally get stack after loading the kernel and bios checks
So I have to powerdown the laptop and start all over again. Sometimes the whole boot process will proceed smoothly. and i'll get to a login prompt, and when I do I can keep the laptop up and running for virtually ever. that is it doesn't seem to be slackware related... Hwever the problems started after I installed slackware. I didn't have any problem with the fedora installation and i wonder if it has something to do with the network boot.... additional note, with feodra i didn't have a problem restarting or shutting down the laptop. now if i restart, the pc will go through the process of shutting down, but it will never actually reboot - i'll have to do it manually..
I want to move to Slack, so I took a look around the web to see if it can give support to my wireless card but couldn't find any relevant info.Is it supported? Can be installed?
I see the device in dmesg. On the macbook pro 6,1 it gets issued IRQ 19 and loads sata_sil24 and ata_piix correctly, however on the 5,1 and 5,2 macbook pro it only loads sata_sil24 and gets IRQ 24. Is there anyway to specify the IRQ assigned to the device via the kernel (is it an IRQ conflict or device not working on IRQ24)? MacBook Pro uses an EFI so not traditional bios where I can set irqs. Am I looking in the right direction as to the cause of my problem? Slackware 13.1 with standard linux kernel 2.6.35.8
I have a problem with the built-in wireless-card of my laptop. I can connect to the wireless DSL-router using wicd (wicd-1.7.0-486-2 from /extra), wicd reports that it connects and obtains an IP-address. It then changes the status to connected. Immediately after that (may be a second later) the status changes back to disconnected and I can't reach the network.
Here some specs: Kernel: self-compiled 2.6.37-6-generic, the only option I changed from the standard generic config was to enable PAE, but I also tried it with the standard generic kernel and the huge kernel. Wireless card: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01) Firmware installed with the packages from Slackbuilds.org: network/b43-fwcutter network/b43-firmware. The wireless card is working correctly under Debian, so I think this is not a hardware issue.
I'm running slackware 12.2 and I have yet to get the b44 kernel driver working with 2.6.27.31 (custom build, b44 compiled in). Does it require a firmware cutter (ex. b43-fwcutter)? Does it work in later kernel versions out-of-the-box?
On a second note, if it is better supported in later kernels, would it be problematic to upgrade kernels (for instance, anything other than just building the new kernel via instructions in the Slackbook)?
I have searched many times but just have come across "it should work" which it doesn't, at least here...
A little background first: Wireless card: Broadcom BCM4312 Wireless driver used: [URL].... (and slackbuild variation of the same) GFX card: nVidia geForce 7150m I installed Slackware yesterday, along side my Ubuntu (yes yes, I use Ubuntu lol. I've been using it for about four years, I added Slackware to grub.cfg, using the OS prober, which added four menu entries. The first two caused kernel panic, the third worked, and I don't think I tried the fourth. (I'm pretty sure they were, in this order: generic, generic-smp, huge, and huge-smp). Using huge, I could not modprobe my wireless driver, I would get a "Invalid Module Format" error with wl, and when installing the nVidia drivers (from their site), I would get:
[code]....
I then booted using a menuentry my friend gave me, created my initrd, and everything worked fine, both graphics and wireless (mostly fine). So I upgraded to -current, kernel 2.6.35.10, and I started getting the same errors as before, 'Invalid Module format' and the same thing with the nVidia drivers, although this time, it happens regardless of if I use the generic kernel, or the huge kernel. I've done heaps of Google'ing around, and nothing I found worked.
When Ubuntu 10.10 loads I get the above pop-up after logging in.Does anyone know how I would go about finding out what this refers to, or how I could address it?
Sometimes it doesn't load all of a webpage. In Firefox this results in only some of the page being displayed. In konqueror I get the "Connection to host www.page.invalid is broken" error message. The computer was doing this when running Opensuse 11.3 and continues to do it when running a clean install of Opensuse 11.4. I haven't tried a live CD of Ubuntu or something but that might be worth a go.
I just installed a fresh version of fedora 11, and it went extremely smooth, except for one thing; I opened up firefox and it was at the fedora start page with a google search, i typed text into the search box, hit enter, and got a infamous "This page cannot be displayed" error.I have checked my connection, turned off the firewall, and rebooted the system. The problem still persists. I have no idea what is going on, it says i'm connected, I can do a software update which has to go through the internet connection, but for some reason, firefox doesn't want me to go anywhere besides fedoraproject.org.
I was installing fedora 13 just for fun and it move grub boot to different partition. Now I can't boot anything but fedora I know I need to be booting from hd0 sa1 but grub loads from hd0 sa7 .I just need my ubuntu os back .
I've been using Ubuntu for more than a year (just basic simple stuff like surfing the net or the occasional document) and in the last months I've been running into the following problem.I've been updating regularly to the latest Kernels the last one should be 2.6.32-25. However at start up Grub loads only 2.6.31-19 and below and there's no mentioning of 2.6.32 in grub.cfg while it is present in menu.lst. I tried to update grub with no success.
just 3 or 4 weeks with it and i like it very much. But I have a problem Some days ago, I just partitioned my HDD, installed Windows on it (for playing videogames) and ubuntu later. The problem is that ubuntu loads automatically, i cant go windows because ubuntu starts always, what can i do?
I can launch applications via SSH on a remote wins box. the pid shows up with @:>tasklist. However, for some reason I can not access the app via its web interface after its launched. Also, the process is not showing up in the desktop gui. its like its there but not at the same time...kinda like democracy in the US...Really though, could use some help. do i need to open applications with a " run as" or something like that. I already have the user account szet on the machine.
I used yum 5 days ago when I installed mplayer and some dependencies. And now I manage to use Yum and it is not working, I cant find out what is happening but yum loads the plugins and then freezes and is no reaction to ctrl-c or something to stop it so I am have to kill it dna finally got no result from any update processes. Also I manage to clean cache or even to run yum. I checked the logs and it writes nothing about this ,neither an error or something to make me understand whats happening. Tried to install with rpm but the same thing happens. It just freezes...
I have an odd issue -- fairly fresh Debian Testing install, using Lightdm.
After booting up, Lightdm starts, and then a moment or two later restarts. As a result, any keystrokes captured by the first run (e.g. the first few characters of my username) are lost. My lightdm log is:
Code: Select all[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log [+0.00s] DEBUG: Starting Light Display Manager 1.16.7, UID=0 PID=827 [+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf [+0.00s] DEBUG: [SeatDefaults] is now called [Seat:*], please update this configuration
[Code] ....
This log shows me seeing the login screen, waiting for it to restart, and then logging in correctly on the first attempt.
I just upgraded my fedora 13 to fedora 14. I changed the cpu and the motherboard so i had to install from scratch...but I saved my iptables. The problem is that I do all the suff service iptables save And apparently it works... But everytime I reboot I have to re run the script to forward Internet...Everything else works just fine...I mean I can ssh, vnc, etc but wont forward intel :S dont know why?
I'm using KDE Version 4.4.00 on OS11.2 all my browsers (konqueror, firefox, chrome) webpages loads painfully slowly on vista same connection, same machine is loading is faster. I did not notice this in OS11.1 on same machine.I tried disable IPv6 in boot and in firefox but it did not improve situation significantly. I still get long looking up of dns time after time.Am I "paranoid" or is there some way I can address this this slow loading issue?
Anyway, I installed Ubuntu normally. Whenever I try to run Firefox for the first time, it loads for a bit, then it crashes. Every time. I tried reinstalling it, and the isntallation was fine. I managed to connect properly. But it won't run.
What I have noticed on several versions of Ubuntu, both 32 and 64 bit (including 9.10, 10.04 b2 and UNR 9.10) is that after the launch of Firefox (including the current 3.6.3 version), I continue to get a spinning cursor for more than 10 seconds after the FF window is present and ready to accept input. Sometimes I get it only when moving the cursor outside the FF window and other times it will be in the window, too. I have even noticed it persist for a short time after quitting FF. I think it's definitely related to FF because I don't see this occur unless FF is launched, not even when another browser (Chromium in this case) is launched. To add to the mystery, I see it in Ubuntu and Mint 8 xfce, but not in Ubuntu-based distros with simpler window managers like Mint 8 fluxbox or CrunchBang 9.04 (openbox). To try to get rid of this, I have tried various FF configuration speedups available from the Net - changes implemented through about:config. These do speed up FF, but they don't get rid of the spinning wheel.As far as I can tell, the spinning wheel has no impact on FF operation - it doesn't stop me from entering a url and accessing it, though perhaps it slows down implementation.
When I load Ubuntu, it goes to the desktop screen, shows my desktop picture, loads Pidgin which I have set to start on startup, loads Icons, and then the screen goes black. The mouse cursor shows up, I can move it around, and then it goes black again, and the mouse cursor shows up again. This repeats a few times until the cursor freezes. This started happening after I tried fixing a bug with new drivers for my Intel 845gl video card. The instructions I followed are these:
Code: To use the available fix, run the following commands: pt-add-repository ppa:glasen/855gm-fix apt-add-repository ppa:brian-rogers/graphics-fixes apt-add-repository ppa:glasen/intel-driver aptitude update aptitude install linux 855gm-fix-dkms aptitude dist-upgrade ,taken from here.
I have tried some of the options in recovery mode from GRUB menu, none really work, except booting with default graphic configuration, or something similar like this.
So I have used ubuntu for about 2 years now, and this has never been an issue. Basically my trackpad(touchpad) on my laptop stops working when the wallpaper and other gui aspects load. The mouse works in windows and works in ubuntu for a few seconds while the screen is still black and gui is loading. So I know ubuntu does know it exists.
This problem occured after watching a movie and ubuntu froze up. Also while watching the movie I had the trackpad disabled, which might have something to do with my problem. (I have a hpdv6500 which has a button on the trackpad to disable it. I did no software tricks or hacks to do it). After resetting my computer the problem existed and persists every time I turn it on and off. So does anyone have any experience with such a problem or maybe how to reset the settings of the mouse?
The screen will show a blinking cursor for a few seconds. The keyboard works and a signal is found for the speakers. Then the 'Ubuntu' loading screen will show but at this point the screen would freeze and the keyboard will cease to function. At this point I have to reboot from the on/off switch. It can take several attempts before the desktop will load, or if I'm lucky, it'll load up first time. I've had this problem since 9.10. I'm not quite sure why it's taken me this long to attempt to sort it out.
Whenever I power on my Xubuntu machine, GRUB does not load until I reboot. Once the system is running, I can reboot back into Xubuntu but if I power down GRUB does not seem to load. I've got the system to power on at 8am every morning but the fact that I have to reboot it is really annoying me.
Update: Reinstalled GRUB to the master boot record of my first hard disk and it solved everything. I had to follow the second part of this guide to get it to work: http://ubuntuforums.org/showthread.php?t=224351
