Install Experience needed to install Fedora 7 on HP tx1000 series laptop

jiabo · #1 3rd June 2007, 03:12 AM

Hi, all

I'd like to install Fedora 7 on my sexy HP tx1115nr laptop, if you had such expericence, could you please share with me? Thanks.

Best regards.

matth45 · #2 25th July 2007, 04:06 PM

I've installed fedora 7 on my hp tx1000. It's no easy task, because of a couple issues:

The APIC/ACPI support is broken for linux. This is partly because the DSDT was compiled by a Microsoft compiler, and explicitly checks the OS name to enable/disable various features. There's support for faking it out in kernel 2.6.22, but as far as I know, no one has everything working yet in any distro.

The front headphone jacks don't work, even when you get the audio working, because the codec isn't fully supported in ALSA snd-hda-intel.

The touchscreen driver (evtouch) isn't working under x86_64 (I hear it works under i386) but it also isn't included in any repos, so you'll have to build it yourself.

At any rate, even though I run fedora I've been participating in this thread on the ubuntuforums, which you'll probably find very helpful.

http://ubuntuforums.org/showthread.php?t=442483

Let me know if you need any specific help.

jiabo · #3 28th July 2007, 05:32 AM

Thank you matt, may I call you matt?
Actually I've already installed ubuntu 7.0.4 on my laptop via the guide you refered.
It's OK, and it works fine.

The reason I want to install fedora or Redhat enterprise desktop on my laptop is just because I was so familiar with redhat.

I will try to install fedora 7 on my laptop. ^_^. Thank you agian..

matth45 · #4 28th July 2007, 07:50 PM

Yeah, I've used ubuntu a little but I like fedora a lot better. All the dpkg stuff reminds me of the traumatic days of debian and the 2.2 kernel :P

Anyway, good luck installing fedora. If you got ubuntu working, the procedure is much the same with fedora. I've been booting with

Code:

rhgb quiet acpi_osi="!Linux" acpi_os_name="Windows 2006" noapic

But the usb won't hotplug that way. If you boot with nolapic instead of noapic it won't hang either, and the usb system will work, but the proprietary NVIDIA driver won't want to run in edge triggered interrupt mode. There's supposed to be a way to disable the check, (NVreg_RMEdgeIntrCheck) but it doesn't seem to work.

For the wireless I recommend the latest svn for the ndiswrapper along with this driver:

Code:

Card:Broadcom Corporation Dell Wireless 1390 WLAN Mini-PCI Card rev 02

    *  PCIID: 03:00.0 0280: 14e4:4311 (rev 02)
    *  PC: HP pavilion tx1000 series ‘GD617AV’
    *  OS: Fedora 7
    *  Driver Used: Win32 Driver from HP
      http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=ob-45290-1&lc=en&cc=sg&dlc=en&product=3245619&os=228&lang=en HP Driver
    *  Other: Kernel version 2.6.21-1.3228.fc7.x86_64 Ndis 1.47

