On 5 February 2013 20:15, Rowan Berkeley wrote:
>
> It worked!
Yay! \o/
>Now, we need some way of directing people away from all the
> erroneous Ubuntu Forums pages that also say [SOLVED] but don't work, like
> the one I followed, which was:
>
> http://ubuntuforums.org/showthread.php?t=1850267
On 05/02/13 19:29, Mark Einon wrote:
Ok, looks like the same issue, in that the kernel isn't quite recent
enough to support this device.
I'd suggest giving the instructions in the link I posted earlier a go.
It may need to be patched to work, if so, It's not a biggie - let me
know if it doesn't
On 5 February 2013 17:47, Rowan Berkeley wrote:
> Hi Mark,
>
> Here we are. I can see what I did wrong: I screwed up r8169, which is the
> Ethernet driver, thinking it was maybe a rival wireless driver. Definitely
> my bad.
>
> uname -a
> linuc rowan-Compaq 3.5.0-23-generic #35-Ubuntu SMP [date &
Hi Mark,
Here we are. I can see what I did wrong: I screwed up r8169, which is
the Ethernet driver, thinking it was maybe a rival wireless driver.
Definitely my bad.
uname -a
linuc rowan-Compaq 3.5.0-23-generic #35-Ubuntu SMP [date & time]
sudo lshw -C network
*-network
description: Ethernet
On 5 February 2013 13:36, Rowan Berkeley wrote:
> On 05/02/13 12:49, Rowan Berkeley wrote:
>>
>>
>> I've given the machine a complete 12.10 reinstall from the USB stick, so
>> as to start again without the ill effects of whatever I did previously,
>> fixing which could have gone on forever. In a m
On 05/02/13 12:49, Rowan Berkeley wrote:
I've given the machine a complete 12.10 reinstall from the USB stick, so
as to start again without the ill effects of whatever I did previously,
fixing which could have gone on forever. In a minute I shall be able to
see what I've got and what I've not.
On 05/02/13 11:55, Rowan Berkeley wrote:
No, the machine is running 12.10, but I downgraded the kernel to
3.5.0-22 because I broke 3.5.0-23's Ethernet interface somehow with my
tinkering. So, before proceeding with your suggestion, I decided to
reinstall 3.5.0-23 and see if it worked. And when I
On 05/02/13 11:32, Mark Einon wrote:
It appears that the chip you have is quite new,
and is only supported for newer kernels - for some reason I had it in
my head that the laptop was quite old. As you have a 2.5.0 kernel, I
assume you're on 12.04 - so I think this may help, short of compiling
a n
On 5 February 2013 10:51, Rowan Berkeley wrote:
> I think the double dash in --nn is wrong, should be a single dash.
Yep, sorry about that - my bad.
> -nn Show both textual and numeric ID's (names and numbers)
> lspci -nn
> 04.00.0 Network controller [0280]: Ralink corp. RT3290
> Wireless 802.11
On 05/02/13 09:48, Mark Einon wrote:
On 5 February 2013 08:58, Rowan Berkeley wrote:
Hi, Mark. Thanks for the thoughts.
~/pcilist.text: No such file or directory
Ah, ok. Not sure what when on there - perhaps you could just try
'lspci --nn' and copy the printout the way you know works?
The P
On 5 February 2013 08:58, Rowan Berkeley wrote:
> On 04/02/13 23:03, Mark Einon wrote:
>>
>>
>> Ok. So the device doesn't have a driver loaded, so it is a kernel
>> issue... It knows it's a ralink device (PCI vendor ID 0x1814) but
>> doesn't know what the device ID is. Can you please run, to find
On 04/02/13 23:03, Mark Einon wrote:
Ok. So the device doesn't have a driver loaded, so it is a kernel
issue... It knows it's a ralink device (PCI vendor ID 0x1814) but
doesn't know what the device ID is. Can you please run, to find out
what this ID is:
$> lspci --nn > ~/pcilist.txt
and copy t
On 4 February 2013 17:03, Rowan Berkeley wrote:
> Now I have the huge print-out from the terminal which was requested, having
> somehow managed to copy it from the terminal, paste it into a notepad file,
> copy that to the external hard drive, then from there to the Lenovo, which
> is what I'm usi
On 04/02/13 16:43, Mark Einon wrote:
The command 'rfkill list' should tell you which rf kill switches are
available, and what their state is.
0: hp wifi: Wireless LAN
hard blocked: no
soft blocked: no
1: hp-bluetooth: Bluetooth
hard blocked: no
soft blocked: no
Now I have the huge print-out
On 4 February 2013 16:38, Rowan Berkeley wrote:
> On 04/02/13 15:59, Colin Law wrote:
>>
>> On 4 February 2013 15:48, Rowan Berkeley wrote:
>>>
>>>
>>> Now it has Ubuntu installed, it simply won't boot from
>>> the USB stick, no matter how much I juggle the boot order around. Don't
>>> ask
>>> me
On 4 February 2013 16:38, Rowan Berkeley wrote:
> On 04/02/13 15:59, Colin Law wrote:
>>
>> On 4 February 2013 15:48, Rowan Berkeley wrote:
>>>
>>>
>>> Now it has Ubuntu installed, it simply won't boot from
>>> the USB stick, no matter how much I juggle the boot order around. Don't
>>> ask
>>> me
On 04/02/13 15:59, Colin Law wrote:
On 4 February 2013 15:48, Rowan Berkeley wrote:
Now it has Ubuntu installed, it simply won't boot from
the USB stick, no matter how much I juggle the boot order around. Don't ask
me why, it just won't.
What you have installed on the disk will not affect wh
On 4 February 2013 15:48, Rowan Berkeley wrote:
> On 04/02/13 15:22, Colin Law wrote:
>>
>>
>> I suggested (I think) some time back in a different thread that you
>> try booting from the live CD/USB and confirm that the wireless is not
>> found in that case, but I don't think you replied. See wha
On 4 February 2013 14:42, Rowan Berkeley wrote:
> On 04/02/13 14:31, Mark Einon wrote:
>>
>> I'm really surprised that this driver is not supported in your kernel
>> - what version do you have? (run '$> uname -a' on the command line to
>> find out).
>>
>> I think it's been in since 3.0, and availa
On 04/02/13 15:22, Colin Law wrote:
I suggested (I think) some time back in a different thread that you
try booting from the live CD/USB and confirm that the wireless is not
found in that case, but I don't think you replied. See what
sudo lshw -C network
says about the wireless network when liv
On 4 February 2013 14:42, Rowan Berkeley wrote:
> On 04/02/13 14:31, Mark Einon wrote:
>>
>> I'm really surprised that this driver is not supported in your kernel
>> - what version do you have? (run '$> uname -a' on the command line to
>> find out).
>>
>> I think it's been in since 3.0, and availa
On 04/02/13 14:31, Mark Einon wrote:
I'm really surprised that this driver is not supported in your kernel
- what version do you have? (run '$> uname -a' on the command line to
find out).
I think it's been in since 3.0, and available with compat-wireless from 2.6.30.
The rt2860.bin file is also
On 4 February 2013 13:41, Alan Pope wrote:
> On 04/02/13 13:21, Rowan Berkeley wrote:
>>
>> I already in effect tried that; when I ran the command 'unzip' on it,
>> the machine renamed it "sp58586.exe.ZIP" and looked at it and said "gar
>> nicht," or words to that effect.
>>
>
> I grabbed the same
On 04/02/13 13:41, Alan Pope wrote:
> On 04/02/13 13:21, Rowan Berkeley wrote:
>> I already in effect tried that; when I ran the command 'unzip' on it,
>> the machine renamed it "sp58586.exe.ZIP" and looked at it and said
>> "gar nicht," or words to that effect.
>
> I grabbed the same file and i
On 04/02/13 13:21, Rowan Berkeley wrote:
I already in effect tried that; when I ran the command 'unzip' on it,
the machine renamed it "sp58586.exe.ZIP" and looked at it and said "gar
nicht," or words to that effect.
I grabbed the same file and indeed it's a windows executable and not a
zip or
On 04/02/13 13:21, Rowan Berkeley wrote:
> On 04/02/13 13:14, Kris Douglas wrote:
>>
>> What he meant was that there may be zip data inside. Rename the file
>> yo something.zip and see if it opens in your Archive viewer.
>>
>> Ahem. OK. But anyway, to return to my original point and Alan's
>> respo
On 04/02/13 13:14, Kris Douglas wrote:
What he meant was that there may be zip data inside. Rename the file
yo something.zip and see if it opens in your Archive viewer
You should be able to right click the thing and open with option should
be archive manager
--
ubuntu-uk@lists.ubuntu.co
On 04/02/13 13:14, Kris Douglas wrote:
What he meant was that there may be zip data inside. Rename the file
yo something.zip and see if it opens in your Archive viewer.
Ahem. OK. But anyway, to return to my original point and Alan's
response to it, there's nothing to unzip.
I already in ef
What he meant was that there may be zip data inside. Rename the file yo
something.zip and see if it opens in your Archive viewer.
On 4 Feb 2013 12:36, "Rowan Berkeley" wrote:
> On 04/02/13 12:07, Colin Law wrote:
>
>> On 4 February 2013 12:01, Rowan Berkeley
>> wrote:
>>
>>> On 04/02/13 11:46, C
On 04/02/13 12:07, Colin Law wrote:
On 4 February 2013 12:01, Rowan Berkeley wrote:
On 04/02/13 11:46, Colin Law wrote:
On 4 February 2013 11:40, Rowan Berkeley wrote:
Unfortunately, it seems that you can
have a package sitting in plain view on the desktop but the terminal will
keep telling
On 4 February 2013 12:01, Rowan Berkeley wrote:
> On 04/02/13 11:46, Colin Law wrote:
>>
>> On 4 February 2013 11:40, Rowan Berkeley wrote:
>>>
>>> Unfortunately, it seems that you can
>>> have a package sitting in plain view on the desktop but the terminal will
>>> keep telling you "no such file
On 04/02/13 11:46, Colin Law wrote:
On 4 February 2013 11:40, Rowan Berkeley wrote:
Unfortunately, it seems that you can
have a package sitting in plain view on the desktop but the terminal will
keep telling you "no such file or package." This rather stops me in my
tracks.
Show us the command
Have you thought about trying
Lauchpad or Bugzilla?
I had problems with my HP3070a Printer/Scanner and it was fixed
after I posted my problem in Launchpad.
I was given this link;
http://www.hplipopensource.com/hplip-web/install/install/ind
On 4 February 2013 11:40, Rowan Berkeley wrote:
> On 04/02/13 08:38, Alan Pope wrote:
>>
>> On 04/02/13 04:03, Rowan Berkeley wrote:
>>>
>>> In my unending search for ways to implement the wireless driver on my
>>> converted Compaq machine, I have found the recommended driver on HP's
>>> website,
On 04/02/13 08:38, Alan Pope wrote:
On 04/02/13 04:03, Rowan Berkeley wrote:
In my unending search for ways to implement the wireless driver on my
converted Compaq machine, I have found the recommended driver on HP's
website, and it comes in an MS-DOS .exe package which ndiswrapper cannot
use be
On 04/02/13 04:03, Rowan Berkeley wrote:
In my unending search for ways to implement the wireless driver on my
converted Compaq machine, I have found the recommended driver on HP's
website, and it comes in an MS-DOS .exe package which ndiswrapper cannot
use because the latter needs to access cert
In my unending search for ways to implement the wireless driver on my
converted Compaq machine, I have found the recommended driver on HP's
website, and it comes in an MS-DOS .exe package which ndiswrapper cannot
use because the latter needs to access certain component files in the
package.
-
37 matches
Mail list logo
