1:52 p.m.
I installed F7t4 from the KDE live CD, my hardware profile is:
ebf36068-3809-426c-ade0-d0c531b5b402. Here are the results:
Desktop - everything works fine, except for kpowersave - it crashes, but
rpmverify kpowersave shows no problem. It worked fine from the CD and works
with the xen kernel (2.6.20, no .21 for xen), but after leaving the laptop on
for the night it was not responding.
Network - iwlwifi seemed to work untill it connected to the AP (wpa2) and
nothing more (no traffic, no ping). b44 worked fine (Ethernet).
X11's intel driver was used instead of i810 and worked fine, frozen-bubble
and ppracer are playable. There was no need to use 915resolution any more. The
same trick (change i810 to intel) does not work with FC6, after resume from
ram the display is black or with wrong colors and the mouse is not working.
With the live CD my mouse pad was a bit crazy - left was middle button
(which I don't have), up was right, down was left, right was nothing and
scrolling did not work (moving up/down on the right side of the pad). After
installing some more X packages (don't ask me which, many) it worked fine
(missing from the live KDE CD, some fonts too). Maybe kudzu did something at
some point...
Suspend to ram did not work with any kernel. In most cases, when the machine
(laptop - ACER aspire 5610) wakes up the disk led stays on and nothing more
happens. Just once, after suspending to ram the machine wakes up, but the
keyboard does nothing. I have no idea what's the problem, I was able
to see the kernel complaining about unknown keys once (volume,
brightness...), but no caps-lock/num-lock or anything else. The disk led is
constantly on.
Hybernation (suspend to disk) works if I kill iwlwifi.ko. I
created /etc/pm/hooks/11iwlwifi, which solved the problem:
--- cut ---
#!/bin/sh
exit 0
case "$1" in
hibernate|suspend)
/sbin/lsmod | grep -q iwlwifi || exit 0
{ touch /var/run/iwlwifi && /sbin/modprobe -r iwlwifi ; } \
2>/dev/null
;;
thaw|resume)
[ -f /var/run/iwlwifi ] || exit 0
{ /sbin/modprobe iwlwifi && rm -f /var/run/iwlwifi \
&& /sbin/service NetworkManager restart ; } 2>/dev/null
;;
*)
;;
esac
exit $?
--- cut ---
Have not tried ipw3945, but I guess it will work as it does in FC6.
After updating from kernel 2.6.20-1.3104.fc7 to 2.6.21-1.3116.fc7 the system
did not boot. I had to replace 'root=LABEL=/1' with
'root=/dev/VG0/LVroot1'
in grub.conf to get it working again. The label is really '/1', but it could
not find it. After installing 2.6.20-2925.5.fc7xen the new grub entry was
copied from my FC6 (root=/dev/VG0/LVroot instead of /dev/VG0/LVroot1), I have
FC6's grub chainloading F7's and F7's is on hda2 (sda2). Nothing else really
changed.
Should I fill bug reports for these?
--
Regards,
Doncho
1:59 p.m.
On 5/1/07, Doncho N. Gunchev <gunchev(a)gmail.com> wrote:
Network - iwlwifi seemed to work untill it connected to the AP
(wpa2)
and
nothing more (no traffic, no ping). b44 worked fine (Ethernet).
can you try the kernel from here:
http://people.redhat.com/davej/kernels/Fedora/fc7/RPMS.kernel/
iwlwifi works fine for me using this (and the previous one) the version in
the livecd does not even connet to my wpa/wpa2 ap.
but no everything seems to work with it, traffic, ping etc.
2:08 p.m.
On Tuesday 2007-05-01 21:59:38 dragoran dragoran wrote:
On 5/1/07, Doncho N. Gunchev <gunchev(a)gmail.com> wrote:
> Network - iwlwifi seemed to work untill it connected to the AP (wpa2)
> and
> nothing more (no traffic, no ping). b44 worked fine (Ethernet).
can you try the kernel from here:
http://people.redhat.com/davej/kernels/Fedora/fc7/RPMS.kernel/
iwlwifi works fine for me using this (and the previous one) the version in
the livecd does not even connet to my wpa/wpa2 ap.
but no everything seems to work with it, traffic, ping etc.
That's what I'm downloading now... kernel-2.6.21-1.3123.fc7.i686.rpm, thanks
for the link ;-)
--
Regards,
Doncho
7:38 a.m.
New subject: iwlwifi in kernel 2.6.21-1.3125 (was Re: F7t4 KDE live CD test report)
dragoran dragoran wrote:
can you try the kernel from here:
http://people.redhat.com/davej/kernels/Fedora/fc7/RPMS.kernel/
iwlwifi works fine for me using this (and the previous one) the
version in the livecd does not even connet to my wpa/wpa2 ap.
but no everything seems to work with it, traffic, ping etc.
The iwlwifi in the kernel from davej is much better, but all is not
sweetness and light, at least when running Network Manager. I have
attached my observations to this message, but they boil down to two things:
1/ Connection strengths don't seem to be correct.
2/ It is impossible to change wifi networks.
Peter F. Patel-Schneider
Problems with iwlwifi and NetworkManager in kernel 2.6.21-1.3125.fc7
1/ Connection strengths are all maximum.
I currently see three wifi networks. All are showing maximum
connection strength. Normally in my current location two would be
about 75% and one about 40%.
2/ Can't change wifi networks.
Connected to a WPA network, using Network Manager to switch to an open network:
May 2 08:00:19 localhost NetworkManager: <info> User Switch:
/org/freedesktop/NetworkManager/Devices/wlan0 / linksys
May 2 08:00:19 localhost NetworkManager: <info> Deactivating device wlan0.
May 2 08:00:19 localhost dhclient: wmaster0: unknown hardware address type 801
May 2 08:00:19 localhost dhclient: wmaster0: unknown hardware address type 801
May 2 08:00:19 localhost dhclient: DHCPRELEASE on wlan0 to 192.168.1.1 port 67
May 2 08:00:20 localhost wpa_supplicant[3582]: CTRL-EVENT-TERMINATING - signal 15
received
May 2 08:00:20 localhost avahi-daemon[2341]: Withdrawing address record for 192.168.1.7
on wlan0.
May 2 08:00:20 localhost avahi-daemon[2341]: Leaving mDNS multicast group on interface
wlan0.IPv4 with address 192.168.1.7.
May 2 08:00:20 localhost avahi-daemon[2341]: Interface wlan0.IPv4 no longer relevant for
mDNS.
May 2 08:00:20 localhost NetworkManager: <info> Device wlan0 activation
scheduled...
May 2 08:00:20 localhost NetworkManager: <info> Activation (wlan0) started...
May 2 08:00:20 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5
(Device Prepare) scheduled...
May 2 08:00:20 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5
(Device Prepare) started...
May 2 08:00:20 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5
(Device Configure) scheduled...
May 2 08:00:20 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5
(Device Prepare) complete.
May 2 08:00:20 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5
(Device Configure) starting...
May 2 08:00:20 localhost NetworkManager: <info> Activation (wlan0/wireless):
access point 'linksys' is unencrypted, no key needed.
May 2 08:00:20 localhost NetworkManager: <info> SUP: sending command
'INTERFACE_ADD wlan0 wext /var/run/wpa_supplicant '
May 2 08:00:20 localhost NetworkManager: <info> SUP: response was 'OK'
May 2 08:00:20 localhost NetworkManager: <info> SUP: sending command 'AP_SCAN
1'
May 2 08:00:20 localhost NetworkManager: <info> SUP: response was 'OK'
May 2 08:00:20 localhost NetworkManager: <info> SUP: sending command
'ADD_NETWORK'
May 2 08:00:20 localhost NetworkManager: <info> SUP: response was '0'
May 2 08:00:20 localhost NetworkManager: <info> SUP: sending command
'SET_NETWORK 0 ssid 6c696e6b737973'
May 2 08:00:20 localhost NetworkManager: <info> SUP: response was 'OK'
May 2 08:00:20 localhost NetworkManager: <info> SUP: sending command
'SET_NETWORK 0 key_mgmt NONE'
May 2 08:00:20 localhost NetworkManager: <info> SUP: response was 'OK'
May 2 08:00:20 localhost NetworkManager: <info> SUP: sending command
'ENABLE_NETWORK 0'
May 2 08:00:20 localhost NetworkManager: <info> SUP: response was 'OK'
May 2 08:00:20 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5
(Device Configure) complete.
May 2 08:00:21 localhost kernel: iwlwifi: check mac addr 1 | 1
May 2 08:00:21 localhost kernel: iwlwifi: check basic rate 2 | 1
May 2 08:00:21 localhost kernel: iwlwifi: check assoc id 3 | 1
May 2 08:00:21 localhost kernel: iwlwifi: check CCK and short slot 4 | 1
May 2 08:00:21 localhost kernel: iwlwifi: check CCK & auto detect 5 | 1
May 2 08:00:21 localhost kernel: iwlwifi: check TGG 6 | 1
May 2 08:00:21 localhost kernel: iwlwifi: check antenna 7 1
May 2 08:00:21 localhost kernel: iwlwifi: Tuning to channel 8
May 2 08:00:21 localhost kernel: iwlwifi: Error not a valid ipw_rxon_assoc_cmd field
values
May 2 08:00:21 localhost kernel: iwlwifi: Invalid RXON configuration. Not committing.
May 2 08:00:23 localhost kernel: iwlwifi: check mac addr 1 | 1
May 2 08:00:23 localhost kernel: iwlwifi: check basic rate 2 | 1
May 2 08:00:23 localhost kernel: iwlwifi: check assoc id 3 | 1
May 2 08:00:23 localhost kernel: iwlwifi: check CCK and short slot 4 | 1
May 2 08:00:23 localhost kernel: iwlwifi: check CCK & auto detect 5 | 1
May 2 08:00:23 localhost kernel: iwlwifi: check TGG 6 | 1
May 2 08:00:23 localhost kernel: iwlwifi: check antenna 7 1
May 2 08:00:23 localhost kernel: iwlwifi: Tuning to channel 8
May 2 08:00:23 localhost kernel: iwlwifi: Error not a valid ipw_rxon_assoc_cmd field
values
May 2 08:00:23 localhost kernel: iwlwifi: Invalid RXON configuration. Not committing.
May 2 08:00:28 localhost wpa_supplicant[3618]: Failed to initiate AP scan.
May 2 08:00:36 localhost wpa_supplicant[3618]: Failed to initiate AP scan.
May 2 08:00:40 localhost NetworkManager: <info> Activation (wlan0/wireless):
association took too long (>20s), failing activation.
May 2 08:00:40 localhost NetworkManager: <info> Activation (wlan0) failure
scheduled...
May 2 08:00:40 localhost NetworkManager: <info> Activation (wlan0) failed for
access point (linksys)
May 2 08:00:40 localhost NetworkManager: <info> Activation (wlan0) failed.
May 2 08:00:40 localhost NetworkManager: <info> Deactivating device wlan0.
May 2 08:00:40 localhost wpa_supplicant[3618]: CTRL-EVENT-TERMINATING - signal 15
received
No connection set up.
Attempting to connect back to the WPA network:
May 2 08:04:18 localhost NetworkManager: <info> User Switch:
/org/freedesktop/NetworkManager/Devices/wlan0 / L4ME1
May 2 08:04:18 localhost NetworkManager: <info> Deactivating device wlan0.
May 2 08:04:18 localhost NetworkManager: <info> Device wlan0 activation
scheduled...
May 2 08:04:18 localhost NetworkManager: <info> Activation (wlan0) started...
May 2 08:04:18 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5
(Device Prepare) scheduled...
May 2 08:04:18 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5
(Device Prepare) started...
May 2 08:04:18 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5
(Device Configure) scheduled...
May 2 08:04:18 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5
(Device Prepare) complete.
May 2 08:04:18 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5
(Device Configure) starting...
May 2 08:04:18 localhost NetworkManager: <info> Activation (wlan0/wireless):
access point 'L4ME1' is encrypted, but NO valid key exists. New key needed.
May 2 08:04:18 localhost NetworkManager: <info> Activation (wlan0) New wireless
user key requested for network 'L4ME1'.
May 2 08:04:18 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5
(Device Configure) complete.
May 2 08:04:18 localhost NetworkManager: <info> Activation (wlan0) New wireless
user key for network 'L4ME1' received.
May 2 08:04:18 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5
(Device Prepare) scheduled...
May 2 08:04:18 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5
(Device Prepare) started...
May 2 08:04:18 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5
(Device Configure) scheduled...
May 2 08:04:18 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5
(Device Prepare) complete.
May 2 08:04:18 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5
(Device Configure) starting...
May 2 08:04:18 localhost NetworkManager: <info> Activation (wlan0/wireless):
access point 'L4ME1' is encrypted, and a key exists. No new key needed.
May 2 08:04:18 localhost NetworkManager: <info> SUP: sending command
'INTERFACE_ADD wlan0 wext /var/run/wpa_supplicant '
May 2 08:04:18 localhost NetworkManager: <info> SUP: response was 'OK'
May 2 08:04:18 localhost NetworkManager: <info> SUP: sending command 'AP_SCAN
1'
May 2 08:04:18 localhost NetworkManager: <info> SUP: response was 'OK'
May 2 08:04:18 localhost NetworkManager: <info> SUP: sending command
'ADD_NETWORK'
May 2 08:04:18 localhost NetworkManager: <info> SUP: response was '0'
May 2 08:04:18 localhost NetworkManager: <info> SUP: sending command
'SET_NETWORK 0 ssid 4c344d4531'
May 2 08:04:18 localhost NetworkManager: <info> SUP: response was 'OK'
May 2 08:04:18 localhost NetworkManager: <info> SUP: sending command
'SET_NETWORK 0 proto WPA'
May 2 08:04:18 localhost NetworkManager: <info> SUP: response was 'OK'
May 2 08:04:18 localhost NetworkManager: <info> SUP: sending command
'SET_NETWORK 0 key_mgmt WPA-PSK'
May 2 08:04:18 localhost NetworkManager: <info> SUP: response was 'OK'
May 2 08:04:18 localhost NetworkManager: <info> SUP: sending command
'SET_NETWORK 0 psk <key>'
May 2 08:04:18 localhost NetworkManager: <info> SUP: response was 'OK'
May 2 08:04:18 localhost NetworkManager: <info> SUP: sending command
'ENABLE_NETWORK 0'
May 2 08:04:18 localhost NetworkManager: <info> SUP: response was 'OK'
May 2 08:04:18 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5
(Device Configure) complete.
May 2 08:04:19 localhost wpa_supplicant[3640]: Trying to associate with 00:18:01:e8:33:f9
(SSID='L4ME1' freq=2447 MHz)
May 2 08:04:19 localhost kernel: iwlwifi: REPLY_ADD_STA failed
May 2 08:04:19 localhost wpa_supplicant[3640]: Associated with 00:18:01:e8:33:f9
May 2 08:04:20 localhost kernel: hwcrypto disabled!
May 2 08:04:20 localhost wpa_supplicant[3640]: WPA: Key negotiation completed with
00:18:01:e8:33:f9 [PTK=TKIP GTK=TKIP]
May 2 08:04:20 localhost wpa_supplicant[3640]: CTRL-EVENT-CONNECTED - Connection to
00:18:01:e8:33:f9 completed (auth) [id=0 id_str=]
May 2 08:04:20 localhost NetworkManager: <info> Activation (wlan0/wireless) Stage
2 of 5 (Device Configure) successful. Connected to access point 'L4ME1'.
May 2 08:04:20 localhost NetworkManager: <info> Activation (wlan0) Stage 3 of 5
(IP Configure Start) scheduled.
May 2 08:04:20 localhost NetworkManager: <info> Activation (wlan0) Stage 3 of 5
(IP Configure Start) started...
May 2 08:04:20 localhost kernel: hwcrypto disabled!
May 2 08:04:21 localhost NetworkManager: <info> Activation (wlan0) Beginning DHCP
transaction.
May 2 08:04:21 localhost NetworkManager: <info> Activation (wlan0) Stage 3 of 5
(IP Configure Start) complete.
May 2 08:04:21 localhost NetworkManager: <info> DHCP daemon state is now 12
(successfully started) for interface wlan0
May 2 08:04:21 localhost dhclient: wmaster0: unknown hardware address type 801
May 2 08:04:21 localhost dhclient: wmaster0: unknown hardware address type 801
May 2 08:04:21 localhost NetworkManager: <info> DHCP daemon state is now 1
(starting) for interface wlan0
May 2 08:04:21 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67
interval 7
May 2 08:04:26 localhost dhclient: DHCPOFFER from 192.168.1.1
May 2 08:04:26 localhost dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
May 2 08:04:27 localhost dhclient: DHCPACK from 192.168.1.1
May 2 08:04:27 localhost dhclient: bound to 192.168.1.7 -- renewal in 40227 seconds.
May 2 08:04:27 localhost NetworkManager: <info> DHCP daemon state is now 2 (bound)
for interface wlan0
May 2 08:04:27 localhost NetworkManager: <info> Activation (wlan0) Stage 4 of 5
(IP Configure Get) scheduled...
May 2 08:04:27 localhost NetworkManager: <info> Activation (wlan0) Stage 4 of 5
(IP Configure Get) started...
May 2 08:04:27 localhost dhcdbd: message_handler: message handler not found under
/com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.nis_domain
May 2 08:04:27 localhost dhcdbd: message_handler: message handler not found under
/com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.nis_servers
May 2 08:04:27 localhost NetworkManager: <info> Retrieved the following IP4
configuration from the DHCP daemon:
May 2 08:04:27 localhost NetworkManager: <info> address 192.168.1.7
May 2 08:04:27 localhost NetworkManager: <info> netmask 255.255.255.0
May 2 08:04:27 localhost NetworkManager: <info> broadcast 192.168.1.255
May 2 08:04:27 localhost NetworkManager: <info> gateway 192.168.1.1
May 2 08:04:27 localhost NetworkManager: <info> nameserver 192.168.1.1
May 2 08:04:27 localhost NetworkManager: <info> hostname 'idefix'
May 2 08:04:27 localhost NetworkManager: <info> domain name 'home'
May 2 08:04:27 localhost NetworkManager: <info> Activation (wlan0) Stage 5 of 5
(IP Configure Commit) scheduled...
May 2 08:04:27 localhost NetworkManager: <info> Activation (wlan0) Stage 4 of 5
(IP Configure Get) complete.
May 2 08:04:27 localhost NetworkManager: <info> Activation (wlan0) Stage 5 of 5
(IP Configure Commit) started...
May 2 08:04:27 localhost avahi-daemon[2341]: Joining mDNS multicast group on interface
wlan0.IPv4 with address 192.168.1.7.
May 2 08:04:27 localhost avahi-daemon[2341]: New relevant interface wlan0.IPv4 for mDNS.
May 2 08:04:27 localhost avahi-daemon[2341]: Registering new address record for
192.168.1.7 on wlan0.IPv4.
May 2 08:04:28 localhost NetworkManager: <info> Activation (wlan0) successful,
device activated.
May 2 08:04:28 localhost NetworkManager: <info> Activation (wlan0) Finish handler
scheduled.
May 2 08:04:28 localhost NetworkManager: <info> Activation (wlan0) Stage 5 of 5
(IP Configure Commit) complete.
Sucess.
It appears that any attempt to switch to a different wireless network
will fail, but that switching to a wired network and then back to the
same wireless network does work.
7:48 a.m.
New subject: iwlwifi in kernel 2.6.21-1.3125 (was Re: F7t4 KDE live CD test report)
Peter F. Patel-Schneider wrote:
dragoran dragoran wrote:
>
> can you try the kernel from here:
> http://people.redhat.com/davej/kernels/Fedora/fc7/RPMS.kernel/
> iwlwifi works fine for me using this (and the previous one) the
> version in the livecd does not even connet to my wpa/wpa2 ap.
> but no everything seems to work with it, traffic, ping etc.
>
The iwlwifi in the kernel from davej is much better, but all is not
sweetness and light, at least when running Network Manager. I have
attached my observations to this message, but they boil down to two
things:
1/ Connection strengths don't seem to be correct.
noticed this too:
http://marc.info/?l=linux-wireless&m=117809490027074&w=2
2/ It is impossible to change wifi networks.
only with nm (have not tested it yet;lack of aps...) or also when you do
it by hand (wpa_supplicant or iwconfig for unencrypted aps) ?
and please file a bug with the description you wrote
8:54 a.m.
New subject: iwlwifi in kernel 2.6.21-1.3125 (was Re: F7t4 KDE live CD test report)
> 2/ It is impossible to change wifi networks.
>
only with nm (have not tested it yet;lack of aps...) or also when you
do it by hand (wpa_supplicant or iwconfig for unencrypted aps) ?
and please file a bug with the description you wrote
How would I change networks without nm?
peter
2:13 p.m.
On Tuesday 2007-05-01 21:52:04 you wrote:
I installed F7t4 from the KDE live CD, my hardware profile is:
ebf36068-3809-426c-ade0-d0c531b5b402. Here are the results:
...
Suspend to ram did not work with any kernel. In most cases, when
the
...
I think it has something to do with the new IDE /should I say SCSI ;-)/ disk
driver. It complains that something is not supported...
OT: Now, when hdparm -d 0/1 does nothing, how can I switch DMA on/off for my
DVD-Writer and hard disk?
--
Regards,
Doncho
3:21 p.m.
On 5/1/07, Doncho N. Gunchev <gunchev(a)gmail.com> wrote:
On Tuesday 2007-05-01 21:52:04 you wrote:
> I installed F7t4 from the KDE live CD, my hardware profile is:
> ebf36068-3809-426c-ade0-d0c531b5b402. Here are the results:
...
> Suspend to ram did not work with any kernel. In most cases, when the
...
I think it has something to do with the new IDE /should I say SCSI ;-)/
disk
driver. It complains that something is not supported...
OT: Now, when hdparm -d 0/1 does nothing, how can I switch DMA on/off for
my
DVD-Writer and hard disk?
there is no reason to turn it off the new driver should select and set the
best dma mode that your drive/chipset supports; if not its a bug.
--
Regards,
Doncho
--
fedora-test-list mailing list
fedora-test-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
4:07 p.m.
On Tuesday 2007-05-01 23:21:53 dragoran dragoran wrote:
On 5/1/07, Doncho N. Gunchev <gunchev(a)gmail.com> wrote:
> On Tuesday 2007-05-01 21:52:04 you wrote:
> > I installed F7t4 from the KDE live CD, my hardware profile is:
> > ebf36068-3809-426c-ade0-d0c531b5b402. Here are the results:
>
> ...
>
> > Suspend to ram did not work with any kernel. In most cases, when the
>
> ...
> I think it has something to do with the new IDE /should I say SCSI ;-)/
> disk
> driver. It complains that something is not supported...
>
> OT: Now, when hdparm -d 0/1 does nothing, how can I switch DMA on/off for
> my
> DVD-Writer and hard disk?
there is no reason to turn it off the new driver should select and set the
best dma mode that your drive/chipset supports; if not its a bug.
I know it should (remember when these settings got removed from
/etc/sysconfig/*?), that's why I asked 'how?'. My DVD-Writer seems
to not use any DMA at all (~1MB/sec vs >4MB/sec in FC6). How do
I know if it uses "the best mode", if I can't try any other?
--
Regards,
Doncho
4:16 p.m.
On 5/1/07, Doncho N. Gunchev <gunchev(a)gmail.com> wrote:
On Tuesday 2007-05-01 23:21:53 dragoran dragoran wrote:
> On 5/1/07, Doncho N. Gunchev <gunchev(a)gmail.com> wrote:
> > On Tuesday 2007-05-01 21:52:04 you wrote:
> > > I installed F7t4 from the KDE live CD, my hardware profile is:
> > > ebf36068-3809-426c-ade0-d0c531b5b402. Here are the results:
> >
> > ...
> >
> > > Suspend to ram did not work with any kernel. In most cases, when
the
> >
> > ...
> > I think it has something to do with the new IDE /should I say SCSI
;-)/
> > disk
> > driver. It complains that something is not supported...
> >
> > OT: Now, when hdparm -d 0/1 does nothing, how can I switch DMA on/off
for
> > my
> > DVD-Writer and hard disk?
>
> there is no reason to turn it off the new driver should select and set
the
> best dma mode that your drive/chipset supports; if not its a bug.
>
I know it should (remember when these settings got removed from
/etc/sysconfig/*?), that's why I asked 'how?'. My DVD-Writer seems
to not use any DMA at all (~1MB/sec vs >4MB/sec in FC6). How do
I know if it uses "the best mode", if I can't try any other?
its simple a higher dma mode means higher speed.
what does hdparm -i /dev/yourdevice show?
(both fc6 and f7 output) ?
--
Regards,
Doncho
--
fedora-test-list mailing list
fedora-test-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
5:24 p.m.
New subject: How to turn on/off DMA
On Wednesday 2007-05-02 00:16:37 dragoran dragoran wrote:
On 5/1/07, Doncho N. Gunchev <gunchev(a)gmail.com> wrote:
> On Tuesday 2007-05-01 23:21:53 dragoran dragoran wrote:
> > On 5/1/07, Doncho N. Gunchev <gunchev(a)gmail.com> wrote:
> > > On Tuesday 2007-05-01 21:52:04 you wrote:
> > > > I installed F7t4 from the KDE live CD, my hardware profile is:
> > > > ebf36068-3809-426c-ade0-d0c531b5b402. Here are the results:
...
> > > OT: Now, when hdparm -d 0/1 does nothing, how can I
switch DMA on/off
>
> for
>
> > > my
> > > DVD-Writer and hard disk?
> >
> > there is no reason to turn it off the new driver should select and set
>
> the
>
> > best dma mode that your drive/chipset supports; if not its a bug.
>
> I know it should (remember when these settings got removed from
> /etc/sysconfig/*?), that's why I asked 'how?'. My DVD-Writer seems
> to not use any DMA at all (~1MB/sec vs >4MB/sec in FC6). How do
> I know if it uses "the best mode", if I can't try any other?
its simple a higher dma mode means higher speed.
what does hdparm -i /dev/yourdevice show?
(both fc6 and f7 output) ?
What was not clear in my question, I asked how do I do turn DMA on/off with
the new kernels, not why I should not do this? Is there a reason to keep this
secret?
Here's the info for my DVD-Writer, it has DMA off in FC6 and I'm turning it on
in rc.local to get it working faster. I also have to 'killall
hald-addon-storage' (or more specificly, the one that monitors my DVD) or the
machine (laptop) will die in a few hours (does not matter if I have DMA on,
off or if I try to play with /usr/share/hal/fdi/policy/10osvendor/*.fdi.
Haven't seen it locking for this reason with F7t4 yet.
--- Fedora Core 6 ---
# hdparm -i /dev/hdb
/dev/hdb:
Model=TSSTcorpCD/DVDW TS-L632D, FwRev=AC01, SerialNo=
Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
BuffType=unknown, BuffSize=0kB, MaxMultSect=0
(maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
IORDY=on/off, tPIO={min:227,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 *udma2
AdvancedPM=no
* signifies the current active mode
# hdparm /dev/hdb
/dev/hdb:
IO_support = 0 (default 16-bit)
unmaskirq = 0 (off)
using_dma = 0 (off)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 256 (on)
HDIO_GETGEO failed: Inappropriate ioctl for device
*** There is a difference when hdparm /dev/hdb shows DMA on - when I watch DVD
movie it works (and the time taken by the kernel while reading the DVD drops
down), when off - it skips frames and looses a/v sync.
--- Fedora 7 test 4 ---
# ll /dev/dvdrw
lrwxrwxrwx 1 root root 4 2 май 0,56 /dev/dvdrw -> scd0
# hdparm -i /dev/scd0
/dev/scd0:
Model=TSSTcorpCD/DVDW TS-L632D , FwRev=AC01 , SerialNo=
Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
BuffType=unknown, BuffSize=0kB, MaxMultSect=0
(maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
IORDY=on/off, tPIO={min:227,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 *udma2
AdvancedPM=no
* signifies the current active mode
# hdparm /dev/scd0
/dev/scd0:
IO_support = 0 (default 16-bit)
readonly = 0 (off)
readahead = 256 (on)
HDIO_GETGEO failed: Inappropriate ioctl for device
--
Regards,
Doncho
7:55 a.m.
New subject: How to turn on/off DMA
Doncho N. Gunchev wrote:
What was not clear in my question, I asked how do I do turn DMA
on/off with
the new kernels, not why I should not do this? Is there a reason to keep this
secret?
I don't know the exact reason; but its as simple as "there is no need
to" (libata never allowed this; so it was always the case for sata drives)
Here's the info for my DVD-Writer, it has DMA off in FC6 and
I'm turning it on
in rc.local to get it working faster.
which is a bug, please fill one (kernel)...
I also have to 'killall
hald-addon-storage' (or more specificly, the one that monitors my DVD) or the
machine (laptop) will die in a few hours (does not matter if I have DMA on,
off or if I try to play with /usr/share/hal/fdi/policy/10osvendor/*.fdi.
also a bug fill it against hal
Haven't seen it locking for this reason with F7t4 yet.
--- Fedora Core 6 ---
# hdparm -i /dev/hdb
/dev/hdb:
Model=TSSTcorpCD/DVDW TS-L632D, FwRev=AC01, SerialNo=
Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
BuffType=unknown, BuffSize=0kB, MaxMultSect=0
(maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
IORDY=on/off, tPIO={min:227,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 *udma2
AdvancedPM=no
* signifies the current active mode
# hdparm /dev/hdb
/dev/hdb:
IO_support = 0 (default 16-bit)
unmaskirq = 0 (off)
using_dma = 0 (off)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 256 (on)
HDIO_GETGEO failed: Inappropriate ioctl for device
*** There is a difference when hdparm /dev/hdb shows DMA on - when I watch DVD
movie it works (and the time taken by the kernel while reading the DVD drops
down), when off - it skips frames and looses a/v sync.
I know that there is a difference between dma on and off ;)
--- Fedora 7 test 4 ---
# ll /dev/dvdrw
lrwxrwxrwx 1 root root 4 2 май 0,56 /dev/dvdrw -> scd0
# hdparm -i /dev/scd0
/dev/scd0:
Model=TSSTcorpCD/DVDW TS-L632D , FwRev=AC01 , SerialNo=
Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
BuffType=unknown, BuffSize=0kB, MaxMultSect=0
(maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
IORDY=on/off, tPIO={min:227,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 *udma2
AdvancedPM=no
* signifies the current active mode
this seems correct (udma33)
# hdparm /dev/scd0
/dev/scd0:
IO_support = 0 (default 16-bit)
readonly = 0 (off)
readahead = 256 (on)
HDIO_GETGEO failed: Inappropriate ioctl for device
ok hdparm seems not to report the dma flag here.... tested on my box and
it seems that it does not do it for harddisks either (SATA)
but again if the kernel does not enable the dmamode for you _its a bug_
so please file one against kernel (one for fc6 and one for f7)
8:27 a.m.
New subject: How to turn on/off DMA
On Wednesday 2007-05-02 15:55:50 dragoran wrote:
Doncho N. Gunchev wrote:
> What was not clear in my question, I asked how do I do turn DMA on/off with
> the new kernels, not why I should not do this? Is there a reason to keep this
> secret?
>
I don't know the exact reason; but its as simple as "there is no need
to" (libata never allowed this; so it was always the case for sata drives)
Ok, so there's no way... Thanks. From http://freshmeat.net/projects/hdparm/ :
"""
is hdparm useful with sata drives, does
it work with sata drives?
SATA drives in the 2.6 kernel are handled by the new
"libata" SCSI driver. If
you add the "ATA passthru" patch (from Jeff Garzik) to your kernel, then
hdparm can work with those drives.
Some flags, like "-d", are not supported by libata. Currently, ALL SATA hard
drives use DMA, so there is no need for -d. But eventually libata will have to
implement ATA PIO (for CF cards..), and at that time it may (or not) begin to
support the "-d" flag.
"""
> Here's the info for my DVD-Writer, it has DMA off in FC6 and
I'm turning it on
> in rc.local to get it working faster.
which is a bug, please fill one (kernel)...
> I also have to 'killall
> hald-addon-storage' (or more specificly, the one that monitors my DVD) or the
> machine (laptop) will die in a few hours (does not matter if I have DMA on,
> off or if I try to play with /usr/share/hal/fdi/policy/10osvendor/*.fdi.
>
also a bug fill it against hal
> Haven't seen it locking for this reason with F7t4 yet.
> --- Fedora Core 6 ---
> # hdparm -i /dev/hdb
>
> /dev/hdb:
>
> Model=TSSTcorpCD/DVDW TS-L632D, FwRev=AC01, SerialNo=
> Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
> RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
> BuffType=unknown, BuffSize=0kB, MaxMultSect=0
> (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
> IORDY=on/off, tPIO={min:227,w/IORDY:120}, tDMA={min:120,rec:120}
> PIO modes: pio0 pio1 pio2 pio3 pio4
> DMA modes: mdma0 mdma1 mdma2
> UDMA modes: udma0 udma1 *udma2
> AdvancedPM=no
>
> * signifies the current active mode
>
> # hdparm /dev/hdb
>
> /dev/hdb:
> IO_support = 0 (default 16-bit)
> unmaskirq = 0 (off)
> using_dma = 0 (off)
> keepsettings = 0 (off)
> readonly = 0 (off)
> readahead = 256 (on)
> HDIO_GETGEO failed: Inappropriate ioctl for device
>
> *** There is a difference when hdparm /dev/hdb shows DMA on - when I watch DVD
> movie it works (and the time taken by the kernel while reading the DVD drops
> down), when off - it skips frames and looses a/v sync.
>
I know that there is a difference between dma on and off ;)
> --- Fedora 7 test 4 ---
> # ll /dev/dvdrw
> lrwxrwxrwx 1 root root 4 2 май 0,56 /dev/dvdrw -> scd0
> # hdparm -i /dev/scd0
>
> /dev/scd0:
>
> Model=TSSTcorpCD/DVDW TS-L632D , FwRev=AC01 , SerialNo=
> Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
> RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
> BuffType=unknown, BuffSize=0kB, MaxMultSect=0
> (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
> IORDY=on/off, tPIO={min:227,w/IORDY:120}, tDMA={min:120,rec:120}
> PIO modes: pio0 pio1 pio2 pio3 pio4
> DMA modes: mdma0 mdma1 mdma2
> UDMA modes: udma0 udma1 *udma2
> AdvancedPM=no
>
> * signifies the current active mode
>
>
this seems correct (udma33)
> # hdparm /dev/scd0
>
> /dev/scd0:
> IO_support = 0 (default 16-bit)
> readonly = 0 (off)
> readahead = 256 (on)
> HDIO_GETGEO failed: Inappropriate ioctl for device
>
>
ok hdparm seems not to report the dma flag here.... tested on my box and
it seems that it does not do it for harddisks either (SATA)
but again if the kernel does not enable the dmamode for you _its a bug_
so please file one against kernel (one for fc6 and one for f7)
Yep, it reports that DMA is used even when it is not. I will fill the bug reports
tonight, after work. I didn't fill a bug report for FC6's kernel because there
were
enough of this type at that time and there was something about changing the
way hal pulls data from the CD...
Thanks.
--
Regards,
Doncho
6236
days inactive
6237
days old
12 comments
3 participants
participants (3)
-
Doncho N. Gunchev -
drago01 -
Peter F. Patel-Schneider