(From here: http://ndiswrapper.sourceforge.net/j...,33/id,list_b/)

By checking through the ALSA source code (/alsa-kernel/pci/hda/patch_realtek.c) and the codec info (/proc/asound/card0/codec#0) I think I see why the headphone jacks don't work? (uninitialized nid's... 0x05 and 0x06???). Fixing it may not be too complicated, but I'll be away for a couple weeks so I won't have time to look at it. You should keep checking alsa releases here: ftp://ftp.suse.com/pub/projects/alsa/snapshot/driver/

matth45 · #5 24th August 2007, 03:34 AM

Headphone jacks are working!

I just downloaded the latest alsa development snapshot (ftp://ftp.suse.com/pub/projects/alsa...070824.tar.bz2) and they now have a HP TX 1000 model for the ALC861VD/660VD chip!

Quote:

ALC861VD/660VD
3stack 3-jack
3stack-dig 3-jack with SPDIF OUT
6stack-dig 6-jack with SPDIF OUT
3stack-660 3-jack (for ALC660VD)
3stack-660-digout 3-jack with SPDIF OUT (for ALC660VD)
lenovo Lenovo 3000 C200
dallas Dallas laptops
hp HP TX1000

auto auto-config reading BIOS (default)
I built and installed this on my system, and the headphone jacks both work (once you unmute them)! The mute light turns off when I unmute the headphones too. But it strangely turns back on under some circumstances. This doesn't seem to affect the audio at all though.

**REMEMBER if you have added another model to the snd-hda-intel module in the /etc/modprobe.conf file, you must delete it and re-insert the snd-hda-intel module before the audio will work.

OperatorOne · #6 10th September 2007, 11:27 PM

Anyone have any luck getting rid of the "disabling IRQ#7'" message? also, how can I remove the pre-installed firmware/driver and get my wifi working? It keeps complaining my firmware is out of date for the driver I am using, I installed the Win XP driver and ndiswrapper.

matth45 · #7 11th September 2007, 01:51 AM

You get the irq 7 message when you boot with noapic, right? Add irqfixup as well. That should take care of the irq 7 messages, and also the fact that usb doesn't hotplug.

As far as wifi, use this - taken from (http://ndiswrapper.sourceforge.net/j...,33/id,list_b/):

Quote:

83.
Card:Broadcom Corporation Dell Wireless 1390 WLAN Mini-PCI Card rev 02

*
PCIID: 03:00.0 0280: 14e4:4311 (rev 02)
*
PC: HP pavilion tx1000 series ‘GD617AV’
*
OS: Fedora 7
*
Driver Used: Win32 Driver from HP
*
http://h10025.www1.hp.com/ewfrf/wc/s...os=228&lang=en HP Driver
*
Other: Kernel version 2.6.21-1.3228.fc7.x86_64 Ndis 1.47

I've been using the CVS ndiswrapper, since the version 1.47 seems to lockup occasionally with this card/driver.

If that doesn't solve your wifi problem, can you post more details?

OperatorOne · #8 12th September 2007, 07:34 PM

BTW, headphone jack thing works like a charm, nice job. Ok I changed my boot options to the following...

Code:

kernel /boot/vmlinuz-2.6.22.4-65.fc7 ro root=LABEL=/1 pci=nommconf irqfixup rhgb quiet nolapic irqpoll

So far that seems to be doing the job. As far as the Wifi, how do I gut out the remnants of the currently installed setup? FC is complaining that I the firmware is wrong and then throws a boatdload of errors....

Code:

b43-phy0 debug: Adding Interface type 2
b43-phy0 ERROR: Microcode not responding
b43-phy0 debug: Adding Interface type 2
b43-phy0 ERROR: YOUR FIRMWARE IS TOO OLD. Firmware from binary drivers older than version 4.x is unsupported. You must upgrade your firmware files.

I had followed another thread on here about installing the right ndiswrapper driver, and so I did that, which is when the system began complaining about the firmware, leading me to think if I can just change that part it might work? would be nice to have wifi again. I hate booting into Vista. blah.

Here is the output of ndiiswrapper

Code:

#ndiswrapper -l
bcmwl5 : driver installed
        device (14E4:4311) present (alternate driver: b43)

OperatorOne · #9 12th September 2007, 07:40 PM

Ok so mu USB works as it's supposed to now, thanks so much. It's almost impossible to function without USB support. :P

OperatorOne · #10 13th September 2007, 05:52 PM

So I ended up changing my boot parameters to basically what you have above, except I added the irqfixup thing. Can't remember where I got pci=nommconf but it seems to be more stable without it, so I removed it.

I had the wifi actually working last night, but then pup or whatever the automatic update is called ran and updated a bunch of things, not I get wirless (sort of). It detects APs and I can attempt to connect but it either doesnt connect or it connects for a second or two and then dumps out.

Now I get this horrendous message on bootup about my b43-phy0 device.... here's a clip from dmesg...

Code:

b43-phy0 debug: Adding Interface type 2
b43-phy0 debug: Loading firmware version 351.126 (2006-07-29 05:54:02)
b43-phy0 debug: Radio turned on
b43-phy0 debug: Radio enabled by hardware
b43-phy0 debug: Invalid LO control pair (I: 111, Q: 111)

Call Trace:
 [<ffffffff88176159>] :b43:b43_lo_g_adjust_to+0x66/0x71
 [<ffffffff88176646>] :b43:lo_measure_restore+0xd4/0x360
 [<ffffffff8817790b>] :b43:b43_lo_g_measure+0x1039/0x1078
 [<ffffffff881737da>] :b43:b43_phy_initg+0xad2/0xd10
 [<ffffffff881741c6>] :b43:b43_phy_init+0x582/0x5a7
 [<ffffffff88167f3a>] :b43:b43_chip_init+0x69e/0x9b5
 [<ffffffff881684ef>] :b43:b43_wireless_core_init+0x29e/0x7bb
 [<ffffffff8816955a>] :b43:b43_add_interface+0x5f/0xf4
 [<ffffffff881367ca>] :mac80211:ieee80211_open+0x23f/0x370
 [<ffffffff811e6af2>] rtnl_fill_ifinfo+0x32d/0x488
 [<ffffffff811e05d1>] dev_open+0x2f/0x6e
 [<ffffffff811de799>] dev_change_flags+0x5a/0x118
 [<ffffffff811e768c>] rtnl_setlink+0x2bf/0x3f2
 [<ffffffff811e6d74>] rtnetlink_rcv_msg+0x0/0x1e5
 [<ffffffff811f4ecb>] netlink_run_queue+0x75/0x103
 [<ffffffff811e6d21>] rtnetlink_rcv+0x30/0x4c
 [<ffffffff811f53a7>] netlink_data_ready+0x12/0x50
 [<ffffffff811f419d>] netlink_sendskb+0x23/0x3c
 [<ffffffff811f5382>] netlink_sendmsg+0x2b7/0x2ca
 [<ffffffff811d4855>] sock_sendmsg+0xea/0x107
 [<ffffffff810453e1>] autoremove_wake_function+0x0/0x2e
 [<ffffffff810453e1>] autoremove_wake_function+0x0/0x2e
 [<ffffffff81075ebe>] zone_statistics+0x3f/0x60
 [<ffffffff810706c8>] get_page_from_freelist+0x38a/0x51c
 [<ffffffff810708cc>] __alloc_pages+0x72/0x2d4
 [<ffffffff811d4a89>] sys_sendmsg+0x217/0x28a
 [<ffffffff811163a7>] __up_read+0x19/0x7f
 [<ffffffff8106185a>] audit_syscall_entry+0x31/0x174
 [<ffffffff81009cd5>] tracesys+0xd5/0xda

b43-phy0 ERROR: Adjusting Local Oscillator to an uncalibrated control pair: rfatt=3,no-padmix bbatt=0
b43-phy0 ERROR: bbatt(11) >= size of LO array
b43-phy0 ERROR: Adjusting Local Oscillator to an uncalibrated control pair: rfatt=3,no-padmix bbatt=0
b43-phy0 debug: Chip initialized
b43-phy0 debug: 32-bit DMA initialized
b43-phy0 debug: Wireless interface started
b43-phy0 ERROR: Adjusting Local Oscillator to an uncalibrated control pair: rfatt=3,no-padmix bbatt=0
ADDRCONF(NETDEV_UP): wlan0: link is not ready
bridge-eth1: enabling the bridge
bridge-eth1: up
eth1: no IPv6 routers present
b43-phy0 ERROR: Adjusting Local Oscillator to an uncalibrated control pair: rfatt=3,no-padmix bbatt=2
b43-phy0 debug: Invalid LO control pair (I: 111, Q: 111)

Call Trace:
 [<ffffffff88176159>] :b43:b43_lo_g_adjust_to+0x66/0x71
 [<ffffffff88176646>] :b43:lo_measure_restore+0xd4/0x360
 [<ffffffff8817790b>] :b43:b43_lo_g_measure+0x1039/0x1078
 [<ffffffff8816577b>] :b43:b43_shm_read16+0xb1/0xbc
 [<ffffffff8816765b>] :b43:do_periodic_work+0x41/0x1ed
 [<ffffffff881795ae>] :b43:b43_dma_tx_suspend_ring+0x53/0x62
 [<ffffffff8816a454>] :b43:b43_periodic_work_handler+0x104/0x1d8
 [<ffffffff8816a350>] :b43:b43_periodic_work_handler+0x0/0x1d8
 [<ffffffff81041d3f>] run_workqueue+0x7f/0x10b
 [<ffffffff810425d6>] worker_thread+0x0/0xe4
 [<ffffffff810426b0>] worker_thread+0xda/0xe4
 [<ffffffff810453e1>] autoremove_wake_function+0x0/0x2e
 [<ffffffff8104528c>] kthread+0x47/0x73
 [<ffffffff8100a978>] child_rip+0xa/0x12
 [<ffffffff81045245>] kthread+0x0/0x73

the rest is pretty much more of the same. Before the update I did not recieve these errors. blah. Now what do I do?

matth45 · #11 13th September 2007, 06:10 PM

I noticed there was a new kernel available last night. so if you updated with yum, you probably got it. The easiest thing to do is select your old kenel at boot in the grub menu, and you should be back where you were before the upgrade. You can make this the default by changing the "default=" line in /etc/grub.conf. Remember this is 0 based. You can also tell yum not to upgrade the kernel any further. Google knows how to do this

I think the reason that you're getting what you pasted up there is that 1) the b43 driver doesn't work with the bmc4311 chip very well (http://linuxwireless.org/en/users/Dr...supportedchips) (it's in the tx1000), and 2) the name of the driver has changed in upstream kernels. So, if you had previously blacklisted bmc43xx so that the ndiswrapper could load, the b43 driver will now be loading and grabbing the card before the ndiswrapper.

So to blacklist it again you'll have to add lines to two files (if someone knows a better way to do this please let me know):

/etc/modprobe.d/blacklist:
blacklist b43

/etc/modprobe.conf:
alias b43 off

Then if you get a message like "module off not found" during boot you can ignore it.

Also, if you're using the ndiswrapper, you'll need a line like
/etc/modprobe.conf
alias wlan0 ndiswrapper

But if you've had it working once you probably have this already.

Just FYI, my kernel boot line is something like: quiet rhgb noapic irqfixup acpi_osi="!Linux" acpi_os_name="Windows 2006"

I've found this works pretty well.

matth45 · #12 13th September 2007, 06:14 PM

Oops, I hadn't read your earlier posts. Do the blacklist thing above for the b43 driver so that you're only using the ndiswrapper. If you're loading both the ndiswrapper and b43 there's some contention for the card, and who wins is kind of a crap shoot. This should solve your wireless problems. And remove irqpoll from your kernel boot line. You shouldn't use it with irqfixup. If anything it slows down your system a lot.

OperatorOne · #13 14th September 2007, 03:34 AM

Well, since I posted last I have changed my situation... some good and some bad.

In testing, I when I rmmod b43 my wireless card no longer works. This might be because I became irritated with the ndiswrapper thing so I followed instructions on a post located here....

http://www.linuxhomenetworking.com/w...ess_Networking

and when that didn't work I followed this one here...

http://fedoraforum.org/forum/showthr...light=broadcom

My current situation is that my wifi is working (mostly). Sometimes it refuses to connect but alot of the time I can make it connect. I have WEP enabled on my WAP. I still get the crazy messages so this is what I did to try and stop them....

First I tried to blacklist b43, figuring that must be the issue, but when I do that my WiFi no longer works. it disappears completely from the Knetwork widget in the "system tray". So when I remove b43 from the blacklist, the WiFi shows up in the widget, and shows me all of the radios it sees and their strengths. So that's pretty sweet, when I click to connect to my WAP, it's a hit and miss thing.

So if I can get rid of those little messages, and resolve the hit and miss, I think I'm styling. I have a strong feeling I am somewhere between two different solutions and I am not sure how to press the undo button. ;-)

and if this matters, sometimes it only connects at 1mb, which is ridiculous considering the WAP is about 6 feet from the notebook and reports a 91% signal strength in the widget. Othertimes (like now for example) I am running at 62mb with 96% signal strength.

1 Last thing... for some reason the widget doesn't save my wep key and I have to retype that hex number each time it connects.

matth45 · #14 14th September 2007, 03:47 AM

From what you describe it sounds like you're actually using the b43 driver to connect. That's good news, because I'd much rather use the native linux driver than the ndiswrapper if its actually working.

However, it sounds like when the b43 people say that they don't fully support the 4311 chipset, they aren't kidding. I am guessing that the spotty performance you're seeing is an effect of poor support for this particular chipset. So I think you ought to try using the ndiswrapper for another couple months until b43 is more stable.

Here's what you can try (as root):
blacklist the b43 driver, as above.
# modprobe -r b43
# lsmod | grep b43
There should be no output from the above command, confirming that b43 is removed from your system.
# ndiswrapper -l
You should see the same message from your previous post, confirming that the ndiswrapper is set up correctly
# modprobe ndiswrapper
# lsmod | grep ndiswrapper
You should see "ndiswrapper ### ###" confirming that the ndiswrapper module is inserted.
# ifconfig wlan0
You should see a full list of parameters from your wireless card, much like this:

wlan0 IEEE 802.11b ESSID:"mynetwork"
Mode:Managed Frequency:2.412 GHz Access Point: 00:0C:41:F3

B

B
Bit Rate=11 Mb/s Tx-Power:32 dBm
RTS thr:off Fragment thr:off
Power Management:off
Link Quality:64/100 Signal level:-55 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:223 Invalid misc:20969 Missed beacon:0

Once you get this, your other network manager should be able to take over and configure the connection.

Hope that helps. Let me know if any of these steps fail.

OperatorOne · #15 14th September 2007, 06:20 AM

Ok I have successfully blacklsited the b43 driver, and the wierd messages have disappeared! Sweet. Ok so then I retraced my steps to install ndiswrapper, and when I used ndiswrapper -l I got this...

Code:

[root@localhost operatorone]# /usr/sbin/ndiswrapper -l
bcmwl5 : driver installed
        device (14E4:4311) present (alternate driver: ssb)

I also blacklisted ssb, and now when I rebooted, I can use modprobe ndiswrapper to load the driver and it works great.

Now I just need to figure out how to make the 'modprobe ndiswrapper' part permanent so I don't have to execute that each boot time. - SCRATCH THAT I just added it to /etc/rc.d/rc.local and now it works like a charm. Now I get an odd message about ACPI and IRQ9...

Code:

ACPI: PCI Interrupt Link [LK1E] enabled at IRQ 9
PCI: setting IRQ 9 as level-triggered
ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [LK1E] -> GSI 9 (level, low) -> IRQ 9
PCI: Setting latency timer of device 0000:03:00.0 to 64
ndiswrapper: using IRQ 9
wlan0: ethernet device 00:1a:73:32:43:78 using NDIS driver: bcmwl5, version: 0x4640f05, NDIS version: 0x501, vendor: 'NDIS Network Adapter', 14E4:4311.5.conf
wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
usbcore: registered new interface driver ndiswrapper
ADDRCONF(NETDEV_UP): wlan0: link is not ready

But this all looked ok to me so I am not concerned about it as it works great. I can scratch this off my tx1120 to do list.

You rock man thanks.

Left is my touchscreen, fingerprint reader, and my webcam works but not in kopete for some reason I get a green screen. I have looked at the touchscreen stuff, but have decided to put it off for now as my X windows currently works great so the touchscreen is not that important.