Announcement

**Detonate** · Jun 28, 2010, 05:48 PM

Re: boot and networking issues

As this is a new install, something went wrong when installing grub. Since you are new to all of this, I would suggest a complete reinstall. This time when you get to the part about where to install grub, be sure you install it to the boot sector of the primary hard drive (you only have one). Once you have completed the install and rebooted without the cd, we can tackle the network issues. Also before beginning the install run the check cd option to make sure you have a good cd. While installing have your computer hooked to the network in wired mode if possible.

**oshunluvr** · Jun 29, 2010, 09:09 PM

Re: boot and networking issues

to put a finer point on it:

when asked where to install grub the answer should be (in your case)

/dev/sda

NOT

/dev/sda1 - or any other number.

You need a boot loader on the master boot record (MBR). linux and grub are flexible enough to be installed literally anywhere, but your computer needs a boot loader on the MBR.

Quick and simplified linux intro to hard drive devices and partition numbers:
Each piece of hardware has a device ID. For hard drives (of late) the old scsi interface is emulated (aka sata) so drives all start with "s" then "d" for device and a letter starting with "a" in order of detected by the OS. Soooo... first hard drive is known as s d a, the second is s d b, you get the idea. With one drive you have "device" "sda" aka /dev/sda. So your drive as a whole is referred to in this manner.

Each partition on the drive has a number. So the first is 1 and so on. SO the first partition on the first drive is /dev/sda1, first partition on the second drive is /dev/sdb1.

Therefore: MBR install of grub requires it be pointed at the drive - not a partition. /dev/sda being the obvious choice.

When/if you get into multiboot or multiboot-loaders you may want to install grub or lilo or others to a partition instead of a drive's MBR.

**PredictChaos** · Jun 30, 2010, 08:11 PM

Re: boot and networking issues

Thank you very much to both of you for the info.

I've performed the clean install again as before, and I'm now getting the OS to run without the CD. The networking issues persist, however, both wired and wireless. Again, it's seeing the wireless network, but will not connect.

**Detonate** · Jun 30, 2010, 08:48 PM

Re: boot and networking issues

Let's take them one at a time. We will start with the wired network, because that is more straight forward, and we will need some kind of connection already established to work on the wireless. I want you to read this post very carefully, and post back before you begin following the instructions found there if you have any questions.

http://kubuntuforums.net/forums/inde...opic=3100052.0

**PredictChaos** · Jul 13, 2010, 01:08 PM

Re: boot and networking issues

okay, turns out the wired connection issue was a problem with my router, which I've replaced and now that's working. Still struggling with the wireless connection...

**vinnywright** · Jul 13, 2010, 01:17 PM

Re: boot and networking issues

Originally posted by PredictChaos

okay, turns out the wired connection issue was a problem with my router, which I've replaced and now that's working. Still struggling with the wireless connection...

info on your wireless card will be neaded.......post the output of these hear.

Code:

ifconfig -a

and

Code:

iwconfig

and

Code:

lspci

for a start.

VINNY

**PredictChaos** · Jul 13, 2010, 01:33 PM

Re: boot and networking issues

david@Joshua:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:07:e9:b5:4f:18
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::207:e9ff:feb5:4f18/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:146471 errors:0 dropped:0 overruns:0 frame:0
TX packets:75767 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:219354113 (219.3 MB) TX bytes:5223383 (5.2 MB)

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:40 errors:0 dropped:0 overruns:0 frame:0
TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2000 (2.0 KB) TX bytes:2000 (2.0 KB)

wlan0 Link encap:Ethernet HWaddr 00:e0:98:ba:3e:52
UP BROADCAST 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 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

david@Joshua:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11b ESSID

ff/any
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry long limit:7 RTS thr

ff Fragment thr

ff
Power Management

ff

david@Joshua:~$ lspci
00:00.0 Host bridge: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface (rev 01)
00:01.0 PCI bridge: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE Host-to-AGP Bridge (rev 01)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 81)
00:1f.0 ISA bridge: Intel Corporation 82801DB/DBL (ICH4/ICH4-L) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801DB (ICH4) IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 01)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 MX 420] (rev a3)
02:00.0 PCI bridge: Hint Corp HB6 Universal PCI-PCI bridge (non-transparent mode) (rev 13)
02:01.0 Network controller: ADMtek ADM8211 802.11b Wireless Interface (rev 11)
02:08.0 Ethernet controller: Intel Corporation 82801DB PRO/100 VE (LOM) Ethernet Controller (rev 81)
02:0c.0 Communication controller: Conexant Systems, Inc. HSF 56k Data/Fax/Voice/Spkp Modem (rev 01)
03:00.0 FireWire (IEEE 1394): Texas Instruments TSB12LV26 IEEE-1394 Controller (Link)
03:08.0 Multimedia controller: C-Cube Microsystems E4? (rev b1)
david@Joshua:~$

**vinnywright** · Jul 13, 2010, 01:46 PM

Re: boot and networking issues

your wirless seams to be recognized and working (a relativ term)

wlan0 Link encap:Ethernet HWaddr 00:e0:98:ba:3e:52
UP BROADCAST 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 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

but not conected to eneything

david@Joshua:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11b ESSID

ff/any
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry long limit:7 RTS thr

ff Fragment thr

ff
Power Management

ff

how did you go about conecting it?
and are you using WEP/WPA incription?

the stock network manager gives some pepole problems with WEP/WPA and have beter luck with wicd.

VINNY

Announcement

boot and networking issues

boot and networking issues

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment