Learning to PORT
- Thread starter Invincible Madness
- Start date
That is a constant debate. It really is a matter of preference. I would suggest you start with GNOME, but try the KDE and the Xfce at some point. I use all three, each on a different machine, for various reasons. Which version of Mint are you going for?
XFCE if you want a minimalist interface that gets the job done. KDE if you like to have a pretty desktop that is still very functional. GNOME 3 if you want to change the way you think about the desktop xD. Personally, I like GNOME 3. It takes some getting used too but it's really not that bad. You should try out all 3 on some live CDs and then pick the one you like.
Thanks both you guys. I was off the system for a day, so replying late.
I installed Linux Mint 12, Gnome version. Been having little problem with wifi.
My adapter doesn't even turn on, it stays red no matter what. I learnt that it's a common problem with most Linux distros installed on HP laptops. Looks like it doesn;t use the proprietary driver and needs another one to be installed. Looking all over the place for it. Please do let me know if you know a solution to this.
wifi adapter details: Broadcom BCM4322AG 802. 11a/b/g/n wireless lan controller
RealTek Semiconductor RTL8102E/8103E Fast Ethernet NIC (this might just be for Ethernet but just in case if u need the details)
PS: I'm off to sleep after 38 hours, so might look here lil late but I will.
Broadcom cards are notoriously a nuisance. Try the repositories, using Synaptic or aptitude, to search for 'bcm43'. If the firmware is not installed, install it and reboot (unless you already know how to modprobe).
No idea what is and how to modprobe but going to try this now. Looking for some commands I need to run to install this.
The other thing you might try is using ndiswrapper with the windows driver. You can try downloading the driver from the manufacturer's website and looking up how to use ndiswrapper. I would do this as a last resort though as it is sure to cause you pain and suffering. I had to do it once when I was using Puppy Linux on an HP and making ndiswrapper work wasn't that hard, it was finding the right driver that drove me nuts.
epidenimus, 2 days back I had Mint installed but It wouldn't show up in the boot menu. System would directly boot to windows. I did some googling and found a command for updating grub. Did that (worst mistake).
Rebooted my system only to an error message saying MBR not found or something.
Got tired and installed windows 7 again. Now I have both the OS on DVDs. What do you think I should do.
I'm thinking to go with Ubuntu since I installed it once without any issues. Let me know.
another question: If I partitioned My harddisk into 2 drives. C for windows (160gb) and 60gb emply drive.
I want to install Linux (Ubuntu or Mint) on this 60gb drive. How do I do that. Prompts seem to be confusing when not doing the install in default fashion. Like selecting drive is a headache, can;t seem to find the right one.
It would be really great if you or others could guide me through installing Linux on this 60gb partition, Like an idiots guide.
General Instructions:
1. When installing a Linux system with a custom partition table you generally need to select the "Other Options" or advanced option.
2. The next thing you need to do is to create a root partition that is ext4 or some other file system of your choosing. Ext4 is the poplar stable choice right now and should be fine for your needs. You also need to tell gparted (that is the partitioning program you will be using) that this partition is your root partition when looking at all the options that you have.
3. Create a swap partition. This is basically used just like RAM except that it is significantly slower since you are writing the hard disk. It's really just for when you fill up your RAM and the system needs a place to write things to memory. If you've got 4 GB of RAM you probably won't need much swap. The default for most installations is 5 GB but that's really overkill. I usually just do 2 unless I am running a system with 512 MB of RAM, I might select more then. Good places for your swap partition are at the beginning and end of you disk, but it is not necessary to put it there. Those places are just the fastest for reading and writing from what I have read.
4. Once you have created your root partition and your swap partition out of the 60 GB you saved you should have 4 main partitions and you can continue with your install. If you somehow have more than 4 main partitions then something is wrong and I can't help you with that.
This is not the most flexible installation. You could create a logical partition and then cut that up into home partition, root, var and swap partitions, but that's for when you figure out more about partitioning your disk. This should be enough to get you started. Also, Google is your friend. That's where I learned everything I have just summarized for you so if you get stuck at a step, have another computer up so you can search the interwebs for help.
1. When installing a Linux system with a custom partition table you generally need to select the "Other Options" or advanced option.
2. The next thing you need to do is to create a root partition that is ext4 or some other file system of your choosing. Ext4 is the poplar stable choice right now and should be fine for your needs. You also need to tell gparted (that is the partitioning program you will be using) that this partition is your root partition when looking at all the options that you have.
3. Create a swap partition. This is basically used just like RAM except that it is significantly slower since you are writing the hard disk. It's really just for when you fill up your RAM and the system needs a place to write things to memory. If you've got 4 GB of RAM you probably won't need much swap. The default for most installations is 5 GB but that's really overkill. I usually just do 2 unless I am running a system with 512 MB of RAM, I might select more then. Good places for your swap partition are at the beginning and end of you disk, but it is not necessary to put it there. Those places are just the fastest for reading and writing from what I have read.
4. Once you have created your root partition and your swap partition out of the 60 GB you saved you should have 4 main partitions and you can continue with your install. If you somehow have more than 4 main partitions then something is wrong and I can't help you with that.
This is not the most flexible installation. You could create a logical partition and then cut that up into home partition, root, var and swap partitions, but that's for when you figure out more about partitioning your disk. This should be enough to get you started. Also, Google is your friend. That's where I learned everything I have just summarized for you so if you get stuck at a step, have another computer up so you can search the interwebs for help.
Hell, partition planning is a class or two in and of itself, which probably does not belong in this device's area. Getting it right is worth it though. Here are some basic ideas and recommendations:
1. Use gParted Live CD. Yes, I know that several distros come with the tool, but they are often either outdated or do not work as well as part of the installer. Use the Live CD and set it up first, then allow your installers to work with what you have allocated. This also allows for some more complex partition tables, which you may appreciate.
2. Windows is a selfish child that doesn't like to play nice. It needs to be your first partition on the table. It also only reads its own file systems by default (i.e. NTFS and FAT).
3. Your swap needs to be twice the amount of RAM you have (or will have) if you want the machine to be able to hibernate/suspend to disk.
4. Use GRUB as your primary bootloader. It's just a smarter creature. You can chain the Windows bootloader to it, if you want, but do not use the Windows bootloader as the primary and expect it to pick up on Linux.
5. Do the Windows install first on the partition that you created for it. Do the Linux and GRUB install second.
6. Windows partition needs to be NTFS; Linux partition should be EXT4. Having a shared /data partition is a good idea on a dual boot system -- EXT2/3 works well for this and there is a tool you can install on Windows to make it recognize it. (I'll try to dig it up.)
7. Using the Ubuntu "dual boot" menu option is a queerball way to do all of this that I do not recommend. It does expedite getting a trial install ready for use on the HDD, but it as it installs it within a Windows, partition is not sustainable for a serious set up. I'm not sure if Mint is incorporating this in its Ubuntu-based releases, but I hope not.
Finally, I do not expect anyone to be a Linux convert before even installing, but using Virtualbox on a Linux host OS for a Windows guest OS is perfect for most uses (Windows gaming excluded) and rather easy to set up. This is how my work box is configured, since I only really need Windows for 4-5 tasks. Used the unused Windows driver disk as an office frisbee.
1. Use gParted Live CD. Yes, I know that several distros come with the tool, but they are often either outdated or do not work as well as part of the installer. Use the Live CD and set it up first, then allow your installers to work with what you have allocated. This also allows for some more complex partition tables, which you may appreciate.
2. Windows is a selfish child that doesn't like to play nice. It needs to be your first partition on the table. It also only reads its own file systems by default (i.e. NTFS and FAT).
3. Your swap needs to be twice the amount of RAM you have (or will have) if you want the machine to be able to hibernate/suspend to disk.
4. Use GRUB as your primary bootloader. It's just a smarter creature. You can chain the Windows bootloader to it, if you want, but do not use the Windows bootloader as the primary and expect it to pick up on Linux.
5. Do the Windows install first on the partition that you created for it. Do the Linux and GRUB install second.
6. Windows partition needs to be NTFS; Linux partition should be EXT4. Having a shared /data partition is a good idea on a dual boot system -- EXT2/3 works well for this and there is a tool you can install on Windows to make it recognize it. (I'll try to dig it up.)
7. Using the Ubuntu "dual boot" menu option is a queerball way to do all of this that I do not recommend. It does expedite getting a trial install ready for use on the HDD, but it as it installs it within a Windows, partition is not sustainable for a serious set up. I'm not sure if Mint is incorporating this in its Ubuntu-based releases, but I hope not.
Finally, I do not expect anyone to be a Linux convert before even installing, but using Virtualbox on a Linux host OS for a Windows guest OS is perfect for most uses (Windows gaming excluded) and rather easy to set up. This is how my work box is configured, since I only really need Windows for 4-5 tasks. Used the unused Windows driver disk as an office frisbee.
Last edited:
I understand that I'll have to install Linux after windows 7. I'm clear until that.
How do I install GRUB, it it seperate from Linux installation itself. If I remember it right, thats what happened last time. Installed Windows first, Linux next and never saw Linux at the boot menu. So, I put in the Live CD to boot to Linux and installed Grub and it destroyed/messed my MBR. Had to do a complete install of windows again.
So, my question is, once I install Windows and Linux next - how to properly install GRUB and make sure I have both options at the boot menu?
GRUB is pretty good at picking up your installs. You just have to be sure to install it. As I recall, the installer asks you whether to install the bootloader...
It didn't for Mint obviously
Hope it will for Ubuntu Thanks much though. Do you have a GIT set up and building from source?
More questions to come.
Soooooooo.....completely off topic, but...when you're up and running, do you have plans to port a sense rom over? 
(completey unrelated to that butthole who got banned, ive always wanted sense
)
i wouldnt wanna bug drew and LeWa is awesome xD
(completey unrelated to that butthole who got banned, ive always wanted sense
)i wouldnt wanna bug drew and LeWa is awesome xD
Soooooooo.....completely off topic, but...when you're up and running, do you have plans to port a sense rom over?
(completey unrelated to that butthole who got banned, ive always wanted sense
i wouldnt wanna bug drew and LeWa is awesome xD
idk at this point. gannon started working on it already. if he wants me to port it to S, I'll be more than happy to
and yeah, my Linux is up and running
If looking for an option to port, the O1 has a codenameandroid rom up. Just a thought.
It is looking pretty sweet . . .
It is looking pretty sweet . . .
If looking for an option to port, the O1 has a codenameandroid rom up. Just a thought.
It is looking pretty sweet . . .
For sense? Could you post a link? I can't find it. I might wait for gannon to port it first. Since I just started learning this stuff and porting ROM from another device needs kernel to be changed which I guess hides in the boot.img. And I haven't yet learnt to extract and pack an .img file yet
I can give it a try though if you could post the link.If looking for an option to port, the O1 has a codenameandroid rom up. Just a thought.
It is looking pretty sweet . . .
ive ported it already
For sense? Could you post a link? I can't find it. I might wait for gannon to port it first. Since I just started learning this stuff and porting ROM from another device needs kernel to be changed which I guess hides in the boot.img. And I haven't yet learnt to extract and pack an .img file yet
I'll teach you once I get the time
Sent from my Amazon Kindle Fire using Tapatalk
For sense? Could you post a link? I can't find it. I might wait for gannon to port it first. Since I just started learning this stuff and porting ROM from another device needs kernel to be changed which I guess hides in the boot.img. And I haven't yet learnt to extract and pack an .img file yet
http://forum.xda-developers.com/showthread.php?p=23064084
Reading thru it, looks like they build from source and made similar changes that lupo made to get it working on the O1. I would imagine that compiling from source with drew/kravens mods for cm9 would be a place to start.
ive ported it already
I'll teach you once I get the time
Sent from my Amazon Kindle Fire using Tapatalk
Yay, 1 more new ROM
gannon, I'm totally loving this whole learning experience btw Similar threads
Trending Posts
-
Don't buy the snap ring!!- Started by 0078265317
- Replies: 7
-
5" affordable phone that doesnt crash fast processor 1.8ghz 3gb 32gb atleast GSM t-mobile netork 4g Volte
- Started by JustinRaney
- Replies: 5
-
Unable to Restore WhatsApp Messages from Local Backup (Crypt14 Files Present)
- Started by shayman
- Replies: 3
-
UI- 8 installed and battery is now back to lasting as when first purchased it.- Started by gtt1
- Replies: 4
-
Facebook
Twitter
Instagram