This bug report was marked as Incomplete and has not had any updated
comments for quite some time. As a result this bug is being closed.
Please reopen if this is still an issue in the current Ubuntu
development release http://cdimage.ubuntu.com/daily-live/current/ .
Also, please be sure to
This bug report was marked as Incomplete and has not had any updated
comments for quite some time. As a result this bug is being closed.
Please reopen if this is still an issue in the current Ubuntu release
http://www.ubuntu.com/getubuntu/download . Also, please be sure to
provide any requested
Maybe someone should look into the error I got, Before marking this as
expired?
[ 0.167144] pci :01:0b.0: BAR 6: address space collision on of
device [0xfc9f-0xfc97fff]
I would try myself but I no idea what this error means, and no idea where to
start.
I'm sure someone more familiar
Things got worse with Karmic.
I was able to get this card working in Jaunty by downloading and compiling the
driver from
http://www.realtek.com/downloads/downloadsView.aspx?Langid=1PNid=24PFid=1Level=6Conn=5DownTypeID=3GetDown=falseDownloads=true
but, after upgrading to Karmic, also compilation
Eventually got around to trying out 9.10 Beta live CD - the problem is
still here: lockup just before showing the login manager
However I did get an error message early on in the boot process, before the
bootsplash logo which said this:
[0.167144] pci :01:0b.0: BAR 6: address space
From these last few comments, it appears to be a hardware problem. Try
9.10 as below and if it occurs, try disabliing devs per #21. If it
works, note the IRQ etc. and let us know.
Can you confirm this issue exists with the most recent Karmic Koala 9.10
Beta release? ISO CD images are available
I have just now downloaded the 9.10 beta and am currently burning it. I
will try it out very soon
But is this really a true hardware issue? What is the definition of
such? As I said before, the computer which locks up under Kubuntu runs
fine with Windows XP.
I would have thought that a proper
That might definately be possible, the PC is an old Dell optiplex gx270 which
only has 1 pci slot, I did disable the com and lpt ports in order to be sure
enough IRQs where available.
My neighbour is running 9.04 with exactly the same car (same card/chipset/etc)
and for him it worked out of the
I can confirm this bug in 9.10 , apperently it is only with certain
revisions/brands using this chip as I've seen people succesfully using this
card in 9.10, with the modules disabled (actually renamed) the machine boots
correctly with card plugged in.
I'll drop an lspci after getting the
I think there is more to this than just the WiFi card itself, possibly.
I put the card in another PC (Socket 939 AMD with nForce 4 SLI chipset)
and with Kubuntu 9.04 it worked perfectly.
Strangely enough, I still got the Unknown hardware address type 801
error but the card DOES WORK.
Perhaps
I was able to get to a GUI with these steps:
1) Restart computer with Live CD in tray (I used Jaunty)
2) At the boot menu choose boot options, press escape to get rid of the menu,
replace 'quiet splash' with 'single'
3) At the recovery menu choose 'root'
4) Unload the faulty rtl8180 driver with
I've had this problem ever since Intrepid came out. I tried reporting
the bug then but nobody ever looked at it.
I have no problems using NDISwrapper but when the system locks up
because of a bad driver I can't do that. Would it be possible to
blacklist the RTL818x driver?
If you'd like, I can
I tried single without quiet and splash but all I get is the
recovery menu. If I choose Resume normal boot It just locks up at the
cursor before the login screen again.
I did however manage to get it to lockup in the console by choosing
shell prompt with networking
Attached is a photo
**
Agreed, orbiting KDE cursors are a bit useless here. I have had to resort to
my Nikon DSLR and just shoot frames until I finally got one that made sense.
The fact that you got to X and the KDE logo is a good sign, of sorts. Try
adding single
to the boot command line, leaving the delete of
Sorry about not beiing clear in the apport command line. The bug 3
should have been 395403.
The info you sent didn't show the device. Could you clarify, is this a
pcmcia hotplug or a pci slot card? If it is the former, what happens
when you plug it in after the machine is up?
Try editing the
No worries about the apport confusion. I figured it out pretty quickly.
It's a PCI slot card (not hot swappable) and due to the lockup I can't
post debug info with it attached.
But I will try what you say to show the console messages and take a
photo. I'll upload it shortly.
--
Realtek
Unfortunately the console text disappears before the lockup occurs.
The computer freezes with the KDE4 hourglass frozen in the middle of a
black screen.
Please advise on how to proceed from here.
** Attachment added: IMG_3416.PNG
http://launchpadlibrarian.net/28900535/IMG_3416.PNG
--
After confirming the issue remains with the latest update, be sure to
also run the following command from a Terminal
(Applications-Accessories-Terminal). It will automatically gather and
attach updated debug information to this report, using this bug number
on the command line.
apport-collect -p
I did apply the latest updates but that was with the card removed.
I can't even load the shell with networking support from the recovery
menu with the card attached, it also causes a lockup.
I will do what you said and send the debug information but only with the
card not plugged in - It would
I tried to run: apport-collect -p linux-image-2.6.28-11-generic bug
395403
but just received this error: bash: syntax error near unexpected token
`newline'
--
Realtek RTL-8185 based Wifi NIC causes system lockup
https://bugs.launchpad.net/bugs/395403
You received this bug notification because
20 matches
Mail list logo
