Bug#614326: Pegasus adapter didn't work for me

2011-06-08 Thread Ken Yee
FYI, looks like the Pegasus driver also has issues.
I'm running the latest Debian 2.6.39-1 kernel w/ the latest sid updates.  No 
luck.  Apparently, the udev updates have broken all the usb/ethernet adapters 
:-P


kenyee@JumpGate:/etc/network/if-pre-up.d$ ethtool -i eth1
driver: pegasus
version: v0.6.14 (2006/09/27)
firmware-version: 
bus-info: usb-:00:12.0-1
supports-statistics: no
supports-test: no
supports-eeprom-access: no
supports-register-dump: no

ifconfig -a
eth1  Link encap:Ethernet  HWaddr 00:00:00:00:00:00  
  BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
`



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110608204412.32...@web008.roc2.bluetie.com



Bug#614326: Pegasus adapter didn't work for me

2011-06-08 Thread Ken Yee
 udev deals with auto-loading modules and maintaining network interface
 names. And it's clearly done that correctly, so I don't see any reason
 to blame it.

Good point.  Not sure what else would have gotten updated via a dist-upgrade 
that would have broken the asix driver then :-P
The pegasus driver is also broken even worse for me unfortunately.  At least 
the asix driver reports a mac address...
---BeginMessage---
On Wed, 2011-06-08 at 20:44 -0400, Ken Yee wrote:
 FYI, looks like the Pegasus driver also has issues.
 I'm running the latest Debian 2.6.39-1 kernel w/ the latest sid
 updates.  No luck.  Apparently, the udev updates have broken all the
 usb/ethernet adapters :-P
[]

udev deals with auto-loading modules and maintaining network interface
names.  And it's clearly done that correctly, so I don't see any reason
to blame it.

Ben.

-- 
Ben Hutchings
Lowery's Law:
 If it jams, force it. If it breaks, it needed replacing anyway.


signature.asc
Description: This is a digitally signed message part
---End Message---


Bug#614326: bug still appears in 2.6.38-2

2011-04-18 Thread Ken Yee
Tried plain Debian 2.38.3 kernel.
Also tried Liquorix 2.38.3 kernel since people seem to like it for better 
hardware support.
Same queue timeout error :-(



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110418230933.5...@web008.roc2.bluetie.com



Bug#614326: bug still appears in 2.6.38-2

2011-04-04 Thread Ken Yee
FYI, bug still happens with the latest 2.6.38.-2 kernel, so it definitely 
doesn't seem kernel related:

[  150.720026] [ cut here ]
[  150.720040] WARNING: at 
/tmp/buildd/linux-aptosid-2.6-2.6.38/debian/build/source_amd64_none/net/sched/sch_generic.c:256
 dev_watchdog+0x25b/0x270()
[  150.720043] Hardware name: System Product Name
[  150.720046] NETDEV WATCHDOG: eth1 (asix): transmit queue 0 timed out
[  150.720048] Modules linked in: vboxnetadp vboxnetflt nf_nat_irc 
nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp ppdev lp ipt_REJECT ipt_ULOG 
xt_limit xt_state ipt_REDIRECT xt_tcpudp iptable_nat nf_nat nf_conntrack_ipv4 
nf_conntrack sco nf_defrag_ipv4 bnep rfcomm l2cap crc16 bluetooth rfkill ipx 
p8023 iptable_filter ip_tables x_tables capifs ntfs nls_utf8 nls_cp437 vfat fat 
ext3 jbd mbcache xfs exportfs vboxdrv psmouse powernow_k8 freq_table mperf 
hwmon_vid eeprom fuse dm_crypt snd_hda_codec_hdmi snd_hda_codec_realtek 
lgdt330x snd_hda_intel cx88_dvb cx88_vp3054_i2c videobuf_dvb dvb_core radeon 
ir_kbd_i2c rtc_isl1208 snd_hda_codec tuner_simple tuner_types snd_seq_dummy 
snd_hwdep sp5100_tco snd_pcm_oss snd_mixer_oss snd_seq_oss tda9887 tda8290 
tuner snd_seq_midi ttm asix ir_lirc_codec lirc_dev ir_sony_decoder 
ir_jvc_decoder ir_rc6_decoder cx88_alsa cx8802 ir_rc5_decoder cx8800 
ir_nec_decoder cx88xx rc_core snd_rawmidi tveeprom snd_seq_midi_event snd_pcm 
drm_kms_helper i2c_piix4 usbnet v4l2_common snd_seq videodev 
v4l2_compat_ioctl32 videobuf_dma_sg tpm_tis drm tpm i2c_algo_bit btcx_risc 
videobuf_core i2c_core shpchp pci_hotplug tpm_bios amd64_edac_mod edac_core 
pcspkr k8temp edac_mce_amd evdev snd_timer snd_seq_device rtc_cmos snd rtc_core 
rtc_lib asus_atk0110 soundcore snd_page_alloc parport_pc wmi button parport 
processor reiserfs raid1 md_mod dm_mirror dm_region_hash dm_log dm_mod sg 
sr_mod cdrom sd_mod usbhid crc_t10dif hid ata_generic ahci r8169 pata_acpi 
ohci_hcd ssb ehci_hcd libahci firewire_ohci usbcore mii mmc_core pata_atiixp 
pcmcia libata firewire_core crc_itu_t floppy scsi_mod pcmcia_core nls_base 
[last unloaded: scsi_wait_scan]
[  150.720170] Pid: 0, comm: kworker/0:0 Not tainted 
2.6.38-2.slh.2-aptosid-amd64 #1
[  150.720173] Call Trace:
[  150.720175]  IRQ  [81051b4b] ? warn_slowpath_common+0x7b/0xc0
[  150.720185]  [81051c45] ? warn_slowpath_fmt+0x45/0x50
[  150.720190]  [811dc22f] ? strlcpy+0x3f/0x50
[  150.720194]  [812ee79b] ? dev_watchdog+0x25b/0x270
[  150.720197]  [81047c53] ? get_nohz_timer_target+0x53/0xa0
[  150.720202]  [8105e7e0] ? mod_timer+0x130/0x220
[  150.720206]  [8105dfc0] ? run_timer_softirq+0x130/0x250
[  150.720209]  [812ee540] ? dev_watchdog+0x0/0x270
[  150.720212]  [81057c18] ? __do_softirq+0x98/0x120
[  150.720217]  [8100ccdc] ? call_softirq+0x1c/0x30
[  150.720220]  [8100eef5] ? do_softirq+0x65/0xa0
[  150.720223]  [81057d95] ? irq_exit+0x95/0xa0
[  150.720228]  [81027c2a] ? smp_apic_timer_interrupt+0x6a/0xa0
[  150.720231]  [8100c793] ? apic_timer_interrupt+0x13/0x20
[  150.720233]  EOI  [8102fd82] ? native_safe_halt+0x2/0x10
[  150.720242]  [8107314c] ? __atomic_notifier_call_chain+0x4c/0x70
[  150.720246]  [81015013] ? default_idle+0x23/0x40
[  150.720248]  [81015084] ? c1e_idle+0x54/0x110
[  150.720253]  [8100a1e6] ? cpu_idle+0x56/0xa0
[  150.720256] ---[ end trace a5ad661b39f55810 ]---



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110404081608.16...@web013.roc2.bluetie.com



Bug#614326: bug still appears in 2.6.37-2

2011-03-05 Thread Ken Yee
Noticed this bug was marked as not in 2.6.37-1.  FWIW, it's still in 2.6.37-2 
and the latest dist-upgrade from today (5 Mar 2011) doesn't fix it.

What's interesting is that this doesn't seem to be dependent on kernel version, 
even though the asix driver is part of the kernel.

I've also tried another usb adapter...the Monoprice Gigabit one.  It doesn't 
log any errors, but you can't transfer packets outside the machine or into the 
machine from that interface.  However, in VirtualBox, you can ping the VM from 
that interface and vice-versa (the host machine and the VM both have two 
interfaces).  This behavior doesn't makes sense to me...it's like the physical 
layer doesn't work for that interface bug Linux understands how to short 
circuit packets that stay on the same machine? :-P

.



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110305170256.19...@web009.roc2.bluetie.com



Bug#293508: possible solution to LVM module checking for LVM2

2006-02-26 Thread Ken Yee

For the mkinitrd script, a solution for the LVM2 module checking (assuming you 
have LVM2 built into your kernel instead) is:

   elif module_exists drivers/md/dm-mod; then

---

   elif module_exists drivers/md/dm-mod \

 || [ -d /lib/lvm-200 ]; then



i.e., check for the existence of the LVM2 module or the lvm-200 directory.



That said, I ended up using the lvm2create_initrd script w/ a bunch of changes 
instead.



yaird might be a better option since it generates an initramfs image that 
supports LVM on RAID so hopefully mkinitrd will be retired soon...



___
Join Excite! - http://www.excite.com
The most personalized portal on the Web!




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#293508: bug still in 2.6.14

2006-02-18 Thread Ken Yee

FYI, this bug is still in 2.6.14 (I'm using Kanotix 2005-04 amd64).



The basic problem is mkinitrd fails to detect modules that are built-into the 
kernel.  The script seems to looks for loadable modules instead.  It needs code 
to detect modules compiled into the kernel.



There are workarounds on this page to get mkinitrd to work:

http://pigeon.dyndns.org/stuff/lvm-root/lvm-root.html

Or you can just unzip this file and use it instead of mkinitrd:

/usr/share/doc/lvm2/examples/lvm2create_initrd.gz









___
Join Excite! - http://www.excite.com
The most personalized portal on the Web!




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]