Not necessary anymore, you can have a single partition linux.(not including swap partition)

I believe grub isn't installed or not properly installed.
Since you have a livecd, I would suggest you follow this instruction:

1. Boot using livecd.
2. mount your installed linux partition
3. chroot to that partition
4. run : grub-install /dev/hda

Example:
Your linux partition = /dev/hda1

# mount -rw /dev/hda1 /mnt/hda1
# chroot /mnt/hda1
# mount -t proc /proc proc
# check or edit if necessary /boot/grub/menu.lst
# grub-install /dev/hda
# umount /proc
# exit

then reboot.

Please refer to my previous post:
http://forum.lowyat.net/index.php?showtopic=334125

The first thing you need to do on any Debian/Ubuntu is to :
sudo apt-get update

so that the packages database will be updated and Ubuntu knows where to find it.

I missed the proxy part.

Since you are using proxy, wget (which used by apt) and any other means to connect ot outside world need to go through proxy.

What you can do is set wget to use proxy by editing /home/your-username/.bashrc and add these lines (I'm not sure if it will work) :



You can add other transfer protocol which use bash/cli mode.

Than you can try download things using wget.
Example:
wget http://packages.freecontrib.org/ubuntu/plf...-1plf4_i386.deb

If you can download, then you are ready to apt-get.
I you can't, maybe you need to adjust something on the proxy url. Try consult with your U on how to set manually the proxy.

Update after doing some surfing on your U site:



This post has been edited by oshiri: Oct 24 2006, 10:25 AM

Check your bios if you are using usb keyboard; and enable USB legacy support.
Sometimes when you enable both keyboard and mouse usb legacy support, it will conflict.
Try play a bit with it.

babymilo
Paste your /etc/network/interfaces please.......

Yes.
So many networkcard? Please check using ifconfig or lspci and iwconfig.

Try use static ip rather than dhcp.
If you use dhcp, DNS will be forwarded by your router to your pc. That is why your nameserver in /etc/resolv.conf always changes.
You can use dhcp if you set DNS in your router similar to your ISP.
ex: streamyx
202.188.0.133
202.188.1.5

In order to use static ip, edit /etc/network/interfaces something like this.
ex:
Your router ip is = 192.168.1.1 (this is your gateway)
and the networkcard connected to that router is = eth0




Save and restart networking: # /etc/init.d/networking restart

This post has been edited by oshiri: Nov 28 2006, 06:48 PM

The easiest way to uncompress file is by using unp.

unp xxx.tar
unp xxx.bz
unp xxx.zip

almost every compression format supported (depends on compression library installed)

From my experience, it'd due to heavy use of flash ads on lowyat (not blaming lowyat ) + some sort of kernel bug.
Read my post : http://mambang.org/modules/news/article.php?storyid=133

First of all, kernel 2.6.20 suppose to have zydas driver builtin into kernel.
Please check with this command:


Newer version of kernel does not include config.h anymore.
What you can do is, remove any statement with: #include <linux/config.h> in your source code.
But that's not practical

What I did was, create a fake/empty file by that name in my kernel headers.





Instead of using user, try change it to users. Something like this:



Good luck

This post has been edited by oshiri: Aug 27 2007, 09:32 AM

my guess is you are having bad blocks on ntfs partition.
You can use badblocks to check that particular partition.
Or you can try use ntfsfix to try fix it.

**Backup first**

Sorry, I'm using pure Debian. But you can try search apt for kernel image that support bigmem.
Try:
$ apt-cache search linux-image |grep bigmem
linux-headers-2.6.18-5-686-bigmem - Header files for Linux 2.6.18 on PPro/Celeron/PII/PIII/P4
linux-image-2.6.18-5-686-bigmem - Linux 2.6.18 image on PPro/Celeron/PII/PIII/P4
linux-headers-2.6.18-4-686-bigmem - Header files for Linux 2.6.18 on PPro/Celeron/PII/PIII/P4
linux-image-2.6.18-4-686-bigmem - Linux 2.6.18 image on PPro/Celeron/PII/PIII/P4
linux-headers-2.6.23-1-686-bigmem - Header files for Linux 2.6.23 on PPro/Celeron/PII/PIII/P4
linux-image-2.6-686-bigmem - Linux 2.6 image on PPro/Celeron/PII/PIII/P4
linux-image-2.6.23-1-686-bigmem - Linux 2.6.23 image on PPro/Celeron/PII/PIII/P4
linux-image-686-bigmem - Linux image on PPro/Celeron/PII/PIII/P4


If you can't find any bigmem kernel image support from apt, then you need to compile your own kernel.
This is the place you should configure:

This post has been edited by oshiri: Jan 7 2008, 11:16 AM


Attached thumbnail(s)

dpkg --purge resolvconf
edit /etc/resolv.conf again.

If that doesn't work...try purge avahi especially avahi-dnsconfd

This post has been edited by oshiri: Aug 19 2008, 08:54 PM

Are you using network-manager?
If that the case, it is similar to resolvconf which detect dhcp broadcast and replace nameserver automatically.
Some routers does not send dns ip properly or even don't have place to set those ip. That's the origin of the problem.
You could try let your dhcpclient takeover the dns ip from your router.
Edit your dhcp client. Not sure which version you are using. if dhcp3-client, then edit /etc/dhcp3/dhclient.conf anda prepend tmnet dns ip:


My advise is...remove all those automatic tools, do the old fashion, set everything manually.
Only 2 file necessary if you do it manually:
/etc/resolv.conf and /etc/network/interfaces

I'm not so sure what you mean.
Are you having problem or cannot authenticate to your wpa/wep router?

Read my note on how to use wpa supplicant or wlassistant:
http://mambang.org.my/modules/news/article...78&keywords=wpa
http://mambang.org.my/modules/news/article...77&keywords=wpa

Get latest kernel if available because kernel 2.6.26 has more support for wireless devices.
Or you could try my kernel:
http://mambang.org.my/modules/news/article.php?storyid=205

1. Have you install firmware for your wifi card?
For broadcom, you need fw_cutter.

2. Happen to me once. I mess up with kernel. Try use different kernel.




Don't know about "it just work". I never use Ubuntu because their versioning system really confusing. I can't figure out which is stable, which is unstable, experimental...so on. Looks like they "cocktail" everything up. Still stick to "pure" Debian for ages. I prefer doing things manually.
About your key problem...you could try disable acpi but at the cost of having power mangement and others depends on acpi to not working.



This is probably acpi problem. Try get newer kernel. Dont know what brand your notebook is.
Usually notebook has function (Fn) key to control various aspect of their system. Try use it.
Or you could try command line.
Check in this : cat /proc/acpi/video/lcd/brightness
*video could have different name
You could just change the brightness using command such as: echo 100 > /proc/acpi/video/lcd/brightness
Change the numerical value to your liking, 0 -100

This post has been edited by oshiri: Aug 20 2008, 09:10 AM

Try use Fn up or Fn down

For user using laptop, better install laptop-mode-tools.

Why primary DNS still using 10.0.0.1?
check /etc/resolv.conf again.
No matter you using wired or wireless.... both will refer to that file.

That does not help.
Try paste output of: iwconfig


Yes annoying.
That is why I only use kernel which I compiled myself.
Anyway... I don't use ubuntu.

This post has been edited by oshiri: Aug 20 2008, 08:35 PM

Similar but not the same.
Yes, Ubuntu at earlier stage follow Debian. The filesystem layout and packaging system.
But now I think Ubuntu has gone it's own path.
Like I said before, it does not follow Debian versioning system. It does not go through strict release system: experimental--> unstable-->testing---->stable. That is why Ubuntu can release new version every few months.
Is it really stable? Everytime people file bugs...they will repair it in new release. So which is stable release? Future release?
I'm not comdemning Ubuntu, just curious.


Nothing wrong with your iwconfig.
Your wireless connected to your router.
Are you sure you have check /etc/resolv.conf and tmnet dns is on the first line?

How about ping?
Does it reply from outside?

Something you could check, is the routing table.
Try this command:
ip route get 1.2.3.4

It should show it's trying to get the ip through your router. Something like this:

# ip route get 1.2.3.1
1.2.3.1 via 10.0.0.1 dev wlan0 src 10.0.0.3
cache mtu 1500 advmss 1460 hoplimit 64