[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#724931: Please include the patch in git



Hi,

On 13.10.2013 10:21, ian_bruce@fastmail.net wrote:
I'm not done with this yet. I'm working on a more general patch with new
features, which will be forthcoming shortly. I would ask that nothing
major be done until that is ready.
I'm curious, what features do you want to add?

"loopback" is the name of a virtual network device; the proper term in
this context is in fact "loopmount", hence the name of the boot
parameter.
Yes, loopback is the lo network interface, but for some reason I don't understand, GRUB uses the term loopback for booting from an ISO:
https://www.gnu.org/software/grub/manual/grub.html#Loopback-booting
This is why I constantly get confused between loopback and (the more descriptive) loopmount.

If the boot parameter is not given (or no ISO could be found),
everything works essentially as before.

As far as I know, if the "loopmount" parameter is not specified, then
everything works EXACTLY as before (by design).
In my latest patch, some changes are effective, even if loopmount is not used, e.g.: * I cleared up the workaround for bug #608201, so that in the future it should not be necessary to change apt-cdrom-setup, if one adds a new booting method. * Since I included more filesystem drivers in the initrd, I changed the code so that USB-HDD also works from filesystems other than FAT. * I also exported the boot options from cdrom-detect and imported them in several places, instead of determining the again. This should not have any effect, if loopmount is not used, but if it is, the 'loop' option is used. If in the future some changes are made with the boot options in cdrom-detect, they will be respected by apt-cdrom-setup.

It appears that the ext4 module would be sufficient to also mount
ext2/ext3, whereas the reverse would not be true.
I just tested loopmounting from an ext2 filesystem, while only the ext4 filesystem driver was in the initrd: It worked, blkid identified it as ext4 and mounting as such only gave an info message: kernel: [ 13.170123] EXT4-fs (sdb1): mounted filesystem without journal. Opts: (null) And according to Ben there will be no ext2/ext3 modules in the kernel starting with 3.11. So just add the ext4 module.

I don't know what usage UDF gets (besides DVDs) that would justify
including it in the initrd.
I have to admit, that I didn't know more than that a month ago.

(Fat is somewhat outdated.)

VFAT is by no means outdated, since it is used on almost every USB
flashdrive in existence. You might expect that it would eventually be
replaced for this purpose by F2FS, but that certainly hasn't happened
yet.
FAT32 is no modern filesystem, since it doesn't support files larger than 4 GB, e.g. the debian-7.1.0-amd64-DVD-2.iso with 4.7 GB. The reason for it to be still widespread is, that it is supported by (nearly?) all operating systems. While F2FS might be modern and optimized for flash drives, it is only supported in Linux and thus cannot replace FAT32. UDF on the other hand is used for DVDs and most operating systems can read (and even write to) it. Furthermore it supports large files and thus is the most probable replacement for FAT32. For further explanation see:
http://duncanlock.net/blog/2013/05/13/using-udf-as-an-improved-filesystem-for-usb-flash-drives/
Already, some USB sticks sold are formatted with UDF.
So I recommend to add UDF support now, although it will probably not be relevant for the broad audience until several years have passed by.

The patch also cleans up the somewhat messy workaround for bug
#608201.

A proper fix would be for all ISO images to be treated the same,
regardless of whether they were contained in a CD, a disk partition, or
a loop-mounted file. I'm not sure why this shouldn't be possible, but
it's not the issue we're mainly concerned with at the moment.
In fact, with my patch, they are treated practically the same, with the one exception of CD set support, which is only available for actual disks in a drive and loopmounted ISOs. It is probably possible to extend this support to isohybrid and USB-HDD, but it is assumed, that one does not want to use multiple USB sticks to install Debian.

For ease of use, I propose to add a loopback.cfg similar to the the
attached one to the ISO in the folder /boot/grub/. This would allow to
easily mount the ISO using grub2.

I can supply similar config files for Syslinux, allowing the use of the
original boot menus with a loop-mounted ISO.
That would be great.

As I have suggested previously, you don't actually have to modify the
ISOs for testing; you can just patch an external copy of the initrd and
boot with that. That way, the official MD5 and SHA256 hashes still
verify.
The problem is, that I also have to modify the apt-cdrom-setup.udeb, that is not in the initrd, but gets loaded afterwards from /pool/main/a/apt-setup.

* CD: I can't open the CD drive with the button the on the drive. I
have to change to another TTY and use 'eject'. (This problem exists
also with the original ISO image, see #726137.)

I think I also ran into this at some point.
Perhaps you could drop this info at bug #726137 for confirmation of the problem.

Since the patch works well and does no harm, I ask you to include it
in git.

I think this will be a highly useful feature, and may become the primary
method of booting Debian. (Does anybody really bother burning install
CDs anymore?)
I agree fully.

However, as I said above, I'm still working on some improvements, so
it's not quite done yet.
I would be glad for any improvements, though it already works quite well.

* The script mountmedia uses 'mount -t auto', but this only tries to
mount as fat and nothing else, so I changed this to detect the
filesystem with blkid. Now firmware can be loaded from a harddrive/USB
with any of the filesystems, for which drivers are in the initrd.

That's what "mount -t auto" is supposed to do. From the manual page:

     If no -t option is given, or if the auto type is specified, mount
     will try to guess the desired type. Mount uses the blkid library for
     guessing the filesystem type; if that does not turn up anything that
     looks familiar, mount will try to read the file /etc/filesystems,
     or, if that does not exist, /proc/filesystems.

So I don't know why using /sbin/blkid directly would make any
difference. Maybe there's some peculiarity about the Busybox version of
"mount".
I also don't know why '-tauto' does not work.
With 'mount $1 -tauto $MNT' it gives a lot of the following warnings:
UDF-fs: warning (device sdc1): udf_fill_super: No partition found (1)
FAT-fs (sdc1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
And it does not actually load the firmware.
With 'mount -t $fs_type $1 $MNT' and $fs_type determined with blkid it just works (see attached syslogs).

* Removed $FATFS from cdrom-detect and instead let the filesystem be
automatically detected using blkid. With this it is possible to use
USB-HDD for all filesystems, for which drivers are in the initrd.

For the reasons given above, I'm not very confident about this. I think
it's better to specify the relevant filesystem types directly.

"mount -t vfat,ext4,iso9660" actually works; I suggest we just add ntfs
or whatever seems desirable to that list.
Sorry, I must have missed your reasoning for why specifying the supported filesystems directly is better. I think you only wrote it would be 'easy enough' to give the filesystems by hand. But, as I said, it is easier not having to change the source code for every driver added to or removed from the initrd. And I can see no drawbacks in that. Furthermore, in my opinion, there should be as little as possible differences between the used kernel (Linux/kFreeBSD/Hurd), but these have different names for the filesystems. So I think it is best to let blkid determine the right filesystem and leave the rest independent of the used kernel.

Best regards,
Andreas
Oct 13 16:10:22 check-missing-firmware: Check on /loop for firmware
Oct 13 16:10:23 kernel: [   77.902355] NTFS volume version 3.1.
Oct 13 16:10:23 kernel: [   78.091080] NTFS volume version 3.1.
Oct 13 16:10:24 kernel: [   78.568302] NTFS volume version 3.1.
Oct 13 16:10:24 kernel: [   78.757029] NTFS volume version 3.1.
Oct 13 16:10:24 main-menu[535]: (process:4536): mount: can't find /media in /etc/fstab
Oct 13 16:10:24 main-menu[535]: (process:4536): umount: can't umount /media: Invalid argument
Oct 13 16:10:24 main-menu[535]: (process:4536): mount: can't find /media in /etc/fstab
[...]
Oct 13 16:10:24 main-menu[535]: (process:4536): umount: can't umount /media: Invalid argument
Oct 13 16:10:24 main-menu[535]: (process:4536): mount: can't find /media in /etc/fstab
Oct 13 16:10:24 main-menu[535]: (process:4536): mount: mounting 
Oct 13 16:10:24 kernel: [   78.963760] EXT4-fs (sda11): mounted filesystem with ordered data mode. Opts: (null)
Oct 13 16:10:24 kernel: [   79.023219] EXT4-fs (sda11): mounted filesystem with ordered data mode. Opts: (null)
Oct 13 16:10:25 kernel: [   79.146508] EXT4-fs (sda12): mounted filesystem with ordered data mode. Opts: (null)
Oct 13 16:10:25 kernel: [   79.214300] EXT4-fs (sda12): mounted filesystem with ordered data mode. Opts: (null)
Oct 13 16:10:25 kernel: [   79.348066] NTFS volume version 3.1.
Oct 13 16:10:25 kernel: [   79.348078] NTFS-fs warning (device sda2): load_system_files(): Unsupported volume flags 0x4000 encountered.
Oct 13 16:10:25 kernel: [   79.348088] NTFS-fs error (device sda2): load_system_files(): Volume has unsupported flags set.  Mounting read-only.  Run chkdsk and mount in Windows.
Oct 13 16:10:25 kernel: [   79.525630] NTFS volume version 3.1.
Oct 13 16:10:25 kernel: [   79.525633] NTFS-fs warning (device sda2): load_system_files(): Unsupported volume flags 0x4000 encountered.
Oct 13 16:10:25 kernel: [   79.525636] NTFS-fs error (device sda2): load_system_files(): Volume has unsupported flags set.  Mounting read-only.  Run chkdsk and mount in Windows.
Oct 13 16:10:25 kernel: [   79.700077] NTFS volume version 3.1.
Oct 13 16:10:25 kernel: [   79.922051] NTFS volume version 3.1.
Oct 13 16:10:26 kernel: [   80.172564] NTFS volume version 3.1.
Oct 13 16:10:26 kernel: [   80.438950] NTFS volume version 3.1.
Oct 13 16:10:26 kernel: [   80.783073] EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: (null)
Oct 13 16:10:26 kernel: [   80.846531] EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: (null)
Oct 13 16:10:26 kernel: [   80.943104] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
Oct 13 16:10:26 kernel: [   80.999517] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
Oct 13 16:10:28 check-missing-firmware: installing firmware package /media/firmware/firmware-iwlwifi_0.40_all.deb
Oct 13 16:10:30 kernel: [   84.165087] cfg80211: Calling CRDA to update world regulatory domain
Oct 13 16:10:30 kernel: [   84.168246] Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
Oct 13 16:10:30 kernel: [   84.168248] Copyright(c) 2003-2011 Intel Corporation
Oct 13 16:10:30 kernel: [   84.168391] iwlwifi 0000:03:00.0: setting latency timer to 64
Oct 13 16:10:30 kernel: [   84.168433] iwlwifi 0000:03:00.0: pci_resource_len = 0x00002000
Oct 13 16:10:30 kernel: [   84.168435] iwlwifi 0000:03:00.0: pci_resource_base = ffffc90000674000
Oct 13 16:10:30 kernel: [   84.168437] iwlwifi 0000:03:00.0: HW Revision ID = 0x34
Oct 13 16:10:30 kernel: [   84.168747] iwlwifi 0000:03:00.0: irq 48 for MSI/MSI-X
Oct 13 16:10:30 kernel: [   84.168858] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Wireless-N 1030 BGN, REV=0xB0
Oct 13 16:10:30 kernel: [   84.169017] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
Oct 13 16:10:30 kernel: [   84.185947] iwlwifi 0000:03:00.0: device EEPROM VER=0x716, CALIB=0x6
Oct 13 16:10:30 kernel: [   84.185948] iwlwifi 0000:03:00.0: Device SKU: 0X150
Oct 13 16:10:30 kernel: [   84.185950] iwlwifi 0000:03:00.0: Valid Tx ant: 0X1, Valid Rx ant: 0X3
Oct 13 16:10:30 kernel: [   84.185963] iwlwifi 0000:03:00.0: Tunable channels: 13 802.11bg, 0 802.11a channels
Oct 13 16:10:30 kernel: [   84.188749] iwlwifi 0000:03:00.0: firmware: agent loaded iwlwifi-6000g2b-6.ucode into memory
Oct 13 16:10:30 kernel: [   84.188756] iwlwifi 0000:03:00.0: loaded firmware version 18.168.6.1
Oct 13 16:10:30 kernel: [   84.188984] Registered led device: phy0-led
Oct 13 16:10:30 kernel: [   84.191571] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
Oct 13 16:10:30 net/hw-detect.hotplug: Detected hotpluggable network interface wlan0
Oct 13 16:10:31 check-missing-firmware: /dev/.udev/firmware-missing does not exist, skipping
Oct 13 16:10:31 check-missing-firmware: no missing firmware in /dev/.udev/firmware-missing /run/udev/firmware-missing
Oct 13 16:10:31 kernel: [   85.393879] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
Oct 13 16:10:31 kernel: [   85.400510] iwlwifi 0000:03:00.0: Radio type=0x2-0x2-0x1
Oct 13 16:10:31 kernel: [   85.490515] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
Oct 13 16:10:31 kernel: [   85.497110] iwlwifi 0000:03:00.0: Radio type=0x2-0x2-0x1
Oct 13 16:10:31 kernel: [   85.588371] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Oct 13 16:10:31 kernel: [   85.652838] atl1c 0000:04:00.0: irq 49 for MSI/MSI-X
Oct 13 16:10:31 kernel: [   85.737810] ADDRCONF(NETDEV_UP): eth0: link is not ready
Oct 13 16:10:32 check-missing-firmware: /dev/.udev/firmware-missing does not exist, skipping
Oct 13 16:10:32 check-missing-firmware: no missing firmware in /dev/.udev/firmware-missing /run/udev/firmware-missing
Oct 13 16:10:32 main-menu[535]: /dev/sda10 on /media failed: No such device
Oct 13 16:10:32 main-menu[535]: (process:4536): umount: can't umount /media: Invalid argument
Oct 13 16:10:32 main-menu[535]: (process:4536): mount: mounting /dev/sda10 on /media failed: No such device
Oct 13 16:10:32 main-menu[535]: (process:4536): mount: can't find /media in /etc/fstab
Oct 13 16:10:32 main-menu[535]: (process:4536): umount: can't umount /media: Invalid argument
Oct 13 16:10:32 main-menu[535]: (process:4536): mount: can't find /media in /etc/fstab
Oct 13 16:10:32 main-menu[535]: (process:4536): mount: can't find /media in /etc/fstab
Oct 13 16:10:32 main-menu[535]: (process:4536): umount: can't umount /media: Invalid argument
Oct 13 16:10:32 main-menu[535]: (process:4536): mount: can't find /media in /etc/fstab
Oct 13 16:10:32 main-menu[535]: (process:4536): mount: mounting /dev/sda7 on /media failed: No such device
Oct 13 16:10:32 main-menu[535]: (process:4536): umount: can't umount /media: Invalid argument
Oct 13 16:10:32 main-menu[535]: (process:4536): mount: mounting /dev/sda7 on /media failed: No such device
Oct 13 16:10:32 main-menu[535]: (process:4536): mount: mounting /dev/sdb1 on /media failed: Device or resource busy
Oct 13 16:10:32 main-menu[535]: (process:4536): umount: can't umount /media: Invalid argument
Oct 13 16:10:32 main-menu[535]: (process:4536): mount: mounting /dev/sdb1 on /media failed: Device or resource busy
Oct 13 16:10:33 main-menu[535]: DEBUG: resolver (libgcc1): package doesn't exist (ignored)
Oct 13 16:10:33 main-menu[535]: INFO: Menu item 'netcfg' selected
Oct 13 16:05:45 check-missing-firmware: Check on /loop for firmware
Oct 13 16:05:46 kernel: [   94.333541] UDF-fs: warning (device sda): udf_fill_super: No partition found (1)
Oct 13 16:05:46 kernel: [   94.414866] FAT-fs (sda): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[...]
Oct 13 16:05:50 kernel: [   98.212169] UDF-fs: warning (device sda8): udf_fill_super: No partition found (1)
Oct 13 16:05:50 kernel: [   98.294462] FAT-fs (sda8): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
Oct 13 16:05:50 main-menu[550]: gument
Oct 13 16:05:50 main-menu[550]: (process:4539): umount: can't umount /media: Invalid argument
Oct 13 16:05:50 main-menu[550]: (process:4539): mount: mounting /dev/sda6 on /media failed: Invalid argument
Oct 13 16:05:50 main-menu[550]: (process:4539): mount: mounting /dev/sda7 on /media failed: Invalid argument
Oct 13 16:05:50 main-menu[550]: (process:4539): umount: can't umount /media: Invalid argument
Oct 13 16:05:50 main-menu[550]: (process:4539): mount: mounting /dev/sda7 on /media failed: Invalid argument
Oct 13 16:05:50 main-menu[550]: (process:4539): mount: mounting /dev/sda8 on /media failed: Invalid argument
[...]
Oct 13 16:05:50 main-menu[550]: (process:4539): umount: can't umount /media: Invalid argument
Oct 13 16:05:50 main-menu[550]: (process:4539): mount: mounting /dev/sda6 on /media failed: Invalid argument
Oct 13 16:05:50 main-menu[550]: (process:4539): mount: mounting /dev/sda7 on /media failed: Invalid argument
Oct 13 16:05:50 main-menu[550]: (process:4539): umount: can't umount /media: Invalid argument
Oct 13 16:05:50 main-menu[550]: (process:4539): mount: mounting /dev/sda7 on /media failed: Invalid argument
Oct 13 16:05:50 main-menu[550]: (process:4539): mo
Oct 13 16:05:50 kernel: [   98.336276] UDF-fs: warning (device sda8): udf_fill_super: No partition found (1)
Oct 13 16:05:50 kernel: [   98.442298] FAT-fs (sda8): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[...]
Oct 13 16:06:01 kernel: [  109.257009] UDF-fs: warning (device sda9): udf_fill_super: No partition found (1)
Oct 13 16:06:01 kernel: [  109.378443] FAT-fs (sda9): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
Oct 13 16:06:01 main-menu[550]: unt: mounting /dev/sda8 on /media failed: Invalid argument
Oct 13 16:06:01 main-menu[550]: (process:4539): umount: can't umount /media: Invalid argument
Oct 13 16:06:01 main-menu[550]: (process:4539): mount: mounting /dev/sda8 on /media failed: Invalid argument
Oct 13 16:06:01 main-menu[550]: (process:4539): mount: mounting /dev/sda9 on /media failed: Invalid argument
[...]
Oct 13 16:06:01 main-menu[550]: (process:4539): mount: mounting /dev/sda8 on /media failed: Invalid argument
Oct 13 16:06:01 main-menu[550]: (process:4539): mount: mounting /dev/sda9 on /media failed: Invalid argument
Oct 13 16:06:01 main-menu[550]: (process:4539): umount: can't umount /media: Invalid argument
Oct 13 16:06:01 main-menu[550]: (process:4539): mount: mounting /dev/sda9 on /media failed:
Oct 13 16:06:01 kernel: [  109.411110] UDF-fs: warning (device sdc1): udf_fill_super: No partition found (1)
Oct 13 16:06:01 kernel: [  109.522629] FAT-fs (sdc1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
Oct 13 16:06:01 kernel: [  109.555593] UDF-fs: warning (device sdc1): udf_fill_super: No partition found (1)
Oct 13 16:06:01 kernel: [  109.722349] FAT-fs (sdc1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
Oct 13 16:06:01 kernel: [  109.776869] Floppy drive(s): fd0 is 1.44M
Oct 13 16:06:04 kernel: [  112.790625] floppy0: no floppy controllers found
Oct 13 16:06:06 kernel: [  114.098604] UDF-fs: warning (device sda): udf_fill_super: No partition found (1)
Oct 13 16:06:06 kernel: [  114.197151] FAT-fs (sda): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[...]
Oct 13 16:06:10 kernel: [  118.426046] UDF-fs: warning (device sda9): udf_fill_super: No partition found (1)
Oct 13 16:06:10 kernel: [  118.524261] FAT-fs (sda9): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
Oct 13 16:06:10 main-menu[550]:  Invalid argument
Oct 13 16:06:10 main-menu[550]: (process:4539): mount: mounting /dev/sdb1 on /media failed: Device or resource busy
Oct 13 16:06:10 main-menu[550]: (process:4539): umount: can't umount /media: Invalid argument
Oct 13 16:06:10 main-menu[550]: (process:4539): mount: mounting /dev/sdb1 on /media failed: Device or resource busy
Oct 13 16:06:10 main-menu[550]: (process:4539): mount: mounting /dev/sdc1 on /media failed: Invalid argument
[...]
Oct 13 16:06:10 main-menu[550]: (process:4539): mount: mounting /dev/sda9 on /media failed: Invalid argument
Oct 13 16:06:10 main-menu[550]: (process:4539): mount: mounting /dev/sdb1 on /media failed: Device or resource busy
Oct 13 16:06:10 main-menu[550]: (process:4539): umount: can't umount /media: Invalid argument
Oct 13 16:06:10 kernel: [  118.565373] UDF-fs: warning (device sdc1): udf_fill_super: No partition found (1)
Oct 13 16:06:10 kernel: [  118.668515] FAT-fs (sdc1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[...]
Oct 13 16:06:21 kernel: [  129.441992] UDF-fs: warning (device sdc1): udf_fill_super: No partition found (1)
Oct 13 16:06:21 kernel: [  129.572750] FAT-fs (sdc1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
Oct 13 16:06:21 kernel: [  129.591318] Floppy drive(s): fd0 is 1.44M
Oct 13 16:06:24 kernel: [  132.608857] floppy0: no floppy controllers found
Oct 13 16:06:24 main-menu[550]: (process:4539): mount: mounting /dev/sdb1 on /media failed: Device or resource busy
Oct 13 16:06:24 main-menu[550]: (process:4539): mount: mounting /dev/sdc1 on /media failed: Invalid argument
Oct 13 16:06:24 main-menu[550]: (process:4539): umount: can't umount /media: Invalid argument
[...]
Oct 13 16:06:24 main-menu[550]: (process:4539): umount: can't umount /media: Invalid argument
Oct 13 16:06:24 main-menu[550]: (process:4539): mount: mounting /dev/sdc1 on /media failed: Invalid argument
Oct 13 16:06:24 main-menu[550]: (process:4539): mount: mounting /dev/fd0 on /media failed: No such file or directory
Oct 13 16:06:24 main-menu[550]: (process:45
Oct 13 16:06:25 kernel: [  133.267235] cfg80211: Calling CRDA to update world regulatory domain
Oct 13 16:06:25 kernel: [  133.270948] Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
Oct 13 16:06:25 kernel: [  133.270951] Copyright(c) 2003-2011 Intel Corporation
Oct 13 16:06:25 kernel: [  133.271124] iwlwifi 0000:03:00.0: setting latency timer to 64
Oct 13 16:06:25 kernel: [  133.271172] iwlwifi 0000:03:00.0: pci_resource_len = 0x00002000
Oct 13 16:06:25 kernel: [  133.271174] iwlwifi 0000:03:00.0: pci_resource_base = ffffc90000674000
Oct 13 16:06:25 kernel: [  133.271176] iwlwifi 0000:03:00.0: HW Revision ID = 0x34
Oct 13 16:06:25 kernel: [  133.271512] iwlwifi 0000:03:00.0: irq 48 for MSI/MSI-X
Oct 13 16:06:25 kernel: [  133.271623] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Wireless-N 1030 BGN, REV=0xB0
Oct 13 16:06:25 kernel: [  133.271781] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
Oct 13 16:06:25 kernel: [  133.288724] iwlwifi 0000:03:00.0: device EEPROM VER=0x716, CALIB=0x6
Oct 13 16:06:25 kernel: [  133.288725] iwlwifi 0000:03:00.0: Device SKU: 0X150
Oct 13 16:06:25 kernel: [  133.288727] iwlwifi 0000:03:00.0: Valid Tx ant: 0X1, Valid Rx ant: 0X3
Oct 13 16:06:25 kernel: [  133.288739] iwlwifi 0000:03:00.0: Tunable channels: 13 802.11bg, 0 802.11a channels
Oct 13 16:06:25 kernel: [  133.290779] iwlwifi 0000:03:00.0: firmware: agent aborted loading iwlwifi-6000g2b-6.ucode (not found?)
Oct 13 16:06:25 kernel: [  133.292914] iwlwifi 0000:03:00.0: firmware: agent aborted loading iwlwifi-6000g2b-5.ucode (not found?)
Oct 13 16:06:25 kernel: [  133.292956] iwlwifi 0000:03:00.0: no suitable firmware found!
Oct 13 16:06:26 check-missing-firmware: /dev/.udev/firmware-missing does not exist, skipping
Oct 13 16:06:26 check-missing-firmware: missing firmware files (iwlwifi-6000g2b-6.ucode iwlwifi-6000g2b-5.ucode) for iwlwifi iwlwifi


Reply to: