Kubuntu install problem

[skreid]

While trying to install Kubuntu (and Ubuntu), I encountered a problem. When it asks me where I want to install, it doesn't see my hard drive.

It's a 320gb sata western digital.

When I try to press next, it says something about not being on the root user (I'm running off the LiveCD).

Any suggestions?

 

[linux_0]

Please open a terminal and run the following:

[code:1:aa56b200bc]
lspci
dmesg |grep -i sd
dmesg |grep -i hd
[/code:1:aa56b200bc]

and post the output

Also please post your full hardware specs.

While trying to install Kubuntu (and Ubuntu), I encountered a problem. When it asks me where I want to install, it doesn't see my hard drive.

It's a 320gb sata western digital.

When I try to press next, it says something about not being on the root user (I'm running off the LiveCD).

Any suggestions?

 

[skreid]

I'll have to try again this weekend - I did some bad tinkering with partitions and screwed up my Windows partition (accidentally made it inactive, now I can't get it back to normal).

Once I fix everything I'll post my specs.

 

[bmouring]

You can use the Gparted LiveCD to fix the issue (you changed a partition flag to make it a hidden partition, select the offending partition, right-click, and goto "Manage Partition Flags", uncheck).

 

[skreid]

Well, see, the problem with that is the LiveCD's aren't seeing my hard drive...

Anyway, I installed Windows on the other partition, installed Partition Magic and fixed everything. I'll run that little query for you now, linux_0

 

[skreid]

Ok, so I got this:

Host Bridge: Ati Technologies Inc Rs480 Host Bridge (rev10)
PCI bridge: Ati Technologies Inc PCI Bridge
IDE Interface: Ati Technologies Inc unknown device 4380
USB controller: unknown device 4387
USB controller: unknown device 4388
USB controller: unknown device 438a
USB controller: unknown device 438b
USB controller: unknown device 4386
SMbus: Ati Technologies Inc unknown devices 4385 (rev 13)
IDE interface: Ati Technologies Inc unknown 438c
Audio device: Ati Technologies Inc unknown 4383
ISA bridge: Ati Technologies Inc unknown 438d
PCI bridge: Ati Technologies Inc unknown 4384
Host Bridge: AMD K8 [Athlon 64/Opteron) hypertransport technology configuration
Host Bridge: AMD K8 [Athlon 64/Opteron] address map
Host Bridge: AMD K8 [Athlon 64/Opteron] DRAM controller
Host Bridge: AMD K8 [Athlon 64/Opteron] Miscellaneous control
VGA Compatable controller: Ati Technologies Inc RS482 (Radeon xpress200)
Firewire [IEEE1394]: Via Tech, inc IEEE1394 host controller (rec c0)
Network Controller: RaLink RT 2561/RT61 802.11g pci
Ethernet Controller: RealTek semiconductor Co., LTD unknown device 8167 (rev 10)


[17179569.184000] ACPI: RSDP (V000 acpiam) @ 0x000f84e0
[17179569.184000] ACPI: RSDT (V001 amit oemrsdt 0x07000604 mfst 0x00000097) @ 0x37fc0000
[17179569.184000] ACPI: SSDT (V001 ami acpi2ppc 0x00000001 ami 0x00000001) @ 0x37fc4290
[17179569.184000] ACPI: DSDT (v001 ammr_ ammr_b36 0x00000b36 intl 0x20051117) @ 0x00000000
[17179569.680000] ACPI: looking for DSDT...not found!


[17179610.856000] ide0: bm-dma at 0xff00-0xff07, Bios settings: hda:dma, hdbio
[17179611.596000] hda: lite-on dvdrw L+1-20a1+l, atapi cd/dvd-ram drive
[17179612.848000] hda: atapi 48x dvd-ram dvd-ram cd-r/rw drive, 2048kb cache, vdmal66
[17179658.585000] hda_codec: unknown model for alc883, trying to auto-probe from BIOS...
17179620.636000) hda-inter: invalid position buffer using lpib read method instead

Sorry if i misspelled/left something out... this is all from memory.

As for system specs:

Motherboard: MSI K9AGM
HD: Western Digital Caviar SE16 WD3200KS 320GB 7200 RPM SATA 3.0Gb/s Hard Drive
Processor: AMD Athlon 64 x2 Dual-Core 4600+ 2.4
RAM: not 100% sure
DVD: lightscribe burner
No special video card, yet, just shared

 

[linux_0]

Thanks for the info.

I can see several unknown IDs in your lspci. What version are you trying to install?

For your system I would suggest version 6.10-desktop-amd64

http://mirrors.kernel.org/ubuntu-releases/6.10/ubuntu-6.10-desktop-amd64.iso

http://mirrors.kernel.org/ubuntu-releases/6.10/MD5SUMS

http://mirrors.kernel.org/ubuntu-releases/6.10/MD5SUMS.gpg


If you are using an older version it may not be able to recognize all of your hardware.


I did not see the SATA controller on the list, is it enabled in the BIOS in non-RAID mode?


You might also want to give Fedora a shot too:

http://mirrors.kernel.org/fedora/core/6/x86_64/iso/FC-6-x86_64-DVD.iso

http://mirrors.kernel.org/fedora/core/6/x86_64/iso/SHA1SUM

http://mirrors.kernel.org/fedora/core/6/x86_64/iso/README-BURNING-ISOS-en_US.txt

GL :-D

 

[skreid]

I was trying to install i386 (v6.10). Someone told me not to do 64 because the ATI drivers for it aren't that great.

 

[linux_0]

May I ask who said that? So I can give them a cookie.

PM me if you prefer to keep their identity private :-D

I was trying to install i386 (v6.10). Someone told me not to do 64 because the ATI drivers for it aren't that great.

 

[skreid]

heh, It's not someone from this forum

Edit: Downloading the one you recommended. I'll give that a try in a bit (watching Lost )

I was going to try Fedora, but I need more blank dvd's =\

 

[linux_0]

Fedora also comes on a set of about 50 CDs, j/k :lol: :lol:

I recommend the DVD if you have or can get blanks.

It is a lot easier to use one DVD instead of 6 CDs

heh, It's not someone from this forum

Edit: Downloading the one you recommended. I'll give that a try in a bit (watching Lost )

I was going to try Fedora, but I need more blank dvd's =\

 

[bmouring]

It seems that the issue here is the ATI SB600 chipset that handles the SATA ports on your motherboard. For the time being (until a proper patch has made it back into the mainline kernel), on install change the boot parameters to include the pci=nomsi parameter.

For Fedora, on boot, then you get to the screen which has the "boot:" prompt, type in[code:1:6cf145f9c9]linux pci=nomsi[enter][/code:1:6cf145f9c9] This should get the machine to recognize the drive, if not you may also try the irqpoll kernel parameter, but be warned that this little daisy tends to create lotsa kernel warning and error messages so logs are harder to sift through but seems stable from what I've read.

I would say the best option is to try the latest kernels as there are patches and fixes floating around concerning this issue so it will likely make it into mainline sooner than later.