Networking :: NIC Detects When Booting Live But Not After Install?
Jan 19, 2009
I am using a laptop with a realtek8139 integrated adapter. When I boot the live cd (Puppy), I go to configure the internet connection, and shows the module for the card has automatically loaded, and I just set it to DHCP and that is all. After installing the os, however, I go to configure the connection, and it tells me that no module has been loaded, so I should manually choose from the list. When I do, it tells me that it failed to load. I have also tried allowing it to probe by loading every possible driver, to no avail. I have reinstalled the os twice, and it does not recognize the adapter, but when I boot live, it works fine. Any reason why it would do this?
ok so the router works in windows and i know the config details of it.i can see other wifi access points in the area but not my one. i have tried joining it as a "hidden network" to no avail.is there any reason why fedora would not detect my own wifi when it detects substantially weaker signals instead??
Yesterday I did follow exactly the description how to build a live system on a USB Stick with the additional second partition for the data of Live_USB_stick. So far I had success, as my Netbook did start booting and loaded the OpenSUSE 11.2. Then I rebooted the Netbook and it never again comes up with the 11.2. It looks as if it would stop somewhere at starting the graphical system, but I'm not sure.
Today, second try, I created the USB stick with the 11.2 Live System only (no second partition). My Netbook starts booting and shows the 11.2 system successfully, also further boots are the same successful. Then having created the Live system with the second partition again, results in a un-bootable Netbook again (not even the first time it comes up).
What I wonder when I did check the USB partitions: the one (sdg1) with the Live-CD can be mounted and the content is readable. The second one (sdg2) cannot be mounted; shouldn't it be mountable and shouldn't it be formated with a file system? Did anyone have some experience on this? Or, at least, the people having a running persistent live system, what does the partition them show up?
I've currently have opensuse 11.3 installed on my system and I would like to do a new fresh install of opensuse 11.4. I therefore downloaded the DVD 11.4 x64 install. However, when booting the kernel from the DVD (that leads to the installation procedure) I obtain the following error message "unable to handle kernel paging request". The system then stops and I need to perform a hard reset to restart again. The same happens if I try do boot from the live gnome CD. Thus, I'm unable to install opensuse 11.4 at all due to this problem. A possible solution would be to perform a hot update (i.e. changing repositories in my 11.3 and perform a zypper refresh and zypper dup). But I'm a bit scared of doing this since this will install the problematic kernel. how to circumvent this problem ? Is there any updated version of the live CD? I've been able to install opensuse 11.4 x64 without problems at home. Now I'm trying to install it at work. The current kernel (at work) is:
I am in a situation to boot fedora 15 live cd in to command line mode, not graphical mode, for some testing purpose. how to change argument during booting mode
I post here wanting to know if it's Possible to run wvdial as soon as linux detects USB modem.I have already installed and done the setting for using wvdial. I can successfully use wvdial command to setup internet connection.But I have only 1 USB modem. When my wife wants to use it for her PC, she disconnects it from my linux machine.What I want to do now is... 1 that when I attatch the USB back to my linux, I'd want it to do "wvdial &" automatically.2 that when linux is rebooted, "wvdial &" done automatically as soon as it detects USB modem.
My wireless card in my Acer Aspire 7551G shows wireless networks in range but wont connect to any of them. I am running an Atheros AR928x Wireless network card (windows reports it as a AR5b93). Also as a side note, whenever i turn on my computer, my wireless is disabled. However not connecting is my primary problem.
sud rfkill list
Code:
sojurner@Sojurner-Laptop:~$ sudo rfkill list 0: acer-wireless: Wireless LAN Soft blocked: yes Hard blocked: no
I'm developing an application to monitorize the network interfaces plugged in my PC. I know that wireless interfaces are listed in /proc/net/dev, but I don't know how to identify a cellular NIC.Is there any virtual file in /proc that shows the cellular NICs in the system? Could I identify different cellular NICs looking at /dev/tty?
Working on a quad boot system. Two Karmic installs (I find I tend to hork one every once in a while by playing too much, so having a backup around is nice), windows 7, and Snow Leopard. I got everything up and running, except I had Leopard installed instead of snow leopard. At that time, I had the following:
Grub2 detected everything just fine, made a real nice grub.cfg file and away I went.Now, I've made a change. Snow Leopard required GUID partitions and I had my stuff all set up as MBR and was /not/ about to reformat and start over. So I added a second drive, sdb.
Now, I can boot to that drive independently. Fine.I can boot to sda just fine and go to either Ubuntu install or windows just fine. Great. Grub2 finds Mac OSX on /dev/sdb2. Awesome (sdb1 is a fat32 bootloader for hackintosh reasons). It not only doesn't update grub.cfg, it leaves the old /dev/sda2 listing for my old Leopard install ... whose partition I deleted. It isn't visible anymore.
Code:
> sudo update-grub Generating grub.cfg ... Found Debian background: radar.png
[code]....
But nothing after Ubuntu 9.10 on /dev/sda6 shows up in grub.cfg? I'm at a loss. Any ideas how to get it to populate? I'd rather not hack grub.cfg and have to rebuild it by hand every once in a while especially as grub was fine with finding it.
Basically, I just installed Fedora in my desktop (use it on my laptop), and have a big problem, which is that Fedora (13), detects my wireless card (Edimax nMAX EW-7728IN), but when I try to connect to my wireless networks (WEP & WPA) it hangs and asks again for the password. I know the problem isn't from my routers,since I'm right now connected via Fedora 13 in my laptop.
I've installed F13 on two Dell E6400 laptops, both with Broadcom BCM4312 wireless cards. After updating them both, I enabled the RPMFusion repos and installed the akmod-ed wireless driver on each (following these instructions: [URL] Wireless works perfectly on one laptop, but doesn't seem to be working on the other. The wl module is activated (shows up in lsmod) and the wireless card is enabled (wlan0 shows up in ifconfig), but Network Manager isn't showing any available networks. For the record, wireless works on both laptops with Ubuntu 9.10 I am going to try cloning the entire drive on the working laptop and sticking it on the dud one.
I'm wondering here with my 64-bit 9.10 why my wireless does not seem to work with my Zonet wireless USB adapter. The adapter is working and it detects my network (a WPA) and attempts to connect, and after about 20 seconds or so, I am disconnected.
so my wireless isn't working. My netbook wireless detects the available networks but when I try to connect it doesn't. The box that asks me to put in the password occasionally shows up but it still doesn't load. I even tried re-installing Ubuntu and didn't fix anything.I'm using kernel version 2.6.35-22-generic and
I have 6GB of RAM and I'm planning to install Fedora 14 32-bit to achieve a higher degree of compatibility. Does fedora automatically download and install a PAE enabled kernel when it detects more than 4GB of RAM (Just like Ubuntu)?
I do not have any shares setup on my home network so this has never been a big deal to me. My mother finally took enough interest in my operating system to allow me to dual boot 3 of her computers. Everything was up and running like a charm and then she asked "What about connecting to the file server?"
I click on "network" under nautilus and start clicking around - no where in here is the file server that every Windows system on the network can see (5 or so other systems with xp/vista/7 on them - so I know the share works). A small bit of time and some command life foo later I had hunted down and manually mounted the share and added and fstab entry for the drive so my mother would never have to go through that on her own.
That being said - did I do things the hardway here? Can someone please tell me there is an easy method that successfully detects and connects to samba shares without having to resort to CLI? Personally I do not mind doing this, but it is an issue when I am installing Linux for a beginner.
I'm running Ubuntu 10.04 server 64bit. I'm trying to get my ASUS PCE-N13 wireless PCI card working for searching and connecting to wireless networks. But I have no networks applet appearing in the panel. system->preferences->sessions has the Network Manager enabled The Notification Area is added to the panel. system->preferences-Network Connections-->Wireless[tab] shows a pink box, with no available connections.
I'm using the Ultimate Boot CD, and I've added a bunch of customized .iso's to it. I can boot into those .iso files fine, but most of them are mini-versions of Linux that are designed to run off of a CD. When they try to boot, they try to run off the CD (which obviously isn't there since they're on a USB drive) and then either freeze, or don't work in some other way.
Is there any way to edit the .iso files to tell them they're booting off of a USB drive? I'm assuming there'd be something somewhere in the boot configuration files to do this. Where would that be? I would think it'd be different for different ones, but are there some places that are standard for live CDs? What would I have to change? EDIT: Just to make exactly what I'm asking clear...I know there's stuff all over the place on how to boot a .iso from USB. That's not the problem, I can already do that. What I'm wondering is how to make the OS stored in the .iso realize that it's booting from USB and not CD?
I am on my new HP envy 14, and I have both a USB drive and a Live CD with the latest version of 64 bit ubuntu.
When I run the Live CD, it takes me to a purple screen with a keyboard and person symbol at the bottom, and after a minute it opens up a black window that looks like a command prompt, and then the screen goes black.
When I try to run the USB, either selecting the "install" option or the "run from USB option", it goes through the boot processes like everything is working, and then the screen goes black.
The same thing happened on my main computer with a 32 bit live CD.
This is my first attempt at using Fedora (the only other distro i've used is Ubuntu), and I'm having trouble booting from a USB device created using the LiveUSB Creator utility, containing the Fedora-14-i686-Live-Desktop disc image. After selecting my USB device from the startup menu, I see a black screen with the following information:
Code:
With a blinking cursor. I cannot enter any input, but my keyboard has lights on as normal, so I assume it's working.
The following is a list of my hardware:
Processor: Intel Core2 Duo E6750 Motherboard: MSI nForce 650i P6N SLI-FI Graphics: nVidia GeForce GT 240 HDD: Western Digital Raptor 150 GB USB: Memorex Mini TravelDrive 2GB
I am trying to create a dual-boot system, and currently have Windows 7 Ultimate 32-bit installed.
my system crashed and so i tried booting from a live usb pen drive. but i get the following error messages (see picture). does this mean that my hard drive is curruped? what can i do? i alreadys tried booting from different live medias, but i cant get anything to run (gparted and system recovery live).
I am not too new to the Linux scene, I mainly use CentOS on a day to day basis on my server, however, I would like to start using Ubuntu on a full time basis, I am sick of how slow Win7 can be and all of the bulk. Sooo, I downloading ubuntu, burned it, verified it, y'know, the usual.Backed up everything I needed and restarted pc. The purple splash screen came up and started to load. After about 3 minutes I see a very distorted version of my Win7 desktop! I am then unable to Ctrl+Alt+F1 as my keyboard becomes unresponsive. I have disabled my graphics card (Nvidia 240 GT (I think)) and just used the on board Intel chipset but still this happens. What is going on? I am desperate to use it and I am finding this really frustrating.Also I did manage to ctrl alt f1 at one point and I tried to restart gdm but it errored out on me
Well, I noticed this by accident while trying to use dash for the rc.d scripts. I messed up and forgot to link it to /bin, and as such, the system failed to boot properly and would not respond. I rebooted (forcefully), but this messed up the filesystem. I booted the sw64 install DVD and tried to mount it, and it would not mount.
I tried to run fsck on it, but it said that fsck.jfs in NOT available. Eventually I booted my old slamd64 12.1 DVD and it had fsck.jfs. Any reason why this rather useful program was removed ? Or is it a bug, or is my DVD messed up? I guess I should just keep around another live CD, I do keep knoppix, but it boots so slow and I don't understand it at all, it's so hard to do anything with it.
i have laptop Toshiba Satellite A500 with Intel i5 processor and Intel Graphics Media Accelerator HD , i am having this problem when booting from any live CD or USB when i choose "run from USB or Live CD " or even "install Ubuntu..." i got large list of error lines (as i think) and after that , no response until i manually switch laptop off. attached two photos and a small video that i could took as it is very quick .
While trying to boot ubuntu, I noticed that it was taking a long time. A lot longer than usual, in fact.I then forced a restart on my computer, and noticed that Grub looked different - the resolution was weird.I then tried again to boot ubuntu, and got the following messages:vga=792 is deprecated. Use set gfxpayload=1024x768x24,1024x768 before linux command.mount: mounting /proc/ on /root/proc failed: Input/Output error.And then the computer seems to stay idle forever.Recovery mode is also not useful: I can only see some periodic messages about a failed command: READ FPDMA QUEUED.
However, I also noticed that grub showed something before it allowed me to choose which OS I would like to boot (Im running a dualboot configuration with Ubuntu 10.10 and Windows 7).I managed to get it:error: hd0, msdos6 out of diskerror: no suitable mode foundConsidering that I have no trouble booting into Win 7, and that I can actually access my Ext4 partition from there, Im trying to reinstall Grub from a Live CD.Heres the output of fdisk -l :ubuntu@ubuntu:~$ sudo fdisk -l
Disk /dev/sda: 250.1 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
I am getting a flicker when FC10 Live boots and then it just freezes. I am guessing that the video driver which is loaded when X starts is not the right one I have an nVidia GForce 7025.
I am trying to install Ubuntu 9.04 (Jaunty) on my home PC. I am using the same DVD that i used on my work PC, thus the DVD is not defective. My home PC has the following specs:
I'm trying to get back into Linux after a few years off.
I have tried booting from a Live CD using Flash Linux and Damn Small Linux.
Flash Linux reports unable to mount CDROM and then provides a command line - I assume I have the kernel, a shell and little else at this point? Can I mount the CD and continue?
DSL seems to do something similar but freezes with a blank screen. I have the option of entering parameters prior to booting with DSL (but not with Flash) I have tried the parameter which copies the CD to RAM and then boots without success.
I plan on installing Debian to my HD in the near future but felt like playing around with Live CDs prior to this in order to get reacquainted.
I have googled this issue and it seems there are other noobs out there with the same model of PC (HP DV6) who are having similar problems but I could not find a solution.
As an aside - this is the kind of issue that IMO, still prevents Linux from becoming a mainstream OS.