Downloaded and ran Live CD just fine..........went to install and same old problem with ATI cards........have to edit settings to VESA after install. ATI's X8XX and X1XXX cards have been out for quite some time now.........
You should post a bug report. The sooner you post, the sooner they'll fix it before Edgey hits.
https://launchpad.net/distros/ubuntu
https://launchpad.net/distros/ubuntu
Already did for Breezy and the response was that ATI isn't supporting/supplying drivers for Linux support.......which I agree with but the still should be some way to default drivers to VESA on detection of non-supported card rather than having to edit the settings manually......
Don't forget to enable all of the Dapper repositories. 
I had a few of them but apparently not all of them. I did an apt-get update and apt-get dist-upgrade. It started then deleted a bunch of stuff and just finished. About 5 minutes total. Nothing worked. I rebooted and it booted to the command line. I manually went in and edited /etc/apt/sources.list to include these (found via Google):
deb http://us.archive.ubuntu.com/ubuntu dapper main restricted
deb****** http://us.archive.ubuntu.com/ubuntu dapper main restricted
deb http://us.archive.ubuntu.com/ubuntu dapper-updates main restricted
deb****** http://us.archive.ubuntu.com/ubuntu dapper-updates main restricted
deb http://us.archive.ubuntu.com/ubuntu dapper universe
deb****** http://us.archive.ubuntu.com/ubuntu dapper universe
deb http://us.archive.ubuntu.com/ubuntu dapper-backports main restricted universe multiverse
deb****** http://us.archive.ubuntu.com/ubuntu dapper-backports main restricted universe multiverse
deb http://security.ubuntu.com/ubuntu dapper-security main restricted
deb****** http://security.ubuntu.com/ubuntu dapper-security main restricted
deb http://security.ubuntu.com/ubuntu dapper-security universe
deb****** http://security.ubuntu.com/ubuntu dapper-security universe
deb http://archive.ubuntu.com/ubuntu dapper multiverse
deb****** http://archive.ubuntu.com/ubuntu dapper multiverse
deb http://archive.ubuntu.com/ubuntu dapper-backports main restricted universe multiverse
I then disabled all of the Breezy repos and added the ones above and did another apt-get update and apt-get dist-upgrade. It's running now and appearst to be working. Downloading a lot anyway. Fingers crossed...
I had a few of them but apparently not all of them. I did an apt-get update and apt-get dist-upgrade. It started then deleted a bunch of stuff and just finished. About 5 minutes total. Nothing worked. I rebooted and it booted to the command line. I manually went in and edited /etc/apt/sources.list to include these (found via Google):
deb http://us.archive.ubuntu.com/ubuntu dapper main restricted
deb****** http://us.archive.ubuntu.com/ubuntu dapper main restricted
deb http://us.archive.ubuntu.com/ubuntu dapper-updates main restricted
deb****** http://us.archive.ubuntu.com/ubuntu dapper-updates main restricted
deb http://us.archive.ubuntu.com/ubuntu dapper universe
deb****** http://us.archive.ubuntu.com/ubuntu dapper universe
deb http://us.archive.ubuntu.com/ubuntu dapper-backports main restricted universe multiverse
deb****** http://us.archive.ubuntu.com/ubuntu dapper-backports main restricted universe multiverse
deb http://security.ubuntu.com/ubuntu dapper-security main restricted
deb****** http://security.ubuntu.com/ubuntu dapper-security main restricted
deb http://security.ubuntu.com/ubuntu dapper-security universe
deb****** http://security.ubuntu.com/ubuntu dapper-security universe
deb http://archive.ubuntu.com/ubuntu dapper multiverse
deb****** http://archive.ubuntu.com/ubuntu dapper multiverse
deb http://archive.ubuntu.com/ubuntu dapper-backports main restricted universe multiverse
I then disabled all of the Breezy repos and added the ones above and did another apt-get update and apt-get dist-upgrade. It's running now and appearst to be working. Downloading a lot anyway. Fingers crossed...
Weird, did they say they wouldn't make the xserver choose vesa in absence of a driver that supports a certain graphics card? I agree with what you said, it should do that. That's how Suse handled my graphics card in 10.0. In fact, I consider it a bug if it tries to use the radeon driver for a non-supported graphics card.
No......I just assumed it would be addressed in the next build. I mean like I said.......I agree ATI does a shabby job of supporting Linux, but, like you state, Suse and others at least give you basic graphics to enter...........with Ubuntu I have to go in and edit just to enter and I'm hearing people with X1900 cards are just SOL according to several threads on Ubuntu forums.......
Have you tried installing without an overclocked system? Sometimes that just might be it....
Btw, I've noticed some weird bugs that haven't been fixed for a long time. SCIM + Acrobat Reader still don't love eachother (I need the Adobe version so I can output to gtklp, which I'm unsure of how to do using evince) and this is a problem that has existed since Breezy came out.
Also for some reason Firefox is crashing like crazy...thank god for crash recovery
Btw, I've noticed some weird bugs that haven't been fixed for a long time. SCIM + Acrobat Reader still don't love eachother (I need the Adobe version so I can output to gtklp, which I'm unsure of how to do using evince) and this is a problem that has existed since Breezy came out.
Also for some reason Firefox is crashing like crazy...thank god for crash recovery
Have you tried installing without an overclocked system? Sometimes that just might be it....
Btw, I've noticed some weird bugs that haven't been fixed for a long time. SCIM + Acrobat Reader still don't love eachother (I need the Adobe version so I can output to gtklp, which I'm unsure of how to do using evince) and this is a problem that has existed since Breezy came out.
Also for some reason Firefox is crazy crashing
EDIT:
lol it did it again! Thank god for crash recovery! I don't know what I'd do without this...either way its annoying. I'll hopefullyl search later to see if I'm having an isolated issue or everyone else started to get these crazy crashes
Btw, I've noticed some weird bugs that haven't been fixed for a long time. SCIM + Acrobat Reader still don't love eachother (I need the Adobe version so I can output to gtklp, which I'm unsure of how to do using evince) and this is a problem that has existed since Breezy came out.
Also for some reason Firefox is crazy crashing
EDIT:
lol it did it again! Thank god for crash recovery! I don't know what I'd do without this...either way its annoying. I'll hopefullyl search later to see if I'm having an isolated issue or everyone else started to get these crazy crashes
I did mine through the 'apt-get dist-upgrade' method. When prompted to keep my current settings or let it update I let it update everything. When it restarted I get this:
"Error 18: Selected cylinder exceeds maximum supported by BIOS"
Now, I've done some research on this error and most people say to make sure LBA is enabled in the BIOS. I've searched *everywhere* in my IBM Thinkpad T42 BIOS and it's simply not an available option. I updated to the most recent BIOS as well and that didn't help.
Windows boots fine and if I try to boot the previous kernel it will boot but not load the GUI. I'm wondering if I should try another 'apt-get dist-upgrade' from my previous kernel?
Help?!
"Error 18: Selected cylinder exceeds maximum supported by BIOS"
Now, I've done some research on this error and most people say to make sure LBA is enabled in the BIOS. I've searched *everywhere* in my IBM Thinkpad T42 BIOS and it's simply not an available option. I updated to the most recent BIOS as well and that didn't help.
Windows boots fine and if I try to boot the previous kernel it will boot but not load the GUI. I'm wondering if I should try another 'apt-get dist-upgrade' from my previous kernel?
Help?!
MBrown
Diamond Member
- Jul 5, 2001
- 5,726
- 35
- 91
Yeah my rig is actually running at stock at the moment. Its the summer time and it runs hotter than usual. I need to update the sig. I don't know what it is. Originally I thought it was my motherboard. So I bought a new motherboard and it still woudnt work. I am starting to think the problem is my harddrive. And I was also never able to install XP with SP1.
Well, this didn't go well for me. I attempted to reinstall GRUB to the MBR and now my system doesn't boot. I'm going to do a fixmbr from the Recovery Console.
Looks like it's back to Windows for me now... :-/
Okay, I've got Windows back booting with the Windows boot loader. Does anyone know how I can boot my Ubuntu install with it? I tried using a method I found in a Google search but it didn't work.
It involved doing a 'dd if=/dev/hda2 of=ubuntu.bin bs=512 count=1' to create the file then put that file on the root of 'C' on my Windows drive and point to it in the boot.ini. When I view the file created in Ubuntu (doing a 'more ubuntu.bin') and Windows (notepad) it's empty. I want my Ubuntu back. Any ideas?
I never had to edit the windows boot.ini, I've always installed grub to the master boot record. If searching google for an article that deals with this didn't help, then I can't help you here. Maybe you should grab a different livecd and just install a boot loader with it. My brother had some sort of error with the desktop installer when he tried installing grub so he just used the old text based installer and it worked for him.
Oh btw, the place where I set my hard drive access mode was where I could see my ide devices (primary master device, secondary master device, primary slave device, seconadary slave device). I just hit enter on my hard drive and changed the access mode. But that was with my old motherboard and plus your's is probably much different. What bios/chipset do you have?
Oh btw, the place where I set my hard drive access mode was where I could see my ide devices (primary master device, secondary master device, primary slave device, seconadary slave device). I just hit enter on my hard drive and changed the access mode. But that was with my old motherboard and plus your's is probably much different. What bios/chipset do you have?
I didn't have to do anything on my original Ubuntu 5.10 install either. I installed Windows, then installed Ubuntu 5.10. I put GRUB into the MBR and everything worked fine. I could boot WinXP and Ubuntu including previous kernels. This problem started when I did an 'apt-get dist-upgrade'. After that I got the Error 18. When I tried to setup GRUB again and put it in the MBR on rebooting I got a flashing cursor in the upper left. That's when I did a 'fixmbr' from the Recovery Console of WinXP. Now I can boot WinXP but can't figure out how to get Ubuntu back.
Hmmm... Installation completed but what a mess. Booting takes forever (sits on Preparing restricted drivers). It's a much longer bootup than Breezy and at least 3x what XP Pro takes to hit the desktop. When I (finally) hit the desktop my display is dim and I have to bump up the brightness. Also, I get an error saying, "The application 'gnome-settings-daemon' has quit unexpectedly", and I assume that's why I'm getting the following errors... Alt-tab doesn't work. Key repeat doesn't work. Attempt to launch 'Preferences | Keyboard' to check the settings and it bails with an error. I had used Automatix for my Breezy install so I figured I'll do it for Dapper and see if that fixes the errors I'm getting. Nope. Still screwed up. Breezy was a quick and trouble-free install. Maybe it's because I'm doing an upgrade with an existing home directory but right now I'd have to say that Dapper is pretty much suck.
I'm backing up my bookmarks, pics, Evolution mail, and Gaim message history now. It's been like 15+ minutes to make a < 1GB .rar file archive of my .evolution directory. No status to indicate how far along it is and no file on the desktop where it's being created. That's odd. I'm guessing I could do that archive in a minute or two in XP w/ WinRAR. Why so much longer in Ubuntu? :-/
I'm going to wipe and reload. The question is, do I give Ubuntu another chance or just stick with tried and true WinXP (it's been 100% stable for me).
I'm backing up my bookmarks, pics, Evolution mail, and Gaim message history now. It's been like 15+ minutes to make a < 1GB .rar file archive of my .evolution directory. No status to indicate how far along it is and no file on the desktop where it's being created. That's odd. I'm guessing I could do that archive in a minute or two in XP w/ WinRAR. Why so much longer in Ubuntu? :-/
I'm going to wipe and reload. The question is, do I give Ubuntu another chance or just stick with tried and true WinXP (it's been 100% stable for me).
Nothinman
Elite Member
- Sep 14, 2001
- 30,672
- 0
- 0
RAR has always seemed to run about the same speed for me, but I haven't done any real benchmarking since I don't use RAR much any more. And if the file being created isn't on the desktop it's either not being created in your desktop directory or you somehow broke Nautilus as well.
I don't know the cause of your problems, but I highly doubt your existing home directory is it. I've been running sid for years and have been through countless Gnome upgrades with the same home directory without any major issues.
Sounds to me like the BIOS on your laptop just simply sucks and you've been lucky not to have gotten burned by it in the past. For some reason it's very common for PC manufacturers to cripple laptop bioses and take options and such out of it. Probably because there is bugs with sleep or something like that and so they simply remove functionality, at least that's my guess why the do it.
Probably what happenned is that before when you installed kernels and initrd and the grub stuff all that ended up in BIOS accessable territory on your partition. When you did you upgrade it reinstalled a bunch of stuff, the file system choose to put it farther back on your harddrive and now it's at a point were your bios can't reach it anymore hence the error.
That's my guess.
To solve this from happenning again you should make a seperate /boot partition nearer the beginning of your harddrive. That way you won't run into any bios limitations.
For evolution I don't bother backing it up. I open it up, select all my emails and do a 'save as'. That's what I back up and the nice thing about that is that it's easily importable into other email applications... such as thunderbird when you get tired up putting up with evolution's crappiness. (if you want to do that check out galternatives (it's a debian-ism, I expect it to be present in ubuntu, but I am not sure) program for selecting system-wide defaults on things like default browsers and email clients)
For GNOME if you want to check to make sure your preferences are not screwing things up you can do 1 of 2 things...
1. create a new user and try that out.
2. log out of gnome and log into the console. Make sure that all your gnome applications and daemons are gone so that they don't try to write new preferences files when they shut down..
ps aux|grep gnome
killall whatever
(or kill "pidnumber")
Next make a backup directory for your preferences and move everything to that.
mkdir ~/backup.preferences
mv ~/.??* ~/backup.preferences
The ~/.??* will select every file and directory beginning with a . and including at least 2 characters, which will basicly be all your preferences. This is to avoid the . and .. special files.
Probably want to copy back some of the .bash* files or whatnot.
now go and log back in to Gnome and see if it fixes it. Later on you can then go and move things back. Also look for the bookmarks* files in Firefox/Epiphany/whatever for that sort of thing. Keep in mind that the gnome settings daemon will write out it's configuration when it shuts down, so that if your delete all the gnome configuratin stuff then log out some will be recreated or overwritten.
Also less invasive method is to choose 'failsafe' gnome in the session properties when you log in, which is sort of like a safe mode.
Probably what happenned is that before when you installed kernels and initrd and the grub stuff all that ended up in BIOS accessable territory on your partition. When you did you upgrade it reinstalled a bunch of stuff, the file system choose to put it farther back on your harddrive and now it's at a point were your bios can't reach it anymore hence the error.
That's my guess.
To solve this from happenning again you should make a seperate /boot partition nearer the beginning of your harddrive. That way you won't run into any bios limitations.
For evolution I don't bother backing it up. I open it up, select all my emails and do a 'save as'. That's what I back up and the nice thing about that is that it's easily importable into other email applications... such as thunderbird when you get tired up putting up with evolution's crappiness. (if you want to do that check out galternatives (it's a debian-ism, I expect it to be present in ubuntu, but I am not sure) program for selecting system-wide defaults on things like default browsers and email clients)
For GNOME if you want to check to make sure your preferences are not screwing things up you can do 1 of 2 things...
1. create a new user and try that out.
2. log out of gnome and log into the console. Make sure that all your gnome applications and daemons are gone so that they don't try to write new preferences files when they shut down..
ps aux|grep gnome
killall whatever
(or kill "pidnumber")
Next make a backup directory for your preferences and move everything to that.
mkdir ~/backup.preferences
mv ~/.??* ~/backup.preferences
The ~/.??* will select every file and directory beginning with a . and including at least 2 characters, which will basicly be all your preferences. This is to avoid the . and .. special files.
Probably want to copy back some of the .bash* files or whatnot.
now go and log back in to Gnome and see if it fixes it. Later on you can then go and move things back. Also look for the bookmarks* files in Firefox/Epiphany/whatever for that sort of thing. Keep in mind that the gnome settings daemon will write out it's configuration when it shuts down, so that if your delete all the gnome configuratin stuff then log out some will be recreated or overwritten.
Also less invasive method is to choose 'failsafe' gnome in the session properties when you log in, which is sort of like a safe mode.
Megatomic
Lifer
- Nov 9, 2000
- 20,127
- 6
- 81
So I've went and reinstalled Kubuntu 6.06 LTS and I'm VERY happy with myself right now. I got my 3D card working and I can access my Netgear SC101 NAS. I remembered to try a samba share with the drive shared on my wife's laptop. That works beautifully, though my download speed from the NAS is limited by my wife's wireless card. Once I get my music and mail and pics and other stuff I will rarely need to access the NAS so that won't be a burden often.
Next up: get my music and video playback configured.
Next up: get my music and video playback configured.
I reloaded Ubuntu 6.06 from scratch. I was running into installer crashes and had problems repartitioning the drive. I managed to get it installed but it took a few times. However, I believe I found the source of my slow HD performance issue. My Hitachi Deskstar 7200RPM drive had a bad sector. I was trying to copy my mail back to my system and kept getting timeouts and the drive was making unusual 'bzzz bzzz click' noises (yikes!). The good news is I was able to use a disk duplicator to clone the drive and now everything is back to normal. All is good now and I take back all the negative comments I said toward you Dapper!
Had a few quirks when trying to update from 5.10 to 6.06. After a few minutes of screwing around, I got the update to work. So far so good, I've been able to do exactly what I want with it, I've got my codecs, wine, music players, video players, firefox 1.5.0.4, etc. Only problem I'm having is getting flash 8.
I've successfully moved my /home/andy (user) directory to a separate 180GB reiserfs mount. It's been working great so far. Here's my mount system:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda2 45896256 37548700 8347556 82% /
varrun 1030612 176 1030436 1% /var/run
varlock 1030612 4 1030608 1% /var/lock
udev 1030612 184 1030428 1% /dev
devshm 1030612 0 1030612 0% /dev/shm
/dev/sda1 188284040 2889784 185394256 2% /home/andy
/dev/sda5 5116668 4893388 223280 96% /media/sda5
/dev/sdb1 145404224 140640384 4763840 97% /media/sdb1
/dev/sdb2 47458504 36681656 10776848 78% /home/andy/storage
/dev/sdb4 43359860 37029888 6329972 86% /home/andy/storage2
/dev/hdc 716350 716350 0 100% /media/cdrom0
----------------- Migrating your /home/user dir to a bigger partition (post-installation)
Note: I have not followed the below exactly step-by-step, but I have done steps very similar to this to get mine working. Thus, please make sure you know what you're doing before you attempt this and that you have backed up all critical data. As long as you don't mistakenly format a Windows partition and if you have only system files (no critical documents) on your Linux partition so far, you should have nothing to worry about. I still recommend you backup in case you or the partition editor makes an error.
Before starting, YOU MUST have an empty/unallocated/blank partition unless you have a partition full of data you don't care about! Type gksudo gparted in the console to start the partition editor. Format the new partition (you will lose all data previously there) as ext2, ext3, or reiserfs (reiserfs is my favorite). Write down the new partition's device (e.g. /dev/sdb2). Exit gparted.
With the Ubuntu user administration tools create another user like "admin2", give him an administrator template and a password you'll remember. Then, logout of GNOME. Get to a console by pressing Ctrl+Alt+F1. Login as admin2. Then type sudo mv /home/user /home/user.old, replacing "user" as necessary.
Now we are going to add the new partition to your file system table. First recreate the directory. Type sudo mkdir /home/user Use a terminal text editor (as root under sudo) to add the following line to /etc/fstab (of course, replace /dev/sdb2 with the appropriate device). Do not replace the last "user" with your user name. "user" is an option given to the file system. Do change the "user" in italics to your user name. For my example I'm using /dev/sdb2 as the device.
/dev/sdb2 /home/user auto user 0 1
Space out the line as you wish to match the others, and save to /etc/fstab. Exit the text editor.
Proceed to mount your partition. Type sudo mount /home/user Hopefully everything went fine (it will print absolutely nothing in the case of no errors). If it errored out, make sure that partition is formatted as either ext2, ext3, or reiserfs.
It's time to copy your old data over. Remember that first command you used to move your original user directory to user.old? We are going to use that user.old directory now.
Type sudo cp -a /home/user.old/* /home/user/
This may take awhile as all of your data is being copied over. Now set ownership of everything in there to you: sudo chown -R user /home/user/ (do NOT do this to anything more than your home directory).
When the commands finish, you should just reboot by pressing Ctrl+Alt+Del or if you know how, it's fine to login as the user now under GNOME.
Once you're confident everything is working correctly, delete the /home/user.old directory which is still sucking up space on your root / partition.
(If you have problems you can also login as admin2 to GNOME.)
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda2 45896256 37548700 8347556 82% /
varrun 1030612 176 1030436 1% /var/run
varlock 1030612 4 1030608 1% /var/lock
udev 1030612 184 1030428 1% /dev
devshm 1030612 0 1030612 0% /dev/shm
/dev/sda1 188284040 2889784 185394256 2% /home/andy
/dev/sda5 5116668 4893388 223280 96% /media/sda5
/dev/sdb1 145404224 140640384 4763840 97% /media/sdb1
/dev/sdb2 47458504 36681656 10776848 78% /home/andy/storage
/dev/sdb4 43359860 37029888 6329972 86% /home/andy/storage2
/dev/hdc 716350 716350 0 100% /media/cdrom0
----------------- Migrating your /home/user dir to a bigger partition (post-installation)
Note: I have not followed the below exactly step-by-step, but I have done steps very similar to this to get mine working. Thus, please make sure you know what you're doing before you attempt this and that you have backed up all critical data. As long as you don't mistakenly format a Windows partition and if you have only system files (no critical documents) on your Linux partition so far, you should have nothing to worry about. I still recommend you backup in case you or the partition editor makes an error.
Before starting, YOU MUST have an empty/unallocated/blank partition unless you have a partition full of data you don't care about! Type gksudo gparted in the console to start the partition editor. Format the new partition (you will lose all data previously there) as ext2, ext3, or reiserfs (reiserfs is my favorite). Write down the new partition's device (e.g. /dev/sdb2). Exit gparted.
With the Ubuntu user administration tools create another user like "admin2", give him an administrator template and a password you'll remember. Then, logout of GNOME. Get to a console by pressing Ctrl+Alt+F1. Login as admin2. Then type sudo mv /home/user /home/user.old, replacing "user" as necessary.
Now we are going to add the new partition to your file system table. First recreate the directory. Type sudo mkdir /home/user Use a terminal text editor (as root under sudo) to add the following line to /etc/fstab (of course, replace /dev/sdb2 with the appropriate device). Do not replace the last "user" with your user name. "user" is an option given to the file system. Do change the "user" in italics to your user name. For my example I'm using /dev/sdb2 as the device.
/dev/sdb2 /home/user auto user 0 1
Space out the line as you wish to match the others, and save to /etc/fstab. Exit the text editor.
Proceed to mount your partition. Type sudo mount /home/user Hopefully everything went fine (it will print absolutely nothing in the case of no errors). If it errored out, make sure that partition is formatted as either ext2, ext3, or reiserfs.
It's time to copy your old data over. Remember that first command you used to move your original user directory to user.old? We are going to use that user.old directory now.
Type sudo cp -a /home/user.old/* /home/user/
This may take awhile as all of your data is being copied over. Now set ownership of everything in there to you: sudo chown -R user /home/user/ (do NOT do this to anything more than your home directory).
When the commands finish, you should just reboot by pressing Ctrl+Alt+Del or if you know how, it's fine to login as the user now under GNOME.
Once you're confident everything is working correctly, delete the /home/user.old directory which is still sucking up space on your root / partition.
(If you have problems you can also login as admin2 to GNOME.)
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes + WCL Discussion Threads
- Started by Tigerick
- Replies: 23K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
-
Facebook
Twitter